HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Warning Messages (Continued)
22970 MESSAGE WARNING - DBEFile ! in DBEFileSet ! is a
pseudo-mapped file, which is not supported under
the target version of ALLBASE/SQL (DBWARN 22970).
The MPE/iX filename for this DBEFile is !.
CAUSE 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.
ACTION You must use the SQLUtil MOVEFILE command to move
this DBEFile into a mapped file before a migration
can be attempted.
----------------------------------------------------------------------------
23020 MESSAGE 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.
CAUSE 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.
ACTION No action is necessary.
----------------------------------------------------------------------------
23030 MESSAGE 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.
CAUSE 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.
ACTION No action is necessary.
----------------------------------------------------------------------------
23040 MESSAGE 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.
CAUSE 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.
ACTION If you need to transfer this procedure to the
target release, use the SQLGEN GEN PROCEDURE
command.
----------------------------------------------------------------------------
23050 MESSAGE 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.
CAUSE 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.
ACTION 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.
----------------------------------------------------------------------------
23060 MESSAGE 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.
CAUSE 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.
ACTION If you need to transfer this data to the target
release, use the ISQL UNLOAD EXTERNAL command.
----------------------------------------------------------------------------
23070 MESSAGE 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.
CAUSE 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.
ACTION 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.
----------------------------------------------------------------------------
23080 MESSAGE WARNING - DBEFile ! (having FILEID '!') in
DBEFileSet ! is detached, which is not supported
under the target version of ALLBASE/SQL (DBWARN
23080).
CAUSE 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.
ACTION 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.
----------------------------------------------------------------------------
23090 MESSAGE WARNING - DBEFile ! (having FILEID '!') in
DBEFileSet ! is detached, which is not supported
under the target version of ALLBASE/SQL (DBWARN
23090).
CAUSE 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.
ACTION You must use the SQLUtil ATTACHFILE command to
attach this DBEFile back to the DBEnvironment
before a migration can be attempted.
----------------------------------------------------------------------------
23100 MESSAGE WARNING - DBEFile ! (having FILEID '!') exists in
a group.account other than the one in which the
DBECON file resides, which is not supported under
the target version of ALLBASE/SQL (DBWARN 23100).
CAUSE 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.
ACTION SQLMIGRATE will not perform a migration on the
DBEnvironment if this DBEFILE remains in this
group.account when the MIGRATE command is issued.
Use the SQLUtil MOVEFILE command to move this
DBEFile into the same group.account as the DBECon
file before attempting the migration.
----------------------------------------------------------------------------
23120 MESSAGE WARNING - DBEFile ! (having FILEID '!') exists in
a group.account other than the one in which the
DBECON file resides, which is not supported under
the target version of ALLBASE/SQL (DBWARN 23120).
CAUSE 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.
ACTION You must use the SQLUtil MOVEFILE command to move
this DBEFile into the same group.account as the
DBECON file before a migration can be attempted.
----------------------------------------------------------------------------
23130 MESSAGE WARNING - Constraint, procedure, or rule sections
exist in DBEFileSet !, which is not supported under
the target version of ALLBASE/SQL (DBWARN 23130).
CAUSE 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.
ACTION 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.
----------------------------------------------------------------------------
23150 MESSAGE WARNING - Constraint, procedure, or rule sections
exist in DBEFileSet !, which is not supported under
the target version of ALLBASE/SQL (DBWARN 23150).
CAUSE 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.
ACTION You must use the ISQL EXTRACT and INSTALL commands
to move these sections into the SYSTEM DBEFileSet
before a migration can be attempted.
----------------------------------------------------------------------------
29007 MESSAGE Local database connection failed with DBERR !.
Remote access attempted. (DBWARN 29007)
CAUSE You specified a file name in the START DBE or
CONNECT statement that does not exist on the local
node.
ACTION If you wanted to access a local DBEnvironment,
refer to the DBERR returned in the error message.
----------------------------------------------------------------------------
33002 MESSAGE LU 6.2 Connect Warning. (DBWARN 33002)
CAUSE The AliasDB file entry has specified a DB2
connection through LU 6.2.
ACTION SQL syntax in subsequent commands should be
appropriate for DB2 connections.
----------------------------------------------------------------------------
34073 MESSAGE Number of tables exceeds internal maximum (max=!)
(DBWARN 34073)
CAUSE 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.
ACTION If you need the limit increased, please contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
34074 MESSAGE Number of indexes exceeds internal maximum
(max=!) (DBWARN 34074)
CAUSE 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.
ACTION If you need the limit increased, please contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
34075 MESSAGE Number of DBEFiles exceeds internal maximum
(max=!) (DBWARN 34075)
CAUSE 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.
ACTION If you need the limit increased, please contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
34078 MESSAGE Number of referential constraints exceeds
internal maximum (max=!) (DBWARN 34078)
CAUSE 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.
ACTION If you need the limit increased, please contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
[REV BEG]
34095 MESSAGE *** Bad JOB CONTROL WORD 'COLUMNS'. Default
Column Size used. (DBWARN 34095)
CAUSE Incorrect column size specification.
ACTION No action required if default column size is
acceptable.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
34096 MESSAGE *** Bad JOB CONTROL WORD 'LINES'. Default Line
Size used. (DBWARN 34096)
CAUSE Incorrect line size syntax.
ACTION No action required if default line size is
acceptable.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
34097 MESSAGE *** Variable 'COLUMNS' badly set. 80 used.
(DBWARN 34097)
CAUSE Incorrect variable column syntax.
ACTION No action required if 80 is acceptable.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
34098 MESSAGE *** Variable 'LINES' badly set. 24 used. (DBWARN
34098)
CAUSE Incorrect variable line syntax.
ACTION No action required if 24 is acceptable.
[REV END]
----------------------------------------------------------------------------
34400 MESSAGE Specified lock is not currently held by any
users. (DBWARN 34400)
CAUSE The LOCK OBJECT screen was being accessed when this
message was displayed. The table, page, or row
that you specified is not locked.
ACTION No action is necessary. Check that you specified
the correct lock object.
----------------------------------------------------------------------------
34402 MESSAGE CID not connected to the DBEnvironment. (DBWARN
34402)
CAUSE The CID that you specified is not a valid CID.
ACTION Check that you specified the correct CID.
----------------------------------------------------------------------------
34403 MESSAGE No locks qualify under the LOCKFILTER and
LOCKTABFILTER. (DBWARN 34403)
CAUSE No locks were found that matched the selection
criteria defined by the LOCKFILTER and
LOCKTABFILTER variables.
ACTION 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.
----------------------------------------------------------------------------