Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
Cause: The time to wait on a lock in a distributed transaction has been exceeded. This time is specified in the initialization parameter DISTRIBUTED_LOCK_TIMEOUT.
Action: This situation is treated as a deadlock and the statement was rolled back. To set the time-out interval to a longer interval, adjust the initialization parameter DISTRIBUTED_LOCK_TIMEOUT, then shut down and restart the instance.
Cause: There was a network failure or a remote failure during the two-phase commit.
Action: Notify the database administrator. The remote databases will automatically resynchronize when the failure is repaired.
Cause: A session at the same site with the same global transaction identification failed.
Action: No action is necessary; the transaction will automatically recover.
Cause: There was some error in a remote transaction at the named database link.
Action: More descriptive messages will follow. Correct the problem specified in the following messages and retry the operation.
Cause: There was a network failure or a remote failure during the two-phase commit.
Action: Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired.
Cause: There was a network failure or a remote failure in the two-phase commit.
Action: Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired. Monitor the DBA_2PC_INDOUBT and DBA_2PC_INCONSISTENT tables for the outcome and resubmit the transaction, if necessary.
Cause: A failure during a distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent with others, the transaction must roll back to a savepoint or roll back entirely.
Action: Roll back to a savepoint or roll back the entire transaction and resubmit the rolled-back statements.
Cause: There was a two-phase commit protocol error.
Action: The transaction may automatically recover. Monitor the DBA_2PC_INDOUBT and DBA_2PC_INCONSISTENT tables to determine the resolution. Enter the transaction again, if necessary. Contact customer support, if necessary.
Cause: An internal error in the two-phase recovery protocol occurred.
Action: Contact customer support.
Cause: A COMMIT FORCE was attempted on a transaction, but the transaction with LOCAL_TRAN_ID or GLOBAL_TRAN_ID was not found in the DBA_2PC_INDOUBT table in prepared state.
Action: Check the DBA_2PC_INDOUBT table to ensure the proper transaction ID is used and attempt the commit again.
Action: Do not use this special Comment unless working with customer support.
Cause: An attempt was made to join tables in different remote databases in a SELECT... FOR UPDATE statement.
Action: Joined tables in a SELECT statement with the FOR UPDATE clause must reside at the same database. Simplify the SELECT... FOR UPDATE statement so that it joins only tables in the same database.
Cause: An attempt was made to lock more than one table in different remote databases in a LOCK TABLE statement. Tables in a LOCK TABLE statement must reside at the same database.
Action: Issue multiple LOCK TABLE commands.
Cause: A database link at the coordinator point no longer points to the expected database. The database link may have been redefined, or a different database may have been mounted.
Action: Check the database link at the coordinator point to see if it was redefined. If so, contact the database administrator for the remote database to check whether the link still references a valid database. If the link changed, recreate it to reference a valid database at the remote site.
Cause: An Oracle error message was received from a remote database link.
Action: Refer to the preceding messages. Correct the problem mentioned in the preceding messages and try the operation again.
Cause: One of the following unsupported operations was attempted:
Action: Simplify the remote update statement.
Cause: The option specified for ALTER SYSTEM is not supported.
Action: Refer to Oracle8 Server SQL Reference for the proper syntax of the ALTER SYSTEM command.
Cause: A character string literal was expected, but not found, in the ALTER SYSTEM SET MTS_DISPATCHERS command.
Action: Place the string literal containing the dispatcher's specification in the ALTER SYSTEM SET MTS_DISPATCHERS command.
Cause: A failure occurred, probably in a trigger or stored procedure with multiple remote updates. Some sites in the transaction may be inconsistent, so the previous Oracle call cannot be executed, and the transaction cannot be committed.
Action: Roll back to a previous savepoint or to the beginning of the transaction. Then resubmit the rolled-back statements.
Cause: A severe error, a disconnect or fatal Oracle error, was received from the given database link. See the accompanying messages for a more detailed description of the problem.
Action: Contact the remote system administrator to determine the cause of the remote problem and the estimated time of the problem's resolution.
Cause: A remote mapping of the statement is required but cannot be done because the parameter GLOBAL_NAMES is not set to TRUE.
Action: Issue the statement ALTER SESSION SET GLOBAL_NAMES = TRUE, if possible.
Cause: The remote database does not support the named capability in the context in which it was used.
Action: Simplify the SQL statement.
Cause: Oracle could not load the capability table from the named remote database.
Action: Contact customer support concerning the remote SQL*Connect product.
Cause: This error should never occur between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.
Action: Upgrade the older release.
Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.
Action: Perform the operation without specifying a sequence number.
Cause: A COMMIT or ROLLBACK was attempted from a session other than the parent of a distributed transaction.
Action: Only the parent session can issue a COMMIT or ROLLBACK.
Cause: All referenced sequences must be located on the same node as the updated table or the long column.
Action: Correct the problem and then reissue the statement.
Cause: All tables returning values of long columns in a SELECT statement must be located at the same node.
Action: Correct the problem, then reissue the statement.
Cause: An invalid value was used.
Cause: A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch. That is, a call to UPI2EN was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager.
Action: Contact customer support.
Cause: A transaction is active or a cursor is open on the database link.
Action: Before closing a database link, you must first close all cursors and then end all transactions that use it.
Cause: An attempt was made to use a database link that is not currently open.
Action: Resolve network problems or contact the remote database administrator to determine if the remote database's problem has been fixed. Contact the local database administrator to determine if network problems have been resolved. Wait until the link is open and try the operation again.
Cause: An attempt was made to create a database link with the same name as the current database.
Action: This database link needs a trailing qualifier to make the name unique. These qualifiers are operating system-specific. See your operating system-specific Oracle documentation for more information about creating database links.
Cause: The database name supplied contains an invalid character. For example, there can be no periods, semicolons, single quotes, double quotes, blanks, or non-printable characters in the database name. See Oracle8 Server Administrator's Guide for naming rules.
Action: Specify a valid database name.
Cause: The complete database name was not given
Action: Specify the full database name.
Cause: The database link attempted to connect to a database with a different name. The name of the database link must be the same name as the name of the database.
Action: Create a database link with the same name as the database to which it connects.
Cause: The name of the database or database link is too long. Database and database link names can be no longer than 128 characters.
Action: Specify the correct database or database link name or specify a name with fewer characters.
Cause: In a Parallel Server environment, a database link that loops back to the same instance is being used, and one session is trying to convert a lock that was obtained by the other session.
Action: Obtain a more restrictive lock first. For example if session 1 needs a SHARE lock, and session 2 needs an EXCLUSIVE lock, make sure that the EXCLUSIVE lock is obtained first. Otherwise, use the same session to access the object.
Cause: The distributed database option is not installed at this site, so the requested operation is not possible.
Action: Contact Oracle Corporation about obtaining the distributed database option.
Cause: COMMIT was issued in a session that is not the two-phase commit global coordinator.
Action: Issue commits only at the global coordinator.
Cause: This is an internal error.
Action: Contact Oracle Worldwide Support.
Cause: The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back.
If the transaction aborted at a remote site, only ORA-02091 will be seen. If the transaction aborted at the host site, then both ORA-02091 and ORA-02092 will be seen.
Action: Complete the current transaction and then do the operation required.
Cause: The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back.
If the transaction aborted at a remote site, only ORA-02091 will be seen. If the transaction aborted at the host site, then both ORA-2091 and ORA-2092 will be seen.
Action: Add a rollback segment and do the operation again.
Cause: The value of the initialization parameter specified is greater than allowed on this port.
Action: Use the default value or reduce it to less than the maximum.
Cause: The replication option was not installed at this site. Updatable snapshots, deferred remote procedure calls, and other replication features were, therefore, unavailable.
Action: Install the replication option. The replication option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle sales representative if the replication option needs to be purchased.
Cause: Specified initialization parameter is not modifiable with this option.
Action: Check the DBA guide for information about under what scope the parameter may be modified.
For more information about modifying an initialization parameter, see the index entry on "initialization parameters, altering" in Oracle8 Server SQL Reference.
Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command.
Action: Check the DBA guide for information about under what scope the parameter may be modified. For more information about modifying an initialization parameter, see the index entry on "initialization parameters, altering" in Oracle8 Server SQL Reference.
Cause: Though the initialization parameter is modifiable, an invalid value was assigned to the parameter.
Action: Check the DBA guide for the range of acceptable values for this parameter.
Cause: An incorrect index-table (:I) syntax was encountered.
Action: This syntax is for Oracle internal use only.
The messages in this range have the same cause and action as listed in Chapter 17, "Precompiler Messages". For example, ORA-2100 is the same as SQL-2100.
This section lists some of the messages generated when SQL statements are parsed by the Oracle Server.
Cause: A valid tablespace name does not follow ALTER TABLESPACE.
Action: Specify a valid tablespace name following ALTER TABLESPACE.
Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE in an ALTER TABLESPACE statement.
Action: The user must either specify no option following OFFLINE or one of these options: NORMAL or IMMEDIATE.
Cause: An invalid option was specified after ALTER TABLESPACE.
Action: Use one of the valid options, such as ADD DATAFILE, RENAME DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE, BEGIN BACKUP, or END BACKUP.
Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, FREELISTS, FREELIST GROUPS, or PCTINCREASE was specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.
Action: Check syntax, specify only valid options, and try again.
Cause: No valid ALTER CLUSTER options were specified.
Action: Specify one or more valid options, such as PCTFREE, PCTUSED, SIZE, INITRANS, MAXTRANS, or STORAGE.
Cause: No STORAGE options were specified following the keyword STORAGE.
Action: Check syntax, specify one or more valid STORAGE options, and try again.
Cause: The SHARED option was specified more than once in a CREATE DATABASE statement.
Action: Only specify the SHARED option once.
Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.
Action: Specify SHARED or EXCLUSIVE, but not both.
Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement more than once.
Action: Only specify the EXCLUSIVE option once.
Cause: Partition not found the base object.
Action: Enter the correct partition specification and retry the operation.
Cause: An encoded password string does not follow the VALUES clause.
Action: Place a proper encoded password string after the VALUES clause.
Cause: A valid tablespace name does not follow DEFAULT TABLESPACE.
Action: Place a valid tablespace name after DEFAULT TABLESPACE and try again.
Cause: A valid tablespace name does not follow TEMPORARY TABLESPACE.
Action: Place a valid tablespace name after TEMPORARY TABLESPACE and try again.
Cause: No options were specified.
Action: Specify at least one ALTER USER option and try again.
Cause: An option other than PCTFREE, INITRANS, MAXTRANS, NOSORT, STORAGE, or TABLESPACE was specified.
Action: Specify one of the valid CREATE INDEX options and try again.
Cause: The parameter file specified GC_*PARAMETERS that allow locks to be released by the LCK process when not in use. This mode required additional support in DLM that was not available.
Action: Specify configuration parameters that do not require the additional function.
For more information about the distributed lock manager(DLM), see the index entry on "LCK" in Oracle8 Server Concepts and the index entries on "distributed lock manager" and on "distributed lock manager, LCKn process" in Oracle8 Parallel Server Concepts & Administration.
Cause: An attempt was made to define a column of type LONG for an index only table.
Action: Do not use columns of type LONG in index only tables.
Cause: A number does not follow MAXLOGFILES.
Action: Specify a number after MAXLOGFILES and try again.
Cause: A number does not follow MAXDATAFILES.
Action: Specify a number after MAXDATAFILES and try again.
Cause: A number does not follow FREELIST GROUPS.
Action: Specify a number after FREELIST GROUPS and try again.
Cause: The CREATE DATABASE statement contains more than one DATAFILE clause.
Action: Specify at most one DATAFILE clause and try again.
Cause: An invalid CREATE DATABASE option is present.
Action: Specify only valid CREATE DATABASE options and try again.
Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.
Action: Specify either of these two options, but not both, and try again.
Cause: The CREATE DATABASE statement contains more than one LOGFILE clause.
Action: Specify at most one LOGFILE clause and try again.
Cause: A number does not follow the FREELISTS storage option of the CREATE TABLE or CREATE INDEX statement.
Action: Specify a number after FREELISTS and try again.
Cause: An attempt was made to specify the FREELISTS storage option when performing an operation other than CREATE TABLE or CREATE INDEX.
Action: Check the syntax of the statement, remove this option, then re-execute the statement.
Cause: An attempt was made to specify the FREELIST GROUPS storage option. This option may be specified only when using the CREATE TABLE command and when the ALLOW_FREELIST_GROUPS parameter is specified in the initialization parameter file.
Action: Retry the statement without the FREELIST GROUPS storage option or set the ALLOW_FREELIST_GROUPS parameter in the initialization parameter file.
Cause: A number does not follow MAXLOGHISTORY.
Action: Specify a number after MAXLOGHISTORY.
Cause: The PUBLIC keyword was specified when disabling a thread.
Action: Check the syntax of the command and retry.
Cause: Something other than INCLUDING CONTENTS was found following the tablespace name, or text other than CASCADE CONSTRAINTS was found following INCLUDING CONTENTS.
Action: Place either nothing or only INCLUDING CONTENTS after the tablespace name, or place either nothing or only CASCADE CONSTRAINTS after INCLUDING CONTENTS and try again.
Cause: A thread number must be specified after THREAD keyword.
Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, a valid rollback segment name does not follow ROLLBACK SEGMENT.
Action: Place a valid rollback segment name after ROLLBACK SEGMENT and try again.
Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
Action: Specify one of the valid options, TABLESPACE or STORAGE, and try again.
Cause: A group number must be specified after GROUP keyword.
Action: Check the syntax of the command, specify a group number after GROUP, and retry it.
Cause: There is a syntax error in the user's statement.
Action: Correct the syntax as indicated and try again.
Cause: There was a syntax error in the user's statement.
Action: Correct the syntax as indicated.
Cause: An invalid option follows CREATE TABLESPACE.
Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, or OFFLINE, and try again.
Cause: A word other than TO follows ROLLBACK [WORK].
Action: Place either nothing or TO SAVEPOINT after ROLLBACK [WORK] and try again.
Cause: A valid savepoint name does not follow ROLLBACK [WORK] TO [SAVEPOINT].
Action: Place a savepoint name following TO [SAVEPOINT] and try again.
Cause: There was a syntax error in the user's statement.
Action: Correct the syntax as indicated.
Cause: In a revoke statement, a resource quota was specified.
Action: Specify the resource privilege without the quota and try again.
Cause: A token other than WORK follows COMMIT.
Action: Place either nothing or WORK after COMMIT and try again.
Cause: An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked.
Action: Use a separate GRANT or REVOKE statement for the resource quota privilege and try again.
Cause: In a GRANT or REVOKE statement, an attempt was made to grant a tablespace quota above the upper limit.
Action: Grant a smaller tablespace quota and try again.
Cause: The GRANT or REVOKE statement specifying a tablespace quota requires the ON tablespace clause.
Action: Correct the syntax and try again.
Cause: The keyword TABLES is expected following DROP CLUSTER cluster name INCLUDING.
Action: Place the keyword TABLES after INCLUDING and try again.
Cause: There is a syntax error in the SET TRANSACTION statement.
Action: Correct the syntax error and retry the statement.
Cause: The storage parameter PCTINCREASE was specified in a CREATE or ALTER ROLLBACK SEGMENT command.
Action: Retry the command without the PCTINCREASE clause.
Cause: There is a syntax error in an event specification.
Action: Check syntax and spelling and try again.
Cause: The object type was inconsistent with tablespace contents.
Action: Create the object in a different tablespace, or change the user defaults.
For more information about auditing schema objects, see the index entry on "AUDIT command" in Oracle8 Server SQL Reference.
Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once.
Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
For more information about the parameters of CREATE TABLESPACE, see the index entry on "CREATE TABLESPACE" in Oracle8 Server SQL Reference.
Cause: In a CREATE TABLESPACE statement, more than one DATAFILE clause was specified.
Action: Merge the DATAFILE clauses into a single clause specifying multiple files and try again.
Cause: In a CREATE TABLESPACE statement, the ONLINE and/or OFFLINE options were specified more than once.
Action: Specify either ONLINE or OFFLINE, but not both, and try again.
Cause: A CREATE TABLESPACE statement has no DATAFILE clause.
Action: Specify the missing DATAFILE clause and try again.
Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
Action: Remove either the PUBLIC or the WITH GRANT OPTION clause and try again.
Cause: An attempt was made to reference a sequence in a FROM list. This is not permitted. A sequence can only be referenced in a SELECT list.
Action: Check the statement syntax, correct the reference, and try again.
Cause: An attempt was made to create a table in a cluster that already contains 32 tables. No more than 32 tables may be stored in a cluster.
Action: Do not try to cluster more than 32 tables.
Cause: The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. This option may be specified only when the object is created.
Action: Remove the INITIAL option and try again.
Cause: An attempt was made to grant or revoke an invalid privilege on a view.
Action: Do not attempt to grant or revoke the privileges ALTER, INDEX, or REFERENCES on views.
Cause: An attempt was made to grant or revoke an invalid privilege on a sequence.
Action: Do not attempt to grant or revoke the privileges DELETE, INDEX, INSERT, UPDATE, REFERENCES, or EXECUTE on sequences.
Cause: INITRANS is specified more than once.
Action: Specify INITRANS only once and try again.
Cause: The INITRANS value is not an integer between 2 and 255, or it is not less than or equal to the MAXTRANS value.
Action: Specify a valid INITRANS value and try again.
Cause: The MAXTRANS option is specified more than once.
Action: Specify MAXTRANS only once and try again.
Cause: The MAXTRANS value is not an integer between 2 and 255, or it is not greater than or equal to the INITRANS value.
Action: Specify a valid MAXTRANS value and try again.
Cause: No ALTER TABLE option was specified.
Action: Specify at least one ALTER TABLE option and try again.
Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.
Action: Specify an appropriate value for the option and try again.
Cause: The PCTFREE option was specified more than once.
Action: Specify the PCTFREE option only once and try again.
Cause: The PCTUSED option was specified more than once.
Action: Specify the PCTUSED option only once and try again.
Cause: The BACKUP option to ALTER TABLE was specified more than once.
Action: Specify the BACKUP option only once and try again.
Cause: There is more than one TABLESPACE clause in one of the following statements: GRANT/REVOKE RESOURCE, CREATE TABLE, CREATE INDEX, CREATE/DROP TABLESPACE, CREATE CLUSTER, and CREATE ROLLBACK SEGMENT.
Action: Check the statement syntax, specify only one TABLESPACE clause, and try again.
Cause: A valid tablespace name is not present where required in one of the following statements: CREATE TABLE, CREATE INDEX, CREATE/DROP TABLESPACE, CREATE CLUSTER, and CREATE ROLLBACK SEGMENT.
Action: Check the statement syntax, specify a valid tablespace name where required, and try again.
Cause: A storage option, such as INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE, was specified more than once.
Action: Specify storage options only once and try again.
Cause: The specified value must be an integer.
Action: Specify an appropriate integer value and try again.
Cause: The specified value must be an integer.
Action: Specify an appropriate integer value and try again.
Cause: The specified value must be a positive integer that is less than or equal to MAXEXTENTS.
Action: Specify an appropriate integer value and try again.
Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS.
Action: Specify an appropriate integer value and try again.
Cause: The specified value must be a positive integer.
Action: Specify an appropriate integer value and try again.
Cause: The specified value must be an integer.
Action: Chose an appropriate integer value for the OPTIMAL storage option.
Cause: An attempt was made to GRANT or REVOKE an invalid privilege on a table.
Action: Do not attempt to GRANT or REVOKE the EXECUTE privilege on tables.
Cause: An attempt was made to GRANT or REVOKE an invalid privilege on a procedure, function, or package.
Action: Do not attempt to GRANT or REVOKE any privilege other than EXECUTE on procedures, functions, or packages.
Cause: The value specified for MAXEXTENTS is too large for the database block.
Action: Specify a value for MAXEXTENTS that is smaller than the number given in the message.
Cause: A cluster name was not properly formed.
Action: Check the rules for forming object names and enter an appropriate cluster name.
Cause: The SIZE option is specified more than once.
Action: Specify the SIZE option only once and try again.
Cause: The specified value must be an integer number of bytes.
Action: Specify an appropriate integer value and try again.
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE was specified in an ALTER CLUSTER statement.
Action: Specify only valid options in the ALTER CLUSTER statement and try again.
Cause: An invalid option was specified in the statement.
Action: Check the syntax of the ALTER DATABASE command. Specify only valid options in the ALTER DATABASE statement and try again.
Cause: A mode other than SHARED or EXCLUSIVE follows the keyword MOUNT in an ALTER DATABASE statement.
Action: Specify either SHARED, EXCLUSIVE, or nothing following the keyword MOUNT in the ALTER DATABASE statement and try again.
Cause: A mode other than NORMAL or IMMEDIATE follows the keyword CLOSE in an ALTER DATABASE statement.
Action: Specify either NORMAL, IMMEDIATE, or nothing following the keyword CLOSE in the ALTER DATABASE statement and try again.
Cause: The log table to be added is a duplicate of another.
Action: Do not add this change log to the system; check that the replication product's system tables are consistent.
Cause: The table to be altered is already a change log for another table.
Action: Do not log changes to the specified base table to this table; check that the replication product's system tables are consistent.
Cause: In a LOGFILE, DATAFILE, or RENAME clause, a character string literal was expected, but not found, in a filename list.
Action: Specify filenames using character string literals and try again.
Cause: An integer file size does not follow SIZE in a LOGFILE or DATAFILE file list.
Action: Specify an appropriate file size following the keyword SIZE and try again.
Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing filenames does not equal the number of new filenames.
Action: Make sure a new filename corresponds to each existing filename and try again.
Cause: The sequence to be dropped is still referenced by other objects.
Action: Make sure the sequence name is correct or drop the constraint or object that references the sequence.
Cause: A number does not follow OBJNO or TABNO.
Action: Specify a number after OBJNO or TABNO.
Cause: There was an error in the extent storage clause.
Action: Respecify the storage clause using the correct syntax and retry the command.
Cause: No options were specified after ALTER INDEX.
Action: Specify the INITRANS, MAXTRANS, or STORAGE option in the ALTER INDEX statement and try again.
Cause: An option other than INITRANS, MAXTRANS, or STORAGE was specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.
Action: Specify only valid options and try again.
Cause: An option other than STORAGE was found.
Action: Specify the STORAGE option and try again.
Cause: A rollback segment name was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.
Action: Place a rollback segment name after SEGMENT and try again.
Cause: A character string literal was expected, but not found, following the ALTER SESSION SET EVENTS command.
Action: Place the string literal containing the EVENTS text after the keyword EVENTS and try again.
Cause: The option SET EVENTS was expected, but not found, following the ALTER SESSION command.
Action: Place the SET EVENTS option after the ALTER SESSION command and try again.
Cause: An option other than SET EVENTS was found following the ALTER SESSION command.
Action: Specify the SET EVENTS option after the ALTER SESSION command and try again.
Cause: A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the operating system-specific maximum number of log file members.
Action: Specify a valid number after MAXLOGMEMBERS.
Cause: The constraint name is missing or invalid.
Action: Specify a valid constraint name and try again.
Cause: A subquery is not allowed at this point in the statement.
Action: Remove or relocate the subquery and try again.
Cause: The specified search condition for the check constraint is not properly ended.
Action: Check and correct the search condition's syntax. Then retry the operation.
Cause: A constraint specification is not allowed at this point in the statement.
Action: Remove or relocate the constraint specification and try again.
Cause: A default-value expression is not allowed for the column at this point in the statement.
Action: Remove or relocate the default-value expression and try again.
Cause: A NOT NULL specification conflicts with the NULL default value.
Action: Remove either the NOT NULL or the DEFAULT NULL specification and try again.
Cause: The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list.
Action: Ensure that the referencing columns match the referenced columns.
Cause: The number of columns in the key list exceeds the maximum number.
Action: Reduce the number of columns in the list.
Cause: A duplicate or conflicting NULL and/or NOT NULL was specified.
Action: Remove one of the conflicting specifications and try again.
Cause: A duplicate unique or primary key was specified.
Action: Remove the duplicate specification and try again.
Cause: Two or more primary keys were specified for the same table.
Action: Remove the extra primary keys and try again.
Cause: A unique or primary key was specified that already exists for the table.
Action: Remove the extra key and try again.
Cause: An attempt to alter a column's datatype caused a type-checking error because the new datatype conflicted with the existing column's default value expression.
Action: Remove the default value expression or do not alter the column's datatype, and try again.
Cause: The required datatype for the column is missing.
Action: Specify the required datatype and try again.
Cause: The specified constraint name is not unique.
Action: Specify a unique constraint name for the constraint and try again.
Cause: The datatype of the referenced column is not defined as yet.
Action: Make sure that the datatype of the referenced column is defined before referencing it.
Cause: An attempt was made to drop or truncate a table with unique or primary keys referenced by foreign keys enabled in another table.
Action: Before dropping or truncating the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command:
select constraint_name, table_name, status
from user_constraints
where r_constraint_name in (
select constraint_name from user_constraints where table_name
='tabnam');
Cause: An attempt was made to perform an operation on a pair of columns with incompatible datatypes.
Action: Specify a compatible datatype for the referencing column.
Cause: The referenced table does not have a primary key.
Action: Do not attempt to reference the table using a unique key, or create a unique key for the table.
Cause: An attempt was made to define a key column of datatype LONG. This is not allowed.
Action: Change the datatype of the column or remove the LONG column from the key, and try again.
Cause: An attempt was made to reference a unique or primary key in a table with a CREATE or ALTER TABLE statement when no such key exists in the referenced table.
Action: Add the unique or primary key to the table or find the correct names of the columns with the primary or unique key, and try again.
Cause: An attempt was made to reference a table using a constraint that does not exist.
Action: Check the spelling of the constraint name or add the constraint to the table, and try again.
Cause: A constrained column cannot be defined as datatype LONG. This is not allowed.
Action: Change the datatype of the column or remove the constraint on the column, and try again.
Cause: A unique or primary key referenced by foreign keys cannot be dropped.
Action: Remove all references to the key before dropping it.
Cause: A referential constraint was specified more than once. This is not allowed.
Action: Remove the duplicate specification.
Cause: An attempt was made to specify a referential constraint that already exists. This would result in duplicate specifications and so is not allowed.
Action: Be sure to specify a constraint only once.
Cause: The type of the evaluated default expression is incompatible with the datatype of the column.
Action: Modify the default expression or change the column's datatype, and try again.
Cause: An invalid sequence name was specified.
Action: Check syntax and spelling, specify a valid sequence name, and try again.
Cause: Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications.
Action: Remove one of the conflicting specifications and try again.
Cause: Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified.
Action: Remove one of the conflicting specifications and try again.
Cause: Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified.
Action: Remove one of the conflicting specifications and try again.
Cause: Duplicate or conflicting CACHE and/or NOCACHE clauses were specified.
Action: Remove one of the conflicting specifications and try again.
Cause: Duplicate or conflicting ORDER and/or NOORDER clauses were specified.
Action: Remove one of the conflicting specifications and try again.
Cause: An attempt was made to alter a starting sequence number. This is not allowed.
Action: Do not try to alter a starting sequence number.
Cause: A duplicate INCREMENT BY clause was specified.
Action: Remove the duplicate specification and try again.
Cause: A duplicate START WITH clause was specified.
Action: Remove the duplicate specification and try again.
Cause: No ALTER SEQUENCE option was specified.
Action: Check the syntax. Then specify at least one ALTER SEQUENCE option.
Cause: The specified sequence number reference, CURRVAL or NEXTVAL, is inappropriate at this point in the statement.
Action: Check the syntax. Then remove or relocate the sequence number.
Cause: A mode other than RESETLOGS was specified in an ALTER DATABASE OPEN statement. RESETLOGS is the only valid OPEN mode.
Action: Remove the invalid mode from the statement or replace it with the keyword RESETLOGS, and try again.
Cause: The specified sequence does not exist, or access privilege is required for this operation. Also, this error can occur if attempting to access a remote sequence through an invalid or non-existent database link.
Action: Check spelling of the sequence name or obtain the required access privilege. If necessary, create the sequence. All remote sequences accessed in a distributed transaction must be on the same node.
Cause: The value or values attempted to be entered in a field or fields violate a defined check constraint.
Action: Enter values that satisfy the constraint.
Cause: An attempt was made to INSERT or UPDATE a foreign key value. The result was a value that is not in the parent key.
Action: UPDATE to or INSERT a value that is in the parent key.
Cause: An attempt was made to delete a row that is referenced by a foreign key.
Action: It is necessary to DELETE or UPDATE the foreign key before changing this row.
Cause: An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that had no complying values.
Action: Retry the ALTER TABLE statement, specifying a check constraint on a table containing complying values. For more information about ALTER TABLE, see the index entry on "ALTER TABLE" in Oracle8 Server SQL Reference.
Cause: An attempt was made via an ALTERTABLE statement to add a referential constraint to a populated table that had no matching parent values.
Action: Retry the ALTER TABLE statement, specifying a valid primary key in a parent table.
Cause: An attempt was made via a CREATE or ALTER TABLE statement to specify more than one ENABLE and/or DISABLE clause for a given constraint.
Action: Only one ENABLE or DISABLE clause may be specified for a given constraint.
Cause: An ALTER TABLE command with an ENABLE CONSTRAINT clause failed because the table contains values that do not satisfy the constraint.
Action: Make sure that all values in the table satisfy the constraint before issuing an ALTER TABLE command with an ENABLE CONSTRAINT clause. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the index entries on "ALTER TABLE" and on "ENABLE clause" in Oracle8 Server SQL Reference.
Cause: An alter table disable constraint failed because the table has foreign keys that are dependent on the constraint.
Action: Either disable the foreign key constraints or use a DISABLE CASCADE command.
Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has orphaned child records.
Action: Make sure that the table has no orphaned child records before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the index entries on "ALTER TABLE" and on "ENABLE clause" in Oracle8 Server SQL Reference.
Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has duplicate key values.
Action: Make sure that the table has no duplicate key values before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the index entries on "ALTER TABLE" and on "ENABLE clause" in Oracle8 Server SQL Reference.
Cause: A number was not specified for the value of OIDGENERATORS.
Action: Specify a number after OIDGENERATORS.
Cause: A number greater than 255 was specified for the value of OIDGENERATORS.
Action: Make sure the number specified for OIDGENERATORS does not exceed 255.
Cause: An invalid or missing type name was entered in a statement.
Action: Enter a valid type name in the statement and retry the operation.
Cause: An attempt was made to drop or replace a type that has dependents.
Action: Drop all type(s) and table(s) depending on the type, then retry the operation or use the FORCE option.
Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either:
Action: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation.
Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE) on a type.
Action: GRANT or REVOKE only the EXECUTE privilege on types.
Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist).
Action: Drop the dependents first before creating the type, or do not create the type.
Cause: An attempt was made to ALTER with REPLACE option a type that is not valid.
Action: Use the CREATE OR REPLACE TYPE command to modify the type.
Cause: An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column.
Action: Remove the invalid option from column specification and retry the operation.
Cause: An attempt was made to access the attributes of a NULL object instance.
Action: Ensure that the object instance is non-NULL before accessing.
Cause: The attributes in the object type column exceeded the maximum number of columns allowed in a table.
Action: Specify fewer attributes for the object type and retry the operation.
Cause: An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents.
Action: No need to perform this operation.
Cause: An attempt was made to create extent table for VALUE Object Type.
Action: Specify object type when creating extent table.
Cause: The specified object type contains a nested attribute whose type is non-queryable.
Action: Use an object type with queryable attribute types.
Cause: The number of arguments specified for the default constructor does not match the number of attributes of the object type.
Action: Specify the correct number of arguments for the default constructor and retry the operation.
Cause: An error occurred while creating the storage table for the specified nested table column.
Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support.
Cause: An error occured while performing DML on the storage table of the nested table column.
Action: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Support.
Cause: More than one column was selected in the THE subquery.
Action: Specify only one column in the SELECT list of the THE subquery and retry the operation.
Cause: An attempt was made to create an index on a non-indexable column.
Action: Change the column datatype or do not create the index on a column whose datatype is one of VARRAY, nested table, object, LOB, or REF.
Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF.
Action: Change the column datatype or remove the constraint. Then retry the operation.
Cause: An attempt was made to specify the data type in the column constraint specification of an object table.
Action: Remove data type specification and retry the operation.
Cause: An attempt was made to create a constraint on a column posessing a non-constrainable datatype -- VARRAY, nested table, object, LOB, FILE, or REF.
Action: Change the column datatype, or remove the constraint.
Cause: An attempt was made to create an index on an attributes of an object type column.
Action: Do not specify the index on the attribute.
Cause: An attempt was made to create a constraint on an attribute of an object type column.
Action: Remove the constraint or change the object type.
Cause: A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column.
Action: Declare a datatype for the column.
Cause: An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE.
Action: Remove the CLUSTER column or change the datatype of the column.
Cause: An attempt was made to extract an attribute of an object type column.
Action: Change the object type for the column and retry the operation.
Cause: An attempt was made to use dotted notation on a non-object type column; that is, "a.b.c" where "a" is not an object type.
Action: Either change the column type to an object type or do not perform this operation.
Cause: A column constraint was not specified.
Action: Remove the column specification or specify a column constraint. Then retry the operation.
Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column.
Action: Remove the PACKED or UNPACKED keyword in the column specification and retry the operation.
Cause: An attempt was made to specify an UNPACKED column within a packed table.
Action: Remove the UNPACKED keyword in the column specification.
Cause: Attempt to refer to an object type attribute that is of a non-queryable type in SQL.
Action: Change attribute type to a SQL-queryable type, or reference the attribute through a 3GL.
Cause: The use of the ALTER...REPLACE statement on a valid type caused a compilation error.
Action: Use the ALTER...REPLACE statement to replace the type with a valid type which does not cause compilation errors.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|