Chapter 9 ALLBASE/SQL Error Messages 4050-10933

ALLBASE/SQL internal error at !(!) (Node ! out of context). (DBERR 4050)

Internal error. The node in question is not a valid one in current context.

If you have performed a backward migration, the view or stored section that you are accessing needs to be dropped and recreated under the current release. If you continue to see this message, record as much information as possible and contact your HP Service Representative or Response Center.

ALLBASE/SQL internal error at ! (! ). (DBERR 4051)

Internal error.

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

ALLBASE/SQL internal error (! !). (DBERR 4053)

Internal error, possibly caused by the incorrect handling of installed sections after database migration.

Re-preprocess the application and install the new module into the migrated database.

ALLBASE/SQL internal error (! !). (DBERR 4054)

Internal error.

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

ALLBASE/SQL internal error (!,!,!,!,!). (DBERR 4059)

Internal error.

Record the file system error code returned and as much information as possible. Contact your HP Service Representative or Response Center.

ALLBASE/SQL shared memory allocation failed. (! !). (DBERR 4101)

An HP-UX file system error occurred.

Refer to the system administration manual.

ALLBASE/SQL unable to fork. (! !). (DBERR 4102)

An HP-UX error occurred.

Refer to the system administration manual.

ALLBASE/SQL unable to execute hpsqlproc. (! !). (DBERR 4103)

An HP-UX file system error occurred or you do not have hpsqlproc on the client node.

Refer to the system administration manual, reinstall ALLBASE/SQL if local access is desired, or use NETUtil to configure an AliasDB file for ALLBASE/NET remote access.

ALLBASE/SQL shared memory attachment failed. (! !). (DBERR 4104)

An HP-UX file system error occurred.

Refer to the system administration manual.

hpsqlproc process terminated prematurely. (DBERR 4105)

The process, hpsqlproc, has been terminated prematurely. (hpsqlproc is a process invoked whenever ISQL, the preprocessors, or application programs are executed.)

Issue your command or run your program again. If this problem persists, record as much information as possible and contact your HP Service Representative or Response Center.

Cannot get ALLBASE/SQL system pointer. (DBERR 4111)

Internal error.

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

Cannot set ALLBASE/SQL system pointer. (DBERR 4112)

Internal error.

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

Invalid JRB version is found. (DBERR 4118)

The application being run is linked to a newer version of ALLBASE than what is currently installed on your system.

The application needs to be relinked with the current version which is currently installed on your system, or a version of ALLBASE consistent with the application needs to be installed on your system. Contact your system administrator.

hpsqlproc shared memory attachment failed. (! !). (DBERR 4121)

An HP-UX file system error occurred.

Refer to the system administration manual.

hpsqlproc detected premature termination of application. (DBERR 4122)

ISQL, the preprocessor, or an application program terminated prematurely causing hpsqlproc to terminate. (hpsqlproc is a process invoked whenever ISQL, the preprocessors, or an application program is executed.)

If you were running an application program, check for a programming error. If it was not a programming error, record as much information as possible and contact your HP Service Representative or Response Center.

Back-end data segment increment failed. (! !). (DBERR 4127)

An HP-UX error occurred.

Refer to the /usr/include/sys/errno.h file for an error description. Record as much information as possible and contact your HP Service Representative or Response Center.

Back-end data segment decrement failed. (! !). (DBERR 4128)

An HP-UX error occurred.

Refer to the /usr/include/sys/errno.h file for an error description. Record as much information as possible and contact your HP Service Representative or Response Center.

ALLBASE/SQL internal error. (! !) (DBERR 4130)

Internal error.

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

ALLBASE/SQL internal error. (! !) (DBERR 4131)

Internal error.

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

ALLBASE/SQL internal error. (! !) (DBERR 4132)

Internal error.

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

ALLBASE/SQL internal error. (! !) (DBERR 4133)

Internal error.

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

ALLBASE/SQL internal error. (! !) (DBERR 4134)

Internal error.

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

ALLBASE/SQL already started. (! !) (DBERR 4150)

Internal error.

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

hpsqlproc unable to get a semaphore. (HP-UX errno !) (DBERR 4170)

The system limit on semaphores may have been reached.

Increase the values of the semmni and semmns system parameters. If the problem persists, refer to the /usr/include/sys/errno.h file for an error description, record as much information as possible, and contact your HP Service Representative or Response Center.

ALLBASE/SQL unable to post a semaphore. (HP-UX errno !) (DBERR 4171)

An HP-UX error occurred.

Refer to /usr/include/sys/errno.h file for an error description. Record as much information as possible and contact your HP Service Representative or Response Center.

hpsqlproc failed while waiting on a semaphore. (HP-UX errno !) (DBERR 4172)

An HP-UX error occurred.

Refer to /usr/include/sys/errno.h file for an error description. Record as much information as possible and contact your HP Service Representative or Response Center.

hpsqlproc failed to get attributes of a semaphore. (HP-UX errno !) (DBERR 4173)

An HP-UX error occurred.

Refer to /usr/include/sys/errno.h file for an error description. Record as much information as possible and contact your HP Service Representative or Response Center.

hpsqlproc failed to set attributes of a semaphore. (HP-UX errno !) (DBERR 4174)

An HP-UX error occurred.

Refer to /usr/include/sys/errno.h file for an error description. Record as much information as possible and contact your HP Service Representative or Response Center.

Multi-connect not supported using signal IPC. (DBERR 4175)

The front-end and back-end processes are communicating with signals, but multi CONNECT requires a fastipc environment. Fastipc is supported on HP-UX 7.08 and later.

Update HP-UX to a version that supports fastipc.

ALLBASE/SQL alignment error on column ! in buffer !. (DBERR 4200)

The formatting information on host variables was generated incorrectly.

Check the format node information in your application program. If the problem was not caused by a programming error, record as much information as possible and contact your HP Service Representative or Response Center.

Unrecognized command. (DBERR 8101)

The command name you entered does not exist or was entered incorrectly.

Use the SQLUtil HELP command or refer to the ALLBASE/SQL Database Administration Guide to obtain a list and description of valid SQLUtil commands.

Command not yet implemented. (DBERR 8102)

The command name you entered does not exist or was entered incorrectly.

Use the SQLUtil HELP command or refer to the ALLBASE/SQL Database Administration Guide to obtain a list and description of valid SQLUtil commands.

File '!' not found. (DBERR 8103)

The file name specified in the MOVEFILE or PURGEFILE command was entered incorrectly or does not exist.

Check your spelling. Use the HP-UX ls command to verify the existence of the specified file.

Re-typed maintenance word doesn't match. Maintenance word not changed. (DBERR 8111)

The maintenance word was not changed because SQLUtil was unsure what the new maintenance word should be.

Issue the SETDBEMAINT command.

Value must be in the range !..!. (DBERR 8115)

The value specified for one or more parameters of the ALTDBE is invalid.

Issue the ALTDBE command again, specifying valid numbers for following parameters: Number of Runtime Control Block Pages should be 17 to 128 pages; Number of Data Buffer Pages should a minimum of 15; Number of Log Buffer Pages should be 24 to 120 pages; and Max. Transactions should be 2 to 240 transactions.

Bad numeric input. (DBERR 8116)

You entered non-numeric input where numeric input was expected.

Issue the ALTDBE command again, specifying valid numbers.

Cannot open file. (! !). (DBERR 8118)

An HP-UX file system error occurred.

Refer to the system administration manual.

File '!' is not a DBEFile. (DBERR 8131)

The specified file is not a DBEFile.

Issue the command again, specifying a valid DBEFile.

File '!' not accessible. (! !). (DBERR 8132)

An HP-UX file system error occurred.

Refer to the system administration manual.

Internal error occurred. (! !). (DBERR 8133)

An HP-UX file system error occurred.

Refer to the system administration manual.

Open failed on DBECon file. (! !). (DBERR 8201)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Close failed on DBECon file. (! !). (DBERR 8202)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Read failed on DBECon file. (! !). (DBERR 8203)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Write failed on DBECon file. (! !). (DBERR 8204)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

STORE failed. (! !). (DBERR 8205)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

RESTORE failed. (! !). (DBERR 8206)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Operation not performed; illegal capability. (DBERR 8207)

You do not have the capability to perform the specified command.

Contact a user who has the required capability. Refer to the ALLBASE/SQL Database Administration Guide for additional information on SQLUtil.

Invalid DBECon file. (DBERR 8208)

The file you specified in the ALTDBE, MOVEFILE, or PURGEDBE command is not a DBECon file.

Check your spelling. Issue the command again, specifying a valid DBECon file.

GETINFO failed. (! !). (DBERR 8209)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Open failed on a DBEFile. (! !). (DBERR 8210)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Close failed on a DBEFile. (! !) (DBERR 8211)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Read failed on a DBEFile. (! !) (DBERR 8212)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Write failed on a DBEFile. (! !) (DBERR 8213)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Unable to access System Catalog due to error #!. (DBERR 8214)

You cannot access the System Catalog due to another error.

Refer to the cause and action of the additional error.

BUILD failed. (! !) (DBERR 8215)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file.

Permission denied. (DBERR 8216)

You tried to issue PURGEFILE with superuser but the DBEnvironment directory does not have correct permission.

Set the DBEnvironment directory correctly. Refer to the ALLBASE/SQL Database Administration Guide.

Specified DBEFile is not associated with specified DBEnvironment. (DBERR 8217)

The DBEFile you specified in the MOVEFILE command exists, but is not associated with the specified DBEnvironment.

Issue the command again, specifying the correct DBEnvironment

Internal error #!, detail #!. (DBERR 8219)

Internal error.

Record as much information as possible and contact your ALLBASE/SQL Service Representative or Response Center.

Not a valid ALLBASE/SQL DBEnvironment. (DBERR 8220)

You tried to access an HP IMAGE DBEnvironment through SQLUtil.

Use HPIUtil to access HP IMAGE DBEnvironments, and SQLUtil to access ALLBASE/SQL DBEnvironments.

Internal NLS error. (DBERR 8221)

The local language table corresponding to your language cannot be accessed, probably because the environment file or custdatatable file does not exist.

Contact your system administrator.

Message catalog not available - see system administrator. (DBERR 8222)

The message catalog file cannot be accessed, probably because it does not exist.

Contact your system administrator.

Invalid Syntax. (DBERR 8223)

The syntax of the command is invalid.

Refer to the ALLBASE/SQL Database Administration Guide for the correct syntax.

Integer overflow, maximum value = ! (DBERR 8224)

The integer value specified exceeds the maximum value.

Issue the command again with a valid integer value.

Backward migration is needed - use SQLMIGRATE. (DBERR 8225)

The release of the ALLBASE/SQL software does not match the version of the DBEnvironment.

Use the migration tool, SQLMigrate, to migrate the DBEnvironment backward to the proper version or use a newer release of the ALLBASE/SQL software.

Forward migration is needed - use SQLMIGRATE. (DBERR 8226)

The release of the ALLBASE/SQL software does not match the version of the DBEnvironment.

Use the migration tool, SQLMigrate, to migrate the DBEnvironment forward to the proper version or use an older release of the ALLBASE/SQL software.

DBEnvironment corrupted during previous migration. (DBERR 8227)

At some prior time, a migration attempt failed which corrupted the DBEnvironment in the process.

Restore the DBEnvironment from the backup.

Keyword required for this command. (DBERR 8229)

The command you entered requires a keyword for completion.

Enter an appropriate keyword as shown in the help message syntax for the command you entered.

Illegal input - invalid Unit or Keyword (DBERR 8231)

The responses to the maximum timeout or default timeout prompts of the ALTDBE command contain an incorrect unit or keyword.

Refer to the ALLBASE/SQL Database Administration Guide for the correct syntax of the ALTDBE command.

Index exceeds buffer size (DBERR 8232)

An SQLUtil internal error occurred.

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

Unknown option: ! (DBERR 8233)

The option specified is invalid.

Refer to the ALLBASE/SQL Database Administration Guide for the correct syntax.

Restorelog on device '!' failed. (DBERR 8234)

You specified an invalid input device when issuing a RESTORELOG command.

Check with your system administrator to obtain the correct device name.

No such user exists on system. (DBERR 8235)

The user name you specified in the RESTORE command does not exist.

Check your spelling and the HP-UX password file for legal names and enter the command again, specifying a valid name.

File name must be no more than ! bytes. (DBERR 8238)

File name is more than 256 characters.

Change the file name to have a maximum of 256 characters only.

No Log file name was specified. (DBERR 8249)

There is no log file name specified.

Please specify a log file name to convert to a wrapper DBEnvironment.

Cannot make DBEFile0 pseudo-mapped. (DBERR 8270)

You cannot convert DBEFile0 to a pseudo-mapped file.

No action required. If you wish, choose a different DBEFile for conversion, then issue the MOVEFILE command again.

Pseudo-mapped file exists in DBEnvironment. Cannot perform STOREONLINE. (DBERR 8271)

One or more DBEFiles within the DBEnvironment has the file access mode set to pseudo-mapped. The DBEnvironment must contain only mapped access files in order to use the STOREONLINE command.

Use the SQLUtil SHOWACCESS command to determine which files have pseudo-mapped access. If desired, change the access mode of each file from pseudo-mapped to mapped using the SQLUtil MOVEFILE command. Then reissue the STOREONLINE command.

Too many files, MAX = 128 files. (DBERR 8273)

Number of files exceeds the limit.

Keep the number of files to be within 128.

Too many files, MAX = 256 files. (DBERR 8274)

Number of files while restoring exceeds the limit.

Keep the number of files within 256 while restoring.

Chkpthlp Failed. (DBERR 8275)

Chkpthlp help command failed. Error occurred while flushing dirty pages from buffer pool.

Checkpoint process is not done. Try this again after giving the checkpoint command in ISQL.

Allbase Server Error. Invalid format node data type encountered.(DBERR 9126)

An incorrect node data type was used.

Change to a correct data type.

Internal error detected at run time. (DBERR 10000)

SQLCA is corrupt. The command was not executed.

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

Internal error detected at run time. (DBERR 10001)

SQLCA.SQLEXT is corrupt. The command was not executed.

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

More than one row qualifies for SELECT INTO. (DBERR 10002)

This form of the SELECT statement in a program can handle only single row query results.

Modify the program to use BULK SELECT or FETCH via a cursor.

EXECUTE IMMEDIATE invalid for a SELECT statement. (DBERR 10003)

You attempted to use a SELECT statement with an EXECUTE IMMEDIATE statement.

Use the DESCRIBE statement to distinguish between queries and non-queries. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information on handling dynamic queries.

EXECUTE IMMEDIATE invalid with host variable. (DBERR 10004)

The EXECUTE IMMEDIATE statement contained a host variable.

Eliminate the host variable from the EXECUTE IMMEDIATE statement in the source file and re-preprocess your program.

Too many columns in dynamic FETCH. (DBERR 10005)

There was not enough buffer space for the number of columns specified in the FETCH statement.

Reduce the number of columns specified in the select list or increase your buffer space, then re-preprocess your program.

Bad starting index. (DBERR 10006)

The value stored in the StartIndex host variable named in the INTO clause of a BULK SELECT, BULK FETCH, or BULK INSERT statement was either less than 1 or greater than the number of records the host variable array can accommodate. Control returns to the calling program, but the command is not executed.

Modify the source file constructs that assign a value to StartIndex to ensure that the value is from 1 through the maximum number of records that the host variable can accommodate and re-preprocess your program.

Bad row count. (DBERR 10007)

The value stored in the NumberOfRows host variable you named in the INTO clause of a BULK SELECT or BULK FETCH or the VALUES clause of a BULK INSERT statement is negative

or

the NumberOfRows plus the StartIndex minus 1 is greater than the number of rows the host variable array can accommodate.

Control returns to the calling program, but the command is not executed. No rows were retrieved or inserted.

Modify the source file constructs that assign a value to StartIndex to ensure that the value is from 1 through the maximum number of records that the host variable can accommodate and re-preprocess your program.

Message catalog not available - see system administrator. (DBERR 10008)

The message catalog may not be installed on your system.

Contact your system administrator.

DBEnvironment name too long. (DBERR 10010)

The DBEnvironment name specified at run-time exceeds the maximum of 128 bytes fully qualified.

Re-run your application, specifying a valid DBEnvironment name.

PREPARE invalid with host variable. (DBERR 10011)

The PREPARE statement contained a host variable.

Eliminate the host variable from the PREPARE statement in the source file and re-preprocess your program.

Internal error. Cannot get language information table for user's language. (DBERR 10012)

The character set table for the language you specified is not accessible.

Install NLS onto system.

Invalid number of columns specified in SQLDA.SQLN (DBERR 10013)

The number of columns you specified is less than zero, equal to zero, or greater than 1024.

Change the number of columns to a value greater than zero and less than 1025.

Invalid format array address in SQLDA.SQLFMTARR. (DBERR 10014)

SQLDA.SQLFMTARR is not pointing to the buffer.

Initialize SQLDA.SQLFMTARR.

Invalid version number specified in the SQLX TABLE parameter. (DBERR 10015)

An unknown TABLE.VERSION setting was passed to the SQLX interface.

Correct the TABLE.VERSION setting.

Invalid version number specified in the SQLX COLUMNS parameter. (DBERR 10016)

An unknown COLUMNS.VERSION setting was passed to the SQLX interface.

Correct the COLUMNS.VERSION setting.

Internal error. Could not allocate or deallocate the linear tree node. (DBERR 10017)

The linear tree node could not be allocated or deallocated. This may be caused by a memory resource failure.

Try your program again later. If the condition persists, then record as much information as possible and contact your HP Service Representative or Response Center.

Invalid setting in PARMCB.CODE_FLAG. (DBERR 10018)

An unknown PARMCB.CODE_FLAG setting was passed to the SQLX interface.

Correct the PARMCB.CODE_FLAG setting.

Invalid setting in PARMCB.SECTION.SECTION_NUM. (DBERR 10019)

The PARMCB.SECTION.SECTION_NUM specified is 0, less than -32767, or greater than 32767.

Specify a valid RMCB.SECTION.SECTION_NUM value.

Cannot change current connection because a transaction is active. (DBERR 10020)

A transaction is still active when issuing a CONNECT, SET CONNECTION, START DBE, START DBE NEW, or START DBE NEWLOG statement in single-transaction mode.

Either commit or rollback the transaction, or change to multi-transaction mode. Then retry the operation.

The SQLX function code setting is not supported or invalid. (DBERR 10021)

An unknown CODE parameter setting was passed to the SQLX interface.

Specify a valid CODE parameter.

Invalid version number specified in the SQLX AREAS parameter. (DBERR 10022)

An unknown AREAS.VERSION setting was passed to the SQLX interface.

Specify a valid AREAS.VERSION setting.

Invalid version number specified in the SQLX SQLEA parameter. (DBERR 10023)

An unknown SQLEA.VERSION setting was passed to the SQLX interface.

Specify a valid SQLEA.VERSION setting.

Invalid version number specified in the SQLX SQLPA parameter. (DBERR 10024)

An unknown SQLPA.VERSION setting was passed to the SQLX interface.

Specify a valid SQLPA.VERSION setting.

Invalid version number specified in the SQLX PARMCB parameter. (DBERR 10025)

An unknown PARMCB.VERSION setting was passed to the SQLX interface.

Specify a valid PARMCB.VERSION setting.

Invalid version number specified in the SQLX SECTION parameter. (DBERR 10026)

An unknown SECTION.VERSION setting was passed to the SQLX interface.

Specify a valid SECTION.VERSION setting.

Invalid version number specified in the SQLX STATEMENT parameter. (DBERR 10027)

An unknown STATEMENT.VERSION setting was passed to the SQLX interface.

Specify a valid STATEMENT.VERSION setting.

Invalid version number specified in the SQLX PARMS parameter. (DBERR 10028)

An unknown PARMS.VERSION setting was passed to the SQLX interface.

Specify a valid PARMS.VERSION setting.

Invalid version number specified in the SQLX DATABUF parameter. (DBERR 10029)

An unknown DATABUF.VERSION setting was passed to the SQLX interface.

Specify a valid DATABUF.VERSION setting.

SQL statement not allowed. (DBERR 10030)

The SQL statement you specified is not allowed in the SQLX routine called.

Specify a valid SQL statement for the SQLX routine called.

Number of PARMS formats did not match the SQL command. (DBERR 10031)

The PARMS.PARMBUF_FMT is passed when not needed, or is not passed when needed, or does not match the number of input host variables.

Correct the PARMS.PARMBUF_FMT parameter.

Number of DATABUF formats did not match the SQL command. (DBERR 10032)

The DATABUF.BUFFER_FMT is passed when not needed, or is not passed when needed, or does not match the number of input host variables.

Correct the DATABUF.BUFFER_FMT parameter.

No input host variables specified for BULK INSERT. (DBERR 10033)

You have not specified input host variables for a BULK INSERT statement.

Specify input host variables in the BULK INSERT statement.

No output host variables specified for FETCH or SELECT. (DBERR 10034)

You have not specified output host variables for FETCH or SELECT statements.

Specify output host variables in the FETCH or SELECT statements.

The SQL statement is unknown. (DBERR 10035)

The SQL statement you specified cannot be processed by the SQLX interface.

Specify a valid SQL statement.

The specified connection name is already in use. (DBERR 10036)

You have specified a connection name that is already used by another CONNECT.

Specify a unique connection name.

The specified connection name is not open. (DBERR 10037)

You specified a connection name that is not associated with a CONNECT.

Specify a valid connection name.

Invalid number of columns in PARMCB.COLUMNS.NUM_COLUMNS. (DBERR 10038)

The number of columns you specified in PARMCB.COLUMNS.NUM_COLUMNS is less than 0 or greater than 255.

Correct the value of PARMCB.COLUMNS.NUM_COLUMNS.

Invalid number of formats specified. (DBERR 10039)

The number of format elements you specified is either less than or equal to 0, or greater than 1024.

Specify the correct number of format elements.

No more WSL records to transmit. (DBERR 10040)

A Transmit_Log reader has encountered the end of log. No more log records can be transmitted beyond this point until some more get written.

Wait for a certain period and then retry.

Invalid MODE specified. (DBERR 10041)

The mode specified is invalid. Each intrinsic has a specified set of valid modes.

Check the specified mode.

Invalid FLAG specified. (DBERR 10042)

The flag specified in the arglist is invalid. Each intrinsic has a specified set of valid flags.

Check the specified flag.

Invalid log scan id passed. (DBERR 10043)

This error can be seen by either Transmit_Log or Close_Log_Scan when the scan_id specified in the arglist does not match that of a valid log scan currently open by this process.

Check the scan_id specified in the arglist against the scan_ids previously returned by Open_Log_Scan.

Invalid log buffer size. (DBERR 10044)

The buffer_size specified in the arglist is not large enough to contain even the smallest WSL record. This error can be encountered by Transmit_Log and Apply_Log.

Check the buffer_size field in the arglist to determine if it has been properly initialized. If it has been, then a larger buffer should be defined since it is too small to receive any WSL records.

Invalid value of used log buffer space. (DBERR 10045)

Apply_Log has determined that the size_used specified in the arglist is invalid. This indicates that either the size_used is smaller than the smallest WSL record possible, or that the size_used is greater than the number of bytes reserved in the log buffer (as indicated by the buffer_size field in the arglist).

Check that the size_used is less than or equal to the buffer_size field in the arglist. The size_used being passed to Apply_Log should also be checked against the value that was returned by Transmit_Log.

Invalid buffer offset passed. (DBERR 10046)

Apply_Log has determined that the buffer_offset field specified in the arglist does not point to a valid position in the log buffer. This will occur if the buffer_offset contains a negative value, or a number greater than the size_used field specified in the arglist.

Check the application.

A WSL record in the log buffer has an invalid record length specified. (DBERR 10047)

The Apply_Log intrinsic attempts consistency checking on the lengths of records encountered in the log buffer. If the current position in the buffer plus the length of the next log record takes it beyond the end of the used buffer space, Apply_Log will generate this error. On BEGIN WORK, if the op code of the next log record allows predetermining its correct length, the specified record length is checked against this value.

Check the parameters set up by the application.

A BEGIN WORK WSL record encountered out of sequence. (DBERR 10048)

This error is generated when Apply_Log encounters the BEGIN WORK WSL record for a new transaction while a previous Apply_Log transaction is still in progress. A possible cause is if an application started applying transaction T1 (which spanned multiple log buffers) and tried to apply transaction T2 before applying the COMMIT WORK WSL record for T1. This error is most likely encountered when a single Apply-Log server process is applying transactions received from multiple open scans. Another possible cause is if a transmission error occurred and the end of the transaction (containing the COMMIT WORK WSL record) was lost.

Check the application. If the application is handling transactions correctly (especially ones that span multiple log buffers) then you may try transmitting again the transactions being applied.

No apply WSL records transaction currently active. (DBERR 10049)

Apply_Log encountered a WSL record that was not a BEGIN WORK record, and the BEGIN WORK WSL record has not been processed for the transaction. One cause is if the Apply_Log transaction was aborted and the user tries to continue applying log records without starting at the beginning of the transaction. Another cause is if a transmission error has occurred and the beginning of the transaction has been lost.

Check the application to determine if transactions are correctly reapplied (especially transactions which span multiple log buffers). Then try to transmit the transactions and apply them again. If the condition persists, try closing and reopening the log scan.

WSL records applied did not match transaction length. (DBERR 10050)

Apply_Log determined that applying the WSL record will lead to a mismatch between the number of bytes applied for the transaction and the length of the transaction specified in the BEGIN WORK WSL record. For all records, except a COMMIT WORK WSL record, this indicates that the record length plus the number of bytes previously applied would be greater than the transaction length specified in the BEGIN WORK record. For COMMIT WORK records, this error indicates that the length of the COMMIT WORK record plus the number of bytes previously applied does not exactly equal the required transaction length. This is encountered if part of the transaction has been lost (due to transmission errors, buffering schemes, etc.).

Check the application to make sure complete transactions are being buffered and transmitted correctly. Then try to transmit the transactions and apply them again. If the condition persists, try closing and reopening the log scan.

Invalid number of partitions specified. (DBERR 10051)

Get_Scr or Modify_Scr encountered an invalid num_partitions in the arglist. The acceptable values for this field are somewhat dependent on the procedure being called in conjunction with the mode specified.

Check the num_partitions specified in the arglist.

Invalid partition id encountered. (DBERR 10052)

Get_Scr or Modify_Scr encountered an invalid partition id passed in from the user. For Get_Scr, the partition id in error must be in the array pointed to be the partition_array field in the arglist. For Modify_Scr, the partition id must be in the SCR array for mode 1 (UPDATE SCR), or the partition array for mode 2 (DELETE SCR). All partition ids are required to be positive, non-zero numbers.

Check the partition ids specified by the application.

Invalid number of SCR slots specified. (DBERR 10053)

An invalid num_SCR was specified in the arglist. In most cases, a non-positive value was specified. In the case of Get_Scr using mode 1 (SOFT RESYNC), this error can also be encountered if the num_SCR value is less than the value of num_partitions.

Check the parameters specified by the application.

Invalid specification for number of SCR slots used. (DBERR 10054)

The num_SCR_used field specified in the arglist is invalid so Open_Log_Scan or Modify_Scr generates this error. For Open_Log_Scan and Modify_SCR (mode 1 only), num_SCR_used must be within the range from 1 to num_SCR.

Check the parameters specified by the application.

Invalid specification for maximum number of log files.(DBERR 10055)

An invalid number of max_logfiles for the backward scan during Open_Log_Scan was specified. This parameter can be either -1 (the default) or a non-positive number.

Check the parameters specified by the application.

Could not allocate heap space needed for procedure. (DBERR 10056)

Open_Log_Scan gives this error while allocating control blocks needed for opened scans. This error states that the routine was unable to allocate the necessary heap space to be able to open the log scan. If multiple scans are opened on the same DBEnvironment, each opened scan receives a new set of control blocks (which are allocated in the heap), and this problem could be due to having many scans opened (instead of combining them into one open scan).

Determine the amount of heap space used by the application. If an excessive amount is used, the application should be modified to use less. If the heap allocation has previously worked on the system, first check the number of users on the system, then use SQLMON to see global swap space utilization plus heap usage for individual user processes. If numerous scans are open on the same DBE, the problem could be alleviated if the open scans are combined into one open scan (and thus only one set of scan control blocks).

Invalid exception number. (DBERR 10057)

You specified an invalid exception number when requesting diagnostic information.

Specify a valid exception number.

Invalid DBEnvironment or connection name length. (DBERR 10058)

You specified a DBEnvironment or connection name length which is less than or equal to 0, or greater than 128.

Specify a valid DBEnvironment or connection name.

Invalid BEGIN WORK setting. (DBERR 10059)

You specified a bad transaction priority or isolation level when starting a transaction.

Specify a valid transaction priority or isolation level in the BEGIN WORK statement.

Invalid format node data type encountered. (DBERR 10060)

The data type you specified in one of the format array elements is not a valid SQL data type.

Specify a valid SQL data type.

Invalid format string specified. (DBERR 10061)

The format string you specified is invalid.

Specify a valid format string.

Invalid setting in PARMCB.CURSOR_NUM. (DBERR 10062)

The cursor number you specified in PARMCB.CURSOR_NUM is either 0, less then -32767, or greater than 32767.

Specify a valid cursor number in PARMCB.CURSOR_NUM.

Invalid format node type encountered. (DBERR 10063)

The format node type you specified in one of the format array elements is invalid.

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

Invalid PARMCB.PARMS.PARMBUF_LEN specified. (DBERR 10064)

The length you specified in PARMCB.PARMS.PARMBUF_LEN is less than or equal to zero.

Specify a valid length in PARMCB.PARMS.PARMBUF_LEN.

Invalid PARMCB.DATABUF.ROW_LEN specified. (DBERR 10065)

The length you specified in PARMCB.DATABUF.ROW_LEN is less than or equal to zero.

Specify a valid length in PARMCB.DATABUF.ROW_LEN.

Invalid savepoint specified. (DBERR 10066)

The savepoint number you specified is negative.

Specify a valid savepoint number.

Invalid setting in PARMCB.DATABUF.USE_FLAG. (DBERR 10067)

The data buffer use flag you specified in PARMCB.DATABUF.USE_FLAG is invalid.

Specify a valid data buffer use flag in PARMCB.DATABUF.USE_FLAG.

Invalid setting in SQLEA. (DBERR 10068)

You specified an invalid SQLX environment control setting.

Correct the value of SQLEA.

The maximum number of DBEnvironments have been connected. (DBERR 10069)

An attempt to connect to a DBEnvironment was rejected because the maximum number of database connections has been reached.

Release some existing connections.

SQLX internal error - Pascal escapecode !.(DBERR 10071)

Internal error.

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

Invalid offset for last record passed. (DBERR 10074)

This can be returned by audit_log when the last_rec_offset field contains an invalid value.

Check the application to determine what value is being passed and whether it is within the domain of the log buffer space.

Invalid number of records in column array. (DBERR 10075)

The num_columns field in the Arglist has been initialized to a negative number.

Check the application program to determine whether this field is being initialized properly.

Invalid number of records in update column array. (DBERR 10076)

The num_upd_cols field in the Arglist has been initialized to a negative number.

Check the application program to determine whether this field is being initialized properly.

Insufficient space in log buffer to return next log record. (DBERR 10077)

Transmit log was unable to transmit the log record into the log buffer because there was insufficient space to hold it. This warning can only be encountered if the first record to transmit will not fit into the log buffer.

Allocate a larger log buffer space and call transmit_log again.

XA Interface protocol error occurred. (DBERR 10080)

You specified incorrect XA call interface protocol.

Refer to the X/OPEN XA Interface standard for possible causes.

Internal error. Could not allocate or deallocate the DCB. (DBERR 10081)

The DBE Control Block could not be allocated or deallocated, possibly because of a memory resource failure.

Try your program later. If the condition persists, then record as much information as possible and contact your HP Service Representative or Response Center.

Internal error. Could not allocate or deallocate the GCB. (DBERR 10082)

The Global Control Block could not be allocated or deallocated, possibly because of a memory resource failure.

Try your program later. If the condition persists, then record as much information as possible and contact your HP Service Representative or Response Center.

Internal error. Could not get the Star/Externals KPO. (DBERR 10083)

The SQLX runtime interface is unable to obtain the Star/Externals KPO.

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

Internal error. Could not set the Star/Externals KPO. (DBERR 10084)

The SQLX runtime interface is unable to set the Star/Externals KPO.

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

Internal error. Could not allocate the Star/Externals KPO. (DBERR 10085)

The Star/Externals KPO could not be allocated, possibly because of a memory allocation failure.

Try your program later. If the condition persists, then record as much information as possible and contact your HP Service Representative or Response Center.

XA Interface ALLBASE/SQL protocol error occurred. (DBERR 10086)

An incorrect combination of XA call interface and ALLBASE/SQL protocol was performed.

Refer to the X/OPEN XA Interface standard for possible causes.

A transaction is active in another DBEnvironment connection. (DBERR 10087)

A SET MULTITRANSACTION OFF statement was rejected because at least one transaction is active outside of the current DBEnvironment connection.

Complete any active transactions associated with other DBEnvironment connections using either COMMIT WORK or ROLLBACK WORK, and retry the statement.

XA Interface rmfail error occurred. (DBERR 10088)

A resource manager failure has occurred in the XA interface.

Refer to the X/OPEN XA Interface standard for possible causes.

Error occurred opening the module file. (DBERR 10089)

The specified module file could not be opened.

Ensure that the module file exists, and that it can be read and written to. If the condition persists, then record as much information as possible and contact your HP Service Representative or Response Center.

The module file is empty. (DBERR 10090)

The specified module file to be installed is empty.

Specify the correct module file name, or create new module file.

The file is not a module file, or it is corrupted. (DBERR 10091)

The specified module file to be installed is either corrupt or is not a module file.

Specify the correct module file name, or create new module file.

Incorrect protocol when installing or creating a module file. (DBERR 10092)

You attempted to install and create a module file simultaneously

or

the file identifier passed to the install is different from the one assigned when the module file was opened.

Do not attempt to install and create a module file simultaneously

or

pass the file identifier set when the module file was opened.

Error occurred reading the module file. (DBERR 10093)

The specified module file could not be read.

Ensure that the module file exists and that it has the correct read/write permissions. If the condition persists, then record as much information as possible and contact your HP Service Representative

Error occurred closing the module file. (DBERR 10094)

The specified module file could not be closed.

Ensure that the module file exists. If the condition persists, then record as much information as possible and contact your HP Service Representative

Module file created with with different product or version. (DBERR 10095)

The specified module file to be installed was created from an incompatible version of ALLBASE/SQL.

Recreate the module file with the current version of ALLBASE/SQL.

Error occurred writing the module file. (DBERR 10096)

The specified module file could not be written to.

Ensure that the module file exists and that it can be written to. If the condition persists, then record as much information as possible and contact your HP Service Representative

PRESERVE or REVOKE may not be used without DROP option. (DBERR 10900)

The preprocessor INFO string contained the NODROP option (or defaulted to NODROP because DROP was not specified) and also contained a PRESERVE or REVOKE option.

The PRESERVE and REVOKE options only apply when the DROP option is also specified. Invoke the preprocessor again, specifying only valid combinations of options in the INFO string.

DROP or NODROP option may only be specified once. (DBERR 10901)

The preprocessor INFO string contained both DROP and NODROP options or duplicate DROP or NODROP options.

Invoke the preprocessor again eliminating the invalid DROP and NODROP combination or specifying the DROP or NODROP option only once.

DBEnvironment name too long. (DBERR 10902)

The DBEnvironment name specified in the invocation line for the preprocessor was too long.

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

DBEnvironment name missing. (DBERR 10903)

The preprocessor invocation line contained neither a DBEnvironment name nor the -s option.

Invoke the preprocessor again, specifying one of these two options.

Invalid DBEnvironment name. (DBERR 10904)

The DBEnvironment name you specified in the preprocessor invocation line is invalid.

Invoke the preprocessor again, specifying a valid DBEnvironment name.

MODULE name too long. (DBERR 10905)

The module name you specified in the preprocessor invocation line exceeded the maximum length of 20 bytes.

Invoke the preprocessor again, specifying a valid module name.

OWNER name too long. (DBERR 10906)

The owner name you specified in the preprocessor invocation line exceeded the maximum length of 20 bytes.

Invoke the preprocessor again, specifying a valid owner name.

File open error. (DBERR 10907)

The source file you specified in the preprocessor invocation line does not exist.

Check your spelling. Use the HP-UX ls command to make sure the specified file exists.

Error in preprocessor command line. (DBERR 10908)

An error occurred in the preprocessor invocation line. An additional error message will be returned.

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

Memory allocation failed. (DBERR 10920)

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

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

Input source file not found. (DBERR 10921)

The preprocessor could not locate the specified input source file name.

Check your spelling and the pathname specified, then invoke the preprocessor again.

System error in opening input source file. (DBERR 10922)

The source file you specified is currently being accessed.

Wait until the source file is no longer being accessed, then invoke the preprocessor again.

Processing terminated prematurely. (DBERR 10923)

An error occurred which caused preprocessing to be terminated. An additional error message will be returned.

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

Integer value too large. (DBERR 10925)

You specified an integer value in the source program that exceeds the largest legal integer on the system.

Correct the integer value and re-preprocess your program.

Comment not ended before end of file. (DBERR 10926)

A comment line was not closed before the end of the file.

Close the comment line with " *) " and re-preprocess your program.

Illegal character. (DBERR 10927)

The preprocessor detected a control character before the end of the file. The character was skipped and no module was stored.

Delete the control character and re-preprocess your program.

No ending semicolon before end of file. (DBERR 10929)

An SQL statement was not ended with a semicolon.

Check your Pascal program to make sure that all SQL statements are ended with a semicolon and then re-preprocess your program.

Syntax error in program header. (DBERR 10931)

Your program statement contained a syntax error.

Refer to the appropriate host language reference manual for correct syntax.

Syntax error in host variable declaration. (DBERR 10932)

Declarations that appear in the declare section of the source file are not allowed by the preprocessor. No module was stored.

Correct the host variable declaration in the source file and re-preprocess your program. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information on host variable declaration syntax.

Unsupported type syntax for host variable. (DBERR 10933)

The host variable type you specified in the BEGIN or 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.