Chapter 9 ALLBASE/SQL Error Messages: 11007-22540

Invalid module/owner name. (DBERR 11007)

The module or owner name you specified in the preprocessor invocation line was invalid.

Invoke the preprocessor again, specifying a valid module or owner name. Refer to the ALLBASE/SQL Reference Manual for naming conventions.

Too many routines within subprogram. (DBERR 11012)

You have exceeded the maximum number of routines allowable in a subprogram.

Modify your subprogram to include 100 or fewer routines and re-preprocess your program.

Cannot get language information. See System Administrator. (DBERR 11013)

Native language support error occurred. Most likely language environment file is not accessible.

Verify that native language support is properly installed.

Cannot get Asian language information. (DBERR 11014)

Native language support error occurred. Most likely language environment file is not accessible.

Verify that native language support is properly installed.

Internal error. Could not truncate line correctly. (DBERR 11015)

Native language support error occurred during truncation of source line.

Verify that native language support is properly installed.

Internal error. Cannot upshift characters in invocation line. (DBERR 11016)

Native language support error occurred while processing the invocation line.

Verify that native language support is properly installed.

Out of preprocessor symbol table memory. (DBERR 11017)

You used too many host variables or cursor names.

Reduce the number of host variables or cursor names or use subprograms.

File ! open error. (Paserr 692). (DBERR 11018)

You tried to open a file with a Pascal statement.

Check the status of the file named in the error message. For information on the Pascal error message, refer to the Pascal Reference Manual.

Insufficient heap area to allocate variable. (Paserr 600) (DBERR 11019)

The heap memory space is exhausted.

Allocate more heap space.

Unexpected internal error. (DBERR 11020)

An unexpected internal error was detected.

Record as much information as possible and contact your HP Service Representative or Response Center.

Statement not supported when dynamic-only option is specified. (DBERR 11021)

You specified an SQL statement which is not supported when preprocessing with the dynamic-only option.

Modify the SQL statement, or perform preprocessing without the dynamic-only option.

Statement supported only when dynamic-only option is specified. (DBERR 11022)

You specified an SQL statement which is supported only when preprocessing with the dynamic-only option.

Modify the SQL statement, or perform preprocessing with the dynamic-only option.

Host variable declaration larger than maximum DBE name length. (DBERR 11023)

You specified a host variable with a declared length greater than the maximum DBEnvironment name length.

Specify a host variable with a declared length less than or equal to the maximum DBEnvironment name length. Consult the ALLBASE/SQL Reference Manual for the maximum DBEnvironment name length.

Host variable declaration too large for this usage. (DBERR 11024)

You specified a host variable with a declared length greater than the maximum allowed length.

Specify a host variable with a declared length less than or equal to the maximum allowed length. Consult the ALLBASE/SQL Reference Manual for the maximum allowed length.

Character string too large for this usage. (DBERR 11025)

You specified a character string which is longer than the maximum allowed length.

Specify a character string which is less than or equal to the maximum allowed length. Consult the ALLBASE/SQL Reference Manual for the maximum allowed length.

DYNAMIC option may be specified only once. (DBERR 11026)

The preprocessor was invoked with the DYNAMIC option specified more than once in the command line.

Invoke the preprocessor specifying the DYNAMIC option only once.

DBEnvironment name not allowed for DYNAMIC preprocessing. (DBERR 11028)

You specified a DBEnvironment name when invoking the preprocessor with the DYNAMIC option.

Omit the DBEnvironment name when invoking the preprocessor with the DYNAMIC option.

No ending END-EXEC before end of file. (DBERR 11200)

SQLIN contains an SQL statement that is preceded by EXEC SQL but is not followed by END-EXEC.

Insert END-EXEC in the appropriate location in SQLIN and process SQLIN again.

Missing or incorrect PROGRAM-ID paragraph. (DBERR 11201)

The preprocessor did not find a PROGRAM-ID in SQLIN.

Insert a PROGRAM-ID label in SQLIN or check your spelling on the existing label and re-preprocess your program.

Host variable must have USAGE COMPUTATIONAL. (DBERR 11202)

The declaration for the StartIndex or NumberOfRows value in a BULK command is invalid.

Declare the host variable as PIC S9(4) or PIC S9(9) and re-preprocess your program.

Host variable must not be a table. (DBERR 11203)

You specified a host variable name in an SQL statement that is declared as a table but should be declared as an elementary data item.

Correct the host variable declaration and re-preprocess your program.

Host variable must be a one-dimensional table. (DBERR 11204)

The declaration of the first host variable you named in the INTO clause of a BULK SELECT, BULK FETCH, or BULK INSERT statement is invalid.

Declare the host variable as follows, and use the ARRAY-NAME in the INTO clause:

        01 ARRAY-NAME.
        05 ROW-NAME           OCCURS n TIMES.
           10 COLUMN1-NAME    Valid data clause.
           .
           .
           .
           10 COLUMNn-NAME    Valid data clause.

Syntax error in COPY statement. (DBERR 11206)

A syntax error was encountered in a COBOL COPY statement.

Verify that the COPY statement follows conventions specified in the HP COBOL II/XL Reference Manual.

Syntax error in REPLACE statement. (DBERR 11207)

A syntax error was encountered in a COBOL REPLACE statement.

Verify that the REPLACE statement follows conventions specified in the HP COBOL II/XL Reference Manual.

COPY not allowed within another COPY statement. (DBERR 11208)

The keyword COPY was encountered within another COPY statement. COPY is a keyword which can only be used to specify the start of a COPY statement.

Terminate previous COPY statement before beginning another COPY statement. Verify that the COPY statement follows conventions specified in the HP COBOL II/XL Reference Manual.

Copy file open error. (DBERR 11209)

A system error was encountered while attempting to open the specified copy file.

Check the spelling of the copy file. Verify that the specified copy file exists. Verify that the specified group and account exist. Verify that appropriate read privileges exist for the specified copy file.

Statement not properly terminated; period expected. (DBERR 11210)

A terminating period for a COBOL statement was expected but not found.

Verify that the COBOL statement follows conventions specified in the HP COBOL II/XL Reference Manual.

MESSAGE: No ending '==' before end of line. (DBERR 11211)

A REPLACE/REPLACING parameter literal was not properly terminated before the end of the line or end of the file. No ending '==' was found to match a beginning '==' literal delimiter.

Verify that the REPLACE/REPLACING parameter literal is terminated by a '==' on the same line as the beginning '==' literal delimiter. If the parameter literal is longer than a single line, verify that the line is properly continued following conventions specified in the HP COBOL II/XL Reference Manual.

Error in continuation of parameter. (DBERR 11212)

A REPLACE/REPLACING parameter literal was not properly continued on the following line.

Verify that the REPLACE/REPLACING parameter literal is continued following conventions specified in the HP COBOL II/XL Reference Manual.

Too many characters. (DBERR 11213)

The copy file specification exceeds the allowed maximum number of characters.

Change the copy file specification so that it does not exceed the maximum number of characters for a valid file name.

Illegal continuation line, ignored. (DBERR 11300)

The statement contains an illegal continuation character. The current line is ignored.

Specify a valid continuation character in the source file.

Statement too long for FORTRAN. (DBERR 11301)

Your FORTRAN statement included more than the maximum number of continuation lines allowable.

Modify your FORTRAN statement to include no more than 19 continuation lines (20 lines if you add an initial line) and re-preprocess your program.

Type must be array [1..n] of record. (DBERR 11400)

Your BULK command did not contain the required host variable type.

Refer to the ALLBASE/SQL Pascal Application Programming Guide for additional information on host variables.

Type must be a structure array. (DBERR 11500)

The host variable used in your bulk command was not a structure array.

Modify the DECLARE section of your program so that the host variable is a structure array.

The host variable must be an array of CHAR. (DBERR 11502)

The host variable you specified in the DECLARE section of your program was not an array of char.

Modify the DECLARE section of your program so that the host variable is a char array.

Illegal host variable array type. (DBERR 11503)

The host variable array you specified in the DECLARE section of your program was not a char type or a structure.

Modify the DECLARE section and re-preprocess your program.

Illegal type for structure field. (DBERR 11504)

The host variable you specified in the DECLARE section of your program had an invalid field type.

Modify the DECLARE section of your program specifying a valid field type.

Label must start with alphabetic character. (DBERR 11506)

A label in a WHENEVER statement started with a number or some other non-alphabetic character.

Change the label to start with an alphabetic character.

Nested structures disallowed in host variables. (DBERR 11507)

A host variable was declared in the DECLARE section as a structure with a structure as one of its fields.

Modify the DECLARE section and re-preprocess your program.

The host variable must be an array type with minimum size 1. (DBERR 11508)

You specified a host variable for sqlvarbinary without an array specification or with an array size less than 1.

Specify the sqlvarbinary host variable with an array size greater than zero.

User does not have authority to wrap DBE. (DBERR 13130)

You are not the creator of the original DBEnvironment or the superuser (HP-UX) or a system administrator (MPE/iX).

Only the original DBEnvironment creator or superuser (HP-UX) or system administrator (MPE/iX) can use the WRAPDBE command.

Log file list contains non-existing log file. (DBERR 13131)

You specified a log file(s) that could not be found or opened on the system.

Check the list of log files specified and determine if they are actually on the system. If so, check the security on the log files.

Log file list contains duplicates. (DBERR 13132)

When entering the WRAPDBE command, you specified the same log file more than once.

Check the list of log files and reenter the new list with no duplicates.

DBEFile does not belong to specified DBEFileSet. (DBERR 13153)

The specified DBEFile does not belong to the specified DBEFileSet as required by the requested function.

Check the specified DBEFile and DBEFileSet.

DBCore could not find free page buffer. (DBERR 13261)

Due to the number of current users, DBCore was unable to find free page buffer space. CAUTION: Transaction not necessarily rolled back.

Try your transaction again later. You can lock your table explicitly using the LOCK TABLE statement to decrease the size of page buffers required or use the SQLUtil ALTDBE command to allocate more buffer space. If the problem persists, record as much information as possible and contact your HP Service Representative or Response Center.

DBCore internal error !. (DBERR 13262) Please record the above message including both numbers.

An internal error caused your query to be terminated.

Record as much information as possible and contact your HP Service Representative or Response Center.

The log directory is full. (DBERR 13310).

The log directory allows for 34 log ids (single log names or pairs of log names in DUAL LOG mode). Any attempt to add the 35th log will fail. Note that this error can happen during ADDLOG or during SETUPRECOVERY In SQLUtil. The latter also adds a log to the log directory.

Check the log directory (use the SHOWLOG command for that purpose) to see if there were any logs that you could have backed up that you did not. If so, use STORELOG to back up these logs. Now you have two options. If it was a direct ADDLOG, then maybe you do not need to ADDLOG any more.

or

If it was an implicit ADDLOG during SETUPRECOVERY, use the SQLUtil PURGELOG command to purge the backed up log files BEFORE attempting SETUPRECOVERY again.

Wrong number of log file names specified. (DBERR 13313)

The ADDLOG command expects either one file name in single logging mode or two file names in dual logging mode. You may have tried to enter more or less than the permitted number of names.

Check the logging mode and number of log names you specified.

DBEnvironment has already finished recovery. (DBERR 13317)

You issued a TerminateRecovery command, but recovery has already ended.

Eliminate the extra TerminateRecovery command.

Attempted ENDRECOVERY in an inconsistent state. (DBERR 13318)

You are trying to end recovery at a time before the DBEnvironment was consistent after a STOREONLINE operation. When you enable archive mode with the STOREONLINE command, an archive checkpoint record is written to the log file after the online backup is finished. This process can take some time, during which other DBEnvironment activity continues to be logged. You can only recover to a point beyond the archive checkpoint record.

Do not terminate recovery. Continue to apply more logs through RECOVERLOG at least until the archive checkpoint record is reached. At that time, ENDRECOVERY will be successful.

The specified file is not a log file. (DBERR 13319)

The log file name specified in response to RECOVERLOG is not an ALLBASE log file.

Specify the correct log file name.

The specified log file does not have the desired sequence number. (DBERR 13320)

You specified a file name with an inappropriate sequence number. During RECOVERLOG, the log manager expects log sequence numbers in order (starting with the number specified in the DBECon file of the online backup).

Specify the log file name with the correct sequence number.

SETUPRECOVERY is not done. (DBERR 13322)

You attempted a RECOVERLOG or ENDRECOVERY without first having done a SETUPRECOVERY.

Issue the SETUPRECOVERY command before the RECOVERLOG or ENDRECOVERY commands.

Log does not contain an archive checkpoint. (DBERR 13323)

An archive checkpoint was not written to the log file, so the log file cannot be used for rollforward recovery.

Refer to the ALLBASE/SQL Database Administration Guide for additional information on archive checkpoints, and to the ALLBASE/SQL Reference Manual for information on the BEGIN ARCHIVE and COMMIT ARCHIVE statements.

Archive mode was never enabled on this DBEnvironment. (DBERR 13324)

You attempted a SETUPRECOVERY on this DBEnvironment, but archive mode was never turned on.

Check the sequence of operations. Perhaps this log is a non-archival log, and has always been so. If that is the case, do not attempt rollforward recovery on this log.

Log mode specification should be SINGLE or DUAL. (DBERR 13325)

You entered an incorrect log mode in response to a prompt from SETUPRECOVERY in SQLUtil.

Response with either SINGLE or DUAL.

Specified log id is out of range. (DBERR 13326)

The specified log id is either < 1 or > 35 when you issued either the PURGELOG or STORELOG command.

Use the SHOWLOG command to get the appropriate log id.

SHOWLOG internal error in computing free log blocks. (DBERR 13331)

Internal corruption.

Record as much information as possible and contact your HP Service Representative or Response Center.

FORMAL Designator is Invalid. (DBERR 13338)

The group and account do not match.

Supply the correct MPE/iX group and account name.

SETUPRECOVERY has already been done (DBERR 13339)

You attempted a SETUPRECOVERY followed by either another SETUPRECOVERY or by a set of RECOVERLOG commands and then another SETUPRECOVERY.

Remove the extra SETUPRECOVERY command.

DBE in ARCHIVE mode. Cannot overwrite with NON ARCHIVE logging. (DBERR 13345)

STOREONLINE was attempted with NON_ARCHIVE logging option. However, the DBEnvironment is in archive mode. This cannot be done because NON_ARCHIVE logging can be done only if the DBE is in non-archive mode.

For NON_ARCHIVE logging, turn off the archive logging before doing STOREONLINE.

Build of file STORLIST failed because of duplicate file. (DBERR 13346)

Duplicate STORLIST file exists in the group where SQLUtil is used.

To find and delete STORLIST, do the following:

   :LISTFTEMP STORLIST
   :PURGE STORLIST

Execute the SQLUtil command again.

Deadlock detected. (DBERR 14024)

Deadlock was detected between your transaction and another. Your current transaction was rolled back.

Issue your command again.

Session terminated by DBA. (DBERR 14027)

Your session was terminated by a user with DBA capability.

Access the DBE again when the system is available.

No updates are allowed on a Wrapper DBE. (DBERR 14028)

You attempted to do an operation that would try to update a wrapper DBEnvironment. No updates are allowed once the DBEnvironment has been converted to a wrapper DBEnvironment.

Do not try to update the wrapper DBEnvironment.

Your current transaction was rolled back by DBCore. (DBERR 14029)

Your transaction was rolled back due to another error. An additional message will be returned.

Refer to the cause and action of the additional message.

DBCore shared memory access error. (DBERR 14031)

Unable to access DBCore shared memory segments. Your current transaction was rolled back.

Record as much information as possible and contact your HP Service Representative or Response Center.

DBCore shared memory overflow. (DBERR 14035)

There was not enough space in DBCore shared memory to complete the transaction. Your current transaction was rolled back.

Increase the number of run-time control block pages using the SQLUtil ALTDBE command and try your transaction again. If the problem persists, record as much information as possible and contact your HP Service Representative or Response Center.

DBCore shared memory allocation failed. (DBERR 14038)

ALLBASE ran out of space for runtime control blocks.

Use SQLUtil to increase the number of runtime control block pages allocated.

DBCore unable to allocate local heap space. (DBERR 14044)

The application may have too many cursors open at one time.

Close cursors as soon as they are no longer needed since they require a large amount of local heap space.

Log file corruption detected in DBCore. (DBERR 14045)

Warm start could not find a checkpoint in any log file.

Perform a roll forward recovery.

Log full. (DBERR 14046)

The log file is full. Your current transaction was rolled back.

Shut down the database and issue a START DBE NEWLOG statement.

Current clock lower than highest in log. (DBERR 14047)

The system clock was set forward incorrectly, used by one or more databases, and then reset backward.

or

The system clock was set backward incorrectly. To ensure that recovery works correctly, ALLBASE/SQL requires that the date/time of the current action is later than the date/time of the preceding action. If the date/time of the current action is earlier than the date/time of the previous action (as is the case when this message is returned), ALLBASE/SQL will not function until the date/time of the current action is later than the date/time of the previous action. For example, if the year 1990 is entered instead of 1989, the database system will wait for a year, unless the action below is followed.

Consult your system administrator for assistance in resetting the system clock.

Failed to start DBCORE. (DBERR 14052)

You are trying to use a command which causes the database to be started in single user mode, but the database is already being accessed by other users

Make sure all users are logged off the database before you issue the command that starts the database in single user mode.

File System Error in DBEnvironment. (DBERR 14056)

Internal error.

Record as much information as possible and contact your HP Service Representative or Response Center.

DBCore File Close error. (DBERR 14059)

ALLBASE was not able to close the file. File name may not be correct.

Supply the correct file name.

DBECon Error - File is invalid. (DBERR 14066)

The DBECon file name specified in the START DBE, START DBE NEW, or START DBE NEWLOG statement is invalid.

Refer to the ALLBASE/SQL Reference Manual for DBECon file naming conventions.

DBECon error - File System Error. (DBERR 14067)

Internal error.

Record as much information as possible and contact your HP Service Representative or Response Center.

Database already started in single user mode. (DBERR 14071)

You tried to initiate a multi-user session on a single user DBEnvironment.

Ask your database administrator to change the DBECon file user mode to MULTI.

Database already started in multi-user mode. (DBERR 14072)

You tried to issue a START DBE or START DBE NEWLOG statement when someone was already connected to the database.

Make sure that no one is currently connected to the DBEnvironment. The SQLMON OVERVIEW SESSION screen can be used to see who is connected to the DBEnvironment.

Attempted to connect to more than one DBEnvironment. (DBERR 14073)

You tried to connect to a second DBEnvironment while still connected to another DBEnvironment. Your current transaction was rolled back.

Issue a RELEASE statement to disconnect from the first DBEnvironment and then issue a START DBE or CONNECT statement for the second DBEnvironment.

DBCore internal error ! - Transaction rolled back. (DBERR 14074) Please record the above message including both numbers.

An internal error caused your current transaction to be rolled back.

Record as much information as possible and contact your HP Service Representative or Response Center.

DBCore internal error ! - Rollforward recovery required. (DBERR 14075) Please record the above message including both numbers.

An internal error may have caused the DBEnvironment to be corrupted. Your current transaction was rolled back.

Do not perform additional transactions at this time. Contact your database administrator for rollforward recovery on the DBEnvironment. Record as much information as possible and contact your HP Service Representative or Response Center.

No next log to switch to. (DBERR 14076)

There is no valid log file to change log to.

Use ADDLOG to create a new log file then try the CHANGELOG command again.

Log directory is empty. (DBERR 14081)

An internal error occurred when you executed the STORELOG command

or

an internal error occurred when you executed the PURGELOG command,

or

you specified an invalid logid.

Use the SQLUtil SHOWLOG command to verify the logid. If the log id is correct, record as much information as possible and contact your HP Service Representative or Response Center.

Log file cannot be purged - backup pending (DBERR 14082)

You attempted to use the PURGELOG command on a log file that has not been backed up.

Use the STORELOG command to store the log file, and then purge it.

Log file is not in use. (DBERR 14083)

Note that the STORELOG command operates in two modes - one in which the user may specify a log id and one in which the user does not. In the latter case, DBCore will simply scan the log directory looking for the oldest log ready to back up. This error will occur in the former case where DBCore will look for the specified slot number in the log directory (the log id is a subscript into the directory entries). If that slot is currently unoccupied, this error is generated.

Check the log id specified.

Log file is not ready to be backed up. (DBERR 14084)

You attempted to STORELOG the current log file.

The user must wait till this log is no longer current.

Transaction was externally aborted. (DBERR 14092)

The transaction was aborted by another user.

None.

Insufficient authorization for DBA operation. (DBERR 14101)

The user does not have the proper authorization.

Check the authorization and change if appropriate.

DBCORE version mismatch with session already started. (DBERR 14102)

DBCORE version does not match with the DBCORE for the session.

Check DBCORE versions.

Current log file cannot be purged. (DBERR 14103)

The file to be purged is in use.

Issue the SHOWLOG command in SQLUtil to inquire if the log file is in use.

New partition instance found, and the current SCR does not have any more slots. (DBERR 14200)

This typically happens on a system with a large number of partition numbers. Further, if this system has switched master- replicate roles with a number of other systems, it has a large number of non-empty partitions.

The transaction is aborted by ALLBASE/SQL but the application needs to terminate at this point. Issue a START DBE NEWLOG with a larger MAXPARTITIONS.

Multiple database environments updated in the same transaction. (DBERR 14201)

A transaction attempted to replicate logging against more than one database id.

Check the transaction logic.

Log full error due to warm standby log scan. (DBERR 14202)

Logging cannot be done because a log lock would be overwritten.

Remove the log lock to resume logging.

DBCore internal I/O error - ! (!). (DBERR 15047)

An unexpected file system write error occurred during a transaction. Your current transaction was rolled back.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description, and contact your system administrator to check for possible disk drive physical I/O problems.

DBCore internal I/O error - ! (!). (DBERR 15048)

An unexpected file system write error occurred during a transaction. Your current transaction was rolled back.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description, and contact your system administrator to check for possible disk drive physical I/O problems.

*** Cannot update DBECON file. (! !, !, !, !) (DBERR 20027)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

*** Cannot purge SQLMigrate log file (AASQLMIG). (! !, !, !) (DBERR 20029)

A file system error was encountered when trying to purge the file named AASQLMIG. This is a temporary file used by SQLMigrate. This file is located in the same group as the DBECon file.

Take the necessary steps to purge this file before attempting again the SQLMigrate command which caused this error.

Cannot purge existing user log file (! !, !, !).(DBERR 20031)

An error occurred while trying to purge a log file named in the DBECon file. It may not exist on the system where the migration is being performed.

Because the log file could not be purged, SQLMigrate did not attempt to execute the START DBE NEWLOG command. The migration has completed successfully, but you will not be able to use the DBEnvironment until you have run ISQL and issued a START DBE NEWLOG command.

*** Cannot purge DBECON file. (! !, !) (DBERR 20032)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot start DBCore. (RC !, !, !, !) (DBERR 20034)

An unexpected error occurred while trying to establish a single user session with the DBEnvironment.

Record as much information as possible and contact your HP Service Representative or Response Center.

*** DBCore error. (FNC !, RC !, !, !, !) (DBERR 20035)

An unexpected internal error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Unexpected INTERNAL error (!, !, !, !) (DBERR 20036)

An unexpected internal error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

*** Cannot open expanded DBECON file. (! !, !) (DBERR 20040)

An MPE/iX file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

*** Cannot close expanded DBECON file. (! !, !) (DBERR 20041)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot purge expanded DBECON file. (! !, !) (DBERR 20042)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot write to expanded DBECON file. (! !, !) (DBERR 20043)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot rename DBECON file to BBSQLMIG file. (! !, !) (DBERR 20044)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot allocate expanded DBECON file. (! !, !) (DBERR 20045)

A file system error was encountered. There probably is not enough extra disk space on your system.

Refer to the system administration manual. Try to create more free disk space before using SQLMigrate again.

*** Cannot open BBSQLMIG file. (! !, !) (DBERR 20046)

A file system error was encountered when trying to create a file named BBSQLMIG in the same directory as the DBECon file. It probably already exists.

Refer to the MPE/iX Error Message Manual, Volume 1. Remove any files named BBSQLMIG from the same directory as the DBECon file before using SQLMigrate again.

*** Cannot close BBSQLMIG file. (! !, !) (DBERR 20047)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot purge BBSQLMIG file. (! !, !) (DBERR 20048)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot write to BBSQLMIG file. (! !, !) (DBERR 20049)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot rename BBSQLMIG file to DBECON file. (! !, !) (DBERR 20050)

A file system error was encountered.

Refer to the system administration manual.

*** Illegal command. (DBERR 20051)

SQLMigrate did not recognize the command that was entered.

Use the HELP command or refer to the ALLBASE/SQL Database Administration Guide to determine the valid SQLMigrate commands.

Input too long. Maximum length is !. (DBERR 20052)

The total length of the input line exceeded the allowed limit.

Issue the command again.

*** Input limit reached. No semicolon found. (DBERR 20053)

SQLMigrate commands must be terminated with a semicolon. None was found in the input string submitted.

Issue the command again.

*** Unexpected semicolon found. (DBERR 20054)

A semicolon was found in the input string in an unexpected location. Semicolons are allowed either: 1) at the end of the command or 2) in the DBEnvironmentName, when the operating system file naming convention allows it.

Issue the command again without the illegal semicolon.

*** Unexpected end of input. (DBERR 20055)

An error was encountered trying to retrieve the next command.

Check the output and input to determine if all commands executed properly.

*** Illegal syntax. (DBERR 20056)

Command was entered incorrectly.

Issue the command again. You can use the HELP command to verify your syntax.

*** SQLMIGRATE log file (AASQLMIG) already exists. (DBERR 20070)

AASQLMIG, a temporary file used by SQLMigrate, already exists in the same location as the DBECON file. Another user is probably running SQLMigrate on another DBEnvironment at the same time.

Try again later.

*** Cannot create BBSQLMIG file. (! !, !) (DBERR 20080)

BBSQLMIG, a temporary file used by SQLMigrate, already exists in the same location as the DBECON file. Another user is probably running SQLMigrate on another DBEnvironment at the same time.

Try again later.

*** Invalid target version. Use the SHOW VERSIONS command. (DBERR 20200)

The release of SQLMigrate being used does not support the version that was specified in the last command.

Use the SHOW VERSIONS command to determine the valid versions that may be used with this release of SQLMigrate.

*** DBEnvironmentName is too long. Maximum length is !. (DBERR 20201)

A DBEnvironmentName is restricted to operating system file naming conventions.

Refer to the MPE/iX General User's Reference Manual for information on file naming conventions.

*** Cannot MIGRATE FORWARD to earlier version. (DBERR 20202)

A logic error was encountered in the command. The keyword FORWARD is only used when migrating an older version DBEnvironment to one that is compatible with a newer release of ALLBASE/SQL.

Either change the keyword FORWARD to BACKWARD, or change the target version. Issue the command again.

*** Cannot MIGRATE BACKWARD to later version. (DBERR 20203)

A logic error was encountered in the command. The keyword BACKWARD is only used when migrating a newer version DBEnvironment to one that is compatible with an older release of ALLBASE/SQL.

Either change the keyword BACKWARD to FORWARD, or change the target version. Issue the command again.

*** Cannot PREVIEW FORWARD to earlier version. (DBERR 20204)

A logic error was encountered in the command. The keyword FORWARD is only used when previewing an older version DBEnvironment to one that is compatible with a newer release of ALLBASE/SQL.

Either change the keyword FORWARD to BACKWARD, or change the target version. Issue the command again.

*** Cannot PREVIEW BACKWARD to later version. (DBERR 20205)

A logic error was encountered in the command. The keyword BACKWARD is only used when previewing a newer version DBEnvironment to one that is compatible with an older release of ALLBASE/SQL.

Either change the keyword BACKWARD to FORWARD, or change the target version. Issue the command again.

*** DBEnvironment is already compatible with target version. (DBERR 20206)

The version of the DBEnvironment is already the same as the target version of the command.

If the target version was incorrectly specified, modify it and issue the command again.

*** Existing DBEnvironment not supported by SQLMigrate (DBERR 20207)

The release of SQLMigrate being used does not support migrations for the DBEnvironment specified in the command.

Contact your HP Service Representative or Response Center to determine if another release of SQLMigrate is available that will migrate your DBEnvironment.

*** DBEnvironment version is not recognized by SQLMigrate. (!) (DBERR 20208)

The release of SQLMigrate being used does not recognize the version number of your DBEnvironment, and cannot support migrations for it.

Contact your HP Service Representative or Response Center to determine if another release of SQLMigrate is available that will migrate your DBEnvironment.

*** DBEFileName is too long. Maximum length is !. (DBERR 20209)

The allowable length for the DBEFileName was exceeded.

Issue the command again, using a valid DBEFileName.

*** SystemFileName name is too long. Maximum length is !. (DBERR 20210)

The allowable length for the SystemFileName was exceeded.

Issue the command again, using a valid SystemFileName.

*** Migration path is not supported by SQLMIGRATE (!,!).(DBERR 20211)

SQLMigrate can only be used for a migration path to/from the release of ALLBASE/SQL on which SQLMigrate came. The attempted migration was for a path that did not involve the current release of ALLBASE/SQL.

Specify a valid migration path.

Log full. (DBERR 20220)

The log file is full.

If you see this message, you should notify your HP Service Representative or Response Center, because a problem probably exists in SQLMIGRATE.

During the MIGRATE, PREVIEW, CREATE DBEFILE, and ADD DBEFILE commands, SQLMIGRATE "connects" to the DBEnvironment by performing a START DBE NEWLOG command using a temporary log file. On MPE/iX, the file is named "AASQLMIG" and is created in the same group as the DBECON file. On HP-UX, the file is named "/tmp/AASQLMIGxxxxxx", where "xxxxx" is a unique id for each SQLMIGRATE process.

SQLMIGRATE needs to create it's own log file for several reasons, but the most important ones are 1) the existing log file(s) may not be compatible with the newest release, and 2) the existing log file(s) may not have enough free space on them. SQLMIGRATE creates the log in non-archive mode (so it is circular), and tries to use it efficiently so that a log full condition does not occur.

As a workaround, you can increase the size of the temporary log file (the default size is 400 pages) by issuing one of the following before running SQLMIGRATE:

On MPE/iX:
   : setjcw MIGLOGSZ 1000
 
On HP-UX (csh):
   % setenv MIGLOGSZ 1000
 
On HP-UX (sh or ksh):
   $ MIGLOGSZ=1000
   $ export MIGLOGSZ

In the examples above, the size of the temporary log file will be 1000 pages. Set the MIGLOGSZ variable to the value needed to accomplish a migration for your DBEnvironment.

ERROR - DBEFileName already exists in !. (DBERR 20330)

A row exists in SYSTEM.DBEFILE which has a DBEFNAME that is the same as the DBEFileName that was specified.

Issue the CREATE DBEFILE statement again, using a different DBEFileName.

ERROR - DBEFILE size is too small. Minimum size is !. (DBERR 20335)

The "WITH PAGES = " parameter did not meet minimum requirements.

Issue the CREATE DBEFILE statement again, using a larger value in the "WITH PAGES = " parameter.

ERROR - DBEFILE size is too large. Maximum size is ! (DBERR 20336)

The "WITH PAGES = " parameter exceeded maximum requirements.

Issue the CREATE DBEFILE statement again, using a smaller value in the "WITH PAGES = " parameter.

ERROR - DBEFILE name cannot be partially or fully qualified. (DBERR 20337)

The DBEFileName you specified was qualified by an MPE/iX group or account.

Issue the command again with an unqualified DBEFileName.

ERROR - SystemFileName already exists. (DBERR 20340)

Either the SystemFileName already exists as a physical file, or a row exists in SYSTEM.DBEFILE which has a FILEID that is the same as the SystemFileName.

Use a different SystemFileName, and issue the CREATE DBEFILE statement again.

ERROR - DBEFileName has not been CREATED in !. (DBERR 20350)

You issued an ADD DBEFILE statement before a CREATE DBEFILE statement had been issued.

Issue the CREATE DBEFILE statement, and then issue the ADD DBEFILE command again.

ERROR - DBEFileName has already been ADDED to a DBEFILESET. (DBERR 20360)

The row for DBEFileName in SYSTEM DBEFILE indicates that the DBEFSNAME has already been assigned.

The name specified in the ADD DBEFILE statement was probably incorrect. Modify it, and issue the command again.

ERROR - User is not DBECreator. (DBERR 20518)

Only the DBECreator or the system manager is authorized to use SQLMigrate.

Contact someone having the proper capabilities to use SQLMigrate.

ERROR - Invalid DBECON file format detected. (DBERR 20520)

Migration is not supported for this DBEnvironment using SQLMigrate.

UNLOAD and LOAD your data to install another release of ALLBASE/SQL.

ERROR - Previous failed attempt to MIGRATE detected. (DBERR 20530)

SQLMigrate was used is the past to migrate the DBEnvironment, but the migration was unsuccessful.

Purge the DBEnvironment and restore the backup version before attempting migration again.

ERROR - Insufficient space in the SYSTEM DBEFileSet. (DBERR 22540) DBEFile(s) containing ! pages need to be added to the SYSTEM DBEFileSet before attempting the migration.

The space estimate calculated during the PREVIEW command indicates that more space is needed for the migration than is currently present in the SYSTEM DBEFileSet.

Issue a CREATE DBEFILE statement followed by an ADD DBEFILE statement to add space to the SYSTEM DBEFileSet.

If you are concerned about the amount of additional space being added, CREATE and ADD multiple small DBEFiles, rather than one large one. After the migration is complete, perform an UPDATE STATISTICS on SYSTEM.TABLE. Review SYSTEM.DBEFILE to determine the empty DBEFiles in the SYSTEM DBEFileset, and remove them. Remember to leave about 20% of the pages free for the temporary processing needs of ALLBASE/SQL.