Chapter 3 ALLBASE/SQL Warning Messages

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

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

Contact your system administrator.

Local response options are not unique. (DBWARN 8002)

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

Contact your system administrator.

Unable to upshift multi-byte native language string. (DBWARN 8003)

SQLUtil 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 trim trailing blanks from multi-byte native language string. (DBWARN 8004)

SQLUtil 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 8005)

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

Issue your command again, specifying valid input.

Cannot obtain user's language id. Assuming !. (DBWARN 8006)

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 or set again with valid language.

Local message catalog is not available. Set to ! message catalog. (DBWARN 8007)

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

Contact your system administrator.

Maximum Log files exceeded, last log name ignored. (DBWARN 8248)

You entered more than 34 log file names when entering the log file list for the WRAPDBE command.

Check list to see what log files can be dropped from the list. The list must contain 34 or fewer entries.

No ending single quote: Single quote inserted. (DBWARN 10600)

One of your statements does not include an ending single quote.

No action is necessary. The preprocessor inserted the required ending single quote.

No ending double quote: Double quote inserted. (DBWARN 10601)

An ending double quote was missing in one of your statements.

No action is necessary. The preprocessor inserted the required ending double quote.

Cannot obtain user's language. Default language ! assumed. (DBWARN 10603)

The environment variable, LANG, is set to an unrecognized language.

Reset LANG to a supported language.

Source line longer than allowed. Source line truncated. (DBWARN 10604)

A source line is longer than supported.

Consult the application programming guide for maximum allowed source line length.

User's and DBE's languages are different. (DBWARN 10605)

The environment variable, LANG, and the language of the DBEnvironment are different.

Set LANG to the proper language, if using native data.

Native version of ALLBASE/SQL message catalog not accessible. (DBWARN 10606)

The native version of hpsqlcat is not found under /usr/lib/nls/$LANG.

Install native hpsqlcat, if required.

Program name exceeds maximum module name length. Truncated to 20 bytes. (DBWARN 10607)

The program name is used as the module name when none is specified in the program invocation line. A program name was specified which is longer than the maximum allowed module name length of 20 bytes.

Modify the source file to specify a program name with a length of 20 bytes or less.

ALLBASE/SQL preprocessor warning. (DBWARN 10608)

A warning condition was detected by the preprocessor. Additional warning messages will be returned.

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

ALLBASE/SQL statement parser warning. (DBWARN 10609)

A warning condition was detected by the statement parser. Additional warning messages will be returned.

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

ALLBASE/SQL query processor warning. (DBWARN 10610)

A warning condition was detected by the query processor. Additional warning messages will be returned.

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

Cannot obtain user's language. Default language NATIVE-3000 assumed. (DBWARN 10611)

The environment variable, LANG, is set to an unrecognized language.

Set LANG to a supported language.

Native version of ALLBASE/SQL message catalog not accessible. (DBWARN 10612)

The native version of the hpsqlcat message catalog is not found under /usr/lib/nls/$LANG.

Install the native version of hpsqlcat.

User's and DBE's languages are different. (DBWARN 10613)

The environment variable, LANG, and the language of the DBEnvironment are different.

Set LANG to the proper language.

Not enough space to return parse information. (DBWARN 10614)

The buffer space passed to hold the returned parse information was not sufficient.

Increase the buffer space.

***REDEFINES clause: Non-standard host variable declaration. (DBWARN 10621)

A possible cause is that the REDEFINE clause was used.

No action required. Only elementary level items are allowed in ALLBASE/SQL calls. In order to pass an item with subitems in the COBOL preprocessor, you can use a REDEFINE clause. However, you will receive a warning because you are using a non-standard host variable declaration.

Cannot obtain user's language. Default language C assumed. (DBWARN 10622)

The user's language is not found.

Check the native language parameters.

Filler added to adjust for odd-byte field. (DBWARN 10700)

The preprocessor generated in the preprocessor output file a one-byte filler character for an odd-byte host variable declaration to ensure that the data is aligned on word boundaries.

No action is necessary. The preprocessor inserted the required one-byte filler character in the preprocessor output file.

Maximum COBOL work length exceeded. Truncated to 30 bytes. (DBWARN 10701)

A word appears in the COBOL source file which is longer than the maximum allowed length of 30 bytes.

Modify the source file to shorten the word to a length of 30 bytes or less.

'INCLUDE SQLCA' is not declared for embedded SQL statement. (DBWARN 10750)

You did not include an SQLCA common area in your program.

Modify the source file specifying EXEC SQL INCLUDE SQLCA and re-preprocess your program.

ALLBASE/SQL query processor error. (DBWARN 10979)

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

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

Syntax check only due to severe ALLBASE/SQL query processor error. (DBWARN 10980)

An unrecoverable error condition was detected by the query processor. Only the syntax of the SQL statement was verified. Validation of the SQL statement was not performed. Additional error messages will be returned.

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

Missing log files from log file list. (DBWARN 13026)

WRAPDBE determined that log files were missing from the log file list by checking the log sequence numbers. The log file names can be entered in any order; as long as there is a correct and continuous sequence; WRAPDBE puts them in the correct order.

Check the log sequence numbers that were assigned on the original DBEnvironment with the SQLUtil SHOWLOG command to determine if all log files exist in the target area.

Consistency point may not be exactly enforced by DBCORE. (DBWARN 13343)

DBCORE is adjusting the consistency point.

No action required.

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

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

Contact your system administrator.

*** Bad environment variable MIGLOGSZ. Default log size used. (DBWARN 20012)

The environment variable MIGLOGSZ has been set to an integer value that is less than 400 (the default log size) or the environment variable MIGLOGSZ has not been set to a valid integer value.

Set the environment variable MIGLOGSZ again, but specify a log file size that is no less than 400.

Cannot verify ALLBASE/SQL license. Assuming IMAGE/SQL (! !) (DBWARN 20014)

An error occurred during processing that determines whether or not your system is licensed to use ALLBASE/SQL.

If you have not purchased a license to use ALLBASE/SQL, no action is necessary. Otherwise, record as much information as possible and contact your HP Service Representative or Response Center, because restrictions imposed by IMAGE/SQL are currently in effect for your DBEnvironment.

WARNING - No DBEnvironment has been referenced yet. (DBWARN 20300).

Either the CREATE DBEFILE or the ADD DBEFILE statement was issued before a DBEnvironment had been mentioned in a command.

Use either the SHOW 'DBEnvironmentName' VERSION command or the PREVIEW command to indicate to SQLMigrate which DBEnvironment should be used for this command.

WARNING - Before continuing, please verify that a complete backup of the DBEnvironment exists. (DBWARN 20550)

This warning is issued to insure that you do not accidentally corrupt a DBEnvironment when using SQLMigrate and you will be unable to recover your data. If an unexpected error is encountered during the MIGRATE or PREVIEW command, it is critical that a backup of the DBEnvironment be available.

If you have not made a complete backup of the DBEnvironment, type No at the prompt to prevent SQLMigrate from continuing. Make a full backup of the DBEnvironment, and then issue the MIGRATE or PREVIEW command again.

WARNING - Table !.! contained the following columns which are not supported under the target release of ALLBASE/SQL. (DBWARN 20570)

A backward migration was in progress when this message was issued. Column types that were only supported under the newer release of ALLBASE/SQL were present in the user table mentioned in the warning. The table was dropped during the migration.

If you need to recover the table, the backup version of the DBEnvironment must be restored. The offending columns must be eliminated or modified to be of types supported by the target version before a migration is attempted again.

WARNING - Views and stored sections created under later releases of ALLBASE/SQL may not function correctly under the target version of ALLBASE/SQL. (DBWARN 20580)

This message is issued as a warning whenever a backward migration occurs.

Drop all views created under later releases, and recreate them. Also drop all stored sections created under later releases, and either:

INSTALL backup installable module files that were created under the target version of ALLBASE/SQL,

or

preprocess programs again to obtain stored sections that are compatible with the target version of ALLBASE/SQL.

WARNING - Table !.! has been created using the HASH option, which is not supported under the target version of ALLBASE/SQL (DBWARN 20650). This table is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table !.! has been created using INTEGRITY CONSTRAINTS, which is not supported under the target version of ALLBASE/SQL (DBWARN 20660). This table is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table !.! has been created using DEFAULT column values, which is not supported under the target version of ALLBASE/SQL (DBWARN 20670). This table is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - TEMPSPACE ! has been created using the CREATE TEMPSPACE statement, which is not supported under the target version of ALLBASE/SQL (DBWARN 20680). This TEMPSPACE is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Table !.! has been created with a REFERENTIAL CONSTRAINT on a table that was dropped during the migration. (DBWARN 20690) Table !.! is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - INDEX has been defined on sixteen (16) columns. (DBWARN 20700). Index ! defined on table !.! is being dropped.

In the target release, the maximum number of columns on which an index may be defined is fifteen (15). Functionality that is not present in the target release has been detected.

After migration to the target release, recreate the dropped index using fewer columns.

WARNING - DBEFile ! in DBEFileSet ! has been defined using RAW I/O, which is not supported under the target version of ALLBASE/SQL (DBWARN 20710).

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

You must use the SQLUtil MOVEFILE command to move this DBEFile into a standard HP-UX file before a migration can be attempted.

SET NEWLOG OFF was previously issued. (DBWARN 20754)

The current value of the NEWLOG variable is OFF, so a START DBE NEWLOG command was not performed during the MIGRATE command.

No action is necessary. If you want a START DBE NEWLOG command to be performed during future MIGRATE commands, issue a SET NEWLOG ON command.

WARNING - Table !.! contains the following columns which are not supported under the target release of ALLBASE/SQL. (DBWARN 22530)

A backward migration is being PREVIEWed when this message is issued. Column types that are only supported under the newer release of ALLBASE/SQL are present in the user table mentioned in the warning.

The offending columns must be eliminated or modified to be of types supported by the target version before a migration is attempted. If they are not removed, then the table will be dropped during the MIGRATE command.

WARNING - Table !.! has been created using the HASH option, which is not supported under the target version of ALLBASE/SQL (DBWARN 22620). This table will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table !.! has been created using INTEGRITY CONSTRAINTS, which is not supported under the target version of ALLBASE/SQL (DBWARN 22630). This table will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table !.! has been created using DEFAULT column values, which is not supported under the target version of ALLBASE/SQL (DBWARN 22640). This table will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - TEMPSPACE ! has been created using the CREATE TEMPSPACE statement, which is not supported under the target version of ALLBASE/SQL (DBWARN 22650). This TEMPSPACE will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - INDEX has been defined on sixteen (16) columns. (DBWARN 22670). Index ! defined on table !.! will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. In the target release, the maximum number of columns on which an index may be defined is fifteen (15). Functionality that is not present in the target release has been detected.

After migration to the target release, recreate the dropped index using fewer columns.

WARNING - DBEFile ! in DBEFileSet ! has been defined using RAW I/O, which is not supported under the target version of ALLBASE/SQL (DBWARN 22680). SQLMIGRATE will not perform a migration on the DBEnvironment if this DBEFILE uses RAW I/O when the MIGRATE command is issued.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

Use the SQLUtil MOVEFILE command to move this DBEFile into a standard HP-UX file before attempting the migration.

WARNING - View !.! was not found, so it will not be dropped during the migration (DBWARN 22690).

A PREVIEW command was in progress when this message was issued. SQLMigrate could not find a view that needs to be dropped during the migration. The DBEnvironment is probably being migrated a second time (i.e. backward after a forward migration, or forward after a backward migration) without performing a START DBE NEWLOG after the first migration.

No action is necessary.

WARNING - View !.! was not found, so it was not dropped (DBWARN 22695).

A MIGRATE command was in progress when this message was issued. SQLMigrate could not find a view that needs to be dropped during the migration. The DBEnvironment is probably being migrated a second time (i.e. backward after a forward migration, or forward after a backward migration) without performing a START DBE NEWLOG after the first migration.

No action is necessary.

WARNING - View !.! is defined on a table or view that will be dropped during the migration (DBWARN 22700). This view will also be dropped. The SELECTSTRING from SYSTEM.VIEWDEF for this view is: !

A PREVIEW command was in progress when this message was issued. The view is being dropped because a structure that it is dependent upon is being dropped.

You may wish to recreate the view after the DBEnvironment has been migrated by typing the command recorded in the SELECTSTRING.

WARNING - View !.! is defined on a table or view that is being dropped (DBWARN 22710). This view is also being dropped. The SELECTSTRING from SYSTEM.VIEWDEF for this view is: !

A MIGRATE command was in progress when this message was issued. The view is being dropped because a structure that it is dependent upon is being dropped.

You may wish to recreate the view after the DBEnvironment has been migrated by typing the command recorded in the SELECTSTRING.

WARNING - Table !.! has been created using CHECK CONSTRAINTS, which is not supported under the target version of ALLBASE/SQL (DBWARN 22720). This table will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table !.! has been created using CHECK CONSTRAINTS, which is not supported under the target version of ALLBASE/SQL (DBWARN 22730). This table is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table/view !.! is owned by user HPODBSS, and is assumed to be part of the ObjectDB product (DBWARN 22740). ObjectDB is not supported under the target version of ALLBASE/SQL. This table/view will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If the object is a table and you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command. If the object is a view, then the SELECTSTRING from SYSTEM.VIEWDEF for the view will be listed immediately after this message. You may wish to recreate the view after the DBEnvironment has been migrated by typing the command recorded in the SELECTSTRING.

WARNING - Table/view !.! is owned by user HPODBSS, and is assumed to be part of the ObjectDB product (DBWARN 22750). ObjectDB is not supported under the target version of ALLBASE/SQL. This table/view is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If the object is a table and you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command. If the object is a view, then the SELECTSTRING from SYSTEM.VIEWDEF for the view will be listed immediately after this message. You may wish to recreate the view after the DBEnvironment has been migrated by typing the command recorded in the SELECTSTRING.

WARNING - Table/view !.! is owned by user CATALOG, which will become a special user under the target version of ALLBASE/SQL (DBWARN 22760). New views owned by CATALOG will be created during the START DBE command under the target version of ALLBASE/SQL. To ensure that ALLBASE/SQL is able to create all new views correctly, please take the following steps using the target version of ALLBASE/SQL: 1) perform a START DBE NEWLOG command (to complete the migration of this DBEnvironment), 2) perform a DROP TABLE or DROP VIEW command to drop this table/view, 3) perform a STOP DBE command, and 4) perform a START DBE command, to ensure that all new views owned by CATALOG are created correctly.

A forward migration was either PREVIEWED or in progress when this message was issued. User data which may cause unexpected problems within ALLBASE/SQL has been detected.

Perform the steps listed in the message.

WARNING - Table/view !.! is owned by user HPODBSS, which will become a special user under the target version of ALLBASE/SQL (DBWARN 22780). To ensure that unexpected problems are not encountered, please take the following steps using the target version of ALLBASE/SQL: 1) perform a START DBE NEWLOG command (to complete the migration of this DBEnvironment), and 2) perform a DROP TABLE or DROP VIEW command to drop this table/view.

A forward migration was either PREVIEWED or in progress when this message was issued. User data which may cause unexpected problems within ALLBASE/SQL has been detected.

Perform the steps listed in the message.

WARNING - Procedure !.! has been detected in the system catalog (DBWARN 22900). Procedures are not supported under the target version of ALLBASE/SQL, so this information will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Procedure !.! has been detected in the system catalog (DBWARN 22910). Procedures are not supported under the target version of ALLBASE/SQL, so this information is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Rule !.! has been detected in the system catalog (DBWARN 22920). Rules are not supported under the target version of ALLBASE/SQL, so this information will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Rule !.! has been detected in the system catalog (DBWARN 22930). Rules are not supported under the target version of ALLBASE/SQL, so this information is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Module !.! is owned by user HPODBSS, and is assumed to be part of the ObjectDB product (DBWARN 22940). ObjectDB is not supported under the target version of ALLBASE/SQL. This module will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Module !.! is owned by user HPODBSS, and is assumed to be part of the ObjectDB product (DBWARN 22950). ObjectDB is not supported under the target version of ALLBASE/SQL. This module is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Table !.! is currently defined as a PUBLICROW table, which is not supported under the target version of ALLBASE/SQL (DBWARN 23020). This table will be altered to become a PUBLIC table during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Table !.! is currently defined as a PUBLICROW table, which is not supported under the target version of ALLBASE/SQL (DBWARN 23030). This table is being altered to become a PUBLIC table.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary.

WARNING - Procedure !.! has a multiple row result set (DBWARN 23040). In other words, the procedure includes at least one SELECT statement with no INTO clause. This feature is not supported under the target version of ALLBASE/SQL, so this procedure will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to transfer this procedure to the target release, use the SQLGEN GEN PROCEDURE command.

WARNING - Procedure !.! has a multiple row result set (DBWARN 23050). In other words, the procedure includes at least one SELECT statement with no INTO clause. This feature is not supported under the target version of ALLBASE/SQL, so this procedure is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary. If you need to recover the procedure, the backup version of the DBEnvironment must be restored. If you need to transfer this procedure to the target release, use the SQLGEN GEN PROCEDURE command.

WARNING - Table !.! has more than 255 columns, which is not supported under the target version of ALLBASE/SQL(DBWARN 23060). This table will be dropped during the migration.

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - Table !.! has more than 255 columns, which is not supported under the target version of ALLBASE/SQL(DBWARN 23070). This table is being dropped.

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

No action is necessary. If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.

WARNING - DBEFile ! (having FILEID '!') in DBEFileSet ! is detached, which is not supported under the target version of ALLBASE/SQL (DBWARN 23080).

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

SQLMIGRATE will not perform a migration on the DBEnvironment if this DBEFILE is detached when the MIGRATE command is issued. Use the SQLUtil ATTACHFILE command to attach this DBEFile back to the DBEnvironment before attempting the migration.

WARNING - DBEFile ! (having FILEID '!') in DBEFileSet ! is detached, which is not supported under the target version of ALLBASE/SQL (DBWARN 23090).

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

You must use the SQLUtil ATTACHFILE command to attach this DBEFile back to the DBEnvironment before a migration can be attempted.

WARNING - Constraint, procedure, or rule sections exist in DBEFileSet !, which is not supported under the target version of ALLBASE/SQL (DBWARN 23130).

A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

SQLMIGRATE will not perform a migration on the DBEnvironment if these sections remain in this DBEFileSet when the MIGRATE command is issued. Use the ISQL EXTRACT and INSTALL commands to move these sections into the SYSTEM DBEFileSet before attempting the migration.

WARNING - Constraint, procedure, or rule sections exist in DBEFileSet !, which is not supported under the target version of ALLBASE/SQL (DBWARN 23150).

A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.

You must use the ISQL EXTRACT and INSTALL commands to move these sections into the SYSTEM DBEFileSet before a migration can be attempted.

Datacomm type must be ARPA if the client and/or server is running HP-UX 10.0 or greater. (DBWARN 28027)

ARPA is the only valid datacomm type if the client and/or server is running HP-UX 10.0 or greater.

If HP-UX release on the client and/or server is 10.0 or greater, then change datacomm type to ARPA, otherwise current entry is valid.

Local database connection failed with DBERR !. Remote access attempted. (DBWARN 29007)

You specified a file name in the START DBE or CONNECT statement that does not exist on the local node.

If you wanted to access a local DBEnvironment, refer to the DBERR returned in the error message.

Diskless node. Remote access attempted directly. (DBWARN 29009)

This is the second of two messages. The first message indicates a failure to remotely connect to a DBEnvironment. This message acknowledges that no attempt to connect to the local DBE was made because you are on a diskless node.

Resolve the remote access problem, as specified in the first of the two messages and try again.

Number of tables exceeds internal maximum (max=!) (DBWARN 34073)

In shared memory, table ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON reads from SYSTEM.TABLE and SYSTEM.COLUMN to obtain information that maps each TID to an OWNER.TABLE name. There is a limit to the number that can be mapped: if the number of tables within the DBEnvironment exceeds the limit, then DBWARN 34073 is displayed. A table encountered after the limit has been reached is treated as follows:

In the LOCK subsystem, the name of the table is displayed in TID format, instead of as an OWNER.TABLE string, when locks are acquired on the table.

In the SAMPLEIO subsystem, the table is never displayed on the TABLES or TABINDEX screens, even though I/O activity might have been observed for it, because the internal limit also affects the number of tables for which historical I/O data is maintained. The table can appear on the OBJECTS screen if it is observed in the data buffer pool: the name of the table is displayed in TID format, instead of as an OWNER.TABLE string, and the TOTALIO field is always '???'.

In the STATIC subsystem, the table is never displayed.

If you need the limit increased, please contact your HP Service Representative or Response Center.

Number of indexes exceeds internal maximum (max=!) (DBWARN 34074)

In shared memory, B-tree index ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON reads from SYSTEM.INDEX and SYSTEM.CONSTRAINT to obtain information that maps each B-tree TID to an OWNER.TABLE/INDEX name. There is a limit to the number that can be mapped: if the number of B-tree indexes within the DBEnvironment exceeds the limit, then DBWARN 34074 is displayed. A B-tree index encountered after the limit has been reached is treated as follows:

In the SAMPLEIO subsystem, the index is never displayed on the INDEXES or TABINDEX screens, even though I/O activity might have been observed for it, because the internal limit also affects the number of indexes for which historical I/O data is maintained. The index can appear on the OBJECTS screen if it is observed in the data buffer pool: the name of the index is displayed in TID format, instead of as an OWNER.TABLE/INDEX string, and the TOTALIO field is always '???'.

In the STATIC subsystem, the index is never displayed.

If you need the limit increased, please contact your HP Service Representative or Response Center.

Number of DBEFiles exceeds internal maximum (max=!) (DBWARN 34075)

In shared memory, DBEFile ids are represented by integers. During the SET DBENVIRONMENT command, SQLMON reads from SYSTEM.DBEFILE to obtain information that maps each integer to a DBEFile name. There is a limit to the number that can be mapped: if the number of DBEFiles within the DBEnvironment exceeds the limit, then DBWARN 34075 is displayed. A DBEFile encountered after the limit has been reached is treated as follows:

In the SAMPLEIO subsystem, the DBEFile is never displayed on the SAMPLEIO screen, even though I/O activity might have been observed for it, because the internal limit also affects the number of DBEFiles for which historical I/O data is maintained.

In the STATIC subsystem, the DBEFile is never displayed.

If you need the limit increased, please contact your HP Service Representative or Response Center.

Number of referential constraints exceeds internal maximum (max=!) (DBWARN 34078)

In shared memory, referential constraint (PCR) ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON reads from SYSTEM.CONSTRAINT to obtain information that maps each PCR TID to an OWNER.TABLE/CONSTRAINT name. There is a limit to the number that can be mapped: if the number of PCRs within the DBEnvironment exceeds the limit, then DBWARN 34078 is displayed. A PCR encountered after the limit has been reached is treated as follows:

In the LOCK subsystem, the name of the PCR is displayed in TID format, instead of as an OWNER.TABLE/CONSTRAINT string, when locks are acquired on the PCR.

In the SAMPLEIO subsystem, the PCR is never displayed on the INDEXES or TABINDEX screens, even though I/O activity might have been observed for it, because the internal limit also affects the number of PCRs for which historical I/O data is maintained. The PCR can appear on the OBJECTS screen if it is observed in the data buffer pool: the name of the PCR is displayed in TID format, instead of as an OWNER.TABLE/CONSTRAINT string, and the TOTALIO field is always '???'.

In the STATIC subsystem, the PCR is never displayed.

If you need the limit increased, please contact your HP Service Representative or Response Center.

*** Bad JOB CONTROL WORD 'COLUMNS'. Default Column Size used. (DBWARN 34095)

Incorrect column size specification.

No action required if default column size is acceptable.

*** Bad JOB CONTROL WORD 'LINES'. Default Line Size used. (DBWARN 34096)

Incorrect line size syntax.

No action required if default line size is acceptable.

*** Variable 'COLUMNS' badly set. 80 used. (DBWARN 34097)

Incorrect variable column syntax.

No action required if 80 is acceptable.

*** Variable 'LINES' badly set. 24 used. (DBWARN 34098)

Incorrect variable line syntax.

No action required if 24 is acceptable.

Specified lock is not currently held by any users. (DBWARN 34400)

The LOCK OBJECT screen was being accessed when this message was displayed. The table, page, or row that you specified is not locked.

No action is necessary. Check that you specified the correct lock object.

PID not connected to the DBEnvironment. (DBWARN 34401)

The PID that you specified is not a valid PID.

Check that you specified the correct PID.

No locks qualify under the LOCKFILTER and LOCKTABFILTER. (DBWARN 34403)

No locks were found that matched the selection criteria defined by the LOCKFILTER and LOCKTABFILTER variables.

No action is necessary. Use the SET command to check the current value of each variable. If necessary, use the SET LOCKFILTER or SET LOCKTABFILTER command to change a value.

No other session is waiting on this session. (DBWARN 34404)

The LOCK IMPEDE screen was being accessed when this message was displayed. The session that is being analyzed is not holding any lock that is causing another session to wait.

No action is necessary. Check that you have specified the correct session.

XID changed while collecting data! (DBWARN 34405)

The LOCK SESSION, LOCK IMPEDE, or LOCK TABSUMMARY screen was being accessed when this message was displayed. To minimize performance degradation of the DBEnvironment, SQLMON itself never holds locks or latches in the LOCK subsystem; it essentially performs "dirty" reads to collect data. While data was being collected, the transaction id of the session being analyzed changed.

No action is necessary. When interpreting the screen, keep in mind that the information displayed may represent locks from two different transactions.

Lock information changed while collecting data! (DBWARN 34406)

The LOCK OBJECT screen was being accessed when this message was displayed. To minimize performance degradation of the DBEnvironment, SQLMON itself never hold locks or latches in the LOCK subsystem; it essentially performs "dirty" reads to collect data. SQLMON has detected that an inconsistent snapshot may have been taken.

Ignore the information displayed on the screen.

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

You tried to access an SQLMON screen without naming the database that you wish to examine.

Issue a SET DBENVIRONMENT command.

DBEnvironment is not active (no other session in progress). (DBWARN 34505)

Except for your SQLMON session, the database is idle.

You can only access screens in the STATIC subsystem. All other screens display information that is only available when the database is active.

DBEnvironment is in the process of shutting down (RC 215). (DBWARN 34510)

The DBA has probably issued a STOP DBE command. Once it has completed, the database will be idle.

No action is necessary. When the database becomes idle, you will only be able to access screens in the STATIC subsystem.

DBEnvironment transaction limit has been reached. (DBWARN 34511)

A timeout occurred when SQLMON tried to begin a transaction, probably because the configured limit for the maximum number of active transactions has been reached.

Access the OVERVIEW screen: the MAX XACT field displays the transaction limit, and the ACTIVE XACT field displays the current number of active transactions. You may wish to use the SQLUtil ALTDBE command to increase the transaction limit.

Also, use the SET command to check the current value of the USERTIMEOUT variable, which specifies the number of seconds that SQLMON will wait before timing out. You may wish to use the SET USERTIMEOUT command to increase the value, and then issue your original command again.

Could not obtain share lock on SUBSYSTEM CATALOG. (DBWARN 34515)

SQLMON could not read from an internal table.

Please contact your HP Service Representative or Response Center.

Not attempting to map information from SYSTEM.TABLE. (DBWARN 34518)

In shared memory, table ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON normally reads from SYSTEM.TABLE to obtain information that maps each TID to an OWNER.TABLE name. Because of some error, SQLMON is not able to read from SYSTEM.TABLE. Therefore, table names will be displayed in TID format, instead of as OWNER.TABLE strings.

Resolve the error, and try again. If necessary, contact your HP Service Representative or Response Center.

Not attempting to map information from SYSTEM.INDEX. (DBWARN 34519)

In shared memory, B-tree index ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON normally reads from SYSTEM.INDEX to obtain information that maps each TID to an OWNER.TABLE/INDEX name. Because of some error, SQLMON is not able to read from SYSTEM.INDEX. Therefore, index names will be displayed in TID format, instead of as OWNER.TABLE/INDEX strings.

Resolve the error, and try again. If necessary, contact your HP Service Representative or Response Center.

Not attempting to map information from SYSTEM.DBEFILE. (DBWARN 34520)

In shared memory, DBEFile ids are represented by integers. During the SET DBENVIRONMENT command, SQLMON normally reads from SYSTEM.DBEFILE to obtain information that maps each integer to a DBEFile name. Because of some error, SQLMON is not able to read from SYSTEM.DBEFILE. Therefore, DBEFile names will be displayed as integers, instead of strings.

Resolve the error, and try again. If necessary, contact your HP Service Representative or Response Center.

Not attempting to map information from SYSTEM.CONSTRAINT. (DBWARN 34521)

In shared memory, referential constraint (PCR) ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON normally reads from SYSTEM.CONSTRAINT to obtain information that maps each PCR TID to an OWNER.TABLE/CONSTRAINT name. Because of some error, SQLMON is not able to read from SYSTEM.CONSTRAINT. Therefore, PCR names will be displayed in TID format, instead of as OWNER.TABLE/CONSTRAINT strings.

Resolve the error, and try again. If necessary, contact your HP Service Representative or Response Center.

USERTIMEOUT exceeded maximum, so it was reset to ! seconds. (DBWARN 34580)

You probably tried to issue a SET USERTIMEOUT command using a timeout value that was larger than the maximum timeout value that has been configured for the database. The USERTIMEOUT variable has automatically been reset to the maximum timeout value, which is displayed in the message.

No action is necessary.