Chapter 2 ALLBASE/SQL Warning Messages

Output will be truncated. (DBWARN 1)

The SELECT statement generated rows that are longer than the size specified by the PAGEWIDTH option of the SET command. The pagewidth may be set to a maximum of 254 bytes.

Increase the pagewidth value using the ISQL SET command.

File '!' already exists. Next SELECT will overwrite. (DBWARN 2)

You have specified a file name that already exists as the output file for the results of a SELECT.

No action is necessary if you want to overwrite the existing file. Specify another output file name using the OUTPUT option of the ISQL SET command if you want output to go to a different file.

Column name ! truncated to ! bytes. (DBWARN 3)

A column name specified in the ISQL INPUT command was greater than 20 bytes. This probably occurred because you did not leave a space between column names. If the bytes which remained after the truncation formed an existing column name, the command was executed for that column.

Delete any rows that were incorrectly input. Issue the INPUT command again, separating the column names with spaces.

Parameter substitution caused overflow - command truncated. (DBWARN 4)

Substitution of parameter values into the command caused the command length to exceed 2048 bytes, necessitating truncation.

Try to rewrite the command so that the command length after parameter substitution will be no greater than 2048 bytes.

BULK not allowed interactively - ignored. (DBWARN 5)

You issued a BULK SELECT or BULK FETCH option while in ISQL.

Any SELECT performed in ISQL is automatically treated as a BULK SELECT. BULK is an option for programming with SQL only. Refer to the ALLBASE/SQL Reference Manual for additional information.

Transaction terminated. (DBWARN 6)

EOF was reached on input file.

SQLCore automatically rolled back the transaction. No action is necessary.

Commands after START ignored. (DBWARN 7)

You may not have any additional commands on the command line after a START command.

Refer to the ALLBASE/SQL Reference Manual for more information.

Numeric field error on line !, column !. (DBWARN 8)

The line number specified contains non-numeric data in the column indicated. The LOAD EXTERNAL command continues executing and loads a 0 value for that column.

Refer to the ALLBASE/ISQL Reference Manual for additional information on the LOAD EXTERNAL command.

Entire command has been deleted. (DBWARN 9)

You deleted the entire command using the REDO command.

No action is necessary.

Load file is empty. (DBWARN 10)

The file that you named in the LOAD EXTERNAL command is empty. No rows were processed.

No action is necessary.

LOAD command stopped because of error. (DBWARN 11)

An INTERNAL load could not be continued due to another error. An additional message will be returned.

Refer to the cause and action of the additional message.

Starting row is beyond end of load file. (DBWARN 12)

The starting row number specified in the LOAD PARTIAL command was beyond the last line of the file. No rows were loaded.

Issue the LOAD command again, specifying an appropriate starting row.

Number of rows specified exceeds number in load file. (DBWARN 13)

The number of rows specified in the LOAD PARTIAL command was greater than the number of rows between the starting row and the end of the file.

No action is necessary. All qualifying rows, from the starting row to the end of the file, were loaded.

User language and DBE language differ. (DBWARN 14)

You started or connected to a DBEnvironment with a language other than your current language.

Exit ISQL. Set your LANG environment variable and invoke ISQL.

Local catalog is inaccessible. Default catalog in use. (DBWARN 15)

The ALLBASE/SQL message catalog corresponding to your language cannot be accessed, probably because it does not exist.

Contact your system administrator.

Unable to load all local response options. (DBWARN 16)

One or more of the local response options was missing from the message catalog or contained invalid data.

Contact your system administrator.

Local response options are not unique. (DBWARN 17)

The local response options in the message catalog are not unique.

Contact your system administrator.

Field boundaries specified do not coincide with character boundaries. (DBWARN 18)

The byte at a starting location specified in the LOAD command is the second byte of a two-byte character, or the last byte of a field is the first byte of a two-byte character.

Delete the rows loaded. Issue the LOAD command again, specifying field boundaries that coincide with character boundaries.

Unable to upshift native language string. (DBWARN 19)

ISQL was unable to upshift a character string, probably because the string contains one or more invalid bytes.

Issue your command again, specifying valid input.

Unable to split string into lines. (DBWARN 20)

ISQL was unable to split a character string into lines, probably because the string contains one or more invalid bytes.

Issue your command again, specifying valid input.

Unable to trim trailing blanks from multi-byte native language string. (DBWARN 21)

ISQL was unable to trim trailing blanks from a character string, probably because the string contains one or more invalid bytes.

Issue your command again, specifying valid input.

Unable to truncate multi-byte native language string. (DBWARN 22)

ISQL was unable to truncate a character string, probably because the string contains one or more invalid bytes.

Issue your command again, specifying valid input.

Unable to obtain user language. Default language n-computer assumed. (DBWARN 23)

Your LANG environment variable is set to a language that is not configured, or the support files for your language are missing.

Contact your system administrator.

No language set. Default language n-computer assumed. (DBWARN 24)

Your LANG environment variable is not set.

Set your LANG variable if desired.

Local welcome file is inaccessible. Default file in use. (DBWARN 25)

The ISQL welcome file corresponding to your language cannot be accessed, probably because it does not exist.

Contact your system administrator.

! conversion error on line !, column !. (DBWARN 232)

There is a problem converting Date, Time, DateTime, or Interval field to internal format when trying to load the data from an external data file. The error messages following this one will give more specific information on the problem.

Check the load information specified for this field (start position, length, date/time/interval field format) and the format of the data value for possible problems. Correct problems and redo LOAD operation.

Default format not used for ! field, column !. (DBWARN 233)

You did not use the default format for a Date, Time, DateTime or Interval field in the load description file.

Modify the format in the descriptor file. Make sure the data is in the default format and redo the LOAD operation. Refer to the ALLBASE/ISQL Reference Manual for format specifications.

Unable to convert ! value to a displayable format. (DBWARN 234)

Unable to convert a Date, Time, DateTime or Interval value to a value that can be stored in the data file. This was probably due to a bad format or length specified for the field.

Check the unload format and length given for this field. Correct any problems and redo the UNLOAD operation.

Only first ! rows can be displayed. (DBWARN 235)

More rows qualified for the SELECT statement than can be viewed through ISQL.

If all the rows of data need to be viewed, use the UNLOAD EXTERNAL command to unload the data to an ASCII file.

*WARNING*: DATA NOT COMPLETE - FIRST ! ROWS DISPLAYED. (DBWARN 236)

This message is displayed on the last line of the outfile when an outfile is specified with the OUTPUT option of the ISQL SET command and more rows qualify for the SELECT than can be viewed within ISQL. The outfile will hold all the rows that can be viewed within ISQL.

If all the rows of data need to be viewed, use the UNLOAD EXTERNAL command to unload the data to an ASCII file.

File Device Full. (DBWARN 302)

Your storage medium (tape or disk) is full.

If your storage is on tape, mount another tape. If your storage is on disk, exit, clean up the file system, and try again. If the problem persists, contact the system administrator.

Nothing left to audit. (DBWARN 502)

This warning is returned if SQLAudit determines that there is nothing left to audit in the DBEnvironment log files. This usually is the case if there have been no new transactions committed between the time the beginning audit point was defined and the ending audit point was defined.

This is not a real error, but you should check to make sure the partitions that have been supplied to SQLAudit include all partitions you wish to see transactions for.

Partition ! has no committed transactions. (DBWARN 506)

The partition being audited has no committed transactions. This basically means that no committed transactions have touched data belonging to the specified partition.

No action required except to make sure the partition was intended to be audited.

Duplicate Partition Number entered. Ignored. (DBWARN 522)

The same partition was entered previously.

No action necessary since the duplicate partition is ignored.

No transactions exist for the given set of Partition Numbers. (DBWARN 523)

No transactions have been committed which affect the list of audited partitions.

No action necessary.

Partition ! has no transactions to audit. (DBWARN 523)

No transaction information was found in the ending audit point for the given partition. This would be possible if no committed transactions have touched the partition, or the transaction information was removed through a hard resync.

No action necessary.

SET DBENVIRONMENT command has not been issued yet. (DBWARN 528)

Calling SET DBENVIRONMENT for you before proceeding with command.

You do not currently have a DBEnvironment session active. This would be established by using the SET DBENVIRONMENT command. This command will automatically be issued on your behalf.

Enter the name of the DBEnvironment at the prompt to establish the DBEnvironment session.

A DBE session is already started. (DBWARN 700) Type 'RELEASE' if you wish to start a new DBE session.

A DBE session has already been started.

Issue the RELEASE statement to end the current session and then use the STARTDBE statement to begin a new DBEnvironment session.

A DBE session has not been started. (DBWARN 701) Calling STARTDBE for you before proceeding with command.

A DBEnvironment session has not been started.

The STARTDBE statement was automatically called to begin the session. Enter the necessary DBEnvironment name.

[RETURN] not allowed for UNLOAD/LOAD Schema File name. (DBWARN 703)

A carriage return was entered at the UNLOAD/LOAD Schema File name prompt. This is not allowed.

Enter a valid UNLOAD/LOAD Schema File name.

Prefix is required to be from 1 to 5 bytes long. (DBWARN 704)

Entered prefix was an invalid length.

Re-enter the prefix name with a length of 1 to 5 bytes.

Unrecognized command. (DBWARN 705)

An unknown command was entered.

Enter a valid SQLGEN command.

No help for that command. (DBWARN 706) HELP keywords are GENERAL, MAIN, OBJECT, and SUMMARY. Type '//' to leave SQLGEN HELP.

An unrecognized command was entered for HELP.

Enter a valid SQLGEN command at the HELP prompt.

No View Names qualify for specified owner. (DBWARN 707)

The entered view name does not match any of the owner names in the DBEnvironment.

Enter a valid view name from the DBEnvironment.

No owner names match the entered Owner Name. (DBWARN 711)

The entered Owner name does not match any of the Owner names in the DBEnvironment.

Enter a valid owner name from the DBEnvironment.

No owners qualify for specified generate command. (DBWARN 712)

The owner name or DBEFileSet name entered does not match any owner names or DBEFileSet names in the DBEnvironment.

Reissue the command specifying valid Owner names or DBEFileSet names found in the DBEnvironment.

Unacceptable object name entered. (DBWARN 713) For information on object names, type 'HELP OBJECT' at the SQLGEN prompt.

An invalid object name was entered.

Reissue the command specifying a valid object name. If more detailed information is needed, issue the HELP command to illustrate valid object names.

Unacceptable null indicator entered. (DBWARN 714) Default null indicator used instead.

An invalid null indicator was entered.

The default null indicator "?" was used. No additional user response is necessary.

User needs to have DBA authority to use SQLGEN. (DBWARN 715) Terminating the DBE session.

User does not have DBA authority to the DBEnvironment.

Before using SQLGEN, the user must obtain DBA authority.

No SQL commands generated. (DBWARN 716)

The executed SQLGEN command did not generate any commands which were put into the Schema File.

No response is necessary. If SQL commands should have been generated, check for misspelled object names, etc.

Please check object names entered. (DBWARN 717) For information on object names, type 'HELP OBJECT' at the SQLGEN prompt.

The entered object name may not have been correct.

Reissue the command using the correct object name. Use the HELP command to obtain more information on object names.

No DBE session has been started. (DBWARN 719)

A RELEASE statement was issued on a session that had not been started yet.

Use the STARTDBE statement to start a DBEnvironment session.

ALLBASE/SQL error occurred. Recovering file ! (DBWARN 721)

An error in executing an ALLBASE/SQL command occurred while the Schema File was being modified.

No response is necessary. The Schema File will be recovered to the state prior to the SQLGEN command execution.

Illegal character encountered in file name. (DBWARN 723)

An illegal character was entered in the file name.

Re-type the file name without the illegal character.

Designated Schema File has been purged from system. (DBWARN 724) Will attempt to rebuild the Schema File.

The designated Schema File was non-existent when SQLGEN tried to open the file. Will attempt to rebuild the Schema File.

No response is necessary. SQLGEN will attempt to build a new Schema File.

Object name entered is too long. It will be truncated. (DBWARN 725)

The object name entered was longer than 20 bytes.

Enter a valid object name no more than 20 bytes in length.

Native catalog not available. Using n-computer catalog. (DBWARN 730)

The LANG environment variable was not set or the message catalog 'hpsqlcat' was not found in the /usr/lib/nls/$LANG directory.

If native language support is desired, verify that the LANG environment variable is set correctly or contact your system administrator.

Unable to load all native language information. (DBWARN 731)

There was a problem loading the native language responses from the message catalog. Local language responses in the message catalog were incorrect. Only default language responses will be used.

Contact your system administrator.

User language and DBE language differ. (DBWARN 732)

The user's LANG environment variable and the DBEnvironment's language are different.

Exit SQLGEN. Set your LANG environment variable to match the DBEnvironment language, then invoke SQLGEN.

SQLGEN cannot be used on remote DBEnvironments. (DBWARN 733)

SQLGEN cannot access remote DBEnvironments.

Do not execute SQLGEN on a remote DBEnvironment.

No Users qualify for specified generate command. (DBWARN 736)

No users had the authority for the specified command.

Check the authorization requirements.

Local catalog is inaccessible. Default catalog in use. (DBWARN 1681)

The ALLBASE/SQL message catalog corresponding to your language cannot be accessed, probably because it does not exist.

Contact your system administrator.

Non-standard command or extension. (DBWARN 1800)

This is an ALLBASE/SQL extension to the ANSI SQL/89 standard.

Do not use this command or extension if portability is a concern.

Non-standard extension, label (!) needs to be preceded by a COLON. (DBWARN 1801)

This is an ALLBASE/SQL extension to the ANSI SQL/89 standard.

Add the colon in the front of the label if portability is a concern.

Non-standard extension, lower case keyword (!) is used. (DBWARN 1802)

Lower case keywords are not allowed in the ANSI SQL/89 standard.

Use upper case keywords if portability is a concern.

Non-standard extension, identifier (!) exceeds maximum length of 18 bytes. (DBWARN 1803)

Identifier exceeds maximum allowed in ANSI SQL/89 standard.

Do not use this identifier length if portability is a concern.

Use of multiple DISTINCTs within a query or subquery is a non-standard extension. (DBWARN 1804)

Allowing multiple distincts in a query or subquery is an ALLBASE/SQL extension to the ANSI SQL/89 standard.

Do not use this statement if portability is a concern.

DDL statement outside a CREATE SCHEMA statement is a non-standard extension. (DBWARN 1805)

ANSI SQL/89 requires DDL commands to be within a CREATE SCHEMA AUTHORIZATION statement.

Place all DDL commands within the CREATE SCHEMA statement if portability is a concern.

Use of keyword as an identifier is a non-standard extension. (DBWARN 1806)

Use of keywords as identifiers is an ALLBASE/SQL extension to the ANSI SQL/89 standard.

Do not use keywords as identifiers if portability is a concern.

Access to SYSTEM/CATALOG tables/views is a non-standard extension. (DBWARN 1807)

ALLBASE/SQL system/catalog views and tables are non-standard objects.

Do not access these objects if portability is a concern.

An object with owner (!) not equal to schema name (!) is a non-standard extension. (DBWARN 1808)

This is an ALLBASE/SQL extension to the ANSI SQL/89 standard.

Modify the syntax if portability is a concern.

The index dropped is a clustering index. (DBWARN 2005)

The index you just dropped with the DROP INDEX statement was created with the CLUSTERED attribute.

No action is necessary.

User ! already has ! authorization. (DBWARN 2006)

You tried to grant an authorization to a user that already has that authorization.

No action is necessary.

User ! already has ! authorization on !.!. (DBWARN 2007)

You tried to grant authority on a table or a module to a user that had already been granted authority on the specified table or module. Either you granted the table authority before, or you are the OWNER of the table or a DBA (and so you will be able to revoke it even if you are not the grantor of it).

No action is necessary.

User ! already has ! authorization on !.!.!. (DBWARN 2008)

You tried to grant authority on a specific column to a user that had already been granted authority on the specified column. Either you granted the column authority before, or you are the OWNER of the table or a DBA (and so you will be able to revoke it even if you are not the grantor of it).

No action is necessary.

A transaction in progress was aborted. (DBWARN 2010)

You issued a RELEASE or STOP DBE statement without issuing a COMMIT WORK or ROLLBACK WORK statement first.

No action is necessary.

Use SQLUtil to purge physical file !. (DBWARN 2011)

When you issue a DROP DBEFILE statement, the actual physical file is not deleted; it is only deleted from the system catalog.

Use the SQLUtil PURGEFILE command to purge the physical file.

DBEFile already of specified DBEFile type. (DBWARN 2012)

The DBEFile you attempted to ALTER was already of the specified type.

No action is necessary.

Module !.! not found. (DBWARN 2014)

The module specified in the EXECUTE or DROP MODULE statement does not exist.

Check your spelling. Ask your database administrator to check the SYSTEM.SECTION view to make sure that the module exists in the DBEnvironment to which the application is connected.

Row size of table !.! exceeds ! bytes. (DBWARN 2015)

The row size of the table you created exceeds the maximum number of bytes.

No action necessary. An error will occur only if you attempt an operation that causes the row length of the table to exceed the maximum number of bytes.

Length of index ! on table !.! exceeds ! bytes. (DBWARN 2016 )

The index that you created exceeds the maximum key length and contains a VARCHAR column.

No action is necessary as long as the length of the VARCHAR data does not cause the maximum key length to be exceeded. The key length is determined using the actual data length in the VARCHAR column. If the maximum key length is exceeded, an error will occur when the index is accessed.

The data updated/deleted is in the RC/RU transaction. (DBWARN 2017)

You updated or deleted data in the transaction which is started in RC or RU mode.

If you are using a non-cursor UPDATE or DELETE statement, you may ignore this message.

If you are using the UPDATE/DELETE WHERE CURRENT statement, ALLBASE/SQL only guarantees that the data still satisfies the cursor definition. To guarantee integrity, you might wish to use the REFETCH statement to validate the data before you actually update/delete the data.

Length of hash key on table !.! exceeds ! bytes. (DBWARN 2018)

The key length of the hash defined on the table exceeds the maximum key length and the key contains a VARCHAR column.

No action is necessary as long as the actual length of the VARCHAR data does not cause the maximum key length to be exceeded. The key length is determined using the actual data length in the VARCHAR column. If the maximum key length is exceeded, an error will occur when the hash structure is accessed.

ASCII definition of view !.! not available for storage. (DBWARN 2019)

The stored module being executed contains a CREATE VIEW that was prepared or preprocessed before the existence of the SYSTEM.VIEWDEF table. Therefore, it is not possible to store the select string that defines the view.

If it is important that the ASCII view definition be stored, use the PREPARE statement through ISQL to create a new version of the module containing the CREATE VIEW statement or preprocess the program again. Refer to the ALLBASE/SQL Reference Manual for information on the PREPARE statement.

DBEnvironment corruption suspected - Rollforward recovery required. (DBWARN 2020)

An error may have caused the DBEnvironment to be corrupted. An additional message will be returned.

Refer to the cause and action of the additional message. Do not perform additional transactions at this time. Contact your database administrator for rollforward recovery on the DBEnvironment.

Device name is ignored on HP-UX system. (DBWARN 2021)

The CREATE DBEFile command contained a device specification. A device specification is only applicable to MPE/iX.

Ignore the warning, or resubmit the command without a device specification.

Please close all open scans before proceeding with RESUME. (DBWARN 2023)

CREATE DBEFile command contained a DEVICE specification. The MPE/iX system where the replicated database resides does not have a volume with this name. DBEFile is create on whatever volume the system chooses.

Ignore the warning, or MOVE the DBEFile to a desired device using SQLUtil.

User ! has no grantable authority on !.!. (DBWARN 2025)

You issued a GRANT ALL statement but have no Owner or DBA authority and have no grantable privileges on the table. Nothing was granted.

No action required.

REVOKE CASCADE has dropped a view or foreign key. (DBWARN 2026)

A view or foreign key depended on the SELECT or REFERENCES privilege being revoked, so REVOKE CASCADE dropped the dependent item.

Rollback will recover the item if it needs recovery; otherwise, no action is necessary.

Column ! not found in table/view !.!. (DBWARN 2027)

A column included in a column-level GRANT was not found in the table or view specified.

If the column was mis-spelled, revoke that column authority and grant on the correct column.

User ! already has ! authorization on columns of !.! from a different grantor. (DBWARN 2028)

Your GRANT of a table level authority has overridden one performed by another grantor. The column authorities given by that grantor are removed, and replaced with your table level authorities (with you as the grantor).

None necessary. The other grantor will not be able to revoke this table level authority.

User ! does not have any explicit authority on !.!. (DBWARN 2029)

REVOKE ALL failed to find any applicable authorities for the given user.

None necessary. REVOKE ALL will only include those authorities which the revoker is authorized to revoke, so the user may still have authorities from other grantors. Owner and DBA are authorized to revoke all authorities.

ALLBASE/SQL could not predrop user shared memory. HP-UX errno (!) (DBWARN 2030)

There was an abnormal termination of an application and the allocated shared memory still remains on the system.

Refer to the system administration manual.

Remove shared memory manually in case of abnormal terminations. (DBWARN 2031)

There was an abnormal termination of an application and the allocated shared memory still remains on the system.

Contact your system administrator to remove the shared memory.

Character string truncation during storage in host variable. (DBWARN 2040)

A host variable character string was shorter than a character column in the select list.

Check the string returned to see if it needs to be longer in order to capture all necessary information from the column. If so, modify the declaration of the datatype.

NULL values eliminated from the argument of an aggregate function. (DBWARN 2041)

A NULL value occurred in a column where an aggregate (SUM, AVG, MAX, MIN, COUNT) was evaluated, but was dropped from the computation.

Determine whether the information was needed for correct computation. If it was, set the NULL column to the needed value. To prevent future lapses, change the column to be NOT NULL if possible.

ADD_MONTHS result adjusted to last day of month. (DBWARN 2042)

Result of ADD_MONTHS function was an invalid date, which resulted in the day being adjusted to the last day of the month.

No action required.

Binary literal truncation during insert on column !. (DBWARN 2043)

The binary input is longer than the column definition.

No action is necessary; however, the extra data is lost.

DEFAULT USER is specified, corresponding column length should be at least 20 characters long. (DBWARN 2044)

You entered a column length less than 20 bytes.

No action necessary.

DEFAULT 'literal' truncated, length ! exceeds column length !. (DBWARN 2045)

You specified a default constant length which is longer than the column length defined when the table was created.

Define a default value whose length will not exceed the corresponding column length.

String concatenation result is truncated. (DBWARN 2046)

Result length of string concatenation exceeds the maximum.

No action needed.

LONG column data exceeds defined length. Truncated. (DBWARN 2050)

The actual long column data is longer than the defined length. The long column data was truncated.

No action is necessary.

Sort length of UNION may exceed maximum allowed ! bytes. (DBWARN 2052)

The UNION command specifies a number of columns whose total sort tuple length exceeds the maximum allowable and contains a VARCHAR column.

No action is necessary as long as the length of the VARCHAR data does not cause the maximum sort tuple length to be exceeded. The sort tuple length is determined using the actual data length in the VARCHAR column. If the maximum sort tuple length is exceeded, an error will occur when the sorting is performed.

Sort length of ORDER BY/GROUP BY/DISTINCT/UNION may exceed maximum allowed ! bytes. (DBWARN 2053)

The ORDER BY, GROUP BY, DISTINCT, or UNION clause of the SELECT statement specifies a number of columns whose total sort tuple length exceeds the maximum allowable and contains a VARCHAR column.

No action is necessary as long as the length of the VARCHAR data does not cause the maximum sort tuple length to be exceeded. The sort tuple length is determined using the actual data length in the VARCHAR column. If the maximum sort tuple length is exceeded, an error will occur when the sorting is performed. You can calculate the maximum sort tuple length from the formula given in Appendix A of the ALLBASE/SQL Database Administration Guide.

Sort length of sort merge join may exceed maximum allowed ! bytes. (DBWARN 2054)

The sort merge join query specifies a number of columns whose total sort tuple length exceeds the maximum allowable and contains a VARCHAR column.

No action is necessary as long as the length of the VARCHAR data does not cause the maximum sort tuple length to be exceeded. The sort tuple length is determined using the actual data length in the VARCHAR column. If the maximum sort tuple length is exceeded, an error will occur when the sorting is performed.

A cursor opened using KEEP CURSOR WITH NOLOCKS requires sorting. You must ensure data integrity yourself. (DBWARN 2056)

You are using the KEEP CURSOR WITH NOLOCKS option on a cursor requiring a sort operation such as the ORDER BY clause or a join.

You need to verify that the data is correct if you want to do an update where your cursor is located.

There are deferred UNIQUE/PRIMARY KEY and/or FOREIGN KEY constraint violations that may not be resolvable. (DBWARN 2059)

There are UNIQUE/PRIMARY KEY constraint or FOREIGN KEY constraint violations pending at deferred constraint checking mode.

Avoid truncating or dropping data when there are deferred constraint violations.

Audit logging already disabled. (DBWARN 2060)

You specified a redundant DISABLE AUDIT LOGGING statement.

Check the sequence of operations.

Audit logging already enabled. (DBWARN 2061)

You specified a redundant ENABLE AUDIT LOGGING statement.

Check the sequence of operations.

Partition not found. (DBWARN 2062)

A non-existent partition id was specified when retrieving synchronization checkpoint data.

Check and correct the specified partition ids.

Some partitions (but not all) failed on Open_Log_Scan. (DBWARN 2063)

Open_Log_Scan failed to open the scan for some of the specified partitions.

Check the per partition return codes.

DML ATOMICITY already set to ! level. (DBWARN 2065)

The DML ATOMICITY is already set to row or statement level.

Determine whether the SET DML ATOMICITY statement is needed.

! constraints already set to !. (DBWARN 2066)

Constraints specified were already set to deferred or immediate.

Determine whether the SET CONSTRAINTS statement is needed.

User timeout exceeds maximum timeout; maximum assumed (! seconds). (DBWARN 2067)

The specified user timeout value is greater than the maximum timeout value limit. When this error occurs, the user timeout value is automatically set to the maximum timeout limit.

Set the user timeout to a value less than or equal to the maximum timeout limit or set the maximum timeout limit to a value greater than or equal to the desired user timeout value.

Length of substring requested ! starting at ! exceeds length of source string. (DBWARN 2068)

In the SUBSTRING function, (Length - StartPosition + 1) is greater than the length of the SourceString parameter.

No action is necessary. You should be aware that the substring returned is shorter than expected.

Length of substring requested ! exceeds maximum length allowed !. (DBWARN 2069)

The length of the substring requested by the SUBSTRING function is longer than the maximum length allowed.

No action is necessary. You should be aware that the substring returned is shorter than expected and that truncation may occur.

The transaction was committed, since it is read only. (DBWARN 2070)

The transaction that was being prepared for COMMIT was found to have no associated updates. The transaction was therefore committed.

No action needed.

The transaction was aborted due to deadlock. (DBWARN 2071)

A deadlock situation caused the transaction to abort.

Refer to the ALLBASE/SQL Advanced Application Programming Guide to determine ways to avoid deadlock situations.

The transaction was aborted due to integrity violation. (DBWARN 2072)

An unresolved integrity violation caused the transaction to abort.

Check the application logic to ensure that all uniqueness and referential constraint violations are resolved before attempting to commit the transaction.

The transaction was aborted due to timeout. (DBWARN 2073)

A timeout occurred while the application was waiting for a resource.

Check the application for possible cross-database deadlocks.

The transaction was aborted. (DBWARN 2074)

A database internal problem caused the transaction to abort.

Retry the transaction.

Cannot revalidate Section !.!(!). (DBWARN 2075)

Either you have recently performed a migration or you have installed a module that was created on an earlier release of ALLBASE/SQL.

Preprocess or run the application to validate module. After you have validated the module successfully in this manner, you will then be able to use the VALIDATE statement on this module.

Failed to validate module !.!. (DBWARN 2076)

The module specified does not exist.

Check module name in the SYSTEM.SECTION view or with the ISQL LIST INSTALL command.

Failed to validate module !.!.(!). (DBWARN 2077)

An error occurred during validation process.

Check the other error messages generated.

No modules to be validated. (DBWARN 2078)

There are no modules to be validated.

You specified the ALL option, but there are no modules to be validated.

Failed to validate procedure !.!. (DBWARN 2079)

A procedure specified by name in the VALIDATE statement does not exist.

Check your spelling, and verify the procedure owner and name, then reissue the VALIDATE statement.

No procedure(s) to be validated. (DBWARN 2080)

You issued a VALIDATE ALL PROCEDURES statement, but there are no procedures to be validated.

No action is required.

Warning(s) occurred processing statement ! during procedure creation/validation. (DBWARN 2081)

An SQL statement in the procedure could not be compiled at procedure creation or validation time. The procedure was created or validated, but the section corresponding to the statement was stored as an invalid section.

Use the statement number in the message to determine which procedure statement generated the warning. Refer to the accompanying message or messages for more information.

LABEL ! defined but not used. (DBWARN 2082)

A procedure statement label is not referenced in any GOTO statement in the procedure.

If this warning is accompanied by DBERR 2237, check your spelling. Otherwise, the superfluous label may be removed.

Multiple rows returned in procedure. (DBWARN 2083)

A non-cursor SELECT in a procedure returned multiple rows. Only the first row of values was returned in the local variables or parameters.

Use a cursor in procedures for any query that will return more than one row of data.

Procedure returns multiple row result set(s). (DBWARN 2084)

A procedure that returns multiple row result sets was executed directly, without using a procedure cursor.

or

A procedure that returns multiple row result sets was specified in a CREATE RULE statement.

If retrieval of the result sets is not required by the application, no action is required. If retrieval is required, you must use a procedure cursor.

or

No action is required.

Section !.! (!) being revalidated due to obsolete execution code. (DBWARN 2085)

Obsolete execution code is causing the specified section to be revalidated.

No action is required.

View !.! has been dropped. (DBWARN 2087)

The specified view has been dropped.

No action is required if the view is no longer required.

RAISE ERROR text truncated, length ! exceeds maximum allowed (!). (DBWARN 2090)

The text given to the RAISE ERROR statement exceeded the maximum allowed length.

No action is necessary; however, the extra text is not returned.

Rule !.! fired on ! statement. (DBWARN 2091)

The named rule fired while PRINTRULES was SET ON due to execution of a statement of the given type (INSERT, UPDATE, or DELETE).

No action is necessary.

Rules already disabled. (DBWARN 2092)

DISABLE RULES statement was in effect when this DISABLE RULES statement was issued.

No action is necessary.

Rules already enabled. (DBWARN 2093)

ENABLE RULES statement was in effect when this ENABLE RULES statement was issued.

No action is necessary.

PRINTRULES already ON. (DBWARN 2094)

SET PRINTRULES ON statement was in effect when this SET PRINTRULES ON statement was issued.

No action is necessary.

PRINTRULES already OFF. (DBWARN 2095)

SET PRINTRULES OFF statement was in effect when this SET PRINTRULES OFF statement was issued.

No action is necessary.

! on DBEFileSet ! already granted for !. (DBWARN 2096)

The SECTIONSPACE/TABLESPACE authority already granted to the user.

Delete the command.

Default ! on DBEFileSet ! already set for !. (DBWARN 2097)

The default SECTIONSPACE/TABLESPACE authority already set to the user.

Delete the command.

! on DBEFileSet ! is not granted for !. Default DBEFileSet ! used. (DBWARN 2098)

You do not have authority to store a table or section in the specified DBEFileSet. The table or section was added to the default DBEFileSet instead.

No action is necessary. However, if it is not desirable to have the table or section in the default DBEFileSet, then the table or section can be dropped and recreated in another DBEFileSet for which you do have authority to store the table or section.

User ! already has INSTALL AS ! authority. (DBWARN 2344)

You granted INSTALL AS authority to a user who already has the authority.

No action required.

User ! already has general INSTALL authority. (DBWARN 2345)

You granted INSTALL authority to a user who already has the authority.

No action required.

Cursor, associated with the aborted query has been closed. (DBWARN 2531)

The cursor has been closed.

No action required for the closed cursor. Check the aborted query.

! on DBEFileSet ! is not granted for !. Default DBEFileSet used. (DBWARN 2880)

The authority is not previously granted to the user.

Grant the authority to the user.

SQLCore could not use the plan as specified. (DBWARN 3230)

The plan you specified is not applicable to the query.

Use GENPLAN command to verify the plan produced by SQLCore and reset SETOPT statement if it is necessary.

The join order specified in SETOPT does not match with the prefix join order of outer join query. (DBWARN 3231)

The plan you specified is not applicable to the query.

Use GENPLAN command to verify the plan produced by SQLCore and reset SETOPT statement if it is necessary.

Section (!) could not be found on Module !.!. (DBWARN 3232)

The section you specified was not found in the Module.

Check your source file to get the correct section number.

Section (!) could not be found on Procedure !.!. (DBWARN 3233)

The section you specified was not found in the Procedure.

Check your source file to get the correct section number.