OnLine Message Log 8-7
Alphabetized Messages
The messages can be interpreted as follows:
■The first message indicates the inconsistency.
■The second message identifies the database server process affected.
■Thethird message is the header for the hexadecimal/ASCII dump of
the buffer header structure that follows.
■Thefourth message is the headers for the hexadecimal/ASCII dump
of the page header structure that follows.
call to ptmap() from ptbld() failed
OnLinedetected an error in an attempt to build a table. No action is needed.
OnLine handles the situation internally.
call to ptmap() from ptphyaddr() failed
OnLine detected an error in an attempt to translate a tblspace number to a
physical address within the tblspace tblspace. No action is needed. OnLine
handles the situation internally.
Cannot Allocate Physical Log File, nn wanted, nn available
OnLine attempted to initialize shared memory with a physical log size that
exceeds the amount of contiguous space available in the dbspace (specified
asPHYSDBS in the configuration file). Both quantities of space, wanted and
available, are expressed as kilobytes. You must either reduce the size of the
physical log (specified asPHYSFILE in the configuration file) or change the
location of the log to a dbspace that contains adequate contiguous space to
accommodate the log.
Cannot Commit Partially Complete Transactions
Withinthe fast recovery or data restore procedure, the logical log recordsare
first rolled forward. It is possible for an open transaction to fail during the
rollforward, leaving a transaction that should be committed in an incom-
plete, uncommitted state. This error does not prevent OnLine from moving
to quiescent or online mode, but it might indicate an inconsistent database.
Examine the logical log using thetblog utility to determine if any action is
needed.