HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
14052 MESSAGE Failed to start DBCORE. (DBERR 14052)
CAUSE You are trying to use a command which causes the
database to be started in single user mode, but the
database is already being accessed by other users
ACTION Make sure all users are logged off the database
before you issue the command that starts the
database in single user mode.
----------------------------------------------------------------------------
14056 MESSAGE File System Error in DBEnvironment. (DBERR 14056)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
14059 MESSAGE DBCore File Close error. (DBERR 14059)
CAUSE ALLBASE was not able to close the file. File name
may not be correct.
ACTION Supply the correct file name.
----------------------------------------------------------------------------
14066 MESSAGE DBECon Error - File is invalid. (DBERR 14066)
CAUSE The DBECon file name specified in the START DBE,
START DBE NEW, or START DBE NEWLOG statement is
invalid.
ACTION Refer to the ALLBASE/SQL Reference Manual for
DBECon file naming conventions.
----------------------------------------------------------------------------
14067 MESSAGE DBECon error - File System Error. (DBERR 14067)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
14071 MESSAGE Database already started in single user mode.
(DBERR 14071)
CAUSE You tried to initiate a multi-user session on a
single user DBEnvironment.
ACTION Ask your database administrator to change the
DBECon file user mode to MULTI.
----------------------------------------------------------------------------
14072 MESSAGE Database already started in multi-user mode.
(DBERR 14072)
CAUSE You tried to issue a START DBE or START DBE NEWLOG
statement when someone was already connected to the
database.
ACTION Make sure that no one is currently connected to the
DBEnvironment. The SQLMON OVERVIEW SESSION screen
can be used to see who is connected to the
DBEnvironment.
----------------------------------------------------------------------------
14073 MESSAGE Attempted to connect to more than one
DBEnvironment. (DBERR 14073)
CAUSE You tried to connect to a second DBEnvironment
while still connected to another DBEnvironment.
Your current transaction was rolled back.
ACTION Issue a RELEASE statement to disconnect from the
first DBEnvironment and then issue a START DBE or
CONNECT statement for the second DBEnvironment.
----------------------------------------------------------------------------
14074 MESSAGE DBCore internal error ! - Transaction rolled
back. (DBERR 14074) Please record the above
message including both numbers.
CAUSE An internal error caused your current transaction
to be rolled back.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
14075 MESSAGE DBCore internal error ! - Rollforward recovery
required. (DBERR 14075) Please record the above
message including both numbers.
CAUSE An internal error may have caused the DBEnvironment
to be corrupted. Your current transaction was
rolled back.
ACTION Do not perform additional transactions at this
time. Contact your database administrator for
rollforward recovery on the DBEnvironment. Record
as much information as possible and contact your HP
Service Representative or Response Center.
----------------------------------------------------------------------------
14076 MESSAGE No next log to switch to. (DBERR 14076)
CAUSE There is no valid log file to change log to.
ACTION Use ADDLOG to create a new log file then try the
CHANGELOG command again.
----------------------------------------------------------------------------
14081 MESSAGE Log directory is empty. (DBERR 14081)
CAUSE An internal error occurred when you executed the
STORELOG command
or
an internal error occurred when you executed the
PURGELOG command,
or
you specified an invalid logid.
ACTION Use the SQLUtil SHOWLOG command to verify the
logid. If the log id is correct, record as much
information as possible and contact your HP Service
Representative or Response Center.
----------------------------------------------------------------------------
14082 MESSAGE Log file cannot be purged - backup pending (DBERR
14082)
CAUSE You attempted to use the PURGELOG command on a log
file that has not been backed up.
ACTION Use the STORELOG command to store the log file, and
then purge it.
----------------------------------------------------------------------------
14083 MESSAGE Log file is not in use. (DBERR 14083)
CAUSE Note that the STORELOG command operates in two
modes - one in which the user may specify a log id
and one in which the user does not. In the latter
case, DBCore will simply scan the log directory
looking for the oldest log ready to back up. This
error will occur in the former case where DBCore
will look for the specified slot number in the log
directory (the log id is a subscript into the
directory entries). If that slot is currently
unoccupied, this error is generated.
ACTION Check the log id specified.
----------------------------------------------------------------------------
14084 MESSAGE Log file is not ready to be backed up. (DBERR
14084)
CAUSE You attempted to STORELOG the current log file.
ACTION The user must wait till this log is no longer
current.
----------------------------------------------------------------------------
14092 MESSAGE Transaction was externally aborted. (DBERR
14092)
CAUSE The transaction was aborted by another user.
ACTION None.
----------------------------------------------------------------------------
[REV BEG]
14101 MESSAGE Insufficient authorization for DBA operation.
(DBERR 14101)
CAUSE The user does not have the proper authorization.
ACTION Check the authorization and change if appropriate.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
14102 MESSAGE DBCORE version mismatch with session already
started. (DBERR 14102)
CAUSE DBCORE version does not match with the DBCORE for
the session.
ACTION Check DBCORE versions.
[REV END]
----------------------------------------------------------------------------
14103 MESSAGE Current log file cannot be purged. (DBERR 14103)
CAUSE The file to be purged is in use.
ACTION Issue the SHOWLOG command in SQLUtil to inquire if
the log file is in use.
----------------------------------------------------------------------------
14200 MESSAGE New partition instance found, and the current SCR
does not have any more slots. (DBERR 14200)
CAUSE This typically happens on a system with a large
number of partition numbers. Further, if this
system has switched master- replicate roles with a
number of other systems, it has a large number of
non-empty partitions.
ACTION The transaction is aborted by ALLBASE/SQL but the
application needs to terminate at this point.
Issue a START DBE NEWLOG with a larger
MAXPARTITIONS.
----------------------------------------------------------------------------
14201 MESSAGE Multiple database environments updated in the
same transaction. (DBERR 14201)
CAUSE A transaction attempted to replicate logging
against more than one database id.
ACTION Check the transaction logic.
----------------------------------------------------------------------------
14202 MESSAGE Log full error due to warm standby log scan.
(DBERR 14202)
CAUSE Logging cannot be done because a log lock would be
overwritten.
ACTION Remove the log lock to resume logging.
----------------------------------------------------------------------------
15047 MESSAGE DBCore internal I/O error - ! (!). (DBERR 15047)
CAUSE An unexpected file system write error occurred
during a transaction. Your current transaction was
rolled back.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description, and contact your system
administrator to check for possible disk drive
physical I/O problems.
----------------------------------------------------------------------------
15048 MESSAGE DBCore internal I/O error - ! (!). (DBERR 15048)
CAUSE An unexpected file system write error occurred
during a transaction. Your current transaction was
rolled back.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description, and contact your system
administrator to check for possible disk drive
physical I/O problems.
----------------------------------------------------------------------------
20027 MESSAGE *** Cannot update DBECON file. (! !, !, !, !)
(DBERR 20027)
CAUSE A file system error was encountered.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
[REV BEG]
20029 MESSAGE *** Cannot purge SQLMigrate log file (AASQLMIG).
(! !, !, !) (DBERR 20029)
CAUSE A file system error was encountered when trying to
purge the file named AASQLMIG. This is a temporary
file used by SQLMigrate. This file is located in
the same group as the DBECon file.
ACTION Take the necessary steps to purge this file before
attempting again the SQLMigrate command which
caused this error.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
20031 MESSAGE Cannot purge existing user log file (! !, !,
!).(DBERR 20031)
CAUSE An error occurred while trying to purge a log file
named in the DBECon file. It may not exist on the
system where the migration is being performed.
ACTION Because the log file could not be purged,
SQLMigrate did not attempt to execute the START DBE
NEWLOG command. The migration has completed
successfully, but you will not be able to use the
DBEnvironment until you have run ISQL and issued a
START DBE NEWLOG command.
[REV END]
----------------------------------------------------------------------------
20032 MESSAGE *** Cannot purge DBECON file. (! !, !) (DBERR
20032)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20034 MESSAGE *** Cannot start DBCore. (RC !, !, !, !) (DBERR
20034)
CAUSE An unexpected error occurred while trying to
establish a single user session with the
DBEnvironment.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
20035 MESSAGE *** DBCore error. (FNC !, RC !, !, !, !) (DBERR
20035)
CAUSE An unexpected internal error was encountered.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
20036 MESSAGE Unexpected INTERNAL error (!, !, !, !) (DBERR
20036)
CAUSE An unexpected internal error was encountered.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
20040 MESSAGE *** Cannot open expanded DBECON file. (! !, !)
(DBERR 20040)
CAUSE An MPE/iX file system error was encountered.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
----------------------------------------------------------------------------
20041 MESSAGE *** Cannot close expanded DBECON file. (! !, !)
(DBERR 20041)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------