Replication Option is a software product that lets you
distribute whole databases, or parts of them, to target
directories on the same or different nodes in a network. The
source database for extraction and extraction rollup target
databases can be a DSRI-compliant database such as Oracle Rdb or
one of the Oracle data access products, known as gateways.
Note that RDO does not support all the latest Replication Option
features. Oracle recommends that you use the SQL interface instead
of RDO because SQL is an industry-standard database access language
and only SQL supports all the latest Replication Option features.
1 – Release Notes
To see the current Release Notes for Replication Option, type
or print the following file:
SYS$HELP:DDALvvu.RELEASE_NOTES
where vv = version and u = update
For example:
SYS$HELP:DDAL060.RELEASE_NOTES
2 – Error msg doc
Errors returned by Replication Option are documented online
in the file SYS$HELP:DDAL$MSG.DOC, which you can PRINT, TYPE, or
SEARCH at DCL level.
3 – EXTRACTION
Specifies that Replication Option create an extraction
database at the target site. Because each extraction database
is independent of the source database, users at the target
directory can access extraction databases with either read-only
or read/write transactions. Each time an extraction transfer
executes, Replication Option creates a new version of the
target database and transfers a complete copy of the selected
records to the target node.
Indexes, constraints, and access rights are not transferred when
the target database is created. Once the target database has been
created, you can define views, indexes, and constraints for it
and modify the access rights. Refer to the Replication Option
Handbook for more information about extraction databases.
4 – EXTRACTION_ROLLUP
Specifies that Replication Option create an extraction rollup
database at the target site with records selected from one or
more source databases. Because each extraction rollup database is
independent of the source database, users at the target directory
can access extraction rollup databases with either read-only or
read/write transactions. Each time an extraction rollup transfer
executes, Replication Option creates a new version of the
target database and transfers a complete copy of the selected
records to the target node.
Indexes, constraints, and access rights are not transferred when
the target database is created. Once the target database has been
created, you can define indexes and constraints for it and modify
the access rights. Refer to the Replication Option Handbook for
more information about extraction databases.
5 – REPLICATION
Specifies that Replication Option create a replication database
at the target site. When a replication transfer executes,
Replication Option creates a database at the target site during the
initial execution and supplies updates to it during subsequent
transfers. In addition, the execution of a replication transfer
might create special-purpose relations in the source database and
the target database to handle updating.
Refer to the Replication Option Handbook for specific
information about these special database entities. Because the
source database is modified with the addition of these new system
relations, the user who defined the transfer needs the DEFINE
access right to the source database.
After Replication Option creates the target database and
transfers the data records to it, users are expected to access
the replication database to retrieve data only. Applications
should not attempt to store, modify, or erase values in records
of the replication database.
6 – SHOW_TRANSFER
Displays information about the transfer definition, schedule
definition, the transfer status, or all these transfer
attributes. When you enter the SHOW TRANSFER statement, you can
display information about one transfer or all transfers.
NOTE
The RDO SHOW TRANSFER statement does not display transfer
protection, the checkpoint attribute, or the NO DELETE
attribute that may have been established for a transfer
definition using SQL. You must issue the SQL SHOW TRANSFER
statement to display these attributes.
6.1 – Format
(B)0[m[4mSHOW[m [4mTRANSFER[m qqqq> transfer-attribute qqqk
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqqqqq> [4mFOR[m qqqwqqq> [4mALL[m qqqqqqqqqqqqwqqq>
mqqq> transfer-name qqj
6.1.1 – transfer-attribute
(B)0[mtransfer-attribute =
qqqwqqq> [4mDEFINITION[m qqqqqwqqqq>
tqqq> [4mSCHEDULE[m qqqqqqqu
tqqq> [4mSTATUS[m qqqqqqqqqu
mqqq> [4mALL[m qqqqqqqqqqqqj
The type of information you want displayed about the selected
transfer or all transfers.
6.1.1.1 – DEFINITION
Displays transfer definition information for the specified
transfer or for all transfers.
6.1.1.2 – SCHEDULE
Displays schedule definition information for the specified
transfer or for all transfers.
6.1.1.3 – STATUS
Displays the following status information for the specified
transfer or for all transfers:
o Transfer name
o State of the current transfer (unscheduled, scheduled, active,
waiting-to-retry, retrying, suspended)
o Time the transfer entered its current transfer state
o Last transfer status
o Time the last successful transfer completed
o Next scheduled transfer time (for transfers in the scheduled
or waiting-to-retry state)
o Number of the currently executing retry (for transfers in the
retrying state)
o Number of the next retry (for transfers in the waiting-to-
retry state)
6.1.1.4 – ALL
Displays all information about the definition, schedule, and
status for the specified transfer or for all transfers.
6.1.2 – ALL
Specifies that you want Replication Option to display
information about all transfers associated with your UIC. For
transfers belonging to other UICs, Replication Option displays
only the transfer name. To display information about transfers
belonging to other UICs, you must have OpenVMS BYPASS or READALL
privilege.
6.1.3 – transfer-name
The transfer about which you want Replication Option to display
information.
7 – DELETE_SCHEDULE
Deletes the schedule definition associated with a transfer
definition. You can delete a schedule definition only when the
associated transfer is in the suspended state. Refer to the
STOP TRANSFER statement for information about how to suspend a
transfer. If you issue a START TRANSFER statement after deleting
the schedule, the transfer will be placed in the unscheduled
state.
7.1 – Format
(B)0[m[4mDELETE[m [4mSCHEDULE[m qq> FOR qqq> transfer-name qqqqqq> .
7.1.1 – transfer-name
Identifies the transfer whose schedule is to be deleted. The
transfer-name parameter is required.
7.2 – More
You must execute the DELETE SCHEDULE statement outside of the
scope of a transaction. If you issue this statement when a
transaction is outstanding, Replication Option returns an error
message.
If a transfer has a schedule definition, DELETE TRANSFER also
deletes the corresponding schedule definition. If you want to
delete a transfer schedule, the schedule definition must be
associated with your UIC.
7.3 – Example
This example places the NH_EMPLOYEES transfer in a suspended
state and then deletes the associated schedule.
RDO> STOP TRANSFER NH_EMPLOYEES
RDO> DELETE SCHEDULE FOR NH_EMPLOYEES.
8 – DELETE_TRANSFER
Deletes a transfer definition. If a transfer has a schedule
definition, DELETE TRANSFER also deletes the corresponding
schedule definition.
8.1 – Format
(B)0[m[4mDELETE[m [4mTRANSFER[m qqq> transfer-name qqqq> .
8.1.1 – transfer-name
The transfer definition to be deleted. The transfer-name
parameter is required.
8.2 – More
To issue the DELETE TRANSFER statement, the transfer definition
you delete must be associated with your UIC or you must have the
DROP transfer privilege or the OpenVMS BYPASS privilege.
You must execute the DELETE TRANSFER statement outside of the
scope of a transaction. If you issue this statement when a
transaction is outstanding, Replication Option returns an error
message.
You can delete a transfer only if the transfer is in the
suspended state. Refer to the STOP TRANSFER statement for
information about how to suspend a transfer.
When you delete a transfer definition, the associated target
database does not change in any way.
8.3 – Example
The following example suspends the MA_EMPLOYEES transfer and then
deletes its definition:
RDO> STOP TRANSFER MA_EMPLOYEES
RDO> DELETE TRANSFER MA_EMPLOYEES.
9 – DEFINE_TRANSFER
Creates a transfer definition and stores it in the transfer
database. A transfer definition contains all the information
necessary to select a set of records from the source database
and to define a target database. A transfer definition also can
contain the views to be defined on the target database and the
command procedures to be executed before and after the execution
of the transfer.
A source database for extraction transfers can be Oracle Rdb, or
a database accessed through one of the Rdb Transparent Gateways.
For replication transfers, the source database must be an Oracle Rdb
database.
NOTE
The DEFINE TRANSFER statement, unlike the SQL CREATE
TRANSFER statement, cannot be used to define transfers
to existing databases (including replication transfers
with the NO DELETE attribute). It also does not provide
a checkpoint clause. Furthermore, unlike the SQL CREATE
TRANSFER statement, the RDO utility does not support the
MIA character set attributes. It is possible to create a
transfer definition using RDO and name a database containing
MIA features. However, the character set attributes of the
resulting target database might not be correct.
Use of RDO is recommended only when you want to manipulate
databases that use only the DEC_MCS character set for
text data.
9.1 – Format
(B)0[m[4mDEFINE[m [4mTRANSFER[m qq> transfer-name qqwqqq> [4mREPLICATION[m qqqqqqqqqwqqk
tqqq> [4mEXTRACTION[m qqqqqqqqqqu x
mqqq> [4mEXTRACTION[m [4mROLLUP[m qqqj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqwq>qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwqq> [4mTO[m qq> file-spec qk
mq> [4mDESCRIPTION[m IS q> /* text */ qj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqwq>qqqqqqqqqqqqqqqqqqqqqqqwqwqwq>qqqqqqqqqqqqqqqqqqqqqqqqqqqqqwqwqk
mq>target-db-param-clauseqj x tq>move-relations-clause qqqqqqqu x x
x tq>move-views-clause qqqqqqqqqqqu x x
x mq>move-relations-rollup-clauseqj x x
mqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqwqqqqqqqqqq>qqqqqqqqqqqqqqqqqqqqqqqqqwqqqqqqqqqqqqqqqqqqqqqqqqqqk
mqqq> transfer-file-options-clause qqj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqq> [4mEND[m qqqwqqqqqqqqq>qqqqqqqqqwqqwqqqqqqq>qqqqqqwqqqqqqq> .
mq> transfer-name qqj mq> [4mTRANSFER[m qqj
9.1.1 – transfer-name
Identifies the transfer by name. The transfer name must be unique
across all of the nodes at a given VAXcluster or VMScluster site
because a single transfer database serves all nodes in a cluster
environment. For example, you could have two users on the same
server attempting to create a transfer called PERS_REC. One user
would succeed while the other would receive an error message
saying that the transfer already exists. To ensure that names
are unique, you may wish to make the user identifier part of each
transfer name.
A valid transfer name has the following characteristics:
o Has a length from 1 to 31 bytes (octets).
o Can be formed using any of the set of ASCII characters:
A B C ... Z 0 1 2 ... 9 _ $ a b c ... z
Lower case letters may be used, but are treated as if they
were uppercase.
o Cannot include letters with diacritical marks (which are used
in European languages for instance).
o The first character of the name must either be a letter or the
dollar sign ($). However, Oracle Corporation recommends that you do not
use dollar signs in a transfer name; dollar signs are reserved
for special use by Digital Equipment Corporation.
The transfer-name parameter is required.
9.1.2 – REPLICATION
Specifies that Replication Option create a replication database
at the target site. When a replication transfer executes,
Replication Option creates a database at the target site
during the initial execution and maintains a connection to that
target database so the source can supply updates to the target.
Subsequent transfers involve only those modifications that have
been made to the selected records in the source database. (If the
target and source database should become inconsistent with each
other, you can use the REINITIALIZE TRANSFER statement to restore
consistency.)
In addition, the execution of a replication transfer generally
creates special-purpose relations in the source database and the
target database to handle updating. Because the source database
is modified with the addition of these system relations, the
transfer definer's account needs the DEFINE access right to the
source database itself.
Users are expected to access the replication target database
only to retrieve data. Applications should not attempt to store,
modify, or erase values in records of the replication database.
Although data values should not be manipulated in a replication
database, you can modify the target database by defining views
and indexes, and adding access rights.
9.1.3 – EXTRACTION
Specifies that Replication Option create an extraction
database at the target site. Because each extraction database
is independent of the source database, users at the target
directory can access extraction databases with read/write as
well as read-only transactions. Each time an extraction mode
transfer executes, Replication Option creates a new version of
the target database and transfers a complete copy of the selected
records to the target node.
Indexes, constraints, and access rights are not transferred
when the target database is created. Similarly, primary key
and foreign key attributes for a particular relation are
not transferred because key attributes are implemented as
constraints. Once the target database has been created, you can
define indexes, constraints, and triggers for it and modify the
access rights.
9.1.4 – EXTRACTION_ROLLUP
Specifies that Replication Option create an extraction rollup
database at the target site by transferring selected relations
and fields from one or more source databases into a single
target database. An extraction rollup database is created at the
target site, and Replication Option reads data from the source
databases and stores the data in a target database.
Each time an extraction rollup transfer is executed, Replication
Option creates a new version of the target database and
transfers to it a complete copy of the selected records.
The EXTRACTION ROLLUP option in the DEFINE TRANSFER statement has
the following characteristics and limitations:
o Replication Option issues an error message if you do not
enter a MOVE RELATION clause or a SELECT FIELDS list in a
move-relations-rollup-clause.
o You must refer to each source database in the DEFINE TRANSFER
statement by its database handle.
o On the target database, relation names and field names must
be unique. Consequently, all target relations of the same name
must have the same definition, and all target fields of the
same name must have the same data type. If the definitions
or data types differ, Replication Option issues an error
message and the transfer fails.
o If any database specified in the transfer definition is on a
node that is not available, Replication Option places the
transfer in a waiting-to-retry state. Replication Option
will retry the transfer at the time specified for retry in the
schedule definition.
o If any of the source nodes specified in the transfer
definition fail during the transfer, the transfer will also
fail. Replication Option will retry the transfer at the time
specified for retry in the schedule definition.
o If the transfer fails, the retry will start at the beginning,
not where the transfer left off.
Indexes, constraints, and access rights are not transferred
when the target database is created. Similarly, primary key
and foreign key attributes for a particular relation are
not transferred because key attributes are implemented as
constraints. Once the target database has been created, you can
define indexes, constraints, and triggers for it and modify the
access rights.
9.1.5 – text
A text string that allows you to associate a comment with the
transfer definition. The text string, together with other
parts of the transfer definition, appears in the SHOW TRANSFER
DEFINITION display. The DESCRIPTION IS clause is optional.
9.1.6 – file-spec
Designates a file specification for the target database, which
is an Oracle Rdb database. Replication Option uses the file
specification to create and access the target database. You can
use either a full or partial file specification or a logical
name. The file-spec parameter is required. If you do not specify
the node, device, or directory, Replication Option assumes the
SYS$LOGIN of the user defining the transfer. If the file type
is not .RDB, the transfer will fail during the creation of the
target database. The default file type is .RDB.
When you specify the name of a remote node as part of the file
specification, you can include an access control list (ACL) for
login. However, the most effective method of allowing access to a
target node uses proxy accounts.
If you use DECnet/OSI note that Replication Option expects node
names in file specifications to be from one to six characters
long. DECnet/OSI permits node names to be much longer than this.
In order to use Replication Option in a DECnet/OSI environment,
you must define and use short synonyms for the long node names.
Node name synonyms can be registered either in a local or
distributed name service database. For details on establishing
node name synonyms, refer to the documentation for DECnet/OSI.
Note that the file specification is resolved at run time. All
logical names used for the file-spec parameter are resolved
within the copy process after it executes the transfer definer's
login initialization file, LOGIN.COM. If the target database
name is a logical symbol name, when it is translated, the default
directory is the one pointed to by SYS$LOGIN.
Replication Option makes no attempt to verify whether a
database or file of the same name already exists in the target
directory. When you issue a duplicate file specification,
Replication Option creates a second file with the same name, but a
higher version number.
If the database system (Oracle Rdb) returns an error while
attempting to create a database in the target directory, the
copy process writes the error in the copy process log file and
returns the error status to the transfer monitor.
9.1.7 – target-db-param-clause
(B)0[mtarget-db-param-clause =
qqqwqwq>qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwqwqq>
x tq> [4mALLOCATION[m IS qqqqqqqq> number-pages qq> PAGES qqqqu x
x tq> [4mPAGE[m [4mSIZE[m IS qqq> page-blocks qqqqqq> BLOCKS qqqqqqu x
x tq> [4mNUMBER[m OF [4mBUFFERS[m IS qq> number-buffers qqqqqqqqqqqu x
x tq> [4mNUMBER[m OF [4mUSERS[m IS qqqq> number-users qqqqqqqqqqqqqu x
x tq> [4mBUFFER[m [4mSIZE[m IS qq> buffer-blocks qqq> BLOCKS qqqqqqu x
x tq> [4mEXTENT[m IS qqqqqqqqqqwq> ext-pages qqq> PAGES qqqwqqu x
x x mq> (multi-vol-ext-clause) qj x x
x tq> [4mSNAPSHOT[m IS qqqqwq> [4mENABLED[m qwq> [4mIMMEDIATE[m qqwqwqqqu x
x x x mq> [4mDEFERRED[m qqj x x x
x x mq> [4mDISABLED[m qqqqqq>qqqqqqqqqqqj x x
x tq> [4mSNAPSHOT[m [4mALLOCATION[m IS q> snp-pages q> PAGES qqqqqqu x
x mq> [4mSNAPSHOT[m [4mEXTENT[m IS qw> ext-pages qqqq> PAGES qqqqwqj x
x m> (multi-vol-ext-clause) qqqj x
mqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqj
Enables you to specify values for the parameters that affect
the creation of the target database. This clause uses syntax
similar to the Oracle Rdb DEFINE DATABASE statement. However,
Replication Option does not support all the parameters that DEFINE
DATABASE supports. Replication Option uses the values provided
in this clause to create the target database.
9.1.7.1 – number-pages
The number of database pages initially allocated to the target
database. Oracle Rdb automatically extends the allocation to handle
the loading of data and subsequent expansion. The default is 400
pages. If you are transferring a large number of records, a large
page allocation helps to prevent fragmented records.
9.1.7.2 – page-blocks
The size in blocks of each database page in the target directory.
Page size is allocated in 512-byte blocks. The default is two
blocks (1024 bytes). If your largest record has more than
approximately 950 bytes, you can specify more blocks for each
page to prevent records from being fragmented.
9.1.7.3 – number-buffers
The number of buffers Oracle Rdb allocates for each process using
the target database. The value must be greater than zero. The
default is 20 buffers.
9.1.7.4 – number-users
The maximum number of users allowed to access the target database
at one time. The default is 50 users. After the maximum is
reached, the next user who tries to invoke the database receives
an error message and must wait for access. The largest number of
users you can specify is 508, and the smallest is 1.
9.1.7.5 – buffer-blocks
The number of blocks Oracle Rdb allocates for each buffer. The value
must be greater than zero. If you do not specify this parameter,
Oracle Rdb uses a buffer size that is three times the page size
value.
9.1.7.6 – ext-pages
The number of pages of each target database extent. This
parameter provides direct control over the extent of the
target database. For greater control, and particularly for
multivolume databases, use the MINIMUM, MAXIMUM, and PERCENT
GROWTH parameters of the multi-vol-ext-clause instead. The
default extent is 100 pages.
9.1.7.7 – ENABLED_IMMEDIATE
Specifies that READ_WRITE transactions write previously updated
copies of records they modify to the snapshot file, regardless
of whether a read-only transaction is active. Snapshot writing
is enabled immediately by default. With snapshots enabled, users
or applications can read from either the snapshot file or the
database file itself.
9.1.7.8 – ENABLED_DEFERRED
Specifies that READ_WRITE transactions not write previously
updated copies of records they modify to the snapshot file unless
a READ_ONLY transaction is already active. READ_ONLY transactions
that attempt to start after an active READ_WRITE transaction
must wait for all active READ_WRITE users to complete their
transactions. With snapshots enabled, users or applications can
read from either the snapshot file or the database file itself.
9.1.7.9 – DISABLED
Specifies that snapshot writing be disabled. There is usually
some performance gain when snapshot writing is disabled because
Oracle Rdb does not need to perform write operations to the snapshot
file during updates to the database.
You should not disable snapshots for replication databases.
Although users are expected only to retrieve data from the
replication database, retrieval can occur in either READ_ONLY
or READ_WRITE transactions.
9.1.7.10 – snp-pages
The number of pages allocated for the snapshot file. The default
is 100 pages. After the target database has been created, you can
use the RDO CHANGE DATABASE statement to truncate the snapshot
file. To truncate the file, specify an allocation size smaller
than the current snapshot file size.
9.1.7.11 – multi-vol-ext-clause
(B)0[mmulti-vol-ext-clause =
qqqqq> [4mMINIMUM[m OF qq> min-pages qqq> PAGES, qk
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqq> [4mMAXIMUM[m OF qq> max-pages qqq> PAGES, qk
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqq> [4mPERCENT[m [4mGROWTH[m IS qqq> growth qqqq>
9.1.7.11.1 – min-pages
The minimum number of pages of each target database extent. The
default is 100 pages.
9.1.7.11.2 – max-pages
The maximum number of pages of each target database extent. The
default is 10,000 pages.
9.1.7.11.3 – growth
The percent of growth for each target database extent. The
default is 20 percent growth.
9.1.8 – move_relations_clause
(B)0[mmove-relations-clause =
qwqq> [4mMOVE[m [4mRELATIONS[m [4mALL[m qqqqqqqqqqqqqqqqqqqqqqq>qqqqqqqqqqqwqqqq>
x x
mqwqq> [4mMOVE[m [4mRELATION[m qqwqqqqqqqqqqqqqqqwqq> rse qqqqqqk x
x mq> /* text */ qj x x
x lqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqj x
x mq> [4mSELECT[m [4mFIELDS[m qwqq> [4mALL[m qqqqqqqq>qqqqqqqwqqwqqj
x mwq> select-field-name qwj x
x mqqqqqqqq , <qqqqqqqqqqj x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq ; <qqqqqqqqqqqqqqqqqqqj
Selects the records Replication Option transfers to the target
database during an extraction or a replication transfer. The
records selected for replications are specified with a restricted
form of a record selection expression (RSE). You must specify a
move-relations-clause for each user relation moved to the target
database. If you do not include a move-relations-clause, Replication
Option assumes the default, MOVE RELATIONS ALL.
When you specify a view in a MOVE RELATION clause, the records
selected by that view are created as a relation in the target
database. You can also transfer views using the move-views-
clause.
You must have READ privilege for the relations of an Oracle Rdb
source database that you specify in a MOVE RELATION clause or
a MOVE RELATIONS ALL clause. For databases accessed through the
Rdb Transparent Gateways, Replication Option does not check for
READ privilege for views.
9.1.8.1 – MOVE_RELATIONS_ALL
Allows you to have Replication Option select all records and
fields from all user relations, excluding views, that are in
the source database at the time the transfer is defined. If
you wish to move views, you must use the move-views-clause or
the MOVE RELATION clause. Fields defined with a COMPUTED_BY
clause are restricted to those that use the value expressions
shown in the value-expr syntax diagram in this section. If a
field is not defined by a supported value expression, you will
receive a warning message, and the COMPUTED_BY fields will not be
transferred.
If you define a transfer on a source database that is itself a
target extraction database, do not use the MOVE RELATIONS ALL
clause. An error will result during transfer execution because
Replication Option will attempt to define the DDAL$VINTAGE
relation in the new target database twice. The second transfer
would create a DDAL$VINTAGE relation in the target database.
Then, using the MOVE RELATIONS ALL clause, it would attempt to
copy the DDAL$VINTAGE relation that already exists in the source
database. To avoid this error, specify explicitly each relation
to be moved instead of using MOVE RELATIONS ALL.
Do not use the MOVE RELATIONS ALL statement for an extraction
rollup transfer. If you use the MOVE RELATIONS ALL statement to
define an extraction rollup transfer, the transfer will fail on
execution. Instead, you must name the individual relations you
want to transfer to the extraction rollup target.
9.1.8.2 – text
A text string that allows you to associate a comment with the
transfer definition. The text string, together with other parts
of the transfer definition, appears in the SHOW DEFINITION
display. The DESCRIPTION IS clause is optional.
9.1.8.3 – rse
The record selection expression (RSE) used to identify records
from the source database that Replication Option includes in
a record stream and transfers to the target database. The RSE
specifies conditions that individual records must satisfy in
order to be included in the transfer to the target database.
Replication Option supports COMPUTED_BY fields named in an RSE
if the fields are defined using the value expressions shown in
the value-expr syntax diagram in this section. If the fields are
not defined by a supported value expression, you will receive a
fatal error message.
In extraction, extraction rollup, and replication transfers,
you can use a relation-clause and with-clause. In extraction and
extraction rollup transfers, you can also use a first-clause,
reduce-clause, and sort-clause.
9.1.8.4 – SELECT_FIELDS_ALL
Enables you to include every field in a specific relation. Fields
defined with a COMPUTED_BY clause are restricted to those that
use the value expressions shown in the value-expr syntax diagram
in this section. If a field is not defined by a supported value
expression, you will receive a warning message, and the COMPUTED_
BY fields will not be transferred. You cannot use the SELECT
FIELDS ALL statement for an extraction rollup transfer.
9.1.8.5 – select-field-name
(B)0[mselect-field-name =
qqqqqqqq> context-variable qq> . qqq> field-name qqqqq>
Allows you to name a specific field or group of fields you want
moved to the target database. You can specify only one SELECT
clause for each MOVE clause. Replication Option moves only the
named fields to the target database. If you do not specify SELECT
FIELDS ALL, the select-field-name clause is required.
Replication Option supports COMPUTED_BY fields named in the
select-field-name clause if the fields are defined using the
value expressions shown in the value-expr syntax diagram in
this section. If the fields are not defined by a supported value
expression, you will receive a fatal error message.
9.1.9 – move-views-clause
(B)0[mmove-views-clause =
qqqq> [4mMOVE[m [4mVIEWS[m qqwqq> [4mALL[m qqqqqqqqqqqwqqq>
mwq> view-name qqwqqj
mqqqqqq , <qqqqqqj
Selects the views Replication Option defines on the target
database during an extraction or a replication transfer. All the
relations, views, and fields on which the transferred views are
based must also be explicitly or implicitly named in the DEFINE
TRANSFER statement. The transfer definition will fail if any
underlying relation, view, or field is not named when you define
the transfer. Note that, if you omit the move-relations-clause,
relations are implicitly named in the transfer definition because
MOVE RELATIONS ALL is the default.
If you specify a view name in this clause, the view definition
is transferred to the target database. You can include only one
move-views-clause in a DEFINE TRANSFER statement. However, you
can specify two or more views in that move-views-clause.
Transferring views is limited by the following restrictions:
o COMPUTED_BY fields
Replication Option transfers those COMPUTED_BY fields that
depend only on the values of the relation in which the field
is defined. Views that contain unsupported COMPUTED_BY fields
cannot be transferred. If views that contain unsupported
COMPUTED_BY fields are specified in the move-views-clause
of a DEFINE TRANSFER statement, the transfer definition fails.
You need to redefine the transfer, excluding the views that
refer to the unsupported COMPUTED_BY fields.
o READ privilege for the view
For a view in an Oracle Rdb database to be transferred, Replication
Option requires that you have Oracle Rdb READ privilege for
the view and for the underlying relations. If you do not have
READ privilege for views you specify in the move-views-clause
of a DEFINE TRANSFER statement, the transfer will fail. You
need to obtain READ privilege for these views before including
them in a DEFINE TRANSFER statement.
For databases accessed through the Rdb Transparent Gateways,
Replication Option does not check for READ privilege for views.
You can also move views with the move-relations-clause. However,
when you use the move-relations-clause to move a view, the view
becomes a relation in the target database.
9.1.9.1 – view-name
The name of the view Replication Option transfers to the target
during a transfer. If you do not specify a view name, Replication
Option assumes the default, MOVE VIEWS ALL.
9.1.10 – move-relations-rollup-clause
(B)0[mmove-relations-rollup-clause =
qwq> [4mMOVE[m [4mRELATION[m qqqqwqqqqqqqq>qqqqqqqqwq> rse qqqqwqqqqwq>
x mq> / *text*/qqqqqj x x
x lqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqj x
x mqqwqqqqqqqqqqqqqqqqqqqqqq>qqqqqqqqqqqqqqqqqqqwqk x
x mq> [4mINTO[m [4mRELATION[m qqqq> relation-name qqqqqj x x
x lqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqj x
x mq> [4mSELECT[m [4mFIELDS[m qqwqq> select-field-name qqqqqwqwqj
x mqqqqqqqqqq , <qqqqqqqqqqqqqj x
mqqqqqqqqqqqqqqqqqqqqqqqqqqq ; <qqqqqqqqqqqqqqqqqqqqqqqj
Selects the records Replication Option transfers into the
target database from a number of source databases during an
extraction rollup transfer. The move-relations-rollup-clause
has the following restrictions:
o Replication Option requires you to invoke each source
database with a different database handle. You must then use
these handles in the move-relations-rollup-clause to identify
tables of each source database.
o The move-relations-rollup-clause must be used with the
EXTRACTION ROLLUP parameter.
Rollup transfers must be extractions. If you attempt to use
the move-relations-rollup-clause with a replication transfer,
the transfer definition will fail.
o The MOVE RELATIONS ALL and SELECT FIELDS ALL clauses are not
allowed in rollup transfers.
9.1.10.1 – rse
For more information on record selection expression, select the
subtopic RSE under the DEFINE_TRANSFER Format subtopic.
9.1.10.2 – select-field-name
(B)0[mselect-field-name =
qqqqqqqq> context-variable qq> . qqq> field-name qqqqq>
Allows you to name a specific field or group of fields you want
moved to the target database. You can specify only one SELECT
clause for each MOVE clause. Replication Option moves only the
named fields to the target database. If you do not specify SELECT
FIELDS ALL, the select-field-name clause is required. All fields
that you name in the record selection expression (RSE) must also
be named in the SELECT FIELDS clause.
Replication Option supports COMPUTED_BY fields named in the
select-field-name clause if the fields are defined using the
value expressions shown in the value-expr syntax diagram in
this section. If the fields are not defined by a supported value
expression, you will receive a fatal error message.
9.1.11 – transfer-file-options-clause
(B)0[mtransfer-file-options-clause
qwqwqqqqqqqqqqqqqqqqqqqqqqqqq>qqqqqqqqqqqqqqqqqqqqqqqqqqqwqqqqqqq>
x tqq> [4mPROLOGUE[m FILE IS qqqq> prologue-file-spec qqqqqqqu
x tqq> [4mNOPROLOGUE[m qqqqqqqqqq>qqqqqqqqqqqqqqqqqqqqqqqqqqqu
x tqq> [4mEPILOGUE[m FILE IS qqqq> epilogue-file-spec qqqqqqqu
x tqq> [4mNOEPILOGUE[m qqqqqqqqqq>qqqqqqqqqqqqqqqqqqqqqqqqqqqu
x tqq> [4mLOG[m FILE [4mIS[m qqqqqqqqq> log-file-spec qqqqqqqqqqqqu
x mqq> [4mNOLOG[m qqqqqqqqqqqqqqq>qqqqqqqqqqqqqqqqqqqqqqqqqqqu
mqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqj
The DCL command procedures to be executed before or after
transfers and the OpenVMS file where logging information related
to the transfer execution is located.
9.1.11.1 – prologue-file-spec
The name of the prologue command procedure file to be run before
the transfer executes. This file runs at the beginning of the
first execution of the transfer and of all subsequent transfers.
The prologue file is a DCL command file. You can include a
version number and a remote node name in the file specification.
The name is resolved when the transfer is defined.
The prologue-file-spec parameter is optional. If you do not
include this parameter, Replication Option assumes that
NOPROLOGUE is in effect. The default file type is .COM. The
default directory for the prologue file is SYS$LOGIN.
If your file specification includes a node name and you are using
DECnet/OSI, note that Replication Option expects node names
in file specifications to be from one to six characters long.
DECnet/OSI permits node names to be much longer than this. In
order to use Replication Option in a DECnet/OSI environment,
you must define and use short synonyms for the long node names.
Node name synonyms can be registered either in a local or
distributed name service database. For details on establishing
node name synonyms, refer to the documentation for DECnet/OSI.
9.1.11.2 – epilogue-file-spec
The name of the epilogue command procedure file to be run after
the transfer executes. This file runs after the first execution
of the transfer and after all subsequent transfers. The epilogue
file is a DCL command file. You can include a version number or a
remote node name in the file specification. The name is resolved
when the transfer is defined.
The epilogue-file-spec parameter is optional. If you do not
include this parameter, Replication Option assumes that
NOEPILOGUE is in effect. The default file type is .COM. The
default directory for the epilogue file is SYS$LOGIN.
If your file specification includes a node name and you are using
DECnet/OSI, note that Replication Option expects node names
in file specifications to be from one to six characters long.
DECnet/OSI permits node names to be much longer than this. In
order to use Replication Option in a DECnet/OSI environment,
you must define and use short synonyms for the long node names.
Node name synonyms can be registered either in a local or
distributed name service database. For details on establishing
node name synonyms, refer to the documentation for DECnet/OSI.
9.1.11.3 – log-file-spec
The OpenVMS file where the Replication Option copy process
writes any logging information related to the execution of the
transfer. If you include a version number or a node name in the
file specification, Replication Option returns an error.
Replication Option creates a new log file every time a transfer
executes. The name is resolved when the transfer is defined.
The log-file-spec parameter is optional. If you do not include
this parameter, Replication Option assumes that NOLOG is in
effect. The default file type is .LOG. The default directory for
the log file is SYS$LOGIN.
9.1.12 – RSE
(B)0[mrse =
qqwqqqqqqqq>qqqqqqqqwqq> relation-clause qq>qqqqqqqqqqqqqqqqqqqqk
mq> first-clause qj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mwqqqqqqq>qqqqqqqqwqwqqqqqqqq>qqqqqqqqqqwqqwqqqqqqqq>qqqqqqqqwqqq>
mq> with-clause qj mq> reduce-clause qqj mq> sort-clause qqj
The record selection expression (RSE) used to identify records
from the source database that Replication Option includes in
a record stream and transfers to the target database. The RSE
specifies conditions that individual records must satisfy in
order to be included in the transfer to the target database.
Replication Option supports COMPUTED_BY fields named in an RSE
if the fields are defined using the value expressions shown in
the value-expr syntax diagram in this section. If the fields are
not defined by a supported value expression, you will receive a
fatal error message.
In extraction, extraction rollup, and replication transfers,
you can use a relation-clause and with-clause. In extraction and
extraction rollup transfers, you can also use a first-clause,
reduce-clause, and sort-clause.
9.1.12.1 – first-clause
(B)0[mfirst-clause =
qqqq> [4mFIRST[m qqqqqq> value-expr qqqqqqqqqqq>
(B)0[mvalue-expr =
qqqqqqqwqqqq> database-field qqqqqqwqq>
tqqqq> quoted-string qqqqqqqu
tqqqq> numeric-literal qqqqqu
tqqqq> arithmetic-expr qqqqqu
tqqqq> missing-value qqqqqqqu
tqqqq> concat-expr qqqqqqqqqu
tqqqq> ( value-expr ) qqqqqqu
mqqqq> q qq> value-expr qqqj
Specifies how many records are selected from the record stream
formed by the record selection expression (RSE). You can only
use the first-clause for an extraction or an extraction rollup
transfer. If you specify a first-clause for a replication
transfer, Replication Option issues an error message.
9.1.12.2 – relation-clause
(B)0[mrelation-clause =
q> context-variable q> [4mIN[m wqqqqqqqq>qqqqqqqqwq> relation-name q>
m> db-handle q> . j
The context variables and relations to be included in the record
stream or loop.
If you specify a view name in the relation-clause, the moved view
becomes a relation in the target database.
The context-variable supplies a temporary name to identify the
record stream. Once you have associated a context-variable with
a relation, you use the context-variable to refer to fields from
that relation.
The db-handle is a host variable or name used to refer to a
specific database you have invoked.
In extraction or replication transfers, you should not use
database handles in the RSE of a MOVE RELATION clause. Replication
Option returns an error message if you include a database
handle in the RSE. However, in an extraction rollup transfer, you
must use database handles in the RSE to specify the relation or
Replication Option will return an error message.
9.1.12.3 – with-clause
(B)0[mwith-clause =
qqqqqqqqqqqqq> [4mWITH[m qqqqqqqqqq> conditional-expr qqqqqqqqqqq>
(B)0[mconditional-expr =
qwqqq> conditional-expr qq> [4mAND[m qq> conditional-expr qqqwqqq>
tqqq> conditional-expr qq> [4mOR[m qqq> conditional-expr qqqu
tqqqqqqqqqqqqqqqqqqqqqqqq> [4mNOT[m qq> conditional-expr qqqu
tqqq> value-expr1 qq> rel-oper qq> value-expr2 qqqqqqqqu
tqqq> between-clause qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
tqqq> containing-clause qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
tqqq> matching-clause qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
tqqq> starting-with-clause qqqqqqqqqqqqqqqqqqqqqqqqqqqqu
mqqq> missing-clause qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
The with-clause contains a conditional expression that allows
you to specify conditions that must be true for a record to be
included in a record stream.
9.1.12.4 – reduce-clause
(B)0[mreduce-clause =
qqqqqqqqqqqqqq> [4mREDUCED[m [4mTO[m qqqwqqqqq> value-expr qqqwqqqqq>
mqqqqqqqq , <qqqqqqqqqj
(B)0[mvalue-expr =
qqqqqqqwqqqq> database-field qqqqqqwqq>
tqqqq> quoted-string qqqqqqqu
tqqqq> numeric-literal qqqqqu
tqqqq> arithmetic-expr qqqqqu
tqqqq> missing-value qqqqqqqu
tqqqq> concat-expr qqqqqqqqqu
tqqqq> ( value-expr ) qqqqqqu
mqqqq> q qq> value-expr qqqj
Allows you to eliminate duplicate values for fields in a record
stream. You can use the reduce-clause for an extraction or an
extraction rollup transfer. If you specify a reduce-clause for
a replication transfer, Replication Option issues an error
message.
9.1.12.5 – sort-clause
(B)0[msort-clause =
qqq> [4mSORTED[m [4mBY[m qqwqwqqqqqqqqqqqqqqqqqqwqqqqq> value-expr qqwqqq>
x tqq> [4mASCENDING[m qqqqu x
x mqq> [4mDESCENDING[m qqqj x
mqqqqqqqqqqqqqqqqqqqqqq , <qqqqqqqqqqqqqqqj
(B)0[mvalue-expr =
qqqqqqqwqqqq> database-field qqqqqqwqq>
tqqqq> quoted-string qqqqqqqu
tqqqq> numeric-literal qqqqqu
tqqqq> arithmetic-expr qqqqqu
tqqqq> missing-value qqqqqqqu
tqqqq> concat-expr qqqqqqqqqu
tqqqq> ( value-expr ) qqqqqqu
mqqqq> q qq> value-expr qqqj
Allows you to sort the records in the record stream by the values
of specific fields. You can sort the records according to a
value expression called a sort key. The sort key determines the
order of the records in the record stream. You can use the sort-
clause for an extraction or an extraction rollup transfer. If
you specify a sort-clause for a replication transfer, Replication
Option issues an error message.
Specifying ASCENDING (the default) causes the records to be
sorted in ascending order. Specifying DESCENDING causes Oracle Rdb
to sort the records in descending order.
The value expression specifies the sort value. This value is
called the sort key.
9.2 – More
After you issue the DEFINE TRANSFER statement, the transfer does
not execute until one of the following events occurs:
- The time specified in the corresponding DEFINE SCHEDULE
statement arrives
- You issue a START TRANSFER NOW statement
You cannot alter a transfer using RDO. You must either drop
the transfer and re-create it, or use the SQL ALTER TRANSFER
statement.
You must have READ privilege for the relations and views of a
Oracle Rdb source database that you specify in a DEFINE TRANSFER
statement. Replication Option returns an error message when you
specify relations and views in a DEFINE TRANSFER statement for
which you do not have READ privilege. Replication Option does not
check for READ privilege for relations and views when you specify
a database accessed through the Rdb Transparent Gateways.
You must execute the DEFINE TRANSFER statement outside of the
scope of a transaction. If you issue this statement when a
transaction is outstanding, Replication Option returns an error
message.
You can refer to relations, fields, and views in a DEFINE
TRANSFER statement either implicitly or explicitly. When you
include either the MOVE RELATIONS ALL, SELECT FIELDS ALL, or
MOVE VIEWS ALL clause, you refer to relations, fields, or views
implicitly. Replication Option uses the current definitions
of the relations, fields, and views in the source database and
stores those names explicitly in the transfer definition. You
refer to relations, fields, and views explicitly when you include
the MOVE RELATION, SELECT FIELDS, or MOVE VIEWS clauses and
supply specific relation, field, or view names.
All fields that you name in the record selection expression (RSE)
of the DEFINE TRANSFER statement must also be included in the
SELECT FIELDS clause. If you do not name the fields explicitly
in the SELECT FIELDS select-field-name statement or implicitly
in the select-field-name clause, Replication Option returns
an error message when the transfer executes, indicating that the
field name is not found in the symbol table.
Replication Option transfers those COMPUTED_BY fields that
depend only on the values of a relation in which the field is
defined. You cannot transfer views that contain unsupported
COMPUTED_BY fields. If views that contain unsupported COMPUTED_
BY fields are specified in the move-views-clause of a DEFINE
TRANSFER statement, the transfer definition fails. You need to
redefine the transfer, excluding the views that refer to the
unsupported COMPUTED_BY fields.
Replication Option allows you to transfer views in two ways:
o Using the move-views-clause
Replication Option transfers the definition of the view
when you specify MOVE VIEWS view-name or MOVE VIEWS ALL. You
must also explicitly or implicitly name in the DEFINE TRANSFER
statement all the relations, views, or fields on which the
transferred view definitions are based. The transfer will fail
if any underlying relations, views, or fields are not named.
o Using the move-relations-clause
Replication Option transfers a view by creating a relation
in the target database containing the view's records when
you use the MOVE RELATION clause. This method improves query
performance in the target database. For example, you can
achieve the effect of a CROSS clause by transferring a view
that is a CROSS in the source.
You specify the relations you wish to move in the move-relations-
clause and the views in the move-views-clause of the DEFINE
TRANSFER statement. When you are doing an extraction rollup
transfer, you specify the relations you wish to move in the
move-relations-rollup-clause of the DEFINE TRANSFER statement.
The same clause can occur in a DEFINE TRANSFER statement no more
than once. You cannot specify the same relation or view more than
once in the move clauses. If a relation name or view name appears
in more than one move clause, Replication Option returns an
error.
Individual move-relations clauses are separated by semicolons,
as indicated in the syntax diagrams. You can implement the move-
relations-clause in two ways:
o Specify MOVE RELATIONS ALL
o Specify a series of relations separated by semicolons
The move-relations-clause has the following characteristics and
limitations:
o All fields in each move-relations-clause must reside in the
same relation.
o You cannot name the same relation in more than one MOVE clause
of a single transfer definition.
The move-relations-rollup-clause has the following
characteristics and limitations:
o All fields in each move-relations-rollup-clause must reside in
the same relation.
o You cannot name the same relation in more than one MOVE clause
of a single transfer definition.
o For each relation of a move-relations-rollup-clause that you
enter, you can supply a target relation specification in the
form of an INTO RELATION clause. You can create one or many
relations in the target database from several source database
relations by renaming the target relations in the transfer
definition.
o You cannot specify MOVE RELATIONS ALL or SELECT FIELDS ALL in
a move-relations-rollup-clause. When you specify these clauses
in the DEFINE TRANSFER statement, the transfer will fail at
the time of definition.
The format of record selection expressions (RSE) that you can
include in a transfer definition for extraction and extraction
rollup transfers is more limited than the RSE allowed by RDO. You
cannot include the following expressions and clauses in the RSE
of the MOVE clause of the DEFINE TRANSFER statement:
o CROSS clause
o ANY operator
o UNIQUE operator
o Host variable
o Statistical expressions
o FIRST FROM expression
o Database key values
o Segmented string expressions
You can specify FIRST clauses, REDUCED clauses, and SORTED BY
clauses in the RSE of both extraction and extraction rollup
transfers. You can achieve the effect of a CROSS clause in an
extraction or an extraction rollup transfer by transferring a
relation, that is itself a view, defined in the source database
as a cross of two or more relations.
The next example shows an extraction transfer definition that
specifies the FIRST, REDUCED, and SORTED BY clauses in the RSE.
The transfer also achieves the capability of a CROSS clause by
moving a view, CURRENT_SALARY. In the source database, CURRENT_
SALARY is a cross of the EMPLOYEES, SALARY_HISTORY, and JOB_
HISTORY relations.
RDO> INVOKE DATABASE FILENAME PERSONNEL
RDO> DEFINE TRANSFER SALARY_HISTORY EXTRACTION
cont> TO NEWNODE::NEWDISK:[NEWDIR]EMP_SALARY
cont> MOVE RELATION FIRST 1000 E IN EMPLOYEES
cont> REDUCED TO E.LAST_NAME
cont> SORTED BY ASCENDING E.LAST_NAME
cont> SELECT FIELDS ALL;
cont> MOVE RELATION C IN CURRENT_SALARY SELECT FIELDS ALL
cont> LOG IS FIRSTDISK:[FIRSTDIR]EMP_SALARY.LOG
cont> END.
Because you cannot use certain expressions to identify required
records, the resulting groups of records transferred to the
extraction database might be larger than the number of extracted
records users will actually use. However, local users on
the target node can then include precise RSEs accessing the
extraction database.
The format of an RSE that you can include in the transfer
definition for replication transfers is more limited than the
RSE allowed by RDO. You cannot include the following forms of
expressions or clauses in the RSE of the MOVE clause of the
DEFINE TRANSFER statement:
o FIRST clause
o CROSS clause
o REDUCED clause
o SORTED BY clause
o ANY operator
o UNIQUE operator
o Host variable
o Statistical expressions
o FIRST FROM expression
o Database key values
o Segmented string expression
Because you cannot use certain expressions to identify required
records, the resulting groups of records transferred to the
replication database might be larger than the number of records
users will actually use. However, local users on the target node
can then include precise record selection expressions when using
RDO to access the replication database.
If a transfer fails during execution, the transfer will begin
again at the next scheduled retry time if the failure results
from a nonfatal error.
This next transfer will start from the beginning to ensure
consistency with any updates that might have been made to the
source database.
Replication Option transfers only definitions for the database,
fields, and relations specified in the transfer definition. If
the source database includes additional database entities such
as indexes, constraints, or access control lists, these are not
transferred to the target database. You must either directly
access the individual target database and explicitly define these
entities or run command procedures to define the entities after
the transfer executes.
When relations specified in the transfer definition are created
in the target database, they are given the access control lists
(ACLs) that have the Oracle Rdb default values. You can change the
ACLs in the target database after it has been created.
Replication Option does not support SQL ANSI-style privileges.
Target databases that Replication Option creates use the
default Oracle Rdb ACL-style privileges. SQL ANSI-style privileges
assigned to a source database are not copied to or preserved on
target databases during transfers.
In a transfer definition, you can use logical symbol names to
name the source database file, the target database file, the
copy process log file, and the prologue and the epilogue command
procedure files. However, Replication Option treats these file
names differently:
o Source database file logical names
If the source file name is a logical symbol that translates
to a standard OpenVMS file name specification, Replication
Option performs the logical name translation. The
SHOW TRANSFER DEFINITION statement shows the source file
name in its translated form. The logical symbol can also
translate into strings that, in turn, contain logical symbols.
As long as the resulting string looks like a OpenVMS file
specification and the logical symbol is not a concealed device
name, the translation process is repeated.
If the logical symbol translates into an Rdb Transparent Gateway
access string (for example, /TYPE=VIDA/FILE=ACCESS_FILE/...),
Replication Option does no further translations. Even if
the VIDA name string contains logical symbol references,
these references are not translated into OpenVMS file
specifications. You can use a logical name in place of the
string to identify an Rdb Transparent Gateway database.
o Target database file logical name
If the target database name is a logical name, it is not
translated by Replication Option when it is stored in the
transfer definition.
o Copy process log file logical name
Replication Option translates the log file logical name in
the same way as source file logical names, with the following
exceptions:
o The log file specification is translated in RDO when the
DEFINE TRANSFER statement is executed.
o These log file names must be standard OpenVMS file
specifications. Node names or version numbers are not
allowed.
o Prologue and epilogue command procedure file logical names
Replication Option translates the prologue and epilogue file
logical names in the same way as the source file logical name,
with the following exceptions:
o The prologue and epilogue file specifications are
translated in RDO when the DEFINE TRANSFER statement is
executed.
o The log file names must be standard OpenVMS file
specifications. Node names and version numbers are
allowed. Replication Option expects node names in file
specifications to be from one to six characters long.
DECnet/OSI permits node names to be much longer than
this. In order to use Replication Option in a DECnet/OSI
environment, you must define and use short synonyms for
the long node names. Node name synonyms can be registered
either in a local or distributed name service database. For
details on establishing node name synonyms, refer to the
documentation for DECnet/OSI.
Prior to Rdb/VMS Version 3.1, data values for text fields were
sorted in ascending or descending order based on the ASCII
character set. With Rdb/VMS Version 3.1 and higher (and Oracle Rdb
Version 5.0 and higher), you can create databases that specify
different sort sequences on a field-by-field basis. You can
specify the default for the database as a whole. Replication Option
has not enhanced transfer definitions to handle collation
sequences in any way. In addition, target databases created by
Replication Option do not have the collation sequence attributes
defined. Sorting in a target database remains ASCII-based.
Currently, there is no way that users can transfer default
collation sequences for fields or databases.
In an extraction transfer, you can change table definitions
in the source database or definitions of columns on which the
transferred tables are based. However, those changes are not
reflected in the transfer definition.
In replication transfers, you can make such changes until the
initial transfer begins. Thereafter, any attempts to change
or delete definitions for tables or columns in the replication
transfer are not allowed, with the exception of the following
four column attributes; these attributes can be modified even
after the initial transfer begins:
o Edit string
o Default value for DATATRIEVE
o Query name for DATATRIEVE
o Query header
However, note that if you do change the attributes listed in a
source column, a comparable change is not made automatically to
the target database column. If you want that to happen, you must
make the change in both the source and the target databases.
In both extraction and replication transfers, if you make changes
that cause the source tables or columns to be incompatible
with the transfer definitions, Replication Option detects these
differences at the time of transfer execution. The transfer
fails, the transfer status reflects the failure, and the transfer
is suspended.
However, with extractions or initial replications, the copy
process does not detect changes to the data type of a field.
For example, you can change a field from the data type CHAR to
the data type INTEGER without causing a failure.
9.3 – Examples
Example 1
The following example defines a transfer, NH_EMPLOYEES, that
creates an extraction database. The transfer definition selects
New Hampshire employees' address records for transfer to the
remote node.
RDO> INVOKE DATABASE FILENAME PERSONNEL
RDO> DEFINE TRANSFER NH_EMPLOYEES EXTRACTION
cont> DESCRIPTION IS /* Employees who live in New Hampshire */
cont> TO NODE1::DISK1:[ADAMS]NH_EMP
cont> MOVE RELATION E IN EMPLOYEES WITH E.STATE = "NH"
cont> SELECT FIELDS E.EMPLOYEE_ID,
cont> E.LAST_NAME,
cont> E.FIRST_NAME,
cont> E.MIDDLE_INITIAL,
cont> E.ADDRESS_DATA_1,
cont> E.ADDRESS_DATA_2,
cont> E.CITY,
cont> E.STATE,
cont> E.POSTAL_CODE
cont> LOG IS NH_EMPLOYEES.LOG
cont> END.
Example 2
This example shows an extraction from a remote source database to
a local target database. The DEFINE TRANSFER statement specifies
the transfer of all personnel records to the target node.
RDO> INVOKE DATABASE FILENAME NODE1::DISK1:[DIR1]PERSONNEL
RDO> DEFINE TRANSFER PERS_EXAMP EXTRACTION
cont> DESCRIPTION IS /* Extraction of personnel records*/
cont> TO [LEARNER.PERS]PERS_COPY
cont> MOVE RELATIONS ALL
cont> LOG IS [LEARNER.PERS]PERS_EXAMP.LOG
cont> END.
Example 3
This example shows an extraction transfer from a remote source
to a remote target database. The log file, PERS_EXAMP.LOG, is
located on the source node.
RDO> INVOKE DATABASE FILENAME NODE1::DISK1:[DIR1]PERSONNEL
RDO> DEFINE TRANSFER PERS_EXAMP EXTRACTION
cont> DESCRIPTION IS /* Extraction of personnel records*/
cont> TO NODE2::DISK2:[PROTO]PERS_TARGET
cont> MOVE RELATIONS ALL
cont> LOG IS PERS_EXAMP.LOG
cont> END.
Example 4
This example of a replication transfer definition sends the
entire colleges relation and the entire degrees relation to the
target database. The replication database can be accessed for
information about employees' college and degree histories. The
transfer definition includes some database parameters for the
target database.
RDO> INVOKE DATABASE FILENAME PERSONNEL
RDO> DEFINE TRANSFER COLLEGE_INFO REPLICATION
cont> DESCRIPTION IS /* Info about employees' colleges only */
cont> TO NODE1::DISK1:[BURTON]EMP_COLLEGE
cont> NUMBER OF USERS IS 25
cont> SNAPSHOT ALLOCATION IS 150 PAGES
cont> MOVE RELATION C IN COLLEGES
cont> SELECT FIELDS ALL;
cont> MOVE RELATION D IN DEGREES
cont> SELECT FIELDS ALL
cont> LOG IS COLLEGE_INFO.LOG
cont> END.
Example 5
This replication transfer specifies three fields from the CREDIT_
CARDS source database for transfer to the target database. The
fields are CARD_NUM, EXPIRATION_DATE, and VALID. Only invalid
credit card records are selected for the transfer.
RDO> DEFINE TRANSFER BAD_CARDS REPLICATION
cont> DESCRIPTION IS /* Invalid credit cards */
cont> TO NODE1::DISK1:[CREDIT]BAD_CARDS
cont> MOVE RELATION C IN CARDS WITH C.VALID = "N"
cont> SELECT FIELDS C.CARD_NUM,
cont> C.EXPIRATION_DATE,
cont> C.VALID
cont> LOG IS BAD_CARDS.LOG
cont> END.
Example 6
The following example defines a replication transfer that sends
the entire EMPLOYEES, JOB_HISTORY, SALARY_HISTORY, DEPARTMENTS,
and JOBS relations. The definition also selects three views for
transfer: CURRENT_INFO, CURRENT_JOB, and CURRENT_SALARY.
RDO> INVOKE DATABASE FILENAME PERSONNEL
RDO> DEFINE TRANSFER NH_PERSONNEL REPLICATION
cont> TO NODE1::DISK1:[DBADMIN]NHP.RDB
cont> MOVE RELATION E IN EMPLOYEES SELECT FIELDS ALL;
cont> MOVE RELATION JH IN JOB_HISTORY SELECT FIELDS ALL;
cont> MOVE RELATION SH IN SALARY_HISTORY SELECT FIELDS ALL;
cont> MOVE RELATION D IN DEPARTMENTS SELECT FIELDS ALL;
cont> MOVE RELATION J IN JOBS SELECT FIELDS ALL
cont> MOVE VIEWS CURRENT_INFO, CURRENT_JOB, CURRENT_SALARY
cont> LOG FILE IS DISK1:[DBADMIN]NHP.LOG
cont> END.
Example 7
The following example moves the CURRENT_JOB view defined in the
source database as a CROSS of the EMPLOYEES relation and the JOB_
HISTORY relation. You can achieve the effect of a CROSS clause
by transferring a view that is a CROSS in the source database. On
the target database, the records selected by the view are created
as a relation.
RDO> INVOKE DATABASE FILENAME PERSONNEL
RDO> DEFINE TRANSFER CJOB EXTRACTION
cont> TO NODE1::DISK1:[RAMESH]JOB_DB
cont> MOVE RELATION C IN CURRENT_JOB WITH C.JOB_CODE = "SEII"
cont> SELECT FIELDS C.LAST_NAME, C.FIRST_NAME, C.ADDRESS
cont> LOG FILE IS CJOB.LOG
cont> END TRANSFER.
Example 8
The following example shows an extraction rollup transfer that
invokes several source databases: PERSONNEL, WORKERS, and STAFF.
The transfer selects fields in the EMPLOYEES relations from the
three databases identified by the database handles DB1, DB2, and
DB3 and located on three different nodes and in the JOBS relation
from DB1. Then the transfer moves these relations to a single
target database, LOCAL_DB.
RDO> INVOKE DATABASE DB1=FILENAME "NODE1::DISK1:[DIR1]PERSONNEL"
RDO> INVOKE DATABASE DB2=FILENAME "NODE2::DISK2:[DIR2]WORKERS"
RDO> INVOKE DATABASE DB3=FILENAME "NODE3::DISK3:[DIR1]STAFF"
RDO> DEFINE TRANSFER LABOR EXTRACTION ROLLUP
cont> TO NODE4::DISK4:[DIR4]LOCAL_DB
cont> MOVE RELATION E IN DB1.EMPLOYEES WITH E.EMP_CODE= "A+"
cont> INTO RELATION EXEMPT_EMPLOYEES
cont> SELECT FIELDS E.EMP.ID,E.SALARY,E.JOB_CODE;
cont> MOVE RELATION E IN DB2.EMPLOYEES WITH E.EMP_CODE= "A+"
cont> INTO RELATION EXEMPT_EMPLOYEES
cont> SELECT FIELDS E.EMP_ID,E.SALARY,E.JOB_CODE;
cont> MOVE RELATION E IN DB3.EMPLOYEES WITH E.EMP_CODE= "A+"
cont> INTO RELATION EXEMPT_EMPLOYEES
cont> SELECT FIELDS E.EMP.ID,E.SALARY,E.JOB_CODE;
cont> MOVE RELATION J IN DB1.JOBS WITH J.JOB_CODE= "J17"
cont> INTO RELATION ENTRY_JOBS
cont> SELECT FIELDS J.JOB_NAME,J.JOB_CODE
cont> LOG FILE IS DISK4:[DIR4]LOCAL.LOG
cont> END.
Example 9
The following EMPLOYEES transfer creates an extraction database.
The transfer selects records using a first-clause, with-clause,
reduce-clause, and sort-clause.
RDO> INVOKE DATABASE FILENAME PERSONNEL
RDO> DEFINE TRANSFER EMPLOYEES EXTRACTION
cont> TO NODE1::DISK1:[NELSON]EMPLOYEES_INFO
cont> MOVE RELATION FIRST 10 E IN EMPLOYEES
cont> WITH E.CITY = "BOSTON"
cont> REDUCED TO E.LAST_NAME, E.FIRST_NAME, E.ADDRESS
cont> SORTED BY DESCENDING E.LAST_NAME
cont> SELECT FIELDS E.LAST_NAME, E.FIRST_NAME, E.ADDRESS
cont> LOG FILE IS DISK1:[NELSON]EMPLOYEES.LOG
cont> END TRANSFER.
Example 10
The following extraction transfer includes two command files.
The prologue command procedure establishes a connection to a
remote node, and the epilogue command procedure terminates the
connection. This example shows how to specify the prologue file
and epilogue file; it does not show the command procedures.
RDO> INVOKE DATABASE FILENAME NODE1::DISK1:[DBADMIN.PERS]PERSONNEL
RDO> DEFINE TRANSFER PERS_SAMPLE EXTRACTION
cont> TO PERS_COPY
cont> MOVE RELATIONS ALL
cont> PROLOGUE FILE IS DIALUP.COM
cont> EPILOGUE FILE IS HANGUP.COM
cont> LOG IS PERS_SAMPLE.LOG
cont> END.
10 – DEFINE_SCHEDULE
Creates a schedule definition and stores it in the transfer
database. The schedule definition specifies when and how often
a transfer should execute. A transfer can have only one schedule
definition associated with it. Replication Option returns an
error if you attempt to define a schedule for a transfer that
already has one.
10.1 – Format
(B)0[mD[4mEFINE[m [4mSCHEDULE[m qq> FOR qq> transfer-name qqqk
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqqwqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwqk
mqq> [4mSTART[m qq> start-date-time qqqj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqqwqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwqk
mqq> [4mEVERY[m qqwq> every-delta-time qqqqqwqqj x
mq> every-absolute-time qqj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqwqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwqk
mq> [4mRETRY[m q> count q> [4mTIMES[m qwqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwj x
mq> [4mRETRY[m [4mEVERY[m qq> delta-time qj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqq> [4mEND[m qwqqqqqqqqqqqqqqqqqqqwqwqqqqqqqqqqqqqwqqq> .
mqq> transfer-name qj mq> SCHEDULE qj
10.1.1 – transfer-name
The transfer for which this schedule is being defined. The
transfer must already exist when you create a schedule definition
for it. The transfer-name parameter is required.
10.1.2 – start-date-time
The time to execute the initial transfer. You can specify an
absolute or delta time. If you supply an absolute time, the
initial transfer will be executed at the time specified. If you
use a delta time, Replication Option uses the current time and
the delta-time value to calculate the actual transfer time. The
START clause is optional. If you do not include a START clause,
the start time is set to the current time so that the transfer
will execute as soon as the transfer schedule definition is
processed.
The start-date-time parameter uses the following absolute and
delta-time formats. You can omit any of the trailing fields in
the date or time. You can omit any of the fields in the middle
of the format as long as you include the punctuation marks. For
more information on date and time formats, see the entry on the
$BINTIM OpenVMS system service in the OpenVMS documentation set.
Absolute-time
dd-mmm-yyyy hh:mm:ss.cc
Delta time
dddd:hh:mm:ss.cc
In the absolute and delta time designations, the abbreviations
have the following meanings:
dddd Number of days
dd Day of the month
mmm Month
yyyy Year
hh Hours
mm Minutes
ss Seconds
cc Hundredths of a second
10.1.3 – every-delta-time
Used to calculate the time to execute the next transfer. The
EVERY clause is optional. If you specify the EVERY clause, you
must specify either every-delta-time or every-absolute-time. If
you omit the EVERY clause, the transfer occurs only once.
The valid specification for every-delta-time is the delta format
used by the $BINTIM OpenVMS system service. The delta time you
specify is the time from the completion of the last transfer
sequence until the start of the next one. A transfer sequence
is the set of transfers from the first attempt until one of the
following conditions is met: the execution is successful, the
maximum number of retries specified in the RETRY clause has been
reached, or a fatal error has occurred (one for which retries are
not attempted).
10.1.4 – every-absolute-time
(B)0[mevery-absolute-time =
qqqqqwqqqqqq> [4mDAY[m qqqqqqwqqwqqqqqqqqqqq>qqqqqqqqqwqwqqq>
tqqqqqq> [4mWEEK[m qqqqqu mqq> [4mAT[m qq> at-time qqj x
tqqqqqq> [4mMONTH[m qqqqj x
mqqwqqq> weekday qqqwqqqqqqqqqq>qqqqqqqqwqqwqqj
x mq> [4mAT[m qq>at-time qqj x
mqqqqqqqqqqqqqqqq , <qqqqqqqqqqqqqqqqqqqj
Used to calculate the time to execute the next transfer. The
EVERY clause is optional. If you specify the EVERY clause, you
must specify either every-absolute-time or every-delta-time. If
you omit the EVERY clause, the transfer occurs only once.
10.1.4.1 – DAY
The transfer executes on a daily basis.
10.1.4.2 – WEEK
The transfer occurs every week on the same day of the week as the
initial transfer.
10.1.4.3 – MONTH
The transfer occurs on a monthly cycle on the same day of the
month as the initial transfer.
Note that if the initial transfer starts on the 31st of the
month and the transfer schedule specifies EVERY MONTH, the
next execution of the transfer will be on the last day of the
following month, whether the last day is the 28th, 29th, 30th, or
31st.
10.1.4.4 – weekday
The transfer executes on the weekdays that you list. If you
list more than one weekday, separate the days with commas. Valid
weekday specifications are:
SUNDAY
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
SATURDAY
10.1.4.5 – at-time
Qualifies every-absolute-time by specifying the time of day at
which the transfer should occur. This parameter is optional.
If you specify DAY, WEEK, or MONTH, but do not specify an at-
time, Replication Option uses the time of day of the initial
transfer. In the case of a list of weekdays, the at-time for
each day can be specified. If the at-time for any weekday is not
specified, the default is the time used for the previous entry in
the list. For the first entry in the list, the time of day of the
initial transfer is used, if none is specified.
10.1.5 – count
The maximum number of times to retry a transfer if a transfer
execution fails. If you do not include a retry count or if the
count value is set to zero, Replication Option does not attempt
to retry the transfer until the next scheduled transfer time as
indicated by the EVERY clause.
Replication Option does not retry a transfer if the transfer
failed as a result of a fatal error. You can recover from a fatal
error only by manual intervention.
10.1.6 – delta-time
The length of time Replication Option waits between the time of
the last failed attempt and the time of the next retry attempt.
The RETRY EVERY delta-time clause is optional and can only be
specified if the RETRY count TIMES clause is included.
If you specify RETRY count TIMES in the schedule definition,
but do not specify RETRY EVERY delta-time, Replication Option
attempts the retry immediately. See the description of the start-
date-time parameter earlier in this section for valid delta-time
values.
10.2 – More
To define a transfer schedule, you must have the same user
identification code (UIC) as the user who defined the transfer,
or have the ALTER transfer privilege or the OpenVMS BYPASS
privilege. If you try to define a transfer schedule for a
transfer defined by a user with a different UIC, and you do
not have the appropriate access right or privilege, Replication
Option returns an error message and prevents the schedule
from executing. If you have BYPASS privilege and define a
schedule for a transfer associated with a different UIC, the
UIC associated with the transfer does not change.
When you define a schedule for a transfer in the unscheduled
state, that transfer is placed in the scheduled state. If the
transfer is in the suspended state, it remains in the suspended
state. To place the suspended transfer in the scheduled state,
use the START TRANSFER statement. When the transfer executes,
Replication Option places the transfer in the active state.
You cannot modify a schedule definition using RDO. If you need to
change a parameter value in a schedule definition, you must first
delete the schedule using the DELETE SCHEDULE statement and then
define a new schedule, or, use the SQL ALTER SCHEDULE statement.
When you define a one-time-only transfer schedule and specify
a transfer time that has already passed, issuing a START
TRANSFER statement changes the transfer status from suspended
to scheduled. However, when you issue a SHOW TRANSFER STATUS
statement, the "next transfer to be executed" phrase is not
included. To avoid this problem and cause the transfer to
execute, use the START TRANSFER NOW statement.
You must execute the DEFINE SCHEDULE statement outside of the
scope of a transaction. If you issue this statement when a
transaction is outstanding, Replication Option returns an error
message.
You can change the default date/time format that was established
before VMS Version 5.0 to a date/time format that complies with
the LIB$ international date and time formatting routines of VMS
Version 5.0 and higher. For example, you might want to change the
input format from 1-APR-1989 to one that allows entry of dates in
the form April 1, 1989. You can change the output format as well.
To change the input date/time format, define the LIB$DT_INPUT_
FORMAT logical name as discussed in the OpenVMS RTL Library (LIB$)
documentation. To change the output date/time format, define the
logical name LIB$DT_FORMAT. If you change the date/time format from
the one used prior to VMS Version 5.0, then you must place the date
and time in quotation marks. If you continue to use the date
/time format in effect before VMS Version 5.0, you can enter the
date and time with or without quotation marks as you wish. ,b
For further information about the date/time routines provided by
the OpenVMS Run-Time Library, refer to the OpenVMS RTL Library
(LIB$) documentation. Refer also to the Oracle Rdb documentation
set for details specific to that product's use of international
date/time formats.
Replication Option does not guarantee the reexecution of
a transfer at the specified rate. If the copy process is
tied up for any reason and cannot finish its task before the
next transfer repetition cycle, the copy process ignores the
repetition. The cycle is reset to the next expected transfer
time.
A replication transfer with a schedule that runs on an infrequent
basis can consume a considerable amount of disk space in the
source database. For example, if a replication transfer is
scheduled to occur once a month, any new or changed records
to be transferred are duplicated in the relation RDB$CHANGES
in the source database and are retained for the remainder of
the month until the schedule starts the transfer. This space is
released only after the duplicate records have been transferred
and erased. Thus, for the entire month that the duplication
records are stored, they take up disk space. In general, you
should not choose an infrequent transfer cycle if the number of
daily changes to the source database is high.
In addition, even if this monthly replication transfers only a
single record each month, another problem can arise if other
replication transfers use the same source database. Although
those transfers might execute more frequently than once a month,
their records are not necessarily erased from the RDB$CHANGES
relation right away. Replication Option erases the records only
if no records entered earlier are waiting to be transferred.
10.3 – Examples
Example 1
Executes the NH_EMPLOYEES transfer at 1:24 a.m. on June 24,
1988. The transfer will then execute every day at 5:30 p.m.
If a nonfatal error occurs, the transfer execution will be
retried three times with 30 minutes between the end of the failed
transfer execution and the start of the next one.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> START 24-JUN-1988 01:24:00.00 <---- Absolute time
cont> EVERY DAY AT 17:30 <---- Absolute time
cont> RETRY 3 TIMES
cont> RETRY EVERY 0 00:30:00
cont> END SCHEDULE.
Example 2
This example uses a delta-time specification to have 36 hours
(1 day plus 12 hours) between the completion of one transfer
execution and the beginning of the next. The example uses two
delta times, EVERY 1 12:00 and RETRY EVERY 0 03:00:00. EVERY 1
12:00 states that there will be 36 hours (1 day plus 12 hours)
between the completion of the first transfer and the beginning
of the next. If transfer execution does not succeed on the first
attempt, the transfer schedule permits Replication Option to
make up to five additional attempts to complete the transfer.
RETRY EVERY 0 03:00:00 means Replication Option should retry
the transfer three hours after a nonfatal failure until the
transfer completes successfully or until the maximum of five
retries has been attempted. If the transfer does not complete
successfully after five retries, the next attempt will be 36
hours after the last failed attempt.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> START 15-MAY-1988
cont> EVERY 1 12:00 !<---- 1 day plus 12 hours
cont> RETRY 5 TIMES
cont> RETRY EVERY 0 03:00:00 !<---- 3 hours
cont> END.
Example 3
The following transfer schedule causes Replication Option
to execute a transfer for the first time at 12 noon on the
15th of October 1988. Subsequent transfers will occur every
day thereafter at 5:30 p.m. If an error occurs preventing a
successful transfer, Replication Option will retry every 30
minutes until the transfer is successful or the maximum of three
retries has been reached.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> START 15-OCT-1988 12:00
cont> EVERY DAY AT 17:30 !<---- Every day
cont> RETRY 3 TIMES
cont> RETRY EVERY 0 00:30:00
cont> END SCHEDULE.
Example 4
The following schedule definition assumes that you want to
execute the transfer immediately after you complete the schedule
definition and, therefore, it contains no START clause. If
the system time is 20-OCT-1988 16:00:00 when you complete the
DEFINE SCHEDULE statement, the next execution of the NH_EMPLOYEES
transfer will start on 20-NOV-1988 16:00:00.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> EVERY MONTH
cont> RETRY 3 TIMES
cont> RETRY EVERY 0 00:30:00
cont> END.
Example 5
This example calls for the NH_EMPLOYEES transfer to execute at
3:00 p.m. every Wednesday. The schedule definition calls for a
maximum of three retries occurring at intervals of 30 minutes.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> START 12-NOV-1988 15:00:00.00
cont> EVERY WEDNESDAY AT 15:00:00 !<---- Wednesdays at 3 p.m.
cont> RETRY 3 TIMES
cont> RETRY EVERY 0 00:30:00
cont> END.
Example 6
The following example causes an initial transfer to execute on
the 15th of July at 5 p.m., on every Monday after the 15th at
5 p.m., every Tuesday at 11 a.m., and every Friday at 11 a.m.
Because a RETRY clause is not specified, even if a nonfatal
failure occurs, the transfer will not execute until the next
regularly scheduled time.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> START 15-JUL-1988 17:00
cont> EVERY MONDAY, TUESDAY AT 11:00, FRIDAY
cont> END.
Example 7
This example causes a transfer to start at midnight on July 15th
and on the 15th of every month thereafter at 7 p.m.
RDO> DEFINE SCHEDULE FOR NH_EMPLOYEES
cont> START 15-JUL-1988
cont> EVERY MONTH AT 19:00
cont> END.
11 – REINITIALIZE_TRANSFER
Reinitializes a replication transfer. You use this statement when
the source database and the replication target database are no
longer consistent with each other.
11.1 – Format
(B)0[m[4mREINITIALIZE[m [4mTRANSFER[m qqqqqq> transfer-name qqq>
11.1.1 – transfer-name
The replication transfer that you want to reinitialize. The
transfer-name parameter is required.
11.2 – More
If you want to reinitialize a particular transfer, the transfer
definition must be associated with your UIC, or you must have
the DBCTRL or ALTER transfer privilege, or the OpenVMS BYPASS
privilege.
You can reinitialize a transfer only when the transfer is in
the suspended state. To suspend a transfer, first issue a STOP
TRANSFER statement. You must execute the REINITIALIZE TRANSFER
statement outside the scope of a transaction. If you issue this
statement when a transaction is outstanding, Replication Option
returns an error message.
After you enter the REINITIALIZE statement, the transfer remains
in the suspended state. You must then issue a START TRANSFER
statement to restart the transfer.
The REINITIALIZE TRANSFER statement has different effects
depending on the type of replication transfer being reinitialized
and whether the transfer is TO NEW or TO EXISTING:
o For a standard replication transfer created with SQL to an
existing database, REINITIALIZE TRANSFER forces the next
execution of the transfer to drop all target tables and create
new target tables rather than update the tables with changed
data.
o For a replication transfer created with the NO DELETE
attribute using SQL, REINITIALIZE TRANSFER forces the next
execution of the transfer to drop all rows in the target
tables except those whose dbkey has been set to zero. Any row
whose dbkey has not been set to zero is copied to the target
database from the source database.
o For a replication transfer specifying TO NEW FILENAME
target-file-spec created with SQL, or for any RDO transfer
definition, new versions of the target database files are
created and all tables specified in the transfer definition
and their corresponding rows will be copied from the source
database to the target database.
11.3 – Example
This example places the CARS_LAX transfer in a suspended state
and then reinitializes it. The schedule and definition for this
replication transfer remain in place. Once the transfer has been
reinitialized, you can restart it.
RDO> STOP TRANSFER CARS_LAX
RDO> REINITIALIZE TRANSFER CARS_LAX
RDO> START TRANSFER CARS_LAX
12 – START_TRANSFER
Executes a transfer on demand, or changes the state of a transfer
from the suspended state to the scheduled, unscheduled, or active
state.
12.1 – Format
(B)0[m[4mSTART[m [4mTRANSFER[m qqqqq> transfer-name qqk
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqqwqqqqqqqqqqqq>qqqqqqqqqqqqqqwqqqq>
mqqq> [4mNOW[m qqwqqqqqqqqqqqqwqqj
tq> [4mWAIT[m qqqqu
mq> [4mNOWAIT[m qqj
12.1.1 – transfer-name
The transfer to be started. The transfer-name parameter is
required.
12.1.2 – NOW
Changes the transfer state to active and begins execution.
If the transfer has a schedule defined for it, subsequent
transfers occur as specified by that schedule. The NOW argument
is optional.
12.1.3 – WAIT_NOWAIT
Specifies whether Replication Option returns control to RDO
immediately after the transfer starts or waits until the transfer
completes. You must use the NOW argument if you specify WAIT
or NOWAIT. The default, NOWAIT, causes Replication Option to
return control immediately to the RDO command mode while the
transfer executes. With NOWAIT in effect, you can enter other
RDO statements while the copy process completes the transfer of
database records to the target database.
The WAIT option ensures that the transfer completes before
control is returned to RDO.
12.2 – More
If you want to start a transfer, the transfer definition must
be associated with your UIC, or you must have the ALTER transfer
privilege, or the OpenVMS BYPASS privilege.
You can use the START TRANSFER statement without any qualifiers
to change the state of a suspended transfer. Issuing the START
TRANSFER statement places the transfer in the scheduled state
if a schedule definition exists for the transfer. Execution then
occurs at the next scheduled time. If a schedule definition does
not exist, the transfer is placed in the unscheduled state and
will execute only when you issue a START TRANSFER statement using
the NOW qualifier or you define a schedule for the transfer.
If you specify both the NOW and WAIT arguments and your transfer
has an epilogue procedure, Replication Option waits for the
epilogue procedure to finish before resuming execution.
You cannot enter the START TRANSFER statement when a transaction
is outstanding. You must terminate any outstanding transactions
before issuing the START TRANSFER statement.
You can use the START TRANSFER statement to initiate a transfer
on demand by including the NOW option. The NOW option immediately
places the transfer in the active state. This execute-on-demand
feature is useful in batch processing environments when you
want to initiate the transfer after another job has completed
successfully, regardless of the transfer's schedule.
When you define a one-time-only transfer schedule and specify
a transfer time that has already passed, issuing a START
TRANSFER statement changes the transfer status from suspended
to scheduled. However, when you issue a SHOW TRANSFER STATUS
statement, the "next transfer to be executed" phrase is not
included. To avoid this problem and cause the transfer to
execute, use the START TRANSFER NOW statement.
Do not issue a START TRANSFER NOW WAIT statement when RDO is
attached to a source database and the transfer is either a
replication transfer that has not finished or a replication
initialization transfer. Instead, issue a FINISH statement to
detach from the database, and then enter the START TRANSFER NOW
WAIT statement. Otherwise, the copy process waits indefinitely
for you to release the source database. Because you specified
that you want to wait for the copy process to complete, the
transfer operation will never complete.
12.3 – Examples
Example 1
This example starts a transfer called ENROLL_SPANISH1. If this
transfer has a schedule defined for execution one hour from
now but the transfer is suspended, issuing the START TRANSFER
statement only changes the transfer's state to scheduled.
Execution of the transfer will not occur for another hour.
RDO> START TRANSFER ENROLL_SPANISH1
Example 2
In this example, transfer ENROLL_SPANISH1 has been defined but
has no schedule. You issue this START TRANSFER NOW statement
because you want to execute the transfer immediately. Control
returns to RDO as soon as the transfer begins.
RDO> START TRANSFER ENROLL_SPANISH1 NOW
13 – STOP_TRANSFER
Places a transfer in the suspended state. Replication Option
does not attempt to execute the transfer until you remove it from
the suspended state using the START TRANSFER statement. If the
transfer is in the active state, the STOP TRANSFER statement also
stops the copy process associated with that transfer.
13.1 – Format
(B)0[m[4mSTOP[m [4mTRANSFER[m qqqqqqq> transfer-name qqqqq>
13.1.1 – transfer-name
The transfer to be suspended. The transfer-name parameter is
required.
13.2 – More
If you want to stop a particular transfer, the transfer
definition must be associated with your UIC, or you must
have ALTER or DROP transfer privilege, or the OpenVMS BYPASS
privilege.
You must terminate any outstanding transactions before you issue
a STOP TRANSFER statement.
If you want to stop a particular transfer, the transfer
definition must be associated with your UIC.
A transfer cannot occur until you remove it from the suspended
state using the START TRANSFER statement. If the transfer is in
the active state, the STOP TRANSFER statement also stops the copy
process associated with that transfer. After you stop a currently
executing extraction, extraction rollup, or initial replication
transfer, you cannot access the partially created target database
unless you restart the transfer.
If a replication update transfer is executing and you stop the
transfer, users of the target database can continue their work
unaffected. Furthermore, stopping the transfer does not stop
the capture of the changes in the source database (written to
RDB$CHANGES). The changes are transferred to the target database
when the transfer is restarted. No updates to the target database
are missed as a result of stopping a replication transfer for
which the target relations have already been created. However,
since stopping a transfer does not stop the capture of record
changes, changes continue to be written to RDB$CHANGES regardless
of a transfer's state. Records are added to RDB$CHANGES even
for transfers that are suspended for a long time. The number of
records in RDB$CHANGES and the overall size of the database both
continue to grow.
13.3 – Example
The following example places the EUROPE_PERS transfer in the
suspended state.
RDO> STOP TRANSFER EUROPE_PERS
14 – RDO_ERRORS
RDO$MSG
14.1 – 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.
14.2 – 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.
14.3 – 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.
14.4 – 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.
14.5 – ACENOTFND
no matching access control entry found Explanation: In a protection statement that refers to an existing access control entry, there was no existing entry that matched the input. User Action: Use SHOW PROTECTION to see what the ACL currently looks like, and correct your statement.
14.6 – ACLNOTIMP
ACL not imported for <str> Explanation: The ACL contained in the RBR file could not be imported to the named object (database/relation/field) User Action: If you really want it, you must either obtain the needed privileges (BYPASS) or import the database under the account of the former owner (which may not be sufficient anyway). If you do not care about the restoration of protections you can ignore the message or import the database using the NOACL parameter which will cause all privileges and protections in the RBR file to be ignored.
14.7 – ACTMISMATCH
journal is for database activation <time>, not <time> Explanation: The activation time and date stamp in the root does not match the activation time and date stamp in the journal file. This journal cannot be applied to this database. User Action: Use the correct journal file or backup file.
14.8 – AGGNOTALL
aggregate expressions are not allowed in VALID IF expressions Explanation: You entered a VALID IF expression that contained something other than an operator, literal value, or the field name. User Action: Check the Oracle Rdb Reference Manual for details on VALID IF.
14.9 – AIJACTIVE
<num> active transaction(s) not yet committed or aborted Explanation: Upon completion of the roll-forward operations for the current AIJ file, more than 1 transaction remains active. That is, the commit or roll-back information resides in the next AIJ file to be processed. It is also possible that one or more of these active transactions are prepared transactions, which may be committed or aborted by the recovery operation using DECdtm information; in this case, a separate message indicating the number of prepared transactions will be displayed. User Action: No user action is required. This message is informational only.
14.10 – 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.
14.11 – 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.
14.12 – 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.
14.13 – AIJBADPAGE
inconsistent page <num> from storage area <str> needs AIJ sequence number <num> Explanation: The indicated page has been marked inconsistent with the rest of the database. The AIJ file with the indicated sequence number is required to commence recovery of the page. If the sequence number of the AIJ file is different than the indicated sequence number, recovery of the area will not be performed. User Action: No user action is required. This message is informational only.
14.14 – 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.
14.15 – 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)").
14.16 – 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.
14.17 – 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.
14.18 – AIJBCKCNFT
cannot specify a backup filename and use SAME AS JOURNAL option Explanation: An attempt was made to specify an after-image backup filename and use the BACKUP SAME AS JOURNAL option. User Action: Specify one or the other of the after-image backup options, but not both.
14.19 – 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.
14.20 – 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.
14.21 – 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).
14.22 – AIJBCKDSBL
database contains no after-image journals that qualify for backup Explanation: An attempt was made to perform an after-image backup for a database that has after-image journaling disabled and does not have any journals that qualify to be backed up. This situation occurs if there are no after-image journals, or all journals are unmodified and do not require backup. User Action: No user action is required.
14.23 – 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.
14.24 – 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.
14.25 – 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.
14.26 – AIJBCKFIX
cannot perform by-sequence AIJ backup of extensible journals Explanation: An attempt has been made to back up an "extensible" after-image journal using the "by-sequence" command qualifier. User Action: Do NOT use the "by-sequence" command qualifier when backing up an extensible AIJ journal.
14.27 – 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).
14.28 – 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.
14.29 – 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.
14.30 – AIJBCKINTR
invalid after-image journal backup interval value "<num>" specified Explanation: An invalid AIJ journal backup interval was specified. User Action: The AIJ journal backup interval specifies the number of seconds for which the backup utility will wait. The value must be a positive number, which may include the value "0".
14.31 – 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.
14.32 – 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.
14.33 – 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.
14.34 – AIJBCKRENAME
/RENAME qualifier invalid when backup filespec also specified Explanation: The /RENAME qualifier cannot be specified when an AIJ backup filename specification is also specified, since these are conflicting options. User Action: Specify either the /RENAME qualifier (using "" for the AIJ backup filename specification) or the AIJ backup filename specification, but not both.
14.35 – 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.
14.36 – 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.
14.37 – 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.
14.38 – 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".
14.39 – AIJCCHDIR
AIJ-cache file name "<str>" does not include device and directory Explanation: The AIJ-cache filename specified does not include a device and directory. User Action: For maximum protection, you should always include a device and directory in the AIJ-cache file specification, preferably one that is different from both the database device and AIJ device.
14.40 – 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.
14.41 – 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.
14.42 – 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.
14.43 – AIJDELCUR
cannot remove the current AIJ journal "<str>" Explanation: An attempt was made to remove the AIJ journal currently in use. User Action: Disable AIJ journaling first, or try to remove the AIJ journal when the journal is no longer in use.
14.44 – 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.
14.45 – 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.
14.46 – 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.
14.47 – 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.
14.48 – 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.
14.49 – 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.
14.50 – 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.
14.51 – 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.
14.52 – 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.
14.53 – AIJFNLSEQ
to start another AIJ file recovery, the sequence number needed will be <num> Explanation: This message informs the user what the next AIJ file sequence number will be. AIJ file sequence numbers are modified for a variety of reasons (such as, performing an AIJ backup, enabling or disabling AIJ logging, etc.). User Action: No user action is required. This message is informational only.
14.54 – 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.
14.55 – 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.
14.56 – 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.
14.57 – 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.
14.58 – 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.
14.59 – AIJJRNBSY
journal <str> is busy and cannot be backed up Explanation: An attempt has been made to back up an after-image journal that is currently required for process recovery. The journal is considered to be "busy" until no process requires the journal for recovery. User Action: Use the /WAIT command qualifier to indicate that the after-image backup is to "wait" for the journal to become available; that is, the journal becomes available for backup when no more processes require it for recovery.
14.60 – AIJLSSDONE
"Hot Standby" has been shutdown Explanation: "Hot Standby" has been terminated. User Action: Restart the database replication operation.
14.61 – 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.
14.62 – 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.
14.63 – 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.
14.64 – AIJMODSWTCH
AIJ switch-over suspended - add new journal or backup current Explanation: The AIJ switch-over operation is suspended and performing the requested operation will not succeed and possibly result in the database being shutdown. User Action: Add a new AIJ journal or, if possible, backup the existing journals.
14.65 – 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.
14.66 – 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.
14.67 – 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.
14.68 – 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 enabled. User Action: The offending process(es) need to commit or rollback their current transaction or unbind from the database.
14.69 – 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.
14.70 – 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.
14.71 – 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.
14.72 – AIJNORCVR
recovery must start with journal sequence <num> Explanation: The AIJ file supplied was created subsequent to the expected AIJ journal. Usually, this condition occurs for the following reasons: 1) an incorrect AIJ file or VMS file "version" was specified, 2) the supplied AIJ file was not created for this database, 3) AIJ logging was disabled and then later enabled, or 4) a transaction is continued in this journal from a previous journal. User Action: This is a fatal condition; recovery of the AIJ journal CANNOT start with this journal. You MUST start recovery with the AIJ journal indicated by the preceeding AIJSEQAFT or AIJSEQPRI message.
14.73 – 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>.
14.74 – 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.
14.75 – 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.
14.76 – AIJOPTRST
Optimized AIJ journal will not be applied during restart Explanation: An optimized AIJ was encountered during a restarted AIJ roll-forward operation. Since an optimized AIJ journal only contains 1 real transaction, nothing in the AIJ 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.
14.77 – AIJOPTSUC
AIJ optimization completed successfully Explanation: An AIJ optimization has completed successfully. User Action: No user action is required.
14.78 – 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.
14.79 – 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.
14.80 – 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.
14.81 – AIJRECBEG
recovering after-image journal "state" information Explanation: When performing a full database restore operation, the restore utility attempts to recover the "state" information of any after-image journals that were available at the time of the backup operation. Recovering the after-image journal information permits subsequent "automatic" (i.e., hands-off) AIJ-recovery operations. User Action: No user action is required.
14.82 – AIJRECEND
after-image journal "state" recovery complete Explanation: The after-image journal "state" recovery operation has completed. User Action: No user action is required.
14.83 – 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.
14.84 – 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.
14.85 – 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.
14.86 – 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.
14.87 – 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.
14.88 – 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.
14.89 – 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.
14.90 – 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.
14.91 – AIJRSTBEG
restoring after-image journal "state" information Explanation: When performing a full database restore operation, the restore utility attempts to restore the "state" information of any after-image journals that were available at the time of the backup operation. Restoring the after-image journal information permits subsequent "automatic" (i.e., hands-off) AIJ-recovery operations. User Action: No user action is required.
14.92 – 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.
14.93 – AIJRSTEND
after-image journal "state" restoration complete Explanation: The after-image journal restore operation has completed. User Action: No user action is required.
14.94 – 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.
14.95 – 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.
14.96 – AIJRSTMOD
<num> after-image journal(s) marked as "modified" Explanation: This message indicates the number of after-image journals that were successfully restored, but contain data that needs to be backed up. User Action: No user action is required.
14.97 – 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.
14.98 – 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.
14.99 – 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.
14.100 – AIJRSTSUC
journal "<str>" successfully restored from file "<str>" Explanation: The indicated after-image journal was successfully restored. User Action: No user action is required.
14.101 – AIJSEQAFT
incorrect AIJ file sequence <num> when <num> was expected Explanation: The AIJ file supplied was created subsequent to the expected AIJ file. Usually, this condition occurs for the following reasons: 1) an incorrect AIJ file or VMS file "version" was specified, 2) the supplied AIJ file was not created for this database, or 3) AIJ logging was disabled and then later enabled. User Action: The utility will prompt for confirmation that the supplied AIJ file is valid. If AIJ logging was disabled and then later enabled without any intervening database transaction activity, then confirming the AIJ file will permit the roll-forward operation to continue applying all transactions contained in the AIJ file. Otherwise, the AIJ file should be rejected and the correct AIJ file specified. Should confirmation be given for an incorrect AIJ file, no transactions will be applied.
14.102 – 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.
14.103 – 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.
14.104 – 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.
14.105 – AIJTERMINATE
inaccessible AIJ file forced image exit to protect database Explanation: To maintain the integrity of the database, the database system has forced your image to exit. An error has been encountered with one or more of the after-image journals that could jeopardize your ability to recover the database should a it become necessary to restore and recover the database. Until the journaling problem has been remedied no further updates to the database are allowed. User Action: The RMU or DBO /DUMP/HEADER=JOURNAL command will display the current state of the journals. Various remedies are possible, depending on the error encountered. Contact Oracle Support if you have questions on how to fix the problem. Typically, disabling and re-enabling journaling is the simplest way to restore operation of the database. This can be 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.
14.106 – 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.
14.107 – 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.
14.108 – 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.
14.109 – ALSNAVAIL
"Hot Standby" not available or improperly installed Explanation: "Hot Standby" cannot be started because it has not been installed. User Action: Make sure the "Hot Standby" component has been properly installed.
14.110 – 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.
14.111 – 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.
14.112 – 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.
14.113 – 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.
14.114 – AMB_KEYWORD
ambiguous keyword abbreviation Explanation: You used an ambiguous abbreviation. User Action: Specify the entire keyword.
14.115 – ANODBHAND
another database has been invoked with the same db_handle name <str> Explanation: You specified in the INVOKE statement the same name for the db_handle as in a previous INVOKE statement. User Action: Reenter the INVOKE statement with a different db_handle name.
14.116 – ANYNOTALL
ANY and UNIQUE are not allowed in a VALID IF expression Explanation: You entered a VALID IF expression containing something other than an operator, literal value, or field name. User Action: Check the Oracle Rdb Reference Manual for details on VALID IF.
14.117 – 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.
14.118 – 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.
14.119 – 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.
14.120 – AREA_DELETED
area is not active or was previously deleted Explanation: An attempt was made to ready an area which does not exist.
14.121 – AREA_INCONSIST
storage area <str> is inconsistent Explanation: The storage area has been marked inconsistent with the rest of the database. It cannot be readied. User Action: Recover the area to make it consistent.
14.122 – 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.
14.123 – ARIEXPEXP
an arithmetic expression was expected Explanation: An arithmetic expression was expected in the current context. A Boolean expression was found. User Action: You must use an arithmetic expression in this context.
14.124 – ASCEIGNOR
ASCENDING/DESCENDING keywords are ignored for a hashed index Explanation: The ASCENDING and DESCENDING keywords are ignored when they are specified for a hashed index. User Action: Do not specify the ASCENDING or DESCENDING keywords for a hashed index.
14.125 – ATTMISSING
invalid or missing attributes Explanation: Internal error -- a required attribute (such as the data type in a GLOBAL FIELD clump) is missing. User Action: Contact your Oracle support representative for assistance.
14.126 – BACKCONV
please backup your database and use the RMU/CONVERT command Explanation: The database has an obsolete root file and must be converted. User Action: The database must be converted. First make a backup copy. Then use the RMU/CONVERT command.
14.127 – BADADJLOCKGRAN
ADJUSTABLE LOCK GRANULARITY clause is not allowed in the DEFINE TRANSFER statment. Explanation: You have specified an ADJUSTABLE LOCK GRANULARITY clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the ADJUSTABLE LOCK GRANULARITY clause.
14.128 – 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.
14.129 – BADAIJBCK
previous AIJ backup did not complete Explanation: It appears that the previous AIJ file backup process, which was started on the indicated date/time, either failed or was prematurely terminated by the user. User Action: No user action required. The current AIJ backup will backup the complete AIJ file to ensure there is no loss of transactions. The AIJ file created by the failed backup utility MUST be preserved; DO NOT discard the AIJ backup file created by the failed backup utility. Even though the AIJ backup failed, the AIJ backup file must be used for successful roll-forward operations.
14.130 – 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.
14.131 – 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.
14.132 – 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.
14.133 – BADAIJVER
after-image journal version is incompatible with the runtime system Explanation: Your after-image journal file was created with an incompatible version of the software. User Action: Your after-image journal file cannot be used with the version of the software you have installed on your machine. Make sure you are using the correct AIJ journal, or if "multi-version" software is installed, make sure you are using the correct software version.
14.134 – 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.
14.135 – BADBLOB
unable to IMPORT segmented string Explanation: Error from Rdb$CREATE_SEGMENTED_STRING. See the following message for more information. User Action: If the nature of the problem is not obvious, then contact your Oracle support representative for assistance.
14.136 – 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.
14.137 – BADBNDPRM0
bad bind parameter Explanation: A logical bind parameter value is invalid. User Action: See the secondary error message for more information. Because of unfortunate logistics, no further information is available at this point, check the Monitor log for more info.
14.138 – 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.
14.139 – 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.
14.140 – BADCCHNAM
record cache "<str>" does not exist Explanation: The specified record cache is not defined in the database. User Action: Please specify a valid record cache name.
14.141 – BADCLUMP
invalid clump type encountered Explanation: Internal error - bad data in the Oracle Rdb interchange file (RBR). User Action: Contact your Oracle support representative for assistance.
14.142 – BADCORATT
invalid core attribute <num>, <num> in RBR file Explanation: Internal error - bad data in the Oracle Rdb interchange file (RBR). User Action: Contact your Oracle support representative for assistance.
14.143 – 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.
14.144 – 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.
14.145 – BADDTFMT
date or time format is not set up correctly Explanation: You entered a SHOW DATE_FORMAT command, but LIB$DT_FORMAT is not properly defined. User Action: Check the definition of LIB$DT_FORMAT. If it is a process logical, it should be changed. If it is a group or system logical, contact your system manager to change it.
14.146 – BADEPILOGUE
only one epilogue file clause can be specified per transfer Explanation: You specified more than one epilogue file clause in the DEFINE TRANSFER statement. This is not permitted. User Action: Reenter the DEFINE TRANSFER statement, specifying only one EPILOGUE IS or NOEPILOGUE clause.
14.147 – BADFILEVER
incompatible RBR file type Explanation: This version of RDO cannot import a database from this Oracle Rdb interchange file (RBR). User Action: Use a version of RDO that corresponds to the version of RDO that created this file.
14.148 – 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.
14.149 – BADFLDTYP
field <str> of target relation <str> has different field types Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you have entered MOVE RELATION clauses with the same target relation name and specified fields with the same names but of different data types in the source databases. User Action: Reenter the DEFINE TRANSFER statement by specifying fields of the same datatype in all the MOVE RELATION clauses with the same target relation.
14.150 – BADIDXMAP
fields specified for partitioning index do not agree with fields for index Explanation: The user named fields to partition an index but in an incorrect order, or specified too many fields. User Action: Review the DML statement and specify it again.
14.151 – 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.
14.152 – BADINTERVAL
INTERVAL clause is not allowed in the DEFINE TRANSFER statement. Explanation: You have specified an INTERVAL clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the INTERVAL clause.
14.153 – BADLOGFILE
only one log file clause can be specified per transfer Explanation: You specified more than one log file clause in the DEFINE TRANSFER statement. This is not permitted. User Action: Reenter the DEFINE TRANSFER statement, specifying only one LOG FILE IS or NOLOG clause.
14.154 – BADLOGNAM
invalid log file name Explanation: You entered an invalid log file name. User Action: Refer to the explanation in the user action section of the secondary error message.
14.155 – BADMETNAM
metadata names must end in A - Z or 0 - 9 Explanation: The name given in a DML or DDL statement ended in a dollar sign or an underscore. These symbols are not allowed. User Action: Specify a valid name.
14.156 – BADMVIEWFLD
field <str> of relation <str> must be moved for view <str> Explanation: You attempted to transfer a view without transferring a field to which the view refers. You must also explicitly transfer in the DEFINE TRANSFER statement all relevant fields of relations to which the view refers. User Action: Reenter the DEFINE TRANSFER statement, adding the required field to the appropriate MOVE RELATION clause.
14.157 – 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 DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement adding the required MOVE RELATION clause.
14.158 – BADMVIEWVEW
underlying view <str> of view <str> must also be moved Explanation: You attempted to transfer a view without transferring other views that underlie the view you want to transfer. You must explicitly transfer the views to which the view refers in the DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement adding the required views to the MOVE VIEW clause.
14.159 – BADMVRELS
move-relations-clause is allowed only once in DEFINE TRANSFER Explanation: You specified more than one move-relations-clause in a DEFINE TRANSFER statement. Possibly you did not separate the MOVE RELATION clauses with semicolons. User Action: When you use a DEFINE TRANSFER statement, group all the MOVE RELATION clauses together and separate them with semicolons.
14.160 – BADMVVIEWS
move-views-clause is allowed only once in DEFINE TRANSFER Explanation: You entered more than one move-views-clause in a DEFINE TRANSFER statement. Only one move-views-clause is allowed in a DEFINE TRANSFER statement. User Action: Combine all MOVE VIEWS clauses into one list and separate the view names with commas.
14.161 – BADPAGEFORMAT
PAGE FORMAT clause is not allowed in the DEFINE TRANSFER statement. Explanation: You have specified a PAGE FORMAT clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the PAGE FORMAT clause.
14.162 – 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.
14.163 – 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:
14.164 – 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.
14.165 – BADPARAM
<str> (<num>) is out of valid range (<num>..<num>) Explanation: An illegal parameter was specified during creation or modification of the database. User Action: Examine your command line for illegal parameter values.
14.166 – BADPROLOGUE
only one prologue file clause can be specified per transfer Explanation: You specified more than one prologue file clause in the DEFINE TRANSFER statement. This is not permitted. User Action: Reenter the DEFINE TRANSFER statement, specifying only one PROLOGUE IS or NOPROLOGUE clause.
14.167 – BADRECBUF
NUMBER OF RECOVERY BUFFERS clause is not allowed in the DEFINE TRANSFER statement. Explanation: You have specified the NUMBER OF RECOVERY BUFFERS clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the NUMBER OF RECOVERY BUFFERS clause.
14.168 – BADROLMVFLD
MOVE RELATION clauses of target relation <str> have different fields Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you have entered a MOVE RELATION clauses with the same target relation name but specified a different set of fields in each clause. User Action: Reenter the DEFINE TRANSFER statement by specifying the same set of fields in all the MOVE RELATION clauses with the same target relation.
14.169 – 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.
14.170 – 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.
14.171 – BADSNAPFILENAME
SNAPSHOT_FILENAME clause is not allowed in the DEFINE TRANSFER statement. Explanation: You have specified a SNAPSHOT_FILENAME clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the SNAPSHOT_FILENAME clause.
14.172 – 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.
14.173 – BADSPECATR
attribute is incorrectly specified Explanation: You specified a field attribute that does not make sense. User Action: Check the documentation and specify the data definition statement again.
14.174 – BADSTATVER
statistics input file version is incompatible with the software version Explanation: The binary statistics file specified by the /INPUT qualifier was created with an incompatible version of the software. User Action: The binary statistics file cannot be used with the version of the software you have installed on your machine.
14.175 – BADTHRESHOLD
THRESHOLDS clause is not allowed in the DEFINE TRANSFER statement. Explanation: You have specified a THRESHOLDS clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the THRESHOLDS clause.
14.176 – BADVAXCLUSNODES
NUMBER OF VAXCLUSTER NODES clause is not allowed in the DEFINE TRANSFER statement. Explanation: You have specified a NUMBER OF VAXCLUSTER NODES clause as an attribute for the target database in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement without the NUMBER OF VAXCLUSTER NODES clause.
14.177 – BAD_END_NAME
the name in END <str> does not match item name <str> Explanation: The name given in an END <name> <structure> (for example, END name RELATION) does not match the name given to the item (DEFINE RELATION name). User Action: Specify the same item name.
14.178 – BAD_NAME
identifiers and names may not exceed 31 characters in length Explanation: The name given in a DML/DDL statement was longer than the permitted limit. User Action: For data definition statements, specify a shorter name. For data manipulation statements, consult your database design specifications to find the correct name.
14.179 – 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.
14.180 – 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.
14.181 – BOOEXPEXP
a Boolean expression was expected Explanation: Either a numeric or string expression was found where a Boolean expression was expected. User Action: You must use a Boolean expression in this context.
14.182 – 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.
14.183 – 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.
14.184 – 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.
14.185 – 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.
14.186 – BUGCHK
there has been a fatal error; please contact your Oracle support representative; no dump was produced Explanation: A fatal error has occurred. User Action: Contact your Oracle support representative for assistance. You will need to provide information about the circumstances under which the bug occurred. Note that RDO$_BUGCHECKs do not produce dumps as RDB$_BUGCHECKs do.
14.187 – 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.
14.188 – CABORT
user entered Control-C to abort command Explanation: You entered a CTRL/C to abort the current command. User Action: None.
14.189 – 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.
14.190 – 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.
14.191 – 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.
14.192 – 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.
14.193 – CANTBACKUP
BACKUP command may not be issued, use RDO EXPORT Explanation: The BACKUP command is no longer available in RDO. User Action: Use the RDO EXPORT command, which provides the same functionality.
14.194 – CANTBINDRT
error mapping database root file Explanation: An error occurred during mapping to the database root file. User Action: Examine the associated messages to determine the reason for failure.
14.195 – 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.
14.196 – CANTCONVERT
CONVERT command may not be issued, use RMU/CONVERT Explanation: The CONVERT command is no longer available in RDO. User Action: Use the RMU/CONVERT command which provides the same functionality.
14.197 – 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.
14.198 – 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.
14.199 – 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.
14.200 – 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.
14.201 – 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.
14.202 – 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.
14.203 – 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.
14.204 – 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).
14.205 – 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.
14.206 – CANTCRERCS
error creating Record Cache Server process Explanation: An error occurred when you attempted to create a detached Record Cache Server process. User Action: Examine the secondary message(s) or look in the database monitor log file (SYS$SYSTEM:*MON.LOG) for more information.
14.207 – 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.
14.208 – CANTCVRT
cannot convert this database version Explanation: Your database is not recognized as one which can be converted. User Action: Either the database being converted has already been converted, is too old to be converted, or is not a database. You should check your backups.
14.209 – 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.
14.210 – 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.
14.211 – CANTFINDLAREA
cannot locate logical area <num> in area inventory page list Explanation: This is an internal error. A request was made to find logical area information for the specified logical area number but no active AIP entries could be found for that logical area number. User Action: Contact your Oracle support representative for assistance.
14.212 – 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.
14.213 – 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.
14.214 – 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.
14.215 – 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.
14.216 – 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.
14.217 – 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.
14.218 – 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.
14.219 – 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.
14.220 – 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.
14.221 – 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.
14.222 – 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.
14.223 – CANTRESTORE
RESTORE command may not be issued, use RDO IMPORT Explanation: The RESTORE command is no longer available in RDO. User Action: Use the RDO IMPORT command, which provides the same functionality.
14.224 – 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.
14.225 – CANTRESUMELRS
error resuming AIJ Log Roll-Forward Server process Explanation: An error occurred when you attempted to resume the detached AIJ Log Roll-Forward Server process. User Action: Examine the secondary message(s) or look in the database monitor log file (SYS$SYSTEM:*MON.LOG) for more information.
14.226 – 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.
14.227 – 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.
14.228 – CANTSPOOL
SPOOL command may not be issued, use RMU/BACKUP/AFTER_JOURNAL Explanation: The SPOOL command is no longer available in RDO. User Action: Use the RMU/BACKUP/AFTER_JOURNAL command, which provides the same functionality.
14.229 – 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.
14.230 – 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.
14.231 – CANTSTARTLCS
error starting AIJ Log Catch-Up Server process Explanation: An error occurred when you attempted to start the detached AIJ Log Catch-Up Server process on the replicated database. User Action: Examine the secondary message(s) or look in the database monitor log file (SYS$SYSTEM:*MON.LOG) for more information.
14.232 – 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.
14.233 – 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.
14.234 – 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.
14.235 – CANTSTARTTX
cannot start transaction Explanation: Cannot start a transaction as requested. User Action: Examine the secondary message for more information.
14.236 – 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.
14.237 – 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.
14.238 – 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.
14.239 – 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.
14.240 – 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.
14.241 – 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.
14.242 – 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.
14.243 – 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.
14.244 – CDDDEFERR
unable to update or read the CDD default path Explanation: An error occurred updating or reading the CDD default path. User Action: Check the CDD message that follows for more details.
14.245 – CDDERR
error occurred during CDD signin, CDD will not be used Explanation: An error occurred during signin. Refer to the CDD manual for more information. User Action: Check the CDD message that follows for more details.
14.246 – CHDBNOPARAM
command CHANGE DATABASE included no parameters
Explanation: User entered CHANGE DATABASE {PATH | NAME} db_name
without entering any parameters to change.
User Action: Specify what you intend to change on a CHANGE
DATABASE command.
14.247 – 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.
14.248 – CHGINDMAP
This index was previously specified with a STORE clause, continue? [N] Explanation: You are specifying a CHANGE INDEX statement without a STORE clause, which places the index into the RDB$SYSTEM storage area. The index was previously specified as being stored in a different area. RDO is confirming that you want the index placed in the RDB$SYSTEM storage area. User Action: An affirmative reply (Y or YES) causes the operation to continue. A negative reply (a carriage return, N, or NO) terminates the operation.
14.249 – CHGINDMAPSTP
terminating operation at user's request Explanation: See above. User Action: None.
14.250 – 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.
14.251 – 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.
14.252 – 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.
14.253 – 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.
14.254 – CMPBYINVW
view <str> cannot be transferred Explanation: In a DEFINE TRANSFER statement, you are attempting to move a view which references a COMPUTED_BY field which contains an unsupported value expression. User Action: Reenter the DEFINE TRANSFER statement and omit the view that contains the COMPUTED_BY field that uses the unsupported value expression. Refer to the DEFINE TRANSFER statement in the Replication Option for Rdb Handbook for information on what value expressions are supported for a COMPUTED_BY field.
14.255 – 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.
14.256 – 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.
14.257 – COL_DROPPED
collating sequence dropped for non-text field <str> Explanation: A collating sequence was defined on a non-text field. This collating sequence is dropped from the field. User Action: None.
14.258 – 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.
14.259 – COMPNOTRANS
<str> in relation <str> will not be transferred Explanation: You entered a SELECT FIELDS ALL clause in the DEFINE TRANSFER statement to move a relation that contains a COMPUTED_BY field using a value expression that is unsupported. The DEFINE TRANSFER statement is accepted with all the fields of this MOVE RELATION clause except the specified COMPUTED_BY field that is unsupported. User Action: Refer to the DEFINE TRANSFER statement in the Replication Option for Rdb Handbook for information on what value expressions are supported.
14.260 – 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.
14.261 – CONALREXI
constraint <str> already exists in this database Explanation: You requested that a constraint be named with the name of an existing constraint. User Action: Choose a different name.
14.262 – CONAMBIG
the constraint <str> was not qualified and is in multiple
databases
Explanation: You must qualify the constraint with database
handles when accessing more than one database containing
that constraint.
User Action: Make sure the INVOKE statements include
qualifiers, and retype the query using the appropriate
qualifier.
14.263 – 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.
14.264 – CONFATRSPEC
conflicting or contradictory attributes specified Explanation: You specified attributes which cannot be used together. Because Oracle Rdb cannot determine which attribute to use, it rejects the command. User Action: Respecify the DDL without the redundant clauses.
14.265 – CONFTXNOPTION
Do you really want to <str> this transaction? [<char>]: Explanation: Confirm that the user actually wants to take the action.
14.266 – CONNOTDEF
constraint <str> is not defined in database Explanation: The specified constraint does not exist in the current database. User Action: Invoke the correct database. Check the constraint name for correct spelling. Check the constraint definition to make sure you did not specify a term where the constraint name was expected.
14.267 – CONVARDEF
context variable <str> is already defined Explanation: The current statement attempts to define an existing context variable such as the P in OPEN IN STREAM S FOR P IN PORT. However, the context variable has already been defined in another RSE. User Action: Use another context variable, or close the stream in which the context variable is defined.
14.268 – CONVARILL
cannot use the context variable, <str>, declared in the store Explanation: A context variable was used in a STORE statement that was the same as the one declared in the STORE RSE. Example: STORE J IN PORT USING J.CITY = J.COUNTRY END_STORE User Action: Change the command to include the correct context variable.
14.269 – CONVARUND
context variable <str> is not defined Explanation: The current statement attempts to use a context variable that is not defined in a current RSE. You may have closed the stream in which the context variable was defined. User Action: Use the context variable within a FOR loop, OPEN STREAM loop, or aggregate expression.
14.270 – 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.
14.271 – CONVONLY
only a CONVERT command may be issued Explanation: User Action:
14.272 – CS_ERR
error retrieving collating sequence <str> Explanation: The collating sequence could not be retrieved -- see the message that follows. User Action: Correct the problem and try the operation again.
14.273 – CVT_PROCEED
convert proceeding Explanation: You issued a CONVERT command and the conversion is underway. User Action: Wait a moment.
14.274 – 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.
14.275 – 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.
14.276 – 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.
14.277 – DATCONERR
data conversion error Explanation: An error occurred during data conversion. Refer to next message. User Action: The secondary message should clarify the problem.
14.278 – DATNOTSUP
date data type not supported in this context Explanation: The output of a date value to the language file is not supported. Example: HV = rdb$missing(date field). User Action: Do not use dates in this manner.
14.279 – DATTYPUNK
datatype unknown. Expression cannot use only host variables Explanation: An assignment or a Boolean expression must have at least one database field or literal. User Action: You must use a database variable or literal in the expression.
14.280 – DBACTIVE
database is already being used Explanation: You attempted to open a database that is already being used. You can only open a database that is not being accessed. User Action: Wait for all users to finish using the database, or force the users off by closing the database.
14.281 – 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.
14.282 – DBHANDUNK
no DATABASE command specified a handle of <str> Explanation: You specified an unknown database handle in a context variable table definition. User Action: Check the query and the INVOKE statement to make sure they match.
14.283 – DBHDLREQ
db handle should be specified for EXTRACTION ROLLUP transfers Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you are attempting to move a relation without specifying the database handle of the source database. User Action: Reenter the DEFINE TRANSFER statement by specifying the database handle of the source database for each of the move-relation-clauses.
14.284 – DBKNOTALL
DB key references are not allowed in VALID IF expressions Explanation: You entered a VALID IF expression that did not contain an operator, literal value, or field name. User Action: Check the Oracle Rdb Reference Manual for details on VALID IF.
14.285 – 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 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.
14.286 – DBNAMEHV
a database name is not allowed in a qualified host variable Explanation: You cannot use a database field name to qualify a host variable. For example, you cannot have the following expression: FOR E IN EMPLOYEES WITH E.EMPLOYEE_ID = HOST_VAR(E.EMPLOYEE_ID) ~.~.~. User Action: Use an additional GET statement to assign the value of the database field to another host variable and use that host variable to qualify the first host variable. For example, FOR E IN EMPLOYEES GET HOST-VAR-2 = E.EMPLOYEE_ID FOR E1 IN EMPLOYEES WITH E.EMPLOYEE_ID = HOST-VAR(HOST-VAR-2) ~.~.~. END_FOR END_FOR
14.287 – 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.
14.288 – 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.
14.289 – 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.
14.290 – DBNOTACTIVE
database is not being used, or must be manually opened first Explanation: You attempted to close a database that is not open, or you attempted to access a closed database that requires manual open. User Action: There is no need to close the database - it is already closed. If you are attempting to access a closed database that requires manual open, open the database first.
14.291 – 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.
14.292 – DBNOTSPEC
db handle not specified for segmented string creation Explanation: A CREATE_SEG was done with more than one database invoked. You did not specify in which database the segmented string was to be created. User Action: Add a database handle to the segment handle.
14.293 – 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.
14.294 – 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.
14.295 – DBRBOUND
attach not allowed while your process is being recovered Explanation: The database recovery process (DBR) is currently recovering an image for your process. While the recovery operation is running, you cannot start another image that attempts to attach/bind to the database. User Action: You can attach/bind to another database. Otherwise, you must wait for the database recovery process to complete recovery of your previous image.
14.296 – 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.
14.297 – DB_CVT_FAIL
database conversion failed Explanation: You issued a CONVERT command and the conversion has failed. User Action: Accompanying messages should indicate further action. The conversion process will have left the database in an inconsistent state so you will have to restore a copy of the database from the backup media and retry the CONVERT command on the restored copy of the database.
14.298 – DB_CVT_SCS
database <str> successfully converted from version <num>.<num> to <num>.<num> Explanation: You issued a CONVERT command and the conversion has completed. User Action: None.
14.299 – DB_HANDEC
handle already declared Explanation: You declared a database handle through ACMS. This interferes with defining a handle through the interpreter. User Action: You should not specify another handle.
14.300 – DB_HANDEC2
handle already declared Explanation: You declared a database handle through ACMS. This interferes with defining a handle through the interpreter. This also interferes with declaring multiple database handles. User Action: You should not specify another handle.
14.301 – DB_HANLON
the DB handle must be a longword Explanation: Database handles that are passed to RDB$INTERPRET must be longwords passed by descriptor. User Action: Define the database handle to be a longword. Examples: For COBOL: 01 DBHANDLE PIC S9(9) COMP. For FORTRAN: INTEGER*4 DBHANDLE. For BASIC: LONG DBHANDLE.
14.302 – DB_NOTCVT
database not converted Explanation: You issued a convert command and the conversion was not attempted. User Action: You should correct the problem and retry the convert.
14.303 – DDALERR
Replication Option for Rdb fatal error Explanation: You entered a Replication Option for Rdb statement which failed. User Action: Refer to the explanation in the user action section of the secondary error message.
14.304 – 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.
14.305 – DEGMODSPC
only one degree mode may be specified for a transaction Explanation: You specified two degree modes (consistency or concurrency) in a START_TRANSACTION statement. User Action: Specify one degree mode in your START_TRANSACTION statement.
14.306 – DELETEFAILS
Cache file <str> deletion failed Explanation: Attempt made to delete non existing file. User Action: Check for the existence of the cache file.
14.307 – 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.
14.308 – DESCTOOBIG
the description clause's maximum length is <num> Explanation: Oracle Rdb currently has a limit for a description clause size. User Action: Use a shorter description clause.
14.309 – DOENBLAIJ
after-image journaling must be enabled to ensure recovery Explanation: After adding an AIJ journal, it is necessary to enable AIJ journaling (if it is not already enabled). Failure to enable AIJ journaling will result in the AIJ file being NOT recoverable. User Action: IT IS HIGHLY RECOMMENDED that after-image journaling be enabled AS SOON AS POSSIBLE.
14.310 – 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.
14.311 – DTFMTTOOBIG
date or time format must be in the range 1 to 999 Explanation: You entered a DATE or TIME value outside the range 1 to 999 in the SET DATE_FORMAT statement. User Action: Enter a value greater than or equal to 1 and less than or equal to 999.
14.312 – DTONCEEACH
you can specify DATE or TIME only once each Explanation: You entered DATE date-number twice or TIME time-number twice in the SET DATE_FORMAT statement. User Action: Enter nothing, or enter DATE, TIME, or one of each with SET DATE FORMAT.
14.313 – 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.
14.314 – DUPAIJNAM
duplicate AIJ name "<str>" specified Explanation: A duplicate AIJ name was specified during AIJ journal addition. Each AIJ name is used to identify a specific journal and must be unique within a database. User Action: Please specify a unique AIJ name.
14.315 – 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.
14.316 – DUPFLDDEF
field <str> has different definitions in relations <str> and <str> Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you are attempting to move a field which does not have the same definition in all the source databases. Since we cannot have two definitions of a field in the target database, the DEFINE TRANSFER command is invalid. User Action: Reenter the DEFINE TRANSFER statement by including only one definition of the field mentioned above or by changing all the definitions of this field into the same type.
14.317 – 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.
14.318 – 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.
14.319 – EMPTYFILE
<str> file is empty Explanation: The file is empty. User Action: None.
14.320 – ERRDET
an error was detected Explanation: An "error level" (-E-) error condition was detected by RDO and returned to DCL during the execution of an RDO statement. User Action: If possible, run the statement(s) again in interactive RDO and read any additional RDO error messages to determine what caused the error condition. Then fix the error. Remember, in a DCL command procedure containing RDO statements, use the $SEVERITY symbol to test for RDO$_ERRDET.
14.321 – 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.
14.322 – 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.
14.323 – 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.
14.324 – ERRWRITE
error writing file Explanation: An error occurred during a file write. User Action: Examine the secondary message for more information.
14.325 – 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.
14.326 – EXPCV_DOT
expected context variable and dot, host variables not permitted here Explanation: You attempted to use a name where a variable or literal was required. The error message indicates that you probably forgot to type the context variable and a period before a field name, or you forgot to use quotation marks around a quoted string. User Action: Add a context variable and a period or use a literal.
14.327 – 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.
14.328 – EXTNOTSUP
EXTERNAL database handles are not supported for RDB$INTERPRET Explanation: External database handles are not supported for RDB$INTERPRET. Only LOCAL and the default database handle are supported. External database handles apply only to preprocessors that can declare variables for database handles. User Action: For database handles that must be accessed in multiple modules, use LOCAL. Otherwise, use the default database handle.
14.329 – EXTRADATA
unexpected data at the end of the RBR file Explanation: Internal error - found more data than expected in the Oracle Rdb interchange file (RBR). User Action: Contact your Oracle support representative for assistance.
14.330 – 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.
14.331 – FETNOTDON
a fetch has not been done yet for stream <str> Explanation: You referenced a stream, but you did not issue a FETCH statement for that stream. User Action: Type FETCH <stream name>.
14.332 – FIELD_EXISTS
field <str> already exists in this database Explanation: You requested that a field be named with the name of an existing field. User Action: Choose a different name.
14.333 – FIENOTALL
field, <str>, is not allowed in the VALID IF expression for field <str> Explanation: You entered a field name in a VALID IF clause that does not match the name of the field being defined. User Action: Check the Oracle Rdb Reference Manual for details on VALID IF, or use the name of the field you are defining.
14.334 – FIENOTREN
field <str> cannot rename CDD field <str> Explanation: You requested that a field being defined from a CDD definition be named something other than the name of the CDD field. User Action: Respecify the field definition using the CDD field name.
14.335 – FIENOTSEG
field, <str>, is not a segmented string Explanation: You attempted a START_SEGMENTED_STRING operation using a field that is not a segmented string. User Action: Use a segmented string field with the START_SEGMENTED_STRING statement.
14.336 – FILACCERR
error <str> file <str> Explanation: A file-access error occurred. User Action: Examine the secondary message for more information.
14.337 – 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.
14.338 – FLDAMBIG
field <str> is not unique in previous relations in the CROSS Explanation: You specified a field that does not exist in the previous relations specified by the CROSS clause. User Action: The relation definition associated with the context variable does not include a definition for the specified field. You may have specified the wrong context variable with the field or mistyped the field name.
14.339 – FLDNOTCRS
field <str> was not found in previous relations in the CROSS Explanation: You specified a field that is not in the relations specified in the CROSS clause. User Action: The relation definition associated with the context variable did not include a definition for the specified field. You may have specified the wrong context variable with the field or mistyped the field name.
14.340 – FLDNOTDEF
field <str> is not defined in relation <str> Explanation: You specified a field that does not exist in the named relation. User Action: The relation definition associated with the context variable did not include a definition for the specified field. You may have specified the wrong context variable with the field or mistyped the field name.
14.341 – FLDNOTINREL
<str> is not a field in relation, <str> Explanation: The field you specified is not part of the named relation. User Action: Check the relation definition for the correct field name, or specify another relation.
14.342 – FLDNOTREFD
defined field, <str>, is not used in VALID IF clause Explanation: You defined a field with a VALID IF clause that does not reference the defined field. User Action: Define the field again, and name that field in the VALID IF clause.
14.343 – FLUINPBUF
indirect command file buffer flushed for Control C Explanation: You entered CTRL/C while executing an indirect command file. User Action: None.
14.344 – FOREIGN_NOUNQCON
no Primary/Unique constraint matching foreign constraint <str> Explanation: The foreign relation constraint must have a primary or unique constraint (with its key matching the foreign relation constraint's referenced key) defined and stored or defined in the same relation with the foreign relation constraint. User Action: Correct the problem and try the operation again.
14.345 – FOREIGN_REFGREFD
referencing/referenced fields number mismatch in foreign constraint <str> Explanation: The number of referencing and referenced fields must be equal in the foreign relation constraint. User Action: Correct the problem and try the operation again.
14.346 – 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.
14.347 – GARBLED
interchange file is corrupt Explanation: Internal error - probably mismatched BEGIN and END clumps. User Action: Contact your Oracle support representative for assistance.
14.348 – GETTXNOPTION
Do you wish to COMMIT/ABORT/IGNORE this transaction: Explanation: Ask the user whether to COMMIT/ABORT/IGNORE this blocked transaction.
14.349 – 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.
14.350 – 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.
14.351 – 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.
14.352 – 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.
14.353 – 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).
14.354 – 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.
14.355 – HOTCMDPEND
request cannot be completed due to pending hot standby command Explanation: A Hot Standby command was pervious requested from this node using the /NOWAIT qualifier; the command has not yet completed. The command just requested cannot be completed until the Hot Standby feature command already active but pending on this node has first completed. User Action: The requested Hot Standby command must be completed prior to issuing this command. Use the SHOW USERS command to indicate the status of the Hot Standby command.
14.356 – HOTEXCHMSG
error exchanging replication message Explanation: User Action:
14.357 – HOTFAILURE
hot standby failure: <str> Explanation: A hot standby failure occurred. User Action: Examine the secondary message for more information.
14.358 – HOTLCLCNCT
error allocating local network connection Explanation: User Action:
14.359 – 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.
14.360 – HOTNOCIRCEXT
cannot switch from circular to extensible AIJ journaling if replication active Explanation: User Action: Terminate database replication first.
14.361 – 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.
14.362 – 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.
14.363 – 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.
14.364 – 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.
14.365 – HOTRECVMSG
error receiving replication message Explanation: User Action:
14.366 – HOTREMCNCT
error allocating remote network connection Explanation: User Action:
14.367 – HOTREMDELT
error deleting replication connection Explanation: User Action:
14.368 – HOTREMDSCT
error disconnecting from replication server Explanation: User Action:
14.369 – HOTRWTXACTV
database in use with active or pre-started read/write transactions Explanation: Database replication cannot be started on the standby database if there are processes with active or pre-started read/write transactions. User Action: All read/write transaction activity must be stopped prior to starting database replication on the standby database.
14.370 – 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.
14.371 – 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.
14.372 – HOTSVRCNCT
error connecting to replication server Explanation: User Action:
14.373 – HOTSVRFIND
error identifying remote replication server Explanation: User Action:
14.374 – HOTWRONGDB
attempt to start replication for wrong master database Explanation: An attempt has been made to start replication on a master database whose standby database is already replicating a different master database. The master root file name does not match the name used when replication was first started on the standby database. This could happen if you copied or renamed the master database root file, or if the file was created using a concealed logical device name and that logical name is no longer defined. User Action: Ensure that the specified standby database is correct. If so, ensure that replication on the standby database has been fully terminated; replication termination occassionally has long-duration shutdown processing to be performed. If the master database rootfile had been moved, rename or copy the root file back to its original name or location, or redefine the necessary concealed logical device name in the system logical name table.
14.375 – HOWCHANOT
no attribute specified for command to change field <str> Explanation: You tried to change a field but did not specify any attribute to change. User Action: Specify an attribute to change.
14.376 – 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.
14.377 – ILLBEGIN
file <str> is corrupt or not an Oracle Rdb interchange file Explanation: IMPORT can recreate databases only from the Oracle Rdb interchange file (RBR). This file is not an Oracle Rdb interchange file (RBR). User Action: Retry the operation with the correct file name.
14.378 – ILLCHAR
illegal character detected Explanation: An illegal character has been detected. User Action: Use only valid characters.
14.379 – 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.
14.380 – 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.
14.381 – IMP_CDD_NODATA
importing a CDD dictionary with NODATA is not allowed Explanation: You used the NODATA option when importing a CDD/Plus dictionary database. User Action: You cannot use the NODATA option when importing CDD/Plus dictionaries. The resulting database is not usable by CDD/Plus. Use the DATA option and try again.
14.382 – IMP_DDLWARN
warnings reported while importing or creating object <str> Explanation: Warnings were issued during the import of the named object. This may indicate that the object is valid but may not be optimal. For instance, the new definition 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.
14.383 – IMP_IDXNOTDEF
index <str> not defined - check spelling of the relation name Explanation: The IMPORT operation could not process a DEFINE INDEX clause because the named relation was not defined in the database. User Action: Check that the relation name was spelled correctly.
14.384 – IMP_IDXNOTDEL
index <str> not deleted - check spelling of the index name Explanation: The IMPORT operation could not process a DELETE INDEX clause because the named index was not defined in the database. User Action: Check that the index name was spelled correctly.
14.385 – IMP_IDX_CONFLICT
DEFINE and DELETE INDEX <str> specified Explanation: You specified a DEFINE and DELETE INDEX using the same name. User Action: Specify either a DEFINE or a DELETE INDEX.
14.386 – IMP_IDX_TWICE
DEFINE or DELETE INDEX <str> specified twice Explanation: You specified a DEFINE or DELETE INDEX twice using the same name. User Action: Specify a INDEX name only once.
14.387 – IMP_STANOTDEL
storage area <str> not deleted - check spelling of the storage area name Explanation: The IMPORT operation could not process a DELETE STORAGE AREA clause because the named storage area was not defined in the database. User Action: Check that the storage area name was spelled correctly.
14.388 – IMP_STMNOTDEF
storage map <str> not defined - check spelling of the relation name Explanation: The IMPORT operation could not process a DEFINE STORAGE MAP clause because the named relation was not defined in the database. User Action: Check that the relation name was spelled correctly.
14.389 – IMP_STMNOTDEL
storage map <str> not deleted - check spelling of the storage map name Explanation: The IMPORT operation could not process a DELETE STORAGE MAP clause because the named storage map was not defined in the database. User Action: Check that the storage map name was spelled correctly.
14.390 – IMP_STO_CONFLICT
DEFINE and DELETE STORAGE AREA <str> specified Explanation: You specified a DEFINE and DELETE STORAGE AREA using the same name. User Action: Specify a either a DEFINE or a DELETE STORAGE AREA.
14.391 – IMP_STO_MAP_CONFLICT
DEFINE and DELETE STORAGE MAP <str> specified Explanation: You specified a DEFINE and DELETE STORAGE MAP using the same name. User Action: Specify either a DEFINE or a DELETE STORAGE AREA.
14.392 – IMP_STO_MAP_TWICE
DEFINE or DELETE STORAGE MAP <str> specified twice Explanation: You specified a DEFINE or DELETE STORAGE MAP twice using the same name. User Action: Specify a STORAGE MAP name only once.
14.393 – IMP_STO_TWICE
DEFINE or DELETE STORAGE AREA <str> specified twice Explanation: You specified a DEFINE or DELETE STORAGE AREA twice using the same name. User Action: Specify a STORAGE AREA name only once.
14.394 – INDEXTS
there is another index named, <str>, in this database Explanation: The index name you tried to define already exists. This message is also printed during an IMPORT operation if the backup file contains multiple definitions of an index. Duplicate definitions may indicate corruption of the .RBR file, or improper operation during the EXPORT operation. User Action: Try another index name. If this message arose during an IMPORT operation, then contact your Oracle support representative for assistance.
14.395 – INDNOEXI
index <str> does not exist in this database Explanation: The index you attempted to change was not found. User Action: Check the name of the storage map using the SHOW command and try again to change it.
14.396 – INSFRPGS
physical memory has been exhausted Explanation: Physical memory has been exhausted on the machine, typically because of an excessive number of cache global sections, or excessively large cache global section sizes. User Action: If possible, increase the amount of physical memory on the machine. Reduce the number of cache global sections, or reduce the size of each active cache global sections. Possibly moving a cache from SSB to VLM will also solve this problem. It might be necessary to delete some caches to alleviate this problem. Also, re-configuring the operating system parameters may be necessary to reduce physical memory consumption.
14.397 – INTEGDBDIF
Database filespec must equate to filespec <str> recorded in CDD Explanation: The INTEGRATE database filespec and the filespec recorded with the dictionary database definitions found at the specified pathname refer to different databases. User Action: Reissue the command with a filespec that corresponds to the database referenced in the data dictionary, or with a different pathname.
14.398 – INTEGFRFAIL
attempt to INTEGRATE FROM nonexistent CDD entity <str> Explanation: The data dictionary entity required for INTEGRATE FROM does not exist. User Action: Respecify a path that points to an existing data dictionary entity.
14.399 – INTONOTALW
INTO RELATION clause is not allowed in this context Explanation: In a DEFINE TRANSFER statement of an EXTRACTION or REPLICATION transfer, you have specified an INTO RELATION clause. User Action: Reenter the DEFINE TRANSFER statement by not specifying an INTO RELATION clause.
14.400 – INTSYNERR
<str> <str> Explanation: This message is used by the interpreter to put the line with the syntax error into the message vector. User Action: Call RDB$SIGNAL and find the syntax error.
14.401 – INVCHAINP
invalid character in input Explanation: The input contains an illegal or unrecognizable character. User Action: Correct the source text and resubmit the job.
14.402 – 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.
14.403 – INVCONS
unable to IMPORT constraint <str> Explanation: Internal error - the named constraint will not appear in the recreated database. User Action: Contact your Oracle support representative for assistance. In the meantime, you can redefine this constraint explicitly.
14.404 – 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.
14.405 – INVDBKREF
invalid use of a database key Explanation: Dbkeys cannot be used in an RSE except to check for equality or non-equality with a dbkey fetched from the database. User Action: Correct the problem and try the operation again.
14.406 – 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.
14.407 – INVFLD
unable to IMPORT field <str> Explanation: Internal error - the named field will not appear in the recreated database. User Action: Contact your Oracle support representative for assistance.
14.408 – INVFLDPRO
invalid protection defined for field, only MODIFY allowed Explanation: Only MODIFY may be specified for field protection. User Action: Do not specify field privileges other than MODIFY.
14.409 – INVFLDSIZE
specified invalid field size Explanation: You specified an illegal field size. User Action: Please specify a field size between 0 and 32768 exclusive.
14.410 – 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.
14.411 – INVINDEX
unable to IMPORT index <str> Explanation: Internal error - the named index will not appear in the recreated database. User Action: Contact your Oracle support representative for assistance. In the meantime, you can redefine this index explicitly.
14.412 – INVMARKOP
invalid markpoint commit/rollback for TSN <num>:<num>, MARK_SEQNO <num> Explanation: A fatal, unexpected error was detected by the database management system during the commit or rollback of a markpoint. This message indicates the "transaction sequence number" of the transaction and the "markpoint sequence number" of the markpoint that has to be committed or rolled back. User Action: Contact your Oracle support representative for assistance.
14.413 – INVNODESIZE
invalid node size parameter specified Explanation: The command specified a number for a node size which was invalid. It was either less than or equal to zero or greater than 32768. User Action: Review the command and respecify using a node size within the above range (but big enough to meet the implementation requirements).
14.414 – INVNOTDON
no DATABASE invoked yet, please issue a DATABASE command Explanation: You must invoke a database before you issue an RDO statement. can be executed. User Action: Invoke the database, and then issue the RDO statement.
14.415 – 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.
14.416 – INVPERCENTFILL
invalid percent fill parameter specified Explanation: The command specified a number for a percent fill which was invalid. It was either less than or equal to zero or greater than 100. User Action: Review the command and respecify using a percent fill within the above range.
14.417 – INVPRIVNAMES
invalid privilege names specified in message file Explanation: The names specified in PRIV_NAMES0 and PRIV_NAMES1 were incorrect in some way. User Action: Contact your Oracle support representative for assistance.
14.418 – INVRELVIEW
unable to IMPORT relation or view <str> Explanation: Internal error - the named relation or view (and its data) has been lost. User Action: Contact your Oracle support representative for assistance.
14.419 – INVSEGSTRATR
invalid segmented string attribute Explanation: You specified a MISSING VALUE or VALID IF clause along with a segmented string data type. User Action: You should respecify the data definition statement without the MISSING VALUE or VALID IF clauses.
14.420 – INVSTOMAP
storage map is invalid as specified Explanation: You specified an invalid storage map. User Action: Review the command and issue it correctly.
14.421 – INVTRG
unable to IMPORT trigger <str> Explanation: Internal error - the named trigger will not appear in the recreated database. User Action: Contact your Oracle support representative for assistance. In the meantime, you can redefine this trigger explicitly.
14.422 – 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.
14.423 – INXNOFLD
no field name in the index definition Explanation: You must specify one or more field names in the index definition. User Action: Correct the index definition and retry the command.
14.424 – IOERROR
an unexpected I/O error occurred Explanation: Unable to read any more of the Oracle Rdb interchange file (RBR); part of the database may be imported. User Action: Correct the problem indicated by the message that follows this message and retry the operation.
14.425 – 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.
14.426 – 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.
14.427 – LANFILEXT
<str> is the language file extension, please use another
extension
Explanation: The input file type you specified to the
preprocessor is the same file type as the output file type.
User Action: Rename the file with the default file
specifications and run the preprocessor again. Refer to the
______ ___ _____ __
default file specifications in the Oracle Rdb Guide to
___________
Programming.
14.428 – 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.
14.429 – 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.
14.430 – LENMISMAT
truncating right hand side string for assignment to field <str> Explanation: You executed a STORE or MODIFY statement, and the string on the right hand side of the equation is longer than the string on the left. User Action: The message is just a warning. You can issue a MODIFY statement to correct the store or a ROLLBACK statement to terminate the transaction.
14.431 – LHSNOTDBN
the left hand side of the assignment expression is not a DB name Explanation: The left side of an assignment expression in a STORE or MODIFY statement must be a field name qualified by a context variable. Example: P.CITY User Action: Use a qualified database field name in the left side of an assignment expression.
14.432 – LHSNOTVAR
the left hand side of the assignment expression is not a variable Explanation: The left side of an assignment expression in a GET command must be a host variable. For preprocessed statements, the variable must be a host language variable. For Callable RDO, the variable must be "!VAL". User Action: Use a host variable in the left side of an assignment expression.
14.433 – 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.
14.434 – LOGADDCCH
added record cache definition "<str>" Explanation: A new record cache definition has been successfully added the the database.
14.435 – 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.
14.436 – 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.
14.437 – 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.
14.438 – 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.
14.439 – LOGDELAIJ
deleted temporary after-image journal file <str> Explanation: This message indicates the action taken on a specific file.
14.440 – LOGDELCCH
deleted record cache definition "<str>" Explanation: A record cache definition has been successfully deleted from the database.
14.441 – LOGMODCCH
modifying record cache definition "<str>" Explanation: The parameters for a record cache are in the process of being modified.
14.442 – LOGMODSPM
modified <num> spam page(s) Explanation: None.
14.443 – LOGMODSTO
modifying storage area <str> Explanation: The parameters for a storage area are in the process of being modified.
14.444 – LOGRECOVR
<num> transaction(s) <str> Explanation: Database recovery was successful. The specified number of transactions were re-applied to the database, ignored, or rolled back. User Action: None.
14.445 – 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.
14.446 – 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.
14.447 – 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.
14.448 – LOOK_FOR
syntax error, looking for <str>, found <str> instead Explanation: The syntax expected a specific keyword, but you entered another. User Action: Check the syntax and reenter the correct keyword.
14.449 – LOOK_FOR_CON
<str> Explanation: This message is used for listing syntactically legitimate alternatives. User Action: Consider options from the list.
14.450 – LOOK_FOR_FIN
found <str> instead Explanation: This terminates the list of syntactically valid alternatives and should give you an idea of what has happened. User Action: Reenter the statement, or use EDIT to correct it.
14.451 – LOOK_FOR_STT
syntax error, looking for: Explanation: The syntax expected a list of things, list follows. User Action: Consider options from the list.
14.452 – LOOK_FOR_UNTERM
syntax error, looking for <str>, found <str> instead Explanation: This is issued with a RDO-F-BUGCHK because it indicates that a severe error has occurred in the syntax tables. User Action: Contact your Oracle support representative for assistance. You will need to record the exact command line as typed (use EDIT to write it to a file). Then consider finding a workaround.
14.453 – 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.
14.454 – LRSNOOUT
AIJ Log Roll-Forward Server does not have an output file Explanation: The AIJ Log Roll-Forward Server process does not have an output file associated with it. User Action: Use the /OUTPUT qualifier to specify an output filename when database replication is started on the standby database.
14.455 – 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.
14.456 – MAXFLDPRTSTR
maximum number of fields in a print star relation is <num> Explanation: You used a PRINT <context variable>.* for a relation that has too many fields. User Action: Name the fields explicitly in the PRINT statement.
14.457 – MAXLINLEN
maximum allowed line_length is <num> bytes Explanation: You entered a line length that exceeds the limit. User Action: Choose a smaller length.
14.458 – MAXNESEXC
maximum statement nesting level is exceeded Explanation: You exceeded the maximum nesting of FOR and START_STREAM statements. User Action: Reduce the nesting level.
14.459 – MAXRELEXC
maximum number of relations in an RSE has been exceeded Explanation: You exceeded the maximum number of relations in an RSE. There are too many CROSS clauses. User Action: Reduce the number of CROSS expressions.
14.460 – MAXVOLLABEXC
maximum size of volume label is <num> Explanation: You entered a name for a volume label that exceeds the limit for a journal file name. User Action: Choose a smaller name.
14.461 – 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.
14.462 – MISMMORDD
missing either month or day field in date string Explanation: The date string must contain the month and day field. Otherwise, it will not be converted to the DATE data type. User Action: Re-enter the DATE data item and specify both the month and day fields.
14.463 – MONFLRMSG
failure message received from the monitor Explanation: An error happened in the monitor process. The user process received the error message. User Action: Examine the monitor log on the node where the user program was running to see messages relating to the monitor error.
14.464 – MONMBXOPN
monitor is already running Explanation: The monitor has already been started by another user. User Action: No action is required.
14.465 – 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.
14.466 – MULSPECATR
attribute is specified redundantly Explanation: You specified a field attribute more than once. Because Oracle Rdb cannot determine which attribute to use, it rejects it. User Action: Respecify the data definition statement without the redundant clauses.
14.467 – MUSINVPATH
cannot DEFINE FROM CDD unless database invoked by pathname Explanation: You requested that a field or relation be defined from the CDD but no CDD has been attached via an INVOKE by PATHNAME. User Action: INVOKE the database by PATHNAME, then respecify the definition.
14.468 – 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.
14.469 – MVRELABSNT
no MOVE RELATION clause is specified in an EXTRACTION ROLLUP transfer Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you have not specified any MOVE RELATION clause. User Action: Since a MOVE RELATIONS ALL clause is not allowed in this context, you have to explicitly specify the MOVE RELATION clauses. Reenter the DEFINE TRANSFER statement by specifying the MOVE RELATION clauses explicitly.
14.470 – NEEDSNOEXTEND
area <str> already has <num> page(s) Explanation: The extension of the specified storage area was trivial, as the number of pages before was exactly same. User Action: Check page count of the current area allocation. (If it should differ)
14.471 – NETACCERR
error <str> <str> network <str> Explanation: A network-access error occurred. User Action: Examine the secondary message for more information.
14.472 – NOAGGALL
aggregate expressions are not allowed in MOVE RELATION clauses Explanation: You entered a MOVE RELATION clause that contained an aggregate expression. Only an operator, literal value, or field name are allowed in a MOVE RELATION clause. User Action: Check the Replication Option for Rdb Handbook or the RDO Reference Manual for details on the MOVE RELATION clause. Reenter the DEFINE TRANSFER statement with a correct MOVE RELATION clause.
14.473 – 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.
14.474 – 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.
14.475 – 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.
14.476 – NOAIJSERVER
database replication server is not running or running on other node Explanation: The database replication server process is not running on the standby node specified, or has abnormally terminated. There may also be a problem with the mailbox used to communicate with the database replication server. User Action: Check the system to determine whether or not the database replication server process is actually running on your system. Check the use of cluster aliases, as the replication connection may have been attempted on another node of the designated cluster. If the database replication server process does not appear to be running, have your database administrator start the replication server, and try again. If the database replication server process appears to be running properly, then the problem may be related to the mailbox by which user processes communicate with the replication server process. Make sure the "server name" specified for both the live and standby databases logical are unique and identical. On VMS platforms, the "server name" is used to create a logical of the same name that resides in a logical name table accessible to all users, typically the LNM$PERMANENT_MAILBOX name table. If the replication server process abnormally terminated, a bugcheck dump will normally be produced. Search the bugcheck dump for a string of five asterisks (*****) using the SEARCH/WINDOW command. You will see a line with a format similar to this: ***** Exception at <address> : <database module name> + <offset> %facility-severity-text, <error text> The exception line will be followed by one or more additional errors that will help you to determine what caused the replication server process to fail. Typically, the problem is caused by insufficient quotas or system resources. However, other possible causes include misdefined or undefined filename logicals. Depending 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.
14.477 – 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.
14.478 – NOANYALL
ANY and UNIQUE are not allowed in a MOVE RELATION clause Explanation: You entered a MOVE RELATION clause containing ANY or UNIQUE. Only an operator, literal value, or field name are allowed in a MOVE RELATION clause. User Action: Check the Replication Option for Rdb Handbook or the RDO Reference Manual for details on the MOVE RELATION clause. Reenter the DEFINE TRANSFER statement with a correct MOVE RELATION clause.
14.479 – 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).
14.480 – 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.
14.481 – 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).
14.482 – NOCDD
there is no CDD on this system, specify a filename on the DATABASE command Explanation: Because there is no CDD running on this system, you cannot invoke a database using a path name. User Action: Invoke the database with the database file name.
14.483 – NOCDDUPDAT
database invoked by filename, the CDD will not be updated Explanation: (In RDO or Rdb$INTERPRET) You issued a data definition statement after invoking by file name. User Action: This is a warning. You can roll back and invoke the database by specifying the path name. This ensures that data definitions are updated both in the data dictionary and in the database itself.
14.484 – 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.
14.485 – NOCMPBYRES
computed field <str> in relation <str> not IMPORTed Explanation: You specified a computed field in your database that could not be imported. Perhaps the field references other fields and relations that were deleted from the database by an older version of the software that would have permitted such a thing. User Action: You must investigate the problem further. The relation should have been properly imported except for the listed field.
14.486 – NOCOLRES
unable to IMPORT collating sequence <str> Explanation: This collating sequence could not be imported -- see the message that follows. User Action: Correct the problem and try the operation again.
14.487 – NOCONGET
the concatenate operator cannot be used within a GET statement Explanation: The concatenate operator may not be used within a GET statement. User Action: You must do the concatenation outside of Oracle Rdb statements.
14.488 – NOCONRES
unable to IMPORT constraint <str> Explanation: Could not import this constraint -- see the message that follows. User Action: Correct the problem and retry the operation.
14.489 – 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.
14.490 – NODATRES
remaining data for this relation will be ignored Explanation: An error occurred while you attempted to store the data; see the following message. User Action: Correct the problem and retry the operation.
14.491 – NODBHALW
database handles are not allowed in a MOVE RELATION clause Explanation: You specified a database handle for the record selection expression (RSE) in a MOVE RELATION clause. Inside a MOVE RELATION clause, database handles are not allowed for the RSE. User Action: Reenter the DEFINE TRANSFER statement omitting the database handle name.
14.492 – NODBHAN
a database handle may not be specified on this statement Explanation: You specified a database handle on a statement that either does not or can not use one. User Action: Remove the handle.
14.493 – 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.
14.494 – NODBKALL
database key references are not allowed in a MOVE RELATION clause Explanation: You entered a MOVE RELATION clause that contained a database key or a host variable. Only an operator, literal value, or field name are allowed in a MOVE RELATION clause. User Action: Check the Replication Option for Rdb Handbook or the RDO Reference Manual for details on the MOVE RELATION clause. Reenter the DEFINE TRANSFER statement with a correct MOVE RELATION clause.
14.495 – NODBNAME
a database name was not specified on a DATABASE command Explanation: You issued an INVOKE DATABASE statement that did not specify a database by file specification or data dictionary path name. User Action: Check the syntax of the INVOKE DATABASE statement.
14.496 – 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.
14.497 – NODISTBATU
attempt to start a distributed transaction with BATCH_UPDATE Explanation: You specified attributes which cannot be used together, for example, batch update and distributed transaction. User Action: Specify the START_TRANSACTION statement again without the conflicting clauses.
14.498 – NODPRIRES
Unable to import database ANSI privileges for <str> Explanation: RDO could not import these ANSI privileges; see the message that follows. User Action: Correct the problem and try the operation again.
14.499 – 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: Reenter the DEFINE TRANSFER statement by specifying the view either in a move-relations-clause or in a move-views-clause but not in both.
14.500 – NOENTRYPT
no entry point Explanation: There is no entry point for the routine in the shareable image. User Action: Make sure you are in the right Oracle Rdb environment.
14.501 – 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.
14.502 – 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.
14.503 – NOEXTLMNOENA
cannot extract - AIJ file <str> does not have LogMiner enabled Explanation: This AIJ file came from a database that did not have LogMiner enabled at the time the AIJ file was created. User Action: No user action is required. This AIJ file cannot be extracted.
14.504 – 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.
14.505 – 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.
14.506 – 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.
14.507 – 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.
14.508 – NOFLDRES
unable to IMPORT field <str> Explanation: Could not import this field. See the following message. User Action: Correct the problem and retry the operation.
14.509 – NOFPRIRES
Unable to import ANSI privileges on field <str>.<str> for <str> Explanation: RDO could not import these ANSI privileges -- see the message that follows. User Action: Correct the problem and try the operation again.
14.510 – NOFSTINREPT
FIRST clause is not allowed in MOVE RELATION clause of a REPLICATION transfer Explanation: In the MOVE RELATION clause of a REPLICATION TRANSFER definition you have entered a FIRST clause. User Action: Reenter the DEFINE TRANSFER statement without the FIRST clause in the MOVE RELATION clause.
14.511 – NOIDXRES
unable to IMPORT index <str> Explanation: Could not import this index. See the following message. User Action: Correct the problem and retry the operation.
14.512 – 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.
14.513 – NOITEMDEF
unable to define item from command line Explanation: Could not define an item from the command line. See the following message. User Action: Correct the problem and retry the operation.
14.514 – NOLOCKSOUT
no locks on this node with the specified qualifiers Explanation: No locks were found on the current node that match the specified command qualifiers. This usually indicates that either no monitors are active on this node, or no databases are currently being accessed on this node. User Action: If databases are active on the node, try using a less restrictive set of command-qualifiers.
14.515 – NOMAPRES
unable to IMPORT storage map <str> Explanation: Could not import this storage map. See the following message. User Action: Correct the problem and retry the operation.
14.516 – NOMLTIMV
attempt to move the relation <str> multiple times Explanation: You attempted to specify the same relation name more than once in the MOVE clause of a DEFINE TRANSFER statement. In a DEFINE TRANSFER statement, you can not move the same relation more than once. User Action: Reenter the DEFINE TRANSFER statement omitting the duplicate MOVE RELATION clause.
14.517 – NOMLTIMVIEW
attempt to move the view <str> multiple times Explanation: You attempted to move the named view more than once in a DEFINE TRANSFER statement. This action is not permitted. User Action: Reenter the DEFINE TRANSFER statement, specifying each view only once.
14.518 – 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.
14.519 – NOMONITOR
database monitor is not running Explanation: The database monitor process is not running or has abnormally terminated. There may also be a problem with the mailbox used to communicate with the database monitor. User Action: Check the system to determine whether or not the database monitor process is actually running on your system. If the database monitor process does not appear to be running, have your database administrator start the monitor, and try again. If the database monitor process appears to be running properly, then the problem may be related to the mailbox by which user processes communicate with the monitor process. Make sure the logical <fac>$MAILBOX_CHANNEL resides in a logical name table accessible to all users, typically the LNM$PERMANENT_MAILBOX name table. If the monitor abnormally terminated, a bugcheck dump will normally be written to the monitor log. Search the monitor log for a string of five asterisks (*****) using the SEARCH/WINDOW command. You will see a line with a format similar to this: ***** Exception at <address> : <database module name> + <offset> %facility-severity-text, <error text> The exception line will be followed by one or more additional errors that will help you to determine what caused the monitor process to fail. Typically, the problem is caused by insufficient quotas or system resources. However, other possible causes include misdefined or undefined filename logicals. Depending on the cause of the problem, take the appropriate action. If you are uncertain of what to do, contact your Oracle support representative for assistance.
14.520 – 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.
14.521 – NOMVRALL
MOVE RELATIONS ALL clause is not allowed in an EXTRACTION ROLLUP transfer Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you have specified a MOVE RELATIONS ALL clause. User Action: Reenter the DEFINE TRANSFER statement by specifying each relation explicitly in a MOVE RELATION clause.
14.522 – NOMVVROL
MOVE VIEWS clause is not allowed in an EXTRACTION ROLLUP transfer Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you have specified a MOVE VIEWS clause. User Action: Reenter the DEFINE TRANSFER statement without the MOVE VIEWS clause.
14.523 – 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.
14.524 – 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.
14.525 – NOOPTCUR
cannot optimize -- AIJ file <str> is the current AIJ file Explanation: The current AIJ file cannot be optimized, because the optimized AIJ file would not be equivalent to the current AIJ file if more journaling was done after optimization. User Action: Start a new AIJ file, and then optimize the AIJ file in question.
14.526 – 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.
14.527 – 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.
14.528 – 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.
14.529 – 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.
14.530 – NOPARAMETER
SHOW command permits no parameters Explanation: The collating sequence could not be retrieved -- see the message that follows. User Action: Correct the problem and try the operation again.
14.531 – NOPRECOMPSEL
no precompiler selected Explanation: You invoked the preprocessor without specifying the language option desired. User Action: Specify a switch or file type.
14.532 – 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.
14.533 – NOPRVMVIEW
insufficient privilege to transfer the view <str> Explanation: You attempted to transfer the named view without READ privilege on the view. You must have READ privilege on the view to be able to transfer the view in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement excluding the named view. Check the RDO Reference Manual for details on PROTECTION statements.
14.534 – NOPRVMVREL
insufficient privilege to transfer the relation <str> Explanation: You specified a relation for which you do not have READ privilege. You must have READ privilege on the relation to transfer the relation in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement excluding the named relation. Check the RDO Reference Manual for details on PROTECTION statements. Also consult your database administrator.
14.535 – NOPRVREPLI
insufficient privilege to define a replication transfer Explanation: You attempted to define a replication transfer without DEFINE privilege on the source database. To define a replication transfer, you must have DEFINE privilege on the source database. User Action: Check the RDO Reference Manual for details on PROTECTION statements. See your database administrator to obtain DEFINE privilege.
14.536 – NOPRVROLMVR
insufficient privilege to transfer the relation <str>.<str> Explanation: You specified a relation for which you do not have READ privilege in the specified database. You must have READ privilege on the relation to transfer the relation in a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement excluding the named relation. Check the RDO Reference Manual for details on PROTECTION statements. Also consult your database administrator.
14.537 – NOREDINREPT
REDUCE clause is not allowed in MOVE RELATION clause of a REPLICATION transfer Explanation: In the MOVE RELATION clause of a REPLICATION TRANSFER definition you have entered a REDUCE clause. User Action: Reenter the DEFINE TRANSFER statement without the REDUCE clause in the MOVE RELATION clause.
14.538 – NORELRES
unable to IMPORT relation <str> Explanation: Could not import this relation. See the following message. User Action: Correct the problem and retry the operation.
14.539 – NOREMVER
remote node or version number is not allowed in a log file name Explanation: You used a node name or a version number in the log file specification of a DEFINE TRANSFER statement. User Action: Reenter the DEFINE TRANSFER statement using a log file specification which contains neither a node name nor a version number.
14.540 – NOREQHAN
a request handle may not be specified on this statement Explanation: You specified a request handle on a statement that does not use one. User Action: Remove the handle.
14.541 – 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.
14.542 – NORPRIRES
Unable to import ANSI privileges on relation <str> for <str> Explanation: RDO could not import these ANSI privileges -- see the message that follows. User Action: Correct the problem and try the operation again.
14.543 – 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.
14.544 – NOSEGSTRAREA
segmented string storage area <str> is not defined Explanation: You specified a storage area in the SEGMENTED STRING STORAGE AREA clause that does not exist. User Action: Specify a storage area which is already defined in the DEFINE DATABASE statement.
14.545 – NOSELALL
SELECT FIELDS ALL clause is not allowed in an EXTRACTION ROLLUP transfer Explanation: In a DEFINE TRANSFER statement of an EXTRACTION ROLLUP transfer, you have specified a SELECT FIELDS ALL clause. User Action: Reenter the DEFINE TRANSFER statement by specifying each field explicitly in the SELECT FIELDS clause.
14.546 – 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
14.547 – 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.
14.548 – 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.
14.549 – NOSIP
transaction is not a snapshot transaction Explanation: You have already started a transaction that is not a snapshot transaction. User Action: Use COMMIT or ROLLBACK to terminate your current transaction. Use READY BATCH RETRIEVAL to start a new snapshot transaction.
14.550 – 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.
14.551 – NOSORTINREPT
SORT clause is not allowed in MOVE RELATION clause of a REPLICATION transfer Explanation: In the MOVE RELATION clause of a REPLICATION TRANSFER definition you have entered a SORT clause. User Action: Reenter the DEFINE TRANSFER statement without the SORT clause in the MOVE RELATION clause.
14.552 – 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.
14.553 – 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.
14.554 – NOSUCHDATEFMT
format DATE <num> does not exist Explanation: You entered DATE date-number where the logical LIB$DATE_FORMAT_nnn does not exist. User Action: Contact the system manager to install the date formats.
14.555 – NOSUCHLANG
specified language not defined on this system Explanation: You entered the SET LANGUAGE statement, but the logical name table LNM$LANGUAGE_xxx does not exist. User Action: Contact your system manager to make sure everything has been set up properly; the language may not be supported, or the language may have been spelled incorrectly. The language name cannot be abbreviated.
14.556 – NOSUCHTIMEFMT
format TIME <num> does not exist Explanation: You entered TIME time-number where the logical LIB$TIME_FORMAT_nnn does not exist. User Action: Contact the system manager to install the date/time formats.
14.557 – NOSUCHUSER
unknown user "<str>" Explanation: An attempt was made to access information with a user name unknown to the database (for example, sending mail to the monitor or attempting to execute a database recovery process (DBR)) or to access information with a user name unknown to the operating system (for example, no record in the UAF file). User Action: Make sure the user name is spelled correctly and has been properly identified to either the database or the operating system. Do not attempt to run DBR from DCL; this is not allowed, because the system will automatically manage database recovery. Be sure the monitor user name is correctly specified.
14.558 – NOSUPREPLI
replication transfer is not supported for this source database Explanation: You attempted to define a replication transfer on a source database which is not an Rdb database. Replication transfers can be defined only for Rdb databases. For other databases you can define only extraction transfers. User Action: If your source database is not an Rdb database, define an extraction transfer.
14.559 – 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".
14.560 – NOTAVIEW
<str> is not a view Explanation: The name you specified in a MOVE VIEWS clause is not the name of a view. User Action: Retype the DEFINE TRANSFER command with the correct view name.
14.561 – 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.
14.562 – NOTDSKFIL
filename does not specify disk device type Explanation: A file name was specified which does not reference a disk oriented device type. User Action: Check the file name for a proper disk device type.
14.563 – 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.
14.564 – NOTENUFHV
not enough host variables passed; <num> passed, at least <num> used Explanation: You did not pass enough host variables to RDB$INTERPRET. For RDB$INTERPRET, there were more !VALs in the command string than host variable descriptors passed. If one more host variable is detected by the parser than was passed, parsing stops. There could be more host variables used than the error message specifies. User Action: Supply matching number of host variables and !VALs.
14.565 – NOTEXPSEG
cannot assign an expression to RDB$VALUE or RDB$LENGTH Explanation: Your preprocessor does not support assigning an expression value to RDB$VALUE or RDB$LENGTH. User Action: You can work around this problem by assigning the value of the expression to a temporary variable. Then assign the temporary variable value to RDB$VALUE or RDB$LENGTH.
14.566 – 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.
14.567 – 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.
14.568 – 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.
14.569 – 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.
14.570 – 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.
14.571 – 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.
14.572 – NOTREQSTA
not a request statement. Can only use request options on request statement Explanation: You attempted to use a REQUEST_HANDLE or TRANSACTION_HANDLE clause in a statement that was not a request statement. Request options are not necessary on statements that are not request statements. User Action: Put the handle option clause in the request statement.
14.573 – NOTRGRES
unable to IMPORT trigger <str> Explanation: This trigger could not be imported -- see the message that follows. User Action: Correct the problem and try the operation again.
14.574 – 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.
14.575 – NOTSEGSTR
context variable <str> does not reference a segmented string Explanation: You attempted to use a context variable with RDB$VALUE or RDB$LENGTH, and the context variable does not refer to a segmented string field. User Action: Use a context variable defined for a segmented string with RDB$VALUE and RDB$LENGTH.
14.576 – 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.
14.577 – 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.
14.578 – 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.
14.579 – NOT_INSTALLED
<str> is not installed Explanation: The product is not installed on the system. User Action: The named product must be installed before the attempted statement can be successfully executed.
14.580 – 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.
14.581 – 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.
14.582 – 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.
14.583 – NOUPDCOMP
can not update computed by field, <str> Explanation: You tried to store or modify a COMPUTED BY field. This is not allowed. User Action: Restate the update removing the COMPUTED BY field.
14.584 – NOVIERES
unable to IMPORT view <str> Explanation: Could not import this view -- see the message that follows. User Action: Correct the problem and retry the operation.
14.585 – NOVIEWINREPT
view <str> is not allowed in MOVE RELATION clause of a REPLICATION transfer Explanation: In the MOVE RELATION clause of a REPLICATION TRANSFER definition you have specified a view. User Action: Reenter the DEFINE TRANSFER statement without the view in the MOVE RELATION clause. The view definition can be moved by specifying the view in the MOVE VIEWS clause.
14.586 – 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.
14.587 – 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.
14.588 – NO_CROSEG
no CROSS clause may be used with a segmented string specification Explanation: You attempted to use a CROSS clause with a segmented string specification. This is not permitted. User Action: Remove the CROSS clause.
14.589 – NO_FILFND
file <str> not found for input to the precompiler Explanation: You attempted to open a nonexistent file. User Action: Check the file specified. Supply complete file specification.
14.590 – NO_FIRSEG
no FIRST clause may be used with a segmented string specification Explanation: You attempted to use a FIRST clause with a segmented string specification. This is not permitted. User Action: Remove the FIRST clause.
14.591 – NO_MORSEG
there are no more segments in this segmented string Explanation: You attempted to print or get a segment from a segmented string and the last segment has already been read. User Action: This is a normal case. You have retrieved the entire segmented string.
14.592 – NO_PERBLO
no periods are permitted within a FOR or an ON ERROR block Explanation: COBOL does not permit periods between the PERFORM and END_PERFORM block, or the IF and END_IF block that the preprocessor generates. User Action: Remove the period from the end of the DML statement within the FOR or ON ERROR block.
14.593 – NO_REDSEG
no REDUCED TO clause may be used with a segmented string specification Explanation: You attempted to use a REDUCED TO clause with a segmented string specification. This is not permitted. User Action: Remove the REDUCED TO clause.
14.594 – NO_SORSEG
no SORTED BY clause may be used with a segmented string specification Explanation: You attempted to use a SORTED BY clause with a segmented string specification. This is not permitted. User Action: Remove the SORTED BY clause.
14.595 – NO_SUCH_FIELD
field, <str>, does not exist in this database Explanation: You specified a field that does not exist in the database. User Action: Check database entity definitions for the valid database field name.
14.596 – NO_TXNOUT
no transaction outstanding Explanation: You attempted to terminate a transaction with a COMMIT or a ROLLBACK when no transaction was outstanding. User Action: Enter a START_TRANSACTION statement before COMMIT or ROLLBACK.
14.597 – NO_WITSEG
no WITH clause may be used with a segmented string specification Explanation: You attempted to use a WITH clause with a segmented string specification. This is not permitted. User Action: Remove the WITH clause.
14.598 – 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.
14.599 – ONLFIRVAR
only first variable in qualified variable expression Explanation: COBOL allows only the first variable in a qualification to be an array. The preprocessors do not recognize the arrays of arrays in FORTRAN, COBOL or BASIC. User Action: Rewrite the query and check the appropriate reference manual.
14.600 – ONLONEDB
only one database can be referenced in an RSE or an expression Explanation: You cannot use database variables from more than one database in an RSE or in an expression. You can, however, refer to variables from one database in an expression and refer to variables in another database in a STORE or a MODIFY statement. Nested FOR statements may refer to different databases in the RSEs of each FOR statement. User Action: Use separate statements or nested FOR loops for multiple database access.
14.601 – ONLONERED
only one REDUCE clause can appear in an RSE Explanation: You included more than one REDUCED TO clause in the RSE. This is not permitted. User Action: Specify all reduce expressions in one reduce list.
14.602 – ONLONEREQ
only one request handle may be specified on a STMT Explanation: You included more than one REQUEST_HANDLE in your statement. Only one is permitted. User Action: Use only one REQUEST_HANDLE. You may have intended to use a TRANSACTION_HANDLE.
14.603 – ONLONESOR
only one SORT clause can appear in an RSE Explanation: You included more than one SORTED BY clause in your RSE. This is not permitted. User Action: Specify all sort expressions in one sort list.
14.604 – ONLONETRA
only one transaction handle may be specified on a STMT Explanation: You included more than one TRANSACTION_HANDLE in your statement. Only one TRANSACTION_HANDLE is permitted. User Action: Use only one TRANSACTION_HANDLE. You may have intended to use a REQUEST_HANDLE.
14.605 – ONLONETRN
only one transaction allowed at a time Explanation: You attempted to use more than one transaction. Only one transaction is allowed at a time. Note that RDO does an implicit START_TRANSACTION on the first DML statement. User Action: A COMMIT or ROLLBACK terminates a transaction.
14.606 – ONLONEWIT
only one WITH clause can appear in an RSE Explanation: You included more than one WITH clause in the RSE. This is not permitted. User Action: Specify all Boolean expressions in one WITH clause.
14.607 – ONLYONEPSECT
only one PSECT statement per module is supported Explanation: You attempted to use more than one PSECT directive per module. The PSECT directive may only be used once per module. User Action: Decide which PSECT statement is really desired and delete all others.
14.608 – OPENERR
unable to open <str> as the interchange file Explanation: Could not access the Oracle Rdb interchange file (RBR). User Action: Correct the problem indicated by subsequent messages and retry the operation.
14.609 – 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.
14.610 – OPERNOTIFY
system operator notification: <str> Explanation: The indicated message was sent to one of the configured system operators. User Action: Examine the indicated message and perform the appropriate operation.
14.611 – 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.
14.612 – OPRSTK_OVRFLO
operator stack overflow Explanation: The internal limit of the parsing operator stack was exceeded. User Action: Contact your Oracle support representative for assistance.
14.613 – 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.
14.614 – 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.
14.615 – OPTEXCSRT
AIJ record count exceeded specified <num> sort threshold Explanation: The number of AIJ records processed exceeded the maximum sort threshold specified by the <fac>$BIND_OPT_SORT_THRESHOLD logical name. This is not a fatal error. User Action: None. Use of the <fac>$BIND_OPT_SORT_THRESHOLD may reduce the sort work file disk space required for the AIJ optimization operation. However, this may result in a larger output file.
14.616 – 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.
14.617 – OPTINCONSIS
optimized AIJ file is inconsistent with the database Explanation: The database and/or some areas within the database are not consistent with the optimized AIJ file. The last transaction committed to the database and/or to some database areas is not the same as the last transaction committed to the database at the time the optimized AIJ file's original AIJ file was created. To use an optimized AIJ file for recovery, it must be consistent with the database and all areas. User Action: Use the original, non-optimized AIJ file to do the recovery.
14.618 – 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.
14.619 – 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.
14.620 – 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.
14.621 – OPTSRTSTAT
<str>: <num> Explanation: During optimization operations, statistics are often collected to aid the user in tuning. This message displays a single statistic.
14.622 – 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.
14.623 – 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.
14.624 – PARSE_STACK_OVERFLOW
parse stack overflow Explanation: The internal limits of the parsing stack were exceeded. User Action: Contact your Oracle support representative for assistance.
14.625 – 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.
14.626 – PATHREQCDD
a pathname is specified but no CDD is available Explanation: The statement entered specifies a CDD pathname, but there is no CDD available for use (may not be installed). User Action: Choose a statement or statement option that does not specify a pathname, or check with the system administrator to determine why the CDD is not available.
14.627 – PLACENEEDGET
PLACE operator must fetch data Explanation: A PLACE statement has been used without a GET or PRINT statement. PLACE must retrieve something from the database, usually a dbkey. User Action: Use the GET or PRINT statement to retrive the appropriate dbkey.
14.628 – PREMATURE_EOF
statement is syntactically incomplete Explanation: You entered a syntactically incomplete statement. User Action: Complete the statement before pressing RETURN.
14.629 – PREMEOF
premature end of file encountered in <str> Explanation: A premature end-of-file was encountered while reading the specified file.
14.630 – 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.
14.631 – 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.
14.632 – QUIETPTREL
released database quiet point at <time> Explanation: The database quiet point lock has been released. User Action: None.
14.633 – 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.
14.634 – 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".
14.635 – 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.
14.636 – RDORECOBS
RECOVER command is obsolete, please use RMU/RECOVER Explanation: You requested that an RDO RECOVER statement be executed. This statement is no longer supported in RDO. User Action: Use the RMU/RECOVER command instead.
14.637 – 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.
14.638 – REANOWRT
a READ_ONLY transaction cannot specify write locks Explanation: You specified a READ_ONLY transaction and a relation was locked for write access. This is a conflict of access modes. User Action: Start a transaction READ_WRITE or use a read lock. Note, the default is always READ_ONLY.
14.639 – 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.
14.640 – 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.
14.641 – 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.
14.642 – 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.
14.643 – REFREMONITROBS
REFRESH MONITOR and START MONITOR command are obsolete, please use RMU/MONITOR REOPEN Explanation: The START and REFRESH MONITOR command is no longer available in RDO. User Action: Use the RMU/MONITOR REOPEN command, which provides the same functionality.
14.644 – REFSEGSTR
reference to segmented string <str> must use RDB$VALUE or RDB$LENGTH Explanation: You attempted to use a context variable that was defined in a segmented string RSE with a field name that was neither RDB$VALUE or RDB$LENGTH, or you attempted to ERASE a segmented string segment using that context variable. You can only use RDB$VALUE or RDB$LENGTH to refer to a segmented string contents and individual segments can not be erased using RDO or RDBPRE. User Action: Use either <context-variable>.RDB$VALUE or <context-variable>.RDB$LENGTH, where context variable is the one defined in the segmented string RSE. Or erase an entire segmented string by assigning zero to the segmented string field name.
14.645 – RELAMBIG
the relation <str> was not qualified and is in multiple databases Explanation: You must qualify the database with relation names when accessing more than one database containing that relation. User Action: Make sure the INVOKE statements include qualifiers, and retype the query using the appropriate qualifier.
14.646 – RELNOTDEF
relation <str> is not defined in database Explanation: The specified relation does not exist in the current database. User Action: Invoke the correct database. Spell the relation name correctly. You may have specified a name other than a relation name.
14.647 – REL_EXISTS
relation <str> already exists in this database Explanation: You attempted to define a relation with the name of an existing relation. User Action: Choose a different name.
14.648 – REMNOTALW
a remote source database is not allowed to be replicated Explanation: You were attached to a database which is on a remote node when you tried to define a replication mode transfer using the DEFINE TRANSFER statement. User Action: Define an extraction transfer instead.
14.649 – REORGONLCHSM
REORGANIZE may only be used in CHANGE STORAGE MAP Explanation: You specified the REORGANIZE keyword in a statement other than the CHANGE STORE MAP statement. User Action: Specify the REORGANIZE keyword only in the CHANGE STORAGE MAP statement. There is no REORGANIZE keyword in the DEFINE STORAGE MAP statement.
14.650 – 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.
14.651 – RESABORT
terminating the IMPORT operation Explanation: The IMPORT operation has been aborted; see the messages preceding this one. User Action: None.
14.652 – RESERVED_WORD
<str> is a keyword; it cannot be used as a name Explanation: You entered a keyword where a name was expected. User Action: Specify a unique name instead of the keyword.
14.653 – 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.
14.654 – RETMODSPC
only one retain mode may be specified for a transaction Explanation: You specified two transaction modes in a START_TRANSACTION statement. User Action: Specify only one transaction mode in a START_TRANSACTION statement.
14.655 – 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.
14.656 – 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.
14.657 – ROOT_CORRUPT
database has been corrupted and must be restored from backup
Explanation: The database has been corrupted and must be
restored from a full database backup.
User Action: Restore the database from the latest full database
backup, apply any incremental backups that might exist, and
roll-forward ("recover") the corresponding after-image journal.
14.658 – 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.
14.659 – RSENOTSEG
the RSE in a START_SEGMENTED_STRING does not reference a segmented string Explanation: The START_SEGMENTED_STRING record selection expression refers to a real record stream instead of a segmented string field. START_SEGMENTED_STRING may refer only to segmented strings. User Action: Use a segmented string field in the RSE portion of the START_SEGMENTED_STRING command.
14.660 – RTAIJMSMTCH
AIJ references root file "<str>" - expected "<str>"
14.661 – RTOCMDILL
requested command is not supported in runtime-only or remote environment Explanation: You issued a statement that is not supported in a run-time-only or remote system (such as DEFINE FIELD). User Action: You may have to move your database to a system that has a development system to do this task.
14.662 – RUJDEVDIR
RUJ filename "<str>" does not include a device/directory Explanation: The RUJ filename you specified did not include a device and directory. User Action: For maximum protection, you should always include a device and directory in the file specification, preferably one that is different from the database device.
14.663 – 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.
14.664 – 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.
14.665 – 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.
14.666 – SCALEOPSBASIC
cannot use scaled operands in BASIC operations Explanation: You attempted to perform arithmetic operations on scaled data types. This is not supported in the BASIC preprocessor. User Action: Use simple assignment statements to convert the variables to the desired data types and perform operations on those data types.
14.667 – 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.
14.668 – SEGALRSTA
segmented string <str> is already started Explanation: You issued a START_SEGMENTED_STRING statement using a segmented string name for which a START_SEGMENTED_STRING statement has been issued without a corresponding END_SEGMENTED_STRING. User Action: Issue END_SEGMENTED_STRING or use another segmented string.
14.669 – SEGNOTSTA
segmented string <str> is not started or created
Explanation: You issued an END_SEGMENTED_STRING statement using
a name for which no corresponding START_SEGMENTED_STRING or
CREATE_SEGMENTED_STRING was issued, or for which an
END_SEGMENTED_STRING has already been entered.
User Action: Issue a START_SEGMENTED_STRING or
CREATE_SEGMENTED_STRING statement before using
END_SEGMENTED_STRING, or only use END_SEGMENTED_STRING
once for each START_SEGMENTED_STRING or CREATE_SEGMENTED_STRING.
14.670 – SEGOUTSCO
segmented string <str> was used out of scope Explanation: You attempted to issue an END_SEGMENTED_STRING command using a name that was already ended. User Action: Use only one END_SEGMENTED_STRING per START_SEGMENTED_STRING.
14.671 – SEGSTREXP
cannot use a segmented string in an expression Explanation: You attempted to use a segmented string in an expression. Segmented strings may be used only in expressions using the MISSING operator. User Action: Remove the operations on the segmented string from the DML query.
14.672 – 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.
14.673 – 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.
14.674 – 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.
14.675 – 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.
14.676 – SEVERRDET
a severe error was detected Explanation: A severe error was detected by RDO and returned to DCL during the execution of an RDO statement. User Action: If possible, run the statement(s) again in interactive RDO and read any additional RDO error messages to determine what caused the severe error condition. Then fix the error. Remember, in a DCL command procedure containing RDO statements, use the $SEVERITY symbol to test for RDO$_SEVERRDET.
14.677 – SFDBONLY
<str> function restricted to Single File DataBases Explanation: This function is restricted to single file databases. It cannot be used with multifile databases. User Action: Use the corresponding RMU function for a multifile database.
14.678 – SHINDCIU
Compression in use Explanation: Used for SHOW INDICES. User Action: None.
14.679 – SHINDFLDSIZE
size of index key is Explanation: Used to display the number of characters used in the key for an index. The field used for the key must be at least of this length. User Action: None.
14.680 – SHINDMAPVAL
mapping values Explanation: Uses values from <low> to <high> for minimizing space needed for index node. User Action: None.
14.681 – SHINDMAPVAL2
to Explanation: Uses values from <low> to <high> for minimizing space needed for index node. User Action: None.
14.682 – SHOMONITROBS
SHOW MONITOR command is obsolete, please use RMU/SHOW SYSTEM Explanation: The SHOW MONITOR command is no longer available in RDO. User Action: Use the RMU/SHOW SYSTEM command, which provides the same functionality.
14.683 – SHOUSEROBS
SHOW USERS command is obsolete , please use RMU/SHOW USER Explanation: The SHOW USERS command is no longer available in RDO. User Action: Use the RMU/SHOW USER command, which provides the same functionality.
14.684 – 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.
14.685 – 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.
14.686 – 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.
14.687 – SOURCEDISC
source code after END statement ignored Explanation: There may have been source code after an end statement. User Action: Review the program and if there was meaningful source code after the end statement in a precompiled module, separate it into another module.
14.688 – 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.
14.689 – 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.
14.690 – 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.
14.691 – SPAMNOTWRM
cannot enable SPAMs for WORM area <str> Explanation: WORM areas cannot have SPAMs enabled. User Action: Do not enable SPAMs for WORM areas.
14.692 – SPELLCORR
identifier <str> replaced with <str> Explanation: A keyword was misspelled, but the error has been corrected by RDO. User Action: None required, unless the correction was not the intended keyword.
14.693 – 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.
14.694 – 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.
14.695 – 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.
14.696 – STAREAFUL
storage area <str> is full Explanation: You attempted to store a record in the database, but the storage area in which the record would go is full. This condition can be caused by the storage area being set to disallow being extended or when the ABM pages are at their limit and cannot map a new extension for the storage area. User Action: Modify the storage area extend parameter to allow storage area extension if it is disabled, or increase the page size or redistribute objects across other storage areas to free up existing space.
14.697 – STARNOTALL
invalid use of asterisk - expected field name Explanation: You attempted to use a context_variable.* in a field-required context. User Action: Supply names of fields to be referenced.
14.698 – 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.
14.699 – STATNODEUNKN
node is not actively collecting statistics Explanation: A node was specified that is NOT actively collecting statistics for this SHOW STATISTIC utility session. User Action: Make sure the node name is spelled correctly and has been properly identified.
14.700 – 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".
14.701 – 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.
14.702 – STOCONVAR
must use the context variable, <str>, declared in the STORE/MODIFY. You had <str> Explanation: You used a context variable in a STORE statement that does not match the one declared in the RSE of the STORE statement. For example: FOR P IN PORT STORE J IN PORT USING P.CITY = J.CITY END_STORE END_FOR User Action: Include the correct context variable in your STORE or MODIFY statement.
14.703 – STOMAPNOEXI
storage map <str> does not exist in this database Explanation: The storage map you attempted to change was not found. User Action: Check the name of the storage map using the SHOW command and try again to change it.
14.704 – STOMAP_LITS
too many fields in limit clause Explanation: A DEFINE STORAGE MAP statement has specified more literal values as limits than corresponding fields in the USING clause. User Action: Correct the statement. The number of literal values you specify must match the number of fields in the USING clause.
14.705 – STOPMONITROBS
STOP MONITOR command is obsolete, please use RMU/MONITOR STOP Explanation: The STOP MONITOR command is no longer available in RDO. User Action: Use the RMU/MONITOR STOP command, which provides the same functionality.
14.706 – STRALRDEC
stream <str> is already declared Explanation: You attempted to declare a stream that was already declared. User Action: Use another stream name.
14.707 – STRALROPE
stream <str> is already opened Explanation: You attempted to open a stream that was already open. User Action: Close the open stream or use another stream name.
14.708 – 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.
14.709 – STRNOTDEC
stream <str> has not been declared Explanation: You attempted to open a predeclared stream that hasn't been declared User Action: Declare the stream or use the name of a predeclared stream.
14.710 – STRNOTOPE
stream <str> is not opened Explanation: You attempted to fetch a row from a stream that was not open, or you attempted to close a stream that was not open. User Action: Issue a START_STREAM <stream-name> command before using FETCH. Start a stream before closing, or close a stream only once after opening it.
14.711 – STROUTSCO
stream <str> was used out of scope Explanation: You attempted to use a stream name outside the scope of the START_STREAM/END_STREAM block. This is not permitted. User Action: Use FETCH only within the START/END block.
14.712 – STTREMCNCT
error allocating remote statistics network connection Explanation: None.
14.713 – STTSVRFIND
error identifying remote statistics server Explanation: None.
14.714 – 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.
14.715 – SYM_EXP
one of the following symbols was expected: Explanation: You typed an unexpected keyword. User Action: Type a correct keyword.
14.716 – SYNTAX_ERR
syntax error Explanation: A syntax error was detected in a your RDO statement. User Action: Correct the syntax error and retry the statement.
14.717 – 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.
14.718 – 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.
14.719 – 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 assistance.
14.720 – TIMEOUT
timeout on <str> Explanation: A lock request has been canceled by the database management system because the request could not be granted within the user-specified timeout period. User Action: Execute a ROLLBACK or a COMMIT to release your locks, and try the transaction again.
14.721 – TOKTOOBIG
symbol name is too big Explanation: You entered a symbol (token) name with a length greater than 32 characters. The length of a symbol name must be less than or equal to 32 characters. User Action: Use a symbol with no more than 32 characters.
14.722 – TOOBIGBLR
request BLR would be too large to execute Explanation: Your request is too large to be compiled. User Action: The DML statement must be broken up into smaller parts.
14.723 – TRAACT
a database cannot be invoked while a transaction is active Explanation: You issued an INVOKE statement while a transaction was still in progress. User Action: You must either commit or roll back the current transaction or wait until the current transaction is terminated before invoking another database.
14.724 – TRAACT_1
a database cannot be defined while a transaction is active Explanation: You issued a DEFINE DATABASE command while a transaction was still in progress. User Action: You must either commit or roll back the current transaction or wait until the current transaction is terminated before invoking another database.
14.725 – TRAACT_2
ROLLBACK or COMMIT the transaction Explanation: You are attempting an operation that cannot be executed while the current transaction is still in progress. User Action: You must either commit or roll back the current transaction or wait until the current transaction is terminated before attempting the new database activity.
14.726 – TRAACT_3
a database cannot be deleted while a transaction is active Explanation: You issued a data definition statement while a data manipulation transaction was still in progress. User Action: Commit or roll back the data manipulation transaction, start a new transaction, and reissue the data definition statement.
14.727 – TRAHDLBVAL
transaction handle must be !VAL Explanation: You specified a transaction handle name to RDB$INTERPRET. User Action: You must use !VAL and a longword variable.
14.728 – TRAHDLINV
transaction handle datatype invalid, must be longword Explanation: You specified a transaction handle to RDB$INTERPRET that was not a longword. User Action: You must use !VAL and a longword variable.
14.729 – TRAMODSPC
only one transaction mode may be specified for a transaction Explanation: You specified two transaction modes in a START_TRANSACTION statement. User Action: Specify one transaction mode in a START_TRANSACTION statement.
14.730 – TRANONERR1
start_transaction not allowed in on error Explanation: A START_TRANSACTION statement is not allowed in an ON ERROR clause. User Action: The ON ERROR clause is within a request. If a new transaction is desired, leave the current request and then start the transaction.
14.731 – TRANONERR2
must leave current request to start a new transaction Explanation: A START_TRANSACTION statement is not allowed in an ON ERROR clause. User Action: The ON ERROR clause is within a request. If a new transaction is desired, leave the current request and then start the transaction.
14.732 – 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.
14.733 – TREE_OVRFLO
tree storage overflow Explanation: The internal limit of the AST tree nodes was exceeded. User Action: Contact your Oracle support representative for assistance.
14.734 – TRGALREXI
trigger <str> already exists in this database Explanation: The trigger name you requested is already the name of an existing trigger. User Action: Choose a different name.
14.735 – 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.
14.736 – TRUE
condition value is true Explanation: None.
14.737 – 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.
14.738 – 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.
14.739 – UNBTMPFIL
unable to open a temporary file called <str> Explanation: RDO attempted to open a temporary file. It was either in the default directory or the directory specified with the OBJ compile option. User Action: Include a valid directory specification with protection level that allows temporary files to be created.
14.740 – UNDERFLOW
data conversion underflow Explanation: You attempted an operation that would cause loss of information on a data-item movement. User Action: Correct the error and try again.
14.741 – 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.
14.742 – 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.
14.743 – 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.
14.744 – 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.
14.745 – 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.
14.746 – 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.
14.747 – UNLCONVAR
unlike context variables; can update only one relation at a time Explanation: The current MODIFY or STORE statement attempts to update database fields in multiple relations. Example: "MODIFY USING P.EMPLOYEE_NUM = "FOO"; J.NAME = "JONES" END-MODIFY." User Action: Use a separate MODIFY or STORE statement to update fields in multiple relations.
14.748 – 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.
14.749 – UNSCOMP
unsupported data comparison Explanation: You attempted an operation that would compare two incommensurate data items. User Action: Correct the error and try again.
14.750 – UNSCOMPBY
<str>.<str> is not supported in this context Explanation: You included the COMPUTED_BY field named in this error message in the SELECT FIELDS clause of a DEFINE TRANSFER statement. This COMPUTED_BY field uses a value expression that is unsupported. User Action: Reenter the DEFINE TRANSFER statement and omit the COMPUTED_BY field that uses the unsupported value expression. Refer to the DEFINE TRANSFER statement in the Replication Option for Rdb Handbook for information on what value expressions are supported.
14.751 – UNSCONV
unsupported data conversion Explanation: You attempted an operation that would cause loss of information on a data-item movement. User Action: Correct the error and try again.
14.752 – UNSDSCCLA
unsupported descriptor class <num> Explanation: The class of the descriptor in an input parameter is not supported by Oracle Rdb. User Action: Use class S, D, DS, or VS.
14.753 – UNSIMPORT
RDO IMPORT does not support all Oracle Rdb features, please use SQL IMPORT
14.754 – UNSSTRXPR
unsupported string expression Explanation: You attempted an operation on a string that is not supported. ie string = string + string; User Action: Please check the manual for the string expressions allowed. If you are using the preprocessors, you might be able to work around the limitation by using a temporary variable.
14.755 – UNSSUPDAT
unsupported datatype requested Explanation: You requested input or output of an unsupported data type from Callable RDO. User Action: Review the data types of the variables in the call and change the offending data type to a supported data type.
14.756 – 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.
14.757 – UNTSTR
unterminated string found
Explanation: The matching quotation mark (" or ') for a string
was not found.
User Action: Reenter the command with the matching quotation
mark.
14.758 – UPDATEJOIN
relation <str> is part of join cannot be updated Explanation: You tried to modify or erase records from a relation that is joined (using the CROSS clause) with other relations. User Action: Redefine the query so that the relation you are trying to update is not directly joined to other relations. i.e. do not use a CROSS clause, but instead represent the other relation references as subqueries.
14.759 – 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.
14.760 – USINGCLSMNGLESS
USING clause present with no WITH LIMIT clause Explanation: You specified a STORE USING clause, but no WITH LIMIT clause. User Action: The STORE USING clause is meaningless without the WITH LIMIT clause.
14.761 – USINGNOTSPEC
no USING clause specified Explanation: A DEFINE STORAGE MAP statement has specified literal values as limits but has specified no fields in the USING clause. User Action: Correct the statement. The number of literal values you specify must match the number of fields in the USING clause.
14.762 – VEWNOTDEF
view <str> is not defined in database Explanation: The specified view does not exist in the current database. User Action: Invoke the proper database. Spell the view name correctly. You may have specified an expression where a view name was expected.
14.763 – VWNOFETCH
view <str> cannot be fetched within a stream Explanation: Records from the specified view cannot be retrieved in a stream. This indicates that the view was defined as an AGGREGATE (SQL GROUP BY) or MERGE (SQL UNION) stream. User Action: Retrieve the records using a FOR statement.
14.764 – WAIMODSPC
only one wait mode may be specified for a transaction Explanation: You specified two transaction modes in a START_TRANSACTION statement. User Action: Specify only one transaction mode in a START_TRANSACTION statement.
14.765 – 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.
14.766 – WISH_LIST
feature not yet implemented Explanation: The action you requested requires a feature that is not implemented in the current version of this product. User Action: Avoid using this feature.
14.767 – WRMCANTREAD
error reading WORM pages <num>:<num>-<num> Explanation: An error occurred when you attempted to read one or more WORM pages. The message indicates the storage area ID number and the page numbers of the first and last pages being read. User Action: Examine the associated messages to determine the reason for failure. One possible cause for this error is disabling logging for the WORM area and subsequently restoring that area from an earlier backup.
14.768 – 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.
14.769 – 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.
14.770 – 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.
14.771 – 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.
14.772 – XPR_STACK_OVFL
expression forces too many levels of recursion/stack overflow Explanation: You provided an expression which forces too many levels of recursion, which resulted in stack overflow. User Action: The expression should be rewritten to use parentheses and therefore cause fewer levels of recursion. It may also be possible to increase the size of the stack.
14.773 – ZABORT
user entered Control-Z to abort command Explanation: You entered a CTRL/Z to abort the current command. User Action: None.
15 – RDMS_ERRORS
RDMS$MESSAGE
15.1 – 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.
15.2 – 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.
15.3 – 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.
15.4 – 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.
15.5 – ACENOTFND
no matching access control entry found Explanation: In a protection statement that refers to an existing access control entry, there was no existing entry that matched the input. User Action: Use SHOW PROTECTION to see what the ACL currently looks like and correct your statement.
15.6 – ACTMISMATCH
journal is for database activation <time>, not <time> Explanation: The activation time and date stamp in the root does not match the activation time and date stamp in the journal file. This journal cannot be applied to this database. User Action: Use the correct journal file or backup file.
15.7 – ACTQUERY
there are queries compiled that reference relation "<str>" Explanation: You tried to change metadata associated with the specified table or view however a compiled query exists that depends on the current table or view metadata. User Action: You may have to disconnect, and re-attach to the database before executing this action.
15.8 – ACTQUERYRTN
there are queries compiled that reference routine "<str>" Explanation: You tried to change metadata associated with the specified routine however a compiled query exists that depends on the current routine metadata. User Action: You may have to disconnect, and re-attach to the database before executing this action.
15.9 – ACTQUERYSEQ
there are queries compiled that reference sequence "<str>" Explanation: You tried to change metadata associated with the specified sequence however a compiled query exists that depends on the current sequence metadata. User Action: You may have to disconnect, and re-attach to the database before executing this action.
15.10 – ACTUPDREQ
there are active update requests that reference relation <str> Explanation: You tried to change metadata associated with the specified relation but a request is active that depends on the current relation metadata for some update action. User Action: Finish using the referencing request and release it; then try the metadata update again.
15.11 – AIJACTIVE
<num> active transaction(s) not yet committed or aborted Explanation: Upon completion of the roll-forward operations for the current AIJ file, more than 1 transaction remains active. That is, the commit or roll-back information resides in the next AIJ file to be processed. It is also possible that one or more of these active transactions are prepared transactions, which may be committed or aborted by the recovery operation using DECdtm information; in this case, a separate message indicating the number of prepared transactions will be displayed. User Action: No user action is required. This message is informational only.
15.12 – 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.
15.13 – 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.
15.14 – 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.
15.15 – AIJBADPAGE
inconsistent page <num> from storage area <str> needs AIJ sequence number <num> Explanation: The indicated page has been marked inconsistent with the rest of the database. The AIJ file with the indicated sequence number is required to commence recovery of the page. If the sequence number of the AIJ file is different than the indicated sequence number, recovery of the area will not be performed. User Action: No user action is required. This message is informational only.
15.16 – 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.
15.17 – 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)").
15.18 – 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.
15.19 – 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.
15.20 – AIJBCKCNFT
cannot specify a backup filename and use SAME AS JOURNAL option Explanation: An attempt was made to specify an after-image backup filename and use the BACKUP SAME AS JOURNAL option. User Action: Specify one or the other of the after-image backup options, but not both.
15.21 – 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.
15.22 – 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.
15.23 – 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).
15.24 – AIJBCKDSBL
database contains no after-image journals that qualify for backup Explanation: An attempt was made to perform an after-image backup for a database that has after-image journaling disabled and does not have any journals that qualify to be backed up. This situation occurs if there are no after-image journals, or all journals are unmodified and do not require backup. User Action: No user action is required.
15.25 – 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.
15.26 – 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.
15.27 – 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.
15.28 – AIJBCKFIX
cannot perform by-sequence AIJ backup of extensible journals Explanation: An attempt has been made to back up an "extensible" after-image journal using the "by-sequence" command qualifier. User Action: Do NOT use the "by-sequence" command qualifier when backing up an extensible AIJ journal.
15.29 – 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).
15.30 – 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.
15.31 – 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.
15.32 – AIJBCKINTR
invalid after-image journal backup interval value "<num>" specified Explanation: An invalid AIJ journal backup interval was specified. User Action: The AIJ journal backup interval specifies the number of seconds for which the backup utility will wait. The value must be a positive number, which may include the value "0".
15.33 – 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.
15.34 – 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.
15.35 – 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.
15.36 – AIJBCKRENAME
/RENAME qualifier invalid when backup filespec also specified Explanation: The /RENAME qualifier cannot be specified when an AIJ backup filename specification is also specified, since these are conflicting options. User Action: Specify either the /RENAME qualifier (using "" for the AIJ backup filename specification) or the AIJ backup filename specification, but not both.
15.37 – 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.
15.38 – 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.
15.39 – 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.
15.40 – 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".
15.41 – AIJCCHDIR
AIJ-cache file name "<str>" does not include device and directory Explanation: The AIJ-cache filename specified does not include a device and directory. User Action: For maximum protection, you should always include a device and directory in the AIJ-cache file specification, preferably one that is different from both the database device and AIJ device.
15.42 – 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.
15.43 – 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.
15.44 – 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.
15.45 – AIJDELCUR
cannot remove the current AIJ journal "<str>" Explanation: An attempt was made to remove the AIJ journal currently in use. User Action: Disable AIJ journaling first, or try to remove the AIJ journal when the journal is no longer in use.
15.46 – 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.
15.47 – 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.
15.48 – 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.
15.49 – 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.
15.50 – 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.
15.51 – 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.
15.52 – 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.
15.53 – 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.
15.54 – 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.
15.55 – AIJFNLSEQ
to start another AIJ file recovery, the sequence number needed will be <num> Explanation: This message informs the user what the next AIJ file sequence number will be. AIJ file sequence numbers are modified for a variety of reasons (such as, performing an AIJ backup, enabling or disabling AIJ logging, etc.). User Action: No user action is required. This message is informational only.
15.56 – 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.
15.57 – 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.
15.58 – 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.
15.59 – 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.
15.60 – 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.
15.61 – AIJJRNBSY
journal <str> is busy and cannot be backed up Explanation: An attempt has been made to back up an after-image journal that is currently required for process recovery. The journal is considered to be "busy" until no process requires the journal for recovery. User Action: Use the /WAIT command qualifier to indicate that the after-image backup is to "wait" for the journal to become available; that is, the journal becomes available for backup when no more processes require it for recovery.
15.62 – AIJLSSDONE
"Hot Standby" has been shutdown Explanation: "Hot Standby" has been terminated. User Action: Restart the database replication operation.
15.63 – 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.
15.64 – 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.
15.65 – 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.
15.66 – AIJMODSWTCH
AIJ switch-over suspended - add new journal or backup current Explanation: The AIJ switch-over operation is suspended and performing the requested operation will not succeed and possibly result in the database being shutdown. User Action: Add a new AIJ journal or, if possible, backup the existing journals.
15.67 – 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.
15.68 – 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.
15.69 – 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.
15.70 – 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 enabled. User Action: The offending process(es) need to commit or rollback their current transaction or unbind from the database.
15.71 – 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.
15.72 – 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.
15.73 – 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.
15.74 – AIJNORCVR
recovery must start with journal sequence <num> Explanation: The AIJ file supplied was created subsequent to the expected AIJ journal. Usually, this condition occurs for the following reasons: 1) an incorrect AIJ file or VMS file "version" was specified, 2) the supplied AIJ file was not created for this database, 3) AIJ logging was disabled and then later enabled, or 4) a transaction is continued in this journal from a previous journal. User Action: This is a fatal condition; recovery of the AIJ journal CANNOT start with this journal. You MUST start recovery with the AIJ journal indicated by the preceeding AIJSEQAFT or AIJSEQPRI message.
15.75 – 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>.
15.76 – 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.
15.77 – 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.
15.78 – AIJOPTRST
Optimized AIJ journal will not be applied during restart Explanation: An optimized AIJ was encountered during a restarted AIJ roll-forward operation. Since an optimized AIJ journal only contains 1 real transaction, nothing in the AIJ 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.
15.79 – AIJOPTSUC
AIJ optimization completed successfully Explanation: An AIJ optimization has completed successfully. User Action: No user action is required.
15.80 – 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.
15.81 – 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.
15.82 – 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.
15.83 – AIJRECBEG
recovering after-image journal "state" information Explanation: When performing a full database restore operation, the restore utility attempts to recover the "state" information of any after-image journals that were available at the time of the backup operation. Recovering the after-image journal information permits subsequent "automatic" (i.e., hands-off) AIJ-recovery operations. User Action: No user action is required.
15.84 – AIJRECEND
after-image journal "state" recovery complete Explanation: The after-image journal "state" recovery operation has completed. User Action: No user action is required.
15.85 – 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.
15.86 – 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.
15.87 – 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.
15.88 – 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.
15.89 – 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.
15.90 – 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.
15.91 – 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.
15.92 – 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.
15.93 – AIJRSTBEG
restoring after-image journal "state" information Explanation: When performing a full database restore operation, the restore utility attempts to restore the "state" information of any after-image journals that were available at the time of the backup operation. Restoring the after-image journal information permits subsequent "automatic" (i.e., hands-off) AIJ-recovery operations. User Action: No user action is required.
15.94 – 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.
15.95 – AIJRSTEND
after-image journal "state" restoration complete Explanation: The after-image journal restore operation has completed. User Action: No user action is required.
15.96 – 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.
15.97 – 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.
15.98 – AIJRSTMOD
<num> after-image journal(s) marked as "modified" Explanation: This message indicates the number of after-image journals that were successfully restored, but contain data that needs to be backed up. User Action: No user action is required.
15.99 – 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.
15.100 – 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.
15.101 – 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.
15.102 – AIJRSTSUC
journal "<str>" successfully restored from file "<str>" Explanation: The indicated after-image journal was successfully restored. User Action: No user action is required.
15.103 – AIJSEQAFT
incorrect AIJ file sequence <num> when <num> was expected Explanation: The AIJ file supplied was created subsequent to the expected AIJ file. Usually, this condition occurs for the following reasons: 1) an incorrect AIJ file or VMS file "version" was specified, 2) the supplied AIJ file was not created for this database, or 3) AIJ logging was disabled and then later enabled. User Action: The utility will prompt for confirmation that the supplied AIJ file is valid. If AIJ logging was disabled and then later enabled without any intervening database transaction activity, then confirming the AIJ file will permit the roll-forward operation to continue applying all transactions contained in the AIJ file. Otherwise, the AIJ file should be rejected and the correct AIJ file specified. Should confirmation be given for an incorrect AIJ file, no transactions will be applied.
15.104 – 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.
15.105 – 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.
15.106 – 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.
15.107 – AIJTERMINATE
inaccessible AIJ file forced image exit to protect database Explanation: To maintain the integrity of the database, the database system has forced your image to exit. An error has been encountered with one or more of the after-image journals that could jeopardize your ability to recover the database should a it become necessary to restore and recover the database. Until the journaling problem has been remedied no further updates to the database are allowed. User Action: The RMU or DBO /DUMP/HEADER=JOURNAL command will display the current state of the journals. Various remedies are possible, depending on the error encountered. Contact Oracle Support if you have questions on how to fix the problem. Typically, disabling and re-enabling journaling is the simplest way to restore operation of the database. This can be 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.
15.108 – 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.
15.109 – ALLMIN
<str> must be greater than <num> Explanation: The allocation for the database you specified is too small. User Action: Try another value.
15.110 – ALLSORTWORKERR
all SORTWORKn.TMP files failed Explanation: Sort failed to extend sortwork.tmp files and attempted remedial action by trying each in turn has also failed. User Action: Define sortwork logicals (SORTWORK1, SORTWORK2, etc) such that the target devices have available disk space.
15.111 – 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.
15.112 – 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.
15.113 – ALSNAVAIL
"Hot Standby" not available or improperly installed Explanation: "Hot Standby" cannot be started because it has not been installed. User Action: Make sure the "Hot Standby" component has been properly installed.
15.114 – 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.
15.115 – 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.
15.116 – 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.
15.117 – 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.
15.118 – AMBPRFENT
"<str>" is an ambiguous or unknown user identifier Explanation: The identifier specified is ambiguous or is not known. A wildcard or group identifier was used. User Action: Respecify the identifier using an unambiguous, known identifier.
15.119 – 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.
15.120 – 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.
15.121 – 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.
15.122 – AREA_DELETED
area is not active or was previously deleted Explanation: An attempt was made to ready an area which does not exist.
15.123 – AREA_INCONSIST
storage area <str> is inconsistent Explanation: The storage area has been marked inconsistent with the rest of the database. It cannot be readied. User Action: Recover the area to make it consistent.
15.124 – AREA_NAME
area <str> Explanation: This message supplies supplementary information for an accompanying message. User Action: As specified for accompanying message.
15.125 – 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.
15.126 – ARITH
arithmetic exception Explanation: An exception occurred while Oracle Rdb was evaluating an arithmetic expression. The subordinate status explains the exception. User Action: Change the expression to eliminate the error. For example, if the exception was division by zero, change your query to exclude records that cause a division by zero.
15.127 – 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.
15.128 – BADAIJBCK
previous AIJ backup did not complete Explanation: It appears that the previous AIJ file backup process, which was started on the indicated date/time, either failed or was prematurely terminated by the user. User Action: No user action required. The current AIJ backup will backup the complete AIJ file to ensure there is no loss of transactions. The AIJ file created by the failed backup utility MUST be preserved; DO NOT discard the AIJ backup file created by the failed backup utility. Even though the AIJ backup failed, the AIJ backup file must be used for successful roll-forward operations.
15.129 – 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.
15.130 – 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.
15.131 – 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.
15.132 – BADAIJVER
after-image journal version is incompatible with the runtime system Explanation: Your after-image journal file was created with an incompatible version of the software. User Action: Your after-image journal file cannot be used with the version of the software you have installed on your machine. Make sure you are using the correct AIJ journal, or if "multi-version" software is installed, make sure you are using the correct software version.
15.133 – 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.
15.134 – 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.
15.135 – BADBNDPRM0
bad bind parameter Explanation: A logical bind parameter value is invalid. User Action: See the secondary error message for more information. Because of unfortunate logistics, no further information is available at this point, check the Monitor log for more info.
15.136 – 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.
15.137 – 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.
15.138 – BADCCHNAM
record cache "<str>" does not exist Explanation: The specified record cache is not defined in the database. User Action: Please specify a valid record cache name.
15.139 – 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.
15.140 – 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.
15.141 – 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.
15.142 – BADHANDLE
invalid handle passed on call to Oracle Rdb Explanation: A call to Oracle Rdb passed a non-zero handle when zero was expected or passed a handle that was not valid. A handle is output by certain Oracle Rdb calls. This error can be caused by errors in software, such as a pre-processor, that creates the calls to Oracle Rdb. User Action: None.
15.143 – 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.
15.144 – BADIORECLEN
query would result in illegal record length Explanation: Solving the user's query would result in an illegal record length being used for an RMS operation. User Action: The user will have to reconsider the database design, environment or query structure. This error would be obtained as the result of a conjunct match strategy which does not have enough VM. This can be resolved by providing a large enough value for the logical RDMS$BIND_WORK_VM). Alternately, the problem might be alleviated by dropping the indices which are used for query resolution or by reducing the size of the columns being joined.
15.145 – 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.
15.146 – 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:
15.147 – 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.
15.148 – BADPARAM
<str> (<num>) is out of valid range (<num>..<num>) Explanation: An illegal parameter was specified during creation or modification of the database. User Action: Examine your command line for illegal parameter values.
15.149 – 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.
15.150 – 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.
15.151 – BADSEGSTROPT
option specified is incompatible with segmented string storage maps Explanation: You defined a storage map for segmented strings and included an option which is not supported or is meaningless. User Action: Review the documentation and correct the syntax.
15.152 – 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.
15.153 – BADSTATVER
statistics input file version is incompatible with the software version Explanation: The binary statistics file specified by the /INPUT qualifier was created with an incompatible version of the software. User Action: The binary statistics file cannot be used with the version of the software you have installed on your machine.
15.154 – BAD_AREA_NAME
area named <str> does not exist Explanation: You specified an area name that is incorrect. User Action: Check with your DBA to determine the correct area names for your database, and reissue your command correctly.
15.155 – BAD_CODE
corruption in the query string Explanation: An illegal entry was found in the query string. User Action: If you called Oracle Rdb, check the query string. Otherwise, contact your Oracle support representative for assistance.
15.156 – BAD_OUTLINE_VERSION
unsupported query outline version Explanation: The query outline version number is either 0 or is greater than the maximum OBLR version supported by the Oracle Rdb image. User Action: If an outline is being moved from one version of Oracle Rdb to an earlier version of Oracle Rdb, and that earlier version of Oracle Rdb supported an earlier version of the outline format, then you must create a new outline that uses only supported outline features.
15.157 – BAD_SYM
unknown <str> symbol - <str> Explanation: Invalid symbol. User Action: Check the definition and retype the command.
15.158 – BAD_XPR
corrupt expression Explanation: A corrupt expression was found in the query string. User Action: If you called Oracle Rdb, check the query string. Otherwise, contact your Oracle support representative for assistance.
15.159 – 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.
15.160 – 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.
15.161 – BLR_MISMATCH
a table or subquery in query outline was not found in query Explanation: You have used a table context number or subquery hierarchy within the query outline definition that cannot be found in the query to which the outline will be applied. User Action: Only use those context numbers in your query outline that exist in the query for which you are creating the outline. Additionally, do not change the subquery hierarchy in the outline.
15.162 – 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.
15.163 – BPPMAX
<num> blocks per page is greater than the Oracle Rdb maximum of <num> Explanation: The page size for the database you specified is too large. User Action: Try another value.
15.164 – BPPMIN
<num> blocks per page is less than the Oracle Rdb minimum of <num> Explanation: The page size for the database you specified is too small. User Action: Try another value.
15.165 – 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.
15.166 – BUFLIMEXC
internal buffer limit exceeded Explanation: You have provided a request whose compilation exceeds the buffer capabilities of Oracle Rdb. An example would be a request that attempts to retrieve several thousand fields from a relation. User Action: Rewrite the request, possibly breaking it up into multiple requests.
15.167 – BUFSMLPAG
buffer size is less than page size Explanation: Buffer size must be large enough for at least one page. User Action: Try another value for the buffer size.
15.168 – 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.
15.169 – 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.
15.170 – 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.
15.171 – BUILDPENDING
index in build pending state - operation not permitted Explanation: This table has an index defined with a build pending. Therefore, change to the data (such as using DELETE, INSERT, or UPDATE) is not permitted. User Action: Complete the index build so that the table is again writable.
15.172 – 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.
15.173 – CACHEUSED
in use by storage area "<str>", cache "<str>" not deleted Explanation: You attempted to drop the cache which is used by a storage area. User Action: Make sure the cache you drop is not used by any storage map or use DROP CASCADE to have each storage updated.
15.174 – 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.
15.175 – CANNOTNEST
transaction BLR is nested too deeply Explanation: BLRK_TRANSACTION can not be nested within a BLR$K_FOR or a BLR$K_STATEMENT. You can not start, commit, or rollback a transaction from within these statements. User Action: This is an unexpected internal error. If you are using DSRI, then please recode the DSRI request to avoid the nesting. If you are using SQL, contact your Oracle support representative for assistance. You will need to provide the statements that produced this error.
15.176 – 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.
15.177 – 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.
15.178 – CANTBINDRT
error mapping database root file Explanation: An error occurred during mapping to the database root file. User Action: Examine the associated messages to determine the reason for failure.
15.179 – 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.
15.180 – 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.
15.181 – 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.
15.182 – 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.
15.183 – 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.
15.184 – 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.
15.185 – 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.
15.186 – 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.
15.187 – 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).
15.188 – 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.
15.189 – CANTCRERCS
error creating Record Cache Server process Explanation: An error occurred when you attempted to create a detached Record Cache Server process. User Action: Examine the secondary message(s) or look in the database monitor log file (SYS$SYSTEM:*MON.LOG) for more information.
15.190 – 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.
15.191 – 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.
15.192 – 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.
15.193 – CANTFINDLAREA
cannot locate logical area <num> in area inventory page list Explanation: This is an internal error. A request was made to find logical area information for the specified logical area number but no active AIP entries could be found for that logical area number. User Action: Contact your Oracle support representative for assistance.
15.194 – 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.
15.195 – 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.
15.196 – 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.
15.197 – 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.
15.198 – 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.
15.199 – 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.
15.200 – 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.
15.201 – 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.
15.202 – 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.
15.203 – 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.
15.204 – 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.
15.205 – 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.
15.206 – CANTRESUMELRS
error resuming AIJ Log Roll-Forward Server process Explanation: An error occurred when you attempted to resume the detached AIJ Log Roll-Forward Server process. User Action: Examine the secondary message(s) or look in the database monitor log file (SYS$SYSTEM:*MON.LOG) for more information.
15.207 – 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.
15.208 – 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.
15.209 – 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.
15.210 – 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.
15.211 – CANTSTARTLCS
error starting AIJ Log Catch-Up Server process Explanation: An error occurred when you attempted to start the detached AIJ Log Catch-Up Server process on the replicated database. User Action: Examine the secondary message(s) or look in the database monitor log file (SYS$SYSTEM:*MON.LOG) for more information.
15.212 – 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.
15.213 – 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.
15.214 – 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.
15.215 – CANTSTARTTX
cannot start transaction Explanation: Cannot start a transaction as requested. User Action: Examine the secondary message for more information.
15.216 – 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.
15.217 – 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.
15.218 – 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.
15.219 – 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.
15.220 – 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.
15.221 – 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.
15.222 – 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.
15.223 – CASTDOMAIN
<str> <str> uses domain <str> as CAST or local variable Explanation: A dependency exists for this domain. It is used in a CAST expression or as a local variable. User Action: You need to change the reference in the routine, trigger, constraint, or column before dropping the domain.
15.224 – CATALOGEXISTS
catalog <str> already exists Explanation: The named catalog already exists. User Action: Use a different name for the catalog.
15.225 – CATALOGINUSE
catalog <str> currently in use Explanation: You attempted to drop a catalog which still contains a schema. User Action: Drop all the schemas from the catalog before attempting to drop the catalog.
15.226 – CATNOTFOUND
catalog with id <num> not found in this database Explanation: The catalog id referenced by the CREATE SCHEMA statement does not exist. User Action: Please select another catalog.
15.227 – 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.
15.228 – CDDISREQD
CDD required for metadata updates is not being maintained Explanation: You attempted to change a definition in a database which requires that all definition changes be reflected in the CDD, after issuing an INVOKE DATABASE FILENAME statement. User Action: INVOKE DATABASE PATHNAME, and retry the metadata update.
15.229 – 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.
15.230 – CHGIDXNOADDMAP
INDEX may not be altered/changed to have map Explanation: A CHANGE or ALTER INDEX command cannot add a storage map to an index that was not previously mapped. User Action: Review the index's use. If you want to move it to another area, the index must be deleted and defined again.
15.231 – 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.
15.232 – 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.
15.233 – CMTCONNOTDEL
cannot delete constraint <str> queued for COMMIT evaluation Explanation: The specified constraint was not deleted because an update action has caused the constraint to be queued for evaluation on a COMMIT. User Action: COMMIT or ROLLBACK the current transaction and try the metadata update again.
15.234 – 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.
15.235 – COLEXTS
there is another collating sequence named <str> in this database Explanation: The collating sequence name you tried to define already exists. User Action: Try another collating sequence name.
15.236 – COLINVFLDTYP
collating sequence invalid for data type Explanation: An attempt was made to create or change a domain or column such that the result is a non-text data type with a collating sequence. User Action: Ensure that collating sequences are not used on non-text data types.
15.237 – COLLFAILURE
could not reformat the collating sequence Explanation: Oracle Rdb translates an NCS collating sequence into an internal format for use in building indices, comparisons, and matching. The translation could not be performed. User Action: Contact your Oracle support representative for assistance. You will need to provide the files BUG.MAR and BUG.NCS obtained from the command: NCS/MAC=BUG/OUT=BUG/EXT=<collating_name> <library> where <collating_name> is the name of the collating sequence that you selected from the library indicated by <library> or from NCS.NLB if you did not specify a library.
15.238 – COLLFMTUNK
collating format unknown Explanation: Oracle Rdb understands the internal format of the collating sequences defined in NCS.NLB. Apparently there is a new format in use that Oracle Rdb does not know about. Perhaps you are using an obsolete version of Oracle Rdb. User Action: Contact your Oracle support representative for assistance. If the problem is not that an obsolete version of Oracle Rdb is in use, then you will need to provide the files BUG.MAR and BUG.NCS obtained from the command: NCS/MAC=BUG/OUT=BUG/EXT=<collating_name> <library> where <collating_name> is the name of the collating sequence that you selected from the library indicated by <library> or from NCS.NLB if you did not specify a library.
15.239 – COLNOEXTS
there is no collating sequence named <str> in this database Explanation: The collating sequence name you tried to delete does not exist. User Action: You may have typed the collating sequence name incorrectly, or you did not define the collating sequence name.
15.240 – COLNOTDEF
field <str> is not defined in relation <str> Explanation: The specified field does not exist in the relation specified. User Action: The relation definition associated with the context variable did not include a definition for the specified field. You may have specified the wrong context variable with the field or mistyped the field name.
15.241 – COLRESERVED
collating sequence name "<str>" is reserved and may not be defined Explanation: The collating sequence name you tried to use is predefined and reserved for use by Oracle Rdb. User Action: Please choose another name.
15.242 – COLUMNORDER
column "<str>" is out of order in the USING clause of "<str>" Explanation: The ADD PARTITION USING clause specified a column in the wrong order. User Action: Please review the original storage map or index definition, and ensure that all the same columns are specified in the same order.
15.243 – COLUSEDDB
the collating sequence named <str> is used by the database Explanation: The collating sequence name you tried to delete was defined as the collating sequence for the database. User Action: Investigate.
15.244 – COLUSEDFLD
the collating sequence named <str> is used in field <str> Explanation: The collating sequence name you tried to delete is in use. User Action: Investigate.
15.245 – COLUSEDREL
the collating sequence named <str> is used in field <str> of relation <str> Explanation: The collating sequence name you tried to delete is in use. User Action: Investigate.
15.246 – 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.
15.247 – COMPNOTENA
index compression has not been enabled Explanation: You attempted to remap index values without enabling compression for the index. User Action: Review the command you typed, and issue a corrected command if appropriate.
15.248 – COMPNOTNUM
index mapping applies to BYTE, WORD and LONGWORD fields only Explanation: You attempted to remap index values but the fields must be of a SIGNED BYTE (TINYINT), SIGNED WORD (SMALLINT) or SIGNED LONGWORD (INTEGER) data type. User Action: Review the command you typed, and issue it again specifying a column of the appropriate data type.
15.249 – COMPNOTTEXT
only text and varying text fields may be shortened in indices Explanation: You attempted to specify a shortened size for an index field, but specified a data type other than text or varying text. Only fields with a text or varying text data type can be shortened in an index. User Action: Review the command you typed, and issue it again specifying a text or varying text field if appropriate.
15.250 – CONCATSTRLEN
concatenation result is too long Explanation: The result of a concatenation operation exceeds the maximum supported string size. User Action: Check the length of the strings used in the expression to determine appropriate action.
15.251 – CONDELVIAREL
constraint <str> can only be deleted by changing or deleting relation <str> Explanation: The constraint specified was defined as a relation-specific constraint, and can only be deleted by using the CHANGE RELATION or DELETE RELATION statement on the relation declaring the constraint. User Action: First, review the database design; then, if desired, delete the relation-specific constraint.
15.252 – CONEXI
relation <str> is referenced in constraint <str> Explanation: Before you can delete a relation, all constraints and views based on this relation must be deleted. User Action: Delete the dependent constraints and any views that refer to this relation.
15.253 – CONEXTS
there is another constraint named <str> in this database Explanation: The constraint name you tried to define already exists. User Action: Choose another constraint name.
15.254 – CONFEVAL
constraint <str> contains conflicting evaluation time attributes Explanation: This constraint contains conflicting evaluation time attributes. Only one of the SQL options DEFERRABLE or NOT DEFERRABLE, or RDO options VERB TIME or COMMIT TIME should be specified. User Action: Remove conflicting clauses.
15.255 – CONFLATTR
conflicting attributes specified: <str> and <str> Explanation: The two attributes you specified may not be used together in the same statement. User Action: Choose one of the attributes, or alter the definition to combine legal attributes. For instance, a database can not have synonyms enabled and also be a multischema database.
15.256 – CONFRESERVE
RESERVE can not be used with ADD/DROP in the same ALTER DATABASE command Explanation: RESERVE STORAGE AREAS cannot be specified with either ADD STORAGE AREA or DROP STORAGE AREA in a single ALTER DATABASE command. User Action: Perform RESERVE STORAGE AREAS in a separate command from either ADD STORAGE AREA or DROP STORAGE AREA.
15.257 – CONFTRANOPT
conflicting transaction options specified Explanation: Two or more options which were specified on the SET TRANSACTION (SQL) (or RDO START_TRANSACTION) statement are in conflict and cannot be specified together. User Action: Refer to the SQL Reference Manual description of the SET TRANSACTION statement and remove the options which are in conflict.
15.258 – CONFTXNOPTION
Do you really want to <str> this transaction? [<char>]: Explanation: Confirm that the user actually wants to take the action.
15.259 – CONMODEXI
constraint "<str>" specified in default transaction for the module "<str>" Explanation: An attempt was made to perform the delete operation on a constraint. The constraint is specified with the EVALUATING clause in the default transaction characteristics for the module. User Action: First, review the database design; then, if desired, delete the module, and then delete the constraint.
15.260 – CONNODEFER
constraint <str> can not be deferred using the EVALUATING clause Explanation: This constraint is defined as NOT DEFERRABLE, and so the evaluation time can not be changed by SQL's SET TRANSACTION or RDO's START_TRANSACTION statements. User Action: Remove the constraint's name from the EVALUATING clause.
15.261 – CONNOEXI
constraint <str> does not exist Explanation: The name specified for the constraint was not found in the database or the constraint named does not reference table named. User Action: Check the name of the constraint using the SHOW command and try again. Check to make sure the constraint is defined on the named table.
15.262 – CONNOTDEF
constraint <str> has not been defined Explanation: The specified constraint was not defined. User Action: Correct the problem and try the metadata update again.
15.263 – CONNOTDEL
constraint <str> has not been deleted Explanation: The specified constraint was not deleted. User Action: Correct the problem, and retry the metadata update.
15.264 – CONRTNEXI
constraint "<str>" is referenced in the routine "<str>" Explanation: The specified constraint you attempted to delete is used in a routine. User Action: First, review the database design; then, if desired, delete the routine, and then delete the constraint.
15.265 – 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.
15.266 – CONVW
views cannot be used within constraints Explanation: Constraints cannot be placed on views. User Action: Place constraints on the relation referred to in the view definition.
15.267 – CSETBADASSIGN
incompatible character sets prohibit the requested assignment Explanation: An attempt was made to assign one string to another, but the character sets of the two strings were incompatible. User Action: Ensure that character sets are compatible before assignment.
15.268 – CSETBADCOMPARE
incompatible character sets prohibit the requested comparison Explanation: An attempt was made to compare one string to another but the character sets of the two strings were incompatible. User Action: Ensure that character sets are compatible before trying comparison.
15.269 – CSETBADCONCAT
incompatible character sets prohibit concatenation Explanation: An attempt was made to concatenate strings together, but the character sets of the two strings were incompatible. User Action: Ensure that character sets are compatible before trying concatenation.
15.270 – CSETBADESCAPE
character set of ESCAPE character must match that of source Explanation: An escape character was used that did not have the same character set as the source value expression. User Action: Ensure that the correct character set is used with the ESCAPE character.
15.271 – CSETBADOPER
character set prohibits the requested operation Explanation: An attempt was made to carry out a string operation but the character set of the string prevented the operation. User Action: Ensure that the operation is valid on the character set before trying the operation again.
15.272 – CSETBADPOS
incompatible character sets prohibits use of POSITION Explanation: An attempt was made to search for a string within another string but the character sets of the two strings are incompatible. User Action: Ensure that character sets are compatible before trying to use the POSITION operator.
15.273 – CSETBADTRIM
incompatible character sets prohibit use of TRIM Explanation: An attempt was made to trim characters from a source string, but the character sets of the trim character and source string are incompatible. User Action: Ensure that character sets are compatible before trying to use the TRIM operator.
15.274 – CSETNOASCII
character set must contain ASCII Explanation: An attempt was made to assign or compare a numeric or date with a text string that had a character set that did not contain ASCII. User Action: Ensure that destination character string character set contains ASCII.
15.275 – CSETNOTFOUND
invalid or undefined character set Explanation: The character set specified is not known to Oracle Rdb. User Action: Check the character set name and/or identifier to ensure that they are valid.
15.276 – 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.
15.277 – 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.
15.278 – 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.
15.279 – DBACTIVE
database is already being used Explanation: You attempted to open a database that is already being used. You can only open a database that is not being accessed. User Action: Wait for all users to finish using the database, or force the users off by closing the database.
15.280 – 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.
15.281 – DBCRUPT
database is corrupt Explanation: Your database is not a valid Oracle Rdb database. This can happen if DEFINE DATABASE does not terminate normally. User Action: Recreate your database. If the database was not just created, contact your Oracle support representative for assistance.
15.282 – DBKFORMAT
database key format incorrect "<str>?<str>" - unexpected character Explanation: While converting the text dbkey string to binary an unexpected character was detected, shown by the ? in the displayed text. User Action: Correct the database key string literal to conform to the rules defined in the SQL Reference Manual.
15.283 – 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 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.
15.284 – 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.
15.285 – 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.
15.286 – 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.
15.287 – DBNOTACTIVE
database is not being used, or must be manually opened first Explanation: You attempted to close a database that is not open, or you attempted to access a closed database that requires manual open. User Action: There is no need to close the database - it is already closed. If you are attempting to access a closed database that requires manual open, open the database first.
15.288 – DBNOTEXTEN
database not multi-file, areas may not be added Explanation: Your database was not specified as multi-file, yet you attempted to add areas to the database. User Action: If you want to create a multi-file database from a single file database, use the EXPORT and IMPORT statements.
15.289 – DBNOTINTRAN
that database is not in the current transaction Explanation: You tried to start a request or use a segmented string in a database not included in your current transaction. User Action: Commit or roll back your transaction, and start a new transaction that includes the proper databases.
15.290 – DBNOTMULTSCHEM
multischema support is not enabled in this Oracle Rdb database Explanation: Multischema support is an option feature. User Action: Use the SQL ALTER RDB DATABASE ENABLED MULTISCHEMA statement to enable this feature and then repeat your command.
15.291 – 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.
15.292 – 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.
15.293 – 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.
15.294 – DBRBOUND
attach not allowed while your process is being recovered Explanation: The database recovery process (DBR) is currently recovering an image for your process. While the recovery operation is running, you cannot start another image that attempts to attach/bind to the database. User Action: You can attach/bind to another database. Otherwise, you must wait for the database recovery process to complete recovery of your previous image.
15.295 – 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.
15.296 – DB_CORRECT_VER
the database is already the correct version Explanation: The database is already accessible by the current version of the software. This message is used only by special versions of the software and is referenced in RMU CONVERT. User Action: None.
15.297 – DDLDONOTMIX
the "<str>" clause can not be used with some ALTER DATABASE clauses Explanation: You attempted to mix the specified clause with other ALTER DATABASE clauses that modify storage areas, template areas or database cache objects. This is not currently supported. User Action: Execute two separate ALTER DATABASE statements, one containing structure altering clauses, and one with the remaining attributes.
15.298 – DDLFAILED
operation on "<str>" failed - in use by <num>:<num>, reason: <num> Explanation: This DDL operation failed because the object is in use by another DDL user. The process id and database stream are shown for reference User Action: Retry this operation at another time, or determine why the conflicting process is still active.
15.299 – DDL_CONFLICT
relation <str> specified reserved for data definition Explanation: An attempt was made to compile a query or perform an incompatible data definition language operation against a table specified in a RESERVING clause with the table reserved for SHARED DATA DEFINITION or EXCLUSIVE DATA DEFINITION. User Action: Commit or rollback the current transaction and start another transaction that is compatible with the operation being attempted.
15.300 – 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.
15.301 – DEFINC
DEFAULT is incompatible with datatype of <str> "<str>"."<str>" Explanation: The DEFAULT specified is not compatible with the datatype of the routine parameter or module global variable. User Action: Ensure that the datatype of the parameter or variable and the DEFAULT (SQL) are compatible. Check the domain used by the parameter or variable to verify consistency between datatypes and DEFAULTs.
15.302 – DEFINCCOL
DEFAULT is incompatible with datatype of column "<str>"."<str>" Explanation: The DEFAULT (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) is not compatible with the datatype of the column (field). The column default could be incompatible with the type of the column or of the domain used by the column. User Action: Ensure that the datatype of the column and the DEFAULT (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) are compatible. Check the domain used by the column to verify consistency between datatypes and DEFAULTs.
15.303 – DEFINCDOM
DEFAULT is incompatible with datatype of domain "<str>" Explanation: The DEFAULT (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) is not compatible with the datatype of the domain (global field). User Action: Ensure that the datatype of the domain displayed in the error message is consistent with the DEFAULT (SQL) or DEFAULT VALUE FOR SQL (CDD/Rep) of the domain (global field).
15.304 – DEFLISTWORM
default list (segmented string) storage area can not be a WRITE ONCE area Explanation: An attempt was made to create a database with a default list (segmented string) storage area on a WORM (write one read many) device. This is not supported by Oracle Rdb because the format of the lists written by the system relations is not compatible with the WORM drive characteristics. User Action: Create the default list storage area on read/write media and create a storage map to assign the lists to particular storage areas.
15.305 – DEFONLYNULL
Default value can only be NULL for a segmented string Explanation: The only valid value for a default value on a segmented string is NULL. User Action: Ensure that the default value is NULL when the datatype of the column or domain is segmented string.
15.306 – DELETEFAILS
Cache file <str> deletion failed Explanation: Attempt made to delete non existing file. User Action: Check for the existence of the cache file.
15.307 – 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.
15.308 – DOENBLAIJ
after-image journaling must be enabled to ensure recovery Explanation: After adding an AIJ journal, it is necessary to enable AIJ journaling (if it is not already enabled). Failure to enable AIJ journaling will result in the AIJ file being NOT recoverable. User Action: IT IS HIGHLY RECOMMENDED that after-image journaling be enabled AS SOON AS POSSIBLE.
15.309 – 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.
15.310 – DORMUCOLLECT
index statistics need updating with RMU/COLLECT Explanation: This index has out of date statistics. Continued use in this state might lead to degraded query performance. User Action: Please use the RMU/COLLECT OPTIMIZER_STATISTICS on this index so that the statistics can be updated
15.311 – DT_FRACMBZ
fractional seconds precision must be zero for this sub type Explanation: The date/time data type supplied a sub-type which does not allow a fractional seconds precision to be supplied. User Action: This appears to be an error in the code generated by SQL. Contact your Oracle support representative for assistance. You will need to provide the statements that produced this error.
15.312 – DT_PRECMBZ
interval leading field precision must be zero for this sub type Explanation: The date/time data type supplied a sub-type which does not allow a leading interval field precision to be supplied. User Action: This appears to be an error in the code generated by SQL. Contact your Oracle support representative for assistance. You will need to provide the statements that produced this error.
15.313 – 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.
15.314 – DUPAIJNAM
duplicate AIJ name "<str>" specified Explanation: A duplicate AIJ name was specified during AIJ journal addition. Each AIJ name is used to identify a specific journal and must be unique within a database. User Action: Please specify a unique AIJ name.
15.315 – 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.
15.316 – DUPLANAME
area name <str> already used Explanation: The area name specified is already in use for this database. User Action: Choose a different name.
15.317 – DUPLCNAME
cache name "<str>" already used Explanation: The cache name specified is already in use for this database. User Action: Choose a different name.
15.318 – DUPLFNAME
file name <str> already used Explanation: The file name specified is already in use for this database. User Action: Choose a different name.
15.319 – DUPLTRGTYPE
trigger <str> already defined for specified relation and trigger type Explanation: There can be only one trigger of each update time and type defined for a particular relation, with the exception that multiple BEFORE MODIFY or AFTER MODIFY triggers can be defined as long as they all have exclusive (non-intersecting) field lists. The trigger being defined conflicts with the specified trigger for either update time and type, or in one of the modify field names. User Action: First, review the database design and defined triggers; then, if desired, try the operation again with non-conflicting types and fields.
15.320 – DUPNOTALL
duplicate records not allowed for index <str> Explanation: You are trying to add a duplicate record to an index on a field that does not allow duplicates. User Action: Do not add duplicate records unless you restructure the relation to allow them.
15.321 – DUPSYSREC
Cannot create duplicate system record in "<str>" Explanation: Two or more processes were attempting to create hashed indexes concurrently in an empty mixed format storage area that did not have a system record logical area previously defined. This can result in a duplicate system record logical area. User Action: Wait for the process that did not fail to finish defining the index. This process will cause a system record logical area to be defined for the area indicated in the error message. Try again to create the index that caused the failure.
15.322 – DYN_REG_ALLOC_FAIL
dynamic register allocation algorithm has failed Explanation: A register allocation algorithm internal to Oracle Rdb has failed while generating code to evaluate an expression. In theory this message should never get through to the user. User Action: Contact your Oracle support representative for assistance. You will need to provide the statements that produced this error. Using parentheses again around the problematic expression may give you a workaround.
15.323 – 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.
15.324 – 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.
15.325 – EMPTYFILE
<str> file is empty Explanation: The file is empty. User Action: None.
15.326 – EMPTY_SUBQUERY
a subquery in the query outline contains no tables Explanation: Tables or subqueries can be omitted in the query outline; however, if all the tables and subqueries of a subquery are omitted, the subquery must be removed also. Empty subqueries are not permitted. User Action: Delete the empty subquery, and try again.
15.327 – 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.
15.328 – 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.
15.329 – 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.
15.330 – ERRWRITE
error writing file Explanation: An error occurred during a file write. User Action: Examine the secondary message for more information.
15.331 – EXCMAPLIMIT
exceeded limit on last partition in storage map for <str> Explanation: An attempt was made: to store a record; or to modify an index key value that is higher than allowed by any partition; or to create or alter an index that would not hold all existing values. User Action: Check that the application is generating correct key values. Add a partition to handle the new key values or add an overflow partition.
15.332 – 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.
15.333 – 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.
15.334 – EXTABORT
routine <str> execution has been aborted Explanation: Execution of the specified external routine has been aborted. User Action: Review the secondary error message for the reason for the abort, eliminate the problem, and retry the operation or query.
15.335 – EXTDBONLY
operation is not allowed on single file databases Explanation: You attempted to change or delete storage areas or change the number of nodes or number of users in a single-file database or use a non-default specification for the snapshot file. User Action: If you want to create a multi-file database from a single-file database, use the EXPORT and IMPORT statements.
15.336 – EXTERNALRTN
invalid use of external routine "<str>" Explanation: You tried to use an EXTERNAL routine where only a stored routine is permitted. User Action: Repeat the action using a stored routine instead.
15.337 – EXTRTNATTCHG
an external routine attribute was changed for this platform Explanation: The external routine definition was modified on this platform because an attribute (such as CLIENT SITE) is not supported. User Action: This is just a warning, and can be ignored. To avoid the warning change the external function or procedure definition to be compatible with this platform, or allow the attribute to default for each platform.
15.338 – 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.
15.339 – EXT_JULIAN_TS
invalid type for EXTRACT JULIAN - must be DATE or TIMESTAMP Explanation: The EXTRACT JULIAN requires that the result of the value expression be a DATE or a TIMESTAMP. User Action: Correct the query to use a valid data type for EXTRACT.
15.340 – EXT_LENGTH_CH
invalid type for EXTRACT LENGTH - must be CHAR or VARCHAR Explanation: The EXTRACT WEEKDAY requires that the result of the value expression be a CHAR or a VARCHAR. User Action: Correct the query to use a valid data type for EXTRACT.
15.341 – EXT_NEED_DT
invalid option for EXTRACT - source must be a datetime type Explanation: The EXTRACT option requires that the result of the value expression be a datetime type. User Action: Correct the query to use a valid option for EXTRACT.
15.342 – EXT_NO_DT_FIELD
invalid option for EXTRACT, source does not include required date/time field Explanation: The EXTRACT option specifies a date/time field which does not exist in the value expression. User Action: Correct the query by using a valid option for EXTRACT.
15.343 – EXT_WEEKDAY_TS
invalid type for EXTRACT WEEKDAY - must be DATE or TIMESTAMP Explanation: The EXTRACT WEEKDAY requires that the result of the value expression be a DATE or a TIMESTAMP. User Action: Correct the query to use a valid data type for EXTRACT.
15.344 – FCJOUDIS
fast commit cannot be enabled if journaling is disabled Explanation: An attempt was made to enable fast commit while journaling is turned off. User Action: Enable journaling for the database before enabling fast commit.
15.345 – FCJOUENB
journaling cannot be disabled if fast commit is enabled Explanation: An attempt was made to disabling journaling while the fast commit feature is turned on. User Action: Disable fast commit before disabling journaling.
15.346 – FEAT_UNSUP
<str> are not supported in this context Explanation: You attempted to use a feature that is not supported in this location. Typically this is a general table feature that is not supported by a LOCAL TEMPORARY TABLE (created or declared) User Action: Remove the problem clause and try again.
15.347 – FETABSOLUTE
fetch absolute (<num>) out of range 1..<num> Explanation: The value of the FETCH ABSOLUTE, FIRST, or LAST is out of the range of the number of segments. User Action: Correct the value passed to FETCH.
15.348 – FETILLOFFSET
FETCH offset must be zero for NEXT, PRIOR, FIRST, LAST Explanation: The FETCH_OFFSET argument contains a value other than zero. User Action: Correct the call to RDB_GET_SEGMENT.
15.349 – FETINVALID
invalid list cursor FETCH attributes (<num>,<num>) Explanation: The FETCH_ORIENTATION argument contains a value not recognized by Oracle Rdb. User Action: Correct the call to RDB_GET_SEGMENT.
15.350 – FETNOTSCROLL
illegal FETCH attribute - must be FETCH NEXT for non-SCROLL cursor Explanation: The LIST CURSOR was opened without the SCROLL attribute, but an attempt was made to perform an action other than FETCH NEXT. User Action: Add the SCROLL attribute to the cursor, or change the FETCH to FETCH NEXT.
15.351 – FETRELATIVE
fetch relative (<num>) causes reference out of range 1..<num> Explanation: The value of the FETCH RELATIVE, NEXT, or PRIOR is out of the range of the number of segments. User Action: Correct the value passed to FETCH.
15.352 – FIEUSETRA
field <str> is used in the transferred relation <str> Explanation: The specified field is used in the specified relation. The relation is involved in a DDAL transfer definition. User Action: You must delete the DDAL transfer definition before modifying the field.
15.353 – FILACCERR
error <str> file <str> Explanation: A file-access error occurred. User Action: Examine the secondary message for more information.
15.354 – 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.
15.355 – FLDEX
column name "<str>" appears more than once in this table, view or map Explanation: The column name appears more than once within a table, view or storage map (COLUMNS clause) definition. User Action: For a table or view the column name can only be used once. Therefore, remove or change the name of the column to avoid this problem. For a storage map the column name may only be used in one COLUMNS clause. You may not map a column to more than one vertical partition.
15.356 – FLDINCOM
field <str> is referenced in COMPUTED BY field <str> Explanation: You attempted to delete a field from a relation, but the field is used in a COMPUTED BY field in the same relation. User Action: First, review the database design; then, if desired, delete the COMPUTED BY field, and then delete the field from the relation.
15.357 – FLDINCOMREL
field <str> is referenced in COMPUTED BY field <str> in relation <str> Explanation: You attempted to delete a field from a relation, but the field is used in a COMPUTED BY field in another relation. User Action: First, review the database design; then, if desired, delete the COMPUTED BY field, and then delete the field from the relation.
15.358 – FLDINCON
field <str> is referenced in constraint <str> Explanation: You attempted to delete a field from a relation, but the field is used in a constraint. User Action: First, review the database design; then, if desired, delete the constraint, and then delete the field from the relation.
15.359 – FLDINRTN
field "<str>" is referenced in routine "<str>" Explanation: You attempted to delete a field from a relation, but the field is used in a routine. User Action: First, review the database design; then, if desired, delete the routine, and then delete the field from the relation.
15.360 – FLDINSTO
field <str> is referenced in storage map <str> Explanation: You attempted to delete a field from a relation but the field is used in a storage map. User Action: First, review the database design; then, if desired, delete the storage map, and then delete the field from the relation.
15.361 – FLDINTRG
field <str> is referenced in trigger <str> Explanation: You attempted to delete a field from a relation, but the field is used in a trigger. User Action: First, review the database design; then, if desired, delete the trigger and then delete the field from the relation.
15.362 – FLDINUSE
field <str> is referenced in index <str> Explanation: The field you attempted to delete is an indexed field. User Action: First, delete the index on the field, and then delete the field.
15.363 – FLDINVIEW
field <str> is referenced in view <str> Explanation: You attempted to delete a field from a relation, but the field is used in a view of that relation. User Action: First, review the database design; then, if desired, delete the view, and then delete the field from the relation.
15.364 – FLDLSTCONDUPS
modify field name list contains duplicates of a field name Explanation: The list of field names supplied for a MODIFY type trigger contains multiple instances of a particular field name. User Action: Choose a different set of field names for the modify list.
15.365 – FLDNOEX
field <str> is not part of this relation Explanation: The field you named is not part of the target relation. User Action: Check the relation definition for the correct field name.
15.366 – FLDNOEXI
field <str> does not exist in this database Explanation: The field that you attempted to delete was not found. It might be a local field in a relation rather than a global field. User Action: Check the exact name of the field and try again to delete it. If it is a local field, use the CHANGE RELATION statement to delete the field.
15.367 – FLDNOTCHG
field <str> has not been changed Explanation: The field specified was not deleted. User Action: Correct the problem and retry the operation.
15.368 – FLDNOTDEL
field <str> has not been deleted Explanation: The field in question has not been deleted for the reason explained by the previous message. User Action: Correct the problem and retry the statement.
15.369 – FLDNOTINREL
<str> is not a field in relation <str> Explanation: The field you named is not part of the named relation. User Action: Check the relation definition for the correct field name or specify another relation.
15.370 – FLDVALIDIF
in VALID IF definition for global field <str> Explanation: During processing of the VALID IF a BLR syntax problem was detected. User Action: Correct the definition so that the VALID IF is legal for Oracle Rdb.
15.371 – FLDVALIDIFNAME
in VALID IF definition for global field <str>, references name <str> Explanation: During processing of the VALID IF definition, a BLR syntax problem was detected. The name referenced in the VALID IF expression is not equal to the global field name. User Action: Correct the definition so that the VALID IF expression contains the same name as the global field definition.
15.372 – 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.
15.373 – GETTXNOPTION
Do you wish to COMMIT/ABORT/IGNORE this transaction: Explanation: Ask the user whether to COMMIT/ABORT/IGNORE this blocked transaction.
15.374 – 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.
15.375 – GFLDEXTS
there is another global field named <str> in this database Explanation: The field name you tried to define already exists. User Action: Use another field name.
15.376 – GFLDNOEX
there is not a global field named <str> in this database Explanation: The field you tried to include in a relation definition does not exist. User Action: Define the field and then try to create the relation again.
15.377 – 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.
15.378 – HASHEDMIX
index of TYPE HASHED must be stored in area(s) with PAGES MIXED Explanation: You attempted to define a hashed index to be stored in a storage area with a uniform-page format. A hashed index must be stored in a storage area with a mixed-page format. User Action: Specify one or more storage areas with mixed-page format for the hashed index.
15.379 – 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.
15.380 – 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.
15.381 – 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).
15.382 – 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.
15.383 – HOTCMDPEND
request cannot be completed due to pending hot standby command Explanation: A Hot Standby command was pervious requested from this node using the /NOWAIT qualifier; the command has not yet completed. The command just requested cannot be completed until the Hot Standby feature command already active but pending on this node has first completed. User Action: The requested Hot Standby command must be completed prior to issuing this command. Use the SHOW USERS command to indicate the status of the Hot Standby command.
15.384 – HOTEXCHMSG
error exchanging replication message Explanation: User Action:
15.385 – HOTFAILURE
hot standby failure: <str> Explanation: A hot standby failure occurred. User Action: Examine the secondary message for more information.
15.386 – HOTLCLCNCT
error allocating local network connection Explanation: User Action:
15.387 – 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.
15.388 – HOTNOCIRCEXT
cannot switch from circular to extensible AIJ journaling if replication active Explanation: User Action: Terminate database replication first.
15.389 – 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.
15.390 – 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.
15.391 – 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.
15.392 – 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.
15.393 – HOTRECVMSG
error receiving replication message Explanation: User Action:
15.394 – HOTREMCNCT
error allocating remote network connection Explanation: User Action:
15.395 – HOTREMDELT
error deleting replication connection Explanation: User Action:
15.396 – HOTREMDSCT
error disconnecting from replication server Explanation: User Action:
15.397 – HOTRWTXACTV
database in use with active or pre-started read/write transactions Explanation: Database replication cannot be started on the standby database if there are processes with active or pre-started read/write transactions. User Action: All read/write transaction activity must be stopped prior to starting database replication on the standby database.
15.398 – 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.
15.399 – 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.
15.400 – HOTSVRCNCT
error connecting to replication server Explanation: User Action:
15.401 – HOTSVRFIND
error identifying remote replication server Explanation: User Action:
15.402 – HOTWRONGDB
attempt to start replication for wrong master database Explanation: An attempt has been made to start replication on a master database whose standby database is already replicating a different master database. The master root file name does not match the name used when replication was first started on the standby database. This could happen if you copied or renamed the master database root file, or if the file was created using a concealed logical device name and that logical name is no longer defined. User Action: Ensure that the specified standby database is correct. If so, ensure that replication on the standby database has been fully terminated; replication termination occassionally has long-duration shutdown processing to be performed. If the master database rootfile had been moved, rename or copy the root file back to its original name or location, or redefine the necessary concealed logical device name in the system logical name table.
15.403 – IDXBLDPEND
index in build pending state - maintenance is disabled Explanation: This index is now in build-pending state and can not currently be used for queries. An ALTER INDEX ... MAINTENANCE IS ENABLED statement must be used to re-enable this index. Only perform this final step when all partitions have been rebuilt. Note that the table on which this index is defined may not be modified (INSERT, UPDATE, or DELETE) while indices are in the build pending state. User Action: This is just a warning to remind the database administrator of additional tasks which must be performed.
15.404 – IDXCOLEXIST
an index with this column list already exists Explanation: An index exists with the same column list, and same type (either SORTED or HASHED), with the same column ordering (ASC/DESC) This warning is intended to alert the database administrator that this index may be redundant. User Action: If this index is not needed then drop this index, or ROLLBACK the CREATE INDEX statement. If you wish to replace an existing index with a different partitioning schema you should use ALTER INDEX. You can also disable the existing index using ALTER INDEX ... MAINTENANCE IS DISABLED so that it is no longer updated or used by queries. It can then be dropped at later time.
15.405 – IDXCOMP
a key value inserted into this index may exceed the maximum length Explanation: It is possible that when the key compression algorithm is run for some values inserted into this index the resulting key length may exceed 255 bytes. This condition is dependent on the data values and will probably occur rarely. User Action: This is just a warning. If you drop the index and recreate it as an uncompressed index you will guarantee that all rows can be stored.
15.406 – IDXCOMPLENERR
index compression length exceeds field length Explanation: You attempted to specify a shortened size for an index field that is greater than the field size. User Action: Specify a shortened size that is not larger than the field size.
15.407 – IDXDUPCOL
index definition contains a redundant reference to a column Explanation: The index definition repeated a reference to a column in a table. This usage is not needed and does not add any value to the index. User Action: This is just a warning. If you drop the index and recreate it without the redundant column reference it will occupy less space in the database.
15.408 – IDXMAPLIM
value exceeds bounds specified for mapping of index <str> Explanation: The data stored in a field exceeds the bounds specified for mapping the field. User Action: Determine the cause of the problem and correct either the record or the index.
15.409 – IDXMAPLMT
range of mapped index limited to HIGH - LOW = 2147483647 Explanation: You attempted to define an index using mapping ranges on variables so that the resulting key requires 32 or more bits. The maximum permitted is 2**31-4 User Action: Try to define the index again without using the relation-map-clause.
15.410 – IDXMAPLMTERR
index map limit exceeds value limit for field Explanation: You attempted to define an index using mapping ranges on variables that is bigger than the data type. User Action: Try to define the index again using accepted limits.
15.411 – IDXMAPNODIF
values for mapping of index must be different Explanation: The data used for a field mapping must be different. This message can appear for two reasons: you used the MAPPING VALUES clause in a CREATE INDEX definition and both the high and low values of the range were equal, or you used the ALTER INDEX ... ADD PARTITION statement and specified a new partition which matched exactly the WITH LIMIT OF clause of an existing partition, or it specified no WITH LIMIT OF clause and matched an existing OTHERWISE partition. User Action: Determine the cause of the problem and correct the index definition.
15.412 – IDXNOBLDPEND
index not in build pending state - build ignored Explanation: This index was not created with the MAINTENANCE IS DISABLED option, and therefore all partitions are already built. User Action: This is just a warning to help the database administrator.
15.413 – IDXNODPAG
index node size exceeds free space on page - fragmentation Explanation: You specified a node size which exceeds the free space on pages in one of the storage areas. The node will be fragmented and result in more I/O than necessary. User Action: This is just a warning. If you size the index node to better fix the page, or size the page for this index node size you may improve I/O performance when using this index.
15.414 – IDXNOTCHG
index <str> has not been changed Explanation: The specified index was not altered. User Action: Correct the problem and retry the metadata update.
15.415 – IDXNOTCOMP
index is not compressed Explanation: The index must be compressed if you want to specify these attributes (minimum run length, compressed octets). User Action: Redefine the index with the enable compression clause.
15.416 – IDXNOTDEF
index <str> has not been defined Explanation: The specified index was not defined. User Action: Correct the problem and try the metadata update again.
15.417 – IDXNOTDEL
index <str> has not been deleted Explanation: The specified index was not deleted. User Action: Correct the problem and retry the metadata update.
15.418 – IDXNOTHASH
index is not a hashed index Explanation: The hash type can only be specified for hashed indexes. This is not a hashed index. User Action: Redefine the index.
15.419 – IGNNOLOG1
ignoring NOLOGGING - Hot Standby is enabled and logging required Explanation: This is an informational message reported to the user when NOLOGGING is partially ignored. HOT STANDBY needs full logging to function correctly. User Action: No user action is required, but database administrators should note that full logging is still in use to the after image journal. Only logging to the recovery unit journal is disabled.
15.420 – IGNNOLOG2
ignoring NOLOGGING - logical area just created DEFERRED Explanation: This is an informational message reported to the user when NOLOGGING is ignored. When CREATE INDEX ... NOLOGGING is used with MAINTENANCE IS ENABLED DEFERRED logging is also deferred. However, Rdb can not disable logging in the same session. User Action: No user action is required, but database administrators should note that full logging is still in use and DDL operations on the index may generate more log file space than expected.
15.421 – IGNNOLOG3
alert for NOLOGGING - LogMiner requires logging to unload table data Explanation: This is an informational message reported to the user when NOLOGGING is seen on a LogMiner enabled database. Logging of table rows is required to support LogMiner actions on the table. User Action: No user action is required, but database administrators should note that any rows inserted into the table prior to COMMIT will not been seen by RMU/UNLOAD/AFTER_IMAGE.
15.422 – 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.
15.423 – 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.
15.424 – 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.
15.425 – INCCMTOPTIONS
inconsistent commit options on temporary table Explanation: If there is a constraint on temporary table T_SOURCE which references temporary table T_TARGET, and if temporary table T_TARGET has commit options ON COMMIT DELETE ROWS, then temporary table T_SOURCE must have the same commit options ON COMMIT DELETE ROWS. User Action: Please review and correct the temporary table definition to have commit options ON COMMIT DELETE ROWS.
15.426 – INCSEQATTR
sequence "<str>" has attributes incompatible with <str> Explanation: The attribute(s) specified during a create sequence or an alter sequence command is incompatible with other attributes specified. For example, the attribute RANDOMIZE is incompatible with the attributes ORDER, MAXVALUE and MINVALUE. User Action: Please review attributes and correct the sequence command. If the attribute was RANDOMIZE make sure it not specified with ORDER, MAXVALUE or MINVALUE.
15.427 – INDBLRBAD
incorrect storage map BLR generated for partitioned index <str> Explanation: The BLR generated for the index operation is incorrect. This may indicate that a problem exists in the product and should be reported to your support organization. It may also indicate that the index definition provided was incorrect but was not diagnosed through other software checks. User Action: Review the index definition and, if possible, correct it. If you think it is a software error, then contact your Oracle support representative for assistance.
15.428 – INDEXTS
there is another index named <str> in this database Explanation: The index name you tried to define already exists. User Action: Try another index name.
15.429 – INDEX_S_MAX
user requested node size of <num> bytes exceeds limit Explanation: The index node size you specified is greater than that supported by the implementation. User Action: Refer to the documentation and supply another value.
15.430 – INDEX_S_MIN
user requested node size of <num> bytes for index needing <num> Explanation: The index node size you specified is less than that needed by the implementation. User Action: Refer to the documentation, and supply another value.
15.431 – INDINMAP
index "<str>" is used in storage map "<str>" Explanation: You attempted to drop an index used in a storage map PLACEMENT VIA INDEX clause. User Action: You must alter the storage map to be NO PLACEMENT VIA INDEX before dropping this index.
15.432 – INDLIMITBAD
partition field <str> not in index Explanation: You attempted to partition an index using a field not included in the index. User Action: Specify the command again using only fields defined for the index.
15.433 – INDLIMITORDBAD
partition <num> limits are not in index order for partitioned index <str> Explanation: The limits are not specified according to the index order. For a descending segment, the corresponding limit values must be in descending order. User Action: Specify the command again with limits in index order.
15.434 – INDMAINTDIS
maintenance on index <str> has been disabled Explanation: An attempt was made to use an index that has been marked as maintenance disabled. User Action: Try another index.
15.435 – INDNEEDSLIMIT
limits must be specified for index Explanation: You attempted to define an index without specifying limits for all but the last partition of the index. User Action: Respecify your index definition, providing limits for all but the last area.
15.436 – INDNOTEXI
index <str> does not exist in this database Explanation: There is no index with the given name. User Action: Try SHOW INDEX to see which indexes exist.
15.437 – INDNOTREL
index <str> does not reference same relation as storage map Explanation: The index specified in the PLACEMENT VIA INDEX clause is not an index on the relation whose storage map is being defined. User Action: Select or create a new index for placement.
15.438 – INDTABBAD
index <str> does not reference table <str> Explanation: The specified index does not reference the specified table. User Action: You may have specified the wrong context variable or table name or have mistyped the index name. Try again.
15.439 – INDTOOBIG
requested index is too big Explanation: You attempted to define an index that requires more than 255 characters. The limit is the number of fields plus the sum of the number of bytes specifying the size of each field. User Action: Simplify the index definition or break it into two or more components.
15.440 – INDTOOMNYCOL
too many columns have been specified in the storage map BLR generated for partitioned index <str> Explanation: The storage map for the index does not agree with the index and has specified more columns for the partitioning than for the index. User Action: Please review and correct the index definition.
15.441 – INSFRPGS
physical memory has been exhausted Explanation: Physical memory has been exhausted on the machine, typically because of an excessive number of cache global sections, or excessively large cache global section sizes. User Action: If possible, increase the amount of physical memory on the machine. Reduce the number of cache global sections, or reduce the size of each active cache global sections. Possibly moving a cache from SSB to VLM will also solve this problem. It might be necessary to delete some caches to alleviate this problem. Also, re-configuring the operating system parameters may be necessary to reduce physical memory consumption.
15.442 – INSNOREAD
cannot read column "<str>" from target row during INSERT Explanation: The AUTOMATIC column attempted to reference the row being inserted. User Action: AUTOMATIC columns can not reference the target row during insert because the data may not yet be completely materialized. Correct the AUTOMATIC column definition to either be UPDATE (which can reference the old row version), or rework the value expression to avoid reference to the inserted row.
15.443 – INVACC_IN_PARAM
attempt to write to an IN parameter Explanation: This parameter is declared as mode IN which does not allow updates. User Action: If you wish to update this parameter, then change its mode to INOUT or OUT. Otherwise correct the reference to this parameter.
15.444 – INVACC_OUT_PARAM
attempt to read from an OUT parameter Explanation: This parameter is declared as mode OUT which does not allow read access (its value is undefined). User Action: If you wish to read this parameter, then change its mode to INOUT or IN. Otherwise correct the reference to this parameter.
15.445 – INVACC_PARAM
invalid expression passed to INOUT/OUT parameter "<str>" (<num>) Explanation: The value expression used for this parameter can not accept an output value. User Action: Correct the usage for this parameter to be a variable or parameter.
15.446 – INVACE_LENGTH
invalid Access Control Entry length Explanation: You specified too many identifiers in the access control entry (ACE). User Action: Reduce the number of identifiers in the ACE. The maximum number of identifiers in ACE is 30.
15.447 – INVALID_CALL
routine "<str>" returns a value -- use only in an expression Explanation: You referenced a function as a procedure using a CALL statement. You must only use the function in a value expression. User Action: Correct the usage of the function.
15.448 – INVALID_FUN
routine "<str>" is not a function -- usage is invalid Explanation: You referenced a procedure as a function in a value expression. You must only use the CALL statement to call a procedure. User Action: Correct the usage of the procedure.
15.449 – INVALID_OBLR
syntax error or missing query in query outline Explanation: A syntax error or omission was found in the query outline OBLR. User Action: Dump the OBLR using RDMS$DEBUG_FLAGS="Sos"; then compare the OBLR structure with the BLR from the corresponding query.
15.450 – INVALID_OUTLINE_ID
"<str>" (<num>) in outline does not match the query Explanation: An illegal table identifier was found in the query outline string. User Action: The outline is incomplete or invalid. Regenerate a query outline with the optimizer, and ensure that query blocks are not deleted and that table identifiers are not modified.
15.451 – INVASSIGNMENT
illegal target for assignment Explanation: Oracle Rdb restricts the targets for BLR$K_ASSIGNMENT to be columns within the table referenced by the BLR$K_STORE, BLR$K_STORE2 or BLR$K_PLACE statements. Additionally, built-in functions, such as BLR$K_GET_INFO, BLR$_CURRENT_TIME, BLR$_CURRENT_TIMESTAMP, and BLR$_CURRENT_DATE can only be sources in an assignment, not in targets. User Action: If you called Oracle Rdb using DSRI, please correct the query string. Otherwise, contact your Oracle support representative for assistance. You will need to provide the statements that produced this error.
15.452 – INVCASEEXP
case expression has no data type (all branches are NULL) Explanation: The result data type of a CASE expression is calculated from each of the result value expressions following the THEN clause. This CASE expression only has NULL which has no data type attributes. (Note that a missing ELSE clause also defaults to NULL.) User Action: If you want to use NULL, then use CAST(NULL AS some-dtype) to apply a data type to the NULL specification.
15.453 – INVCATALOGID
invalid catalog identification <num> - must be negative Explanation: Catalog identifiers are always negative numbers. User Action: Correct the MBLR generation and try again.
15.454 – INVDATOPR
invalid date arithmetic operation Explanation: The operation requested is not legal. The operands, operator, or the result is not valid for date/time arithmetic. User Action: Correct the operation to one that is valid.
15.455 – 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.
15.456 – 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.
15.457 – INVDB_TYPE
invalid database type for attach Explanation: You attempted to attach to an SERdb database from Oracle Rdb. User Action: Use only Oracle Rdb to attach to an Oracle Rdb database and use only SERdb to attach to an SERdb database.
15.458 – INVDSCTYP
specified data type can not be passed/returned by descriptor or length Explanation: The specified data type for the parameter or function result can not be passed or returned by mechanism DESCRIPTOR or LENGTH. User Action: Change the specified passing mechanism to be by-reference or by-value, or change the data type of the parameter or return type.
15.459 – INVDTYPINDX
cannot use computed by or segmented string for index Explanation: You attempted to define an index using either a COMPUTED BY field or a segmented string as the key. User Action: Select another field as the key.
15.460 – INVDTYPKEY
key <str> cannot be a computed by or segmented string field Explanation: You attempted to define a UNIQUE, PRIMARY KEY, or FOREIGN KEY REFERENCES relation-specific constraint with a key field having either a computed by or segmented string datatype. User Action: Select another field for the key.
15.461 – INVESCSEQ
invalid character found after escape character Explanation: A character other than a wildcard or an escape character was found following an escape character in the pattern provided. User Action: Ensure that only a wildcard character or an escape character follows the escape character.
15.462 – INVESCVAL
invalid escape clause value Explanation: An escape clause value must be non-null and exactly one character in length. User Action: Ensure that the escape clause value is one character in length.
15.463 – INVFORUPDATE
invalid FOR UPDATE option (<num>) - must be a Boolean value Explanation: The value passed to a compile request was outside the legal range. Please specify a valid option. User Action: Please correct the item-list to RDB_COMPILE_REQUEST.
15.464 – 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.
15.465 – INVIDENT
invalid rights identifier found Explanation: In a protection statement that refers to an existing access control entry, there was no entry in the rights database. User Action: Make sure that any identifiers and/or UIC you specify are defined in the system rights database.
15.466 – INVIDXATTR
invalid attribute specification for the index Explanation: One or more of the index attribute specifications is invalid. User Action: Re-enter the request with the correct index attribute definition.
15.467 – INVIDXRL
invalid value specified for the index minimum run length Explanation: An invalid value was specified for the minimum run length attribute of the index. User Action: Redefine the index.
15.468 – INVINFOTBL
invalid use of information table Explanation: You attempted to create an information table or reference an information table in an invalid way. Here are some invalid ways it could have been used: 1) Constraints and triggers cannot be defined on an information table. 2) Indexes cannot be defined on an information table. 3) Storage maps cannot be defined on an information table. 4) An information table cannot be altered. User Action: Redefine the information table or reference to the information table to comply as described above.
15.469 – INVJOINBOOL
invalid join condition specified Explanation: You have specified a join condition for a CROSS or UNION join which is not allowed. User Action: Remove the join condition.
15.470 – INVMARKOP
invalid markpoint commit/rollback for TSN <num>:<num>, MARK_SEQNO <num> Explanation: A fatal, unexpected error was detected by the database management system during the commit or rollback of a markpoint. This message indicates the "transaction sequence number" of the transaction and the "markpoint sequence number" of the markpoint that has to be committed or rolled back. User Action: Contact your Oracle support representative for assistance.
15.471 – INVMAXROWS
invalid optimizer maximum rows (<num>) - must be greater than zero Explanation: The value passed to a compile request was outside the legal range. Please specify a valid number of rows which is expressed as a positive integer. User Action: Please correct the item-list to RDB_COMPILE_REQUEST.
15.472 – INVMAXTIME
invalid compile time limit (<num>) - must be greater than zero Explanation: The value passed to a compile request was outside the legal range. Please specify a valid number of seconds which is expressed as a positive integer. User Action: Please correct the item-list to RDB_COMPILE_REQUEST.
15.473 – INVMETACACHE
cached metadata for table "<str>" invalidated by online change Explanation: An online metadata change to the TABLE in the exception message has produced a new version of the TABLE. The exception indicates an attempt to update a record in the database with obsolete, in- consistent metadata from the in memory cache. User Action: Detach and re-attach to the database. This will cause any cached metadata to be reloaded into the in memory symbol tables.
15.474 – INVMODAUTH
invalid module authorization name specified Explanation: The module authorization clause does not specify a valid system rights identifier. User Action: Re-enter the command with the correct user name in the authorization clause.
15.475 – INVMOD_NAME
invalid module name Explanation: You entered a misspelled or nonexistent module name. User Action: Reenter the command with the correct spelling of a valid module name.
15.476 – INVNAME
symbol <str> contains invalid characters or is too long Explanation: Name symbols may contain only the characters A through Z, 0 through 9, and $ and _. They may not end in $ or _. User Action: Use a different name symbol.
15.477 – INVOPTPREF
invalid optimizer preference (<num>) - must be total-time or fast-first Explanation: The value passed to a compile request was outside the legal range. Please specify a valid option. User Action: Please correct the item-list to RDB_COMPILE_REQUEST.
15.478 – INVORDHASH
invalid ORDERED hashed index definition Explanation: The ORDERED hashed index being defined is invalid. Compression cannot be enabled with an ORDERED hashed index. The last column referenced in the ORDERED hashed index must be a binary value (TINYINT, SMALLINT, INTEGER, BIGINT, DATE, TIME, TIMESTAMP, or INTERVAL). User Action: Redefine the index either by not enabling compression or by ensuring that the last column in the index definition is a binary value.
15.479 – 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.
15.480 – INVPRMCNT
routine <str> expected <num> parameter(s), passed <num> parameter(s) Explanation: The wrong number of parameters was passed to the specified routine. User Action: Check the definition of the routine in the database. Pass the correct number of parameters to the specified routine.
15.481 – INVRETTYP
result data type can not be returned by value Explanation: The specified data type for the function result can not be returned by value. User Action: Change the specified passing mechanism to be by-reference or by-descriptor, or change the data type of the return type.
15.482 – INVRTNUSE
routine <str> can not be used, image "<str>" not activated Explanation: The specified external routine can not be used because the image was not successfully dynamically activated. User Action: Review the secondary error message or messages, verify that the external routine definition location specification is correct, verify that the image is available at the specified location, and that the image is a shareable image which can be dynamically activated.
15.483 – INVRTN_NAME
invalid routine or procedure name Explanation: You entered a misspelled or nonexistent routine name. User Action: Reenter the command with the correct spelling of a valid routine name.
15.484 – INVSCHEMAID
invalid schema identification <num> - must be positive Explanation: Schema identifiers are always positive numbers. User Action: Correct the MBLR generation and try again.
15.485 – INVSECIMAGE
image location specification fails secure translation Explanation: The image location specification specified by the primary error could not be successfully translated using OpenVMS secure EXEC mode logicals. User Action: Review the secondary error message or messages, verify that the external routine definition location specification is correct, verify the definition of all associated logical names, and that the image file can be accessed via the appropriate logicals.
15.486 – INVSEQATTR
sequence "<str>" has an illegal value for <str> Explanation: The attribute specified during a create sequence or alter sequence command is illegal. The attribute "INCREMENT BY" must not be zero (0). User Action: Please review attributes and correct the sequence command. If the attribute was "INCREMENT BY" make sure it is non-zero.
15.487 – INVSYNONYM
invalid synonym name "<str>" - name used by another object Explanation: The synonym is named the same as an existing synonym, or some other object (such as a table, sequence, domain, module, type or routine). User Action: Choose another name for this synonym.
15.488 – INVTBL_NAME
invalid relation name Explanation: You entered a misspelled or nonexistent relation name. User Action: Reenter the command with the correct spelling of a valid relation name.
15.489 – INVTEMPTBL
invalid use of temporary table Explanation: You attempted to create a temporary table or reference a temporary table in an invalid way. Here are some invalid ways it could have been used: 1) A temporary table definition cannot contain a constraint which references a non-temporary(base) table. 2) A base table definition cannot contain a constraint which references a temporary table. 3) Datatrieve attributes, a CDD Pathname or COMMENT ON cannot be specified on a declared temporary table definition. 4) Indexes cannot be defined on a temporary table. 5) Only storage maps with no areas are legal on temp tables. User Action: Redefine the temporary table or reference to the temporary table to comply as described above.
15.490 – INVTRANOPT
the transaction option "<str>" is not allowed Explanation: A transaction mode was specified on the SET TRANSACTION (SQL) (or RDO START_TRANSACTION) statement which is currently not allowed for this database. These modes are established using the SET or ALTER TRANSACTION MODES clause on CREATE and ALTER DATABASE. User Action: Use the SHOW DATABASE statement in SQL to examine the enabled modes for this database and change your set transaction accordingly. Or, have the database administrator modify the database-wide settings to allow this transaction to be executed.
15.491 – INVTRGACT_STMT
invalid trigger action statement - can not modify target table Explanation: A trigger action has attempted to modify (INSERT, UPDATE or DELETE) the table that is the target of an active trigger. Any table that is the target of a trigger action becomes temporarily read-only while the trigger actions execute. User Action: Correct the application logic to remove this modify attempt.
15.492 – INVTRIMOPT
trim error - invalid trim option specified Explanation: The TRIM option specified for the TRIM operator must be one of the following: LEADING, TRAILING, or BOTH User Action: Correct the BLR to generate a valid option for TRIM.
15.493 – INVVALTYP
parameter <num> can not be passed BY VALUE Explanation: The specified data type or the parameter mode (OUT or INOUT) can not be passed BY VALUE. User Action: You should either change the data type, parameter mode or parameter mechanism to a combination which is legal.
15.494 – INV_DATE_CHG
invalid field datatype change to/from datetime Explanation: An attempt was made to change the data type of a datetime field to a data type which was not compatible. User Action: Consult the documentation for a list of valid conversions to/from datetime fields.
15.495 – INV_DIGITS
invalid precision for exact numeric, must be in range <num>..<num> Explanation: The data definition language requested a TINYINT, SMALLINT, INTEGER, or BIGINT with a precision restriction (number of digits) which was larger than that supported by the data type. User Action: Correct the definition so that the number of digits requested is within the legal range.
15.496 – INV_PCT_FILL
percent fill out of valid range of 1 through 100 Explanation: The index percent fill you specified is not a valid value. User Action: Refer to the documentation and supply another value.
15.497 – INV_PRECISION
invalid interval leading field precision for datetime Explanation: The data definition language requested an interval leading field precision which is outside the supported range. User Action: Correct the definition so that the interval leading field precision is within the legal range.
15.498 – 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.
15.499 – INV_SCALE
invalid fractional seconds precision for datetime Explanation: The data definition language requested a fractional seconds precision for a TIME, TIMESTAMP, or INTERVAL definition which is outside the correct range. User Action: Correct the definition so that the fractional seconds precision is within the legal range.
15.500 – INV_SUB_TYPE
invalid sub_type in definition Explanation: The data definition language requested a sub-type which was not recognized. User Action: Correct the definition so that the sub-type is within the legal range.
15.501 – IOINDDUPDEF
a nested index definition implies that duplicates are sorted Explanation: An INDEX ONLY index must be unique or have duplicates sorted. If a nested index definition exists, then the duplicates handling must be specified as sorted. Likewise, if the duplicates handling is specified as sorted, then a nested index definition must exist. User Action: The index can not be created in this manner. Recreate the index as a unique index, or with a nested duplicates index, specifying that the duplicates are to be sorted.
15.502 – IOINDDUPINV
sorted duplicates are only valid within a nested index definition Explanation: If the duplicates handling is specified as sorted, then a nested index definition must exist. User Action: The index can not be created in this manner. Recreate the index without the duplicates are sorted clause or with a nested duplicates index, specifying that the duplicates are to be sorted.
15.503 – IOINDDUPKEY
index definition contains an identical column reference in both keys Explanation: The index definition repeated a reference to a column in a table within the primary index key and the duplicates index key. This usage is not allowed within an INDEX ONLY index definition which has duplicates sorted. User Action: The index can not be created in this manner. Recreate the index using making sure that the column values within the primary index key are not reused within the duplicates index key.
15.504 – IOINDDUPSORT
An INDEX ONLY index must be unique or have duplicates sorted. Explanation: You attempted to create an INDEX ONLY index which is not unique and does not have duplicates sorted. This operation is not allowed. User Action: An INDEX ONLY index must be unique or have duplicates sorted. Please create the index accordingly.
15.505 – IOINDEXISTS
An INDEX ONLY index has already been defined on this table Explanation: You attempted to create additional secondary indices on an INDEX ONLY table. This operation is not allowed. User Action: If secondary indices are required, then do not use INDEX ONLY indices.
15.506 – IOINDONLY
An INDEX ONLY index must be the only index defined on the table Explanation: You attempted to create an INDEX ONLY index on a table which already had indices defined upon the table. This operation is currently restricted. User Action: Either use a sorted or hashed secondary index on the table, or delete the currently defined indices on this table, so that the INDEX ONLY index can be created.
15.507 – IOINDTBLDATA
An INDEX ONLY index can only be created on an empty table Explanation: You attempted to create an INDEX ONLY index on a table which already contains data. This operation is currently restricted. User Action: Either create a sorted or hashed secondary index on the table, or unload the data from the table so that the INDEX ONLY index can be created.
15.508 – 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.
15.509 – JOIN_CTX_UPD
relation <str> is part of a join - cannot be updated Explanation: You tried to modify or erase records from a relation that is joined with other relations. User Action: Redefine the query so that the relation you are trying to update is not directly joined to other relations.
15.510 – LASTARENOLIMIT
last area clause must not have a LIMIT clause Explanation: You specified limits (RDO) or BLR (DSRI) for the data to be inserted into the last area listed. User Action: Do not specify a limit for the data in the last storage area.
15.511 – 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.
15.512 – 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.
15.513 – LEVEL_MISMATCH
the table/subquery nesting levels in the query outline do not match the query Explanation: The subquery hierarchy of the query outline does not match the subquery hierarchy of the query. Subqueries or tables can be omitted from the query outline, but for each subquery that is present, all containing subqueries must also be present. User Action: Edit the query outline to correct the inconsistency, or regenerate a new outline by running the optimizer. Then make the desired modifications to the new outline.
15.514 – LISTAREAFULL
the areas specified in the list storage map for <str> are full Explanation: The areas specified for the table or column have returned errors during file extension operations. If these are WORM areas, they may be marked as "WORM device full". User Action: Consider adding more areas to the storage map or moving the areas to a higher capacity device. Refer to the ALTER facility or RMU MOVE command documentation for clearing the full flag for WORM areas.
15.515 – LISTNODEFAULT
default list storage area "<str>" must be specified in storage map Explanation: The default list storage area (defined using the CREATE DATABASE statement) must be used as a catch all for list mappings. This enables the system table LIST OF BYTE VARYING to be automatically mapped to this storage area. User Action: Consult the SQL Reference Manual for correct LIST storage map syntax. There should be an IN clause which specifies the default list storage area, without a FOR clause.
15.516 – 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.
15.517 – LOGADDCCH
added record cache definition "<str>" Explanation: A new record cache definition has been successfully added the the database.
15.518 – 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.
15.519 – 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.
15.520 – 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.
15.521 – 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.
15.522 – LOGDELAIJ
deleted temporary after-image journal file <str> Explanation: This message indicates the action taken on a specific file.
15.523 – LOGDELCCH
deleted record cache definition "<str>" Explanation: A record cache definition has been successfully deleted from the database.
15.524 – LOGMODCCH
modifying record cache definition "<str>" Explanation: The parameters for a record cache are in the process of being modified.
15.525 – LOGMODSPM
modified <num> spam page(s) Explanation: None.
15.526 – LOGMODSTO
modifying storage area <str> Explanation: The parameters for a storage area are in the process of being modified.
15.527 – LOGRECOVR
<num> transaction(s) <str> Explanation: Database recovery was successful. The specified number of transactions were re-applied to the database, ignored, or rolled back. User Action: None.
15.528 – 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.
15.529 – 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.
15.530 – 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.
15.531 – 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.
15.532 – LRSNOOUT
AIJ Log Roll-Forward Server does not have an output file Explanation: The AIJ Log Roll-Forward Server process does not have an output file associated with it. User Action: Use the /OUTPUT qualifier to specify an output filename when database replication is started on the standby database.
15.533 – 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.
15.534 – MAPAREAINUSE
area <str> already specified for map <str> in partition <num> Explanation: You used the area name more than once in the same storage map. The area can only be used once for table storage maps, and can not appear more than once in an area set for a list (segmented string) storage map. User Action: Use the area name only once in the storage map or list area set definition.
15.535 – MAPBLRMISSING
one or more areas is missing a limitation (WITH LIMIT clause) Explanation: You have not specified WITH LIMIT clauses for all storage areas in the map which are required to have limits. You must omit limits on all storage areas for RANDOMLY ACROSS maps, or you may omit the WITH LIMIT clause for the final storage area for value partitioned maps. If you specified that the map partitioning is NOT UPDATABLE then you are creating a map that enforces strict data partitioning. Therefore, you must provide WITH LIMIT clauses for each area (and optionally the last area) in the map. User Action: Correct the storage map creation statement to provide WITH LIMIT clauses where needed.
15.536 – MAPNMINUSE
map name <str> is already in use in this database Explanation: You tried to define a map or index using a name that already exists in the database. User Action: Use a name that has not already been used in the database.
15.537 – MAPNOTCHG
map "<str>" has not been changed Explanation: The specified storage map was not been altered or renamed. User Action: Correct the problem and try the metadata update again.
15.538 – MAPREFAREA
error deleting storage area <str> referenced by <str> Explanation: You attempted to delete a storage area currently referenced by a storage map. User Action: Make sure the storage area you wish to delete is empty and no storage maps refer to it.
15.539 – MAXMINSEQ
maximum or minimum sequence value has been reached Explanation: The maximum value for an ascending sequence or the minimum value for a descending sequence has been reached. There are no more sequence values available. User Action: Alter the sequence to increase the maximum value for an ascending sequence or decrease the minimum value for a descending sequence. Alternatively, alter the sequence to enable the CYCLE attribute.
15.540 – MAXRECLIM
query governor maximum limit of rows has been reached Explanation: The query governor quota of the maximum number of rows has been reached. User Action: Please refer to the documentation on the setting of query governor limits.
15.541 – MAXRELVER
exceeded maximum table (relation) identifier Explanation: No more table (relation) identifiers are available. User Action: Unload your database, recreate the database, and reload using the EXPORT/IMPORT utilities or using programs.
15.542 – MAXRTNVER
exceeded maximum routine/module identifier Explanation: No more routine/module identifiers are available. User Action: Unload your database, re-create the database, and reload it by using the EXPORT/IMPORT utilities or by using programs.
15.543 – MAXTIMLIM
query governor maximum timeout has been reached Explanation: The query governor quota of the maximum number of seconds that a database request can be optimized has been reached. User Action: Please refer to the documentation on the setting of query governor limits.
15.544 – MAXVIEWID
exceeded maximum view identifier Explanation: No more view identifiers are available. User Action: Unload your database, recreate the database, and reload using the EXPORT/IMPORT utilities or using programs.
15.545 – MAX_CCTX
exceeded maximum allowable context number Explanation: The number of contexts used in a request exceeds the limit, where a context is defined as a cursor value source or a query/subquery. (Note that the term "context" is used differently here than elsewhere in Oracle Rdb.) A cursor value source consists of a table, aggregate, EXISTS predicate, UNIQUE predicate, quantified predicate or UNION clause in a request. In terms of BLR, a cursor value is any of the following BLR$K_ objects: AGGREGATE, ALL, ANY, ANY2, AVERAGE, COUNT, FROM, MAXIMUM, MERGE, MINIMUM, RELATION, RELATION_ID, TOTAL, UNIQUE, VIA. Cursor values are obtained from a user-generated request; or from the BLR associated with a view, constraint, trigger, or other metadata object. Cursor queries/sub-queries are produced for each record selection expression (RSE) and FETCH statement. User Action: If you called Oracle Rdb, check the query string and simplify if possible. Otherwise, Contact your Oracle support representative for assistance.
15.546 – MAX_CEQV
exceeded maximum allowable equivalence number Explanation: The number of join equivalences used in a request exceeds the limit. The limit is 32 in Rdb versions prior to 7.0, and it is 1024 in later versions. User Action: Break up the query into separate requests, materialize the results of each request, and then join each result to get the intended result. If temporary table support is available in the version of Rdb you are using, you can use the temporary tables to store the result of each request.
15.547 – 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.
15.548 – MISMMORDD
missing either month or day field in date string Explanation: The date string must contain the month and day field. Otherwise, it will not be converted to the DATE data type. User Action: Re-enter the DATE data item and specify both the month and day fields.
15.549 – MISSINGINV
existing records in relation <str> would violate VALID IF expression Explanation: When a new field is added to a relation, previously stored records will have the new field's value set to NULL (MISSING). In your relation, the VALID IF constraint defined for the new field is violated by this action. User Action: Modify all the records where the new field is set to NULL (MISSING) to have a non-null value, or change the VALID IF clause for the field to allow MISSING values.
15.550 – MISSINVSEG
Missing value is an invalid segmented string attribute Explanation: The missing value attribute cannot be specified with a domain or column which has a datatype of segmented string. User Action: Ensure that the missing value attribute is not specified with a segmented string on the domain or column.
15.551 – MIXCLUST
relation or index may not be stored in mixed and uniform areas Explanation: You attempted to define a storage map that refers to both mixed and uniform areas. User Action: Define the storage map to refer to only uniform areas or only mixed areas.
15.552 – MODEXTS
there is another module named <str> in this database Explanation: The module name you tried to define or on which you attempted to perform an operation, already exists in this database. Note that stored and non-stored modules share the same name space. User Action: Use another module name. If you have already invoked a non-stored module, then disconnect the session before performing any operation on the stored module. Alternatively, if you have already invoked a stored module, then disconnect the session before performing any operation on the non-stored module.
15.553 – MODIDNEXTS
module ID, <num> does not exist in this database Explanation: The specified module ID does not exist in the current database. User Action: Invoke the correct database. Specify the module ID correctly.
15.554 – MODNEXTS
module <str> does not exist in this database Explanation: The specified module does not exist in the current database. User Action: Invoke the correct database. Spell the module name correctly. Check the name of the module and try the command again.
15.555 – MODNOTDEL
module "<str>" has not been deleted Explanation: The specified module was not deleted. User Action: Correct the problem and try the metadata update again.
15.556 – MODRTNNEXTS
no routines with module ID <num> Explanation: There are no routines with the specified module ID in the current database. User Action: Invoke the correct database. Specify the module ID correctly.
15.557 – MONALSTART
database monitor is already running Explanation: The database monitor has previously been started. User Action: Continue or see your system manager.
15.558 – MONFLRMSG
failure message received from the monitor Explanation: An error happened in the monitor process. The user process received the error message. User Action: Examine the monitor log on the node where the user program was running to see messages relating to the monitor error.
15.559 – MONMBXOPN
monitor is already running Explanation: The monitor has already been started by another user. User Action: No action is required.
15.560 – 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.
15.561 – MSSINCCOL
MISSING VALUE is incompatible with datatype of column <str>.<str> Explanation: The specified MISSING_VALUE (RDO) or MISSING VALUE (CDD/Rep) is not compatible with the datatype of the column (field). User Action: Ensure that the datatype of the column and the MISSING VALUE are consistent. Check the domain used by column to verify consistency between datatypes and MISSING VALUEs.
15.562 – MSSINCDOM
MISSING VALUE is incompatible with datatype of domain <str> Explanation: The specified MISSING_VALUE (RDO) or MISSING VALUE (CDD/Rep) is not compatible with the datatype of the domain (global field). User Action: Ensure that the datatype of the domain displayed in the error message is consistent with the MISSING_VALUE (RDO) or MISSING VALUE (CDD/Rep) of the domain.
15.563 – MULTCHGAREA
multiple references to area <str> in same CHANGE DATABASE command Explanation: You attempted to change one storage area multiple times in your CHANGE DATABASE statement. User Action: Combine your changes to one storage area to one clause.
15.564 – MULTPLACEVIA
storage map command contains multiple PLACEMENT VIA clauses Explanation: The storage map command contained either multiple PLACEMENT VIA clauses or both a PLACEMENT VIA and NO PLACEMENT VIA clause. User Action: Refer to the documentation on storage map usage for more information on how to use the command.
15.565 – MULTSCHEMNODIS
the multischema database attribute can not be disabled Explanation: You attempted to change the database to be NO MULTISCHEMA. This is not supported. User Action: Please use EXPORT and IMPORT to effect this change.
15.566 – MULTSCHEMNOW
the database is already a multischema database Explanation: You attempted to change the database to be MULTISCHEMA when it was already. User Action: No user action required. The database has the multischema attribute.
15.567 – 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.
15.568 – NDXPMTDUPS
text compressed indices must permit duplicates Explanation: You attempted to create an index with duplicates not allowed using the DUPLICATES NOT ALLOWED clause. However, you cannot use the DUPLICATES NOT ALLOWED clause when defining a text compressed index. User Action: Do not use the DUPLICATES NOT ALLOWED clause when you define a text compressed index.
15.569 – NEEDSNOEXTEND
area <str> already has <num> page(s) Explanation: The extension of the specified storage area was trivial, as the number of pages before was exactly same. User Action: Check page count of the current area allocation. (If it should differ)
15.570 – NETACCERR
error <str> <str> network <str> Explanation: A network-access error occurred. User Action: Examine the secondary message for more information.
15.571 – NOACCSEGSTR
cannot access buffer for segmented string Explanation: At least part of the user's buffer is not accessible. User Action: Check program logic; the segmented string buffer address and/or length is incorrect.
15.572 – 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.
15.573 – 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.
15.574 – 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.
15.575 – NOAIJSERVER
database replication server is not running or running on other node Explanation: The database replication server process is not running on the standby node specified, or has abnormally terminated. There may also be a problem with the mailbox used to communicate with the database replication server. User Action: Check the system to determine whether or not the database replication server process is actually running on your system. Check the use of cluster aliases, as the replication connection may have been attempted on another node of the designated cluster. If the database replication server process does not appear to be running, have your database administrator start the replication server, and try again. If the database replication server process appears to be running properly, then the problem may be related to the mailbox by which user processes communicate with the replication server process. Make sure the "server name" specified for both the live and standby databases logical are unique and identical. On VMS platforms, the "server name" is used to create a logical of the same name that resides in a logical name table accessible to all users, typically the LNM$PERMANENT_MAILBOX name table. If the replication server process abnormally terminated, a bugcheck dump will normally be produced. Search the bugcheck dump for a string of five asterisks (*****) using the SEARCH/WINDOW command. You will see a line with a format similar to this: ***** Exception at <address> : <database module name> + <offset> %facility-severity-text, <error text> The exception line will be followed by one or more additional errors that will help you to determine what caused the replication server process to fail. Typically, the problem is caused by insufficient quotas or system resources. However, other possible causes include misdefined or undefined filename logicals. Depending 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.
15.576 – 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.
15.577 – NOALTIOIND
ALTER is not allowed on an INDEX ONLY index Explanation: You have attempted to alter an INDEX ONLY index. This operation is not allowed. User Action: Re-evaluate why this change is necessary on the INDEX ONLY index. If the change is necessary then drop the INDEX ONLY index which will move the data from the index into the table. The action of dropping the INDEX ONLY index will convert the INDEX ONLY table into a regular table. The user can then alter the table, and recreate the INDEX ONLY index.
15.578 – NOALTIOTBL
ALTER is not allowed on an INDEX ONLY table Explanation: You have attempted to alter an INDEX ONLY table. When an INDEX ONLY index is defined on a table, the table is then labeled an INDEX ONLY table. This operation is not allowed. User Action: Re-evaluate why this change is necessary on the INDEX ONLY table. If the change is necessary then drop the INDEX ONLY index which will move the data from the index into the table. The action of dropping the INDEX ONLY index will cause the the INDEX ONLY table to revert to regular table, and the alter table operation will be allowed.
15.579 – NOALTSUBIND
A duplicates sub-index may not be altered Explanation: You attempted to ALTER a sub-index which has been defined to manage duplicates within an INDEX ONLY index. This is not permitted. User Action: If you wish to ALTER the sub-index, then you must drop the INDEX ONLY index, and recreate the index and the sub-index.
15.580 – 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).
15.581 – 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.
15.582 – NOCACHEEXT
cache "<str>" not defined in the database Explanation: A cache mentioned in the ALTER DATABASE statement is not defined in the database. User Action: Reenter your statement with valid cache names.
15.583 – NOCATALOG
catalog <str> does not exist - alter or drop not possible Explanation: The catalog does not exist. User Action: Repeat the command with a name of a catalog which exists.
15.584 – 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).
15.585 – 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.
15.586 – NOCHGRDBSYS
cannot change RDB$SYSTEM storage area explicitly Explanation: You included a CHANGE STORAGE AREA RDB$SYSTEM clause in the CHANGE DATABASE statement. User Action: Issue the CHANGE DATABASE statement without this clause. When you change database-wide parameters, the RDB$SYSTEM parameters are automatically changed.
15.587 – NOCHGVW
the definition of view "<str>" may not be changed Explanation: An attempt to alter a view was made that is not supported. User Action: You must use the ALTER VIEW statement to change attributes of the view. Correct the statement and try again.
15.588 – NOCMPLXMAP
can not use complex map for non-empty table Explanation: You specified a storage map for a table which has data in it, however, the storage map was not a simple map. You may only specify a simple map when the table contains data. This map simply describes the state of the currently stored data. Once defined the ALTER STORAGE MAP statement can be used to apply a more complex mapping to the table. User Action: Redefine the storage map and ensure that the storage map specifies only the default storage area, that there is no PLACEMENT VIA INDEX clause, that the thresholds and compression attributes are not specified, and that the COLUMNS clause is not used to vertically partition the table.
15.589 – NOCOROUTINE
function can not act as a co-routine Explanation: A stored routine is invoked from another BLR program and so can not synchronize with a host program using BLR$K_SEND nor BLR$K_RECEIVE User Action: Remove or conditionalize references to these BLR statements
15.590 – 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.
15.591 – NOCRESYNONYM
target object for "<str>" can not be resolved Explanation: A synonym chain is formed when synonyms reference other synonyms. This error occurs that synonym chain has been broken using DROP SYNONYM ... CASCADE or a loop is formed because ALTER SYNONYM references a target synonym already appearing in the chain. User Action: This problem is detected during CREATE and ALTER SYNONYM. This statement has failed, repeat the statement with a corrected synonym reference which avoids this error.
15.592 – NODACINDEX
index "<str>" in area does not correspond to table Explanation: DROP STORAGE AREA <name> CASCADE was used in a case where it cannot be simply applied. User Action: Please review and correct the operation and issue the appropriate set of commands.
15.593 – NODACMTCHPART
index partitioning for index "<str>" does not match storage map "<str>"
15.594 – NODACSTRICT
PARTITIONING UPDATABLE specified for storage map "<str>"
15.595 – 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.
15.596 – NODELCACHE
the default cache RDB$CACHE may not be deleted Explanation: You attempted to drop the default cache RDB$CACHE. This is not permitted. User Action: Make sure the cache you drop is not the default cache RDB$CACHE.
15.597 – NODELPRIVANSI
privileges may not be deleted in an ANSI database Explanation: You attempted to delete a privilege in an ANSI-style database. User Action: You cannot delete a privilege in an ANSI-style database.
15.598 – NODELRESAREA
"<str>" is used as a default area and may not be deleted Explanation: You attempted to drop either the default storage area, or the default template area. This is not permitted. User Action: Make sure the area you drop is not reserved as a special area in this database.
15.599 – NODELSEGSTR
the segmented string storage area, <str> can not be deleted Explanation: You attempted to delete the segmented string storage area. User Action: Make sure the storage area you wish to delete is not the segmented string storage area.
15.600 – NODELSUBIND
A duplicates sub-index may not be deleted Explanation: You attempted to drop a sub-index which has been defined to manage duplicates within an INDEX ONLY index. This is not permitted. User Action: If you wish to delete the INDEX ONLY index, then this will in turn delete the sub-index.
15.601 – 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.
15.602 – NODMAX
<num> number of cluster nodes is greater than the Oracle Rdb maximum of <num> Explanation: The number of cluster nodes that may access the database you specified is too large. User Action: Refer to documentation, and try another value.
15.603 – NODMIN
<num> number of cluster nodes is less than the Oracle Rdb minimum of <num> Explanation: The number of cluster nodes that may access the database you specified is too small. User Action: Refer to documentation, and supply another value.
15.604 – NODUPSANSI
no duplicate identifiers allowed in ANSI ACL Explanation: Databases defined as ANSI compliant are restricted to a single instance of a UIC. User Action: Enter a protection command changing the user's protection to what is desired rather than having two entries in the ACL for the same user.
15.605 – 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.
15.606 – 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.
15.607 – NOEXTFUNC
external routines have not been initialized Explanation: The routine to initialize the OpenVMS client site external routine interface has failed. User Action: No user action is available at this time.
15.608 – NOEXTLMNOENA
cannot extract - AIJ file <str> does not have LogMiner enabled Explanation: This AIJ file came from a database that did not have LogMiner enabled at the time the AIJ file was created. User Action: No user action is required. This AIJ file cannot be extracted.
15.609 – 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.
15.610 – 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.
15.611 – 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.
15.612 – NOEXTSEC
external database security checking is not supported Explanation: SECURITY CHECKING IS EXTERNAL is not supported on NT. User Action: Specify SECURITY CHECKING IS INTERNAL.
15.613 – 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.
15.614 – NOGRPANSI
no group UIC's allowed in ANSI database access control list Explanation: Databases defined as ANSI compliant are restricted to single user UIC's in the access control entry, except for PUBLIC. User Action: Enter a protection command for each user rather than referring to them as a group, or give privilege to PUBLIC.
15.615 – NOIDENTANSI
no identifiers allowed in ANSI database access control list Explanation: Databases defined as ANSI compliant are restricted to single user UIC's in the access control entry, except for PUBLIC. No system or general identifiers are allowed. User Action: Enter a protection command for each user rather than referring to them as a group, or give privilege to PUBLIC.
15.616 – NOINTERUNI
no interval may be specified on uniform format pages Explanation: You attempted to specify a SPAM interval on a PAGES UNIFORM storage area. User Action: Do not specify an interval, as one will be automatically determined for you.
15.617 – 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.
15.618 – NOLOCKSOUT
no locks on this node with the specified qualifiers Explanation: No locks were found on the current node that match the specified command qualifiers. This usually indicates that either no monitors are active on this node, or no databases are currently being accessed on this node. User Action: If databases are active on the node, try using a less restrictive set of command-qualifiers.
15.619 – NOMAPONVIEW
a storage map may not be defined for a view Explanation: You tried to define a storage map for a view. User Action: You must define the storage map for a relation, not a view.
15.620 – NOMETADATA
metadata operations are disabled Explanation: The database has been setup with DDL operations disabled, using the METADATA CHANGES ARE DISABLED clause on CREATE or ALTER DATABASE. You may not CREATE, DROP or ALTER database objects. User Action: The database administrator must alter the database to re-enable metadata changes before this command can be used.
15.621 – NOMETAUPD
metadata updates are prohibited until CONVERT is COMMITTED Explanation: Metadata updates are not permitted unless the CONVERT operation has been committed or rolled back. User Action: Use RMU CONVERT to COMMIT or ROLLBACK the last CONVERT operation.
15.622 – NOMETSYSREL
operation illegal on system defined metadata Explanation: You attempted to define, delete, or change an index, constraint, or trigger on one or more Oracle Rdb system relations. Or you attempted to drop or alter an Oracle Rdb system sequence. Such changes, if permitted, could render the database unusable. User Action: Do not attempt any of these modifications to the system relations or system sequences.
15.623 – 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.
15.624 – NOMONITOR
database monitor is not running Explanation: The database monitor process is not running or has abnormally terminated. There may also be a problem with the mailbox used to communicate with the database monitor. User Action: Check the system to determine whether or not the database monitor process is actually running on your system. If the database monitor process does not appear to be running, have your database administrator start the monitor, and try again. If the database monitor process appears to be running properly, then the problem may be related to the mailbox by which user processes communicate with the monitor process. Make sure the logical <fac>$MAILBOX_CHANNEL resides in a logical name table accessible to all users, typically the LNM$PERMANENT_MAILBOX name table. If the monitor abnormally terminated, a bugcheck dump will normally be written to the monitor log. Search the monitor log for a string of five asterisks (*****) using the SEARCH/WINDOW command. You will see a line with a format similar to this: ***** Exception at <address> : <database module name> + <offset> %facility-severity-text, <error text> The exception line will be followed by one or more additional errors that will help you to determine what caused the monitor process to fail. Typically, the problem is caused by insufficient quotas or system resources. However, other possible causes include misdefined or undefined filename logicals. Depending on the cause of the problem, take the appropriate action. If you are uncertain of what to do, contact your Oracle support representative for assistance.
15.625 – 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.
15.626 – 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.
15.627 – 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.
15.628 – NOOPTCUR
cannot optimize -- AIJ file <str> is the current AIJ file Explanation: The current AIJ file cannot be optimized, because the optimized AIJ file would not be equivalent to the current AIJ file if more journaling was done after optimization. User Action: Start a new AIJ file, and then optimize the AIJ file in question.
15.629 – 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.
15.630 – 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.
15.631 – 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.
15.632 – 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.
15.633 – NOOVERIOIND
Overflow area is only allowed during INDEX ONLY index creation Explanation: You have attempted to create an Overflow area which is not associated with an INDEX ONLY index. This operation is not allowed. User Action: Only create an Overflow area during an INDEX ONLY index creation.
15.634 – NOPAGELOCK
page level locking can not be specified for <str> Explanation: Page level locking can never be applied to RDB$SYSTEM or the DEFAULT STORAGE AREA by CREATE, ALTER or IMPORT DATABASE.
15.635 – NOPLACEANSI
no user placement clauses allowed in ANSI ACL Explanation: Placement of ANSI database users' access control entries is controlled by the database facility. User Action: Enter a protection command without specifying either the POSITION or AFTER clause.
15.636 – 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.
15.637 – NORBK_MDBTRAN
a server procedure can not rollback or commit a multi-database transaction Explanation: You attempted to ROLLBACK or COMMIT in a multistatement, or stored procedure which executes as part of a transaction which spans multiple databases. This is not permitted because the server procedure is not aware of the other databases in the transaction. User Action: Instead execute a single statement ROLLBACK or COMMIT which is perform by the client and informs all associated databases.
15.638 – NORBK_MODINUSE
an active procedure may not rollback its own CREATE statement Explanation: A stored procedure attempted to ROLLBACK the transaction in which the procedure was created. This is not permitted. User Action: Before executing the procedure COMMIT the transaction in which the procedure was created. Or, execute ROLLBACK in the context of a committed object.
15.639 – NORECURSION
no recursive routine calls permitted Explanation: This release of Rdb does not support recursive calls to procedures or functions. This routine is already active. User Action: Correct the usage of the function or procedure.
15.640 – 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.
15.641 – NORTNENTRY
routine "<str>" can not be used, entry point "<str>" not found Explanation: The specified external routine can not be used because the specified entry point symbol was not found. User Action: Verify that the external routine definition location specification references the desired image, check the corresponding routine source for the global symbol definition, and verify that the associated image construction procedure makes the global entry symbol available to the image activator.
15.642 – 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.
15.643 – NOSCHEMA
schema <str> (<num>) does not exist, alter or drop not possible Explanation: The schema does not exist. User Action: Repeat the command with a name of a schema which exists.
15.644 – 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
15.645 – 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.
15.646 – 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.
15.647 – NOSIP
transaction is not a snapshot transaction Explanation: You have already started a transaction that is not a snapshot transaction. User Action: Use COMMIT or ROLLBACK to terminate your current transaction. Use READY BATCH RETRIEVAL to start a new snapshot transaction.
15.648 – 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.
15.649 – NOSOL_FOUND
No possible solution has been found by Rdb optimizer Explanation: No possible solution has been found by Rdb optimizer for the following reason: - Full outer join query with cross strategy is not possible. Only MATCH join execution is allowed for full outer join. User Action: Check if the join keys of the join predicates are compatible in data type. If the keys are not compatible, please apply a CAST function to make it compatible data type to be used as a join key in a match join strategy.
15.650 – NOSTAREAEXT
storage area <str> not defined in the database Explanation: A storage area mentioned in the ALTER DATABASE statement is not defined in the database. User Action: Reenter your statement with valid storage area names.
15.651 – 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.
15.652 – 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.
15.653 – NOSUCHPRF
unknown profile user or role Explanation: The user or role that you have specified does not exist in this database or at the operating system level, when identified externally. User Action: Specify only valid (known) users or roles or create them.
15.654 – NOSUCHTRANS
translation name <str> is invalid or undefined Explanation: The translation name is not known to Oracle Rdb. User Action: Check the translation name to ensure it is valid.
15.655 – NOSUCHUSER
unknown user "<str>" Explanation: An attempt was made to access information with a user name unknown to the database (for example, sending mail to the monitor or attempting to execute a database recovery process (DBR)) or to access information with a user name unknown to the operating system (for example, no record in the UAF file). User Action: Make sure the user name is spelled correctly and has been properly identified to either the database or the operating system. Do not attempt to run DBR from DCL; this is not allowed, because the system will automatically manage database recovery. Be sure the monitor user name is correctly specified.
15.656 – NOSYNONYM
synonym "<str>" does not exists in this database Explanation: This synonym could not be found. This may indicate an error in the synonym name. User Action: Please repeat the command using an object which exists.
15.657 – 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".
15.658 – 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.
15.659 – NOTDSKFIL
filename does not specify disk device type Explanation: A file name was specified which does not reference a disk oriented device type. User Action: Check the file name for a proper disk device type.
15.660 – NOTEMPHASH
cannot define an index of TYPE HASHED on a temporary table Explanation: Temporary tables only support indexes of TYPE SORTED. You attempted to create an index of TYPE HASHED on a temporary table. User Action: Redefine the index with TYPE SORTED for a temporary table.
15.661 – 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.
15.662 – 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.
15.663 – NOTHRESUNI
no thresholds may be specified on uniform format pages Explanation: You attempted to specify thresholds on PAGES UNIFORM storage area. User Action:
15.664 – 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.
15.665 – 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.
15.666 – 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.
15.667 – NOTLOCALRTN
invalid call to a local routine - in the wrong context Explanation: The routine is declared as LOCAL and may only be called by routines in the same owning module. User Action: Call the routine from within the module, or use USAGE IS GLOBAL for the routine so it can be called outside the module.
15.668 – 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.
15.669 – NOTRIGRTN
this stored routine may not be called from a trigger Explanation: Not all stored routines may be called from a trigger condition or trigger action. Routines which perform the following actions may not be called from triggers: includes the DELETE, INSERT, UPDATE data manipulation commands, includes transaction commands SET TRANSACTION, COMMIT, or ROLLBACK, or calls a stored routine using the CALL statement, or references a user defined SQL function. User Action: Correct the function or procedure to comply with these restrictions.
15.670 – 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.
15.671 – 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.
15.672 – 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.
15.673 – 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.
15.674 – 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.
15.675 – NOT_LICENSED
system is not licensed for use of database software Explanation: A Oracle Rdb kit has not been properly installed on the system. User Action: Check to see that you are licensed to use Oracle Rdb; and if you are, install or re-install the Oracle Rdb kit.
15.676 – 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.
15.677 – NOT_RESERV
attempt to access relation not mentioned in reserving list Explanation: You tried to access a relation not mentioned in the reserving list of your START_TRANSACTION statement. User Action: Start a new transaction and include the required relations in the reserving list.
15.678 – 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.
15.679 – NOT_VALID_FR
field <str> in relation <str> fails validation Explanation: When the CHANGE FIELD ... VALID IF operation was attempted, data that violated the specified validation criteria was found. User Action: Either change the validation criteria or change the data.
15.680 – NOUSERPRF
operation denied - user "<str>" does not exist in this database Explanation: The current user has not been defined in the profiles table. Undefined users are restricted to a subset of DDL operations. User Action: Create the user in the database using the SQL CREATE USER command.
15.681 – NOVIEWIND
cannot define an index for a view Explanation: You attempted to define an index for a view. User Action: Define an index for the field in the relation named in the view definition.
15.682 – 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.
15.683 – 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.
15.684 – NO_NEQFOJ
non-equi full outer join is not supported Explanation: An attempt was made to specify a full outer join without using an equijoin condition in the ON clause of the joined table expression. Full outer joins that do not include an equijoin condition are not supported in the current version of Oracle Rdb. User Action: Specify a full outer join with at least one equijoin condition, or rephrase the query by using the UNION operator to get the intended full outer join result.
15.685 – NULLRTNPRM
parameter <num> can not be a NULL value, external routine "<str>" not invoked Explanation: External routine was passed a NULL value as parameter. User Action: Check the corresponding external routine invocation expression for NULL values, and reissue the query.
15.686 – OBJ_INUSE
object "<str>" is referenced by <str> (usage: <str>) Explanation: You attempted to delete a database object, but the object is used by another object or other definition as described in the message text. User Action: First, review the database design; then, if desired, delete the other definition which references this object, and then delete this object.
15.687 – OBSUSERMU
specified command is obsolete, please use RMU equivalent Explanation: You requested that an RDO OPEN, CLOSE or RECOVER statement be executed, perhaps with an older version of RDO. These statements are no longer supported. User Action: Use the RMU/OPEN, RMU/CLOSE or RMU/RECOVER instead.
15.688 – OBSVER
obsolete version of database Explanation: You are trying to use an obsolete version of an Oracle Rdb database. User Action: Using an older version of Oracle Rdb, back up the database, and then restore it using your current version of Oracle Rdb.
15.689 – OK_NO_ACE
successful protection execution - no ACE returned Explanation: Indicates that no access control entry is returned. User Action: No user action.
15.690 – 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.
15.691 – OPERNOTIFY
system operator notification: <str> Explanation: The indicated message was sent to one of the configured system operators. User Action: Examine the indicated message and perform the appropriate operation.
15.692 – 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.
15.693 – 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.
15.694 – 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.
15.695 – OPTEXCSRT
AIJ record count exceeded specified <num> sort threshold Explanation: The number of AIJ records processed exceeded the maximum sort threshold specified by the <fac>$BIND_OPT_SORT_THRESHOLD logical name. This is not a fatal error. User Action: None. Use of the <fac>$BIND_OPT_SORT_THRESHOLD may reduce the sort work file disk space required for the AIJ optimization operation. However, this may result in a larger output file.
15.696 – 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.
15.697 – OPTINCONSIS
optimized AIJ file is inconsistent with the database Explanation: The database and/or some areas within the database are not consistent with the optimized AIJ file. The last transaction committed to the database and/or to some database areas is not the same as the last transaction committed to the database at the time the optimized AIJ file's original AIJ file was created. To use an optimized AIJ file for recovery, it must be consistent with the database and all areas. User Action: Use the original, non-optimized AIJ file to do the recovery.
15.698 – 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.
15.699 – 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.
15.700 – 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.
15.701 – OPTSRTSTAT
<str>: <num> Explanation: During optimization operations, statistics are often collected to aid the user in tuning. This message displays a single statistic.
15.702 – OUTLIDEXTS
a query outline with mode <num> already exists for this query Explanation: The query outline ID and mode specified in your query outline definition is already used by another query outline in this database. User Action: Use another mode value that has not already been used.
15.703 – OUTLINE_FAILED
could not comply with mandatory query outline directives Explanation: The query optimizer could not fully comply with the directives in the query outline, and the outline indicated that compliance with the outline was mandatory. User Action: Change the query outline to indicate that compliance is optional, or modify the outline constraints.
15.704 – OUTLNMINUSE
there is another query outline named <str> in this database Explanation: The query outline name you are trying to define already exists. User Action: Use another query outline name, or if the query name has been automatically generated for you, use another mode value.
15.705 – OUTLNOEXI
query outline <str> does not exist in this database Explanation: The query outline name you tried to use does not exist. User Action: Use another query outline name.
15.706 – OUTLNOID
object name or signature required Explanation: You have not provided appropriate query identification to indicate to which query the outline definition should apply. You must supply either a request signature or the name of an existing stored object within the query outline definition. User Action: Provide either an object name or request signature within your query outline definition.
15.707 – OUTLNOTAPPL
a query outline could not be generated for this procedure Explanation: You tried to create a query outline for a procedure that does not contain any statement to which a query outline can be applied. Query outlines are only applicable to statements that contain record selection expressions. User Action: Try another procedure.
15.708 – 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.
15.709 – 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.
15.710 – 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.
15.711 – PARTEXTS
partition "<str>" already exists for this map or index "<str>" Explanation: The name specified for this CREATE/ALTER STORAGE MAP or INDEX has been used before. User Action: Please restate the command using a unique partition name.
15.712 – PARTNEXTS
partition "<str>" does not exist in this map or index "<str>" Explanation: The name specified for this ALTER STORAGE MAP or INDEX does not exist in this database. User Action: Please restate the command using a known partition name.
15.713 – PARTNOFOLLOW
partition "<str>" has no following partition in map "<str>" - drop not allowed Explanation: You performed a DROP PARTITION on the final partition of an an index or storage map. DROP wants to migrates the data to the next partition in the map, but can not if this is the last partition. User Action: Use MOVE to move the data to another partition, or DROP INDEX or DROP STORAGE MAP to remove the partition.
15.714 – PARTOPERBAD
operator used in partitioning BLR is bad Explanation: The BLR specified for a storage map includes an unsupported operator. User Action: Contact your Oracle support representative for assistance.
15.715 – PGPEXISTS
<str> "<str>" has already been granted to <str> "<str>" Explanation: The role or profile has already been granted to the specified user. User Action: None.
15.716 – PGPNEXISTS
<str> "<str>" has not been granted to <str> "<str>" Explanation: The role is not granted for the specified user. User Action: The role must be granted first.
15.717 – PLACEVIA1ST
PLACEMENT VIA must only be on the first vertical partition Explanation: The storage map command contained multiple PLACEMENT VIA INDEX clauses. This clause must only appear on the first vertical partition, and not on subsequent partitions. User Action: Please refer to the documentation on storage map usage for more information on how to use this clause.
15.718 – PREMEOF
premature end of file encountered in <str> Explanation: A premature end-of-file was encountered while reading the specified file.
15.719 – PRFCREATED
some users or roles were created Explanation: Some of the users or roles specified did not exist in the profiles table, so they were created. User Action: This is just a warning. If you mistyped a user or role name, you may want to delete the user or role that was created and re-execute the operation with the correct name.
15.720 – PRFDISABLED
user or role was marked as disabled Explanation: The user or role does not exist on the system. Therefore, it was marked as disabled in the RDB$PROFILES table. User Action: This is just for your information. If you wanted this user to be enabled, they must be created at the operating system level and then be re-enabled.
15.721 – PRFEXISTS
a <str> already exists with the name "<str>" Explanation: The role, user or profile already exists in the database. User Action: Respecify using a name that has not been used previously.
15.722 – PRFIDEXT
name is used externally; potential name conflict Explanation: The name chosen for the role created is also used externally at the operating system level for a user, group, node or domain name. User Action: This is just a warning. If you wish to use that name in the future, to define a profile for the external definition, then delete the profile just created and choose another name.
15.723 – PRFINUSE
entry "<str>" is referenced by <str> "<str>" Explanation: You attempted to delete a role, user or profile, but it uses or is used by another role, user or profile as described in the message text. User Action: Revoke the dependency between the roles, users and profiles specified and then drop this object.
15.724 – PRFMISMATCH
external identifier for "<str>" does not match current profile id for "<str>" Explanation: The user or role is identified externally. Therefore, the external identifier for the new name must match the current profile id. This is not true, in this case. User Action: Only rename externally identified users and roles, when the external name has changed.
15.725 – PRFNEXISTS
a <str> does not exist with the name "<str>" Explanation: The specified role, user or profile does not exist in the database. User Action: Respecify the name using a known profile name.
15.726 – PRFNOTDEF
<str> "<str>" has not been defined Explanation: The specified role, user or profile does not exist in the database. User Action: Respecify the name using a known profile name.
15.727 – PRI_RELCONEXTS
cannot define multiple PRIMARY KEY constraints for a relation Explanation: An attempt has been made to define a second PRIMARY KEY constraint for a relation. Only one is allowed. User Action: First, review the database design and defined relation-specific constraints; then, if desired, try the operation again specifying a constraint of a different type.
15.728 – PRTNOTCOMPLETE
partition <str> still in build pending state Explanation: An ALTER INDEX ... MAINTENANCE IS ENABLED statement failed because one or more index partitions are still in build-pending state. User Action: Use the ALTER INDEX ... BUILD PARTITION, or ALTER INDEX ... BUILD ALL PARTITIONS statement before using this statement.
15.729 – 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.
15.730 – QRYINVALID
some queries have been marked invalid by metadata change Explanation: These are informational messages reported to the user when DROP TABLE or some other operation makes queries invalid. User Action: No user action is required, but database administrators should note that this metadata operation may cause queries to fail.
15.731 – 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.
15.732 – QUIETPTREL
released database quiet point at <time> Explanation: The database quiet point lock has been released. User Action: None.
15.733 – RCHLENEXC
row length or node size exceeds size of row cache - check cache attributes Explanation: This is an informational message that is reported when CREATE TABLE, CREATE INDEX, ALTER TABLE or ALTER DOMAIN cause a tables row size or index node to exceed that defined by the logical area row cache of the same name. User Action: The longer rows will no longer fit in the cache and therefore the row cache might not be effective. The database administrator may need to adjust the row cache definition to compensate for this change. Please note that row compression might allow some or all of the longer rows to fit within the row cache.
15.734 – 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.
15.735 – 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".
15.736 – 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.
15.737 – READONLY
data in a read-only storage area may not be accessed for update Explanation: Your transaction attempted to access data in a read-only storage area for update. User Action: Explicitly specify the correct access mode for the data, or change the read-only area to a read/write area.
15.738 – READONLYVAR
variable (<num>) has been marked as CONSTANT and may not be updated Explanation: An attempt was made to assign a value to a CONSTANT, i.e. not updatable variable. User Action: Correct the routine so that this variable is not marked as CONSTANT or is not updated.
15.739 – 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.
15.740 – 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.
15.741 – 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.
15.742 – 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.
15.743 – RECMAXEXC
relation <str> definition exceeds data limit Explanation: You attempted to define or change a relation that is too large. User Action: Modify the relation definition.
15.744 – 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.
15.745 – REFINGFLDMSMTCH
a FOREIGN KEY referencing field does not correspond to a referenced field Explanation: The referencing fields of the FOREIGN KEY REFERENCES relation-specific constraint being defined do not correspond to the referenced fields of the referenced relation in either number or type (datatype, length, and scale). User Action: Choose referencing fields for the FOREIGN KEY which correspond to the referenced fields of the UNIQUE or PRIMARY KEY of the referenced relation.
15.746 – RELALRDYMP
there already exists a map for relation <str> Explanation: You tried to define a storage map for a relation that already has a storage map defined for it. User Action: Use CHANGE STORAGE MAP if you want to change the storage map for that relation.
15.747 – RELCONEXTS
there is another Relation constraint named <str> in this database Explanation: The relation-specific constraint specified already exists. User Action: Choose another relation-specific constraint name.
15.748 – RELCONNOEXI
table constraint <str> does not exist for the specified table Explanation: The specified table constraint does not exist for the table referenced in the ALTER TABLE or CHANGE RELATION statement. User Action: Check the name of the constraint and the name of the table using the SHOW statement.
15.749 – RELEXI
field <str> is used in relation <str> Explanation: The specified field you attempted to delete is used in a relation. User Action: You should first change the relation to exclude this field, and then delete the field.
15.750 – RELEXTS
there is another relation named <str> in this database Explanation: The relation name you tried to define already exists. If the named table is a temporary table then it may be that a previous drop statement for a temporary table of the same name needs to be committed or rolled back. User Action: Use another relation name. Or in the case of a temporary table the user may need to commit or rollback a previous drop statement.
15.751 – RELFLDEX
there is another field named <str> in relation <str> Explanation: The field name you want to define already exists in this relation. User Action: Choose another name for the field.
15.752 – RELFLDNOC
field <str> in relation <str> has not been changed Explanation: The field named was not changed. User Action: Correct the problem and then change the field.
15.753 – RELFLDNOD
field <str> has not been deleted from relation <str> Explanation: The field named was not deleted. User Action: Correct the problem and then delete the field.
15.754 – RELINCOM
relation <str> is referenced in COMPUTED BY field <str> in relation <str> Explanation: You attempted to delete a field from a relation, but the field is used in a COMPUTED BY field in another relation. User Action: First, review the database design; then, if desired, delete the COMPUTED BY field, and then delete the field from the relation.
15.755 – RELMODEXI
relation "<str>" referenced in the default transaction for module "<str>" Explanation: An attempt was made to perform DROP TABLE on a table referenced by the RESERVING clause in the default transaction for a module. User Action: First, review the database design; then, if desired, drop the module, and then delete the relation. Use the CASCADE option to avoid this error and leave the module intact. Note that attempts to use the module without re-creating the table will fail.
15.756 – RELNEXTS
relation <str> does not exist in this database Explanation: The relation name you tried to use does not exist. User Action: Use another relation name.
15.757 – RELNOEXI
relation <str> does not exist in this database Explanation: The table or view that was referenced was not found. User Action: Check the name of the relation using the SHOW command.
15.758 – RELNOTCHG
relation <str> has not been changed Explanation: The specified relation was not changed. User Action: Correct the problem and retry the metadata update.
15.759 – RELNOTDEL
relation <str> has not been deleted Explanation: The specified relation was not deleted. User Action: Correct the problem and retry the metadata update.
15.760 – RELNOTEMPTY
table "<str>" has data in it Explanation: You attempted to create or drop a storage map for a table that contains data, and that operation is not allowed. User Action: If this error was reported for DROP then you should drop the table to delete the data. If this error was reported from CREATE then check that the map being defined is a simple map (see secondary message).
15.761 – RELNOTTRUNC
relation "<str>" has not been truncated Explanation: The specified relation was not truncated. User Action: Correct the problem and retry the TRUNCATE statement.
15.762 – RELUSETRA
relation <str> is used in a transferred definition Explanation: The specified field is used in the specified relation. The relation is involved in a DDAL transfer definition. User Action: You must delete the DDAL transfer definition before modifying the field.
15.763 – REL_RTNEXI
relation "<str>" is referenced in routine "<str>" Explanation: You attempted to delete a relation, but the relation is used in a routine. User Action: First, review the database design; then, if desired, delete the routine and then delete the relation.
15.764 – 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.
15.765 – REQPBLCANSI
identifier for [*,*] required in ANSI ACL Explanation: Databases defined as ANSI compliant are restricted to always having an identifier [*,*] even if this identifier is not allowed any access to the entity. User Action: Enter a protection command changing the [*,*] protection to none rather than deleting the entry in the ACL.
15.766 – REQUNIFORM
storage area RDB$SYSTEM must contain uniform format pages Explanation: You attempted to assign PAGE FORMAT IS MIXED to RDB$SYSTEM storage area. User Action:
15.767 – 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.
15.768 – RLCREFDBYRLC
relation constraint <str> is referenced by relation <str> constraint <str> Explanation: The UNIQUE or PRIMARY KEY relation-specific constraint that you tried to delete with the DELETE RELATION or CHANGE RELATION statement cannot be deleted. You cannot delete the UNIQUE or PRIMARY KEY relation-specific constraint because it is referenced by one or more FOREIGN KEY REFERENCES relation-specific constraints from one or more relation or relations. User Action: First, review the database design; then, if desired, delete the FOREIGN KEY REFERENCES relation-specific constraint (or constraints) and try the operation again.
15.769 – ROLENOTIDENT
some roles are NOT IDENTIFIED; security checking cannot be set to external Explanation: In order to alter a database and set security checking to external, no roles existing in the database can be defined as NOT IDENTIFIED. User Action: Redefine or drop the roles before altering the database security checking to external or do not alter the database security checking.
15.770 – 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.
15.771 – 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.
15.772 – ROOT_CORRUPT
database has been corrupted and must be restored from backup
Explanation: The database has been corrupted and must be
restored from a full database backup.
User Action: Restore the database from the latest full database
backup, apply any incremental backups that might exist, and
roll-forward ("recover") the corresponding after-image journal.
15.773 – 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.
15.774 – RTAIJMSMTCH
AIJ references root file "<str>" - expected "<str>"
15.775 – RTNEXI
field "<str>" is used in routine "<str>" Explanation: The specified field you attempted to delete is used in a routine. User Action: You should first change the routine to exclude this field, and then delete the field.
15.776 – RTNEXTS
there is another routine named <str> in this database Explanation: The routine name you tried to define already exists. User Action: Specify another routine name.
15.777 – RTNIDNEXTS
routine ID, <num>, does not exist in this database Explanation: The specified routine ID does not exist in the current database. Perhaps you specified a term or keyword where a routine ID was expected. User Action: Invoke the correct database. Specify the correct routine ID.
15.778 – RTNIMAGEERR
error activating routine image "<str>" Explanation: The image has not been built correctly. User Action: Check the corresponding external routine source file and rebuild the image correctly.
15.779 – RTNIMAGE_UNINSTALLED
routine image not installed Explanation: The external routine image specified by the primary error message can not be activated at the execution site because the main image is installed execute only or privileged and the external routine image is not installed. User Action: Install the specified external routine image.
15.780 – RTNINCOM
routine "<str>" is referenced in COMPUTED BY field <str> in relation <str> Explanation: An attempted was made to delete a routine but the routine is used in a COMPUTED BY field of a relation. User Action: First, review the database design; then, if desired, delete the COMPUTED BY field, and then delete the routine.
15.781 – RTNINCON
routine "<str>" is referenced in constraint "<str>" Explanation: Before you can delete a routine, all constraints, triggers, and views based on this relation must be deleted. User Action: Delete the dependent constraints, triggers, and views that refer to this routine.
15.782 – RTNINTRG
routine "<str>" is referenced in trigger "<str>" Explanation: Before you can delete a routine, all constraints, triggers, and views based on this routine must be deleted. User Action: Delete the dependent constraints, triggers, and views that refer to this routine.
15.783 – RTNINVW
routine "<str>" is referenced in view "<str>" Explanation: Before you can delete a routine, all view, constraints, and triggers based on this routine must be deleted. User Action: Delete the dependent views, constraints, and triggers that refer to this routine.
15.784 – RTNNEXTS
routine <str> does not exist in this database Explanation: The routine name you tried to use does not exist. User Action: Use another routine name.
15.785 – RTNNOTCHG
routine "<str>" has not been changed Explanation: The specified routine was not been altered or renamed. User Action: Correct the problem and try the metadata update again.
15.786 – RTNNOTDEF
routine <str> is not defined in database Explanation: The specified routine does not exist in the current database. User Action: Invoke the correct database. Make sure you spell the routine name correctly. Perhaps you specified a term or keyword where the parser expected a routine name.
15.787 – RTNNOTDEL
routine "<str>" has not been deleted Explanation: The specified routine was not deleted. User Action: Correct the problem and try the metadata update again.
15.788 – RTNNOTSAME
routine "<str>" is not compatible with forward declaration Explanation: A DECLARE FUNCTION or DECLARE PROCEDURE was used to declare a forward reference for this routine, but this routine uses different parameter data types, passing mechanisms, number of parameters, default parameter value, or function return type. User Action: Correct the CREATE statement and try again.
15.789 – RTNSBC_INITERR
Cannot init. external routine server site executor; reason <num> Explanation: The attempt to create and initialize a server site client external routine executor has failed. This is usually an indication of a lack of privileges or quotas, a lack of system resources, or the inability to establish the necessary client environment. The reason value represents a more specific indication of the failure. User Action: For reasons 1 thru 9, check for sufficient quotas. For reasons 10 thru 19, increase the value for environment variable RDMS$RTX_SHRMEM_PAGE_CNT as required. For reasons 20 thru 29, make sure the proper images have been installed. For all other reasons, contact your Oracle support representative for assistance. You will need to provide a script allowing reproduction of the problem.
15.790 – RTNSBC_TASKERR
Cannot use external routine server site executor; reason <num> Explanation: An attempt to perform an external routine task using the server site client executor failed. This usually is an indication that either the executor process has terminated, or there is insufficient shared memory for either a routine callout or a RCI callback from a routine. The reason value represents a more specific indication of the failure. User Action: For reasons 1 thru 9, check for sufficient quotas. For reasons 10 thru 19, increase the value for environment variable RDMS$RTX_SHRMEM_PAGE_CNT as required. For reasons 20 thru 29, make sure the proper images have been installed. For all other reasons, contact your Oracle support representative for assistance. You will need to provide a script allowing reproduction of the problem.
15.791 – RTNUSENOTALL
routine "<str>" can not be used, too many privileges available Explanation: The specified external routine can not be used because the the execution site environment has more available privileges than the user is authorized to use. User Action: Retry the operation or query in a less privileged environment such as defining the external routine as BIND ON SERVER. If possible the shareable image should be installed with the OpenVMS INSTALL ADD/SHARE command to make it a known (and therefore) trusted shareable image.
15.792 – RTN_DEACTERR
routine "<str>" image "<str>" can not be deactivated Explanation: The specified external routine can not be deactivated. This is generally an indication of a system related problem. User Action: Review the secondary error message or messages, and take appropriate action.
15.793 – RTN_ERROR
routine "<str>" generated an error during execution Explanation: Execution of the specified external routine caused an exception to be generated. User Action: Review the secondary error message or messages, and rework the external routine code to avoid this error.
15.794 – RTN_INVALID
routine can not be invoked - it is marked invalid Explanation: This routine can not be invoked. It has been marked invalid as a result of a data definition language operation on an object upon which this routine was dependent (with language semantics dependency). User Action: Revalidate the procedure by recompiling the procedure. This may require that you drop and re-create the routine or module.
15.795 – RTN_LANGSEMEXI
table used by routine with language dependency - routine invalid on COMMIT Explanation: There are one or more routines that depend upon this object with a language semantics dependency. Those routines will be marked invalid and need to be recompiled through the language interface before reuse. i.e. the module will need to be extracted and re-created before this routine can be used. User Action: Review your database design, and understand the implications of this data definition language operation. Roll back the transaction if you do not want the routines to be marked invalid.
15.796 – RTN_NOMETA
metadata may not be created/altered from within an external routine Explanation: You attempted a metadata operation from within an external routine. User Action: Do not attempt such an operation.
15.797 – RTN_NOTIFYERR
routine "<str>" generated an error during "<str>" notification Explanation: Execution of the specified external routine notification code for the specified notification action caused an exception to be generated. User Action: Review the secondary error message or messages, and rework the external routine code to avoid the error.
15.798 – RTN_RTNEXI
routine "<str>" is referenced in module "<str>" by routine "<str>" Explanation: You attempted to delete a routine, but the routine is used in another routine. User Action: First, review the database design; then, if desired, delete the routine that uses this one, and then delete this routine.
15.799 – RUJDEVDIR
RUJ filename "<str>" does not include a device/directory Explanation: The RUJ filename you specified did not include a device and directory. User Action: For maximum protection, you should always include a device and directory in the file specification, preferably one that is different from the database device.
15.800 – 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.
15.801 – 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.
15.802 – 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.
15.803 – SCHEMAEXISTS
schema <str> already exists in this catalog <str> Explanation: The named schema already exists. User Action: Use a different name for the schema.
15.804 – SCHEMAINUSE
schema <str> currently in use Explanation: You attempted to drop a schema which still contains database object (such as, domains, tables, indices, etc). User Action: Drop all the objects from the schema before attempting to drop the schema.
15.805 – SCHNOTFOUND
schema with id <num> not found in this database Explanation: The schema id referenced by the ALTER statement does not exist. User Action: Please select another schema.
15.806 – 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.
15.807 – SCROLLDISABLED
SCROLL is disabled for chained style lists (segmented strings) Explanation: The logical name RDMS$DIAG_FLAGS is defined as "L" which disables the SCROLL emulation for chained style segmented strings. User Action: This logical name is used to determine if any columns are still using chained segmented strings.
15.808 – SECNOTINT
database security checking is not internal Explanation: The database is defined as SECURITY CHECKING IS EXTERNAL. Therefore, users and roles cannot be created. User Action: Users and roles can only be defined in databases where security checking is internal.
15.809 – SEGALRDYMP
a map for segmented strings already exists Explanation: You tried to define a storage map for a relation that already has a storage map defined for it. User Action: Use the CHANGE STORAGE MAP statement if you want to change the storage map for segmented strings or lists.
15.810 – SEGMAPONWORM
only segmented strings may be stored in a WRITE_ONCE area Explanation: You tried to define a storage map that would allow something other than a segmented string to be stored in a WRITE_ONCE area. User Action: You must define the storage map on an area that is not WRITE_ONCE.
15.811 – SEGSTR_AREA_INC
segmented string was stored incorrectly Explanation: The database has a storage map for segmented strings. The database has stored part of the segmented string in the incorrect area. User Action: Currently this is only expected to happen when the RDML or RDBPRE pre-compilers are in use and the logical name RDMS$BIND_SEGMENTED_STRING_BUFFER has not been specified to a large enough value to permit buffering of the entire segmented string.
15.812 – SEGSTR_NO_CHG
you cannot change a field's datatype to or from a segmented string Explanation: Non-segmented string fields cannot be changed to or from segmented string fields. User Action: Define a new field with the desired data type and use a program to properly load/unload the segmented string.
15.813 – SEGTOOBIG
segmented string segment exceeds maximum allowed size Explanation: A segmented string segment has been specified that is larger than the maximum size allowed. Segment size is maintained in a word, which allows 65,535 unsigned bytes of data. The initial (first) segment stored requires 27 bytes of overhead, leaving 65,508 bytes for the user's data. All subsequent segments require only 13 bytes of overhead, leaving 65,522 bytes for the user's data. User Action: Specify a segment size that meets the above criteria for user data.
15.814 – SEQEXTS
there is another sequence named "<str>" in this database Explanation: The name used for the sequence already exits for another created sequence, or table(relation) in this database. The name of any new sequence must be unique and not match an existing sequence or table name. Use another sequence name.
15.815 – 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.
15.816 – SEQNEXTS
sequence "<str>" does not exist in this database Explanation: The sequence that you attempted to modify or delete was not found. User Action: Check the name of the sequence using the SHOW command and try again to modify it or delete it.
15.817 – SEQNOTCHG
sequence "<str>" has not been changed Explanation: The specified sequence was not changed. User Action: Correct the problem and retry the metadata update.
15.818 – SEQNOTDEF
sequence "<str>" is not defined in database Explanation: The specified sequence does not exist in the current database. User Action: Invoke the correct database. Spell the sequence name correctly. Perhaps you specified a term or keyword where the parser expected a sequence name.
15.819 – SEQNOTDEL
sequence "<str>" has not been deleted Explanation: The specified sequence was not deleted. User Action: Correct the problem and try the metadata update again.
15.820 – 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.
15.821 – 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.
15.822 – SIGNATURE_MISMATCH
invalid parameter signature on procedure call Explanation: (DSRI Users) The unique identifier generated for the procedures message BLR string does not match what is stored in the database. (SQL users) The user interface to the database object being called by the application has changed, or the created routine is different from the previously declared forward reference. User Action: Ensure that the routine parameters are identical in number, order, type and passing mechanism to those currently defined in the database, or declared for the session.
15.823 – 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.
15.824 – 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.
15.825 – SNPDISCJ
snapshots must be disabled or enabled deferred with commit to journal optimization Explanation: Within the ALTER DATABASE statement, the user tried to turn on commit to journal while snapshots were enabled. User Action: Disable snapshots before turning on commit to journal.
15.826 – SORTKEYEXT
sort key is external to RSE context Explanation: A sort key refers to record stream contexts that are totally external to the Record Selection Expression that contains the sort clause. This type of sort key provides an invariant value to the sort, making the sort more costly for no useful purpose, and may indicate an improperly positioned sort clause. User Action: Define the sort key or keys again, or reposition the sort clause to a more external RSE.
15.827 – SORTMEMFAIL
memory allocation for Hypersort failed. Use SORT_MEM_MAX Explanation: Hypersort bases its large VM request on WS_EXTENT. If this results in a problem ... User Action: Define the logical SORT_MEM_MAX which will limit the memory request.
15.828 – 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.
15.829 – 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.
15.830 – 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.
15.831 – SPAMNOTWRM
cannot enable SPAMs for WORM area <str> Explanation: WORM areas cannot have SPAMs enabled. User Action: Do not enable SPAMs for WORM areas.
15.832 – SPIMAX
SPAM interval of <num> is more than the Oracle Rdb maximum of <num> Explanation: The SPAM interval you specified is too large. User Action: Choose a smaller interval.
15.833 – SPIMIN
SPAM interval of <num> is less than the Oracle Rdb minimum of <num> Explanation: The SPAM interval you specified is too small. User Action: Choose a larger interval.
15.834 – SQLSTATE_ILLCH
illegal character in SQLSTATE string passed to SIGNAL routine Explanation: The value expression which was passed to the SIGNAL routine contained illegal characters. The only permitted characters are '0' through '9' and 'A' through 'Z'. This is specified as part of the ANSI and International SQL standard. User Action: Correct the application so that only legal characters are passed to the SIGNAL routine.
15.835 – SQLSTATE_NULL
unexpected NULL passed to SIGNAL routine Explanation: The value expression which was passed to the SIGNAL routine was NULL. This is not permitted. User Action: Correct the application so that NULL is not passed to the SIGNAL routine. For instance use COALESCE (:mysqlstate, '22023'). SQL92 defines 22023 as "data exception - invalid parameter value".
15.836 – 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.
15.837 – SSAREANOTEMPTY
segmented string area <str> is not empty, it may not be deleted Explanation: You tried to change the storage map for segmented strings and delete an area, but there are segments in the area. User Action: You must determine what relations use the data that is in the area and then determine what you want to do about it before issuing the CHANGE STORAGE MAP statement again.
15.838 – 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.
15.839 – 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.
15.840 – STAREAFUL
storage area <str> is full Explanation: You attempted to store a record in the database, but the storage area in which the record would go is full. This condition can be caused by the storage area being set to disallow being extended or when the ABM pages are at their limit and cannot map a new extension for the storage area. User Action: Modify the storage area extend parameter to allow storage area extension if it is disabled, or increase the page size or redistribute objects across other storage areas to free up existing space.
15.841 – 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.
15.842 – STATNODEUNKN
node is not actively collecting statistics Explanation: A node was specified that is NOT actively collecting statistics for this SHOW STATISTIC utility session. User Action: Make sure the node name is spelled correctly and has been properly identified.
15.843 – 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".
15.844 – 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.
15.845 – STOMAPNOEXI
storage map "<str>" does not exist in this database Explanation: The storage map you attempted to drop or alter was not found. User Action: Check the name of the storage map using the SHOW command and try again to alter or drop the storage map.
15.846 – STTREMCNCT
error allocating remote statistics network connection Explanation: None.
15.847 – STTSVRFIND
error identifying remote statistics server Explanation: None.
15.848 – 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.
15.849 – SYMTOOBIG
symbol <str> is longer than the maximum 31 characters Explanation: The maximum size for a symbol name is 31 characters. You attempted to use a symbol longer than 31 characters. User Action: Use a shorter symbol.
15.850 – SYNEXTS
there is already a synonym named "<str>" in this database Explanation: The name used in the CREATE statement was already in use by a synonym. The name of a table, domain, module, function, sequence, type, or procedure may not duplicate the name of a synonym. User Action: Please choose a different name for this object.
15.851 – SYNNOTDEL
synonym "<str>" has not been deleted Explanation: The synonym in question has not been deleted for the reason explained by the previous message. User Action: Correct the problem and retry the statement.
15.852 – 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.
15.853 – SYSTEMROLE
"<str>" is a system role, operation is not allowed Explanation: A system role cannot be granted to or revoked from another role or user nor can any role be granted to or revoked from it. User Action: Only privileges can be granted to and revoked from system roles.
15.854 – TABCTXEXI
table context <num> already in use within this query Explanation: You have specified a table context number that is already in use within this query . User Action: Choose another table context number
15.855 – TABIDNOTDEF
relation ID, <num>, is not defined in database Explanation: The specified relation identification does not exist in the current database. User Action: Invoke the correct database. Specify the correct relation identification. Perhaps you specified a term or keyword where the parser expected a relation identification.
15.856 – TABLENOMAP
table "<str>" is not partitioned with a storage map Explanation: You attempted to supply a PARTITION clause for a table which is not partitioned. User Action: Do not list the PARTITION clause in the SET and DECLARE TRANSACTION statements for this table.
15.857 – 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.
15.858 – 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 assistance.
15.859 – TEXT
<str> Explanation: Additional information concerning an error. User Action: Review the primary error message or messages and take appropriate action
15.860 – TEXT_EXPECTED
text or variable text data expected Explanation: The external routine expected text or variable text data. User Action: Pass text or variable text data to the external routine.
15.861 – THRESHAREEXI
illegal thresholds usage - area <str> exists, and cannot have THRESHOLDS respecified Explanation: You cannot redefine thresholds on an existing area. User Action: Delete and recreate the area with the desired thresholds or create an area with the new thresholds and move the data from the old to the new area.
15.862 – THRESHUNIF
illegal thresholds usage - area <str> is MIXED format, must be UNIFORM Explanation: Thresholds in storage maps can only be applied to UNIFORM areas. User Action: Reference UNIFORM areas if you wish to use storage map thresholds. Otherwise, define MIXED areas thresholds using CREATE STORAGE AREA or DEFINE STORAGE AREA statements when creating or altering the database.
15.863 – TIMEOUT
timeout on <str> Explanation: A lock request has been canceled by the database management system because the request could not be granted within the user-specified timeout period. User Action: Execute a ROLLBACK or a COMMIT to release your locks, and try the transaction again.
15.864 – TRANSFDEF
there is another transfer named <str> for this database Explanation: DDAL tried to store information in the source database for the transfer name given, and discovered that the transfer name was already stored. User Action: Delete this replication transfer, and pick a new transfer name.
15.865 – 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.
15.866 – TRGEXI
relation <str> is referenced in trigger <str> Explanation: Before you can delete a relation, all constraints, triggers, and views based on this relation must be deleted. User Action: Delete the dependent constraints, triggers, and views that refer to this relation.
15.867 – TRGEXTS
there is another trigger named <str> in this database Explanation: The trigger name you tried to define already exists. User Action: Choose another trigger name.
15.868 – TRGINUPDREQ
there are active update requests that reference trigger <str> Explanation: You tried to delete the specified trigger while there are one or more active update requests that reference the trigger. The specified trigger was not deleted. User Action: Allow the update request or requests to finish, and try the trigger deletion again.
15.869 – TRGNOEXI
trigger <str> does not exist Explanation: The name specified for the trigger was not found in the database or the trigger named does not reference table named. User Action: Check the name of the trigger using the SHOW TRIGGERS statement and try the operation again. Check to make sure the trigger is defined on the referenced table.
15.870 – TRGNOSUBJCTX
trigger may not reference the subject relation context Explanation: A BEFORE STORE or AFTER ERASE trigger or a trigger action that does not specify FOR EACH ROW contains an illegal reference to the subject relation current or NEW/OLD context (row values or dbkey). User Action: Define the trigger to use only the relation contexts declared within the trigger actions.
15.871 – TRGVW
views cannot be used within a trigger Explanation: You cannot define a trigger on a view and must not reference views in the triggered condition or actions. User Action: Define the trigger to use the relation referred to in the view definition.
15.872 – TRG_INVALID
trigger can not be invoked - it is marked invalid Explanation: This trigger can not be invoked. It has been marked invalid as a result of a data definition language operation on an object upon which this trigger was dependent (with language semantics dependency). User Action: The trigger must be dropped and redefined so that it inherits the updated schema.
15.873 – TRG_LANGSEMEXI
table used by trigger with language dependency - trigger invalid on COMMIT Explanation: There are one or more triggers that depend upon this object with a language semantics dependency. Those triggers will be marked invalid and need to be recompiled through the language interface before reuse. User Action: Review your database design, and understand the implications of this data definition language operation. Roll back the transaction if you do not want the trigger to be marked invalid.
15.874 – TRIGNODEL
trigger <str> cannot delete record being modified or stored Explanation: The trigger specified (possibly invoked by another trigger) attempted to delete a record that was currently being stored or modified (by either a user request or a trigger action). User Action: First, review the database design and defined triggers. Then, define one or more of the triggers again to eliminate the possibility of deleting a record that is being modified or stored.
15.875 – TRIG_ERROR
trigger <str> forced an error Explanation: The specified trigger executed an action defined to produce this exception. User Action: This may be an expected occurrence in some situations, but in general determine the conditions that led to the update that caused the triggered error, eliminate those conditions (it may be necessary to discuss a solution with your database manager), and try the operation again.
15.876 – 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.
15.877 – TRNNOTDEF
transfer <str> has not been defined Explanation: The specified transfer was not defined. User Action: Correct the problem and try the metadata update again.
15.878 – TRNNOTDEL
transfer <str> has not been deleted Explanation: The specified transfer was not deleted. User Action: Correct the problem and try the metadata update again.
15.879 – TRUE
condition value is true Explanation: None.
15.880 – 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.
15.881 – TRUNRGTSTR
truncation of right-hand side string for assignment has occurred Explanation: You executed a STORE or MODIFY statement, and the string on the right-hand side of the equation is longer than the string on the left. User Action: The length of the right hand side must fit in the location where the value is being stored. Specify a string which fits into the target location.
15.882 – 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.
15.883 – UNDERFLOW
data conversion underflow Explanation: You attempted an operation that would cause loss of information on a data-item movement. User Action: Correct the error and try again.
15.884 – UNI_RELCONNOEXI
unique Relation constraint <str> does not exist in this database Explanation: The relation-specific constraint specified either was not found in the database or does not reference a UNIQUE or PRIMARY KEY constraint. This relation-specific constraint is referenced by the definition of a FOREIGN KEY REFERENCES relation-specific constraint and must represent either a UNIQUE or PRIMARY KEY for the referenced relation and any referenced fields. User Action: Contact your Oracle support representative for assistance.
15.885 – UNKAMBFLAG
'<str>' is an unknown or ambiguous flag name Explanation: The specified flag name was not recognized as a known debug or diagnostic flag. User Action: Change the unrecognized flag name to a known one and try the operation again.
15.886 – UNKNOWN_VAR
unknown variable <num> found in the query string Explanation: The variable number used by the query has not been declared. User Action: Correct the application to declare the variable first, or use the correct variable number in the expression.
15.887 – 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.
15.888 – 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.
15.889 – 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.
15.890 – 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.
15.891 – 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.
15.892 – 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.
15.893 – UNLIKECOLL
fields of unlike collating sequence may not be compared Explanation: Oracle Rdb does not permit comparisons among fields with unlike collating sequences. User Action: Specify fields with the same collating sequence.
15.894 – UNRES_AREA
area <num> within relation "<str>" is not reserved
15.895 – UNRES_AREAX
area <num> within index "<str>" is not reserved Explanation: Your program began a transaction by reserving a list of relations and specifying particular access modes for certain partitions. The referenced partition was not included in the list. User Action: Examine and correct the SET TRANSACTION statement. These errors may occur when applications or RMU/LOAD if some constraints are being evaluated which require access to partitions not reserved by the transaction.
15.896 – 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.
15.897 – UNSCATALOG
catalogs can not be created, altered or dropped Explanation: You must have multischema support enabled to create, alter, and drop catalogs. User Action: See action for primary message.
15.898 – UNSCOMP
unsupported data comparison Explanation: You attempted an operation that would compare two incommensurate data items. User Action: Correct the error and try again.
15.899 – UNSCONV
unsupported data conversion Explanation: You attempted an operation that would cause loss of information on a data-item movement. User Action: Correct the error and try again.
15.900 – UNSSCHEMA
schemas can not be created, altered or dropped Explanation: You must have multischema support enabled to create, alter, and drop schemas. User Action: See action for primary message.
15.901 – UNSSYNONYM
this database does not have synonyms enabled Explanation: Synonyms can not be created, altered or dropped because this database does not support the SYNONYMS functionality. User Action: Use ALTER DATABASE and specify the clause SYNONYMS ARE ENABLED so that the appropriate system tables and support are enabled, then retry this command.
15.902 – UNS_DTYPE
unsupported datatype Explanation: Oracle Rdb does not support this data type. User Action: Refer to documentation for information on data types and host language data type conversion.
15.903 – 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.
15.904 – UPDRECURSTRIG
update would cause recursive execution of trigger <str> Explanation: The trigger specified and possibly a series of other triggers have been defined such that execution of the update operation which invokes the specified trigger will cause that trigger to be recursively invoked. User Action: First, review the database design and defined triggers; then, redefine one or more of the triggers to eliminate the possibility of recursive invocation.
15.905 – USENEXTVAL
reference sequence using NEXTVAL before using CURRVAL Explanation: The sequence must first be referenced using pseudocolumn NEXTVAL before referencing the sequence using pseudocolumn CURRVAL. User Action: Reference the sequence using pseudocolumn NEXTVAL.
15.906 – 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.
15.907 – USRMAX
<num> number of users is greater than the Oracle Rdb maximum of <num> Explanation: The number of users for the database you specified is too large. User Action: Refer to documentation and try another value.
15.908 – USRMIN
<num> number of users is less than the Oracle Rdb minimum of <num> Explanation: The number of users for the database you specified is too small. User Action: Refer to documentation and supply another value.
15.909 – VCO_NOFIRSTN
CHECK OPTION is not allowed for view "<str>" with row limit Explanation: The CHECK OPTION on a view requires that neither that view nor any view nested in it has FIRST n (RDO) or LIMIT TO n ROWS (SQL) clause. Remove either CHECK OPTION or LIMIT TO n ROWS clause from the view.
15.910 – VCO_READ_ONLY
WITH CHECK OPTION can not be used with read-only view "<str>" Explanation: This view is read-only. This occurs when a UNION, EXCEPT, MINUS, INTERSECT GROUP BY, DISTINCT, or statistical function appears in the outer most query. User Action: You can not apply a WITH CHECK OPTION clause to this view. Remove the clause.
15.911 – VIEWEXI
relation <str> is referenced by view <str> Explanation: Before deleting a relation, all constraints and views based on this relation must be deleted. User Action: Delete the dependent views and any constraints that refer to the relation, then delete the relation.
15.912 – VIEWINVIEW
view <str> is referenced by view <str> Explanation: A view cannot be deleted if another view depends upon it. User Action: Delete the dependent view first.
15.913 – VIEWMODEXI
view "<str>" specified in default transaction for the module "<str>" Explanation: An attempt was made to perform the delete operation on a view. The view is specified with the RESERVING clause in the default transaction characteristics for the module. User Action: First, review the database design; then, if desired, delete the module, and then delete the view.
15.914 – VIEWNOEXI
view <str> does not exist in this database Explanation: The view you attempted to delete was not found. User Action: Check the name of the view using the SHOW command and try again to delete it.
15.915 – VIEWNORET
view cannot be retrieved by database key Explanation: A view defined with a Record Selection Expression that references AGGREGATE or MERGE streams cannot be retrieved via database key. User Action: Retrieve the relations to which the view refers.
15.916 – VIEWNOTDEL
view <str> has not been deleted Explanation: The specified view was not deleted. User Action: Correct the problem and retry the metadata update.
15.917 – VIEWNOTTRUNC
view "<str>" has not been truncated Explanation: The specified view was not truncated. Views cannot be truncated. User Action: A view may be dropped but a view cannot be truncated. If the view is dropped the metadata will be removed. Retry the TRUNCATE statement specifying a table name.
15.918 – VIEWNOUP
view cannot be updated Explanation: A view containing a CROSS, REDUCE TO, or FIRST clause cannot be updated. User Action: Update the relations to which the view refers.
15.919 – VIEW_NO_ANA
views cannot be analyzed Explanation: You attempted to analyze a view. User Action: Use a relation name.
15.920 – VIEW_RTNEXI
view "<str>" is referenced in routine "<str>" Explanation: You attempted to delete a view, but the view is used in a routine. User Action: First, review the database design; then, if desired, delete the routine and then delete the view.
15.921 – VRPINVALID
invalid operation for storage map "<str>" Explanation: The storage map you attempted alter is a vertically partitioned map which currently may not be altered in this release of Rdb. User Action: To change the characteristic for a vertically partitioned map you will need to unload the data, delete the data (or drop the table) and redefine the physical characteristics.
15.922 – 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.
15.923 – WISH_LIST
feature not implemented yet Explanation: The action you requested requires a feature that is not implemented in the current version of this product. User Action: Try a simpler way of doing things.
15.924 – WRMCANTREAD
error reading WORM pages <num>:<num>-<num> Explanation: An error occurred when you attempted to read one or more WORM pages. The message indicates the storage area ID number and the page numbers of the first and last pages being read. User Action: Examine the associated messages to determine the reason for failure. One possible cause for this error is disabling logging for the WORM area and subsequently restoring that area from an earlier backup.
15.925 – 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.
15.926 – 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.
15.927 – 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.
15.928 – WRNDATALOSS
ALTER TABLE ... ALTER COLUMN caused column data to be discarded Explanation: When ALTER TABLE ... ALTER COLUMN converts a column to a COMPUTED BY column the old column data is no longer accessible. User Action: This is just a warning, if this action was not desired then use ROLLBACK to undo the effect of the ALTER TABLE statement.
15.929 – WRNG_REL
attempt to retrieve <str> with DBKEY from another relation Explanation: You attempted to retrieve a relation using a database key value, but the database key was from another relation. User Action: Supply the key value from the correct relation.
15.930 – 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.
15.931 – XPR_STACK_OFLO
expression forces too many levels of recursion Explanation: You provided an expression which forces too many levels of recursion. The expression should be rewritten to use parentheses and therefore cause fewer levels of recursion. User Action: Rewrite the expression.
15.932 – XPR_STACK_OVFL
expression forces too many levels of recursion/stack overflow Explanation: You provided an expression which forces too many levels of recursion, which resulted in stack overflow. User Action: The expression should be rewritten to use parentheses and therefore cause fewer levels of recursion. It may also be possible to increase the size of the stack.
16 – COSI_ERRORS
16.1 – ABKEYW
ambiguous qualifier or keyword - supply more characters Explanation: Too few characters were used to truncate a keyword or qualifier name to make the keyword or qualifier name unique. User Action: Reenter the command. Specify at least four characters of the keyword or qualifier name.
16.2 – ABNEXIT
process has exited abnormally Explanation: The process that is being looked at has exited with some exit status. User Action: Check to see why the process exited.
16.3 – ABORT
abort Explanation: A database procedure has unexpectedly aborted or returned an error in an unexpected way. User Action: Retry the operation. If the error persists, contact your Oracle support representative for assistance.
16.4 – ABSENT
entity or value absent from command string Explanation: This message indicates that the entity value has not been specified in the command line. User Action: No action is required.
16.5 – ABSTIMREQ
absolute time required - delta time supplied Explanation: A delta time is passed to the routine when an absolute time is required. User Action: Contact your Oracle support representative for assistance.
16.6 – ABVERB
ambiguous command verb - supply more characters Explanation: Too few characters were used to truncate a command name to make the command name unique. User Action: Reenter the command. Specify at least four characters of the command name.
16.7 – ACCESS_ERR
an error was returned by the access function Explanation: An error was returned by the 'access' function. User Action: Please refer to the reference pages for 'access' to interpret the meaning of the errno returned by this function.
16.8 – ACCVIO
access violation Explanation: A readable parameter cannot be read, or a writeable parameter cannot be written. User Action: Pass the appropriate parameters.
16.9 – ACLEMPTY
access control list is empty Explanation: There are no access control entries in the access control list. User Action: Do not perform this command when the access control list is empty.
16.10 – AMBDATTIM
ambiguous date-time Explanation: The date-time input string did not match the specified input format. User Action: Correct the date-time input string and input format for date and time values.
16.11 – ARITH
arithmetic exception Explanation: An 'arithmetic exception' was raised as an exception in response to the arithmetic or software condition specified by the given code. Integer overflow, Integer divide by 0, Floating overflow, Floating divide by 0, Floating underflow, Floating invalid operation, and Floating inexact result are specific conditions producing this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.12 – AUTHNOTOWN
the authentication file is not owned by root Explanation: The authentication file has the wrong owner. User Action: Contact the system or database administrator to verify and/or correct the owner of the /usr/lib/dbs/sql/version /lib/cosi_authenticate program.
16.13 – AUTHWRONGPROT
the authentication file does not have the correct protection set Explanation: The authentication file has the wrong protection. User Action: Contact the system or database administrator to verify and/or correct the protection of the /usr/lib/dbs/sql/version /lib/cosi_authenticate program.
16.14 – BADAUTH
there is a problem with the authentication file Explanation: The authentication file does not exist, or it has the wrong owner or protection. User Action: Contact the system or database administrator to verify and/or correct the existence, owner, or protection of the /usr/lib/dbs/sql/version /lib/cosi_authenticate program.
16.15 – BADNODENAME
invalid remote node name specification for network Explanation: You specified a remote node name that contains a quoted string when using TCP/IP transport. User Action: Either check the remote node name for validity, and remove any quoted strings, or change the transport to use DECnet as the network transport.
16.16 – BADPARAM
bad parameter value Explanation: A value specified for a system function is not valid. User Action: This error message indicates a possible error in the use of operating system services by the database system. Contact your Oracle support representative for assistance.
16.17 – BADVMSVER
operating system version is not supported Explanation: The current version of Operating System is higher than the version supported by Oracle Rdb. User Action: Contact your Customer service center. There may be a future version of Oracle Rdb that supports your Operating System version.
16.18 – BAD_CODE
corruption in the query string Explanation: An illegal entry was found in the query string. User Action: If you called Rdb, check the query string. Otherwise, contact your Oracle support representative for assistance.
16.19 – BAD_KEY
invalid key specification Explanation: The key field size, position, data type, or order is incorrect within the key definition. Positions start at 1 and cannot be greater than the maximum record size. Record size must be less than or equal to 32,767 for character data; 1, 2, 4, 8, or 16 for binary data; and less than or equal to 31 for decimal. User Action: Check the command string key specifiers.
16.20 – BAD_LRL
record length (<num>) greater than specified longest record length Explanation: While reading the input file, the sort code encountered a record longer than the specified LRL (longest record length specified in bytes). The record will be truncated to the LRL and sorted. User Action: Reexecute the sort command with a longer LRL.
16.21 – BAD_MERGE
number of work files must be between 0 and 10 Explanation: The number of work files used was either less than 0 or greater than 10. User Action: Specify the correct number of work files, and retry the sort/merge operation.
16.22 – BAD_SRL
record length (<num>) is too short to contain keys Explanation: A record passed to sort/merge is too short to contain all the keys. The record is discarded, and processing continues. User Action: Check your input records and key specification.
16.23 – BAD_TYPE
invalid sort process specified Explanation: One of the following sort type codes was passed to the routine package: - Less than one or greater than four if file I/O - Not equal to one if record I/O - An invalid key word in command PROCESS Legal values are 1 through 4 for file I/O; 0 for record I/O; and RECORD, TAG, INDEX, or ADDRESS for the PROCESS command parameter. User Action: Specify a different sorting process.
16.24 – BUFFEROVF
output buffer overflow Explanation: The service completed successfully. The buffer length field in an item descriptor specified an insufficient value. The buffer was not large enough to hold the requested data. User Action: Provide a larger buffer, or perform another read request to access the remainder of the message.
16.25 – BUGCHECK
internal consistency failure Explanation: A fatal, unexpected error was detected by the database management system. User Action: Contact your Oracle support representative for assistance. You will need to include any bugcheck dump files.
16.26 – CANCEL
operation canceled Explanation: The lock conversion request has been canceled, and the lock has been granted at its previous lock mode. This condition value is returned under the following conditions: a lock request results in queueing a lock conversion request, the request has not been granted yet (it is in the conversion queue), and, in the interim, the unlock service is called to cancel this lock conversion. Note that if the waiting conversion request is granted BEFORE the unlock call can cancel the conversion, the unlock call returns CANCELGRANT, and the conversion request returns NORMAL. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.27 – CANCELGRANT
cannot cancel a granted lock Explanation: The service to unlock a lock was called to cancel a pending lock request; however, before the request to unlock could be completed, the lock was granted. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.28 – CANNOT_OPEN_LIB
cannot open help library Explanation: The help utility could not open the requested help library. User Action: Contact your Oracle support representative for assistance.
16.29 – CANTASSMBX
error assigning a channel to a mailbox Explanation: An error occurred during an attempt to assign a channel to a VMS mailbox. User Action: Examine the secondary messages to determine the reason for the failure.
16.30 – CANTCREMBX
cannot create mailbox Explanation: An error occurred during an attempt to create a mailbox. Mailboxes are used for interprocess communication by the database management system on VMS. User Action: Examine the secondary messages to determine the reason for the 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).
16.31 – CANTSPAWN
error creating sub-process Explanation: An error occurred during an attempt to spawn a sub-process. User Action: Examine the secondary messages to determine the reason for the failure.
16.32 – CAPTIVEACCT
captive account - can't create sub-process Explanation: An error occurred during an attempt to enter a SPAWN command from a captive account on VMS. User Action: Do not use the SPAWN command from a captive account.
16.33 – CHOWN_ERR
an error was returned by the chown function Explanation: An error was returned by the 'chown' function. User Action: Please refer to the reference pages for 'chown' to interpret the meaning of the errno returned by this function.
16.34 – CLOSEERR
cannot close file Explanation: An error occurred during an attempt to close the specified file. User Action: Examine the secondary messages to determine the reason for the failure.
16.35 – COMMA
requested value is terminated by a comma Explanation: The returned value is terminated by a comma, implying that additional values are in the list. User Action: No action is required.
16.36 – CONCAT
requested value is terminated by a plus sign Explanation: The returned value is concatenated to the next value with a plus sign, implying that additional values are in the list. User Action: No action is required.
16.37 – CONFLICT
illegal combination of command elements - check documentation Explanation: Two or more qualifiers, keywords, or parameters that cannot be used in combination were used in the same command line. User Action: Remove the offending element.
16.38 – CONNECFAIL
connect over network timed-out or failed Explanation: An error occurred during an attempt to establish a network connection. User Action: Examine the secondary messages to determine the reason for the failure.
16.39 – COSI_LAST_CHANCE
In cosi_last_chance handler in image <str>.Unhandled exception code was 0x<num>.Exception occurred at <str> = 0x<num>!. Explanation: An exception occurred which was not handled by another exception handler. Cosi exits the process. User Action: Check the message information and the bugheck dump, if one was written, to determine the cause of the error. If necessary, contact your Oracle support representative for assistance.
16.40 – CREATED
file/section did not exist - was created Explanation: The service completed successfully. The specified global section did not previously exist and has been created. User Action: No action is required.
16.41 – CREATEFILEMAPPINGERR
Error encountered while creating a filemapping object Explanation: A system error was encountered while creating a filemapping object User Action: Examine the secondary message to determine the reason for the failure.
16.42 – CREATEMUTEXERR
Error encountered while creating mutex Explanation: A system error was encountered while creating a mutex object User Action: Examine the secondary message to determine the reason for the failure.
16.43 – CREATERR
cannot create file Explanation: An error occurred during an attempt to close the specified file. User Action: Examine the secondary messages to determine the reason for the failure.
16.44 – CREAT_ERR
an error was returned by the creat function Explanation: An error was returned by the 'creat' function. User Action: Please refer to the reference pages for 'creat' to interpret the meaning of the errno returned by this function.
16.45 – CSETNOTFOUND
invalid or undefined character set Explanation: The character set specified is not known. User Action: Check the character set name and/or identifier to ensure that they are valid.
16.46 – CVTASSTS
Status from CVTAS routine is <num> Explanation: Actual status value from convert operation. User Action: Examine the program counter (PC) location displayed in the message. Check the program listing to verify that operands or variables are specified correctly.
16.47 – CVTUNGRANT
cannot convert an ungranted lock Explanation: An attempt was made to convert a lock that is not granted. (Only locks that are granted can be converted to another lock mode.) User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.48 – DEADLOCK
deadlock detected Explanation: The system detected a set of processes waiting for locks in a circular fashion (deadlock). This lock request is denied in order to break the deadlock. User Action: Recovery from a deadlock is application specific. One common action is for the program to rollback the transaction and retry. Deadlocks should be infrequent in properly designed applications.
16.49 – DECOVF
decimal overflow Explanation: During an arithmetic operation, a decimal value exceeds the largest representable decimal number. The result of the operation is set to the correctly signed least significant digit. User Action: No action is required.
16.50 – DEFAULTED
entity present by default in command string Explanation: The specified entity is not explicitly present in the command line, but is present by default. User Action: No action is required.
16.51 – DEFFORUSE
default format used - could not determine user's preference Explanation: Translation of RDB_DT_FORMAT failed, and the native standard representation is used. User Action: Examine and make corrections to the environment variable RDB_DT_FORMAT.
16.52 – DELETERR
error deleting file Explanation: An error occurred during an attempt to delete the specified file. User Action: Examine the secondary messages to determine the reason for the failure. You may have to change the protection on a file before you can delete it.
16.53 – DESSTROVF
destination string overflow Explanation: The destionation string is shorter than the source string when the string is copied during datatype conversion. User Action: Examine the length of the destination string and make sure the length is at least equal to or longer than the source string.
16.54 – DIFSIZ
different message size received from expected Explanation: The message size set by VMS system when message is put in the buffer and the size computed by the monitor (message header + the message length) are different. This can be caused by a multi- user environment, e.g. 5.1 image tries to attach to 6.1 monitor. User Action: Rollback/Abort
16.55 – DIRECT
invalid directory syntax - check brackets and other delimiters Explanation: The directory name in a file specification entered for a command contains an illegal character, or a command that expects a directory name string did not find a directory delimiter in the specified parameter. User Action: Examine the directory name, correct the directory syntax, and reenter the command.
16.56 – DIRNAME_ERR
an error was returned by the dirname function Explanation: An error was returned by the 'dirname' function. User Action: Please refer to the reference pages for 'dirname' to interpret the meaning of the errno returned by this function.
16.57 – DNF
directory not found Explanation: The specified directory does not exist on the specified device. User Action: Verify that the device and/or directory are specified correctly. Create the directory if necessary, or specify an existing directory.
16.58 – DT_FRACMBZ
fractional seconds precision must be zero for this sub-type Explanation: The date/time data type supplied a sub-type which does not allow a fractional seconds precision to be supplied. User Action: This appears to be an error in the code generated by SQL. Contact your Oracle support representative for assistance. You will need to provide the statement that produced this error.
16.59 – DT_PRECMBZ
interval leading field precision must be zero for this sub-type Explanation: The date/time data type supplied a sub-type which does not allow a leading interval field precision to be supplied. User Action: This appears to be an error in the code generated by SQL. Contact your Oracle support representative for assistance. You will need to provide the statement that produced this error.
16.60 – DUP_OUTPUT
output file has already been specified Explanation: The output file argument in the routine package was passed more than once. User Action: Check the file arguments, and verify that the output file was specified only once.
16.61 – EF_ALRFRE
event flag already free Explanation: An event flag that is already free is being freed. User Action: Contact your Oracle support representative for assistance.
16.62 – EF_RESSYS
event flag reserved to system Explanation: The specified event flag is reserved for system use. User Action: Contact your Oracle support representative for assistance.
16.63 – ENDDIAGS
completed with diagnostics Explanation: The operation completed with diagnostics. User Action: Correct the conditions that resulted in the diagnostics, and retry the operation.
16.64 – ENDOFFILE
end of file Explanation: An end-of-file condition was encountered during an I/O operation. User Action: Examine the secondary messages to determine the reason for the failure.
16.65 – ENGLUSED
English used - could not determine user's language Explanation: Translation of the environment variable RDB_LANGUAGE failed. English is being used. User Action: Examine RDB_LANGUAGE. Verify that the environment variable is defined.
16.66 – EOFERR
error determining size of file Explanation: An error occurred when an attempt was made to determine the size of the specified file. User Action: Examine the secondary messages to determine the reason for the failure.
16.67 – ERRFOREIGN
error opening foreign command file as input Explanation: An error occurred when a foreign (indirect) command file was read. User Action: Examine the secondary message for more information.
16.68 – EVLWRTERR
error writing to the Event Log Explanation: This general message indicates an error during a write to the NT Event Log. User Action: Examine the secondary messages to determine the reason for the failure. Make sure that the EventLog service is running and that the Event Log is not full.
16.69 – EXAIOQUOTA
exceeded aio quota Explanation: The program could not proceed because the AIO quota on the system has been exceeded. User Action: Either increase the AIO quota on the system or reduce the AIO quota consumption by Oracle Rdb servers.
16.70 – EXASTQUOTA
exceeded AST quota Explanation: The program could not proceed because the AST quota for the Rdb system has been exceeded. User Action: Increase the maximum number of users allowed on the system by modifying the RDBLCK_MAX_USERS parameter in the rdblck.conf configuration file.
16.71 – EXC_OSF
exception sub facility <num>, code <num>, <num> param(s) (17XA) Explanation: The unrecognized exception with the given sub facilkity number, code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.72 – EXC_OSF0
exception Internal, code <num>, <num> param(s) (17XA) Explanation: An 'Internal' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.73 – EXC_OSF1
exception Facility End, code <num>, <num> param(s) (17XA) Explanation: A 'Facility End' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.74 – EXC_OSF2
exception All, code <num>, <num> param(s) (17XA) Explanation: A 'Wildcard' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.75 – EXC_OSF4
exception ADA User, code <num>, <num> param(s) (17XA) Explanation: An 'ADA user' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.76 – EXC_OSF5
exception PL1 User, code <num>, <num> param(s) (17XA) Explanation: A 'Pl1 user' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.77 – EXC_OSF6
exception C++ User, code <num>, <num> param(s) (17XA) Explanation: A 'C++ user' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.78 – EXC_OSF7
exception C++ User Exit, code <num>, <num> param(s) (17XA) Explanation: A 'C++ Exit Path' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.79 – EXC_OSF8
exception C++ User Other, code <num>, <num> param(s) (17XA) Explanation: A 'C++ Other' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation.
16.80 – EXC_OSF9
exception C User, code <num>, <num> param(s) (17XA) Explanation: An 'C User' exception with the given code and optional parameters was raised in response to an arithmetic or software condition. User Action: Eliminate the cause of the error condition and retry the operation. BASEs 3811-3849 Reserved for future OSF exception types
16.81 – EXDEPTH
exceeded allowed depth Explanation: Either a programming error has occurred or the resource name tree does not have enough depth. The lock management services allow a certain depth to the resource name tree. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.82 – EXENQLM
exceeded enqueue quota Explanation: The process's ENQLM quota was exceeded. User Action: Increase the ENQLM quota, and retry the operation.
16.83 – EXGBLPAGFIL
exceeded global page file limit Explanation: The attempt to allocate a global section with a page file backing store failed because the systemwide limit on these pages is exceeded. User Action: Delete some similar sections or ask the system manager to increase the SYSGEN parameter GBLPAGFIL. Then, try the operation again.
16.84 – EXLOCKQUOTA
exceeded RDBLCK_LOCK_COUNT quota Explanation: The program could not proceed because the RDBLCK_LOCK_COUNT quota for the Oracle Rdb system has been exceeded. User Action: Increase the lock count on the system by modifying the RDBLCK_LOCK_COUNT parameter in the rdblck.conf configuration file.
16.85 – EXPROCESSQUOTA
exceeded RDBLCK_MAX_PROCESS quota Explanation: The program could not proceed because the RDBLCK_MAX_PROCESS quota for the Oracle Rdb system has been exceeded. User Action: Increase the process count on the system by modifying the RDBLCK_MAX_PROCESS parameter in the rdblck.conf configuration file.
16.86 – EXQUOTA
exceeded quota Explanation: The program 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 the appropriate quota.
16.87 – EXRESOURCEQUOTA
exceeded RDBLCK_RESOURCE_COUNT quota Explanation: The program could not proceed because the RDBLCK_RESOURCE_COUNT quota for the Oracle Rdb system has been exceeded. User Action: Increase the resource count on the system by modifying the RDBLCK_RESOURCE_COUNT parameter in the rdblck.conf configuration file.
16.88 – EXTENDERR
error extending file Explanation: An error occurred when the size of the specified file was extended. User Action: Examine the secondary messages to determine the reason for the failure.
16.89 – EXUSERSQUOTA
exceeded RDBLCK_MAX_USERS quota Explanation: The program could not proceed because the RDBLCK_MAX_USERS quota for the Oracle Rdb system has been exceeded. User Action: Increase the maximum number of users allowed on the system by modifying the RDBLCK_MAX_USERS parameter in the rdblck.conf configuration file.
16.90 – FATINTERR
fatal internal error Explanation: An unexpected internal error has occurred. User Action: Contact your Oracle support representative for assistance.
16.91 – FCSFOP
file already open Explanation: A file was already opened when it was not expected to be. This indicates a general logic error in the system database code. User Action: Retry the operation. If the error persists, contact your Oracle support representative for assistance.
16.92 – FILACCERR
error <str> file <str> Explanation: This general message indicates an error during file access. User Action: Examine the secondary messages to determine the reason for the failure.
16.93 – FILEMAPPINGEXISTS
mapping object specified already exists Explanation: The file mapping object specified by a name while creating it, already exists. User Action: Change the name of the mapping object to be unique.
16.94 – FILESYN
syntax error parsing file Explanation: This general message indicates an error that occurs during parsing of a file name (local or remote). User Action: Examine the secondary messages to determine the reason for the failure.
16.95 – FILOPENERR
error opening file <str> Explanation: An error occurred during an attempt to open the indicated file. User Action: Check the attributes and protection of the relevant file and of the associated directories. Verify that the file exists at the time it is needed.
16.96 – FILREADERR
error reading file <str> Explanation: An error occurred during an attempt to read the indicated file. User Action: Check the attributes and protection of the relevant file and of the associated directories.
16.97 – FILWRITEERR
error writing file <str> Explanation: An error occurred during an attempt to write to the indicated file. User Action: Check the attributes and protection of the relevant file and of the associated directories. Verify that sufficient disk space is available at the time that the file is written to.
16.98 – FLK
file currently locked by another user Explanation: An attempt to open or create a file failed. Another user has the file open in a mode incompatible with the attempted access. User Action: Wait until the other user has unlocked the file. If the file cannot be shared, modify the program to detect and respond to this condition by waiting.
16.99 – FLTDENORM
conversion to IEEE floating is denormalized Explanation: Conversion to IEEE float is a denormalized value. User Action: You can force a denormalized IEEE output value to zero by passing a CVT_FORCE_DENORM_TO_ZERO parameter to the cosi_cvt_ftof routine.
16.100 – FLTDIV
floating point division exception Explanation: An arithmetic exception condition occurred as a result of a floating point division operation. User Action: Modify the query to prevent a possible divide-by-zero operation from occurring.
16.101 – FLTEXC
floating point exception Explanation: An arithmetic exception condition occurred as a result of a floating point operation. This may result from a divide-by-zero operation or a floating point overflow. User Action: Modify the query to prevent a possible floating point divide-by-zero or overflow from occurring.
16.102 – FLTINF
conversion to IEEE floating is infinite Explanation: Conversion to IEEE float is an infinite value. User Action: You can force IEEE infinite to max float value by passing a CVT_FORCE_INF_TO_MAX_FLOAT parameter to the cosi_cvt_ftof routine. This will force a positive IEEE infinite output value to +max_float and force a negative IEEE infinite output value to -max_float.
16.103 – FLTINV
invalid floating conversion Explanation: The float conversion result is either ROP (Reserved Operand), NaN (Not a Number), or the closest equivalent. User Action: Make sure the float conversion routine cosi_cvt_ftof is invoked with the proper range of floating value.
16.104 – FLTINX
Float Inexact Result Explanation: An arithmetic exception condition occurred as a result of a floating point inexact result. User Action: Examine the program counter (PC) location displayed in the message. Check the program listing to verify that operands or variables are specified correctly.
16.105 – FLTNAN
Float Not a Number Explanation: An arithmetic exception condition occurred as a result of a floating Not-a-Number (NaN) value. User Action: Examine the program counter (PC) location displayed in the message. Check the program listing to verify that operands or variables are specified correctly.
16.106 – FLTOVF
floating overflow Explanation: An arithmetic exception condition occurred as a result of a floating point overflow. User Action: Examine the program counter (PC) location displayed in the message. Check the program listing to verify that operands or variables are specified correctly.
16.107 – FLTUND
floating underflow Explanation: An arithmetic exception condition occurred as a result of a floating point underflow. User Action: Examine the program counter (PC) location displayed in the message. Check the program listing to verify that operands or variables are specified correctly.
16.108 – FNF
file not found Explanation: The specified file does not exist. User Action: Check the file specification and verify that the directory, file name, and file type were all specified correctly.
16.109 – FORMAT
invalid or corrupt media format Explanation: The media or disk file is in an invalid format. User Action: This message indicates a media or hardware problem. Check the system error log and consult the hardware support group for further information. Reinstalling Oracle Rdb will resolve the problem. However, if the error regularly occurs, faulty hardware is almost certainly the cause.
16.110 – FORMATERR
error in formatting output Explanation: An error occurred during formatting of output to a terminal or a file. User Action: Examine the secondary messages to determine the reason for the failure.
16.111 – GETPWNAM_ERR
an error was returned by the getpwnam function Explanation: An error was returned by the 'getpwnam' function. User Action: Please refer to the reference pages for 'getpwnam' to interpret the meaning of the errno returned by this function.
16.112 – ILLCOMPONENT
illegal initialization component Explanation: The format for the data and time formatting string for one of the fields is illegal. User Action: Check your data and time format string to be used for displaying date and time strings.
16.113 – ILLEFC
illegal event flag cluster Explanation: An event flag number specified in a system service call is greater than 127. User Action: Contact your Oracle support representative for assistance.
16.114 – ILLFORMAT
illegal format - too many or not enough fields Explanation: An invalid date and time format string was given. User Action: Examine the date/time format string, and correct it.
16.115 – ILLINISTR
illegal initialization string Explanation: An incorrect initialization string is passed to date and time formatting services. User Action: Verify that the initialization string begins and ends with the same delimiter character.
16.116 – ILLSTRCLA
illegal string class Explanation: The class code found in the class field of a descriptor is not a supported string class code. User Action: Contact your Oracle support representative for assistance.
16.117 – ILLSTRPOS
illegal string position Explanation: The service completed successfully. However, one of the character-position parameters to a string manipulation routine pointed to a character-position that is before the beginning of the input string or that is after the end of the input string. User Action: Ensure that any character-position parameter is greater than zero and less than or equal to the length of the input string.
16.118 – ILLSTRSPE
illegal string specification Explanation: The service completed successfully, except that the character-position parameters specifying a substring of a string parameter were inconsistent because the ending character position is less than the starting character position. A null string is used for the substring. User Action: The application program should verify that the starting character positions are less than or equal to the ending character positions.
16.119 – 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.
16.120 – INCDATTIM
incomplete date-time - missing fields with no defaults Explanation: An incomplete date or time parameter was supplied. User Action: Examine the date/time value and the data and time format string. Correct the input data/ time value.
16.121 – INPCONERR
input conversion error Explanation: There is an invalid character in the input string; or the output value is not within the range of the destination data type. User Action: Correct the input string, or change the destination data type.
16.122 – INP_FILES
too many input files specified Explanation: More than 10 input files were listed. User Action: Reduce the number of input files or combine them so that no more than 10 input files are listed.
16.123 – INSEF
insufficient event flags Explanation: There were insufficient event flags. There were no more event flags available for allocation. User Action: Contact your Oracle support representative for assistance.
16.124 – INSFARG
insufficient call arguments Explanation: An internal coding error (insufficient number of arguments) occurred. User Action: Contact your Oracle support representative for assistance.
16.125 – INSFMEM
insufficient dynamic memory Explanation: A command or image exhausted the system pool of dynamic memory, and the system cannot complete the request. User Action: Free the resources you are holding, or increase the existing pool of memory.
16.126 – INSFPRM
missing command parameters - supply all required parameters Explanation: A command cannot be executed because one or more required parameters are missing from the command. User Action: Correct the command by supplying all required parameters.
16.127 – INSFSYSRES
insufficient system resources Explanation: The operating system did not have sufficient resources to process the request. User Action: Examine secondary error message for more information.
16.128 – INTOVF
integer overflow Explanation: Either the library routine or the hardware detected an integer overflow. User Action: Choose a destination data type with a larger range.
16.129 – INT_OVERFLOW
Arithmetic exception: Integer Overflow Explanation: Attempt to use a number which was too great in magnitude to be used in the manner intended. User Action: Review the problem and change the data or data format accordingly.
16.130 – INVARG
invalid argument(s) Explanation: An invalid argument is specified to an internal call. User Action: Contact your Oracle support representative for assistance.
16.131 – INVARGORD
invalid argument order Explanation: The ordering of the arguments is invalid. The caller specified the the data and time values in the wrong order. User Action: Contact your Oracle support representative for assistance.
16.132 – INVCLADSC
invalid class in descriptor Explanation: An unsupported class of descriptor is specified. User Action: Retry the operation specifying a supported class of descriptor.
16.133 – INVCLADTY
invalid class data type combination in descriptor Explanation: An unsupported class and data type of descriptor is specified. User Action: Ensure that both the class and data type specified are supported.
16.134 – INVCVT
invalid data type conversion Explanation: 1. source value is negative and destination data type is unsigned, or 2. possible bad parameter, such as invalid input/output type, invalid option value, or 3. float over/under flow (on ALPHA/VMS), or 4. positive/Negative Infinity (on ALPHA/VMS), or 5. reserved operand error. User Action: Ensure that the source value is positive and the destination data type is signed, or the parameters are passed correctly, or contact your Oracle support representative for assistance.
16.135 – INVDTYDSC
invalid data type in descriptor Explanation: An unsupported data type is specified. User Action: Retry the operation specifying a supported data type.
16.136 – INVENTITY
invalid command line entity specified Explanation: An invalid qualifier or parameter was found on the command line. User Action: Reenter the command line using the correct syntax.
16.137 – INVFILNAM
invalid character found in file name Explanation: A non-ASCII character was found in a file name used in a command. User Action: Examine the file name, correct the name, and reenter the command.
16.138 – INVKEY
invalid keyword Explanation: There was an unrecognized keyword in the command string. User Action: Reenter the command using the correct syntax.
16.139 – INVNBDS
invalid numeric byte data string Explanation: There is an invalid character in the input, or the value is outside the range that can be represented by the destination, or the numeric byte date string (NBDS) descriptor is invalid. This error is also signaled when the array size of an NBDS is larger than 65,535 bytes or the array is multi-dimensional. User Action: Specify a valid NBDS.
16.140 – INVREQTYP
invalid request type Explanation: This message is associated with an internal status code returned from the command interpreter result parse routine. The message indicates a request to perform an unimplemented function. User Action: Contact your Oracle support representative for assistance.
16.141 – INVSTRDES
invalid string descriptor Explanation: A string descriptor passed to a general library procedure did not contain a valid CLASS field. User Action: Locate the call to the library that caused the error, and initialize the field to the proper class of descriptor.
16.142 – INVWRKBLK
invalid request type Explanation: This message is associated with an internal status code returned from the command interpreter result parse routine. The message indicates that the parser encountered a corrupt internal data structure. User Action: Contact your Oracle support representative for assistance.
16.143 – INV_PRECISION
invalid interval leading field precision for datetime Explanation: The data definition language requested an interval leading field precision which is outside the supported range. User Action: Correct the definition so that the interval leading field precision is within the legal range.
16.144 – INV_SCALE
invalid fractional seconds precision for datetime Explanation: The data definition language requested a fractional seconds precision for a TIME, TIMESTAMP, or INTERVAL definition which is outside the correct range. User Action: Correct the definition so that the fractional seconds precision is within the legal range.
16.145 – INV_SUB_TYPE
invalid sub_type in definition Explanation: The data definition language requested a sub-type which was not recognized. User Action: Correct the definition so that the sub-type is within the legal range.
16.146 – IO_ERROR
IO error while reading help file Explanation: An IO error occured while reading a help library. User Action: Contact your Oracle support representative for assistance.
16.147 – IVACL
invalid access control list entry syntax Explanation: You have specified syntax for an access control list entry that is not acceptable. User Action: Specify a valid access control list entry syntax. For RMU, this will typically be of the form: (IDENT = identifier, ACCESS = privilege+privilege+...)
16.148 – IVBUFLEN
invalid buffer length Explanation: The length of the buffer supplied was invalid. The length of the resource name provided to the system service to acquire a lock was more than 31 characters, or an I/O message was too large to handle. User Action: This error message indicates a possible error in the use of operating system services. Contact your Oracle support representative for assistance.
16.149 – IVDEVNAM
invalid device name Explanation: A device name contains invalid characters, or no device is specified. User Action: Verify that the device name is specified correctly and is suitable for the requested operation.
16.150 – IVKEYW
unrecognized keyword - check validity and spelling Explanation: There is an unrecognized keyword in the command string. User Action: Reenter the command using the correct syntax.
16.151 – IVLOCKID
invalid lock id Explanation: The lock identification specified in the call to the lock or unlock request is not a valid lock identification for that process. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.152 – IVLOGNAM
invalid logical name Explanation: A name string exceeds the maximum length permitted or has a length of 0. User Action: Check that the character string descriptors pointing to name strings indicate the correct lengths.
16.153 – IVMODE
invalid mode for requested function Explanation: The caller does not have the privilege to perform the operation. User Action: This error message indicates a possible error in the use of operating system primitives. Contact your Oracle support representative for assistance.
16.154 – IVQLOC
invalid qualifier location - place after a parameter Explanation: A qualifier that can be used only to qualify a parameter value in a command is placed following the command name. User Action: Reenter the command. Place the qualifier following the parameter value it qualifies.
16.155 – IVQUAL
unrecognized qualifier - check validity, spelling, and placement Explanation: A qualifier is spelled incorrectly or is improperly placed in the command line. User Action: Correct the command line.
16.156 – IVTILDEUSER
invalid user name found in the file specification Explanation: The user name specified after a ~ (tilde) in the specified file is not a vailid user name, and therefore cannot be used to get to a home directory. User Action: Verify that the user name is specified correctly, and correct any spelling errors.
16.157 – IVTIME
invalid date or time Explanation: A time value specified in a system service call is invalid. Either a delta time is greater than 10,000 days, or a calculated absolute time is less than the system date and time. User Action: Check for a programming error. Verify that the call to the service is coded correctly.
16.158 – IVVERB
unrecognized command verb - check validity and spelling Explanation: The first word on the command line is not a valid command. User Action: Check the spelling of the command name and reenter the command.
16.159 – KEYAMBINC
key specification is ambiguous or inconsistent Explanation: Duplicate key parameters were specified for a single KEY qualifier. User Action: Specify each key parameter only once. For multiple keys, use a KEY qualifier for each key.
16.160 – KEYED
mismatch between sort/merge keys and primary file key Explanation: An empty indexed file was created with a primary key that does not match the sort key. The sort operation is less efficient than it is when the two keys match. User Action: For greater efficiency, create a new indexed file or change the sort key.
16.161 – KEY_LEN
invalid key length, key number <num>, length <num> Explanation: The key size is incorrect for the data type, or the total key size is greater than 32,767. User Action: Specify the correct key field size. Size must be less than or equal to 32,767 for character data; 1, 2, 4, 8, or 16 for binary data; and less than or equal to 31 for decimal. Also, only ascending or descending order is allowed.
16.162 – LIB_NOT_OPEN
help library not open Explanation: An attempt was made to access a help library without opening it first. User Action: Contact your Oracle support representative for assistance.
16.163 – LM_EXCEEDED
licensed product has exceeded current license limits Explanation: The number of active license units has exceeded the current limits. User Action: Reduce the number of active users of the product.
16.164 – LM_ILLPRODUCER
producer argument isn't DEC Explanation: The producer name for the product does not match with the license installed on the system. User Action: Check the license installed on the system.
16.165 – LM_INVALID_DATE
license is invalid for this product date Explanation: The date of the product release does not match with the date of the license installed. User Action: Check the installed license.
16.166 – LM_INVALID_VERS
license is invalid for this product version Explanation: The version of the product does not match with the license on the system. User Action: Check the installed license.
16.167 – LM_NOLICENSE
operation requires software license Explanation: A license for the software does not exist. User Action: Please install the license for the product.
16.168 – LM_NOTINRSRVLIST
not in license reserve list Explanation: This user is not in the list of reserved users (for a user-based license). User Action: Please add the user to the list of reserved users.
16.169 – LM_TERMINATED
license has terminated Explanation: The license for the product has been terminated. User Action: Please renew your license or install a new one.
16.170 – LOADFAILURE
unable to dynamically load or unload image Explanation: The system is unable to dynamically load an executable image. User Action: Ensure that the relevent image is available on your system.
16.171 – LOADINVFILNAM
invalid image filename Explanation: The filename supplied for dynamic image loading was improperly specified or contains illegal characters. User Action: Correct the filename.
16.172 – LOADINVSECFIL
invalid secure image filespec Explanation: The file specification supplied for secure EXEC mode logical translation contains illegal characters or does not reference an existing image. User Action: Ensure that the file specification is correct and that the specified image exists.
16.173 – LOADSYMBOL
unable to look up symbol in dynamically loaded image Explanation: The system is unable to look up a symbol in a dynamically loaded image. User Action: Ensure that the relevent image is available on your system and that the image is intact (not corrupt).
16.174 – LOADUNINSTALLED
unable to dynamically load uninstalled image Explanation: The system is unable to dynamically load a shareable image into the process with the main image which is installed execute_only or privileged. The new image must be installed and any associated filespec must reference only /SYSTEM/EXEC logicals. User Action: Ensure that the relevent image is installed on your system and that the proper logicals are used in the related filespec.
16.175 – LOCNEG
entity explicitly and locally negated in command string Explanation: The specified qualifier is present in its negated form (prefixed with no) and is used as a local qualifier. User Action: No action is required.
16.176 – LOCPRES
entity value is locally present in command string Explanation: The specified qualifier is present and is used as a local qualifier. User Action: No action is required.
16.177 – LRL_MISS
longest record length must be specified Explanation: If a record I/O interface subroutine package is selected, the longest record length (LRL) must be passed to sort in the call. User Action: Specify the LRL.
16.178 – MAPVIEWOFFILEERR
Error encountered while mapping a view of the file Explanation: A system error was encountered while mapping a view of the file into the virtual address space. User Action: Examine the secondary message to determine the reason for the failure.
16.179 – MAXPARM
too many parameters - reenter command with fewer parameters Explanation: A command contained more than the maximum number of parameters allowed. This error can be caused by leaving blanks on a command line where a special character, for example, a comma or plus sign, is required. User Action: Determine the reason for the error, and correct the syntax of the command.
16.180 – MKDIR_ERR
an error was returned by the mkdir function Explanation: An error was returned by the 'mkdir' function. User Action: Please refer to the reference pages for 'mkdir' to interpret the meaning of the errno returned by this function.
16.181 – MODIFYERR
error extending or truncating file Explanation: An error occurred during an attempt to modify the size of the specified file. User Action: Examine the secondary messages to determine the reason for the failure.
16.182 – MSGNOTFND
message not in system message file Explanation: The relevant message was not found in the message file, or the message system was not properly initialized. User Action: Contact your Oracle support representative for assistance.
16.183 – MUTEXEXISTS
mutex object specified already exists Explanation: The mutex object specified while creating already exists. User Action: Change the name of the mutex object to be unique.
16.184 – NAMTOOLON
piece of pathname too long - respecify Explanation: The user-supplied file specification is too long (greater than 255 characters). User Action: Reenter the file name with fewer than 255 characters.
16.185 – NEGATED
entity explicitly negated in command string Explanation: The specified qualifier or keyword is present in its negated form (prefixed with NO). User Action: No action is required.
16.186 – NEGSTRLEN
negative string length Explanation: The service completed successfully, except that a length parameter to a string routine had a negative value. Lengths of strings must always be positive or zero; zero is used. User Action: Verify that all parameters containing string lengths do not contain negative numbers.
16.187 – NEGTIM
a negative time was computed Explanation: The computed time was less than the date (17-NOV-1858). User Action: Contact your Oracle support representative for assistance.
16.188 – NFS
file specification on an NFS mounted device is not allowed Explanation: An NFS mounted device was referenced in the file specification. NFS mounted devices are not supported. User Action: Use a file name that does not reference an NFS mounted device.
16.189 – NOACLSUPPORT
ACLs not supported on selected object Explanation: ACLs are not supported for the specified object. User Action: Make sure that you have correctly specified the object.
16.190 – NOCCAT
parameter concatenation not allowed - check use of plus (+) Explanation: A command that accepts either a single-input value for a parameter or a list of input values separated by commas, contains multiple values concatenated by plus signs ( + ). User Action: Reenter the command with a single file specification. If necessary, enter the command once for each file.
16.191 – NOCOMD
no command on line - reenter with alphabetic first character Explanation: A command begins with a nonalphabetic character. User Action: Reenter the command with an alphabetic character at the beginning.
16.192 – NODEVDIR
filename does not include device and/or directory Explanation: The file specification you made did not include a device and directory. User Action: Include a device and/or directory in the file specification.
16.193 – NODUPEXC
equal-key routine and no-duplicates option cannot both be specified Explanation: Both an equal-key routine and the SOR$M_NODUPS option were specified when only one or the other option is allowed. User Action: Specify either the equal-key routine or the no-duplicates option.
16.194 – NOENTRY
access control entry not found Explanation: You have specified an access control entry that does not exist in the access control list. User Action: Add the desired access control entry to the access control list, or specify a different access control entry for your command.
16.195 – NOKEYW
qualifier name is missing - append the name to the delimiter Explanation: A qualifier delimiter is present on a command but is not followed by a qualifier keyword name. User Action: Reenter the command specifying the qualifier or removing the qualifier delimiter.
16.196 – NOLIST
list of parameter values not allowed - check use of comma (,) Explanation: A command that accepts only a single input value for a parameter contains multiple values separated by commas. User Action: Reenter the command. Specify only one file. If necessary, enter the command once for each file specified.
16.197 – NOLOCKID
no lock identification available Explanation: The system's lock identification table is full when a call to acquire a lock is made. User Action: Increase the size of the lock identification table. If the problem persists, contact your Oracle support representative for assistance.
16.198 – NOLOGNAM
no logical name match Explanation: A specified logical name does not exist. User Action: Verify the spelling of the logical name.
16.199 – NOMEMRESID
requires rights identifier VMS$MEM_RESIDENT_USER Explanation: Attempt to create a memory-resident global section without having the VMS$MEM_RESIDENT_USER identifier. User Action: Enable the VMS$MEM_RESIDENT_USER identifier for the process.
16.200 – NOMOREACE
access control list is exhausted Explanation: There are no more access control entries in the access control list. User Action: Do not perform this command when there are no more access control entries in the access control list.
16.201 – NOMORELOCK
no more locks Explanation: No lkid argument was specified, or the caller requested a wildcard operation by specifying a value of 0 or -1 for the lkidadr argument. The service that provides information about locks, however, has exhausted the locks about which it can return information. This is an alternate success status. User Action: No action is required.
16.202 – NONAME
file name specified where not permitted
16.203 – NONEXPR
nonexistent process Explanation: The process name or the process identifier specified is invalid. User Action: Contact your Oracle support representative for assistance.
16.204 – NOPAREN
value improperly delimited - supply parenthesis Explanation: A value supplied as part of a parenthesized value list for a parameter, qualifier, or keyword is missing a delimiting parenthesis. User Action: Reenter the command with the missing parenthesis.
16.205 – NOPRIV
no privilege for attempted operation Explanation: You do not have the appropriate privilege to perform this operation. User Action: See your database administrator, and request the appropriate privilege for the attempted operation.
16.206 – NOQUAL
qualifiers not allowed - supply only verb and parameters Explanation: A command that has no qualifiers is specified with a qualifier. User Action: Reenter the command. Do not specify any qualifiers.
16.207 – NORECATTRS
missing record specification Explanation: A fatal, internal error has occurred. User Action: Contact your Oracle support representative for assistance.
16.208 – NORECSIZE
record size not specified Explanation: A fatal, internal error has occurred. User Action: Contact your Oracle support representative for assistance.
16.209 – NOSHMEM
operation requires SHMEM privilege Explanation: A command requested a function that requires SHMEM privilege; the current process does not have this privilege. User Action: See your database administrator, and request the SHMEM privilege for the attempted operation.
16.210 – NOSPACE
maximum file size exceeded or file system full Explanation: A file update operation could not be completed. The file system is full, or the file exceeds the system-allowed maximum. User Action: Make space available on the device in question.
16.211 – NOSUCHDEV
no such device available Explanation: The specified device does not exist on the system. User Action: Examine the secondary messages to determine the reason for the failure.
16.212 – NOSUCHID
unknown rights identifier Explanation: The rights identifier that you have specified does not exist on this system. User Action: Specify only valid (known) rights identifiers.
16.213 – NOSUCHNET
no such network available Explanation: A DECnet connection was attempted on a system that does not support DECnet, or a TCP/IP connection was attempted on a system that does not support TCP/IP. User Action: Do not attempt to use a network that cannot be accessed.
16.214 – NOSUCHNODE
remote node is unknown Explanation: An attempt to make a network access failed because the remote node name does not exist or cannot be accessed. User Action: Check the remote node name for validity. If this error occurs when you use a valid node name, see your network administator.
16.215 – NOSUCHOBJECT
specified object does not exist Explanation: You are trying to get or set the security attributes (probably ACLs) for an object that does not exist. User Action: Make sure that you have correctly specified the object.
16.216 – NOSUCHSEC
named shared memory section does not exist Explanation: An attempt to map a shared memory section failed, because the the shared memory section does not exist. User Action: Contact your Oracle support representative for assistance.
16.217 – NOSUCHSRV
network service is unknown at remote node Explanation: An attempt to make a network access failed, because the service is not registered in the services database. User Action: See your network administator.
16.218 – NOTALLPRIV
not all requested privileges authorized Explanation: You have requested a privilege for which you are not authorized. User Action: Request only privileges for which you are authorized.
16.219 – NOTDISKFILE
file is not a disk file Explanation: A file name was specified which does not reference a disk- oriented device type. User Action: Check the file name for a proper disk device type.
16.220 – NOTINITED
COSI facility not initialized Explanation: An internal intialization error occurred. User Action: Contact your Oracle support representative for assistance.
16.221 – NOTNEG
qualifier or keyword not negatable - remove "NO" or omit Explanation: The word "no" preceded a qualifier or keyword, but the qualifier or keyword cannot be specified as a negative. User Action: Reenter the qualifier or keyword in a non-negated form.
16.222 – NOTNETDEV
not a network communication device Explanation: An attempt to be a network service provider has failed, because the process was not started by the DECnet spawner or inetd daemon. User Action: Check for a programming error. Verify that the device specified in the queue I/O request is a valid communications device.
16.223 – NOTQUEUED
request not queued Explanation: The lock request was made with a flag setting indicating that if the request cannot be granted synchronously, it should be ignored. User Action: Wait and retry the operation.
16.224 – NOTSYSCONCEAL
non-system concealed device name in filename Explanation: Concealed device names must be defined in the system logical table. User Action: If the device name has to be concealed, define it in the system logical table (LNM$SYSTEM_TABLE) or in the cluster-wide system logical name table (LNM$SYSCLUSTER_TABLE).
16.225 – NOTYPE
file type specified where not permitted
16.226 – NOVALU
value not allowed - remove value specification Explanation: A qualifier or keyword that does not accept a value is specified with a value. User Action: Reenter the command omitting a value for the qualifier or keyword.
16.227 – NOVER
file version specified where not permitted
16.228 – NOWILD
wild card specified where not permitted Explanation: One or more of these filename components was specified in a context in which it is not allowed. User Action: Review the command used and correct it.
16.229 – NO_SUCH_TOPIC
topic does not exist in help library Explanation: Help was asked for a topic that does not exist in the help library. User Action: Contact your Oracle support representative for assistance.
16.230 – NO_WRK
work files required - cannot do sort in memory as requested Explanation: The work-files=0 qualifier is specified, indicating the data would fit in memory, but the data is too large. User Action: Either increase the working set quota, or allow the sort utility to use two or more work files. If this message accompanies the MSGHLP error, SORTERR, see the description of that message for more information.
16.231 – NULFIL
missing or invalid file specification - respecify Explanation: The command interpreter expected a file specification, but no file specification was entered. User Action: Reenter the command. Place the file specification in the proper position.
16.232 – NUMBER
invalid numeric value - supply an integer Explanation: A numeric value is specified for a command that expects values in certain radices or interprets values within a particular context. For example, the number 999 is entered when an octal value is required, or an alphabetic value is specified in a context that requires a numeric value. User Action: Reenter the command using legal values.
16.233 – NUMELEMENTS
number of elements incorrect for component Explanation: An incorrect number of elements were specified for initialization of data and time format. User Action: Contact your Oracle support representative for assistance.
16.234 – NUM_KEY
too many keys specified Explanation: Up to 255 key definitions are allowed. Either too many key definitions have been specified or the NUMBER value is wrong. User Action: Check your command string key field specifications.
16.235 – NYI
functionality is not yet implemented Explanation: The functionality has not yet been implemented. User Action: Contact your Oracle support representative for assistance.
16.236 – ONEDELTIM
at least one delta time is required Explanation: The DATE and TIME services require at least one of the inputs to be a delta time. User Action: Contact your Oracle support representative for assistance.
16.237 – ONEVAL
list of values not allowed - check use of comma (,) Explanation: A qualifier, keyword, or parameter that accepts only a single value is specified with multiple values. User Action: Reenter the command specifying only one value.
16.238 – OPENERR
cannot open file Explanation: An error occurred during an attempt to open a file. User Action: Examine the secondary messages to determine the reason for the failure.
16.239 – OPENFILEMAPPINGERR
Error encountered while opening a file mapping object Explanation: A system error was encountered while opening a filemapping object User Action: Examine the secondary message to determine the reason for the failure.
16.240 – OPENMUTEXERR
Error encountered while opening mutex Explanation: A system error was encountered while opening mutex object User Action: Examine the secondary message to determine the reason for the failure.
16.241 – OPEN_ERR
an error was returned by the open function Explanation: An error was returned by the 'open' function. User Action: Please refer to the reference pages for 'open' to interpret the meaning of the errno returned by this function.
16.242 – OUTCONERR
output conversion error Explanation: The result would have exceeded the fixed-length string. User Action: Increase the length of the fixed-length string, and retry the operation.
16.243 – OUTSTRTRU
output string truncated Explanation: The source and destination strings are character-coded text datum, and the destination string cannot contain all of the output string. The result is truncated. User Action: No action is required.
16.244 – PARMDEL
invalid parameter delimiter - check use of special characters Explanation: A command contains an invalid character following the specification of a parameter, or an invalid character is present in a file specification. User Action: Check the command string for a spelling or grammatical error. Reenter the command.
16.245 – PARNOTGRANT
parent lock must be granted Explanation: A programming error occurred because an attempt was made to create a sublock under a parent lock that was not granted. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.246 – PRESENT
entity value is present in command string Explanation: You do not have the appropriate privilege to perform this operation. User Action: See your database administrator, and request the appropriate privilege for the attempted operation.
16.247 – PROTERR
Error encountered during attempt to modify protection of a file Explanation: An error was encountered during an attempt to modify the protection of a file. User Action: Examine the secondary message to determine the reason for the failure. You may not have the necessary privileges to modify the protection for that file.
16.248 – PTHTOOLON
file path length too long - respecify Explanation: The user-supplied file specification is too long (greater than 255 characters). User Action: Reenter the file name with fewer characters.
16.249 – PWDEXPIRED
password has expired Explanation: The authentication of the user has failed because a password provided has expired and a new password is required to complete the request. User Action: The password for this user has expired and a new password is required. See your database administrator for help on changing your password.
16.250 – READERR
read error Explanation: An error occurred during a read from a mailbox or socket. User Action: Examine the secondary messages to determine the reason for the failure.
16.251 – READ_ERR
an error was returned by the read function Explanation: An error was returned by the 'read' function. User Action: Please refer to the reference pages for 'read' to interpret the meaning of the errno returned by this function.
16.252 – REMOTE
remote file specification is not allowed 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.
16.253 – RESINUSE
requested resource already in use Explanation: Specified resource (event flag, message facility, etc.) is in use. User Action: Contact your Oracle support representative for assistance.
16.254 – RETRY
retry operation Explanation: This status is returned if the lock management services are performing some internal re-building of the lock tables when the caller requests a lock. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.255 – RNF
record not found Explanation: A requested record could not be located. Either the record was never written or it has been deleted. User Action: Modify the program, if necessary, to detect and respond to the condition.
16.256 – RSLOVF
buffer overflow - specify fewer command elements Explanation: The command buffer has overflowed. User Action: Specifiy fewer command elements.
16.257 – RTNERROR
unexpected error status from user-written routine Explanation: A user-written comparison or equal-key routine returned an unexpected error status. User Action: Correct your comparison or equal-key routine.
16.258 – SETEUID_ERR
an error was returned by the seteuid function Explanation: An error was returned by the 'seteuid' function. User Action: Please refer to the reference pages for 'seteuid' to interpret the meaning of the errno returned by this function.
16.259 – SETREUID_ERR
an error was returned by the setreuid function Explanation: An error was returned by the 'setreuid' function. User Action: Please refer to the reference pages for 'setreuid' to interpret the meaning of the errno returned by this function.
16.260 – SETUID_ERR
an error was returned by the setuid function Explanation: An error was returned by the 'setuid' function. User Action: Please refer to the reference pages for 'setuid' to interpret the meaning of the errno returned by this function.
16.261 – SHMATERR
Error encountered during attach to shared memory Explanation: A system error was encountered during an attach to a shared memory segment that is used for concurrency and synchronization operations. User Action: Examine the secondary message to determine the reason for the failure.
16.262 – SHMCTLERR
Error encountered while controlling shared memory Explanation: A system error was encountered while controlling a shared memory region that was created for concurrency and synchronization operations. User Action: Examine the secondary message to determine the reason for the failure.
16.263 – SHMDTERR
Error encountered during detach from shared memory Explanation: A system error was encountered during a detach from a shared memory segment that is used for concurrency and synchronization operations. User Action: Examine the secondary message to determine the reason for the failure.
16.264 – SHMGETERR
Error encountered while creating shared memory Explanation: A system error was encountered during creation of a shared memory segment that is used for concurrency and synchronization operation. User Action: Examine the secondary message to determine the reason for the failure.
16.265 – SIGEXIT
process has died due to some signal Explanation: The process that is being looked at has died due to some signal. User Action: Check to see why the process died.
16.266 – SIGNAL
signal number <num>, code <num> Explanation: The unrecognized signal specified by the given number was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.267 – SIGNAL1
signal SIGHUP, code <num> Explanation: A 'hangup' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.268 – SIGNAL10
signal SIGBUS, code <num>, PC=!XA Explanation: A 'hardware fault' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.269 – SIGNAL11
signal SIGSEGV, code <num> Explanation: An 'invalid memory reference' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.270 – SIGNAL12
signal SIGSYS, code <num> Explanation: An 'invalid system call' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.271 – SIGNAL13
signal SIGPIPE, code <num> Explanation: A 'write to pipe with no readers' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.272 – SIGNAL14
signal SIGALRM, code <num> Explanation: A 'time out (alarm)' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.273 – SIGNAL15
signal SIGTERM, code <num> Explanation: A 'termination' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.274 – SIGNAL16
signal SIGURG, code <num> Explanation: An 'urgent condition' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. SIGIOINT (printer to backend error signal) is another name for this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.275 – SIGNAL17
signal SIGSTOP, code <num> Explanation: A 'stop' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. This exception is not expected to occur since the SIGSTOP signal cannot be caught. User Action: Eliminate the cause of the error condition and retry the operation.
16.276 – SIGNAL18
signal SIGTSTP, code <num> Explanation: A 'terminal stop character' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.277 – SIGNAL19
signal SIGCONT, code <num> Explanation: A 'continue stopped process' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.278 – SIGNAL2
signal SIGINT, code <num> Explanation: A 'terminal interrupt character' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.279 – SIGNAL20
signal SIGCHLD, code <num> Explanation: A 'change in status of child' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.280 – SIGNAL21
signal SIGTTIN, code <num> Explanation: A 'background read from control tty' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.281 – SIGNAL22
signal SIGTTOU, code <num> Explanation: A 'background write to control tty' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.282 – SIGNAL23
signal SIGIO, code <num> Explanation: An 'asynchronous I/O' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. SIGAIO (base lan i/o), SIGPTY (pty i/o), and SIGPOLL (STREAMS i/o) are other names for this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.283 – SIGNAL24
signal SIGXCPU, code <num> Explanation: A 'CPU time limit exceeded' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.284 – SIGNAL25
signal SIGXFSZ, code <num> Explanation: A 'file size limit exceeded' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.285 – SIGNAL26
signal SIGVTALRM, code <num> Explanation: A 'virtual time alarm' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.286 – SIGNAL27
signal SIGPROF, code <num> Explanation: A 'profiling time alarm' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.287 – SIGNAL28
signal SIGWINCH, code <num> Explanation: A ;terminal window size change' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.288 – SIGNAL29
signal SIGINFO, code <num> Explanation: A 'status request from keyboard' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. SIGPWR (Power Fail/Restart) is another name for this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.289 – SIGNAL3
signal SIGQUIT, code <num> Explanation: A 'terminal quit character' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.290 – SIGNAL30
signal SIGUSR1, code <num> Explanation: A 'user defined' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.291 – SIGNAL31
signal SIGUSR2, code <num> Explanation: A 'user defined' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation. BASEs 3881-3899 Reserved for future OSF signal types
16.292 – SIGNAL4
signal SIGILL, code <num>, PC=!XA Explanation: An 'illegal hardware instruction' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.293 – SIGNAL5
signal SIGTRAP, code <num>, PC=!XA Explanation: A 'hardware fault' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. Decimal overflow, Decimal divide by 0, Decimal invalid operand, Assertion error, Null pointer error, Stack overflow, String length error, Substring error, Range error, and Subscript [n] range error are specific conditions producing this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.294 – SIGNAL6
signal SIGABRT, code <num> Explanation: An 'abnormal termination (abort)' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. SIGIOT (abort (terminate) process) and SIGLOST are other names for this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.295 – SIGNAL7
signal SIGEMT, code <num> Explanation: A 'hardware fault' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. User Action: Eliminate the cause of the error condition and retry the operation.
16.296 – SIGNAL8
signal SIGFPE, code <num>, PC=!XA Explanation: An 'arithmetic exception' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. Integer overflow, Integer divide by 0, Floating overflow, Floating divide by 0, Floating underflow, Floating invalid operation, Floating inexact result, and Reserved Operand are specific conditions producing this signal. User Action: Eliminate the cause of the error condition and retry the operation.
16.297 – SIGNAL9
signal SIGKILL, code <num> Explanation: A 'termination' signal was raised as an exception in response to the arithmetic or software condition specified by the given code. This exception is not expected to occur since the SIGKILL signal cannot be caught. User Action: Eliminate the cause of the error condition and retry the operation.
16.298 – SSCANF_ERR
an error was returned by the sscanf function Explanation: An error was returned by the 'sscanf' function. User Action: Please refer to the reference pages for 'sscanf' to interpret the meaning of the errno returned by this function.
16.299 – STABLEEXC
equal-key routine and stable option cannot both be specified Explanation: Both an equal-key routine and the SOR$M_STABLE option was specified when only one or the other is allowed. User Action: Specify either the equal-key routine or the stable option.
16.300 – STAT_ERR
an error was returned by the stat function Explanation: An error was returned by the 'stat' function. User Action: Please refer to the reference pages for 'stat' to interpret the meaning of the errno returned by this function.
16.301 – STDOUTERR
error writing to stdout Explanation: This general message indicates an error during a write to STDOUT. User Action: Examine the secondary messages to determine the reason for the failure.
16.302 – STRTOOLON
string argument is too long - shorten Explanation: A string did not fit into the specified receiving area, resulting in lost trailing characters. User Action: Correct your program to increase the area specified to receive the string.
16.303 – STRTRU
string truncated Explanation: A string did not fit into the specified receiving area, resulting in lost trailing characters. User Action: Correct your program to increase the area specified to receive the string.
16.304 – SUBLOCKS
cannot dequeue a lock with sublocks Explanation: A programming error occurred because an attempt was made to unlock a lock that had sublocks under it. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.305 – SUPERSEDE
logical name superseded Explanation: The logical name has been created and a previously existing logical name with the same name has been deleted. User Action: No action is required.
16.306 – SYNCH
synchronous successful completion Explanation: This alternate success code indicates that the requested operation completed synchronously and as expected. User Action: No action is required.
16.307 – SYSTEM_ERR
an error was returned by the system function Explanation: An error was returned by the 'system' function. User Action: Please refer to the reference pages for 'system' to interpret the meaning of the errno returned by this function.
16.308 – TIMETRU
time hundreths of seconds truncated Explanation: A time was specified that had hundreths of seconds. This is not supported on. User Action: Do not specify hundreths of seconds in time literals.
16.309 – TKNOVF
command element is too long - shorten Explanation: The command element buffer has overflowed. User Action: Shorten the command element and retry.
16.310 – TRU
truncation Explanation: An attempt was made to place more characters into a string than it could contain. The value is truncated on the right to fit. User Action: Do not exceed the maximum string length. Ignore this error if right truncation is acceptable.
16.311 – TRUNCERR
error truncating file Explanation: An error occurred during truncation of the size of the specified file. User Action: Examine the secondary messages to determine the reason for the failure.
16.312 – UNDOPTION
undefined option flag was set Explanation: Only those option flags used by SORT MERGE can be set. All other bits in the longword are reserved and must be zero. User Action: Correct your specification file.
16.313 – UNEXPERR
unexpected system error Explanation: Some unexpected error occurred during execution of the software. User Action: Contact your Oracle support representative for assistance.
16.314 – UNKNOWN_USER
unknown user Explanation: An authentication routine cannot identify the user. User Action: Use the USER and USING clauses to specify a valid user.
16.315 – UNLINK_ERR
an error was returned by the unlink function Explanation: An error was returned by the 'unlink' function. User Action: Please refer to the reference pages for 'unlink' to interpret the meaning of the errno returned by this function.
16.316 – UNMAPVIEWOFFILEERR
Error encountered while unmapping a view of file Explanation: A system error was encountered while unmapping a view of the file from the virtual address space. User Action: Examine the secondary message to determine the reason for the failure.
16.317 – UNRFORCOD
unrecognized format code Explanation: The format code is not recognized. User Action: Examine the format string for invalid format code. The format string may be supplied in the environment variable or it can be hard-coded.
16.318 – UNSUPP_HW_CPUCNT
unsupported hardware CPU count Explanation: The system CPU count (number of processors in the computer) is not supported by this version. User Action: Contact your Customer service center. There may be a version that supports your configuration.
16.319 – UNSUPP_HW_EV6
unsupported hardware DECchip 21264 or variant Explanation: The hardware DECchip 21264 or variant (EV6 microprocessor) is not supported by this version. User Action: Contact your Customer service center. There may be a version that supports your hardware.
16.320 – UNSUPP_HW_EV7
unsupported hardware DECchip 21364 or variant Explanation: The hardware DECchip 21364 or variant (EV7 microprocessor) is not supported by this version. User Action: Contact your Customer service center. There may be a future version that supports your hardware.
16.321 – UNSUPP_HW_EVX
unsupported hardware DECchip variant Explanation: The hardware DECchip variant microprocessor is not supported by this version. User Action: Contact your Customer service center. There may be a version that supports your hardware.
16.322 – UNSUPP_HW_I64
unsupported hardware processor model Explanation: The Intel Itanium processor family or model is not supported by this version. User Action: Contact your Customer service center. There may be a version that supports your hardware.
16.323 – VALNOTVALID
value block is not valid Explanation: This warning message is returned if the caller has specified the VALBLK flag in the flags argument to the service to request locks. Note that the lock has been successfully granted despite the return of this warning message. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.
16.324 – VALREQ
missing qualifier or keyword value - supply all required values Explanation: A keyword or qualifier that requires a value was specified without a value. User Action: Specify the required value, and retry the command.
16.325 – VASFULL
virtual address space full Explanation: An attempt to map a section of a file or a shared memory region failed because (1) there is not enough address space to map all the bytes, or (2) the specific address range specified is already allocated. User Action: Contact your Oracle support representative for assistance.
16.326 – VIRTUALALLOCERR
Error encountered while reserving/commiting pages Explanation: A system error was encountered while commiting or reserving a block of pages in the virtual address space User Action: Examine the secondary message to determine the reason for the failure.
16.327 – VIRTUALFREEERR
Error encountered while releasing/de-commiting pages Explanation: A system error was encountered while de-commiting or releasing a block of pages in the virtual address space User Action: Examine the secondary message to determine the reason for the failure.
16.328 – WAITPID_ERR
an error was returned by the waitpid function Explanation: An error was returned by the 'waitpid' function. User Action: Please refer to the reference pages for 'waitpid' to interpret the meaning of the errno returned by this function.
16.329 – WASCLR
normal successful completion Explanation: The specified event flag was previously 0. User Action: No action is required.
16.330 – WASSET
normal successful completion Explanation: The specified event flag was previously 1. User Action: No action is required.
16.331 – WORK_DEV
work file <str> must be on random access local device Explanation: Work files must be specified for random access devices that are local to the CPU on which the sort is being performed (that is, not on a node in a network). Random access devices are disk devices. User Action: Specify the correct device.
16.332 – WRITERR
write error Explanation: An error occurred during a write operation to a file, mailbox, or socket. User Action: Examine the secondary messages to determine the reason for the failure.
16.333 – WRITE_ERR
an error was returned by the write function Explanation: An error was returned by the 'write' function. User Action: Please refer to the reference pages for 'write' to interpret the meaning of the errno returned by this function.
16.334 – WRONGSTATE
invalid state for requested operation Explanation: A software protocol error has occurred. The error might be a value specified for a system function that is not valid at this time or a function that cannot be used at this time. For example, the error could be an attempt to read from an I/O channel that is closed. The identical read call would be valid after the channel was open. User Action: Determine the system call that returned the error. Verify that the service is being called correctly.
16.335 – WRONUMARG
wrong number of arguments, <num>, to <str> Explanation: A string facility entry is called with an incorrect number of arguments. User Action: A user who calls the string facility directly should check the argument list in the call.
16.336 – XVALNOTVALID
extended value block is not valid Explanation: This warning occurs as the result of a programming decision. The program read the Extended Lock Value Block, but the previous writer wrote a Short Lock Value Block. This warning message is returned if the caller has specified the XVALBLK flag in the flags argument to the service to request locks. Note that the lock has been successfully granted despite the return of this warning message. User Action: This error message indicates a possible error in the locking protocols. Contact your Oracle support representative for assistance.