RDO Facility Messages





This document provides explanations and user actions for errors
returned with the RDO facility code.  These messages are generated by
the VAX Rdb/VMS Relational Database Operator (RDO) Utility.  RDO error
messages frequently indicate syntactic or semantic errors.  For
information on related messages, type, print, or search the following
files:

        SYS$HELP:RDB_MSG.DOC
        SYS$HELP:RDMS_MSG.DOC

Note that within RDO, you also have the option of typing:

RDO> HELP ERROR <facility-code> <message-name>

For example:

RDO> HELP ERROR RDB DEADLOCK

Or, from DCL level, you can use the SEARCH command to display
information about a particular message.  For example:

$ SEARCH/WINDOW=(0,10) SYS$HELP:RDO_MSG.DOC fldnotinrel
FLDNOTINREL,   <str> is not a field in relation, <str>

Explanation:   The field you specified is not part of the named
               relation.

User Action:   Check the relation definition for the correct field
               name, or specify another relation.

FLDNOTREFD,    defined field, <str>, is not used in VALID IF clause

Explanation:   You defined a field with a VALID IF clause that does













ABSACTIVE,     AIJ backup active or backup operations suspended on
               this node

Explanation:   After-image journal backup operations have already been
               suspended from this node.

User Action:   Examine the secondary message(s) or look in the



                                  1

RDO Facility Messages





               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

ABSNSUSPENDED, AIJ backup operations not suspended on this node

Explanation:   After-image journal backup operations have not been
               suspended from this node.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

ABSSUSPENDED,  AIJ backup operations already suspended on this node

Explanation:   After-image journal backup operations have already been
               suspended from this node.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

ACCVIO,        access violation on read/write of user address

Explanation:   A readable parameter is not readable by the DBCS or a
               writeable parameter is not writeable by the DBCS.

User Action:   Pass good parameters to the DBCS.

ACENOTFND,     no matching access control entry found

Explanation:   In a protection statement that refers to an existing
               access control entry, there was no existing entry that
               matched the input.

User Action:   Use SHOW PROTECTION to see what the ACL currently looks
               like, and correct your statement.

ACLNOTIMP,     ACL not imported for <str>

Explanation:   The ACL contained in the RBR file could not be imported
               to the named object (database/relation/field)

User Action:   If you really want it, you must either obtain the
               needed privileges (BYPASS) or import the database under
               the account of the former owner (which may not be
               sufficient anyway).  If you do not care about the
               restoration of protections you can ignore the message
               or import the database using the NOACL parameter which
               will cause all privileges and protections in the RBR
               file to be ignored.





                                  2

                                                 RDO Facility Messages





ACTMISMATCH,   journal is for database activation <time>, not <time>

Explanation:   The activation time and date stamp in the root does not
               match the activation time and date stamp in the journal
               file.  This journal cannot be applied to this database.

User Action:   Use the correct journal file or backup file.

AGGNOTALL,     aggregate expressions are not allowed in VALID IF
               expressions

Explanation:   You entered a VALID IF expression that contained
               something other than an operator, literal value, or the
               field name.

User Action:   Check the Oracle Rdb Reference Manual for details on
               VALID IF.

AIJACTIVE,     <num> active transaction(s) not yet committed or
               aborted

Explanation:   Upon completion of the roll-forward operations for the
               current AIJ file, more than 1 transaction remains
               active.  That is, the commit or roll-back information
               resides in the next AIJ file to be processed.  It is
               also possible that one or more of these active
               transactions are prepared transactions, which may be
               committed or aborted by the recovery operation using
               DECdtm information; in this case, a separate message
               indicating the number of prepared transactions will be
               displayed.

User Action:   No user action is required.  This message is
               informational only.

AIJALLDONE,    after-image journal roll-forward operations completed

Explanation:   The after-image journal roll-forward operation has
               completed.

User Action:   No user action is required.  This message is
               informational only.

AIJAUTOREC,    starting automatic after-image journal recovery

Explanation:   The /AUTOMATIC command qualifier was specified for the
               after-image roll-forward operation, and the
               roll-forward operation has detected that automatic
               journal recovery is possible.  This message indicates
               that automatic recovery has begun.





                                  3

RDO Facility Messages





User Action:   No user action is required.

AIJBADAREA,    inconsistent storage area <str> needs AIJ sequence
               number <num>

Explanation:   The indicated storage area has been marked inconsistent
               with the rest of the database.  The AIJ file with the
               indicated sequence number is required to commence
               recovery of the area.  If the sequence number of the
               AIJ file is different than the indicated sequence
               number, recovery of the area will not be performed.

User Action:   No user action is required.  This message is
               informational only.

AIJBADPAGE,    inconsistent page <num> from storage area <str> needs
               AIJ sequence number <num>

Explanation:   The indicated page has been marked inconsistent with
               the rest of the database.  The AIJ file with the
               indicated sequence number is required to commence
               recovery of the page.  If the sequence number of the
               AIJ file is different than the indicated sequence
               number, recovery of the area will not be performed.

User Action:   No user action is required.  This message is
               informational only.

AIJBCKACT,     AIJ modify operation not allowed; AIJ backup in
               progress

Explanation:   An AIJ backup is currently in progress.  While an AIJ
               backup is in progress, AIJ modify operations (such as,
               disabling AIJ journaling or changing the default AIJ
               filename) are not permitted.  If the AIJ backup was
               prematurely terminated by the user, another AIJ backup
               must complete before AIJ modifications are permitted.

User Action:   Allow the AIJ backup to finish before attempting the
               AIJ modify operation.  If the AIJ backup was
               prematurely terminated by the user, start another AIJ
               backup and allow it to complete.  The AIJ modify
               operation will then be possible.

AIJBCKACTV,    journal <str> backup (sequence <num>) already active

Explanation:   An AIJ backup is already active for the specified
               journal.  In most cases, the previously active backup
               is being performed by the background AIJ backup server.
               This problem only occurs when using the "by-sequence"
               AIJ backup option, and normally when specifying only a



                                  4

                                                 RDO Facility Messages





               single AIJ sequence number value (i.e.
               "/SEQUENCE=15").

User Action:   Let the active backup finish before attempting to start
               another AIJ backup operation, or specify both a
               starting and ending AIJ sequence number (i.e.
               "/SEQUENCE=(15,15)").

AIJBCKBADSEQ,  invalid AIJ backup sequence numbers (<num> through
               <num>)

Explanation:   The specified AIJ backup sequence numbers incorrect.

User Action:   Specify the sequence numbers in ascending order.

AIJBCKBEG,     beginning after-image journal backup operation

Explanation:   This is an informational message to inform the user
               that the after-image backup operation has begun.

User Action:   No user action is required.

AIJBCKCNFT,    cannot specify a backup filename and use SAME AS
               JOURNAL option

Explanation:   An attempt was made to specify an after-image backup
               filename and use the BACKUP SAME AS JOURNAL option.

User Action:   Specify one or the other of the after-image backup
               options, but not both.

AIJBCKCUR,     cannot backup current AIJ journal if no other
               unmodified journals exist

Explanation:   An attempt was made to backup the "current" after-image
               journal, but no other unmodified after-image journals
               are available.  This situation occurs when a
               "by-sequence" backup is performed in the wrong order;
               that is, the current after-image journal was backed up
               when a "modified" lower sequence after-image journal
               exists.

User Action:   Backup the lower-sequence after-image journal first.

AIJBCKDIR,     AIJ-backup filename "<str>" does not include device and
               directory

Explanation:   The AIJ-backup filename specified does not include a
               device and directory.

User Action:   For maximum protection, you should always include a



                                  5

RDO Facility Messages





               device and directory in the AIJ-backup file
               specification, preferably one that is different from
               both the database device and AIJ device.

AIJBCKDONE,    AIJ backup completed when accessing unmodified journal
               <str>

Explanation:   An attempt was made to backup an after-image journal
               that has not been modified.  This normally occurs when
               a "by-sequence" is done out of order (For instance,
               sequence 6 is backed up, then sequences 5 through 7 are
               attempted).

User Action:   In the above example, the backup was completed when the
               previously backed up AIJ sequence  6 was encountered;
               the journal containing sequence  5 was fully and safely
               backed up.  Restart the backup with the next journal
               requiring backup (in the above example, sequence  7).

AIJBCKDSBL,    database contains no after-image journals that qualify
               for backup

Explanation:   An attempt was made to perform an after-image backup
               for a database that has after-image journaling disabled
               and does not have any journals that qualify to be
               backed up.  This situation occurs if there are no
               after-image journals, or all journals are unmodified
               and do not require backup.

User Action:   No user action is required.

AIJBCKEND,     after-image journal backup operation completed
               successfully

Explanation:   This is an informational message to inform the user
               that the after-image backup operation has completed
               successfully.

User Action:   No user action is required.

AIJBCKFAIL,    the AIJ backup that created the AIJ file did not
               complete

Explanation:   It appears that the AIJ backup process, that created
               the AIJ file currently being recovered, failed or was
               prematurely terminated.  When this situation occurs, it
               is possible that one or more transactions active at the
               time of the backup failure may not have been recovered
               completely.

User Action:   Roll forward the next AIJ file, which should contain



                                  6

                                                 RDO Facility Messages





               the commit information for any transactions that were
               not completely recovered.  If there are no more AIJ
               files to be rolled forward, then all transactions have
               been completely recovered.

AIJBCKFIL,     no after-image journal backup filename specified

Explanation:   An attempt was made to back up an after-image journal,
               but no backup file name was specified, and the journal
               did not contain a default backup-file name
               specification.

User Action:   Specify an after-image journal backup filename, or
               modify the journal to contain a default backup-file
               name specification.

AIJBCKFIX,     cannot perform by-sequence AIJ backup of extensible
               journals

Explanation:   An attempt has been made to back up an "extensible"
               after-image journal using the "by-sequence" command
               qualifier.

User Action:   Do NOT use the "by-sequence" command qualifier when
               backing up an extensible AIJ journal.

AIJBCKGAP,     AIJ backup completed after skipping previously backed
               up journal sequence <num>

Explanation:   An attempt was made to back up an after-image journal
               that does not have the next chronological sequence
               number.  This condition normally occurs when a
               "by-sequence" operation is done out of order.  For
               instance, sequence 6 is backed up, then sequences 5
               through 7 are attempted.

User Action:   In the above example, the backup was completed when the
               previously backed up AIJ sequence  6 was encountered.
               The journal containing sequence  5 was fully and safely
               backed up.  Restart the backup with the next journal
               requiring back up (in the above example, sequence  7).

AIJBCKHARD,    after-image journals cannot be backed up due to
               unrecoverable data loss

Explanation:   An attempt was made to back up an after-image journal
               after loss of AIJ data has occurred.  One or more of
               the following events may have occurred:  1.  An
               inaccessible journal was deleted.  2.  A modified
               journal was deleted while journalling was disabled.  3.
               A journal was overwritten.  4.  Journal switch-over



                                  7

RDO Facility Messages





               failed.

User Action:   A full database backup must be immediately performed to
               make the database recoverable again.

AIJBCKINAC,    AIJ backup completed when accessing inaccessible
               journal <str>

Explanation:   An attempt was made to backup an after-image journal
               that is not currently accessible.

User Action:   The specified after-image journal must be deleted or
               unsuppressed before the backup will be allowed to
               proceed.

AIJBCKINTR,    invalid after-image journal backup interval value
               "<num>" specified

Explanation:   An invalid AIJ journal backup interval was specified.

User Action:   The AIJ journal backup interval specifies the number of
               seconds for which the backup utility will wait.  The
               value must be a positive number, which may include the
               value "0".

AIJBCKMOD,     cannot modify AIJ information while backup is active or
               suspended

Explanation:   An attempt was made to modify after-image journal
               information while an AIJ backup was in progress.

User Action:   Wait until the AIJ backup completes.

AIJBCKOVR,     AIJ backup not possible when modified journals have
               been overwritten

Explanation:   An attempt was made to perform an after-image backup
               when one or more of the active AIJ journals have been
               overwritten.  Backing up an AIJ journal that has been
               overwritten is not possible, because AIJ data was lost
               when the journal was overwritten, making the database
               non-recoverable.  The resulting AIJ backup file could
               not be used for subsequent AIJ roll-forward operations.

User Action:   Perform a full database backup.  Once the full database
               backup has been completed, after-image journal backup
               operations will again be possible.

AIJBCKOVRW,    AIJ backup completed when accessing overwritten journal
               <str>





                                  8

                                                 RDO Facility Messages





Explanation:   An attempt was made to back up an after-image journal
               that has been overwritten.

User Action:   While an after-image journal was in progress, the
               journal being backed up was overwritten.  Consequently,
               data-loss has occurred, and the backup operation cannot
               continue any further.  A full database backup is
               required.

AIJBCKRENAME,  /RENAME qualifier invalid when backup filespec also
               specified

Explanation:   The /RENAME qualifier cannot be specified when an AIJ
               backup filename specification is also specified, since
               these are conflicting options.

User Action:   Specify either the /RENAME qualifier (using "" for the
               AIJ backup filename specification) or the AIJ backup
               filename specification, but not both.

AIJBCKSEQ,     backing up after-image journal sequence number <num>

Explanation:   The created after-image backup file will be internally
               identified with the indicated sequence number.  When
               AIJ files are rolled forward, the roll-forward utility
               will prompt for specific AIJ sequence numbers.  The AIJ
               file sequence number should be included as a component
               of any external file identification information, such
               as magtape labels.

User Action:   No user action is required.  This message is
               informational only.

AIJBCKSTOP,    backup of after-image journal <str> did not complete

Explanation:   The AIJ backup operation of the identified journal did
               not complete, typically because of some previous backup
               failure condition.

User Action:   Restart the AIJ backup operation after correcting the
               identified problems.

AIJBCKSWTCH,   journal <str> is busy and AIJ switch-over suspended -
               add new journal

Explanation:   The AIJ switch-over operation is suspended and
               performing the requested AIJ backup operation cannot
               proceed because active processes require the specified
               AIJ journal for recovery reasons.

User Action:   It is necessary to add a new journal before performing



                                  9

RDO Facility Messages





               the AIJ backup operation.

AIJBCKTHRS,    invalid after-image journal backup threshold value
               "<num>" specified

Explanation:   An invalid AIJ journal backup threshold was specified.

User Action:   The AIJ journal backup threshold specifies the
               approximate limit on the size of the journal.  The
               value must be a positive number, which may include the
               value "0".

AIJCCHDIR,     AIJ-cache file name "<str>" does not include device and
               directory

Explanation:   The AIJ-cache filename specified does not include a
               device and directory.

User Action:   For maximum protection, you should always include a
               device and directory in the AIJ-cache file
               specification, preferably one that is different from
               both the database device and AIJ device.

AIJCONFIRM,    Do you wish to continue the roll-forward operation of
               this journal [<char>]:

Explanation:   Continue or terminate the AIJ roll-forward operation
               with the current journal file.

User Action:   Enter 'YES' to continue the roll-forward operation of
               the journal.  Enter 'NO' to terminate the roll-forward
               operation of the journal.  Any response other then
               'YES' will also result in the termination of the
               roll-forward operation.

AIJCORRUPT,    journal entry <num>/<num> contains <num>!1%Can AIJBUF
               with an invalid length!2%Can AIJBL with an invalid
               length!3%Cthe start of a new AIJBL before previous
               AIJBL is complete!4%Ca new AIJBL that doesn't have the
               start flag set!%E**!%F

Explanation:   The journal contains corruption at the location
               indicated (record number / block number).

User Action:   Contact your Oracle support representative for
               assistance.

AIJCURSEQ,     specified after-image journal contains sequence number
               <num>

Explanation:   The specified after-image journal contains the



                                  10

                                                 RDO Facility Messages





               indicated sequence number.  This sequence number must
               exactly match that expected by the roll-forward
               utility.

User Action:   No user action is required.  This message is
               informational only.

AIJDELCUR,     cannot remove the current AIJ journal "<str>"

Explanation:   An attempt was made to remove the AIJ journal currently
               in use.

User Action:   Disable AIJ journaling first, or try to remove the AIJ
               journal when the journal is no longer in use.

AIJDELMOD,     cannot remove AIJ journal "<str>" until backed up

Explanation:   An attempt was made to remove an AIJ journal that has
               not yet been backed up.

User Action:   Disable AIJ journaling first, or backup the AIJ
               journal.

AIJDEVDIR,     AIJ filename "<str>" does not include a
               device/directory

Explanation:   The after-image journal file name specified does not
               include a device and directory.

User Action:   For maximum protection, you should always include a
               device and directory in the file specification,
               preferably one that is different from the database
               device.

AIJDISABLED,   after-image journaling must be enabled for this
               operation

Explanation:   You attempted to perform an after-image journal
               operation, such as a backup of the journal file, for a
               database that has after-image journaling disabled.

User Action:   Enable after-image journaling for your database, and
               try the backup again at some later time.

AIJDSBLCUR,    cannot manually suppress the current AIJ journal
               "<str>"

Explanation:   An attempt was made to manually suppress the AIJ
               journal currently in use.

User Action:   Disable AIJ journaling first, or try to unsuppress the



                                  11

RDO Facility Messages





               AIJ journal when the journal is no longer in use.

AIJDSBLMOD,    cannot manually suppress AIJ journal "<str>" until
               backed up

Explanation:   An attempt was made to manually suppress an AIJ journal
               that has not yet been backed up.

User Action:   Disable AIJ journaling first, or backup the AIJ
               journal.

AIJDUPSVRNAM,  duplicate "Hot Standby" server name

Explanation:   The specified "Hot Standby" server name is a duplicate
               of an existing server name on this node.

User Action:   Specify another server name.

AIJENABLED,    after-image journaling must be disabled

Explanation:   You attempted to perform an operation that requires
               after-image journaling to be disabled, but the database
               still has after-image journaling enabled.

User Action:   Disable after-image journaling for your database and
               try the operation again.  After the operation has
               completed, you can enable after-image journaling again.

AIJENBOVR,     enabling AIJ journaling would overwrite an existing
               journal

Explanation:   Enabling after-image journaling would result in an
               existing AIJ journal being overwritte, which would
               result in the loss of AIJ data, making the database
               non-recoverable.

User Action:   Modify the database to allow after-image journals to be
               overwritten, or add a new AIJ journal.

AIJFILEGONE,   continuing with AIJ modification operation

Explanation:   When an attempt was made to disable AIJ journaling or
               to change the default AIJ filename, the active AIJ file
               could not be opened.  This condition typically occurs
               only for catastrophic reasons; therefore, the AIJ file
               is assumed to have contained some data records, which
               are presumed to have been lost.

User Action:   No user action is required.  This message is
               informational only.





                                  12

                                                 RDO Facility Messages





AIJFNLSEQ,     to start another AIJ file recovery, the sequence number
               needed will be <num>

Explanation:   This message informs the user what the next AIJ file
               sequence number will be.  AIJ file sequence numbers are
               modified for a variety of reasons (such as, performing
               an AIJ backup, enabling or disabling AIJ logging,
               etc.).

User Action:   No user action is required.  This message is
               informational only.

AIJGOODAREA,   storage area <str> is now consistent

Explanation:   The indicated storage area has been marked consistent
               with the rest of the database.

User Action:   No user action is required.  This message is
               informational only.

AIJGOODPAGE,   page <num> from storage area <str> is now consistent

Explanation:   The indicated page has been marked consistent with the
               rest of the database.

User Action:   No user action is required.  This message is
               informational only.

AIJHRDENB,     cannot unsuppress an AIJ journal that has hard data
               loss

Explanation:   An attempt was made to unsuppress an AIJ journal that
               experienced hard data loss.  This is not permitted
               because it would possibly leave the database in a
               non-recoverable state.

User Action:   The AIJ journal must be removed.

AIJISOFF,      after-image journaling has been disabled

Explanation:   After-image journaling has been disabled.  The database
               is no longer recoverable.  It is highly recommended
               that after-image journaling be re-enabled as soon as
               possible.

User Action:   No user action is required.

AIJISON,       after-image journaling has been enabled

Explanation:   After-image journaling has been enabled.  All
               subsequent database operations will be journaled to the



                                  13

RDO Facility Messages





               "current" journal.

User Action:   A full database backup should be performed.

AIJJRNBSY,     journal <str> is busy and cannot be backed up

Explanation:   An attempt has been made to back up an after-image
               journal that is currently required for process
               recovery.  The journal is considered to be "busy" until
               no process requires the journal for recovery.

User Action:   Use the /WAIT command qualifier to indicate that the
               after-image backup is to "wait" for the journal to
               become available; that is, the journal becomes
               available for backup when no more processes require it
               for recovery.

AIJLSSDONE,    "Hot Standby" has been shutdown

Explanation:   "Hot Standby" has been terminated.

User Action:   Restart the database replication operation.

AIJMINSZ,      allocation size is <num> blocks due to suspended AIJ
               switch-over or active replication

Explanation:   The specified AIJ journal file allocation size was
               overwritten with the optimal size indicated.  This
               action was taken to meet the requirements of the
               suspended AIJ switch-over condition.

User Action:   None.

AIJMODOBS,     cannot use deprecated modification syntax with new AIJ
               features

Explanation:   An attempt was made to modify an AIJ journal using
               deprecated syntax in a database environment where
               advanced AIJ journaling features are in use.

User Action:   The enhanced AIJ journal modification syntax must be
               used in an environment where advanced AIJ journaling
               features, such as multiple AIJ journals, are in use.

AIJMODSEQ,     next AIJ file sequence number will be <num>

Explanation:   This message informs the user what the next AIJ file
               sequence number will be.  AIJ file sequence numbers are
               modified for a variety of reasons (such as, performing
               an AIJ backup, enabling or disabling AIJ logging,
               etc.).



                                  14

                                                 RDO Facility Messages





User Action:   No user action is required.  This message is
               informational only.

AIJMODSWTCH,   AIJ switch-over suspended - add new journal or backup
               current

Explanation:   The AIJ switch-over operation is suspended and
               performing the requested operation will not succeed and
               possibly result in the database being shutdown.

User Action:   Add a new AIJ journal or, if possible, backup the
               existing journals.

AIJMOREWORK,   active transactions will be aborted if you terminate
               recovery

Explanation:   One or more active transactions will be aborted if AIJ
               recovery is terminated.

User Action:   No user action is required.  This message is
               informational only.  This message supplements the
               AIJNXTSEQ message.

AIJNAMREQ,     AIJ name or filespec necessary for modify or delete
               operations

Explanation:   In order to modify or delete an existing AIJ journal,
               either the AIJ name or the exact filename specification
               are mandatory.

User Action:   Please specify either the AIJ name or the exact
               filename specification, including VMS version number.

AIJNOACTIVE,   there are no active transactions

Explanation:   Upon completion of the roll-forward operations for the
               current AIJ file, no transactions remain active.  The
               AIJ recovery process can be terminated without the loss
               of transaction data.

User Action:   No user action is required.  This message is
               informational only.

AIJNOBACKUP,   AIJ contains no transactions that qualify for backup

Explanation:   An attempt was made to backup an after-image journal
               file that does not have any records that qualify to be
               backed up.  This situation occurs if the oldest active
               checkpoint record is in the first block of the AIJ.
               This restriction is necessary to guarantee that all
               transactions for this process will be recoverable in



                                  15

RDO Facility Messages





               the event of unexpected process failure.  This message
               is applicable only if the "fast commit" feature is
               enabled.

User Action:   The offending process(es) need to commit or rollback
               their current transaction or unbind from the database.

AIJNOENABLED,  after-image journaling has not yet been enabled

Explanation:   The after-image journal roll-forward operation has
               completed, but AIJ logging has not yet been enabled.
               This message is a reminder to the user to enable AIJ
               logging, if desired.

User Action:   If AIJ logging is desired, AIJ logging should be
               enabled.  Otherwise, no user action is required.  This
               message is informational only.

AIJNOEXT,      extraction of this journal must start with sequence
               <num>

Explanation:   The AIJ file supplied was created subsequent to the
               expected AIJ journal.  Usually, this condition occurs
               for the following reasons:  1) an incorrect AIJ file or
               VMS file "version" was specified, 2) the supplied AIJ
               file was not created for this database, 3) AIJ logging
               was disabled and then later enabled, or 4) a
               transaction is continued in this journal from a
               previous journal.

User Action:   This is a fatal condition; extraction of the AIJ
               journal CANNOT start with this journal.  You MUST start
               recovery with the AIJ journal indicated by the
               preceeding AIJSEQAFT or AIJSEQPRI message.

AIJNOOVR,      AIJ initialization not possible when journals have not
               been overwritten

Explanation:   An attempt was made to perform an after-image
               initialization when none of the active AIJ journals
               have been overwritten.  Resetting an AIJ journal that
               has not been overwritten is not possible, because AIJ
               data will be lost, making the database non-recoverable.

User Action:   None.

AIJNORCVR,     recovery must start with journal sequence <num>

Explanation:   The AIJ file supplied was created subsequent to the
               expected AIJ journal.  Usually, this condition occurs
               for the following reasons:  1) an incorrect AIJ file or



                                  16

                                                 RDO Facility Messages





               VMS file "version" was specified, 2) the supplied AIJ
               file was not created for this database, 3) AIJ logging
               was disabled and then later enabled, or 4) a
               transaction is continued in this journal from a
               previous journal.

User Action:   This is a fatal condition; recovery of the AIJ journal
               CANNOT start with this journal.  You MUST start
               recovery with the AIJ journal indicated by the
               preceeding AIJSEQAFT or AIJSEQPRI message.

AIJNXTFIL,     enter the next AIJ file name, or enter return to
               terminate:

Explanation:   Enter the name of another AIJ file to be rolled
               forward.  If no AIJ file name is entered, the
               roll-forward operation is terminated.

User Action:   Enter the name of the next AIJ file to be rolled
               forward.  If you wish to terminate the roll-forward
               operation, simply hit return <CR>.

AIJNXTSEQ,     to continue this AIJ file recovery, the sequence number
               needed will be <num>

Explanation:   This message informs the user what the next AIJ file
               sequence number will be.  AIJ file sequence numbers are
               modified for a variety of reasons (such as, performing
               an AIJ backup, enabling or disabling AIJ logging,
               etc.).

User Action:   No user action is required.  This message is
               informational only.

AIJONEDONE,    AIJ file sequence <num> roll-forward operations
               completed

Explanation:   The roll-forward operations for the AIJ file with the
               indicated sequence number have been successfully
               completed.  Note that in some cases, no transactions
               may have been applied; this is normal.

User Action:   No user action is required.  This message is
               informational only.

AIJOPTRST,     Optimized AIJ journal will not be applied during
               restart

Explanation:   An optimized AIJ was encountered during a restarted AIJ
               roll-forward operation.  Since an optimized AIJ journal
               only contains 1 real transaction, nothing in the AIJ



                                  17

RDO Facility Messages





               journal can be applied if transaction recovery has not
               yet commenced.  Therefore, the AIJ journal is simply
               read but not applied to the database.

User Action:   None.

AIJOPTSUC,     AIJ optimization completed successfully

Explanation:   An AIJ optimization has completed successfully.

User Action:   No user action is required.

AIJOVRINIT,    overwritten AIJ journal <str> has been re-initialized

Explanation:   An "overwritten" AIJ journal has been re-initialized.
               This makes the AIJ journal immediately available for
               future re-use.

User Action:   None.

AIJPREPARE,    <num> of the active transactions prepared but not yet
               committed or aborted

Explanation:   Upon completion of the roll-forward operations for the
               current AIJ file, more than 1 transaction remains
               active AND prepared.  That is, the commit or roll-back
               information either resides in the next AIJ file to be
               processed, or the action can be determined using DECdtm
               upon completion of the recovery operation.

User Action:   No user action is required.  This message is
               informational only.

AIJQUIETPT,    AIJ quiet-point backup required when commit-to-journal
               enabled

Explanation:   You attempted to perform a no-quiet-point back up of an
               after-image journal file when the commit-to-journal
               feature was enabled.

User Action:   Either disable the commit-to-journal feature, or use
               the quiet-point AIJ backup mechanism.

AIJRECBEG,     recovering after-image journal "state" information

Explanation:   When performing a full database restore operation, the
               restore utility attempts to recover the "state"
               information of any after-image journals that were
               available at the time of the backup operation.
               Recovering the after-image journal information permits
               subsequent "automatic" (i.e., hands-off) AIJ-recovery



                                  18

                                                 RDO Facility Messages





               operations.

User Action:   No user action is required.

AIJRECEND,     after-image journal "state" recovery complete

Explanation:   The after-image journal "state" recovery operation has
               completed.

User Action:   No user action is required.

AIJRECESQ,     AIJ roll-forward operations terminated due to sequence
               error

Explanation:   Instead of specifying another AIJ file to be rolled
               forward, the AIJ roll-forward operations were
               prematurely terminated because the AIJ files were out
               of sequence.  In this case, it is possible that one or
               more active transactions were aborted by the system.

User Action:   Redo the RMU/RECOVER with the correct sequence of AIJ
               files, continue rolling forward with the next AIJ in
               the correct sequence, or specify /COMMIT=CONTINUE to
               continue with the next AIJ file after skipping the
               missing AIJ file.

AIJRECTRM,     AIJ roll-forward operations terminated at user request

Explanation:   Instead of specifying another AIJ file to be rolled
               forward, the user specified that AIJ roll-forward
               operations should be prematurely terminated.  In this
               case, it is possible that one or more active
               transactions were aborted by the system.

User Action:   No user action is required.  This message is
               informational only.

AIJREMCUR,     cannot remount the current AIJ journal "<str>"

Explanation:   An attempt was made to remount the AIJ journal
               currently in use.

User Action:   Disable AIJ journaling first, or try to remount the AIJ
               journal when the journal is no longer in use.

AIJREMMOD,     cannot remount AIJ journal "<str>" due to hard data
               loss

Explanation:   An attempt was made to remount an AIJ journal that has
               experienced data loss.  This is not permitted.





                                  19

RDO Facility Messages





User Action:   None.

AIJREMOK,      AIJ journal "<str>" is already fully accessible

Explanation:   An attempt was made to remount an AIJ journal that is
               already fully accessible.

User Action:   None.

AIJROOSEQ,     starting after-image journal sequence number required
               is <num>

Explanation:   The after-image journal sequence number indicated
               corresponds to the first AIJ file that can be rolled
               forward.  If the sequence number of the AIJ file to be
               rolled forward does not exactly match the indicated
               sequence number, no transactions will be applied.

User Action:   No user action is required.  This message is
               informational only.

AIJRSTAVL,     <num> after-image journal(s) available for use

Explanation:   This message indicates the number of after-image
               journals that were successfully restored.  One or more
               of these journals may actually be modified, but all of
               them are valid after-image journals for the database.

User Action:   No user action is required.

AIJRSTBAD,     journal is currently marked inaccessible

Explanation:   The journal that is in the process of being restored
               was marked as being inaccessible.  Consequently, this
               journal cannot be restored.

User Action:   No user action is required.

AIJRSTBEG,     restoring after-image journal "state" information

Explanation:   When performing a full database restore operation, the
               restore utility attempts to restore the "state"
               information of any after-image journals that were
               available at the time of the backup operation.
               Restoring the after-image journal information permits
               subsequent "automatic" (i.e., hands-off) AIJ-recovery
               operations.

User Action:   No user action is required.

AIJRSTDEL,     journal "<str>" filename "<str>" has been removed



                                  20

                                                 RDO Facility Messages





Explanation:   The indicated after-image journal could not be
               successfully restored.  Therefore, the information
               regarding the journal has been removed from the
               database.  Note, however, that the specified filename
               was NOT deleted.

User Action:   No user action is required.

AIJRSTEND,     after-image journal "state" restoration complete

Explanation:   The after-image journal restore operation has
               completed.

User Action:   No user action is required.

AIJRSTINC,     after-image journal sequence numbers are incompatible

Explanation:   The sequence number stored in the header of the
               after-image journal does not correspond to the sequence
               number stored in the database.  Typically, this
               situation occurs if the after-image journal was
               modified or backed up AFTER the database backup was
               made.  As a result, the journal information cannot be
               restored in the database.  However, the on-disk
               after-image journal may be acceptable for subsequent
               roll-forward operations.

User Action:   No user action is required.

AIJRSTJRN,     restoring journal "<str>" information

Explanation:   The specified after-image journal was available when
               the database was originally backed up, and restoration
               of the journal "state" will be attempted.

User Action:   No user action is required.

AIJRSTMOD,     <num> after-image journal(s) marked as "modified"

Explanation:   This message indicates the number of after-image
               journals that were successfully restored, but contain
               data that needs to be backed up.

User Action:   No user action is required.

AIJRSTNMD,     journal has not yet been modified

Explanation:   The indicated after-image journal has not yet been
               modified, and is available for immediate use.  Note
               that at least one unmodified after-image journal is
               required before journaling can be enabled.



                                  21

RDO Facility Messages





User Action:   No user action is required.

AIJRSTROOT,    original database root file "<str>" still exists

Explanation:   An after-image journal cannot be restored if the
               database for which it was originally created still
               exists.

User Action:   No user action is required.

AIJRSTSEQ,     journal sequence number is "<num>"

Explanation:   The indicated after-image journal was successfully
               restored.  This message identifies the sequence number
               of the journal.

User Action:   No user action is required.

AIJRSTSUC,     journal "<str>" successfully restored from file "<str>"

Explanation:   The indicated after-image journal was successfully
               restored.

User Action:   No user action is required.

AIJSEQAFT,     incorrect AIJ file sequence <num> when <num> was
               expected

Explanation:   The AIJ file supplied was created subsequent to the
               expected AIJ file.  Usually, this condition occurs for
               the following reasons:  1) an incorrect AIJ file or VMS
               file "version" was specified, 2) the supplied AIJ file
               was not created for this database, or 3) AIJ logging
               was disabled and then later enabled.

User Action:   The utility will prompt for confirmation that the
               supplied AIJ file is valid.  If AIJ logging was
               disabled and then later enabled without any intervening
               database transaction activity, then confirming the AIJ
               file will permit the roll-forward operation to continue
               applying all transactions contained in the AIJ file.
               Otherwise, the AIJ file should be rejected and the
               correct AIJ file specified.  Should confirmation be
               given for an incorrect AIJ file, no transactions will
               be applied.

AIJSEQBCK,     cannot find an AIJ journal with sequence number <num>

Explanation:   A "by-sequence" after-image journal backup operation
               was attempted with a sequence number that did not
               currently exist for any known AIJ journal.



                                  22

                                                 RDO Facility Messages





User Action:   Specify a valid AIJ sequence number, or perform a full
               AIJ backup by not specifying the "by-sequence" command
               qualifier.

AIJSEQPRI,     AIJ file sequence number <num> created prior to
               expected sequence <num>

Explanation:   The after-image journal supplied was created prior to
               the expected AIJ file.  Usually, this condition occurs
               for the following reasons:  1) an incorrect AIJ file or
               VMS file "version" was specified, 2) the supplied AIJ
               file was not created for this database, or 3) a
               database backup was performed subsequent to the AIJ
               backup.

User Action:   No user action is required.  This message is
               informational only.  The AIJ roll-forward operation
               will continue to completion, although no transactions
               will be applied from the AIJ file.

AIJSIGNATURE,  standby database AIJ signature does not match master
               database

Explanation:   The number of AIJ journal slots ("reserved"), or the
               specific journal allocation sizes, are not identical on
               both the master and standby databases.

User Action:   Make sure both the master and standby database AIJ
               journal configurations are identical.  Ensure that the
               AIJ journal device "cluster size" is identical on both
               the master and standby databases.

AIJTERMINATE,  inaccessible AIJ file forced image exit to protect
               database

Explanation:   To maintain the integrity of the database, the database
               system has forced your image to exit.  An error has
               been encountered with one or more of the after-image
               journals that could jeopardize your ability to recover
               the database should a it become necessary to restore
               and recover the database.  Until the journaling problem
               has been remedied no further updates to the database
               are allowed.

User Action:   The RMU or DBO /DUMP/HEADER=JOURNAL command will
               display the current state of the journals.  Various
               remedies are possible, depending on the error
               encountered.  Contact Oracle Support if you have
               questions on how to fix the problem.  Typically,
               disabling and re-enabling journaling is the simplest
               way to restore operation of the database.  This can be



                                  23

RDO Facility Messages





               done using the DBO or RMU SET AFTER command, or from
               interactive SQL.  After the journaling problem has been
               resolved a full database backup must be done to ensure
               that the database can be restored and recovered
               successfully in the future.

AIJVNOSYNC,    AIJ file <str> synchronized with database

Explanation:   When recovering a database for which AIJ journaling was
               enabled, it may be necessary to synchronize information
               in the AIJ file with information in the database root
               file.  This is necessary to ensure that subsequent AIJ
               recovery operations are successful.

User Action:   No user action is required.  This message is
               informational only.

ALSACTIVE,     Database replication is active

Explanation:   Certain database operations, such as terminating the
               AIJ Log Server, cannot be performed while database
               replication is active.

User Action:   Terminate database replication and re-attempt the
               operation.

ALSNACTIVE,    Database replication is not active

Explanation:   Database replication is not active for the specified
               database.

User Action:   Verify that the database is being replicated.

ALSNAVAIL,     "Hot Standby" not available or improperly installed

Explanation:   "Hot Standby" cannot be started because it has not been
               installed.

User Action:   Make sure the "Hot Standby" component has been properly
               installed.

ALSNBEGUN,     database replication has not previously been started

Explanation:   Database replication has not yet been started for this
               database.

User Action:   You specified the replication-start command without
               identifying the master or standby database.  This type
               of command can only be used when database replication
               has been previously started.





                                  24

                                                 RDO Facility Messages





ALSNOOUT,      AIJ Log Server does not have an output file

Explanation:   The AIJ Log Server process does not have an output file
               associated with it.

User Action:   Use the /OUTPUT qualifier to specify an output filename
               when the AIJ Log Server process is started.

ALSNRUNNING,   AIJ Log Server process is not active

Explanation:   The AIJ Log Server process is not running on the
               current node.

User Action:   Verify that the AIJ Log Server has been started.

ALSRUNNING,    AIJ Log Server process is already running

Explanation:   The AIJ Log Server process has already been started on
               the current node.

User Action:   No action is required.

AMB_KEYWORD,   ambiguous keyword abbreviation

Explanation:   You used an ambiguous abbreviation.

User Action:   Specify the entire keyword.

ANODBHAND,     another database has been invoked with the same
               db_handle name <str>

Explanation:   You specified in the INVOKE statement the same name for
               the db_handle as in a previous INVOKE statement.

User Action:   Reenter the INVOKE statement with a different db_handle
               name.

ANYNOTALL,     ANY and UNIQUE are not allowed in a VALID IF expression

Explanation:   You entered a VALID IF expression containing something
               other than an operator, literal value, or field name.

User Action:   Check the Oracle Rdb Reference Manual for details on
               VALID IF.

AREABUSY,      usage of storage area <str> conflicts with a co-user

Explanation:   You attempted to ready an area that is already being
               accessed by another user, and that usage mode is
               incompatible with the usage mode you requested.





                                  25

RDO Facility Messages





User Action:   Wait until the storage area you requested is available,
               and try again, or ready the area with the WAIT option.

AREAUNTILIGN,  /UNTIL qualifier ignored when /AREA qualifier specified

Explanation:   The /UNTIL qualifier to the AIJ roll-forward utility is
               ignored when the /AREA qualifier is also specified.

User Action:   None necessary.

AREA_CORRUPT,  storage area <str> is corrupt

Explanation:   The storage area has been corrupted by an abnormal
               termination of a BATCH UPDATE run unit.  It cannot be
               readied.

User Action:   Either try to fix the problem by verifying the area and
               then altering the corrupt pages or reload/restore the
               area.

AREA_DELETED,  area is not active or was previously deleted

Explanation:   An attempt was made to ready an area which does not
               exist.

AREA_INCONSIST, storage area <str> is inconsistent

Explanation:   The storage area has been marked inconsistent with the
               rest of the database.  It cannot be readied.

User Action:   Recover the area to make it consistent.

AREA_RESTRUCT, storage area <str> is under restructure

Explanation:   An attempt was made to ready an area that is either
               presently being or in the recent past has been
               restructured.

User Action:   See your DBA to have the areas released.

ARIEXPEXP,     an arithmetic expression was expected

Explanation:   An arithmetic expression was expected in the current
               context.  A Boolean expression was found.

User Action:   You must use an arithmetic expression in this context.

ASCEIGNOR,     ASCENDING/DESCENDING keywords are ignored for a hashed
               index

Explanation:   The ASCENDING and DESCENDING keywords are ignored when



                                  26

                                                 RDO Facility Messages





               they are specified for a hashed index.

User Action:   Do not specify the ASCENDING or DESCENDING keywords for
               a hashed index.

ATTMISSING,    invalid or missing attributes

Explanation:   Internal error -- a required attribute (such as the
               data type in a GLOBAL FIELD clump) is missing.

User Action:   Contact your Oracle support representative for
               assistance.

BACKCONV,      please backup your database and use the RMU/CONVERT
               command

Explanation:   The database has an obsolete root file and must be
               converted.

User Action:   The database must be converted.  First make a backup
               copy.  Then use the RMU/CONVERT command.

BADADJLOCKGRAN, ADJUSTABLE LOCK GRANULARITY clause is not allowed in
               the DEFINE TRANSFER statment.

Explanation:   You have specified an ADJUSTABLE LOCK GRANULARITY
               clause as an attribute for the target database in a
               DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement without the
               ADJUSTABLE LOCK GRANULARITY clause.

BADAIJACE,     after-image journal is electronic cache

Explanation:   You have attempted to use the AIJ Cache for Electronic
               disk for an operation which is not supported.  For
               instance, you may have tried to use the electronic
               cache as the roll-forward journal, which is incorrect.

User Action:   Do not use the AIJ Cache for Electronic disk for
               day-to-day operations.  Use the disk-based after-image
               journals for all roll-forward or AIJ operations.

BADAIJBCK,     previous AIJ backup did not complete

Explanation:   It appears that the previous AIJ file backup process,
               which was started on the indicated date/time, either
               failed or was prematurely terminated by the user.

User Action:   No user action required.  The current AIJ backup will
               backup the complete AIJ file to ensure there is no loss



                                  27

RDO Facility Messages





               of transactions.  The AIJ file created by the failed
               backup utility MUST be preserved; DO NOT discard the
               AIJ backup file created by the failed backup utility.
               Even though the AIJ backup failed, the AIJ backup file
               must be used for successful roll-forward operations.

BADAIJFILE,    illegal after-image journal format or journal
               incorrectly mounted

Explanation:   The file you specified does not appear to be an
               after-image journal file.  For example, when performing
               an AIJ roll-forward operation using an after-image
               journal on a magnetic tape, this problem will occur if
               the tape is incorrectly mounted.

User Action:   Check the file name and try again.  Verify that a
               magnetic tape was correctly mounted.

BADAIJSEQ,     AIJ file is incorrect for roll-forward operations

Explanation:   The specified AIJ file is not the correct file to be
               rolled-forward.  Usually, this condition occurs for the
               following reasons:  1) an incorrect AIJ file or VMS
               file "version" was specified, 2) the supplied AIJ file
               was not created for this database, or 3) AIJ logging
               was disabled and then later enabled.

User Action:   No user action is required.  This message is
               informational only.

BADAIJUNTIL,   date specified by /UNTIL (<time>) has not yet been
               reached

Explanation:   The date and time specified by the /UNTIL command
               qualifier had not yet been reached when after-image
               journal roll-forward operations were completed.

User Action:   Another after-image journal, if any, might have to be
               rolled forward to ensure that all transactions have
               been applied up to the specified date and time.  If no
               more AIJ files are available, the AIJ roll-forward
               operations are complete.

BADAIJVER,     after-image journal version is incompatible with the
               runtime system

Explanation:   Your after-image journal file was created with an
               incompatible version of the software.

User Action:   Your after-image journal file cannot be used with the
               version of the software you have installed on your



                                  28

                                                 RDO Facility Messages





               machine.  Make sure you are using the correct AIJ
               journal, or if "multi-version" software is installed,
               make sure you are using the correct software version.

BADASCTOID,    "<str>" is not a valid user identifier

Explanation:   An error occurred when the rights database was accessed
               to translate an identifier name to a binary identifier.

User Action:   See the secondary error message, and supply a valid
               user identifier.

BADBLOB,       unable to IMPORT segmented string

Explanation:   Error from Rdb$CREATE_SEGMENTED_STRING.  See the
               following message for more information.

User Action:   If the nature of the problem is not obvious, then
               contact your Oracle support representative for
               assistance.

BADBNDPRM,     bad bind parameter <str> value "<str>"

Explanation:   The logical bind parameter value is invalid.

User Action:   See the secondary error message for more information.

BADBNDPRM0,    bad bind parameter

Explanation:   A logical bind parameter value is invalid.

User Action:   See the secondary error message for more information.
               Because of unfortunate logistics, no further
               information is available at this point, check the
               Monitor log for more info.

BADBOUNDS,     value not in range <num> to <num>

Explanation:   The value of the translated logical name is not in the
               range of acceptable values.

User Action:   Delete the logical name, or redefine it with a value in
               the acceptable range.

BADBUFSIZ,     buffer size (<num>) is too small for largest page size
               (<num>)

Explanation:   Specified buffer size is too small to hold even one
               page from the storage area with the largest page size.

BADCCHNAM,     record cache "<str>" does not exist



                                  29

RDO Facility Messages





Explanation:   The specified record cache is not defined in the
               database.

User Action:   Please specify a valid record cache name.

BADCLUMP,      invalid clump type encountered

Explanation:   Internal error - bad data in the Oracle Rdb interchange
               file (RBR).

User Action:   Contact your Oracle support representative for
               assistance.

BADCORATT,     invalid core attribute <num>, <num> in RBR file

Explanation:   Internal error - bad data in the Oracle Rdb interchange
               file (RBR).

User Action:   Contact your Oracle support representative for
               assistance.

BADDATDEF,     illegal default format for date string

Explanation:   The logical name, SYS$DATE_INPUT, represents the
               default format for a date string.  It is a
               three-character field (MDY,DMY, etc.), in which M =
               month, D = day, and Y = year.

User Action:   Redefine the logical name with a legal date-string
               format.

BADDBNAME,     can't find database root <str>

Explanation:   The database root file you specified could not be
               accessed.

User Action:   Examine the associated messages to determine the reason
               for failure.

BADDTFMT,      date or time format is not set up correctly

Explanation:   You entered a SHOW DATE_FORMAT command, but
               LIB$DT_FORMAT is not properly defined.

User Action:   Check the definition of LIB$DT_FORMAT.  If it is a
               process logical, it should be changed.  If it is a
               group or system logical, contact your system manager to
               change it.

BADEPILOGUE,   only one epilogue file clause can be specified per
               transfer



                                  30

                                                 RDO Facility Messages





Explanation:   You specified more than one epilogue file clause in the
               DEFINE TRANSFER statement.  This is not permitted.

User Action:   Reenter the DEFINE TRANSFER statement, specifying only
               one EPILOGUE IS or NOEPILOGUE clause.

BADFILEVER,    incompatible RBR file type

Explanation:   This version of RDO cannot import a database from this
               Oracle Rdb interchange file (RBR).

User Action:   Use a version of RDO that corresponds to the version of
               RDO that created this file.

BADFILTYP,     database file must have extension "<str>"

Explanation:   All database files must have the specified file type.

User Action:   You might be attempting to access a non-database file.
               If not, rename or copy the database file to have the
               proper type.

BADFLDTYP,     field <str> of target relation <str> has different
               field types

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have entered MOVE RELATION clauses with
               the same target relation name and specified fields with
               the same names but of different data types in the
               source databases.

User Action:   Reenter the DEFINE TRANSFER statement by specifying
               fields of the same datatype in all the MOVE RELATION
               clauses with the same target relation.

BADIDXMAP,     fields specified for partitioning index do not agree
               with fields for index

Explanation:   The user named fields to partition an index but in an
               incorrect order, or specified too many fields.

User Action:   Review the DML statement and specify it again.

BADINCONSISPAG, inconsistent page is corrupt -- not found in Corrupt
               Page Table

Explanation:   An attempt was made to fetch an inconsistent page.
               Furthermore, the page is probably corrupt, because it
               is not logged in the Corrupt Page Table as an
               inconsistent page.  This page cannot be accessed until
               it is consistent.



                                  31

RDO Facility Messages





User Action:   Take the proper action to make the page consistent.
               For example, perform a RESTORE/RECOVER operation for a
               data or AIP page, or a REPAIR operation for a SPAM or
               ABM page.

BADINTERVAL,   INTERVAL clause is not allowed in the DEFINE TRANSFER
               statement.

Explanation:   You have specified an INTERVAL clause as an attribute
               for the target database in a DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement without the
               INTERVAL clause.

BADLOGFILE,    only one log file clause can be specified per transfer

Explanation:   You specified more than one log file clause in the
               DEFINE TRANSFER statement.  This is not permitted.

User Action:   Reenter the DEFINE TRANSFER statement, specifying only
               one LOG FILE IS or NOLOG clause.

BADLOGNAM,     invalid log file name

Explanation:   You entered an invalid log file name.

User Action:   Refer to the explanation in the user action section of
               the secondary error message.

BADMETNAM,     metadata names must end in A - Z or 0 - 9

Explanation:   The name given in a DML or DDL statement ended in a
               dollar sign or an underscore.  These symbols are not
               allowed.

User Action:   Specify a valid name.

BADMVIEWFLD,   field <str> of relation <str> must be moved for view
               <str>

Explanation:   You attempted to transfer a view without transferring a
               field to which the view refers.  You must also
               explicitly transfer in the DEFINE TRANSFER statement
               all relevant fields of relations to which the view
               refers.

User Action:   Reenter the DEFINE TRANSFER statement, adding the
               required field to the appropriate MOVE RELATION clause.

BADMVIEWREL,   underlying relation <str> of view <str> must also be
               moved



                                  32

                                                 RDO Facility Messages





Explanation:   You attempted to transfer a view without transferring
               the relations to which the view refers.  You must
               explicitly transfer the relations to which the view
               refers in the DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement adding the
               required MOVE RELATION clause.

BADMVIEWVEW,   underlying view <str> of view <str> must also be moved

Explanation:   You attempted to transfer a view without transferring
               other views that underlie the view you want to
               transfer.  You must explicitly transfer the views to
               which the view refers in the DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement adding the
               required views to the MOVE VIEW clause.

BADMVRELS,     move-relations-clause is allowed only once in DEFINE
               TRANSFER

Explanation:   You specified more than one move-relations-clause in a
               DEFINE TRANSFER statement.  Possibly you did not
               separate the MOVE RELATION clauses with semicolons.

User Action:   When you use a DEFINE TRANSFER statement, group all the
               MOVE RELATION clauses together and separate them with
               semicolons.

BADMVVIEWS,    move-views-clause is allowed only once in DEFINE
               TRANSFER

Explanation:   You entered more than one move-views-clause in a DEFINE
               TRANSFER statement.  Only one move-views-clause is
               allowed in a DEFINE TRANSFER statement.

User Action:   Combine all MOVE VIEWS clauses into one list and
               separate the view names with commas.

BADPAGEFORMAT, PAGE FORMAT clause is not allowed in the DEFINE
               TRANSFER statement.

Explanation:   You have specified a PAGE FORMAT clause as an attribute
               for the target database in a DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement without the PAGE
               FORMAT clause.

BADPAGNUM,     page <num> is out of valid range (1:<num>) for physical
               area <num>





                                  33

RDO Facility Messages





Explanation:   The page number requested does not fall within the
               range of pages that exist in the specified physical
               storage area.  Note that a page number of 4294967295 is
               equal to -1.

User Action:   Contact your Oracle support representative for
               assistance.

BADPAGRED,     read requesting physical page <num>:<num> returned page
               <num>:<num>

Explanation:   The area or page numbers stored on the database page do
               not match the area or page numbers of the DBKEY
               requested to be read from the database.  This usually
               is caused by a hardware problem.

User Action:  

BADPAGSIZ,     page size (<num>) conflicts with existing areas
               (<num>..<num>)

Explanation:   An attempt was made to define a new storage area with a
               page size that conflicts with other areas.

User Action:   Define the area with a page size that is within the
               range specified.

BADPARAM,      <str> (<num>) is out of valid range (<num>..<num>)

Explanation:   An illegal parameter was specified during creation or
               modification of the database.

User Action:   Examine your command line for illegal parameter values.

BADPROLOGUE,   only one prologue file clause can be specified per
               transfer

Explanation:   You specified more than one prologue file clause in the
               DEFINE TRANSFER statement.  This is not permitted.

User Action:   Reenter the DEFINE TRANSFER statement, specifying only
               one PROLOGUE IS or NOPROLOGUE clause.

BADRECBUF,     NUMBER OF RECOVERY BUFFERS clause is not allowed in the
               DEFINE TRANSFER statement.

Explanation:   You have specified the NUMBER OF RECOVERY BUFFERS
               clause as an attribute for the target database in a
               DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement without the



                                  34

                                                 RDO Facility Messages





               NUMBER OF RECOVERY BUFFERS clause.

BADROLMVFLD,   MOVE RELATION clauses of target relation <str> have
               different fields

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have entered a MOVE RELATION clauses with
               the same target relation name but specified a different
               set of fields in each clause.

User Action:   Reenter the DEFINE TRANSFER statement by specifying the
               same set of fields in all the MOVE RELATION clauses
               with the same target relation.

BADROOTMATCH,  root file "<str>" no longer has its original name
               "<str>"

Explanation:   The current root file name does not match the name used
               when the root file was created.  This could happen if
               you copied or renamed the root file, or if the file was
               created using a concealed logical device name and that
               logical name is no longer defined.

User Action:   Rename or copy the root file back to its original name
               or location, or redefine the necessary concealed
               logical device name in the system logical name table.

BADRUJVER,     run-unit journal version is incompatible with the
               runtime system

Explanation:   Your run-unit journal file was created with an
               incompatible version of the software.

User Action:   Your run-unit journal file cannot be used with the
               version of the software you have installed on your
               machine.  Make sure you are using the correct RUJ
               journal, or if "multi-version" software is installed,
               make sure you are using the correct software version.

BADSNAPFILENAME, SNAPSHOT_FILENAME clause is not allowed in the DEFINE
               TRANSFER statement.

Explanation:   You have specified a SNAPSHOT_FILENAME clause as an
               attribute for the target database in a DEFINE TRANSFER
               statement.

User Action:   Reenter the DEFINE TRANSFER statement without the
               SNAPSHOT_FILENAME clause.

BADSPAMINT,    spam interval (<num>) is too large for page size (<num>
               block(s))



                                  35

RDO Facility Messages





Explanation:   The SPAM interval is too large for the specified page
               size.

User Action:   Reduce the SPAM interval or increase the page size.

BADSPECATR,    attribute is incorrectly specified

Explanation:   You specified a field attribute that does not make
               sense.

User Action:   Check the documentation and specify the data definition
               statement again.

BADSTATVER,    statistics input file version is incompatible with the
               software version

Explanation:   The binary statistics file specified by the /INPUT
               qualifier was created with an incompatible version of
               the software.

User Action:   The binary statistics file cannot be used with the
               version of the software you have installed on your
               machine.

BADTHRESHOLD,  THRESHOLDS clause is not allowed in the DEFINE TRANSFER
               statement.

Explanation:   You have specified a THRESHOLDS clause as an attribute
               for the target database in a DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement without the
               THRESHOLDS clause.

BADVAXCLUSNODES, NUMBER OF VAXCLUSTER NODES clause is not allowed in
               the DEFINE TRANSFER statement.

Explanation:   You have specified a NUMBER OF VAXCLUSTER NODES clause
               as an attribute for the target database in a DEFINE
               TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement without the
               NUMBER OF VAXCLUSTER NODES clause.

BAD_END_NAME,  the name in END <str> does not match item name <str>

Explanation:   The name given in an END <name> <structure> (for
               example, END name RELATION) does not match the name
               given to the item (DEFINE RELATION name).

User Action:   Specify the same item name.





                                  36

                                                 RDO Facility Messages





BAD_NAME,      identifiers and names may not exceed 31 characters in
               length

Explanation:   The name given in a DML/DDL statement was longer than
               the permitted limit.

User Action:   For data definition statements, specify a shorter name.
               For data manipulation statements, consult your database
               design specifications to find the correct name.

BDDATRANG,     day, month, or year field in date string out of range

Explanation:   The month field must be between 1 and 12 inclusive.
               The day field must be between 1 and 31 inclusive.  The
               year field must be between 0 and 3000 inclusive.

User Action:   Re-enter the DATE data item with the error corrected.

BKUPEMPTYAIJ,  after-image journal file is empty

Explanation:   An attempt was made to back up an empty after-image
               journal file.

User Action:   Be sure the correct after-image journal file was
               specified.

BOOEXPEXP,     a Boolean expression was expected

Explanation:   Either a numeric or string expression was found where a
               Boolean expression was expected.

User Action:   You must use a Boolean expression in this context.

BOUND,         multiple binds are not allowed

Explanation:   You are already bound to a database.  You can only be
               bound to one database at a time for a given stream.

User Action:   You can execute an UNBIND statement and try the BIND
               again, or use the multiple stream feature to bind to a
               database on another stream.

BREAK,         internal system failure -- database session attach
               information not found

Explanation:   The database session information cannot be found; this
               may be indicative of a more serious problem.

User Action:   Contact your Oracle support representative for
               assistance.





                                  37

RDO Facility Messages





BUFTOOSML,     buffer size (<num>) is smaller than largest page
               (<num>)

Explanation:   The buffer size must be large enough to accommodate the
               largest page size within the database.

User Action:   Specify a buffer size at least as large as the message
               indicates.

BUGCHECK,      fatal, unexpected error detected

Explanation:   A fatal, unexpected error was detected by the database
               management system.

User Action:   Contact your Oracle support representative for
               assistance.

BUGCHK,        there has been a fatal error; please contact your
               Oracle support representative; no dump was produced

Explanation:   A fatal error has occurred.

User Action:   Contact your Oracle support representative for
               assistance.  You will need to provide information about
               the circumstances under which the bug occurred.  Note
               that RDO$_BUGCHECKs do not produce dumps as
               RDB$_BUGCHECKs do.

BUGCHKDMP,     generating bugcheck dump file <str>

Explanation:   The database management system has detected a fatal,
               unexpected error, and is writing a bugcheck dump file
               with the specified file name.

User Action:   Please send this bugcheck dump file to your software
               specialist, along with any other related programs or
               data.

CABORT,        user entered Control-C to abort command

Explanation:   You entered a CTRL/C to abort the current command.

User Action:   None.

CACHEINUSE,    record cache <str> is still referenced by storage area
               <str>

Explanation:   Unable to delete record cache because it is still being
               referenced by one or more storage areas.

User Action:   Remove the record cache from the affected storage areas



                                  38

                                                 RDO Facility Messages





               first.

CANNOTCLSRCSGLX, RCS is active on this node and the database is also
               open on another node

Explanation:   The Record Cache Server (RCS) process is active on this
               node and another node has this database open.  The
               database must be closed on all other nodes before it
               can be closed on this node.

CANTADDLAREA,  Cannot create logical area <str>

Explanation:   Too many logical areas have been created.  Can't create
               a new one.

User Action:   Do not attempt to create so many logical areas.
               Redesign.

CANTASSMBX,    error assigning a channel to a mailbox

Explanation:   An error occurred when you attempted to assign a
               channel to a VMS mailbox.

User Action:   Examine the secondary message for more information.

CANTBACKUP,    BACKUP command may not be issued, use RDO EXPORT

Explanation:   The BACKUP command is no longer available in RDO.

User Action:   Use the RDO EXPORT command, which provides the same
               functionality.

CANTBINDRT,    error mapping database root file

Explanation:   An error occurred during mapping to the database root
               file.

User Action:   Examine the associated messages to determine the reason
               for failure.

CANTCLOSEDB,   database could not be closed as requested

Explanation:   The database monitor detected an error while attempting
               to close the database you specified.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCONVERT,   CONVERT command may not be issued, use RMU/CONVERT





                                  39

RDO Facility Messages





Explanation:   The CONVERT command is no longer available in RDO.

User Action:   Use the RMU/CONVERT command which provides the same
               functionality.

CANTCREABS,    error creating AIJ backup server process

Explanation:   An error occurred when you attempted to create a
               detached AIJ backup server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCREALS,    error creating AIJ Log Server process

Explanation:   An error occurred when you attempted to create a
               detached AIJ Log Server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCREBOB,    error creating Buffer Object

Explanation:   An error occurred when you attempted to create an
               OpenVMS buffer object.

User Action:   Examine the secondary message(s) for more information.

CANTCREDBR,    error creating database recovery process

Explanation:   An error occurred when you attempted to create a
               detached database recovery process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCREGBL,    error creating and mapping database global section

Explanation:   An error occurred when you attempted to create a map to
               the database global section.

User Action:   Examine the secondary message(s) for more information.

CANTCRELCS,    error creating AIJ Log Catch-Up Server process

Explanation:   An error occurred when you attempted to create a
               detached AIJ Log Catch-Up Server process.





                                  40

                                                 RDO Facility Messages





User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCRELRS,    error creating AIJ Log Roll-Forward Server process

Explanation:   An error occurred when you attempted to create a
               detached AIJ Log Roll-Forward Server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCREMBX,    cannot create mailbox

Explanation:   An error occurred when you attempted to create a
               mailbox.  Mailboxes are used for interprocess
               communication by the database management system.

User Action:   Examine the associated messages to determine the reason
               for failure.  Usually, you will have to change one of
               your quotas (most likely, the buffered I/O-byte count
               quota or the open-file quota).

CANTCREMON,    unable to start database monitor process

Explanation:   An error occurred when you attempted to start the
               database monitor process.  This is a detached process.

User Action:   Examine the secondary message(s) to determine the
               reason for the failure.

CANTCRERCS,    error creating Record Cache Server process

Explanation:   An error occurred when you attempted to create a
               detached Record Cache Server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTCREVLM,    error creating or mapping Very Large Memory region

Explanation:   An error occurred when you attempted to create or map a
               database Very Large Memory (VLM) region.

User Action:   Examine the secondary message(s) for more information.

CANTCVRT,      cannot convert this database version

Explanation:   Your database is not recognized as one which can be



                                  41

RDO Facility Messages





               converted.

User Action:   Either the database being converted has already been
               converted, is too old to be converted, or is not a
               database.  You should check your backups.

CANTDELETE,    error deleting "<str>"

Explanation:   An error occurred when you attempted to delete the
               indicated file.  You must be able to change the
               protection on a file in order to delete it.

User Action:   Examine the associated messages to determine the reason
               for failure.

CANTFINDAIJ,   cannot locate standby AIJ journal to match master
               database

Explanation:   A master database AIJ journal cannot be located on the
               standby database.

User Action:   You may select an AIJ journal using either the AIJ name
               or the default or current AIJ file specification.  The
               list of valid AIJ journals can be obtained by dumping
               the database header information.

CANTFINDLAREA, cannot locate logical area <num> in area inventory page
               list

Explanation:   This is an internal error.  A request was made to find
               logical area information for the specified logical area
               number but no active AIP entries could be found for
               that logical area number.

User Action:   Contact your Oracle support representative for
               assistance.

CANTLCKTRM,    database monitor error establishing termination lock

Explanation:   The database monitor was unable to assert a request on
               the user's image termination lock.  The user's image
               might already have terminated before the monitor
               received the request.

User Action:   Examine the secondary message(s) for more information.

CANTMAPSHMEM,  error mapping to shared memory "<str>"

Explanation:   An error occurred while mapping to a database shared
               memory section.





                                  42

                                                 RDO Facility Messages





User Action:   Examine the associated messages to determine the reason
               for failure.

CANTOPENDB,    database could not be opened as requested

Explanation:   The database monitor detected an error while attempting
               to open the database you specified.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTOPENIN,    error opening input file <str>

Explanation:   An error occurred during opening of the input file.

User Action:   Examine the associated messages to determine the reason
               for failure.

CANTOPNALSOUT, error opening AIJ Log Server output file

Explanation:   An error occurred during opening of the AIJ Log Server
               output file.

User Action:   Examine the secondary message for more information.

CANTOPNLCSOUT, error opening AIJ Log Catch-Up Server output file

Explanation:   An error occurred during opening of the AIJ Log
               Catch-Up Server output file.

User Action:   Examine the secondary message for more information.

CANTOPNLRSOUT, error opening AIJ Log Roll-Forward Server output file

Explanation:   An error occurred during opening of the AIJ Log
               Roll-Forward Server output file.

User Action:   Examine the secondary message for more information.

CANTOPNLSSOUT, error opening AIJ log server output file

Explanation:   An error occurred during opening of log server output
               file.

User Action:   Examine the secondary message for more information.

CANTQIOMBX,    unable to send mail to a mailbox

Explanation:   An error occurred when you attempted to send mail to a
               mailbox.



                                  43

RDO Facility Messages





User Action:   Examine the secondary message(s) to determine the
               reason for the failure.

CANTREADDB,    error opening or reading database file

Explanation:   An error occurred when you attempted to open or read
               from the database file.

User Action:   Examine the secondary message(s) for more information.

CANTREADDBS,   error reading pages <num>:<num>-<num>

Explanation:   An error occurred when you attempted to read one or
               more database pages.  The message indicates the
               storage-area ID number and the page numbers of the
               first and last pages being read.

User Action:   Examine the associated messages to determine the reason
               for failure.

CANTRESTORE,   RESTORE command may not be issued, use RDO IMPORT

Explanation:   The RESTORE command is no longer available in RDO.

User Action:   Use the RDO IMPORT command, which provides the same
               functionality.

CANTRESUMEABS, error resuming AIJ backup operations

Explanation:   An error occurred when you attempted to resume
               after-image journal backup operations.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTRESUMELRS, error resuming AIJ Log Roll-Forward Server process

Explanation:   An error occurred when you attempted to resume the
               detached AIJ Log Roll-Forward Server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSNAP,      can't ready storage area <str> for snapshots

Explanation:   Snapshots were last enabled for this area by a
               transaction that had not committed before the snapshot
               started.  Information to materialize the snapshot is
               not present.



                                  44

                                                 RDO Facility Messages





User Action:   Restart the snapshot transaction.  If failure of a
               snapshot transaction is critical, you should ready all
               areas before doing any retrievals.

CANTSPAWN,     error spawning sub-process

Explanation:   An error occurred when you attempted to spawn a
               sub-process.

User Action:   Examine the secondary message for more information.

CANTSPOOL,     SPOOL command may not be issued, use
               RMU/BACKUP/AFTER_JOURNAL

Explanation:   The SPOOL command is no longer available in RDO.

User Action:   Use the RMU/BACKUP/AFTER_JOURNAL command, which
               provides the same functionality.

CANTSTARTABS,  error starting AIJ backup server process

Explanation:   An error occurred when you attempted to start a
               detached AIJ backup server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTARTALS,  error starting AIJ Log Server process

Explanation:   An error occurred when you attempted to start a
               detached AIJ Log Server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTARTLCS,  error starting AIJ Log Catch-Up Server process

Explanation:   An error occurred when you attempted to start the
               detached AIJ Log Catch-Up Server process on the
               replicated database.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTARTLRS,  error starting AIJ Log Roll-Forward Server process

Explanation:   An error occurred when you attempted to start the
               detached AIJ Log Roll-Forward Server process on the



                                  45

RDO Facility Messages





               replicated database.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTARTLSS,  error starting "Hot Standby" Server process

Explanation:   An error occurred while attempting to start the
               detached "Hot Standby" Server process on the replicated
               database.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTARTRCS,  error starting Record Cache Server process

Explanation:   An error occurred while attempting to start the
               detached Record Cache Server process on the indicated
               database.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTARTTX,   cannot start transaction

Explanation:   Cannot start a transaction as requested.

User Action:   Examine the secondary message for more information.

CANTSTOPALS,   error stopping AIJ Log Server process

Explanation:   An error occurred when you attempted to stop a detached
               AIJ log-server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTOPLSS,   error stopping "Hot Standby" Server process

Explanation:   An error occurred when you attempted to stop the
               detached "Hot Standby" Server process(es).

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSTOPRCS,   error stopping Record Cache Server process



                                  46

                                                 RDO Facility Messages





Explanation:   An error occurred when you attempted to stop a detached
               Record Cache Server process.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSUSPENDABS, error suspending AIJ backup operations

Explanation:   An error occurred when you attempted to suspend
               after-image journal backup operations.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTSUSPENDLRS, error suspending AIJ Log Roll-Forward Server process

Explanation:   An error occurred when you attempted to suspend the
               detached AIJ Log Roll-Forward Server process on the
               replicated database.

User Action:   Examine the secondary message(s) or look in the
               database monitor log file (SYS$SYSTEM:*MON.LOG) for
               more information.

CANTWRITEDBS,  error writing pages <num>:<num>-<num>

Explanation:   An error occurred when you attempted to write one or
               more database pages.  The message indicates the
               storage-area ID number and the page numbers of the
               first and last pages being written.

User Action:   Examine the associated messages to determine the reason
               for failure.

CAPTIVEACCT,   captive account -- no DCL commands can be issued

Explanation:   An attempt was made to issue a DCL command from a
               captive account.

User Action:   Do not issue DCL commands from captive accounts or
               modify the account flags so that it's possible to spawn
               DCL commands.

CCHDEVDIR,     Cache directory "<str>" does not include a
               device/directory

Explanation:   The specified record cache directory does not include a
               device and directory.





                                  47

RDO Facility Messages





User Action:   Include a device and directory specification.

CDDDEFERR,     unable to update or read the CDD default path

Explanation:   An error occurred updating or reading the CDD default
               path.

User Action:   Check the CDD message that follows for more details.

CDDERR,        error occurred during CDD signin, CDD will not be used

Explanation:   An error occurred during signin.  Refer to the CDD
               manual for more information.

User Action:   Check the CDD message that follows for more details.

CHDBNOPARAM,   command CHANGE DATABASE included no parameters

Explanation:   User entered CHANGE DATABASE {PATH | NAME} db_name
               without entering any parameters to change.

User Action:   Specify what you intend to change on a CHANGE DATABASE
               command.

CHECKSUM,      checksum error - computed <num>, page contained <num>

Explanation:   The computed checksum for the database page disagreed
               with the checksum actually stored on the page.  This
               usually is caused by a hardware problem.

User Action:   None.

CHGINDMAP,     This index was previously specified with a STORE
               clause, continue?  [N]

Explanation:   You are specifying a CHANGE INDEX statement without a
               STORE clause, which places the index into the
               RDB$SYSTEM storage area.  The index was previously
               specified as being stored in a different area.  RDO is
               confirming that you want the index placed in the
               RDB$SYSTEM storage area.

User Action:   An affirmative reply (Y or YES) causes the operation to
               continue.  A negative reply (a carriage return, N, or
               NO) terminates the operation.

CHGINDMAPSTP,  terminating operation at user's request

Explanation:   See above.

User Action:   None.



                                  48

                                                 RDO Facility Messages





CLMCIRCAIJ,    Continuous LogMiner requires fixed-size circular
               after-image journals

Explanation:   The Continuous LogMiner feature requires that
               fixed-size circular after-image journals are used.

User Action:   If Continuous LogMiner features are required the
               database must be re-configured to enable fixed-size
               circular after-image journals.

CLMNOENABLED,  Continuous LogMiner has not yet been enabled

Explanation:   The Continuous LogMiner feature has not been enabled on
               this database.

User Action:   If Continuous LogMiner features are required, The
               Continuous LogMiner should be enabled.

CLOSERR,       error detected when closing RBR file

Explanation:   See the message that follows for details.

User Action:   In the absence of other error messages, the database
               has probably been imported successfully.

CMDINTR,       this statement is not allowed in a transaction

Explanation:   You entered a statement that cannot be used when a
               transaction is outstanding.

User Action:   Commit or rollback the transaction and try the
               statement again.

CMPBYINVW,     view <str> cannot be transferred

Explanation:   In a DEFINE TRANSFER statement, you are attempting to
               move a view which references a COMPUTED_BY field which
               contains an unsupported value expression.

User Action:   Reenter the DEFINE TRANSFER statement and omit the view
               that contains the COMPUTED_BY field that uses the
               unsupported value expression.  Refer to the DEFINE
               TRANSFER statement in the Replication Option for Rdb
               Handbook for information on what value expressions are
               supported for a COMPUTED_BY field.

CNTSPNSUB,     cannot spawn subprocess

Explanation:   The preprocessor was unable to spawn a subprocess to
               compile the program.





                                  49

RDO Facility Messages





User Action:   Read the next message and determine what to do.

CNVNUMDAT,     cannot convert number to a date string

Explanation:   A quadword DATE data type is not in the correct form to
               be converted to a text string.

User Action:   Re-enter the DATE data item in the correct format.

COL_DROPPED,   collating sequence dropped for non-text field <str>

Explanation:   A collating sequence was defined on a non-text field.
               This collating sequence is dropped from the field.

User Action:   None.

COMPLEX,       data conversion error on complex data type

Explanation:   There would have been loss of information on a complex
               data type conversion.  The operation was not performed.

User Action:   Enter another value.

COMPNOTRANS,   <str> in relation <str> will not be transferred

Explanation:   You entered a SELECT FIELDS ALL clause in the DEFINE
               TRANSFER statement to move a relation that contains a
               COMPUTED_BY field using a value expression that is
               unsupported.  The DEFINE TRANSFER statement is accepted
               with all the fields of this MOVE RELATION clause except
               the specified COMPUTED_BY field that is unsupported.

User Action:   Refer to the DEFINE TRANSFER statement in the
               Replication Option for Rdb Handbook for information on
               what value expressions are supported.

COMTOOLON,     command line longer than <num> character maximum

Explanation:   You typed a command line longer than the current
               maximum line length.

User Action:   Break up the command line with continuation lines.
               There is no practical limit on the total length of all
               continuation lines in a single command.

CONALREXI,     constraint <str> already exists in this database

Explanation:   You requested that a constraint be named with the name
               of an existing constraint.

User Action:   Choose a different name.



                                  50

                                                 RDO Facility Messages





CONAMBIG,      the constraint <str> was not qualified and is in
               multiple databases

Explanation:   You must qualify the constraint with database handles
               when accessing more than one database containing that
               constraint.

User Action:   Make sure the INVOKE statements include qualifiers, and
               retype the query using the appropriate qualifier.

CONCHAILL,     cannot begin program with continuation character

Explanation:   Apparently the COBOL program starts with a continuation
               character.

User Action:   Correct the source text and resubmit the job.

CONFATRSPEC,   conflicting or contradictory attributes specified

Explanation:   You specified attributes which cannot be used together.
               Because Oracle Rdb cannot determine which attribute to
               use, it rejects the command.

User Action:   Respecify the DDL without the redundant clauses.

CONFTXNOPTION, Do you really want to <str> this transaction?
               [<char>]:

Explanation:   Confirm that the user actually wants to take the
               action.

CONNOTDEF,     constraint <str> is not defined in database

Explanation:   The specified constraint does not exist in the current
               database.

User Action:   Invoke the correct database.  Check the constraint name
               for correct spelling.  Check the constraint definition
               to make sure you did not specify a term where the
               constraint name was expected.

CONVARDEF,     context variable <str> is already defined

Explanation:   The current statement attempts to define an existing
               context variable such as the P in OPEN IN STREAM S FOR
               P IN PORT.  However, the context variable has already
               been defined in another RSE.

User Action:   Use another context variable, or close the stream in
               which the context variable is defined.





                                  51

RDO Facility Messages





CONVARILL,     cannot use the context variable, <str>, declared in the
               store

Explanation:   A context variable was used in a STORE statement that
               was the same as the one declared in the STORE RSE.
               Example:  STORE J IN PORT USING J.CITY = J.COUNTRY
               END_STORE

User Action:   Change the command to include the correct context
               variable.

CONVARUND,     context variable <str> is not defined

Explanation:   The current statement attempts to use a context
               variable that is not defined in a current RSE.  You may
               have closed the stream in which the context variable
               was defined.

User Action:   Use the context variable within a FOR loop, OPEN STREAM
               loop, or aggregate expression.

CONVERR,       data conversion error

Explanation:   The database management system was unable to convert
               the data item from one data type to another.

User Action:   Enter another value.

CONVONLY,      only a CONVERT command may be issued

Explanation:   User Action:

CS_ERR,        error retrieving collating sequence <str>

Explanation:   The collating sequence could not be retrieved -- see
               the message that follows.

User Action:   Correct the problem and try the operation again.

CVT_PROCEED,   convert proceeding

Explanation:   You issued a CONVERT command and the conversion is
               underway.

User Action:   Wait a moment.

DATACMIT,      unjournaled changes made; database may not be
               recoverable

Explanation:   Changes have been made to the database while AIJ
               journaling was disabled.  This may result in the



                                  52

                                                 RDO Facility Messages





               database being unrecoverable in the event of database
               failure; that is, it may be impossible to roll-forward
               the after-image journals, due to a transaction
               mis-match or attempts to modify objects that were not
               journalled.

User Action:   IMMEDIATELY perform a full database backup.  Following
               successful completion of the full database backup, the
               after-image journals may be backed up.

DATATBLCMIT,   logical area <num> marked corrupt; unjournaled changes
               made to user-defined object

Explanation:   Changes have been made to the database while AIJ/RUJ
               journaling was disabled.  The specified area cannot be
               properly recovered.

User Action:   Drop the area.

DATCNVERR,     conversion error in date string

Explanation:   The date string is not in one of the legal formats.  As
               a result, it cannot be converted to the DATE data type.

User Action:   Re-enter the DATE data item in one of the correct
               formats.

DATCONERR,     data conversion error

Explanation:   An error occurred during data conversion.  Refer to
               next message.

User Action:   The secondary message should clarify the problem.

DATNOTSUP,     date data type not supported in this context

Explanation:   The output of a date value to the language file is not
               supported.  Example:  HV = rdb$missing(date field).

User Action:   Do not use dates in this manner.

DATTYPUNK,     datatype unknown.  Expression cannot use only host
               variables

Explanation:   An assignment or a Boolean expression must have at
               least one database field or literal.

User Action:   You must use a database variable or literal in the
               expression.

DBACTIVE,      database is already being used



                                  53

RDO Facility Messages





Explanation:   You attempted to open a database that is already being
               used.  You can only open a database that is not being
               accessed.

User Action:   Wait for all users to finish using the database, or
               force the users off by closing the database.

DBBUSY,        database is busy - try again later

Explanation:   You attempted to access a database that is shut down.

User Action:   Wait for the database to become available, and try
               again.

DBHANDUNK,     no DATABASE command specified a handle of <str>

Explanation:   You specified an unknown database handle in a context
               variable table definition.

User Action:   Check the query and the INVOKE statement to make sure
               they match.

DBHDLREQ,      db handle should be specified for EXTRACTION ROLLUP
               transfers

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you are attempting to move a relation without
               specifying the database handle of the source database.

User Action:   Reenter the DEFINE TRANSFER statement by specifying the
               database handle of the source database for each of the
               move-relation-clauses.

DBKNOTALL,     DB key references are not allowed in VALID IF
               expressions

Explanation:   You entered a VALID IF expression that did not contain
               an operator, literal value, or field name.

User Action:   Check the Oracle Rdb Reference Manual for details on
               VALID IF.

DBMODIFIED,    database has been modified; AIJ roll-forward not
               possible

Explanation:   The database has been modified.  Consequently,
               performing a "full" roll forward of an after-image
               journal is not possible, because the transaction
               integrity of the database would be compromised by such
               an operation.  Note that the AIJ roll-forward utility
               sometimes converts the /AREA or /PAGE roll- forward



                                  54

                                                 RDO Facility Messages





               operation into a "full" roll-forward operation, if all
               of the specified objects do not need recovery.  In this
               case, this message can be received even when the /AREA
               or /PAGE qualifiers are explicitly specified by the
               user.

User Action:   An after-image journal MUST be rolled forward BEFORE
               any database modifications are made.  In addition, "by
               area" and "by page" after-image journal roll forward
               operations are permitted.

DBNAMEHV,      a database name is not allowed in a qualified host
               variable

Explanation:   You cannot use a database field name to qualify a host
               variable.  For example, you cannot have the following
               expression:  FOR E IN EMPLOYEES WITH E.EMPLOYEE_ID =
               HOST_VAR(E.EMPLOYEE_ID) ...

User Action:   Use an additional GET statement to assign the value of
               the database field to another host variable and use
               that host variable to qualify the first host variable.
               For example, FOR E IN EMPLOYEES GET HOST-VAR-2 =
               E.EMPLOYEE_ID FOR E1 IN EMPLOYEES WITH E.EMPLOYEE_ID =
               HOST-VAR(HOST-VAR-2) ... END_FOR END_FOR

DBNOAIJ,       database does not have AIJ enabled

Explanation:   You attempted to start an AIJ log server for a database
               that does not have AIJ enabled.

User Action:   Enable AIJ for the database, and try again.

DBNOAIJFC,     database does not have AIJ "fast commit" enabled

Explanation:   You attempted to start an AIJ Log Server for database
               replication purposes on a database that does not have
               the AIJ "fast commit" feature enabled.

User Action:   Enable the AIJ "fast commit" feature for the database,
               and try again.

DBNOGB,        database does not have global buffers enabled

Explanation:   The database cannot be opened with the specified global
               buffer parameters because the database does not have
               global buffers enabled.

User Action:   Retry the open operation without specifying global
               buffer parameters.





                                  55

RDO Facility Messages





DBNOTACTIVE,   database is not being used, or must be manually opened
               first

Explanation:   You attempted to close a database that is not open, or
               you attempted to access a closed database that requires
               manual open.

User Action:   There is no need to close the database - it is already
               closed.  If you are attempting to access a closed
               database that requires manual open, open the database
               first.

DBNOTOPEN,     database is not open for access

Explanation:   The database must be opened to allow users to access
               it.

User Action:   Open the database and try again.

DBNOTSPEC,     db handle not specified for segmented string creation

Explanation:   A CREATE_SEG was done with more than one database
               invoked.  You did not specify in which database the
               segmented string was to be created.

User Action:   Add a database handle to the segment handle.

DBOPNNOTCOMP,  database is open on another node in a mode not
               compatible with this node

Explanation:   Another node has already opened the database and the
               database uses some feature that makes it impossible to
               concurrently open the database on this node.  For
               example, if Row Cache is enabled, then all nodes must
               be able to share memory (OpenVMS Galaxy).  If global
               buffers are enabled then every node that is a member of
               the same Galaxy system must use the same global buffer
               parameters when opening the database.

DBRABORTED,    database recovery process terminated abnormally

Explanation:   A detached database recovery process failed to recover
               a transaction.

User Action:   Examine the database monitor log file and any
               SYS$SYSTEM:*DBRBUG.DMP bugcheck dump files for more
               information.

DBRBOUND,      attach not allowed while your process is being
               recovered





                                  56

                                                 RDO Facility Messages





Explanation:   The database recovery process (DBR) is currently
               recovering an image for your process.  While the
               recovery operation is running, you cannot start another
               image that attempts to attach/bind to the database.

User Action:   You can attach/bind to another database.  Otherwise,
               you must wait for the database recovery process to
               complete recovery of your previous image.

DBSHUTDOWN,    database shutdown is in progress

Explanation:   The request you made could not be completed because the
               database is being shut down.

User Action:   Examine the database monitor log file
               (SYS$SYSTEM:*MON.LOG) for more information.

DB_CVT_FAIL,   database conversion failed

Explanation:   You issued a CONVERT command and the conversion has
               failed.

User Action:   Accompanying messages should indicate further action.
               The conversion process will have left the database in
               an inconsistent state so you will have to restore a
               copy of the database from the backup media and retry
               the CONVERT command on the restored copy of the
               database.

DB_CVT_SCS,    database <str> successfully converted from version
               <num>.<num> to <num>.<num>

Explanation:   You issued a CONVERT command and the conversion has
               completed.

User Action:   None.

DB_HANDEC,     handle already declared

Explanation:   You declared a database handle through ACMS.  This
               interferes with defining a handle through the
               interpreter.

User Action:   You should not specify another handle.

DB_HANDEC2,    handle already declared

Explanation:   You declared a database handle through ACMS.  This
               interferes with defining a handle through the
               interpreter.  This also interferes with declaring
               multiple database handles.



                                  57

RDO Facility Messages





User Action:   You should not specify another handle.

DB_HANLON,     the DB handle must be a longword

Explanation:   Database handles that are passed to RDB$INTERPRET must
               be longwords passed by descriptor.

User Action:   Define the database handle to be a longword.  Examples:
               For COBOL:  01 DBHANDLE PIC S9(9) COMP.  For FORTRAN:
               INTEGER*4 DBHANDLE.  For BASIC:  LONG DBHANDLE.

DB_NOTCVT,     database not converted

Explanation:   You issued a convert command and the conversion was not
               attempted.

User Action:   You should correct the problem and retry the convert.

DDALERR,       Replication Option for Rdb fatal error

Explanation:   You entered a Replication Option for Rdb statement
               which failed.

User Action:   Refer to the explanation in the user action section of
               the secondary error message.

DEADLOCK,      deadlock on <str>

Explanation:   The operation you attempted has been forbidden by the
               database management system because it would have led to
               a system deadlock.

User Action:   Execute a ROLLBACK or a COMMIT to release your locks,
               and try the transaction again.

DEGMODSPC,     only one degree mode may be specified for a transaction

Explanation:   You specified two degree modes (consistency or
               concurrency) in a START_TRANSACTION statement.

User Action:   Specify one degree mode in your START_TRANSACTION
               statement.

DELETEFAILS,   Cache file <str> deletion failed

Explanation:   Attempt made to delete non existing file.

User Action:   Check for the existence of the cache file.

DELPRC,        database attach has been terminated





                                  58

                                                 RDO Facility Messages





Explanation:   The user's attach has been terminated.

User Action:   This error message indicates that a request was made to
               eliminate this user's database attach.  The termination
               may have been requested due to a database action such
               as closing the database with the ABORT=DELPRC option,
               or potentially an unrecoverable error was encountered
               by the database system that necessitated terminating
               the user.

DESCTOOBIG,    the description clause's maximum length is <num>

Explanation:   Oracle Rdb currently has a limit for a description
               clause size.

User Action:   Use a shorter description clause.

DOENBLAIJ,     after-image journaling must be enabled to ensure
               recovery

Explanation:   After adding an AIJ journal, it is necessary to enable
               AIJ journaling (if it is not already enabled).  Failure
               to enable AIJ journaling will result in the AIJ file
               being NOT recoverable.

User Action:   IT IS HIGHLY RECOMMENDED that after-image journaling be
               enabled AS SOON AS POSSIBLE.

DOFULLBCK,     full database backup should be done to ensure future
               recovery

Explanation:   After enabling AIJ journaling, it is often necessary to
               perform a full (i.e., not incremental) database backup.
               Failure to backup the database may result in the AIJ
               file NOT being recoverable.

User Action:   IT IS HIGHLY RECOMMENDED that a full database backup be
               performed AS SOON AS POSSIBLE.

DTFMTTOOBIG,   date or time format must be in the range 1 to 999

Explanation:   You entered a DATE or TIME value outside the range 1 to
               999 in the SET DATE_FORMAT statement.

User Action:   Enter a value greater than or equal to 1 and less than
               or equal to 999.

DTONCEEACH,    you can specify DATE or TIME only once each

Explanation:   You entered DATE date-number twice or TIME time-number
               twice in the SET DATE_FORMAT statement.



                                  59

RDO Facility Messages





User Action:   Enter nothing, or enter DATE, TIME, or one of each with
               SET DATE FORMAT.

DUPAIJFIL,     duplicate AIJ filename "<str>" specified

Explanation:   A duplicate AIJ file name was specified during AIJ
               journal addition.  Each AIJ file name is used to
               identify a specific journal and must be unique within a
               database.

User Action:   Please specify a unique AIJ filename.

DUPAIJNAM,     duplicate AIJ name "<str>" specified

Explanation:   A duplicate AIJ name was specified during AIJ journal
               addition.  Each AIJ name is used to identify a specific
               journal and must be unique within a database.

User Action:   Please specify a unique AIJ name.

DUPCCHNAM,     record cache "<str>" already exists

Explanation:   A duplicate record cache name was specified.  The name
               used to identify a cache must be unique within a
               database.

User Action:   Please specify a unique record cache name.

DUPFLDDEF,     field <str> has different definitions in relations
               <str> and <str>

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you are attempting to move a field which does
               not have the same definition in all the source
               databases.  Since we cannot have two definitions of a
               field in the target database, the DEFINE TRANSFER
               command is invalid.

User Action:   Reenter the DEFINE TRANSFER statement by including only
               one definition of the field mentioned above or by
               changing all the definitions of this field into the
               same type.

EDTSTRUNC,     filename edits "<str>" truncated

Explanation:   Internal represenation of filename edits limited to a
               maximum of 31 characters.  Specified filename edits
               truncated to the maximum of 31 characters.

User Action:   No action required.  If desired, the filename edit
               specification can be shortened.



                                  60

                                                 RDO Facility Messages





EMPTYAIJ,      after-image journal file is empty

Explanation:   A recovery operation was attempted on an empty
               after-image journal file, or the UNTIL time predates
               any journaled transactions.  The former can happen if
               no transactions were initiated while after-image
               journaling was in progress.

User Action:   Correct the error and try again.

EMPTYFILE,     <str> file is empty

Explanation:   The file is empty.

User Action:   None.

ERRDET,        an error was detected

Explanation:   An "error level" (-E-) error condition was detected by
               RDO and returned to DCL during the execution of an RDO
               statement.

User Action:   If possible, run the statement(s) again in interactive
               RDO and read any additional RDO error messages to
               determine what caused the error condition.  Then fix
               the error.  Remember, in a DCL command procedure
               containing RDO statements, use the $SEVERITY symbol to
               test for RDO$_ERRDET.

ERRFOREIGN,    error opening foreign command file as input

Explanation:   An error occurred during the reading of a foreign
               command file.

User Action:   Examine the secondary message for more information.

ERROPENIN,     error opening <str> as input

Explanation:   An error occurred during opening of an input file.

User Action:   Examine the secondary message for more information.

ERROPENOUT,    error opening <str> as output

Explanation:   An error occurred during opening of an output file.

User Action:   Examine the secondary message for more information.

ERRWRITE,      error writing file

Explanation:   An error occurred during a file write.



                                  61

RDO Facility Messages





User Action:   Examine the secondary message for more information.

EXNODECNT,     database cannot be opened on this node -- maximum node
               count (<num>) exceeded

Explanation:   The database cannot be opened on this node, because it
               has already been opened on the maximum allowable number
               of nodes.

User Action:   Consider increasing the maximum number of nodes
               configured for the database.

EXPCV_DOT,     expected context variable and dot, host variables not
               permitted here

Explanation:   You attempted to use a name where a variable or literal
               was required.  The error message indicates that you
               probably forgot to type the context variable and a
               period before a field name, or you forgot to use
               quotation marks around a quoted string.

User Action:   Add a context variable and a period or use a literal.

EXQUOTA,       exceeded quota

Explanation:   The image could not proceed because a resource quota or
               limit had been exceeded.

User Action:   The secondary error message describes the resource that
               was exceeded.  If this occurs consistently, increase
               your quota.

EXTNOTSUP,     EXTERNAL database handles are not supported for
               RDB$INTERPRET

Explanation:   External database handles are not supported for
               RDB$INTERPRET.  Only LOCAL and the default database
               handle are supported.  External database handles apply
               only to preprocessors that can declare variables for
               database handles.

User Action:   For database handles that must be accessed in multiple
               modules, use LOCAL.  Otherwise, use the default
               database handle.

EXTRADATA,     unexpected data at the end of the RBR file

Explanation:   Internal error - found more data than expected in the
               Oracle Rdb interchange file (RBR).

User Action:   Contact your Oracle support representative for



                                  62

                                                 RDO Facility Messages





               assistance.

EXTSRTSTAT,    Records:<num> Merges:<num> Nodes:<num> WorkAlq:<num>

Explanation:   During extraction operations, statistics are often
               collected to aid the user in tuning.  This message
               displays statistics.

FETNOTDON,     a fetch has not been done yet for stream <str>

Explanation:   You referenced a stream, but you did not issue a FETCH
               statement for that stream.

User Action:   Type FETCH <stream name>.

FIELD_EXISTS,  field <str> already exists in this database

Explanation:   You requested that a field be named with the name of an
               existing field.

User Action:   Choose a different name.

FIENOTALL,     field, <str>, is not allowed in the VALID IF expression
               for field <str>

Explanation:   You entered a field name in a VALID IF clause that does
               not match the name of the field being defined.

User Action:   Check the Oracle Rdb Reference Manual for details on
               VALID IF, or use the name of the field you are
               defining.

FIENOTREN,     field <str> cannot rename CDD field <str>

Explanation:   You requested that a field being defined from a CDD
               definition be named something other than the name of
               the CDD field.

User Action:   Respecify the field definition using the CDD field
               name.

FIENOTSEG,     field, <str>, is not a segmented string

Explanation:   You attempted a START_SEGMENTED_STRING operation using
               a field that is not a segmented string.

User Action:   Use a segmented string field with the
               START_SEGMENTED_STRING statement.

FILACCERR,     error <str> file <str>





                                  63

RDO Facility Messages





Explanation:   A file-access error occurred.

User Action:   Examine the secondary message for more information.

FILSIGNATURE,  standby database storage area signature does not match
               master database

Explanation:   The number of storage area slots ("reserved"), or the
               specific storage area page size, are not identical on
               both the master and standby databases.

User Action:   Make sure both the master and standby database storage
               area configurations are identical.  Do not change any
               storage area page size when restoring the databases.

FLDAMBIG,      field <str> is not unique in previous relations in the
               CROSS

Explanation:   You specified a field that does not exist in the
               previous relations specified by the CROSS clause.

User Action:   The relation definition associated with the context
               variable does not include a definition for the
               specified field.  You may have specified the wrong
               context variable with the field or mistyped the field
               name.

FLDNOTCRS,     field <str> was not found in previous relations in the
               CROSS

Explanation:   You specified a field that is not in the relations
               specified in the CROSS clause.

User Action:   The relation definition associated with the context
               variable did not include a definition for the specified
               field.  You may have specified the wrong context
               variable with the field or mistyped the field name.

FLDNOTDEF,     field <str> is not defined in relation <str>

Explanation:   You specified a field that does not exist in the named
               relation.

User Action:   The relation definition associated with the context
               variable did not include a definition for the specified
               field.  You may have specified the wrong context
               variable with the field or mistyped the field name.

FLDNOTINREL,   <str> is not a field in relation, <str>

Explanation:   The field you specified is not part of the named



                                  64

                                                 RDO Facility Messages





               relation.

User Action:   Check the relation definition for the correct field
               name, or specify another relation.

FLDNOTREFD,    defined field, <str>, is not used in VALID IF clause

Explanation:   You defined a field with a VALID IF clause that does
               not reference the defined field.

User Action:   Define the field again, and name that field in the
               VALID IF clause.

FLUINPBUF,     indirect command file buffer flushed for Control C

Explanation:   You entered CTRL/C while executing an indirect command
               file.

User Action:   None.

FOREIGN_NOUNQCON, no Primary/Unique constraint matching foreign
               constraint <str>

Explanation:   The foreign relation constraint must have a primary or
               unique constraint (with its key matching the foreign
               relation constraint's referenced key) defined and
               stored or defined in the same relation with the foreign
               relation constraint.

User Action:   Correct the problem and try the operation again.

FOREIGN_REFGREFD, referencing/referenced fields number mismatch in
               foreign constraint <str>

Explanation:   The number of referencing and referenced fields must be
               equal in the foreign relation constraint.

User Action:   Correct the problem and try the operation again.

FULLAIJBKUP,   partially-journaled changes made; database may not be
               recoverable

Explanation:   Partially-journalled changes have been made to the
               database.  This may result in the database being
               unrecoverable in the event of database failure; that
               is, it may be impossible to roll-forward the
               after-image journals, due to a transaction mis-match or
               attempts to modify objects that were not journalled.
               This condition typically occurs as a result of
               replicating database changes using the Hot Standby
               feature.



                                  65

RDO Facility Messages





User Action:   IMMEDIATELY perform a full (not by-sequence)
               quiet-point AIJ backup to clear the AIJ journals,
               followed immediately by a full (no-quiet-point allowed)
               database backup.

GARBLED,       interchange file is corrupt

Explanation:   Internal error - probably mismatched BEGIN and END
               clumps.

User Action:   Contact your Oracle support representative for
               assistance.

GETTXNOPTION,  Do you wish to COMMIT/ABORT/IGNORE this transaction:

Explanation:   Ask the user whether to COMMIT/ABORT/IGNORE this
               blocked transaction.

GETTXNOPT_NO_IGN, Do you wish to COMMIT/ABORT this transaction:

Explanation:   Ask the user whether to COMMIT/ABORT this blocked
               transaction.

User Action:   None.

GOODAIJSEQ,    AIJ file is correct for roll-forward operations

Explanation:   The specified AIJ file is the correct file to be rolled
               forward.

User Action:   No user action is required.  This message is
               informational only.

HIBER,         thread requests hibernate

Explanation:   The currently executing internal thread has requested a
               short term hibernation.

User Action:   This state should never be seen by a user application.
               It is only used by the internal threading mechanisms.

HOTACTVTX,     Active transactions prevent replication startup

Explanation:   The Log Catch Server (LCS) is unable to complete the
               catch-up phase of replication startup.  Active
               transactions prevented the LCS from acquiring a
               quiet-point within the specified interval.

User Action:   Ensure that no extremely long-running transaction are
               active.  Increase the LCS quiet-point timeout interval.





                                  66

                                                 RDO Facility Messages





HOTADDSWTCH,   Hot Standby is active and AIJ switch-over suspended -
               backup existing journals first

Explanation:   The AIJ switch-over operation is suspended and
               performing the requested AIJ journal creation while Hot
               Standby is active could result in replication being
               terminated.

User Action:   It is recommended to backup one or more existing AIJ
               journals before creating the new AIJ journal(s).

HOTBCKCONT,    continuous AIJ backup not permitted when replication
               active

Explanation:   The "continuous" AIJ backup operatoion is not permitted
               when the database replication is active.

User Action:   Use the AIJ Backup Server (ABS) process when using
               multiple AIJ journals, or issue non-continuous AIJ
               backup operations when using a single AIJ journal.

HOTCMDPEND,    request cannot be completed due to pending hot standby
               command

Explanation:   A Hot Standby command was pervious requested from this
               node using the /NOWAIT qualifier; the command has not
               yet completed.  The command just requested cannot be
               completed until the Hot Standby feature command already
               active but pending on this node has first completed.

User Action:   The requested Hot Standby command must be completed
               prior to issuing this command.  Use the SHOW USERS
               command to indicate the status of the Hot Standby
               command.

HOTEXCHMSG,    error exchanging replication message

Explanation:   User Action:

HOTFAILURE,    hot standby failure:  <str>

Explanation:   A hot standby failure occurred.

User Action:   Examine the secondary message for more information.

HOTLCLCNCT,    error allocating local network connection

Explanation:   User Action:

HOTMISMATCH,   standby database version does not match master database





                                  67

RDO Facility Messages





Explanation:   The version time and date stamp in the standby database
               root does not match the version time and date stamp in
               master database root.  Also, it may be possible that
               the standby database was backed up and restored,
               thereby invalidating the abaility to be replicated.

User Action:   Ensure that the specified standby database is correct
               and restored from a master database backup file.

HOTNOCIRCEXT,  cannot switch from circular to extensible AIJ
               journaling if replication active

Explanation:   User Action:  Terminate database replication first.

HOTNOEXTCIRC,  cannot switch from extensible to circular AIJ
               journaling if replication active

Explanation:   Adding a new AIJ journal is not allowed while database
               replication is active, if adding the journal would
               activate circular journaling.

User Action:   Terminate database replication first.

HOTNOONLINE,   attempt to access standby database opened for exclusive
               access

Explanation:   An attempt has been made to attach to a standby
               database for which replication has been started with
               exclusive access.

User Action:   Stop replication and re-start with "online" access to
               the standby database.

HOTNORC,       record cache not allowed on hot standby database during
               replication

Explanation:   The record cache feature must be disabled on the hot
               standby database during hot standby replication.

User Action:   Open (or re-open) the standby database with the
               RECORD_CACHE=DISABLED qualifier.

HOTOFFLINE,    standby database opened for exclusive access

Explanation:   Hot Standby replication has been started on the master
               database using exclusive access.  This occurs when the
               /NOONLINE qualifier is used, or the /ONLINE qualifier
               is not specified during replication startup.  When the
               standby database is in "exclusive" mode, user processes
               cannot attach to the database.





                                  68

                                                 RDO Facility Messages





User Action:   If exclusive access is not desired, Hot Standby
               replication must be terminated and restarted using the
               /ONLINE qualifier.

HOTRECVMSG,    error receiving replication message

Explanation:   User Action:

HOTREMCNCT,    error allocating remote network connection

Explanation:   User Action:

HOTREMDELT,    error deleting replication connection

Explanation:   User Action:

HOTREMDSCT,    error disconnecting from replication server

Explanation:   User Action:

HOTRWTXACTV,   database in use with active or pre-started read/write
               transactions

Explanation:   Database replication cannot be started on the standby
               database if there are processes with active or
               pre-started read/write transactions.

User Action:   All read/write transaction activity must be stopped
               prior to starting database replication on the standby
               database.

HOTSEQBCK,     cannot find AIJ journal required to start replication

Explanation:   Database replication using the Hot Standby feature was
               attempted to be started, but the AIJ journal required
               by the standby database could not be found on the
               master database.  This typically occurs when the AIJ
               Backup Server ("ABS") inadvertantly backs up the AIJ
               journal on the master database following an AIJ
               switch-over operation.

User Action:   The journal specified in the Log Catchup Server ("LCS")
               output file must be manually rolled forward on the
               standby database.  Alternately, the master database
               must be backed up and restored as the standby database.

HOTSTOPWAIT,   stopping database replication, please wait

Explanation:   This message informs the user that database replication
               is being stopped and to wait for shutdown to complete.
               Replication shutdown times vary based on system and



                                  69

RDO Facility Messages





               network activity.

User Action:   Wait for database replication to stop.

HOTSVRCNCT,    error connecting to replication server

Explanation:   User Action:

HOTSVRFIND,    error identifying remote replication server

Explanation:   User Action:

HOTWRONGDB,    attempt to start replication for wrong master database

Explanation:   An attempt has been made to start replication on a
               master database whose standby database is already
               replicating a different master database.  The master
               root file name does not match the name used when
               replication was first started on the standby database.
               This could happen if you copied or renamed the master
               database root file, or if the file was created using a
               concealed logical device name and that logical name is
               no longer defined.

User Action:   Ensure that the specified standby database is correct.
               If so, ensure that replication on the standby database
               has been fully terminated; replication termination
               occassionally has long-duration shutdown processing to
               be performed.  If the master database rootfile had been
               moved, rename or copy the root file back to its
               original name or location, or redefine the necessary
               concealed logical device name in the system logical
               name table.

HOWCHANOT,     no attribute specified for command to change field
               <str>

Explanation:   You tried to change a field but did not specify any
               attribute to change.

User Action:   Specify an attribute to change.

IKEYOVFLW,     compressed IKEY for index "<str>" exceeds 255 bytes

Explanation:   The current index key (IKEY) being stored in a sorted
               or hashed index with compression enabled has exceeded
               the 255-byte IKEY-length limit during compression.
               With IKEY compression enabled, some IKEYs may actually
               increase in size during compression and potentially
               exceed the 255-byte limit.





                                  70

                                                 RDO Facility Messages





User Action:   Refer to your reference documention for details on
               controlling the maximum expansion overhead during IKEY
               compression.  Alternatively, recreate the specified
               index with compression disabled.

ILLBEGIN,      file <str> is corrupt or not an Oracle Rdb interchange
               file

Explanation:   IMPORT can recreate databases only from the Oracle Rdb
               interchange file (RBR).  This file is not an Oracle Rdb
               interchange file (RBR).

User Action:   Retry the operation with the correct file name.

ILLCHAR,       illegal character detected

Explanation:   An illegal character has been detected.

User Action:   Use only valid characters.

ILLNCHAR,      illegal character found in numeric input

Explanation:   You specified a number containing a non-numeric
               character.

User Action:   Correct the error and try again.

IMGABORTED,    image aborted at privileged user request

Explanation:   The current image was aborted by another privileged
               user, typically the database administrator, in response
               to some event that required this action.

User Action:   Consult the database administrator to identify the
               reason the image was aborted.

IMP_CDD_NODATA, importing a CDD dictionary with NODATA is not allowed

Explanation:   You used the NODATA option when importing a CDD/Plus
               dictionary database.

User Action:   You cannot use the NODATA option when importing
               CDD/Plus dictionaries.  The resulting database is not
               usable by CDD/Plus.  Use the DATA option and try again.

IMP_DDLWARN,   warnings reported while importing or creating object
               <str>

Explanation:   Warnings were issued during the import of the named
               object.  This may indicate that the object is valid but
               may not be optimal.  For instance, the new definition



                                  71

RDO Facility Messages





               on the IMPORT command line might duplicate an existing
               index definition, or specify a node size that would not
               fit in the associated row cache.

User Action:   Check the messages which follow for the warning
               information and take appropriate action if necessary.

IMP_IDXNOTDEF, index <str> not defined - check spelling of the
               relation name

Explanation:   The IMPORT operation could not process a DEFINE INDEX
               clause because the named relation was not defined in
               the database.

User Action:   Check that the relation name was spelled correctly.

IMP_IDXNOTDEL, index <str> not deleted - check spelling of the index
               name

Explanation:   The IMPORT operation could not process a DELETE INDEX
               clause because the named index was not defined in the
               database.

User Action:   Check that the index name was spelled correctly.

IMP_IDX_CONFLICT, DEFINE and DELETE INDEX <str> specified

Explanation:   You specified a DEFINE and DELETE INDEX using the same
               name.

User Action:   Specify either a DEFINE or a DELETE INDEX.

IMP_IDX_TWICE, DEFINE or DELETE INDEX <str> specified twice

Explanation:   You specified a DEFINE or DELETE INDEX twice using the
               same name.

User Action:   Specify a INDEX name only once.

IMP_STANOTDEL, storage area <str> not deleted - check spelling of the
               storage area name

Explanation:   The IMPORT operation could not process a DELETE STORAGE
               AREA clause because the named storage area was not
               defined in the database.

User Action:   Check that the storage area name was spelled correctly.

IMP_STMNOTDEF, storage map <str> not defined - check spelling of the
               relation name





                                  72

                                                 RDO Facility Messages





Explanation:   The IMPORT operation could not process a DEFINE STORAGE
               MAP clause because the named relation was not defined
               in the database.

User Action:   Check that the relation name was spelled correctly.

IMP_STMNOTDEL, storage map <str> not deleted - check spelling of the
               storage map name

Explanation:   The IMPORT operation could not process a DELETE STORAGE
               MAP clause because the named storage map was not
               defined in the database.

User Action:   Check that the storage map name was spelled correctly.

IMP_STO_CONFLICT, DEFINE and DELETE STORAGE AREA <str> specified

Explanation:   You specified a DEFINE and DELETE STORAGE AREA using
               the same name.

User Action:   Specify a either a DEFINE or a DELETE STORAGE AREA.

IMP_STO_MAP_CONFLICT, DEFINE and DELETE STORAGE MAP <str> specified

Explanation:   You specified a DEFINE and DELETE STORAGE MAP using the
               same name.

User Action:   Specify either a DEFINE or a DELETE STORAGE AREA.

IMP_STO_MAP_TWICE, DEFINE or DELETE STORAGE MAP <str> specified twice

Explanation:   You specified a DEFINE or DELETE STORAGE MAP twice
               using the same name.

User Action:   Specify a STORAGE MAP name only once.

IMP_STO_TWICE, DEFINE or DELETE STORAGE AREA <str> specified twice

Explanation:   You specified a DEFINE or DELETE STORAGE AREA twice
               using the same name.

User Action:   Specify a STORAGE AREA name only once.

INDEXTS,       there is another index named, <str>, in this database

Explanation:   The index name you tried to define already exists.
               This message is also printed during an IMPORT operation
               if the backup file contains multiple definitions of an
               index.  Duplicate definitions may indicate corruption
               of the .RBR file, or improper operation during the
               EXPORT operation.



                                  73

RDO Facility Messages





User Action:   Try another index name.  If this message arose during
               an IMPORT operation, then contact your Oracle support
               representative for assistance.

INDNOEXI,      index <str> does not exist in this database

Explanation:   The index you attempted to change was not found.

User Action:   Check the name of the storage map using the SHOW
               command and try again to change it.

INSFRPGS,      physical memory has been exhausted

Explanation:   Physical memory has been exhausted on the machine,
               typically because of an excessive number of cache
               global sections, or excessively large cache global
               section sizes.

User Action:   If possible, increase the amount of physical memory on
               the machine.  Reduce the number of cache global
               sections, or reduce the size of each active cache
               global sections.  Possibly moving a cache from SSB to
               VLM will also solve this problem.  It might be
               necessary to delete some caches to alleviate this
               problem.  Also, re-configuring the operating system
               parameters may be necessary to reduce physical memory
               consumption.

INTEGDBDIF,    Database filespec must equate to filespec <str>
               recorded in CDD

Explanation:   The INTEGRATE database filespec and the filespec
               recorded with the dictionary database definitions found
               at the specified pathname refer to different databases.

User Action:   Reissue the command with a filespec that corresponds to
               the database referenced in the data dictionary, or with
               a different pathname.

INTEGFRFAIL,   attempt to INTEGRATE FROM nonexistent CDD entity <str>

Explanation:   The data dictionary entity required for INTEGRATE FROM
               does not exist.

User Action:   Respecify a path that points to an existing data
               dictionary entity.

INTONOTALW,    INTO RELATION clause is not allowed in this context

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION or
               REPLICATION transfer, you have specified an INTO



                                  74

                                                 RDO Facility Messages





               RELATION clause.

User Action:   Reenter the DEFINE TRANSFER statement by not specifying
               an INTO RELATION clause.

INTSYNERR,     <str> <str>

Explanation:   This message is used by the interpreter to put the line
               with the syntax error into the message vector.

User Action:   Call RDB$SIGNAL and find the syntax error.

INVCHAINP,     invalid character in input

Explanation:   The input contains an illegal or unrecognizable
               character.

User Action:   Correct the source text and resubmit the job.

INVCHANUMSTR,  invalid character in numeric string

Explanation:   The string appears to be a numeric literal.  However,
               it contains one or more illegal characters.

User Action:   Correct the source text and resubmit the job.

INVCONS,       unable to IMPORT constraint <str>

Explanation:   Internal error - the named constraint will not appear
               in the recreated database.

User Action:   Contact your Oracle support representative for
               assistance.  In the meantime, you can redefine this
               constraint explicitly.

INVDBK,        <num>:<num>:<num> is not a valid dbkey

Explanation:   An attempt was made to fetch a record by its database
               key value, but the specified page is a SPAM, ABM, or
               AIP.  Alternatively, the specified dbkey refers to a
               non-existing storage area or a system record.

User Action:   Correct the condition, and try again.

INVDBKREF,     invalid use of a database key

Explanation:   Dbkeys cannot be used in an RSE except to check for
               equality or non-equality with a dbkey fetched from the
               database.

User Action:   Correct the problem and try the operation again.



                                  75

RDO Facility Messages





INVDBSFIL,     inconsistent storage area file <str>

Explanation:   The indicated storage area file is inconsistent with
               the root file.  This might happen if you have
               improperly used any unsupported methods for backing up
               or restoring files (for instance, COPY or RENAME).
               This can also happen if you tried to use an old root
               file -- one whose storage area file names have been
               re-used for another database.

User Action:   Restore the correct storage-area file or delete the
               obsolete root file.

INVFLD,        unable to IMPORT field <str>

Explanation:   Internal error - the named field will not appear in the
               recreated database.

User Action:   Contact your Oracle support representative for
               assistance.

INVFLDPRO,     invalid protection defined for field, only MODIFY
               allowed

Explanation:   Only MODIFY may be specified for field protection.

User Action:   Do not specify field privileges other than MODIFY.

INVFLDSIZE,    specified invalid field size

Explanation:   You specified an illegal field size.

User Action:   Please specify a field size between 0 and 32768
               exclusive.

INVHEADER,     invalid file header record

Explanation:   An invalid file header record was read from the file.

User Action:   Check the file specification and try again.

INVINDEX,      unable to IMPORT index <str>

Explanation:   Internal error - the named index will not appear in the
               recreated database.

User Action:   Contact your Oracle support representative for
               assistance.  In the meantime, you can redefine this
               index explicitly.

INVMARKOP,     invalid markpoint commit/rollback for TSN <num>:<num>,



                                  76

                                                 RDO Facility Messages





               MARK_SEQNO <num>

Explanation:   A fatal, unexpected error was detected by the database
               management system during the commit or rollback of a
               markpoint.  This message indicates the "transaction
               sequence number" of the transaction and the "markpoint
               sequence number" of the markpoint that has to be
               committed or rolled back.

User Action:   Contact your Oracle support representative for
               assistance.

INVNODESIZE,   invalid node size parameter specified

Explanation:   The command specified a number for a node size which
               was invalid.  It was either less than or equal to zero
               or greater than 32768.

User Action:   Review the command and respecify using a node size
               within the above range (but big enough to meet the
               implementation requirements).

INVNOTDON,     no DATABASE invoked yet, please issue a DATABASE
               command

Explanation:   You must invoke a database before you issue an RDO
               statement.  can be executed.

User Action:   Invoke the database, and then issue the RDO statement.

INVPAGPRM,     allocation parameter <num> overflows when rounded

Explanation:   the allocation parameter selected, though it may be an
               allowed value, becomes illegal when rounded to make an
               even number of pages in the storage area; i.e., the
               number of pages to actually be allocated is always a
               multiple of the number of pages per buffer

User Action:   select a smaller allocation parameter.

INVPERCENTFILL, invalid percent fill parameter specified

Explanation:   The command specified a number for a percent fill which
               was invalid.  It was either less than or equal to zero
               or greater than 100.

User Action:   Review the command and respecify using a percent fill
               within the above range.

INVPRIVNAMES,  invalid privilege names specified in message file





                                  77

RDO Facility Messages





Explanation:   The names specified in PRIV_NAMES0 and PRIV_NAMES1 were
               incorrect in some way.

User Action:   Contact your Oracle support representative for
               assistance.

INVRELVIEW,    unable to IMPORT relation or view <str>

Explanation:   Internal error - the named relation or view (and its
               data) has been lost.

User Action:   Contact your Oracle support representative for
               assistance.

INVSEGSTRATR,  invalid segmented string attribute

Explanation:   You specified a MISSING VALUE or VALID IF clause along
               with a segmented string data type.

User Action:   You should respecify the data definition statement
               without the MISSING VALUE or VALID IF clauses.

INVSTOMAP,     storage map is invalid as specified

Explanation:   You specified an invalid storage map.

User Action:   Review the command and issue it correctly.

INVTRG,        unable to IMPORT trigger <str>

Explanation:   Internal error - the named trigger will not appear in
               the recreated database.

User Action:   Contact your Oracle support representative for
               assistance.  In the meantime, you can redefine this
               trigger explicitly.

INV_ROOT,      database file has illegal format

Explanation:   You attempted to use a file that is not a database
               file.

User Action:   Check the file specification and try again.

INXNOFLD,      no field name in the index definition

Explanation:   You must specify one or more field names in the index
               definition.

User Action:   Correct the index definition and retry the command.





                                  78

                                                 RDO Facility Messages





IOERROR,       an unexpected I/O error occurred

Explanation:   Unable to read any more of the Oracle Rdb interchange
               file (RBR); part of the database may be imported.

User Action:   Correct the problem indicated by the message that
               follows this message and retry the operation.

IVCHAN,        invalid or unknown I/O channel

Explanation:   The channel number cannot be located in the database
               information.

User Action:   Contact your Oracle support representative for
               assistance.

JUNONLIN,      extraneous characters found after the end of the
               statement

Explanation:   You typed extra characters after the end of the
               statement.

User Action:   Check statement syntax for correct statement
               termination.

LANFILEXT,     <str> is the language file extension, please use
               another extension

Explanation:   The input file type you specified to the preprocessor
               is the same file type as the output file type.

User Action:   Rename the file with the default file specifications
               and run the preprocessor again.  Refer to the default
               file specifications in the Oracle Rdb Guide to
               Programming.

LCKCNFLCT,     lock conflict on <str>

Explanation:   The operation you attempted failed because another run
               unit is holding a lock in a mode that conflicts with
               the lock mode you needed.

User Action:   Wait for the other run unit to finish.  Use ROLLBACK or
               COMMIT to release all your locks and retry the
               transaction, or specify that you want to wait on lock
               conflicts.

LCSNOOUT,      AIJ Log Catch-Up Server does not have an output file

Explanation:   The AIJ Log Catch-Up Server process does not have an
               output file associated with it.



                                  79

RDO Facility Messages





User Action:   Use the /OUTPUT qualifier to specify an output filename
               when database replication is started on the master
               database.

LENMISMAT,     truncating right hand side string for assignment to
               field <str>

Explanation:   You executed a STORE or MODIFY statement, and the
               string on the right hand side of the equation is longer
               than the string on the left.

User Action:   The message is just a warning.  You can issue a MODIFY
               statement to correct the store or a ROLLBACK statement
               to terminate the transaction.

LHSNOTDBN,     the left hand side of the assignment expression is not
               a DB name

Explanation:   The left side of an assignment expression in a STORE or
               MODIFY statement must be a field name qualified by a
               context variable.  Example:  P.CITY

User Action:   Use a qualified database field name in the left side of
               an assignment expression.

LHSNOTVAR,     the left hand side of the assignment expression is not
               a variable

Explanation:   The left side of an assignment expression in a GET
               command must be a host variable.  For preprocessed
               statements, the variable must be a host language
               variable.  For Callable RDO, the variable must be
               "!VAL".

User Action:   Use a host variable in the left side of an assignment
               expression.

LMNOENABLED,   LogMiner has not yet been enabled

Explanation:   The LogMiner feature has not been enabled on this
               database.

User Action:   If LogMiner features are enabled, LogMiner should be
               enabled.

LOGADDCCH,     added record cache definition "<str>"

Explanation:   A new record cache definition has been successfully
               added the the database.

LOGAIJBCK,     backed up <num> <str> transaction(s) at <time>



                                  80

                                                 RDO Facility Messages





Explanation:   The specified number of committed or rolled-back
               transactions were successfully backed up from the
               after-image journal file.

LOGAIJBLK,     backed up <num> after-image journal block(s) at <time>

Explanation:   The specified number of blocks were successfully backed
               up from the after-image journal file.

User Action:   No user action is necessary.

LOGAIJJRN,     backed up <num> after-image journal(s) at <time>

Explanation:   The specified number of after-image journals were
               successfully backed up during the AIJ backup operation.

User Action:   No user action is necessary.

LOGCREOPT,     created optimized after-image journal file <str>

Explanation:   This message indicates the action taken on a specific
               file.

User Action:   No user action is required.

LOGDELAIJ,     deleted temporary after-image journal file <str>

Explanation:   This message indicates the action taken on a specific
               file.

LOGDELCCH,     deleted record cache definition "<str>"

Explanation:   A record cache definition has been successfully deleted
               from the database.

LOGMODCCH,     modifying record cache definition "<str>"

Explanation:   The parameters for a record cache are in the process of
               being modified.

LOGMODSPM,     modified <num> spam page(s)

Explanation:   None.

LOGMODSTO,     modifying storage area <str>

Explanation:   The parameters for a storage area are in the process of
               being modified.

LOGRECOVR,     <num> transaction(s) <str>





                                  81

RDO Facility Messages





Explanation:   Database recovery was successful.  The specified number
               of transactions were re-applied to the database,
               ignored, or rolled back.

User Action:   None.

LOGRECSTAT,    transaction with TSN <num>:<num> <str>

Explanation:   During roll-forward, this message is displayed every
               time a transaction is committed, rolled back, or
               ignored.

LOGRESOLVE,    blocked transaction with TSN <num>:<num> <str>

Explanation:   When a blocked transaction is resolved, this message is
               displayed every time the transaction is committed,
               rolled back, or ignored.

LOGSUMMARY,    total <num> transaction(s) <str>

Explanation:   Database recovery was successful.  The specified total
               number of transactions were re-applied to the database,
               ignored, or rolled back.

User Action:   No user action is required.

LOOK_FOR,      syntax error, looking for <str>, found <str> instead

Explanation:   The syntax expected a specific keyword, but you entered
               another.

User Action:   Check the syntax and reenter the correct keyword.

LOOK_FOR_CON,   <str>

Explanation:   This message is used for listing syntactically
               legitimate alternatives.

User Action:   Consider options from the list.

LOOK_FOR_FIN,   found <str> instead

Explanation:   This terminates the list of syntactically valid
               alternatives and should give you an idea of what has
               happened.

User Action:   Reenter the statement, or use EDIT to correct it.

LOOK_FOR_STT,  syntax error, looking for:

Explanation:   The syntax expected a list of things, list follows.



                                  82

                                                 RDO Facility Messages





User Action:   Consider options from the list.

LOOK_FOR_UNTERM, syntax error, looking for <str>, found <str> instead

Explanation:   This is issued with a RDO-F-BUGCHK because it indicates
               that a severe error has occurred in the syntax tables.

User Action:   Contact your Oracle support representative for
               assistance.  You will need to record the exact command
               line as typed (use EDIT to write it to a file).  Then
               consider finding a workaround.

LRSABORTED,    AIJ Log Roll-Forward Server terminated abnormally

Explanation:   The LRS process has failed.

User Action:   Examine the database monitor log file and any
               SYS$SYSTEM:*LRSBUG.DMP bugcheck dump files for more
               information.

LRSNOOUT,      AIJ Log Roll-Forward Server does not have an output
               file

Explanation:   The AIJ Log Roll-Forward Server process does not have
               an output file associated with it.

User Action:   Use the /OUTPUT qualifier to specify an output filename
               when database replication is started on the standby
               database.

LRSSHUTDN,     AIJ Log Roll-Forward Server being shutdown

Explanation:   The LRS process is in final phase of being shutdown.

User Action:   Try starting Hot Standby after the AIJ Log Roll-Forward
               server has completely stopped execution.

MAXFLDPRTSTR,  maximum number of fields in a print star relation is
               <num>

Explanation:   You used a PRINT <context variable>.* for a relation
               that has too many fields.

User Action:   Name the fields explicitly in the PRINT statement.

MAXLINLEN,     maximum allowed line_length is <num> bytes

Explanation:   You entered a line length that exceeds the limit.

User Action:   Choose a smaller length.





                                  83

RDO Facility Messages





MAXNESEXC,     maximum statement nesting level is exceeded

Explanation:   You exceeded the maximum nesting of FOR and
               START_STREAM statements.

User Action:   Reduce the nesting level.

MAXRELEXC,     maximum number of relations in an RSE has been exceeded

Explanation:   You exceeded the maximum number of relations in an RSE.
               There are too many CROSS clauses.

User Action:   Reduce the number of CROSS expressions.

MAXVOLLABEXC,  maximum size of volume label is <num>

Explanation:   You entered a name for a volume label that exceeds the
               limit for a journal file name.

User Action:   Choose a smaller name.

MFDBONLY,      operation is not allowed on single-file databases

Explanation:   An attempt was made to modify a single-file database in
               such a way that the root file would need to be
               expanded.  This type of change is not permitted for
               single-file databases.  Examples of database
               modifications that cause this error include the
               following:  reserving after-image journals or storage
               areas, adding or deleting storage areas, or changing
               the number of nodes or users.

User Action:   If you want to create a multifile database from a
               single-file database, use the EXPORT and IMPORT
               statements.

MISMMORDD,     missing either month or day field in date string

Explanation:   The date string must contain the month and day field.
               Otherwise, it will not be converted to the DATE data
               type.

User Action:   Re-enter the DATE data item and specify both the month
               and day fields.

MONFLRMSG,     failure message received from the monitor

Explanation:   An error happened in the monitor process.  The user
               process received the error message.

User Action:   Examine the monitor log on the node where the user



                                  84

                                                 RDO Facility Messages





               program was running to see messages relating to the
               monitor error.

MONMBXOPN,     monitor is already running

Explanation:   The monitor has already been started by another user.

User Action:   No action is required.

MONSTOPPED,    database monitor process is being shut down

Explanation:   The request you made could not be completed because the
               database monitor process is being shut down.

User Action:   Examine the database monitor log file
               (SYS$SYSTEM:*MON.LOG) for more information.

MULSPECATR,    attribute is specified redundantly

Explanation:   You specified a field attribute more than once.
               Because Oracle Rdb cannot determine which attribute to
               use, it rejects it.

User Action:   Respecify the data definition statement without the
               redundant clauses.

MUSINVPATH,    cannot DEFINE FROM CDD unless database invoked by
               pathname

Explanation:   You requested that a field or relation be defined from
               the CDD but no CDD has been attached via an INVOKE by
               PATHNAME.

User Action:   INVOKE the database by PATHNAME, then respecify the
               definition.

MUSTRECDB,     database must be closed or recovered

Explanation:   The operation can be done only on databases that are
               closed and recovered.

User Action:   Use the CLOSE command if an OPEN was performed.
               Recovery, if required, can be forced by opening the
               database.  If other users are accessing the database,
               you must wait for them to finish.

MVRELABSNT,    no MOVE RELATION clause is specified in an EXTRACTION
               ROLLUP transfer

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have not specified any MOVE RELATION



                                  85

RDO Facility Messages





               clause.

User Action:   Since a MOVE RELATIONS ALL clause is not allowed in
               this context, you have to explicitly specify the MOVE
               RELATION clauses.  Reenter the DEFINE TRANSFER
               statement by specifying the MOVE RELATION clauses
               explicitly.

NEEDSNOEXTEND, area <str> already has <num> page(s)

Explanation:   The extension of the specified storage area was
               trivial, as the number of pages before was exactly
               same.

User Action:   Check page count of the current area allocation.  (If
               it should differ)

NETACCERR,     error <str> <str> network <str>

Explanation:   A network-access error occurred.

User Action:   Examine the secondary message for more information.

NOAGGALL,      aggregate expressions are not allowed in MOVE RELATION
               clauses

Explanation:   You entered a MOVE RELATION clause that contained an
               aggregate expression.  Only an operator, literal value,
               or field name are allowed in a MOVE RELATION clause.

User Action:   Check the Replication Option for Rdb Handbook or the
               RDO Reference Manual for details on the MOVE RELATION
               clause.  Reenter the DEFINE TRANSFER statement with a
               correct MOVE RELATION clause.

NOAIJDEF,      no default after-image filename available

Explanation:   A default after-image journal file name cannot be
               formed, because no journal file name is presently in
               the database root.

User Action:   Enable after-image journaling, and supply a name for
               the after-image journal.

NOAIJENB,      cannot enable after-image journaling without any AIJ
               journals

Explanation:   An attempt was made to enable AIJ journaling although
               no AIJ journals exist.

User Action:   Create one or more AIJ journals BEFORE enabling AIJ



                                  86

                                                 RDO Facility Messages





               journaling.

NOAIJREM,      cannot remove AIJ journal without disabling journaling
               first

Explanation:   An attempt was made to remove the last AIJ journal.
               The last AIJ journal may be removed only IF AIJ
               journaling has been previously disabled.

User Action:   Disable AIJ journaling first.

NOAIJSERVER,   database replication server is not running or running
               on other node

Explanation:   The database replication server process is not running
               on the standby node specified, or has abnormally
               terminated.  There may also be a problem with the
               mailbox used to communicate with the database
               replication server.

User Action:   Check the system to determine whether or not the
               database replication server process is actually running
               on your system.  Check the use of cluster aliases, as
               the replication connection may have been attempted on
               another node of the designated cluster.  If the
               database replication server process does not appear to
               be running, have your database administrator start the
               replication server, and try again.  If the database
               replication server process appears to be running
               properly, then the problem may be related to the
               mailbox by which user processes communicate with the
               replication server process.  Make sure the "server
               name" specified for both the live and standby databases
               logical are unique and identical.  On VMS platforms,
               the "server name" is used to create a logical of the
               same name that resides in a logical name table
               accessible to all users, typically the
               LNM$PERMANENT_MAILBOX name table.  If the replication
               server process abnormally terminated, a bugcheck dump
               will normally be produced.  Search the bugcheck dump
               for a string of five asterisks (*****) using the
               SEARCH/WINDOW command.  You will see a line with a
               format similar to this:  ***** Exception at <address> :
               <database module name> + <offset>
               %facility-severity-text, <error text> The exception
               line will be followed by one or more additional errors
               that will help you to determine what caused the
               replication server process to fail.  Typically, the
               problem is caused by insufficient quotas or system
               resources.  However, other possible causes include
               misdefined or undefined filename logicals.  Depending



                                  87

RDO Facility Messages





               on the cause of the problem, take the appropriate
               action.  If you are uncertain of what to do, contact
               your Oracle support representative for assistance.

NOAIJSLOTS,    no more after-image journal slots are available

Explanation:   The number of after-image journals that can be created
               is "reserved" in advance.  An attempt has been made to
               create more journals than the number reserved.

User Action:   Either remove an existing AIJ file or reserve more AIJ
               slots before creating additional journals.

NOANYALL,      ANY and UNIQUE are not allowed in a MOVE RELATION
               clause

Explanation:   You entered a MOVE RELATION clause containing ANY or
               UNIQUE.  Only an operator, literal value, or field name
               are allowed in a MOVE RELATION clause.

User Action:   Check the Replication Option for Rdb Handbook or the
               RDO Reference Manual for details on the MOVE RELATION
               clause.  Reenter the DEFINE TRANSFER statement with a
               correct MOVE RELATION clause.

NOAREASLOTS,   no more storage area slots are available

Explanation:   The number of storage areas that can be created is
               "reserved" in advance.  An attempt has been made to
               create more storage areas than the number reserved.

User Action:   Either delete an existing storage area, or reserve more
               storage area slots before creating the area(s).

NOAUDITSERVER, VMS AUDIT_SERVER process is not running on this system

Explanation:   You attempted to generate a database audit record;
               however, the VMS AUDIT_SERVER process is not running on
               this system.

User Action:   Restart the VMS AUDIT_SERVER process.

NOCCHSLOTS,    no more record cache slots are available

Explanation:   The number of record caches that can be added is
               "reserved" in advance.  An attempt has been made to add
               more record caches than the number reserved.

User Action:   Either delete an existing record cache definition or
               reserve more slots before creating the caches(s).





                                  88

                                                 RDO Facility Messages





NOCDD,         there is no CDD on this system, specify a filename on
               the DATABASE command

Explanation:   Because there is no CDD running on this system, you
               cannot invoke a database using a path name.

User Action:   Invoke the database with the database file name.

NOCDDUPDAT,    database invoked by filename, the CDD will not be
               updated

Explanation:   (In RDO or Rdb$INTERPRET) You issued a data definition
               statement after invoking by file name.

User Action:   This is a warning.  You can roll back and invoke the
               database by specifying the path name.  This ensures
               that data definitions are updated both in the data
               dictionary and in the database itself.

NOCHAR,        no character after '' in pattern

Explanation:   A MATCH operation was in progress and the pattern was
               exhausted with the pattern quote character as the last
               character in the pattern.

User Action:   Rewrite the expression in error to have the proper
               format.

NOCMPBYRES,    computed field <str> in relation <str> not IMPORTed

Explanation:   You specified a computed field in your database that
               could not be imported.  Perhaps the field references
               other fields and relations that were deleted from the
               database by an older version of the software that would
               have permitted such a thing.

User Action:   You must investigate the problem further.  The relation
               should have been properly imported except for the
               listed field.

NOCOLRES,      unable to IMPORT collating sequence <str>

Explanation:   This collating sequence could not be imported -- see
               the message that follows.

User Action:   Correct the problem and try the operation again.

NOCONGET,      the concatenate operator cannot be used within a GET
               statement

Explanation:   The concatenate operator may not be used within a GET



                                  89

RDO Facility Messages





               statement.

User Action:   You must do the concatenation outside of Oracle Rdb
               statements.

NOCONRES,      unable to IMPORT constraint <str>

Explanation:   Could not import this constraint -- see the message
               that follows.

User Action:   Correct the problem and retry the operation.

NOCREMBX,      can't create mailbox

Explanation:   An error occurred when you attempted to create a
               mailbox.  See the secondary message for more
               information.

User Action:   Correct the condition and try again.

NODATRES,      remaining data for this relation will be ignored

Explanation:   An error occurred while you attempted to store the
               data; see the following message.

User Action:   Correct the problem and retry the operation.

NODBHALW,      database handles are not allowed in a MOVE RELATION
               clause

Explanation:   You specified a database handle for the record
               selection expression (RSE) in a MOVE RELATION clause.
               Inside a MOVE RELATION clause, database handles are not
               allowed for the RSE.

User Action:   Reenter the DEFINE TRANSFER statement omitting the
               database handle name.

NODBHAN,       a database handle may not be specified on this
               statement

Explanation:   You specified a database handle on a statement that
               either does not or can not use one.

User Action:   Remove the handle.

NODBK,         <num>:<num>:<num> does not point to a data record

Explanation:   An attempt was made to fetch a record by its
               database-key value, but the record has been deleted.





                                  90

                                                 RDO Facility Messages





User Action:   Correct the condition and try again.

NODBKALL,      database key references are not allowed in a MOVE
               RELATION clause

Explanation:   You entered a MOVE RELATION clause that contained a
               database key or a host variable.  Only an operator,
               literal value, or field name are allowed in a MOVE
               RELATION clause.

User Action:   Check the Replication Option for Rdb Handbook or the
               RDO Reference Manual for details on the MOVE RELATION
               clause.  Reenter the DEFINE TRANSFER statement with a
               correct MOVE RELATION clause.

NODBNAME,      a database name was not specified on a DATABASE command

Explanation:   You issued an INVOKE DATABASE statement that did not
               specify a database by file specification or data
               dictionary path name.

User Action:   Check the syntax of the INVOKE DATABASE statement.

NODEVDIR,      filename does not include device and directory

Explanation:   The file you specified did not include a device and
               directory.

User Action:   For maximum protection, you should always include a
               device and directory in the file specification,
               preferably one that is different from the database
               device.

NODISTBATU,    attempt to start a distributed transaction with
               BATCH_UPDATE

Explanation:   You specified attributes which cannot be used together,
               for example, batch update and distributed transaction.

User Action:   Specify the START_TRANSACTION statement again without
               the conflicting clauses.

NODPRIRES,     Unable to import database ANSI privileges for <str>

Explanation:   RDO could not import these ANSI privileges; see the
               message that follows.

User Action:   Correct the problem and try the operation again.

NODUPLIVIEW,   view <str> cannot be specified more than once in a
               transfer definition



                                  91

RDO Facility Messages





Explanation:   You have specified a view name in both a
               move-relations-clause and in a move-views-clause.

User Action:   Reenter the DEFINE TRANSFER statement by specifying the
               view either in a move-relations-clause or in a
               move-views-clause but not in both.

NOENTRYPT,     no entry point

Explanation:   There is no entry point for the routine in the
               shareable image.

User Action:   Make sure you are in the right Oracle Rdb environment.

NOEUACCESS,    unable to acquire exclusive access to database

Explanation:   Exclusive access to the database was not possible.
               Therefore, the requested database operation was not
               performed.

User Action:   Try again later.

NOEXTCUR,      cannot extract, AIJ file <str> is the current AIJ

Explanation:   The current AIJ file cannot be extracted.

User Action:   Use a backup AIJ file.

NOEXTLMNOENA,  cannot extract - AIJ file <str> does not have LogMiner
               enabled

Explanation:   This AIJ file came from a database that did not have
               LogMiner enabled at the time the AIJ file was created.

User Action:   No user action is required.  This AIJ file cannot be
               extracted.

NOEXTNOQUIET,  cannot extract - AIJ file <str> backed up via a
               no-quiet-point backup

Explanation:   An AIJ file, which was backed up with a no-quiet-point
               backup, cannot beextracted, because a no-quiet-point
               backup can leave incomplete transactions in an AIJ
               file.  AIJ extraction cannot handle incomplete
               transactions within an AIJ file.

User Action:   No user action.  This AIJ file cannot be extracted.

NOEXTOPT,      cannot extract - AIJ file <str> is optimized

Explanation:   An optimized AIJ file cannot be extracted.



                                  92

                                                 RDO Facility Messages





User Action:   No user action is required.  This AIJ file cannot be
               extracted.

NOEXTPRVNOQUIET, cannot extract - AIJ file <str> had its previous AIJ
               file backed up via a no-quiet-point backup

Explanation:   An AIJ file for which the previous AIJ file was backed
               up with a no-quiet-point backup, cannot be extract.  A
               no-quiet-point backup can leave incomplete transactions
               in an AIJ file, and AIJ extraction cannot handle
               incomplete transactions within an AIJ file.

User Action:   No user action is required.  This AIJ file cannot be
               extracted.

NOEXTUNRES,    cannot extract, AIJ file <str> has unresolved
               transactions

Explanation:   The AIJ file being extracted has unresolved distributed
               transactions.  AIJ extraction cannot handle unresolved
               transactions, so it must abort.

User Action:   Use a complete AIJ file with no unresolved distributed
               transactions.

NOFLDRES,      unable to IMPORT field <str>

Explanation:   Could not import this field.  See the following
               message.

User Action:   Correct the problem and retry the operation.

NOFPRIRES,     Unable to import ANSI privileges on field <str>.<str>
               for <str>

Explanation:   RDO could not import these ANSI privileges -- see the
               message that follows.

User Action:   Correct the problem and try the operation again.

NOFSTINREPT,   FIRST clause is not allowed in MOVE RELATION clause of
               a REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have entered a FIRST clause.

User Action:   Reenter the DEFINE TRANSFER statement without the FIRST
               clause in the MOVE RELATION clause.

NOIDXRES,      unable to IMPORT index <str>





                                  93

RDO Facility Messages





Explanation:   Could not import this index.  See the following
               message.

User Action:   Correct the problem and retry the operation.

NOIOCHAN,      no more I/O channels available on system

Explanation:   The process has attempted to exceed the number of I/O
               channels that can be assigned at one time; this value
               is "per node".

User Action:   Check the VMS SYSGEN parameter CHANNELCNT to ensure
               that it is large enough to properly service the
               application.

NOITEMDEF,     unable to define item from command line

Explanation:   Could not define an item from the command line.  See
               the following message.

User Action:   Correct the problem and retry the operation.

NOLOCKSOUT,    no locks on this node with the specified qualifiers

Explanation:   No locks were found on the current node that match the
               specified command qualifiers.  This usually indicates
               that either no monitors are active on this node, or no
               databases are currently being accessed on this node.

User Action:   If databases are active on the node, try using a less
               restrictive set of command-qualifiers.

NOMAPRES,      unable to IMPORT storage map <str>

Explanation:   Could not import this storage map.  See the following
               message.

User Action:   Correct the problem and retry the operation.

NOMLTIMV,      attempt to move the relation <str> multiple times

Explanation:   You attempted to specify the same relation name more
               than once in the MOVE clause of a DEFINE TRANSFER
               statement.  In a DEFINE TRANSFER statement, you can not
               move the same relation more than once.

User Action:   Reenter the DEFINE TRANSFER statement omitting the
               duplicate MOVE RELATION clause.

NOMLTIMVIEW,   attempt to move the view <str> multiple times





                                  94

                                                 RDO Facility Messages





Explanation:   You attempted to move the named view more than once in
               a DEFINE TRANSFER statement.  This action is not
               permitted.

User Action:   Reenter the DEFINE TRANSFER statement, specifying each
               view only once.

NOMONHOMEDIR,  monitor home directory is not valid

Explanation:   The directory from which the monitor was invoked is no
               longer valid.  Typically, this occurs when the monitor
               is invoked by the installation IVP procedure, which
               subsequently deletes the invocation directory.
               However, this can also occur during day-to-day
               operations whenever directories are deleted.  When the
               monitor home directory does not exist, the monitor is
               unable to invoke other server processes, such as the
               database recovery process ("DBR") or the AIJ Backup
               Server ("ABS") to name a few.  When the monitor home
               directory does not exist, the server processes will be
               unable to create temporary work files.

User Action:   Stop the monitor, and restart it from a valid
               directory.

NOMONITOR,     database monitor is not running

Explanation:   The database monitor process is not running or has
               abnormally terminated.  There may also be a problem
               with the mailbox used to communicate with the database
               monitor.

User Action:   Check the system to determine whether or not the
               database monitor process is actually running on your
               system.  If the database monitor process does not
               appear to be running, have your database administrator
               start the monitor, and try again.  If the database
               monitor process appears to be running properly, then
               the problem may be related to the mailbox by which user
               processes communicate with the monitor process.  Make
               sure the logical <fac>$MAILBOX_CHANNEL resides in a
               logical name table accessible to all users, typically
               the LNM$PERMANENT_MAILBOX name table.  If the monitor
               abnormally terminated, a bugcheck dump will normally be
               written to the monitor log.  Search the monitor log for
               a string of five asterisks (*****) using the
               SEARCH/WINDOW command.  You will see a line with a
               format similar to this:  ***** Exception at <address> :
               <database module name> + <offset>
               %facility-severity-text, <error text> The exception
               line will be followed by one or more additional errors



                                  95

RDO Facility Messages





               that will help you to determine what caused the monitor
               process to fail.  Typically, the problem is caused by
               insufficient quotas or system resources.  However,
               other possible causes include misdefined or undefined
               filename logicals.  Depending on the cause of the
               problem, take the appropriate action.  If you are
               uncertain of what to do, contact your Oracle support
               representative for assistance.

NOMOREGB,      <num> global buffers not available to bind; <num> free
               out of <num>

Explanation:   Your attempt to bind to the database failed because
               there are not enough global buffers to allow your
               process to bind to the database.

User Action:   There are four ways to alleviate this problem.  1)Try
               to bind to the same database on another node, if you
               are using a VAXcluster.  2)Wait untill another user
               unbinds from the database and retry the bind.
               3)Increase the number of global buffers used for the
               database.  4)Decrease the maximum number of global
               buffers any one user can use, in order to allow more
               users to bind to the database.  Please see your DBA for
               help.

NOMVRALL,      MOVE RELATIONS ALL clause is not allowed in an
               EXTRACTION ROLLUP transfer

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have specified a MOVE RELATIONS ALL
               clause.

User Action:   Reenter the DEFINE TRANSFER statement by specifying
               each relation explicitly in a MOVE RELATION clause.

NOMVVROL,      MOVE VIEWS clause is not allowed in an EXTRACTION
               ROLLUP transfer

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have specified a MOVE VIEWS clause.

User Action:   Reenter the DEFINE TRANSFER statement without the MOVE
               VIEWS clause.

NONODE,        no node name is allowed in the file specification

Explanation:   A node name was found in the file specification.  Node
               names cannot be used.

User Action:   Use a file name without a node specification.



                                  96

                                                 RDO Facility Messages





NOOPTCMTJRNL,  cannot optimize -- commit-to-journal optimization is
               enabled

Explanation:   The 'commit-to-journal' database parameter is enabled.
               When this parameter is enabled, AIJ optimization cannot
               be performed.

User Action:   Use the original, non-optimized AIJ file if needed for
               recovery.  As an alternative, disable the
               commit-to-journal feature.

NOOPTCUR,      cannot optimize -- AIJ file <str> is the current AIJ
               file

Explanation:   The current AIJ file cannot be optimized, because the
               optimized AIJ file would not be equivalent to the
               current AIJ file if more journaling was done after
               optimization.

User Action:   Start a new AIJ file, and then optimize the AIJ file in
               question.

NOOPTNOQUIET,  cannot optimize -- AIJ file <str> backed up via a
               no-quiet-point backup

Explanation:   An AIJ file, which was backed up with a no-quiet-point
               backup, cannot be optimized, because a no-quiet-point
               backup can leave incomplete transactions in an AIJ
               file.  AIJ optimization cannot handle incomplete
               transactions within an AIJ file.

User Action:   No user action.  This AIJ file cannot be optimized.

NOOPTOPT,      cannot optimize -- AIJ file <str> is already optimized

Explanation:   An optimized AIJ file cannot be optimized again.

User Action:   No user action is required.

NOOPTPRVNOQUIET, cannot optimize -- AIJ file <str> had its previous
               AIJ file backed up via a no-quiet-point backup

Explanation:   An AIJ file for which the previous AIJ file was backed
               up with a no-quiet-point backup, cannot be optimized.
               A no-quiet-point backup can leave incomplete
               transactions in an AIJ file, and AIJ optimization
               cannot handle incomplete transactions within an AIJ
               file.

User Action:   No user action is required.  This AIJ file cannot be
               optimized.



                                  97

RDO Facility Messages





NOOPTUNRES,    cannot optimize -- AIJ file <str> has unresolved
               transactions,

Explanation:   The AIJ file being optimized has unresolved distributed
               transactions.  AIJ optimization cannot handle
               unresolved transactions, so it must abort.

User Action:   Use the original, non-optimized AIJ file if needed for
               recovery.

NOPARAMETER,   SHOW command permits no parameters

Explanation:   The collating sequence could not be retrieved -- see
               the message that follows.

User Action:   Correct the problem and try the operation again.

NOPRECOMPSEL,  no precompiler selected

Explanation:   You invoked the preprocessor without specifying the
               language option desired.

User Action:   Specify a switch or file type.

NOPRIV,        no privilege for attempted operation

Explanation:   You attempted an operation that requires VMS
               privileges, and you do not have those privileges
               enabled.

User Action:   Examine the secondary message for more information.

NOPRVMVIEW,    insufficient privilege to transfer the view <str>

Explanation:   You attempted to transfer the named view without READ
               privilege on the view.  You must have READ privilege on
               the view to be able to transfer the view in a DEFINE
               TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement excluding the
               named view.  Check the RDO Reference Manual for details
               on PROTECTION statements.

NOPRVMVREL,    insufficient privilege to transfer the relation <str>

Explanation:   You specified a relation for which you do not have READ
               privilege.  You must have READ privilege on the
               relation to transfer the relation in a DEFINE TRANSFER
               statement.

User Action:   Reenter the DEFINE TRANSFER statement excluding the



                                  98

                                                 RDO Facility Messages





               named relation.  Check the RDO Reference Manual for
               details on PROTECTION statements.  Also consult your
               database administrator.

NOPRVREPLI,    insufficient privilege to define a replication transfer

Explanation:   You attempted to define a replication transfer without
               DEFINE privilege on the source database.  To define a
               replication transfer, you must have DEFINE privilege on
               the source database.

User Action:   Check the RDO Reference Manual for details on
               PROTECTION statements.  See your database administrator
               to obtain DEFINE privilege.

NOPRVROLMVR,   insufficient privilege to transfer the relation
               <str>.<str>

Explanation:   You specified a relation for which you do not have READ
               privilege in the specified database.  You must have
               READ privilege on the relation to transfer the relation
               in a DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement excluding the
               named relation.  Check the RDO Reference Manual for
               details on PROTECTION statements.  Also consult your
               database administrator.

NOREDINREPT,   REDUCE clause is not allowed in MOVE RELATION clause of
               a REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have entered a REDUCE clause.

User Action:   Reenter the DEFINE TRANSFER statement without the
               REDUCE clause in the MOVE RELATION clause.

NORELRES,      unable to IMPORT relation <str>

Explanation:   Could not import this relation.  See the following
               message.

User Action:   Correct the problem and retry the operation.

NOREMVER,      remote node or version number is not allowed in a log
               file name

Explanation:   You used a node name or a version number in the log
               file specification of a DEFINE TRANSFER statement.

User Action:   Reenter the DEFINE TRANSFER statement using a log file



                                  99

RDO Facility Messages





               specification which contains neither a node name nor a
               version number.

NOREQHAN,      a request handle may not be specified on this statement

Explanation:   You specified a request handle on a statement that does
               not use one.

User Action:   Remove the handle.

NOREQIDT,      reached internal maximum number of simultaneous timer
               requests

Explanation:   All allocated timer request ID slots, used to uniquely
               identify timers, are in use.  Therefore, this timer
               request could not be serviced at this time.

NORPRIRES,     Unable to import ANSI privileges on relation <str> for
               <str>

Explanation:   RDO could not import these ANSI privileges -- see the
               message that follows.

User Action:   Correct the problem and try the operation again.

NORTUPB,       no more user slots are available in the database

Explanation:   The maximum number of users are already accessing your
               database.

User Action:   Try again later.

NOSEGSTRAREA,  segmented string storage area <str> is not defined

Explanation:   You specified a storage area in the SEGMENTED STRING
               STORAGE AREA clause that does not exist.

User Action:   Specify a storage area which is already defined in the
               DEFINE DATABASE statement.

NOSELALL,      SELECT FIELDS ALL clause is not allowed in an
               EXTRACTION ROLLUP transfer

Explanation:   In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have specified a SELECT FIELDS ALL
               clause.

User Action:   Reenter the DEFINE TRANSFER statement by specifying
               each field explicitly in the SELECT FIELDS clause.

NOSEQENT,      sequence id <num> has no valid entry in the root file



                                 100

                                                 RDO Facility Messages





Explanation:   Sequence with the sequence id is present in the
               RDB$SEQUENCES table but does not have a valid entry in
               the root file.  Either the seq is not marked as being
               used in root file or the condition minvalue <= next
               value <= maxvalue is false

NOSEQROW,      sequence id <num> has an entry in the root file but no
               row in RDB$SEQUENCES

Explanation:   Sequence with id indicated has a root file entry but
               not corresponding row in the table RDB$SEQUENCES.

NOSHUTDOWN,    database shutdown not allowed while backup processes
               are active

Explanation:   One or more database or AIJ backup utilities are
               active.  Database shutdown is not permitted while these
               types of utilities are active.

User Action:   Wait for the utilities to complete, or shutdown the
               database using the /ABORT=DELPRC qualifier.

NOSIP,         transaction is not a snapshot transaction

Explanation:   You have already started a transaction that is not a
               snapshot transaction.

User Action:   Use COMMIT or ROLLBACK to terminate your current
               transaction.  Use READY BATCH RETRIEVAL to start a new
               snapshot transaction.

NOSNAPS,       snapshots are not allowed or not enabled for area <str>

Explanation:   Snapshots are not allowed or not enabled for this area.

User Action:   This is a normal situation created by the database
               definition or by a change- or modify-database command.
               Check with your DBA to make sure this situation is
               desirable.

NOSORTINREPT,  SORT clause is not allowed in MOVE RELATION clause of a
               REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have entered a SORT clause.

User Action:   Reenter the DEFINE TRANSFER statement without the SORT
               clause in the MOVE RELATION clause.

NOSTATS,       statistics are not enabled for <str>





                                 101

RDO Facility Messages





Explanation:   An attempt was made to show statistics for a database
               that currently has statistics' collection disabled.

User Action:   Enable statistics and try again.

NOSUCHAIJ,     no such AIJ journal "<str>"

Explanation:   The specified AIJ journal does not exist for the
               database.

User Action:   You may select an AIJ journal using either the AIJ name
               or the default or current AIJ file specification.  The
               list of valid AIJ journals can be obtained by dumping
               the database header information.

NOSUCHDATEFMT, format DATE <num> does not exist

Explanation:   You entered DATE date-number where the logical
               LIB$DATE_FORMAT_nnn does not exist.

User Action:   Contact the system manager to install the date formats.

NOSUCHLANG,    specified language not defined on this system

Explanation:   You entered the SET LANGUAGE statement, but the logical
               name table LNM$LANGUAGE_xxx does not exist.

User Action:   Contact your system manager to make sure everything has
               been set up properly; the language may not be
               supported, or the language may have been spelled
               incorrectly.  The language name cannot be abbreviated.

NOSUCHTIMEFMT, format TIME <num> does not exist

Explanation:   You entered TIME time-number where the logical
               LIB$TIME_FORMAT_nnn does not exist.

User Action:   Contact the system manager to install the date/time
               formats.

NOSUCHUSER,    unknown user "<str>"

Explanation:   An attempt was made to access information with a user
               name unknown to the database (for example, sending mail
               to the monitor or attempting to execute a database
               recovery process (DBR)) or to access information with a
               user name unknown to the operating system (for example,
               no record in the UAF file).

User Action:   Make sure the user name is spelled correctly and has
               been properly identified to either the database or the



                                 102

                                                 RDO Facility Messages





               operating system.  Do not attempt to run DBR from DCL;
               this is not allowed, because the system will
               automatically manage database recovery.  Be sure the
               monitor user name is correctly specified.

NOSUPREPLI,    replication transfer is not supported for this source
               database

Explanation:   You attempted to define a replication transfer on a
               source database which is not an Rdb database.
               Replication transfers can be defined only for Rdb
               databases.  For other databases you can define only
               extraction transfers.

User Action:   If your source database is not an Rdb database, define
               an extraction transfer.

NOTALSAUTO,    AIJ Log Server is not automatically invoked by database
               monitor

Explanation:   In order to initiate database replication on the master
               database, it is required that the AIJ Log Server be
               automatically invoked by the database monitor.

User Action:   Change the AIJ Log Server invocation mode from "MANUAL"
               to "AUTOMATIC".

NOTAVIEW,      <str> is not a view

Explanation:   The name you specified in a MOVE VIEWS clause is not
               the name of a view.

User Action:   Retype the DEFINE TRANSFER command with the correct
               view name.

NOTBOOL,       expression in AND, OR, or NOT was not a Boolean

Explanation:   The Boolean evaluator was processing an expression or
               subexpression of the form "A AND B", "A OR B", or "NOT
               A".  Either the "A" or the "B" expression was not in
               the proper form.  The correct forms are "NOT X", "X EQ
               Y", "X NE Y", "X LT Y", "X GT Y", "X LE Y", "X GE Y",
               "X CONTAINS Y", or "X MATCHES Y".  The operand of NOT,
               and both sides of AND and OR expressions, must be
               Boolean expressions.

User Action:   Rewrite the expression to have the proper format.

NOTDSKFIL,     filename does not specify disk device type

Explanation:   A file name was specified which does not reference a



                                 103

RDO Facility Messages





               disk oriented device type.

User Action:   Check the file name for a proper disk device type.

NOTENUFBUF,    requested number of global buffers (<num>) is more than
               USER LIMIT (<num>)

Explanation:   The user has requested more global buffers than are
               allowed for a single user.

User Action:   Either reduce the number of requested global buffers or
               increase the number of global buffers that a user may
               allocate.  See documentation for descriptions of USER
               LIMIT clause used when creating and/or opening a
               database.

NOTENUFHV,     not enough host variables passed; <num> passed, at
               least <num> used

Explanation:   You did not pass enough host variables to
               RDB$INTERPRET.  For RDB$INTERPRET, there were more
               !VALs in the command string than host variable
               descriptors passed.  If one more host variable is
               detected by the parser than was passed, parsing stops.
               There could be more host variables used than the error
               message specifies.

User Action:   Supply matching number of host variables and !VALs.

NOTEXPSEG,     cannot assign an expression to RDB$VALUE or RDB$LENGTH

Explanation:   Your preprocessor does not support assigning an
               expression value to RDB$VALUE or RDB$LENGTH.

User Action:   You can work around this problem by assigning the value
               of the expression to a temporary variable.  Then assign
               the temporary variable value to RDB$VALUE or
               RDB$LENGTH.

NOTEXTENDED,   area <str> cannot be extended to <num> page(s)

Explanation:   The extension of the specified storage area was not
               possible.  This condition is possible if the specified
               new size is less than the current storage area
               allocation.  This condition can also occur when
               attempting to change the size of a WORM device.

User Action:   Specify a new page count that is larger than the
               current area allocation.

NOTFOUND,      No rows were found for this statement



                                 104

                                                 RDO Facility Messages





Explanation:   No rows were found for an UPDATE or DELETE statement,
               or a query produced an empty table.

User Action:   None, this is a warning message.

NOTIMPLYET,    feature is not implemented yet

Explanation:   You attempted to access a feature that has been planned
               but has not been implemented yet.

User Action:   Avoid this feature.

NOTINRANGE,    value not within specified range of acceptable values

Explanation:   The value of the translated logical name is not in the
               range of acceptable values.

User Action:   Delete the logical name, or redefine it with a value in
               the acceptable range.

NOTIP,         no transaction in progress

Explanation:   You attempted to execute a DML verb, but there is no
               transaction in progress yet.

User Action:   Execute a READY statement before executing any other
               DML statements.

NOTRANAPP,     no transactions in this journal were applied

Explanation:   This journal file contains transactions that cannot be
               applied to the specified backup of the database.

User Action:   Be sure you are using the correct database backup and
               journal file.

NOTREQSTA,     not a request statement.  Can only use request options
               on request statement

Explanation:   You attempted to use a REQUEST_HANDLE or
               TRANSACTION_HANDLE clause in a statement that was not a
               request statement.  Request options are not necessary
               on statements that are not request statements.

User Action:   Put the handle option clause in the request statement.

NOTRGRES,      unable to IMPORT trigger <str>

Explanation:   This trigger could not be imported -- see the message
               that follows.





                                 105

RDO Facility Messages





User Action:   Correct the problem and try the operation again.

NOTROOT,       not a root file

Explanation:   The specified file is not a database root file.

User Action:   Specify a database root file and try again.

NOTSEGSTR,     context variable <str> does not reference a segmented
               string

Explanation:   You attempted to use a context variable with RDB$VALUE
               or RDB$LENGTH, and the context variable does not refer
               to a segmented string field.

User Action:   Use a context variable defined for a segmented string
               with RDB$VALUE and RDB$LENGTH.

NOTSNBLK,      no more user slots are available in the database

Explanation:   The maximum number of users are already accessing your
               database.

User Action:   Try again later.

NOTSYSCONCEAL, non-system concealed device name in filename

Explanation:   A concealed device name must be defined in the system
               logical table.

User Action:   If the device name has to be concealed, then define it
               in the system logical table.

NOT_BOUND,     database is not bound

Explanation:   You have not bound to a database yet, or you have
               unbound the database and have not bound to another one
               yet.

User Action:   Bind to a database before continuing.

NOT_INSTALLED, <str> is not installed

Explanation:   The product is not installed on the system.

User Action:   The named product must be installed before the
               attempted statement can be successfully executed.

NOT_LARDY,     area for <num>:<num>:<num> not in proper ready mode

Explanation:   You attempted to access a logical area for which you



                                 106

                                                 RDO Facility Messages





               have not declared your intentions.

User Action:   Retry a ready operation later.

NOT_READY,     storage area <str> not readied

Explanation:   You attempted to access an area for which you have not
               declared your intentions.

User Action:   If the area is included in your subschema, you can use
               the READY statement to prepare it for processing.

NOT_UPDATE,    storage area <str> not readied in update usage mode

Explanation:   You attempted to modify the contents of an area without
               having declared your intentions.

User Action:   If you have not readied the area yet, you can READY for
               UPDATE.  If you have already readied it, you must abort
               your transaction by executing a ROLLBACK before you can
               READY for UPDATE.

NOUPDCOMP,     can not update computed by field, <str>

Explanation:   You tried to store or modify a COMPUTED BY field.  This
               is not allowed.

User Action:   Restate the update removing the COMPUTED BY field.

NOVIERES,      unable to IMPORT view <str>

Explanation:   Could not import this view -- see the message that
               follows.

User Action:   Correct the problem and retry the operation.

NOVIEWINREPT,  view <str> is not allowed in MOVE RELATION clause of a
               REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have specified a view.

User Action:   Reenter the DEFINE TRANSFER statement without the view
               in the MOVE RELATION clause.  The view definition can
               be moved by specifying the view in the MOVE VIEWS
               clause.

NOWILD,        no wild cards are allowed in the file specification

Explanation:   Wild-card characters ("*" and "%") cannot be used in
               that file specification.



                                 107

RDO Facility Messages





User Action:   Use a file specification without wild-card characters.

NOWORMSPT,     WORM areas are not supported

Explanation:   An attempt was made to declare an area as having the
               WORM attribute.  At this time, there is no longer
               support for this attribute.

User Action:   Contact your Oracle support representative for
               assistance.

NO_CROSEG,     no CROSS clause may be used with a segmented string
               specification

Explanation:   You attempted to use a CROSS clause with a segmented
               string specification.  This is not permitted.

User Action:   Remove the CROSS clause.

NO_FILFND,     file <str> not found for input to the precompiler

Explanation:   You attempted to open a nonexistent file.

User Action:   Check the file specified.  Supply complete file
               specification.

NO_FIRSEG,     no FIRST clause may be used with a segmented string
               specification

Explanation:   You attempted to use a FIRST clause with a segmented
               string specification.  This is not permitted.

User Action:   Remove the FIRST clause.

NO_MORSEG,     there are no more segments in this segmented string

Explanation:   You attempted to print or get a segment from a
               segmented string and the last segment has already been
               read.

User Action:   This is a normal case.  You have retrieved the entire
               segmented string.

NO_PERBLO,     no periods are permitted within a FOR or an ON ERROR
               block

Explanation:   COBOL does not permit periods between the PERFORM and
               END_PERFORM block, or the IF and END_IF block that the
               preprocessor generates.

User Action:   Remove the period from the end of the DML statement



                                 108

                                                 RDO Facility Messages





               within the FOR or ON ERROR block.

NO_REDSEG,     no REDUCED TO clause may be used with a segmented
               string specification

Explanation:   You attempted to use a REDUCED TO clause with a
               segmented string specification.  This is not permitted.

User Action:   Remove the REDUCED TO clause.

NO_SORSEG,     no SORTED BY clause may be used with a segmented string
               specification

Explanation:   You attempted to use a SORTED BY clause with a
               segmented string specification.  This is not permitted.

User Action:   Remove the SORTED BY clause.

NO_SUCH_FIELD, field, <str>, does not exist in this database

Explanation:   You specified a field that does not exist in the
               database.

User Action:   Check database entity definitions for the valid
               database field name.

NO_TXNOUT,     no transaction outstanding

Explanation:   You attempted to terminate a transaction with a COMMIT
               or a ROLLBACK when no transaction was outstanding.

User Action:   Enter a START_TRANSACTION statement before COMMIT or
               ROLLBACK.

NO_WITSEG,     no WITH clause may be used with a segmented string
               specification

Explanation:   You attempted to use a WITH clause with a segmented
               string specification.  This is not permitted.

User Action:   Remove the WITH clause.

NULLNOIND,     tried to store null into host variable with no
               indicator variable

Explanation:   Null values can only be stored in host variables which
               have indicator variables.

User Action:   Add an indicator variable to the host variable
               reference or make sure that no null values can be
               returned to it.



                                 109

RDO Facility Messages





ONLFIRVAR,     only first variable in qualified variable expression

Explanation:   COBOL allows only the first variable in a qualification
               to be an array.  The preprocessors do not recognize the
               arrays of arrays in FORTRAN, COBOL or BASIC.

User Action:   Rewrite the query and check the appropriate reference
               manual.

ONLONEDB,      only one database can be referenced in an RSE or an
               expression

Explanation:   You cannot use database variables from more than one
               database in an RSE or in an expression.  You can,
               however, refer to variables from one database in an
               expression and refer to variables in another database
               in a STORE or a MODIFY statement.  Nested FOR
               statements may refer to different databases in the RSEs
               of each FOR statement.

User Action:   Use separate statements or nested FOR loops for
               multiple database access.

ONLONERED,     only one REDUCE clause can appear in an RSE

Explanation:   You included more than one REDUCED TO clause in the
               RSE.  This is not permitted.

User Action:   Specify all reduce expressions in one reduce list.

ONLONEREQ,     only one request handle may be specified on a STMT

Explanation:   You included more than one REQUEST_HANDLE in your
               statement.  Only one is permitted.

User Action:   Use only one REQUEST_HANDLE.  You may have intended to
               use a TRANSACTION_HANDLE.

ONLONESOR,     only one SORT clause can appear in an RSE

Explanation:   You included more than one SORTED BY clause in your
               RSE.  This is not permitted.

User Action:   Specify all sort expressions in one sort list.

ONLONETRA,     only one transaction handle may be specified on a STMT

Explanation:   You included more than one TRANSACTION_HANDLE in your
               statement.  Only one TRANSACTION_HANDLE is permitted.

User Action:   Use only one TRANSACTION_HANDLE.  You may have intended



                                 110

                                                 RDO Facility Messages





               to use a REQUEST_HANDLE.

ONLONETRN,     only one transaction allowed at a time

Explanation:   You attempted to use more than one transaction.  Only
               one transaction is allowed at a time.  Note that RDO
               does an implicit START_TRANSACTION on the first DML
               statement.

User Action:   A COMMIT or ROLLBACK terminates a transaction.

ONLONEWIT,     only one WITH clause can appear in an RSE

Explanation:   You included more than one WITH clause in the RSE.
               This is not permitted.

User Action:   Specify all Boolean expressions in one WITH clause.

ONLYONEPSECT,  only one PSECT statement per module is supported

Explanation:   You attempted to use more than one PSECT directive per
               module.  The PSECT directive may only be used once per
               module.

User Action:   Decide which PSECT statement is really desired and
               delete all others.

OPENERR,       unable to open <str> as the interchange file

Explanation:   Could not access the Oracle Rdb interchange file (RBR).

User Action:   Correct the problem indicated by subsequent messages
               and retry the operation.

OPERCLOSE,     database operator requested database shutdown

Explanation:   Your program has been terminated because the database
               operator shut down the database you were using.

User Action:   Try again later after the database shutdown is
               complete.

OPERNOTIFY,    system operator notification:  <str>

Explanation:   The indicated message was sent to one of the configured
               system operators.

User Action:   Examine the indicated message and perform the
               appropriate operation.

OPERSHUTDN,    database operator requested monitor process shutdown



                                 111

RDO Facility Messages





Explanation:   Your program has been terminated because the database
               operator shut down the database monitor process.

User Action:   Try again later after the database shutdown is
               complete.

OPRSTK_OVRFLO, operator stack overflow

Explanation:   The internal limit of the parsing operator stack was
               exceeded.

User Action:   Contact your Oracle support representative for
               assistance.

OPTDDLREC,     TSN <num>:<num> contains DDL information that cannot be
               optimized

Explanation:   The identified transaction contains an AIJ record with
               DDL information.  DDL information cannot be optimized
               and forces a flush of the accumulated SORT information.
               Too many of these operations limit the effectiveness of
               the resulting optimized after-image journal and
               decrease the overall optimization performance.

User Action:   No user action is required.

OPTEXCMAX,     TSN <num>:<num> record size <num> exceeds maximum <num>
               record size

Explanation:   The identified transaction contains an AIJ record whose
               size exceeds the maximum specified sort record size.
               During AIJ optimization, fixed-length data records are
               passed to the sort utility.  By default, the size of
               the sort records is 1548 bytes in length, which is also
               the maximum value allowed.  The sort record length
               affects the amount of disk space required to complete
               the AIJ optimization operation.  The size of the record
               passed to the sort utility can be adjusted using the
               <fac>$BIND_OPTIMIZE_AIJ_RECLEN logical.

User Action:   If possible, increase the size of the sort record using
               the <fac>$BIND_OPTIMIZE_AIJ_RECLEN logical.

OPTEXCSRT,     AIJ record count exceeded specified <num> sort
               threshold

Explanation:   The number of AIJ records processed exceeded the
               maximum sort threshold specified by the
               <fac>$BIND_OPT_SORT_THRESHOLD logical name.  This is
               not a fatal error.





                                 112

                                                 RDO Facility Messages





User Action:   None.  Use of the <fac>$BIND_OPT_SORT_THRESHOLD may
               reduce the sort work file disk space required for the
               AIJ optimization operation.  However, this may result
               in a larger output file.

OPTEXCTXN,     TSN <num>:<num> error count exceeded <num> failure
               threshold

Explanation:   The number of AIJ optimize errors exceeded the
               transaction error threshold specified by the
               <fac>$BIND_OPT_TXN_THRESHOLD logical name.  This is not
               a fatal error.

User Action:   None.  The remainder of the transaction contents are
               written directly to the optimized AIJ file.  Use of the
               <fac>$BIND_OPT_TXN_THRESHOLD logical name may actually
               increase the AIJ optimize operation performance as the
               number of required sort operations is reduced.
               However, this may result in a larger output file.

OPTINCONSIS,   optimized AIJ file is inconsistent with the database

Explanation:   The database and/or some areas within the database are
               not consistent with the optimized AIJ file.  The last
               transaction committed to the database and/or to some
               database areas is not the same as the last transaction
               committed to the database at the time the optimized AIJ
               file's original AIJ file was created.  To use an
               optimized AIJ file for recovery, it must be consistent
               with the database and all areas.

User Action:   Use the original, non-optimized AIJ file to do the
               recovery.

OPTNOAREAREC,  cannot do by-area recovery with an optimized AIJ file

Explanation:   A recover-by-area operation was attempted with an
               optimized AIJ file.  Optimized AIJ files do not support
               recovery by area, so the recovery operation was
               aborted.

User Action:   Use the original, non-optimized AIJ file to do the by
               area recovery.

OPTNOUNTILREC, cannot do a /RECOVER/UNTIL with an optimized AIJ file

Explanation:   A recover operation specifying an "until" time is not
               allowed with an optimized AIJ file.  No recovery is
               performed if this condition is specified.

User Action:   Use the original, non-optimized AIJ file to do the



                                 113

RDO Facility Messages





               /RECOVER/UNTIL operation.

OPTRECLEN,     AIJ optimization record length was <num> characters in
               length

Explanation:   During AIJ optimization, fixed-length data records are
               passed to the sort utility.  By default, the size of
               the sort records is 1548 bytes in length, which is also
               the maximum value allowed.  The sort record length
               affects the amount of disk space required to complete
               the AIJ optimization operation.  The size of the record
               passed to the sort utility can be adjusted using the
               <fac>$BIND_OPTIMIZE_AIJ_RECLEN logical.  This message
               indicates the size of the largest AIJ record passed to
               the sort utility that was less than or equal to the
               maximum sort record length.

User Action:   No user action is required.

OPTSRTSTAT,    <str>:  <num>

Explanation:   During optimization operations, statistics are often
               collected to aid the user in tuning.  This message
               displays a single statistic.

OVERFLOW,      data conversion overflow

Explanation:   A loss of information would have occurred on a data
               item transformation.  The operation was not performed.

User Action:   Correct the error and try the operation again.

PAGINCONSIS,   page is inconsistent

Explanation:   An attempt was made to fetch an inconsistent page.
               This page cannot be accessed until it is consistent.

User Action:   Take the proper action to make the page consistent.
               For example, perform a RESTORE/RECOVER operation for a
               data or AIP page, or a REPAIR operation for a SPAM or
               ABM page.

PARSE_STACK_OVERFLOW, parse stack overflow

Explanation:   The internal limits of the parsing stack were exceeded.

User Action:   Contact your Oracle support representative for
               assistance.

PARTDTXNERR,   error when trying to participate in a distributed
               transaction



                                 114

                                                 RDO Facility Messages





Explanation:   The process was unable to participate in the DECdtm
               distributed transaction, because of a DECdtm error.
               This error is returned in the secondary error message.

User Action:   Look at the secondary error message, make the necessary
               correction, and try the operation again.

PATHREQCDD,    a pathname is specified but no CDD is available

Explanation:   The statement entered specifies a CDD pathname, but
               there is no CDD available for use (may not be
               installed).

User Action:   Choose a statement or statement option that does not
               specify a pathname, or check with the system
               administrator to determine why the CDD is not
               available.

PLACENEEDGET,  PLACE operator must fetch data

Explanation:   A PLACE statement has been used without a GET or PRINT
               statement.  PLACE must retrieve something from the
               database, usually a dbkey.

User Action:   Use the GET or PRINT statement to retrive the
               appropriate dbkey.

PREMATURE_EOF, statement is syntactically incomplete

Explanation:   You entered a syntactically incomplete statement.

User Action:   Complete the statement before pressing RETURN.

PREMEOF,       premature end of file encountered in <str>

Explanation:   A premature end-of-file was encountered while reading
               the specified file.

QIOXFRLEN,     data transfer length error - expected <num>, actual
               <num>

Explanation:   The expected data-transfer length was not equal to the
               actual data-transfer length.

User Action:   This is usually caused by a hardware problem.

QUIETPT,       waiting for database quiet point at <time>

Explanation:   The user is waiting for the quiet lock in order to
               force a database quiet point.





                                 115

RDO Facility Messages





User Action:   None.

QUIETPTREL,    released database quiet point at <time>

Explanation:   The database quiet point lock has been released.

User Action:   None.

RCSABORTED,    record cache server process terminated abnormally

Explanation:   A detached record cache server process failed
               abnormally.

User Action:   Examine the database monitor log file and any
               SYS$SYSTEM:*RCSBUG.DMP bugcheck dump files for more
               information.

RCSMANYNODES,  database node count exceeds record cache maximum of "1"

Explanation:   The record cache feature can only be used when
               after-image journaling is enabled, the "Fast Commit"
               feature is enabled, and the maximum node count is set
               to "1".

User Action:   Alter the database to set the maximum database node
               count to "1".

RCSRQSTFAIL,   request to Record Cache Server failed

Explanation:   User submitted a request the RCS process which failed
               either during the submission process or, for
               synchronous requests, possibly during the execution of
               the request.

User Action:   Examine the secondary message(s) or the database
               monitor log file (SYS$SYSTEM:*MON.LOG) or any RCS log
               file in root file's directory or any
               SYS$SYSTEM:*RCSBUG.DMP bugcheck dump files for more
               information.

RDORECOBS,     RECOVER command is obsolete, please use RMU/RECOVER

Explanation:   You requested that an RDO RECOVER statement be
               executed.  This statement is no longer supported in
               RDO.

User Action:   Use the RMU/RECOVER command instead.

READ_ONLY,     read-only area <str> must be readied in RETRIEVAL mode
               only





                                 116

                                                 RDO Facility Messages





Explanation:   A read-only area can be readied in RETRIEVAL mode only.

User Action:   Ready this area for retrieval or make the area
               read-write.

REANOWRT,      a READ_ONLY transaction cannot specify write locks

Explanation:   You specified a READ_ONLY transaction and a relation
               was locked for write access.  This is a conflict of
               access modes.

User Action:   Start a transaction READ_WRITE or use a read lock.
               Note, the default is always READ_ONLY.

REBUILDSPAMS,  SPAM pages should be rebuilt for logical area <str>

Explanation:   Modifications have been made to the logical area
               parameters that may have made the SPAM thresholds
               inaccurate.  The RMU utility should be used to rebuild
               the SPAM pages for the logical area.

RECFAILED,     fatal, unexpected roll-forward error detected at AIJ
               record <num>

Explanation:   A fatal, unexpected error was detected by the database
               management system during the roll forward of an AIJ
               file.  This typically is caused by a corrupt AIJ file
               or by applying an AIJ file out of sequence.

User Action:   Contact your Oracle support representative for
               assistance.  Note that the indicated AIJ record number
               can be used to quickly locate the offending information
               in the AIJ journal using the appropriate
               DUMP/AFTER_JOURNAL/START=XXX command; it is recommended
               that when dumping the AIJ file, you use a starting
               record number that is several records prior to the
               indicated record, because the actual cause of the
               problem may be in preceding AIJ records.

RECLASTTSN,    last successfully processed transaction was TSN
               <num>:<num>

Explanation:   A fatal, unexpected error was detected by the database
               management system during the roll forward of an AIJ
               file.  This message indicates the "transaction sequence
               number" of the last transaction successfully processed
               by the AIJ roll-forward utility.

User Action:   Contact your Oracle support representative for
               assistance.  Information concerning the identified
               transaction TSN can be obtained by dumping the AIJ



                                 117

RDO Facility Messages





               journal, using the DUMP/AFTER_JOURNAL command.

RECUNTIL,      work-around:  roll forward AIJ using /UNTIL="<time>"
               qualifier

Explanation:   A fatal, unexpected error was detected by the database
               management system during the roll forward of an AIJ
               file.  However, one or more transactions were
               successfully rolled forward up to the date indicated in
               the message.  Using the /UNTIL qualifier on the
               roll-forward command produces a database that is
               transaction consistent up to the indicated date.

User Action:   Issue the AIJ roll-forward command using the indicated
               /UNTIL qualifier.

REFREMONITROBS, REFRESH MONITOR and START MONITOR command are
               obsolete, please use RMU/MONITOR REOPEN

Explanation:   The START and REFRESH MONITOR command is no longer
               available in RDO.

User Action:   Use the RMU/MONITOR REOPEN command, which provides the
               same functionality.

REFSEGSTR,     reference to segmented string <str> must use RDB$VALUE
               or RDB$LENGTH

Explanation:   You attempted to use a context variable that was
               defined in a segmented string RSE with a field name
               that was neither RDB$VALUE or RDB$LENGTH, or you
               attempted to ERASE a segmented string segment using
               that context variable.  You can only use RDB$VALUE or
               RDB$LENGTH to refer to a segmented string contents and
               individual segments can not be erased using RDO or
               RDBPRE.

User Action:   Use either <context-variable>.RDB$VALUE or
               <context-variable>.RDB$LENGTH, where context variable
               is the one defined in the segmented string RSE.  Or
               erase an entire segmented string by assigning zero to
               the segmented string field name.

RELAMBIG,      the relation <str> was not qualified and is in multiple
               databases

Explanation:   You must qualify the database with relation names when
               accessing more than one database containing that
               relation.

User Action:   Make sure the INVOKE statements include qualifiers, and



                                 118

                                                 RDO Facility Messages





               retype the query using the appropriate qualifier.

RELNOTDEF,     relation <str> is not defined in database

Explanation:   The specified relation does not exist in the current
               database.

User Action:   Invoke the correct database.  Spell the relation name
               correctly.  You may have specified a name other than a
               relation name.

REL_EXISTS,    relation <str> already exists in this database

Explanation:   You attempted to define a relation with the name of an
               existing relation.

User Action:   Choose a different name.

REMNOTALW,     a remote source database is not allowed to be
               replicated

Explanation:   You were attached to a database which is on a remote
               node when you tried to define a replication mode
               transfer using the DEFINE TRANSFER statement.

User Action:   Define an extraction transfer instead.

REORGONLCHSM,  REORGANIZE may only be used in CHANGE STORAGE MAP

Explanation:   You specified the REORGANIZE keyword in a statement
               other than the CHANGE STORE MAP statement.

User Action:   Specify the REORGANIZE keyword only in the CHANGE
               STORAGE MAP statement.  There is no REORGANIZE keyword
               in the DEFINE STORAGE MAP statement.

REQCANCELED,   request canceled

Explanation:   The executing request was canceled.  This can occur if
               a query limit was specified and exceeded, or the
               request was canceled by an external source such as the
               RMU or DBO /SHOW STATISTICS utility.

RESABORT,      terminating the IMPORT operation

Explanation:   The IMPORT operation has been aborted; see the messages
               preceding this one.

User Action:   None.

RESERVED_WORD, <str> is a keyword; it cannot be used as a name



                                 119

RDO Facility Messages





Explanation:   You entered a keyword where a name was expected.

User Action:   Specify a unique name instead of the keyword.

RESTART,       restarted recovery after ignoring <num> committed
               transaction(s)

Explanation:   The specified number of committed transactions did not
               apply to this database root.  All subsequent
               transactions were applied.

User Action:   None.

RETMODSPC,     only one retain mode may be specified for a transaction

Explanation:   You specified two transaction modes in a
               START_TRANSACTION statement.

User Action:   Specify only one transaction mode in a
               START_TRANSACTION statement.

ROOMAJVER,     root major version is incompatible with the software
               version

Explanation:   Your database was created with an incompatible version
               of the software.

User Action:   Your database cannot be used with the version of the
               software you have installed on your machine.

ROOTMAJVER,    database format <num>.<num> is not compatible with
               software version <num>.<num>

Explanation:   Your database was created with an incompatible version
               of the software.

User Action:   Your database cannot be used with the version of the
               software you have installed on your machine.

ROOT_CORRUPT,  database has been corrupted and must be restored from
               backup

Explanation:   The database has been corrupted and must be restored
               from a full database backup.

User Action:   Restore the database from the latest full database
               backup, apply any incremental backups that might exist,
               and roll-forward ("recover") the corresponding
               after-image journal.

ROOVERLAP,     root block <num> is multiply allocated to data



                                 120

                                                 RDO Facility Messages





               structures "<str>" and "<str>"

Explanation:   A blocks in the database root file is assigned to more
               than one root file data structure.

User Action:   Restore database from backups and recover the database
               from journals.

RSENOTSEG,     the RSE in a START_SEGMENTED_STRING does not reference
               a segmented string

Explanation:   The START_SEGMENTED_STRING record selection expression
               refers to a real record stream instead of a segmented
               string field.  START_SEGMENTED_STRING may refer only to
               segmented strings.

User Action:   Use a segmented string field in the RSE portion of the
               START_SEGMENTED_STRING command.

RTAIJMSMTCH,   AIJ references root file "<str>" - expected "<str>"



RTOCMDILL,     requested command is not supported in runtime-only or
               remote environment

Explanation:   You issued a statement that is not supported in a
               run-time-only or remote system (such as DEFINE FIELD).

User Action:   You may have to move your database to a system that has
               a development system to do this task.

RUJDEVDIR,     RUJ filename "<str>" does not include a
               device/directory

Explanation:   The RUJ filename you specified did not include a device
               and directory.

User Action:   For maximum protection, you should always include a
               device and directory in the file specification,
               preferably one that is different from the database
               device.

RUJTOOBIG,     RUJ file size may not exceed 8,000,000 disk blocks

Explanation:   The transaction attempted to extend the RUJ file size
               beyond 8 million disk blocks.  This transaction will be
               rolled back (note that due to the size of the RUJ file,
               the rollback operation may take a very long time).

User Action:   Reduce the number of records being modified by the
               transaction; commit more often or use a BATCH UPDATE



                                 121

RDO Facility Messages





               transaction.

SAMEAREANAME,  storage area name <str> is already in use

Explanation:   The storage area name that is being created is already
               existing.  An attempt has been made to create another
               storage area with the same name.

User Action:   Use different storage area name to avoid conflict.

SAMROOTMATCH,  identical root file "<str>" specified

Explanation:   The specified master and replicated database root file
               names are identical; this is not allowed.

User Action:   Specify the rootfile name of a replicated database that
               was created from the backup of the master database.

SCALEOPSBASIC, cannot use scaled operands in BASIC operations

Explanation:   You attempted to perform arithmetic operations on
               scaled data types.  This is not supported in the BASIC
               preprocessor.

User Action:   Use simple assignment statements to convert the
               variables to the desired data types and perform
               operations on those data types.

SCRNOTFOUND,   specified screen could not be found

Explanation:   The specified screen name was not found in the SHOW
               STATS utility.

User Action:   Check the spelling, or use the menu-based screen
               selection option of the Notepad facility.

SEGALRSTA,     segmented string <str> is already started

Explanation:   You issued a START_SEGMENTED_STRING statement using a
               segmented string name for which a
               START_SEGMENTED_STRING statement has been issued
               without a corresponding END_SEGMENTED_STRING.

User Action:   Issue END_SEGMENTED_STRING or use another segmented
               string.

SEGNOTSTA,     segmented string <str> is not started or created

Explanation:   You issued an END_SEGMENTED_STRING statement using a
               name for which no corresponding START_SEGMENTED_STRING
               or CREATE_SEGMENTED_STRING was issued, or for which an



                                 122

                                                 RDO Facility Messages





               END_SEGMENTED_STRING has already been entered.

User Action:   Issue a START_SEGMENTED_STRING or
               CREATE_SEGMENTED_STRING statement before using
               END_SEGMENTED_STRING, or only use END_SEGMENTED_STRING
               once for each START_SEGMENTED_STRING or
               CREATE_SEGMENTED_STRING.

SEGOUTSCO,     segmented string <str> was used out of scope

Explanation:   You attempted to issue an END_SEGMENTED_STRING command
               using a name that was already ended.

User Action:   Use only one END_SEGMENTED_STRING per
               START_SEGMENTED_STRING.

SEGSTREXP,     cannot use a segmented string in an expression

Explanation:   You attempted to use a segmented string in an
               expression.  Segmented strings may be used only in
               expressions using the MISSING operator.

User Action:   Remove the operations on the segmented string from the
               DML query.

SELMORVAL,     the result of a singleton select returned more than 1
               value

Explanation:   A singleton select statement (SELECT...INTO) may only
               return 1 row of values.  The result table for this
               singleton select contains more than one row.

User Action:   Either embed the SELECT statement (without the INTO
               clause) in a DECLARE CURSOR statement and process it
               with OPEN and FETCH statements, or modify the SELECT
               statement so it will return only one row.

SEQINVAL,      client sequence id <num> does not have a valid value

Explanation:   The sequence with id indicated, has the next value in
               the root file which is either > the max value for the
               sequence or < min value.

SEQTBLFUL,     sequence table is full

Explanation:   An attempt was made to create a sequence but no room
               remains in the Rdb root file for further sequence
               definitions.  Initially only 32 sequences can be
               created in a new or converted database.

User Action:   Use the ALTER DATABASE statement to increase the size



                                 123

RDO Facility Messages





               of the sequences table with the RESERVE ...  SEQUENCES
               clause.  Note that the value entered will be rounded to
               the next highest multiple of 32 so that a full page in
               the root file is used.

SETWIDTH,      error setting width of terminal

Explanation:   An error occurred during the parsing of a file name.

User Action:   Examine the secondary message for more information.

SEVERRDET,     a severe error was detected

Explanation:   A severe error was detected by RDO and returned to DCL
               during the execution of an RDO statement.

User Action:   If possible, run the statement(s) again in interactive
               RDO and read any additional RDO error messages to
               determine what caused the severe error condition.  Then
               fix the error.  Remember, in a DCL command procedure
               containing RDO statements, use the $SEVERITY symbol to
               test for RDO$_SEVERRDET.

SFDBONLY,      <str> function restricted to Single File DataBases

Explanation:   This function is restricted to single file databases.
               It cannot be used with multifile databases.

User Action:   Use the corresponding RMU function for a multifile
               database.

SHINDCIU,      Compression in use

Explanation:   Used for SHOW INDICES.

User Action:   None.

SHINDFLDSIZE,  size of index key is

Explanation:   Used to display the number of characters used in the
               key for an index.  The field used for the key must be
               at least of this length.

User Action:   None.

SHINDMAPVAL,   mapping values

Explanation:   Uses values from <low> to <high> for minimizing space
               needed for index node.

User Action:   None.



                                 124

                                                 RDO Facility Messages





SHINDMAPVAL2,  to

Explanation:   Uses values from <low> to <high> for minimizing space
               needed for index node.

User Action:   None.

SHOMONITROBS,  SHOW MONITOR command is obsolete, please use RMU/SHOW
               SYSTEM

Explanation:   The SHOW MONITOR command is no longer available in RDO.

User Action:   Use the RMU/SHOW SYSTEM command, which provides the
               same functionality.

SHOUSEROBS,    SHOW USERS command is obsolete , please use RMU/SHOW
               USER

Explanation:   The SHOW USERS command is no longer available in RDO.

User Action:   Use the RMU/SHOW USER command, which provides the same
               functionality.

SIP,           transaction is a snapshot transaction

Explanation:   You have already started a transaction that is a
               snapshot transaction.

User Action:   Use READY BATCH RETRIEVAL to ready the area for the
               snapshot transaction or use COMMIT to terminate the
               snapshot transaction.

SNAPFULL,      snapshot area too full for operation

Explanation:   You attempted to store a record in the database,
               because there was an active reader and the snapshot
               area in which the record would go is too full.

User Action:   Modify the snapshot area extend parameter to allow
               snapshot area extension.

SORTOPERR,     a VMS SORT/MERGE operation was unsuccessful

Explanation:   A VMS SORT/MERGE operation completed unsuccessfully.
               See the secondary message for information about what
               operation failed.

User Action:   Fix the VMS SORT/MERGE problem, and try again.

SOURCEDISC,    source code after END statement ignored





                                 125

RDO Facility Messages





Explanation:   There may have been source code after an end statement.

User Action:   Review the program and if there was meaningful source
               code after the end statement in a precompiled module,
               separate it into another module.

SPACREQ,       a space is required before file specification

Explanation:   A space is required to parse the begining of the file
               specification.

User Action:   Run the preprocessor again and include a space before
               the file specification.

SPAMNOTDIS,    cannot disable SPAMs for uniform area <str>

Explanation:   Only mixed-format areas can have SPAMs
               enabled/disabled.

User Action:   Do not enable/disable SPAMs for uniform-format areas.

SPAMNOTRDONLY, cannot enable SPAMs for READ_ONLY area <str>

Explanation:   Read-only areas cannot be modified to have SPAMs
               enabled, because this involves rebuilding the SPAM
               pages.

User Action:   Change the area to be read write.

SPAMNOTWRM,    cannot enable SPAMs for WORM area <str>

Explanation:   WORM areas cannot have SPAMs enabled.

User Action:   Do not enable SPAMs for WORM areas.

SPELLCORR,     identifier <str> replaced with <str>

Explanation:   A keyword was misspelled, but the error has been
               corrected by RDO.

User Action:   None required, unless the correction was not the
               intended keyword.

SRVRSHUTDOWN,  Server process is being shut down

Explanation:   The Server process is currently being shut down, but
               has not yet terminated.

User Action:   Issue the server startup command later.

SSNOTINROOT,   <str> is not in the root file



                                 126

                                                 RDO Facility Messages





Explanation:   The DDCB you specified is not in the root file.  You
               can see which DDCBs a root file has by issuing the
               DBO/DUMP command.

User Action:   Add the DDCB to your root file (DBO/MODIFY), or check
               your bind sequence and try again.

STALL,         asynchronous operation requires a stall

Explanation:   The operation has not completed yet.

User Action:   Check the event flag and I/O status block for final
               completion, and contact your Oracle support
               representative for assistance.

STAREAFUL,     storage area <str> is full

Explanation:   You attempted to store a record in the database, but
               the storage area in which the record would go is full.
               This condition can be caused by the storage area being
               set to disallow being extended or when the ABM pages
               are at their limit and cannot map a new extension for
               the storage area.

User Action:   Modify the storage area extend parameter to allow
               storage area extension if it is disabled, or increase
               the page size or redistribute objects across other
               storage areas to free up existing space.

STARNOTALL,    invalid use of asterisk - expected field name

Explanation:   You attempted to use a context_variable.* in a
               field-required context.

User Action:   Supply names of fields to be referenced.

STATNODEACTV,  node is already actively collecting statistics

Explanation:   A node was specified that is already actively
               collecting statistics for this SHOW STATISTIC utility
               session.

User Action:   Make sure the node name is spelled correctly and has
               been properly identified.

STATNODEUNKN,  node is not actively collecting statistics

Explanation:   A node was specified that is NOT actively collecting
               statistics for this SHOW STATISTIC utility session.

User Action:   Make sure the node name is spelled correctly and has



                                 127

RDO Facility Messages





               been properly identified.

STATNOMATCH,   no logical area names match specified wildcard pattern

Explanation:   No logical areas (tables, indexes, etc) match the
               specified wildcard pattern.  Possibly the wildcard
               characters ("*" and/or "%") were not specified, which
               results in an "exact match" pattern.

User Action:   Use a different wildcard pattern.  Remember to use the
               "*" for "zero or more" and "%" for "exactly one".

STBYDBINUSE,   standby database cannot be exclusively accessed for
               replication

Explanation:   There are one or more application processes or database
               servers accessing the standby database.

User Action:   Make sure there are no active application processes or
               database servers accessing the standby database, on any
               node of the cluster.

STOCONVAR,     must use the context variable, <str>, declared in the
               STORE/MODIFY.  You had <str>

Explanation:   You used a context variable in a STORE statement that
               does not match the one declared in the RSE of the STORE
               statement.  For example:  FOR P IN PORT STORE J IN PORT
               USING P.CITY = J.CITY END_STORE END_FOR

User Action:   Include the correct context variable in your STORE or
               MODIFY statement.

STOMAPNOEXI,   storage map <str> does not exist in this database

Explanation:   The storage map you attempted to change was not found.

User Action:   Check the name of the storage map using the SHOW
               command and try again to change it.

STOMAP_LITS,   too many fields in limit clause

Explanation:   A DEFINE STORAGE MAP statement has specified more
               literal values as limits than corresponding fields in
               the USING clause.

User Action:   Correct the statement.  The number of literal values
               you specify must match the number of fields in the
               USING clause.

STOPMONITROBS, STOP MONITOR command is obsolete, please use



                                 128

                                                 RDO Facility Messages





               RMU/MONITOR STOP

Explanation:   The STOP MONITOR command is no longer available in RDO.

User Action:   Use the RMU/MONITOR STOP command, which provides the
               same functionality.

STRALRDEC,     stream <str> is already declared

Explanation:   You attempted to declare a stream that was already
               declared.

User Action:   Use another stream name.

STRALROPE,     stream <str> is already opened

Explanation:   You attempted to open a stream that was already open.

User Action:   Close the open stream or use another stream name.

STRLITMISQUO,  string literal missing closing quote

Explanation:   The string in a user assignment statement is missing a
               closing quote.

User Action:   Insert one or more quotes as appropriate.

STRNOTDEC,     stream <str> has not been declared

Explanation:   You attempted to open a predeclared stream that hasn't
               been declared

User Action:   Declare the stream or use the name of a predeclared
               stream.

STRNOTOPE,     stream <str> is not opened

Explanation:   You attempted to fetch a row from a stream that was not
               open, or you attempted to close a stream that was not
               open.

User Action:   Issue a START_STREAM <stream-name> command before using
               FETCH.  Start a stream before closing, or close a
               stream only once after opening it.

STROUTSCO,     stream <str> was used out of scope

Explanation:   You attempted to use a stream name outside the scope of
               the START_STREAM/END_STREAM block.  This is not
               permitted.





                                 129

RDO Facility Messages





User Action:   Use FETCH only within the START/END block.

STTREMCNCT,    error allocating remote statistics network connection

Explanation:   None.

STTSVRFIND,    error identifying remote statistics server

Explanation:   None.

SWOPNNOTCOMP,  database is open on another node with incompatible
               software

Explanation:   Incompatible Rdb software exists in this OpenVMS Galaxy
               system and is attempting to open a database in a Galaxy
               shared environment.  Identical versions of Rdb are
               required in order to access a database from multiple
               nodes in an OpenVMS Galaxy environment.

SYM_EXP,       one of the following symbols was expected:

Explanation:   You typed an unexpected keyword.

User Action:   Type a correct keyword.

SYNTAX_ERR,    syntax error

Explanation:   A syntax error was detected in a your RDO statement.

User Action:   Correct the syntax error and retry the statement.

SYSRDONLY,     write access is not allowed if RDB$SYSTEM is read-only

Explanation:   BATCH UPDATE and EXCLUSIVE UPDATE access do not update
               the snapshot files.  The fact that snapshots are not
               being maintained is recorded in the RDB$SYSTEM area.
               Hence, RDB$SYSTEM may not be READ_ONLY.

User Action:   Use another UPDATE access mode, or change RDB$SYSTEM to
               be READ WRITE.

TADMISMATCH,   journal is for database version <time>, not <time>

Explanation:   The version time and date stamp in the root does not
               match the version time and date stamp in the journal
               file.  This journal cannot be applied to this database.

User Action:   Use the correct journal file or backup file.

TERMINATE,     database recovery failed -- access to database denied
               by monitor



                                 130

                                                 RDO Facility Messages





Explanation:   To maintain the integrity of the database, the monitor
               forced your image exit because an unrecoverable error
               has been detected.

User Action:   Look for a file named SYS$SYSTEM:*DBRBUG.DMP.  This is
               a DataBase Recovery process bugcheck dump.  Search the
               file for a string of five asterisks (*****) using the
               SEARCH/WINDOW command.  You will see a line with a
               format similar to this:  ***** Exception at <address> :
               <database module name> + <offset>
               %facility-severity-text, <error text> The exception
               line will be followed by one or more additional errors
               that will help you to determine what caused the
               recovery process to fail.  Possible causes include:
               low quotas, missing Recovery-Unit Journal (RUJ) files,
               or filename logicals misdefined or undefined.
               Depending on the cause of the problem, take the
               appropriate action.  If you are uncertain of what to
               do, contact your Oracle support representative for
               assistance.

TIMEOUT,       timeout on <str>

Explanation:   A lock request has been canceled by the database
               management system because the request could not be
               granted within the user-specified timeout period.

User Action:   Execute a ROLLBACK or a COMMIT to release your locks,
               and try the transaction again.

TOKTOOBIG,     symbol name is too big

Explanation:   You entered a symbol (token) name with a length greater
               than 32 characters.  The length of a symbol name must
               be less than or equal to 32 characters.

User Action:   Use a symbol with no more than 32 characters.

TOOBIGBLR,     request BLR would be too large to execute

Explanation:   Your request is too large to be compiled.

User Action:   The DML statement must be broken up into smaller parts.

TRAACT,        a database cannot be invoked while a transaction is
               active

Explanation:   You issued an INVOKE statement while a transaction was
               still in progress.

User Action:   You must either commit or roll back the current



                                 131

RDO Facility Messages





               transaction or wait until the current transaction is
               terminated before invoking another database.

TRAACT_1,      a database cannot be defined while a transaction is
               active

Explanation:   You issued a DEFINE DATABASE command while a
               transaction was still in progress.

User Action:   You must either commit or roll back the current
               transaction or wait until the current transaction is
               terminated before invoking another database.

TRAACT_2,      ROLLBACK or COMMIT the transaction

Explanation:   You are attempting an operation that cannot be executed
               while the current transaction is still in progress.

User Action:   You must either commit or roll back the current
               transaction or wait until the current transaction is
               terminated before attempting the new database activity.

TRAACT_3,      a database cannot be deleted while a transaction is
               active

Explanation:   You issued a data definition statement while a data
               manipulation transaction was still in progress.

User Action:   Commit or roll back the data manipulation transaction,
               start a new transaction, and reissue the data
               definition statement.

TRAHDLBVAL,    transaction handle must be !VAL

Explanation:   You specified a transaction handle name to
               RDB$INTERPRET.

User Action:   You must use !VAL and a longword variable.

TRAHDLINV,     transaction handle datatype invalid, must be longword

Explanation:   You specified a transaction handle to RDB$INTERPRET
               that was not a longword.

User Action:   You must use !VAL and a longword variable.

TRAMODSPC,     only one transaction mode may be specified for a
               transaction

Explanation:   You specified two transaction modes in a
               START_TRANSACTION statement.



                                 132

                                                 RDO Facility Messages





User Action:   Specify one transaction mode in a START_TRANSACTION
               statement.

TRANONERR1,    start_transaction not allowed in on error

Explanation:   A START_TRANSACTION statement is not allowed in an ON
               ERROR clause.

User Action:   The ON ERROR clause is within a request.  If a new
               transaction is desired, leave the current request and
               then start the transaction.

TRANONERR2,    must leave current request to start a new transaction

Explanation:   A START_TRANSACTION statement is not allowed in an ON
               ERROR clause.

User Action:   The ON ERROR clause is within a request.  If a new
               transaction is desired, leave the current request and
               then start the transaction.

TRAN_IN_PROG,  transaction in progress

Explanation:   You attempted an operation that is allowed only when
               you have no transaction in progress.

User Action:   Complete your transaction by executing a COMMIT or
               ROLLBACK.

TREE_OVRFLO,   tree storage overflow

Explanation:   The internal limit of the AST tree nodes was exceeded.

User Action:   Contact your Oracle support representative for
               assistance.

TRGALREXI,     trigger <str> already exists in this database

Explanation:   The trigger name you requested is already the name of
               an existing trigger.

User Action:   Choose a different name.

TRMTYPUNK,     terminal type is unknown or not supported

Explanation:   The terminal type is either unknown or unsupported.

User Action:   Utilize a support terminal type.  If the terminal type
               is unknown to the operating system, a SET
               TERMINAL/INQUIRE command may help.





                                 133

RDO Facility Messages





TRUE,          condition value is true

Explanation:   None.

TRUNCATION,    data conversion truncation error

Explanation:   You attempted an operation that would cause loss of
               information on a data-item movement.

User Action:   Correct the error and try again.

TSNMISMATCH,   cannot synchronize database due to transaction commit
               mismatch

Explanation:   Attempting to synchronize the master and replicated
               databases failed because the last commit transaction
               sequence numbers in the database do not match exactly.

User Action:   Restart the database replication operation.

UNBTMPFIL,     unable to open a temporary file called <str>

Explanation:   RDO attempted to open a temporary file.  It was either
               in the default directory or the directory specified
               with the OBJ compile option.

User Action:   Include a valid directory specification with protection
               level that allows temporary files to be created.

UNDERFLOW,     data conversion underflow

Explanation:   You attempted an operation that would cause loss of
               information on a data-item movement.

User Action:   Correct the error and try again.

UNKN_ABS,      unknown AIJ backup server process -- ABS image not
               invoked by database monitor

Explanation:   An attempt to bind to the database was made by an
               after-image backup server process (ABS) that was not
               created by the database monitor; this would happen if
               the ABS image was invoked from DCL by the user instead
               of the monitor.

User Action:   DO NOT attempt to execute the ABS image from DCL.  If
               so configured, the database monitor will automatically
               invoke the after-image backup server process to perform
               after-image journal backup operations.

UNKN_ALS,      unknown AIJ Log Server -- ALS image not invoked by



                                 134

                                                 RDO Facility Messages





               database monitor

Explanation:   An attempt to bind to the database was made by an AIJ
               Log Server process (ALS) that was not created by the
               database monitor; this would happen if the ALS image
               was invoked from DCL by the user instead of the
               monitor.

User Action:   DO NOT attempt to execute the ALS image from DCL.  If
               so configured, the database monitor will automatically
               invoke the after-image logging server process to
               perform database journaling activities.

UNKN_DBR,      unknown database recovery process -- DBR image not
               invoked by database monitor

Explanation:   An attempt to bind to the database was made by a
               database recovery process (DBR) that was not created by
               the database monitor; this would happen if the DBR
               image was invoked from DCL by the user instead of the
               monitor.

User Action:   DO NOT attempt to execute the DBR image from DCL.  The
               database monitor will invoke the database recovery
               process to perform database recovery.

UNKN_LCS,      unknown AIJ Log Catch-Up Server -- image not invoked by
               database monitor

Explanation:   An attempt to bind to the database was made by an AIJ
               Log Catch-Up Server process that was not created by the
               database monitor; this would happen if the server image
               was invoked from DCL by the user instead of the
               monitor.

User Action:   DO NOT attempt to execute the server image from DCL.
               Use the appropriate startup syntax to invoke the server
               image.

UNKN_LRS,      unknown AIJ Log Roll-Forward Server -- image not
               invoked by database monitor

Explanation:   An attempt to bind to the database was made by an AIJ
               Log Roll-Forward Server process that was not created by
               the database monitor; this would happen if the server
               image was invoked from DCL by the user instead of the
               monitor.

User Action:   DO NOT attempt to execute the server image from DCL.
               Use the appropriate startup syntax to invoke the server
               image.



                                 135

RDO Facility Messages





UNKN_RCS,      unknown Record Cache Server -- RCS image not invoked by
               database monitor

Explanation:   An attempt to bind to the database was made by a Record
               Cache Server process (RCS) that was not created by the
               database monitor; this would happen if the RCS image
               was invoked from DCL by the user instead of the
               monitor.

User Action:   DO NOT attempt to execute the RCS image from DCL.  If
               so configured, the database monitor will automatically
               invoke the Record Cache Server process to perform
               database journaling activities.

UNLCONVAR,     unlike context variables; can update only one relation
               at a time

Explanation:   The current MODIFY or STORE statement attempts to
               update database fields in multiple relations.  Example:
               "MODIFY USING P.EMPLOYEE_NUM = "FOO"; J.NAME = "JONES"
               END-MODIFY."

User Action:   Use a separate MODIFY or STORE statement to update
               fields in multiple relations.

UNSARITH,      expression includes unsupported arithmetic operation

Explanation:   The Boolean evaluator was processing an expression or
               sub-expression that contained an arithmetic operator.
               Arithmetic operators are not supported.

User Action:   Rewrite the expression in error without the arithmetic
               operator.

UNSCOMP,       unsupported data comparison

Explanation:   You attempted an operation that would compare two
               incommensurate data items.

User Action:   Correct the error and try again.

UNSCOMPBY,     <str>.<str> is not supported in this context

Explanation:   You included the COMPUTED_BY field named in this error
               message in the SELECT FIELDS clause of a DEFINE
               TRANSFER statement.  This COMPUTED_BY field uses a
               value expression that is unsupported.

User Action:   Reenter the DEFINE TRANSFER statement and omit the
               COMPUTED_BY field that uses the unsupported value
               expression.  Refer to the DEFINE TRANSFER statement in



                                 136

                                                 RDO Facility Messages





               the Replication Option for Rdb Handbook for information
               on what value expressions are supported.

UNSCONV,       unsupported data conversion

Explanation:   You attempted an operation that would cause loss of
               information on a data-item movement.

User Action:   Correct the error and try again.

UNSDSCCLA,     unsupported descriptor class <num>

Explanation:   The class of the descriptor in an input parameter is
               not supported by Oracle Rdb.

User Action:   Use class S, D, DS, or VS.

UNSIMPORT,     RDO IMPORT does not support all Oracle Rdb features,
               please use SQL IMPORT



UNSSTRXPR,     unsupported string expression

Explanation:   You attempted an operation on a string that is not
               supported.  ie string = string + string;

User Action:   Please check the manual for the string expressions
               allowed.  If you are using the preprocessors, you might
               be able to work around the limitation by using a
               temporary variable.

UNSSUPDAT,     unsupported datatype requested

Explanation:   You requested input or output of an unsupported data
               type from Callable RDO.

User Action:   Review the data types of the variables in the call and
               change the offending data type to a supported data
               type.

UNTILTAD,      recovery /UNTIL date and time is "<time>"

Explanation:   The specified date and time are being used for the
               after-image journal roll-forward operation.

UNTSTR,        unterminated string found

Explanation:   The matching quotation mark (" or ') for a string was
               not found.

User Action:   Reenter the command with the matching quotation mark.



                                 137

RDO Facility Messages





UPDATEJOIN,    relation <str> is part of join cannot be updated

Explanation:   You tried to modify or erase records from a relation
               that is joined (using the CROSS clause) with other
               relations.

User Action:   Redefine the query so that the relation you are trying
               to update is not directly joined to other relations.
               i.e.  do not use a CROSS clause, but instead represent
               the other relation references as subqueries.

USEUNOPTAIJ,   please use original unoptimized AIJ file for this
               recovery operation

Explanation:   The requested recovery operation is not compatible with
               an optimized AIJ file.  See the accompanying message
               for the cause of the incompatability.

User Action:   Use the original, non-optimized AIJ file to do the
               recovery.

USINGCLSMNGLESS, USING clause present with no WITH LIMIT clause

Explanation:   You specified a STORE USING clause, but no WITH LIMIT
               clause.

User Action:   The STORE USING clause is meaningless without the WITH
               LIMIT clause.

USINGNOTSPEC,  no USING clause specified

Explanation:   A DEFINE STORAGE MAP statement has specified literal
               values as limits but has specified no fields in the
               USING clause.

User Action:   Correct the statement.  The number of literal values
               you specify must match the number of fields in the
               USING clause.

VEWNOTDEF,     view <str> is not defined in database

Explanation:   The specified view does not exist in the current
               database.

User Action:   Invoke the proper database.  Spell the view name
               correctly.  You may have specified an expression where
               a view name was expected.

VWNOFETCH,     view <str> cannot be fetched within a stream

Explanation:   Records from the specified view cannot be retrieved in



                                 138

                                                 RDO Facility Messages





               a stream.  This indicates that the view was defined as
               an AGGREGATE (SQL GROUP BY) or MERGE (SQL UNION)
               stream.

User Action:   Retrieve the records using a FOR statement.

WAIMODSPC,     only one wait mode may be specified for a transaction

Explanation:   You specified two transaction modes in a
               START_TRANSACTION statement.

User Action:   Specify only one transaction mode in a
               START_TRANSACTION statement.

WASBOOL,       expression in CONTAINS or MATCHES was a Boolean

Explanation:   The Boolean evaluator was processing an expression or
               sub-expression of the form "A CONTAINS B" or "A MATCHES
               B".  Either the "A" or the "B" expression was a Boolean
               of the form "NOT X", "X EQ Y", "X NE Y", "X LT Y", "X
               GT Y", "X LE Y", "X GE Y", "X CONTAINS Y", or "X
               MATCHES Y".  Neither side of CONTAINS and MATCHES
               expressions are allowed to be Boolean expressions.

User Action:   Rewrite the expression to have the proper format.

WISH_LIST,     feature not yet implemented

Explanation:   The action you requested requires a feature that is not
               implemented in the current version of this product.

User Action:   Avoid using this feature.

WRMCANTREAD,   error reading WORM pages <num>:<num>-<num>

Explanation:   An error occurred when you attempted to read one or
               more WORM pages.  The message indicates the storage
               area ID number and the page numbers of the first and
               last pages being read.

User Action:   Examine the associated messages to determine the reason
               for failure.  One possible cause for this error is
               disabling logging for the WORM area and subsequently
               restoring that area from an earlier backup.

WRMDEVFUL,     WORM device full for area <str>

Explanation:   The area is marked as "WORM device full," because a
               previous attempt to extend this WORM area failed.

User Action:   Consider adding more areas to the storage map or moving



                                 139

RDO Facility Messages





               the WORM area to a higher capacity WORM device.

WRMNOTMIX,     cannot add WORM attribute to uniform format area <str>

Explanation:   WORM areas should be mixed-format areas only.

User Action:   Examine your command line for illegal combinations.

WRMRDONLY,     cannot add WORM attribute to READ_ONLY area <str>

Explanation:   WORM areas cannot also have the read-only property.

User Action:   Examine your command line for illegal combinations.

XIDNOTFOUND,   specified XID could not be found in the database

Explanation:   The specified XID was not found in the database.
               Either the XID was never in the unresolved state, or it
               has since been resolved with the resolution that had
               been supplied earlier.

User Action:   Check the appropriate transaction manager log for more
               information.

XPR_STACK_OVFL, expression forces too many levels of recursion/stack
               overflow

Explanation:   You provided an expression which forces too many levels
               of recursion, which resulted in stack overflow.

User Action:   The expression should be rewritten to use parentheses
               and therefore cause fewer levels of recursion.  It may
               also be possible to increase the size of the stack.

ZABORT,        user entered Control-Z to abort command

Explanation:   You entered a CTRL/Z to abort the current command.

User Action:   None.



























                                 140