Chapter 4 ALLBASE/SQL Error Messages 1-1011

Command buffer currently empty. (DBERR 1)

You issued a RECALL [CURRENT], CHANGE, or START command before any commands had been stored in the command buffer.

Use the HOLD, RECALL FILE, or RECALL HISTORY command to put information into the command buffer.

Problem with large command. Maximum length is !. (DBERR 2)

New string replacement on CHANGE command caused an overflow of the command buffer

or

the storage file could not be opened when trying to store the large command.

Modify the new string so that the length of the string in the command buffer is less than or equal to 2048 bytes

or

you may be out of disk space. Contact your system administrator.

'!' not found. (DBERR 3)

The search pattern you gave in the ISQL CHANGE command was not found in the command buffer.

Check your spelling and issue the CHANGE command again, specifying a valid search pattern.

The requested editor could not be scheduled. (DBERR 4)

The editor you specified in the EDITOR option of the SET command does not exist.

Check your spelling and issue the SET command again, specifying the correct name for the editor requested. If you still receive this message, contact your system administrator.

Number of copies must be in the range 1..20. (DBERR 5)

The number of copies you specified in the browse PRINT option must be in the range of 1 to 20.

Issue the PRINT command again, specifying a value from 1 through 20.

Error erasing file '!'. (DBERR 7)

You do not have the required permission to delete the specified file.

Check your spelling and issue the command again. If you still receive this message, no action is necessary; you cannot erase the specified file.

No help for command '!'. (DBERR 8)

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

Issue the HELP command again, specifying a valid command name. Enter HELP @ to obtain a list of the ISQL and SQL commands.

Column name list must be terminated by ')'. (DBERR 11)

The right parenthesis was missing after the last column name specified in the INPUT command.

Issue the command again, with column names enclosed in parentheses.

Column names must be enclosed in parentheses. (DBERR 12)

The list of column names in the INPUT command was not surrounded by parentheses.

Issue the command again, with column names enclosed in parentheses.

! not a column name in table !. (DBERR 13)

The column you specified in the LOAD EXTERNAL command does not exist in the table specified.

Use the INFO command to check which columns are in the specified table.

'!' is not acceptable as a name for a stored command. (DBERR 14)

The name you specified for a command file did not conform to operating system specifications. The command was not stored.

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

'!' is not acceptable as a file name. (DBERR 15)

The name you specified as a file name did not conform to operating system specifications.

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

'!' cannot be found. (DBERR 17)

The file name you specified does not exist or was entered incorrectly.

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

Error opening file '!'. (DBERR 18)

The file you specified is currently being accessed.

Wait until a later time to access the file.

Valid options are F[ILE], S[ET], H[ISTORY], I[NSTALL]. (DBERR 19)

The option you specified in the LIST command is not a valid option.

Issue the command again, specifying a valid option. Refer to the ALLBASE/ISQL Reference Manual for additional information on the LIST command.

Valid options are F[ILE], C[URRENT], H[ISTORY]. (DBERR 20)

The option you entered for the RECALL command is not a valid option.

Issue the command again, specifying a valid option. Refer to the ALLBASE/ISQL Reference Manual for additional information on the RECALL command.

Cannot continue with INPUT command. (DBERR 21)

Another error caused the INPUT command to be discontinued. An additional error message will be returned.

Refer to the cause and action of the additional error.

No column selected from table !. (DBERR 27)

You did not specify a column name in the LOAD command.

Issue the LOAD command again, specifying a column name.

History number must be in the range 1..!. (DBERR 28)

The number you specified in the LIST HISTORY or RECALL HISTORY command was out of the acceptable range.

Issue the command again, specifying a number from 1 through 10.

Valid options are Y[ES] and N[O]. (DBERR 29)

The option you entered for the END, LOAD, STORE, or EXIT command is not a valid option.

Issue the command again, specifying a valid option. Refer to the ALLBASE/ISQL Reference Manual for additional information on these commands.

Column is beyond end of record in load file on line #!. (DBERR 30)

At least part of one of the data fields that you specified was beyond the end of the record in the load file. The record was ignored and no data was loaded into the table from the record.

Check the description given for the load file. Make sure the starting location for each field is not beyond the end of the record. Also, check that the length specified for each field does not cause part of the field to be beyond the end of the record. The starting location plus the length should be equal to or less than the record length. Unless the last field in the load file record is a VARCHAR field, all load file records should be the same length.

Search pattern is beyond end of record on line #!. (DBERR 31)

The starting position of the search pattern you specified was beyond the end of the record. The record was ignored and no data was loaded into the table from the record.

Verify the starting position of the search pattern and issue the LOAD command again.

Valid options are ON and OF[F]. (DBERR 32)

The option value you specified for the AUTOCOMMIT, CONTINUE, or ECHO option of the SET command was not a valid option.

Issue the command again, specifying a valid option. Refer to the ALLBASE/ISQL Reference Manual for additional information on the SET command.

Invalid command. (DBERR 33)

The command you entered while viewing the results of a SELECT statement was not valid.

Valid commands are u[p], d[own], l[eft], r[ight], t[op], b[ottom], pr[int], e[nd], and p[ause].

FETCH is not allowed in ISQL. (DBERR 34)

You issued a FETCH statement while in ISQL.

The FETCH statement can only be used in application programs. Refer to the ALLBASE/SQL Reference Manual for additional information.

Error reading from SelectFile. (DBERR 35)

One or more users are accessing the same output file that you specified in the OUTPUT option of the SET command.

Change the name of the output file using the OUTPUT option of the SET command.

Problem executing such a long command. (DBERR 36)

This is an internal error that occurs while executing an SQL statement whose length is greater than 1.5 megabytes.

Record as much information as possible and contact your HP Service Representative or Response Center. You can work around this problem by shortening the length of your command to less than 1.5 megabytes.

ISQL command too long. (DBERR 37)

The number of characters in the ISQL command exceeded the maximum limit of 2048 bytes.

Issue the command again, within the valid limits.

SYSTEM command unsuccessful. Return code is !. (DBERR 38)

The operating system command you issued from ISQL is valid but cannot be executed.

Refer to the /usr/include/sys/errno.h file for a brief explanation of the error code returned.

File '!' already exists. (DBERR 39)

The file name you specified to RENAME a file already exists.

If you do not want to overwrite the existing file, reenter the RENAME command specifying a unique file name. Otherwise, either use the ERASE command to remove the existing file or use the RENAME command to rename the existing file first.

Error attempting to rename '!' to '!'. (DBERR 40)

The ISQL RENAME failed because the file is being accessed

or

you do not have write permission to the file.

Issue the command again, when the file is no longer being accessed

or

contact a user who has write permission to the specified file.

Internal error: Error on rename from '!' to '!'. (DBERR 41)

The ISQL RENAME command failed due to an internal error.

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

Unable to open work file. (DBERR 42)

The file you specified in the SELECT statement cannot be opened because it is being accessed already

or

you do not have write permission in the current directory

or

you are out of disk space.

Wait until the file is not being accessed

or

contact your system administrator.

Bad numeric input. (DBERR 43)

You entered a character where a numeric value was expected.

Issue the command again, specifying a numeric value.

Invalid option. (DBERR 44)

The option you specified in the SET command is not one of the valid options. The command is aborted and no option is set.

Issue the command again, specifying a valid option. The valid options for the SET command are: autoc[ommit], autos[ave], c[ontinue], ec[ho], ed[itor], es[cape], f[raction], n[ull], ou[tput], ow[ner], pa[gewidth], and pr[ompt]. Refer to the ALLBASE/ISQL Reference Manual for additional information on the SET command.

Column ! has already been specified. (DBERR 45)

You specified the same column name twice in the LOAD command.

Issue the LOAD command again, with each column name specified only once. Refer to the ALLBASE/SQL Reference Manual for more information on the LOAD command.

Command buffer empty, STORE not performed. (DBERR 46)

The STORE command works only on information in the ISQL command buffer.

Use the HOLD or RECALL command to put information into the command buffer, then issue the STORE command again.

Missing parameters from command file. (DBERR 47)

The command file you specified in the START command was missing parameters essential to its function.

Check the command buffer or command file specified in the START command to make sure that all required parameters are there. Refer to the ALLBASE/SQL Reference Manual or ALLBASE/ISQL Reference Manual for additional information on the command(s) specified.

Last command not terminated in command file - ignored. (DBERR 49)

The last command you executed in the command file was not terminated with a semicolon (;)

or

the last line in the command file was a comment or blank line.

Correct the command file so that all commands are terminated with a semicolon (;)

or

reissue the commands which were not executed.

Fraction length must be in the range 0..18 (DBERR 50)

The fraction length you specified in the FRACTION option of the SET command was not within the acceptable range. The fraction length was not changed.

Issue the command again, specifying a fraction length between 0 and 18.

Column ! can't be null. You MUST load this column. (DBERR 51)

The LOAD command did not specify a column that was created with the NOT NULL attribute.

Issue the command again, specifying any column created with the NOT NULL attribute.

Internal error trying to load data. (DBERR 52)

An unsuccessful BULK INSERT in DBCore. An additional error message will be returned.

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

Pagewidth must be in the range 10..254. (DBERR 53)

The PAGEWIDTH option you specified in the SET command was not within the valid range. The page width was not changed.

Issue the command again, specifying a page width in the range of 10 through 254.

AutoSave count must be in the range 1..32767. (DBERR 54)

The AUTOSAVE option you specified in the SET command was not within the valid range. The number of rows remains the same.

Issue the command again, specifying an Autosave count in the range of 1 through 32,767.

Problem getting help. (DBERR 55)

Internal error.

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

Output file name must be no more than ! bytes. (DBERR 56)

The output file name you specified in the command is not a valid system file name.

Refer to the A Beginner's Guide to HP-UX for additional information on file naming conventions.

Prompt must be no more than ! bytes. (DBERR 57)

The prompt you specified in the PROMPT option of the SET command exceeded the maximum length of 16 bytes.

Issue the command again, specifying a valid prompt length.

Null character must be a single one-byte character. (DBERR 58)

You specified more than a single one-byte character as the null indicator in the LOAD or UNLOAD EXTERNAL command.

Issue the command again, specifying only a single one-byte character as the null indicator.

Command file execution terminated. (DBERR 60)

Execution was terminated because of an error in the command file. An additional error message will be returned.

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

Escape character must be a single one-byte character. (DBERR 61)

You specified more than a single one-byte character in the ESCAPE option of the SET command. The ESCAPE option was not changed.

Issue the command again, specifying a single one-byte character in the ESCAPE option.

SQLCORE not available. (DBERR 62)

There is an ALLBASE/SQL linking problem.

Contact your system administrator.

Internal error: Unrecognized status code: !. (DBERR 63)

Internal error.

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

Semantic error. (DBERR 64)

An additional message will be returned.

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

Name of editor must not be more than ! bytes. (DBERR 66)

The editor name you specified in the EDITOR option of the SET command exceeds the maximum limit of 255 bytes (including slashes). The EDITOR option was not changed.

Issue the SET command again, with a valid name specified in the EDITOR option.

Command buffer cannot be executed from command file. (DBERR 67)

The command file you specified contains a START command to execute the command buffer. A command file can start other command files, but cannot start the command buffer.

Remove the START command to execute the command buffer from the command file. Refer to the ALLBASE/ISQL Reference Manual for additional information on the START command.

Illegal table name. (DBERR 69)

The table name you specified in the INFO, UNLOAD, or INPUT command was not a valid table name.

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

Valid options are E[XTERNAL] and I[NTERNAL]. (DBERR 73)

The option you specified for the LOAD or UNLOAD command was not a valid option.

Issue the command again, specifying either EXTERNAL or INTERNAL. Refer to the ALLBASE/ISQL Reference Manual for additional information on the LOAD and UNLOAD commands.

Invalid option '!'. (DBERR 74)

The option you specified in the SET command was not a valid option.

Issue the command again, specifying only valid options. Refer to the ALLBASE/ISQL Reference Manual for valid options and additional information on the SET command.

End of file encountered on input. (DBERR 76)

You reached EOF on standard input. The program was terminated.

No action is necessary.

Could not schedule !. (DBERR 77)

SQLUtil or SQLGEN could not be scheduled because execute permission is denied

or

if ALLBASE/SQL was installed in a directory other than usr/bin, SQLUtil and SQLGEN cannot be executed from within ISQL.

Check to make sure that SQLUtil and SGLGEN are in usr/bin. If they are not, contact your system administrator.

Missing keyword FROM. (DBERR 78)

You tried to execute a LOAD or UNLOAD command without specifying the keyword FROM.

Issue the command again, specifying the FROM keyword. Refer to the ALLBASE/ISQL Reference Manual for additional information on the LOAD and UNLOAD commands.

Missing keyword TO. (DBERR 79)

You tried to execute a LOAD or UNLOAD command without specifying the keyword TO.

Issue the command again, specifying the TO keyword. Refer to the ALLBASE/ISQL Reference Manual for additional information on the LOAD and UNLOAD commands.

File is not in INTERNAL format. (DBERR 81)

The input file name you specified in the LOAD command was not unloaded with the INTERNAL option

or

the file name you specified does not exist or was entered incorrectly.

Issue the LOAD command again, specifying the EXTERNAL option

or

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

Unidentified error ! occurred on last command. (DBERR 82)

Internal error.

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

Command buffer cannot be executed from command buffer. (DBERR 83)

The command buffer contains a START command to execute the command buffer. The command buffer can start a command file, but cannot start itself recursively.

Remove the START command to execute the command buffer from the command buffer. The CHANGE command may be used to make this modification. Refer to the ALLBASE/ISQL Reference Manual for additional information on the START command.

New command exceeds maximum. (DBERR 84)

The maximum limit of 2048 bytes was exceeded when you used the insert subcommand of the REDO command.

Issue the command again, so that the total number of bytes in the command is less than or equal to 2048.

Bad bytes after delete command. (DBERR 85)

You entered an invalid option after the delete subcommand of the REDO command.

Issue the command again, specifying only valid options after the delete subcommand. Refer to the ALLBASE/ISQL Reference Manual for valid options and additional information on the REDO command.

Extra bytes. (DBERR 86)

The bytes that you entered after the i, h, x, b, or e subcommands of the REDO command are invalid.

Issue the REDO command again. Refer to the ALLBASE/ISQL Reference Manual for additional information on the REDO command.

Must break line - too long. (DBERR 87)

The bytes you added to the command using the insert subcommand of the REDO command caused the line to be greater than the maximum limit of 80 bytes.

Use the break subcommand before using the insert subcommand again. Refer to the ALLBASE/ISQL Reference Manual for additional information on the REDO command.

No plus or minus sign. (DBERR 88)

You used more than one + or - sign in the same line in the REDO command.

If you want to go forward or backward more than one line, use the +n or -n subcommand (where n is an integer). Refer to the ALLBASE/ISQL Reference Manual for additional information on the REDO command.

No command to edit. (DBERR 89)

You attempted to execute a REDO command when the command history buffer was empty.

No action is necessary.

Redo not allowed in command buffer/command file - ignored. (DBERR 90)

You included a REDO command in either the command buffer or command file.

Remove the REDO command and execute the command buffer or command file again.

Problem opening installation file. (DBERR 91)

Internal error.

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

Problem reading from installation file. Code = !. (DBERR 92)

The installation file you specified did not contain a module. No module was generated for the preprocessed application.

No action is necessary. An installation was not required to run this application.

Empty installation file. (DBERR 93)

The installation file you specified is empty.

No action is necessary.

Installation stopped due to error. (DBERR 94)

The file name you specified in the INSTALL command was not a valid file name

or

the file you specified is currently being accessed by another user.

Issue the command again, specifying a valid file name

or

wait until the file is not being accessed before issuing the command again.

File is not an installation file or it is corrupted. (DBERR 95)

The name of the file you specified in the ISQL INSTALL command was not an installation file

or

the installation file is corrupted.

Correct the file name and issue the INSTALL command again

or

regenerate the installation file by re-preprocessing the application.

Host variables or dynamic parameters not allowed through ISQL. (DBERR 96)

The command you submitted through ISQL contains a host variable or a dynamic parameter.

Substitute a constant value or column name for the host variable or dynamic parameter. If you need to use variables or dynamic parameters in SQL statements, you must do so via an application program. Refer to the appropriate ALLBASE/SQL application programming guide for additional information.

Cannot continue with SELECT. (DBERR 97)

An error occurred which caused the SELECT statement to terminate. An additional message will be returned.

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

Invalid character for null indicator. (DBERR 150)

The character you specified for the null indicator in the LOAD or UNLOAD EXTERNAL command was invalid.

Issue the command again, specifying any single one-byte character for the null indicator except a single quote, double quote, semi-colon, blank, or the current escape character.

File created with different product or version, or not an INTERNAL file. (DBERR 151)

The input file you specified in the LOAD command was created from a different product or a different version of ISQL

or

the file was UNLOADed using the EXTERNAL option.

UNLOAD the data to create a file from the current version specifying the INTERNAL option and issue the LOAD command again

or

issue the LOAD command again, specifying the EXTERNAL option.

INSTALL file created with different product or version. (DBERR 152)

The file you specified in the INSTALL command was created from a different product or different version of the preprocessor you are using.

Re-preprocess your program to create an installable module file from the current version, then issue the INSTALL command again.

EXECUTE IMMEDIATE cannot be used for !. (DBERR 175)

You cannot dynamically preprocess the specified command.

Re-submit the command without using the EXECUTE IMMEDIATE statement to host it. Refer to the ALLBASE/SQL Reference Manual for a list of statements that can be executed using EXECUTE IMMEDIATE.

! cannot be used interactively. (DBERR 176)

The command you specified can only be used in an application program.

Refer to the ALLBASE/SQL Reference Manual for additional information on the specified command.

SELECT cannot be preprocessed interactively with PREPARE. (DBERR 177)

You tried to PREPARE a SELECT statement interactively.

You can either PREPARE a SELECT programmatically or issue the SELECT statement directly or in a command file. Refer to the ALLBASE/ISQL Reference Manual for additional information.

Number of nested start files exceeds maximum. (DBERR 193)

There are more than ten levels of nesting of command files. This error may result from an unintended recursive START command. A maximum of ten command files can be in use at one time.

Rewrite your command files so that there are ten or fewer levels of nesting. Remove any recursive START commands.

Invalid starting row. (DBERR 201)

The value you specified for the starting row is not a positive integer.

Issue the LOAD command again, specifying a positive integer.

Invalid number of rows. (DBERR 202)

The number of rows you specified is not a positive integer.

Issue the LOAD command again, specifying a positive integer for the starting row.

Failed to free heap space. (DBERR 211)

Internal error.

Report this error to your database administrator. If the problem persists, record as much information as possible and contact your HP Service Representative or Response Center.

Failed to get heap space. (DBERR 212)

There was no memory available for your query.

Report this error to your database administrator and try your query later. If this problem persists, record as much information as possible and contact your HP Service Representative or Response Center.

Insufficient file space on disc(s). (DBERR 213)

There is not enough file space on the disk(s) to complete the transaction.

Contact your system administrator.

Security violation, permission denied. (DBERR 220)

You do not have the required capability for the operation attempted.

Check that you have write-access to the directory where you are located. Contact your system administrator to get the required capability.

Total output width exceeds maximum of !. (DBERR 230)

The output length you specified in the UNLOAD EXTERNAL command exceeded the maximum width of 7,990 bytes.

Issue the UNLOAD command again, specifying an output length less than or equal to 7,990. If you require a length greater than 7,990 bytes, issue the UNLOAD command specifying the INTERNAL option.

Owner name must be no more than ! bytes. (DBERR 231)

The length of the Owner name you specified exceeds the maximum length allowed for owner names.

Issue the command again, specifying a shorter owner name.

ISQL internal error. (! !) (DBERR 237)

An internal error has caused a Pascal runtime, operating system, architected call interface (ACI), foreign data access (FDA) or Switch layer error.

The error message includes the type of error and error number. Refer to the cause and action in the appropriate message manual.

This session is not allowed to use the SYSTEM command. (DBERR 238)

This session is not allowed to use the System command.

No action is required.

Write failed on file '!'. (! !). (DBERR 250)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for a brief explanation of the error code returned.

Read failed on file '!'. (! !). (DBERR 251)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for a brief explanation of the error code returned.

Seek failed on file '!'. (! !). (DBERR 252)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for a brief explanation of the error code returned.

LONG data types not allowed through UNLOAD INTERNAL. (DBERR 253)

You attempted to use the UNLOAD command with the INTERNAL option for LONG data type columns.

Use the EXTERNAL option with the UNLOAD command.

SELECT statement length exceeds maximum of ! bytes. (DBERR 256)

The length of the SELECT statement in the UNLOAD command exceeds the maximum of 2048 bytes.

Use the SELECT statement to define a view, and then unload from the view.

Unable to split error message into multiple lines. (DBERR 257)

There was an internal error.

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

Invalid flagger name. (DBERR 263)

An invalid flagger name was specified in the SET FLAGGER statement.

Specify a valid flag name. Currently, the only flagger name supported is "FIPS127.1". Do not include quotes. It is not case sensitive.

Invalid UNLOAD INTERNAL syntax after table name. (DBERR 284)

The UNLOAD INTERNAL syntax after the table name is invalid.

No action is required.

Open failed on file '!'. (! !). (DBERR 300)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for a brief description of the error code returned.

Close failed on file '!'. (! !). (DBERR 301)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for a brief description of the error code returned.

This command is not valid for FDA usage. (DBERR 308)

You specified an ISQL command that cannot be used when connected to a foreign database.

No action necessary.

Already connected. (DBERR 309)

You have already connected to the specified database.

No action necessary.

Invalid CHANGE syntax. (DBERR 310)

The parameter of the CHANGE command is either missing a delimiter or contains an invalid character.

Insert the missing delimiter or delete the invalid character and issue the CHANGE command again.

Invalid characters after RELEASE. (DBERR 311)

Non-blank characters follow the RELEASE statement.

Issue the RELEASE statement with no trailing, non-blank characters.

Invalid EXIT syntax. (DBERR 312)

Non-blank characters follow the EXIT command.

Issue the EXIT command with no trailing, non-blank characters.

Invalid characters after SAVEPOINT. (DBERR 313)

Non-blank characters follow the SAVEPOINT statement.

Issue the SAVEPOINT statement with no trailing, non-blank characters.

DO/REDO pattern not found. (DBERR 314)

The pattern you specified with the DO or REDO command is not in the command history buffer.

Find the correct pattern with the "LIST HISTORY @" command and issue the DO or REDO command again with the correct pattern.

Invalid keyword after PREPARE. (DBERR 315)

You can not use the REPEAT option in a PREPARE statement in ISQL.

Issue the PREPARE statement again without the REPEAT option.

Unsupported Format Type with CONVERT option. (DBERR 340)

The SET CONVERT option is not OFF, and the format type of the input file data specified in the LOAD command is not valid for the target ALLBASE/SQL column.

Issue the LOAD command again with the correct format type. If you did not intend to convert the data in the input file, execute the SET CONVERT OFF command and issue the LOAD command again.

Description file not allowed with CONVERT option. (DBERR 341)

You specified a description file in the LOAD command when the SET CONVERT option is not OFF.

Issue the LOAD command again without the description file parameter. If you did not intend to convert the data in the input file, execute the SET CONVERT OFF command and issue the LOAD command again.

Unsupported Data Format. (DBERR 342)

The SET CONVERT option is not OFF, and the data type of the ALLBASE/SQL column specified in the LOAD command is unsupported.

Issue the LOAD command with an ALLBASE/SQL data type that is supported by the conversion operation. If you do not want to convert the data in the input file, execute the SET CONVERT OFF command and issue the LOAD command again.

Data type of ! not supported with the CONVERT option. (DBERR 343)

The SET CONVERT option is not OFF, and the data type of the ALLBASE/SQL column specified in the LOAD command is unsupported.

Issue the LOAD command with an ALLBASE/SQL data type that is supported by the conversion operation. If you do not want to convert the data in the input file, execute the SET CONVERT OFF command and issue the LOAD command again.

Unable to load native language information. (DBERR 400)

The character set attribute and upshift tables for your language could not be loaded.

Contact your system administrator.

Delimiter must be a single-byte character. (DBERR 401)

You used a multi-byte character as the delimiter in a CHANGE command.

Issue the CHANGE command again, using a single-byte character as the delimiter.

Invalid replacement/insertion string. (DBERR 402)

In the REDO command, you specified a replacement or insertion string containing invalid bytes.

Issue the insert or replace command again, specifying a valid string.

Internal native language support error. (DBERR 403)

An internal Native Language Support error occurred, probably due to an invalid character in input.

Issue your command again, specifying valid input. If this does not solve the problem, contact your system administrator.

Error ! occurred while opening file. (DBERR 501)

Error occurred while you were opening a file. Usually the error is due to file permissions, or the name being misspelled.

Check the name of the file to determine if it is spelled correctly, and check the file permissions assigned.

Invalid Command. (DBERR 503)

You entered a command that SQLAudit does not recognize.

Check the last command entered.

Invalid Lock Point found in Audit Point File. (DBERR 504)

The Audit Point File contains a log file lockpoint that is invalid. You probably used a Recovery File (generated by the AUDIT command) for the Audit Point file for the LOCK AUDITPOINT command.

LOCK AUDITPOINT should only use Audit Point files that were generated by calling GET AUDITPOINT.

Log history does not go back far enough for partition !. (DBERR 507)

This error indicates that the log files have wrapped around and overwritten some of the committed transactions for the partition. If this is encountered, the specified partition will be dropped from the list of auditable partitions.

To prevent this from happening, LOCK AUDITPOINT can be used to protect transactions committed after the beginning audit point is defined. If it is necessary to get the unaudited transactions, the SQLUtil command WRAPDBE can be used to retrieve them. See the ALLBASE/SQL Database Administration Guide to determine how best to do this.

Unable to open scan for partition ! due to status of !. (DBERR 508)

An unexpected error occurred while opening the log file scan for the given set of partitions.

Contact your HP Service Representative or Response Center.

Log scan could not be successfully opened. (DBERR 512)

Due to previous errors, the log scan could not be opened. No auditing is possible for the given list of partitions when this happens.

Verify the list of partitions is correct and check the previous reported errors to determine possible actions.

Error ! occurred while reading Audit Point File. (DBERR 513)

A file system error occurred while reading the Audit Point File. Usually this may occur if an invalid Audit Point File has been entered.

Check the file name entered to determine if correct.

File is not a valid Audit Point File. (DBERR 514)

SQLAudit has determined that the file is not an Audit Point File.

Check the file name entered to determine if correct.

Error ! occurred while writing Audit Point File. (DBERR 515)

You encountered a file system error while trying to create and write out the audit point information into the file. Usually this is caused by file permissions, or possibly lack of disk space.

Check to make sure the file name used was correct. If the file name is correct, make sure the file and/or directory permissions are correct and that there is enough space to write the file.

Native Language Support Error ! encountered. (DBERR 517)

A native language support (NLS) error was encountered by the last command. This usually means that the proper language was not correctly installed on the system, or that you may have an invalid language specified.

Check with the system administrator to insure that your language has been installed on the system, and check the language to ensure it is correct.

Non Existent File entered. (DBERR 519)

You entered a file name that does not exist on the system.

Check the file name that was entered to ensure it is correct.

Error ! occurred while closing file. (DBERR 520)

A file system error occurred while closing a file. This may be due to the file or directory permissions, or a lack of disk space on the system.

Check the file and directory permissions, and the amount of disk space on the system.

Invalid partition number entered. (DBERR 521)

You entered a partition number or name which is not allowed. Partition numbers must be in the range of 1 to 32767 inclusive. Valid partition names are DEFINITION, STORAGE, AUTHORIZATION, and SECTION.

Check the partition name or number that was entered.

Ending Audit Point missing partition instance ! (!). (DBERR 524)

This should only be possible if the database has been hard resynced by an ALLBASE/REPLICATE user.

Determine if the database is being used as a master or slave in an ALLBASE/REPLICATE environment and whether it has been hard resynced lately. If it has been hard resynced, a new beginning audit point should be defined after the hard resync has finished.

Transaction encountered that is greater than ending transaction for partition instance ! (!). (DBERR 526)

The only way this should be possible is if the ending audit point was not generated on the database that is being audited. For instance, if the ending audit point was generated using a different database then used against the audited DBEnvironment, this type of situation can arise.

Determine if the ending audit point file was actually generated against the DBEnvironment being audited.

Error ! occurred while opening Recovery File. (DBERR 527)

A file system error occurred while trying to create the recovery file. This is usually due to an incorrect name being used, or the file/directory permissions are not set correctly. This may also be due to a lack of disk space.

Check the recovery file name specified and make sure it does not exist before doing the audit. Also check disk space, and directory permissions.

Unacceptable response entered (will use default). (DBERR 529)

An invalid response was entered for the prompt. SQLAudit will use the default response (which is the first response listed).

Check the response that was entered.

SYSTEM command unsuccessful. Return code is !. (DBERR 533)

SQLAudit attempted to execute the system command that was entered and it encountered an error returned from the operating system.

Check the command entered to determine if it is a valid operating system command.

No help for that command. (DBERR 534) HELP keywords are GENERAL, MAIN, and SUMMARY. Type '//' to leave SQLAUDIT HELP.

You attempted to obtain help from SQLAudit on an unknown subject.

Check the subject entered. Allowed subjects are any SQLAudit command, or the keywords GENERAL, MAIN, or SUMMARY. If you wish to leave the SQLAudit help facility, type '//'.

The requested editor could not be scheduled due to error !. (DBERR 535)

SQLAudit was unable to start the editor that is currently set.

Check which editor is currently set (through the SET command). If the editor does not seem valid, change it through the SET EDITOR command. Also check to make sure it is possible to start the editor from outside SQLAudit.

SQLGEN Error detected. SQLExplain messages will follow. (DBERR 701)

An unexpected ALLBASE/SQL error occurred.

Read the accompanying SQLExplain message to determine the reason for the error and take corrective action. If the error persists, contact your database administrator.

Internal error. Missing message for SQLCODE of !. (DBERR 702)

The ALLBASE/SQL message catalog does not contain the message associated with error encountered.

Contact your database administrator.

Could not CONNECT to DBEnvironment. (DBERR 703)

SQLGEN could not connect to the DBEnvironment, possibly because the name was not entered correctly or the AUTOSTART option is OFF.

Correct conditions that may have caused the error. If the error persist contact your database administrator.

Error occurred while RELEASING DBEnvironment. (DBERR 704)

An ALLBASE/SQL error occurred while releasing the DBEnvironment.

Contact your database administrator.

Invalid Table Type encountered. RType = !. (DBERR 706)

Encountered an invalid RType in SYSTEM.TABLE.

Contact your database administrator.

Invalid DBEFile Type encountered. Type = !. (DBERR 707)

Encountered an invalid DBEFile in SYSTEM.DBEFILE.

Contact your database administrator.

Invalid Command Number encountered. Location = !. (DBERR 708)

An internal error has occurred.

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

Invalid SQLType encountered. SQLType = !. (DBERR 710)

An invalid column type was encountered for one of the tables being described.

Contact your database administrator.

Error occurred while opening file. (DBERR 711)

Failed to open file as a new file.

Read system error messages to determine the cause of the error and take corrective action. If error persists, contact your system administrator.

Error occurred while calling !. (DBERR 712)

File system error occurred while retrieving information about the schema.

Read system error messages to determine the cause of the error and take corrective action. If error persists, contact your system administrator.

Error occurred while closing file. (DBERR 714)

File system error occurred while attempting to close a file.

Read system error messages to determine the cause of the error and take corrective action. If error persists, contact your system administrator.

Error occurred while calling ! !. (DBERR 715)

File system error occurred while trying to rename the file from EXPSQLG to a schema file name.

Read system error messages to determine the cause of the error and take corrective action. If error persists, contact your system administrator.

SYSTEM command unsuccessful. Return code is !. (DBERR 716)

The operating system command you issued is valid but cannot be executed.

Refer to the /usr/include/sys/errno.h file for a brief description of the error code returned.

The requested editor could not be scheduled. (DBERR 717)

You may have entered an invalid editor name.

Read system error messages to determine the cause of the error and take corrective actions. If error persists, contact your system administrator.

Encountered ! ! while removing expsqlgn. (DBERR 719)

File system error occurred while purging the temporary file EXPSQLGN used during file expansion.

Read system error messages to determine the cause of the error and take corrective action. If error persists, contact your system administrator.

Encountered Error # ! while retrieving DBECon info. (DBERR 720)

An error occurred while calling a DBCore procedure.

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

Unacceptable editor name entered. (DBERR 721)

The editor name you entered is invalid. Check the spelling.

Enter a valid editor name.

Could not open specified file. (DBERR 722)

Failed to open an existing file.

Read the file system error messages to determine the cause of the error and take corrective action. If error persists, contact your system administrator.

Invalid option encountered on command line. (DBERR 723)

The option encountered on the command line contained an invalid parameter.

Make sure the command line contains only valid parameters.

Invalid Schema File name entered. (DBERR 724)

The Schema File name you entered did not match operating system naming conventions.

Reenter, using a valid Schema File Name.

Error occurred while writing to output file. (DBERR 725)

A file system error occurred while writing to the Schema File.

Contact your system administrator.

Error occurred while expanding file. (DBERR 726)

A file system error occurred while moving data from the Schema File to the temporary file EXPSQLGN.

Contact your system administrator.

Error occurred while appending to file. (DBERR 727)

A file system error occurred while opening the Schema File in APPEND mode.

Contact your system administrator.

Encountered EOF on input file. (DBERR 728)

The file you specified as redirected input ran out of commands before exiting SQLGEN.

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

Unacceptable response to prompt (will use default). (DBERR 729)

You entered an invalid response to the last prompt.

Enter a valid response.

Encountered error during ROLLBACK WORK. (DBERR 730)

An ALLBASE/SQL error was encountered during ROLLBACK WORK.

Contact your database administrator. If necessary, record as much information as possible, and contact your HP Service Representative or Response Center.

Invalid native language character encountered. (DBERR 744)

An unrecognized native language character was encountered. The character does not belong to the present character set as specified by the LANG environment variable.

Reenter the user input using only characters found in the character set of the current language.

Unexpected internal native language error encountered. (DBERR 745)

An unexpected error occurred while using an internal native language procedure.

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

Invalid Constraint Index Type encountered. (DBERR 746)

Internal Error.

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

Invalid Default Type encountered TYPE=<val> (DBERR 747)

Internal Error.

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

Invalid Constraint Type encountered. (DBERR 748)

Internal Error.

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

Syntax error. (DBERR 1001)

You entered the Command incorrectly.

Correct the syntax using the CHANGE or REDO command in ISQL, or use an editor to correct your source code. You can use the ISQL HELP command to verify your syntax.

Identifier too long. (DBERR 1002)

One of the keywords you specified in the SQL statement was too long. This was probably caused by a typographical error such as not leaving a blank space between keywords

or

one of the variable names you specified was too long.

Issue the command again correcting the keywords which were entered incorrectly

or

choose a variable name that is less than or equal to 30 bytes.

Single-quoted string too long. (DBERR 1003)

The string enclosed in single quotes in your SQL statement is too long.

Issue the command again, specifying a string which contains less than or equal to 3,996 bytes.

Expected end of string character. (DBERR 1004)

String was not terminated with a quotation mark.

Issue the command again terminating the string with a quotation mark.

Expected something between the double quotes. (DBERR 1005)

In the command where a database object was referenced, you did not specify an object name within the quotes.

Issue the command again, specifying an appropriate name within quotes.

Unexpected keyword. (DBERR 1006)

The syntax was incorrect for the command specified.

Refer to the ALLBASE/SQL Reference Manual for the correct syntax and issue the command again.

DBEnvironment name is too long. (DBERR 1007)

A DBEnvironment name is restricted to operating system file naming conventions.

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

Query too large. (DBERR 1008)

The internal buffer space has been exceeded.

Break the query into smaller units and issue the command again.

Double-quoted string too long. (DBERR 1009)

The string enclosed in double quotes was too long.

Issue the command again, specifying an object name containing less than or equal to 20 bytes.

Duplicate DBEFile0 clause defined. (DBERR 1010)

You specified the DBEFile0 clause twice in the START DBE NEW statement.

Issue the START DBE NEW statement again, specifying the DBEFile0 only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the START DBE NEW statement.

Duplicate LOG DBEFile clause defined. (DBERR 1011)

You specified the LOG DBEFILE clause twice in the START DBE NEW or START DBE NEWLOG statement.

Issue the command again, specifying the LOG DBEFILE only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the START DBE NEW and START DBE NEWLOG statements.