ALLBASE/SQL Message Manual (36216-90213)

70 Chapter2
ALLBASE/SQL Warning Messages
in mind that the information displayed may represent
locks from two different transactions.
34406 MESSAGE Lock information changed while collecting
data!
(DBWARN 34406)
CAUSE 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.
ACTION Ignore the information displayed on the screen.
34500 MESSAGE SET DBENVIRONMENT command has not been issued
yet.
(DBWARN 34500)
CAUSE You tried to access an SQLMON screen without naming
the database that you wish to examine.
ACTION Issue a SET DBENVIRONMENT command.
34505 MESSAGE DBEnvironment is not active (no other session
in progress).
(DBWARN 34505)
CAUSE Except for your SQLMON session, the database is idle.
ACTION You can only access screens in the STATIC subsystem. All
other screens display information that is only available
when the database is active.
34510 MESSAGE DBEnvironment is in the process of shutting
down (RC 215).
(DBWARN 34510)
CAUSE The DBA has probably issued a STOP DBE command.
Once it has completed, the database will be idle.
ACTION No action is necessary. When the database becomes idle,
you will only be able to access screens in the STATIC
subsystem.
34511 MESSAGE DBEnvironment transaction limit has been
reached.
(DBWARN 34511)
CAUSE 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.
ACTION Access the OVERVIEW screen: the MAX XACT field