SQL Error Message Documentation

This file documents messages returned with the SQL facility code.
This file contains the same text as the Errors help topic in
interactive SQL Help.

The Appendix on error messages in the SQL Reference Manual describes
how to use this file and files documenting related error messages with
other facility codes.
%RUNOFF-W-JEC, Unexpected text at end of command: ".sthl {level=1, bold, leavecase, numbered}"

	on output page 1; on input line 8 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-JEC, Unexpected text at end of command: ".sthl {level=2, bold, leavecase, numbered}"

	on output page 1; on input line 9 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-JEC, Unexpected text at end of command: ".sthl {level=3, bold, leavecase, numbered}"

	on output page 1; on input line 10 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-ILC, Illegal command: ".stch {bold, leavecase}"

	on output page 1; on input line 11 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-ILC, Illegal command: ".stap {bold, leavecase}"

	on output page 1; on input line 12 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-ILC, Illegal command: ".style table {bold, leavecase}"

	on output page 1; on input line 13 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-ILC, Illegal command: ".style figure {bold, leavecase}"

	on output page 1; on input line 14 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"

%RUNOFF-W-ILC, Illegal command: ".style example {bold, leavecase}"

	on output page 1; on input line 15 of page 1 of file "DISK$WEORG_PUBLIC:[DOCTOOLS]USERTEMPL.RNO;2"











ABMCOLNAME,    Column name matches simple function <str>; column value
               used

Explanation:   You have given a column the name of a SQL builtin
               function and SQL will use the column value instead of
               evaluating the function.  This ambiguous reference has
               been resolved in favor or the user define name.

User Action:   This is just a warning.  However, you may want to
               consider changing the column name, adding delimiters
               ("UID"), or qualifying with table, view or correlation
               name (E.UID).  If the function result is desired then
               you can use an alternate format for the function (e.g.
               adding the fractional precision CURRENT_TIME(2), using
               an equivalent function CURRENT_UID, instead of UIC, or
               writing a SQL function which has its own query scope)

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.

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



                                  1






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 command that refers to an existing
               access control entry, you specified identifiers that
               did not match any existing entry.

User Action:   Use SHOW PROTECTION to see what the access control list
               currently looks like, and correct your command.

ACE_ID_OVFL,   ACE identifier stack overflow during ACE parsing

Explanation:   You included too many identifiers in an expression.
               The identifier stack for the access control entry (ACE)
               overflowed during parsing.

User Action:   Simplify the access control entry that caused the
               error.

ACE_ID_UNFL,   ACE identifier stack underflow during ACE parsing

Explanation:   The access control entry (ACE) identifier stack
               underflowed during ACE parsing.  This happens when
               identifiers are not stored in the stack appropriately.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file.

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.





                                  2






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

ADADISUNS,     Host variable <str> is based on a type that uses
               discriminamts

Explanation:   The host variable you referred to is based on a type
               which uses Ada discriminants.  SQL does not support
               types which include discriminants

User Action:   Use a different type defintion.

ADAVARUNS,     Host variable <str> is based on a record type that uses
               variants

Explanation:   The host variable you referred to is based on a record
               type which uses Ada variants.  SQL does not support
               types which include variants.

User Action:   Use a different type defintion.

AGGIMPLIM,     Too many aggregates or derived columns in query

Explanation:   Your SQL query has more than 255 aggregate functions or
               has a derived table with more than 255 columns.  SQL
               uses an Oracle Rdb facility that is limited to this
               number of instances.

User Action:   Re-write the query to simplify the expression by using
               a view or views to reduce the complexity of this query
               expression.

AGGTBLCUR,     Table cursor, <str>, cannot have list cursors because
               it contains an aggregate or UNION

Explanation:   The table cursor referenced in the WHERE CURRENT OF
               clause of a list list cursor was defined using an
               aggregate or union expression.

User Action:   Change the table cursor to no specify an aggregate or
               union expression.

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



                                  3






               transactions are prepared transactions, which may be
               committed or aborted by the recovery operation using
               DECdtm information; in this case, a separate message
               indicating the number of prepared transactions will be
               displayed.

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

AIJALLDONE,    after-image journal roll-forward operations completed

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

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

AIJAUTOREC,    starting automatic after-image journal recovery

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

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.



                                  4






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

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

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

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

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

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



                                  5






               JOURNAL option

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

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

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

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

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

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

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

User Action:   For maximum protection, you should always include a
               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



                                  6






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

User Action:   No user action is required.

AIJBCKEND,     after-image journal backup operation completed
               successfully

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

User Action:   No user action is required.

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

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

User Action:   Roll forward the next AIJ file, which should contain
               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"



                                  7






               after-image journal using the "by-sequence" command
               qualifier.

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

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

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

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

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

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





                                  8






Explanation:   An invalid AIJ journal backup interval was specified.

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

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

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

User Action:   Wait until the AIJ backup completes.

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

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

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

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

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.





                                  9






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

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

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

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

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

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

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

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

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

User Action:   It is necessary to add a new journal before performing
               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



                                  10






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

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

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

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

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

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

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

User Action:   Contact your Oracle support representative for
               assistance.

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

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



                                  11






               journal when the journal is no longer in use.

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

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

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

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

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

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

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

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

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

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

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

User Action:   Disable AIJ journaling first, or try to unsuppress the
               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.





                                  12






AIJDUPSVRNAM,  duplicate "Hot Standby" server name

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

User Action:   Specify another server name.

AIJENABLED,    after-image journaling must be disabled

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

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

AIJENBOVR,     enabling AIJ journaling would overwrite an existing
               journal

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

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

AIJFILEGONE,   continuing with AIJ modification operation

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

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

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





                                  13






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

AIJGOODAREA,   storage area <str> is now consistent

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

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

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

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

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

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

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

User Action:   The AIJ journal must be removed.

AIJISOFF,      after-image journaling has been disabled

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

User Action:   No user action is required.

AIJISON,       after-image journaling has been enabled

Explanation:   After-image journaling has been enabled.  All
               subsequent database operations will be journaled to the
               "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



                                  14






               journal that is currently required for process
               recovery.  The journal is considered to be "busy" until
               no process requires the journal for recovery.

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

AIJLSSDONE,    "Hot Standby" has been shutdown

Explanation:   "Hot Standby" has been terminated.

User Action:   Restart the database replication operation.

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

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

User Action:   None.

AIJMODOBS,     cannot use deprecated modification syntax with new AIJ
               features

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

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

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

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

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

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



                                  15






               current

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

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

AIJMOREWORK,   active transactions will be aborted if you terminate
               recovery

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

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

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

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

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

AIJNOACTIVE,   there are no active transactions

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

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

AIJNOBACKUP,   AIJ contains no transactions that qualify for backup

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



                                  16






               enabled.

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

AIJNOENABLED,  after-image journaling has not yet been enabled

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

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

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

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

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

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

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

User Action:   None.

AIJNORCVR,     recovery must start with journal sequence <num>

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



                                  17






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

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

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

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

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

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

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

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

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

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

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

AIJOPTRST,     Optimized AIJ journal will not be applied during
               restart

Explanation:   An optimized AIJ was encountered during a restarted AIJ



                                  18






               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
               restore utility attempts to recover the "state"



                                  19






               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.





                                  20






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

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

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



                                  21






               available at the time of the backup operation.
               Restoring the after-image journal information permits
               subsequent "automatic" (i.e., hands-off) AIJ-recovery
               operations.

User Action:   No user action is required.

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

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



                                  22






               journals that were successfully restored, but contain
               data that needs to be backed up.

User Action:   No user action is required.

AIJRSTNMD,     journal has not yet been modified

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

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



                                  23






               disabled and then later enabled without any intervening
               database transaction activity, then confirming the AIJ
               file will permit the roll-forward operation to continue
               applying all transactions contained in the AIJ file.
               Otherwise, the AIJ file should be rejected and the
               correct AIJ file specified.  Should confirmation be
               given for an incorrect AIJ file, no transactions will
               be applied.

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

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

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



                                  24






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

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

ALIASATTOP,    The ON ALIAS clause must appear in the outermost
               compound

Explanation:   You have used the ON ALIAS clause in a compound
               statement that is nested within one or more other
               compound statements.

User Action:   Move the ON ALIAS clause to the outermost compound
               statement in the procedure.

ALIASEMBFIRST, Alias may only be specified in first level name

Explanation:   An alias was embedded in a quoted identifier after the
               first level.

User Action:   Change the name to embed the alias at the first level



                                  25






               of the name.

ALIASONLYONCE, Alias may be specified only once

Explanation:   An alias was embedded in a quoted identifier at more
               than one level in a multilevel name.

User Action:   Change the name to embed the alias at the first level
               of the name.

ALLSCHROLL,    All databases may be moved only by EXTRACTION ROLLUP
               transfers

Explanation:   You have specified *.* in the move tables clause of a
               transfer which was an extraction or replication
               transfer.

User Action:   Re-enter the CREATE TRANSFER statement with a differene
               MOVE clause.

ALLSCHTAB,     All tables must be moved if all databases are moved

Explanation:   The move clause must be *.* or xxx.*, not *.xxx.

User Action:   Re-enter the CREATE TRANSFER statement with a different
               MOVE clause.

ALSACTIVE,     Database replication is active

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

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

ALSNACTIVE,    Database replication is not active

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

User Action:   Verify that the database is being replicated.

ALSNAVAIL,     "Hot Standby" not available or improperly installed

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

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



                                  26






               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.

ALTNOTOCB,     ALTER TABLE may not be used to change a column to
               computed

Explanation:   The ALTER clause of the ALTER TABLE statement was used
               to change an existing column with a data type to a
               computed column.

User Action:   Use the DROP clause of the ALTER TABLE statement to
               drop the existing column and the ADD clause to add a
               computed column.

ALTSCHATT,     You cannot use the ALTER DATABASE statement on an
               attached database

Explanation:   You attempted to alter a database that was already



                                  27






               attached.

User Action:   Either remove the ALTER DATABASE statement or make sure
               the database being altered is not attached.

ALTSOM,        The ALTER statement must alter a valid option

Explanation:   Nothing was altered as a result of the ALTER statement
               which is not permitted.

User Action:   Reenter the ALTER statement and specify a valid option.

AMBHV_DEC,     Host variable <str> was ambiguously defined

Explanation:   You declared a host variable ambiguously by using the
               same name in two host variable declarations.

User Action:   Change the name or level of one of the definitions.

AMBTYP_DEC,    Host variable <str> was based on an ambiguously defined
               type

Explanation:   You declared a host variable which was based on a type.
               The type is ambiguous because two or more type
               declarations use the same name.

User Action:   Change the name or scope of one of the definitions.

AMB_KEYWORD,   Ambiguous keyword abbreviation

Explanation:   You used an ambiguous abbreviation.

User Action:   Specify the entire keyword.

ANODBHAND,     Another database already declared with alias <str>

Explanation:   You specified in the DECLARE ALIAS or ATTACH statement
               the same alias as in a previous DECLARE DECLARE ALIAS
               or ATTACH statement.

User Action:   Either issue a DISCONNECT statement and try the same
               ATTACH statement, or enter the DECLARE ALIAS statement
               again with a different alias .

ANSIPROTONL,   This statement may only refer to database with ANSI
               protection

Explanation:   You tried to execute a SHOW statement which is only for
               ANSI style protections on a database which uses ACL



                                  28






               style protections.

User Action:   Only use this statement with ansi style protections.

ANSI_UPDATE_VIEW, This view is non-updatable by ANSI standards

Explanation:   The way that the view was created violates the ANSI
               requirements for updatableness.  The view is marked
               non-updatable though at this time (version 4.1), the
               view can still be updated.  The violations of the ANSI
               standard are:  a column name used more than once in a
               select expression and a computed-by field

User Action:   None.  For future compatibility, user may want to note
               if a view is updatable or not

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





                                  29






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

User Action:   Recover the area to make it consistent.

AREA_RESTRUCT, storage area <str> is under restructure

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

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

ARGCOUNT,      Procedure <str> expected <num> parameter(s), was passed
               <num>

Explanation:   The module language procedure was not passed as many
               parameters as it expected.  This may be because the
               /CONTEXT qualifier was or was not specified when the
               module was compiled, or because the procedure call and
               procedure declaration do not have the same number of
               parameters.

User Action:   If a context parameter is being passed, make sure that
               the /CONTEXT qualifier is specified on module
               compilation.  Otherwise, make sure that the procedure
               call and declaration specify the same number of
               parameters.

ARGLISGTR255,  Statement requires an argument list whose length
               exceeds maximum specified by the calling standard

Explanation:   The OpenVMS Calling Standard allows only 255 arguments
               to a procedure.  A procedure call generated by the SQL
               Precompiler or SQL Module Language compiler has
               exceeded this limit.  This may be due to an OPEN ...
               USING, FETCH ...  INTO or EXECUTE ...  USING/INTO
               variable list.  Note that the SQLSTATE, SQLCA, or
               SQLCODE must also be passed to generated routines, this
               allows up to 254 user parameters.

User Action:   Reduce the parameters passed to these statements,
               possibly using SQLDA structures instead which can be
               arbitrarily long.

ARIEXPEXP,     Expected arithmetic value expression

Explanation:   You supplied a predicate where SQL expected to find an
               arithmetic value expression.



                                  30






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

ASSSTRLIT,     Numeric literal is assumed to be text

Explanation:   You tried to store a numeric literal into a text column
               or compare a numeric literal to a text column.  SQL
               assumes the string is a text literal and converts it
               for the storage or comparison.  Note that each digit in
               the numeric literal, including leading zeroes, is
               converted to text.  For instance, 001 and 1 represent
               the same number, but are converted to different
               literals ("001" and "1").

User Action:   None.  However, it is good programming practice to
               convert the numeric literal to a string literal by
               enclosing it in quotes.

ATTMISSING,    invalid or missing attributes

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

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

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.



                                  31






               Even though the AIJ backup failed, the AIJ backup file
               must be used for successful roll-forward operations.

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

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

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

BADAIJSEQ,     AIJ file is incorrect for roll-forward operations

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

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

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

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

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

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

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

User Action:   Your after-image journal file cannot be used with the
               version of the software you have installed on your
               machine.  Make sure you are using the correct AIJ



                                  32






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

BADARGAVG,     Argument of AVG, STDDEV and VARIANCE must be numeric or
               interval

Explanation:   The expression for an AVG, STDDEV and VARIANCE function
               must be numeric or interval.

User Action:   Change the value expression to contain only numeric or
               interval fields, or remove the function.

BADARGSUM,     Argument of SUM must be numeric or interval

Explanation:   The expression for an SUM function must be numeric or
               interval.

User Action:   Change the value expression to contain only numeric or
               interval fields, or remove the function.

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

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

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

BADBLOB,       unable to import a list

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

User Action:   If the nature of the problem is not obvious, contact
               your Oracle support representataive.  Retain a copy of
               the Oracle Rdb interchange file that caused the error.

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

Explanation:   The logical bind parameter value is invalid.

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

BADBNDPRM0,    bad bind parameter

Explanation:   A logical bind parameter value is invalid.

User Action:   See the secondary error message for more information.
               Because of unfortunate logistics, no further



                                  33






               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.

BADBUFFERPOOL, BUFFERPOOL clause is not allowed in the CREATE TRANSFER
               statement.

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               BUFFERPOOL clause.

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.

BADCATALOG,    Catalog <str> not used by this query

Explanation:   You used a catalog name to qualify a reference to a
               column and that catalog was not specified in the FROM
               clause of the query.

User Action:   Either remove the catalog name from the select-list or
               specify the same catalog as specified in the FROM
               clause of the query.

BADCATINCRE,   Reference to catalog <str> not permitted within
               definition of catalog <str>

Explanation:   You specified the name of a catalog other than the one
               being defined.

User Action:   Remove the catalog name or use the name of the catalog
               being defined.

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

Explanation:   The specified record cache is not defined in the



                                  34






               database.

User Action:   Please specify a valid record cache name.

BADCLUMP,      invalid clump type encountered

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

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

BADCOLIGNCAS,  The LIKE pattern is incompatible with IGNORE CASE

Explanation:   The use of column names as the pattern string cannot be
               supported if IGNORE CASE is also choosen.

User Action:   Use UPPER or LOWER functions to translate the source
               string into a consistent case before rather than having
               LIKE ignore case.

BADCOLLATION,  COLLATION SEQUENCE clause is not allowed in the CREATE
               TRANSFER statement.

Explanation:   You have specified the COLLATION SEQUENCE clause as an
               attribute for the target database in a CREATE TRANSFER
               statement.

User Action:   Re-enter the CREATE TRANSFER statement without the
               COLLATION SEQUENCE clause.

BADCOLQUAL,    The common column name <str> cannot be qualified with a
               table name

Explanation:   The name given in the error message is a common column
               name which can not be qualified.  The error occurs if
               there are columns with the same name are not specified
               as join columns in a joined table.

User Action:   Use column renaming to make the column names unique or
               specify the column as a named join column using the
               USING clause.

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

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





                                  35






User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

BADCTXLEN,     Illegal length value found in context structure

Explanation:   The LENGTH field of the context structure passed to the
               SQL procedure was illegal.  SQL supports only the
               global tid, which has a length of 16 (symbolically
               DDTM$S_TID).

User Action:   Change the HLL code to pass a context structure whose
               only length is 16 (DDTM$S_TID).

BADCTXTYPE,    Illegal type value found in context structure

Explanation:   The TYPE field of the context structure passed to the
               SQL procedure was illegal.  SQL supports only the
               SQLCONTEXT$K_GLOBAL_TID type.

User Action:   Change the HLL code to pass a context structure whose
               only type is SQLCONTEXT$K_GLOBAL_TID.

BADCTXVER,     Unsupported version of context structure

Explanation:   The VERSION field of the context structure passed to
               the SQL procedure was unsupported.  SQL supports only
               the SQLCONTEXT$K_VERSION1 version.

User Action:   Change the HLL code to pass a context structure whose
               only version is SQLCONTEXT$K_VERSION1.

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.

BADDBHAND,     Alias <str> not used by this query

Explanation:   You used an authorization identifier to qualify a
               reference to a column and that authorization identifier
               was not specified in the FROM clause of the query.

User Action:   Either remove the authorization identifier that



                                  36






               qualifies the select-list item or specify the same
               authorization identifier as specified in the FROM
               clause of the query.

BADDBKEY,      DBKEY SCOPE clause is not allowed in the CREATE
               TRANSFER statement.

Explanation:   You have specified the DBKEY SCOPE clause as an
               attribute for the target database in a CREATE TRANSFER
               statement.

User Action:   Re-enter the CREATE TRANSFER statement without the
               DBKEY SCOPE clause.

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.

BADDICTIONARY, DICTIONARY clause is not allowed in the CREATE TRANSFER
               statement.

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               DICTIONARY clause.

BADDTFMT,      Date or time format is not set up properly.

Explanation:   You entered a SHOW DATE FORMAT statement, but
               LIB$DT_FORMAT is not properly defined.

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

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

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

User Action:   Re-enter the CREATE TRANSFER statement, specifying only



                                  37






               one EPILOGUE IS or NOEPILOGUE clause.

BADEPINAM,     invalid epilogue file name

Explanation:   You entered an invalid epilogue file name.

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

BADEXTENDIBLE, EXTENDIBLE clause is not allowed in the CREATE TRANSFER
               statement.

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               EXTENDIBLE clause.

BADFILEVER,    incompatible .RBR file type

Explanation:   This version of SQL cannot import a database from this
               Oracle Rdb interchange file.

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

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

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

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

BADFLDTYP,     source fields of target relation <str> field number
               <num> have different types

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

User Action:   Re-enter the CREATE TRANSFER statement by specifying
               fields of the same data type in all the MOVE RELATION
               clauses with the same target relation.

BADIDXMAP,     Columns specified for partitioning do not agree with



                                  38






               columns for index

Explanation:   You either named fields to partition a btree index in
               an incorrect order or you named fields to partition a
               btree index that are not part of the index.

User Action:   Review the statement and specify it again.

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

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

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

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

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               INTERVAL clause.

BADLANGUAGE,   Language <str> not properly set up.

Explanation:   SQL attempted to retrieve month or weekdays from the
               logical name table LNM$LANGUAGE_xxx for language xxx,
               but could not retrieve a value.

User Action:   Contact the sytem manager to make sure everything has
               been properly set up.

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

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

User Action:   Re-enter the CREATE TRANSFER statement, specifying only
               one LOG FILE IS or NOLOG clause.

BADLOGNAM,     invalid log file name



                                  39






Explanation:   You entered an invalid log file name.

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

BADMAINT,      Database is an unsupported maintenance release for the
               current version

Explanation:   The maintainance release number and the version number
               of the database that you just attached to forms an
               unknown combination.

User Action:   Check to make sure that you are running with the
               correct versions of Oracle Rdb-supported database
               products for the SQL interface to Oracle Rdb.  Correct
               versions are listed in the Oracle Rdb Installation
               Guide.

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

Explanation:   The name given in a data manipulation or definition
               statement ended with a dollar sign ($) or underscore
               (_).  These symbols are not allowed.

User Action:   Specify a valid name.

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

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

User Action:   Re-enter the CREATE TRANSFER statement, adding the
               required field to the appropriate MOVE RELATION clause.

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

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

User Action:   Re-enter the CREATE TRANSFER statement adding the
               required MOVE RELATION clause.





                                  40






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

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

User Action:   Re-enter the CREATE TRANSFER statement adding the
               required views to the MOVE VIEW clause.

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

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

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

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

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

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

BADNONEXTEND,  NONEXTENDIBLE clause is not allowed in the CREATE
               TRANSFER statement.

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               NONEXTENDIBLE clause.

BADONUSE,      A qualified joined table specifing NATURAL cannot have
               an an ON or USING clause

Explanation:   The ON or USING clause was not specified for a
               qualified join.  One of these clauses is required.

User Action:   Specify the ON or USING clause or specify a NATURAL,
               but not both.



                                  41






BADORIENT,     fetch orientation allowed only for scroll cursors

Explanation:   You specified a fetch orientation for a fetch
               statement, but the cursor for the fetch statement was
               not a scroll cursor.

User Action:   Either ignore the clause or use a scroll cursor.

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

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

User Action:   Re-enter the CREATE TRANSFER statement without the PAGE
               FORMAT clause.

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





                                  42






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

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

BADPREPARE,    Cannot use DESCRIBE or EXECUTE on a statement that is
               not prepared

Explanation:   Either you attempted to use a DESCRIBE or EXECUTE
               statement which named a statement that was not
               successfully prepared, or you passed a non-zero
               statement-id to PREPARE which is not a valid statement.

User Action:   Prepare the statement before calling DESCRIBE or
               EXECUTE, or set the statement-id to zero before calling
               PREPARE.

BADPROCEND,    SQL statement was terminated with an improper statement
               terminator

Explanation:   The SQL statement supplied an invalid terminator for
               the host language.  User Action Use the correct
               statement terminator for the host language.  Host
               Languages have different rules about how to terminate
               an SQL statement.  ADA uses semicolon, COBOL uses
               END-EXEC and FORTRAN uses the end of the line.

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

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

User Action:   Re-enter the CREATE TRANSFER statement, specifying only
               one PROLOGUE IS or NOPROLOGUE clause.

BADPRONAM,     invalid prologue file name

Explanation:   You entered an invalid prologue file name.

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

BADPROTECTION, PROTECTION clause is not allowed in the CREATE TRANSFER
               statement.

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



                                  43






User Action:   Re-enter the CREATE TRANSFER statement without the
               PROTECTION clause.

BADQUALJOI,    A qualified joined table requires NATURAL or an ON or
               USING clause

Explanation:   The ON or USING clause was not specified for a
               qualified join.  One of these clauses is required.

User Action:   Specify the ON or USING clause.

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

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

User Action:   Re-enter the CREATE TRANSFER statement by specifying
               the same set of fields in all the MOVE RELATION clauses
               with the same target relation.

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

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

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

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

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

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

BADSCHEMA,     Schema <str> not used by this query



                                  44






Explanation:   You used a schema name to qualify a reference to a
               column and that schema was not specified in the FROM
               clause of the query.

User Action:   Either remove the schema name from the select-list or
               specify the same schema as specified in the FROM clause
               of the query.

BADSCHINCRE,   Reference to schema <str> not permitted within
               definition of schema <str>

Explanation:   You specified the name of a schema other than the one
               being defined.

User Action:   Remove the schema name or use the name of the schema
               being defined.

BADSEGSTRING,  SEGMENTED STRING clause is not allowed in the CREATE
               TRANSFER statement.

Explanation:   You have specified the SEGMENTED STRING clause as an
               attribute for the target database in a CREATE TRANSFER
               statement.

User Action:   Re-enter the CREATE TRANSFER statement without the
               SEGMENTED STRING clause.

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

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               SNAPSHOT_FILENAME clause.

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



                                  45






               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.

BADSTOGROUP,   STOGROUP clause is not allowed in the CREATE TRANSFER
               statement.

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               STOGROUP clause.

BADSUPLVL,     Attached database has unknown support level

Explanation:   The database you just attached to has an unknown
               support level.

User Action:   Check to make sure that you are using Oracle
               Rdb-supported database products for the SQL interface
               to Oracle Rdb.

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

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

User Action:   Re-enter the CREATE TRANSFER statement without the
               THRESHOLDS clause.

BADVERNUM,     Attached database has unsupported version number

Explanation:   The database you just attached to has a version number
               that is not supported by this version of SQL.

User Action:   Check to make sure that you are running with the
               correct versions of Oracle Rdb-supported database
               products for the SQL interface to Oracle Rdb.  Correct
               versions are listed in the Oracle Rdb Installation
               Guide.

BAD_ARRAY,     Host variable <str> contains an array syntax error in
               its declaration.

Explanation:   The named variable is defined as a C array, but is



                                  46






               either missing the closing "]" or contains a
               non-numeric dimension.

User Action:   Correct the syntax of the declaration and recompile the
               program.

BAD_CDD_DEF,   CDD$DEFAULT is not valid, repository default is now
               CDD$TOP.

Explanation:   Your logical name CDD$DEFAULT is not acceptable to the
               repository.  The repository will be used, but your
               default is set to CDD$TOP.

User Action:   Define a valid CDD$DEFAULT.

BAD_DB,        Repository description of current database is corrupt

Explanation:   The repository description of the schema is missing the
               RDB$INSTANCE node.

User Action:   Verify that the database itself has not been corrupted.
               If it has, recreate the database.

BAD_LENGTH,    Negative length specified for column <str>

Explanation:   You specified a length for a character or varchar
               column that was less than zero.

User Action:   Change the length to a positive number.

BAD_LENGTH1,   Negative length specified for parameter <num>

Explanation:   You specified a length of less than zero for the
               parameter.

BAD_LEVEL,     CONSISTENCY LEVEL <num> is illegal

Explanation:   Only values 2 and 3 are allowed for consistency level.

User Action:   Enter 2 for concurrency; enter 3 for consistency

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

Explanation:   The name given in a data manipulation or data
               definition statement was longer than the permitted
               limit.

User Action:   For data definition statements, specify a shorter name.



                                  47






               For data manipulation statements, consult your database
               design specifications to find the correct name.

BAD_PRECISION, Invalid precision specified for column <str>

Explanation:   The precision specified for a DECIMAL or NUMERIC column
               is less than or equal to zero.  Or, the precision
               specified for a FLOAT column was less than zero or
               greater than 15.  Or the precision contained a decimal
               point.

User Action:   Change the precision to a valid value.

BAD_SCALE,     Negative scale specified for column "<str>"

Explanation:   The scale specified for this column is less than zero.
               This data type only allows zero or positive scale
               values.

User Action:   Change the scale to a positive number or zero.

BAD_TOKEN,     <str> is not a valid SQL language element

Explanation:   The indicator string is neither a predefined language
               element (i.e.  a keyword, delimiter or operator) not a
               valid SQL name.

User Action:   Use a valid SQL language element.

BAD_TXN_STATE, Invalid transaction state.  Transaction already
               started.

Explanation:   A SET TRANSACTION statement was executed, but it was
               not the first statement executed in the transaction.

User Action:   Make the SET TRANSACTION statement the first statement
               to be executed.

BAD_VERSION,   This database system does not support this statement

Explanation:   This statement uses a DSRI feature which is not
               supported by all versions of all DSRI database systems.
               You tried to execute this statement using a version of
               a database system which does not support this feature.

User Action:   Use a simpler statement, or a different base system
               version.

BASROWDEL,     Row containing list has been deleted



                                  48






Explanation:   An attempt was made to fetch or insert into a list
               cursor where the row containing the list has been
               deleted.

User Action:   Do not delete the row containing the list or simply
               close the list cursor.

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.

BINSCAFAC,     Host variable <str> has a binary scale factor

Explanation:   The host variable is a PL/I fixed binary data type with
               a nonzero binary scale factor.  SQL supports only
               decimal scale factors.

User Action:   Either change the scale factor to zero, or change the
               data type to fixed decimal.

BIT_FIELD,     Host variable <str> is a bit field which is illegal in
               SQL statements.

Explanation:   The named variable is defined as a C bit field.  Such
               fields are not legal in SQL statements.

User Action:   Use a different variable.

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.

BOG_DYN_NAME,  Invalid name for dynamic statement or cursor

Explanation:   The user passed either a zero length string, no string
               or a variable not of data type text for a dynamic
               statement name or dynamic cursor name.

User Action:   Pass a string that has a non-zero length.

BOOEXPEXP,     Expected a predicate



                                  49






Explanation:   Either a numeric or string value expression was found
               where SQL expected a predicate.

User Action:   You must use a predicate in this context.

BOUND,         multiple binds are not allowed

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

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

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

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

User Action:   Contact your Oracle support representative for
               assistance.

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

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

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

BUGCHECK,      fatal, unexpected error detected

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

User Action:   Contact your Oracle support representative for
               assistance.

BUGCHK,        There has been a fatal error.  Please contact your
               Oracle support representative.  <str>

Explanation:   A fatal error has occurred.

User Action:   Contact your Oracle support representataive with
               information about the circumstances under which the bug
               occurred.





                                  50






BUGCHKDMP,     generating bugcheck dump file <str>

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

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

CABORT,        User entered Control-C to abort statement

Explanation:   You typed a Control-C to abort the current statement.

User Action:   None.

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

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

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

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

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

CANTADDLAREA,  Cannot create logical area <str>

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

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

CANTASSMBX,    error assigning a channel to a mailbox

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

User Action:   Examine the secondary message for more information.

CANTBINDRT,    error mapping database root file



                                  51






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.

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.





                                  52






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

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.





                                  53






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.

CANTDOVALXPR,  Value expressions may not be moved by CREATE TRANSFER

Explanation:   The user entered a value expression in the select list
               of a select expression in the move tables clause of the
               CREATE TRANSFER statement.  This is not allowed.

User Action:   Move only columns using CREATE TRANSFER.  Use a
               prologue file to define a view on the target database
               which computes the value expression from the columns
               moved.

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.



                                  54






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.

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.



                                  55






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



                                  56






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

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.





                                  57






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.

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.





                                  58






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

CANT_MOVE,     <str> already exists in <str>





                                  59






Explanation:   The object or schema named by the first parameter could
               not be moved to the schema or catalog named by the
               second parameter, because there is already an object or
               schema by that name.

User Action:   Move the object or schema to a different schema or
               catalog, or don't move it at all.

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.

CASENODTP,     CASE expression must have a data type

Explanation:   The CASE expression does not have a data type because
               all of the results are NULL or of an unknown type.

User Action:   Assign a data type to at least one result.

CASENOTFND,    CASE statement has no WHEN clause for selector

Explanation:   There was no WHEN or ELSE clause to handle the selector
               that was specified.

User Action:   Add WHEN clauses to handle expected selector values and
               an ELSE clause to handle unexpected selector values.

CASEWITHDUP,   Duplicate literal in WHEN clause of CASE statement

Explanation:   The same literal or NULL value was used more than once
               in the WHEN clause(s) of the same CASE statement.

User Action:   Remove the WHEN clause(s) containing the duplicate
               values.

CASTNOSTRUC,   CAST cannot operate on a structure

Explanation:   You attempted to perform a CAST on a non-scalar
               variable, stucture, or array.

User Action:   Do not attempt this.

CATNOTDEF,     Catalog <str> is not defined





                                  60






Explanation:   The specified catalog does not exist in the specified
               database.

User Action:   Check the spelling of the catalog name and ensure that
               it is the name of a catalog in the specified database.

CAT_EXISTS,    Catalog <str> already exists

Explanation:   You attempted to create a catalog in the specified
               database with the name of an existing catalog in that
               database.

User Action:   Choose a different name for the new catalog.

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

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

User Action:   Include a device and directory specification.

CDDERR,        Error occurred during attempt to use repository.
               Repository will not be used

Explanation:   An error occurred when SQL attempted to access the
               repository.

User Action:   Refer to following repository messages for more
               information.

CDDUNKPROT,    Unknown repository protocol <str>

Explanation:   The protocol in the repository was not correct.

User Action:   Try to recreate the repository.  If the repository is
               still corrupt, contact your Oracle support
               representative.  Try invoking it with the file name.

CDDVERERR,     Found repository core_level <num> was expecting <num>

Explanation:   The core_level in the repository was not correct.

User Action:   Try to recreate the repository.  If the repository is
               still corrupt, contact your Oracle support
               representative.  Try invoking it with the file name.

CDDVERSTR,     Error reading CDD version string - Defaulting to newest
               CDD Version



                                  61






Explanation:   There was a problem calling cdd$version to get the
               version.  The newest CDD version is the default and the
               bits for the newest CDD version are set.

User Action:  

CHAR_SET_USED, Domain was a non-MCS CHARACTER data type

Explanation:   This message is used as a subcode to SQL$_DOMNOTBCK.
               It indicates that the offending domain was a new
               subtype of CHARACTER or VARYING CHARACTER.

User Action:   If the columns defined using this domain contain only
               MCS data, change the domain to reflect that fact.
               Otherwise, the database cannot be exported WITH NO
               EXTENSIONS until this domain is removed completely.

CHECKOPTRO,    You specified WITH CHECK OPTION for read only view
               <str>

Explanation:   You specified the WITH CHECK OPTION for a view which is
               based on a read only select expression.  You should
               specify the WITH CHECK OPTION only for a read write
               view.

User Action:   Remove the WITH CHECK OPTION clause from this view
               definition, or make the select expression specify an
               updatable select expression.

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

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

User Action:   None.

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

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

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



                                  62






               NO) terminates the operation.

CHGINDMAPSTP,  Terminating operation at user's request

Explanation:   See above.

User Action:   None.

CHRUNIBAD,     Number of octets is not an integral number of
               characters

Explanation:   When defining a column or domain, you specified a size
               that is interpreted as a number of octets.  The number
               of octets is not an integral number of characters.

User Action:   Change the units to characters or specify the correct
               number of octets.

CHR_TOO_SHO,   Character length of <str> <str> is too short

Explanation:   The character string length is too short to contain all
               possible converted data already stored in the column.

User Action:   None.  This is a warning message only.

CHR_TOO_SMA,   The string length of <str> <str> is too small

Explanation:   The length of the character string is too small to
               handle all possible numeric data that might already be
               stored in the table.

User Action:   None.  This is a warning message only.

CIRCTYPE,      Host variable <str> is based on a type which was used
               in its own definition

Explanation:   You referred to a host variable which is based on a
               type.  The type was not validly defined because it was
               based on itself.

User Action:   Fix the type definition.

CIRCULARDEF,   Structure field <str> is a circular definition

Explanation:   The definition of a structure is circular because one
               of the elements has a reference to the structure
               itself.

User Action:   Recode the structure declaration without referencing



                                  63






               the structure itself.

CLAUSENAL,     <str> is not permitted in <str>

Explanation:   The specified clause is not supported in this context.

User Action:   Remove the clause from the statement reported in the
               error message

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

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

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

CLMNOENABLED,  Continuous LogMiner has not yet been enabled

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

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

CLOSERR,       error detected when closing .RBR file

Explanation:   See the message that follows for details.

User Action:   In the absence of other error messages, the database
               has probably been imported successfully.  If the error
               occurred during an EXPORT operation, the file is not
               likely to be usable in a later IMPORT.

CMDINTR,       this statement is not allowed in a transaction

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

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

CMDLN_TOO_LONG, The command line is too long.  Please shorten the
               command

Explanation:   The command line specified for UNIX sqlpre or sqlmod is
               too long.



                                  64






User Action:   Use a shorter command line by moving files or changing
               their path so that directory specifications for files
               can be simplified or eliminated.

CMPBYINVW,     view <str> cannot be transferred because of invalid
               computed field <str> in relation <str>

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

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

CMPBYMVMETOO,  Column <str> in table <str> may not be moved without
               column <str>

Explanation:   You included a column to be transferred that relies
               upon another column in the table.  This column must
               also be moved.

User Action:   Re-enter the transfer definition including all
               necessary columns.

CMPBYWNRL,     Invalid computed field <str> will not be transferred
               from relation <str>

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

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

CMPBYWNVW,     view <str> will not transfer invalid computed field
               <str> from relation <str>

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





                                  65






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

CNTSPNSUB,     Cannot spawn subprocess

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

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

CNVNUMDAT,     cannot convert number to a date string

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

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

COAL1ARG,      The <str> function requires more arguments than you
               have provided

Explanation:   The function named in the message requires more values
               that were supplied.  For instance, COALESCE, NVL, LEAST
               and GREATEST require two or more arguments.

User Action:   Please check the documentation and adjust the function
               call.

COLEXISTS,     Column <str> is named more than once in table <str>

Explanation:   You attempted to create a table or view with using a
               column name more than once.

User Action:   Choose a different name for each column.

COLLSTINV,     A column list is not allowed in an INSERT LIST CURSOR
               statement

Explanation:   A column list was supplied for an INSERT LIST CURSOR
               statement.

User Action:   Remove the column list.

COLL_EXISTS,   Collating sequence <str> already exists

Explanation:   You attempted to create a collating sequence in the



                                  66






               specified schema with the name of an existing collating
               sequence in that schema.

User Action:   Choose a different name for the new collating sequence.

COLNOTFUN,     Column <str> named outside a aggregate function in a
               SELECT with HAVING but no GROUP BY

Explanation:   In select expressions with a HAVING clause but without
               a GROUP BY clause, you cannot directly name columns in
               the select list or HAVING clause.  You can refer to
               them only as aggregate function arguments, or in a
               WHERE clause.

User Action:   Either make the column named in the message an
               aggregate function argument, or if it is in a HAVING
               clause, change the HAVING clause to a WHERE clause.

COLNOTNUL,     Column <str>.<str> cannot be UNIQUE because it can
               contain nulls.

Explanation:   You specified a column using the UNIQUE constraint.
               The column may contain nulls.  This is not legal
               because two rows cannot contain the NULL values in this
               column.

User Action:   Define the named field as NOT NULL.

COLNOTSS,      Column <str> is not a list field

Explanation:   The column specified in a SEGSTR.CREATE or SEGSTR.OPEN
               statement must be a list field.  This column is not.

User Action:   Specify a column whose data type is list

COLNOTUPD,     Column <str> is not included in the FOR UPDATE clause
               of cursor <str>

Explanation:   The SQL interface to Oracle Rdb provides the FOR UPDATE
               clause on a cursor definition for DB2 compatablity.
               The clause is entirely optional.  If a FOR UPDATE
               clause is specified on the cursor and an UPDATE
               statement that uses the CURRENT OF clause with that
               cursor changes a column which is not one of the columns
               included in the FOR UPDATE clause of the DECLARE CURSOR
               statement, you will get this warning message.

User Action:   No action is required.  This message will not effect
               the execution of the statement.



                                  67






COLNOTVAL,     The column CHECK constraint cannot refer to the column
               <str>

Explanation:   The CHECK constraint cannot refer to the column because
               the constraint is defined only for a column, not the
               entire table.

User Action:   Refer to the only that column for which this CHECK
               constraint is being defined or define the CHECK
               constraint for the entire table.

COLONDISILL,   Parameter name colons are disabled and therefore
               illegal

Explanation:   When the /ANSI_PARAMETERS qualifier is used, the module
               processor requires that all parameter declarations and
               references be prefixed by colons.  When the
               /NOANSI_PARAMETERS qualifier is used (it is the
               default), the colon prefix is not allowed.

User Action:   Remove colons from your parameter declarations and
               references.

COLONENAREQ,   Parameter name colons are enabled and therefore
               required

Explanation:   When the /ANSI_PARAMETERS qualifier is used, the module
               processor requires that all parameter declarations and
               references be prefixed by colons.  When the
               /NOANSI_PARAMETERS qualifier is used (it is the
               default), the colon prefix is not allowed.

User Action:   Add colons to your parameter declarations and
               references.

COLSEQNOTDEF,  Collating sequence <str> is not defined

Explanation:   The specified collating sequence does not exist in the
               specified schema.

User Action:   Check the spelling of the collating sequence name and
               ensure that it is the name of a collating sequence in
               the specified schema.

COMPBYONLY,    Column "<str>" has no value expression - invalid for
               outline

Explanation:   The CREATE OUTLINE ...  ON COLUMN clause only operates
               on COMPUTED BY, AUTOMATIC columns of tables, computed



                                  68






               columns of a view definition, or column DEFAULT values
               expressions.

User Action:   Examine the table or view definition and apply the
               command to computed column, or one with a DEFAULT
               value.

COMPLEX,       data conversion error on complex data type

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

User Action:   Enter another value.

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

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

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

COMPUSEQUAL,   Host language module will be compiled using <str>

Explanation:   The host language module, which is generated from the
               embedded SQL source, will be compiled using a qualifier
               which was not specified by the user.  This is to ensure
               the intended semantics of the generated code.

User Action:   Depending on the qualifier specified, this message may
               be supressed by explicitly specifying that this
               qualifier should be used.

COMTOOLON,     Command line longer than <num> character maximum

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

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

CONALREXI,     Constraint name <str> already exists in this database
               or schema



                                  69






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

User Action:   Choose a different name.

CONCHAILL,     Cannot begin program with continuation character

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

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

CONDICREQ,     Conflicting repository requirements

Explanation:   You specified both the DICTIONARY IS REQUIRED and
               DICTIONARY IS NOT REQUIRED clause in the same ALTER
               DATABASE statement.

User Action:   Change the ALTER DATABASE statement to include only one
               type of DICTIONARY REQUIRED option.

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 SORTED
               index does not support the DUPLICATES ARE COMPRESSED
               clause, so either remove that clause or change the
               index to TYPE IS SORTED RANKED.

CONFLQUAL,     conflicting qualifiers specified:  <str> and <str>

Explanation:   The two qualifiers you specified may not be used
               together.

User Action:   Choose one of the qualifiers

CONFSPECATR,   Conflicting specified attribute.  "<str>" are
               conflicting attributes

Explanation:   An attribute was specified in a conflicting manner.

User Action:   Remove conflicts and try the statement again.

CONFTXNALIAS,  Expected alias "<str>" (found "<str>") for table in
               reserving clause





                                  70






Explanation:   The ON ...  USING clause of SET and DECLARE TRANSACTION
               has already specified the ALIAS for the tables.

User Action:   Either use the alias specified by the ON clause, or
               omit the alias from the table specification.

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

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

CONLYOPT,      The LENGTH and AS clause for INCLUDE are only for
               embedded C programs

Explanation:   You used either the LENGTH or AS clause on an INCLUDE
               FROM DICTIONARY statement.  These options are available
               only to embedded C programs.

User Action:   The LENGTH clause is germaine only to C programs.  The
               AS clause must be accomplished by having two distinct
               records in the CDD.

CONNAMEXI,     Connection named "<str>" already exists

Explanation:   A connection with the name given already exists.

User Action:   Pass the name of a connection that doesn't exist.

CONNOTDEF,     Constraint <str> is not defined in database or schema

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

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

CONNOTSUP,     <str> is a constant host variable

Explanation:   You referred to a host variable which was declared as a
               constant.  Constant declarations are not supported.

User Action:   Either specify the constant as a literal, or use a host
               variable with that value.

CONREAATT,     Conflicting READ ONLY Attributes





                                  71






Explanation:   You specified both READ ONLY and READ WRITE in an ALTER
               STORAGE AREA statement.

User Action:   Re-enter the statement with either READ ONLY or READ
               WRITE, not both.

CONSNAATT,     Conflicting snapshot attributes

Explanation:   The CREATE DATABASE statement contained what could be
               conflicting snapshot options.

User Action:   Either remove the SNAPSHOT DISABLED clause from the
               root file parameters, or remove the SNAPSHOT clause
               from the storage area parameters.

CONSTNOUPD,    Variable "<str>" is declared CONSTANT - assignment not
               allowed

Explanation:   The named variable was declared with the CONSTANT
               keyword which indicates that it should not be changed
               within the scope of this compound statement.  This
               variable is the target of a SET, INSERT...RETURNING,
               SELECT...INTO, UPDATE...RETURNING, or GET GIAGNOSTICS
               statement or CALL output parameter.

User Action:   Check that the correct variable is used in this
               statement

CONTCHRILL,    String "<str>" can not be used as a continuation
               character

Explanation:   You specified a SET CONTINUE CHARACTER with a string
               that was not one character in width, or the character
               is not a terminating character and is therefore
               ambiguous.

User Action:   Revise the character used for this purpose.

CONTPREQ,      P characters must be contiguous in an edit string

Explanation:   More than one P characters are permitted in an edit
               string, but they must all be contiguous.  This edit
               string contained more than one P characters that are
               not contiguous.

User Action:   Make the P characters contiguous.

CONTRIACT,     The trigger actions on trigger <str> and trigger <str>
               conflict



                                  72






Explanation:   You cannot have two triggers which will be triggered
               for the same event on the same table.  These two
               triggers would both be triggered by the same event.

User Action:   Combine the two triggers into a single trigger.

CONVARDEF,     Column qualifier <str> is already defined

Explanation:   You either specified the same alias more than once in a
               select expression or did not specify an alias in a
               select expression that joins a table with itself.

User Action:   Either use unique aliases or introduce an alias.

CONVARILLUPD,  Column <str> in table <str> is not allowed in the
               target of an UPDATE

Explanation:   You specified a column which is in a table not allowed
               in this context.  For UPDATE statements, the column
               being updated must be in the table in UPDATE statement.

User Action:   Make sure the the column is named correctly, and any
               qualifier is correct.

CONVARUND,     Column qualifier <str> is not defined

Explanation:   You qualified a column name with an alias or table not
               specified in the FROM clause of the select expression.

User Action:   Make sure the qualifier you used matches an alias or
               table specified in the FROM clause.

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.

CORNAMREQ,     A correlation name is required for a derived table

Explanation:   When specifying a derived table, you failed to specify
               a correlation name.

User Action:   Please specify a correlation name.

CORREFFUN,     Correlated references in aggregate functions must not
               be in expressions





                                  73






Explanation:   You cannot use a correlated reference that is part of a
               value expression containing comparison operators, when
               the value expression is itself an argument to an
               aggregate function.  For example, SUM(corr_reference +
               5).

User Action:   Reformulate the select expression to avoid using a
               correlated reference in this manner.

CRE_CACHE_ERR, CREATE CACHE statement only valid as part of a CREATE
               DATABASE statement

Explanation:   The CREATE CACHE statement is only valid as part of the
               CREATE DATABASE statement.

User Action:   Place the CREATE CACHE statement in the CREATE DATABASE
               statement.

CRE_ERR_SCH,   CREATE <str> statement only valid as part of a CREATE
               DATABASE statement

Explanation:   This CREATE statement is not valid in this context.  It
               can only be used after attaching to the database, or as
               part of the CREATE DATABASE statement.  It is not valid
               in a schema or catalog.

User Action:   Specify the CREATE statement in the CREATE DATABASE
               statement.

CRE_STO_ERR_SCH, CREATE STORAGE AREA statement only valid as part of a
               CREATE DATABASE statement

Explanation:   The CREATE STORAGE AREA statement is only valid as part
               of the CREATE DATABASE statement.

User Action:   Place the CREATE STORAGE statement in the CREATE
               DATABASE statement.

CRE_SYN_ERR_SCH, CREATE SYNONYM statement only valid as part of a
               CREATE DATABASE statement

Explanation:   The CREATE SYNONYM statement is only valid as part of
               the CREATE DATABASE statement.  It is not valid in a
               schema or catalog.

User Action:   Specify the CREATE SYNONYM statement in the CREATE
               DATABASE statement.

CSETNOASCII,   character set <str> does not contain ASCII



                                  74






Explanation:   You specified a character set that does not contain
               ASCII characters where one is necessary.

User Action:   Specify a character set that contains ASCII.

CSETSYN,       invalid syntax in character set clause for variable
               <str>

Explanation:   There was something wrong with the syntax of the
               CHARACTER SET clause for the named variable
               declaration.

User Action:   Correct the syntax error and try again.

CS_ERR,        Error retrieving collating sequence <str>

Explanation:   SQL could not retrieve the specified collating
               sequence; see the message that follows.

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

CTXIGNORED,    <str> ignored due to setting of <str> logical name

Explanation:   Either "USING CONTEXT" or "CONTEXT qualifier" will be
               named first.  In the precompiler and module language
               processor respectively, the named feature will be
               ignored because the logical name named in the message
               was defined as "TRUE".

User Action:   If you want to migrate the application without the use
               of context items (i.e.  2PC/DDTM), no action is
               required.  To use a distributed transaction, you must
               change the definition of the logical name to "FALSE" or
               deassign it.

CTXPARMNOTALL, This statement not allowed in procedure in CONTEXT list

Explanation:   A procedure that was mentioned in the
               /CONTEXT=(proc,proc) list contains a statement which
               may not receive a context parameter.

User Action:   Remove the specified procedure name from the list.
               Using /CONTEXT=ALL is permitted, since those statements
               which may not receive a context parameter will not.

CURALRDCL,     Statement already declared as cursor <str>

Explanation:   The statement id passed into a declare cursor procedure
               was already declared as the cursor named in the



                                  75






               message.  Each statement can create only one cursor.

User Action:   Declare another statement to create a unique statement
               id for each cursor.

CURALROPE,     Cursor <str> was already open

Explanation:   You opened a cursor that was already open.  An implicit
               close will be done on the cursor and the cursor
               reopened.

User Action:   None.

CURNAMEXI,     Cursor name <str> has already been declared

Explanation:   You cannot use the same name in more than one DECLARE
               CURSOR statement.

User Action:   Change the name of this cursor.

CURNOTOPE,     Cursor <str> is not opened

Explanation:   You named a cursor that was not open in a FETCH
               statement, CLOSE statement, or in the WHERE CURRENT OF
               clause of an UPDATE or DELETE statement.

User Action:   Issue an OPEN statement for the cursor before naming it
               in any of those statements.  Close the cursor only once
               after opening it.

CUROFNOT,      CURRENT OF cursor-name is allowed only in DECLARE LIST
               CURSOR, UPDATE and DELETE statements

Explanation:   The CURRENT OF cursor-name clause is used to modify or
               delete the current record in a cursor.  It has no
               meaning in the WHERE clause of a select expression
               except in declare list cursor.

User Action:   Replace the WHERE CURRENT OF clause with a WHERE
               predicate clause that specifies the record you wish to
               select.

CUROFNOTFOR,   CURRENT OF clause references cursor not in FOR loop

Explanation:   The CURRENT OF clause of an UPDATE or DELETE statement
               specifies a cursor that is not specified in the FOR
               loop.

User Action:   Use a cursor which is part of the FOR loop.



                                  76






CUROFREQ,      CURRENT OF cursor-name is required

Explanation:   In a positioned INSERT statement, the WHERE clause must
               be WHERE CURRENT OF cursor-name.

User Action:   Restrict usage of to only WHERE CURRENT OF

CUROFSTA,      CURRENT OF clause cannot refer to cursor based on
               prepared statement

Explanation:   The CURRENT OF clause of an UPDATE or DELETE statement
               specifies a cursor based on a prepared statement.
               Because the prepared statements are generated at run
               time, you cannot precompile UPDATE or DELETE statements
               that refer to cursors based on them.

User Action:   Use a cursor which is based on an embedded SELECT
               statement (which is known at compile time), or
               dynamically execute the UPDATE or DELETE statement so
               it can be interpreted at run time.

CURSTMTTXN,    Cursor statements must be executed in the same
               transaction

Explanation:   The statement was executed in the wrong transaction.  A
               cursor statement, such as FETCH, INSERT (positioned),
               UPDATE (positioned), DELETE (positioned), OPEN (list
               cursor) must be executed in the same transaction as the
               OPEN statement of the cursor to which the statement
               refers.

User Action:   If a context structure was used for the OPEN statement,
               the same one must be used for the statements which
               operate on the cursor.  If no context structure was
               used for the OPEN statement, no context structure may
               be used for the statements which operate on the cursor.

CURTWOOPEN,    Cursor <str> has two open procedures

Explanation:   There are two open procedures for this cursor.  A
               module can only have one procedure which opens a
               particular cursor.

User Action:   Remove one of the procedures which opens this cursor.
               Call the remaining procedure more than one time.

CURUSEINV,     USING clause not allowed for this cursor

Explanation:   An OPEN or FETCH statement can specify a USING clause



                                  77






               only for cursors based on a statement named in a
               PREPARE statement.  The cursor specified in this OPEN
               or FETCH statement is not.

User Action:   Remove the USING clause from the OPEN or FETCH
               statement.

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.

DATCNVERR,     conversion error in date string

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

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

DATCONERR,     Data conversion error for string '<str>'

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

User Action:   The secondary message should clarify the problem.

DATEADDILL,    Operands of date/time addition are incorrect

Explanation:   You used an addition operator with two operands which



                                  78






               were not of the correct data types.

User Action:   Change the expression to use a different operator or
               operands.

DATEDIGNEQ,    Date/time expressions with different interval leading
               digits precision are not comparable

Explanation:   You attempted to compare or perform an arithmetic
               operation on two date/time expressions with different
               interval leading digits precisions.  These expressions
               are considered not comparable, and therefore this
               operation is not allowed.

User Action:   Use different operands or use the CAST function to
               change the interval leading digits precision of one of
               the operands.

DATEDIVILL,    Operands of date/time division are incorrect

Explanation:   You used an division operator with two operands which
               were not of the correct data types.

User Action:   Change the expression to use a different operator or
               operands.

DATEEQLILL,    Operands of date/time comparison are incompatible

Explanation:   You used a comparison operator with two operands which
               were not of compatible data types.

User Action:   Change the expression to use a different operator or
               operands.

DATEFORTIMES,  DATE VMS used instead of TIMESTAMP

Explanation:   This database does not support the datetime data types.
               DATE VMS will be used instead of TIMESTAMP.

User Action:   Upgrade attached database or remove TIMESTAMP from
               statement

DATEMULILL,    Operands of date/time multiplication are incorrect

Explanation:   You used an multiplication operator with two operands
               which were not of the correct data types.

User Action:   Change the expression to use a different operator or
               operands.



                                  79






DATEOPR,       Illegal date operator

Explanation:   Used an invalid operator in a date expression

User Action:   remove expression

DATESCANEQ,    Date/time expressions with different fractional seconds
               precision are not comparable

Explanation:   You attempted to compare or perform an arithmetic
               operation on two date/time expressions with different
               fractional seconds precisions.  These expressions are
               considered not comparable, and therefore this operation
               is not allowed.

User Action:   Use different operands or use the CAST function to
               change the fractional seconds precision of one of the
               operands.

DATESUBILL,    Operands of date/time subtraction are incorrect

Explanation:   You used an subtraction operator with two operands
               which were not of the correct data types.

User Action:   Change the expression to use a different operator or
               operands.

DATETIMES,     This database does not support date/time data types

Explanation:   You executed a query that requires use of the date/time
               types and arithmetic support.  However, the source
               database does not have those capabilities.

User Action:   Upgrade the database to a more recent version of Oracle
               Rdb

DATETIME_PREC, Date/time leading precision for <str> must be in the
               range of 1 and 9

Explanation:   The scale supplied with the DATE TIME data type must be
               between 2 and 9 inclusive.

User Action:   Supply a legal date time leading precision.

DATETIM_PREC,  Date/time leading precision for <str> declared twice

Explanation:   The leading precision for a DATETIME data type was
               declared more than once.  This is typical of a
               declaration of INTERVAL DAY(3) TO SECOND(2.1)



                                  80






User Action:   Supply a legal date time scale

DATETIM_SCALE, Date/time scale for <str> must be less than or equal to
               <num>

Explanation:   The scale supplied with the DATE TIME data type must be
               less than or equal to six.

User Action:   Supply a legal date time scale.

DATIM_SCALE,   Date/time scale for <str> must be positive

Explanation:   The scale supplied with the DATE TIME data type must be
               greater than or equal to zero.

User Action:   Supply a legal date time scale.

DATNOTSUP,     Date data type not supported in this context

Explanation:   The output of a date value to the language file is not
               supported.

User Action:   Do not use dates in this manner.

DATTYPUNK,     Data type unknown.  Expression cannot use only host
               variables

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

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

DBABWCLEANIS,  Async batch write clean buffers is <num>

Explanation:   Batch write clean buffer count as found in the
               interchange file.

User Action:   None.

DBABWCLEANWAS, Async batch write clean buffers was <num>, now is <num>

Explanation:   Batch write clean buffer count as found in the
               interchange file.  New value was specified by user.

User Action:   None.

DBABWISN,      Asynchronous Batch Write is DISABLED





                                  81






Explanation:   Asynchronous Batch Write is DISABLED in newly-created
               database.  Value either specified by user or found in
               the interchange file.

User Action:   None.

DBABWISY,      Asynchronous Batch Write is ENABLED

Explanation:   Asynchronous Batch Write is ENABLED in newly-created
               database.  Value either specified by user or found in
               the interchange file.

User Action:   None.

DBABWMAXIS,    Async batch write max buffers is <num>

Explanation:   Batch write max buffer count as found in the
               interchange file.

User Action:   None.

DBABWMAXWAS,   Async batch write max buffers was <num>, now is <num>

Explanation:   Batch write max buffer count as found in the
               interchange file.  New value was specified by user.

User Action:   None.

DBABWWASN,     Asynchronous Batch Write was DISABLED, now is ENABLED

Explanation:   Asynchronous Batch Write was DISABLED as found in the
               interchange file.  New value was specified by user.

User Action:   None.

DBABWWASY,     Asynchronous Batch Write was ENABLED, now is DISABLED

Explanation:   Asynchronous Batch Write was ENABLED as found in the
               interchange file.  New value was specified by user.

User Action:   None.

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



                                  82






               force the users off by closing the database.

DBAIJ_SHTDWN_WAS, Journal shutdown minutes was <num>

Explanation:   Shutdown minutes as found in the interchange file.

User Action:   None.

DBAPFDEPTHIS,  Async prefetch depth buffers is <num>

Explanation:   Number of prefetch buffers as found in the interchange
               file.

User Action:   None.

DBAPFDEPTHWAS, Async prefetch depth buffers was <num>, now is <num>

Explanation:   Number of prefetch buffers as found in the interchange
               file.  New value was specified by user.

User Action:   None.

DBAPFISN,      Asynchronous Prefetch is DISABLED

Explanation:   Asynchronous Prefetch is DISABLED in newly-created
               database.  Value either specified by user or found in
               the interchange file.

User Action:   None.

DBAPFISY,      Asynchronous Prefetch is ENABLED

Explanation:   Asynchronous Prefetch is ENABLED in newly-created
               database.  Value either specified by user or found in
               the interchange file.

User Action:   None.

DBAPFWASN,     Asynchronous Prefetch was DISABLED, now is ENABLED

Explanation:   Asynchronous Prefetch was DISABLED as found in the
               interchange file.  New value was specified by user.

User Action:   None.

DBAPFWASY,     Asynchronous Prefetch was ENABLED, now is DISABLED

Explanation:   Asynchronous Prefetch was ENABLED as found in the
               interchange file.  New value was specified by user.



                                  83






User Action:   None.

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.

DBCLWASOFF,    CARRY OVER LOCKS were DISABLED now are ENABLED

Explanation:   You overrode the original setting of the carry over
               locks during an import

User Action:   None.

DBCLWASON,     CARRY OVER LOCKS were ENABLED now are DISABLED

Explanation:   You overrode the original setting of the carry over
               locks during an import.

User Action:   None.

DBENVSYNERR,   Syntax error in database environment specification

Explanation:   The database environment specification in a CONNECT
               statement is syntactically incorrect.  The sub-error
               returns more specific information.

User Action:   Correct the syntax error and retry execution of the
               statement.

DBFCINTVLIS,   Journal fast commit TRANSACTION INTERVAL is <num>

Explanation:   Journal fast commit TRANSACTION interval as found in
               the interchange file.

User Action:   None.

DBFCINTVLWAS,  Journal fast commit TRANSACTION INTERVAL was <num> now
               is <num>

Explanation:   User Action:  None.

DBFCISOFF,     Commit to journal optimization is DISABLED

Explanation:   Commit to journal optimization is disabled.

User Action:   None.



                                  84






DBFCISON,      Commit to journal optimization is ENABLED

Explanation:   Commit to journal optimization is enabled.

User Action:   None.

DBFCWASON,     Commit to journal optimization was ENABLED

Explanation:   Commit to journal optimization was found in the
               interchange file.  Feature DISABLED during import.

User Action:   None.

DBGBPGISDSK,   Database global buffer page transfer is via DISK

Explanation:   Global buffer pages transfer by DISK.  The value was
               either specified by you or was found in the interchange
               file.

User Action:   None.

DBGBPGISMEM,   Database global buffer page transfer is via MEMORY

Explanation:   Global buffer pages transfer by MEMORY.  The value was
               either specified by you or was found in the interchange
               file.

User Action:   None.

DBGBPGWASDSK,  Database global buffer page transfer was via DISK, now
               via MEMORY

Explanation:   Global buffer pages transfer by DISK as found in the
               interchange file.  A new value was specified.

User Action:   None.

DBGBPGWASMEM,  Database global buffer page transfer was via MEMORY,
               now via DISK

Explanation:   Global buffer pages transfer by MEMORY as found in the
               interchange file.  A new value was specified.

User Action:   None.

DBHANDUNK,     <str> is not the alias of a known database

Explanation:   You specified an unknown alias to qualify a table or
               view name in a select expression.



                                  85






User Action:   Check the query and the DECLARE ALIAS statements in
               your module or any ATTACH statement make sure the alias
               names match.

DBHDLREQ,      db handle should be specified for EXTRACTION ROLLUP
               transfers

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

User Action:   Re-enter the CREATE TRANSFER statement by specifying
               the database handle of the source database for each of
               the move-relation-clauses.

DBINUSE,       Database cannot be dropped because it is currently in
               use.

Explanation:   You issued a DROP DATABASE statement, but another user
               is attached the same database.

User Action:   Wait for other users to detach from the database.  If
               the database is in use, however, one would question the
               wisdom of trying to delete it.  Remember that patience
               is a virtue.

DBJRNCMTISN,   Commit to journal optimization is Disabled

Explanation:   Commit to journal optimization DISABLED in
               newly-created database.  Value either specified by user
               or found in the interchange file.

User Action:   None.

DBJRNCMTISY,   Commit to journal optimization is Enabled

Explanation:   Commit to journal optimization ENABLED in newly-created
               database.  Value was either specified by user or found
               in the interchange file.

User Action:   None.

DBJRNCMTWASN,  Commit to journal optimization was Disabled

Explanation:   Commit to journal optimization was DISABLED in the
               interchange file.  You specified a new value.

User Action:   None.





                                  86






DBJRNCMTWASY,  Commit to journal optimization was Enabled

Explanation:   Commit to journal optimization was ENABLED in the
               interchange file.  You specified a new value.

User Action:   None.

DBKAMBIG,      DBKEY reference is ambigous

Explanation:   You made an unqualified reference to DBKEY in a context
               where there is more than one source of a dbkey.

User Action:   Add a table qualifier to the DBKEY reference.

DBKBIGVAR,     The DBKEY for table <str> is <num> bytes, variable
               <str> must be the same size or larger

Explanation:   The variable you are using with the DBKEY is not the
               same size as the dbkey.

User Action:   Use a variable that is the same size as the dbkey.

DBKCHRVAR,     DBKEY is compatible only with character variables

Explanation:   The variable you are using with the DBKEY is not a
               character variable.

User Action:   Use a variable of type CHAR or VARCHAR.

DBKNOCTX,      DBKEY isn't valid in this context

Explanation:   You have specified the value DBKEY in a value
               expression where a DBKEY does not exist.

User Action:   Remove the reference to DBKEY.

DBKTOOBIG,     The DBKEY for table <str> is <num> bytes, host variable
               <str> must be the same size or larger.

Explanation:   The host variable you are using with the DBKEY is not
               the same size as the dbkey.

User Action:   Allocate a host variable which is the correct size.

DBLCKTMOUTIS,  LOCK TIMEOUT is <num> second(s)

Explanation:   Lock timeout interval as found in the interchange file.

User Action:   None.



                                  87






DBLCKTMOUTWAS, LOCK TIMEOUT INTERVAL was <num> now is <num> second(s)

Explanation:   Lock timeout interval as found in the interchange file.

User Action:  

DBLOCKISN,     Lock Partitioning is DISABLED

Explanation:   Lock Partitioning is DISABLED in newly-created
               database.  Value either specified by user or found in
               the interchange file.

User Action:   None.

DBLOCKISY,     Lock Partitioning is ENABLED

Explanation:   Lock Partitioning is ENABLED in newly-created database.
               Value either specified by user or found in the
               interchange file.

User Action:   None.

DBLOCKWASN,    Lock Partitioning was DISABLED, now is ENABLED

Explanation:   Lock Partitioning was DISABLED as found in the
               interchange file.  New value was specified by user.

User Action:   None.

DBLOCKWASY,    Lock Partitioning was ENABLED, now is DISABLED

Explanation:   Lock Partitioning was ENABLED as found in the
               interchange file.  New value was specified by user.

User Action:   None.

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

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



                                  88






               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.

DBNAMCONF,     Two databases share the alias name <str>, but their
               handle addresses differ (<num> vs.  <num>)

Explanation:   An application linked against a shared image has
               declared a database with same alias as the shared
               image, but the two databases don't share the same
               handle address.

User Action:   Either choose a different alias name or link the images
               with PSECT attributes GBL,NOSHR for the DB handle
               PSECTs.

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



                                  89






               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.

DBNOTINCONN,   The required database alias is not part of the current
               connection

Explanation:   A SQL statement references a DSRI request that is
               compiled against a database alias that is not attached
               in the current connection.

User Action:   Specify the necessary alias in the connect statement or
               execute an SQL statement that does not reference the
               alias.

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.

DBRBOUND,      attach not allowed while your process is being
               recovered





                                  90






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.

DBSCOPCONF,    Two databases share the same alias name, but their
               scopes differ

Explanation:   You are attempting to override a LOCAL alias with a
               GLOBAL alias or the reverse.

User Action:   Make the scope of the alias (GLOBAL or LOCAL) match the
               alias it overrides or choose a different alias name.

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.

DBSPAMISN,     Incremental Backup Scan Optim does not use SPAM pages

Explanation:   Incremental Backup disabled use of SPAM pages in
               newly-created database.  Value either specified by user
               or found in the interchange file.

User Action:   None.

DBSPAMISY,     Incremental Backup Scan Optim uses SPAM pages

Explanation:   Incremental Backup enabled use of SPAM pages in
               newly-created database.  Value either specified by user
               or found in the interchange file.

User Action:   None.

DBSPAMWASN,    Incremental Backup did not use SPAM pages, now they are
               ENABLED

Explanation:   Incremental Backup disabled use of SPAM pages as found
               in the interchange file.  New value was specified by
               user.





                                  91






User Action:   None.

DBSPAMWASY,    Incremental Backup used SPAM pages, now they are
               Disabled

Explanation:   Incremental Backup enabled use of SPAM pages as found
               in the interchange file.  New value was specified by
               user.

User Action:   None.

DBSPECSYNERR,  Syntax error in database specification

Explanation:   The database specification in an ATTACH statement is
               syntactically incorrect.  The sub-error returns more
               specific information.

User Action:   Correct the syntax error and retry execution of the
               statement.

DBTRISTMT,     Triggered statement is not in the same database as the
               trigger

Explanation:   You specified a triggered statement which uses a
               different database than the database the trigger is a
               part of.  This is not legal.

User Action:   Specify only triggered actions which execute in the
               database in which the trigger is defined.

DB_EXISTS,     The repository pathname, <str>, chosen for the database
               name already exists

Explanation:   The repository path name chosen for the database name
               already exists in the current directory.

User Action:   Use another, unique repository path name.

DB_HANDEC,     Handle already declared

Explanation:   You declared a database handle via ACMS.  This
               interferes with defining a handle through the dynamic
               interface.

User Action:   You should not specify another handle.

DB_HANDEC2,    Handle already declared

Explanation:   You have declared a database handle via ACMS.  This



                                  92






               interferes with defining a handle through the dynamic
               interface.  This also interferes with declaring
               multiple database handles.

User Action:   You should not specify another handle.

DB_HANLON,     The alias must be a 32-bit longword

Explanation:   Aliases that are passed from a program must be 32-bit
               longwords passed by descriptor.

User Action:   Define the alias to be a 32-bit longword.  Examples:
               For COBOL:  01 AUTHID PIC S9(9) COMP.  For FORTRAN:
               INTEGER*4 AUTHID.

DB_IN_TXN,     Authorization identifier <str> is already part of this
               transaction

Explanation:   You specified an authorization identifier twice within
               in the transaction parameters of SET TRANSACTION or
               DECLARE TRANSACTION.

User Action:   Specify the authorization identifier only once.

DCLBEFEXE,     DECLARE TRANSACTION and DECLARE ALIAS must be before
               executable statements

Explanation:   DECLARE TRANSACTION and DECLARE ALIAS must come before
               the first executable statement in a program.  An
               executable statement is a statement such as SELECT,
               INSERT, UPDATE, OR CREATE.  To avoid this error, put
               all DECLARE ALIAS and DECLARE TRANSACTION statements in
               a context file, if possible.

User Action:   Move all DECLARE TRANSACTION statements and DECLARE
               ALIAS statements before all executable statements.  You
               should specify all DECLARE ALIAS statements before the
               first DECLARE TRANSACTION statement.

DCLDATBEF,     DECLARE ALIAS must be before other DECLARE statements

Explanation:   All DECLARE ALIAS statements must come before any
               DECLARE CURSOR, DECLARE TRANSACTION, or DECLARE TABLE
               statements in a program.

User Action:   Move all DECLARE ALIAS statements before other DECLARE
               statements.

DDALERR,       Replication Option for Rdb fatal error



                                  93






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

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

DDALFMTUNK,    Replication Option for Rdb ACK file format not
               understood

Explanation:   The format of the ACK file was not as expected by SQL.

User Action:   See the system manager to check for compatibility
               between versions of SQL and DDAL.  If not incompatible,
               contact your Oracle support representative.

DDALNOTINS,    Replication Option for Rdb not installed

Explanation:   The Replication Option for Rdb (previously called DEC
               Data Distributor) product is not installed on the
               system.

User Action:   See the system manager to install the product.

DDLPARAM,      You referred to parameter <str> in a DDL statement

Explanation:   You specified a parameter in a DDL statement such as a
               CREATE VIEW or CREATE TRIGGER statement.  This is not
               supported.

User Action:   Remove the parameter specification.

DDNOTSUPP,     Installed version of repository does not support this
               SQL version.

Explanation:   The version of the repository on your system does not
               contain the necessary SQL support.

User Action:   Upgrade the version of repository on your system.
               Alternatively, do not access the repository with this
               version of SQL.

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.



                                  94






DECCURINTO,    DECLARE CURSOR statement cannot include an INTO clause

Explanation:   You specified an INTO clause in the select expression
               in the DECLARE CURSOR statement.  It should go in the
               FETCH statement or in a singleton select statement.

User Action:   Remove the INTO clause.

DEFCONMOD,     Command line specified default constraint evaluation
               mode is off

Explanation:   Your command line specified (either explicitly or by
               default) that the constraint mode when you start a
               transaction is OFF; that is, that by default,
               constraints will not be evaluated until a COMMIT is
               executed.  The ANSI and ISO SQL standards require that
               the constraint mode when you start a transaction be ON;
               that is, that constraints be evaulated at the end of
               every SQL statement.

User Action:   If it is important to have standard behavior in your
               program, and you have constraints in your database, you
               should specify the /CONSTRAINT_MODE=ON in the module
               language command line or
               /SQLOPTIONS=(CONSTRAINT_MODE=ON) in the precompiler
               command line.

DEFDBDEC,      A database has already been declared with the default
               alias

Explanation:   You attempted to attach a database using the default
               alias when there already was a one.  In interactive
               SQL, you get this error only if you choose not to
               override the current default database.

User Action:   Include an alias which has not been declared in the
               DECLARE ALIAS or ATTACH statement.

DEFLT_DBSRC,   Defaulting to the .dbsrc file in the home directory

Explanation:   SQL is unable to use the value specified for the .dbsrc
               file, therefore, SQL is defaulting to the .dbsrc file
               in the your home directory.

User Action:  

DEFLT_SQLINI,  Defaulting to the sqlini.sql file in the pwd

Explanation:   SQL is unable to use the value specified for the



                                  95






               sqlini.sql file, therefore, SQL is defaulting to the
               sqlini.sql file in the present working directory.

User Action:  

DEFVALINC,     You specified a default value for <str> which is
               inconsistent with its data type

Explanation:   The value specified for the default value must have the
               same type (i.e.  both character, both exact numeric,
               both approximate numeric or both dates) as the column
               or domain for which it is the default.  It must also be
               small enough to fit into column or domain.

User Action:   Replace the specified value with a value that is
               compatible with the column.

DEFVALNOTCB,   Default values are not allowed for COMPUTED BY or
               AUTOMATIC INSERT columns

Explanation:   You specified a default value for a COMPUTED BY column,
               or an AUTOMATIC AS or AUTOMATIC INSERT AS column for
               which defaults are not supported.

User Action:   Remove the default clause from this definition.

DEFVALUNS,     Default values are not supported for the data type of
               <str>

Explanation:   You specified a default value for a data type (such as
               segmented string) for which defaults are not supported.

User Action:   Remove the default clause from this definition.

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

Explanation:   You specified both concurrency options (CONSISTENCY
               LEVEL 2 and CONSISTENCY LEVEL 3) in a DECLARE
               TRANSACTION statement.

User Action:   Specify only one option in your DECLARE TRANSACTION
               statement.

DELBACKUP,     EXPORT errors, interchange file deleted

Explanation:   The export that you were performing could not be
               successfully completed.

User Action:   Determine why the export failed and correct that



                                  96






               situation.

DELETEFAILS,   Cache file <str> deletion failed

Explanation:   Attempt made to delete non existing file.

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

DELLSTDYNCUR,  DELETE LIST cannot reference dynamic table cursor,
               <str>

Explanation:   A precompiled DELETE LIST statement references a table
               cursor that is dynamic.

User Action:   The DELETE LIST statement for the dynamic cursor should
               be PREPAREd and EXECUTEd.

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.

DEPIMPCAS,     Implicit cascading may not be supported in a future
               version

Explanation:   On a DROP TABLE, SQL will currently drop all indexes,
               views triggers and constraints which reference the
               table.  In a future release, these objects will only be
               dropped if you specify CASCADE.  On a DROP VIEW, SQL
               will currently drop all views which references that
               view.  In a future release, they will only be dropped
               if you specify CASCADE.

User Action:   If you want these objects to be deleted, specify the
               CASCADE option on the drop.

DEPR_ANSI_PARM, NOANSI_PARAMETERS is the default.  Future versions may
               require colons

Explanation:   None.

DEPR_DIAGNOSTIC, DIAGNOSTIC is replaced by CONSTRAINT



                                  97






DEPR_DQUOTES,  " used instead of ' for string literal

Explanation:   Double quotes were used to delimit a string literal.
               This usage is deprecated.  Single quotes are the
               correct delimiters for string literals

User Action:   Use single quotes for string literals; double quotes
               have a special usage, denoting identifiers that bypass
               reserved word checking

DEPR_FEATURE,  Deprecated Feature:  <str>

Explanation:   The syntax indicated is a deprecated feature.  It may
               not be supported in a future version of SQL.

User Action:   Please look in the SQL Reference Manual appendix of
               deprecated features and replace this syntax with the
               syntax that has superceded it.

DEPR_INHERDESC, inheritance of DESC qualifier

Explanation:   Default inheritance of previous item order direction is
               deprecated.  A future release will make unqualified
               items default to ASCENDING.

DEP_FEATURE,   Deprecated Feature

Explanation:   The syntax indicated is a deprecated feature.  It may
               not be supported in a future version of SQL.

User Action:   Please look in the SQL Reference Manual appendix of
               deprecated features and replace this syntax with the
               syntax that has superceded it.

DIC_DB_CHG1,   A repository definition used by database <str> has
               changed

Explanation:   This database refers to a definition in the repository
               that has changed.

User Action:   Use the INTEGRATE statement to resolve any differences.

DIC_DB_CHG2,   Use the INTEGRATE statement to resolve any differences
               between the repository and the database

Explanation:   The data definitions in the repository no longer match
               the definitions in the database file.

User Action:   Use the INTEGRATE statement to resolve any differences.



                                  98






DIFFDEFINV,    The invoker is not the definer, <str>

Explanation:   The RESTRICT_INVOKER option was specified at compile
               time to ensure ANSI semantic behavior.  This requires
               that only the same user who compiles a module (the
               definer) may be the user who executes it (the invoker).

User Action:   Recompile the module.  If it is not important that ANSI
               semantics be maintained, do not specify the
               RESTRICT_INVOKER option; any user will be able to
               execute a program linked with this module.  If ANSI
               semantics must be maintained, make sure that the user
               who will be the invoker also compiles the program.
               Alternatively, a module language AUTHORIZATION clause
               specifies who the definer is, and may be used by one
               user to compile a module for another.

DIFFSCHVIEW,   Views and tables must be moved from the same database

Explanation:   The user entered a move tables clause specifying a
               database with a different as the database named in the
               move views clause.

User Action:   Enter the CREATE TRANSFER statement with a move views
               clause whose database is the same as the one in the
               move tables clause.

DIGNUMPIC,     more than 31 digits in a numeric edit string

Explanation:   The edit string generates more than 31 digits.

User Action:   Reduce the number of digits in this numeric picture
               string.

DISABLED_OSF,  <str> is disabled on OSF

Explanation:   This feature was not part of the SQL port to OSF.  This
               feature may be ported in a future release.  It is
               currently unavailable on OSF.

User Action:   Do not use this feature.

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

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



                                  99






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.

DOMCONSNODEFER, Domain constraint must be NOT DEFERRABLE

Explanation:   You tried to specify that a domain constraint's
               evaluation is DEFERRABLE either by explicit syntax or
               by taking the default evaluation.

User Action:   Either specify NOT DEFERRABLE or choose a dialect that
               defaults to the NOT DEFERRABLE constraint evaluation.

DOMCONSNONAM,  A name for a domain constraint is not allowed

Explanation:   You tried to specify the name of a domain constraint
               which is not allowed at this time.

User Action:   Do not specify a name for a domain constraint.

DOMNOTBCK,     Domain <str> cannot be exported WITH NO EXTENSIONS

Explanation:   This domain cannot be exported when NO EXTENSIONS is
               specified.  It is of a data type which was not
               supported before Rdb 4.1 in any fashion.  The secondary
               message will describe exactly which data type was used.

User Action:   If the interchange file will not be used to create a
               database in prior versions of Oracle Rdb, Oracle Rdb
               Engineering would recommend restarting the EXPORT
               specifying WITH EXTENSIONS.  Otherwise, change the
               affected domain to a type which was supported in
               earlier versions or remove it entirely.

DOM_INVALID,   collating sequence invalid for non-text domain <str>

Explanation:   A collating sequence was defined on a non-text domain.
               The domain definition is invalid.





                                 100






User Action:   None.

DPBFMTUNK,     Replication Option for Rdb DPB buffer not understood

Explanation:   The format of the DPB buffer from the ACK file was not
               as expected by SQL.

User Action:   See the system manager to check for compatibility
               between versions of SQL and DDAL.  If not incompatible,
               contact your Oracle support representative.

DROP_COLDOM,   Column <str> in table <str> is being altered to remove
               domain

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify the CASCADE behavior, SQL drops
               all of the domains in that schema or catalog.  If one
               of the columns in a table outside of the schema or
               catalog references one of those domains, it is altered
               in such a way that it no longer depends on the domain
               being deleted.

User Action:   None.

DROP_COLL,     Collating sequence <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify CASCADE behavior, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message is simply to indicate which
               objects are being dropped.

User Action:   None.

DROP_DOM,      Domain <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify CASCADE behavior, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message is simply to indicate which
               objects are being dropped.

User Action:   None.

DROP_FUNCTION, Function <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG



                                 101






               statement and specify the CASCADE clause, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message indicates which objects are being
               dropped.

User Action:   None.

DROP_IDX,      Index <str> is also being dropped.

Explanation:   When you issue the DROP TABLE statement, SQL also drops
               all indexes that use that table.  Also, when you issue
               the DROP SCHEMA or DROP CATALOG statement and specify
               CASCADE behavior, SQL drops all of the objects in that
               schema or catalog and all of the objects referenced by
               any objects being dropped.  This message notifies you
               which indices those are.  It is informational only.

User Action:   None.

DROP_MODULE,   Module <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify the CASCADE clause, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message indicates which objects are being
               dropped.

User Action:   None.

DROP_OUTLINE,  Query Outline <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify CASCADE behavior, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message is simply to indicate which
               objects are being dropped.

User Action:   None.

DROP_PROCEDURE, Procedure <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify the CASCADE clause, SQL drops all
               of the objects in that schema or catalog and also drops
               all of the objects referenced by any of the objects
               being dropped.  This informational message indicates



                                 102






               which objects are being dropped.

User Action:   None.

DROP_SEQUENCE, Sequence <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify the CASCADE clause, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message indicates which objects are being
               dropped.

User Action:  

DROP_STOMAP,   VIA clause on storage map <str> is also being dropped.

Explanation:   When you issue the DROP TABLE statement, SQL also drops
               the the index for that table.  In order to drop the
               index, any via clauses which reference the index must
               be delete so the index can be dropped.  The message is
               informational only.

User Action:   None.

DROP_STORMAP,  Storage map <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify CASCADE behavior, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message is simply to indicate which
               objects are being dropped.

User Action:   None.

DROP_TABLE,    Table <str> is also being dropped

Explanation:   When you issue the DROP SCHEMA or DROP CATALOG
               statement and specify CASCADE behavior, SQL drops all
               of the objects in that schema or catalog and all of the
               objects referenced by any objects being dropped.  This
               informational message is simply to indicate which
               objects are being dropped.

User Action:   None.

DROP_TRIG,     Trigger <str> is also being dropped.





                                 103






Explanation:   When you issue the DROP TABLE statement, SQL also drops
               all triggers that use that table.  Also, when you issue
               the DROP SCHEMA or DROP CATALOG statement and specify
               CASCADE behavior, SQL drops all of the objects in that
               schema or catalog and all of the objects referenced by
               any objects being dropped.  This message notifies you
               which triggers SQL is dropping.  The message is
               informational only.

User Action:   None.

DROP_VIEW,     View <str> is also being dropped.

Explanation:   When you issue the DROP TABLE statement, SQL also drops
               all views that use that table.  Also, when you issue
               the DROP SCHEMA or DROP CATALOG statement and specify
               CASCADE behavior, SQL drops all of the objects in that
               schema or catalog and all of the objects referenced by
               any objects being dropped.  This message notifies you
               which views those are.  It is informational only.

User Action:   None.

DTFMTTOOBIG,   Date or time format must be less than 999.

Explanation:   You entered a DATE or TIME value greater than 999 in
               the SET DATE FORMAT statement.

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

DTONCEEACH,    You can specify DATE or TIME only once each.

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

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

DUPAIJFIL,     duplicate AIJ filename "<str>" specified

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

User Action:   Please specify a unique AIJ filename.

DUPAIJNAM,     duplicate AIJ name "<str>" specified





                                 104






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

User Action:   Please specify a unique AIJ name.

DUPCCHNAM,     record cache "<str>" already exists

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

User Action:   Please specify a unique record cache name.

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

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

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

DUPL_SRC_FILE, Source file already specified, found <str>

Explanation:   A source file has already been supplied.  A second
               source file has been specified.

User Action:   Remove or correct the second source file.

DUPPROCNAM,    <str> is a duplicate procedure name

Explanation:   There are two procedures in this module with this name.

User Action:   Change the name of one of the procedures.

DUPREFACT,     Duplicate <str> referential action

Explanation:   You specified two update or two delete actions on a
               referential constraint.  This is not supported.

User Action:   Remove one of the referential actions.





                                 105






DUPVAR,        Variable <str> is already defined

Explanation:   You defined a SQL variable for which there was already
               a declaration.

User Action:   Either use the variable, or specify the name of a
               variable which is not already defined.

DUPVARPROC,    Variable <str> is already defined as a parameter

Explanation:   You defined a SQL variable for which there was already
               a parameter declaration.

User Action:   Specify the name of a variable which is not already
               declared as a parameter

DWNGRDCLS,     Option <str> is not supported by this version and has
               been downgraded to <str>

Explanation:   The listed option is not supported by this Rdb or CDD
               version, the command is attempted using supported
               option.

User Action:   In many cases the downgraded c;lause may succeed, if
               not then you must use an alternate clause that is
               supported.  Note that CDD Repository does not support
               CASCADE for all objects and so DROP may fail if
               attached by PATHNAME.  Try attaching by FILENAME and
               repeating the operation.

DYNHVVER,      Compiled SQL data structures not recognized by runtime
               SQL

Explanation:   Your application was compiled using a version of SQL
               that uses data structures unrecognized by the running
               version of SQL.

User Action:   Re-compile the program under the original version of
               SQL or use the running version of SQL.

DYNSIZARR,     Host variable <str> is an array whose bounds are
               determined at runtime

Explanation:   The SQL precompilers do not support references to
               arrays whose bounds are determined at run time
               (dynamically-sized arrays).

User Action:   Assign the value in the dynamically-sized array to a
               field which is not in a dynamically-sized array before



                                 106






               using it in an SQL statement.

EDITUSING,     The EDIT USING clause may only be used in interactive
               SQL

Explanation:   The EDIT USING clause is only supported by the
               interactive SQL interface.

User Action:   Rewrite the query without the EDIT USING clause.

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.

EMPMSGVEC,     Empty message vector returned.  Please contact your
               Oracle support representative

Explanation:   The database system returned an empty message vector
               and nothing can be determined about the success or
               failure of the SQL statement for which the message
               vector was returned.  This is a database system
               software error.

User Action:   Contact your Oracle support representative.  Retain the
               source of the program which caused this error.

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.

END,           End of input





                                 107






Explanation:   No more input was given to SQL.

User Action:   None.

ENUM_VAR,      Host variable <str> is an enum variable which is
               illegal in SQL statements.

Explanation:   The named variable is defined as a C enum variable.
               Such fields are not legal in SQL statements.

User Action:   Use a different variable.

ERRATTDEC,     Error attaching to database <str>

Explanation:   An ATTACH, DECLARE ALIAS or CONNECT statement specified
               an invalid or nonexistent file specification or
               repository path name.  See the messages following this
               message for more information.

User Action:   Change the statement to specify a valid file
               specification or path name.

ERRATTDEF,     Could not use database file specified by <str>

Explanation:   If you do not issue an explicit DECLARE ALIAS, ATTACH
               or CONNECT statement, SQL uses the database file
               specified by the logical name SQL$DATABASE.  Because
               the logical name SQL$DATABASE is not defined or does
               not refer to a valid database, SQL could not attach to
               a database.  See the messages following this message
               for more information.

User Action:   Explicitly declare a schema before executing any
               statements which require a database, or define the
               logical name SQL$DATABASE to specify the database file
               you wish to use.

ERRCRESCH,     Error creating database filename <str>

Explanation:   There was an error creating the database.

User Action:   Correct the CREATE DATABASE statement and try again.

ERRDET,        An error was detected

Explanation:   This is the exit status for a preprocessor when an
               error was detected.

User Action:   Correct the error in the host language program and



                                 108






               resubmit the job to the preprocessor.

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.

ERRINCPATH,    Error including record at pathname "<str>"

Explanation:   An error was reported trying to include a record from
               the repository.

User Action:   Correct the pathname in the include from repository
               statement.

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.

ERRSYMDEL,     Error symbol deleted

Explanation:   When parsing an SQL statement, the parser encountered
               an error.  The message for that error appeared prior to
               this message.  In an attempt to recover from that error
               SQL deleted the token it found, and generated this
               message to help you understand any additional messages
               that follow.

User Action:   None.  This is an informational message only.

ERRSYMREP,     Error symbol replaced by <str>

Explanation:   When parsing an SQL statement, the parser encountered
               an error.  The message for that error appeared prior to
               this message.  In an attempt to recover from that
               error, SQL replaced the token it found with the
               specified token, and generated this message to help you
               understand any additional messages that follow.





                                 109






User Action:   None.  This is an informational message only.

ERRWRITE,      error writing file

Explanation:   An error occurred during a file write.

User Action:   Examine the secondary message for more information.

ES_ILL_RPT,    repeat count in edit string is not numeric

Explanation:   The user specified an edit string that contained a
               repeat count that was not a number, for example, X(9)
               is legal, but X(a) is not.

User Action:   Specify only numeric values for repeat counts.

EVACLAUNS,     EVALUATING clause ignored

Explanation:   The DECLARE TRANSACTION statement in SQL does not
               support the EVALUATING clause to specify when the
               database system evaluates constraints.  Constraints are
               evaluated as specified in their definitions.

User Action:   Issue the DECLARE TRANSACTION statement without the
               EVALUATING clause.

EXESELSTA,     Attempted to EXECUTE a SELECT statement

Explanation:   You used a prepared SELECT statement in an EXECUTE
               statement.  In dynamic SQL, the only way to process
               prepared SELECT statements is through cursors.

User Action:   Define a cursor based on the statement you tried to
               execute, and use the cursor in OPEN and FETCH
               statements.  Otherwise, use non-SELECT statements only
               in EXECUTE statements.

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.

EXPECTING_NUMERIC, Expecting numeric value in declaration





                                 110






Explanation:   Parsing the data declaration for this variable
               indicated that a numeric value was expected and not
               received.

User Action:   Check the declaration of the variable.

EXPECT_RIGHT_PAREN, Expecting right parentheses in declaration

Explanation:   While parsing the data declaration for this variable, a
               right parentheses was expected but not found.

User Action:   Check the declaration of this variable.

EXPNUMLIT,     Expected a numeric literal

Explanation:   A numeric literal was expected in this context.

User Action:   Correct the syntax.

EXPQUEXPR,     A query expression was expected

Explanation:   SQL expected a query expression.  You entered something
               else.

User Action:   Enter a query expression.

EXP_CDD_NODATA, Exporting a repository with NODATA is not allowed

Explanation:   You used the NODATA option when exporting a repository
               database.

User Action:   You cannot use the NODATA option when exporting data
               dictionaries.  The repository cannot use the resulting
               database.  Use the DATA option and try again.

EXP_CDD_NOEXT, Exporting a repository with NOEXTENSIONS is not allowed

Explanation:   You used the NOEXTENSIONS option when exporting a
               repository database.

User Action:   You cannot use the NOEXTENSIONS option when exporting
               data dictionaries.  The repository cannot use the
               resulting database.  Use the EXTENSIONS option and try
               again.

EXP_CONVERT,   Domain <str> converted from TINYINT to SMALLINT

Explanation:   This domain may not be exported directly when NO
               EXTENSIONS is specified.  The domain (and all columns



                                 111






               defined using this domain) will be of data type
               SMALLINT in any database created from this interchange
               file.

User Action:   If using IMPORT and EXPORT to move data to a much older
               version of Oracle Rdb or to ELN, keep in mind that the
               data types have changed and that some errors may occur
               since only data has been converted, and objects (such
               as constraints) which refer to that data have not.
               Otherwise, Oracle Rdb Engineering would recommend
               restarting the EXPORT specifying WITH EXTENSIONS.

EXP_NOPROFILE, Database Creator <str> is not defined as an user -
               IMPORT may fail

Explanation:   The database creator does not have a profile entry.  It
               is suggested that the database creator be defined.  One
               can do this by specifying the CREATE USER statement.

User Action:   This is a warning that the named user should be
               defined.  It may be advisable to perform a CREATE USER
               for the database creator and then export the database.
               If not, the subsequent IMPORT may fail.

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.

EXTNAMEIGND,   Stored name "<str>" is ignored in a single schema
               database

Explanation:   You specified a STORED NAME clause and this is not a
               multischema database.

User Action:   None needed.  The STORED NAME is ignored.

EXTNAMEXISTS,  Stored name <str> already exists in this database

Explanation:   You attempted to create an object with an stored name
               which is already in use by an object of the same type.

User Action:   Choose a different stored name for the object or omit
               the STORED NAME clause and allow SQL to provide a
               default stored name for you.



                                 112






EXTRADATA,     unexpected data at the end of the .RBR file

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

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

EXTREPONESCH,  Only one database allowed by EXTRACTION and REPLICATION
               transfers

Explanation:   You have specified tables to be moved which come from
               more than one database.

User Action:   Use multiple transfers to move tables from multiple
               databases.

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.

FCNALREXI,     function <str> already exists in this schema or
               database

Explanation:   The specified function or procedure already exists in
               the specified database.  This could be caused by
               another procedure or an external function with the same
               name.  Remember that procedure names are scoped to the
               schema not the module.

User Action:   Check the spelling of the function or procedure name
               and ensure that it is a unique function or procedure in
               the specified database.

FCNNOTDEF,     function <str> is not defined

Explanation:   The specified function or procedure does not exist in
               the specified database.

User Action:   Check the spelling of the function or procedure name
               and ensure that it is the name of a function or
               procedure in the specified database.

FCNNOTEXT,     SHOW PROTECTION and SHOW PRIVILEGES are invalid on SQL
               functions





                                 113






Explanation:   The specified routine is an SQL function.  Because the
               GRANT and REVOKE statements are only allowed on the
               module level, you cannot specify the SHOW PROTECTION or
               SHOW PRIVILEGES statements on a SQL function.

User Action:   Specify the SHOW PROTECTION or SHOW PRIVILEGES
               statements on the stored module.

FETNOTDON,     A fetch has not been done yet for cursor <str>

Explanation:   You named a cursor in a CURRENT OF clause of an UPDATE
               or DELETE statement but you did not issue a FETCH
               statement for that cursor.

User Action:   Issue a FETCH statement for the cursor.

FIELD_EXISTS,  Domain <str> already exists in this database or schema

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

User Action:   Choose a different name.

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.

FINNOSES,      FINISH is not compatible with sessions

Explanation:   FINISH is not only deprecated, but cannot be used with
               sessions since the semantics aren't compatible.

User Action:   Use DISCONNECT DEFAULT.

FKCONSNOTCB,   Computed column may not reference a foreign key





                                 114






Explanation:   You specified a foreign key constraint for a computed
               column, which does not support this constraint.

User Action:   Remove the foreign key constraint from this definition.

FLDAMBIG,      Column <str> is not unique in tables in the FROM clause

Explanation:   The specified column exists in more than one of the
               tables specified in the FROM clause.

User Action:   Qualify the column name in the select list with the
               table name or an alias.

FLDASREC,      Param <str> included repository field as record
               definition

Explanation:   SQL module compiler allows a repository field in a
               record definition for a module parameter declaration.
               Processing continues without any errors.

User Action:   Include the correct repository record definition for
               the module parameter definition if that supports the
               clarity of the code.

FLDNOTBCK,     Column <str>.<str> defined in terms of missing domain
               <str>

Explanation:   The base field for a local field is not defined.  The
               database cannot be exported if any columns refer to
               non-existant domains.

User Action:   This is caused by an inconsistency in the database.
               Try to recover the missing global field.

FLDNOTCRS,     Column <str> was not found in the tables in current
               scope

Explanation:   The specified column does not exist in the tables
               specified in the current scope.

User Action:   Check the select expression:  you may have mistyped the
               column name or specified the wrong table name or alias
               to qualify the column name.

FLDNOTDEF,     Column <str> is not defined in table <str>

Explanation:   The specified column does not exist in the table
               specified.





                                 115






User Action:   Check the select expression:  you may have mistyped the
               column name or specified the wrong table name or alias
               to qualify the column name.

FLDNOTINREL,   <str> is not a column in table, <str>

Explanation:   The column you specified is not part of the named
               table.

User Action:   Check the table definition for the correct column name
               or specify another table.

FLUINPBUF,     Indirect command file buffer flushed for Control-C

Explanation:   You typed Control-C while executing an indirect command
               file.

User Action:   None.

FORCOLNMASS,   Column <str> in table <str> does not match assumed
               <str> data type

Explanation:   You implicitly declared the named column with numeric,
               character or date data type when using it in a forward
               reference.  When the named table was eventually
               created, the actual column declaration did not match
               the implicit one.

User Action:   Change the forward declaration or the column
               declaration so that the two have the same basic data
               type.

FORCOLNMDECL,  Column <str> in table <str> does not match <str> of
               forward reference

Explanation:   You implicitly declared the named column when using it
               in a forward reference.  When the named table was
               eventually created, the actual column declaration did
               not match the implicit one.

User Action:   Change the forward declaration or the column
               declaration so that the two match in data type, length
               and scale.

FORCOLNODECL,  Column <str> in forward reference of table <str> not
               declared

Explanation:   You implicitly declared the named column when using it
               in a forward reference.  When the named table was



                                 116






               eventually created, the column was not declared.

User Action:   Change the forward declaration or the actual table
               declaration so that the table contains all of the
               columns found in the forward declaration.

FORCONSTNOUPD, Variable "<str>" is a FOR loop counter - assignment not
               allowed

Explanation:   The named variable was used by the FOR counted loop
               which makes it a CONSTANT for the duration of the loop
               body.  This variable is the target of a SET,
               INSERT...RETURNING, SELECT...INTO, UPDATE...RETURNING,
               or GET GIAGNOSTICS statement or CALL output parameter.

User Action:   Check that the correct variable is used in this
               statement.  If you need to update the loop counter,
               replace the FOR IN loop with a WHILE loop.

FORFCHVARRO,   FOR statement variable "<str>" is read only

Explanation:   (a) If the variable is on a FOR cursor loop then this
               variable and the select list value names are considered
               constant (i.e.  read only) within the FOR body.  (b) If
               the variable is on a FOR counted loop then this
               variable needs to be updated by the FOR loop but can
               not be changed because it is declared as CONSTANT.

User Action:   (a) Use the UPDATE ...  WHERE CURRENT OF statement to
               update rows fetched by the FOR cursor loop.  (b) Change
               the variable declaration to be UPDATABLE or use another
               variable name for the loop

FORPASLEN,     Host variable <str> is an unsupported passed-length
               variable

Explanation:   The host variable declaration uses the FORTRAN
               passed-length (*) feature which is not supported.

User Action:   Either change the declaration so that only supported
               attributes are used, or move the data to another
               variable which uses only supported attributes.

FORTABNODECL,  Forward referenced table <str> not declared

Explanation:   You used the named table in a forward reference.  This
               table was never created.

User Action:   Change the CREATE DATABASE statement to include the



                                 117






               definition of all forward declared tables.

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

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

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.

FUNCNOLABEL,   Label of function was not declared

Explanation:   You attempted to reference an undeclared label.

User Action:   Reference a label which has been declared.

FUNCNORET,     A function was specified without a RETURNS clause

Explanation:   If a function is specified, you must also specify a
               RETURNS clause.

User Action:   Reenter the function using a RETURNS clause.

FUN_ARGCOUNT,  Function <str> expected <num> parameter(s), was passed
               <num>

Explanation:   The function was not passed as many parameters as
               expected.

User Action:   Specify the correct number of parameters in either the
               function definition or the invocation.

FUN_VAR,       Host variable <str> is a function which is illegal in
               SQL statements.

Explanation:   The named variable is defined as a C function.
               Functions references are not supported in SQL
               statements.





                                 118






User Action:   Use a different variable.

GARBLED,       interchange file is corrupt

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

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

GETCRESEG,     Attempt to get from a created list

Explanation:   You attempted to do a SEGSTR.GET using a handle
               returned by a SEGSTR.CREATE statement.  You can only do
               SEGSTR.PUTs using the handle returned by create.

User Action:   Specify the correct handle

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.

GFLOAT,        <str> does not support G_FLOAT

Explanation:   /G_FLOAT was specified for a language such as COBOL
               which does not support the G_FLOAT data type.

User Action:   Unless you are taking the G_FLOAT number and passing it
               to a language which understands G floating numbers, you
               probably want to reprecompile without the /G_FLOAT
               qualifier.  If you use it from this language, the
               compiled code will think it is a different number than
               the database system did.

GNAT_LINKOPTS, Pragma Linker_Options ("<str>");

Explanation:   Used in interface file generation in precompiler

User Action:   None.





                                 119






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.

GRELEASTNODTP, GREATEST or LEAST expression must have a data type

Explanation:   The GREATEST and LEAST expression does not have a data
               type because all of the results are NULL or of an
               unknown type.

User Action:   Assign a data type to at least one result.

HEXSTREVE,     A hexadecimal string must have an even number of digits

Explanation:   A hexadecimal string must have an even number of
               digits.  This is because it takes two hexadecimal
               digits to represent each ASCII character.

User Action:   Enter a hexadecimal number with an even number of
               digits.

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.

HI_ORD_LOS,    Increasing the scale of <str> <str> may result in the
               loss of high order digits

Explanation:   Changing the data type and/or increasing the scale of a
               column may result in the loss of significant digits of
               the data already stored in that column.

User Action:   None.  This is a warning message only.

HNDL_INIT,     Command line switch conflicts with database handle
               declaration; handle will be initialized

Explanation:   The database handle declaration is either GLOBAL or
               LOCAL (both of which are always initialized) and either
               NOINITIALIZE_HANDLES or EXTERN_ALIAS was specified on
               the command line.  For this declaration, the command



                                 120






               line switch will be ignored and the handle will be
               initialized.

User Action:   Change the database handle declaration to EXTERNAL.

HOLDATTOP,     The WITH HOLD clause must appear in the outermost
               compound

Explanation:   You have used the WITH HOLD clause in a compound
               statement that is nested within one or more other
               compound statements.

User Action:   Move the WITH HOLD clause to the outermost compound
               statement in the procedure.

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





                                 121






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.



                                 122






HOTNOONLINE,   attempt to access standby database opened for exclusive
               access

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

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

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

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

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

HOTOFFLINE,    standby database opened for exclusive access

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

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



                                 123






               transactions

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

User Action:   All read/write transaction activity must be stopped
               prior to starting database replication on the standby
               database.

HOTSEQBCK,     cannot find AIJ journal required to start replication

Explanation:   Database replication using the Hot Standby feature was
               attempted to be started, but the AIJ journal required
               by the standby database could not be found on the
               master database.  This typically occurs when the AIJ
               Backup Server ("ABS") inadvertantly backs up the AIJ
               journal on the master database following an AIJ
               switch-over operation.

User Action:   The journal specified in the Log Catchup Server ("LCS")
               output file must be manually rolled forward on the
               standby database.  Alternately, the master database
               must be backed up and restored as the standby database.

HOTSTOPWAIT,   stopping database replication, please wait

Explanation:   This message informs the user that database replication
               is being stopped and to wait for shutdown to complete.
               Replication shutdown times vary based on system and
               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.



                                 124






               This could happen if you copied or renamed the master
               database root file, or if the file was created using a
               concealed logical device name and that logical name is
               no longer defined.

User Action:   Ensure that the specified standby database is correct.
               If so, ensure that replication on the standby database
               has been fully terminated; replication termination
               occassionally has long-duration shutdown processing to
               be performed.  If the master database rootfile had been
               moved, rename or copy the root file back to its
               original name or location, or redefine the necessary
               concealed logical device name in the system logical
               name table.

HVNOTDECL,     Host variable <str> was not declared

Explanation:   Every host variable that is used in an SQL statement in
               a program must been declared in the host language.

User Action:   Declare the specified variable using a supported
               declaration.

HV_NOT_IN,     Host variable, <str>, not within scope of BEGIN DECLARE
               and END DECLARE section

Explanation:   Your program referred to a variable that was declared
               outside of the BEGIN DECLARE and END DECLARE
               statements.

User Action:   Either move the desired host variable declaration to be
               within this section or remove the BEGIN DECLARE and END
               DECLARE statement.  You can also ignore this warning
               message.  BEGIN DECLARE and END DECLARE are only for
               standard complicance.

IDMISSING,     an alias or a filename is required to create a database

Explanation:   The user specified an IMPORT or a CREATE DATABASE
               statement without specifying an authorization ID or a
               filename.  One of is required.

User Action:   Specify the missing parameter and try the operation
               again.

IGNCTXBLK,     Context structure is being ignored

Explanation:   You are passing a context structure to a platform that
               does not support this construct.  The context structure



                                 125






               will be ignored on this platform.

User Action:   Your application may depend on some external control
               agent (such as DECdtm) and may not function properly
               without this external agent, therefore, your
               application may have to be written to deal with the
               lack of this agent on the target platform.

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.

ILLBEGIN,      file <str> is corrupt or not an Oracle Rdb interchange
               file

Explanation:   SQL IMPORT can recreate databases only from the Oracle
               Rdb interchange file.  This file is not a Oracle Rdb
               interchange file.

User Action:   Try the operation again with the correct file name.

ILLCHAR,       Illegal character detected

Explanation:   An illegal character has been detected.

User Action:   Use only valid characters.

ILLCOMPREC,    RECORD or structure may not be compared

Explanation:   You included the name of a RECORD parameter or
               structure variable in a comparison.  This is not
               allowed.

User Action:   Compare individual fields of records or structures with
               other values.

ILLDATLEN,     An invalid SQLLEN(<num>) was found for a date field in
               the SQLDA





                                 126






Explanation:   You passed in a date column in a SQLDA with a SQLLEN
               that was not 8.

User Action:   Set the SQLLEN to 8 for date columns in the SQLVAR.

ILLDROPCONS,   DROP ALL CONSTRAINTS is only valid for ALTER DOMAIN

Explanation:   The DROP ALL CONSTRAINTS clause only works for the
               ALTER DOMAIN statement and not the ALTER TABLE
               statement.

User Action:   DROP the individual constraints by name.

ILLEXEIMM,     Illegal EXECUTE IMMEDIATE statement type

Explanation:   You tried to issue a statement that is not allowed in
               an EXECUTE IMMEDIATE statement (SELECT, DECLARE, OPEN,
               FETCH, CLOSE, PREPARE, DESCRIBE, EXECUTE, INCLUDE, or
               WHENEVER).

User Action:   Use PREPARE and a full EXECUTE statement for these
               statements.

ILLFLOLEN,     An invalid SQLLEN(<num>) was found for a FLOAT field in
               the SQLDA

Explanation:   You passed in an SQLDA with a SQLTYPE FLOAT SQLLEN that
               was invalid.  Only 4, 8, and 16 are legal
               floating-point lengths.

User Action:   Set the SQLLEN to 4, 8, or 16, depending on the length
               of the floating-point variable passed.

ILLFRASECPRE,  Fractional seconds precision may not be specified in
               this context

Explanation:   You entered fractional seconds precision in a context
               in which it was not allowed.  TIME and TIMESTAMP
               literals may not include explicit fractional seconds
               precision; it is implied from the time string or
               timestamp string itself.

User Action:   Remove the fractional seconds precision.

ILLFROM,       Repository definitions may not be included using FROM
               within CREATE DATABASE

Explanation:   You cannot use the FROM PATHNAME clause within a CREATE
               DATABASE statement.



                                 127






User Action:   Create the database first, then include the
               definitions.

ILLHEXNUM,     Illegal hexadecimal number.

Explanation:   The format of a hexadecimal number is X'ffff', where
               ffff may be up to 16 hexadecimal digits.  A hexadecimal
               digit is a numeric digit (0 to 9) or an A, B, C, D, E,
               or F.  The letters may be upper or lower case.  There
               must be an even number of digits.

User Action:   Enter a proper hexadecimal number.  Make sure that the
               trailing apostrophe is included.

ILLINTLEN,     An invalid SQLLEN(<num>) was found for a integer column
               in the SQLDA

Explanation:   You passed in an integer column in a SQLDA with a
               SQLLEN that was invalid.  For SQLTYPE of INTEGER,
               SQLLEN must be 4.  For SQLTYPE of SMALLINT, SQLLEN must
               be 2.

User Action:   Set the SQLLEN to 2 for SMALLINT, or 4 for INTEGER.

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.

ILLPICSTR,     illegal character <str> in edit string

Explanation:   An edit string contained the illegal character
               specified in the message.

User Action:   Change the edit string to not have that character.

ILLSTRCONT,    Illegal string continuation

Explanation:   Your program has illegal string continuation.

User Action:   In COBOL, to continue a string you must do three
               things:  1) not end the string with a quote on the
               initial line; 2) insert a continuation character (-) in
               the first column of the next line; and, 3) start the
               continued string with a quote as the first nonblank
               character after the continuation character (this quote
               is ignored).



                                 128






ILLSUBQRY,     Scalar subqueries are illegal in this context

Explanation:   Subqueries are illegal in domain constraint definitions
               and within the FILTER clause for an aggregate.

User Action:   Do not use subqueries in this context.  If necessary
               call a SQL stored function which can include the
               subquery.

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.

IMPLNOTDBI,    Feature supported only in the Distributed Option for
               Rdb

Explanation:   An attempt was made to create or alter an object, such
               as a link or a partitioned view, in a non-Distributed
               Option for Rdb database which does not support this
               type.

User Action:   Check which is the default database, and whether the
               database in question has been accessed with '/TYPE =
               INTEGRATOR'

IMPL_DIM,      Host variable <str> is defined with an implicit
               dimension.

Explanation:   The named variable is defined using the C feature of
               determining the dimension of an array from its
               initialization.  Such variables are not legal in SQL
               statements.

User Action:   Define the array variable using an explicitly-sized
               array.

IMP_CACHENOTDRO, Cache <str> not dropped - check spelling of the cache
               name

Explanation:   IMPORT could not process a DROP CACHE clause because
               the named cache was not defined in the database or
               schema.

User Action:   Check that you have spelled the cache name correctly.



                                 129






IMP_CACHE_AREA, Importing cache:  <str>

Explanation:   The named cache area is being imported from the
               interchange file.

User Action:   None

IMP_CACHE_CONFLICT, CREATE and DROP CACHE <str> specified

Explanation:   You have specified a CREATE and DROP CACHE clause using
               the same cache name.

User Action:   Specify either the CREATE CACHE or a DROP CACHE clause.

IMP_CACHE_DEL, Definition of cache <str> deleted

Explanation:   You have specified that the cache be dropped on IMPORT.

User Action:   None

IMP_CACHE_OVR, Definition of cache <str> overridden

Explanation:   You have specified a new definition of cache on IMPORT
               which supercedes the definition in the interchange
               file.

User Action:   None

IMP_CACHE_TWICE, CREATE CACHE <str> specified twice

Explanation:   You have specified a CREATE CACHE clause twice using
               the same name.

User Action:   Specify a cache name only once.

IMP_CDD_NODATA, Importing a repository with NODATA is not allowed

Explanation:   You used the NODATA option when importing a repository
               database.

User Action:   You cannot use the NODATA option when importing data
               dictionaries.  The repository cannot use the resulting
               database.  Use the DATA option and try again.

IMP_DDLWARN,   warnings reported while importing or creating object
               <str>

Explanation:   Warnings were issued during the import of the named
               object.  This may indicate that the object is valid but



                                 130






               may not be optimal.  For instance, the new definition
               on the IMPORT command line might duplicate an existing
               index definition, or specify a node size that would not
               fit in the associated row cache.

User Action:   Check the messages which follow for the warning
               information and take appropriate action if necessary.

IMP_IDXNOTCRE, index <str> not created - check spelling of the table
               name

Explanation:   IMPORT could not process a CREATE INDEX clause because
               the named table was not defined in the database or
               schema.

User Action:   Check that you spelled the table name correctly.

IMP_IDXNOTDRO, index <str> not dropped - check spelling of the index
               name

Explanation:   IMPORT could not process a DROP INDEX clause because
               the named index was not defined in the database or
               schema.

User Action:   Check that you spelled the index name correctly.

IMP_IDX_CONFLICT, DEFINE and DELETE INDEX <str> specified

Explanation:   The user specified a DEFINE and DELETE INDEX using the
               same name.

User Action:   Specify a either a DEFINE or a DELETE INDEX.

IMP_IDX_TWICE, DEFINE INDEX <str> specified twice

Explanation:   The user specified a DEFINE INDEX twice using the same
               name.

User Action:   Specify a INDEX name only once.

IMP_STANOTDRO, storage area <str> not dropped - check spelling of the
               storage area name

Explanation:   IMPORT could not process a DROP STORAGE AREA clause
               because the named storage area was not defined in the
               database or schema.

User Action:   Check that you spelled the storage area name correctly.





                                 131






IMP_STAREADONLY, Storage area was READ ONLY, now set to READ WRITE

Explanation:   The interchange file specified that this storage area
               was READ ONLY.  This has not been reflected in the new
               database.

User Action:   Use the syntax available in the ALTER STORAGE AREA
               statement to change the access mode of this area after
               the IMPORT operation has completed.

IMP_STMNOTCRE, storage map <str> not created - check spelling of the
               table name

Explanation:   IMPORT could not process a CREATE STORAGE MAP clause
               because the named table was not defined in the
               database.

User Action:   Check that you spelled the table name correctly.

IMP_STMNOTDRO, storage map <str> not dropped - check spelling of the
               storage map name

Explanation:   IMPORT could not process a DROP STORAGE MAP clause
               because the named storage map was not defined in the
               database or schema.

User Action:   Check that you spelled the storage map name correctly.

IMP_STO_CONFLICT, DEFINE and DELETE STORAGE AREA <str> specified

Explanation:   The user specified a DEFINE and DELETE STORAGE AREA
               using the same name.

User Action:   Specify a either a DEFINE or a DELETE STORAGE AREA.

IMP_STO_MAP_CONFLICT, DEFINE and DELETE STORAGE MAP <str> specified

Explanation:   The user specified a DEFINE and DELETE STORAGE MAP
               using the same name.

User Action:   Specify a either a DEFINE or a DELETE STORAGE AREA.

IMP_STO_MAP_TWICE, DEFINE STORAGE MAP <str> specified twice

Explanation:   The user specified a DEFINE STORAGE MAP twice using the
               same name.

User Action:   Specify a STORAGE MAP name only once.





                                 132






IMP_STO_TWICE, DEFINE STORAGE AREA <str> specified twice

Explanation:   The user specified a DEFINE STORAGE AREA twice using
               the same name.

User Action:   Specify a STORAGE AREA name only once.

IMP_TRA_BEG,   Starting <str> definition <str>

Explanation:   Importing Relation/Index/Constraint info message.

User Action:   None.

IMP_TRA_END,   Completed <str>.  DIO = <num>, CPU = <str>, FAULTS =
               <num>

Explanation:   Text for Import Tracing.

User Action:   None.

INCCSASS,      Incompatible character set assignment between <str> and
               <str>

Explanation:   An assignment between two different character sets in
               not allowed because of incompatibilities of the
               character sets.

User Action:   Use character fields with the same or compatible
               character sets.

INCCSCMP,      Incompatible character set comparision between <str>
               and <str>

Explanation:   Comparision between two different character sets in not
               allowed because of incompatibilities of the character
               sets.

User Action:   Use character fields with the same or compatible
               character sets.

INCCSCON,      Incompatible character set concatenation between <str>
               and <str>

Explanation:   Concatenation between two different character sets in
               not allowed because of incompatibilities of the
               character sets.

User Action:   Use character fields with the same or compatible
               character sets.



                                 133






INCNOTREC,     <str> is not a repository record definition

Explanation:   The repository path name in an INCLUDE FROM DICTIONARY
               statement must specify a repository record definition.
               The repository object specified is not a record
               definition.

User Action:   Change the path name to the path name for a record
               definition, or remove the INCLUDE statement.

INC_DAT_TYP,   Altering <str> <str> to an incompatible data type may
               cause data loss

Explanation:   Altering a column to a data type that is incompatible
               with the old data type might cause data already stored
               in that column to appear lost.

User Action:   None.  This is a warning message only.

INDEXTS,       There is another index named, <str>, in this database
               or schema

Explanation:   This message is printed during an IMPORT operation if
               the backup file contains multiple definitions of an
               index.  Duplicate definitions may indicate corruption
               of the interchange, or improper operation during the
               EXPORT operation.

User Action:   Contact your Oracle support representataive.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.  Subsequent definitions of the index should be
               ignored during the IMPORT operation; your database may
               not be currupt.

INDFIXINT,     Indicator variable <str> is not an unscaled fixed
               numeric

Explanation:   You must declare indicator variables as the host
               language equivalent of an unscaled integer data type.

User Action:   Declare the indicator variable as an unscaled integer
               host variable.

INDIC_OVFLOW,  Indicator parameter is too small to hold source string
               size

Explanation:   The indicator parameter holds the size of the source
               string if the target is too small.  The storage unit
               chosen for the indicator was not large enough to hold



                                 134






               the size of the requested string.

User Action:   Evaluate your use of indicator parameters.

INDNOTDEF,     Index <str> is not defined in this database or schema

Explanation:   The specified index does not exist in the current
               database or schema.

User Action:   Declare the proper schema.  Spell the index name
               correctly.  You may have specified an expression where
               an index name was expected.

INDSHOINT,     Indicator variable <str> is not a SMALLINT

Explanation:   Indicator variables in the dynamic interface should be
               declared as the host language equivalent a SMALLINT
               data type.

User Action:   In COBOL, declare indicator variables as PIC S9(4)
               COMP.  In FORTRAN, declare indicator variables as
               INTEGER*2.  In PL/I, declare indicator variables as
               FIXED(15) BINARY.

IND_EXISTS,    Index <str> already exists in this database or schema

Explanation:   You attempted to create an index with the name of an
               existing index

User Action:   In the precompiler and module language, this is just a
               warning.  If the index exists when you execute the
               statement, you will get a fatal error.  If you expect
               to drop the index before you execute this statement,
               then you do not need to make any changes.  In
               interactive, dynamic and runtime for precompiled and
               module language programs, this is a fatal error.  You
               must choose a different name.

INFODET,       An informational was detected

Explanation:   This is the exit status for a preprocessor when an
               informational was detected.

User Action:   Correct the error in the host language program and
               resubmit the job to the preprocessor or ignore the
               informational.

INPUTERROR,    Error reading input file





                                 135






Explanation:   There was an error reading from the module language or
               precompiler source file.  SQL will display a secondary
               status message.

User Action:   Act upon the secondary status message.  See the system
               manager, if necessary.

INSCOLALR,     Column <str> appears more than once in the INSERT
               column list

Explanation:   You specified the same column name more than once in an
               INSERT statement.  Columns can only appear once.

User Action:   Remove one occurrence of all columns which appear more
               than once.

INSCURDYN,     cursor <str> for positioned insert statement is dynamic

Explanation:   An embedded positioned insert statement refers to an
               insert cursor that is dynamic.

User Action:   You must execute immediate the positioned insert
               statement or make the insert cursor static.

INSEXPVAL,     Table "<str>" has <num> updatable column(s) but was
               passed <num> value(s)

Explanation:   An INSERT statement without a column list was passed
               the wrong number of values compared to the updatable
               columns of the table.

User Action:   Pass the correct number of values for this table.
               COMPUTED BY, AUTOMATIC AS and IDENTITY columns are
               considered read-only and should not be supplied values.

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



                                 136






               parameters may be necessary to reduce physical memory
               consumption.

INSVALSPEC,    insert value is not a value specification or NULL

Explanation:   You used a value expression in the VALUES clause of an
               INSERT statement which was not a value specification or
               NULL.  The ANSI standard does not support this.

User Action:   If ANSI standard behavior is important for your program
               then replace this value expression with one which fits
               the rules for value specification or NULL.

INS_INTO_RO,   List cursor <str> cannot insert into READ ONLY table
               cursor <str>

Explanation:   The list cursor named is an INSERT ONLY cursor while
               the table cursor that it references is a READ ONLY
               cursor.

User Action:   The table cursor that the list cursor is based on must
               either be an INSERT ONLY or UPDATE cursor.

INS_MUST_INS,  List cursor <str> cannot fetch from INSERT ONLY table
               cursor <str>

Explanation:   The list cursor named is a READ ONLY cursor, but the
               table cursor is an INSERT CURSOR which won't allow
               FETCHes.

User Action:   The list cursor must be an INSERT ONLY list cursor or
               the table cursor must be an INSERT or UPDATE cursor.

INTERVAL_USED, Domain was an INTERVAL data type

Explanation:   This message is used as a subcode to SQL$_DOMNOTBCK.
               It indicates that the offending domain was a new
               subtype of DATE.  Specifically, INTERVAL data is not
               stored in the previous (ADT) format and cannot be
               interpreted in the same fashion.

User Action:   The database cannot be exported WITH NO EXTENSIONS
               until this domain is removed completely.

INTIGNSYS,     Interval option ignored for system relation area

Explanation:   The storage area that contain the system relations must
               have UNIFORM page formats.  Either through the use of
               the defaults, or by directly specifing the INTERVAL



                                 137






               option, SQL has been told to apply the INTERVAL option
               for the area containing the system relations.  SQL is
               ignoring that option.

User Action:   None.  This is an informational message.  The user
               might want to change the command if it originated in a
               command file.  This may avoid confusion later.

INTNOTQUAL,    Interval expression not qualified

Explanation:   An interval value expression was produced by the
               subtraction of two datetime value expressions, but no
               interval qualifier was specified.

User Action:   Specify a valid interval qualifier for the expression.

INTNOTSYS,     Interval option not valid for system relation area

Explanation:   The storage area for RDB$SYSTEM was defined to have the
               interval option.  This is not allowed for RDB$SYSTEM.

User Action:   Remove the interval option from the command and try
               again.

INTONOTALW,    INTO clause is not allowed in this context

Explanation:   The INTO clause may only be used for a single table or
               view.  It may not be used with a wildcard table or view
               specifiction.

User Action:   Re-enter the CREATE TRANSFER statement without
               specifying an INTO clause or name the tables and views
               individually, each with its own INTO clause.

INTONOTQUAL,   The table name specified in the INTO clause must not be
               qualified

Explanation:   The user entered INTO xxx.yyy for an extraction rollup
               transfer.

User Action:   Re-enter the statement without the 'xxx.'

INTQUALINV,    Interval qualifier not valid for this expression

Explanation:   An interval qualifier was specified for a value
               expression where such a qualifier is illegal.  An
               interval qualifier may only be specified for an
               interval expression yielded by subtracting two datetime
               value expressions.



                                 138






User Action:   Remove the interval qualifier.

INTVALLOW,     Interval value must be at least 256

Explanation:   The specified interval value for space management pages
               is too small.  The minimum value is 256 pages.

User Action:   Change the interval value for space management pages on
               the CREATE DATABASE statement to a legal value.

INTVALOVR,     Interval value overwritten to 256 pages

Explanation:   The specified interval value for space management pages
               is too small.  The minimum value is 256 pages.  SQL
               overwrote the specified value with 256.

User Action:   Change the interval value for space management pages on
               the CREATE DATABASE statement to a legal value.

INVACCTYP,     A function was specified whose parameter access mode is
               not IN

Explanation:   If a function is specified, you must specify the
               parameter access mode IN.

User Action:   Reenter the function with parameter access mode IN.

INVACL,        Invalid Access Control List entry

Explanation:   The syntax of the access control list entry string is
               not valid.

User Action:   Correct the syntax of the access control list entry.

INVARRSUB,     Host variable <str> defined with illegal use of
               subscripts

Explanation:   The named host variable uses subscripts in a way that
               is illegal for the C compiler.  Most likely the use is
               through a typedef that is defined as an array.

User Action:   Use a different variable or redefine the type structure
               of the program.

INVATTVAL,     Invalid attribute value.  "<str>" attribute has an
               invalid value

Explanation:   You specified an attribute with an invalid value.





                                 139






User Action:   Change the offending value and try the statement again.

INVBLRID,      BLR identification is invalid

Explanation:   You tried to specify that a BLR ID that is either not
               exactly 32 hexadecimal characters long or contains
               characters other than '0' through '9' or 'A' through
               'F'.

User Action:   Only specify valid hexadecimal characters and ensure
               that the string size is exactly 32 hexadecimal
               characters long.

INVBUFRCNT,    Invalid APF or ABW negative buffer count specified

Explanation:   An invalid APF/ABW buffer parameter of zero (0) or less
               was specified.

User Action:   Specify an APF/ABW buffer parameter greater than zero
               (0).

INVCHAINP,     Invalid character in input

Explanation:   The input contains an illegal or unrecognizable
               character.

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

INVCHANUMSTR,  Invalid character in numeric string

Explanation:   The string appears to be a numeric literal.  However,
               it contains one or more illegal characters.

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

INVCOLLST,     The degree of the column list does not match the degree
               of the result table

Explanation:   The list of column names you specified in a view
               definition or derived table contain a different number
               of names than the number of value expressions in the
               select list of the definition's SELECT expression.
               There must be a strict one-to-one correspondence
               between the two lists.

User Action:   Specify the same number of column names in the column
               list as value expressions in the select list.

INVCOLSPC,     Column names must be qualified by table names.



                                 140






Explanation:   You must qualify the column name in a COMMENT ON COLUMN
               statement with a table name.

User Action:   Specify the column name as <table-name>.<column-name>.

INVCOMLIN,     Invalid command line

Explanation:   You specified extra parameters or invalid command line
               syntax in a module language compiler command line.

User Action:   Specify only supported command line options.

INVCONS,       unable to import constraint <str>

Explanation:   Internal error - the named constraint will not appear
               in the recreated database.

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.  In the meantime, you can redefine this
               constraint explicitly.

INVCORRSL,     Invalid select list in a UNION query - repeated column
               <str>

Explanation:   There are two columns with the same name in one of the
               select lists in the UNION CORRESPONDING or UNION
               NATURAL query expression.

User Action:   Either remove one of the columns with the same name
               from the select list, or match columns to be combined
               in the UNION by position rather than name.

INVCSET,       character set in declaration for variable <str> doesn't
               exist

Explanation:   You specified a character set that does not exist.  For
               lack of a better choice, the module default character
               set is assumed.

User Action:   Specify a character set that exists.

INVDATCON,     Invalid conversion between DATE column <str> and host
               variable <str>

Explanation:   Only binary dates can be compared or assigned to or
               from DATE columns.

User Action:   Use a date declaration for the host variable to be used



                                 141






               with the date field:  in COBOL, use S9(11)V9(7) COMP;
               in PL/I, use CHAR(8) or BYTE_FIELD(8); in FORTRAN, use
               CHARACTER*8.

INVDBK,        <num>:<num>:<num> is not a valid dbkey

Explanation:   An attempt was made to fetch a record by its database
               key value, but the specified page is a SPAM, ABM, or
               AIP.  Alternatively, the specified dbkey refers to a
               non-existing storage area or a system record.

User Action:   Correct the condition, and try again.

INVDBKREF,     Invalid DBKEY reference

Explanation:   You can refer to dbkeys only on the right hand side of
               an assignment or in an equals Boolean.

User Action:   Remove the invalid dbkey reference.

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.

INVDECLSTMT,   Invalid declaration statement in module <str>

Explanation:   The module named in the error message contains a
               declaration statement that is invalid for a stored
               module.

User Action:   Use only the subset of declarations valid for stored
               modules.

INVDEFACC,     A DEFAULT clause for parameters is only valid with the
               IN parameter access mode

Explanation:   If a DEFAULT clause is specified, you must specify the
               parameter access mode IN.

User Action:   Reenter the routine with parameter access mode IN.



                                 142






INVESCVAL,     Invalid escape clause value

Explanation:   The value specified in the escape clause of a LIKE
               predicate must be a single character string value.

User Action:   Specify a valid value expression in the escape clause

INVEXTCALL,    External procedure "<str>" must be CALLed within a
               compound statement

Explanation:   The referenced procedure is external and therefore may
               not be CALLed within a simple statement.

User Action:   Use a compound statement to CALL the external
               procedure.

INVFLD,        unable to import field <str>

Explanation:   Internal error - the named field will not appear in the
               recreated database.

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

INVFLT,        Encountered invalid floating point value

Explanation:   The floating point value cannot be represented with the
               specified floating point type.

User Action:   Change the field type to accomodate the floating point
               value or do not use the offending value.

INVFUNREF,     Invalid aggregate function reference

Explanation:   You cannot include in the WHERE clause (or in any
               subqueries of the WHERE clause) aggregate functions
               that use columns of tables in the FROM clause as their
               argument.

User Action:   Change your select expression to eliminate aggregate
               functions with this type of argument.

INVGBCOL,      GROUP BY anything but a column is illegal

Explanation:   You have tried to specify something other than a column
               reference in a GROUP BY list.

User Action:   Specify only columns in the GROUP BY list.



                                 143






INVGRPROFILE,  unable to import granted profile for grantee <str>

Explanation:   Internal error:  the named granted profile has been
               lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

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.

INVHVDECL,     Host variable <str> was invalidly declared.

Explanation:   Every host variable that is used in an SQL statement in
               a program must be declared in the host language using
               the supported subset of declaration syntax for the
               language.  Not using the supported subset causes this
               error.  Another way this message can be generated is to
               use an indicator variable that is not a signed word
               (for example, in COBOL:  PIC S9(4) COMP).

User Action:   Use host variable declaration syntax for this variable
               that is supported by SQL.

INVIEWATTR,    the clause "<str>" is not a valid attribute for view
               "<str>"

Explanation:   You tried to alter a view using the ALTER TABLE syntax,
               but the clause is not supported by ALTER VIEW.

User Action:   Correct the syntax.

INVINDEX,      unable to import index <str>

Explanation:   Internal error - the named index will not appear in the
               recreated database.

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.  In the meantime, you can recreate this index
               explicitly.

INVINTMOD,     Size modifier for INTEGER parameters must be 4 or 8

Explanation:   You specified a size other than 4 or 8 bytes for the
               size of a modifier on a Module Language INTEGER



                                 144






               parameter.

User Action:   Specify either 4 or 8 bytes.

INVINTOTAR,    target for an INTO clause must be a variable or
               parameter

Explanation:   The INTO clause of a FETCH, SELECT, INSERT or UPDATE
               statement must be an updatable variable or parameter.

User Action:   Correct the statement to use the correct target for the
               assignment.  A common error is to omit the leading :
               from a parameter, as such it may appear to SQL that
               this is a reference to a column with the same name.

INVINTQUAL,    Invalid interval qualifier

Explanation:   An interval value expresssion yielded an interval that
               could not be presented by the interval qualifier
               specified in the value expression.

User Action:   Examine the data types of the expression and the
               interval qualifier to determine where the discrepency
               lies.  For example, the subtraction of two time value
               expressions cannot be qualified by YEAR TO MONTH.

INVLENHV,      Only a numeric variable may be used receive the length

Explanation:   You used a variable which was not numeric.  This is not
               supported.

User Action:   Either omit the argument to receive the length, or use
               a numeric

INVMAPVAL,     Invalid Mapping Value Specified:  "<str>"

Explanation:   The MAPPING VALUES limits specified has an out-of-range
               number.  Each limit specified must be in the range of
               the smallest negative to largest positive 32 bit
               integer.

User Action:   Specify a number for each limit of the range which is
               in range -1073741824 through 1073741823

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



                                 145






               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.

INVMODULE,     unable to import module <str>

Explanation:   Internal error:  the named module has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

INVNODESIZE,   Invalid node size parameter specified

Explanation:   You specified an invalid node size.  It was either less
               than or equal to zero or greater than 32768.

User Action:   Review the command and specify a node size within the
               above range (but big enough to meet the implementation
               requirements).

INVNUMLIT,     <str> is an invalid numeric literal

Explanation:   An invalid numeric literal was specified which could
               not be converted to a numeric value.  This is usually
               because it is to big to fit into any VMS data type
               without losing significance.

User Action:   Change the literal to be a valid numeric literal.

INVNUMSTRPRE,  Invalid numeric string precision (<num>), maximum
               precision is (<num>)

Explanation:   You specified a precision for a NUMERIC, UNSIGNED
               NUMERIC, or DECIMAL field that exceeded the maximum.

User Action:   Specify a precision that is less than the maximum.

INVOBJFIL,     Invalid object file <str> specified

Explanation:   SQL uses the same directory specification and file name
               for any files it creates (such as the language files)
               as that specified in the /OBJECT qualifier on the
               command line.  You specified a nonexistent or invalid
               file specification for the /OBJECT qualifier.





                                 146






User Action:   Use a valid object file specification with the /OBJECT
               qualifier.

INVOKE_ERR,    Cannot invoke image <str>

Explanation:   The main sqlpre/sqlmod image cannot be invoked.

User Action:   Check the installation and make sure that the main
               image is in the correct location and can be executed by
               the user.

INVORDNUM,     ORDER BY number is less than 1 or exceeds count of
               select-list items

Explanation:   The number in the ORDER BY clause, used to specify
               which expression from the select list to sort by, is
               bigger than the number of items in the select list or
               it is below 1.

User Action:   Use a number which corresponds to an item in the sort
               list.

INVOUTL,       Outline <str> is marked as invalid and is not imported

Explanation:   The outline is marked as invalid and is not imported.
               The import operation will continue.

User Action:  

INVOUTTAR,     parameter <str> has an invalid target for assignment

Explanation:   The named parameter must return a value, but is called
               with a specification not capable of receiving a value.

User Action:   Specify the name of a parameter or variable to receive
               the 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.

INVPARAMETER,  unable to import parameter <str>





                                 147






Explanation:   Internal error:  the named parameter will not appear in
               the recreated database.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

INVPARTPRD,    invalid predicate in partition <str>

Explanation:   The WHERE clause specifying which rows to chose from a
               partition in a partitioned view is specified
               incorrectly.  The condition must be of the form:  WHERE
               column-name comp literal or column-name IS NULL or
               column-name BETWEEN literal and literal or OTHERWISE,
               where comp is either <, <=, =, >=, or >.

User Action:   Check that the column-name specified is that of the
               partitioning column and that the comparison operator is
               in the list above.

INVPERCENTFILL, Invalid percent fill parameter specified

Explanation:   You specified an invalid percent fill parameter.  It
               was either less than or equal to zero or greater than
               100.

User Action:   Review the command and specify a percent fill parameter
               within the above range.

INVPICN,       PIC N and CHARACTER SET specified for <str>.  What does
               this mean?

Explanation:   You declared the variable with both a character set and
               N as the picture character.

User Action:   Use either PIC N or CHARACTER SET PIC X, but not both.

INVPRIV,       Invalid privilege for this object

Explanation:   You used the ENTRY keyword with the GRANT statement.
               ENTRY is supported for REVOKE only.  Or, a GRANT or
               REVOKE statement specified for a database privilege
               which is valid only for tables, or specified for a
               table a privilege which is valid only for a database.

User Action:   Do not use ENTRY with GRANT.  Or, make sure that the
               privileges you specify in GRANT or REVOKE are valid for
               the object (database or table) named.

INVPRIVNAMES,  Invalid privilege names specified in message file



                                 148






Explanation:   The names specified in PRIV_NAMES0 and PRIV_NAMES1 are
               incorrect.

User Action:   Contact your Oracle support representative.

INVPROCEDURE,  unable to import procedure <str>

Explanation:   Internal error:  the named procedure has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

INVPROCRET,    A procedure was specified with a RETURNS clause

Explanation:   If a procedure is specified, you cannot specify a
               RETURNS clause.

User Action:   Reenter the procedure without using a RETURNS clause.

INVPROFILE,    unable to import profile <str>

Explanation:   Internal error:  the named profile has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

INVPROFILENAM, <str> "<str>" is not defined

Explanation:   The specified user, role or profile does not exist in
               the specified database.

User Action:   Please check that name exists in this database.

INVPROXY,      Invalid user for proxy

Explanation:   Proxies cannot be defined for the PUBLIC or DEFAULT
               user.

User Action:   There is no need for such proxies.  Users for whom
               there is no explicit proxy defined will acquire the
               access information contained in the containing link
               definition.

INVQUAL,       Invalid qualifier <str> specified on command line

Explanation:   You specified invalid command qualifiers in a module
               language compiler command line.

User Action:   Specify only supported command line qualifiers



                                 149






INVREFCLA,     Invalid referencing clause

Explanation:   You specified a referencing clause on a trigger which
               is not for update.  The referencing clause is only
               valid if the trigger is invoked on updates.

User Action:   Remove the referencing clause.

INVRELVIEW,    unable to import table or view <str>

Explanation:   Internal error - the named relation or view (and its
               data) has been lost.

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.

INVRNG,        Invalid range.  You specified <str>.  Valid range is
               from !@SQ to !@SQ

Explanation:   You specified a value that was out of range.

User Action:   Use a number that is in the specified range.

INVRTOSTM,     Invalid SQL statement with the Runtime license

Explanation:   You referred to an interactive SQL statement that is
               not valid with your currently installed license for
               Oracle Rdb.

User Action:   Upgrade your license to get full functionality from the
               interactive SQL interface.

INVSEGVAL,     Value for a list segment must be either a parameter or
               literal string

Explanation:   The value for a list segment was something other than a
               literal string or a parameter.

User Action:   Replace the value with one of the two valid parameters
               types.

INVSELLIS,     Select list cannot mix columns and aggregate functions
               without GROUP BY

Explanation:   The select list in a select expression without a GROUP
               BY clause cannot include both aggregate functions and
               column references which are not within aggregate
               functions.



                                 150






User Action:   Either add a GROUP BY clause, remove the aggregate
               function references, or remove the column references
               that are not in aggregate functions.

INVSELSTAR,    * is not allowed in this context

Explanation:   You specified a column wildcard (* or p.*) in a context
               where wildcards are not supported, such as outside a
               select list or in a select list for a select expression
               containing a HAVING clause but no GROUP BY (in such a
               case, you cannot specify columns, either, unless they
               are an argument to an aggregate function).

User Action:   Replace the wildcard with the column name you want to
               use.

INVSEQUENCE,   unable to import sequence <str>

Explanation:   Internal error:  the named sequence has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

INVSQLCODE,    SQLCODE has an invalid data type

Explanation:   SQLCODE must be declared as a signed longword.  The
               declaration of SQLCODE in this program is a different
               data type.

User Action:   Change the data type of SQLCODE.

INVSQLSTATE,   SQLSTATE has an invalid data type

Explanation:   SQLSTATE must be declared as a 5 character string.  The
               declaration of SQLSTATE in this program is a different
               data type.

User Action:   Change the data type of SQLSTATE.

INVSQLSTLEN,   SQLSTATE has a length that is too short

Explanation:   SQLSTATE must be declared as a 5 character string.  The
               declaration of SQLSTATE in this program is less than 5
               characters.

User Action:   Change the length of SQLSTATE.

INVSSCONV,     Invalid conversion for list column <str>





                                 151






Explanation:   You attempted to do an assignment using a list.

User Action:   Do not use lists.

INVSSHAN,      Invalid segmented string handle

Explanation:   The host variable supplied to hold a segmented string
               handle must be at least 4 bytes long.

User Action:   Specify a larger host variable.

INVSTRLEN,     Host variable <str> is defined as CHAR[1] and cannot be
               used in SQL statements.

Explanation:   The named variable is defined as CHAR[1].  The length
               of character variables used in SQL statements must be
               at least 2 since SQL always includes a NULL terminator.

User Action:   Use a different variable.

INVSYNONYM,    unable to import synonym <str>

Explanation:   Internal error:  the named synonym has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

INVTRG,        Unable to IMPORT trigger <str>

Explanation:   This is an internal error.  The named trigger will not
               appear in the recreated database.

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.  In the meantime, you can redefine this trigger
               explicitly.

INVTRISTMT,    Invalid triggered statement

Explanation:   You specified a statement or clause in a triggered
               statement list which is not supported.  Examples of
               such statements are:  - any statement other than
               DELETE, INSERT, UPDATE, ROLLBACK or error statement.  -
               a WHERE CURRENT OF clause in an UPDATE or DELETE
               statement.  - a RETURNING clause on an INSERT
               statement.

User Action:   Remove the invalid statement or clause





                                 152






INVTYPE,       Host variable <str> is based on an invalid type

Explanation:   The host variable you referred to is based on a type
               which is either not a supported type definition or was
               invalidally declared.

User Action:   Use a different type defintion.

INVUSERAS,     The AS clause is invalid with user PUBLIC

Explanation:   You can not specify a value for PUBLIC.

User Action:   Do not specify the AS clause when creating the username
               PUBLIC

INVUSERNAME,   Alias.PUBLIC is invalid in this statement

Explanation:   When an alias name is specified in this statement, you
               cannot specify alias_name.PUBLIC.

User Action:   Do not attach to the database via an alias when the
               username is PUBLIC.

INVUSEROPT,    The IDENTIFIED clause is not valid for user PUBLIC

Explanation:   If the username is PUBLIC, the IDENTIFIED clause is not
               valid.

User Action:   Remove the IDENTIFIED clause when referencing PUBLIC.

INVVALLIS,     The value list must have as many items as the column
               list

Explanation:   An INSERT statement must have as many values in the
               value list as there are in the column list.  You
               specified the wrong number of items.  Note that if
               there are any host structures in the value list, they
               will be expanded to include their elementary items.  In
               that case, to get the number of items in the value
               list, you must count the elementary items for all the
               host variables.

User Action:   Enter the correct number of values.

INVVARREF,     Variable "<str>" is illegal in this context

Explanation:   It is illegal to create a database object based on a
               variable definition.  Specifically, when using a
               COMPUTED BY clause to define a column using CREATE or



                                 153






               ALTER TABLE the COMPUTED BY clause cannot reference a
               previously declared variable.

User Action:   Change the COMPUTED BY clause so that it does not
               reference a declared variable.

INV_PARAM_VAL, Invalid parameter value passed between the program and
               module

Explanation:   The value of an input host language parameter or an
               output parameter from the module falls outside the
               supported set of values.

User Action:   Verify the parameter values and datatypes .

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_TBL_DCL,   Invalid use of declared local temporary table <str>

Explanation:   A declared local temporary table my not be used in this
               context.  A scratch table defined using DECLARE LOCAL
               TEMPORARY TABLE may not be the target of an ALTER
               TABLE, or DROP TABLE statement.  In addition the
               declared name may not be referenced by base table
               constraint, a view definition or similar stored
               metadata object.  The DECLARE LOCAL TEMPORARY TABLE
               clause may only appear a SQL Module Language or
               Pre-compiler source as part of a CREATE MODULE
               statement.

User Action:   Do not reference the scratch table name in a DDL
               statement or use the DECLARE LOCAL TEMPORARY TABLE in
               an unsupported context.

INV_TBL_USE,   Invalid use of created temporary table <str>

Explanation:   A temporary table cannot be referenced in a constraint
               on a persistent base table or in a SET TRANSACTION
               statement.  A global temporary table cannot be
               referenced in a constraint on a local temporary table.

User Action:   There is no need to reserve a temporary table since
               each user session has its own copy of the data.





                                 154






IOERROR,       an unexpected I/O error occurred

Explanation:   Unable to read any more of the Oracle Rdb interchange
               file part of the database may be imported.

User Action:   Correct the problem indicated by the message that
               follows this message and try the operation again.

ISAFUNC,       <str> is a function, not a procedure

Explanation:   The name object is a function, but is being used as a
               procedure.

User Action:   Functions must be invoked as a value_expression.

ISAPROC,       <str> is a procedure, not a function

Explanation:   The named object is a procedure, but is being used as a
               function.

User Action:   Procedures must be invoked with a CALL statement.

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.

JOITOOBIG,     Query joins too many tables

Explanation:   A join contained too many tables.

User Action:   Rewrite the query to use fewer tables.

JUNONLIN,      Extraneous characters found after the end of the
               statement

Explanation:   You typed extra characters after the end of the
               statement.

User Action:   Check statement syntax for correct statement
               termination.

KEYTOIDENT,    Nonstandard -- You used a keyword as an identifier

Explanation:   You specified an SQL keyword in a place where it is not
               a valid keyword, but where an identifier may be



                                 155






               specified.  The keyword will be used as an identifier.

User Action:   None.  This is an informational message.  However, note
               that you will not be able to specify this identifier in
               any context where the keyword may appear.

LABELALDECL,   Label <str> was already declared

Explanation:   An attempt was made to declare a label that has already
               been declared.

User Action:   Declare a label with a unique name.

LABELMISMATCH, Ending label does not match beginning label

Explanation:   An attempt was made to use an ending label that did not
               match the beginning label.

User Action:   Use an ending label that matches the beginning label.

LABELNODECL,   Label <str> was not declared

Explanation:   An attempt was made to reference an undeclared label.

User Action:   Reference a label which has been declared.

LABELNOTLOOP,  ITERATE requires label "<str>" to be on a looping
               statement

Explanation:   ITERATE must reference the label of a looping statement
               such as a WHILE, LOOP, REPEAT, or FOR loop.  The label
               used, or defaulted, is the label of some other
               statement.

User Action:   Correct the label referenced so that it is that of a
               looping statement or use an explicit label from a
               looping statement.

LANFILEXT,     <str> is the language file extension, please use
               another extension

Explanation:   The input file type you specified to the precompiler is
               the same file type as the output file type.

User Action:   Rename the file with the default file specifications
               and run the precompiler again.  Refer to the default
               file specifications in the Guide to Using SQL.

LANSWIVAL,     Value not allowed on the language qualifier



                                 156






Explanation:   The SQL precompiler requires a language qualifier (such
               as /COBOL) to specify the host language.  However, you
               specified a value with that qualifier (such as
               COBOL=3), which is not allowed.

User Action:   Remove the value from the language qualifier.

LANUNSDSCDTP,  <str> does not pass the data type for parameter <str>
               by descriptor

Explanation:   The language specified in the LANGUAGE clause of the
               module will not support the data type specified for
               this parameter by descriptor.  However, you can build a
               descriptor as a record and pass the descriptor.  Hence,
               this is only a warning.

User Action:   If you did not intend to pass the data type by
               descriptor, change the passing mechanism in the SQL
               module and in the host language.

LANUNSDTP,     <str> does not support the data type for parameter
               <str>

Explanation:   The language specified in the LANGUAGE clause of the
               module does not support the data type specified for
               this parameter.

User Action:   If you did not intend to use a data type the language
               does not support, change the data type to one the
               language supports.  If you know the language does not
               support the data type, you can use it anyway.  This is
               is only a warning message.

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.

LCKTMOUTIS,    LOCK TIMEOUT INTERVAL is <num> second(s)

Explanation:   Used in import

User Action:   None.



                                 157






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.

LENMISMAT,     Truncating right hand side string for assignment to
               column <str>

Explanation:   You executed an INSERT or UPDATE statement, and the
               string you assigned to a text column is longer than the
               column's definition.

User Action:   The message is just a warning.  You can issue an UPDATE
               statement to change the value stored or a ROLLBACK
               statement to terminate the transaction and cancel the
               INSERT operation.

LIMFIXINT,     LIMIT TO must specify an unscaled fixed numeric

Explanation:   The "n" in LIMIT TO n ROWS must be a literal, parameter
               or host variable of an unscaled fixed numeric data
               type.

User Action:   Change the LIMIT TO clause to use an unscaled fixed
               numeric data type for the row limit, n.

LINETOOLONG,   Input line was too long

Explanation:   The module language or procompiler source file
               contained a line which was too long for the input
               buffer.

User Action:   Split the offending line into two or more different
               lines.

LISTNOTVAL,    List data type is not valid for parameter or variable

Explanation:   It is illegal to define a parameter or variable with a
               data type of list

User Action:   Use another data type.

LIT_EXCEPT,    Truncation of a numeric value at compiletime

Explanation:   SQL encountered an error trying to convert a numeric



                                 158






               literal in the precompiler or module compiler to the
               data type of the field it was used with.

User Action:   Change either the literal or field so that the literal
               can be assigned to the field

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.

LOBCONVERT,    specified <str> data type converted to <str>

Explanation:   The datatype LONG is synonymous with CLOB; The datatype
               LONG RAW is synonymous with BLOB;

User Action:   None.  This is an informational message only.

LOCALNEVER,    Local routine "<str>" is never called

Explanation:   The USAGE IS LOCAL routine is not called by any SQL
               code in the module.  It there can never be use any
               application.

User Action:   Check to make sure this was intended.

LOCALRTN,      "<str>" is a local routine and may not be called here

Explanation:   The referenced function or procedure was declared with
               USAGE IS LOCAL and therefore can only be called within
               the module that contains it.

User Action:   Redefine the routine as USAGE IS GLOBAL or call an
               alternate global routine.

LOGADDCCH,     added record cache definition "<str>"

Explanation:   A new record cache definition has been successfully
               added the the database.

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

Explanation:   The specified number of committed or rolled-back
               transactions were successfully backed up from the
               after-image journal file.





                                 159






LOGAIJBLK,     backed up <num> after-image journal block(s) at <time>

Explanation:   The specified number of blocks were successfully backed
               up from the after-image journal file.

User Action:   No user action is necessary.

LOGAIJJRN,     backed up <num> after-image journal(s) at <time>

Explanation:   The specified number of after-image journals were
               successfully backed up during the AIJ backup operation.

User Action:   No user action is necessary.

LOGCREOPT,     created optimized after-image journal file <str>

Explanation:   This message indicates the action taken on a specific
               file.

User Action:   No user action is required.

LOGDELAIJ,     deleted temporary after-image journal file <str>

Explanation:   This message indicates the action taken on a specific
               file.

LOGDELCCH,     deleted record cache definition "<str>"

Explanation:   A record cache definition has been successfully deleted
               from the database.

LOGMODCCH,     modifying record cache definition "<str>"

Explanation:   The parameters for a record cache are in the process of
               being modified.

LOGMODSPM,     modified <num> spam page(s)

Explanation:   None.

LOGMODSTO,     modifying storage area <str>

Explanation:   The parameters for a storage area are in the process of
               being modified.

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

Explanation:   Database recovery was successful.  The specified number
               of transactions were re-applied to the database,



                                 160






               ignored, or rolled back.

User Action:   None.

LOGRECSTAT,    transaction with TSN <num>:<num> <str>

Explanation:   During roll-forward, this message is displayed every
               time a transaction is committed, rolled back, or
               ignored.

LOGRESOLVE,    blocked transaction with TSN <num>:<num> <str>

Explanation:   When a blocked transaction is resolved, this message is
               displayed every time the transaction is committed,
               rolled back, or ignored.

LOGSUMMARY,    total <num> transaction(s) <str>

Explanation:   Database recovery was successful.  The specified total
               number of transactions were re-applied to the database,
               ignored, or rolled back.

User Action:   No user action is required.

LOOK_FOR,      Syntax error, looking for <str>, found <str> instead

Explanation:   The syntax expected a specific keyword, but you entered
               another.

User Action:   Check the syntax and re-enter the correct keyword.

LOOK_FOR_CON,   <str>

Explanation:   This message lists syntactically legitimate
               alternatives.

User Action:   Consider options from the list.

LOOK_FOR_FIN,   found <str> instead

Explanation:   Last of three messages generated by syntax errors, this
               message shows the invalid syntax that SQL encountered.

User Action:   Re-enter the statement, or use EDIT to correct it.

LOOK_FOR_STMT, Syntax error, looking for a valid SQL statement, found
               <str> instead

Explanation:   SQL did not find the beginning of a statement where it



                                 161






               expected one.

User Action:   Supply a valid statement.

LOOK_FOR_STT,  Syntax error, looking for:

Explanation:   The syntax expected one of several valid possibilities,
               list follows.

User Action:   Consider options from the list in the next message.

LOOK_FOR_UNTERM, Syntax error, looking for <str>, found <str> instead

Explanation:   This is issued with a SQL-F-BUGCHK because it indicates
               that a severe error has occurred in the syntax tables.

User Action:   Record the exact command line as typed, (use EDIT to
               write it to a file) and contact your Oracle support
               representative.

LOWCASNOTALL,  Identifer <str> contains illegal characters

Explanation:   You supplied lower case letters in a delimited
               (double-quoted) identifier.  This is not currently
               supported by SQL.

User Action:   Change lower case letters to upper case in delimited
               identifiers.

LOW_ORD_LOS,   Reducing the scale of <str> <str> may result in the
               loss low order precision

Explanation:   Altering the scale of a column may result in the
               perceived loss of data stored in that column due to
               rounding.

User Action:   None.  This is a warning message.

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





                                 162






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

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

LRSSHUTDN,     AIJ Log Roll-Forward Server being shutdown

Explanation:   The LRS process is in final phase of being shutdown.

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

LSTCURSTA,     Cursor statement has active list cursor statements

Explanation:   You executed a RELEASE statement on a a cursor
               statement while list cursors defined based on that
               cursor exist.

User Action:   Release all of the list cursor statements before
               executing this statement.

LSTFILENAME,   The FILENAME clause may only be used on an INSERT LIST
               CURSOR

Explanation:   The INSERT ...  FILENAME clause is only supported by
               the interactive SQL interface and must be used on an
               INSERT ONLY LIST CURSOR.

User Action:   Rewrite the INSERT as a DECLARE of a table and list
               cursor, and then use INSERT ...  FILENAME for the list
               cursor.  This will read the file and load it into the
               LIST OF BYTE VARYING column.

LSTNOTNUL,     List column must be NULL to insert a new list

Explanation:   An attempt was made to insert a new list into an
               existing list.

User Action:   First delete the list with the DELETE LIST statement.

LSTREFAMB,     Column referenced in List Cursor is ambiguous in Table
               Cursor

Explanation:   The field specified in the list cursor select statement
               was mentioned in more than one select expression in the
               table cursor definition.





                                 163






User Action:   Specify a table cursor where the list reference isn't
               ambiguous.

MAXDISEXC,     The maximum number of DISTINCT expressions (<num>) was
               exceeded

Explanation:   You have exceeded the maximum number of expressions
               permitted in the DISTINCT clause.

User Action:   SQL will ignore the remaining expressions.  In most
               cases this will be suffient to generate a correctly
               reduced row set.  However, you should examine the query
               and rewrite it if necessary.

MAXFLDPRTSTR,  Maximum number of columns for table in SELECT * is
               <num>

Explanation:   You used the column wildcard (*) in the select list for
               a table that has too many columns.

User Action:   Name a subset of the columns explicitly in the select
               expression.

MAXNESEXC,     Maximum allowed statement nesting level exceeded

Explanation:   You exceeded the maximum allowed nesting of subqueries.

User Action:   Reduce the nesting level.

MAXOCTEXC,     The maximum number of octets was exceeded.

Explanation:   You have exceeded the maximum number of octete
               permitted in the CHAR or VARCHAR string.

User Action:   Reduce the size of this CHAR or VARCHAR string to keep
               the total number of octets within limit.

MAXORDEXC,     The maximum number of ORDER BY expressions (<num>) was
               exceeded

Explanation:   You have exceeded the maximum number of expressions
               permitted in the ORDER BY clause.

User Action:   SQL will ignore the remaining expressions.  In most
               cases this will be suffient to generate a correctly
               ordered set.  However, you should examine the query and
               rewrite it if necessary.

MAXRELEXC,     Maximum number of tables allowed in SELECT exceeded



                                 164






Explanation:   You exceeded the maximum number of tables allowed in
               the FROM clause of a select expression.

User Action:   Reduce the number of tables named in the FROM clause.

MFDBONLY,      operation is not allowed on single-file databases

Explanation:   An attempt was made to modify a single-file database in
               such a way that the root file would need to be
               expanded.  This type of change is not permitted for
               single-file databases.  Examples of database
               modifications that cause this error include the
               following:  reserving after-image journals or storage
               areas, adding or deleting storage areas, or changing
               the number of nodes or users.

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

MINGTRMAX,     Minimum mapping value greater than maximum value

Explanation:   You have supplied a minimum mapping value that is
               larger than the maximum mapping value.

User Action:   Correct the error and try the command again.

MINUSDATINT,   Operand of unary minus must be interval

Explanation:   You used a unary minus operator with a datetime
               operand.  Only intervals and numerics may be negated.

User Action:   Change the expression to use a different operator or
               operand.

MIN_SNPSZ,     SNAPSHOT file ALLOCATION is set to the minimum value of
               <num>

Explanation:   User specified a snapshot allocation of less than the
               Oracle Rdb minimum.  The user specified value is being
               replaced with the minimum value.

User Action:   Change the statement to specify a valid snapshot
               allocation, or take the default.

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



                                 165






               type.

User Action:   Re-enter the DATE data item and specify both the month
               and day fields.

MISPAREN,      Misplaced closing parenthesis

Explanation:   You have entered a query expression clause before
               closing the parenthesis of a search-condition.  The
               parentheses are balanced, however, are misplaced.

User Action:   Move the closing parenthesis to the proper place.

MISREQVAL,     <str> must have a value

Explanation:   No value was specified for a qualifier that was which
               must have a value.

User Action:   Correct the command line syntax error, specifying a
               value for the qualifier.

MISSINGNAME,   The schema name or authorization clause was missing

Explanation:   The CREATE SCHEMA statement requires either a schema
               name or authorization clause.  Neither was specified.

User Action:   Reenter the CREATE SCHEMA statement making sure to
               include a schema name or authorization clause.

MIXTABLIS,     Incorrect STORE CLAUSE type for this storage map

Explanation:   You specified a LIST storage clause when altering a
               table storage map or a TABLE storage map option when
               altering a LIST storage map.

User Action:   Only try to change attributes which are appropriate for
               the kind of storage map you are altering

MLTDFNRTN,     Routine <str> is multiply defined

Explanation:   A routine name was seen more than once in a Pascal
               program but the previous declaration was not marked as
               FORWARD.

User Action:   Remove the duplication of routine names and
               re-precompile

MODALLLOCAL,   Module "<str>" only contains local routines - invalid
               module



                                 166






Explanation:   A USAGE IS LOCAL routine can only be called from within
               the module scope.  This module definition is invalid
               because there is no GLOBAL routine than can be used to
               access the local definitions.

User Action:   Correct the definition of this module so that it is a
               valid definition.

MODALREXI,     module <str> already exists in the schema or database

Explanation:   The specified module already exists in the specified
               database.

User Action:   Check the spelling of the module name and ensure that
               it is a unique module name in the specified database.

MODNOTDEF,     module <str> is not defined

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

User Action:   Check the spelling of the module name and ensure that
               it is the name of a module in the specified database.

MODONLYATTR,   <str> not valid for routine "<str>" - used in CREATE
               MODULE only

Explanation:   You used a routine attribute in CREATE FUNCTION or
               CREATE PROCEDURE that is only valid for a routine
               within a CREATE MODULE statement.

User Action:   Correct the definition by removing this clause.

MODTOOOLD,     Module not compatible with session

Explanation:   The SQL module (either Module Language or Embedded SQL)
               containing the procedure returning the error was
               compiled prior to Rdb V4.1 and is trying to participate
               in a session other than the implicit session.

User Action:   Recompile the module containing the procedure and
               relink the application.

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



                                 167






               program was running to see messages relating to the
               monitor error.

MONMBXOPN,     monitor is already running

Explanation:   The monitor has already been started by another user.

User Action:   No action is required.

MONSTOPPED,    database monitor process is being shut down

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

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

MOVENOCOLS,    Relation <str> has no valid columns to move

Explanation:   None of the fields for the specified relation could be
               moved.  Each of those invalid fields caused a warning
               message to be displayed, but with no valid fields
               remaining, the transfer definition may not proceed.

User Action:   Re-enter the transfer definition with one or more valid
               columns.

MSPSIGNALSTR,  SIGNAL statement requires a 5 character string literal

Explanation:   In order to use the SIGNAL statement within a compound
               statement, you must specify a 5 character string
               literal.

User Action:   Specify a 5 character string literal when using the
               SIGNAL statement.

MSP_FUNC_NORET, You must specify a RETURN statement with a stored
               function

Explanation:   A RETURN statement is required in a stored function.

User Action:   Specify a RETURN statement in your module definition.

MSP_LIKE_XLATE, Translation of LIKE pattern string not supported in a
               compound statement

Explanation:   A search condition within a compound statement
               references LIKE which must be translated to a
               BLR$K_MATCHES.  The pattern string must be translated



                                 168






               from the LIKE special characters to the MATCHES
               characters.  This cannot be done by the database system
               involved.

User Action:   For Oracle Rdb systems, use the UPPER statement to
               convert characters to upper case and perform the LIKE
               statement on the result.  For non-Oracle Rdb systems,
               this string must be a compiletime literal.

MSP_NODEFAULT, DEFAULT clause required for variable "<str>" - CONSTANT
               or CHECK clause used

Explanation:   A variable declared as CONSTANT must be assigned an
               initial value using the DEFAULT (also =) clause.  An
               initial value must also be assigned to a variable when
               the CHECK clause is applied.

User Action:   Specify the a DEFAULT clause for this variable.

MSP_NO_OPTIMIZE, OPTIMIZE FOR clause not supported in a compound
               statement

Explanation:   A select specification specified an OPTIMIZE FOR
               clause.  This clause is not supported for statements
               within a compound statement.

User Action:   The optimization for a multistatement procedure should
               always be TOTAL_TIME.

MSP_RET_NOFUNC, A RETURN statement is only valid if a function is
               defined

Explanation:   A function must be defined in order for the RETURN
               statement to be valid.

User Action:   Define an SQL function within a stored module and then
               specify the RETURN statement.

MSP_RET_NOMOD, A RETURN statement is only valid within a stored module

Explanation:   A RETURN statement is permitted only within a stored
               module.

User Action:   Reenter the RETURN statement within a stored module.

MSP_RET_NO_INTO, A RETURNING clause must have an INTO clause in a
               compound statement

Explanation:   The INTO clause was omitted from the RETURNING clause



                                 169






               in a compound statement.

User Action:   Add the INTO clause to the RETURNING clause.

MSP_SELECT_1_ONLY, Only singleton select statements are allowed in a
               compound statement

Explanation:   The INTO clause was omitted from an interactive SELECT
               statement.

User Action:   Add the INTO clause to the SELECT statement.

MSP_USER_XLATE, Translation of USER not supported in a compound
               statement

Explanation:   A value expression refers to the literal USER.
               However, the database system doesn't support
               BLR$K_USER.

User Action:   For Oracle Rdb systems, upgrade the system to a current
               version of Oracle Rdb.  For non-Oracle Rdb systems,
               this string must be a compiletime literal.

MSP_VARNOTSUPP, <str> clause is not supported for procedures

Explanation:   This clause is only supported for external functions
               and stored SQL functions.

User Action:   Reenter your procedure definitions without using this
               clause.

MULDIMARR,     Host variable <str> is a multi-dimensioned array

Explanation:   The SQL precompilers do not support references to
               multi-dimensioned arrays.

User Action:   Assign the value in the multi-dimensioned array to a
               field which is not in a multi-dimensioned array before
               using it in an SQL statement or passing it into a
               module language procedure.

MULSPECATR,    Attribute is specified redundantly

Explanation:   You specified a field attribute more than once.
               Because SQL can not determine which attribute to use,
               it rejects it.

User Action:   Respecify the definition without the redundant clauses.





                                 170






MULTIADAVAR,   Only one Ada Language variant can be specified in a
               PRAGMA

Explanation:   A Module PRAGMA clause can specify at most one Ada
               language variant keyword.  SQL interface.

User Action:   Rewrite the PRAGMA clause with a single Ada language
               variant keyword.

MULTSPECATR,   Multiple specified attribute.  "<str>" was specified
               more than once

Explanation:   An attribute was specified more than once in a
               conflicting manner.

User Action:   Remove conflicts and try the statement again.

MULT_STRUCT,   Host variable <str> is based on a structure defined
               more than once.

Explanation:   The named host variable is based on a structure that is
               defined more than once in the file being precompiled.
               Either the user defined the structure more than once in
               a single C procedure (which is illegal in any C
               program), or there is more than one procedure that
               defines the structure (legal in C, but the SQL C
               precompiler does not recognize that the structures are
               in two different procedures and generates this error).

MUL_UIC,       Multiple UIC in ACL entry

Explanation:   You used more than one user identification code (UIC)
               in an ACL entry.

User Action:   Use only one UIC in ACL entry.

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.

MVMULTITARG,   <str> cannot be a target for more than one move clause

Explanation:   The user entered a transfer with more than one move



                                 171






               clause specifying the named target as the target.  Note
               that even if an into clause is not specified, the
               target name, taken from the source table name, must be
               unique.

User Action:   Re-enter the statement making sure that tables
               specified in INTO clauses are unique and do not
               duplicate names of source tables without INTO clauses.

MVRELABSNT,    No MOVE RELATION clause is specified in an EXTRACTION
               ROLLUP transfer

Explanation:   In a CREATE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have not specified any MOVE RELATION
               clause.

User Action:   Since a MOVE RELATIONS ALL clause is not allowed in
               this context, you have to explicitly specify the MOVE
               RELATION clauses.  Re-enter the CREATE TRANSFER
               statement by specifying the MOVE RELATION clauses
               explicitly.

NAMCONF,       the database pathname <str> is the same as another
               repository entity

Explanation:   The name chosen for the database is the same as another
               repository entity of a different type.

User Action:   Choose a different name.

NAME_IN_USE,   Cannot use name "<str>" - name in use by synonym

Explanation:   A synonym exists for another object name.

User Action:   Please choose another name.

NAMTOOBIG,     The name <str> is longer than the <num> character
               maximum

Explanation:   You specified a name which is longer than the maximum
               supported length for names in this context.

User Action:   Use a shorter name.

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.



                                 172






User Action:   Check page count of the current area allocation.  (If
               it should differ)

NEG_DIM,       Host variable <str> has a negative dimension.

Explanation:   The size of this array is less than or equal to zero.

User Action:   Only use positive dimensions.

NESFUNINV,     Aggregate functions may not be nested

Explanation:   Functions cannot contain other functions in their
               arguments.  For example, AVG(COUNT(DISTINCT(CITY)) is
               illegal.

User Action:   Do not nest aggregate functions.

NESINCFIL,     Cannot include file <str> from another included file

Explanation:   You attempted to nest INCLUDE file-spec statements.
               Source code files specified in an INCLUDE file-spec
               statement cannot themselves contain nested INCLUDE
               file-spec statements.

User Action:   Move the INCLUDE statement to the main program.

NESQRYEXP,     Column select expression was expected

Explanation:   You supplied something besides a column select
               expression where SQL expected one.

User Action:   Correct the syntax error.

NETACCERR,     error <str> <str> network <str>

Explanation:   A network-access error occurred.

User Action:   Examine the secondary message for more information.

NO1ST,         LIMIT TO clause is not valid in an INSERT or LIST
               CURSOR

Explanation:   It is illegal to specify a LIMIT TO clause in an INSERT
               or LIST CURSOR.

User Action:   Remove the LIMIT TO clause.

NOAGGALL,      aggregate expressions are not allowed in MOVE RELATION
               clauses



                                 173






Explanation:   You entered a MOVE RELATION clause that contained an
               aggregate expression.  The MOVE RELATION clause only
               allows an operator, literal value, or field name.

User Action:   Check the Replication Option for Rdb Handbook for
               details on the MOVE RELATION clause.  Re-enter the
               CREATE TRANSFER statement with a correct MOVE RELATION
               clause.

NOAIJDEF,      no default after-image filename available

Explanation:   A default after-image journal file name cannot be
               formed, because no journal file name is presently in
               the database root.

User Action:   Enable after-image journaling, and supply a name for
               the after-image journal.

NOAIJENB,      cannot enable after-image journaling without any AIJ
               journals

Explanation:   An attempt was made to enable AIJ journaling although
               no AIJ journals exist.

User Action:   Create one or more AIJ journals BEFORE enabling AIJ
               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



                                 174






               another node of the designated cluster.  If the
               database replication server process does not appear to
               be running, have your database administrator start the
               replication server, and try again.  If the database
               replication server process appears to be running
               properly, then the problem may be related to the
               mailbox by which user processes communicate with the
               replication server process.  Make sure the "server
               name" specified for both the live and standby databases
               logical are unique and identical.  On VMS platforms,
               the "server name" is used to create a logical of the
               same name that resides in a logical name table
               accessible to all users, typically the
               LNM$PERMANENT_MAILBOX name table.  If the replication
               server process abnormally terminated, a bugcheck dump
               will normally be produced.  Search the bugcheck dump
               for a string of five asterisks (*****) using the
               SEARCH/WINDOW command.  You will see a line with a
               format similar to this:  ***** Exception at <address> :
               <database module name> + <offset>
               %facility-severity-text, <error text> The exception
               line will be followed by one or more additional errors
               that will help you to determine what caused the
               replication server process to fail.  Typically, the
               problem is caused by insufficient quotas or system
               resources.  However, other possible causes include
               misdefined or undefined filename logicals.  Depending
               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.

NOALTER,       No attributes specified for ALTER <str>

Explanation:   The user specified an ALTER DOMAIN statement or an
               ALTER TABLE ALTER column-name clause without specifying
               any attributes.

User Action:   Specify something to change.

NOANYALL,      ANY and UNIQUE are not allowed in a MOVE RELATION



                                 175






               clause

Explanation:   You entered a MOVE RELATION clause containing ANY or
               UNIQUE.  The MOVE RELATION clause only allows an
               operator, literal value, or field name.

User Action:   Check the Replication Option for Rdb for details on the
               MOVE RELATION clause.  Re-enter the CREATE TRANSFER
               statement with a correct MOVE RELATION clause.

NOAREASLOTS,   no more storage area slots are available

Explanation:   The number of storage areas that can be created is
               "reserved" in advance.  An attempt has been made to
               create more storage areas than the number reserved.

User Action:   Either delete an existing storage area, or reserve more
               storage area slots before creating the area(s).

NOAUDITSERVER, VMS AUDIT_SERVER process is not running on this system

Explanation:   You attempted to generate a database audit record;
               however, the VMS AUDIT_SERVER process is not running on
               this system.

User Action:   Restart the VMS AUDIT_SERVER process.

NOBATCHUPDATE, BATCH UPDATE is not allowed without setting of <str>
               logical name

Explanation:   BATCH UPDATE transactions are not allowed with 2PC
               turned on.  2PC is only turned off by setting the
               logical name named in the message to "TRUE".

User Action:   If you want to migrate the application without the use
               of of context items (i.e.  2PC/DDTM) and allowing BATCH
               UPDATE transactions, define the logical name to "TRUE".
               Otherwise, you should change the BATCH UPDATE option to
               another transaction option.

NOBATUPD,      BATCH_UPDATE is not supported in the SQL interface to
               Oracle Rdb

Explanation:   A DECLARE TRANSACTION statement specified the
               BATCH_UPDATE transaction mode.  The SQL interface to
               Oracle Rdb does not support BATCH_UPDATE.

User Action:   Replace BATCH_UPDATE with READ_WRITE reserving the
               tables you want to update with EXCLUSIVE WRITE locking.



                                 176






NOBCKFIL,      export file <str> not created

Explanation:   An error has occurred during creation of the EXPORT
               file.

User Action:   Follow actions directed by the corresponding RMS error.

NOBCKTRNS,     you cannot EXPORT a database from within a transaction

Explanation:   You typed EXPORT from inside a transaction.

User Action:   End the transaction and try again.

NOBUCTXPARM,   BATCH UPDATE not allowed in procedure with CONTEXT
               parameter

Explanation:   Your source contains a SET TRANSACTION statement in a
               procedure which will have a context parameter added to
               it.  This is not allowed.

User Action:   Change the transaction options to use something other
               than BATCH UPDATE or compile the module without the
               /CONTEXT=ALL qualifier or remove the name of this
               procedure from the list of procedures to receive a
               context parameter.

NOBUUSINGCTX,  BATCH UPDATE not allowed in statement with USING
               CONTEXT

Explanation:   Your source contains a SET TRANSACTION statement with a
               USING CONTEXT clause.  This is not allowed.

User Action:   Change the transaction options to use something other
               than BATCH UPDATE or remove the USING CONTEXT clause
               from the statement.

NOCASING,      <str> not supported for character set <str> - ignored

Explanation:   The predicate LIKE ...  IGNORE CASE, and functions
               UPPER and LOWER require character sets that include
               upper and lower case characters.  This character does
               not support this functionality.

User Action:   This is a warning and the function or clause will be
               discarded by SQL.  This character set does not require
               IGNORE CASE, UPPER or LOWER functions.  They can be
               removed from the query.

NOCATRES,      Unable to import catalog <str>



                                 177






Explanation:   Could not import this catalog.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOCAT_DECL,    The table "<str>" cannot be qualified by a catalog name
               "<str>"

Explanation:   A local temporary table (DECLARE LOCAL TEMPORARY TABLE)
               is not associated with a catalog and schema, but with
               its containing module.

User Action:   The correct way to refer to the local temporary table
               is alias-name.MODULE.table-name.  Note that alias-name
               is optional.

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

NOCDD,         There is no repository on this system.  Specify
               FILENAME in the DECLARE ALIAS or ATTACH statement

Explanation:   You declared or attach to a database with a repository
               path name, but there is no repository running on this
               system.  You must declare or attach to the database
               using a file name.

User Action:   Declare or attach to the database by file name.

NOCDDALT,      There is no repository on this system.  Specify
               FILENAME in the ALTER DATABASE statement

Explanation:   You altered a database with a repository path name, but
               there is no repository running on this system.  You
               must alter a database using a file name.

User Action:   Alter the database with the database file name.

NOCDDRES,      The repository will not be updated

Explanation:   You cannot store the database information in the
               repository.  See the following message.





                                 178






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

NOCDDUPDAT,    Database invoked by filename, the repository will not
               be updated

Explanation:   You issued a data definition statement after invoking
               by file name

User Action:   This is a warning.  You can ROLLBACK and invoke the
               database by specifying the path name.  This ensures
               that data definitions are updated both in the
               repository and in the database itself.

NOCHAR,        no character after '' in pattern

Explanation:   A MATCH operation was in progress and the pattern was
               exhausted with the pattern quote character as the last
               character in the pattern.

User Action:   Rewrite the expression in error to have the proper
               format.

NOCMPBYRES,    computed field <str> in relation <str> not imported

Explanation:   You specified a computed field in your database that
               could not be imported.  Perhaps the field references
               other fields and relations that were deleted from the
               database by an older version of the software that would
               have permitted such a thing.

User Action:   You must investigate the problem further.  The table
               should have been properly imported except for the
               listed column.

NOCMPINTDY,    Day-time intervals are not compatible with year-month
               intervals

Explanation:   You tried to compare a value of type INTERVAL day-time
               (which may include the fields DAY, HOUR, MINUTE, or
               SECOND) with a value of type INTERVAL year-month (which
               may include the fields YEAR or MONTH).  These two types
               are not compatible.

User Action:   Use the CAST function and compare values of the same
               interval class.

NOCOLALL,      <str> interpreted as column name where none are allowed

Explanation:   An expression included a string SQL interpreted as a



                                 179






               column name where a column name does not make sense.
               For example, specifying a column name in the VALUES
               clause of an INSERT statement generates this error.
               Or, omitting quotes around a string literal can also
               generate this error.

User Action:   Replace the string with a quoted literal or host
               variable, or use a different form of the statement
               which will allow column names.

NOCOLCLAUSE,   Vertical row partitioning requires COLUMNS clauses



NOCOLLST,      Specifying a column list is incompatible with WHERE
               CURRENT OF

Explanation:   It is illegal to specify both a column list and WHERE
               CURRENT OF.

User Action:   Remove one of the clauses.

NOCOLNAM,      This view definition must explicitly list column names

Explanation:   You must specify names for all the columns in a view if
               the select expression in the view definition uses
               aggregate functions or arithmetic expressions to create
               columns not in the source tables.

User Action:   Explicitly name each coulumn in the view definition.

NOCOLRES,      Unable to import collating sequence <str>

Explanation:   SQL could not import this collating sequence.  See the
               following message.

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

NOCONNAM,      Cannot create <str> constraint name for table <str>

Explanation:   SQL tried to create a unique name for a CHECK type
               constraint on the named table.  SQL could not generate
               a unique name for this table.

User Action:   You can either delete all CHECK constraints for this
               table and then recreate all of the constraints or you
               can specify the DIAGNOSTIC parameter to give the
               constraint an explicit name.

NOCONRES,      unable to import constraint <str>



                                 180






Explanation:   Could not import this constraint -- see the message
               that follows.

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

NOCORRCOL,     There are no matching columns in the corresponding
               select lists

Explanation:   You specified a UNION CORRESPONING query expression in
               which there were no corresponding columns in the two
               select lists.  There must be at least one column which
               matches.

User Action:   Either omit the CORRESPONDING keyword, or specify at
               least one pair of columns which match.

NOCPRIRES,     Unable to import privileges on column <str>.<str> for
               <str>

Explanation:   SQL could not import these privileges -- see the
               message that follows.

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

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.

NOCSET,        character set <str> does not exist

Explanation:   You specified a character set that does not exist.  For
               lack of a better choice, the database default character
               set is assumed.

User Action:   Specify a character set that exists.

NOCUROF,       A list specification must have a WHERE CURRENT OF
               clause

Explanation:   A list specification requires a WHERE CURRENT OF clause
               and one wasn't specified.

User Action:   Specify the WHERE CURRENT OF clause.

NODATDIV,      No DATA DIVISION found in COBOL program.



                                 181






Explanation:   Every COBOL program that uses embedded SQL must have a
               DATA DIVISION statement.  None was found in your input
               file.

User Action:   Add a DATA DIVISION statement to your program.

NODATRES,      remaining data for this relation will be ignored

Explanation:   An error occurred while you attempted to store the
               data; see the following message.

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

NODBFILE,      Alias <str> is missing a declaration

Explanation:   You have declared an alias as EXTERNAL in every module
               in your application (thus, no filename is provided at
               runtime).

User Action:   Change one module to declare the alias as GLOBAL.

NODBHALW,      database handles are not allowed in a MOVE RELATION
               clause

Explanation:   You specified a database handle for the record
               selection expression (RSE) in a MOVE RELATION clause.
               Inside a MOVE RELATION clause, database handles are not
               allowed for the RSE.

User Action:   Re-enter the CREATE TRANSFER statement omitting the
               database handle name.

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.

NODBKALL,      database key references are not allowed in a MOVE
               RELATION clause

Explanation:   You entered a MOVE RELATION clause that contained a
               database key or a host variable.  The MOVE RELATION
               clause only allows an operator, literal value, or field
               name.

User Action:   Check the Replication Option for Rdb for details on the
               MOVE RELATION clause.  Re-enter the CREATE TRANSFER



                                 182






               statement with a correct MOVE RELATION clause.

NODBKDRVTBL,   DBKEY can't be returned for a derived-table

Explanation:   You attempted to return a dbkey from a derived table
               which is not allowed.

User Action:   Return only fields from the derived table.

NODBKGRO,      There is no DBKEY for a row in a result table with a
               GROUP BY

Explanation:   A SELECT expression with a group by clause requested
               the DBKEY.  There is no DBKEY for a row in a grouped
               table.

User Action:   Remove the DBKEY reference.

NODBNAME,      A database name was not specified on a DECLARE ALIAS or
               ATTACH statement

Explanation:   You issued a DECLARE ALIAS or ATTACH statement that did
               not specify a database by file specification or
               repository path name.

User Action:   Check the syntax of the DECLARE ALIAS or ATTACH
               statement.

NODBSINTXN,    No databases specified for this transaction

Explanation:   You executed an embedded SET TRANSACTION, but none of
               the aliases declared at compiletime were present in the
               current environment.

User Action:   Issue a dynamic SET TRANSACTION statement to pick up
               dynamically attached aliases in the environment.

NODECLMOD,     DECLARE MODULE is valid only in plan files

Explanation:   A Module Language module contains a DECLARE MODULE
               statement.  In Module Language, DECLARE MODULE is
               restricted to plan files.

User Action:   Put the DECLARE MODULE statement in a plan file.

NODEFAULTCONN, Default connection is not attached.

Explanation:   The default connection must be attached for this
               operation to succeed.



                                 183






User Action:   Attach to the default connection.

NODEFDB,       There is no default database

Explanation:   You specified a table name without an alias but there
               is no default database.

User Action:   Either attach a default database, or include the alias
               for a database you have attached in the table name.

NODELSYS,      System tables and views may not be deleted

Explanation:   A system table or view was specified in a DROP TABLE or
               DROP VIEW statememt.

User Action:   Check the spelling of the name of the object.

NODEVDIR,      filename does not include device and directory

Explanation:   The file you specified did not include a device and
               directory.

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

NODISTINCT,    DISTINCT columns are not valid in an INSERT or LIST
               CURSOR

Explanation:   It is illegal to specify DISTINCT in an INSERT or LIST
               CURSOR.

User Action:   Remove the DISTINCT clause.

NODROPPROC,    Procedure <str> is within a stored module and cannot be
               dropped

Explanation:   The specified procedure is a stored procedure and
               cannot be dropped.  Only external procedures can be
               dropped.

User Action:   Drop the stored module if you wish to drop the
               procedure.

NODROPSYSCAT,  Catalog <str> may not be dropped

Explanation:   The named catalog may not be dropped because it
               contains system relations.



                                 184






User Action:   Drop individual schemas or objects instead of this
               catalog.

NODROPSYSSCH,  Schema <str> may not be dropped

Explanation:   The named schema may not be dropped because it contains
               system relations.

User Action:   Drop individual objects instead of this schema.

NODUPLIVIEW,   view <str> cannot be specified more than once in a
               transfer definition

Explanation:   You have specified a view name in both a
               move-relations-clause and in a move-views-clause.

User Action:   Re-enter the CREATE TRANSFER statement by specifying
               the view either in a move-relations-clause or in a
               move-views-clause but not in both.

NOENTRYPT,     Older SQL version not compatible with compiled SQL

Explanation:   1 - You tried to run an SQL program with a version of
               SQL that is older than the version with which it was
               compiled.  The program also required SQL features not
               available from the older version of SQL.  -OR- 2 - You
               tried to run an SQL program with a shareable image
               without installing RDB$SHR or SQL$INT.

User Action:   1 - Re-compile the program under the older version of
               SQL or run it under the newer version.  -OR- 2 -
               Install RDB$SHR or SQL$INT images.

NOEUACCESS,    unable to acquire exclusive access to database

Explanation:   Exclusive access to the database was not possible.
               Therefore, the requested database operation was not
               performed.

User Action:   Try again later.

NOEXTCUR,      cannot extract, AIJ file <str> is the current AIJ

Explanation:   The current AIJ file cannot be extracted.

User Action:   Use a backup AIJ file.

NOEXTLMNOENA,  cannot extract - AIJ file <str> does not have LogMiner
               enabled



                                 185






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.

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

Explanation:   The AIJ file being extracted has unresolved distributed
               transactions.  AIJ extraction cannot handle unresolved
               transactions, so it must abort.

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

NOFILLIST,     SQL does not support lists of files

Explanation:   You specified a list of module language files on the



                                 186






               module language command line, or a list of context
               files on the precompiler command line.  SQL does not
               support lists of files.

User Action:   Specify only one language file and one context file on
               a command line.

NOFLDRES,      unable to import domain <str>

Explanation:   Could not import this domain.  See the following
               message.

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

NOFLOAT,       <str> has no floating point qualifiers

Explanation:   The language does not support a command line qualifier
               such as /FLOAT or /G_FLOAT

User Action:   The qualifier has no effect on the source language
               compiler but may be needed for Dynamic SQL SQLDA
               parameters.

NOFOR_UPD,     FOR UPDATE clause is ignored in this context

Explanation:   You specified a FOR UPDATE clause on a SELECT statement
               that ignores the FOR UPDATE clause.

User Action:   Remove the FOR UPDATE clause from the SELECT statement.

NOFSTINREPT,   FIRST clause is not allowed in MOVE RELATION clause of
               a REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have entered a FIRST clause.

User Action:   Re-enter the CREATE TRANSFER statement without the
               FIRST clause in the MOVE RELATION clause.

NOGROUP,       GROUP BY clause is not valid in an INSERT or LIST
               CURSOR

Explanation:   It is illegal to specify a GROUP BY clause in an INSERT
               or LIST CURSOR.

User Action:   Remove the GROUP BY clause.

NOIDXRES,      unable to import index <str>





                                 187






Explanation:   Could not import this index.  See the following
               message.

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

NOIMPTXN,      no implicit transaction to commit or rollback

Explanation:   The commit or rollback statement was used without there
               being a valid implicit transactin outstanding.
               Explicit transactions must be terminated via DDTM.

User Action:   Do not use the commit or rollback statement unless
               there is an implicit transaction outstanding.

NOINCDIC,      The INCLUDE statement with the FROM DICTIONARY clause
               is not supported in <str>

Explanation:   The INCLUDE statement with the FROM DICTIONARY clause
               is not supported for languages which do not have an
               equivalent statement in the language.  An example of
               this is Ada.

User Action:   Remove the INCLUDE statement with FROM DICTIONARY
               clause.

NOINCLEXT,     You cannot use the EXTERNAL keyword with the INCLUDE
               statement in this host language; EXTERNAL keyword
               ignored

Explanation:   SQL does not support the use of INCLUDE EXTERNAL
               statements in this host language.

User Action:   Remove the EXTERNAL keyword from the INCLUDE statement.

NOIOCHAN,      no more I/O channels available on system

Explanation:   The process has attempted to exceed the number of I/O
               channels that can be assigned at one time; this value
               is "per node".

User Action:   Check the VMS SYSGEN parameter CHANNELCNT to ensure
               that it is large enough to properly service the
               application.

NOITEMDEF,     unable to define item "<str>" from command line

Explanation:   Could not define an item from the command line.  See
               the following messages which will report the reason for
               the failure.



                                 188






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

NOJOINHERE,    outer join operator (+) not allowed in this context

Explanation:   Outer join operator (+) can only appear in the WHERE
               clause not in the select list.  Oracle7 has the same
               rules, but generates no compiler error.

User Action:   Rewrite the query.

NOJOINTBL,     A joined table specification is required within
               parentheses

Explanation:   Within a table-reference, parentheses denote a joined
               table or a derived table.  This set of parentheses does
               not specify a correlation name so it must be a joined
               table However, no joined table specification was found.

User Action:   Specify a joined table specification.

NOLANGFIL,     No input file specified

Explanation:   You did not specify a file for the precompiler.

User Action:   Enter the precompiler command line again, specifying a
               file this time.

NOLICENSE,     No license found

Explanation:   This system is not licensed for the SQL programming
               interface

User Action:   Install a valid license and try again.

NOLISTQUAL,    /MACHINE qualifier requires /LIST

Explanation:   The /MACHINE qualifier was specified on the command
               line without specifying the /LIST qualifier.  /LIST is
               required with /MACHINE

User Action:   Add the /LIST qualifer to the command line.

NOLOCKSOUT,    no locks on this node with the specified qualifiers

Explanation:   No locks were found on the current node that match the
               specified command qualifiers.  This usually indicates
               that either no monitors are active on this node, or no
               databases are currently being accessed on this node.





                                 189






User Action:   If databases are active on the node, try using a less
               restrictive set of command-qualifiers.

NOMAPIMPO,     Mapping Values on CREATE INDEX within an IMPORT is not
               supported

Explanation:   The data type of the columns used in the index must be
               checked for validation of the mapping values.  Since
               the tables do not exist at this time, their data types
               cannot be checked.

User Action:   Remove the mapping values from the create index and
               apply them after the import is complete.

NOMAPRES,      unable to import storage map <str>

Explanation:   Could not import this storage map.  See the following
               message.

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

NOMATCHKEY,    <str> has no matching UNIQUE or PRIMARY KEY constraint

Explanation:   You specified a referenced column list which does not
               match the columns specified as the key for any UNIQUE
               or PRIMARY KEY constraint.  The referenced column list
               must be an exact match for the key of such a
               constraint.

User Action:   Specify a referenced column list that matches a key for
               a UNIQUE or PRIMARY KEY column, or define a UNIQUE or
               PRIMARY KEY constraint that matches the referenced
               column list you specified.

NOMBLR_V2,     MBLR Version 2 required for preserving upper and lower
               case

Explanation:   Submessage for UNSUPVER.  You have used a lower case
               name, but the database does not support it.  This is
               most likely to be from a CREATE statement on a remote
               node running a version of Rdb earlier than V4.2.

User Action:   Upgrade the remote node or use upper case names.

NOMLTIMV,      attempt to move the relation <str> multiple times

Explanation:   You attempted to specify the same relation name more
               than once in the MOVE clause of a CREATE TRANSFER
               statement.  In a CREATE TRANSFER statement, you cannot



                                 190






               move the same relation more than once.

User Action:   Re-enter the CREATE TRANSFER statement omitting the
               duplicate MOVE RELATION clause.

NOMLTIMVIEW,   attempt to move the view <str> multiple times

Explanation:   You attempted to move the named view more than once in
               a CREATE TRANSFER statement.  This action is not
               permitted.

User Action:   Re-enter the CREATE TRANSFER statement, specifying each
               view only once.

NOMODFIL,      No module file specified on command line

Explanation:   A module language compiler command line must include
               the name of a module file to compile.  This command
               line did not.

User Action:   Repeat the command line with the name of a module file
               you wish to compile.

NOMODRES,      unable to import module <str>

Explanation:   Internal error:  the named module has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOMONHOMEDIR,  monitor home directory is not valid

Explanation:   The directory from which the monitor was invoked is no
               longer valid.  Typically, this occurs when the monitor
               is invoked by the installation IVP procedure, which
               subsequently deletes the invocation directory.
               However, this can also occur during day-to-day
               operations whenever directories are deleted.  When the
               monitor home directory does not exist, the monitor is
               unable to invoke other server processes, such as the
               database recovery process ("DBR") or the AIJ Backup
               Server ("ABS") to name a few.  When the monitor home
               directory does not exist, the server processes will be
               unable to create temporary work files.

User Action:   Stop the monitor, and restart it from a valid
               directory.

NOMONITOR,     database monitor is not running



                                 191






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



                                 192






NOMOVESYS,     System relations may not be moved

Explanation:   A system relation was specified in the MOVE TABLES
               clause.

User Action:   Reenter the transfer definition without the system
               relation.

NOMVRALL,      MOVE RELATIONS ALL clause is not allowed in an
               EXTRACTION ROLLUP transfer

Explanation:   In a CREATE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have specified a MOVE RELATIONS ALL
               clause.

User Action:   Re-enter the CREATE TRANSFER statement by specifying
               each relation explicitly in a MOVE RELATION clause.

NOMVVROL,      MOVE VIEWS clause is not allowed in an EXTRACTION
               ROLLUP transfer

Explanation:   In a CREATE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have specified a MOVE VIEWS clause.

User Action:   Re-enter the CREATE TRANSFER statement without the MOVE
               VIEWS clause.

NONCONARR,     Noncontiguous arrays not supported.

Explanation:   You have passed a parameter that is a noncontiguous
               array to the module language.  SQL does not support
               noncontiguous arrays.

User Action:   Use contiguous arrays to pass data to the module
               language.

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.

NONOVAL,       Negated qualifiers may not have values

Explanation:   You specified a value for a qualifier that was preceded
               by NO.

User Action:   Correct the command line syntax error, removing NO or



                                 193






               the value.

NONSINGLE_INTO, An INTO clause is only allowed on a singleton select

Explanation:   An INTO clause is not allowed on a query specification.

User Action:   Remove the INTO clause and reissue the SQL statement.

NONSTAAMB,     Host variable <str> is ambiguous in the host file

Explanation:   The ANSI and ISO SQL standards require that host
               variable names be unique in the entire file being
               preprocessed.  The SQL interface to Oracle Rdb only
               requires it to be unique in its language scope.  This
               host variable is not unique in the file.

User Action:   If it is important to have only standard features in
               your program, you should change the name of this host
               variable to make it unique in the file.

NONSTAANSPARM, Nonstandard omission of colons in module lang
               parameters

Explanation:   The /ANSI_PARAMS qualifier was not used to enforce the
               use of colons in module language parameters.  Using the
               default /NOANSI_PARAMS does not conform to the ANSI-89
               standard.

User Action:   If it is important to have your program conform to ANSI
               standard semantics, use the appropriate qualifier to
               enforce use of colons.

NONSTACAS,     Nonstandard use of lowercase

Explanation:   This token contains lowercase characters.  The ANSI and
               ISO SQL standards only supports lowercase character in
               quoted strings.

User Action:   If it is important to have only standard syntax in your
               program, you should correct this syntax.

NONSTACOB,     COBOL file is not ANSI format

Explanation:   The file being processed by the COBOL SQL precompiler
               is not in ANSI format, or, if it is in ANSI format, you
               did not specified the /ANSI switch.  The ANSI and ISO
               SQL standards require that all precompiled COBOL
               programs be in ANSI format.





                                 194






User Action:   If it is important to have your program in a standard
               format, you should convert your program to ANSI format.
               See the COBOL Reference Manual for a definition of what
               ANSI and TERMINAL formats are and how to convert
               between them.

NONSTACOL,     Column <str> has a nonstandard data type

Explanation:   You referred to a column whose data type is not
               included in the ANSI and ISO SQL standards.

User Action:   If it is important to have only standard features in
               your program, you should change the data types of these
               columns to be an standard data type.

NONSTACOLQUAL, Nonstandard qualifier used with column name

Explanation:   Additional qualifiers were supplied with a column name.
               In certain statements the standard does not allow
               column names to be qualified.

User Action:   If it is important to have your program conform to ANSI
               standard semantics, remove the extra qualifiers.

NONSTACON,     The standard does not permit this data type conversion

Explanation:   You are comparing, assigning or unioning to expressions
               with different data types.  These two expressions must
               be converted to a common data type.  The ANSI and ISO
               SQL standards do not support this conversion.

User Action:   If it is important to have only standard features in
               your program, you should change your statement to use
               supported conversions.

NONSTACUC,     The standard requires columns merged by UNION be
               identical

Explanation:   The ANSI and ISO SQL standards require that columns
               which are being merged into a single result column by a
               UNION clause must have identical definitions; that is,
               they must have the same data type, length, scale, and
               so on.  The column pointed to is not identical to the
               column with which it is being merged.

User Action:   If it is important to have only standard features in
               your program, you should change the data types of these
               columns to be identical, or remove the UNION from your
               program.



                                 195






NONSTACUR,     Cursor <str> has a nonstandard type

Explanation:   You referred to a cursor of a type not included in the
               ANSI and ISO SQL standards.

User Action:   If it is important to have only standard features in
               your program, you should not use this type of cursor.

NONSTADEF,     Significant digits of default clause literal will be
               lost

Explanation:   Differences in scale between the datatype of the column
               and the default value cause significant digits of the
               default clause value to be lost.  The ANSI/ISO standard
               requires that no significant digits be lost.

User Action:   To be ANSI conformant, make sure the default value does
               not lose significant digits.

NONSTADIS,     The standard only permits one DISTINCT clause in a
               select expression

Explanation:   You entered a select expression which either has two
               aggregate functions with DISTINCT clauses, or has a
               DISTINCT clause for the entire select list and a
               DISTINCT in an aggregate function.  The ANSI and ISO
               SQL standards do not support multiple distinct clauses.

User Action:   If it is important to have only standard features in
               your program, you should remove one of the distinct
               clauses.

NONSTADTP,     Nonstandard data type

Explanation:   The data type indicated or the data type of the column
               indicated is not included in the current ANSI and ISO
               standards for SQL.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTADYN,     The SQL standard does not include the dynamic interface

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.  The standard does not
               define the dynamic interface.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.



                                 196






NONSTAHV,      Host variable <str> has a nonstandard declaration

Explanation:   The ANSI and ISO SQL standards only require that a
               small subset of host language data declarations be
               supported.  The declaration for this host variable uses
               language features which the standards do not require.

User Action:   If it is important to have only standard features in
               your program, you should change the definition of this
               host variable.

NONSTAINVOKER, Invoker not restricted to definer

Explanation:   The /RESTRICT_INVOKER or /SQLOPTIONS=RESTRICT_INVOKER
               qualifier was not used to restrict the invoker to be
               the definer of a module.  That is, any user may invoke
               this module, but in order to conform to ANSI, only the
               definer of the module may invoke it.  The definer is
               considered to be the user who compiles a module or the
               user specified by the AUTHORIZATION clause of the
               module language.

User Action:   If it is important to have your program conform to ANSI
               standard semantics, use the appropriate qualifier to
               invoker restricting.

NONSTAMOD,     The SQL standard does not include Module Language

Explanation:   Module language is not allowed in the standard that is
               being flagged.

User Action:   Do not use module language.

NONSTANAM,     Nonstandard name

Explanation:   This name is not a valid name in the ANSI and ISO SQL
               standards.  It is either longer than 18 characters or
               contains a $.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTAOKW,     Nonstandard syntax -- required keyword or clause
               omitted

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.  The standard requires
               a clause or keyword which is optional in the SQL
               interface to Oracle Rdb.  You have omitted that clause



                                 197






               or keyword.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTAPHY,     The SQL standard does not specify the physical database

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.  The standard does not
               define physical objects.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTAQUO,     Nonstandard quote character

Explanation:   This informational message is generated by either of
               two situations:  - The ANSI and ISO SQL standards
               require the single quotation mark (') character.  You
               used the double quotation mark (") character.  - ANSI
               requires continuation be done by language rules, which
               in COBOL means the first character on the line being
               continued must be a double quotation mark (").  You
               used a single quotation mark (').

User Action:   If it is important to have only standard syntax in your
               program, correct this syntax.

NONSTARSW,     <str> is a SQL reserved keyword:  its use as an
               identifier is non-standard

Explanation:   According to SQL89 and SQL92, no nondelimited
               (unquoted) identifier can be a SQL reserved keyword.
               If a SQL keyword must be used, it must be delimited by
               double quotes.  This bypasses keyword checking in the
               scanner.

User Action:   If it is important to have only standard features in
               your program, change the identifier so that it is not a
               SQL keyword.  If the identifier must be the same as a
               SQL keyword, delimit it with double quotes (e.g.
               DOUBLE becomes "DOUBLE")

NONSTASCL,     Nonstandard scale.  Your scale (<num>) exceeds the
               precision (<num>)

Explanation:   The scale specfied exceeds the precision.  The current
               ANSI and ISO standards for SQL require a scale less
               than or equal to the precision.



                                 198






User Action:   If it is important to have only standard syntax in your
               program, you should have scale less than or equal to
               precision.

NONSTASM,      The SQL standard does not include schema manipulation

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.  The standard does not
               define the schema manipulation language.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTASYN,     Nonstandard syntax

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTASYN89,   Nonstandard SQL89 syntax

Explanation:   The syntax specified is not included in the ANSI and
               ISO standards for SQL89.

User Action:   If it is important to have only standard syntax in your
               program, remove this syntax.

NONSTASYN92E,  Nonstandard SQL92 Entry-level syntax

Explanation:   The syntax specified is not included in the ANSI and
               ISO standards for SQL92 Entry-level.

User Action:   If it is important to have only standard syntax in your
               program, remove this syntax.

NONSTASYN92F,  Nonstandard SQL92 Full-level syntax

Explanation:   The syntax specified is not included in the ANSI and
               ISO standards for SQL92 Full-level.

User Action:   If it is important to have only standard syntax in your
               program, remove this syntax.

NONSTASYN92I,  Nonstandard SQL92 Intermediate-level syntax

Explanation:   The syntax specified is not included in the ANSI and
               ISO standards for SQL92 Intermediate-level.



                                 199






User Action:   If it is important to have only standard syntax in your
               program, remove this syntax.

NONSTASYN92T,  Nonstandard SQL92 Transitional-level syntax

Explanation:   The syntax specified is not included in the ANSI and
               ISO standards for SQL92 Transitional-level.

User Action:   If it is important to have only standard syntax in your
               program, remove this syntax.

NONSTATXN,     The SQL standard does not specify how to control
               transaction characteristics

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.  The standard does not
               specify how transaction characteristics are to be
               defined.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSTAUNI,     The standard only permits UNION outside of subqueries
               in DECLARE CURSOR

Explanation:   You have included a UNION in a context in which the
               ANSI and ISO SQL standards do not support.  Only
               DECLARE CURSOR statements may have a UNION in the
               standard.

User Action:   If it is important to have only standard features in
               your program, you should remove this UNION clause.

NONSTAVIA,     Nonstandard feature for integration with Digital(tm)
               products

Explanation:   The syntax indicated is not included in the current
               ANSI and ISO standards for SQL.  This is a feature
               which is provided for compatability with Digital(tm)
               products such as DATATRIEVE and CDD/Plus.

User Action:   If it is important to have only standard syntax in your
               program, you should remove this syntax.

NONSUPPKEY,    <str> option <str> not supported

Explanation:   The precompiler does not support the value supplied
               with the specified qualifier.





                                 200






User Action:   Omit the qualifier or choose a different value.

NOOJFORMED,    no outer join has been formed -- outer join operator
               (+) ignored

Explanation:   A column was marked with the outer join operator (+)
               and compared to a simple expression that doesn't
               contain another table and column reference.  Since no
               outer join has been formed between two tables Oracle
               Rdb will ignore the outer join notation.

User Action:   If this Boolean expression appears before other AND
               comparisions then you should reorder the AND
               expressions so that comparisions with literal values
               and other simple expressions appear last.

NOONUSING,     The ON clause is illegal within a compound statement

Explanation:   The ON clause was specified in a SET TRANSACTION
               statement within a compound statement.  This clause is
               illegal because the compound statement must be in a
               single database.

User Action:   Do not use the ON clause within a compound statement.
               Issue the SET TRANSACTION statement outside of the
               compound statement.

NOOPENCUR,     There is no OPEN procedure for cursor <str>

Explanation:   There are no OPEN procedures for this cursor.  A module
               must have exactly one procedure which opens a
               particular cursor.

User Action:   Add a procedure which opens this cursor.

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





                                 201






Explanation:   The current AIJ file cannot be optimized, because the
               optimized AIJ file would not be equivalent to the
               current AIJ file if more journaling was done after
               optimization.

User Action:   Start a new AIJ file, and then optimize the AIJ file in
               question.

NOOPTNOQUIET,  cannot optimize -- AIJ file <str> backed up via a
               no-quiet-point backup

Explanation:   An AIJ file, which was backed up with a no-quiet-point
               backup, cannot be optimized, because a no-quiet-point
               backup can leave incomplete transactions in an AIJ
               file.  AIJ optimization cannot handle incomplete
               transactions within an AIJ file.

User Action:   No user action.  This AIJ file cannot be optimized.

NOOPTOPT,      cannot optimize -- AIJ file <str> is already optimized

Explanation:   An optimized AIJ file cannot be optimized again.

User Action:   No user action is required.

NOOPTPOS,      Optimizer clauses are not legal in positioned
               statements

Explanation:   You have specified one of the optimizer clauses in a
               positioned update or delete statement.  This is
               meaningless and is, therefore, ignored.

User Action:   You can remove the clause or choose to ignore this
               message.

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.

NOOPTTRI,      Optimizer clauses are not legal in trigger statements



                                 202






Explanation:   You have specified one of the optimizer clauses in a
               data manipulation statement within a trigger.  The
               optimizer clause is not supported in triggers, and is
               ignored.

User Action:   You can remove the clause or choose to ignore this
               message.

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.

NOORDER,       ORDER BY clause is not valid in an INSERT or LIST
               CURSOR

Explanation:   It is illegal to specify a ORDER BY clause in an INSERT
               or LIST CURSOR.

User Action:   Remove the ORDER BY clause.

NOORINJOIN,    outer join operator (+) not allowed in operand of OR or
               IN

Explanation:   Outer join operator (+) not allowed in operand of OR or
               IN The (+) notation must not be specified in an OR
               expression, unless the expression is parenthesized or
               appears in some type of sub-expression.

User Action:   Rewrite the predicate.

NOOUTLRES,     Unable to IMPORT outline <str>

Explanation:   Internal error:  the named outline has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOPARTCOL,     partitioning column <str> not in view

Explanation:   A name for partitioning a view was specified which is
               not in the list of columns.

User Action:   Check the spelling of the partitioning column and of



                                 203






               the column names of the view.

NOPASQLDA,     SQLDA is not supported in Pascal

Explanation:   The Pascal precompiler does not support the SQLDA data
               structure or the dynamic interface.

User Action:   Remove all references to SQLDA in your program.  If the
               SQL Dynamic interface is required with Pascal, use the
               SQL module language.

NOPGPRES,      unable to import granted profile for grantee <str>

Explanation:   Internal error:  the named Granted PROFILE has been
               lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOPHYSMULSCH,  The physical multischema attribute was not specified
               for the database

Explanation:   You attempted to attach to a database using multischema
               naming but the database was not physically enabled for
               it.

User Action:   Either ALTER the database and enable multischema or do
               not attempt to attach it for multischema naming.

NOPOSCUR,      Positioned (cursor) insert not allowed in compound or
               stored module

Explanation:   Insert cursor is not allowed in a begin ...  end block
               or CREATE MODULE statement

User Action:   Recode the module to use a FOR loop to process the
               rows.

NOPRECOMPSEL,  No precompiler selected

Explanation:   You invoked the precompiler without specifying the
               language option desired.

User Action:   Specify a switch or file extension.

NOPREPCONN,    This statement may not be prepared within a shared
               connection

Explanation:   You have attempted to prepare a statement that would



                                 204






               change the connection or the files attached to in the
               current connection.  This is not allowed within a
               shared connection.

User Action:   Do not prepare statements that effect the connection
               from with in a shared connection.

NOPRFRES,      unable to import profile <str>

Explanation:   Internal error:  the named PROFILE has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOPRIMKEY,     Table <str> has no primary key

Explanation:   You omitted the referenced column list in a referential
               constraint for which the referenced table has no
               PRIMARY KEY.  If the referenced table has no primary
               key, you must specify a column list which matches the
               columns in a UNIQUE constraint.

User Action:   Add a referenced column list, or define a PRIMARY KEY
               for the referenced table.

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.

NOPROC,        SQL statements must follow a procedure declaration

Explanation:   SQL statements must come after a procedure statement.
               This statement was found before any procedure
               statement.

User Action:   Put your SQL statements inside a procedure.

NOPRVMVIEW,    insufficient privilege to transfer the view <str>

Explanation:   You attempted to transfer the named view without READ
               privilege on the view.  You must have READ privilege on
               the view to be able to transfer the view in a CREATE
               TRANSFER statement.

User Action:   Re-enter the CREATE TRANSFER statement excluding the



                                 205






               named view.  Check the Oracle Rdb SQL Reference Manual
               for details on PROTECTION statements.

NOPRVMVREL,    insufficient privilege to transfer the relation <str>

Explanation:   You specified a relation for which you do not have READ
               privilege.  You must have READ privilege on the
               relation to transfer the relation in a CREATE TRANSFER
               statement.

User Action:   Re-enter the CREATE TRANSFER statement excluding the
               named relation.  Check the Oracle Rdb SQL Reference
               Manual for details on PROTECTION statements.  Also
               consult your database administrator.

NOPRVREPLI,    insufficient privilege to CREATE a replication transfer

Explanation:   You attempted to CREATE a replication transfer without
               CREATE privilege on the source database.  To CREATE a
               replication transfer, you must have CREATE privilege on
               the source database.

User Action:   Check the Oracle Rdb SQL Reference Manual for details
               on PROTECTION statements.  See your database
               administrator to obtain CREATE privilege.

NOPRVROLMVR,   insufficient privilege to transfer the relation
               <str>.<str>

Explanation:   You specified a relation for which you do not have READ
               privilege in the specified database.  You must have
               READ privilege on the relation to transfer the relation
               in a CREATE TRANSFER statement.

User Action:   Re-enter the CREATE TRANSFER statement excluding the
               named relation.  Check the Oracle Rdb SQL Reference
               Manual for details on PROTECTION statements.  Also
               consult your database administrator.

NOQUALNM,      Column name must be qualified by at least a table name

Explanation:   You queried SQL to show protection on a column name but
               did not indicate the table in which the column resides.

User Action:   Reenter the statement qualifing the column name with
               the table name.

NORDBPRIV,     GRANT or REVOKE specified only unsupported privileges





                                 206






Explanation:   A GRANT or REVOKE statement specified only unsupported
               DB2 privileges.  It has no effect.

User Action:   None.  SQL ignores the statement.  However, to avoid
               this message, either remove the statement or add some
               supported privileges to it.

NOREDINREPT,   REDUCE clause is not allowed in MOVE RELATION clause of
               a REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have entered a REDUCE clause.

User Action:   Re-enter the CREATE TRANSFER statement without the
               REDUCE clause in the MOVE RELATION clause.

NORELFOU,      No relation found for map <str>

Explanation:   The map name given has no table in the database or
               schema.

User Action:   Use the correct map name.

NORELRES,      unable to import table <str>

Explanation:   Could not import this table.  See the following
               message.

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

NOREMVER,      remote node or version number is not allowed in a log
               file name

Explanation:   You used a node name or a version number in the log
               file specification of a CREATE TRANSFER statement.

User Action:   Re-enter the CREATE TRANSFER statement using a log file
               specification that does not contain a node name or a
               version number.

NOREPSQLDA,    Cannot represent using SQLDA

Explanation:   An SQLDA was used, and either the length of the derived
               column name was greater than 30 octets, the data type
               was DATETIME or INTERVAL, or the data type was
               character and the character set was not the default
               one-octet character set or the maximum length in octets
               excedes 32767.





                                 207






User Action:   Use an SQLDA2 or change the code to conform to the
               limitations of an SQLDA.

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.

NORESET,       Parser unable to reset parse stack

Explanation:   A syntactic error occurred and the parser spent too
               much time trying to recover the parse stack.  In the
               past, some of these recoveries seemed to be in an
               infinite loop, though they do terminate eventually.

User Action:   Previous syntactic errors were diagnosed.  Correct them
               and retry the compilation.

NORETURN,      Specifying a RETURNING clause is incompatible with a
               positioned insert statement

Explanation:   It is illegal to specify a RETURNING clause with a
               positioned insert.

User Action:   Remove the RETURNING clause.

NOROCOL,       Read only column expressions are not allows in an
               INSERT or LIST CURSOR

Explanation:   A column expression specified something other than a
               simple column reference such as an expression.

User Action:   Limit usage to only column names.

NORTNPRIV,     GRANT and REVOKE are invalid on routines in a stored
               module

Explanation:   The specified routine was created as part of a CREATE
               MODULE statement.  Privileges are managed at the module
               level for such routines.

User Action:   Use GRANT or REVOKE on the module to change the
               privileges for any SQL or external routines in that
               module.

NORTNRES,      unable to import routine <str>





                                 208






Explanation:   Internal error:  the named routine has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NORTPARM,      <str> is not declared in procedure <str>

Explanation:   You used the parameter as a runtime parameter for a
               filename or pathname in a DECLARE SCHEMA statement.
               Such parameters must be declared in every procedure in
               the module, and must be character data types.  You did
               not declare this paramter in this procedure.

User Action:   Declare the parameter as a character variable in the
               procedure.  The use of DECLARE SCHEMA is deprecated and
               should be changed to use DECLARE ALIAS and connect.

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.

NOSCHALT,      Nothing altered in ALTER DATABASE statement

Explanation:   There was nothing altered in the ALTER DATABASE query.

User Action:   Remove the query or modify it to alter database
               characteristics.

NOSCHRES,      Unable to import schema <str>

Explanation:   Could not import this schema.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOSEGSTRAREA,  list storage area <str> is not defined

Explanation:   You specified a storage area in the LIST STORAGE AREA
               clause that does not exist.

User Action:   Specify a storage area which is already defined in the
               CREATE DATABASE statement.

NOSELALL,      SELECT FIELDS ALL clause is not allowed in an
               EXTRACTION ROLLUP transfer





                                 209






Explanation:   In a CREATE TRANSFER statement of an EXTRACTION ROLLUP
               transfer, you have specified a SELECT FIELDS ALL
               clause.

User Action:   Re-enter the CREATE TRANSFER statement by specifying
               each field explicitly in the SELECT FIELDS clause.

NOSELXPR,      Specifying a SELECT expression is incompatible with a
               positioned insert statement

Explanation:   It is illegal to specify a SELECT expression with a
               positioned insert.

User Action:   Specify only a VALUES clause.

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

NOSEQRES,      unable to import sequence <str>

Explanation:   Internal error:  the named sequence has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOSEQROW,      sequence id <num> has an entry in the root file but no
               row in RDB$SEQUENCES

Explanation:   Sequence with id indicated has a root file entry but
               not corresponding row in the table RDB$SEQUENCES.

NOSHUTDOWN,    database shutdown not allowed while backup processes
               are active

Explanation:   One or more database or AIJ backup utilities are
               active.  Database shutdown is not permitted while these
               types of utilities are active.

User Action:   Wait for the utilities to complete, or shutdown the
               database using the /ABORT=DELPRC qualifier.

NOSIP,         transaction is not a snapshot transaction

Explanation:   You have already started a transaction that is not a



                                 210






               snapshot transaction.

User Action:   Use COMMIT or ROLLBACK to terminate your current
               transaction.  Use READY BATCH RETRIEVAL to start a new
               snapshot transaction.

NOSNAPS,       snapshots are not allowed or not enabled for area <str>

Explanation:   Snapshots are not allowed or not enabled for this area.

User Action:   This is a normal situation created by the database
               definition or by a change- or modify-database command.
               Check with your DBA to make sure this situation is
               desirable.

NOSORTINREPT,  SORT clause is not allowed in MOVE RELATION clause of a
               REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have entered a SORT clause.

User Action:   Re-enter the CREATE TRANSFER statement without the SORT
               clause in the MOVE RELATION clause.

NOSPRIRES,     Unable to import database privileges for <str>

Explanation:   SQL could not import these privileges; see the message
               that follows.

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

NOSQLCA,       No INCLUDE SQLCA statement was specified

Explanation:   Every precompiled SQL program must have an INCLUDE
               SQLCA statement in it.  This program did not have one.

User Action:   Add an INCLUDE SQLCA statement.

NOSQLCODE,     Neither SQLCA, SQLCODE nor SQLSTATE were declared

Explanation:   All precompiled SQL programs must include a definition
               for an SQL status variable.  This can be done by
               specifying an INCLUDE SQLCA statement or by defining an
               integer host variable name SQLCODE or by defining a 5
               character SQLSTATE variable.  This program did none of
               the above.

User Action:   Add either an SQLCODE variable or an INCLUDE SQLCA
               statement or an SQLSTATE variable.



                                 211






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.

NOSTRDEF,      Host variable <str> is based on an undefined structure

Explanation:   The FORTRAN RECORD host variable declaration uses a
               structure name which has not be declared.

User Action:   Either change the name of the structure this host
               variable is based on, or define a structure with that
               name.

NOSTRNAM,      RECORD host variable <str> does not specify a structure
               name

Explanation:   The FORTRAN RECORD host variable declaration does not
               specify the structure name which the record is based
               on.

User Action:   Add the name of the structure this host variable is
               based on.

NOSUCHAIJ,     no such AIJ journal "<str>"

Explanation:   The specified AIJ journal does not exist for the
               database.

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

NOSUCHCON,     There is no active connection with the name "<str>"

Explanation:   A connection with the name given does not exist.

User Action:   Pass the name of a known connection.

NOSUCHCUR,     Cursor <str> has not been declared

Explanation:   You must declare a cursor before you refer to it in an
               OPEN, CLOSE, FETCH, UPDATE, or DELETE statement.

User Action:   Declare the cursor, or use the name of a cursor which
               is already declared.



                                 212






NOSUCHDATEFMT, Format DATE <num> does not exist

Explanation:   You entered DATE date-number where the logical
               LIB$DATE_FORMAT_nnn does not exist.

User Action:   Contact system manager to install the date formats.
               Make sure that these logical names are defined in EXEC
               mode as required by the OpenVMS documentation.

NOSUCHLANG,    Language <str> does not exist.

Explanation:   You entered SET LANGUAGE statement, but the logical
               name table LNM$LANGUAGE_xxx does not exist.

User Action:   Contact your system manager to make sure everything has
               been set up properly; the language may not be
               supported.

NOSUCHPROC,    Procedure <str> in CONTEXT list not defined

Explanation:   The value of the /CONTEXT qualifier specified a
               procedure which was not defined in the body of the
               module.

User Action:   Either add the procedure to the module or omit the
               offending procedure name from the /CONTEXT qualifier
               value list.

NOSUCHSTMT,    <str> is not the name of an prepared statement

Explanation:   A prepared statement with the name given does not
               exist.

User Action:   Pass the name of a known statement.

NOSUCHTIMEFMT, Format TIME <num> does not exist

Explanation:   You entered TIME time-number where the logical
               LIB$TIME_FORMAT_nnn does not exist.

User Action:   Contact system manager to install the date/time
               formats.  Make sure that these logical names are
               defined in EXEC mode as required by the OpenVMS
               documentation.

NOSUCHUSER,    unknown user "<str>"

Explanation:   An attempt was made to access information with a user
               name unknown to the database (for example, sending mail



                                 213






               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.

NOSUPREPLI,    replication transfer is not supported for this source
               database

Explanation:   You attempted to create a replication transfer on a
               source database that is not a Oracle Rdb database.
               Replication transfers can be created only for Oracle
               Rdb databases.  For other databases you can create only
               extraction transfers.

User Action:   If your source database is not a Oracle Rdb database,
               create an extraction transfer.

NOSYNRES,      unable to import synonym <str>

Explanation:   Internal error:  the named synonym has been lost.

User Action:   Contact your Oracle support representative.  Retain the
               Oracle Rdb interchange file that caused the error.

NOTALSAUTO,    AIJ Log Server is not automatically invoked by database
               monitor

Explanation:   In order to initiate database replication on the master
               database, it is required that the AIJ Log Server be
               automatically invoked by the database monitor.

User Action:   Change the AIJ Log Server invocation mode from "MANUAL"
               to "AUTOMATIC".

NOTAVIEW,      <str> is not a view

Explanation:   The name you specified in a MOVE VIEWS clause is not
               the name of a view.

User Action:   Retype the CREATE TRANSFER command with the correct
               view name.





                                 214






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

Explanation:   The Boolean evaluator was processing an expression or
               subexpression of the form "A AND B", "A OR B", or "NOT
               A".  Either the "A" or the "B" expression was not in
               the proper form.  The correct forms are "NOT X", "X EQ
               Y", "X NE Y", "X LT Y", "X GT Y", "X LE Y", "X GE Y",
               "X CONTAINS Y", or "X MATCHES Y".  The operand of NOT,
               and both sides of AND and OR expressions, must be
               Boolean expressions.

User Action:   Rewrite the expression to have the proper format.

NOTCATOBJ,     The object "<str>" cannot be qualified by a catalog
               name "<str>"

Explanation:   The object cannot be associated with a catalog and
               schema, but only with its containing database.

User Action:   The correct way to refer to the object is
               alias-name.object-name.  Note that the alias-name is
               optional.

NOTDB2,        "<str>" is a DB2 feature not supported by the SQL
               interface to Oracle Rdb.

Explanation:   This is a feature supported by DB2 that the SQL
               interface to Oracle Rdb does not support.

User Action:   Remove references to this feature.

NOTDB2DUR,     Labelled durations are a DB2 feature not supported by
               SQL.

Explanation:   The SQL interface to Oracle Rdb does not support
               labelled durations.

User Action:   Remove references to labelled durations.

NOTDB2FN,      DB2 function not supported by SQL.

Explanation:   This is a function supported by DB2 that the SQL
               interface to Oracle Rdb does not support.

User Action:   Remove references to this function.

NOTDSKFIL,     filename does not specify disk device type

Explanation:   A file name was specified which does not reference a



                                 215






               disk oriented device type.

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

NOTENUFBUF,    requested number of global buffers (<num>) is more than
               USER LIMIT (<num>)

Explanation:   The user has requested more global buffers than are
               allowed for a single user.

User Action:   Either reduce the number of requested global buffers or
               increase the number of global buffers that a user may
               allocate.  See documentation for descriptions of USER
               LIMIT clause used when creating and/or opening a
               database.

NOTEXTENDED,   area <str> cannot be extended to <num> page(s)

Explanation:   The extension of the specified storage area was not
               possible.  This condition is possible if the specified
               new size is less than the current storage area
               allocation.  This condition can also occur when
               attempting to change the size of a WORM device.

User Action:   Specify a new page count that is larger than the
               current area allocation.

NOTFOUND,      No rows were found for this statement

Explanation:   No rows were found for an UPDATE or DELETE statement,
               or a query produced an empty table.

User Action:   None.  This is a warning message.

NOTGROFLD,     Column <str> cannot be referred to in the select list,
               ORDER BY, or HAVING clause because it is not in the
               GROUP BY clause

Explanation:   In the select list and HAVING clauses of select
               expressions containing the GROUP BY clause, you can
               refer only to those columns named in the GROUP BY
               clause.

User Action:   Either add the column named in the message to the GROUP
               BY clause, or delete from the select list or HAVING
               clause.

NOTHVDECL,     <str> is not a host variable





                                 216






Explanation:   The object referenced as a host variable was not a host
               variable.

User Action:   Refer to a host variable.

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.

NOTIMPSES,     Implicit session required for rollback or commit

Explanation:   You called a procedure that tried to commit or rollback
               the implicit session's implicit transaction when the
               current session was one other than the implicit
               session.  This could be accomplished by calling a
               procedure that does a rollback or commit that was
               compiled without session support or from an RDML/RdbPRE
               module.

User Action:   Define an SQL module procedure to Rollback or Commit
               and compile with session support enabled.

NOTINPARAM,    Parameter <str> is referenced as an IN parameter, but
               declared as OUT

Explanation:   The parameter named in the message was declared with an
               explicit parameter mode, but its usage conflicts with
               the declaration.

User Action:   Make the parameter INOUT or change the usage in the
               procedure.

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.

NOTINSCUR,     Cursor <str> is not an INSERT ONLY cursor

Explanation:   In a positioned INSERT statement, the cursor named
               wasn't an INSERT ONLY CURSOR

User Action:   Restrict usage of INSERT statements to INSERT ONLY



                                 217






               CURSORS.

NOTINTBLCUR,   Column, <str>, not specified in table cursor, <str>

Explanation:   The list column specifed for a list cursor wasn't
               specified in the related table cursor.

User Action:   Modify the table cursor to add the list column to the
               select list or modify the list cursor to use a
               different column.

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.

NOTLISTCOL,    Column <str> is not of data type LIST

Explanation:   The column named in the error message has a data type
               other than LIST.

User Action:   Specify a column with the proper data type.

NOTLSTCUR,     Cursor <str> is not a list cursor

Explanation:   An attempt was made to use a list INSERT statement into
               a table cursor.

User Action:   Use the INSERT INTO CURSOR statement.

NOTOUTPARAM,   Parameter <str> is referenced as an OUT parameter, but
               declared as IN

Explanation:   The parameter named in the message was declared with an
               explicit parameter mode, but its usage conflicts with
               the declaration.

User Action:   Make the parameter INOUT or change the usage in the
               procedure.

NOTPRIRES,     Unable to import privileges on table <str> for <str>

Explanation:   SQL could not import these privileges -- see the
               message that follows.

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



                                 218






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.

NOTRGRES,      Unable to IMPORT trigger <str>

Explanation:   SQL could not import this trigger; see the message that
               follows.

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

NOTROOT,       not a root file

Explanation:   The specified file is not a database root file.

User Action:   Specify a database root file and try again.

NOTROWNUM,     ROWNUM is not available in this context

Explanation:   You have used ROWNUM and have violated one of the
               restrictions.  The restrictions are, ROWNUM:  can only
               be used in ORACLE LEVEL1 dialect can only be used in a
               comparison of select expression predicate cannot be
               used with a LIMIT TO clause cannot appear more than
               once in the predicate of a WHERE clause can only appear
               in SELECT statements cannot be compared to a column
               cannot be used in a compound statement cannot appear on
               either side of an OR boolean operator cannot be
               selected or used in a function call

User Action:   Re-issue the query and adhere to the restrictions.

NOTSAMESCOPE,  You cannot override a database attach with different
               scopes

Explanation:   The database scope (GLOBAL or LOCAL) in an ATTACH
               statement differs from the one already attached with
               the same alias.  The scope of the both aliases must be
               the same.

User Action:   Either choose a different alias or specify the same
               scope for the new database.

NOTSAMETBL,    List cursor <str> is based on a different than table
               cursor <str>



                                 219






Explanation:   The table cursor named in the message references a
               table cursor that is based on a different table from
               the LIST cursor.

User Action:   Base the list cursor on a table cursor that references
               that same table.

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.

NOTTBLCUR,     Cursor <str> is not a table cursor

Explanation:   You must declare list cursor to be the current of a
               table cursor.  The cursor specified in the WHERE
               CURRENT OF clause is another list cursor.

User Action:   Reference a table cursor.

NOTUSEIND,     Cannot use indicator variables in WHERE or HAVING

Explanation:   You cannot use indicator variables in WHERE clauses or
               HAVING clauses.

User Action:   Use the NULL keyword to test if a value is null.

NOTYPES,       Domain reference in column <str> is illegal in a
               DECLARE TABLE statement

Explanation:   You referred to a user defined domain in a DECLARE
               TABLE statement.  All domains in the DECLARE TABLE
               statement must be SQL predefined types.

User Action:   Substitute the predefined equivalent of the user
               defined domain.

NOT_A_DB,      <str> is not the name of a DSRI-compliant database





                                 220






Explanation:   You supplied the name of a database that does not exist
               under this repository directory, or you supplied a name
               that is not a DSRI-compliant database.

User Action:   Supply the name of a valid database.

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_CDD_DB,    Database was not declared using PATHNAME.  Repository
               access is illegal.

Explanation:   You tried to include a repository entity in the schema,
               but the database itself is not using the repository.

User Action:   Attach to the database using PATHNAME.

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_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_SAME_CONTEXT, The <str> being defined must be in the same database
               as the <str> it references

Explanation:   When creating an item, the item was named as part of
               one database, but it was being created from items of
               another database.  For example, trying to create an
               index in one database from a table in another database
               generates this error.

User Action:   Create the item naming only items from the same
               database.





                                 221






NOT_SCH_ID,    Alias <str> not permitted within definition of database
               <str>

Explanation:   You specified an alias of a database that was other
               than the one for the database being defined.

User Action:   Create defintions only for a single database in a
               CREATE DATABASE statement.  Use the standalone CREATE
               statements for accessing other databases.

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.

NOUNION,       UNION or derived table not valid in an INSERT or LIST
               CURSOR

Explanation:   It is illegal to specify a UNION expression or a
               derived table as the target for an INSERT CURSOR.

User Action:   Limit usage to only a single table.

NOVAL_TRIG,    NOVALIDATE must not be specified when enabling Triggers

Explanation:   In the ALTER TABLE statement, if you specify enable
               novalidate, you cannot specify triggers.  If you wish
               to enable triggers, do not specify either VALIDATE or
               NOVALIDATE.

User Action:   Respecify the ALTER TABLE statement

NOVIERES,      unable to import view <str>

Explanation:   Could not import this view -- see the message that
               follows.

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

NOVIEWINREPT,  view <str> is not allowed in MOVE RELATION clause of a
               REPLICATION transfer

Explanation:   In the MOVE RELATION clause of a REPLICATION TRANSFER
               definition you have specified a view.



                                 222






User Action:   Re-enter the CREATE TRANSFER statement without the view
               in the MOVE RELATION clause.  The view definition can
               be moved by specifying the view in the MOVE VIEWS
               clause.

NOWHERE,       WHERE clause is not valid in an INSERT or LIST CURSOR

Explanation:   It is illegal to specify a WHERE clause in an INSERT or
               LIST CURSOR.

User Action:   Remove the WHERE clause.

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_CDDACC,     No access to the repository.

Explanation:   Access is not permitted to the repository.  Previous
               error message should indicate the reason.

User Action:   Correct problem from previous error message.

NO_COMMAND,    An empty command string was passed to PREPARE.

Explanation:   A null command string was passed to PREPARE.

User Action:   Pass a string to PREPARE that is not empty.

NO_DCLTXN,     You cannot declare a transaction while a transaction is
               active.

Explanation:   There is a currently transaction in progress.  You
               cannot declare a transaction while a transaction is in
               progress.

User Action:   Commit or rollback the current transaction before



                                 223






               issuing another DECLARE TRANSACTION statement.

NO_DECIMAL,    <str> is being converted from DECIMAL to <str>.

Explanation:   DECIMAL is not a supported data type.  SQL converts
               DECIMAL columns and types to a supported data type.

User Action:   None.  This is an informational message only.

NO_DESCENDING, DSRI does not support descending index segments

Explanation:   You specified that a descending index segment; DSRI
               does not support descending index segments.

User Action:   Remove the DESC clause from the index specification.

NO_DMLPLAN,    You can only use DECLARE statements in a context file.

Explanation:   You can only include DECLARE statements in a context
               file.  These statements include DECLARE TRANSACTION,
               DECLARE ALIAS, and DECLARE TABLE.

User Action:   Remove everything but DECLARE statements from the
               context file.

NO_DTYPE,      Definition requires an unsupported data type

Explanation:   Submessage for UNSUPVER.  The definition requires the
               use of a data type not supported by the database
               system.  This is most likely to be from a CREATE
               statement on a remote node running a version of Rdb
               earlier than V4.2.

User Action:   Upgrade the remote node or use only supported data
               types.

NO_ENDCOM,     No comment terminator found

Explanation:   A PL/I begin comment was found (/*) and no
               corresponding end comment (*/) was found before the end
               of the program.

User Action:   Insert the comment terminator.

NO_ENDEXEC,    An EXEC SQL flag was found before the previous END-EXEC
               flag.

Explanation:   The previous SQL statement was missing its END-EXEC
               flag.  Every COBOL SQL statement must be preceded by



                                 224






               EXEC SQL and be terminated by END-EXEC.  A period may
               optionally follow the 'END-EXEC' flag.

User Action:   Add an END-EXEC flag to the previous SQL statement.
               Make sure that the END-EXEC flag has no embedded
               spaces, and that there is no COBOL terminator period
               before the END-EXEC flag.

NO_FILFND,     File <str> not found for input to the SQL processor

Explanation:   Attempted to open a nonexistent file.

User Action:   Check the file specified.  Supply complete file
               specification.

NO_HDRPLAN,    Module header is not legal in a plan file

Explanation:   You have put the module header in a plan file.

User Action:   Use DECLARE MODULE in the plan file and put the module
               header in the module.

NO_INCFND,     Could not find file <str> named in INCLUDE statement

Explanation:   You attempted to include a nonexistent file.

User Action:   Check the file specification in the INCLUDE statement.
               Supply a complete file specification.  Note that the
               default file extension is .SQL.

NO_NUMBER,     <str> is being converted from NUMBER to <str>

Explanation:   The NUMBER format is supported by Rdb by being
               converted to another underlying data type.  Support
               includes limiting the precision limits (values 1
               through 18 only).  NUMBER without precision and scale,
               or with precision greatre than 18 will default to
               DOUBLE PRECISON.

User Action:   None.  This is an informational message only.

NO_NUMERIC,    <str> is being converted from NUMERIC to <str>.

Explanation:   NUMERIC is not a supported data type.  The SQL
               interface to Oracle Rdb converts NUMERIC columns or
               types to a supported data type.

User Action:   None.  This is an informational message only.





                                 225






NO_PLNFND,     Context file <str> was not found for input to the
               precompiler

Explanation:   Attempted to open a nonexistent context file.

User Action:   Check the file specified.  Supply a complete file
               specification.

NO_SQLDA,      The SQLDA cannot be used in this language

Explanation:   You cannot use the PREPARE...INTO and DESCRIBE
               statements in this language.

User Action:   Remove references to the SQLDA from this module
               program.

NO_STMTB4HDR,  Statements not allowed before MODULE header

Explanation:   You entered some declare statements before a MODULE
               header in a Module Language Program.

User Action:   Put the statements in a plan file or following the
               MODULE header.

NO_SUCH_FIELD, Domain <str> does not exist in this database or schema

Explanation:   You specified a domain that does not exist in the
               database or schema.

User Action:   Check database or schema entity definitions for the
               valid type names.

NO_SUCH_TYPE,  Type "<str>" does not exist in this database or schema

Explanation:   You specified a type that does not exist in the
               database or schema.

User Action:   Check database or schema entity definitions for the
               valid type names.

NO_SYS_CONFIG, SQL cannot load the system configuration file

Explanation:   The UNIX system configuration file cannot be loaded.
               It is possible that it might not exist.

User Action:   Check the installation and make sure the system
               configuration file is installed.

NO_TRIGGER_VALS, The values in the row are not available for this



                                 226






               trigger

Explanation:   You tried to refer to the values in the row that was
               changed in a trigger action.  The values are not
               available in an action if action does not specify FOR
               EACH ROW or is triggered at a time when values are not
               supported.

User Action:   Rewrite your trigger so that values are available or
               there are no references to the values.

NO_TXNOUT,     No transaction outstanding

Explanation:   You attempted to terminate a transaction with a COMMIT
               or a ROLLBACK when no transaction was outstanding.  SQL
               does not start a transaction when you issue a DECLARE
               TRANSACTION, but waits until it encounters the first
               statement that requires a transaction.

User Action:   Execute a statement that requires a transaction before
               issuing COMMIT or ROLLBACK.  All statements except
               DECLARE TRANSACTION, DECLARE ALIAS, CREATE DATABASE,
               ATTACH and DROP DATABASE require transactions.

NO_UNSNUMERIC, <str> is being converted from UNSIGNED NUMERIC to
               <str>.

Explanation:   UNSIGNED NUMERIC is not a supported data type.  The SQL
               interface to Oracle Rdb converts NUMERIC columns or
               types to a supported data type.

User Action:   None.  This is an informational message only.

NO_USER_CONFIG, SQL cannot load the user configuration file <str>

Explanation:   The UNIX user configuration file cannot be loaded.  It
               is possible that it might not exist.

User Action:   Check that the user configuration file exists and can
               be accessed.

NSEGBLR,       unable to recover BLR string

Explanation:   Attempt to import a BLR list with more than one
               segment.

User Action:   Contact your Oracle support representative.  Retain a
               copy of the Oracle Rdb interchange file that caused the
               error.



                                 227






NULLNOIND,     Tried to store null into host variable with no
               indicator variable

Explanation:   Null values can only be stored in host variables which
               have indicator variables.

User Action:   Add an indicator variable to the host variable
               reference or make sure that no null values can be
               returned to it.

NULLUSRPWD,    A username and/or password was expected on the command
               line.  Null is being used

Explanation:   In a DECLARE ALIAS statement the DEFAULT keyword was
               used in place of the actual username or password.  The
               necessary qualifiers were not provided in the
               compilation command line, so a null is being used.

User Action:   Compile the module again and provide the necessary
               username and/or password qualifiers.  For SQL$MOD use
               /USERNAME=username /PASSWORD=password.  For SQL$PRE use
               /SQLOPTIONS=(USERNAME=username,PASSWORD=password).

NULL_COMP_COL, Computed Column <str> in table <str> is invalid - drop
               cascade

Explanation:   When you DROP an object and specify CASCADE, SQL drops
               or marks as invalid objects referencing it.  Any
               computed column in another table that references the
               dropped table, is now invalid.  This informational
               message indicates the column that was affected.

User Action:   Rollback the DROP ...  CASCADE operation or redefined
               the missing object.

NUMCMPTXT,     Numeric column will be compared with string literal as
               text

Explanation:   You tried to compare a text literal with a numeric
               column.  The numeric column is converted to text and
               the comparison is made from left-to-right, character by
               character.  This can lead to unexpected results.  For
               example, the comparison N between "0001" and "0999", no
               matter what N is, will never be true, because N is
               converted to text without a leading zero and compared
               alphabetically with the two string literals.

User Action:   None, as long as you understand the semantics of the
               operation.  You should be aware that the comparison



                                 228






               will take place between text values.

NUMHVSNOT,     Number of host variables passed (<num>) does not match
               number of parameters (<num>)

Explanation:   The number of host variables you passed in to an
               EXECUTE, OPEN, or FETCH statement does not match the
               number of parameter markers (question marks) in the
               PREPARE statement's command string.

User Action:   Make sure the number of host variables matches the
               number of parameter markers in the PREPARE statement.
               There are two ways to pass in host variables.  One,
               explicitly pass in a list of host variables in a USING
               list.  Or two, pass in an SQLDA in a USING DESCRIPTOR
               clause.  If you are using an SQLDA, you must specify in
               the SQLDA SQLN field the number of SQLVAR structures
               you have initialized to point to your variables.

NUMITESEL,     Number of items selected does not match number of items
               in the INTO clause

Explanation:   A SELECT statement must have as many values in the
               select list as there are in the INTO clause.

User Action:   Enter the same number of columns in the select list and
               the INTO clause.  If you are using 'SELECT *', check
               the columns that are defined in the selected table.

NUMXPREXP,     A numeric expression was expected

Explanation:   A numeric literal, a numeric host variable, was
               expected but something else was found.

User Action:   Correct the syntax error.

NUM_TO_DATE,   Numeric data in <str> <str> cannot be converted to a
               date data type

Explanation:   Oracle Rdb will not allow numeric data types to be
               converted to date.

User Action:   Do not try it again.

OBJECT_EXISTS, Object <str> already exists

Explanation:   The object exists in the specified database.

User Action:   Please check that name exists in this database.



                                 229






OBJNOTEXI,     The object <str> does not exist in this schema or
               database

Explanation:   The specified object does not exist in the database.
               The objects checked were tables, views, procedures,
               functions, domains, modules, types, sequences, and
               synonyms.

User Action:   Create the object first then recreate the synonym.

ONEDBINMOD,    Only one alias is legal in this module

Explanation:   This statement declares more than one alias in a
               module.  This is illegal because it requires the use of
               a database facility that cannot cross databases.

User Action:   Remove the offending statement or additional alias
               declarations.

ONEEPERM,      only one E character is permitted in an edit string

Explanation:   An edit string contains more than one E character.
               Only one is allowed.

User Action:   Redefine the edit string with only one E character.

ONEJOIN,       a predicate may reference only one outer-joined table

Explanation:   A predicate may reference only one outer-joined table
               The (+) notation, may only be specified on the columns
               of one table in a predicate for a given join.  Multiple
               joins may exist in a predicate.

User Action:   Rewrite the predicate.

ONETABLEJOIN,  a table may be outer joined to at most one other table

Explanation:   A table may be outer joined to at most one other table.
               When multiple joins are being expressed, the (+)
               notation may only be specified on columns of a table
               being compared to the columns of exactly one other
               table.

User Action:   Rewrite the predicate.

ONETXNMOD,     Only one DECLARE TRANSACTION statement is allowed per
               module

Explanation:   You can use only one DECLARE TRANSACTION statement in a



                                 230






               preprocessed module.  It must occur before the first
               executable statement (SELECT, INSERT, UPDATE, CREATE,
               etc.).

User Action:   Only use one DECLARE TRANSACTION statement in a module.

ONLFIRPRE,     Only the first file in the list will be precompiled

Explanation:   You specified a list of files to be processed.  This
               list will be passed along to the compiler with the
               first file replaced by the generated language file.
               However, only the first file in the list will be
               precompiled.

User Action:   If more than one of the files has SQL statements, they
               must be precompiled in separate command lines.  If you
               want only the first file precompiled, then no user
               action is neccessary.

ONLFIRVAR,     Only first variable in qualified variable expression

Explanation:   COBOL allows only the first variable in a qualification
               to be an array.  The preprocessors do not recognize the
               arrays of arrays constructs in FORTRAN, COBOL or BASIC.

User Action:   Rewrite the query and check the appropriate language
               reference manual.

ONLONEDB,      Only one database can be referred to in this statement

Explanation:   You cannot use objects from more than one database in a
               SELECT, UPDATE, DELETE or CREATE statement.  You can,
               however, refer to tables from one database in an INSERT
               statement and refer to tables in another database in
               the SELECT which provides the values for that INSERT
               statement if the insert statement is not part of a
               trigger definition.

User Action:   Use separate statements for multiple database access.

ONLONETRN,     Only one transaction allowed at a time

Explanation:   Only one transaction is allowed at a time.  Note that
               SQL starts a transaction, even if none was previously
               declared, on the first data manipulation statement.

User Action:   Issue a COMMIT or ROLLBACK statement to terminate the
               transaction, then declare another.





                                 231






ONLVALLST,     Only a value list is valid in an INSERT LIST CURSOR
               statement

Explanation:   The only valid expression is a value list.

User Action:   Use only a VALUES expression.

ONLY1LIST,     Only one list column may be specified

Explanation:   The list specification specifies more than one column
               in the SELECT list.  List cursors are limited to
               processing only a single list.

User Action:   DECLARE a separate list cursor for each list.

ONLY1TBL,      Only one table may be specified in an INSERT or LIST
               CURSOR

Explanation:   It is illegal to specify more than one table in an
               INSERT or LIST CURSOR.

User Action:   Limit usage to specifying only a single table.

ONLYONEPSECT,  Only one PSECT statement per module is supported

Explanation:   The PSECT directive may only be used once per module.

User Action:   Decide which PSECT statement is really desired and
               delete all others.

OPENERR,       unable to open <str> as the interchange file

Explanation:   Could not access the Oracle Rdb interchange file.

User Action:   Correct the problem indicated by subsequent messages
               and try the operation again.

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.



                                 232






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.

OPRSTK_OVRFLO, Operator stack overflow

Explanation:   The internal limit of the parsing operator stack was
               exceeded.

User Action:   Contact your Oracle support representative.  Retain the
               the query that caused the error.

OPTDDLREC,     TSN <num>:<num> contains DDL information that cannot be
               optimized

Explanation:   The identified transaction contains an AIJ record with
               DDL information.  DDL information cannot be optimized
               and forces a flush of the accumulated SORT information.
               Too many of these operations limit the effectiveness of
               the resulting optimized after-image journal and
               decrease the overall optimization performance.

User Action:   No user action is required.

OPTEXCMAX,     TSN <num>:<num> record size <num> exceeds maximum <num>
               record size

Explanation:   The identified transaction contains an AIJ record whose
               size exceeds the maximum specified sort record size.
               During AIJ optimization, fixed-length data records are
               passed to the sort utility.  By default, the size of
               the sort records is 1548 bytes in length, which is also
               the maximum value allowed.  The sort record length
               affects the amount of disk space required to complete
               the AIJ optimization operation.  The size of the record
               passed to the sort utility can be adjusted using the
               <fac>$BIND_OPTIMIZE_AIJ_RECLEN logical.

User Action:   If possible, increase the size of the sort record using
               the <fac>$BIND_OPTIMIZE_AIJ_RECLEN logical.

OPTEXCSRT,     AIJ record count exceeded specified <num> sort



                                 233






               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
               number of required sort operations is reduced.
               However, this may result in a larger output file.

OPTIMATTOP,    The OPTIMIZE clause must appear in the outermost
               compound

Explanation:   You have used the OPTIMIZE clause in a compound
               statement that is nested within one or more other
               compound statements.

User Action:   Move the OPTIMIZE clause to the outermost compound
               statement in the procedure.

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



                                 234






               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.

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.

ORAROWNUM,     ROWNUM only available in ORACLE LEVEL1 dialect

Explanation:   You have used ROWNUM outside of the ORACLE LEVEL1
               dialect.





                                 235






User Action:   Set your dialect to ORACLE LEVEL1 and re-issue the
               query.

OTHPARTEX,     duplicate otherwise partition <str> defined

Explanation:   This partitioned view already has a default partition.

User Action:   Remove one of the partitions or redefine one of their
               conditions.

OUTLNOTDEF,    query outline <str> is not defined

Explanation:   The specified query outline does not exist in the
               specified database.

User Action:   Check the spelling of the query outline name and ensure
               that it is the name of a query outline in the specified
               database.

OUTL_EXISTS,   query outline <str> already exists

Explanation:   A query outline with the name given already exists.

User Action:   Pass the name of a query outline that doesn't exist.

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.

PARAMNAMEREQ,  Parameter name required for stored routines

Explanation:   A parameter name is required when defining a parameter
               within a stored routine.  A parameter name is not
               required when defining a parameter within an external
               routine and/or an external routine defined within a
               stored module.



                                 236






User Action:   Redefine the routine and when defining a parameter,
               specify the parameter name.

PARAMNOTSTR,   Parameter <str> in procedure <str> must be a character
               parameter

Explanation:   You used the parameter as a runtime parameter for a
               filename or pathname in a DECLARE SCHEMA statement.
               Such parameters must be declared in every procedure in
               the module, and must be character data types.  The
               parameter in this procedure is not a character data
               type

User Action:   Declare the parameter as a character variable in the
               procedure.  The use of DECLARE SCHEMA is deprecated and
               should be changed to use DECLARE ALIAS and connect.

PARAMQUAL,     Parameters must not be qualified

Explanation:   A reference to a parameter included qualifiers.  You
               cannot qualify parameters.

User Action:   Define the parameter in the procedure, or use a
               parameter name which is defined in the procedure.

PARBADCLA,     Parameter <str> passed by invalid descriptor class
               (<num>)

Explanation:   The parameter was passed to a module language procedure
               by descriptor when parameter checking was enabled and
               the class of the descriptor was not a supported
               descriptor class.

User Action:   Correct the argument in the host language program

PARBADDAT,     Parameter <str> has invalid data type:  <num> declared,
               <num> passed.

Explanation:   The parameter was passed to a module language procedure
               with a different data type than it was declared in the
               procedure.  The codes for the data type as declared and
               as passed are specified in the message.  The codes are
               from the DSC$B_DTYPE from the descriptor.  See the
               "Introduction to VMS System Routines" manual for these
               codes.

User Action:   Make the parameter agree in the module and the host
               language.





                                 237






PARBADLEN,     Parameter <str> has invalid length:  <num> declared,
               <num> passed.

Explanation:   The parameter was passed to a module language procedure
               with a different length than it was declared in the
               procedure.  The error message indicates the length of
               the parameter as declared in the module, and the length
               of the parameter passed at run-time.

User Action:   Make the parameter agree in the module and the host
               language.

PARBADSCA,     Parameter <str> has invalid scale:  <num> declared,
               <num> passed.

Explanation:   The parameter was passed to a module language procedure
               with a different scale than it was declared in the
               procedure.  The error message indicates the scale of
               the parameter as declared in the module, and the scale
               of the parameter passed at run-time.

User Action:   Make the parameter agree in the module and the host
               language.

PARBINSCA,     Parameter <str> has a binary scale factor

Explanation:   The parameter was passed to a module language procedure
               with a binary scale factor.  SQL supports only decimal
               scale factors.

User Action:   Either do not use a scale factor, or use a data type
               with which your language uses decimal scale factors.
               For example, PL/I uses binary scale factors with fixed
               binary data and decimal scale factors with fixed
               decimal data.  If you want to use scale factors, use
               fixed decimal.  Be sure to change the module to agree
               with the new data type.

PARMLISTREQ,   FETCH LIST statements require a parameter list

Explanation:   The FETCH LIST statement requires that the user
               explicitly specify a parameter list.

User Action:   Specify the parameter list.

PARSE_INIT,    SQL cannot parse either the command line or the DBSINIT
               environment variable

Explanation:   The format of either the command line or the DBSINIT



                                 238






               environment variable is invalid.

User Action:   Check the formats of both the command line and the
               DBSINIT environment variable.

PARSE_STACK_OVERFLOW, Parse stack overflow

Explanation:   The internal limit of the parsing stack were exceeded.

User Action:   Contact your Oracle support representative.  Retain the
               the query that caused the error.

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.

PASPRGNOTFND,  No Pascal program was found

Explanation:   No Pascal program was found in the input preprocessor
               file.  The embedded SQL statements can only be
               processed within a program block.

User Action:   Add a program block around the SQL statements.

PASRECUNS,     Host variable <str> is based on a record type that is
               unsupported

Explanation:   The host variable you referred to is based on a record
               type which is unsupported.

User Action:   Use a different type defintion.

PASVARUNS,     Host variable <str> is based on a record type that uses
               variants

Explanation:   The host variable you referred to is based on a record
               type which uses Pascal variants.  SQL does not support
               types which include variants.

User Action:   Use a different type definition.

PATH_NAM_REQ,  PATHNAME clause necessary when the repository is
               required



                                 239






Explanation:   When you create a database using the DICTIONARY IS
               REQUIRED clause, then you must also specify the
               PATHNAME clause.

User Action:   Change the CREATE DATABASE statement to either add the
               the PATHNAME clause or to remove the DICTIONARY IS
               REQUIRED clause.

PHYBACDAT,     it was physically exported on <str>

Explanation:   Information about the Oracle Rdb interchange file.

User Action:   None.

PKCONSNOTCB,   Computed column may not be a primary key

Explanation:   You specified a primary key constraint for a computed
               column, which does not support this constraint.

User Action:   Remove the primary key constraint from this definition.

PKGNAMCHG,     The SQL package name has been changed from <str> to
               <str>

Explanation:   The name of the Ada source file is used to generate the
               name of a SQL package.  Because the SQL package name is
               not a legal Ada name, the package name is changed to a
               legal Ada name.

User Action:   If the SQL package name and declaration file must be
               the same name as the Ada source file, then change the
               name of the Ada source file.  If not, no user action is
               required.

PKNOTNULL,     Column <str> is used in a primary or unique key but
               permits NULL values

Explanation:   You specified a column in a primary or unique key
               definition which permits NULL values.  The current ANSI
               and ISO SQL standards require that only fields for
               which NOT NULL is specified may be included in a
               primary or unique key.

User Action:   If it is important to have only standard syntax in your
               program, you should either remove the column from the
               primary or unique key, or add the NOT NULL attribute to
               the column.

PREC_SPEC_TWICE, Precision specified twice in declaration



                                 240






Explanation:   Parsing the data declaration for this variable
               indicated that the precision was specified twice.

User Action:   Check the declaration of this variable.  Pay particular
               attention to the area surrounding the precision
               declaration.

PREFORSTR,     The host variable in the PREPARE FROM clause must be a
               string.

Explanation:   A host variable in the FROM clause of a PREPARE
               statement must have a string data type.

User Action:   In COBOL declare the variable to be PIC X(n).  In PL/I
               declare the variable to be CHAR(n).  In FORTRAN,
               declare the variable to be CHARACTER XYZ*n.

PREMATURE_EOF, Statement is syntactically incomplete

Explanation:   You entered a syntactically incomplete statement.

User Action:   Complete the statement before typing "RETURN".

PREMEOF,       premature end of file encountered in <str>

Explanation:   A premature end-of-file was encountered while reading
               the specified file.

PREPNOCTXSTR,  This statement may not be prepared with a context
               structure

Explanation:   A PREPARE or EXECUTE IMMEDIATE with an embedded USING
               CONTEXT clause or in a module language procedure with a
               context parameter was passed a statement which may not
               be prepared with a context structure.

User Action:   If you are using a precompiled program, remove the
               USING CONTEXT clause.  If you are calling a module
               language procedure, either remove the procedure name
               from the /CONTEXT=(...) list or, if /CONTEXT=ALL is
               used, pass a zero as the address of the context
               structure or fill the distributed TID portion of the
               context structure with zeroes.

PRESS_RET,     Press RETURN for more:

Explanation:   Used in online HELP display paging

User Action:  



                                 241






PRESTAOPE,     Cannot prepare or release statement name used by an
               open cursor

Explanation:   You declared a cursor based on a prepared statement
               name and opened the cursor.  While that cursor was
               still open, you tried to prepare or release the same
               statement name.

User Action:   Close the cursor or end the transaction before using a
               PREPARE or RELEASE statement with the same statement
               name.

PRIKEYEXI,     Table <str> already has a primary key

Explanation:   You specified a primary key definition for a table
               which already had one.  A table can have only one
               primary key.

User Action:   Remove the primary key definition from the statement,
               or delete the existing primary key before executing the
               statement.

PRMLENMISMAT,  Value assigned to <str> in the routine "<str>"
               truncated during call

Explanation:   When calling a function or procedure you passed a
               character string value which was longer than could be
               held by the parameter.  SQL will therefore truncate the
               value during assignment to the parameter.

User Action:   This is just a warning.  However, you should probably
               correct the strings length (possibly using the CAST
               function), or adjust the routine definition to avoid
               loss of data.

PROCALREXI,    procedure <str> already exists in this schema or
               database

Explanation:   The specified function or procedure already exists in
               the specified database.  This could be caused by
               another procedure or an external function with the same
               name.  Remember that procedure names are scoped to the
               schema not the module.

User Action:   Check the spelling of the function or procedure name
               and ensure that it is a unique function or procedure in
               the specified database.

PROCNOCA,      Procedure <str> has neither an SQLCA nor SQLCODE



                                 242






               parameter

Explanation:   A module language procedure must have either an SQLCA
               or an SQLCODE parameter declared.  This procedure had
               neither.

User Action:   Add either an SQLCODE or SQLCA parameter.

PROCNOTDEF,    procedure <str> is not defined

Explanation:   The specified function or procedure does not exist in
               the specified database.

User Action:   Check the spelling of the function or procedure name
               and ensure that it is the name of a function or
               procedure in the specified database.

PROCNOTEXT,    SHOW PROTECTION and SHOW PRIVILEGES are invalid on
               stored procedures

Explanation:   The specified routine is a stored procedure.  Because
               the GRANT and REVOKE statements are only allowed on the
               module level, you cannot SHOW PROTECTION or SHOW
               PRIVILEGES on a stored procedure.

User Action:   Specify the SHOW PROTECTION or SHOW PRIVLEGES
               statements on the stored module.

PROCSTATWO,    Procedure <str> has more than one SQLCA or SQLCODE
               parameter

Explanation:   A module language procedure must have either an SQLCA
               or an SQLCODE parameter declared.  This procedure had
               more than one.

User Action:   Remove an SQLCODE or SQLCA parameter.

PRPSELINTO,    Preprocessed SELECT statements must include an INTO
               clause

Explanation:   A preprocessed SELECT statement needs a place to put
               the data it retrieves.  An INTO clause is required to
               specify where to put the data.

User Action:   Add an INTO clause to the SELECT statement.

PRVERRSDTPUNK, Data type unknown due to previous errors

Explanation:   Due to previous errors, the precompiler or module



                                 243






               language compiler does not understand either side of an
               assignment.

User Action:   Correct errors previously reported, and recompile.

PTR_VAR,       Host variable <str> is a pointer variable which is
               illegal in SQL statements.

Explanation:   The named variable is defined as a C pointer variable.
               These variables are currently not supported by the C
               precompiler.

User Action:   Use a different variable.

PUTOPESEG,     Attempt to put to an opened list

Explanation:   You attempted to do a SEGSTR.PUT using a handle
               returned by a SEGSTR.OPEN statement.  You can only do
               SEGSTR.GETs using the handle returned by open.

User Action:   Specify the correct handle

QIOXFRLEN,     data transfer length error - expected <num>, actual
               <num>

Explanation:   The expected data-transfer length was not equal to the
               actual data-transfer length.

User Action:   This is usually caused by a hardware problem.

QUAINVVAL,     An invalid value <str> was specified for <str>

Explanation:   You specified an invalid value for a command line
               qualifier

User Action:   Correct the command line syntax error.

QUALNOTALLOW,  A qualified name is not allowed in this context

Explanation:   A qualified name was entered by the user where a
               non-qualified name was required.

User Action:   Reenter the statement omitting the illegal name
               qualifier.

QUALVALPOS,    The value of the <str> qualifier must be a positive
               number

Explanation:   The value of the specified qualifier must be a positive



                                 244






               number.  A negative number was specified.

User Action:   Change the qualifier to specify a positive value.

QUANOVAL,      The <str> qualifier does not take a value

Explanation:   You specified a value for a command line qualifier
               which cannot have a value.

User Action:   Correct the command line syntax error.

QUERYCAN,      Query cancelled at user's request

Explanation:   The query was cancelled at the user's request.

User Action:   No action required.  If the query was cancelled due to
               its complexity, try a simpler query.

QUERYLIMPOS,   Query limit must be a positive number

Explanation:   The limit of the number of rows or the number of
               seconds must be positive.

User Action:   Change the SET statement of compiler qualifiers to
               specify a positive value.

QUETOOBIG,     Query or routine contains too many table references

Explanation:   A query expression, trigger actions, procedures or
               function definition involves too many tables, views or
               table expressions in joins and unions.

User Action:   Rewrite the query to use fewer tables.  Creating views
               to define intermediate unions and joins may solve the
               problem.  For stored routines break the routine into
               small routines and use the CALL statement to execute
               parts of the program.

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.





                                 245






User Action:   None.

RCSABORTED,    record cache server process terminated abnormally

Explanation:   A detached record cache server process failed
               abnormally.

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

RCSMANYNODES,  database node count exceeds record cache maximum of "1"

Explanation:   The record cache feature can only be used when
               after-image journaling is enabled, the "Fast Commit"
               feature is enabled, and the maximum node count is set
               to "1".

User Action:   Alter the database to set the maximum database node
               count to "1".

RCSRQSTFAIL,   request to Record Cache Server failed

Explanation:   User submitted a request the RCS process which failed
               either during the submission process or, for
               synchronous requests, possibly during the execution of
               the request.

User Action:   Examine the secondary message(s) or the database
               monitor log file (SYS$SYSTEM:*MON.LOG) or any RCS log
               file in root file's directory or any
               SYS$SYSTEM:*RCSBUG.DMP bugcheck dump files for more
               information.

RDBVMSONL,     Operation supported for Oracle Rdb databases only

Explanation:   You issued a GRANT or REVOKE statement on a non-Oracle
               Rdb database.  The SQL interface to Oracle Rdb supports
               GRANT and REVOKE for Oracle Rdb databases only.

User Action:   Do not issue any GRANT or REVOKE statements with this
               database.

RDONDB,        You are compiling against a read only database <str>

Explanation:   The database specified for use during compilation is
               currently read only.  This module cannot be executed if
               the run time environment is also read only.





                                 246






User Action:   Alter the database to be read write, put in a declare
               transaction read only statement, or execute this
               against a different database which is not read only.

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.

REANOWRT,      A READ_ONLY transaction can not specify write locks.

Explanation:   The transaction was specified as READ_ONLY but a table
               in the RESERVING clause was locked for write access.
               This is a conflict of access modes.

User Action:   Declare the transaction READ_WRITE or use a read lock.
               Note that the default is always READ_WRITE.

REAONLATT,     You specified other attributes in addition to READ ONLY

Explanation:   You specified other attributes in addition to READ ONLY
               in the ALTER STORAGE AREA clause.  If you specify READ
               ONLY, you cannot include other attributes in the same
               statement.

User Action:   Specify the other attributes in separate ALTER DATABASE
               statements.

REBUILDSPAMS,  SPAM pages should be rebuilt for logical area <str>

Explanation:   Modifications have been made to the logical area
               parameters that may have made the SPAM thresholds
               inaccurate.  The RMU utility should be used to rebuild
               the SPAM pages for the logical area.

RECEXCMAX,     size of edit string exceed internal data structure
               limits

Explanation:   The length of an edit string exceeds the size of the
               internal data structures that used to represent it.

User Action:   Temporarily reduce the size of the edit string and
               contact your Oracle support representative.  Retain a
               description of the table and domains that produce this
               error.





                                 247






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.

RECUNTIL,      work-around:  roll forward AIJ using /UNTIL="<time>"
               qualifier

Explanation:   A fatal, unexpected error was detected by the database
               management system during the roll forward of an AIJ
               file.  However, one or more transactions were
               successfully rolled forward up to the date indicated in
               the message.  Using the /UNTIL qualifier on the
               roll-forward command produces a database that is
               transaction consistent up to the indicated date.

User Action:   Issue the AIJ roll-forward command using the indicated
               /UNTIL qualifier.

REFKEYCOL,     Referencing column <str> and corresponding referenced
               column <str> do not match





                                 248






Explanation:   A referencing column and its corresponding referenced
               column must have the same data type, size and scale.
               These columns differ in one of these attributes.

User Action:   Specify a referential constraint where the columns all
               match.

REFKEYNUM,     Constraint column lists must have the same number of
               columns

Explanation:   The referencing column list and the referenced column
               list (explicit or implicit) must have the same number
               of columns.  This is not true for this referential
               constraint (FOREIGN KEY).

User Action:   The number of columns for the REFERENCES (aka FOREIGN
               KEY) constraint must be the same as the referenced
               PRIMARY KEY, or the listed column list.

RELNOTDCL,     Table <str> has not been declared in module or
               environment

Explanation:   The local temporary table has not been declared, or its
               declaration is not valid in this context.

User Action:   Declare the local temporary table (DECLARE LOCAL
               TEMPORARY TABLE) in the module header.

RELNOTDEF,     Table <str> is not defined in database or schema

Explanation:   The specified table does not exist in the current
               database or schema.

User Action:   Declare the correct database or schema.  Spell the
               table name correctly.  You may have specified a name
               other than a table name.

REL_EXISTS,    Table <str> already exists in this database or schema

Explanation:   You attempted to create a table with the name of an
               existing table

User Action:   Choose a different name.

REMNOTALW,     a remote source database is not allowed to be
               replicated

Explanation:   You were attached to a database on a remote node when
               you tried to create a replication mode transfer using



                                 249






               the CREATE TRANSFER statement.

User Action:   Create an extraction transfer instead of a replication
               mode transfer.

REORGONLALTSM, REORGANIZE is only legal with ALTER STORAGE MAP

Explanation:   You specified the REORGANIZE clause in a statement
               other than ALTER STORAGE MAP.

User Action:   Remove the REORGANIZE clause.

REPCOLNAM,     Column name <str> appears twice in the column list

Explanation:   A column name is repeated in a column list where unique
               names are required.

User Action:   Specify only unique names.

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.

REQ_ARG,       Switch <str> requires an argument

Explanation:   An argument is required for the specified switch, and
               none was supplied.

User Action:   Use an argument.

REQ_VAL_ARG,   Switch <str> requires a valid argument

Explanation:   The argument for the specified switch is invalid.

User Action:   Use a valid argument.

RESABORT,      terminating the IMPORT operation

Explanation:   The IMPORT operation has been aborted; see the messages
               preceding this one.

User Action:   None.

RESERVED_WORD, <str> is a keyword.  It cannot be used as a name

Explanation:   You entered a keyword where a name was expected.



                                 250






User Action:   Specify a unique name instead of the keyword.

RESTART,       restarted recovery after ignoring <num> committed
               transaction(s)

Explanation:   The specified number of committed transactions did not
               apply to this database root.  All subsequent
               transactions were applied.

User Action:   None.

RESWORDCHKOFF, ANSI identifier checking is OFF

Explanation:   Identifiers are not checked for keyword status:  see
               above for full explanation.  No keyword checking is the
               standard behavior in SQL89.  This checking behavior is
               turned on by the SET ANSI IDENTIFIERS ON statement and
               turned off by the SET ANSI IDENTIFIERS OFF statement.

RESWORDCHKON,  ANSI identifier checking is ON

Explanation:   Identifiers are checked for keyword status:  if they
               are keywords in SQL89 or SQL92 then they are flagged as
               such.  This checking behavior is turned on by the SET
               ANSI IDENTIFIERS ON statement and turned off by the SET
               ANSI IDENTIFIERS OFF statement.

RES_KEYWORD,   <str> is a reserved word in SQL and cannot be used as
               an identifier

Explanation:   The identifier is a SQL keyword and cannot be used as
               an identifier

User Action:   Use an identifier that is not in the set of valid SQL
               keywords

RES_WORD_AS_IDENT, Keyword <str> used as an identifier

Explanation:   You used a ANSI keyword as an identifier.

User Action:   Use ANSI QUOTING rules and double quotes.

RETRYPOS,      The retry count must be positive

Explanation:   The count specified in the RETRY clause of the CREATE
               SCHEDULE statement must be positive.

User Action:   Re-enter the schedule definition with a positive retry
               count.



                                 251






RET_NO_POS,    A RETURNING clause cannot be used with a positioned
               UPDATE statement

Explanation:   A RETURNING clause was used with a positioned-UPDATE
               statement.

User Action:   Use either a searched-UPDATE statement or the FETCH
               statement to fetch the cursor after the update.

REVENTANS,     REVOKE ENTRY is not supported for databases with ANSI
               privileges

Explanation:   You executed a REVOKE ENTRY statement in a database
               that has ANSI style privileges.  There are no entries
               in ANSI style privileges so this is not supported.

User Action:   Execute the statement again specifying the privileges
               you would like to revoke.

REVOKE_ALL_R,  ALL must be specified for REVOKE ALL ROLES

Explanation:   REVOKE ALL ROLES must be specified to revoke all roles
               from an user or role.

User Action:   Correct the syntax of the REVOKE statement

ROOMAJVER,     root major version is incompatible with the software
               version

Explanation:   Your database was created with an incompatible version
               of the software.

User Action:   Your database cannot be used with the version of the
               software you have installed on your machine.

ROOTMAJVER,    database format <num>.<num> is not compatible with
               software version <num>.<num>

Explanation:   Your database was created with an incompatible version
               of the software.

User Action:   Your database cannot be used with the version of the
               software you have installed on your machine.

ROOT_CORRUPT,  database has been corrupted and must be restored from
               backup

Explanation:   The database has been corrupted and must be restored
               from a full database backup.



                                 252






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



RTCSASS_C2C,   Cannot convert from character to character in the
               specified character set

Explanation:   A runtime conversion from character to character was
               specified, but the character sets weren't compatible.
               Use Action:  Choose a different character set for the
               target.

RTCSASS_C2N,   Cannot convert from character in the specified
               character set to numeric

Explanation:   A runtime conversion from character to numeric was
               specified, but the character set of the character field
               doesn't support ASCII.

User Action:   Choose a different character set for the target.

RTCSASS_D2C,   Cannot convert from date to character in the specified
               character set

Explanation:   A runtime conversion from date to character was
               specified, but the character set of the character field
               doesn't support ASCII.

User Action:   Choose a different character set for the target.

RTCSASS_N2C,   Cannot convert from numeric to character in the
               specified character set

Explanation:   A runtime conversion from numeric to character was
               specified, but the character set of the character field
               doesn't support ASCII.



                                 253






User Action:   Choose a different character set for the target.

RTNALREXI,     function or procedure <str> already exists in this
               schema or database

Explanation:   The specified function or procedure already exists in
               the specified database.  This could be caused by
               another procedure or an external function with the same
               name.  Remember that procedure names are scoped to the
               schema not the module.

User Action:   Check the spelling of the function or procedure name
               and ensure that it is a unique function or procedure in
               the specified database.

RTNATTRSAID,   <str> clause is not valid for stored routines

Explanation:   For stored routines the specified clause is illegal
               syntax.

User Action:   Reenter the definition an omit this clause.

RTNMECHSAID,   Passing mechanism is ignored for stored routines

Explanation:   For stored routines, a passing mechanism is ignored.  A
               passing mechanism is acceptable for external routines,
               and external routines defined within a stored module.

User Action:   This is just a warning.  However, you may wish to
               redefine the stored routine without specifying the
               passing mechanism.

RTNNOTDEF,     function or procedure <str> is not defined

Explanation:   The specified function or procedure does not exist in
               the specified database.

User Action:   Check the spelling of the function or procedure name
               and ensure that it is the name of a function or
               procedure in the specified database.

RUJDEVDIR,     RUJ filename "<str>" does not include a
               device/directory

Explanation:   The RUJ filename you specified did not include a device
               and directory.

User Action:   For maximum protection, you should always include a
               device and directory in the file specification,



                                 254






               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.

SAME_CONTEXT,  context number <num> already used

Explanation:   You have used a context number that has already been
               used within the same query.

User Action:   Select a new context number that has not already been
               used within the query

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.

SCHCATMULTI,   Schemas and catalogs may only be referenced with
               multischema enabled

Explanation:   You used a statement that referred to a logical schema
               or catalog but multischema was not enabled.  This is
               not allowed.

User Action:   Enable multischema using the SET MULTISCHEMA ON
               statement in interactive or dynamic SQL, the
               MULTISCHEMA option of the /SQLOPTION qualifier in the
               precompiler, or the /MULTISCHEMA qualifier in the



                                 255






               module processor.

SCHNOABSTIM,   EVERY or RETRY EVERY must not specify an absolute time

Explanation:   You entered an absolute time for the EVERY or RETRY
               EVERY clause of the CREATE SCHEDULE statement.

User Action:   Use a delta time or, for the EVERY clause, use a day of
               the week, DAY, WEEK, or MONTH.

SCHNOTDEF,     Schema <str> is not defined

Explanation:   The specified schema does not exist in the specified
               catalog.

User Action:   Check the spelling of the schema name and ensure that
               it is the name of a schema in the specified catalog.

SCH_EXISTS,    Schema <str> already exists

Explanation:   You attempted to create a schema in the specified
               catalog with the name of an existing schema in that
               catalog.

User Action:   Choose a different name for the new 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.

SEGAREERR,     List area <str> referred to but not defined

Explanation:   The CREATE DATABASE statement indicated that lists must
               be stored in a specific storage area, but that storage
               area was never created.

User Action:   Change the CREATE DATABASE statement to include a
               CREATE STORAGE AREA statement with the name referred to
               by the LIST clause.

SEGSTREXP,     Cannot use a list in an expression

Explanation:   You attempted to use a list column in an expression.
               Segmented strings may be used only in expressions using
               the NULL operator.



                                 256






User Action:   Remove the operations on the list from the DML query.

SELLISTSUB,    Select list contains a subquery

Explanation:   Subqueries in select lists are not allowed in the
               standard being flagged.

User Action:   Remove the subquery from the select list.

SELMORVAL,     The result of a singleton select returned more than 1
               value

Explanation:   A singleton select statement (SELECT...INTO) may only
               return 1 row of values.  The result table for this
               singleton select contains more than one row.

User Action:   Either embed the SELECT statement (without the INTO
               clause) in a DECLARE CURSOR statement and process it
               with OPEN and FETCH statements, or modify the SELECT
               statement so it will return only one row.

SEQALREXI,     Sequence <str> already exists in the schema or database

Explanation:   The specified sequence already exists in the specified
               database.

User Action:   Check the spelling of the sequence name and ensure that
               it is a unique sequence name in the specified database.

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.

SEQNOTDEF,     Sequence <str> is not defined

Explanation:   The specified sequence does not exist in the specified
               database.

User Action:   Check the spelling of the sequence name and ensure that
               it is the name of a sequence in the specified database.

SEQPCOLREF,    invalid pseudo column reference "<str>" for sequence
               "<str>"

Explanation:   Sequences allow just two names for the pseudo columns
               CURRVAL and NEXTVAL.  It is likely that the name used
               in the query was mistyped, or a sequence name was used



                                 257






               instead of a table reference.

User Action:   Correct the spelling of the pseudo column name, or use
               a table and column reference.

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.

SESNOTENA,     This module is not capable of handling multiple
               sessions

Explanation:   The procedure contains a session-oriented command, but
               the compiled module doesn't support sessions.

User Action:   Choose the /SESSION or SQLOPTION=(SESSION) when
               compiling the module in question.

SETTRASLI,     SET TRANSACTION statement specifies conflicting options

Explanation:   The SET TRANSACTION statement specified READ ONLY and
               some other incompatible attribute, such as Isolation
               Level 1.

User Action:   Do not specify incompatible attributes.

SETWIDTH,      error setting width of terminal

Explanation:   An error occurred during the parsing of a file name.

User Action:   Examine the secondary message for more information.

SEVERRDET,     A severe error was detected

Explanation:   This is the exit status for a preprocessor when a
               severe error is detected.

User Action:   Fix the error.

SF_NOCOMMIT,   A COMMIT statement is not permitted within an SQL



                                 258






               function definition

Explanation:   A COMMIT statement is valid within a stored procedure
               but not within an SQL function.

User Action:   Define an SQL function without a COMMIT statement.

SF_NOROLLBACK, A ROLLBACK statement is not permitted within an SQL
               function definition

Explanation:   A ROLLBACK statement is valid within a stored procedure
               but not within an SQL function.

User Action:   Define an SQL function without a ROLLBACK statement.

SF_NOSAVEPOINT, a SAVEPOINT control statement is not permitted within
               a SQL function definition

Explanation:   Neither a SAVEPOINT, ROLLBACK TO SAVEPOINT nor SET
               TRANSACTION statement is permitted within an SQL
               function.  These statements may only be used in a SQL
               stored procedure, or an anonymous compound statement
               (also known as a multi-statement procedure).

User Action:   Define the SQL function without any SAVEPOINT control
               statements.

SF_NOSETTRANS, A SET TRANSACTION statement is not permitted within a
               SQL function definition

Explanation:   Neither a SET TRANSACTION nor a START TRANSACTION
               statement is permitted within an SQL function.

User Action:   These statements may only be used in a SQL stored
               procedure, or an anonymous compound statement (also
               known as a multi-statement procedure).

User Action:   Define the SQL function without any TRANSACTION control
               statements.

SHAREDCONNS,   Shared connections exist.  The default connection may
               not be disconnected

Explanation:   There are existing shared connections.  The default
               connection cannot be disconnected until all shared
               connections are disconnected.

User Action:   Disconnect all shared connections before attempting to
               disconnect the default connection.



                                 259






SHINDFLDSIZE,  size of index key is <num>

Explanation:   Used to display the number of characters used in the
               key for an index.  The size of index key is the minimum
               length for the column used for the key.

User Action:   None.

SHINDMAPVAL,   mapping values <str> to <str>

Explanation:   Uses values from <low> to <high> to minimize space
               needed for index node.

User Action:   None.

SHINDMAPVAL2,  this space for hire

Explanation:   Uses values from <low> to <high> to minimize space
               needed for index node.

User Action:   None.

SHOFLAGMIA,    The MIA flagger mode is ON

Explanation:   Used in SHOW FLAGGER [MODE]

User Action:   None.

SHOFLAGSQL89,  The SQL89 flagger mode is ON

Explanation:   Used in SHOW FLAGGER [MODE]

User Action:   None.

SHOFLAGSQL92E, The SQL92 Entry-level flagger mode is ON

Explanation:   Used in SHOW FLAGGER [MODE]

User Action:   None.

SHOFLAGSQL92F, The SQL92 Full-level flagger mode is ON

Explanation:   Used in SHOW FLAGGER [MODE]

User Action:   None.

SHOFLAGSQL92I, The SQL92 Intermediate-level flagger mode is ON

Explanation:   Used in SHOW FLAGGER [MODE]



                                 260






User Action:   None.

SHOFLAGSQL92T, The SQL92 Transitional-level flagger mode is ON

Explanation:   Used in SHOW FLAGGER [MODE]

User Action:   None.

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.

SMA_DAT_TYP,   Altering <str> <str> to a smaller data type may cause
               data loss

Explanation:   Altering a column to a smaller data type might cause
               data already stored in that column to appear lost.

User Action:   None.  This is a warning message only.

SNAPFULL,      snapshot area too full for operation

Explanation:   You attempted to store a record in the database,
               because there was an active reader and the snapshot
               area in which the record would go is too full.

User Action:   Modify the snapshot area extend parameter to allow
               snapshot area extension.

SORTOPERR,     a VMS SORT/MERGE operation was unsuccessful

Explanation:   A VMS SORT/MERGE operation completed unsuccessfully.
               See the secondary message for information about what
               operation failed.

User Action:   Fix the VMS SORT/MERGE problem, and try again.

SPACREQ,       A space is required before file specification

Explanation:   A space is required to parse the begining of the file
               specification.

User Action:   Run the preprocessor again and include a space before
               the file specification.



                                 261






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.

SPANOTVAL,     Space management options not valid on areas with
               uniform page format

Explanation:   Space management options of thresholds, interval or
               both were specified for an area with a uniform page
               formats.

User Action:   Remove the space management option(s) from the storage
               area with uniform page format, or change the storage
               area with the specified space managment option(s) to
               have mixed page format.

SPCALLVER,     procedure <str> is not callable by this version of SQL

Explanation:   The stored procedure named in the error message is not
               in the proper format or was written by a version of SQL
               that does not recognize stored procedures.

User Action:   Redefine the procedure using SQL or use a more current
               version of SQL to compile the CALL statement.

SPELLCORR,     identifier <str> replaced with <str>

Explanation:   A keyword was misspelled, but the error has been
               corrected by SQL.

User Action:   None required, unless the correction was not the
               intended keyword.



                                 262






SQLCHSCALE,    An invalid SQLCHRONO_SCALE value of <num> was found in
               the SQLDA

Explanation:   You passed in an SQLDA with a illegal SQLCHRONO_SCALE
               value.

User Action:   You must enter a valid SQLCHRONO_SCALE value in every
               SQLCHRONO_SCALE field in the prepared command string
               that SQLD indicates is necessary.  For datetime values,
               this is is a value indicating the subtype of the
               datetime.

SQLDANOT,      SQLDA not large enough (<num>) to handle number of
               parameters (<num>)

Explanation:   The SQLDA passed to PREPARE or DESCRIBE is not large
               enough to handle all of the parameters in the
               associated PREPARE command string.

User Action:   Allocate an SQLDA to be large enough to have one SQLVAR
               for each input or output parameter ('?') in the PREPARE
               command string.  Then set SQLN to indicate the number
               of SQLVARs in the SQLDA.

SQLDATA,       An SQLDATA field in the SQLDA was not initialized

Explanation:   You passed in an SQLDA with a SQLDATA value of zero in
               one of the SQLVAR blocks.

User Action:   You must enter nonzero values in every SQLDATA field in
               the prepared command string that SQLD indicates is
               necessary.

SQLLEN,        An invalid SQLLEN value of <num> was found in the SQLDA

Explanation:   You passed in an SQLDA with a illegal SQLLEN value.

User Action:   You must enter a valid SQLLEN value in every SQLLEN
               field in the prepared command string that SQLD
               indicates is necessary.  For interval values, this is
               is a value indicating the subtype of the interval.

SQLNOIND,      Indicator parameters are not allowed in LANGUAGE SQL
               modules

Explanation:   A procedure in a module, whose language is SQL,
               specified an indicator variable.

User Action:   LANGUAGE SQL parameters inherently support NULL values.



                                 263






               Omit the indicator reference.

SQLRTERROR,    An error was detected at runtime

Explanation:   An error occurred at runtime.  This message precedes
               other messages which are also displayed.

User Action:   Take the action displayed by the other messages.

SQLTYPE,       An invalid SQLTYPE value of <num> was found in the
               SQLDA

Explanation:   You passed in an SQLDA with a illegal SQLTYPE value.

User Action:   You must enter a valid SQLTYPE value in every SQLTYPE
               field in the prepared command string that SQLD
               indicates is necessary.

SQLVARASIND,   declared variables are not supported as indicator
               parameters

Explanation:   An attempt was made to use a variable as an indicator
               variable.  This is not supported.

User Action:   Use the IS NULL operator to test the variable for null
               or non null values.  Use a host variable or module
               language parameter as an indicator for another host
               variable or parameter.

SQLVARNOIND,   indicator parameters are not supported for declared
               variables

Explanation:   An attempt was made to use a variable with an
               INDICATOR.  This is not supported.  Variables declared
               within a compound statement or in a module
               automatically support the NULL attribute and therefore
               do not require a separate NULL indicator variable.

User Action:   Remove the INDICATOR variable and simply use the
               declared variable.  Use the IS NULL operator to test
               the variable for null or non null values.

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.





                                 264






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.

SSTOOBIG,      The segmented string ID for column <str> is <num>
               bytes, host variable must be the same size or larger.

Explanation:   The host variable you are using with the DBKEY is not
               the same size as the dbkey.

User Action:   Allocate a host variable which is the correct size.

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.

STANOTDEF,     The '<str>' statement has not been defined

Explanation:   You attempted to use a statement name in an EXECUTE or
               a DESCRIBE statement that had not been used in a
               PREPARE statement.

User Action:   Prepare a statement name before using it in an EXECUTE
               or a DESCRIBE statement.

STANOTSEL,     Cursor can only be used with prepared SELECT statements

Explanation:   You attempted to declare a cursor based on a prepared
               statement that was not a SELECT statement.  Cursors can
               be based only on SELECT statements.

User Action:   Use EXECUTE to execute this statement.

STAREAFUL,     storage area <str> is full

Explanation:   You attempted to store a record in the database, but
               the storage area in which the record would go is full.
               This condition can be caused by the storage area being
               set to disallow being extended or when the ABM pages
               are at their limit and cannot map a new extension for



                                 265






               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.

STAREQCOL,     The standard requires a column in this context

Explanation:   The ANSI and ISO SQL standards require that you specify
               a column which is not in an expression in this context.

User Action:   If it is important to have only standard features in
               your program, you should change your querry to use a
               column here

STARNOTALL,    Invalid use of asterisk - expected column name

Explanation:   You attempted to use the column wildcard (*) where SQL
               requires an explicit column name.

User Action:   Supply the names of the columns to be referenced.

STAROCUR,      Nonstandard update of read-only cursor <str>

Explanation:   In the ISO and ANSI standards for SQL, a cursor is
               read-only if it includes an ORDER BY clause.  Read-only
               cursors cannot be used in UPDATE or DELETE statements.

User Action:   If it is important to have only standard features in
               your program, you should change the cursor to not
               include the ORDER by clause, or not use it in an UPDATE
               or DELETE statement.

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



                                 266






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

STATWOCUR,     Cannot declare a second cursor based on statement <str>

Explanation:   A prepared statement can only have one cursor based on
               it.  You tried to declare a second cursor based on the
               same prepared statement name used in a previous DECLARE
               CURSOR statement.

User Action:   Remove one of the cursor definitions from your program
               or base the second cursor on a different statement
               name.

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.

STMSGOVR,      Parameters for procedure <str> are too large for stored
               message buffer

Explanation:   The aggregate size of the parameters for a stored
               procedure exceeds 64K which is a current implementation
               limit.

User Action:   Reduce the number or size of the parameters.

STMTALREXI,    <str> is the name of an existing dynamic statement

Explanation:   Another prepared statement name with the name given
               does not exist.

User Action:   Pass the name that does not match an existing statement
               name.



                                 267






STMTNOTINPRG,  The embedded SQL statement is not within the program
               block

Explanation:   The embedded SQL statement is either before the program
               statement or after the last end statement.

User Action:   Move the embedded SQL statement between the program
               statement and the last end statement.

STOCLAUSE_TOO_MANY, Storage Map "<str>" has multiple STORE clauses

Explanation:   Only one STORE clause is allowed per storage map
               definition.  (This assumes a non-vertical row
               partitioning storage map definition.)

User Action:   Specify only one STORE clause if you're not specifying
               vertical row partitioning.

STOCOLERR,     Differing column count for USING and WITH LIMIT clauses

Explanation:   The number of columns specified for the USING clause is
               different from the number of literal values specified
               in the WITH LIMIT list.

User Action:   The STORAGE MAP or INDEX definition requires the same
               number of literal values as there are columns in the
               USING clause.  Either correct the list of columns in
               the USING clause, or the number of literals in the WITH
               LIMIT OF clause.

STOCOLUKN,     Column "<str>" in the USING clause does not exist in
               table "<str>"

Explanation:   A column that did not exist in the table was used in
               the CREATE STORAGE MAP statement.

User Action:   Specify a valid column name.

STOMAPNOTDEF,  Storage map <str> is not defined

Explanation:   The specified storage map does not exist in the
               specified schema.

User Action:   Check the spelling of the storage map name and ensure
               that it is the name of a storage map in the specified
               schema.

STOMAP_EXISTS, Storage map <str> already exists





                                 268






Explanation:   You attempted to create a storage map in the specified
               schema with the name of an existing storage map in that
               schema.

User Action:   Choose a different name for the new storage map.

STOTABUKN,     Table "<str>" referenced in storage map does not exist
               in this database or schema.

Explanation:   The table named in the CREATE STORAGE MAP statement can
               not be found the database or schema.

User Action:   Specify a valid table name.

STRARRAY,      Host variable <str> is either a structure array or in a
               structure array

Explanation:   The SQL precompilers do not support references to
               fields in a structure array (a host structure defined
               as an array).

User Action:   Assign the value in the structure array to a field
               which is not in a structure array before using it in an
               SQL statement.

STRCVTNUM,     String literal will be converted to numeric

Explanation:   You tried to store a text literal into a numeric
               column.  The string literal will be converted to a
               numeric data type, if possible.

User Action:   None.  However, if the string literal cannot be
               converted to a numeric data type, an error will result.

STRINXPR,      Host structure <str> used in a value expression

Explanation:   SQL statements can only refer to a host structure in
               contexts where the host structure can be expanded to a
               list of values.  A value expression requires a single
               value, so host structures cannot be used there.

User Action:   Replace the host structure with an elementary item.

STRLITEXP,     A string literal was expected

Explanation:   A string literal was expected but something else was
               found.

User Action:   Correct the syntax error.



                                 269






STRLITMISQUO,  String literal missing closing quote

Explanation:   The string in a user assignment statement is missing a
               closing quote.

User Action:   Insert one or more quotes as appropriate.

STRMORELE,     The <str> structure has more elements than the <str>
               indicator vector

Explanation:   The specified structure has more elements than the
               indicator vector it is associated with.

User Action:   Make the indicator vector larger.

STRTOOBIG,     String literal is too big

Explanation:   You entered a string literal with a length greater than
               1024 characters.  The length of a string literal must
               be less than or equal to 1024 characters.  A likely
               cause of this error is an unmatched quote mark.

User Action:   Put missing quote marker, or use a string literal with
               no more than 1024 characters.

STRTOOLON,     String expression must not be longer than <num> octets

Explanation:   The string expression must be shorter than the
               specified length.  For example a database filespec must
               be less than 255 octets.

User Action:   Specify a shorter string expression.

STRVALTRUNC,   string value in "<str>" will be truncated to maximum
               length of <num> octets

Explanation:   Rdb supports strings up to 65535 octets in length.
               Even though you declared this host variable in excess
               of this length only the first 65535 octets will be used
               if the variable is passed to a SQL statement.
               Applications which expect to pass more than 65535 bytes
               to Rdb need to be corrected.

User Action:   Reduce the length to a value less than or equal to
               65535 to eliminate the warning.  The application may
               need to be changes to check for this limit.

STRXPREXP,     A string expression was expected





                                 270






Explanation:   A string literal, a character host variable, or USER
               was expected but something else was found.  (Note that
               USER is not permitted in EXECUTE IMMEDIATE, and
               specifying it will also generate this message.)

User Action:   Correct the syntax error.

STTREMCNCT,    error allocating remote statistics network connection

Explanation:   None.

STTSVRFIND,    error identifying remote statistics server

Explanation:   None.

SUBNOGB,       Subqueries in basic predicates cannot use GROUP BY

Explanation:   A subquery used in a basic predicate, such as WHERE
               CITY = (SELECT ...), cannot contain the GROUP BY
               clause.  The ANSI standard does not support this.

User Action:   If it is important to have only standard SQL statements
               in your program, remove the GROUP BY clause or change
               the predicate to include ANY or ALL.

SUBNONATOMIC,  Atomic compounds may contain only atomic compounds

Explanation:   An attempt was made to use the NOT ATOMIC clause in a
               compound which is contained in a compound that
               specifies ATOMIC.  Atomic compounds may contain only
               atomic compounds.

User Action:   Use the ATOMIC clause for all sub-compounds of an
               atomic compound.

SUBTOOVAL,     Column select expression specifies too many columns

Explanation:   A column select expression may only fetch one value
               unless it is in an EXISTS predicate.  This means any
               column select expression that uses the column wildcard
               (*) must have only one-column tables in its FROM
               clause.

User Action:   If you specified more than one column explicitly,
               remove all but one.  If you used a wildcard, explicitly
               name a single column instead.

SWITCH_REQ,    Switch required, found <str>





                                 271






Explanation:   A command line switch is required.

User Action:   Supply a valid switch.

SWOPNNOTCOMP,  database is open on another node with incompatible
               software

Explanation:   Incompatible Rdb software exists in this OpenVMS Galaxy
               system and is attempting to open a database in a Galaxy
               shared environment.  Identical versions of Rdb are
               required in order to access a database from multiple
               nodes in an OpenVMS Galaxy environment.

SYM_EXP,       One of the following symbols was expected:

Explanation:   You typed an unexpected keyword.

User Action:   Type a correct keyword.

SYNALREXI,     Synonym <str> already exists in the database

Explanation:   The specified synonym already exists in the specified
               database.

User Action:   Check the spelling of the synonym name and ensure that
               it is a unique synonym name in the specified database.

SYNNOTDEF,     Synonym <str> is not defined

Explanation:   The specified synonym does not exist in the specified
               database.

User Action:   Check the spelling of the synonym name and ensure that
               it is the name of a synonym in the specified database.

SYNTAX_ERR,    Syntax error

Explanation:   A syntax error was detected in a your SQL statement.

User Action:   Correct the syntax error and try the statement again.

SYSPAGFOR,     Page format for system relations cannot be MIXED

Explanation:   The system relations for Oracle Rdb must be placed in
               an area that contains the uniform page format.

User Action:   Either create a separate storage area for RDB$SYSTEM or
               change the default page format to uniform.





                                 272






SYSPAGUNI,     Page format for system relations being changed to
               UNIFORM

Explanation:   The storage area that contain the system relations must
               have UNIFORM page formats.  Either through the use of
               the defaults, or by directly specifing PAGE FORMAT IS
               MIXED, SQL has been told to use MIXED page format for
               the area containing the system relations.  SQL is
               overriding that to UNIFORM pages.

User Action:   None.  This is an informational message.  The user
               might want to change the command if it originated in a
               command file.  This may avoid confusion later.

SYSRDONLY,     write access is not allowed if RDB$SYSTEM is read-only

Explanation:   BATCH UPDATE and EXCLUSIVE UPDATE access do not update
               the snapshot files.  The fact that snapshots are not
               being maintained is recorded in the RDB$SYSTEM area.
               Hence, RDB$SYSTEM may not be READ_ONLY.

User Action:   Use another UPDATE access mode, or change RDB$SYSTEM to
               be READ WRITE.

S_ABW_DISABLED, Asynchronous Batch Write is Disabled

Explanation:   Used in show commands

User Action:  

S_ABW_ENABLED,  Asynchronous Batch Write is Enabled (clean buffers
               <num>, max buffers <num>)

Explanation:   Used in show commands

User Action:  

S_APF_DISABLED, Asynchronous Prefetch is Disabled

Explanation:   Used in show commands

User Action:  

S_APF_ENABLED,  Asynchronous Prefetch is Enabled (depth is <num>)

Explanation:   Used in show commands

User Action:  





                                 273






S_ENTRY,       Entry Point is:  <str>

Explanation:   Used in SHOW FUNCTION and SHOW PROCEDURE statements.

User Action:  

S_GB_PGVIADSK,  page transfer via disk)

Explanation:   Used in SHOW commands

User Action:   None.

S_GB_PGVIAMEM,  page transfer via memory)

Explanation:   Used in show commands

User Action:   None.

S_INCR_BACKUP,  Incremental Backup Scan Optim uses SPAM pages

Explanation:   Used in show commands

User Action:  

S_LOCATION,    External Location is:  <str>

Explanation:   Used in SHOW FUNCTION and SHOW PROCEDURE statements.

User Action:  

S_LOCK_DISABLED, Lock Partitioning is DISABLED

Explanation:   Used in show commands

User Action:  

S_LOCK_ED,      Reserving table <str> for exclusive data definition

Explanation:   Used in SHOW TRANSACTION statement.

User Action:  

S_LOCK_ENABLED, Lock Partitioning is ENABLED

Explanation:   Used in show commands

User Action:  

S_LOCK_PD,      Reserving table <str> for protected data definition



                                 274






Explanation:   Used in SHOW TRANSACTION statement.

User Action:  

S_LOCK_SD,      Reserving table <str> for shared data definition

Explanation:   Used in SHOW TRANSACTION statement.

User Action:  

S_NOINCR_BACKUP, Incremental Backup Scan Optim does not use SPAM pages

Explanation:   Used in show commands

User Action:  

S_SHUTDOWN_MINS, Shutdown Time is <num> minutes

Explanation:   Used in show commands

User Action:  

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.

TBLCOLAFT,     You specified both COLUMN and TABLE privileges with a
               POSITION or AFTER clause

Explanation:   You specified both COLUMN and TABLE privileges in a
               GRANT or REVOKE statement with a POSITION or AFTER
               clause.  Unless the ACLs are identical on both the
               column and the table, this could produce misleading
               results.

User Action:   Specify the column and table privileges in separate
               GRANT or REVOKE statements.

TBLCURDYN,     List cursor <str> cannot reference dynamic table
               cursor, <str>

Explanation:   The list cursor named in the message references a table
               cursor that is dynamic.

User Action:   The list cursors for the table cursor must also be



                                 275






               dynamic.

TBLNOPRIM,     The table does not contain a Primary Key

Explanation:   The table does not contain a primary key.  Therefore
               there is nothing to enable/disable.

User Action:   Do not specify primary key if there is none.

TBLNOTCUR,     Table <str> is not included in cursor <str>

Explanation:   An UPDATE or DELETE statement that uses the CURRENT OF
               clause must name the same table specified in the
               cursor.

User Action:   Either change the UPDATE or DELETE statement to use the
               table specified in the cursor, or use a cursor declared
               for the table you specified.

TBLREF_SELXPR, Correlation Name or select expression expected

Explanation:   Either a select expression or a correlation name is
               expected.

User Action:   Either add a correlation name or a select expression.
               Check parenthesis as they may not be matched correctly.

TERMINATE,     database recovery failed -- access to database denied
               by monitor

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



                                 276






               assistance.

THRESHIGNO,    Threshold clause with no specific storage area found in
               statement

Explanation:   You did not specify a storage area for the threshold
               clause.

User Action:   Please specify the storage area(s) or remove the
               threshold clause.

THRIGNSYS,     Threshold options ignored for system relation area

Explanation:   The storage area that contain the system relations must
               have UNIFORM page formats.  Either through the use of
               the defaults, or by directly specifing THRESHOLD
               options, SQL has been told to apply threshold options
               for the area containing the system relations.  SQL is
               ignoring those options.

User Action:   None.  This is an informational message.  The user
               might want to change the command if it originated in a
               command file.  This may avoid confusion later.

THRNOTALL,     Threshold buffers is not a valid option for Async
               Prefetch

Explanation:   The THRESHOLD option is only valid with DETECTED ASYNC
               PREFETCH and not with ASYNC PREFETCH.

User Action:   If you want the ASYNC PREFETCH feature, remove the
               THRESHOLD syntax.  If you want the DETECTED ASYNC
               PREFETCH feature, you must specify the DETECTED keyword
               and include the THRESHOLD syntax.

THRNOTSYS,     Theshold option not valid for system relation area

Explanation:   The storage area for RDB$SYSTEM was defined to have
               threshold options.  This is not allowed for RDB$SYSTEM.

User Action:   Remove the threshold option from the command and try
               again.

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.





                                 277






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

TOKINSBEF,     <str> inserted before error symbol

Explanation:   When parsing an SQL statement, the parser encountered
               an error.  The message for that error appeared prior to
               this message.  In an attempt to recover from that
               error, SQL inserted the specified token before the
               token that generated the error, and generated this
               message to help you understand any additional messages
               that follow.

User Action:   None.  This is an informational message only.

TOKTOOBIG,     Symbol name is too big

Explanation:   You entered a symbol (token) name with a length greater
               than 32.  The length of a symbol name must be less than
               or equal to 32 characters.

User Action:   Use a symbol with no more than 32 characters.

TOOBIGBLR,     Request BLR is too large to execute

Explanation:   Your request is too large to compile.

User Action:   Break the DML statement into smaller parts.

TOOMANYNAMES,  Too many levels of naming used without multischema

Explanation:   The user entered the name of an object which was
               qualified with too many names.  When multischema is
               disabled (the default), table names may be qualified
               only by a schema name; column names may be qualified
               only by a schema and table name.

User Action:   In order to qualify a schema name, table name or column
               name with an additonal name for the catalog,
               multischema must be enabled using the MULTISCHEMA
               compiler option or the SET MULTISCHEMA statement in
               interactive or dynamic.

TOOMANYTBL,    Table cursor, <str>, references more than one table

Explanation:   The table cursor named in the message references more
               than one table.

User Action:   Base the list on a table cursor that references only



                                 278






               single table.

TOO_MANY_SWITCHES, Too many command line switches have been specified

Explanation:   You have specified too many switches on the command
               line for UNIX sqlpre or sqlmod.

User Action:   Use fewer switches.

TRAACT,        A database cannot be attached while a transaction is
               active

Explanation:   You issued an ATTACH statement while a transaction was
               still in progress.

User Action:   You must either COMMIT or ROLLBACK the current
               transaction or wait until the current transaction is
               terminated before attaching another database.

TRAACT_1,      A database cannot be created or altered while a
               transaction is active

Explanation:   You issued a CREATE DATABASE or an ALTER DATABASE
               statement while a transaction was still in progress.

User Action:   You must either COMMIT or ROLLBACK the current
               transaction or wait until the current transaction is
               terminated before creating another database or altering
               an exsisting one.

TRAACT_2,      ROLLBACK or COMMIT the transaction

Explanation:   You are attempting an operation that cannot be executed
               while the current transaction is still in progress.

User Action:   You must either COMMIT or ROLLBACK the current
               transaction or wait until the current transaction is
               terminated before attempting the new database activity.

TRAACT_3,      A database cannot be dropped while a transaction is
               active

Explanation:   You issued a DROP DATABASE statement while a data
               manipulation transaction was still in progress.

User Action:   COMMIT or ROLLBACK the transaction, start a new
               transaction, and reissue the DROP DATABASE statement.

TRADBPNEWONL,  Database parameters are only allowed for new database



                                 279






Explanation:   You used one of the database parameter clauses in a
               transfer definition in which you used the TO EXISTING
               clause.  Database parameters are only allowed with the
               TO NEW FILENAME clause.

User Action:   Use the TO NEW FILENAME clause or omit the database
               parameters in the transfer definition.

TRAHDLINV,     Transaction handle data type invalid, must be 32-bit
               longword

Explanation:   You specified a transaction handle that was not a
               32-bit longword.

User Action:   You must use !VAL and 32-bit longword variable.

TRAMODSPC,     Only one transaction mode may be specified for a
               transaction

Explanation:   You specified both the READ_WRITE and READ_ONLY
               transaction modes in a DECLARE TRANSACTION statement.

User Action:   Specify either transaction mode, not both, for a single
               database.  You can specify different transaction modes
               for different databases in a single DECLARE TRANSACTION
               statement, however.

TRANOTOWNER,   This transfer is not the owner of <str> <str>

Explanation:   The transfer definition attempts to create an object
               which already exists in the target database and which
               is not owned by this transfer.  That is, it was not
               created by this transfer.

User Action:   If the objects are not expected to exist in the target
               database when the transfer will be executed, the
               WITHOUT CHECKING option will avoid this error.
               Otherwise, those objects must be dropped in the target
               database before the transfer may be created.

TRANSFDISTREP, DISTINCT is not allowed in queries moved by replication
               transfers

Explanation:   The user entered the DISTINCT keyword in a query as
               part of a CREATE TRANSFER statement which defined a
               replication transfer.

User Action:   Re-enter the statement without the DISTINCT keyword.





                                 280






TRANSFGRPBY,   GROUP BY is not allowed in queries moved by CREATE
               TRANSFER

Explanation:   The user entered a GROUP BY clause in a query as part
               of a CREATE TRANSFER statement.

User Action:   Re-enter the statement without the GROUP BY clause.

TRANSFHAVING,  HAVING is not allowed in queries moved by CREATE
               TRANSFER

Explanation:   The user entered a HAVING clause in a query as part of
               a CREATE TRANSFER statement.

User Action:   Re-enter the statement without the HAVING clause.

TRANSFSUBQRY,  Subqueries are not allowed in queries moved by CREATE
               TRANSFER

Explanation:   The user entered a subquery in a query as part of a
               CREATE TRANSFER statement.

User Action:   Re-enter the statement without the subquery.

TRANSFUNIONALL, ALL keyword must be specified for union in CREATE
               TRANSFER

Explanation:   The user failed to enter the ALL keyword after the
               UNION keyword in the select expression as part of a
               CREATE TRANSFER statemetn.

User Action:   Re-enter the statement with UNION ALL, not just UNION.

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.

TRATOEXEXTR,   Existing target database is not allowed for this
               transfer type

Explanation:   You used the TO EXISTING clause in a REPLICATION or
               EXTRACTION ROLLUP transfer definition.  This is only
               allowed for EXTRACTION transfers.  REPLICATION and
               EXTRACTION ROLLUP transfers must create a new database.





                                 281






User Action:   Use the EXTRACTION transfer type or the TO NEW FILENAME
               clause in the transfer definition.

TRATOEXPRIV,   Insufficient privilege to create tables in target
               database

Explanation:   You used to the TO EXISTING clause specifying a
               database for which you do not have the CREATETAB
               privilege.

User Action:   Use the TO NEW FILENAME clause, specify an existing
               target database for which you have the CREATETAB
               privilege, or obtain

TRATOEXRDB,    Existing target database must be a Oracle Rdb database
               if WITH CHECKING is specified.

Explanation:   You used the TO EXISTING clause specifying a database
               that is not an Oracle Rdb database and did not specify
               the WITH NO CHECKING clause.  The default is WITH
               CHECKING, however, this can only be used with Oracle
               Rdb databases.

User Action:   Use the WITH NO CHECKING clause in the transfer
               definition.

TREE_OVRFLO,   Tree storage overflow

Explanation:   The internal limit of the Abstract Syntax Tree (AST)
               nodes was exceeded.

User Action:   Contact your Oracle support representative.  Retain the
               query that caused the error.

TRIGNOTDEF,    Trigger <str> is not defined

Explanation:   The specified trigger does not exist in the specified
               schema.

User Action:   Check the spelling of the trigger name and ensure that
               it is the name of a trigger in the specified schema.

TRIG_EXISTS,   Trigger <str> already exists

Explanation:   You attempted to create a trigger in the specified
               schema with the name of an existing trigger in that
               schema.

User Action:   Choose a different name for the new trigger.



                                 282






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.

TRNNOTBLS,     No tables were found in the database or schema

Explanation:   The user entered MOVE TABLES *, but no tables were
               found.

User Action:   Re-enter the transfer definition for a schema which
               contains tables.

TRNNOVIEWS,    No views were found in the database or schema

Explanation:   The user entered MOVE VIEWS *, but no views were found.

User Action:   Re-enter the transfer definition for a schema which
               contains views, or omit the MOVE VIEWS clause.

TRUE,          condition value is true

Explanation:   None.

TRUNCATION,    data conversion truncation error

Explanation:   You attempted an operation that would cause loss of
               information on a data-item movement.

User Action:   Correct the error and try again.

TRUNCPARAM,    routine <str> expects between <num> and <num>
               parameter(s)

Explanation:   You may truncate the procedure or function parameter
               list when those parameters are IN parameters.  They
               will then use the defined DEFAULT or be passed as NULL.
               In this case you passed too few parameters.

User Action:   Specify the correct number of parameters upon
               invocation.

TRUNCPARAM0,   routine <str> expects no parameters

Explanation:   This routine expected no parameters.





                                 283






User Action:   Correct the routine definition, or remove the parameter
               list.

TRUNCPARAM1,   routine <str> expects <num> parameter(s)

Explanation:   You passed more parameters than was expected by this
               routine.

User Action:   Specify the correct number of parameters upon
               invocation.

TRUN_STORE,    String truncated during assignment to a column

Explanation:   The character string cannot be assigned to a column
               because the string is too long.  This error is only
               signaled if the truncated portion of the character
               string contains non-blank characters.

User Action:   Enter a shorter character string or alter the database
               column so that it is large enough to hold the full
               source string and recompile.

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.

TWOIMPTXN,     Attempt to declare second implicit transaction handle

Explanation:   An application linked against a shared image has more
               than one implicit transaction handle (PSECT
               RDB$TRANSACTION_HANDLE).  You altered the PSECT
               attributes during linking of the shared image to create
               two different transaction handles.

User Action:   Don't alter the PSECT attributes of the
               RDB$TRANSACTION_HANDLE PSECT.

TXNINATOMIC,   Transaction statements not allowed in atomic blocks

Explanation:   You have used a transaction statement (SET TRANSACTION,
               COMMIT, ROLLBACK) in a compound statement that
               specifies ATOMIC.

User Action:   Use transaction statements only in non-atomic blocks.



                                 284






TXNINFORLOOP,  Transaction statements not allowed in FOR loops

Explanation:   You have used a transaction statement (SET TRANSACTION,
               COMMIT, ROLLBACK) in a FOR loop.

User Action:   You cannot use transaction statements in FOR loops.

TXNNOTLONG,    Transaction handle is not a 32-bit longword.

Explanation:   Transaction handles must be defined using a 32-bit
               longword data type.

User Action:   Use a 32-bit longword to declare the transaction
               handle:  In COBOL, use PICTURE S9(9) COMP.  In PL/I,
               use FIXED BINARY(31).  In FORTRAN, use INTEGER*4.

TXN_HNDL_IGNORED, Transaction handle parameter ignored

Explanation:   Transaction handles currently are not supported.

User Action:   None; this is an informational message.

TYPE_EXISTS,   User defined type "<str>" already exists

Explanation:   A user defined type with the given name already exists.

User Action:   Use a different name when creating this type.

UDCURDEL,      Cursor in fetch, update or delete, positioned on a
               deleted record

Explanation:   You attempted to perform a positioned UPDATE or DELETE
               on a row that has already been deleted or you attempted
               to fetch a row that no longer exists.

User Action:   Do not attempt to FETCH, UPDATE or DELETE this row
               again.

UKN_ALT_OPT,   Unknown ALTER DATABASE option

Explanation:   The ALTER DATABASE statement contains an option that is
               not understood.

User Action:   Re-enter the statement with the syntax supported by
               this version of SQL.

UNAOBTDSR,     Unable to obtain database dsri level

Explanation:   SQL was unable to obtain the database information



                                 285






               needed to establish its level of DSRI compliance.

User Action:   Make sure that all individual databases are DSRI
               compliant

UNBCLSFIL,     Unable to close file <str>

Explanation:   SQL was unable to close an open file.  A problem such
               as running out of disk space or a hardware failure may
               be the cause.

User Action:   Correct the problem with the hardware resource.

UNBDECFIL,     Unable to create declarations file <str>

Explanation:   SQL attempted to open a DECLARATIONS file but could
               not.

User Action:   Include a valid directory specification and valid
               declarations name.

UNBTMPFIL,     Unable to open a temporary file called <str>

Explanation:   SQL attempted to open a temporary file.  It was either
               in the default directory or the directory specified
               with the /OBJ compile switch.

User Action:   Include a valid directory specification with protection
               level that allows temporary files to created in it.

UNBWRTFIL,     Unable to write to file <str>

Explanation:   SQL was unable to write to an open file.  A problem
               such as running out of disk space or a hardware failure
               may be the cause.

User Action:   Correct the problem with the hardware resource.

UNDEFVAR,      Variable <str> is not defined

Explanation:   You referenced a host variable which is not defined.

User Action:   Either define the variable, or specify the name of a
               variable which is already defined.

UNDERFLOW,     data conversion underflow

Explanation:   You attempted an operation that would cause loss of
               information on a data-item movement.



                                 286






User Action:   Correct the error and try again.

UNDPARAM,      Parameter <str> is not declared in procedure <str>

Explanation:   This error is generated in two situations.  In the
               first, a procedure referred to a parameter which was
               not declared in the procedure.  In the second, you used
               a column in a context where it could be a parameter
               reference and an indicator variable was specified (or a
               comma omitted).

User Action:   Define the parameter in the procedure, or use a
               parameter name which is defined in the procedure.

UNICONSNOTCB,  Computed column may not have UNIQUE constraint

Explanation:   You specified a unique constraint for a computed
               column, which does not support this constraint.

User Action:   Remove the unique constraint from this definition.

UNIKEYEXI,     Column <str> is already part of a unique key

Explanation:   You specified a unique key definition for a column
               which is already mentioned in a unique key.  A column
               may only be mentioned in one unique key.

User Action:   Enter the unique key definition without the column
               which was part of another unique key.

UNIONEXTROLL,  Unions are only allowed by EXTRACTION ROLLUP transfers

Explanation:   You have specified for an EXTRACTION or REPLICATION
               transfer a query which is a union.

User Action:   Use multiple select expressions to achieve the desired
               result.

UNIQNODUP,     The index <str> cannot be unique and have a duplicates
               clause

Explanation:   An index cannot be defined as UNIQUE and specify that
               DUPLICATES ARE SORTED or DUPLICATES ARE COMPRESSED.

User Action:   Remove either the UNIQUE syntax or the DUPLICATES ARE
               SORTED or DUPLICATES ARE COMPRESSED syntax.

UNISELLIS,     The standard requires the select lists of the selects
               for UNION to have the same number of columns



                                 287






Explanation:   The select lists of the two select expressions in this
               UNION have a different number of elements.  The ANSI
               and ISO SQL standards require that they have the same
               number of elements.

User Action:   If it is important to have only standard features in
               your program, you should change your selects to have
               the same number of items in the select list.

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



                                 288






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.

UNKTYPE,       <str> is based on an unknown type

Explanation:   You referred to a host variable which was based on a
               host language the SQL precompiler does not support.

User Action:   Base the host variable on a host language the SQL
               precompiler supports.

UNK_CMDLN_SWITCH, Unknown command line switch:  <str>



                                 289






Explanation:   The specified command line switch is not recognized and
               invalid for UNIX sqlpre or sqlmod.

User Action:   Remove the switch from the command line.

UNMATEND,      Unmatched end

Explanation:   The Pascal precompiler found more END statements than
               BEGIN statements.  The scope for all variable
               declaration and usage is at the global level.  This is
               caused by an error in the precompiler or an error in
               your program.

User Action:   Investigate if it is a error in your program.  If it is
               an error in the precompiler, then please contact your
               Oracle support representative.

UNSARITH,      expression includes unsupported arithmetic operation

Explanation:   The Boolean evaluator was processing an expression or
               sub-expression that contained an arithmetic operator.
               Arithmetic operators are not supported.

User Action:   Rewrite the expression in error without the arithmetic
               operator.

UNSCOMP,       unsupported data comparison

Explanation:   You attempted an operation that would compare two
               incommensurate data items.

User Action:   Correct the error and try again.

UNSCOMPBY,     <str>.<str> is not supported in this context

Explanation:   You included the COMPUTED_BY field named in this error
               message in the SELECT FIELDS clause of a DEFINE
               TRANSFER statement.  This COMPUTED_BY field uses a
               value expression that is unsupported.

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

UNSCONV,       unsupported data conversion

Explanation:   You attempted an operation that would cause loss of



                                 290






               information on a data-item movement.

User Action:   Correct the error and try again.

UNSDATASS,     Unsupported date/time assignment from <str> to <str>

Explanation:   You attempted an unsupported assignment between dates.

User Action:   Check the documentation for valid date assignments.
               The two dates must be comparable.  A secondary error
               message may provide a more precise reason for the
               error.  The CAST function might be an appropriate
               workaround for a data type mismatch.

UNSDATATYPE,   Host variable <str> is an unsupported data type

Explanation:   The host variable declaration uses a COMPLEX or REAL*16
               FORTRAN data type.  These data types are not supported.

User Action:   Either change the declaration so that only supported
               data types are used, or move the data to another data
               item which only uses supported data types.

UNSDATCVT,     Unsupported DATE conversion

Explanation:   You tried to ALTER a column with a datatype of DATE to
               a numeric datatype.  This is unsupported.

User Action:  

UNSDATXPR,     Unsupported date expression

Explanation:   You attempted an operation on a date that is not
               supported.

User Action:   Check the documentation for valid date expressions.  If
               you are using the preprocessors, you might be able to
               work around the limitation by using a temporary
               variable.

UNSDB2PRIV,    Unsupported DB2 privilege ignored

Explanation:   A GRANT or REVOKE statement specified a DB2 privilege
               which the SQL interface to Oracle Rdb does not support.

User Action:   None.  SQL ignores the unsupported privileges.

UNSDECLDTYP,   Unsupported datatype in DECLARE variable statement





                                 291






Explanation:   The data type for the DECLARE variable statement is not
               supported.  This applies to the interactive DECLARE
               variable statement and the multistatement procedure
               DECLARE variable statement.  This message is also
               generated if the DECLARE variable statement uses a
               DOMAIN whose data type is unsupported.

User Action:   Declare the variable with a supported data type or
               supported domain data type.

UNSDSCCLA,     Unsupported descriptor class <num>

Explanation:   The class of the descriptor in an input parameter is
               not supported by the SQL interface to Oracle Rdb.

User Action:   Use class S, D, DS, or VS.

UNSDTPCVT,     Unsupported data type conversion

Explanation:   A dynamic SQL program tried to get SQL to perform a
               data type conversion which it does not support.  For
               example, a date field was fetched into a numeric field.
               The SQL dynamic interface does not support conversions
               from date to numeric.

User Action:   Change the data type used to pass data to or from the
               dynamic interface to a data type which can be converted
               to the data type of the data in the database.

UNSFIXINT,     <str> must specify an unscaled fixed numeric

Explanation:   The specified quantity must be a fixed numeric literal,
               parameter, or host variable.  This could be the
               position or length of a SUBSTRING.

User Action:   Change the quantity to be an unscaled fixed numeric
               data type.  If the message specifies SUBSTRING, change
               the position or length of the SUBSTRING to be an
               unscaled fixed numeric data type.

UNSIGNED_VAR,  Host variable <str> is an unsigned variable which is
               illegal is SQL statements.

Explanation:   The named variable is defined as an C unsigned
               variable.  Unsigned variables are illegal in SQL
               statements.

User Action:   Use a signed version of this variable in the SQL
               statement.



                                 292






UNSINTXPR,     Unsupported interval expression

Explanation:   You attempted an operation that is not supported on an
               interval value expression.

User Action:   Check the documentation for valid interval expressions.
               The FOR cursor loop requires that all intervals be
               single field.  e.g.  INTERVAL DAY

UNSLOBASS,     Unsupported data type conversion from <str> to <str>

Explanation:   You attempted an unsupported conversion.

User Action:   LIST OF BYTE VARYING types may not be converted to the
               target type that was given.  Revise the application to
               perform the conversion in a different way.

UNSNUMXPR,     Unsupported numeric expression

Explanation:   You attempted an operation that is not supported on a
               numeric value expression.  For example:  numeric =
               numeric || numeric;

User Action:   Check the documentation for valid numeric expressions.
               If you are using the preprocessors, you might be able
               to work around the limitation by using a temporary
               variable.

UNSPLIATT,     Host variable <str> uses an unsupported PLI attribute

Explanation:   The host variable declaration uses a PLI attribute
               which is not supported.

User Action:   Either change the declaration so that only supported
               attributes are used, or move the data to another data
               item which only uses supported attributes.

UNSSTRXPR,     Unsupported string expression

Explanation:   You attempted an operation on a string that is not
               supported.  For example:  string = string + string;

User Action:   Check the documentation for valid string expressions.
               If you are using the preprocessors, you might be able
               to work around the limitation by using a temporary
               variable.

UNSSUPDAT,     Unsupported data type requested





                                 293






Explanation:   You requested input or output of an unsupported data
               type from the dynamic interface.

User Action:   You should review the data types of the variables in
               the dynamic statement and change the offending data
               type to a supported data type.

UNSUPCDD,      Feature is not supported for version of CDD

Explanation:   You are attempting to use a feature that requires
               version 5.4 or higher of CDD.

User Action:   Refrain from using this feature or upgrade to at least
               CDD V5.4.

UNSUPOP,       Operation supported for read-write databases only

Explanation:   You attempted to perform data definition or updates on
               an Rdb Transparent Gateway to DB2 or Rdb Transparent
               Gateway to Oracle database.  Rdb Transparent Gateway to
               DB2 or Rdb Transparent Gateway to Oracle databases are
               read-only.

User Action:   Do not issue any CREATE, INSERT, UPDATE, or DELETE
               statements with an Rdb Transparent Gateway to DB2 or
               Rdb Transparent Gateway to Oracle database.

UNSUPVER,      Operation is unsupported for version of database.

Explanation:   You tried to do something with a pre-V3.1 database that
               requires version 3.1 or higher.  This can happen when
               Rdb/Remote is used to access a database of a different
               version than that of the database system.

User Action:   Convert the database to the current version of Rdb or
               do not attempt the operation that caused the problem.

UNTERM_C_STR,  Missing null terminator for C string

Explanation:   C strings must be terminated with the null terminator.
               The string in this program was not terminated properly.

User Action:   Change the string to terminate properly.

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.





                                 294






UNTSTR,        Unterminated string found

Explanation:   The matching quote (" or ') for a string was not found.

User Action:   Re-enter statement with matching quote character.

UPDCOLPRIV,    UPDATE(column-name) privilege is not supported

Explanation:   UPDATE(column-name) is a DB2 privilege not supported by
               the SQL interface to Oracle Rdb.  UPDATE privilege will
               be granted on the entire table.

User Action:   None.

UPDINSCUR,     Cursor <str> is an INSERT ONLY cursor

Explanation:   The cursor referenced in the statement was defined as
               INSERT ONLY.  Thus, UPDATE, FETCH and DELETE statements
               are illegal.

User Action:   Either change either the cursor declaration to UPDATE,
               or do not attempt to update the cursor.

UPDREACUR,     Cursor <str> is read-only

Explanation:   A cursor is read-only if it includes a DISTINCT phrase,
               a aggregate function, a GROUP BY, HAVING, or UNION, or
               more than one table in its FROM clause.  Read-only
               cursors cannot include FOR UPDATE clauses and cannot be
               used in UPDATE or DELETE statements.

User Action:   Either change whatever made the cursor read-only, or do
               not attempt to update the cursor.

USERALREXI,    User <str> already exists in the database

Explanation:   The specified user already exists in the specified
               database.

User Action:   Check the spelling of the user name and ensure that it
               is a unique name of a user in the specified database.

USERINVIEW,    USER literals are not permitted in DDL statements

Explanation:   SQL cannot store a USER literal in a ddl object such as
               a view or a constraint.

User Action:   You must either explicitly specify the user name as
               string literal in the select list of the view



                                 295






               definition, or specify USER in a query outside of the
               view definition.

USERNOTDEF,    User <str> is not defined

Explanation:   The specified user does not exist in the specified
               database.

User Action:   Check the spelling of the name of the user and ensure
               that it is the name of a user in the specified
               database.

USEUNOPTAIJ,   please use original unoptimized AIJ file for this
               recovery operation

Explanation:   The requested recovery operation is not compatible with
               an optimized AIJ file.  See the accompanying message
               for the cause of the incompatability.

User Action:   Use the original, non-optimized AIJ file to do the
               recovery.

USINGCTXNOTALL, USING CONTEXT is not allowed for this statement

Explanation:   Your source contains a USING CONTEXT clause with a
               statement that does not allow that clause.

User Action:   Remove the USING CONTEXT clause from the statement.

USINGCTXREQ,   USING CONTEXT is required for this statement

Explanation:   Your source doesn't contains a USING CONTEXT clause
               with a statement that requires one.

User Action:   Add the USING CONTEXT clause for the statement.

USRDEFTYP,     Host variable <str> is of an unknown user defined type

Explanation:   The named variable is of a user defined type that
               wasn't defined within the pre-compilation unit.  User
               defined types must be defined in the same
               pre-compilation unit for them to be legal.

User Action:   Use a different variable or include the type definition
               in the pre-compilation unit.

VAL_TRIG,      VALIDATE must not be specified when enabling Triggers

Explanation:   In the ALTER TABLE statement, if you specify enable



                                 296






               validate, you cannot specify triggers.  If you wish to
               enable triggers, do not specify either VALIDATE or
               NOVALIDATE.

User Action:   Respecify the ALTER TABLE statement

VARNOTUSED,    Variable "<str>" was declared but never used

Explanation:   This variable was declared by the module, or routine
               but was never referenced.

User Action:   SQL will eliminate this declaration.  This is just an
               informational message to aid in application
               development.

VECNOTIND,     Host variable <str> is a vector but is not used as an
               indicator structure

Explanation:   The host variable is defined as a vector
               (one-dimensional array).  SQL only allows references to
               vectors if they are used as indicator variables for
               host structures (such indicator variables are also
               called indicator structures or indicator vectors).

User Action:   Either change the host variable declaration so it is
               not an array, or move the data from the array to a
               variable that is not an array.

VEWNOTDEF,     View <str> is not defined in database or schema

Explanation:   The specified view does not exist in the current
               database or schema.

User Action:   Attach the proper database schema.  Spell the view name
               correctly.  You may have specified an expression where
               a view name was expected.

VOID_HV,       Host variable <str> is of type void, which is illegal
               in SQL statements

Explanation:   The named variable is defined as a C variable of
               datatype 'void'.  These variables are currently not
               supported by the C precompiler.

User Action:   Use a different variable or specify a supported
               datatype.

VRP_ILLEGAL_STORE, Storage Map "<str>" specified STORE COLUMNS after a
               STORE



                                 297






Explanation:   In a vertical row partitioned storage map, all the
               STORE COLUMNS clauses must precede the optional catch
               all STORE clause.

User Action:   Specify the STORE COLUMNS clauses first, then if
               desired a single STORE clause.

WAIMODSPC,     Only one wait mode may be specified for a transaction

Explanation:   You specified both wait modes in a DECLARE TRANSACTION
               statement.

User Action:   Specify either WAIT or NOWAIT, not both, in a DECLARE
               TRANSACTION statement.

WARDET,        A warning was detected

Explanation:   This is the exit status for a preprocessor when an
               warning was detected.

User Action:   Correct the error in the host language program and
               resubmit the job to the preprocessor.

WARNINGCB,     column attributes and data will be lost on commit

Explanation:   You used the ALTER statement to change a column into a
               computed column.  Because of the way this is
               implemented, all attributes and data existing before
               the ALTER statement will be lost when you issue a
               COMMIT statement.

User Action:   If this behavior is unexpected, use the ROLLBACK
               statement to undo the effects of the ALTER statement.

WASBOOL,       expression in CONTAINS or MATCHES was a Boolean

Explanation:   The Boolean evaluator was processing an expression or
               sub-expression of the form "A CONTAINS B" or "A MATCHES
               B".  Either the "A" or the "B" expression was a Boolean
               of the form "NOT X", "X EQ Y", "X NE Y", "X LT Y", "X
               GT Y", "X LE Y", "X GE Y", "X CONTAINS Y", or "X
               MATCHES Y".  Neither side of CONTAINS and MATCHES
               expressions are allowed to be Boolean expressions.

User Action:   Rewrite the expression to have the proper format.

WHYTWICE,      Column <str> is specified more than once in the column
               list of a constraint.





                                 298






Explanation:   You specified the same column more than once in the
               column list of a UNIQUE, PRIMARY KEY or FOREIGN KEY
               constraint.  Alternatively, you specified the column in
               more than one NOT NULL constraint.

User Action:   Specify each column only once.  Check the CREATE or
               ALTER TABLE command and remove the redundant reference.

WILDALLWILD,   Wildcard may not be followed by non-wildcard

Explanation:   A CREATE TRANSFER statement was entered with a MOVE
               TABLES clause which specified a wildcard followed by a
               non-wildcard.  For example, A.*.*.B is not allowed;
               A.*.*.* is allowed.

User Action:   Change the MOVE TABLES clause to make use of
               wildcarding at all subsequent levels once wildcarding
               has begun.

WISHLIST,      Feature not implemented yet

Explanation:   The action you requested requires a feature that is not
               implemented in the current version of the product.

User Action:   Do not request such an action.

WISH_LIST,     Feature not yet implemented - <str>

Explanation:   The action you requested requires a feature that is not
               implemented in the current version of this product.

User Action:   Try to work around the unimplemented feature.

WRICIRREF,     A subquery in an INSERT, UPDATE or DELETE statement
               referenced the subject table

Explanation:   You tried to use the same table in an INSERT, UPDATE or
               DELETE statement both as the target and in a subquery.
               The current ANSI and ISO SQL standards do not permit
               this.

User Action:   If it is important to use only standard features in
               your program, you should remove the subquery which
               references the subject table.

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



                                 299






               area ID number and the page numbers of the first and
               last pages being read.

User Action:   Examine the associated messages to determine the reason
               for failure.  One possible cause for this error is
               disabling logging for the WORM area and subsequently
               restoring that area from an earlier backup.

WRMDEVFUL,     WORM device full for area <str>

Explanation:   The area is marked as "WORM device full," because a
               previous attempt to extend this WORM area failed.

User Action:   Consider adding more areas to the storage map or moving
               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.

WRONGARGS,     procedure <str> called with wrong number of argument

Explanation:   The named procedure was called with the wrong number of
               arguments.

User Action:   Call the procedure with the right number of arguments.

XIDNOTFOUND,   specified XID could not be found in the database

Explanation:   The specified XID was not found in the database.
               Either the XID was never in the unresolved state, or it
               has since been resolved with the resolution that had
               been supplied earlier.

User Action:   Check the appropriate transaction manager log for more
               information.

XPR_STACK_OVFL, expression forces too many levels of recursion/stack
               overflow

Explanation:   You provided an expression which forces too many levels



                                 300






               of recursion, which resulted in stack overflow.

User Action:   The expression should be rewritten to use parentheses
               and therefore cause fewer levels of recursion.  It may
               also be possible to increase the size of the stack.

ZABORT,        User entered Control-Z to abort statement

Explanation:   You typed a Control-Z to abort the current statement.

User Action:   None.

ZEROLENCHAR,   Nonstandard character string length

Explanation:   A zero (0) length string was specified

User Action:   A zero (0) length string is not supported by the
               standard specified.  Specify a length of 1, or do not
               use the flagger.

ZEROSIZE,      Size value is zero.

Explanation:   You have supplied a zero value in a context that does
               not allow such a value.  You specified SIZE IS 0 for an
               index key compression in CREATE INDEX statement,
               INCREMENT BY 0 for a CREATE SEQUENCE or ALTER SEQUENCE
               statement, or IDENTITY with a 0 for the increment-by
               parameter in a CREATE TABLE or ALTER TABLE statement.

User Action:   Use a non-zero value.  SIZE IS requires a value great
               than zero, sequences and IDENTITY require any value
               except zero.





































                                 301