Utility Error Messages (contd) [ TurboIMAGE/XL Database Management System Reference Manual ] MPE/iX 5.0 Documentation
TurboIMAGE/XL Database Management System Reference Manual
Utility Error Messages (contd)
Utility Program Conditional Messages (contd)
MESSAGE FWRITE ERROR ON filename:ferrmsg
MEANING FWRITE failure on user recovery file.
ACTION Check ferrmsg to determine the cause.
---------------------------------------------------------------
MESSAGE GROUP NAME MORE THAN 8 CHARACTERS
MEANING The group name part of dbname2 is too long.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE ILR MUST BE DISABLED BEFORE AUTODEFER CAN BE
ENABLED
MEANING Deferred output option (AUTODEFER) cannot be used
when the database has been enabled for ILR or
ROLLBACK.
ACTION Use DBUTIL to disable ILR or ROLLBACK and enable
AUTODEFER. (Refer to chapters 7 and 8 for more
information on AUTODEFER.)
---------------------------------------------------------------
MESSAGE INCOMPLETE
PURGE
RELEASE
SECURE
MEANING The operation was interrupted while in process.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INCOMPLETE DBNAME2
MEANING 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 EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE INCOMPLETE LOCAL PART
MEANING 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 EDITOR to change the HELLO command in the RDBA
access file.
---------------------------------------------------------------
MESSAGE INCOMPLETE REMOTE PART
MEANING The period following the rusername was missing, or
the raccountname was missing, or the raccountname
was followed by a comma and the rgroupname was
missing.
ACTION Use EDITOR to change the HELLO command in the RDBA
access file.
---------------------------------------------------------------
MESSAGE INSUFFICIENT DISC SPACE
MEANING The amount of disk space required for the database
is not available on the system.
ACTION Consult with the database administrator about disk
space requirements.
---------------------------------------------------------------
MESSAGE INSUFFICIENT VIRTUAL MEMORY
MEANING Not enough virtual memory is available to open and
access the database.
ACTION Try running the utility later when the system is
not as busy.
---------------------------------------------------------------
MESSAGE INTERNAL ERROR--DATABASE CONTAINS INVALID LOGGING
IDENTIFIER
MEANING The logging ID configured in the database through
DBUTIL is not configured through the MPE GETLOG
command.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID ACCESS CLASS NUMBER
MEANING The access class should be a number between 1 and
63.
ACTION Reenter with a valid access class number.
---------------------------------------------------------------
MESSAGE INVALID CHARACTER IN PASSWORD
MEANING Password does not consist of allowed characters.
ACTION Check the password specified and reenter the
command.
---------------------------------------------------------------
MESSAGE INVALID COMMAND
MEANING Command is unknown to the utility.
ACTION Check spelling or see manual for legal commands.
---------------------------------------------------------------
MESSAGE INVALID CONTENTS OF ASCII ACCESS FILE
ACTIVATION / DEACTIVATION FAILED
MEANING The file specified is either
1. Not a database-access file, or
2. It does not contain the valid format and
parameters.
ACTION Either
1. Verify the correct database-access file, or
2. Use EDITOR to make the required changes and
try accessing again.
---------------------------------------------------------------
MESSAGE INVALID DATABASE CONTROL BLOCK
MEANING TurboIMAGE/XL encountered an inconsistency in the
control blocks.
ACTION Contact your system engineer.
---------------------------------------------------------------
MESSAGE INVALID DATABASE ACCESS FILE NAME
MEANING The file name or database name must be 1 to 6
characters starting with a letter.
ACTION Reenter the command with the correct name.
---------------------------------------------------------------
MESSAGE INVALID DATABASE NAME
MEANING The file name or database name must be 1 to 6
characters starting with a letter.
ACTION Reenter the command with the correct name.
---------------------------------------------------------------
MESSAGE INVALID DATABASE NAME OR ACCESS FILE NAME
MEANING The file name or database name must be 1 to 6
characters starting with a letter.
ACTION Reenter the command with the correct name.
---------------------------------------------------------------
MESSAGE INVALID DB INTRINSIC CODE IN LOG RECORD CODE FIELD
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID DELIMITER
MEANING The command or a space is incorrectly positioned.
ACTION Use HELP to check command syntax and reenter the
command.
---------------------------------------------------------------
MESSAGE INVALID FIRST LOG FILE NAME
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID FIRST LOG FILE SEQUENCE NUMBER
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID FIRST LOG FILE TIMESTAMP
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID IMAGE LOG RECORD DETECTED
MEANING DBRECOV encountered an undefined log record code.
ACTION Notify the database administrator and HP support
personnel.
---------------------------------------------------------------
MESSAGE INVALID LANGUAGE
MEANING Language name or number has invalid characters.
ACTION Retype the correct language name or number.
---------------------------------------------------------------
MESSAGE INVALID LOG CODE IN LOG RECORD
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID LOG DEVICE TYPE IN LOG RECORD
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID LOG FILE DEVICE TYPE
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE INVALID MAINTENANCE WORD
MEANING An incorrect maintenance word was used.
ACTION Check the maintenance word specified and reenter
the command.
---------------------------------------------------------------
MESSAGE INVALID NUMBER OF BUFFERS SPECIFIED
MEANING The number of buffers must be between 4 and 255.
ACTION Reenter the DBUTIL SET command with a valid number.
---------------------------------------------------------------
MESSAGE INVALID NUMBER OF USERS SPECIFIED
MEANING The minimum number of users allowed is 1 and the
maximum is 120. The ranges of users specified must
be in ascending order.
ACTION Reenter the DBUTIL SET command with a valid number.
---------------------------------------------------------------
MESSAGE INVALID PARAMETER
MEANING You specified an incorrect parameter.
ACTION Use HELP to check the command format and reenter
the command.
---------------------------------------------------------------
MESSAGE INVALID PASSWORD FOR DATABASE LOGGING IDENTIFIER
MEANING Log password does not correspond with the log
identifier used with the MPE GETLOG command.
ACTION Use DBUTIL to set the valid log identifier password
into the database.
---------------------------------------------------------------
MESSAGE INVALID SUBSYSTEM ACCESS FLAG IN ROOT FILE
MEANING TurboIMAGE/XL detected an invalid value for the
subsystem access in the root file. Valid accesses
are READ, R/W, and NONE.
ACTION Reset the subsystem access flag using the DBUTIL
SET command.
---------------------------------------------------------------
MESSAGE INVALID (x) IN COLUMN y
MEANING The x represents the invalid character found in
column y.
ACTION Use EDITOR to change the database-access file
record which returns the error message.
---------------------------------------------------------------
MESSAGE LANGUAGE MUST NOT BE LONGER THAN 16 CHARACTERS
MEANING The language name is too long.
ACTION Retype the correct language name.
---------------------------------------------------------------
MESSAGE LANGUAGE NOT SUPPORTED
MEANING The language is not supported on your system or is
not a valid language name.
ACTION Check with your database administrator for the
configuration of the language, or enter a valid
language name or number.
---------------------------------------------------------------
MESSAGE LESS THAN 3 RECORDS IN FILE!
MEANING The database-access file does not contain a FILE,
DSLINE, or HELLO command.
ACTION Use EDITOR to create the missing records.
---------------------------------------------------------------
MESSAGE LOCAL ACCT NAME IS TOO LONG
MEANING lacctname is more than eight characters.
ACTION Use EDITOR to change the lacctname.
---------------------------------------------------------------
MESSAGE LOCAL GROUP NAME IS TOO LONG
MEANING lgroupname has more than eight characters.
ACTION Use EDITOR to change the lgroupname.
---------------------------------------------------------------
MESSAGE LOCAL USER NAME TOO LONG
MEANING lusername has more than eight characters.
ACTION Use EDITOR to change the lusername.
---------------------------------------------------------------
MESSAGE LOG BUFFER OVERFLOW
MEANING Buffer space is insufficient to build the log
record.
ACTION Notify the database administrator and HP support
personnel.
---------------------------------------------------------------
MESSAGE LOG BUFFER OVERFLOW DURING GET NEXT LOGICAL LOG
RECORD
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE LOG FILE AND DATABASE IDs DO NOT MATCH
MEANING Internal error. Database is not using the correct
log file.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE LOGFILE AND DATABASE LOGID'S DO NOT MATCH
MEANING The restored database does not match the log file.
ACTION Be sure the log file and the backup database are
properly attached.
---------------------------------------------------------------
MESSAGE LOG FILE HEADER RECORD IS NOT FIRST RECORD
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE LOGFILE IS EMPTY
MEANING The log file has no records.
ACTION Be sure you have correctly identified the log file.
---------------------------------------------------------------
MESSAGE LOG FILE OPEN FAILED
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE LOG FILE RECORD SIZE IS IMPROPER
MEANING Internal error. The records are not 256 bytes with
a fixed length.
ACTION Be sure this file is actually a log file. Contact
your database administrator.
---------------------------------------------------------------
MESSAGE LOGID:logid IS INVALID
MEANING The database logid has been removed from the MPE
table.
ACTION Set the database to an existing logid, or use the
MPE GETLOG command to establish the database logid
on the MPE table.
---------------------------------------------------------------
MESSAGE LOGID MUST NOT BE LONGER THAN 8 CHARACTERS
MEANING The logid name is too long.
ACTION Retype the correct logid to set into the database.
---------------------------------------------------------------
MESSAGE LOGID PASSWORD IS INCORRECT
MEANING The password has been altered, or you are using the
wrong password.
ACTION Set the logid with the correct password into the
database.
---------------------------------------------------------------
MESSAGE LOGGING IS ENABLED, CAN NOT CLEAR LOGID
MEANING The logid cannot be changed while logging is in
process in order to ensure validity of recovery and
logging.
ACTION Change the logid after the recovery process has
completed.
---------------------------------------------------------------
MESSAGE LOG PERIOD DOES NOT EQUAL ONE (1)
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE MAINTENANCE WORD CANNOT BE CHANGED UNTIL RECOVERY
HAS COMPLETED
MEANING Changing maintenance word was attempted when
recovery was enabled.
ACTION After the recovery process has completed use the
DBUTIL SET command to change the maintenance word.
---------------------------------------------------------------
MESSAGE MAINTENANCE WORD REQUIRED
MEANING The user invoking the utility is not the creator of
the referenced database and has not supplied a
maintenance word.
ACTION If DBUTIL, reenter the command with the maintenance
word. Otherwise correct the error or press return
to terminate the program.
---------------------------------------------------------------
MESSAGE MAINTENANCE WORD TOO LONG
MEANING The specified maintenance word has more than eight
characters.
ACTION Reenter the command with the correct maintenance
word.
---------------------------------------------------------------
MESSAGE MAXIMUM ERROR COUNT HAS BEEN EXCEEDED
MEANING DBRECOV keeps track of all the errors that were
encountered. If the number goes past a certain
threshold (default is 0, but can be configured up
to a maximum of 3000), DBRECOV will abort.
ACTION Correct the problems causing the errors. If the
user specifies an error count, this count could
also be increased.
---------------------------------------------------------------
MESSAGE MAXIMUM WARNING COUNT HAS BEEN EXCEEDED
MEANING DBRECOV keeps track of all the warnings that were
encountered. If the number goes past a certain
threshold, DBRECOV will abort.
ACTION If the user specifies a warning count, this count
could be increased.
---------------------------------------------------------------
MESSAGE MISSING!!
MEANING The keyword FILE is not found in the first record;
or the keyword DSLINE is not found in the second
record; or the keyword HELLO is not found in any of
the remaining records.
ACTION Use EDITOR to modify the record in the
database-access file that returned the error
message.
---------------------------------------------------------------
MESSAGE MISSING DBNAME1
MEANING An equal sign (=), semicolon (;), or end of line
followed the keyword FILE.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE MISSING DBNAME2
MEANING dbname1= was followed by a semicolon (;) or end of
line.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE MISSING DSDEVICE
MEANING DEV= was followed by a semicolon (;), #, or the
rest of the record was blank.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE MISSING LOCAL PART
MEANING No characters preceded the =HELLO command.
ACTION Use EDITOR to change the HELLO command.
---------------------------------------------------------------
MESSAGE MISSING REMOTE PART
MEANING The remote-ID-sequence of the database-access file
is missing.
ACTION Use EDITOR to add the remote part.
---------------------------------------------------------------
MESSAGE MISSING REMOTE PASWD
MEANING HELLO was not followed by text, or was followed by
a semicolon (;).
ACTION Using the EDITOR, change the HELLO command.
---------------------------------------------------------------
MESSAGE MISSING SEMI-COLON
MEANING DEV= was not preceded by a semicolon (;)
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE MISSING # SIGN
MEANING dsdevice was not followed by a #.
ACTION Use EDITOR to change the FILE command.
---------------------------------------------------------------
MESSAGE MORE THAN ONE (1) LOG FILE HEADER RECORD IS FOUND
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE MULTIPLE LOG IDENTIFIERS NOT ALLOWED
MEANING You tried to simultaneously recover databases that
logged to different log files.
ACTION Run DBRECOV once for each log file.
---------------------------------------------------------------
MESSAGE MUSTRECOVER MUST BE DISABLED BEFORE LOGGING CAN BE
DISABLED
MEANING Logging cannot be disabled while MUSTRECOVER is
active.
ACTION Disable MUSTRECOVER first and then disable logging.
---------------------------------------------------------------
MESSAGE MUSTRECOVER & ROLLBACK MUST BE DISABLED BEFORE
DISABLING LOGGING
MEANING Logging cannot be disabled if either MUSTRECOVER or
roll-back recovery is active.
ACTION Disable both MUSTRECOVER and roll-back recovery
before disabling Logging.
---------------------------------------------------------------
MESSAGE NEGATIVE CURRENT RECORD NUMBER IN BACKSPACE REQUEST
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE NEGATIVE NUMBER OF BACKSPACES REQUESTED
MEANING Internal error.
ACTION Contact your database administrator.
---------------------------------------------------------------
MESSAGE NLS RELATED ERROR
MEANING An error was returned by NLS/3000 on a DBOPEN on
the database.
ACTION Notify the database administrator.
---------------------------------------------------------------
MESSAGE NLINFO FAILURE
MEANING An error was returned by NLS/3000.
ACTION Notify database administrator.
---------------------------------------------------------------
MESSAGE NO DATABASE HAS BEEN SPECIFIED FOR RECOVERY
MEANING RUN command has been entered and no databases have
been specified for recovery.
ACTION Use the RECOVER command to specify database(s) or
EXIT to terminate.
---------------------------------------------------------------
MESSAGE NO INDEXING PRODUCT CONFIGURED
MEANING This message is returned if you are not using
third-party indexing (TPI) and you attempted to
disable the database for indexing. The message is
generated by the DBUTIL DISABLE database name FOR
INDEXING command when the database is not
configured for third-party indexing.
ACTION Disregard the message if your database is not
configured for third- party indexing.
---------------------------------------------------------------
MESSAGE NO INDEXING PRODUCT CONFIGURED; CANNOT ENABLE
INDEXING
MEANING This message is returned if you are using
third-party indexing (TPI). The message is
generated by the DBUTIL ENABLE database name FOR
INDEXING command when the database is not yet
configured for third-party indexing using the
third-party utility. The database must be
configured for indexing before it can be enabled
for indexing.
ACTION Refer to your third-party vendor documentation for
instructions on configuring the database for
indexing. Once you have configured the database
for indexing, retry enabling the database for
indexing.
---------------------------------------------------------------
MESSAGE NON-CREATOR ACCESS NOT PERMITTED
MEANING You must be the database creator to perform this
function, or you must use the maintenance word.
ACTION Log on as the database creator, or use the
maintenance word with the command. If the
maintenance word is not set, have the creator set
one.
---------------------------------------------------------------
MPE/iX 5.0 Documentation