Chapter 10 ALLBASE/SQL Error Messages 10934-20046

Semicolon expected. (DBERR 10934)

There was a semicolon missing on the specified line of your C or Pascal program.

Add the semicolon and re-preprocess your program.

Unmatched END DECLARE SECTION. (DBERR 10935)

You did not include a BEGIN DECLARE SECTION in your source file.

Add BEGIN DECLARE SECTION before your first host variable declaration and re-preprocess your program.

Syntax error. (DBERR 10936)

An unrecognized syntax error occurred.

Correct the syntax in either the line specified in the error message or the line immediately preceding or immediately following the specified line. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information.

Syntax error caused skip to end of DECLARE SECTION. (DBERR 10937)

An unrecognized syntax error occurred in the host variable declaration section.

Correct the syntax in either the specified line in the error message or the line immediately preceding or immediately following the specified line. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information.

This host variable was previously declared. (DBERR 10938)

You specified the same name for more than one host variable.

Either delete one occurrence of the variable or correct one of the host variables to specify a unique name and re-preprocess your program.

Table element must occur one or more times. (DBERR 10939)

You specified a table declaration in the DECLARE section with an invalid value in the OCCURS clause.

Specify an integer value greater than zero in the table declaration OCCURS clause.

Array lower bound may not exceed upper bound. (DBERR 10940)

The array lower bound was greater than the array upper bound.

Correct the host variable declare section specifying valid array bounds, and re-preprocess your program. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information.

Invalid STRING size. (DBERR 10941)

The size of the string you specified is invalid for a Pascal program.

Modify your Pascal program so that the string is from 1 through 32,767 bytes long, then re-preprocess your program.

Invalid size for variable of that type. (DBERR 10942)

The size you specified for the FORTRAN host variable is not valid for that type of host variable.

Modify the declaration of the host variable so that it is a valid size. Refer to the ALLBASE/SQL FORTRAN Application Programming Guide for additional information on host variables.

Include file open error. (DBERR 10943)

You encountered a system error while attempting to open the specified include file.

Verify that the specified include file exists; if so, check the spelling of the include file name. Verify that all components of the specified path exist. Verify that appropriate read privileges exist for the specified include file.

Unrecognized syntax encountered. Parse aborted. (DBERR 10944)

An unrecognized syntax error occurred. The preprocessor was unable to continue.

Correct the syntax in either the line specified in the error message or the line immediately preceding. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information.

Illegal type for record field. (DBERR 10945)

The host variable type you specified in the DECLARE section of your program was invalid.

Refer to the ALLBASE/SQL application programming guide for the language you are using for valid host variable types.

Preprocessor does not support this statement. (DBERR 10947)

You included an SQL statement which cannot be embedded in the language you are using.

Delete the SQL statement and re-preprocess your program.

Unrecognized WHENEVER action. (DBERR 10948)

The condition or action you specified in the WHENEVER clause is invalid or the label specified for a GOTO action is invalid.

Correct the syntax in your WHENEVER clauses and re-preprocess your program. Keep in mind that valid conditions are SQLWARNING, SQLERROR, and NOT FOUND. Valid actions are STOP, GOTO, and CONTINUE.

Undeclared host variable. (DBERR 10949)

The SQL statement you specified a host variable which was either not declared or was incorrectly declared in the host variable declaration section.

Either enter the host variable if it was not declared or correct it if it was entered incorrectly and re-preprocess your program.

Indicator variable type must be SQLIND. (DBERR 10950)

The host variable you used as an indicator variable in an SQL statement was not declared as SQLIND in the host variable declaration.

Either modify the SQL statement to use a host variable declared as SQLIND or modify the declaration of the host variable to be SQLIND and re-preprocess your program.

Stand-alone SELECT statement requires INTO clause. (DBERR 10951)

Your embedded SELECT statement did not include the required INTO clause which defines the host variables for holding rows returned to the application program.

Modify the SELECT statement to include the required INTO clause and re-preprocess your program. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Cannot connect to DBEnvironment. (DBERR 10953)

The DBEnvironment you specified does not exist

or

the DBEnvironment you specified is in use and the user mode is set to SINGLE

or

you do not have the required authority to access the DBEnvironment.

Check your spelling

or

wait until the DBEnvironment is not being accessed

or

contact your database administrator to obtain the required CONNECT authority.

Cannot begin transaction. (DBERR 10954)

A transaction could not begin. An additional message will be returned.

Refer to the cause and action of the additional message.

Cannot drop module. (DBERR 10955)

You do not have the required authority to drop the specified module

or

an additional message will be returned.

No action is necessary. You must either be the owner or the database administrator to drop a module

or

refer to the cause and action of the additional message.

Cursor name must be a single identifier. (DBERR 10956)

You attempted to qualify a cursor with an owner or module name.

Delete the cursor name qualification in the specified statement and re-preprocess your program.

Indicator variables not allowed in this statement. (DBERR 10957)

You specified an indicator variable in a statement that does not allow indicator variables.

Remove the indicator variable from the statement

or

verify that the host variables have the correct data types.

A query is already defined with this cursor name. (DBERR 10958)

You attempted to declare a cursor which was already declared.

Modify one occurrence of the DECLARE CURSOR statement to specify a unique cursor name and re-preprocess your program.

There is no declared query with this cursor name. (DBERR 10959)

The SQL statement referenced a cursor which had not been declared.

Insert a DECLARE CURSOR statement before referencing the cursor and re-preprocess your program.

Insufficient input host variables. (DBERR 10960)

You specified too few input host variables in the OPEN statement to cover the columns specified in the cursor declaration.

Make sure that there is a host variable listed for each column specified and re-preprocess your program.

Too many input host variables. (DBERR 10961)

You specified too many host variables in the OPEN statement for the number of columns specified in the cursor declaration.

Make sure that there is a column specified for each host variable listed and re-preprocess your program.

Command name must be a single identifier. (DBERR 10962)

You qualified a command name with the owner or module name.

Delete the command name qualification.

This command already used. (DBERR 10963)

You attempted to PREPARE a statement using a command name which has already been used in another PREPARE statement.

Modify one of the PREPARE statements to specify a unique command name and re-preprocess your program.

The host variable must be of type STRING or PAC. (DBERR 10964)

You specified host variables which were not of the string or packed array type.

Modify the DECLARE section of your host variable so that the host variable is of the string or packed array type. Refer to the ALLBASE/Pascal Application Programming Guide for additional information.

Character string is too long. (DBERR 10965)

A string literal you specified in a PREPARE or EXECUTE IMMEDIATE statement exceeded the maximum limit of 2048 characters.

Modify the command to specify a value within the valid limits.

No prepared query found by this command name. (DBERR 10966)

The EXECUTE statement contained a command name which was not prepared in the same subprogram unit.

Check your spelling. If the command name is correct, insert an appropriate PREPARE statement before the EXECUTE statement and re-preprocess your program.

Cannot open command with host variable parameters. (DBERR 10967)

You specified a host variable in your DECLARE CURSOR statement.

Remove the host variable from your DECLARE CURSOR statement and re-preprocess your program.

A cursor on a PREPAREd command is illegal for non-dynamic queries. (DBERR 10968)

The cursor you specified was associated with a PREPAREd dynamic query. A cursor with a non-dynamic query should be used.

Change the query to use a cursor associated with a non-dynamic query or change the query to a dynamic query. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information.

A cursor on a PREPAREd command is required for dynamic queries. (DBERR 10969)

The cursor you specified was not associated with a PREPAREd dynamic query. A cursor associated with a dynamic query should be used.

Change the query to use a cursor associated with a dynamic query or change the query to a non-dynamic query. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information.

Warnings when connecting to DBEnvironment. (DBERR 10970)

Additional messages will be returned.

Refer to the cause and action of the additional messages.

Warnings when beginning transaction. (DBERR 10971)

Additional messages will be returned.

Refer to the cause and action of the additional messages.

Fields of type SQLIND must follow non-SQLIND fields. (DBERR 10972)

Fields of type SQLIND cannot be the first field in a host variable record declaration nor immediately follow another SQLIND field.

Resequence the fields in the record declaration and check for missing or duplicated fields, then re-preprocess your program.

Host variable type must be integer. (DBERR 10973)

The host variable type you specified in your BULK command was invalid.

Declare the host variable as integer and then re-preprocess your program.

Too many INTO parameters found in bulk statement. (DBERR 10974)

You named more than three host variables in the INTO clause of a BULK FETCH or BULK SELECT statement. Preprocessing terminates and no module is stored.

Correct the INTO clause so that it contains at most three host variables: Buffer, StartIndex, and NumberOfRows and re-preprocess your program.

Illegal host variable type. (DBERR 10975)

The host variable type you specified was invalid.

Declare the host variable specifying a valid type. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information on host variable types.

Variable must be compatible with CHAR(n), n > 1. (DBERR 10976)

The declaration for a host variable you named in an SQLEXPLAIN, PREPARE, or EXECUTE statement is not valid.

Specify a valid type in the host variable declaration. Refer to the ALLBASE application programming guide for the language you are using for additional information.

ALLBASE/SQL preprocessor error. (DBERR 10977)

An error condition was detected by the preprocessor. Additional error messages will be returned.

Refer to the cause and action of the additional error messages.

ALLBASE/SQL statement parser error. (DBERR 10978)

An error condition was detected by the statement parser. Additional error messages will be returned.

Refer to the cause and action of the additional error messages.

No ending single quote before end of line. (DBERR 10982)

A string literal was not properly terminated before the end of the line or end of the file. No ending single quote was found to match a beginning single quote.

Verify that the string literal is terminated by an ending single quote on the same line as the beginning single quote. If the string literal is longer than a single line, verify that the line is properly continued following conventions specified in the ALLBASE/SQL application programming guide for the language you are using.

No ending double quote before end of line. (DBERR 10983)

A string literal was not properly terminated before the end of the line or end of the file. No ending double quote was found to match a beginning double quote.

Verify that the string literal is terminated by an ending double quote on the same line as the beginning double quote. If the string literal is longer than a single line, verify that the line is properly continued following conventions specified in the ALLBASE/SQL application programming guide for the language you are using.

Error in continuation of string literal. (DBERR 10984)

A string literal was not properly continued across lines.

Verify that the line continuation follows conventions specified in the ALLBASE/SQL application programming guide for the language you are using.

Heap allocation failed. (DBERR 10985)

The preprocessor was unable to obtain the additional memory it needed.

Try preprocessing your program later or reduce the size of the program.

Error while writing to file. (DBERR 10990)

An error occurred while the preprocessor was writing to a file.

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

Host variable type must be integer or short integer. (DBERR 10992)

The data type of the host variable is invalid.

Declare the host variable as an integer or a small integer.

Embedded savepoint requires a host variable. (DBERR 10993)

A host variable was not specified in your SAVEPOINT statement.

Modify your command specifying a valid host variable and re-preprocess your program. Refer to the ALLBASE/SQL Reference Manual for additional information on the SAVEPOINT statement.

Syntax error in option specification. (DBERR 10994)

A syntax error was encountered in a compiler option.

Verify that the specified compiler option follows conventions specified in the ALLBASE/SQL application programming guide for the language you are using.

Invalid array size. (DBERR 10995)

A string or array size you specified was greater than the maximum allowable.

Modify the declaration of the string or array so that the length is less than or equal to 32764 bytes.

Host variable buffer required. (DBERR 10996)

You did not specify a host variable buffer in the value field of the BULK INSERT statement.

Modify the command within your program to specify a host variable buffer in the value field and re-preprocess your program.

Output filename too long. (DBERR 10998)

The output filename you specified in the invocation string is greater than 9 bytes (excluding extensions)

or

if no output filename was specified, the input source file name (the default) is greater than 9 bytes (excluding extensions).

Reinvoke the preprocessor specifying an output filename containing less than or equal to 9 bytes (excluding extensions).

Preprocessor Internal Error (!). (DBERR 10999)

Unknown escape occurred in the preprocessor.

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

-d option may only be specified once. (DBERR 11000)

You specified the -d option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -d option only once.

-r option may only be specified once. (DBERR 11001)

You specified the -r option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -r option only once.

-s option may only be specified once. (DBERR 11002)

You specified the -s option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -s option only once.

-m option may only be specified once. (DBERR 11003)

You specified the -m option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -m option only once.

-o option may only be specified once. (DBERR 11004)

You specified the -o option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -o option only once.

Unrecognized option. Valid options are -d, -r, -s, -m, -o and -p. (DBERR 11005)

You specified an invalid option in the preprocessor invocation line. Valid options are -d, -r, -s, -m, -o and -p.

Invoke the preprocessor again, specifying one or more of the valid options. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information on preprocessor invocation.

-s option may not be used with any other option. (DBERR 11006)

You specified additional options in the preprocessor invocation line along with the -s option.

Invoke the preprocessor again, specifying the -s option as the only option if you want to run the preprocessor in syntax checking mode. Do not specify the -s option if you want to run the preprocessor in full preprocessing mode.

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.

-i option may only be specified once. (DBERR 11008)

You specified the -i option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -i option only once.

-p option may only be specified once. (DBERR 11009)

You specified the -p option more than once in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -p option only once.

-r option may not be used without the -d option. (DBERR 11010)

You specified the -r option without the -d option in the preprocessor invocation line.

Invoke the preprocessor again, specifying the -d option if you specify the -r option.

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 COBOL/HP-UX Language 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 COBOL/HP-UX Language 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 COBOL/HP-UX Language 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 all components of the specified path 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 COBOL/HP-UX Language Reference Manual.

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 COBOL/HP-UX Language 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 COBOL/HP-UX Language 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.

Message catalog not available - see system manager. (DBERR 12008)

The message catalog 'hpsqlcat' was not found in the /usr/lib/nls/n-computer directory.

See your system manager.

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.

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.

OMNIBACK/ALLBASE STORE on UX error. (DBERR 14093)

Any of the following could cause the problem: not able to read/open DBEFILE, not enough space, or DBEFILE to be restored is already existing.

The action depends on what is determined to be the cause. Note that ALLBASE/SQL no longer supports OMNIBACK as the backup routine for SQLUtil. Check that the DBEFILE to be stored can be opened/read. Check that there is enough space to restore on the disk. For RESTORE, check if the DBEFILE is already existing.

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 /usr/include/sys/errno.h file 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 /usr/include/sys/errno.h file for an error description, and contact your system administrator to check for possible disk drive physical I/O problems.

*** Installation error detected. Check permissions and owner. (DBERR 20013)

The permissions, owner, or group of /usr/bin/sqlmig are incorrect.

Change the attributes of /usr/bin/sqlmig so that the permission is 4555, the owner is hpdb, and the group is bin.

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

A file system error was encountered.

Refer to the /usr/include/sys/errno.h file for an error description.

*** Cannot purge log file /tmp/SQLMIG.(! !, !, !) (DBERR 20030)

A file system error was encountered when trying to purge the file named /tmp/SQLMIGxxxxxx. (The string xxxxxx is unique for each run of SQLMigrate.)

Take the necessary steps to purge this file before reattempting 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. The ownership or file mode of the log file, or the directory that contains the log file, may be incorrect.

Check that user hpdb (uid 27) has at least read and write permission to the directories that contain the database and log files. Check that all database and log files are owned by hpdb, and have a file mode of 600 (-rw- - - - - - -). If necessary, contact your system administrator. 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. (errno !) (DBERR 20040)

A file system error was encountered.

Refer to the system administration manual.

*** 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 /usr/include/sys/errno.h file. Remove any files named BBSQLMIG from the same directory as the DBECon file before using SQLMigrate again.