HP 3000 Manuals HP 3000 Manuals
Utility Error Messages
Two types of error messages are generated by the utility programs. The
first type is conditional errors, which occur when a utility cannot begin
a function. Conditional errors do not cause utility program termination;
this is discussed in more detail below. The second type is unconditional
errors, which occur when a utility cannot complete a function.
Unconditional errors usually cause program termination.
Conditional errors are associated with accessing the specified database.
If you are in session mode, conditional errors can be corrected without
terminating the run. After printing the error message, all utility
programs, with the exception of DBUTIL, reprompt with the message "WHICH
DATABASE?", allowing you to reenter the database reference. If you wish
to terminate the utility program at this point, you can type a carriage
return with or without leading blanks. DBUTIL, after printing the error
message, reprompts with two greater than symbols (>>) at which point you
can exit or enter another command. When DBUTIL encounters any errors
while executing, a job control word (JCW) is set to 99. You can check
the JCW in batch mode to determine whether or not a command was accepted.
If you are in job mode and a conditional error occurs while a function is
executing, that function is terminated.
The messages associated with conditional and unconditional errors are
described along with their meanings in the sections entitled "Utility
Program Conditional Messages" and "Utility Program Unconditional
Messages."
Utility Program Conditional Messages
-----------------------------------------------------------------
MESSAGE ACCESS DISABLED UNTIL RECOVERY HAS COMPLETED
MEANING Database is disabled for access, and recovery is
enabled.
ACTION Users will be able to access the database after the
recovery process has completed.
-----------------------------------------------------------------
MESSAGE ACCT NAME MORE THAN 8 CHARACTERS
MEANING The acctname part of DBNAME2 is too long.
ACTION Use EDITOR to change the FILE command.
-----------------------------------------------------------------
MESSAGE APPARENT BACKUP/LOGFILE MISMATCH
MEANING A call to DBPUT, DBUPDATE, or DBDELETE, that
apparently succeeded when logging to the original
database has failed during recovery.
ACTION Make sure the proper backup database was restored
and that the matching log file was used for
recovery.
-----------------------------------------------------------------
MESSAGE AUTODEFER MUST BE DISABLED BEFORE ILR CAN BE
ENABLED
MEANING AUTODEFER option in DBUTIL has been enabled for the
database. ROLLBACK or ILR cannot be enabled while
deferred output is enabled.
ACTION Use DBUTIL to disable AUTODEFER and enable ILR or
ROLLBACK for the database.
-----------------------------------------------------------------
MESSAGE AUTODEFER MUST BE DISABLED BEFORE ROLLBACK CAN BE
ENABLED
MEANING The rollback recovery option cannot be used when
the database has been enabled for AUTODEFER.
ACTION Use DBUTIL to disable AUTODEFER and enable ROLLBACK
for the database. (Refer to chapters 7 and 8 for
more information on roll-back recovery.)
-----------------------------------------------------------------
MESSAGE BACKUP DATABASE AND LOG FILE DO NOT MATCH
MEANING The logid of the log file and the logid in the
database being recovered do not match; i.e., the
correct log file is not being used for recovery.
ACTION Make sure that the database is using the correct
log file.
-----------------------------------------------------------------
MESSAGE BAD DATABASE REFERENCE
MEANING Database reference following the utility program
:RUN command has a syntax error.
ACTION Correct the error in session mode or press return
to terminate the program.
-----------------------------------------------------------------
MESSAGE BAD MAINTENANCE WORD
MEANING User invoking the utility is not the creator of the
referenced database and has not supplied the
correct maintenance word.
ACTION Correct the error in session mode or press return
to terminate the program.
-----------------------------------------------------------------
MESSAGE CANNOT ENABLE BREAK KEY
MEANING Internal error.
ACTION Contact your database administrator.
-----------------------------------------------------------------
MESSAGE CANNOT OPEN DATABASE
MEANING The database cannot be opened at this time. It
could already be open in a mode that does not allow
concurrent access.
ACTION Try the DBUTIL command again later.
-----------------------------------------------------------------
MESSAGE CANNOT PARSE LOG FILE NAME
MEANING Internal error.
ACTION Contact your database administrator.
-----------------------------------------------------------------
MESSAGE Cannot process data set file filename
MEANING Cannot read/write to the file due to a file system
error. Another process may have exclusive access
to the data set.
ACTION Check if the data set file exists or is locked.
Retry.
-----------------------------------------------------------------
MESSAGE CAN'T RECOVER DATA BASES IN STATISTICAL MODE
MEANING The CONTROL STATS command was entered subsequent to
a RECOVER command.
ACTION Rerun DBRECOV without using statistical mode, or
use statistical mode without specifying databases
or recovery.
-----------------------------------------------------------------
MESSAGE CAN'T OPEN DATABASE- DBERROR message
MEANING Database cannot be opened.
ACTION Check the DBERROR message to determine the problem.
-----------------------------------------------------------------
MESSAGE CHECKSUM FAILURE ON LOG RECORD #n -EOF ASSUMED
MEANING Can occur if the system failed and a startup
recovery is not performed. Also can occur if a
statistical recovery is used against an open log
file.
ACTION You may want to use a start recovery operation in
the future, but this is not absolutely necessary.
-----------------------------------------------------------------
MESSAGE COULD NOT FIND OPEN DATABASE IN DATABASE TABLE
MEANING Internal error.
ACTION Contact your database administrator.
-----------------------------------------------------------------
MESSAGE CURRENT SINGLE TRANSACTION DOESN'T MATCH LOG
TRANSACTION
MEANING Internal error.
ACTION Contact your database administrator.
-----------------------------------------------------------------
MESSAGE CURRENT TRANSACTION DOESN'T MATCH LOG FILE
TRANSACTION
MEANING Internal error.
ACTION Contact your database administrator.
-----------------------------------------------------------------
MESSAGE DATABASE-ACCESS FILE DOES NOT EXIST
MEANING No such file exists in the logon user or account.
ACTION Check the files in group to determine the correct
file name.
-----------------------------------------------------------------
MESSAGE DATABASE-ACCESS FILE NAME MAY NOT BE QUALIFIED
MEANING The DBA file name cannot be qualified with group
and account.
ACTION Log on in the same group and account as the
database- access file.
-----------------------------------------------------------------
MESSAGE DATABASE-ACCESS FILENAME TOO LONG
MEANING The file name has more than six characters.
ACTION Rename the file and try DBUTIL again.
-----------------------------------------------------------------
MESSAGE DATABASE ALREADY CREATED
MEANING You have invoked DBUTIL in the CREATE mode and
specified the name of a database which already
exists.
ACTION In session mode, correct the error or press return
to terminate program.
-----------------------------------------------------------------
MESSAGE DATABASE ALREADY DISABLED FOR option
MEANING The option has already been disabled for this
database.
ACTION Press return to terminate the program.
-----------------------------------------------------------------
MESSAGE DATABASE ALREADY ENABLED FOR INDEXING USING
third-party product name
MEANING This message is returned if you are using
third-party indexing (TPI). The message is
generated from the DBUTIL ENABLE database name FOR
INDEXING command if this database has already been
enabled for indexing.
ACTION This message is generated from the DBUTIL ENABLE
command, and you can disregard it if you want the
database to remain enabled for indexing. You can
use the DBUTIL SHOW command to verify whether or
not indexing is enabled for a particular
third-party product.
-----------------------------------------------------------------
MESSAGE DATABASE ALREADY ENABLED FOR option
MEANING The option has already been enabled for this
database.
ACTION Press return to terminate the program.
-----------------------------------------------------------------
MESSAGE DATABASE CANNOT BE ERASED UNTIL RECOVERY HAS
COMPLETED
MEANING Erasing database is attempted when recovery was
started but not completed, or while recovery is in
RESTART mode.
ACTION Press return to terminate program. After the
recovery process has completed, the user can run
DBUTIL again.
-----------------------------------------------------------------
MESSAGE DATABASE CANNOT BE PURGED UNTIL RECOVERY HAS
COMPLETED
MEANING Purging the database is attempted when recovery was
started but not completed, or while recovery is in
RESTART mode.
ACTION Press return to terminate program. After the
recovery process has completed, the user can run
DBUTIL again.
-----------------------------------------------------------------
MESSAGE DATABASE CONFIGURED FOR INDEXING USING third-party
product name, BUT NOT ENABLED FOR INDEXING
MEANING This message is returned if you are using
third-party indexing (TPI). The message is
generated from the DBUTIL DISABLE database name FOR
INDEXING command if the database has not yet been
enabled for indexing. Even if the database is
configured for indexing, by default it remains
disabled for indexing until the database is enabled
for indexing either by the TPI configuration
utility or the DBUTIL ENABLE command.
ACTION Disregard the message if you want the database to
remain disabled for indexing.
-----------------------------------------------------------------
MESSAGE DATABASE CONTAINS INVALID LOGGING IDENTIFIER
MEANING The log identifier in the database root file does
not exist in the MPE logging identifier table.
ACTION Use DBUTIL to set a valid log identifier into the
database.
-----------------------------------------------------------------
MESSAGE DATABASE HAS BEEN MODIFIED SINCE LAST RESTORE
MEANING The DBSTORE flag has not been reset. This can mean
a backup database has not been restored, or that
there have been modifications since the last
restoration.
ACTION Restore the backup database, or use the CONTROL
NOSTORE option and reenter the RECOVER command.
-----------------------------------------------------------------
MESSAGE DATABASE n HASN'T BEEN CREATED YET
MEANING The database creator must run DBUTIL and CREATE the
database.
ACTION In session mode, correct the error or press return
to terminate the program.
-----------------------------------------------------------------
MESSAGE DATABASE IN USE
MEANING Utility program cannot get exclusive access to the
referenced database due to other current users.
ACTION In session mode, press return to terminate the
program.
-----------------------------------------------------------------
MESSAGE DATABASE IS NOT ATTACHED TO ANY HP SQL
DBEnvironment
MEANING This message is returned if you are not using
ALLBASE/Turbo CONNECT (ATC) and specify an
ATC-specific option. In this case, the DETACH
option of the DBUTIL PURGE command is specified,
but the database is not attached to any ALLBASE/SQL
database environment (DBEnvironment).
ACTION Contact your database administrator.
-----------------------------------------------------------------
MESSAGE DATABASE IS NOT EMPTY. LANGUAGE CANNOT BE CHANGED
MEANING The language can be changed only on a virgin root
file or an empty database.
ACTION In session mode, press return to terminate the
program.
-----------------------------------------------------------------
MESSAGE DATABASE IS REMOTE
MEANING You must be logged on to the same group and account
containing the root file to use DBUTIL.
ACTION Do a remote logon and run DBUTIL from your remote
session.
-----------------------------------------------------------------
MESSAGE DATABASE LANGUAGE NOT SYSTEM SUPPORTED
MEANING The language of the database is not currently
configured on your system.
ACTION Notify the database administrator.
-----------------------------------------------------------------
MESSAGE DATABASE NAME MAY NOT BE QUALIFIED
MEANING The database name cannot be qualified with group
and account.
ACTION Log on to the same group and account as the
database and reenter the command.
-----------------------------------------------------------------
MESSAGE DATABASE NAME TOO LONG
MEANING The database name you specified has more than six
characters.
ACTION Try the command again with the correct name.
-----------------------------------------------------------------
MESSAGE DATABASE NOT ENABLED FOR RECOVERY
MEANING The recovery flag in the database root file is
disabled.
ACTION Be sure you are running recovery against the
appropriately restored database. You can override
the disable flag with DBUTIL if necessary.
-----------------------------------------------------------------
MESSAGE DATABASE OR ACCESS FILE DOES NOT EXIST
MEANING No such file exists in logon group or account.
ACTION Check the files in your group to find the correct
file name.
-----------------------------------------------------------------
MESSAGE DATABASE OR FILE ACCESS NAME REQUIRED
MEANING The command must include the database or access
file name.
ACTION Reenter the command.
-----------------------------------------------------------------
MESSAGE DATABASE OR FILE ACCESS NAME TOO LONG
MEANING File name has more than six characters.
ACTION Reenter the command with the correct name.
-----------------------------------------------------------------
MESSAGE DATABASE REQUIRES CREATION
MEANING The database creator must run the DBUTIL program in
CREATE mode prior to executing DBUNLOAD, DBLOAD, or
DBUTIL in ERASE mode.
ACTION In session mode, correct the error or press return
to terminate the program.
-----------------------------------------------------------------
MESSAGE DATA SET n IS MISSING
MEANING The data set could have been purged, or was not
restored.
ACTION Contact your database administrator or system
manager.
-----------------------------------------------------------------