Chapter 8 ALLBASE/SQL Error Messages 2771-4013

KEEP CURSOR with NOLOCKS is not supported on NON-UPDATABLE CURSOR. (DBERR 2771)

You specified the KEEP CURSOR WITH NOLOCKS option for a cursor which was declared as SELECT...ORDER BY or SELECT DISTINCT. These operations need to build temporary tables, and if KEEP CURSOR WITH NOLOCKS is in effect, the consistency between permanent and temporary tables cannot be guaranteed between transactions.

Revise the program to open the cursor with the KEEP CURSOR WITH LOCKS option.

Cursor !.!(!) containing SUBQUERY is not allowed in the REFETCH command. (DBERR 2772)

You attempted to perform a REFETCH on a cursor containing a subquery.

REFETCH cannot be done on cursors containing subqueries. Either remove the subquery from the cursor, or do not perform REFETCH on that cursor.

Multiple-rows operation is NOT allowed in the REFETCH command. (DBERR 2773)

You specified more than one record in the REFETCH statement.

Make sure to specify only one record for the REFETCH statement.

Escape character in LIKE pattern must be followed by escape character, underscore, or percent. (DBERR 2774)

There is an escape character in a LIKE predicate pattern that is not followed by an escape character, underscore, or percent.

Change the pattern to a legal pattern.

Escape character must be a single character. (DBERR 2775)

You specified a multi-character string for the escape pattern, or passed in a host variable containing more than a single character.

Correct the specification of the escape string to be a single character, or make sure that the host variable is set to blanks after the escape character.

Dynamic parameters as both operands of a single binary operator disallowed. (DBERR 2776)

You specified dynamic parameters for both operands of an arithmetic or comparison operator.

Modify your statement to not specify dynamic parameters for both operands of the arithmetic or comparison operator.

Dynamic parameter as the operand of a unary arithmetic operator disallowed. (DBERR 2777)

You specified a dynamic parameter in a NULL predicate or a minus sign is specified in front of the dynamic parameter.

Modify your statement to not contain a dynamic parameter in a NULL predicate nor a minus sign in front of a dynamic parameter.

Dynamic parameter in the SELECT list disallowed. (DBERR 2778)

You specified a dynamic parameter in the SELECT list.

Modify your statement to not contain a dynamic parameter in a SELECT list.

TID data type is not supported. (DBERR 2779)

You specified a column of TID data type in the CREATE TABLE or ALTER TABLE statement. There is no TID data type.

Check and modify the statement.

Psuedotable can not be updated. (DBERR 2780)

You attempted to perform an update on a system pseudotable.

Check that the correct table name has been specified.

Illegal reference to TID function in group operation. (DBERR 2781)

Within a single query block, you cannot specify the GROUP BY clause when using the TID function in the select list.

Check and modify the command.

TID function is not allowed for the pseudotable (!.!). (DBERR 2782)

The parameter in the TID function is a system pseudotable.

Check and modify the command.

TID function is not allowed for the non-updatable view (!.!). (DBERR 2783)

The parameter in the TID function is not an updatable view.

Check and modify the command.

DDL statement not allowed in PREPARE REPEAT command. (DBERR 2784)

Data definition language statements (CREATE TABLE, CREATE INDEX, DROP TABLE, etc.) are not allowed in a PREPARE command with the REPEAT option.

Do not use the REPEAT option for DDL commands.

The starting position is invalid for the SUBSTRING function. (DBERR 2785)

The StartPosition parameter of the SUBSTRING function is less than 1 or greater than the length of the SourceString.

Change the StartPosition parameter to a value greater than 0, and less than or equal to the length of the SourceString parameter.

The substring length is invalid for the SUBSTRING function. (DBERR 2786)

The Length parameter of the SUBSTRING function is less than 1 or greater than the length of the SourceString parameter.

Change the Length parameter to a value greater than 0, and less than or equal to the length of the SourceString parameter.

Length of item ! in select list exceeds that of corresponding procedure result column. (DBERR 2787)

An item in the select list in a procedure SELECT statement with no INTO clause has a length greater than that specified for the corresponding procedure result column in the WITH RESULT clause of the CREATE PROCEDURE statement.

Re-issue the CREATE PROCEDURE statement, either omitting the WITH RESULT clause, or ensuring that all multiple row result sets returned from the procedure are compatible with the format specified.

USING Clause is required for output dynamic parameters. (DBERR 2788)

You tried to execute a prepared EXECUTE PROCEDURE statement with output dynamic parameters, but no output variables were provided in the USING clause of an EXECUTE or CLOSE statement.

Issue the EXECUTE or CLOSE statement again with the USING clause, specifying output variables for output dynamic parameters in the prepared statement.

CANNOT use DROP PARTITION on DEFAULT partition. (DBERR 2790)

You attempted to drop the DEFAULT partition.

This partition cannot be dropped. Its partition number can be changed with the START DBE NEWLOG statement.

Cannot CREATE PARTITION !. (DBERR 2791)

You attempted to create a partition named NONE or DEFAULT. This partition name cannot be used since it refers to the nonexistent partition.

No partition can be created with this name in the CREATE PARTITION statement.

Comment text for LOG COMMENT must have data type CHAR or VARCHAR. (DBERR 2792)

The value for a log comment was not a character value.

Check the type of the value and be sure it is CHAR or VARCHAR.

Cannot LOG COMMENT when AUDIT LOG not enabled. (DBERR 2793)

You specified a LOG COMMENT statement in a DBEnvironment without audit logging or with audit logging disabled.

Enable AUDIT LOG for the DBEnvironment or refrain from issuing LOG COMMENT on the DBEnvironment.

Cannot open log scan on AUDIT CHECKPOINT only DBEnvironment. (DBERR 2794)

Unable to open the log scan on the AUDIT CHECKPOINT.

Enable AUDIT LOG for the DBEnvironment, not for AUDIT CHECKPOINT.

Table's language not compatible with DBE's language. (DBERR 2800)

The language you specified for the table is neither the same as DBEnvironment's language, nor n-computer.

Make sure the table's language is either n-computer or the same as the DBEnvironment's language.

Column's language not compatible table/DBE's language. (DBERR 2801)

The language you specified for the column is neither table/DBEnvironment's language nor n-computer.

Make sure the column's language is either the same as table/DBEnvironment's language or n-computer.

Procedure result language is not compatible with procedure/DBEnvironment language. DBERR 2802)

A language other than that of the DBEnvironment or n-computer was specified for a procedure result.

Re-issue the CREATE PROCEDURE statement, either omitting the language clause, or specifying either the DBEnvironment language or n-computer.

Procedure language is not compatible with DBEnvironment language. (DBERR 2803)

The language you specified for the procedure was neither the DBEnvironment language nor n-computer.

Issue the CREATE PROCEDURE statement again, specifying either the DBEnvironment language or n-computer for the procedure, or specifying no procedure language.

Parameter language is not compatible with procedure/DBEnvironment language. (DBERR 2804)

The language you specified for the parameter was neither the procedure/DBEnvironment language nor n-computer.

Issue the CREATE PROCEDURE statement again, specifying either the procedure/DBEnvironment language or n-computer for the parameter, or specifying no parameter language.

NLINFO error !. Language ID = !. (DBERR 2805)

An error was returned from the NLS library routine NLINFO, with the specified language.

Check the validity of your NLS data and reissue the statement.

Comment text cannot be NULL for LOG COMMENT. (DBERR 2806)

The value passed to a LOG COMMENT was NULL.

Check the value and reissue the statement with a non-null value.

Cannot drop a non-empty partition. (DBERR 2807)

You issued a DROP PARTITION on a partition that currently contains tables.

Remove the tables from the partition with the ALTER TABLE SET PARTITION statement and reissue the statement.

Partition ! already exists. (DBERR 2808)

A CREATE PARTITION attempted to create a partition with a name of a partition that is already defined.

Reissue the CREATE PARTITION statement with another partition name or issue a DROP PARTITION to remove the existing partition and then reissue the CREATE PARTITION statement.

Partition ! not found. (DBERR 2809)

The partition name you specified by a DROP PARTITION, ALTER TABLE SET PARTITION, or CREATE TABLE statement does not exist.

Check the partition name against the system catalog table SYSTEM.PARTITION and reissue the CREATE TABLE or ALTER TABLE SET PARTITION statement with the name of an existing partition.

Audit logging not set for DBE. (DBERR 2810)

You issued an ENABLE AUDIT LOGGING statement for the session, but audit logging is turned off for the DBEnvironment.

Check the correctness of operations. Either audit logging for the DBEnvironment should be turned on (this may be done through the START DBE NEWLOG statement) or the ENABLE AUDIT LOGGING statement is not valid.

Insufficient size specified for the new SCR. (DBERR 2811)

Note that it is possible to change the MAXPARTITIONS parameter through the START DBE NEWLOG statement. In so doing, the product restores the current SCR slots into this new log file (the current SCR value has an image stored in the DBECon file). If the new MAXPARTITIONS specified is not large enough to contain all the occupied slots from the old SCR, this error is generated.

Reissue the START DBE NEWLOG statement with the appropriate MAXPARTITIONS.

There are still some active transactions in the old SCR. (DBERR 2812)

You attempted a START DBE NEWLOG, and the old SCR (out of the DBECon file) still contains some active transactions. This can only happen if the database was not shut down in a manner such that all operations could be properly terminated.

Connect to the database and release it. This allows ALLBASE/SQL to terminate any uncommitted transactions. Then you can reissue the START DBE NEWLOG statement.

More than one slot found for the same partition. (DBERR 2813)

The partition was specified twice when opening a log scan.

Eliminate the duplication.

Open_Log_Scan failed on ALL specified partitions. (DBERR 2814)

Check the per partition return codes.

Use the per partition return code information to determine your action.

Hard resync record encountered in partition !. Scan aborted. (DBERR 2815)

The master and slave databases are inconsistent.

Resync the indicated partition.

Open_Log_Scan could not reserve log for partitions found. (DBERR 2816)

The specified starting point for opening a log scan has been overwritten.

Use a Wrapper DBE to recover the needed log records or hard resync the partition.

Invalid audit log record found. (DBERR 2817)

The log record being applied in an Apply_Log was not a valid audit log record.

The log records being applied in an Apply_Log command must have come from an Transmit_Log from a master instance. Check your application to make sure that the log records from the Transmit_Log are being passed appropriately to the Apply_Log according to the External Specifications.

Apply_Log cannot find the tuple to be modified/deleted. (DBERR 2818)

The master and slave databases are not synchronized.

Perform a hard resync.

Attempting to apply a log record while audit is not enabled. (DBERR 2819)

The architecture of Apply_Log requires audit to be turned on at the slave (target).

Use SQLUTIL (SHOWDBE) to check the startup parameters, and turn audit on (through a START DBE NEWLOG) if necessary.

Audit parameters not set. (DBERR 2820)

You tried to use audit logging without setting all of the required parameters.

Check that the AUDIT NAME, DEFAULT PARTITION, and MAXPARTITIONS are all set in the DBEnvironment, or set them (through a START DBE NEWLOG) if necessary.

Active transactions found on partition !. (DBERR 2821)

An attempt is being made to hard resync an active partition.

Terminate access to the partition and redo the hard resync.

Duplicate partition instance found in SCR array. (DBERR 2822)

The duplicate partition instance (PID/DBID) was found in the SCR array passed to modify SCR.

Eliminate the duplicates and try again.

Open log scan failed due to missing log file (sequence #!). (DBERR 2823)

A log needed for the log scan being opened has been purged.

For a resync application, perform a hard resync. Auditing cannot be done.

More than one tuple qualified for key column search. (DBERR 2824)

Multiple tuples found during Apply_Log with key column search enabled.

Try the Apply_Log with key column search disabled.

Timeout expired (! seconds). (DBERR 2825)

A request for a database resource, such as a lock, could not be granted before the user timeout was exceeded. The current transaction was rolled back.

Retry the transaction when the requested resource becomes available, or increase the user timeout value.

Insufficient number of transactions. (! is required) (DBERR 2826)

An attempt to start the DBE with the maximum allowable transactions less than or equal to the number of persistent transactions currently present in the DBE.

Specify a larger number of transactions to start the DBE.

The function was invoked in an improper context. (DBERR 2827)

An XA function has been invoked in an invalid context.

Correct the context and try again.

Comment is disallowed. (DBERR 2828)

An attempt was made to log a comment for a transaction that is already persistent.

Retry the function without a comment.

Blocking condition exists. (DBERR 2829)

A transaction join was attempted with the nowait option specified. The function would have had to wait.

Try again later or remove the nowait option.

Duplicate global transaction identifier. (DBERR 2830)

Attempted to start a transaction with a global identifier that already exists.

Try again with a unique GTRID.

The global transaction identifier is unknown. (DBERR 2831)

The specified global transaction identified does not exist in the DBE.

Check the validity of the GTRID.

A transaction scan is already opened. (DBERR 2832)

An attempt was made to open a recovery scan when was already open. A session can have only one open recovery scan.

Close the open scan before opening another.

A transaction scan is not opened. (DBERR 2833)

A recovery scan is required for the requested function, but one is not open.

Open a recovery scan and try again.

The transaction has already been heuristically committed. (DBERR 2834)

A request was made to commit or abort a transaction that has already been heuristically committed.

None.

Timeout. (DBERR 2836)

The requested function has timed out waiting for access to a transaction.

Try again when the transaction is available.

The global transaction identifier is invalid. (DBERR 2837)

The specified global transaction id has an invalid format.

Check the GTRID.

Log lock point specified is invalid. (DBERR 3228)

The log location specified for a log lock is invalid.

Check the location.

Cannot drop ! default DBEFileSet !. (DBERR 2881)

You have the space default on the DBEFileSet you tried to drop.

Change the space default or modify your command.

Cannot revoke ! default on DBEFileSet ! from !. (DBERR 2882)

The authority you tried to revoke is a DEFAULT for the user.

Change the space default or modify your command.

User ! does not have explicit ! authority on DBEFileSet !. (DBERR 2884)

The authority is not previously granted to you.

Cannot REVOKE, please modify the command.

! on DBEFileSet ! is not granted for !. (DBERR 2885)

The authority is not previously granted to you.

You must grant the authority to the user before you run the command.

Multiple rows returned in subquery. (DBERR 2901)

A subquery within a comparison predicate returns more than one row. Comparison predicates can only work with single values.

For a subquery that returns more than one value, the EXISTS predicate, IN predicate, or one of the quantified predicates (SOME, ALL, ANY) must be used.

Multiple columns returned in subquery. (DBERR 2902)

You specified more than one column in the select list of a subquery. If an asterisk was specified, there was more than one column in the table being queried. Only the EXISTS predicate allows more than one column to be specified in a subquery.

Change the subquery so that only one column is specified in the select list.

Number of output variables does not match the number of output dynamic parameters in the referenced section. (DBERR 2909)

The number of output values in the USING clause of an EXECUTE or CLOSE statement is not equal to the number of output dynamic parameters in the prepared statement.

Modify either your EXECUTE or CLOSE statement or the related PREPARE statement so that there is a one to one mapping of output dynamic parameters.

Number of input values does not match the number of dynamic parameters in the referenced section. (DBERR 2910)

The number of input values in the USING clause of an OPEN or EXECUTE statement is not equal to the number of dynamic parameters in the prepared statement.

Modify either your OPEN or EXECUTE statement or the related PREPARE statement so that there is a one to one mapping of dynamic parameters.

Incompatible conversion from ! to ! for the dynamic parameter (!). (DBERR 2912)

The data type of the input value in the USING clause of an OPEN or EXECUTE statement is not compatible with the default data type of the dynamic parameter in the prepared statement.

Modify the data type of the referenced input value to be compatible with the default data type of the corresponding dynamic parameter.

Invalid conversion from ! to ! for the dynamic parameter (!). (DBERR 2913)

You attempted an invalid conversion from one specified type to another.

Refer to the "CAST Function" in the "Expressions" chapter of the ALLBASE/SQL Reference Manual for the correct conversion types.

Invalid conversion from DECIMAL (!,!) to DECIMAL (!,!) for the dynamic parameter (!). (DBERR 2914)

The value length, precision, or scale of the decimal value you specified in the USING clause of an OPEN or EXECUTE statement is greater than that of the data type of the corresponding dynamic parameter in the prepared statement.

Modify the referenced decimal input value to be compatible with the corresponding dynamic parameter.

Invalid conversion from !(!) to !(!) for the dynamic parameter (!). (DBERR 2915)

The length of the input value you referenced in the USING clause of an OPEN or EXECUTE statement is greater than the length of the data type of the corresponding dynamic parameter in the prepared statement.

Modify the definition of the referenced input value to be compatible in length with the corresponding dynamic parameter.

Invalid Table/View/Column in the dynamic format computation. (DBERR 2916)

A dynamic parameter is associated with an invalid table, view, or column in the statement. Its format cannot be determined.

Check that the query references existing tables, views, and columns you are authorized to access and reissue the statement.

No corresponding column for the dynamic parameter. (DBERR 2917)

A dynamic parameter in the VALUE clause of an INSERT statement has no corresponding column.

Check that the number of columns in the INSERT matches the number of values specified, and reissue the statement.

Using Clause is required for the input dynamic parameters. (DBERR 2918)

You attempted to issue an OPEN or EXECUTE statement on a section that contains dynamic parameters without passing the values for the dynamic parameters via the USING clause.

Add a USING clause to the statement and provide values for the dynamic parameters with the USING clause.

An invalid NLS data was encountered. (DBERR 2919)

NLS data is invalid.

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

SQLCORE encountered error from (!) (!). (DBERR 2920)

SQLCORE has an error from the above routine.

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

Integer or float overflow or underflow on operation ADD. (DBERR 2921)

The result of an addition operation with INTEGER or FLOAT operands is either too big or too small for the hardware to accommodate.

Modify the expression to yield a result within the limits for the data type.

PUBLICROW is not allowed on a hash table. (DBERR 2922)

You are trying to define a hash on a PUBLICROW table, and this combination is not supported.

or

You are trying to alter a hash table to type PUBLICROW, but this combination is not supported

Either use a table type of PUBLIC as you define the hash structure, or else convert to a non-hash PUBLICROW table by dropping and recreating the table.

Invalid ALLBASE/SQL request block. (DBERR 3001)

Internal error. The ALLBASE/SQL request block has an invalid brand name in its first field. This could be caused by an invalid request block pointer.

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

Invalid parameter-buffer flag in ALLBASE/SQL request block. (DBERR 3002)

Internal error. The ALLBASE/SQL request block (JRB) has an invalid value for input parameter buffer flag. There is a discrepancy between a module in the program and the stored module.

If you moved a modified program to your DBEnvironment you must drop the old module and reinstall a new module,

or

don't use ISQL to execute a module created with a preprocessor

or

record as much information as possible and contact your HP service representative or Response Center.

Invalid parameter-buffer address in ALLBASE/SQL request block. (DBERR 3003)

Internal error. The ALLBASE/SQL request block (JRB) has an invalid pointer pointing to a parameter buffer.

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

Invalid parameter-buffer length in ALLBASE/SQL request block. (DBERR 3004)

Internal error. ALLBASE/SQL request block (JRB) has an invalid parameter buffer length.

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

Invalid data-buffer flag in ALLBASE/SQL request block. (DBERR 3005)

Internal error. ALLBASE/SQL request block (JRB) has an invalid data-buffer flag.

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

Invalid data-buffer address in ALLBASE/SQL request block. (DBERR 3006)

The SQLRowBuf was set to an invalid address for a dynamic query

or

an internal error occurred.

Correct the SQLRowBuf and re-preprocess your program

or

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

Invalid data-buffer length in ALLBASE/SQL request block. (DBERR 3007)

SQLBufLen was set to an invalid length for a dynamic query

or

an internal error occurred.

Correct the SQLBufLen and re-preprocess your program

or

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

Invalid number of rows requested in ALLBASE/SQL request block. (DBERR 3008)

SQLNRows was set to an invalid number for a dynamic query

or

an internal error occurred.

Correct SQLNRows and re-preprocess your program

or

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

Column number ! in node ! out of range. (DBERR 3024)

Internal error.

Record as much information as possible and contact your HP service representative or Response Center.

Null length of ! for value ! is invalid. (DBERR 3025)

Internal error.

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

Unsupported data format of type ! length !. (DBERR 3026)

Internal error. ALLBASE/SQL detected an unsupported data type or invalid data length.

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

Command rejected - DBCore was terminated. (DBERR 3040)

Your database administrator issued a STOP DBE statement causing your transaction to be terminated.

Contact your database administrator to find out when the DBEnvironment will be available.

Command rejected - DBCore is terminating now. (DBERR 3041)

Your database administrator issued a STOP DBE statement causing the DBEnvironment to shut down.

Contact your database administrator to find out when the DBEnvironment will be available.

Command rejected - User session was terminated. (DBERR 3042)

Your database administrator or another user connected to the DBEnvironment using your login name issued a TERMINATE USER statement for your login name. Any active transactions for your login name were terminated.

Contact the person who issued the TERMINATE USER statement and reconnect to the DBEnvironment.

Command rejected - User session is terminating now. (DBERR 3043)

Your database administrator or another user connected to the DBEnvironment issued a TERMINATE USER statement for your login name. Any active transactions for your login name were terminated.

Contact the person who issued the TERMINATE USER statement and reconnect to the DBEnvironment.

Number of query sections exceeds system limit !. (DBERR 3047)

The number of PREPARE commands exceeded system limit per session.

Keep the number of PREPARE commands within the limit.

File System Error - Privileged file violation. (DBERR 3050)

The ownership or file mode of a database or log file, or the directory that contains the file, is 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 (- r w - - - - - - -). If necessary, contact your system administrator.

File System Error - Not enough space in device. (DBERR 3051)

There is not enough space in the device to support your operation.

Use a different device or contact your database administrator to add more space to the current device.

File System Error - Nonexistent DBEFile or log file. (DBERR 3054)

You attempted to access a DBEFile or log file which is missing.

Use the SQLUtil SHOWDBE command and/or SELECT information from SYSTEM.DBEFILE to find out the names of DBEFile0, DBELog and other DBEFiles. Make sure they co-exist with your DBECon file.

File System Error - Security violation. (DBERR 3059)

The ownership or file mode of the DBEFile or executable program files (SQLUtil or hpsqlproc) is incorrect. (hpsqlproc is a process invoked whenever ISQL, the preprocessors, or application programs are executed.)

Refer to the ALLBASE/SQL Database Administration Guide for additional information.

File System Error - File already exists or file does not have the permission expected by ALLBASE/SQL. (DBERR 3060)

The file name you specified in the CREATE DBEFILE statement already exists, or the file does not have the permissions expected by ALLBASE/SQL.

If you are using HP-UX raw files for DBEFiles and logs, you must set the permissions to mode 0600 for the raw file. Any other mode will cause this error.

File System Error - ! (!). (DBERR 3061)

An HP-UX file system error occurred.

Refer to the system administration manual.

Location already used for another Tempspace. (DBERR 3062)

The physical location you specified by the CREATE TEMPSPACE statement is already being used for another tempspace.

Issue the CREATE TEMPSPACE statement again with a different physical location. Or, execute the DROP TEMPSPACE statement to remove the original tempspace from the physical location, and issue the CREATE TEMPSPACE statement again.

DBECon Error - Cannot use CONNECT command with autostart off. (DBERR 3063)

You tried to initiate a single-user session with the CONNECT statement and the autostart flag is OFF.

Either use the START DBE statement to initiate the session or ask your database administrator to change the autostart flag to ON.

DBECon Error - This DBEnvironment does not have !. (DBERR 3064)

You tried to CONNECT to a DBEnvironment which is not an ALLBASE/SQL DBEnvironment.

No action is necessary. You can only CONNECT to an ALLBASE/SQL DBEnvironment.

DBECon Error - User attempted NEWLOG and is not creator of DBECon file. (DBERR 3065)

You attempted to execute the START DBE NEWLOG statement and you are not the creator of the specified DBEnvironment.

Contact your database administrator to find out who the DBECreator is and have the DBECreator issue the appropriate command.

DBECon Error - File is invalid. (DBERR 3066)

The file specified is not a DBECon file.

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

DBECon Error - Not enough space in device. (DBERR 3068)

There is not enough space in the device to support your operation.

Use a different device or contact your database administrator to add more space to the current device.

DBECon Error - Nonexistent file name. (DBERR 3071)

You specified a non-existent file name on the local node in the START DBE or CONNECT statement. This message may be the first of two messages received. ALLBASE/SQL attempted a remote connection but was unsuccessful.

If your CONNECT statement is for a DBEnvironment on the local node, check your spelling. If you still receive this error, use the HP-UX ls command to make sure that the file really exists in your current working directory. If your CONNECT statement is for a remote DBEnvironment, read the second message for further action to be taken.

DBECon Error - Security violation. (DBERR 3076)

The ownership or file mode of the DBECon file or the directory that contains the DBECon file is incorrect.

Check that user hpdb (uid 27) has at least read and write permission to the directory that contains the DBECon file. Check that the DBECon files is owned by hpdb, and has a file mode of 600 (- r w - - - - - - -). If necessary, contact your system administrator. Refer to the ALLBASE/SQL Database Administration Guide for additional information.

DBECon Error - File already exists. (DBERR 3077)

The file name you specified already exists.

Issue the command again, specifying a unique file name.

DBECon Error - (! !). (DBERR 3078)

An HP-UX file system error occurred on the DBECon file.

Refer to the system administration manual.

DBECon error - Permission denied. (DBERR 3079)

The DBECon file is inaccessible because: the owner or access mode of the DBECon file have been changed (the owner should be 'hpdb', and the access mode should be 600)

or

the owner or access mode of the database process /usr/lib/hpsqlproc have been changed (the owner should be 'hpdb', and the access mode should be 4555).

Use the chmod and / or chown commands to restore the correct owner and access mode to the DBECon file.

or

Contact your system administrator.

DBECon error - Attempted a MULTI user session on a SINGLE user DBEnvironment. (DBERR 3080)

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

or

your database administrator has started the DBEnvironment in single-user mode in order to make changes through SQLUtil.

Ask your database administrator to change the DBECon file user mode to MULTI or ask your database administrator to notify you when the DBEnvironment is again accessible in multi-user mode.

DBECon Error - File is NFS mounted. (DBERR 3086)

You attempted to create or access a DBEnvironment on an NFS mounted disk.

To create the DBEnvironment, log onto the server where the DBEnvironment will reside. Install ALLBASE/NET to access the remote DBEnvironment.

DBECon Error - File mounted on another node in the cluster. (DBERR 3087)

You attempted to create or access a DBEnvironment on a disk in the cluster that is not mounted locally.

To create the DBEnvironment, log onto the system on which the disk is mounted locally. Install ALLBASE/NET to access the remote DBEnvironment.

MOVEFILE cannot be used to move DBECon. (DBERR 3088)

You tried to move the DBECon file using the MOVEFILE statement.

The DBECon file stores the start up parameters for the DBEnvironment defined by the START DBE NEW statement and must remain in the same location as the DBEnvironment.

COMMIT ARCHIVE attempt was not preceded by a successful BEGIN ARCHIVE. (DBERR 3100)

Some user has already got a BEGIN ARCHIVE in progress, and some other user attempts to COMMIT ARCHIVE. This is illegal.

Refrain from performing a COMMIT ARCHIVE if you were not the one to have a BEGIN ARCHIVE in the first place.

START DBE NEWLOG disallowed. Need rollforward recovery. (DBERR 3101)

You are most probably trying a START DBE NEWLOG on a DBEnvironment that has incomplete transactions in its log. The only operations permitted are START DBE or CONNECT (if AutoStart is enabled); either of these will roll back incomplete transactions and force completed transactions to disk.

First, issue a START DBE statement or a CONNECT (if AutoStart is enabled). Next, stop the DBEnvironment. Finally, attempt the START DBE NEWLOG again.

START DBE disallowed. Need rollforward recovery. (DBERR 3102)

The DBEnvironment is still in a fuzzy state. Either you are attempting a START DBE or START DBE NEWLOG on a restored version of an online backup of the DBEnvironment, OR you have performed some but not all the necessary rollforward recovery on this DBEnvironment.

Check the previous rollforward steps if any. Perform as many RECOVERLOG steps with as many logs as necessary to reach the matching COMMIT ARCHIVE point in the log file.

There are no more logs to switch to. (DBERR 3103)

This is different from a log full condition. Essentially, if the user attempts to overwrite an archive checkpoint, DBCore will first try to switch to the next log. If this operation fails, the above error is generated.

Check to see if indeed an attempt was made to overwrite an existing archive checkpoint. If the need is genuine, use the ADDLOG command in SQLUtil to add one or more new logs.

START DBE disallowed: DBEnvironment points to a wrong log file. (DBERR 3106)

You did not follow your static restore of a DBEnvironment with the NEWLOG command.

Restore DBEnvironment again and perform a NEWLOG command.

Invalid LONG column I/O syntax. (DBERR 3200)

You specified a long column input or output target which is not correct.

Check the > or < I/O redirection syntax.

Invalid LONG column file name. (DBERR 3201)

The file name is incorrect.

Refer to A Beginner's Guide to HP-UX for file naming conventions.

LONG column file path length too long. ! maximum. (DBERR 3204)

The pathname exceeds the maximum length allowed.

Shorten the pathname.

LONG column file access error in module !(!), status code !. (DBERR 3205)

There is a problem with the file used as the input or output device in a LONG column operation. Either the file does not exist, cannot be read, or cannot be written to.

Ensure that the file exists and has the appropriate permissions.

LONG column file already exists. (DBERR 3206)

The output file exists but the OVERWRITE option was not specified.

Remove the file or add the OVERWRITE option.

LONG column shared memory failed. (DBERR 3207)

The shared memory id cannot be attached. The shared memory id may be missing or is incorrect.

Verify that you are using the correct shared memory id. Use the ipcs command to double-check the allocated shared memory.

LONG columns exceed maximum 40 columns. (DBERR 3208)

You entered more than 40 LONG columns.

Reduce the number of LONG columns.

Negative length value not allowed for LONG column INSERT. (DBERR 3210)

You specified a negative value for the length of the long value to be read from the shared memory.

Remove the unary minus sign from the length specification and reissue the statement.

Length specified is greater than allowed. (DBERR 3211)

The length of the long value to be read from the shared memory is too large.

Specify a shorter length for the shared memory and reissue the statement.

LONG column disallowed from remote access. (DBERR 3220)

You tried to access a long column on another machine.

This feature is not supported yet.

LONG column disallowed on ORDER BY/DISTINCT/UNION. (DBERR 3221)

You tried to use an ORDER BY, DISTINCT or UNION on a column defined as a long data type.

Remove the long column from ORDER BY, DISTINCT or UNION clause.

LONG column disallowed on GROUP BY. (DBERR 3222)

You tried to use the GROUP BY clause with a column defined as a long data type.

Remove the long column from the GROUP BY clause.

LONG column disallowed on Expression. (DBERR 3223)

You tried to use an expression with a column that has been defined as a long data type.

Remove the long column from the expression.

LONG column disallowed on INDEX. (DBERR 3224)

You tried to create an index on a column defined as a long data type.

Remove the long column from the column list in the CREATE INDEX statement.

LONG column disallowed on HASH. (DBERR 3225)

You tried to specify a hash structure on a column that has been defined as a long data type.

Remove the UNIQUE HASH clause from the CREATE TABLE syntax, or the long column from the UNIQUE HASH clause.

LONG column disallowed on INSERT from SELECT. (DBERR 3226)

You tried to insert a column defined as a long data type in a type II INSERT statement.

Remove the long column from the SELECT clause in the INSERT statement.

Long fields cannot be replicated. (DBERR 3227)

You attempted to replicate a long data type field.

Remove the long column from the replicate statement.

Log lock point specified is invalid. (DBERR 3228)

An invalid log lock point was specified.

Change to a valid log lock point.

Invalid node type ! not allowed inside atomic block. (DBERR 3241)

The specified node type is not valid inside an atomic block.

Change to a valid node type.

Atomic block does not exist while requesting end atomic operation. (DBERR 3242)

There is an end for an atomic operation without it being started.

Correct the atomic block commands.

Execution failed causing rollback work inside atomic block. (DBERR 3244)

The execution failed within an atomic block.

Review the commands within the atomic block and correct the problem.

Atomic block started already. Nested atomic block is not allowed. (DBERR 3245)

You have specified a nested atomic block.

Remove the nested atomic block.

Incorrect data type declared for input/output parameter. (DBERR 3248)

The input or output parameter has an incorrect data type.

Change to the correct data type.

DBEFile ! is currently DETACH-ed. (DBERR 3300)

You attempted to DETACH an already DETACHed DBEFile.

None.

Attempting to ATTACH an already attached DBEFile !. (DBERR 3301)

You attempted to ATTACH an already ATTACHed DBEFile.

None.

Cannot DETACH the SYSTEM DBEFileset or any DBEFile in it. (DBERR 3302)

You attempted to DETACH a SYSTEM DBEFileset or a DBEFile in the SYSTEM DBEFileset.

If the reason for DETACHment is media failure, perform a complete rollforward recovery.

DBEFileset ! is currently DETACH-ed. (DBERR 3303)

You attempted to DETACH an already DETACHed DBEFileset.

None.

Attempting to ATTACH an already attached DBEFileset !. (DBERR 3304)

You attempted to ATTACH an already ATTACHed DBEFileset.

None.

Cannot DROP DBEFile ! while online backup is in progress. (DBERR 3305)

You attempted to DROP a DBEFile after the online backup has started, but before it has finished.

Wait until the online backup completes and resubmit the command.

Attempting to access DBEFile ! which is currently DETACH-ed.(DBERR 3306)

You attempted to read/write data from a detached DBEFile.

ATTACH a DBEFile (partial or full rollforward recovery may be needed before ATTACHing), and restart the transaction.

Cannot partially rollforward the SYSTEM DBEFileset or any DBEFile in it. (DBERR 3307)

You attempted to perform a partial rollforward on the SYSTEM.DBEFileSet or a DBEFile in the SYSTEM DBEFileSet.

Perform a complete rollforward recovery.

OMNIBACK error !. (DBERR 3308)

OMNIBACK has encountered some problem trying to store/restore DBEnvironment file(s).

Please refer to the OMNIBACK manual.

DBECreator ! does not exist on the system. (DBERR 3309)

The DBECreator named does not exist on the system.

Use a correct DBECreator name for this system.

Cannot specify pseudo-mapped access for DBECon or DBEFile0. (DBERR 3310)

Pseudo-mapped was specified for DBECon or DBEFile0. They cannot be pseudo-mapped.

Remove pseudo-mapping from the DBECon or DBEFile0 file.

Command disallowed: user not DBECreator or does not have maintenance word. (DBERR 3311)

You are not the creator of the DBEnvironment, or the maintenance word was not supplied.

Log on as DBECreator, or supply the maintenance word.

Maximum IMAGESQL DBEFILESET can not exceed ! pages. (DBERR 3500)

You attempted to add a DBEFile to IMAGESQL DBEFileSet which would cause the DBEFileSet to exceed its maximum size.

Add a DBEFile which does not violate the maximum number of pages with IMAGESQL DBEFileSet.

Grant TABLESPACE on ! DBEFILESET is not allowed. (DBERR 3501)

You attempted to modify default table space. This command is not allowed for users without ALLBASE/SQL license.

No action.

!.!(!) is not a permanent section or it is a procedure. (DBERR 3550)

You attempted to EXTRACT a section which is not a permanent section, or it is a procedure.

EXTRACT a section which is a permanent section and it is not a procedure.

TBL of ! is needed to EXTRACT !.!(!). (DBERR 3551)

The tuple buffer length is too small for the linear tree.

EXTRACT the section with larger buffer.

Section !.!(!) is a view. (DBERR 3552)

The specified section is a view. Views can not be extracted.

No action.

ALLBASE/SQL code buffer overflow at !. Query aborted. (DBERR 4000)

ALLBASE/SQL internal code buffer overflow. Input command was too long or too complicated.

Try to simplify the input command.

ALLBASE/SQL static buffer overflow at !. Query aborted. (DBERR 4001)

ALLBASE/SQL internal static buffer overflow. Input command was too long or too complicated.

Try to simplify the input command.

ALLBASE/SQL module buffer overflow at !. Query aborted. (DBERR 4002)

ALLBASE/SQL internal module buffer overflow. The executable tree for the module was too long.

Try to simplify the input command by breaking up your large query into multiple queries.

ALLBASE/SQL max query buffers exceeded. Query aborted. (DBERR 4003)

ALLBASE/SQL internal query buffer overflow. Input command was too long or too complicated.

Try to simplify the input command. Refer to base tables instead of to views as much as possible.

ALLBASE/SQL input heap overflow at ! - Query aborted. (DBERR 4004)

ALLBASE/SQL internal input heap overflow. Input command was too long or too complicated.

Try to simplify the input command. Reduce the amount of table and column qualifications as much as possible. If necessary, record as much information as possible and contact your HP Service Representative or Response Center.

ALLBASE/SQL memory allocation failed. (DBERR 4005)

ALLBASE/SQL cannot allocate run-time memory. This may be an internal ALLBASE/SQL problem or an operating system problem.

The requested operation cannot be performed. Try starting the database later, issuing the problem operation earlier in the session. Report this problem to your database administrator and system administrator.

ALLBASE/SQL memory deallocation failed. (DBERR 4006)

ALLBASE/SQL cannot deallocate (return for re-use) run-time memory. This may be an internal ALLBASE/SQL or an operating system problem.

After this error occurs, you may continue normal processing. The problem becomes a serious one when a long session eventually uses up all space and can not obtain any more space. Report this problem to your database administrator and system administrator.

ALLBASE/SQL UPDATE STATISTICS ! mismatch with DBCore. (DBERR 4007)

Internal error.

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

ALLBASE/SQL shared memory lock allocation failed in DBCore. (DBERR 4008)

ALLBASE/SQL ran out of run-time control block space. Your transaction was rolled back.

In multi-user mode, try your query again later

or

issue the ALTDBE command in SQLUtil to increase the number of control block pages

or

use LOCK TABLE so that individual pages are not locked

or

you may be able to use BEGIN WORK CS or BEGIN WORK RU to prevent this error.

ALLBASE/SQL shared memory allocation failed in DBCore. (DBERR 4009)

ALLBASE/SQL ran out of run-time control block space. Your transaction was rolled back.

In multi-user mode, try your query again later

or

issue the ALTDBE command in SQLUtil to increase the number of control block pages

or

use LOCK TABLE so that individual pages are not locked

or

you may be able to use BEGIN WORK CS or BEGIN WORK RU to prevent this error.

ALLBASE/SQL lock limit for session exceeded. (DBERR 4010)

The total number of locks currently in place for your user session is at the limit specified in the hpsqldebug environment variable.

Either delete the environment variable or else set it to a higher value.

ALLBASE/SQL pseudocode error. (DBERR 4012)

Internal error. ALLBASE/SQL opcode is invalid.

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

ALLBASE/SQL tmp buffer overflow at !. Query aborted. (DBERR 4013)

A temporary, internal SQL buffer overflowed.

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