HP 3000 Manuals HP 3000 Manuals
Utility Error Messages
Two types of error messages are generated by the utility programs. The
first type consists of conditional errors associated with accessing the
desired database. For all utility programs except DBUTIL, errors
generating these messages can be corrected without terminating the run if
you are in session mode. DBUTIL errors of this type may terminate the
program. After printing the error message, the DBUTIL program reprompts
with two greater than symbols (>>). Other utilities 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 may type
a carriage return with or without leading blanks. If you are in job
mode, conditional errors always cause program termination. Conditional
error messages and their meanings are described in the section entitled
"Utility Program Conditional Messages".
Unconditional errors occur in utility programs after successful execution
has already begun. These errors usually cause program termination. The
accompanying messages and their meanings are described in the section
entitled "Utility Program Unconditional Messages."
Utility Program Conditional Messages
---------------------------------------------------------------
MESSAGE ACCESS DISABLED UNTIL RECOVERY HAS COMPLETED
CAUSE 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
CAUSE The acctname part of DBNAME2 is too long.
ACTION Use the EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE APPARENT BACKUP/LOGFILE MISMATCH
CAUSE A call to DBPUT, DBUPDATE, or DBDELETE, that
apparently succeeded when logging 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
CAUSE AUTODEFER option in DBUTIL has been enabled for the
database. ROLLBACK or ILR cannot be enabled while
output deferred mode is enabled.
ACTION Run DBUTIL and >>DISABLE AUTODEFER and >>ENABLE ILR
or ROLLBACK for the database.
---------------------------------------------------------------
MESSAGE AUTODEFER MUST BE DISABLED BEFORE ROLLBACK CAN BE
ENABLED
CAUSE The rollback recovery option cannot be used when
the database has been enabled for AUTODEFER.
ACTION Disable AUTODEFER and enable ROLLBACK using DBUTIL.
---------------------------------------------------------------
MESSAGE BACKUP DATABASE AND LOG FILE DO NOT MATCH
CAUSE 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 DATA BASE REFERENCE
CAUSE Data base 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
CAUSE 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
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE CANNOT OPEN DATABASE
CAUSE The database cannot be opened at this time. It may
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
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE CAN'T RECOVER DATA BASES IN STATISTICAL MODE
CAUSE 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 DATA BASE- DBERROR message
CAUSE Database cannot be opened.
ACTION Check the DBERROR message to determine the problem.
---------------------------------------------------------------
MESSAGE CHECKSUM FAILURE ON LOG RECORD #n -EOF ASSUMED
CAUSE May occur if the system failed and a startup
recovery is not performed. Also may occur if a
statistical recovery is used against an open log
file.
ACTION You may want to use a warmstart recovery in the
future, but this is not absolutely necessary.
---------------------------------------------------------------
MESSAGE COULD NOT FIND OPEN DATABASE IN DATABASE TABLE
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE CURRENT SINGLE TRANSACTION DOESN'T MATCH LOG
TRANSACTION
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE CURRENT TRANSACTION DOESN'T MATCH LOG FILE
TRANSACTION
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DATABASE-ACCESS FILE DOES NOT EXIST
CAUSE 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
CAUSE 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
CAUSE The file name has more than six characters.
ACTION Rename the file and try DBUTIL again.
---------------------------------------------------------------
MESSAGE DATA BASE ALREADY CREATED
CAUSE 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 DATA BASE ALREADY DISABLED FOR option
CAUSE The option has already been disabled for this
database.
ACTION Press return to terminate the program.
---------------------------------------------------------------
MESSAGE DATA BASE ALREADY ENABLED FOR option
CAUSE The option has already been enabled for this
database.
ACTION Press return to terminate the program.
---------------------------------------------------------------
MESSAGE DATA BASE CANNOT BE ERASED UNTIL RECOVERY HAS
COMPLETED
CAUSE 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 DATA BASE CANNOT BE PURGED UNTIL RECOVERY HAS
COMPLETED
CAUSE 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 DATA BASE CONTAINS INVALID LOGGING IDENTIFIER
CAUSE The log identifier in the database root file does
not exist in the MPE/iX table.
ACTION Use DBUTIL to set a valid log identifier into the
database.
---------------------------------------------------------------
MESSAGE DATA BASE HAS BEEN MODIFIED SINCE LAST RESTORE
CAUSE The DBSTORE flag has not been reset. This may 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 DATA BASE n HASN'T BEEN CREATED YET
CAUSE The database creator must run DBUTIL and CREATE the
database.
ACTION In session mode, correct the error or Return to
terminate the program.
---------------------------------------------------------------
MESSAGE DATA BASE IN USE
CAUSE 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 DATA BASE IS NOT EMPTY. LANGUAGE CANNOT BE CHANGED
CAUSE 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 DATA BASE IS REMOTE
CAUSE 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 DATA BASE NAME MAY NOT BE QUALIFIED
CAUSE 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 DATA BASE NAME TOO LONG
CAUSE The database name you specified has more than six
characters.
ACTION Try the command again with the correct name.
---------------------------------------------------------------
MESSAGE DATA BASE NOT ENABLED FOR RECOVERY
CAUSE 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 DATA BASE LANGUAGE NOT SYSTEM SUPPORTED
CAUSE The language of the database is not currently
configured on your system.
ACTION Notify the system manager.
---------------------------------------------------------------
MESSAGE DATABASE OR ACCESS FILE DOES NOT EXIST
CAUSE No such file exists in logon group or account.
ACTION Check the files in your group to find the correct
file name.
---------------------------------------------------------------
MESSAGE DATA BASE OR FILE ACCESS NAME REQUIRED
CAUSE The command must include the database or access
file name.
ACTION Reenter the command.
---------------------------------------------------------------
MESSAGE DATA BASE OR FILE ACCESS NAME TOO LONG
CAUSE File name has more than six characters.
ACTION Reenter the command with the correct name.
---------------------------------------------------------------
MESSAGE DATA BASE REQUIRES CREATION
CAUSE 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 DATABASE TABLE OVERFLOWED
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DATABASE TABLE TRANSACTION COUNT IS NEGATIVE
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DATA SET n IS MISSING
CAUSE The data set may have been purged, or was not
restored.
ACTION Contact your database administrator or system
manager.
---------------------------------------------------------------
MESSAGE DBBEGIN FOUND AN ALREADY ACTIVE TRANSACTION
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DBBEGIN FOUND PROCESS ALIVE, BUT NOT ACTIVE
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DBEND FOUND TRANSACTION STILL ALIVE AND ACTIVE
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DBEND FOUND TRANSACTION WHICH ALREADY ENDED
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE DBNAME DBSTORE OF TIME, DATE REQUIRED
CAUSE DBSTORE timestamp in database does not match those
in DBOPEN records.
ACTION Restore the proper database or use the proper log
file. You can also use the NOSTAMP option in
recovery.
---------------------------------------------------------------
MESSAGE DBLOAD TO DIFFERENT DATABASE NAME
MAINTENANCE WORD IS NOT ALLOWED
CAUSE The DBLOAD database name and maintenance word must
be the same as those used for DBUNLOAD.
ACTION Use a database name and maintenance word which were
used for the DBUNLOAD.
---------------------------------------------------------------
MESSAGE DBLOAD TO DIFFERENT GROUP OR ACCOUNT IS NOT
ALLOWED.
CAUSE DBLOAD must be done from the same group and account
as the DBUNLOAD file.
ACTION Log on to the same group and account from which the
DBUNLOAD was done. Then use DBLOAD again.
---------------------------------------------------------------
MESSAGE DUPLICATE FILE NAME
CAUSE The required file name is already assigned to
another file. Example: If the ORDERS database
requires six data sets (ORDERS01-ORDERS06), then a
previously defined file ORDERS03 will trigger this
message. This can occur if a database is not
purged before running DBRESTOR.
ACTION In session mode, correct the error or press return
to terminate the program.
---------------------------------------------------------------
MESSAGE DBNAME1 MORE THAN SIX CHARACTERS
CAUSE dbname1 is too long.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE 'DEV' MISSING
CAUSE Either the keyword DEV or the following "=" was not
found.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE DEVICE NOT 'DISC'
CAUSE The string following the "#" sign was not "DISC."
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE DSDEVICE DOESN'T MATCH FILE COMMAND
CAUSE The dsdevice name in the DSLINE command was not the
same as the dsdevice name in the FILE command.
ACTION Use EDITOR to change the command which is in error.
---------------------------------------------------------------
MESSAGE DSDEVICE NAME MORE THAN 8 CHARACTERS
CAUSE The dsdevice name is too long.
ACTION Use EDITOR to change the command which is in error.
---------------------------------------------------------------
MESSAGE EMBEDDED BLANK IN DBNAME2
CAUSE One of the periods separating the user name from
the group name or the group name from the account
name was preceded or followed by a blank.
ACTION Use EDITOR to change the file command.
---------------------------------------------------------------
MESSAGE ERROR READING ROOT FILE LABEL
CAUSE DBUTIL is unable to read the root file.
ACTION Contact your HP systems engineer.
---------------------------------------------------------------
MESSAGE ERROR READING ROOT FILE RECORD
CAUSE DBUTIL is unable to read a root file record.
ACTION Contact your HP systems engineer.
---------------------------------------------------------------
MESSAGE ERROR WRITING ROOT FILE LABEL
CAUSE DBUTIL found an error while writing the root file
label.
ACTION Contact your HP systems engineer.
---------------------------------------------------------------
MESSAGE ERROR WRITING ROOT FILE RECORD
CAUSE DBUTIL found an error while writing to a root file
record.
ACTION Contact your HP systems engineer.
---------------------------------------------------------------
MESSAGE EXCEEDS ACCOUNT DISC SPACE
CAUSE Amount of space required by the database plus the
space already assigned to other files exceeds the
disk space available to the account.
ACTION Request system manager to increase account's disk
space.
---------------------------------------------------------------
MESSAGE EXCEEDS GROUP DISC SPACE
CAUSE The amount of disk space required by the database
plus the space assigned to other files in the group
exceeds the amount of disk space available to the
account.
ACTION Request the system manager to increase the group's
disk space.
---------------------------------------------------------------
MESSAGE EXPECTED DATABASE STATE TO BE "CLOSED"
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE FCHECK FAILURE
FCLOSE FAILURE
FCONTROL FAILURE
FENTRY FAILURE
FGETINFO FAILURE
CAUSE These are exceptional errors indicating a hardware
or software failure.
ACTION Notify your system manager of the failure.
---------------------------------------------------------------
MESSAGE FFILEINFO INTRINSIC FAILED
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE FGETINFO CANNOT VERIFY THAT FILE IS TYPE "LOG"
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE FGETINFO INTRINSIC FAILED
CAUSE Internal error.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE FILE CODE IS NOT 0.
CAUSE The database-access file to be activated has a file
code of other than 0.
ACTION Be sure you have the correct EDITOR file.
---------------------------------------------------------------
MESSAGE FILE EQUATES ARE ILLEGAL FOR DATA BASE AND DATA
BASE ACCESS FILE
CAUSE DBUTIL does not allow you to equate the name of the
database or database-access file to another file
with the :FILE command.
ACTION Use the :RESET command to cancel the :FILE command.
You can either break and resume execution or exit
DBUTIL and run it again.
---------------------------------------------------------------
MESSAGE FILE file name RECSIZE TOO SMALL: LOG(S) TRUNCATED.
CAUSE User recovery file size is too small to hold the
largest log record.
ACTION Increase record size or use variable length
records.
---------------------------------------------------------------
MESSAGE FILE NAME MAY NOT BE QUALIFIED
CAUSE The file name may not be qualified with group and
account.
ACTION Log on to the same group and account and reenter
the command.
---------------------------------------------------------------
MESSAGE FILE NAME MORE THAN SIX CHARACTERS
CAUSE The file name part of dbname2 is too long.
ACTION Use the EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE FOPEN FAILURE ON logfilename:ferrmsg
CAUSE You cannot open the log file.
ACTION Examine ferrmsg to determine the cause.
---------------------------------------------------------------
MESSAGE FREAD ERROR ON ASCII ACCESS FILE
CAUSE Exceptional errors indicate a hardware or software
failure.
ACTION Notify the system manager of the error.
---------------------------------------------------------------
MESSAGE FWRITE ERROR ON filename:ferrmsg
CAUSE FWRITE failure on user recovery file.
ACTION Check ferrmsg to determine the cause.
---------------------------------------------------------------
MESSAGE GROUP NAME MORE THAN 8 CHARACTERS
CAUSE The group name part of dbname2 is too long.
ACTION Use the EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE ILR MUST BE DISABLED BEFORE AUTODEFER CAN BE
ENABLED
CAUSE Output deferred option (AUTODEFER) cannot be used
when the database has been enabled for ILR or
ROLLBACK.
ACTION Disable ILR or ROLLBACK and enable AUTODEFER using
DBUTIL. (Refer to the appropriate documentation for
more information on AUTODEFER.)
---------------------------------------------------------------
MESSAGE INCOMPLETE
PURGE
RELEASE
SECURE
CAUSE The operation was interrupted while in process.
ACTION Contact your system manager.
---------------------------------------------------------------
MESSAGE INCOMPLETE DBNAME2
CAUSE The file name or group name is followed by a period
and the rest of the record is empty. Or the next
character is a semicolon (;).
ACTION Use the EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE INCOMPLETE LOCAL PART
CAUSE The period following the local user name was
missing, or the account name was missing, or a
comma followed the account name and the group name
was missing.
ACTION Use the EDITOR to change the HELLO command.
---------------------------------------------------------------