HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
13132 MESSAGE Log file list contains duplicates. (DBERR 13132)
CAUSE When entering the WRAPDBE command, you specified
the same log file more than once.
ACTION Check the list of log files and reenter the new
list with no duplicates.
----------------------------------------------------------------------------
13153 MESSAGE DBEFile does not belong to specified DBEFileSet.
(DBERR 13153)
CAUSE The specified DBEFile does not belong to the
specified DBEFileSet as required by the requested
function.
ACTION Check the specified DBEFile and DBEFileSet.
----------------------------------------------------------------------------
13261 MESSAGE DBCore could not find free page buffer. (DBERR
13261)
CAUSE Due to the number of current users, DBCore was
unable to find free page buffer space. CAUTION:
Transaction not necessarily rolled back.
ACTION Try your transaction again later. You can lock
your table explicitly using the LOCK TABLE
statement to decrease the size of page buffers
required or use the SQLUtil ALTDBE command to
allocate more buffer space. If the problem
persists, record as much information as possible
and contact your HP Service Representative or
Response Center.
----------------------------------------------------------------------------
13262 MESSAGE DBCore internal error !. (DBERR 13262)
Please record the above message including both
numbers.
CAUSE An internal error caused your query to be
terminated.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
13310 MESSAGE The log directory is full. (DBERR 13310).
CAUSE The log directory allows for 34 log ids (single log
names or pairs of log names in DUAL LOG mode). Any
attempt to add the 35th log will fail. Note that
this error can happen during ADDLOG or during
SETUPRECOVERY In SQLUtil. The latter also adds a
log to the log directory.
ACTION Check the log directory (use the SHOWLOG command
for that purpose) to see if there were any logs
that you could have backed up that you did not. If
so, use STORELOG to back up these logs. Now you
have two options. If it was a direct ADDLOG, then
maybe you do not need to ADDLOG any more.
or
If it was an implicit ADDLOG during SETUPRECOVERY,
use the SQLUtil PURGELOG command to purge the
backed up log files BEFORE attempting SETUPRECOVERY
again.
----------------------------------------------------------------------------
13313 MESSAGE Wrong number of log file names specified. (DBERR
13313)
CAUSE The ADDLOG command expects either one file name in
single logging mode or two file names in dual
logging mode. You may have tried to enter more or
less than the permitted number of names.
ACTION Check the logging mode and number of log names you
specified.
----------------------------------------------------------------------------
13317 MESSAGE DBEnvironment has already finished recovery.
(DBERR 13317)
CAUSE You issued a TerminateRecovery command, but
recovery has already ended.
ACTION Eliminate the extra TerminateRecovery command.
----------------------------------------------------------------------------
13318 MESSAGE Attempted ENDRECOVERY in an inconsistent state.
(DBERR 13318)
CAUSE You are trying to end recovery at a time before the
DBEnvironment was consistent after a STOREONLINE
operation. When you enable archive mode with the
STOREONLINE command, an archive checkpoint record
is written to the log file after the online backup
is finished. This process can take some time,
during which other DBEnvironment activity continues
to be logged. You can only recover to a point
beyond the archive checkpoint record.
ACTION Do not terminate recovery. Continue to apply more
logs through RECOVERLOG at least until the archive
checkpoint record is reached. At that time,
ENDRECOVERY will be successful.
----------------------------------------------------------------------------
13319 MESSAGE The specified file is not a log file. (DBERR
13319)
CAUSE The log file name specified in response to
RECOVERLOG is not an ALLBASE log file.
ACTION Specify the correct log file name.
----------------------------------------------------------------------------
13320 MESSAGE The specified log file does not have the desired
sequence number. (DBERR 13320)
CAUSE You specified a file name with an inappropriate
sequence number. During RECOVERLOG, the log
manager expects log sequence numbers in order
(starting with the number specified in the DBECon
file of the online backup).
ACTION Specify the log file name with the correct sequence
number.
----------------------------------------------------------------------------
13322 MESSAGE SETUPRECOVERY is not done. (DBERR 13322)
CAUSE You attempted a RECOVERLOG or ENDRECOVERY without
first having done a SETUPRECOVERY.
ACTION Issue the SETUPRECOVERY command before the
RECOVERLOG or ENDRECOVERY commands.
----------------------------------------------------------------------------
13323 MESSAGE Log does not contain an archive checkpoint.
(DBERR 13323)
CAUSE An archive checkpoint was not written to the log
file, so the log file cannot be used for
rollforward recovery.
ACTION Refer to the ALLBASE/SQL Database Administration
Guide for additional information on archive
checkpoints, and to the ALLBASE/SQL Reference
Manual for information on the BEGIN ARCHIVE and
COMMIT ARCHIVE statements.
----------------------------------------------------------------------------
13324 MESSAGE Archive mode was never enabled on this
DBEnvironment. (DBERR 13324)
CAUSE You attempted a SETUPRECOVERY on this
DBEnvironment, but archive mode was never turned
on.
ACTION Check the sequence of operations. Perhaps this log
is a non-archival log, and has always been so. If
that is the case, do not attempt rollforward
recovery on this log.
----------------------------------------------------------------------------
13325 MESSAGE Log mode specification should be SINGLE or DUAL.
(DBERR 13325)
CAUSE You entered an incorrect log mode in response to a
prompt from SETUPRECOVERY in SQLUtil.
ACTION Response with either SINGLE or DUAL.
----------------------------------------------------------------------------
13326 MESSAGE Specified log id is out of range. (DBERR 13326)
CAUSE The specified log id is either < 1 or > 35 when you
issued either the PURGELOG or STORELOG command.
ACTION Use the SHOWLOG command to get the appropriate log
id.
----------------------------------------------------------------------------
13331 MESSAGE SHOWLOG internal error in computing free log
blocks. (DBERR 13331)
CAUSE Internal corruption.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
13338 MESSAGE FORMAL Designator is Invalid. (DBERR 13338)
CAUSE The group and account do not match.
ACTION Supply the correct MPE/iX group and account name.
----------------------------------------------------------------------------
13339 MESSAGE SETUPRECOVERY has already been done (DBERR 13339)
CAUSE You attempted a SETUPRECOVERY followed by either
another SETUPRECOVERY or by a set of RECOVERLOG
commands and then another SETUPRECOVERY.
ACTION Remove the extra SETUPRECOVERY command.
----------------------------------------------------------------------------
[REV BEG]
13345 MESSAGE DBE in ARCHIVE mode. Cannot overwrite with NON
ARCHIVE logging. (DBERR 13345)
CAUSE STOREONLINE was attempted with NON_ARCHIVE logging
option. However, the DBEnvironment is in archive
mode. This cannot be done because NON_ARCHIVE
logging can be done only if the DBE is in
non-archive mode.
ACTION For NON_ARCHIVE logging, turn off the archive
logging before doing STOREONLINE.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
13346 MESSAGE Build of file STORLIST failed because of
duplicate file. (DBERR 13346)
CAUSE Duplicate STORLIST file exists in the group where
SQLUtil is used.
ACTION To find and delete STORLIST, do the following:
:LISTFTEMP STORLIST
:PURGE STORLIST
Execute the SQLUtil command again.
[REV END]
----------------------------------------------------------------------------
14024 MESSAGE Deadlock detected. (DBERR 14024)
CAUSE Deadlock was detected between your transaction and
another. Your current transaction was rolled back.
ACTION Issue your command again.
----------------------------------------------------------------------------
[REV BEG]
14027 MESSAGE Session terminated by DBA. (DBERR 14027)
CAUSE Your session was terminated by a user with DBA
capability.
ACTION Access the DBE again when the system is available.
[REV END]
----------------------------------------------------------------------------
14028 MESSAGE No updates are allowed on a Wrapper DBE. (DBERR
14028)
CAUSE You attempted to do an operation that would try to
update a wrapper DBEnvironment. No updates are
allowed once the DBEnvironment has been converted
to a wrapper DBEnvironment.
ACTION Do not try to update the wrapper DBEnvironment.
----------------------------------------------------------------------------
14029 MESSAGE Your current transaction was rolled back by
DBCore. (DBERR 14029)
CAUSE Your transaction was rolled back due to another
error. An additional message will be returned.
ACTION Refer to the cause and action of the additional
message.
----------------------------------------------------------------------------
14031 MESSAGE DBCore shared memory access error. (DBERR 14031)
CAUSE Unable to access DBCore shared memory segments.
Your current transaction was rolled back.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
14035 MESSAGE DBCore shared memory overflow. (DBERR 14035)
CAUSE There was not enough space in DBCore shared memory
to complete the transaction. Your current
transaction was rolled back.
ACTION Increase the number of run-time control block pages
using the SQLUtil ALTDBE command and try your
transaction again. If the problem persists, record
as much information as possible and contact your HP
Service Representative or Response Center.
----------------------------------------------------------------------------
14038 MESSAGE DBCore shared memory allocation failed. (DBERR
14038)
CAUSE ALLBASE ran out of space for runtime control
blocks.
ACTION Use SQLUtil to increase the number of runtime
control block pages allocated.
----------------------------------------------------------------------------
14044 MESSAGE DBCore unable to allocate local heap space.
(DBERR 14044)
CAUSE The application may have too many cursors open at
one time.
ACTION Close cursors as soon as they are no longer needed
since they require a large amount of local heap
space.
----------------------------------------------------------------------------
14045 MESSAGE Log file corruption detected in DBCore. (DBERR
14045)
CAUSE Warm start could not find a checkpoint in any log
file.
ACTION Perform a roll forward recovery.
----------------------------------------------------------------------------
14046 MESSAGE Log full. (DBERR 14046)
CAUSE The log file is full. Your current transaction was
rolled back.
ACTION Shut down the database and issue a START DBE NEWLOG
statement.
----------------------------------------------------------------------------
14047 MESSAGE Current clock lower than highest in log. (DBERR
14047)
CAUSE The system clock was set forward incorrectly, used
by one or more databases, and then reset backward.
or
The system clock was set backward incorrectly.
To ensure that recovery works correctly,
ALLBASE/SQL requires that the date/time of the
current action is later than the date/time of the
preceding action. If the date/time of the current
action is earlier than the date/time of the
previous action (as is the case when this message
is returned), ALLBASE/SQL will not function until
the date/time of the current action is later than
the date/time of the previous action.
For example, if the year 1990 is entered instead of
1989, the database system will wait for a year,
unless the action below is followed.
ACTION 1. If the system clock was set forward
incorrectly, used by databases, and then set
backward, do the following:
a. Kill all database processes.
b. Set the system clock ahead of the
incorrect date used by the data.
c. Back up all the DBEnvironments that
were accessed while the incorrect
date was in effect. Use the SQLUtil
STORE command on each DBEnvironment.
d. Shut down the DBEnvironments.
e. Reset the system clock to the correct
time.
f. Issue the START DBE NEWLOG statement.
g. Resume operations.
2. If the system clock was set backward
incorrectly:
a. Set the system clock forward to the
correct time.
b. Resume operations.
Consult your system administrator for assistance in
resetting the system clock.
----------------------------------------------------------------------------