RDMS Facility Messages





This document provides explanations and user actions for errors
returned with the RDMS facility code.  These messages are generated by
the Rdb Record Storage System.  RDMS error messages are secondary
messages that describe errors underlying an RDB or RDO error message.
For information on related messages, type, print, or search the
following files:

        SYS$HELP:RDB_MSG.DOC
        SYS$HELP:RDO_MSG.DOC

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

$ SEARCH/WINDOW=(0,10) SYS$HELP:RDMS_MSG.DOC rootmajver
ROOTMAJVER,    database format is not compatible with 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.

SEGSTR_NO_CHG, you cannot change a field's datatype to or from a
               segmented string















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
               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.





                                  1

RDMS Facility Messages





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.

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.

ACTQUERY,      there are queries compiled that reference relation
               "<str>"

Explanation:   You tried to change metadata associated with the
               specified table or view however a compiled query exists
               that depends on the current table or view metadata.

User Action:   You may have to disconnect, and re-attach to the
               database before executing this action.

ACTQUERYRTN,   there are queries compiled that reference routine
               "<str>"

Explanation:   You tried to change metadata associated with the



                                  2

                                                RDMS Facility Messages





               specified routine however a compiled query exists that
               depends on the current routine metadata.

User Action:   You may have to disconnect, and re-attach to the
               database before executing this action.

ACTQUERYSEQ,   there are queries compiled that reference sequence
               "<str>"

Explanation:   You tried to change metadata associated with the
               specified sequence however a compiled query exists that
               depends on the current sequence metadata.

User Action:   You may have to disconnect, and re-attach to the
               database before executing this action.

ACTUPDREQ,     there are active update requests that reference
               relation <str>

Explanation:   You tried to change metadata associated with the
               specified relation but a request is active that depends
               on the current relation metadata for some update
               action.

User Action:   Finish using the referencing request and release it;
               then try the metadata update again.

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.



                                  3

RDMS Facility Messages





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.

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.



                                  4

                                                RDMS Facility Messages





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
               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.





                                  5

RDMS Facility Messages





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
               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



                                  6

                                                RDMS Facility Messages





               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
               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



                                  7

RDMS Facility Messages





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
               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



                                  8

                                                RDMS Facility Messages





               backup has been completed, after-image journal backup
               operations will again be possible.

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

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





                                  9

RDMS Facility Messages





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
               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



                                  10

                                                RDMS Facility Messages





               assistance.

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

Explanation:   The specified after-image journal contains the
               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



                                  11

RDMS Facility Messages





               "<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
               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



                                  12

                                                RDMS Facility Messages





               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.

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.





                                  13

RDMS Facility Messages





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
               "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>



                                  14

                                                RDMS Facility Messages





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.

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





                                  15

RDMS Facility Messages





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
               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.



                                  16

                                                RDMS Facility Messages





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
               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



                                  17

RDMS Facility Messages





               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
               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



                                  18

                                                RDMS Facility Messages





               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
               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



                                  19

RDMS Facility Messages





               loss

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

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



                                  20

                                                RDMS Facility Messages





               operations.

User Action:   No user action is required.

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

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.





                                  21

RDMS Facility Messages





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.

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



                                  22

                                                RDMS Facility Messages





               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.

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.



                                  23

RDMS Facility Messages





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
               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.

ALLMIN,        <str> must be greater than <num>

Explanation:   The allocation for the database you specified is too
               small.

User Action:   Try another value.

ALLSORTWORKERR, all SORTWORKn.TMP files failed

Explanation:   Sort failed to extend sortwork.tmp files and attempted
               remedial action by trying each in turn has also failed.

User Action:   Define sortwork logicals (SORTWORK1, SORTWORK2, etc)
               such that the target devices have available disk space.

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



                                  24

                                                RDMS Facility Messages





               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.

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.

AMBPRFENT,     "<str>" is an ambiguous or unknown user identifier

Explanation:   The identifier specified is ambiguous or is not known.
               A wildcard or group identifier was used.

User Action:   Respecify the identifier using an unambiguous, known
               identifier.



                                  25

RDMS Facility Messages





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.

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_NAME,     area <str>

Explanation:   This message supplies supplementary information for an
               accompanying message.

User Action:   As specified for accompanying message.

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.





                                  26

                                                RDMS Facility Messages





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

ARITH,         arithmetic exception

Explanation:   An exception occurred while Oracle Rdb was evaluating
               an arithmetic expression.  The subordinate status
               explains the exception.

User Action:   Change the expression to eliminate the error.  For
               example, if the exception was division by zero, change
               your query to exclude records that cause a division by
               zero.

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
               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



                                  27

RDMS Facility Messages





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
               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.

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





                                  28

                                                RDMS Facility Messages





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

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

User Action:   Please specify a valid record cache name.

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.

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.



                                  29

RDMS Facility Messages





               If not, rename or copy the database file to have the
               proper type.

BADHANDLE,     invalid handle passed on call to Oracle Rdb

Explanation:   A call to Oracle Rdb passed a non-zero handle when zero
               was expected or passed a handle that was not valid.  A
               handle is output by certain Oracle Rdb calls.  This
               error can be caused by errors in software, such as a
               pre-processor, that creates the calls to Oracle Rdb.

User Action:   None.

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.

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.

BADIORECLEN,   query would result in illegal record length

Explanation:   Solving the user's query would result in an illegal
               record length being used for an RMS operation.

User Action:   The user will have to reconsider the database design,
               environment or query structure.  This error would be
               obtained as the result of a conjunct match strategy
               which does not have enough VM.  This can be resolved by
               providing a large enough value for the logical
               RDMS$BIND_WORK_VM).  Alternately, the problem might be
               alleviated by dropping the indices which are used for
               query resolution or by reducing the size of the columns
               being joined.

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

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



                                  30

                                                RDMS Facility Messages





               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.

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,



                                  31

RDMS Facility Messages





               make sure you are using the correct software version.

BADSEGSTROPT,  option specified is incompatible with segmented string
               storage maps

Explanation:   You defined a storage map for segmented strings and
               included an option which is not supported or is
               meaningless.

User Action:   Review the documentation and correct the syntax.

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

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

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

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.

BAD_AREA_NAME, area named <str> does not exist

Explanation:   You specified an area name that is incorrect.

User Action:   Check with your DBA to determine the correct area names
               for your database, and reissue your command correctly.

BAD_CODE,      corruption in the query string

Explanation:   An illegal entry was found in the query string.

User Action:   If you called Oracle Rdb, check the query string.
               Otherwise, contact your Oracle support representative
               for assistance.

BAD_OUTLINE_VERSION, unsupported query outline version

Explanation:   The query outline version number is either 0 or is
               greater than the maximum OBLR version supported by the
               Oracle Rdb image.





                                  32

                                                RDMS Facility Messages





User Action:   If an outline is being moved from one version of Oracle
               Rdb to an earlier version of Oracle Rdb, and that
               earlier version of Oracle Rdb supported an earlier
               version of the outline format, then you must create a
               new outline that uses only supported outline features.

BAD_SYM,       unknown <str> symbol - <str>

Explanation:   Invalid symbol.

User Action:   Check the definition and retype the command.

BAD_XPR,       corrupt expression

Explanation:   A corrupt expression was found in the query string.

User Action:   If you called Oracle Rdb, check the query string.
               Otherwise, contact your Oracle support representative
               for assistance.

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.

BLR_MISMATCH,  a table or subquery in query outline was not found in
               query

Explanation:   You have used a table context number or subquery
               hierarchy within the query outline definition that
               cannot be found in the query to which the outline will
               be applied.

User Action:   Only use those context numbers in your query outline
               that exist in the query for which you are creating the
               outline.  Additionally, do not change the subquery
               hierarchy in the outline.

BOUND,         multiple binds are not allowed





                                  33

RDMS Facility Messages





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.

BPPMAX,        <num> blocks per page is greater than the Oracle Rdb
               maximum of <num>

Explanation:   The page size for the database you specified is too
               large.

User Action:   Try another value.

BPPMIN,        <num> blocks per page is less than the Oracle Rdb
               minimum of <num>

Explanation:   The page size for the database you specified is too
               small.

User Action:   Try another value.

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.

BUFLIMEXC,     internal buffer limit exceeded

Explanation:   You have provided a request whose compilation exceeds
               the buffer capabilities of Oracle Rdb.  An example
               would be a request that attempts to retrieve several
               thousand fields from a relation.

User Action:   Rewrite the request, possibly breaking it up into
               multiple requests.

BUFSMLPAG,     buffer size is less than page size

Explanation:   Buffer size must be large enough for at least one page.

User Action:   Try another value for the buffer size.

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





                                  34

                                                RDMS Facility Messages





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.

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.

BUILDPENDING,  index in build pending state - operation not permitted

Explanation:   This table has an index defined with a build pending.
               Therefore, change to the data (such as using DELETE,
               INSERT, or UPDATE) is not permitted.

User Action:   Complete the index build so that the table is again
               writable.

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
               first.

CACHEUSED,     in use by storage area "<str>", cache "<str>" not
               deleted

Explanation:   You attempted to drop the cache which is used by a
               storage area.

User Action:   Make sure the cache you drop is not used by any storage
               map or use DROP CASCADE to have each storage updated.





                                  35

RDMS Facility Messages





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.

CANNOTNEST,    transaction BLR is nested too deeply

Explanation:   BLRK_TRANSACTION can not be nested within a BLR$K_FOR
               or a BLR$K_STATEMENT.  You can not start, commit, or
               rollback a transaction from within these statements.

User Action:   This is an unexpected internal error.  If you are using
               DSRI, then please recode the DSRI request to avoid the
               nesting.  If you are using SQL, contact your Oracle
               support representative for assistance.  You will need
               to provide the statements that produced this error.

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.

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.



                                  36

                                                RDMS Facility Messages





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.

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



                                  37

RDMS Facility Messages





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.

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.





                                  38

                                                RDMS Facility Messages





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.

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.



                                  39

RDMS Facility Messages





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.

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



                                  40

                                                RDMS Facility Messages





               first and last pages being read.

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

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.

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.

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



                                  41

RDMS Facility Messages





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
               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.





                                  42

                                                RDMS Facility Messages





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

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



                                  43

RDMS Facility Messages





               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.

CASTDOMAIN,    <str> <str> uses domain <str> as CAST or local variable

Explanation:   A dependency exists for this domain.  It is used in a
               CAST expression or as a local variable.

User Action:   You need to change the reference in the routine,
               trigger, constraint, or column before dropping the
               domain.

CATALOGEXISTS, catalog <str> already exists

Explanation:   The named catalog already exists.

User Action:   Use a different name for the catalog.

CATALOGINUSE,  catalog <str> currently in use

Explanation:   You attempted to drop a catalog which still contains a
               schema.

User Action:   Drop all the schemas from the catalog before attempting
               to drop the catalog.

CATNOTFOUND,   catalog with id <num> not found in this database

Explanation:   The catalog id referenced by the CREATE SCHEMA
               statement does not exist.

User Action:   Please select another catalog.

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

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



                                  44

                                                RDMS Facility Messages





User Action:   Include a device and directory specification.

CDDISREQD,     CDD required for metadata updates is not being
               maintained

Explanation:   You attempted to change a definition in a database
               which requires that all definition changes be reflected
               in the CDD, after issuing an INVOKE DATABASE FILENAME
               statement.

User Action:   INVOKE DATABASE PATHNAME, and retry the metadata
               update.

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.

CHGIDXNOADDMAP, INDEX may not be altered/changed to have map

Explanation:   A CHANGE or ALTER INDEX command cannot add a storage
               map to an index that was not previously mapped.

User Action:   Review the index's use.  If you want to move it to
               another area, the index must be deleted and defined
               again.

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.

CMTCONNOTDEL,  cannot delete constraint <str> queued for COMMIT
               evaluation





                                  45

RDMS Facility Messages





Explanation:   The specified constraint was not deleted because an
               update action has caused the constraint to be queued
               for evaluation on a COMMIT.

User Action:   COMMIT or ROLLBACK the current transaction and try the
               metadata update again.

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.

COLEXTS,       there is another collating sequence named <str> in this
               database

Explanation:   The collating sequence name you tried to define already
               exists.

User Action:   Try another collating sequence name.

COLINVFLDTYP,  collating sequence invalid for data type

Explanation:   An attempt was made to create or change a domain or
               column such that the result is a non-text data type
               with a collating sequence.

User Action:   Ensure that collating sequences are not used on
               non-text data types.

COLLFAILURE,   could not reformat the collating sequence

Explanation:   Oracle Rdb translates an NCS collating sequence into an
               internal format for use in building indices,
               comparisons, and matching.  The translation could not
               be performed.

User Action:   Contact your Oracle support representative for
               assistance.  You will need to provide the files BUG.MAR
               and BUG.NCS obtained from the command:
               NCS/MAC=BUG/OUT=BUG/EXT=<collating_name> <library>
               where <collating_name> is the name of the collating
               sequence that you selected from the library indicated
               by <library> or from NCS.NLB if you did not specify a
               library.

COLLFMTUNK,    collating format unknown

Explanation:   Oracle Rdb understands the internal format of the
               collating sequences defined in NCS.NLB.  Apparently



                                  46

                                                RDMS Facility Messages





               there is a new format in use that Oracle Rdb does not
               know about.  Perhaps you are using an obsolete version
               of Oracle Rdb.

User Action:   Contact your Oracle support representative for
               assistance.  If the problem is not that an obsolete
               version of Oracle Rdb is in use, then you will need to
               provide the files BUG.MAR and BUG.NCS obtained from the
               command:  NCS/MAC=BUG/OUT=BUG/EXT=<collating_name>
               <library> where <collating_name> is the name of the
               collating sequence that you selected from the library
               indicated by <library> or from NCS.NLB if you did not
               specify a library.

COLNOEXTS,     there is no collating sequence named <str> in this
               database

Explanation:   The collating sequence name you tried to delete does
               not exist.

User Action:   You may have typed the collating sequence name
               incorrectly, or you did not define the collating
               sequence name.

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

Explanation:   The specified field does not exist in the relation
               specified.

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.

COLRESERVED,   collating sequence name "<str>" is reserved and may not
               be defined

Explanation:   The collating sequence name you tried to use is
               predefined and reserved for use by Oracle Rdb.

User Action:   Please choose another name.

COLUMNORDER,   column "<str>" is out of order in the USING clause of
               "<str>"

Explanation:   The ADD PARTITION USING clause specified a column in
               the wrong order.

User Action:   Please review the original storage map or index
               definition, and ensure that all the same columns are
               specified in the same order.



                                  47

RDMS Facility Messages





COLUSEDDB,     the collating sequence named <str> is used by the
               database

Explanation:   The collating sequence name you tried to delete was
               defined as the collating sequence for the database.

User Action:   Investigate.

COLUSEDFLD,    the collating sequence named <str> is used in field
               <str>

Explanation:   The collating sequence name you tried to delete is in
               use.

User Action:   Investigate.

COLUSEDREL,    the collating sequence named <str> is used in field
               <str> of relation <str>

Explanation:   The collating sequence name you tried to delete is in
               use.

User Action:   Investigate.

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.

COMPNOTENA,    index compression has not been enabled

Explanation:   You attempted to remap index values without enabling
               compression for the index.

User Action:   Review the command you typed, and issue a corrected
               command if appropriate.

COMPNOTNUM,    index mapping applies to BYTE, WORD and LONGWORD fields
               only

Explanation:   You attempted to remap index values but the fields must
               be of a SIGNED BYTE (TINYINT), SIGNED WORD (SMALLINT)
               or SIGNED LONGWORD (INTEGER) data type.

User Action:   Review the command you typed, and issue it again
               specifying a column of the appropriate data type.

COMPNOTTEXT,   only text and varying text fields may be shortened in
               indices



                                  48

                                                RDMS Facility Messages





Explanation:   You attempted to specify a shortened size for an index
               field, but specified a data type other than text or
               varying text.  Only fields with a text or varying text
               data type can be shortened in an index.

User Action:   Review the command you typed, and issue it again
               specifying a text or varying text field if appropriate.

CONCATSTRLEN,  concatenation result is too long

Explanation:   The result of a concatenation operation exceeds the
               maximum supported string size.

User Action:   Check the length of the strings used in the expression
               to determine appropriate action.

CONDELVIAREL,  constraint <str> can only be deleted by changing or
               deleting relation <str>

Explanation:   The constraint specified was defined as a
               relation-specific constraint, and can only be deleted
               by using the CHANGE RELATION or DELETE RELATION
               statement on the relation declaring the constraint.

User Action:   First, review the database design; then, if desired,
               delete the relation-specific constraint.

CONEXI,        relation <str> is referenced in constraint <str>

Explanation:   Before you can delete a relation, all constraints and
               views based on this relation must be deleted.

User Action:   Delete the dependent constraints and any views that
               refer to this relation.

CONEXTS,       there is another constraint named <str> in this
               database

Explanation:   The constraint name you tried to define already exists.

User Action:   Choose another constraint name.

CONFEVAL,      constraint <str> contains conflicting evaluation time
               attributes

Explanation:   This constraint contains conflicting evaluation time
               attributes.  Only one of the SQL options DEFERRABLE or
               NOT DEFERRABLE, or RDO options VERB TIME or COMMIT TIME
               should be specified.

User Action:   Remove conflicting clauses.



                                  49

RDMS Facility Messages





CONFLATTR,     conflicting attributes specified:  <str> and <str>

Explanation:   The two attributes you specified may not be used
               together in the same statement.

User Action:   Choose one of the attributes, or alter the definition
               to combine legal attributes.  For instance, a database
               can not have synonyms enabled and also be a multischema
               database.

CONFRESERVE,   RESERVE can not be used with ADD/DROP in the same ALTER
               DATABASE command

Explanation:   RESERVE STORAGE AREAS cannot be specified with either
               ADD STORAGE AREA or DROP STORAGE AREA in a single ALTER
               DATABASE command.

User Action:   Perform RESERVE STORAGE AREAS in a separate command
               from either ADD STORAGE AREA or DROP STORAGE AREA.

CONFTRANOPT,   conflicting transaction options specified

Explanation:   Two or more options which were specified on the SET
               TRANSACTION (SQL) (or RDO START_TRANSACTION) statement
               are in conflict and cannot be specified together.

User Action:   Refer to the SQL Reference Manual description of the
               SET TRANSACTION statement and remove the options which
               are in conflict.

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

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

CONMODEXI,     constraint "<str>" specified in default transaction for
               the module "<str>"

Explanation:   An attempt was made to perform the delete operation on
               a constraint.  The constraint is specified with the
               EVALUATING clause in the default transaction
               characteristics for the module.

User Action:   First, review the database design; then, if desired,
               delete the module, and then delete the constraint.

CONNODEFER,    constraint <str> can not be deferred using the
               EVALUATING clause

Explanation:   This constraint is defined as NOT DEFERRABLE, and so



                                  50

                                                RDMS Facility Messages





               the evaluation time can not be changed by SQL's SET
               TRANSACTION or RDO's START_TRANSACTION statements.

User Action:   Remove the constraint's name from the EVALUATING
               clause.

CONNOEXI,      constraint <str> does not exist

Explanation:   The name specified for the constraint was not found in
               the database or the constraint named does not reference
               table named.

User Action:   Check the name of the constraint using the SHOW command
               and try again.  Check to make sure the constraint is
               defined on the named table.

CONNOTDEF,     constraint <str> has not been defined

Explanation:   The specified constraint was not defined.

User Action:   Correct the problem and try the metadata update again.

CONNOTDEL,     constraint <str> has not been deleted

Explanation:   The specified constraint was not deleted.

User Action:   Correct the problem, and retry the metadata update.

CONRTNEXI,     constraint "<str>" is referenced in the routine "<str>"

Explanation:   The specified constraint you attempted to delete is
               used in a routine.

User Action:   First, review the database design; then, if desired,
               delete the routine, and then delete the constraint.

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.

CONVW,         views cannot be used within constraints

Explanation:   Constraints cannot be placed on views.

User Action:   Place constraints on the relation referred to in the
               view definition.

CSETBADASSIGN, incompatible character sets prohibit the requested



                                  51

RDMS Facility Messages





               assignment

Explanation:   An attempt was made to assign one string to another,
               but the character sets of the two strings were
               incompatible.

User Action:   Ensure that character sets are compatible before
               assignment.

CSETBADCOMPARE, incompatible character sets prohibit the requested
               comparison

Explanation:   An attempt was made to compare one string to another
               but the character sets of the two strings were
               incompatible.

User Action:   Ensure that character sets are compatible before trying
               comparison.

CSETBADCONCAT, incompatible character sets prohibit concatenation

Explanation:   An attempt was made to concatenate strings together,
               but the character sets of the two strings were
               incompatible.

User Action:   Ensure that character sets are compatible before trying
               concatenation.

CSETBADESCAPE, character set of ESCAPE character must match that of
               source

Explanation:   An escape character was used that did not have the same
               character set as the source value expression.

User Action:   Ensure that the correct character set is used with the
               ESCAPE character.

CSETBADOPER,   character set prohibits the requested operation

Explanation:   An attempt was made to carry out a string operation but
               the character set of the string prevented the
               operation.

User Action:   Ensure that the operation is valid on the character set
               before trying the operation again.

CSETBADPOS,    incompatible character sets prohibits use of POSITION

Explanation:   An attempt was made to search for a string within
               another string but the character sets of the two
               strings are incompatible.



                                  52

                                                RDMS Facility Messages





User Action:   Ensure that character sets are compatible before trying
               to use the POSITION operator.

CSETBADTRIM,   incompatible character sets prohibit use of TRIM

Explanation:   An attempt was made to trim characters from a source
               string, but the character sets of the trim character
               and source string are incompatible.

User Action:   Ensure that character sets are compatible before trying
               to use the TRIM operator.

CSETNOASCII,   character set must contain ASCII

Explanation:   An attempt was made to assign or compare a numeric or
               date with a text string that had a character set that
               did not contain ASCII.

User Action:   Ensure that destination character string character set
               contains ASCII.

CSETNOTFOUND,  invalid or undefined character set

Explanation:   The character set specified is not known to Oracle Rdb.

User Action:   Check the character set name and/or identifier to
               ensure that they are valid.

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
               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.



                                  53

RDMS Facility Messages





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.

DBACTIVE,      database is already being used

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.

DBCRUPT,       database is corrupt

Explanation:   Your database is not a valid Oracle Rdb database.  This
               can happen if DEFINE DATABASE does not terminate
               normally.

User Action:   Recreate your database.  If the database was not just
               created, contact your Oracle support representative for
               assistance.

DBKFORMAT,     database key format incorrect "<str>?<str>" -
               unexpected character

Explanation:   While converting the text dbkey string to binary an
               unexpected character was detected, shown by the ?  in
               the displayed text.

User Action:   Correct the database key string literal to conform to
               the rules defined in the SQL Reference Manual.

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



                                  54

                                                RDMS Facility Messages





               an operation.  Note that the AIJ roll-forward utility
               sometimes converts the /AREA or /PAGE roll- forward
               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.

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.

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.

DBNOTEXTEN,    database not multi-file, areas may not be added



                                  55

RDMS Facility Messages





Explanation:   Your database was not specified as multi-file, yet you
               attempted to add areas to the database.

User Action:   If you want to create a multi-file database from a
               single file database, use the EXPORT and IMPORT
               statements.

DBNOTINTRAN,   that database is not in the current transaction

Explanation:   You tried to start a request or use a segmented string
               in a database not included in your current transaction.

User Action:   Commit or roll back your transaction, and start a new
               transaction that includes the proper databases.

DBNOTMULTSCHEM, multischema support is not enabled in this Oracle Rdb
               database

Explanation:   Multischema support is an option feature.

User Action:   Use the SQL ALTER RDB DATABASE ENABLED MULTISCHEMA
               statement to enable this feature and then repeat your
               command.

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.

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.



                                  56

                                                RDMS Facility Messages





DBRBOUND,      attach not allowed while your process is being
               recovered

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_CORRECT_VER, the database is already the correct version

Explanation:   The database is already accessible by the current
               version of the software.  This message is used only by
               special versions of the software and is referenced in
               RMU CONVERT.

User Action:   None.

DDLDONOTMIX,   the "<str>" clause can not be used with some ALTER
               DATABASE clauses

Explanation:   You attempted to mix the specified clause with other
               ALTER DATABASE clauses that modify storage areas,
               template areas or database cache objects.  This is not
               currently supported.

User Action:   Execute two separate ALTER DATABASE statements, one
               containing structure altering clauses, and one with the
               remaining attributes.

DDLFAILED,     operation on "<str>" failed - in use by <num>:<num>,
               reason:  <num>

Explanation:   This DDL operation failed because the object is in use
               by another DDL user.  The process id and database
               stream are shown for reference

User Action:   Retry this operation at another time, or determine why
               the conflicting process is still active.





                                  57

RDMS Facility Messages





DDL_CONFLICT,  relation <str> specified reserved for data definition

Explanation:   An attempt was made to compile a query or perform an
               incompatible data definition language operation against
               a table specified in a RESERVING clause with the table
               reserved for SHARED DATA DEFINITION or EXCLUSIVE DATA
               DEFINITION.

User Action:   Commit or rollback the current transaction and start
               another transaction that is compatible with the
               operation being attempted.

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.

DEFINC,        DEFAULT is incompatible with datatype of <str>
               "<str>"."<str>"

Explanation:   The DEFAULT specified is not compatible with the
               datatype of the routine parameter or module global
               variable.

User Action:   Ensure that the datatype of the parameter or variable
               and the DEFAULT (SQL) are compatible.  Check the domain
               used by the parameter or variable to verify consistency
               between datatypes and DEFAULTs.

DEFINCCOL,     DEFAULT is incompatible with datatype of column
               "<str>"."<str>"

Explanation:   The DEFAULT (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) is
               not compatible with the datatype of the column (field).
               The column default could be incompatible with the type
               of the column or of the domain used by the column.

User Action:   Ensure that the datatype of the column and the DEFAULT
               (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) are
               compatible.  Check the domain used by the column to
               verify consistency between datatypes and DEFAULTs.

DEFINCDOM,     DEFAULT is incompatible with datatype of domain "<str>"

Explanation:   The DEFAULT (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) is
               not compatible with the datatype of the domain (global
               field).



                                  58

                                                RDMS Facility Messages





User Action:   Ensure that the datatype of the domain displayed in the
               error message is consistent with the DEFAULT (SQL) or
               DEFAULT VALUE FOR SQL (CDD/Rep) of the domain (global
               field).

DEFLISTWORM,   default list (segmented string) storage area can not be
               a WRITE ONCE area

Explanation:   An attempt was made to create a database with a default
               list (segmented string) storage area on a WORM (write
               one read many) device.  This is not supported by Oracle
               Rdb because the format of the lists written by the
               system relations is not compatible with the WORM drive
               characteristics.

User Action:   Create the default list storage area on read/write
               media and create a storage map to assign the lists to
               particular storage areas.

DEFONLYNULL,   Default value can only be NULL for a segmented string

Explanation:   The only valid value for a default value on a segmented
               string is NULL.

User Action:   Ensure that the default value is NULL when the datatype
               of the column or domain is segmented string.

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

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.

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



                                  59

RDMS Facility Messages





               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.

DORMUCOLLECT,  index statistics need updating with RMU/COLLECT

Explanation:   This index has out of date statistics.  Continued use
               in this state might lead to degraded query performance.

User Action:   Please use the RMU/COLLECT OPTIMIZER_STATISTICS on this
               index so that the statistics can be updated

DT_FRACMBZ,    fractional seconds precision must be zero for this sub
               type

Explanation:   The date/time data type supplied a sub-type which does
               not allow a fractional seconds precision to be
               supplied.

User Action:   This appears to be an error in the code generated by
               SQL.  Contact your Oracle support representative for
               assistance.  You will need to provide the statements
               that produced this error.

DT_PRECMBZ,    interval leading field precision must be zero for this
               sub type

Explanation:   The date/time data type supplied a sub-type which does
               not allow a leading interval field precision to be
               supplied.

User Action:   This appears to be an error in the code generated by
               SQL.  Contact your Oracle support representative for
               assistance.  You will need to provide the statements
               that produced this error.

DUPAIJFIL,     duplicate AIJ filename "<str>" specified

Explanation:   A duplicate AIJ file name was specified during AIJ



                                  60

                                                RDMS Facility Messages





               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.

DUPLANAME,     area name <str> already used

Explanation:   The area name specified is already in use for this
               database.

User Action:   Choose a different name.

DUPLCNAME,     cache name "<str>" already used

Explanation:   The cache name specified is already in use for this
               database.

User Action:   Choose a different name.

DUPLFNAME,     file name <str> already used

Explanation:   The file name specified is already in use for this
               database.

User Action:   Choose a different name.

DUPLTRGTYPE,   trigger <str> already defined for specified relation
               and trigger type

Explanation:   There can be only one trigger of each update time and
               type defined for a particular relation, with the
               exception that multiple BEFORE MODIFY or AFTER MODIFY
               triggers can be defined as long as they all have
               exclusive (non-intersecting) field lists.  The trigger



                                  61

RDMS Facility Messages





               being defined conflicts with the specified trigger for
               either update time and type, or in one of the modify
               field names.

User Action:   First, review the database design and defined triggers;
               then, if desired, try the operation again with
               non-conflicting types and fields.

DUPNOTALL,     duplicate records not allowed for index <str>

Explanation:   You are trying to add a duplicate record to an index on
               a field that does not allow duplicates.

User Action:   Do not add duplicate records unless you restructure the
               relation to allow them.

DUPSYSREC,     Cannot create duplicate system record in "<str>"

Explanation:   Two or more processes were attempting to create hashed
               indexes concurrently in an empty mixed format storage
               area that did not have a system record logical area
               previously defined.  This can result in a duplicate
               system record logical area.

User Action:   Wait for the process that did not fail to finish
               defining the index.  This process will cause a system
               record logical area to be defined for the area
               indicated in the error message.  Try again to create
               the index that caused the failure.

DYN_REG_ALLOC_FAIL, dynamic register allocation algorithm has failed

Explanation:   A register allocation algorithm internal to Oracle Rdb
               has failed while generating code to evaluate an
               expression.  In theory this message should never get
               through to the user.

User Action:   Contact your Oracle support representative for
               assistance.  You will need to provide the statements
               that produced this error.  Using parentheses again
               around the problematic expression may give you a
               workaround.

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.



                                  62

                                                RDMS 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.

EMPTY_SUBQUERY, a subquery in the query outline contains no tables

Explanation:   Tables or subqueries can be omitted in the query
               outline; however, if all the tables and subqueries of a
               subquery are omitted, the subquery must be removed
               also.  Empty subqueries are not permitted.

User Action:   Delete the empty subquery, and try again.

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.

User Action:   Examine the secondary message for more information.

EXCMAPLIMIT,   exceeded limit on last partition in storage map for



                                  63

RDMS Facility Messages





               <str>

Explanation:   An attempt was made:  to store a record; or to modify
               an index key value that is higher than allowed by any
               partition; or to create or alter an index that would
               not hold all existing values.

User Action:   Check that the application is generating correct key
               values.  Add a partition to handle the new key values
               or add an overflow partition.

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.

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.

EXTABORT,      routine <str> execution has been aborted

Explanation:   Execution of the specified external routine has been
               aborted.

User Action:   Review the secondary error message for the reason for
               the abort, eliminate the problem, and retry the
               operation or query.

EXTDBONLY,     operation is not allowed on single file databases

Explanation:   You attempted to change or delete storage areas or
               change the number of nodes or number of users in a
               single-file database or use a non-default specification
               for the snapshot file.

User Action:   If you want to create a multi-file database from a
               single-file database, use the EXPORT and IMPORT
               statements.

EXTERNALRTN,   invalid use of external routine "<str>"



                                  64

                                                RDMS Facility Messages





Explanation:   You tried to use an EXTERNAL routine where only a
               stored routine is permitted.

User Action:   Repeat the action using a stored routine instead.

EXTRTNATTCHG,  an external routine attribute was changed for this
               platform

Explanation:   The external routine definition was modified on this
               platform because an attribute (such as CLIENT SITE) is
               not supported.

User Action:   This is just a warning, and can be ignored.  To avoid
               the warning change the external function or procedure
               definition to be compatible with this platform, or
               allow the attribute to default for each platform.

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.

EXT_JULIAN_TS, invalid type for EXTRACT JULIAN - must be DATE or
               TIMESTAMP

Explanation:   The EXTRACT JULIAN requires that the result of the
               value expression be a DATE or a TIMESTAMP.

User Action:   Correct the query to use a valid data type for EXTRACT.

EXT_LENGTH_CH, invalid type for EXTRACT LENGTH - must be CHAR or
               VARCHAR

Explanation:   The EXTRACT WEEKDAY requires that the result of the
               value expression be a CHAR or a VARCHAR.

User Action:   Correct the query to use a valid data type for EXTRACT.

EXT_NEED_DT,   invalid option for EXTRACT - source must be a datetime
               type

Explanation:   The EXTRACT option requires that the result of the
               value expression be a datetime type.

User Action:   Correct the query to use a valid option for EXTRACT.

EXT_NO_DT_FIELD, invalid option for EXTRACT, source does not include
               required date/time field

Explanation:   The EXTRACT option specifies a date/time field which



                                  65

RDMS Facility Messages





               does not exist in the value expression.

User Action:   Correct the query by using a valid option for EXTRACT.

EXT_WEEKDAY_TS, invalid type for EXTRACT WEEKDAY - must be DATE or
               TIMESTAMP

Explanation:   The EXTRACT WEEKDAY requires that the result of the
               value expression be a DATE or a TIMESTAMP.

User Action:   Correct the query to use a valid data type for EXTRACT.

FCJOUDIS,      fast commit cannot be enabled if journaling is disabled

Explanation:   An attempt was made to enable fast commit while
               journaling is turned off.

User Action:   Enable journaling for the database before enabling fast
               commit.

FCJOUENB,      journaling cannot be disabled if fast commit is enabled

Explanation:   An attempt was made to disabling journaling while the
               fast commit feature is turned on.

User Action:   Disable fast commit before disabling journaling.

FEAT_UNSUP,    <str> are not supported in this context

Explanation:   You attempted to use a feature that is not supported in
               this location.  Typically this is a general table
               feature that is not supported by a LOCAL TEMPORARY
               TABLE (created or declared)

User Action:   Remove the problem clause and try again.

FETABSOLUTE,   fetch absolute (<num>) out of range 1..<num>

Explanation:   The value of the FETCH ABSOLUTE, FIRST, or LAST is out
               of the range of the number of segments.

User Action:   Correct the value passed to FETCH.

FETILLOFFSET,  FETCH offset must be zero for NEXT, PRIOR, FIRST, LAST

Explanation:   The FETCH_OFFSET argument contains a value other than
               zero.

User Action:   Correct the call to RDB_GET_SEGMENT.

FETINVALID,    invalid list cursor FETCH attributes (<num>,<num>)



                                  66

                                                RDMS Facility Messages





Explanation:   The FETCH_ORIENTATION argument contains a value not
               recognized by Oracle Rdb.

User Action:   Correct the call to RDB_GET_SEGMENT.

FETNOTSCROLL,  illegal FETCH attribute - must be FETCH NEXT for
               non-SCROLL cursor

Explanation:   The LIST CURSOR was opened without the SCROLL
               attribute, but an attempt was made to perform an action
               other than FETCH NEXT.

User Action:   Add the SCROLL attribute to the cursor, or change the
               FETCH to FETCH NEXT.

FETRELATIVE,   fetch relative (<num>) causes reference out of range
               1..<num>

Explanation:   The value of the FETCH RELATIVE, NEXT, or PRIOR is out
               of the range of the number of segments.

User Action:   Correct the value passed to FETCH.

FIEUSETRA,     field <str> is used in the transferred relation <str>

Explanation:   The specified field is used in the specified relation.
               The relation is involved in a DDAL transfer definition.

User Action:   You must delete the DDAL transfer definition before
               modifying the field.

FILACCERR,     error <str> file <str>

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.

FLDEX,         column name "<str>" appears more than once in this
               table, view or map





                                  67

RDMS Facility Messages





Explanation:   The column name appears more than once within a table,
               view or storage map (COLUMNS clause) definition.

User Action:   For a table or view the column name can only be used
               once.  Therefore, remove or change the name of the
               column to avoid this problem.  For a storage map the
               column name may only be used in one COLUMNS clause.
               You may not map a column to more than one vertical
               partition.

FLDINCOM,      field <str> is referenced in COMPUTED BY field <str>

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a COMPUTED BY field in the same
               relation.

User Action:   First, review the database design; then, if desired,
               delete the COMPUTED BY field, and then delete the field
               from the relation.

FLDINCOMREL,   field <str> is referenced in COMPUTED BY field <str> in
               relation <str>

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a COMPUTED BY field in another
               relation.

User Action:   First, review the database design; then, if desired,
               delete the COMPUTED BY field, and then delete the field
               from the relation.

FLDINCON,      field <str> is referenced in constraint <str>

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a constraint.

User Action:   First, review the database design; then, if desired,
               delete the constraint, and then delete the field from
               the relation.

FLDINRTN,      field "<str>" is referenced in routine "<str>"

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a routine.

User Action:   First, review the database design; then, if desired,
               delete the routine, and then delete the field from the
               relation.

FLDINSTO,      field <str> is referenced in storage map <str>





                                  68

                                                RDMS Facility Messages





Explanation:   You attempted to delete a field from a relation but the
               field is used in a storage map.

User Action:   First, review the database design; then, if desired,
               delete the storage map, and then delete the field from
               the relation.

FLDINTRG,      field <str> is referenced in trigger <str>

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a trigger.

User Action:   First, review the database design; then, if desired,
               delete the trigger and then delete the field from the
               relation.

FLDINUSE,      field <str> is referenced in index <str>

Explanation:   The field you attempted to delete is an indexed field.

User Action:   First, delete the index on the field, and then delete
               the field.

FLDINVIEW,     field <str> is referenced in view <str>

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a view of that relation.

User Action:   First, review the database design; then, if desired,
               delete the view, and then delete the field from the
               relation.

FLDLSTCONDUPS, modify field name list contains duplicates of a field
               name

Explanation:   The list of field names supplied for a MODIFY type
               trigger contains multiple instances of a particular
               field name.

User Action:   Choose a different set of field names for the modify
               list.

FLDNOEX,       field <str> is not part of this relation

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

User Action:   Check the relation definition for the correct field
               name.

FLDNOEXI,      field <str> does not exist in this database





                                  69

RDMS Facility Messages





Explanation:   The field that you attempted to delete was not found.
               It might be a local field in a relation rather than a
               global field.

User Action:   Check the exact name of the field and try again to
               delete it.  If it is a local field, use the CHANGE
               RELATION statement to delete the field.

FLDNOTCHG,     field <str> has not been changed

Explanation:   The field specified was not deleted.

User Action:   Correct the problem and retry the operation.

FLDNOTDEL,     field <str> has not been deleted

Explanation:   The field in question has not been deleted for the
               reason explained by the previous message.

User Action:   Correct the problem and retry the statement.

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

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

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

FLDVALIDIF,    in VALID IF definition for global field <str>

Explanation:   During processing of the VALID IF a BLR syntax problem
               was detected.

User Action:   Correct the definition so that the VALID IF is legal
               for Oracle Rdb.

FLDVALIDIFNAME, in VALID IF definition for global field <str>,
               references name <str>

Explanation:   During processing of the VALID IF definition, a BLR
               syntax problem was detected.  The name referenced in
               the VALID IF expression is not equal to the global
               field name.

User Action:   Correct the definition so that the VALID IF expression
               contains the same name as the global field definition.

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

Explanation:   Partially-journalled changes have been made to the



                                  70

                                                RDMS Facility Messages





               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.

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.

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.

GFLDEXTS,      there is another global field named <str> in this
               database

Explanation:   The field name you tried to define already exists.

User Action:   Use another field name.

GFLDNOEX,      there is not a global field named <str> in this
               database

Explanation:   The field you tried to include in a relation definition
               does not exist.

User Action:   Define the field and then try to create the relation
               again.

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.

HASHEDMIX,     index of TYPE HASHED must be stored in area(s) with



                                  71

RDMS Facility Messages





               PAGES MIXED

Explanation:   You attempted to define a hashed index to be stored in
               a storage area with a uniform-page format.  A hashed
               index must be stored in a storage area with a
               mixed-page format.

User Action:   Specify one or more storage areas with mixed-page
               format for the hashed index.

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.

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



                                  72

                                                RDMS Facility Messages





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

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



                                  73

RDMS Facility Messages





               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.

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



                                  74

                                                RDMS Facility Messages





               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
               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.





                                  75

RDMS Facility Messages





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.

IDXBLDPEND,    index in build pending state - maintenance is disabled

Explanation:   This index is now in build-pending state and can not
               currently be used for queries.  An ALTER INDEX ...
               MAINTENANCE IS ENABLED statement must be used to
               re-enable this index.  Only perform this final step
               when all partitions have been rebuilt.  Note that the
               table on which this index is defined may not be
               modified (INSERT, UPDATE, or DELETE) while indices are
               in the build pending state.

User Action:   This is just a warning to remind the database
               administrator of additional tasks which must be
               performed.

IDXCOLEXIST,   an index with this column list already exists

Explanation:   An index exists with the same column list, and same
               type (either SORTED or HASHED), with the same column
               ordering (ASC/DESC) This warning is intended to alert
               the database administrator that this index may be
               redundant.

User Action:   If this index is not needed then drop this index, or
               ROLLBACK the CREATE INDEX statement.  If you wish to
               replace an existing index with a different partitioning
               schema you should use ALTER INDEX.  You can also
               disable the existing index using ALTER INDEX ...
               MAINTENANCE IS DISABLED so that it is no longer updated
               or used by queries.  It can then be dropped at later
               time.

IDXCOMP,       a key value inserted into this index may exceed the
               maximum length

Explanation:   It is possible that when the key compression algorithm
               is run for some values inserted into this index the
               resulting key length may exceed 255 bytes.  This
               condition is dependent on the data values and will
               probably occur rarely.





                                  76

                                                RDMS Facility Messages





User Action:   This is just a warning.  If you drop the index and
               recreate it as an uncompressed index you will guarantee
               that all rows can be stored.

IDXCOMPLENERR, index compression length exceeds field length

Explanation:   You attempted to specify a shortened size for an index
               field that is greater than the field size.

User Action:   Specify a shortened size that is not larger than the
               field size.

IDXDUPCOL,     index definition contains a redundant reference to a
               column

Explanation:   The index definition repeated a reference to a column
               in a table.  This usage is not needed and does not add
               any value to the index.

User Action:   This is just a warning.  If you drop the index and
               recreate it without the redundant column reference it
               will occupy less space in the database.

IDXMAPLIM,     value exceeds bounds specified for mapping of index
               <str>

Explanation:   The data stored in a field exceeds the bounds specified
               for mapping the field.

User Action:   Determine the cause of the problem and correct either
               the record or the index.

IDXMAPLMT,     range of mapped index limited to HIGH - LOW =
               2147483647

Explanation:   You attempted to define an index using mapping ranges
               on variables so that the resulting key requires 32 or
               more bits.  The maximum permitted is 2**31-4

User Action:   Try to define the index again without using the
               relation-map-clause.

IDXMAPLMTERR,  index map limit exceeds value limit for field

Explanation:   You attempted to define an index using mapping ranges
               on variables that is bigger than the data type.

User Action:   Try to define the index again using accepted limits.

IDXMAPNODIF,   values for mapping of index must be different





                                  77

RDMS Facility Messages





Explanation:   The data used for a field mapping must be different.
               This message can appear for two reasons:  you used the
               MAPPING VALUES clause in a CREATE INDEX definition and
               both the high and low values of the range were equal,
               or you used the ALTER INDEX ...  ADD PARTITION
               statement and specified a new partition which matched
               exactly the WITH LIMIT OF clause of an existing
               partition, or it specified no WITH LIMIT OF clause and
               matched an existing OTHERWISE partition.

User Action:   Determine the cause of the problem and correct the
               index definition.

IDXNOBLDPEND,  index not in build pending state - build ignored

Explanation:   This index was not created with the MAINTENANCE IS
               DISABLED option, and therefore all partitions are
               already built.

User Action:   This is just a warning to help the database
               administrator.

IDXNODPAG,     index node size exceeds free space on page -
               fragmentation

Explanation:   You specified a node size which exceeds the free space
               on pages in one of the storage areas.  The node will be
               fragmented and result in more I/O than necessary.

User Action:   This is just a warning.  If you size the index node to
               better fix the page, or size the page for this index
               node size you may improve I/O performance when using
               this index.

IDXNOTCHG,     index <str> has not been changed

Explanation:   The specified index was not altered.

User Action:   Correct the problem and retry the metadata update.

IDXNOTCOMP,    index is not compressed

Explanation:   The index must be compressed if you want to specify
               these attributes (minimum run length, compressed
               octets).

User Action:   Redefine the index with the enable compression clause.

IDXNOTDEF,     index <str> has not been defined

Explanation:   The specified index was not defined.



                                  78

                                                RDMS Facility Messages





User Action:   Correct the problem and try the metadata update again.

IDXNOTDEL,     index <str> has not been deleted

Explanation:   The specified index was not deleted.

User Action:   Correct the problem and retry the metadata update.

IDXNOTHASH,    index is not a hashed index

Explanation:   The hash type can only be specified for hashed indexes.
               This is not a hashed index.

User Action:   Redefine the index.

IGNNOLOG1,     ignoring NOLOGGING - Hot Standby is enabled and logging
               required

Explanation:   This is an informational message reported to the user
               when NOLOGGING is partially ignored.  HOT STANDBY needs
               full logging to function correctly.

User Action:   No user action is required, but database administrators
               should note that full logging is still in use to the
               after image journal.  Only logging to the recovery unit
               journal is disabled.

IGNNOLOG2,     ignoring NOLOGGING - logical area just created DEFERRED

Explanation:   This is an informational message reported to the user
               when NOLOGGING is ignored.  When CREATE INDEX ...
               NOLOGGING is used with MAINTENANCE IS ENABLED DEFERRED
               logging is also deferred.  However, Rdb can not disable
               logging in the same session.

User Action:   No user action is required, but database administrators
               should note that full logging is still in use and DDL
               operations on the index may generate more log file
               space than expected.

IGNNOLOG3,     alert for NOLOGGING - LogMiner requires logging to
               unload table data

Explanation:   This is an informational message reported to the user
               when NOLOGGING is seen on a LogMiner enabled database.
               Logging of table rows is required to support LogMiner
               actions on the table.

User Action:   No user action is required, but database administrators
               should note that any rows inserted into the table prior
               to COMMIT will not been seen by RMU/UNLOAD/AFTER_IMAGE.



                                  79

RDMS Facility Messages





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.

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.

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.

INCCMTOPTIONS, inconsistent commit options on temporary table

Explanation:   If there is a constraint on temporary table T_SOURCE
               which references temporary table T_TARGET, and if
               temporary table T_TARGET has commit options ON COMMIT
               DELETE ROWS, then temporary table T_SOURCE must have
               the same commit options ON COMMIT DELETE ROWS.

User Action:   Please review and correct the temporary table
               definition to have commit options ON COMMIT DELETE
               ROWS.

INCSEQATTR,    sequence "<str>" has attributes incompatible with <str>

Explanation:   The attribute(s) specified during a create sequence or
               an alter sequence command is incompatible with other
               attributes specified.  For example, the attribute
               RANDOMIZE is incompatible with the attributes ORDER,
               MAXVALUE and MINVALUE.

User Action:   Please review attributes and correct the sequence



                                  80

                                                RDMS Facility Messages





               command.  If the attribute was RANDOMIZE make sure it
               not specified with ORDER, MAXVALUE or MINVALUE.

INDBLRBAD,     incorrect storage map BLR generated for partitioned
               index <str>

Explanation:   The BLR generated for the index operation is incorrect.
               This may indicate that a problem exists in the product
               and should be reported to your support organization.
               It may also indicate that the index definition provided
               was incorrect but was not diagnosed through other
               software checks.

User Action:   Review the index definition and, if possible, correct
               it.  If you think it is a software error, then contact
               your Oracle support representative for assistance.

INDEXTS,       there is another index named <str> in this database

Explanation:   The index name you tried to define already exists.

User Action:   Try another index name.

INDEX_S_MAX,   user requested node size of <num> bytes exceeds limit

Explanation:   The index node size you specified is greater than that
               supported by the implementation.

User Action:   Refer to the documentation and supply another value.

INDEX_S_MIN,   user requested node size of <num> bytes for index
               needing <num>

Explanation:   The index node size you specified is less than that
               needed by the implementation.

User Action:   Refer to the documentation, and supply another value.

INDINMAP,      index "<str>" is used in storage map "<str>"

Explanation:   You attempted to drop an index used in a storage map
               PLACEMENT VIA INDEX clause.

User Action:   You must alter the storage map to be NO PLACEMENT VIA
               INDEX before dropping this index.

INDLIMITBAD,   partition field <str> not in index

Explanation:   You attempted to partition an index using a field not
               included in the index.





                                  81

RDMS Facility Messages





User Action:   Specify the command again using only fields defined for
               the index.

INDLIMITORDBAD, partition <num> limits are not in index order for
               partitioned index <str>

Explanation:   The limits are not specified according to the index
               order.  For a descending segment, the corresponding
               limit values must be in descending order.

User Action:   Specify the command again with limits in index order.

INDMAINTDIS,   maintenance on index <str> has been disabled

Explanation:   An attempt was made to use an index that has been
               marked as maintenance disabled.

User Action:   Try another index.

INDNEEDSLIMIT, limits must be specified for index

Explanation:   You attempted to define an index without specifying
               limits for all but the last partition of the index.

User Action:   Respecify your index definition, providing limits for
               all but the last area.

INDNOTEXI,     index <str> does not exist in this database

Explanation:   There is no index with the given name.

User Action:   Try SHOW INDEX to see which indexes exist.

INDNOTREL,     index <str> does not reference same relation as storage
               map

Explanation:   The index specified in the PLACEMENT VIA INDEX clause
               is not an index on the relation whose storage map is
               being defined.

User Action:   Select or create a new index for placement.

INDTABBAD,     index <str> does not reference table <str>

Explanation:   The specified index does not reference the specified
               table.

User Action:   You may have specified the wrong context variable or
               table name or have mistyped the index name.  Try again.

INDTOOBIG,     requested index is too big



                                  82

                                                RDMS Facility Messages





Explanation:   You attempted to define an index that requires more
               than 255 characters.  The limit is the number of fields
               plus the sum of the number of bytes specifying the size
               of each field.

User Action:   Simplify the index definition or break it into two or
               more components.

INDTOOMNYCOL,  too many columns have been specified in the storage map
               BLR generated for partitioned index <str>

Explanation:   The storage map for the index does not agree with the
               index and has specified more columns for the
               partitioning than for the index.

User Action:   Please review and correct the index definition.

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.

INSNOREAD,     cannot read column "<str>" from target row during
               INSERT

Explanation:   The AUTOMATIC column attempted to reference the row
               being inserted.

User Action:   AUTOMATIC columns can not reference the target row
               during insert because the data may not yet be
               completely materialized.  Correct the AUTOMATIC column
               definition to either be UPDATE (which can reference the
               old row version), or rework the value expression to
               avoid reference to the inserted row.

INVACC_IN_PARAM, attempt to write to an IN parameter

Explanation:   This parameter is declared as mode IN which does not
               allow updates.



                                  83

RDMS Facility Messages





User Action:   If you wish to update this parameter, then change its
               mode to INOUT or OUT.  Otherwise correct the reference
               to this parameter.

INVACC_OUT_PARAM, attempt to read from an OUT parameter

Explanation:   This parameter is declared as mode OUT which does not
               allow read access (its value is undefined).

User Action:   If you wish to read this parameter, then change its
               mode to INOUT or IN.  Otherwise correct the reference
               to this parameter.

INVACC_PARAM,  invalid expression passed to INOUT/OUT parameter
               "<str>" (<num>)

Explanation:   The value expression used for this parameter can not
               accept an output value.

User Action:   Correct the usage for this parameter to be a variable
               or parameter.

INVACE_LENGTH, invalid Access Control Entry length

Explanation:   You specified too many identifiers in the access
               control entry (ACE).

User Action:   Reduce the number of identifiers in the ACE.  The
               maximum number of identifiers in ACE is 30.

INVALID_CALL,  routine "<str>" returns a value -- use only in an
               expression

Explanation:   You referenced a function as a procedure using a CALL
               statement.  You must only use the function in a value
               expression.

User Action:   Correct the usage of the function.

INVALID_FUN,   routine "<str>" is not a function -- usage is invalid

Explanation:   You referenced a procedure as a function in a value
               expression.  You must only use the CALL statement to
               call a procedure.

User Action:   Correct the usage of the procedure.

INVALID_OBLR,  syntax error or missing query in query outline

Explanation:   A syntax error or omission was found in the query
               outline OBLR.



                                  84

                                                RDMS Facility Messages





User Action:   Dump the OBLR using RDMS$DEBUG_FLAGS="Sos"; then
               compare the OBLR structure with the BLR from the
               corresponding query.

INVALID_OUTLINE_ID, "<str>" (<num>) in outline does not match the
               query

Explanation:   An illegal table identifier was found in the query
               outline string.

User Action:   The outline is incomplete or invalid.  Regenerate a
               query outline with the optimizer, and ensure that query
               blocks are not deleted and that table identifiers are
               not modified.

INVASSIGNMENT, illegal target for assignment

Explanation:   Oracle Rdb restricts the targets for BLR$K_ASSIGNMENT
               to be columns within the table referenced by the
               BLR$K_STORE, BLR$K_STORE2 or BLR$K_PLACE statements.
               Additionally, built-in functions, such as
               BLR$K_GET_INFO, BLR$_CURRENT_TIME,
               BLR$_CURRENT_TIMESTAMP, and BLR$_CURRENT_DATE can only
               be sources in an assignment, not in targets.

User Action:   If you called Oracle Rdb using DSRI, please correct the
               query string.  Otherwise, contact your Oracle support
               representative for assistance.  You will need to
               provide the statements that produced this error.

INVCASEEXP,    case expression has no data type (all branches are
               NULL)

Explanation:   The result data type of a CASE expression is calculated
               from each of the result value expressions following the
               THEN clause.  This CASE expression only has NULL which
               has no data type attributes.  (Note that a missing ELSE
               clause also defaults to NULL.)

User Action:   If you want to use NULL, then use CAST(NULL AS
               some-dtype) to apply a data type to the NULL
               specification.

INVCATALOGID,  invalid catalog identification <num> - must be negative

Explanation:   Catalog identifiers are always negative numbers.

User Action:   Correct the MBLR generation and try again.

INVDATOPR,     invalid date arithmetic operation





                                  85

RDMS Facility Messages





Explanation:   The operation requested is not legal.  The operands,
               operator, or the result is not valid for date/time
               arithmetic.

User Action:   Correct the operation to one that is valid.

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.

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.

INVDB_TYPE,    invalid database type for attach

Explanation:   You attempted to attach to an SERdb database from
               Oracle Rdb.

User Action:   Use only Oracle Rdb to attach to an Oracle Rdb database
               and use only SERdb to attach to an SERdb database.

INVDSCTYP,     specified data type can not be passed/returned by
               descriptor or length

Explanation:   The specified data type for the parameter or function
               result can not be passed or returned by mechanism
               DESCRIPTOR or LENGTH.

User Action:   Change the specified passing mechanism to be
               by-reference or by-value, or change the data type of
               the parameter or return type.

INVDTYPINDX,   cannot use computed by or segmented string for index

Explanation:   You attempted to define an index using either a
               COMPUTED BY field or a segmented string as the key.



                                  86

                                                RDMS Facility Messages





User Action:   Select another field as the key.

INVDTYPKEY,    key <str> cannot be a computed by or segmented string
               field

Explanation:   You attempted to define a UNIQUE, PRIMARY KEY, or
               FOREIGN KEY REFERENCES relation-specific constraint
               with a key field having either a computed by or
               segmented string datatype.

User Action:   Select another field for the key.

INVESCSEQ,     invalid character found after escape character

Explanation:   A character other than a wildcard or an escape
               character was found following an escape character in
               the pattern provided.

User Action:   Ensure that only a wildcard character or an escape
               character follows the escape character.

INVESCVAL,     invalid escape clause value

Explanation:   An escape clause value must be non-null and exactly one
               character in length.

User Action:   Ensure that the escape clause value is one character in
               length.

INVFORUPDATE,  invalid FOR UPDATE option (<num>) - must be a Boolean
               value

Explanation:   The value passed to a compile request was outside the
               legal range.  Please specify a valid option.

User Action:   Please correct the item-list to RDB_COMPILE_REQUEST.

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.

INVIDENT,      invalid rights identifier found

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

User Action:   Make sure that any identifiers and/or UIC you specify
               are defined in the system rights database.



                                  87

RDMS Facility Messages





INVIDXATTR,    invalid attribute specification for the index

Explanation:   One or more of the index attribute specifications is
               invalid.

User Action:   Re-enter the request with the correct index attribute
               definition.

INVIDXRL,      invalid value specified for the index minimum run
               length

Explanation:   An invalid value was specified for the minimum run
               length attribute of the index.

User Action:   Redefine the index.

INVINFOTBL,    invalid use of information table

Explanation:   You attempted to create an information table or
               reference an information table in an invalid way.  Here
               are some invalid ways it could have been used:  1)
               Constraints and triggers cannot be defined on an
               information table.  2) Indexes cannot be defined on an
               information table.  3) Storage maps cannot be defined
               on an information table.  4) An information table
               cannot be altered.

User Action:   Redefine the information table or reference to the
               information table to comply as described above.

INVJOINBOOL,   invalid join condition specified

Explanation:   You have specified a join condition for a CROSS or
               UNION join which is not allowed.

User Action:   Remove the join condition.

INVMARKOP,     invalid markpoint commit/rollback for TSN <num>:<num>,
               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.

INVMAXROWS,    invalid optimizer maximum rows (<num>) - must be



                                  88

                                                RDMS Facility Messages





               greater than zero

Explanation:   The value passed to a compile request was outside the
               legal range.  Please specify a valid number of rows
               which is expressed as a positive integer.

User Action:   Please correct the item-list to RDB_COMPILE_REQUEST.

INVMAXTIME,    invalid compile time limit (<num>) - must be greater
               than zero

Explanation:   The value passed to a compile request was outside the
               legal range.  Please specify a valid number of seconds
               which is expressed as a positive integer.

User Action:   Please correct the item-list to RDB_COMPILE_REQUEST.

INVMETACACHE,  cached metadata for table "<str>" invalidated by online
               change

Explanation:   An online metadata change to the TABLE in the exception
               message has produced a new version of the TABLE.  The
               exception indicates an attempt to update a record in
               the database with obsolete, in- consistent metadata
               from the in memory cache.

User Action:   Detach and re-attach to the database.  This will cause
               any cached metadata to be reloaded into the in memory
               symbol tables.

INVMODAUTH,    invalid module authorization name specified

Explanation:   The module authorization clause does not specify a
               valid system rights identifier.

User Action:   Re-enter the command with the correct user name in the
               authorization clause.

INVMOD_NAME,   invalid module name

Explanation:   You entered a misspelled or nonexistent module name.

User Action:   Reenter the command with the correct spelling of a
               valid module name.

INVNAME,       symbol <str> contains invalid characters or is too long

Explanation:   Name symbols may contain only the characters A through
               Z, 0 through 9, and $ and _.  They may not end in $ or
               _.





                                  89

RDMS Facility Messages





User Action:   Use a different name symbol.

INVOPTPREF,    invalid optimizer preference (<num>) - must be
               total-time or fast-first

Explanation:   The value passed to a compile request was outside the
               legal range.  Please specify a valid option.

User Action:   Please correct the item-list to RDB_COMPILE_REQUEST.

INVORDHASH,    invalid ORDERED hashed index definition

Explanation:   The ORDERED hashed index being defined is invalid.
               Compression cannot be enabled with an ORDERED hashed
               index.  The last column referenced in the ORDERED
               hashed index must be a binary value (TINYINT, SMALLINT,
               INTEGER, BIGINT, DATE, TIME, TIMESTAMP, or INTERVAL).

User Action:   Redefine the index either by not enabling compression
               or by ensuring that the last column in the index
               definition is a binary value.

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.

INVPRMCNT,     routine <str> expected <num> parameter(s), passed <num>
               parameter(s)

Explanation:   The wrong number of parameters was passed to the
               specified routine.

User Action:   Check the definition of the routine in the database.
               Pass the correct number of parameters to the specified
               routine.

INVRETTYP,     result data type can not be returned by value

Explanation:   The specified data type for the function result can not
               be returned by value.

User Action:   Change the specified passing mechanism to be
               by-reference or by-descriptor, or change the data type
               of the return type.





                                  90

                                                RDMS Facility Messages





INVRTNUSE,     routine <str> can not be used, image "<str>" not
               activated

Explanation:   The specified external routine can not be used because
               the image was not successfully dynamically activated.

User Action:   Review the secondary error message or messages, verify
               that the external routine definition location
               specification is correct, verify that the image is
               available at the specified location, and that the image
               is a shareable image which can be dynamically
               activated.

INVRTN_NAME,   invalid routine or procedure name

Explanation:   You entered a misspelled or nonexistent routine name.

User Action:   Reenter the command with the correct spelling of a
               valid routine name.

INVSCHEMAID,   invalid schema identification <num> - must be positive

Explanation:   Schema identifiers are always positive numbers.

User Action:   Correct the MBLR generation and try again.

INVSECIMAGE,   image location specification fails secure translation

Explanation:   The image location specification specified by the
               primary error could not be successfully translated
               using OpenVMS secure EXEC mode logicals.

User Action:   Review the secondary error message or messages, verify
               that the external routine definition location
               specification is correct, verify the definition of all
               associated logical names, and that the image file can
               be accessed via the appropriate logicals.

INVSEQATTR,    sequence "<str>" has an illegal value for <str>

Explanation:   The attribute specified during a create sequence or
               alter sequence command is illegal.  The attribute
               "INCREMENT BY" must not be zero (0).

User Action:   Please review attributes and correct the sequence
               command.  If the attribute was "INCREMENT BY" make sure
               it is non-zero.

INVSYNONYM,    invalid synonym name "<str>" - name used by another
               object





                                  91

RDMS Facility Messages





Explanation:   The synonym is named the same as an existing synonym,
               or some other object (such as a table, sequence,
               domain, module, type or routine).

User Action:   Choose another name for this synonym.

INVTBL_NAME,   invalid relation name

Explanation:   You entered a misspelled or nonexistent relation name.

User Action:   Reenter the command with the correct spelling of a
               valid relation name.

INVTEMPTBL,    invalid use of temporary table

Explanation:   You attempted to create a temporary table or reference
               a temporary table in an invalid way.  Here are some
               invalid ways it could have been used:  1) A temporary
               table definition cannot contain a constraint which
               references a non-temporary(base) table.  2) A base
               table definition cannot contain a constraint which
               references a temporary table.  3) Datatrieve
               attributes, a CDD Pathname or COMMENT ON cannot be
               specified on a declared temporary table definition.  4)
               Indexes cannot be defined on a temporary table.  5)
               Only storage maps with no areas are legal on temp
               tables.

User Action:   Redefine the temporary table or reference to the
               temporary table to comply as described above.

INVTRANOPT,    the transaction option "<str>" is not allowed

Explanation:   A transaction mode was specified on the SET TRANSACTION
               (SQL) (or RDO START_TRANSACTION) statement which is
               currently not allowed for this database.  These modes
               are established using the SET or ALTER TRANSACTION
               MODES clause on CREATE and ALTER DATABASE.

User Action:   Use the SHOW DATABASE statement in SQL to examine the
               enabled modes for this database and change your set
               transaction accordingly.  Or, have the database
               administrator modify the database-wide settings to
               allow this transaction to be executed.

INVTRGACT_STMT, invalid trigger action statement - can not modify
               target table

Explanation:   A trigger action has attempted to modify (INSERT,
               UPDATE or DELETE) the table that is the target of an
               active trigger.  Any table that is the target of a



                                  92

                                                RDMS Facility Messages





               trigger action becomes temporarily read-only while the
               trigger actions execute.

User Action:   Correct the application logic to remove this modify
               attempt.

INVTRIMOPT,    trim error - invalid trim option specified

Explanation:   The TRIM option specified for the TRIM operator must be
               one of the following:  LEADING, TRAILING, or BOTH

User Action:   Correct the BLR to generate a valid option for TRIM.

INVVALTYP,     parameter <num> can not be passed BY VALUE

Explanation:   The specified data type or the parameter mode (OUT or
               INOUT) can not be passed BY VALUE.

User Action:   You should either change the data type, parameter mode
               or parameter mechanism to a combination which is legal.

INV_DATE_CHG,  invalid field datatype change to/from datetime

Explanation:   An attempt was made to change the data type of a
               datetime field to a data type which was not compatible.

User Action:   Consult the documentation for a list of valid
               conversions to/from datetime fields.

INV_DIGITS,    invalid precision for exact numeric, must be in range
               <num>..<num>

Explanation:   The data definition language requested a TINYINT,
               SMALLINT, INTEGER, or BIGINT with a precision
               restriction (number of digits) which was larger than
               that supported by the data type.

User Action:   Correct the definition so that the number of digits
               requested is within the legal range.

INV_PCT_FILL,  percent fill out of valid range of 1 through 100

Explanation:   The index percent fill you specified is not a valid
               value.

User Action:   Refer to the documentation and supply another value.

INV_PRECISION, invalid interval leading field precision for datetime

Explanation:   The data definition language requested an interval
               leading field precision which is outside the supported



                                  93

RDMS Facility Messages





               range.

User Action:   Correct the definition so that the interval leading
               field precision is within the legal range.

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.

INV_SCALE,     invalid fractional seconds precision for datetime

Explanation:   The data definition language requested a fractional
               seconds precision for a TIME, TIMESTAMP, or INTERVAL
               definition which is outside the correct range.

User Action:   Correct the definition so that the fractional seconds
               precision is within the legal range.

INV_SUB_TYPE,  invalid sub_type in definition

Explanation:   The data definition language requested a sub-type which
               was not recognized.

User Action:   Correct the definition so that the sub-type is within
               the legal range.

IOINDDUPDEF,   a nested index definition implies that duplicates are
               sorted

Explanation:   An INDEX ONLY index must be unique or have duplicates
               sorted.  If a nested index definition exists, then the
               duplicates handling must be specified as sorted.
               Likewise, if the duplicates handling is specified as
               sorted, then a nested index definition must exist.

User Action:   The index can not be created in this manner.  Recreate
               the index as a unique index, or with a nested
               duplicates index, specifying that the duplicates are to
               be sorted.

IOINDDUPINV,   sorted duplicates are only valid within a nested index
               definition

Explanation:   If the duplicates handling is specified as sorted, then
               a nested index definition must exist.

User Action:   The index can not be created in this manner.  Recreate
               the index without the duplicates are sorted clause or



                                  94

                                                RDMS Facility Messages





               with a nested duplicates index, specifying that the
               duplicates are to be sorted.

IOINDDUPKEY,   index definition contains an identical column reference
               in both keys

Explanation:   The index definition repeated a reference to a column
               in a table within the primary index key and the
               duplicates index key.  This usage is not allowed within
               an INDEX ONLY index definition which has duplicates
               sorted.

User Action:   The index can not be created in this manner.  Recreate
               the index using making sure that the column values
               within the primary index key are not reused within the
               duplicates index key.

IOINDDUPSORT,  An INDEX ONLY index must be unique or have duplicates
               sorted.

Explanation:   You attempted to create an INDEX ONLY index which is
               not unique and does not have duplicates sorted.  This
               operation is not allowed.

User Action:   An INDEX ONLY index must be unique or have duplicates
               sorted.  Please create the index accordingly.

IOINDEXISTS,   An INDEX ONLY index has already been defined on this
               table

Explanation:   You attempted to create additional secondary indices on
               an INDEX ONLY table.  This operation is not allowed.

User Action:   If secondary indices are required, then do not use
               INDEX ONLY indices.

IOINDONLY,     An INDEX ONLY index must be the only index defined on
               the table

Explanation:   You attempted to create an INDEX ONLY index on a table
               which already had indices defined upon the table.  This
               operation is currently restricted.

User Action:   Either use a sorted or hashed secondary index on the
               table, or delete the currently defined indices on this
               table, so that the INDEX ONLY index can be created.

IOINDTBLDATA,  An INDEX ONLY index can only be created on an empty
               table

Explanation:   You attempted to create an INDEX ONLY index on a table



                                  95

RDMS Facility Messages





               which already contains data.  This operation is
               currently restricted.

User Action:   Either create a sorted or hashed secondary index on the
               table, or unload the data from the table so that the
               INDEX ONLY index can be created.

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.

JOIN_CTX_UPD,  relation <str> is part of a join - cannot be updated

Explanation:   You tried to modify or erase records from a relation
               that is joined with other relations.

User Action:   Redefine the query so that the relation you are trying
               to update is not directly joined to other relations.

LASTARENOLIMIT, last area clause must not have a LIMIT clause

Explanation:   You specified limits (RDO) or BLR (DSRI) for the data
               to be inserted into the last area listed.

User Action:   Do not specify a limit for the data in the last storage
               area.

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.

User Action:   Use the /OUTPUT qualifier to specify an output filename
               when database replication is started on the master
               database.





                                  96

                                                RDMS Facility Messages





LEVEL_MISMATCH, the table/subquery nesting levels in the query outline
               do not match the query

Explanation:   The subquery hierarchy of the query outline does not
               match the subquery hierarchy of the query.  Subqueries
               or tables can be omitted from the query outline, but
               for each subquery that is present, all containing
               subqueries must also be present.

User Action:   Edit the query outline to correct the inconsistency, or
               regenerate a new outline by running the optimizer.
               Then make the desired modifications to the new outline.

LISTAREAFULL,  the areas specified in the list storage map for <str>
               are full

Explanation:   The areas specified for the table or column have
               returned errors during file extension operations.  If
               these are WORM areas, they may be marked as "WORM
               device full".

User Action:   Consider adding more areas to the storage map or moving
               the areas to a higher capacity device.  Refer to the
               ALTER facility or RMU MOVE command documentation for
               clearing the full flag for WORM areas.

LISTNODEFAULT, default list storage area "<str>" must be specified in
               storage map

Explanation:   The default list storage area (defined using the CREATE
               DATABASE statement) must be used as a catch all for
               list mappings.  This enables the system table LIST OF
               BYTE VARYING to be automatically mapped to this storage
               area.

User Action:   Consult the SQL Reference Manual for correct LIST
               storage map syntax.  There should be an IN clause which
               specifies the default list storage area, without a FOR
               clause.

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



                                  97

RDMS Facility Messages





               added the the database.

LOGAIJBCK,     backed up <num> <str> transaction(s) at <time>

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



                                  98

                                                RDMS Facility Messages





               being modified.

LOGRECOVR,     <num> transaction(s) <str>

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.

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.



                                  99

RDMS Facility Messages





User Action:   Try starting Hot Standby after the AIJ Log Roll-Forward
               server has completely stopped execution.

MAPAREAINUSE,  area <str> already specified for map <str> in partition
               <num>

Explanation:   You used the area name more than once in the same
               storage map.  The area can only be used once for table
               storage maps, and can not appear more than once in an
               area set for a list (segmented string) storage map.

User Action:   Use the area name only once in the storage map or list
               area set definition.

MAPBLRMISSING, one or more areas is missing a limitation (WITH LIMIT
               clause)

Explanation:   You have not specified WITH LIMIT clauses for all
               storage areas in the map which are required to have
               limits.  You must omit limits on all storage areas for
               RANDOMLY ACROSS maps, or you may omit the WITH LIMIT
               clause for the final storage area for value partitioned
               maps.  If you specified that the map partitioning is
               NOT UPDATABLE then you are creating a map that enforces
               strict data partitioning.  Therefore, you must provide
               WITH LIMIT clauses for each area (and optionally the
               last area) in the map.

User Action:   Correct the storage map creation statement to provide
               WITH LIMIT clauses where needed.

MAPNMINUSE,    map name <str> is already in use in this database

Explanation:   You tried to define a map or index using a name that
               already exists in the database.

User Action:   Use a name that has not already been used in the
               database.

MAPNOTCHG,     map "<str>" has not been changed

Explanation:   The specified storage map was not been altered or
               renamed.

User Action:   Correct the problem and try the metadata update again.

MAPREFAREA,    error deleting storage area <str> referenced by <str>

Explanation:   You attempted to delete a storage area currently
               referenced by a storage map.





                                 100

                                                RDMS Facility Messages





User Action:   Make sure the storage area you wish to delete is empty
               and no storage maps refer to it.

MAXMINSEQ,     maximum or minimum sequence value has been reached

Explanation:   The maximum value for an ascending sequence or the
               minimum value for a descending sequence has been
               reached.  There are no more sequence values available.

User Action:   Alter the sequence to increase the maximum value for an
               ascending sequence or decrease the minimum value for a
               descending sequence.  Alternatively, alter the sequence
               to enable the CYCLE attribute.

MAXRECLIM,     query governor maximum limit of rows has been reached

Explanation:   The query governor quota of the maximum number of rows
               has been reached.

User Action:   Please refer to the documentation on the setting of
               query governor limits.

MAXRELVER,     exceeded maximum table (relation) identifier

Explanation:   No more table (relation) identifiers are available.

User Action:   Unload your database, recreate the database, and reload
               using the EXPORT/IMPORT utilities or using programs.

MAXRTNVER,     exceeded maximum routine/module identifier

Explanation:   No more routine/module identifiers are available.

User Action:   Unload your database, re-create the database, and
               reload it by using the EXPORT/IMPORT utilities or by
               using programs.

MAXTIMLIM,     query governor maximum timeout has been reached

Explanation:   The query governor quota of the maximum number of
               seconds that a database request can be optimized has
               been reached.

User Action:   Please refer to the documentation on the setting of
               query governor limits.

MAXVIEWID,     exceeded maximum view identifier

Explanation:   No more view identifiers are available.

User Action:   Unload your database, recreate the database, and reload



                                 101

RDMS Facility Messages





               using the EXPORT/IMPORT utilities or using programs.

MAX_CCTX,      exceeded maximum allowable context number

Explanation:   The number of contexts used in a request exceeds the
               limit, where a context is defined as a cursor value
               source or a query/subquery.  (Note that the term
               "context" is used differently here than elsewhere in
               Oracle Rdb.) A cursor value source consists of a table,
               aggregate, EXISTS predicate, UNIQUE predicate,
               quantified predicate or UNION clause in a request.  In
               terms of BLR, a cursor value is any of the following
               BLR$K_ objects:  AGGREGATE, ALL, ANY, ANY2, AVERAGE,
               COUNT, FROM, MAXIMUM, MERGE, MINIMUM, RELATION,
               RELATION_ID, TOTAL, UNIQUE, VIA.  Cursor values are
               obtained from a user-generated request; or from the BLR
               associated with a view, constraint, trigger, or other
               metadata object.  Cursor queries/sub-queries are
               produced for each record selection expression (RSE) and
               FETCH statement.

User Action:   If you called Oracle Rdb, check the query string and
               simplify if possible.  Otherwise, Contact your Oracle
               support representative for assistance.

MAX_CEQV,      exceeded maximum allowable equivalence number

Explanation:   The number of join equivalences used in a request
               exceeds the limit.  The limit is 32 in Rdb versions
               prior to 7.0, and it is 1024 in later versions.

User Action:   Break up the query into separate requests, materialize
               the results of each request, and then join each result
               to get the intended result.  If temporary table support
               is available in the version of Rdb you are using, you
               can use the temporary tables to store the result of
               each request.

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



                                 102

                                                RDMS Facility Messages





               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.

MISSINGINV,    existing records in relation <str> would violate VALID
               IF expression

Explanation:   When a new field is added to a relation, previously
               stored records will have the new field's value set to
               NULL (MISSING).  In your relation, the VALID IF
               constraint defined for the new field is violated by
               this action.

User Action:   Modify all the records where the new field is set to
               NULL (MISSING) to have a non-null value, or change the
               VALID IF clause for the field to allow MISSING values.

MISSINVSEG,    Missing value is an invalid segmented string attribute

Explanation:   The missing value attribute cannot be specified with a
               domain or column which has a datatype of segmented
               string.

User Action:   Ensure that the missing value attribute is not
               specified with a segmented string on the domain or
               column.

MIXCLUST,      relation or index may not be stored in mixed and
               uniform areas

Explanation:   You attempted to define a storage map that refers to
               both mixed and uniform areas.

User Action:   Define the storage map to refer to only uniform areas
               or only mixed areas.

MODEXTS,       there is another module named <str> in this database

Explanation:   The module name you tried to define or on which you
               attempted to perform an operation, already exists in
               this database.  Note that stored and non-stored modules
               share the same name space.

User Action:   Use another module name.  If you have already invoked a



                                 103

RDMS Facility Messages





               non-stored module, then disconnect the session before
               performing any operation on the stored module.
               Alternatively, if you have already invoked a stored
               module, then disconnect the session before performing
               any operation on the non-stored module.

MODIDNEXTS,    module ID, <num> does not exist in this database

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

User Action:   Invoke the correct database.  Specify the module ID
               correctly.

MODNEXTS,      module <str> does not exist in this database

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

User Action:   Invoke the correct database.  Spell the module name
               correctly.  Check the name of the module and try the
               command again.

MODNOTDEL,     module "<str>" has not been deleted

Explanation:   The specified module was not deleted.

User Action:   Correct the problem and try the metadata update again.

MODRTNNEXTS,   no routines with module ID <num>

Explanation:   There are no routines with the specified module ID in
               the current database.

User Action:   Invoke the correct database.  Specify the module ID
               correctly.

MONALSTART,    database monitor is already running

Explanation:   The database monitor has previously been started.

User Action:   Continue or see your system manager.

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
               program was running to see messages relating to the
               monitor error.



                                 104

                                                RDMS Facility Messages





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.

MSSINCCOL,     MISSING VALUE is incompatible with datatype of column
               <str>.<str>

Explanation:   The specified MISSING_VALUE (RDO) or MISSING VALUE
               (CDD/Rep) is not compatible with the datatype of the
               column (field).

User Action:   Ensure that the datatype of the column and the MISSING
               VALUE are consistent.  Check the domain used by column
               to verify consistency between datatypes and MISSING
               VALUEs.

MSSINCDOM,     MISSING VALUE is incompatible with datatype of domain
               <str>

Explanation:   The specified MISSING_VALUE (RDO) or MISSING VALUE
               (CDD/Rep) is not compatible with the datatype of the
               domain (global field).

User Action:   Ensure that the datatype of the domain displayed in the
               error message is consistent with the MISSING_VALUE
               (RDO) or MISSING VALUE (CDD/Rep) of the domain.

MULTCHGAREA,   multiple references to area <str> in same CHANGE
               DATABASE command

Explanation:   You attempted to change one storage area multiple times
               in your CHANGE DATABASE statement.

User Action:   Combine your changes to one storage area to one clause.

MULTPLACEVIA,  storage map command contains multiple PLACEMENT VIA
               clauses

Explanation:   The storage map command contained either multiple
               PLACEMENT VIA clauses or both a PLACEMENT VIA and NO
               PLACEMENT VIA clause.



                                 105

RDMS Facility Messages





User Action:   Refer to the documentation on storage map usage for
               more information on how to use the command.

MULTSCHEMNODIS, the multischema database attribute can not be disabled

Explanation:   You attempted to change the database to be NO
               MULTISCHEMA.  This is not supported.

User Action:   Please use EXPORT and IMPORT to effect this change.

MULTSCHEMNOW,  the database is already a multischema database

Explanation:   You attempted to change the database to be MULTISCHEMA
               when it was already.

User Action:   No user action required.  The database has the
               multischema attribute.

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.

NDXPMTDUPS,    text compressed indices must permit duplicates

Explanation:   You attempted to create an index with duplicates not
               allowed using the DUPLICATES NOT ALLOWED clause.
               However, you cannot use the DUPLICATES NOT ALLOWED
               clause when defining a text compressed index.

User Action:   Do not use the DUPLICATES NOT ALLOWED clause when you
               define a text compressed index.

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.





                                 106

                                                RDMS Facility Messages





User Action:   Examine the secondary message for more information.

NOACCSEGSTR,   cannot access buffer for segmented string

Explanation:   At least part of the user's buffer is not accessible.

User Action:   Check program logic; the segmented string buffer
               address and/or length is incorrect.

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
               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



                                 107

RDMS Facility Messages





               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
               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.

NOALTIOIND,    ALTER is not allowed on an INDEX ONLY index

Explanation:   You have attempted to alter an INDEX ONLY index.  This
               operation is not allowed.

User Action:   Re-evaluate why this change is necessary on the INDEX
               ONLY index.  If the change is necessary then drop the
               INDEX ONLY index which will move the data from the
               index into the table.  The action of dropping the INDEX
               ONLY index will convert the INDEX ONLY table into a
               regular table.  The user can then alter the table, and
               recreate the INDEX ONLY index.





                                 108

                                                RDMS Facility Messages





NOALTIOTBL,    ALTER is not allowed on an INDEX ONLY table

Explanation:   You have attempted to alter an INDEX ONLY table.  When
               an INDEX ONLY index is defined on a table, the table is
               then labeled an INDEX ONLY table.  This operation is
               not allowed.

User Action:   Re-evaluate why this change is necessary on the INDEX
               ONLY table.  If the change is necessary then drop the
               INDEX ONLY index which will move the data from the
               index into the table.  The action of dropping the INDEX
               ONLY index will cause the the INDEX ONLY table to
               revert to regular table, and the alter table operation
               will be allowed.

NOALTSUBIND,   A duplicates sub-index may not be altered

Explanation:   You attempted to ALTER a sub-index which has been
               defined to manage duplicates within an INDEX ONLY
               index.  This is not permitted.

User Action:   If you wish to ALTER the sub-index, then you must drop
               the INDEX ONLY index, and recreate the index and the
               sub-index.

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.

NOCACHEEXT,    cache "<str>" not defined in the database

Explanation:   A cache mentioned in the ALTER DATABASE statement is
               not defined in the database.

User Action:   Reenter your statement with valid cache names.

NOCATALOG,     catalog <str> does not exist - alter or drop not
               possible



                                 109

RDMS Facility Messages





Explanation:   The catalog does not exist.

User Action:   Repeat the command with a name of a catalog which
               exists.

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).

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.

NOCHGRDBSYS,   cannot change RDB$SYSTEM storage area explicitly

Explanation:   You included a CHANGE STORAGE AREA RDB$SYSTEM clause in
               the CHANGE DATABASE statement.

User Action:   Issue the CHANGE DATABASE statement without this
               clause.  When you change database-wide parameters, the
               RDB$SYSTEM parameters are automatically changed.

NOCHGVW,       the definition of view "<str>" may not be changed

Explanation:   An attempt to alter a view was made that is not
               supported.

User Action:   You must use the ALTER VIEW statement to change
               attributes of the view.  Correct the statement and try
               again.

NOCMPLXMAP,    can not use complex map for non-empty table

Explanation:   You specified a storage map for a table which has data
               in it, however, the storage map was not a simple map.
               You may only specify a simple map when the table
               contains data.  This map simply describes the state of
               the currently stored data.  Once defined the ALTER
               STORAGE MAP statement can be used to apply a more
               complex mapping to the table.





                                 110

                                                RDMS Facility Messages





User Action:   Redefine the storage map and ensure that the storage
               map specifies only the default storage area, that there
               is no PLACEMENT VIA INDEX clause, that the thresholds
               and compression attributes are not specified, and that
               the COLUMNS clause is not used to vertically partition
               the table.

NOCOROUTINE,   function can not act as a co-routine

Explanation:   A stored routine is invoked from another BLR program
               and so can not synchronize with a host program using
               BLR$K_SEND nor BLR$K_RECEIVE

User Action:   Remove or conditionalize references to these BLR
               statements

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.

NOCRESYNONYM,  target object for "<str>" can not be resolved

Explanation:   A synonym chain is formed when synonyms reference other
               synonyms.  This error occurs that synonym chain has
               been broken using DROP SYNONYM ...  CASCADE or a loop
               is formed because ALTER SYNONYM references a target
               synonym already appearing in the chain.

User Action:   This problem is detected during CREATE and ALTER
               SYNONYM.  This statement has failed, repeat the
               statement with a corrected synonym reference which
               avoids this error.

NODACINDEX,    index "<str>" in area does not correspond to table

Explanation:   DROP STORAGE AREA <name> CASCADE was used in a case
               where it cannot be simply applied.

User Action:   Please review and correct the operation and issue the
               appropriate set of commands.

NODACMTCHPART, index partitioning for index "<str>" does not match
               storage map "<str>"



NODACSTRICT,   PARTITIONING UPDATABLE specified for storage map
               "<str>"



                                 111

RDMS Facility Messages





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.

User Action:   Correct the condition and try again.

NODELCACHE,    the default cache RDB$CACHE may not be deleted

Explanation:   You attempted to drop the default cache RDB$CACHE.
               This is not permitted.

User Action:   Make sure the cache you drop is not the default cache
               RDB$CACHE.

NODELPRIVANSI, privileges may not be deleted in an ANSI database

Explanation:   You attempted to delete a privilege in an ANSI-style
               database.

User Action:   You cannot delete a privilege in an ANSI-style
               database.

NODELRESAREA,  "<str>" is used as a default area and may not be
               deleted

Explanation:   You attempted to drop either the default storage area,
               or the default template area.  This is not permitted.

User Action:   Make sure the area you drop is not reserved as a
               special area in this database.

NODELSEGSTR,   the segmented string storage area, <str> can not be
               deleted

Explanation:   You attempted to delete the segmented string storage
               area.

User Action:   Make sure the storage area you wish to delete is not
               the segmented string storage area.

NODELSUBIND,   A duplicates sub-index may not be deleted

Explanation:   You attempted to drop a sub-index which has been
               defined to manage duplicates within an INDEX ONLY
               index.  This is not permitted.

User Action:   If you wish to delete the INDEX ONLY index, then this
               will in turn delete the sub-index.

NODEVDIR,      filename does not include device and directory



                                 112

                                                RDMS Facility Messages





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.

NODMAX,        <num> number of cluster nodes is greater than the
               Oracle Rdb maximum of <num>

Explanation:   The number of cluster nodes that may access the
               database you specified is too large.

User Action:   Refer to documentation, and try another value.

NODMIN,        <num> number of cluster nodes is less than the Oracle
               Rdb minimum of <num>

Explanation:   The number of cluster nodes that may access the
               database you specified is too small.

User Action:   Refer to documentation, and supply another value.

NODUPSANSI,    no duplicate identifiers allowed in ANSI ACL

Explanation:   Databases defined as ANSI compliant are restricted to a
               single instance of a UIC.

User Action:   Enter a protection command changing the user's
               protection to what is desired rather than having two
               entries in the ACL for the same user.

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.

NOEXTFUNC,     external routines have not been initialized

Explanation:   The routine to initialize the OpenVMS client site
               external routine interface has failed.



                                 113

RDMS Facility Messages





User Action:   No user action is available at this time.

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.

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.

NOEXTSEC,      external database security checking is not supported

Explanation:   SECURITY CHECKING IS EXTERNAL is not supported on NT.

User Action:   Specify SECURITY CHECKING IS INTERNAL.

NOEXTUNRES,    cannot extract, AIJ file <str> has unresolved
               transactions

Explanation:   The AIJ file being extracted has unresolved distributed



                                 114

                                                RDMS Facility Messages





               transactions.  AIJ extraction cannot handle unresolved
               transactions, so it must abort.

User Action:   Use a complete AIJ file with no unresolved distributed
               transactions.

NOGRPANSI,     no group UIC's allowed in ANSI database access control
               list

Explanation:   Databases defined as ANSI compliant are restricted to
               single user UIC's in the access control entry, except
               for PUBLIC.

User Action:   Enter a protection command for each user rather than
               referring to them as a group, or give privilege to
               PUBLIC.

NOIDENTANSI,   no identifiers allowed in ANSI database access control
               list

Explanation:   Databases defined as ANSI compliant are restricted to
               single user UIC's in the access control entry, except
               for PUBLIC.  No system or general identifiers are
               allowed.

User Action:   Enter a protection command for each user rather than
               referring to them as a group, or give privilege to
               PUBLIC.

NOINTERUNI,    no interval may be specified on uniform format pages

Explanation:   You attempted to specify a SPAM interval on a PAGES
               UNIFORM storage area.

User Action:   Do not specify an interval, as one will be
               automatically determined for you.

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.

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



                                 115

RDMS Facility Messages





               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.

NOMAPONVIEW,   a storage map may not be defined for a view

Explanation:   You tried to define a storage map for a view.

User Action:   You must define the storage map for a relation, not a
               view.

NOMETADATA,    metadata operations are disabled

Explanation:   The database has been setup with DDL operations
               disabled, using the METADATA CHANGES ARE DISABLED
               clause on CREATE or ALTER DATABASE.  You may not
               CREATE, DROP or ALTER database objects.

User Action:   The database administrator must alter the database to
               re-enable metadata changes before this command can be
               used.

NOMETAUPD,     metadata updates are prohibited until CONVERT is
               COMMITTED

Explanation:   Metadata updates are not permitted unless the CONVERT
               operation has been committed or rolled back.

User Action:   Use RMU CONVERT to COMMIT or ROLLBACK the last CONVERT
               operation.

NOMETSYSREL,   operation illegal on system defined metadata

Explanation:   You attempted to define, delete, or change an index,
               constraint, or trigger on one or more Oracle Rdb system
               relations.  Or you attempted to drop or alter an Oracle
               Rdb system sequence.  Such changes, if permitted, could
               render the database unusable.

User Action:   Do not attempt any of these modifications to the system
               relations or system sequences.

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



                                 116

                                                RDMS Facility Messages





               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
               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



                                 117

RDMS Facility Messages





               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.

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.

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.



                                 118

                                                RDMS Facility Messages





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.

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.

NOOVERIOIND,   Overflow area is only allowed during INDEX ONLY index
               creation

Explanation:   You have attempted to create an Overflow area which is
               not associated with an INDEX ONLY index.  This
               operation is not allowed.

User Action:   Only create an Overflow area during an INDEX ONLY index
               creation.

NOPAGELOCK,    page level locking can not be specified for <str>

Explanation:   Page level locking can never be applied to RDB$SYSTEM
               or the DEFAULT STORAGE AREA by CREATE, ALTER or IMPORT
               DATABASE.

NOPLACEANSI,   no user placement clauses allowed in ANSI ACL

Explanation:   Placement of ANSI database users' access control
               entries is controlled by the database facility.

User Action:   Enter a protection command without specifying either



                                 119

RDMS Facility Messages





               the POSITION or AFTER clause.

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.

NORBK_MDBTRAN, a server procedure can not rollback or commit a
               multi-database transaction

Explanation:   You attempted to ROLLBACK or COMMIT in a
               multistatement, or stored procedure which executes as
               part of a transaction which spans multiple databases.
               This is not permitted because the server procedure is
               not aware of the other databases in the transaction.

User Action:   Instead execute a single statement ROLLBACK or COMMIT
               which is perform by the client and informs all
               associated databases.

NORBK_MODINUSE, an active procedure may not rollback its own CREATE
               statement

Explanation:   A stored procedure attempted to ROLLBACK the
               transaction in which the procedure was created.  This
               is not permitted.

User Action:   Before executing the procedure COMMIT the transaction
               in which the procedure was created.  Or, execute
               ROLLBACK in the context of a committed object.

NORECURSION,   no recursive routine calls permitted

Explanation:   This release of Rdb does not support recursive calls to
               procedures or functions.  This routine is already
               active.

User Action:   Correct the usage of the function or procedure.

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.

NORTNENTRY,    routine "<str>" can not be used, entry point "<str>"
               not found



                                 120

                                                RDMS Facility Messages





Explanation:   The specified external routine can not be used because
               the specified entry point symbol was not found.

User Action:   Verify that the external routine definition location
               specification references the desired image, check the
               corresponding routine source for the global symbol
               definition, and verify that the associated image
               construction procedure makes the global entry symbol
               available to the image activator.

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.

NOSCHEMA,      schema <str> (<num>) does not exist, alter or drop not
               possible

Explanation:   The schema does not exist.

User Action:   Repeat the command with a name of a schema which
               exists.

NOSEQENT,      sequence id <num> has no valid entry in the root file

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





                                 121

RDMS Facility Messages





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.

NOSOL_FOUND,   No possible solution has been found by Rdb optimizer

Explanation:   No possible solution has been found by Rdb optimizer
               for the following reason:  - Full outer join query with
               cross strategy is not possible.  Only MATCH join
               execution is allowed for full outer join.

User Action:   Check if the join keys of the join predicates are
               compatible in data type.  If the keys are not
               compatible, please apply a CAST function to make it
               compatible data type to be used as a join key in a
               match join strategy.

NOSTAREAEXT,   storage area <str> not defined in the database

Explanation:   A storage area mentioned in the ALTER DATABASE
               statement is not defined in the database.

User Action:   Reenter your statement with valid storage area names.

NOSTATS,       statistics are not enabled for <str>

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



                                 122

                                                RDMS Facility Messages





               the database header information.

NOSUCHPRF,     unknown profile user or role

Explanation:   The user or role that you have specified does not exist
               in this database or at the operating system level, when
               identified externally.

User Action:   Specify only valid (known) users or roles or create
               them.

NOSUCHTRANS,   translation name <str> is invalid or undefined

Explanation:   The translation name is not known to Oracle Rdb.

User Action:   Check the translation name to ensure it is valid.

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
               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.

NOSYNONYM,     synonym "<str>" does not exists in this database

Explanation:   This synonym could not be found.  This may indicate an
               error in the synonym name.

User Action:   Please repeat the command using an object which exists.

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".

NOTBOOL,       expression in AND, OR, or NOT was not a Boolean



                                 123

RDMS Facility Messages





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
               disk oriented device type.

User Action:   Check the file name for a proper disk device type.

NOTEMPHASH,    cannot define an index of TYPE HASHED on a temporary
               table

Explanation:   Temporary tables only support indexes of TYPE SORTED.
               You attempted to create an index of TYPE HASHED on a
               temporary table.

User Action:   Redefine the index with TYPE SORTED for a temporary
               table.

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.

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.





                                 124

                                                RDMS Facility Messages





NOTHRESUNI,    no thresholds may be specified on uniform format pages

Explanation:   You attempted to specify thresholds on PAGES UNIFORM
               storage area.

User Action:  

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.

NOTLOCALRTN,   invalid call to a local routine - in the wrong context

Explanation:   The routine is declared as LOCAL and may only be called
               by routines in the same owning module.

User Action:   Call the routine from within the module, or use USAGE
               IS GLOBAL for the routine so it can be called outside
               the module.

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.

NOTRIGRTN,     this stored routine may not be called from a trigger

Explanation:   Not all stored routines may be called from a trigger
               condition or trigger action.  Routines which perform



                                 125

RDMS Facility Messages





               the following actions may not be called from triggers:
               includes the DELETE, INSERT, UPDATE data manipulation
               commands, includes transaction commands SET
               TRANSACTION, COMMIT, or ROLLBACK, or calls a stored
               routine using the CALL statement, or references a user
               defined SQL function.

User Action:   Correct the function or procedure to comply with these
               restrictions.

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.

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_LARDY,     area for <num>:<num>:<num> not in proper ready mode

Explanation:   You attempted to access a logical area for which you
               have not declared your intentions.

User Action:   Retry a ready operation later.

NOT_LICENSED,  system is not licensed for use of database software

Explanation:   A Oracle Rdb kit has not been properly installed on the
               system.





                                 126

                                                RDMS Facility Messages





User Action:   Check to see that you are licensed to use Oracle Rdb;
               and if you are, install or re-install the Oracle Rdb
               kit.

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_RESERV,    attempt to access relation not mentioned in reserving
               list

Explanation:   You tried to access a relation not mentioned in the
               reserving list of your START_TRANSACTION statement.

User Action:   Start a new transaction and include the required
               relations in the reserving list.

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.

NOT_VALID_FR,  field <str> in relation <str> fails validation

Explanation:   When the CHANGE FIELD ...  VALID IF operation was
               attempted, data that violated the specified validation
               criteria was found.

User Action:   Either change the validation criteria or change the
               data.

NOUSERPRF,     operation denied - user "<str>" does not exist in this
               database

Explanation:   The current user has not been defined in the profiles
               table.  Undefined users are restricted to a subset of
               DDL operations.

User Action:   Create the user in the database using the SQL CREATE
               USER command.

NOVIEWIND,     cannot define an index for a view



                                 127

RDMS Facility Messages





Explanation:   You attempted to define an index for a view.

User Action:   Define an index for the field in the relation named in
               the view definition.

NOWILD,        no wild cards are allowed in the file specification

Explanation:   Wild-card characters ("*" and "%") cannot be used in
               that file specification.

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_NEQFOJ,     non-equi full outer join is not supported

Explanation:   An attempt was made to specify a full outer join
               without using an equijoin condition in the ON clause of
               the joined table expression.  Full outer joins that do
               not include an equijoin condition are not supported in
               the current version of Oracle Rdb.

User Action:   Specify a full outer join with at least one equijoin
               condition, or rephrase the query by using the UNION
               operator to get the intended full outer join result.

NULLRTNPRM,    parameter <num> can not be a NULL value, external
               routine "<str>" not invoked

Explanation:   External routine was passed a NULL value as parameter.

User Action:   Check the corresponding external routine invocation
               expression for NULL values, and reissue the query.

OBJ_INUSE,     object "<str>" is referenced by <str> (usage:  <str>)

Explanation:   You attempted to delete a database object, but the
               object is used by another object or other definition as
               described in the message text.

User Action:   First, review the database design; then, if desired,
               delete the other definition which references this
               object, and then delete this object.





                                 128

                                                RDMS Facility Messages





OBSUSERMU,     specified command is obsolete, please use RMU
               equivalent

Explanation:   You requested that an RDO OPEN, CLOSE or RECOVER
               statement be executed, perhaps with an older version of
               RDO.  These statements are no longer supported.

User Action:   Use the RMU/OPEN, RMU/CLOSE or RMU/RECOVER instead.

OBSVER,        obsolete version of database

Explanation:   You are trying to use an obsolete version of an Oracle
               Rdb database.

User Action:   Using an older version of Oracle Rdb, back up the
               database, and then restore it using your current
               version of Oracle Rdb.

OK_NO_ACE,     successful protection execution - no ACE returned

Explanation:   Indicates that no access control entry is returned.

User Action:   No user action.

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

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.

OPTDDLREC,     TSN <num>:<num> contains DDL information that cannot be
               optimized





                                 129

RDMS Facility Messages





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.

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



                                 130

                                                RDMS Facility Messages





               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
               /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.





                                 131

RDMS Facility Messages





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.

OUTLIDEXTS,    a query outline with mode <num> already exists for this
               query

Explanation:   The query outline ID and mode specified in your query
               outline definition is already used by another query
               outline in this database.

User Action:   Use another mode value that has not already been used.

OUTLINE_FAILED, could not comply with mandatory query outline
               directives

Explanation:   The query optimizer could not fully comply with the
               directives in the query outline, and the outline
               indicated that compliance with the outline was
               mandatory.

User Action:   Change the query outline to indicate that compliance is
               optional, or modify the outline constraints.

OUTLNMINUSE,   there is another query outline named <str> in this
               database

Explanation:   The query outline name you are trying to define already
               exists.

User Action:   Use another query outline name, or if the query name
               has been automatically generated for you, use another
               mode value.

OUTLNOEXI,     query outline <str> does not exist in this database

Explanation:   The query outline name you tried to use does not exist.

User Action:   Use another query outline name.

OUTLNOID,      object name or signature required

Explanation:   You have not provided appropriate query identification
               to indicate to which query the outline definition
               should apply.  You must supply either a request
               signature or the name of an existing stored object
               within the query outline definition.



                                 132

                                                RDMS Facility Messages





User Action:   Provide either an object name or request signature
               within your query outline definition.

OUTLNOTAPPL,   a query outline could not be generated for this
               procedure

Explanation:   You tried to create a query outline for a procedure
               that does not contain any statement to which a query
               outline can be applied.  Query outlines are only
               applicable to statements that contain record selection
               expressions.

User Action:   Try another procedure.

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.

PARTDTXNERR,   error when trying to participate in a distributed
               transaction

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.

PARTEXTS,      partition "<str>" already exists for this map or index
               "<str>"

Explanation:   The name specified for this CREATE/ALTER STORAGE MAP or
               INDEX has been used before.

User Action:   Please restate the command using a unique partition
               name.

PARTNEXTS,     partition "<str>" does not exist in this map or index



                                 133

RDMS Facility Messages





               "<str>"

Explanation:   The name specified for this ALTER STORAGE MAP or INDEX
               does not exist in this database.

User Action:   Please restate the command using a known partition
               name.

PARTNOFOLLOW,  partition "<str>" has no following partition in map
               "<str>" - drop not allowed

Explanation:   You performed a DROP PARTITION on the final partition
               of an an index or storage map.  DROP wants to migrates
               the data to the next partition in the map, but can not
               if this is the last partition.

User Action:   Use MOVE to move the data to another partition, or DROP
               INDEX or DROP STORAGE MAP to remove the partition.

PARTOPERBAD,   operator used in partitioning BLR is bad

Explanation:   The BLR specified for a storage map includes an
               unsupported operator.

User Action:   Contact your Oracle support representative for
               assistance.

PGPEXISTS,     <str> "<str>" has already been granted to <str> "<str>"

Explanation:   The role or profile has already been granted to the
               specified user.

User Action:   None.

PGPNEXISTS,    <str> "<str>" has not been granted to <str> "<str>"

Explanation:   The role is not granted for the specified user.

User Action:   The role must be granted first.

PLACEVIA1ST,   PLACEMENT VIA must only be on the first vertical
               partition

Explanation:   The storage map command contained multiple PLACEMENT
               VIA INDEX clauses.  This clause must only appear on the
               first vertical partition, and not on subsequent
               partitions.

User Action:   Please refer to the documentation on storage map usage
               for more information on how to use this clause.





                                 134

                                                RDMS Facility Messages





PREMEOF,       premature end of file encountered in <str>

Explanation:   A premature end-of-file was encountered while reading
               the specified file.

PRFCREATED,    some users or roles were created

Explanation:   Some of the users or roles specified did not exist in
               the profiles table, so they were created.

User Action:   This is just a warning.  If you mistyped a user or role
               name, you may want to delete the user or role that was
               created and re-execute the operation with the correct
               name.

PRFDISABLED,   user or role was marked as disabled

Explanation:   The user or role does not exist on the system.
               Therefore, it was marked as disabled in the
               RDB$PROFILES table.

User Action:   This is just for your information.  If you wanted this
               user to be enabled, they must be created at the
               operating system level and then be re-enabled.

PRFEXISTS,     a <str> already exists with the name "<str>"

Explanation:   The role, user or profile already exists in the
               database.

User Action:   Respecify using a name that has not been used
               previously.

PRFIDEXT,      name is used externally; potential name conflict

Explanation:   The name chosen for the role created is also used
               externally at the operating system level for a user,
               group, node or domain name.

User Action:   This is just a warning.  If you wish to use that name
               in the future, to define a profile for the external
               definition, then delete the profile just created and
               choose another name.

PRFINUSE,      entry "<str>" is referenced by <str> "<str>"

Explanation:   You attempted to delete a role, user or profile, but it
               uses or is used by another role, user or profile as
               described in the message text.

User Action:   Revoke the dependency between the roles, users and



                                 135

RDMS Facility Messages





               profiles specified and then drop this object.

PRFMISMATCH,   external identifier for "<str>" does not match current
               profile id for "<str>"

Explanation:   The user or role is identified externally.  Therefore,
               the external identifier for the new name must match the
               current profile id.  This is not true, in this case.

User Action:   Only rename externally identified users and roles, when
               the external name has changed.

PRFNEXISTS,    a <str> does not exist with the name "<str>"

Explanation:   The specified role, user or profile does not exist in
               the database.

User Action:   Respecify the name using a known profile name.

PRFNOTDEF,     <str> "<str>" has not been defined

Explanation:   The specified role, user or profile does not exist in
               the database.

User Action:   Respecify the name using a known profile name.

PRI_RELCONEXTS, cannot define multiple PRIMARY KEY constraints for a
               relation

Explanation:   An attempt has been made to define a second PRIMARY KEY
               constraint for a relation.  Only one is allowed.

User Action:   First, review the database design and defined
               relation-specific constraints; then, if desired, try
               the operation again specifying a constraint of a
               different type.

PRTNOTCOMPLETE, partition <str> still in build pending state

Explanation:   An ALTER INDEX ...  MAINTENANCE IS ENABLED statement
               failed because one or more index partitions are still
               in build-pending state.

User Action:   Use the ALTER INDEX ...  BUILD PARTITION, or ALTER
               INDEX ...  BUILD ALL PARTITIONS statement before using
               this statement.

QIOXFRLEN,     data transfer length error - expected <num>, actual
               <num>

Explanation:   The expected data-transfer length was not equal to the



                                 136

                                                RDMS Facility Messages





               actual data-transfer length.

User Action:   This is usually caused by a hardware problem.

QRYINVALID,    some queries have been marked invalid by metadata
               change

Explanation:   These are informational messages reported to the user
               when DROP TABLE or some other operation makes queries
               invalid.

User Action:   No user action is required, but database administrators
               should note that this metadata operation may cause
               queries to fail.

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.

User Action:   None.

QUIETPTREL,    released database quiet point at <time>

Explanation:   The database quiet point lock has been released.

User Action:   None.

RCHLENEXC,     row length or node size exceeds size of row cache -
               check cache attributes

Explanation:   This is an informational message that is reported when
               CREATE TABLE, CREATE INDEX, ALTER TABLE or ALTER DOMAIN
               cause a tables row size or index node to exceed that
               defined by the logical area row cache of the same name.

User Action:   The longer rows will no longer fit in the cache and
               therefore the row cache might not be effective.  The
               database administrator may need to adjust the row cache
               definition to compensate for this change.  Please note
               that row compression might allow some or all of the
               longer rows to fit within the row cache.

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.



                                 137

RDMS Facility Messages





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.

READONLY,      data in a read-only storage area may not be accessed
               for update

Explanation:   Your transaction attempted to access data in a
               read-only storage area for update.

User Action:   Explicitly specify the correct access mode for the
               data, or change the read-only area to a read/write
               area.

READONLYVAR,   variable (<num>) has been marked as CONSTANT and may
               not be updated

Explanation:   An attempt was made to assign a value to a CONSTANT,
               i.e.  not updatable variable.

User Action:   Correct the routine so that this variable is not marked
               as CONSTANT or is not updated.

READ_ONLY,     read-only area <str> must be readied in RETRIEVAL mode
               only

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.

REBUILDSPAMS,  SPAM pages should be rebuilt for logical area <str>



                                 138

                                                RDMS Facility Messages





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
               journal, using the DUMP/AFTER_JOURNAL command.

RECMAXEXC,     relation <str> definition exceeds data limit

Explanation:   You attempted to define or change a relation that is
               too large.

User Action:   Modify the relation definition.

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



                                 139

RDMS Facility Messages





               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.

REFINGFLDMSMTCH, a FOREIGN KEY referencing field does not correspond
               to a referenced field

Explanation:   The referencing fields of the FOREIGN KEY REFERENCES
               relation-specific constraint being defined do not
               correspond to the referenced fields of the referenced
               relation in either number or type (datatype, length,
               and scale).

User Action:   Choose referencing fields for the FOREIGN KEY which
               correspond to the referenced fields of the UNIQUE or
               PRIMARY KEY of the referenced relation.

RELALRDYMP,    there already exists a map for relation <str>

Explanation:   You tried to define a storage map for a relation that
               already has a storage map defined for it.

User Action:   Use CHANGE STORAGE MAP if you want to change the
               storage map for that relation.

RELCONEXTS,    there is another Relation constraint named <str> in
               this database

Explanation:   The relation-specific constraint specified already
               exists.

User Action:   Choose another relation-specific constraint name.

RELCONNOEXI,   table constraint <str> does not exist for the specified
               table

Explanation:   The specified table constraint does not exist for the
               table referenced in the ALTER TABLE or CHANGE RELATION
               statement.

User Action:   Check the name of the constraint and the name of the
               table using the SHOW statement.

RELEXI,        field <str> is used in relation <str>

Explanation:   The specified field you attempted to delete is used in
               a relation.





                                 140

                                                RDMS Facility Messages





User Action:   You should first change the relation to exclude this
               field, and then delete the field.

RELEXTS,       there is another relation named <str> in this database

Explanation:   The relation name you tried to define already exists.
               If the named table is a temporary table then it may be
               that a previous drop statement for a temporary table of
               the same name needs to be committed or rolled back.

User Action:   Use another relation name.  Or in the case of a
               temporary table the user may need to commit or rollback
               a previous drop statement.

RELFLDEX,      there is another field named <str> in relation <str>

Explanation:   The field name you want to define already exists in
               this relation.

User Action:   Choose another name for the field.

RELFLDNOC,     field <str> in relation <str> has not been changed

Explanation:   The field named was not changed.

User Action:   Correct the problem and then change the field.

RELFLDNOD,     field <str> has not been deleted from relation <str>

Explanation:   The field named was not deleted.

User Action:   Correct the problem and then delete the field.

RELINCOM,      relation <str> is referenced in COMPUTED BY field <str>
               in relation <str>

Explanation:   You attempted to delete a field from a relation, but
               the field is used in a COMPUTED BY field in another
               relation.

User Action:   First, review the database design; then, if desired,
               delete the COMPUTED BY field, and then delete the field
               from the relation.

RELMODEXI,     relation "<str>" referenced in the default transaction
               for module "<str>"

Explanation:   An attempt was made to perform DROP TABLE on a table
               referenced by the RESERVING clause in the default
               transaction for a module.





                                 141

RDMS Facility Messages





User Action:   First, review the database design; then, if desired,
               drop the module, and then delete the relation.  Use the
               CASCADE option to avoid this error and leave the module
               intact.  Note that attempts to use the module without
               re-creating the table will fail.

RELNEXTS,      relation <str> does not exist in this database

Explanation:   The relation name you tried to use does not exist.

User Action:   Use another relation name.

RELNOEXI,      relation <str> does not exist in this database

Explanation:   The table or view that was referenced was not found.

User Action:   Check the name of the relation using the SHOW command.

RELNOTCHG,     relation <str> has not been changed

Explanation:   The specified relation was not changed.

User Action:   Correct the problem and retry the metadata update.

RELNOTDEL,     relation <str> has not been deleted

Explanation:   The specified relation was not deleted.

User Action:   Correct the problem and retry the metadata update.

RELNOTEMPTY,   table "<str>" has data in it

Explanation:   You attempted to create or drop a storage map for a
               table that contains data, and that operation is not
               allowed.

User Action:   If this error was reported for DROP then you should
               drop the table to delete the data.  If this error was
               reported from CREATE then check that the map being
               defined is a simple map (see secondary message).

RELNOTTRUNC,   relation "<str>" has not been truncated

Explanation:   The specified relation was not truncated.

User Action:   Correct the problem and retry the TRUNCATE statement.

RELUSETRA,     relation <str> is used in a transferred definition

Explanation:   The specified field is used in the specified relation.
               The relation is involved in a DDAL transfer definition.



                                 142

                                                RDMS Facility Messages





User Action:   You must delete the DDAL transfer definition before
               modifying the field.

REL_RTNEXI,    relation "<str>" is referenced in routine "<str>"

Explanation:   You attempted to delete a relation, but the relation is
               used in a routine.

User Action:   First, review the database design; then, if desired,
               delete the routine and then delete the relation.

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.

REQPBLCANSI,   identifier for [*,*] required in ANSI ACL

Explanation:   Databases defined as ANSI compliant are restricted to
               always having an identifier [*,*] even if this
               identifier is not allowed any access to the entity.

User Action:   Enter a protection command changing the [*,*]
               protection to none rather than deleting the entry in
               the ACL.

REQUNIFORM,    storage area RDB$SYSTEM must contain uniform format
               pages

Explanation:   You attempted to assign PAGE FORMAT IS MIXED to
               RDB$SYSTEM storage area.

User Action:  

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.

RLCREFDBYRLC,  relation constraint <str> is referenced by relation
               <str> constraint <str>

Explanation:   The UNIQUE or PRIMARY KEY relation-specific constraint
               that you tried to delete with the DELETE RELATION or
               CHANGE RELATION statement cannot be deleted.  You



                                 143

RDMS Facility Messages





               cannot delete the UNIQUE or PRIMARY KEY
               relation-specific constraint because it is referenced
               by one or more FOREIGN KEY REFERENCES relation-specific
               constraints from one or more relation or relations.

User Action:   First, review the database design; then, if desired,
               delete the FOREIGN KEY REFERENCES relation-specific
               constraint (or constraints) and try the operation
               again.

ROLENOTIDENT,  some roles are NOT IDENTIFIED; security checking cannot
               be set to external

Explanation:   In order to alter a database and set security checking
               to external, no roles existing in the database can be
               defined as NOT IDENTIFIED.

User Action:   Redefine or drop the roles before altering the database
               security checking to external or do not alter the
               database security checking.

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



                                 144

                                                RDMS 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.

RTAIJMSMTCH,   AIJ references root file "<str>" - expected "<str>"



RTNEXI,        field "<str>" is used in routine "<str>"

Explanation:   The specified field you attempted to delete is used in
               a routine.

User Action:   You should first change the routine to exclude this
               field, and then delete the field.

RTNEXTS,       there is another routine named <str> in this database

Explanation:   The routine name you tried to define already exists.

User Action:   Specify another routine name.

RTNIDNEXTS,    routine ID, <num>, does not exist in this database

Explanation:   The specified routine ID does not exist in the current
               database.  Perhaps you specified a term or keyword
               where a routine ID was expected.

User Action:   Invoke the correct database.  Specify the correct
               routine ID.

RTNIMAGEERR,   error activating routine image "<str>"

Explanation:   The image has not been built correctly.

User Action:   Check the corresponding external routine source file
               and rebuild the image correctly.

RTNIMAGE_UNINSTALLED, routine image not installed

Explanation:   The external routine image specified by the primary
               error message can not be activated at the execution
               site because the main image is installed execute only
               or privileged and the external routine image is not
               installed.

User Action:   Install the specified external routine image.





                                 145

RDMS Facility Messages





RTNINCOM,      routine "<str>" is referenced in COMPUTED BY field
               <str> in relation <str>

Explanation:   An attempted was made to delete a routine but the
               routine is used in a COMPUTED BY field of a relation.

User Action:   First, review the database design; then, if desired,
               delete the COMPUTED BY field, and then delete the
               routine.

RTNINCON,      routine "<str>" is referenced in constraint "<str>"

Explanation:   Before you can delete a routine, all constraints,
               triggers, and views based on this relation must be
               deleted.

User Action:   Delete the dependent constraints, triggers, and views
               that refer to this routine.

RTNINTRG,      routine "<str>" is referenced in trigger "<str>"

Explanation:   Before you can delete a routine, all constraints,
               triggers, and views based on this routine must be
               deleted.

User Action:   Delete the dependent constraints, triggers, and views
               that refer to this routine.

RTNINVW,       routine "<str>" is referenced in view "<str>"

Explanation:   Before you can delete a routine, all view, constraints,
               and triggers based on this routine must be deleted.

User Action:   Delete the dependent views, constraints, and triggers
               that refer to this routine.

RTNNEXTS,      routine <str> does not exist in this database

Explanation:   The routine name you tried to use does not exist.

User Action:   Use another routine name.

RTNNOTCHG,     routine "<str>" has not been changed

Explanation:   The specified routine was not been altered or renamed.

User Action:   Correct the problem and try the metadata update again.

RTNNOTDEF,     routine <str> is not defined in database

Explanation:   The specified routine does not exist in the current



                                 146

                                                RDMS Facility Messages





               database.

User Action:   Invoke the correct database.  Make sure you spell the
               routine name correctly.  Perhaps you specified a term
               or keyword where the parser expected a routine name.

RTNNOTDEL,     routine "<str>" has not been deleted

Explanation:   The specified routine was not deleted.

User Action:   Correct the problem and try the metadata update again.

RTNNOTSAME,    routine "<str>" is not compatible with forward
               declaration

Explanation:   A DECLARE FUNCTION or DECLARE PROCEDURE was used to
               declare a forward reference for this routine, but this
               routine uses different parameter data types, passing
               mechanisms, number of parameters, default parameter
               value, or function return type.

User Action:   Correct the CREATE statement and try again.

RTNSBC_INITERR, Cannot init.  external routine server site executor;
               reason <num>

Explanation:   The attempt to create and initialize a server site
               client external routine executor has failed.  This is
               usually an indication of a lack of privileges or
               quotas, a lack of system resources, or the inability to
               establish the necessary client environment.  The reason
               value represents a more specific indication of the
               failure.

User Action:   For reasons 1 thru 9, check for sufficient quotas.  For
               reasons 10 thru 19, increase the value for environment
               variable RDMS$RTX_SHRMEM_PAGE_CNT as required.  For
               reasons 20 thru 29, make sure the proper images have
               been installed.  For all other reasons, contact your
               Oracle support representative for assistance.  You will
               need to provide a script allowing reproduction of the
               problem.

RTNSBC_TASKERR, Cannot use external routine server site executor;
               reason <num>

Explanation:   An attempt to perform an external routine task using
               the server site client executor failed.  This usually
               is an indication that either the executor process has
               terminated, or there is insufficient shared memory for
               either a routine callout or a RCI callback from a



                                 147

RDMS Facility Messages





               routine.  The reason value represents a more specific
               indication of the failure.

User Action:   For reasons 1 thru 9, check for sufficient quotas.  For
               reasons 10 thru 19, increase the value for environment
               variable RDMS$RTX_SHRMEM_PAGE_CNT as required.  For
               reasons 20 thru 29, make sure the proper images have
               been installed.  For all other reasons, contact your
               Oracle support representative for assistance.  You will
               need to provide a script allowing reproduction of the
               problem.

RTNUSENOTALL,  routine "<str>" can not be used, too many privileges
               available

Explanation:   The specified external routine can not be used because
               the the execution site environment has more available
               privileges than the user is authorized to use.

User Action:   Retry the operation or query in a less privileged
               environment such as defining the external routine as
               BIND ON SERVER.  If possible the shareable image should
               be installed with the OpenVMS INSTALL ADD/SHARE command
               to make it a known (and therefore) trusted shareable
               image.

RTN_DEACTERR,  routine "<str>" image "<str>" can not be deactivated

Explanation:   The specified external routine can not be deactivated.
               This is generally an indication of a system related
               problem.

User Action:   Review the secondary error message or messages, and
               take appropriate action.

RTN_ERROR,     routine "<str>" generated an error during execution

Explanation:   Execution of the specified external routine caused an
               exception to be generated.

User Action:   Review the secondary error message or messages, and
               rework the external routine code to avoid this error.

RTN_INVALID,   routine can not be invoked - it is marked invalid

Explanation:   This routine can not be invoked.  It has been marked
               invalid as a result of a data definition language
               operation on an object upon which this routine was
               dependent (with language semantics dependency).

User Action:   Revalidate the procedure by recompiling the procedure.



                                 148

                                                RDMS Facility Messages





               This may require that you drop and re-create the
               routine or module.

RTN_LANGSEMEXI, table used by routine with language dependency -
               routine invalid on COMMIT

Explanation:   There are one or more routines that depend upon this
               object with a language semantics dependency.  Those
               routines will be marked invalid and need to be
               recompiled through the language interface before reuse.
               i.e.  the module will need to be extracted and
               re-created before this routine can be used.

User Action:   Review your database design, and understand the
               implications of this data definition language
               operation.  Roll back the transaction if you do not
               want the routines to be marked invalid.

RTN_NOMETA,    metadata may not be created/altered from within an
               external routine

Explanation:   You attempted a metadata operation from within an
               external routine.

User Action:   Do not attempt such an operation.

RTN_NOTIFYERR, routine "<str>" generated an error during "<str>"
               notification

Explanation:   Execution of the specified external routine
               notification code for the specified notification action
               caused an exception to be generated.

User Action:   Review the secondary error message or messages, and
               rework the external routine code to avoid the error.

RTN_RTNEXI,    routine "<str>" is referenced in module "<str>" by
               routine "<str>"

Explanation:   You attempted to delete a routine, but the routine is
               used in another routine.

User Action:   First, review the database design; then, if desired,
               delete the routine that uses this one, and then delete
               this routine.

RUJDEVDIR,     RUJ filename "<str>" does not include a
               device/directory

Explanation:   The RUJ filename you specified did not include a device
               and directory.



                                 149

RDMS Facility Messages





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
               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.

SCHEMAEXISTS,  schema <str> already exists in this catalog <str>

Explanation:   The named schema already exists.

User Action:   Use a different name for the schema.

SCHEMAINUSE,   schema <str> currently in use

Explanation:   You attempted to drop a schema which still contains
               database object (such as, domains, tables, indices,
               etc).

User Action:   Drop all the objects from the schema before attempting
               to drop the schema.

SCHNOTFOUND,   schema with id <num> not found in this database

Explanation:   The schema id referenced by the ALTER statement does
               not exist.



                                 150

                                                RDMS Facility Messages





User Action:   Please select another schema.

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.

SCROLLDISABLED, SCROLL is disabled for chained style lists (segmented
               strings)

Explanation:   The logical name RDMS$DIAG_FLAGS is defined as "L"
               which disables the SCROLL emulation for chained style
               segmented strings.

User Action:   This logical name is used to determine if any columns
               are still using chained segmented strings.

SECNOTINT,     database security checking is not internal

Explanation:   The database is defined as SECURITY CHECKING IS
               EXTERNAL.  Therefore, users and roles cannot be
               created.

User Action:   Users and roles can only be defined in databases where
               security checking is internal.

SEGALRDYMP,    a map for segmented strings already exists

Explanation:   You tried to define a storage map for a relation that
               already has a storage map defined for it.

User Action:   Use the CHANGE STORAGE MAP statement if you want to
               change the storage map for segmented strings or lists.

SEGMAPONWORM,  only segmented strings may be stored in a WRITE_ONCE
               area

Explanation:   You tried to define a storage map that would allow
               something other than a segmented string to be stored in
               a WRITE_ONCE area.

User Action:   You must define the storage map on an area that is not
               WRITE_ONCE.

SEGSTR_AREA_INC, segmented string was stored incorrectly

Explanation:   The database has a storage map for segmented strings.
               The database has stored part of the segmented string in



                                 151

RDMS Facility Messages





               the incorrect area.

User Action:   Currently this is only expected to happen when the RDML
               or RDBPRE pre-compilers are in use and the logical name
               RDMS$BIND_SEGMENTED_STRING_BUFFER has not been
               specified to a large enough value to permit buffering
               of the entire segmented string.

SEGSTR_NO_CHG, you cannot change a field's datatype to or from a
               segmented string

Explanation:   Non-segmented string fields cannot be changed to or
               from segmented string fields.

User Action:   Define a new field with the desired data type and use a
               program to properly load/unload the segmented string.

SEGTOOBIG,     segmented string segment exceeds maximum allowed size

Explanation:   A segmented string segment has been specified that is
               larger than the maximum size allowed.  Segment size is
               maintained in a word, which allows 65,535 unsigned
               bytes of data.  The initial (first) segment stored
               requires 27 bytes of overhead, leaving 65,508 bytes for
               the user's data.  All subsequent segments require only
               13 bytes of overhead, leaving 65,522 bytes for the
               user's data.

User Action:   Specify a segment size that meets the above criteria
               for user data.

SEQEXTS,       there is another sequence named "<str>" in this
               database

Explanation:   The name used for the sequence already exits for
               another created sequence, or table(relation) in this
               database.  The name of any new sequence must be unique
               and not match an existing sequence or table name.  Use
               another sequence name.

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.

SEQNEXTS,      sequence "<str>" does not exist in this database

Explanation:   The sequence that you attempted to modify or delete was
               not found.





                                 152

                                                RDMS Facility Messages





User Action:   Check the name of the sequence using the SHOW command
               and try again to modify it or delete it.

SEQNOTCHG,     sequence "<str>" has not been changed

Explanation:   The specified sequence was not changed.

User Action:   Correct the problem and retry the metadata update.

SEQNOTDEF,     sequence "<str>" is not defined in database

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

User Action:   Invoke the correct database.  Spell the sequence name
               correctly.  Perhaps you specified a term or keyword
               where the parser expected a sequence name.

SEQNOTDEL,     sequence "<str>" has not been deleted

Explanation:   The specified sequence was not deleted.

User Action:   Correct the problem and try the metadata update again.

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
               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.

SIGNATURE_MISMATCH, invalid parameter signature on procedure call

Explanation:   (DSRI Users) The unique identifier generated for the
               procedures message BLR string does not match what is
               stored in the database.  (SQL users) The user interface
               to the database object being called by the application
               has changed, or the created routine is different from
               the previously declared forward reference.



                                 153

RDMS Facility Messages





User Action:   Ensure that the routine parameters are identical in
               number, order, type and passing mechanism to those
               currently defined in the database, or declared for the
               session.

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.

SNPDISCJ,      snapshots must be disabled or enabled deferred with
               commit to journal optimization

Explanation:   Within the ALTER DATABASE statement, the user tried to
               turn on commit to journal while snapshots were enabled.

User Action:   Disable snapshots before turning on commit to journal.

SORTKEYEXT,    sort key is external to RSE context

Explanation:   A sort key refers to record stream contexts that are
               totally external to the Record Selection Expression
               that contains the sort clause.  This type of sort key
               provides an invariant value to the sort, making the
               sort more costly for no useful purpose, and may
               indicate an improperly positioned sort clause.

User Action:   Define the sort key or keys again, or reposition the
               sort clause to a more external RSE.

SORTMEMFAIL,   memory allocation for Hypersort failed.  Use
               SORT_MEM_MAX

Explanation:   Hypersort bases its large VM request on WS_EXTENT.  If
               this results in a problem ...

User Action:   Define the logical SORT_MEM_MAX which will limit the
               memory request.



                                 154

                                                RDMS Facility Messages





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.

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.

SPIMAX,        SPAM interval of <num> is more than the Oracle Rdb
               maximum of <num>

Explanation:   The SPAM interval you specified is too large.

User Action:   Choose a smaller interval.

SPIMIN,        SPAM interval of <num> is less than the Oracle Rdb
               minimum of <num>

Explanation:   The SPAM interval you specified is too small.

User Action:   Choose a larger interval.

SQLSTATE_ILLCH, illegal character in SQLSTATE string passed to SIGNAL
               routine

Explanation:   The value expression which was passed to the SIGNAL
               routine contained illegal characters.  The only
               permitted characters are '0' through '9' and 'A'
               through 'Z'.  This is specified as part of the ANSI and
               International SQL standard.



                                 155

RDMS Facility Messages





User Action:   Correct the application so that only legal characters
               are passed to the SIGNAL routine.

SQLSTATE_NULL, unexpected NULL passed to SIGNAL routine

Explanation:   The value expression which was passed to the SIGNAL
               routine was NULL.  This is not permitted.

User Action:   Correct the application so that NULL is not passed to
               the SIGNAL routine.  For instance use COALESCE
               (:mysqlstate, '22023').  SQL92 defines 22023 as "data
               exception - invalid parameter value".

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.

SSAREANOTEMPTY, segmented string area <str> is not empty, it may not
               be deleted

Explanation:   You tried to change the storage map for segmented
               strings and delete an area, but there are segments in
               the area.

User Action:   You must determine what relations use the data that is
               in the area and then determine what you want to do
               about it before issuing the CHANGE STORAGE MAP
               statement again.

SSNOTINROOT,   <str> is not in the root file

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





                                 156

                                                RDMS Facility Messages





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.

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
               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.

STOMAPNOEXI,   storage map "<str>" does not exist in this database





                                 157

RDMS Facility Messages





Explanation:   The storage map you attempted to drop or alter was not
               found.

User Action:   Check the name of the storage map using the SHOW
               command and try again to alter or drop the storage map.

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.

SYMTOOBIG,     symbol <str> is longer than the maximum 31 characters

Explanation:   The maximum size for a symbol name is 31 characters.
               You attempted to use a symbol longer than 31
               characters.

User Action:   Use a shorter symbol.

SYNEXTS,       there is already a synonym named "<str>" in this
               database

Explanation:   The name used in the CREATE statement was already in
               use by a synonym.  The name of a table, domain, module,
               function, sequence, type, or procedure may not
               duplicate the name of a synonym.

User Action:   Please choose a different name for this object.

SYNNOTDEL,     synonym "<str>" has not been deleted

Explanation:   The synonym in question has not been deleted for the
               reason explained by the previous message.

User Action:   Correct the problem 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



                                 158

                                                RDMS Facility Messages





               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.

SYSTEMROLE,    "<str>" is a system role, operation is not allowed

Explanation:   A system role cannot be granted to or revoked from
               another role or user nor can any role be granted to or
               revoked from it.

User Action:   Only privileges can be granted to and revoked from
               system roles.

TABCTXEXI,     table context <num> already in use within this query

Explanation:   You have specified a table context number that is
               already in use within this query .

User Action:   Choose another table context number

TABIDNOTDEF,   relation ID, <num>, is not defined in database

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

User Action:   Invoke the correct database.  Specify the correct
               relation identification.  Perhaps you specified a term
               or keyword where the parser expected a relation
               identification.

TABLENOMAP,    table "<str>" is not partitioned with a storage map

Explanation:   You attempted to supply a PARTITION clause for a table
               which is not partitioned.

User Action:   Do not list the PARTITION clause in the SET and DECLARE
               TRANSACTION statements for this table.

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



                                 159

RDMS 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.

TEXT,          <str>

Explanation:   Additional information concerning an error.

User Action:   Review the primary error message or messages and take
               appropriate action

TEXT_EXPECTED, text or variable text data expected

Explanation:   The external routine expected text or variable text
               data.

User Action:   Pass text or variable text data to the external
               routine.

THRESHAREEXI,  illegal thresholds usage - area <str> exists, and
               cannot have THRESHOLDS respecified

Explanation:   You cannot redefine thresholds on an existing area.

User Action:   Delete and recreate the area with the desired
               thresholds or create an area with the new thresholds
               and move the data from the old to the new area.

THRESHUNIF,    illegal thresholds usage - area <str> is MIXED format,
               must be UNIFORM

Explanation:   Thresholds in storage maps can only be applied to
               UNIFORM areas.





                                 160

                                                RDMS Facility Messages





User Action:   Reference UNIFORM areas if you wish to use storage map
               thresholds.  Otherwise, define MIXED areas thresholds
               using CREATE STORAGE AREA or DEFINE STORAGE AREA
               statements when creating or altering the database.

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.

TRANSFDEF,     there is another transfer named <str> for this database

Explanation:   DDAL tried to store information in the source database
               for the transfer name given, and discovered that the
               transfer name was already stored.

User Action:   Delete this replication transfer, and pick a new
               transfer name.

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.

TRGEXI,        relation <str> is referenced in trigger <str>

Explanation:   Before you can delete a relation, all constraints,
               triggers, and views based on this relation must be
               deleted.

User Action:   Delete the dependent constraints, triggers, and views
               that refer to this relation.

TRGEXTS,       there is another trigger named <str> in this database

Explanation:   The trigger name you tried to define already exists.

User Action:   Choose another trigger name.

TRGINUPDREQ,   there are active update requests that reference trigger
               <str>

Explanation:   You tried to delete the specified trigger while there
               are one or more active update requests that reference



                                 161

RDMS Facility Messages





               the trigger.  The specified trigger was not deleted.

User Action:   Allow the update request or requests to finish, and try
               the trigger deletion again.

TRGNOEXI,      trigger <str> does not exist

Explanation:   The name specified for the trigger was not found in the
               database or the trigger named does not reference table
               named.

User Action:   Check the name of the trigger using the SHOW TRIGGERS
               statement and try the operation again.  Check to make
               sure the trigger is defined on the referenced table.

TRGNOSUBJCTX,  trigger may not reference the subject relation context

Explanation:   A BEFORE STORE or AFTER ERASE trigger or a trigger
               action that does not specify FOR EACH ROW contains an
               illegal reference to the subject relation current or
               NEW/OLD context (row values or dbkey).

User Action:   Define the trigger to use only the relation contexts
               declared within the trigger actions.

TRGVW,         views cannot be used within a trigger

Explanation:   You cannot define a trigger on a view and must not
               reference views in the triggered condition or actions.

User Action:   Define the trigger to use the relation referred to in
               the view definition.

TRG_INVALID,   trigger can not be invoked - it is marked invalid

Explanation:   This trigger can not be invoked.  It has been marked
               invalid as a result of a data definition language
               operation on an object upon which this trigger was
               dependent (with language semantics dependency).

User Action:   The trigger must be dropped and redefined so that it
               inherits the updated schema.

TRG_LANGSEMEXI, table used by trigger with language dependency -
               trigger invalid on COMMIT

Explanation:   There are one or more triggers that depend upon this
               object with a language semantics dependency.  Those
               triggers will be marked invalid and need to be
               recompiled through the language interface before reuse.





                                 162

                                                RDMS Facility Messages





User Action:   Review your database design, and understand the
               implications of this data definition language
               operation.  Roll back the transaction if you do not
               want the trigger to be marked invalid.

TRIGNODEL,     trigger <str> cannot delete record being modified or
               stored

Explanation:   The trigger specified (possibly invoked by another
               trigger) attempted to delete a record that was
               currently being stored or modified (by either a user
               request or a trigger action).

User Action:   First, review the database design and defined triggers.
               Then, define one or more of the triggers again to
               eliminate the possibility of deleting a record that is
               being modified or stored.

TRIG_ERROR,    trigger <str> forced an error

Explanation:   The specified trigger executed an action defined to
               produce this exception.

User Action:   This may be an expected occurrence in some situations,
               but in general determine the conditions that led to the
               update that caused the triggered error, eliminate those
               conditions (it may be necessary to discuss a solution
               with your database manager), and try the operation
               again.

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.

TRNNOTDEF,     transfer <str> has not been defined

Explanation:   The specified transfer was not defined.

User Action:   Correct the problem and try the metadata update again.

TRNNOTDEL,     transfer <str> has not been deleted

Explanation:   The specified transfer was not deleted.

User Action:   Correct the problem and try the metadata update again.

TRUE,          condition value is true



                                 163

RDMS Facility Messages





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.

TRUNRGTSTR,    truncation of right-hand side string for assignment has
               occurred

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 length of the right hand side must fit in the
               location where the value is being stored.  Specify a
               string which fits into the target location.

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.

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.

UNI_RELCONNOEXI, unique Relation constraint <str> does not exist in
               this database

Explanation:   The relation-specific constraint specified either was
               not found in the database or does not reference a
               UNIQUE or PRIMARY KEY constraint.  This
               relation-specific constraint is referenced by the
               definition of a FOREIGN KEY REFERENCES
               relation-specific constraint and must represent either
               a UNIQUE or PRIMARY KEY for the referenced relation and
               any referenced fields.

User Action:   Contact your Oracle support representative for
               assistance.





                                 164

                                                RDMS Facility Messages





UNKAMBFLAG,    '<str>' is an unknown or ambiguous flag name

Explanation:   The specified flag name was not recognized as a known
               debug or diagnostic flag.

User Action:   Change the unrecognized flag name to a known one and
               try the operation again.

UNKNOWN_VAR,   unknown variable <num> found in the query string

Explanation:   The variable number used by the query has not been
               declared.

User Action:   Correct the application to declare the variable first,
               or use the correct variable number in the expression.

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
               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



                                 165

RDMS Facility Messages





               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.

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.

UNLIKECOLL,    fields of unlike collating sequence may not be compared

Explanation:   Oracle Rdb does not permit comparisons among fields
               with unlike collating sequences.





                                 166

                                                RDMS Facility Messages





User Action:   Specify fields with the same collating sequence.

UNRES_AREA,    area <num> within relation "<str>" is not reserved



UNRES_AREAX,   area <num> within index "<str>" is not reserved

Explanation:   Your program began a transaction by reserving a list of
               relations and specifying particular access modes for
               certain partitions.  The referenced partition was not
               included in the list.

User Action:   Examine and correct the SET TRANSACTION statement.
               These errors may occur when applications or RMU/LOAD if
               some constraints are being evaluated which require
               access to partitions not reserved by the transaction.

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.

UNSCATALOG,    catalogs can not be created, altered or dropped

Explanation:   You must have multischema support enabled to create,
               alter, and drop catalogs.

User Action:   See action for primary message.

UNSCOMP,       unsupported data comparison

Explanation:   You attempted an operation that would compare two
               incommensurate data items.

User Action:   Correct the error and try again.

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.

UNSSCHEMA,     schemas can not be created, altered or dropped

Explanation:   You must have multischema support enabled to create,
               alter, and drop schemas.



                                 167

RDMS Facility Messages





User Action:   See action for primary message.

UNSSYNONYM,    this database does not have synonyms enabled

Explanation:   Synonyms can not be created, altered or dropped because
               this database does not support the SYNONYMS
               functionality.

User Action:   Use ALTER DATABASE and specify the clause SYNONYMS ARE
               ENABLED so that the appropriate system tables and
               support are enabled, then retry this command.

UNS_DTYPE,     unsupported datatype

Explanation:   Oracle Rdb does not support this data type.

User Action:   Refer to documentation for information on data types
               and host language data type conversion.

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.

UPDRECURSTRIG, update would cause recursive execution of trigger <str>

Explanation:   The trigger specified and possibly a series of other
               triggers have been defined such that execution of the
               update operation which invokes the specified trigger
               will cause that trigger to be recursively invoked.

User Action:   First, review the database design and defined triggers;
               then, redefine one or more of the triggers to eliminate
               the possibility of recursive invocation.

USENEXTVAL,    reference sequence using NEXTVAL before using CURRVAL

Explanation:   The sequence must first be referenced using
               pseudocolumn NEXTVAL before referencing the sequence
               using pseudocolumn CURRVAL.

User Action:   Reference the sequence using pseudocolumn NEXTVAL.

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



                                 168

                                                RDMS Facility Messages





               recovery.

USRMAX,        <num> number of users is greater than the Oracle Rdb
               maximum of <num>

Explanation:   The number of users for the database you specified is
               too large.

User Action:   Refer to documentation and try another value.

USRMIN,        <num> number of users is less than the Oracle Rdb
               minimum of <num>

Explanation:   The number of users for the database you specified is
               too small.

User Action:   Refer to documentation and supply another value.

VCO_NOFIRSTN,  CHECK OPTION is not allowed for view "<str>" with row
               limit

Explanation:   The CHECK OPTION on a view requires that neither that
               view nor any view nested in it has FIRST n (RDO) or
               LIMIT TO n ROWS (SQL) clause.  Remove either CHECK
               OPTION or LIMIT TO n ROWS clause from the view.

VCO_READ_ONLY, WITH CHECK OPTION can not be used with read-only view
               "<str>"

Explanation:   This view is read-only.  This occurs when a UNION,
               EXCEPT, MINUS, INTERSECT GROUP BY, DISTINCT, or
               statistical function appears in the outer most query.

User Action:   You can not apply a WITH CHECK OPTION clause to this
               view.  Remove the clause.

VIEWEXI,       relation <str> is referenced by view <str>

Explanation:   Before deleting a relation, all constraints and views
               based on this relation must be deleted.

User Action:   Delete the dependent views and any constraints that
               refer to the relation, then delete the relation.

VIEWINVIEW,    view <str> is referenced by view <str>

Explanation:   A view cannot be deleted if another view depends upon
               it.

User Action:   Delete the dependent view first.





                                 169

RDMS Facility Messages





VIEWMODEXI,    view "<str>" specified in default transaction for the
               module "<str>"

Explanation:   An attempt was made to perform the delete operation on
               a view.  The view is specified with the RESERVING
               clause in the default transaction characteristics for
               the module.

User Action:   First, review the database design; then, if desired,
               delete the module, and then delete the view.

VIEWNOEXI,     view <str> does not exist in this database

Explanation:   The view you attempted to delete was not found.

User Action:   Check the name of the view using the SHOW command and
               try again to delete it.

VIEWNORET,     view cannot be retrieved by database key

Explanation:   A view defined with a Record Selection Expression that
               references AGGREGATE or MERGE streams cannot be
               retrieved via database key.

User Action:   Retrieve the relations to which the view refers.

VIEWNOTDEL,    view <str> has not been deleted

Explanation:   The specified view was not deleted.

User Action:   Correct the problem and retry the metadata update.

VIEWNOTTRUNC,  view "<str>" has not been truncated

Explanation:   The specified view was not truncated.  Views cannot be
               truncated.

User Action:   A view may be dropped but a view cannot be truncated.
               If the view is dropped the metadata will be removed.
               Retry the TRUNCATE statement specifying a table name.

VIEWNOUP,      view cannot be updated

Explanation:   A view containing a CROSS, REDUCE TO, or FIRST clause
               cannot be updated.

User Action:   Update the relations to which the view refers.

VIEW_NO_ANA,   views cannot be analyzed

Explanation:   You attempted to analyze a view.



                                 170

                                                RDMS Facility Messages





User Action:   Use a relation name.

VIEW_RTNEXI,   view "<str>" is referenced in routine "<str>"

Explanation:   You attempted to delete a view, but the view is used in
               a routine.

User Action:   First, review the database design; then, if desired,
               delete the routine and then delete the view.

VRPINVALID,    invalid operation for storage map "<str>"

Explanation:   The storage map you attempted alter is a vertically
               partitioned map which currently may not be altered in
               this release of Rdb.

User Action:   To change the characteristic for a vertically
               partitioned map you will need to unload the data,
               delete the data (or drop the table) and redefine the
               physical characteristics.

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 implemented yet

Explanation:   The action you requested requires a feature that is not
               implemented in the current version of this product.

User Action:   Try a simpler way of doing things.

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.



                                 171

RDMS Facility Messages





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
               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.

WRNDATALOSS,   ALTER TABLE ...  ALTER COLUMN caused column data to be
               discarded

Explanation:   When ALTER TABLE ...  ALTER COLUMN converts a column to
               a COMPUTED BY column the old column data is no longer
               accessible.

User Action:   This is just a warning, if this action was not desired
               then use ROLLBACK to undo the effect of the ALTER TABLE
               statement.

WRNG_REL,      attempt to retrieve <str> with DBKEY from another
               relation

Explanation:   You attempted to retrieve a relation using a database
               key value, but the database key was from another
               relation.

User Action:   Supply the key value from the correct relation.

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_OFLO, expression forces too many levels of recursion



                                 172

                                                RDMS Facility Messages





Explanation:   You provided an expression which forces too many levels
               of recursion.  The expression should be rewritten to
               use parentheses and therefore cause fewer levels of
               recursion.

User Action:   Rewrite the expression.

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.









































































                                 173