Skip Headers
Oracle® Database Error Messages
10g Release 2 (10.2)
Part Number A14219-01
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
 

13 ORA-12700 to ORA-19380

ORA-12700: invalid NLS parameter value (string)
Cause: An invalid or unknown NLS configuration parameter was specified.
Action: none
ORA-12701: CREATE DATABASE character set is not known
Cause: The character set specified when creating the database is unknown.
Action: none
ORA-12702: invalid NLS parameter string used in SQL function
Cause: An unknown parameter name or invalid value is specified in a NLS parameter string.
Action: none
ORA-12703: this character set conversion is not supported
Cause: The requested conversion between two character sets in the CONVERT function is not implemented
Action: none
ORA-12704: character set mismatch
Cause: One of the following:

- The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set.

- An nlsparams operand is not in the database character set.

- String data with character set other than the database character set is passed to a built-in function not expecting it.

- The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.

- A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted.

- A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column.

- An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.

Action: none
ORA-12705: Cannot access NLS data files or invalid environment specified
Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located.
Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify the correct directory path/values in the environment variables.
ORA-12706: this CREATE DATABASE character set is not allowed
Cause: It is not allowed to create a database on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.
Action: none
ORA-12707: error while getting create database NLS parameter string
Cause: Internal error
Action: none
ORA-12708: error while loading create database NLS parameter string
Cause: Internal error
Action: none
ORA-12709: error while loading create database character set
Cause: Internal error
Action: none
ORA-12710: CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: none
ORA-12711: this CREATE CONTROLFILE character set is not allowed
Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.
Action: none
ORA-12712: new character set must be a superset of old character set
Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.
Action: Specify a superset character set.
ORA-12713: Character data loss in NCHAR/CHAR conversion
Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.
Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE.
ORA-12714: invalid national character set specified
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set
Action: Ensure that the specified national character set is valid
ORA-12715: invalid character set specified
Cause: The character set specified is not allowed for this operation or is invalid
Action: Ensure that the specified character set is valid
ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated
Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as import/export
ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists
Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. The above type data can be migrated by methods such as import/export.
ORA-12718: operation requires connection as SYS
Cause: This command can only be run when connecting as SYS
Action: Connect as SYS to run this command
ORA-12719: operation requires database is in RESTRICTED mode
Cause: This command can only be run when the database is in RESTRICTED mode
Action: Ensure that the system is in RESTRICTED mode
ORA-12720: operation requires database is in EXCLUSIVE mode
Cause: This command can only be run when the database is in EXCLUSIVE mode
Action: Ensure that the system is in EXCLUSIVE mode
ORA-12721: operation cannot execute when other sessions are active
Cause: This command can only be run when there are no other sessions active
Action: Ensure there are no other connections to the database
ORA-12722: regular expression internal error
Cause: A regular expression internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
ORA-12723: regular expression too complex
Cause: The regular expression was too complex and could not be parsed.
Action: This is an internal error. Contact Oracle Support Services.
ORA-12724: regular expression corrupt
Cause: The regular expression contained an incorrect sequence of metacharacters.
Action: Ensure the metacharacters are correctly positioned.
ORA-12725: unmatched parentheses in regular expression
Cause: The regular expression did not have balanced parentheses.
Action: Ensure the parentheses are correctly balanced.
ORA-12726: unmatched bracket in regular expression
Cause: The regular expression did not have balanced brackets.
Action: Ensure the brackets are correctly balanced.
ORA-12727: invalid back reference in regular expression
Cause: A back references was found before a sub-expression.
Action: Ensure a valid sub-expression is being referenced.
ORA-12728: invalid range in regular expression
Cause: An invalid range was found in the regular expression.
Action: Ensure a valid range is being used.
ORA-12729: invalid character class in regular expression
Cause: An unknown character class was found in the regular expression.
Action: Ensure a valid characters class is being used.
ORA-12730: invalid equivalence class in regular expression
Cause: An unknown equivalence class was found in the regular expression.
Action: Ensure a valid equivalence class is being used.
ORA-12731: invalid collation class in regular expression
Cause: An unknown collation class was found in the regular expression.
Action: Ensure a valid collation class is being used.
ORA-12732: invalid interval value in regular expression
Cause: An invalid interval value was found in the regular expression.
Action: Ensure a valid interval value is being used.
ORA-12733: regular expression too long
Cause: The operation failed because the regular expression it used exceeds the maximum supported size.
Action: Use a shorter regular expression.
ORA-12734: Instant Client Light: unsupported client national character set string
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12735: Instant Client Light: unsupported client character set string
Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12736: Instant Client Light: unsupported server national character set string
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12737: Instant Client Light: unsupported server character set string
Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12800: system appears too busy for parallel query execution
Cause: load on system is too high to perform parallel queries.
Action: re-execute serially or wait until system load is reduced.
ORA-12801: error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause, and consult your error manual for the appropriate action.
ORA-12802: parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.
ORA-12803: parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.
ORA-12804: parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.
ORA-12805: parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. See trace file for more details.
ORA-12806: could not get background process to hold enqueue
Cause: Internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
ORA-12807: process queue could not receive parallel query message
Cause: Internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
ORA-12808: cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809: cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle Real Application Clusters mounted in CLUSTER_DATABASE mode.
ORA-12810: PARALLEL_MAX_SERVERS must be less than or equal to string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.
ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
ORA-12813: value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814: only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
ORA-12815: value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
ORA-12817: parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
ORA-12818: invalid option in PARALLEL clause
Cause: an unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { <n> | DEFAULT } and INSTANCES { <n> | DEFAULT } within the PARALLEL clause.
ORA-12819: missing options in PARALLEL clause
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { <n> | DEFAULT } and INSTANCES { <n> | DEFAULT } within the PARALLEL clause.
ORA-12820: invalid value for DEGREE
Cause: invalid value for DEGREE was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
ORA-12821: invalid value for INSTANCES
Cause: invalid value for INSTANCES was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
ORA-12822: duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: specify each desired PARALLEL clause option only once.
ORA-12823: default degree of parallelism may not be specified here
Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: respecify with an explicit degree of parallelism.
ORA-12824: INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command
Action: respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
ORA-12825: explicit degree of parallelism must be specified here
Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: respecify with an explicit degree of parallelism.
ORA-12826: hung parallel query server was killed
Cause: parallel query server was hung and subsequently killed.
Action: re-execute query and report suspicious events in trace file to Oracle Support Services if error persists.
ORA-12827: insufficient parallel query slaves available
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired
Action: either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves
ORA-12828: Can"t start parallel transaction at a remote site
Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.
Action: Do not use PDML at remote sites.
ORA-12829: Deadlock - itls occupied by siblings at block string of file string
Cause: parallel statement failed because all itls in the current block are occupied by siblings of the same transaction.
Action: increase MAXTRANS of the block or reduce the degree of parallelism for the statement. Reexecute the statement. Report suspicious events in trace file to Oracle Support Services if error persists.
ORA-12830: Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12832: Could not allocate slaves on all specified instances
Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query
Action: To allow results to be returned by sucessfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances
ORA-12833: Coordinator"s instance not a member of parallel_instance_group
Cause: The coordinator"s instance must be a member of the parallel_instance_group in which this operation will be run.
Action: Either add the coordinator"s instance to the current parallel_instance_group or change parallel_instance_group.
ORA-12834: Instance group name, "string", too long, must be less than string characters
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views
Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP
ORA-12838: cannot read/modify an object after modifying it in parallel
Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.
Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.
ORA-12839: cannot modify an object in parallel after modifying it
Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.
Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.
ORA-12840: cannot access a remote table after parallel/insert direct load txn
Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.
Action: Commit/rollback the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.
ORA-12841: Cannot alter the session parallel DML state within a transaction
Cause: Transaction in progress
Action: Commit or rollback transaction and then re-execute
ORA-12842: Cursor invalidated during parallel execution
Cause: The cursor was invalidated during the parse phase of deferred parallel processing, e.g. when set operands are parallelized.
Action: Depends on why the cursor was invalidated. Possible causes include DDL on a schema object and shared pool being flushed.
ORA-12843: pdml lock not held properly on the table
Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire currently.
Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the pdml again.
ORA-12844: cluster reconfiguration in progress
Cause: Internal error
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR.
ORA-12845: failed to receive interinstance parallel execution message
Cause: OS or interconnect problem receiving interinstance message
Action: Check OS specific diagnostics
ORA-12850: Could not allocate slaves on all specified instances: string needed, string allocated
Cause: When executing a query on a gv$ fixed view, one or more instances failed to allocate a slave to process query.
Action: Check trace output for instances on which slaves failed to start. GV$ query can only proceed if slaves can be allocated on all instances.
ORA-12851: PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value less than PARALLEL_MIN_SERVERS.
Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to PARALLEL_MIN_SERVERS value specified in the accompanying message and retry.
ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES.
Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value specified in the accompanying message and retry.
ORA-12853: insufficient memory for PX buffers: current stringK, max needed stringK
Cause: Insufficient SGA memory for PX buffers
Action: Reconfigure sga to include at least (max - current) bytes of additional memory
ORA-12854: Parallel query is not supported on temporary LOBs
Cause: The parallel query statement produced a temporary LOB.
Action: Turn off parallelism for the query or underlying table
ORA-12855: cannot run parallel or insert direct load in a loopback
Cause: A loopback was created in the transaction before this operation.
Action: Do not use loopback when using pdml or insert direct load.
ORA-12856: cannot run parallel query on a loopback connection
Cause: A table or index in a parallel query is referenced via a loopback connection.
Action: Do not use loopback connection when running a query in parallel.
ORA-12872: First slave parse gave different plan
Cause: First hard parse on slave given QC-supplied environment and parameters gave different plan from QC. Try again with outline.
Action: No external action. Internally used for outline-based reparse.
ORA-12899: value too large for column string (actual: string, maximum: string)
Cause: An attempt was made to insert or update a column with a value which is too wide for the width of the destination column. The name of the column is given, along with the actual width of the value, and the maximum allowed width of the column. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes.
Action: Examine the SQL statement for correctness. Check source and destination column data types. Either make the destination column wider, or use a subset of the source column (i.e. use substring).
ORA-12900: must specify a default temporary tablespace for a locally managed database
Cause: a locally managed database must have a temporary tablespace other than SYSTEM tablespace
Action: specify the default temporary tablespace when creating a locally managed database
ORA-12901: default temporary tablespace must be of TEMPORARY type
Cause: in a locally managed database, default temporary tablespace must be TEMPORARY type
Action: none
ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY type
Cause: in a dictionary managed database, default temporary tablespace must be SYSTEM or TEMPORARY type
Action: none
ORA-12910: cannot specify temporary tablespace as default tablespace
Cause: attempt to assign a temporary tablespace to be a user"s default tablespace
Action: assign a permanent tablespace to be the default tablespace
ORA-12911: permanent tablespace cannot be temporary tablespace
Cause: attempt to assign a permanent tablespace to be a user"s temporary tablespace
Action: assign a temporary tablespace to be user"s temporary tablespace
ORA-12912: Dictionary managed tablespace specified as temporary tablespace
Cause: attempt to assign a dictionary managed tablespace to be a user"s temporary tablespace
Action: Assign a locally managed temporary tablespace to be user"s temporary tablespace
ORA-12913: Cannot create dictionary managed tablespace
Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed
Action: Create a locally managed tablespace.
ORA-12914: Cannot migrate tablespace to dictionary managed type
Cause: Attemp to migrate locally managed tablespace to dictionary managed type when the database has locally managed system tablespace.
Action: Command cannot be issued.
ORA-12915: Cannot alter dictionary managed tablespace to read write
Cause: Attemp to alter dictionary managed tablespace to read write in database which has system tablespace as locally managed. This tablespace can only be dropped.
Action: Command cannot be issued.
ORA-12916: Cannot use default permanent tablespace with this release
Cause: To use default permanent tablespace the release should be 10.0 or higher
Action: Check the compatibility setting and reissue the statement
ORA-12918: Invalid tablespace type for default permanent tablespace
Cause: The tablespace is either dropped, temporary or undo
Action: Check the tablespace type and reissue the statement
ORA-12919: Can not drop the default permanent tablespace
Cause: An attemp was made to drop the default permanent tablespace
Action: Make a different tablespace as the default permanent tablespace and reissue the drop
ORA-12920: database is already in force logging mode
Cause: ALTER DATABASE FORCE LOGGING command failed because the database is already in force logging mode.
Action: none
ORA-12921: database is not in force logging mode
Cause: ALTER DATABASE NO FORCE LOGGING command failed because the database is not in force logging mode.
Action: none
ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING command running in the system.
Action: Contact the database administrator who is responsible for the concurrent command.
ORA-12923: tablespace string is in force logging mode
Cause: An attempt to alter the specified tablespace temporary failed because the tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by ALTER TABLESPACE NO FORCE LOGGING command.
ORA-12924: tablespace string is already in force logging mode
Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.
Action: none
ORA-12925: tablespace string is not in force logging mode
Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.
Action: none
ORA-12926: FORCE LOGGING option already specified
Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.
Action: Remove all but one of the FORCE LOGGING options.
ORA-12927: RETENTION option already specified
Cause: In CREATE TABLESPACE, the RETENTION option was specified more than once.
Action: Remove all but one of the RETENTION options.
ORA-12950: SYSTEM tablespace specified as default permanent tablespace
Cause: SYSTEM tablespace was specified as the default permanent during database creation.
Action: If default permanent tablespace is not specified,then SYSTEM will implicitly become the default permanent tablespace. Specify an alternate tablespace or omit the default tablespace clause and reissue the CREATE DATABASE statement
ORA-12951: Attempt to change default permanent tablespace to temporary
Cause: It is incorrect to alter the default permanent tablespace of a database to temporary type
Action: none
ORA-12980: checkpoint option not allowed with SET UNUSED
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove checkpoint option.
ORA-12981: cannot drop column from an object type table
Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
ORA-12982: cannot drop column from a nested table
Cause: An attempt was made to drop a column from a nested table.
Action: This action is not allowed.
ORA-12983: cannot drop all columns in a table
Cause: An attempt was made to drop all columns in a table.
Action: Make sure at least one column remains in the table after the drop column operation.
ORA-12984: cannot drop partitioning column
Cause: An attempt was made to drop a column used as the partitioning key.
Action: This action is not allowed.
ORA-12985: tablespace "string" is read only, cannot drop column
Cause: An attempt was made to drop column from a partition/subpartition on a read only tablespace.
Action: Set the tablespace to read write and resubmit statement.
ORA-12986: columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
Cause: An attempt was made to access a table with columns in partially dropped state (i.e., drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.
ORA-12987: cannot combine drop column with other operations
Cause: An attempt was made to combine drop column with other ALTER TABLE operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
ORA-12988: cannot drop column from table owned by SYS
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed
ORA-12989: invalid value for checkpoint interval
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement
ORA-12990: duplicate option specified
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
ORA-12991: column is referenced in a multi-column constraint
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.
ORA-12992: cannot drop parent key column
Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.
ORA-12993: tablespace "string" is offline, cannot drop column
Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.
Action: Bring the tablespace online and resubmit statement.
ORA-12994: drop column option only allowed once in statement
Cause: An attempt was made to repeat the drop column option in a single statement.
Action: Separate drop column options into different statements and resubmit statements.
ORA-12995: no columns in partially dropped state
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.
Action: Cannot submit this statement.
ORA-12996: cannot drop system-generated virtual column
Cause: An attempt was made to drop a virtual column generated by the system.
Action: none
ORA-12997: cannot drop primary key column from an index-organized table
Cause: An attempt was made to drop a primary key column from an index- organized table.
Action: This action is not allowed.
ORA-13000: dimension number is out of range
Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.
ORA-13001: dimensions mismatch error
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
ORA-13002: specified level is out of range
Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.
ORA-13003: the specified range for a dimension is invalid
Cause: The specified range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004: the specified buffer size is invalid
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13005: recursive HHCODE function error
Cause: An error occurred in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13006: the specified cell number is invalid
Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
ORA-13007: an invalid HEX character was detected
Cause: A character that is not in the range [0-9] or [A-F a-f] was detected.
Action: Verify that all characters in a string are in [0-9] or [A-F a-f].
ORA-13008: the specified date format has an invalid component
Cause: Part of specified date format is invalid.
Action: Verify that the date format is valid.
ORA-13009: the specified date string is invalid
Cause: The specified date string has a bad component or does not match the specified format string.
Action: Make sure that the components of the date string are valid and that the date and format strings match.
ORA-13010: an invalid number of arguments has been specified
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
ORA-13011: value is out of range
Cause: A specified dimension value is outside the range defined for that dimension.
Action: Make sure that all values to be encoded are within the defined dimension range.
ORA-13012: an invalid window type was specified
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
ORA-13013: the specified topology was not INTERIOR or BOUNDARY
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE"s topology.
ORA-13014: a topology identifier outside the range of 1 to 8 was specified
Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
ORA-13015: the window definition is not valid
Cause: The number of values used to define the window does not correspond to the window type.
Action: Verify that the number of values used to defined the window is correct for the window type and number of dimensions.
ORA-13016: specified topology [string] is invalid
Cause: The specified topology did not exist in the database, or some components of the topology were missing from the database.
Action: Check the specified topology by executing the SDO_TOPO.validate_topology function.
ORA-13017: unrecognized line partition shape
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13018: bad distance type
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
ORA-13019: coordinates out of bounds
Cause: Vertex coordinates lie outside the valid range for specified dimension.
Action: Redefine vertex coordinates within specified boundaries.
ORA-13020: coordinate is NULL
Cause: A vertex coordinate has a NULL value.
Action: Redefine vertex coordinate to have non-NULL value.
ORA-13021: element not continuous
Cause: The coordinates defining a geometric element are not connected.
Action: Redefine coordinates for the geometric element.
ORA-13022: polygon crosses itself
Cause: The coordinates defining a polygonal geometric element represent crossing segments.
Action: Redefine coordinates for the polygon.
ORA-13023: interior element interacts with exterior element
Cause: An interior element of a geometric object interacts with the exterior element of that object.
Action: Redefine coordinates for the geometric elements.
ORA-13024: polygon has less than three segments
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
Action: Redefine the coordinates for the polygon.
ORA-13025: polygon does not close
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
Action: Redefine the coordinates of the polygon.
ORA-13026: unknown element type for element string.string.string
Cause: The SDO_ETYPE column in the <layer>_SDOGEOM table contains an invalid geometric element type value.
Action: Redefine the geometric element type in the <layer>_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial documentation for an explanation of SDO_ETYPE and its possible values.
ORA-13027: unable to read dimension definition from string
Cause: There was a problem reading the dimension definition from the <layer>_SDODIM table.
Action: Verify that the <layer>_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message.
ORA-13028: Invalid Gtype in the SDO_GEOMETRY object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
ORA-13029: Invalid SRID in the SDO_GEOMETRY object
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
ORA-13030: Invalid dimension for the SDO_GEOMETRY object
Cause: There is a mismatch between the dimension in the SDO_GTYPE and dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
ORA-13031: Invalid Gtype in the SDO_GEOMETRY object for point object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
Action: Verify that the geometries have valid gtypes.
ORA-13032: Invalid NULL SDO_GEOMETRY object
Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid fields. To specify a NULL geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.
Action: Verify that the geometries have valid data.
ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X or Y or both.
Action: Verify that the geometries have valid data.
ORA-13035: Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.
Action: Verify that the geometries have valid data.
ORA-13036: Operation [string] not supported for Point Data
Cause: The specified geometry function is not supported for point data.
Action: Make sure that the specified geometry function is not called on point data.
ORA-13037: SRIDs do not match for the two geometries
Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.
Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.
ORA-13039: failed to update spatial index for element string.string.string
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services.
ORA-13040: failed to subdivide tile
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
ORA-13041: failed to compare tile with element string.string.string
Cause: The spatial relationship between a generated tile and the specified element could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13041 and contact Oracle Support Services.
ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the <layer>_SDOLAYER table. The most likely cause is that the columns are NULL.
Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial documentation. Then retry the operation.
ORA-13043: failed to read metadata from the <layer>_SDOLAYER table
Cause: An error was encountered reading the layer metadata from the <layer>_SDOLAYER table.
Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, contact Oracle Support Services.
ORA-13044: the specified tile size is smaller than the tolerance
Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as specified in the layer metadata.
Action: See the Oracle Spatial documentation for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a smaller tile size value than the current one.
ORA-13045: invalid compatibility flag
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13046: invalid number of arguments
Cause: An invalid number of arguments were specified for an SDO_GEOM function.
Action: See the Oracle Spatial documentation for a description of the syntax and semantics of the relevant SDO_GEOM function.
ORA-13047: unable to determine ordinate count from table <layer>_SDOLAYER
Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer <layer>.
Action: Verify that the <layer>_SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation.
ORA-13048: recursive SQL fetch error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13049: unable to determine tolerance value from table <layer>_SDODIM
Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer <layer>.
Action: Verify that the <layer>_SDODIM table has a valid value for the column SDO_TOLERANCE.
ORA-13050: unable to construct spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13051: failed to initialize spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13052: unsupported geometric type for geometry string.string
Cause: The geometry type for a specific instance in a <layer>_SDOGEOM table is not among the set of geometry types supported by Oracle Spatial.
Action: Check the Oracle Spatial documentation for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.
ORA-13053: maximum number of geometric elements in argument list exceeded
Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.
Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it in as an argument in a call to the SDO_GEOM function.
ORA-13054: recursive SQL parse error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13055: Oracle object string does not exist in specified table
Cause: The requested object is not present in the specified table.
Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Then retry the operation.
ORA-13060: topology with the name string already exists
Cause: The specified topology name was not unique in the database.
Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology name and that the procedure is invoked from the correct schema.
ORA-13061: topology with the name string does not exist
Cause: The specified topology did not exist in the database.
Action: Verify that the current procedure/function call specifies the correct schema and topology name.
ORA-13062: topology IDs do not match in the feature table and the topology
Cause: The specified topology ID in the feature table did not match the topology ID stored in the topology metadata.
Action: Verify that the specified topology ID matches the topology ID stored in the topology metadata.
ORA-13063: relationship information table is missing data for feature table [string]
Cause: The topology relationship information table (xxx_RELATION$) did not have the matching partition corresponding to the feature table.
Action: Make sure the correct topology IDs and names are specified in the call to register the feature table with the topology.
ORA-13064: relationship information table has inconsistent data for feature table [string]
Cause: The topology_id, tg_layer_id values stored in the feature table did not match the values stored in the topology relationship information table (xxx_RELATION$).
Action: Make sure that the correct feature tables are specified in the call to register the feature table with the topology.
ORA-13065: cannot delete a child layer with a parent layer
Cause: A call was made to delete a feature layer which has a dependent layer defined on it.
Action: Make sure that all dependent feature layers are deleted before deleting the current feature layer.
ORA-13066: wrong feature geometry or element type
Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element type.
Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY object.
ORA-13067: operator requires both parameters from the same topology
Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same topology.
Action: Make sure both the parameters to the operator are from the same topology. If this is not possible, consider using a signature of the operator that does not use two SDO_TOPO_GEOMETRY parameters.
ORA-13068: wrong table or column name in SDO_TOPO_GEOMETRY constructor
Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name.
Action: Fix the parameters in the call and try again.
ORA-13108: spatial table string not found
Cause: The specified spatial table does not exist.
Action: Check the Spatial data dictionary to make sure that the table is registered.
ORA-13109: spatial table string exists
Cause: The specified spatial table is registered in the Spatial data dictionary.
Action: Remove the existing table from the Spatial data dictionary or use a different name.
ORA-13110: cannot drop topology with associated topo_geometry tables
Cause: The drop_topology procedure was invoked for a topology that has assocated topo_geometry layers with it.
Action: Delete the topo_geometry layers from the topology before dropping the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete topo_geometry layers from the topology.
ORA-13111: cannot add topo_geometry layer [string] to topology
Cause: It was not possible to add the specified topo_geometry layer to the topology.
Action: Make sure the topo_geometry layer table exists in the database.
ORA-13112: cannot delete topo_geometry layer [string] from topology
Cause: It was not possible to delete the specified topo_geometry layer from the topology.
Action: Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry layer is part of the topology. Only those topo_geometry layers which are part of the topology can be deleted from it.
ORA-13113: invalid tg_layer_id in sdo_topo_geometry constructor
Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor.
Action: Valid layer_ids are obtained by adding a topo_geometry layer to the topology. Check USER_SDO_TOPO_METADATA to find out the layer_id for an existing topo_geometry layer.
ORA-13114: [string]_NODE$ table does not exist
Cause: The NODE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
ORA-13115: [string]_EDGE$ table does not exist
Cause: The EDGE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
ORA-13116: [string]_FACE$ table does not exist
Cause: The FACE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
ORA-13117: [string]_RELATION$ table does not exist
Cause: The RELATION$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
ORA-13118: invalid node_id [string]
Cause: A topology node operation was invoked with an invalid node_id.
Action: Check the topology node$ table to see if the specified node_id exists in the topology.
ORA-13119: invalid edge_id [string]
Cause: A topology edge operation was invoked with an invalid edge_id.
Action: Check the topology edge$ table to see if the specified edge_id exists in the topology.
ORA-13120: invalid face_id [string]
Cause: A topology face operation was invoked with an invalid face_id.
Action: Check the topology face$ table to see if the specified face_id exists in the topology.
ORA-13121: layer type type mismatch with topo_geometry layer type
Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type specified for the layer.
Action: Check the USER_SDO_TOPO_METADATA view to see the layer type for the layer and use it in the constructor.
ORA-13122: invalid topo_geometry specified
Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was not valid.
Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object.
ORA-13123: invalid <TOPOLOGY> name specified
Cause: The create_topo operation requires a unique TOPOLOGY name, that already does not exist in the database.
Action: Check to see if there is already an entry in the USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE) with this topology name.
ORA-13124: unable to determine column id for column string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13125: partition key is already set
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
ORA-13126: unable to determine class for spatial table string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13127: failed to generate target partition
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13128: current tiling level exceeds user specified tiling level
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13129: HHCODE column string not found
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial data dictionary.
ORA-13135: failed to alter spatial table
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13136: null common code generated
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13137: failed to generate tablespace sequence number
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13138: could not determine name of object string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13139: could not obtain column definition for string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13140: invalid target type
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE and VIEW.
ORA-13141: invalid RANGE window definition
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.
ORA-13142: invalid PROXIMITY window definition
Cause: The PROXIMITY window specified is not correctly defined.
Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.
ORA-13143: invalid POLYGON window definition
Cause: The POLYGON window specified is not correctly defined.
Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.
ORA-13144: target table string not found
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13145: failed to generate range list
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13146: could not find table substitution variable string
Cause: The partition name substitution variable %s was not found in the SQL filter.
Action: The substitution variable %s must be in the SQL filter to indicate where that partition name should be placed.
ORA-13147: failed to generate MBR
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13148: failed to generate SQL filter
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13149: failed to generate next sequence number for spatial table string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13150: failed to insert exception record
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
ORA-13151: failed to remove exception record
Cause: Operation failed to remove a record from the exception table.
Action: Fix any other errors reported.
ORA-13152: invalid HHCODE type
Cause: Specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
ORA-13153: invalid high water mark specified
Cause: The high water mark must be greater than or equal to zero.
Action: Make sure that the high water mark is an integer greater than or equal to zero.
ORA-13154: invalid precision specified
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
ORA-13155: invalid number of dimensions specified
Cause: The number of dimensions specified is out of range.
Action: The number of dimension must be between 1 and 32.
ORA-13156: table to be registered string.string is not empty
Cause: The specified table has rows in it.
Action: Make sure that the table to be registered is empty.
ORA-13157: Oracle error ORAstring encountered while string
Cause: The specified Oracle error was encountered.
Action: Correct the Oracle error.
ORA-13158: Oracle object string does not exist
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
ORA-13159: Oracle table string already exists
Cause: The specified table already exists.
Action: Drop the specified table.
ORA-13181: unable to determine length of column string_SDOINDEX.SDO_CODE
Cause: The length of the SDO_CODE column in the <layer>_SDOINDEX table could not be determined.
Action: Make sure that the <layer>_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Then retry the operation.
ORA-13182: failed to read element string.string.string
Cause: The specified element could not be read from the <layer>_SDOGEOM table.
Action: Verify that the specified element exists in the table. Then retry the operation.
ORA-13183: unsupported geometric type for geometry string.string
Cause: The geometry type in the <layer>_SDOGEOM table is unsupported.
Action: Modify the geometry type to be one of the supported types.
ORA-13184: failed to initialize tessellation package
Cause: Initialization of the tessellation package failed.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13185: failed to generate initial HHCODE
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13186: fixed tile size tessellation failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13187: subdivision failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13188: cell decode failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13189: recursive SQL parse failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13190: recursive SQL fetch failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13191: failed to read SDO_ORDCNT value
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13192: failed to read number of element rows
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13193: failed to allocate space for geometry
Cause: There was insufficient memory to read the geometry from the database.
Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.
ORA-13194: failed to decode supercell
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13195: failed to generate maximum tile value
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13196: failed to compute supercell for element string.string.string
Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13197: element string.string.string is out of range
Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the <layer>_SDODIM table.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13198: Spatial error: string
Cause: Internal error in some Oracle Spatial stored procedure.
Action: Record the sequence of procedure calls or events that preceded this error, and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.
ORA-13199: %s
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13200: internal error [string] in spatial indexing.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
ORA-13201: invalid parameters supplied in CREATE INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.
Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for spatial index creation.
ORA-13202: failed to create or insert into the SDO_INDEX_METADATA table
Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.
Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA view.
Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.
ORA-13204: failed to create spatial index table
Cause: An error was encountered while trying to create the index table.
Action: Check that user has CREATE TABLE privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.
ORA-13205: internal error while parsing spatial parameters
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check that the parameters passed in the parameter string are all valid.
ORA-13206: internal error [string] while creating the spatial index
Cause: An internal error was encountered while creating the spatial index.
Action: Contact Oracle Support Services with the exact error text.
ORA-13207: incorrect use of the [string] operator
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
ORA-13208: internal error while evaluating [string] operator
Cause: An internal error was encountered.
Action: Contact Oracle Support Services with the exact error text.
ORA-13209: internal error while reading SDO_INDEX_METADATA table
Cause: An internal error was encountered while trying to read the SDO_INDEX_METADATA table.
Action: Contact Oracle Support Services. Note this and accompanying error numbers.
ORA-13210: error inserting data into the index table
Cause: An error was encountered while trying to insert data into the index table. Likely causes are:

- Insufficient quota in the current tablespace

- User does not appropriate privileges

Action: Check the accompanying error messages.
ORA-13211: failed to tessellate the window object
Cause: An internal error was encountered while trying to tessellate the window object.
Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure.
ORA-13212: failed to compare tile with the window object
Cause: The spatial relationship between a generated tile and the specified window object could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any accompanying errors and contact Oracle Support Services.
ORA-13213: failed to generate spatial index for window object
Cause: Another error, indicating the real cause of the problem, should accompany this error.
Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services.
ORA-13214: failed to compute supercell for window object
Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13215: window object is out of range
Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13216: failed to update spatial index
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services.
ORA-13217: invalid parameters supplied in ALTER INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.
Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for the spatial ALTER INDEX statement.
ORA-13218: max number of supported index tables reached for [string] index
Cause: An add_index parameter was passed to ALTER INDEX when the number of existing index tables is already at maximum.
Action: Delete one of the index tables before adding another index table.
ORA-13219: failed to create spatial index table [string]
Cause: An error was encountered while trying to create the index table.
Action: There is a table in the index"s schema with the specified name. The CREATE INDEX statement will try to create an index table with this name. Either rename this table or change the name of the index.
ORA-13220: failed to compare tile with the geometry
Cause: The spatial relationship between a generated tile and the specified geometry could not be determined.
Action: This is an internal error. Validate the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13220 and contact Oracle Support Services.
ORA-13221: unknown geometry type in the geometry object
Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value
Action: Redefine the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial documentation for an explanation of SDO_GTYPE and its possible values.
ORA-13222: failed to compute supercell for geometry in string
Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13223: duplicate entry for string in SDO_GEOM_METADATA
Cause: There are duplicate entries for the given table and column value pair in the USER_SDO_GEOM_METADATA view.
Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the USER_SDO_GEOM_METADATA view.
ORA-13224: zero tolerance specified for layer in USER_SDO_GEOM_METADATA
Cause: A tolerance of zero or NULL is supplied for a layer in USER_SDO_GEOM_METADATA view.
Action: Check the tolerance specified to make sure it is a positive value.
ORA-13225: specified index table name is too long for a spatial index
Cause: An index table name is specified which is longer than the supported length of the spatial index table name.
Action: Check the supported size of the index table name and reduce the size of the index name.
ORA-13226: interface not supported without a spatial index
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.
ORA-13227: SDO_LEVEL values for the two index tables do not match
Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.
Action: Verify that two compatible indexes are used for the spatial join operator. Quadtree indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values
ORA-13228: spatial index create failed due to invalid type
Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.
Action: Make sure that the index is created on a column of type SDO_GEOMETRY.
ORA-13230: failed to create temporary table [string] during R-tree creation
Cause: The specified temporary table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace.
ORA-13231: failed to create index table [string] during R-tree creation
Cause: The specified index table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace. If that fails to correct the problem, contact Oracle Support Services.
ORA-13232: failed to allocate memory during R-tree creation
Cause: This feature assumes a minimum of 64K memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional insert operations for the rest of the data.
ORA-13233: failed to create sequence number [string] for R-tree
Cause: The specified sequence number exists.
Action: Delete the sequence object, or contact Oracle Support Services.
ORA-13234: failed to access R-tree-index table [string]
Cause: The index table is either deleted or corrupted.
Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.
ORA-13236: internal error in R-tree processing: [string]
Cause: An internal error occurred in R-tree processing.
Action: Contact Oracle Support Services with the message text.
ORA-13237: internal error during R-tree concurrent updates: [string]
Cause: An inconsistency is encountered during concurrent updates, possibly due to the use of serializable isolation level.
Action: Change the isolation level to "read committed" using the ALTER SESSION statement, or contact Oracle Support Services with the message text.
ORA-13239: sdo_dimensionality not specified during n-d R-tree creation
Cause: An error occurred in reading the dimensionality parameter
Action: Check the documentation for a valid range, and specify the dimensionality as a parameter.
ORA-13240: specified dimensionality greater than that of the query mbr
Cause: An error occurred because of too few values in the query minimum bounding rectangle (MBR).
Action: Omit the dimensionality, or use the dimensionality of the query.
ORA-13241: specified dimensionality does not match that of the data
Cause: An error occurred because the dimensionality specified in the CREATE INDEX statement does not match that of the data.
Action: Change the statement to reflect the data dimensionality.
ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree
Cause: Currently, an R-tree index with three or more index dimensions can be used only with the SDO_FILTER operator.
Action: Use the SDO_FILTER operator, and check the documentation for the querytype parameter for SDO_FILTER; or contact Oracle Support Services.
ORA-13249: %s
Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.
Action: Contact Oracle Support Services with the exact error text.
ORA-13250: insufficient privileges to modify metadata table entries
Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.
Action: Check that the specified feature and geometry table names are correct, and then verify that the current user has at least SELECT privilege on those tables.
ORA-13251: duplicate entry string in metadata table
Cause: The specified entry already exists in the metadata table.
Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.
ORA-13260: layer table string does not exist
Cause: Data migration source table <layer>_SDOGEOM does not exist.
Action: Ensure that the specified layer name is correct and that the corresponding spatial layer tables exist in the current schema.
ORA-13261: geometry table string does not exist
Cause: The specified geometry table does not exist in the current schema.
Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.
ORA-13262: geometry column string does not exist in table string
Cause: The specified table does not have a column of type SDO_GEOMETRY.
Action: Alter or re-create the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.
ORA-13263: column string in table string is not of type SDO_GEOMETRY
Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.
Action: Alter the column definition to be of type SDO_GEOMETRY.
ORA-13264: geometry identifier column string does not exist in table string
Cause: The specified table does not contain a GID column.
Action: Confirm that the GID column name was correctly specified and that it exists in the specified table.
ORA-13265: geometry identifier column string in table string is not of type NUMBER
Cause: GID column is not of type NUMBER.
Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.
ORA-13266: error inserting data into table string
Cause: An OCI error occurred, or the user has insufficient quota in the active tablespace, or the rollback segments are too small.
Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.
ORA-13267: error reading data from layer table string
Cause: There was an error reading the geometry data from the <layer>_SDOGEOM table.
Action: Verify that <layer>_SDOGEOM and <layer>_SDODIM exist. If they do exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer.
ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA
Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified geometry table.
Action: Insert an entry for the destination geometry table with the correct dimension information.
ORA-13269: internal error [string] encountered when processing geometry table
Cause: An internal error occurred.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13270: OCI error string
Cause: An OCI error occurred while processing the layer or geometry tables.
Action: Take the appropriate steps to correct the OCI-specific error.
ORA-13271: error allocating memory for geometry object
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
ORA-13272: geometric object string in table string is invalid
Cause: The specified object failed the geometric integrity checks performed by the validation function.
Action: Check the Oracle Spatial documentation for information about the geometric integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT and correct the geometry definition if required.
ORA-13273: dimension metadata table string does not exist
Cause: The <layer>_SDODIM table does not exist.
Action: Verify that the specified layer name is correct and that the <layer>_SDODIM table exists in the current schema.
ORA-13274: operator invoked with non-compatible SRIDs
Cause: A Spatial operator was invoked with a window geometry with an SRID but the layer has no SRID; or the window has no SRID but the layer has an SRID.
Action: Make sure that the layer and window both have an SRID or that they both do not have an SRID.
ORA-13275: spatial index creation failure on unsupported type
Cause: An attempt was made to create a spatial index create on a column that is not of type SDO_GEOMETRY.
Action: A spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column is of type SDO_GEOMETRY.
ORA-13276: internal error [string] in coordinate transformation
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13278: failure to convert SRID to native format
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13281: failure in execution of SQL statement to retrieve WKT
Cause: OCI internal error, or SRID does not match a table entry.
Action: Check that a valid SRID is being used.
ORA-13282: failure on initialization of coordinate transformation
Cause: Parsing error on source or destination coordinate system WKT, or incompatible coordinate systems.
Action: Check the validity of the WKT for table entries, and check if the requested transformation is valid.
ORA-13283: failure to get new geometry object for conversion in place
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13284: failure to copy geometry object for conversion in place
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13285: Geometry coordinate transformation error
Cause: A coordinate pair was out of valid range for a conversion/projection.
Action: Check that data to be transformed is consistent with the desired conversion/projection.
ORA-13287: can"t transform unknown gtype
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.
Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and specify a value whose last digit is 1 or higher.
ORA-13288: point coordinate transformation error
Cause: An internal error occurred while transforming points.
Action: Check the accompanying error messages.
ORA-13290: the specified unit is not supported
Cause: An Oracle Spatial function was called with an unknown UNIT value.
Action: Check Spatial documentation for the supported units, and call the function with the correct UNIT parameter.
ORA-13291: conversion error between the specified unit and standard unit
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
Action: Check the unit specification and respecify it.
ORA-13292: incorrect ARC_TOLERANCE specification
Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified, and it should not be less than the tolerance specified for the geometry.
Action: Check ARC_TOLERANCE specification and make sure it is correct.
ORA-13293: cannot specify unit for geometry without a georeferenced SRID
Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID.
Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.
ORA-13294: cannot transform geometry containing circular arcs
Cause: It is impossible to transform a 3-point representation of a circular arc without distortion.
Action: Make sure a geometry does not contain circular arcs.
ORA-13295: geometry objects are in different coordinate systems
Cause: An Oracle Spatial function was called with two geometries that have different SRIDs.
Action: Transform geometry objects to be in the same coordinate system and call the spatial function.
ORA-13296: incorrect coordinate system specification
Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.
Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse flattening.
ORA-13300: single point transform error
Cause: Low-level coordinate transformation error trap.
Action: Check the accompanying error messages.
ORA-13303: failure to retrieve a geometry object from a table
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13304: failure to insert a transformed geometry object in a table
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13330: invalid MASK
Cause: The MASK passed to the RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial documentation for a list of supported masks.
ORA-13331: invalid LRS segment
Cause: The given LRS segment was not a valid line string.
Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in the Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or longitude/latitude, plus measure)
ORA-13332: invalid LRS point
Cause: The specified LRS point was not a point geometry with measure information.
Action: Check the given point geometry. A valid LRS point is a point geometry in Oracle Spatial with an additional dimension for measure.
ORA-13333: invalid LRS measure
Cause: The given measure for linear referencing was out of range.
Action: Redefine the measure.
ORA-13334: LRS segments not connected
Cause: The specified geometric segments are not connected.
Action: Check the start/end points of the given geometric segments.
ORA-13335: LRS measure information not defined
Cause: The measure information of a geometric segment was not assigned (IS NULL).
Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).
ORA-13336: failure in converting standard diminfo/geometry to LRS dim/geom
Cause: There is no room for the measure dimension in the given diminfo, or the specified standard geometry is not a point a line string.
Action: Check if the diminfo dimensions are less than 3 or if the geometry type is point or line string.
ORA-13337: failure in concatenating LRS polygons
Cause: LRS concatenation involving LRS polygons is not supported.
Action: Check the geometry and element types to make sure the concatenate operation is not called with a polygon type.
ORA-13338: failure in reversing LRS polygon/collection geometry
Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry.
Action: Check the geometry type to make sure this operation is called on non-polygon geometries.
ORA-13339: LRS polygon clipping across multiple rings
Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.
Action: Polygon clipping is allowed only for a single ring.
ORA-13340: a point geometry has more than one coordinate
Cause: A geometry, specified as being a point, has more than one coordinate in its definition.
Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, remove the extraneous coordinates from its definition.
ORA-13341: a line geometry has fewer than two coordinates
Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition.
Action: A line must consist of at least two distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13342: an arc geometry has fewer than three coordinates
Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition.
Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13343: a polygon geometry has fewer than four coordinates
Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition.
Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13344: an arcpolygon geometry has fewer than five coordinates
Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition.
Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13345: a compound polygon geometry has fewer than five coordinates
Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition.
Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13346: the coordinates defining an arc are collinear
Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.
Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the line type.
ORA-13347: the coordinates defining an arc are not distinct
Cause: Two or more of the three points defining an arc are the same.
Action: Alter the definition of the arc to ensure that three distinct coordinate values are used.
ORA-13348: polygon boundary is not closed
Cause: The boundary of a polygon does not close.
Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.
ORA-13349: polygon boundary crosses itself
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
ORA-13350: two or more rings of a complex polygon touch
Cause: The inner or outer rings of a complex polygon touch.
Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object.
ORA-13351: two or more rings of a complex polygon overlap
Cause: The inner or outer rings of a complex polygon overlap.
Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object.
ORA-13352: the coordinates do not describe a circle
Cause: The set of coordinates used to describe a circle are incorrect.
Action: Confirm that the set of coordinates actually represent points on the circumference of a circle.
ORA-13353: ELEM_INFO_ARRAY not grouped in threes
Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer elements than expected.
Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.
ORA-13354: incorrect offset in ELEM_INFO_ARRAY
Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition references an invalid array subscript in SDO_ORDINATE_ARRAY.
Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.
ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.
Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.
ORA-13356: adjacent points in a geometry are redundant
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
ORA-13357: extent type does not contain 2 points
Cause: Extent type should be represented by two points: lower left and upper right.
Action: Confirm that there are only two points for an extent type.
ORA-13358: circle type does not contain 3 points
Cause: Circle type should be represented by three distinct points on the circumference.
Action: Confirm that there are only three points for a circle type.
ORA-13359: extent does not have an area
Cause: The two points representing the extent are identical.
Action: Confirm that the two points describing the extent type are distinct.
ORA-13360: invalid subtype in a compound type
Cause: This subtype is not allowed within the ETYPE specified.
Action: Check the Oracle Spatial documentation for type definitions.
ORA-13361: not enough sub-elements within a compound ETYPE
Cause: The compound type declare more sub-elements than actually defined.
Action: Confirm that the number of sub-elements is consistent with the compound type declaration.
ORA-13362: disjoint sub-element in a compound polygon
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
ORA-13363: no valid ETYPE in the geometry
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
ORA-13364: layer dimensionality does not match geometry dimensions
Cause: The spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.
Action: Make sure that all geometries in a layer have the same dimensions and that they match the dimensions in the SDO_DIM_ARRAY object for the layer in the USER_SDO_GEOM_METADATA view.
ORA-13365: layer SRID does not match geometry SRID
Cause: The spatial layer has a geometry with a different SRID than the SRID specified for the layer.
Action: Make sure that all geometries in a layer have the same SRID and that the SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view.
ORA-13366: invalid combination of interior exterior rings
Cause: In an Oracle Spatial geometry, interior and exterior rings are not used consistently.
Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.
ORA-13367: wrong orientation for interior/exterior rings
Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly.
Action: Be sure that the exterior rings are oriented counterclockwise and the interior rings are oriented clockwise.
ORA-13368: simple polygon type has more than one exterior ring
Cause: In a polygon geometry there is more than one exterior ring.
Action: Set the type to be multipolygon if more than one exterior ring is present in the geometry.
ORA-13369: invalid value for etype in the 4-digit format
Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is not a valid orientation for interior/exterior rings of the polygon.
Action: Correct the geometry definition.
ORA-13370: failure in applying 3D LRS functions
Cause: Only non-geodetic 3D line string geometries (made of line segments) are supported for 3D LRS functions.
Action: Check the geometry and element types and the SRID values.
ORA-13371: invalid position of measure dimension
Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in the dim_info_array.
Action: Check the geometry"s gtype and its position in the dim_info_array.
ORA-13372: failure in modifying metadata for a table with spatial index
Cause: Modifying the metadata after the index is created will cause an inconsistency between the geometry"s gtype and diminfo.
Action: Modify (or Prepare) metadata before creating an index on the SDO_GEOMETRY column.
ORA-13373: invalid line segment in geodetic data
Cause: A geodetic line segment was not less than half of a great circle.
Action: Densify the line by adding points.
ORA-13374: SDO_MBR not supported for geodetic data
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
ORA-13375: the layer is of type [string] while geometry inserted has type [string]
Cause: The layer has a type that is different or inconsistent with the type of the current geometry.
Action: Change the geometry type to agree with the layer type, or change the layer type to agree with the geometry type.
ORA-13376: invalid type name specified for layer_gtype parameter
Cause: An invalid type name is specified for the layer_gtype constraint.
Action: See the Spatial documentation for of valid keywords that can be used in defining a layer_gtype constraint.
ORA-13377: invalid combination of elements with orientation
Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4-digit etype).
Action: Make sure all the polygon elements have orientation specified using the 4-digit etype notation.
ORA-13378: invalid index for element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the geometry.
ORA-13379: invalid index for sub-element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the geometry.
ORA-13380: network not found
Cause: The specified network was not found in the network metadata.
Action: Insert the network information in the USER_SDO_NETWORK_METADATA view.
ORA-13381: table:string not found in network:string
Cause: The specified table was not found in the network metadata.
Action: Insert the table information in the USER_SDO_NETWORK_METADATA view.
ORA-13382: geometry metadata (table:string column:string) not found in spatial network:string
Cause: The specified geometry metadata was not found in the spatial network metadata.
Action: Insert the spatial metadata information in the USER_SDO_NETWORK_METADATA view.
ORA-13383: inconsistent network metadata: string
Cause: There was an inconsistency between the network metadata and the node/link information.
Action: Check the network metadata and the node/link information.
ORA-13384: error in network schema: string
Cause: The network table(s) did not have required column(s)
Action: Check the network schema.
ORA-13385: error in network manager: [string]
Cause: There was an internal error in network manager.
Action: Contact Oracle Customer Support for more help.
ORA-13386: commit/rollback operation error: [string]
Cause: The index-level changes were not fully incorporated as part of the commit or rollback operation.
Action: Correct the specified error and use the following statement: ALTER INDEX <index-name> PARAMETERS ("index_status=synchronize");
ORA-13387: sdo_batch_size for array inserts should be in the range [number,number]
Cause: The specified value for sdo_batch_size was too high or too low.
Action: Change the value to be in the specified range.
ORA-13388: invalid value for dst_spec parameter
Cause: The dst_spec parameter was specified in the wrong format.
Action: Check the documentation for this parameter.
ORA-13389: unable to compute buffers or intersections in analysis function
Cause: There was an internal error in computing the buffers or intersections in the specified spatial analysis function.
Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA view before invoking the spatial analysis function.
ORA-13390: error in spatial analysis and mining function: [string]
Cause: There was an internal error in the specified analysis function.
Action: Contact Oracle Customer Support for more help.
ORA-13401: duplicate entry for string in USER_SDO_GEOR_SYSDATA view
Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in two or more rows in the USER_SDO_GEOR_SYSDATA view.
Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the USER_SDO_GEOR_SYSDATA view contain the correct information, and that the value pair is unique for each row.
ORA-13402: the rasterType is null or not supported
Cause: The specified rasterType was null or not supported.
Action: Check the documentation for the rasterType number and/or formats supported by GeoRaster.
ORA-13403: invalid rasterDataTable specification: string
Cause: Each GeoRaster object must have an associated raster data table whose name is unique among raster data table names in the database. If the GeoRaster object is not empty and not blank, the raster data table must exist, be visible in the current schema, be defined in the same schema as the GeoRaster data table, and be an object table of SDO_RASTER type. However, one or more of these requirements were not met.
Action: Check the rasterDataTable specification and ensure that all relevant raster data table requirements are met.
ORA-13404: invalid ultCoordinate parameter
Cause: The ultCoordinate array parameter had the wrong length or contained an invalid value.
Action: Check the documentation, and make sure the ultCoordinate parameter is correct.
ORA-13405: null or invalid dimensionSize parameter
Cause: The dimensionSize array parameter was null, had the wrong length, or contained an invalid value.
Action: Check the documentation, and make sure the dimensionSize parameter is correct.
ORA-13406: null or invalid GeoRaster object for output
Cause: The GeoRaster object for output was null or invalid.
Action: Make sure the GeoRaster object for output has been initialized properly.
ORA-13407: invalid storage parameter
Cause: The storage parameter contained an invalid specification.
Action: Check the documentation, and make sure the storage parameter is correct.
ORA-13408: invalid blockSize storage parameter
Cause: The blockSize storage parameter had the wrong length or contained invalid value.
Action: Check the documentation, and make sure the blockSize storage parameter is correct.
ORA-13409: null or invalid pyramidLevel parameter
Cause: The specified pyramidLevel parameter was null or invalid.
Action: Make sure the pyramidLevel parameter specifies a valid pyramid level value for the GeoRaster object.
ORA-13410: invalid layerNumbers or bandNumbers parameter
Cause: The layerNumbers or bandNumbers parameter was invalid.
Action: Check the documentation and make sure the layerNumbers or bandNumbers parameter is valid.
ORA-13411: subset results in null data set
Cause: The intersection of cropArea and source GeoRaster object was null.
Action: Check the documentation, and make sure the cropArea parameter is correct.
ORA-13412: invalid scale parameter
Cause: The scale parameter was invalid.
Action: Check the documentation, and make sure the scale parameter is correct.
ORA-13413: null or invalid resampling parameter
Cause: The resampling parameter was null or invalid.
Action: Check the documentation, and make sure the resampling parameter is correct.
ORA-13414: invalid pyramid parameter
Cause: The pyramid parameter was invalid.
Action: Check the documentation, and make sure the pyramid parameter is correct.
ORA-13415: invalid or out of scope point specification
Cause: The point position specified by the <ptGeom, layerNumber> or <rowNumber, colNumber, bandNumber> parameter combination was invalid or out of scope.
Action: Make sure the parameter(s) specify a valid point that is or can be translated into a cell position inside the cell space of the GeoRaster object.
ORA-13416: invalid geometry parameter
Cause: The geometry parameter did not specify a valid single-point geometry.
Action: Specify a valid single-point geometry.
ORA-13417: null or invalid layerNumber parameter
Cause: The layerNumber parameter was null or out of scope.
Action: Specify a valid layerNumber parameter.
ORA-13418: null or invalid parameter(s) for set functions
Cause: A parameter for set metadata operations was null or invalid.
Action: Check the documentation for information about the parameters.
ORA-13419: cannot perform mosaick operation on the specified table column
Cause: An attempt to perform a mosaick operation failed because the GeoRaster objects in the specified table column did not meet necessary conditions.
Action: Check the documentation for SDO_GEOR.Mosaick for details.
ORA-13420: the SRID of the geometry parameter was not null
Cause: The input geometry must be in the GeoRaster cell space, which has a null SRID value.
Action: Make sure the geometry parameter has a null SRID.
ORA-13421: null or invalid cell value
Cause: The cell value was null or out of scope.
Action: Make sure the cell value is not null and is in the range as designated by the cellDepth of the specified GeoRaster object.
ORA-13422: invalid model coordinate parameter
Cause: The model coordinate array parameter had the wrong length or had null ordinate element(s).
Action: Make sure the model coordinate parameter is valid.
ORA-13423: invalid cell coordinate parameter
Cause: The cell coordinate array parameter had the wrong length or had null ordinate element(s).
Action: Make sure the cell coordinate parameter is valid.
ORA-13424: the GeoRaster object is not spatially referenced
Cause: The GeoRaster object was not spatially referenced.
Action: Make sure the GeoRaster object is spatially referenced.
ORA-13425: function not implemented
Cause: This specific function was not implemented.
Action: Do not use the function that causes this error.
ORA-13426: invalid window parameter for subset operation
Cause: The specified window parameter was invalid.
Action: Specify a valid window parameter. Check the documentation for details.
ORA-13427: invalid BLOB parameter for output
Cause: The specified output BLOB parameter was invalid.
Action: Make sure the output BLOB parameter is initialized properly.
ORA-13428: invalid modelCoordinateLocation
Cause: The program [or user] specified a modelCoordinateLocation that is not supported, or the modelCoordinateLocation of the GeoRaster object was wrong.
Action: Set or specify the modelCoordinateLocation to be CENTER (0) or UPPERLEFT (1).
ORA-13429: invalid xCoefficients or yCoefficients parameter(s)
Cause: An attempt to perform a georeference operation failed. Possible reasons include xCoefficients or yCoefficients having the wrong number of coefficients or invalid coefficients.
Action: Check the documentation for supported coefficient specifications.
ORA-13430: the GeoRaster object has null attribute(s)
Cause: The metadata or rasterType of the GeoRaster object was null.
Action: This object may only be used as an output parameter of procedures or functions. It is not valid for other purposes.
ORA-13431: GeoRaster metadata rasterType error
Cause: The rasterType in the metadata of the GeoRaster object was inconsistent with the GeoRaster rasterType attribute.
Action: Make sure the rasterType in the metadata of the GeoRaster object and the GeoRaster rasterType attribute have the same value.
ORA-13432: GeoRaster metadata blankCellValue error
Cause: The blankCellValue specification could not be found in the metadata of a blank GeoRaster object.
Action: Add blankCellValue to the metadata whenever isBlank is true.
ORA-13433: GeoRaster metadata default RGB error
Cause: At least one of the defaultRed, defaultGreen, and defaultBlue values (logical layer numbers) was zero, negative, or out of range.
Action: Check the documentation for details.
ORA-13434: GeoRaster metadata cellRepresentation error
Cause: The cellRepresentation type was not supported.
Action: Check the documentation for supported cellRepresentation types.
ORA-13435: GeoRaster metadata dimension inconsistent
Cause: The specification of dimensions or totalDimensions was inconsistent with rasterType, or vice versa.
Action: Make sure dimension specifications are consistent.
ORA-13436: GeoRaster metadata dimensionSize error
Cause: Either the dimensionSize for each dimension was not specified, or an extraneous dimensionSize was specified.
Action: Add a dimsenionSize for each dimension of the GeoRaster object and delete extra dimensionSize elements.
ORA-13437: GeoRaster metadata blocking error
Cause: Either the wrong block number(s) or block size(s) along dimensions were specified, or the block numbers and sizes when taken together were not consistent.
Action: Check the documentation for details.
ORA-13438: GeoRaster metadata pyramid type error
Cause: The specified pyramid type was not supported.
Action: Check the documentation for supported pyramid types.
ORA-13439: GeoRaster metadata pyramid maxLevel error
Cause: The specified maxLevel exceeded the maximum level allowed by the specified pyramid type.
Action: Check the documentation for supported pyramid types and their total level limitations.
ORA-13440: GeoRaster metadata compression type error
Cause: The specified compression type was not supported.
Action: Check the documentation for supported compression types.
ORA-13441: GeoRaster metadata SRS error
Cause: The referenced GeoRaster object had no defined polynomial referencing model.
Action: Define or generate the polynomialModel, or set isReferenced to FALSE.
ORA-13442: GeoRaster metadata SRS error
Cause: The polynomialModel did not match the supported number of variables.
Action: Check the documentation for supported number of variables in the polynomialModel specification.
ORA-13443: GeoRaster metadata SRS error
Cause: The polynomialModel specification had an incorrect pType value.
Action: Check the documentation for supported polynomial types.
ORA-13444: GeoRaster metadata SRS error
Cause: The polynomialModel specification had the wrong number of coefficients.
Action: Check the documentation for the required number of coefficients under different conditions.
ORA-13445: GeoRaster metadata SRS error
Cause: The polynomialModel specification had a zero denominator.
Action: Make sure the denominator of the polynomialModel specification is not zero.
ORA-13446: GeoRaster metadata TRS error
Cause: The GeoRaster Temporal Reference System was not supported.
Action: Set isReferenced to FALSE.
ORA-13447: GeoRaster metadata BRS error
Cause: The GeoRaster Band Reference System was not supported.
Action: Set isReferenced to FALSE.
ORA-13448: GeoRaster metadata BRS error
Cause: The GeoRaster spectral extent specification was incorrect.
Action: The MIN value must be less than the MAX value in the spectralExtent element.
ORA-13449: GeoRaster metadata ULTCoordinate error
Cause: The GeoRaster rasterInfo ULTCoordinate was not correct.
Action: Check the documentation for restrictions.
ORA-13450: GeoRaster metadata layerInfo error
Cause: The GeoRaster had more than one layerInfo element, or the layerDimension value was not supported.
Action: The current release only supports one layerInfo element; layer can only be defined along one dimension, and this dimension must be BAND.
ORA-13451: GeoRaster metadata scaling function error
Cause: The scaling function had a zero denominator.
Action: Make sure the scaling function denominator is not zero.
ORA-13452: GeoRaster metadata BIN function error
Cause: The bin function data did not match its type.
Action: For EXPLICIT type, provide a binTableName element; otherwise, provide a binFunctionData element.
ORA-13453: GeoRaster metadata layer error
Cause: Too many subLayers were defined for the GeoRaster object, or layerNumber or layerDimensionOrdinate was not assigned correctly.
Action: The total number of logical layers cannot exceed the total number of physical layers, and each logical layer must be assigned a valid physical layer number following the same order. Check the documentation for more details.
ORA-13454: GeoRaster metadata is invalid
Cause: The GeoRaster metadata was invalid against its XML Schema.
Action: Run the schemaValidate routine to find the errors.
ORA-13455: GeoRaster metadata TRS error
Cause: The beginDateTime value was later than the endDateTime value.
Action: Make sure that the beginDateTime value is not later than the endDateTime value.
ORA-13456: GeoRaster cell data error
Cause: There was error in the GeoRaster cell data.
Action: The GeoRaster object is invalid.
ORA-13457: GeoRaster cell data error
Cause: There was error in the cell data of the pyramids.
Action: Delete the pyramids and re-generate them.
ORA-13458: GeoRaster metadata SRS error
Cause: The polynomial model did not match the requirements of a rectified GeoRaster object.
Action: Check the documentation for the requirements of the polynomial model for a rectified GeoRaster object, or set isRectified to be false.
ORA-13459: GeoRaster metadata SRS error
Cause: The polynomial model was not an six-parameter transformation, or the six-parameter transformation was not valid.
Action: Check the documentation and make sure the polynomial model is a valid six-parameter affine transformation.
ORA-13460: GeoRaster metadata SRS error
Cause: The referenced GeoRaster object had a zero model space SRID or the specified model space SRID was zero.
Action: Set or specify the model space SRID to be a nonzero number.
ORA-13461: the interleaving type is not supported
Cause: The interleaving type of the GeoRaster object was not supported.
Action: Check the documentation for the interleaving types supported by GeoRaster. Use SDO_GEOR.changeFormat to transform the image to a supported interleaving type.
ORA-13462: invalid blocking specification
Cause: The specified blocking configuration was invalid.
Action: Block size must always be a power of 2.
ORA-13463: error retrieving GeoRaster data: string
Cause: An internal error occurred while retrieving GeoRaster data from the database.
Action: Check the error message for details.
ORA-13464: error loading GeoRaster data: string
Cause: An internal error occurred while loading GeoRaster data into the database.
Action: Check the error message for details.
ORA-13465: null or invalid table or column specification
Cause: The specified table or column did not exist, or the column was not a GeoRaster column.
Action: Make sure the specified table exists and the specified column is a GeoRaster column.
ORA-13466: format not appropriate for specified compression method
Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported by the specified compression.
Action: Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormat to transform the GeoRaster object to an appropriate format, or apply another compression method.
ORA-13467: unsupported GeoRaster metadata specification: string
Cause: The GeoRaster metadata specification is not supported.
Action: Check the documentation for the supported GeoRaster metadata specifications.
ORA-13480: the Source Type is not supported
Cause: The specified source type was not supported.
Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster.
ORA-13481: the destination type is not supported
Cause: The specified destination type was not supported.
Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster.
ORA-13482: GeoRaster object is not initialized for the image
Cause: No GeoRaster object has been initialized for the specified image.
Action: Initialize a GeoRaster object to hold this image before loading it into the database. Check the documentation for details.
ORA-13483: insufficient memory for the specified GeoRaster data
Cause: There was insufficient memory to hold the specified GeoRaster data for this operation.
Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock the GeoRaster data into smaller sized blocks. Check the documentation for details.
ORA-13484: the file format and/or compression type is not supported
Cause: The file format and/or compression type was not supported.
Action: Check the documentation for formats that are currently supported by GeoRaster.
ORA-13485: error occurred during compression or decompression: string
Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details.
Action: Check that the GeoRaster object is valid, that its metadata is valid for the specified compression format, and that valid parameters are passed into the compression or decompression operation.
ORA-13497: %s
Cause: This is an internal GeoRaster error.
Action: Contact Oracle Support Services. You may want to make sure the GeoRaster object is valid before you do so.
ORA-13498: %s
Cause: An error related to an external plugin was encountered in the GeoRaster component.
Action: Check the documentation for the external plugin, or contact the plugin provider and supply the exact error text.
ORA-13499: %s
Cause: This is an internal Spatial error.
Action: Contact Oracle Support Services.
ORA-13500: SYSAUX DATAFILE clause specified more than once
Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause.
Action: Specify at most one SYSAUX DATAFILE clause.
ORA-13501: Cannot drop SYSAUX tablespace
Cause: Tried to drop SYSAUX tablespace
Action: None
ORA-13502: Cannot rename SYSAUX tablespace
Cause: An attempt to rename the SYSAUX tablespace failed.
Action: No action required.
ORA-13503: Creating SYSAUX tablespace with invalid attributes
Cause: An attempt to create the SYSAUX tablespace with invalid attributes.
Action: Create SYSAUX tablespace with ONLINE, PERMANENT, EXTENT MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO attributes.
ORA-13504: No SYSAUX datafile clause specified
Cause: If Create Database has the datafile clause, then SYSAUX datafile clause has to be specified, unless using OMF.
Action: Specify the SYSAUX datafile clause.
ORA-13505: SYSAUX tablespace can not be made read only
Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX tablespace must remain read write for database operation.
Action: Leave SYSAUX tablespace read write.
ORA-13506: operation failed due to invalid snapshot range (string, string)
Cause: An attempt was made to perform operation with an invalid Start/End Snapshot Pair.
Action: Choose a valid Start/End Snapshot Pair.
ORA-13509: error encountered during updates to a AWR table
Cause: An update error occurred during OCI operation due to an underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13510: invalid RETENTION string, must be in the range (string, string)
Cause: The user has specified a RETENTION setting that is not in the supported range of (MIN, MAX).
Action: Choose a valid RETENTION setting and retry the operation.
ORA-13511: invalid INTERVAL string, must be in the range (string, string)
Cause: The user has specified a INTERVAL setting that is not in the supported range of (MIN, MAX).
Action: Choose a valid INTERVAL setting and retry the operation.
ORA-13514: Metric Capture too close to last capture, group string
Cause: The metric capture cannot be executed because it is too close to the last capture (within 1 centi-second).
Action: add some delay and reissue command to retry.
ORA-13515: Error encountered during Database Usage Statistics capture
Cause: Error occurred during OCI operation due to underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13516: AWR Operation failed: string
Cause: The operation failed because AWR is not available. The possible causes are: AWR schema not yet created; AWR not enabled; AWR schema not initialized; or database not open or is running in READONLY or STANDBY mode.
Action: check the above conditions and retry the operation.
ORA-13517: Baseline (id = string) does not exist
Cause: The operation failed because the specified baseline ID does not exist in the Workload Repository.
Action: check the baseline id and retry the operation.
ORA-13518: Invalid database id (string)
Cause: The operation failed because the specified database ID does not exist in the Workload Repository.
Action: check the database id and retry the operation.
ORA-13519: Database id (string) exists in the workload repository
Cause: The operation failed because the specified database ID already exists in the Workload Repository.
Action: check the database id and retry the operation.
ORA-13520: Database id (string) not registered, Status = string
Cause: The operation failed because the specified database ID was not registered in the Workload Repository properly.
Action: check the status of database id and retry the operation.
ORA-13521: Unregister operation on local Database id (string) not allowed
Cause: The operation failed because the local database ID cannot be unregistered from the Workload Repository.
Action: check the database id and retry the operation.
ORA-13523: unable to allocate required space for return type
Cause: Out of memory to allocate the space for the return variable for an external procedure.
Action: Try operation again.
ORA-13524: error encountered while retrieving baseline information
Cause: A read error occurred during the OCI operation to retrieve the baseline information
Action: Check associated error. Correct problem and retry the operation.
ORA-13525: error with computing space usage for sysaux occupant
Cause: Error occurred during OCI operation due to underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13526: baseline (string) does not exist
Cause: The operation failed because the specified baseline name does not exist in the Workload Repository.
Action: check the baseline name and retry the operation.
ORA-13527: invalid baseline name
Cause: The operation failed because the specified baseline name does not exist in the Workload Repository.
Action: check the baseline name and retry the operation.
ORA-13528: name (string) is already used by an existing baseline
Cause: The operation failed because the specified baseline name already exists in the Workload Repository.
Action: check the baseline name and retry the operation.
ORA-13529: Error occurred when flushing AWR table group
Cause: An error occurred during the flushing of a table group. Because of the error in the group, we are unable to flush this table.
Action: Check the error associated with the table group.
ORA-13530: invalid TOPNSQL string, must be in the range (string, string)
Cause: The user has specified a TOPNSQL setting that is not in the supported range of (MIN, MAX).
Action: Choose a valid TOPNSQL setting and retry the operation.
ORA-13600: error encountered in Advisor string
Cause: An error occurred in the Advisor. This message will be followed by a second message giving more details about the nature of the error.
Action: See the Advisor documentation for an explanation of the second error message.
ORA-13601: The specified Advisor string does not exist.
Cause: The user specified an advisor name that has not be defined in the advisor repository.
Action: Correct the advisor name and retry the operation.
ORA-13602: The specified parameter string is not valid for task or object string.
Cause: The user attempted to access a task parameter that does not exist for the specified advisor object. The parameter may be misspelled or the user has selected a parameter that is not supported by the particular advisor.
Action: Validate the parameter name and retry the operation.
ORA-13603: The specified parameter string cannot be fetched as a numeric value for task or object string.
Cause: The user attempted to retrieve a string parameter as a numeric value.
Action: Check the datatype for the task parameter and retry the operation.
ORA-13604: The specified parameter string cannot be fetched as a SQL table.
Cause: The user attempted to retrieve a non-table parameter as a table name.
Action: Check the datatype for the task parameter and retry the operation.
ORA-13605: The specified task or object string does not exist for the current user.
Cause: The user attempted to reference an advisor task or object using a name that does not exist in the Advisor repository.
Action: Adjust the name and retry the operation.
ORA-13606: the specified task parameter element string is out of range for parameter string.
Cause: The user attempted to reference an invalid parameter element.
Action: Adjust the element offset and retry the operation.
ORA-13607: The specified task or object string already exists
Cause: The user attempted to create the specified task or object using a name that already exists in the Advisor repository. Task names must be unique to the database user.
Action: Adjust the name and retry the operation.
ORA-13608: The task or object name string is invalid.
Cause: The user attempted to specify a task name that contains invalid characters or an invalid wildcard specifier.
Action: Adjust the name and retry the operation.
ORA-13609: The specified task string must be executing to be cancelled or interrupted.
Cause: The user attempted to cancel or interrupt a task that is not currently executing.
Action: Check the status of the task and retry the operation.
ORA-13610: The directive string does not exist for task string.
Cause: The user attempted to access a task directive that does not exist.
Action: Validate the directive and retry the operation.
ORA-13611: The command string is not a valid advisor command.
Cause: The user attempted to specify a command that does not exist.
Action: Validate the command and retry the operation.
ORA-13612: The recommendation action string,string is not valid for task string.
Cause: The user attempted to access a recommendation action that does not exist in the task.
Action: Validate the recommendation-action and retry the operation.
ORA-13613: The requested operation is not supported for this advisor object.
Cause: The user attempted to perform an operation that is not supported for the particular advisor or task type.
Action: Validate the task or object and retry the operation.
ORA-13614: The template string is not compatible with the current advisor.
Cause: The user attempted to create a new task or object using an existing task or object that was not created by the same advisor.
Action: Validate the template and retry the operation.
ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters.
Cause: The user attempted to create a new task or object using a name that is too long.
Action: Shorten the name and retry the operation.
ORA-13616: The current user string has not been granted the ADVISOR privilege.
Cause: The user attempted an advisor operation that requires privilege.
Action: Adjust the user"s privileges and retry the operation.
ORA-13617: The specified task string already executing
Cause: The user attempted to execute a task that is currently executing.
Action: Wait for the task to finish before attempting any further task activities.
ORA-13618: The specified value is not a valid value for procedure argument string.
Cause: The user executed a procedure but failed to provide correct values for the argument.
Action: Correct the procedure arguments and retry the operation.
ORA-13619: The procedure argument string is greater than the maximum allowable length of string characters.
Cause: The user attempted to pass a character argument that is too long.
Action: Shorten the specified character argument and retry the operation.
ORA-13620: The task or object string is read-only and cannot be deleted or modified.
Cause: The user attempted to perform an operation that will update or delete a read-only task or object.
Action: Adjust the READ_ONLY property for the object and retry the operation.
ORA-13621: The task_or object string is marked as a template and cannot perform the requested operation.
Cause: The user attempted perform an unsupported operation on a task or object that is identified as a template.
Action: Choose a different object and retry the operation.
ORA-13622: invalid recommendation annotation
Cause: The user attempted to mark a recommendation using an invalid annotation. Valid annotation actions are ACCEPT, REJECT and IGNORE.
Action: Correct the action and retry the operation.
ORA-13623: The recommendation string is not valid for task string.
Cause: The user attempted to access a recommendation that does not exist in the task.
Action: Validate the recommendation and retry the operation.
ORA-13624: The task string is executing and cannot be deleted or modified.
Cause: The user attempted to access a task that currently executing.
Action: Wait for the task to complete and retry the operation.
ORA-13625: %s is an invalid advisor object type.
Cause: The user has specified an invlaid object type.
Action: Refre to dba_advisor_object_types for all valid object types
ORA-13626: The specified object string is not valid for task string.
Cause: The user specified an non-existent object for the task
Action: Choose a different object and retry the operation.
ORA-13627: Setting of parameter string is disallowed until the task is reset.
Cause: The user attempted to set the value of a parameter before the task was reset. This parameter cannot be changed until the task is reset.
Action: Reset the task and retry the operation.
ORA-13628: Insufficient privileges to access the task belonging to the specified user
Cause: The user could not access dba_* views.
Action: Retry operation as owner of the task or after granting new privileges.
ORA-13629: The task or object string is being used by another operation.
Cause: The user attempted to access a task or object that is locked by another session.
Action: Wait for the task or object activity to complete and retry the operation.
ORA-13630: The task string contains execution results and cannot be executed.
Cause: The user attempted to execute a task that already contains execution results.
Action: Reset the task to its initial state and retry the operation.
ORA-13631: The task string contains no execution results.
Cause: The user attempted to create a report or script from a task that has not successfully completed an execution.
Action: Execute the task and then retry the operation
ORA-13632: The user cancelled the current operation.
Cause: The user signaled a cancel during a task or object operation.
Action: None
ORA-13633: The task string was interrupted and needs to be resumed.
Cause: The user attempted to execute a task that was interrupted.
Action: Resume the execution of the task via the RESUME_TASK API.
ORA-13634: The task string needs to be reset before being re-executed.
Cause: The task must be in an inital state to be executed.
Action: Reset the task to its initial state and retry the operation.
ORA-13635: The value provided for parameter string cannot be converted to a number.
Cause: A numeric parameter was incorrectly supplied in string form.
Action: Retry by supplying valid numeric value.
ORA-13636: The specified value provided for parameter string is not valid for this advisor.
Cause: The user supplied an invalid parameter value.
Action: Retry by supplying valid value.
ORA-13637: Executing or modifying task string is disallowed until the task is reset to its initial state.
Cause: The user attempted to execute or modify the task that is in not in its INITIAL state.
Action: Reset the task and retry the operation.
ORA-13638: The user interrupted the current operation.
Cause: The user signaled an interrupt during a task or object operation.
Action: None
ORA-13639: The current operation was interrupted because it timed out.
Cause: The task or object operation timed out.
Action: None
ORA-13640: The current operation was cancelled because it timed out, and was not in interruptible mode.
Cause: The task or object operation timed out.
Action: None
ORA-13641: Task cannot be interrupted yet. You may cancel it instead.
Cause: The user attempted to interrupt a task that has not reached interruptible mode.
Action: Wait until the task reaches interruptible mode, or cancel the task execution.
ORA-13642: The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
Cause: The user supplied a date value in an incorrect format.
Action: Retry by supplying valid value.
ORA-13643: The task can not be interrupted or cancelled.
Cause: Request to interrupt or cancel task execution can not be granted because the task has not reached the appropriate mode.
Action: User should wait for a few seconds and try again.
ORA-13644: The user "string" is invalid.
Cause: Invalid user name specified to advisor framework
Action: User should specify a correct, case-sensitive, name
ORA-13699: Advisor feature is not currently implemented.
Cause: The user attempted to execute an unsupported advisor operation.
Action: Verify the availability of the operation.
ORA-13701: Snapshot pair [string, string] seems to be specified in reverse order.
Cause: The start snapshot id was greater than the end snapshot id.
Action: Swap the start and end snapshot ids.
ORA-13702: Snapshot IDs specified by the range [string, string] are equal.
Cause: The start snapshot id and end snapshot id were identical.
Action: Provide different start and end snapshot ids.
ORA-13703: The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
Cause: The snapshot ids or the database id or the instance id was invalid or the specified snapshots have already been purged.
Action: Set valid snapshot ids and retry.
ORA-13704: Invalid value "string" specified for parameter "string".
Cause: The parameter was not set before executing the ADDM.
Action: Set the parameter to a valid value and retry.
ORA-13705: There was a instance shutdown/startup between the snapshots in the range [string, string].
Cause: Instance was shut down and restarted between the two specified snapshots.
Action: Specify start and end snapshot ids that does not have a shutdown/startup in between them.
ORA-13706: Invalid value "string" specified for parameter "string" in "string" analysis mode.
Cause: The parameter was not set to an acceptable value for this particular mode of analysis.
Action: Set the parameter to a valid value and retry.
ORA-13707: Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.
Cause: Either the start or the end snaphots was missing or purged or had encountered errors while creating them.
Action: Verify that AWR is done taking these two snapshots, or Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the start/end snapshots. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that has valid start and end snapshots.
ORA-13708: Some snapshots in the range [string, string] were purged before the analysis was complete.
Cause: One or both of the snapshots have been purged from AWR.
Action: Verify that the AWR auto purging is not trying to purge these snapshots and re-run ADDM.
ORA-13709: Required parameter "string" must be set before execution.
Cause: The parameter needs to be set before running the ADDM
Action: Set the parameter to a valid value and retry.
ORA-13710: Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
Cause: Invalid interaction between two parameter values.
Action: Set at least one of the values so the value of the first parameter is higher than the value of the second parameter.
ORA-13711: Some snapshots in the range [string, string] are missing key statistics.
Cause: Some AWR tables encountered errors while creating one or more snapshots in the given range. The data present in one or more of these missing tables is necessary to perform an ADDM analysis.
Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the given snapshot range. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that does not include any incomplete snapshots.
ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
Cause: ADDM analysis can only be performed on AWR snapshots taken in the current release.
Action: One can still generate AWR and ASH reports using ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots to analyze the data in them.
ORA-13750: User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
Cause: The user attempted an SQL Tuning Set operation that requires a specific privilege.
Action: Adjust the user"s privileges and retry the operation.
ORA-13751: "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
Cause: The user attempted to access a SQL Tuning Set that does not exist or the user does have permission to access the SQL Tuning Set
Action: Check the existence of the "SQL Tuning Set" or adjust the user"s privileges and retry the operation.
ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
Cause: The attempted to create a SQL Tuning Set in another schema without having the right privilege.
Action: Connect as SYS or adjust the user"s privilege and retry the operation.
ORA-13753: "SQL Tuning Set" "string" already exists for user "string".
Cause: The user attempted to create a "\SQL Tuning"\ Set using a name that already exists for that owner.
Action: Change the name of the SQL Tuning Set and retry the operation.
ORA-13754: "SQL Tuning Set" "string" does not exist for user "string".
Cause: The user attempted to access a SQL Tuning Set that does not exist.
Action: Check the speelling of the SQL Tuning Set name and retry the operation.
ORA-13755: invalid "SQL Tuning Set" name
Cause: The user attempted to specify a SQL Tuning Set name that is invalid. A name must not contain wildcards and its length must be less than 30 characters.
Action: Adjust the name and retry the operation.
ORA-13756: Cannot update attribute "string".
Cause: The user attempted to update an attribute element that cannot be modified. The only string attributes that can be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER.
Action: Adjust the attribute name and retry the operation.
ORA-13757: "SQL Tuning Set" "string" owned by user "string" is active.
Cause: The user attempted to update an active SQL Tuning Set.
Action: Remove all reference to the SQL Tuning Set and retry the operation.
ORA-13758: "SQL Tuning Set" "string" owned by user "string" is in use.
Cause: The user attempted to modify a SQL Tuning Set or to add a reference to a SQL Tuning Set which is in use.
Action: Wait until the end of the previous operation and retry.
ORA-13759: User "string" cannot remove reference "string".
Cause: The user attempted to remove a SQL Tuning Set reference that does not exist. The user might not own the reference.
Action: Check the reference ID and the reference owner and retry the operation.
ORA-13761: invalid filter
Cause: The user attempted to select data from a data source using an invalid filter. A filter is a WHERE clause on data source content.
Action: Correct the filter and retry the operation.
ORA-13762: The string ranking measure is invalid.
Cause: The user attempted to select data from a data source using an invlaid ranking measure. A ranking measure must represent a valid numerical expression.
Action: Correct the ranking measure and retry the operation.
ORA-13763: illegal ranking attribute "string"
Cause: The user attempted to use an attribute element that is not allowed in a ranking meseare.
Action: Check the attribute in the ranking meseare and retry the operation.
ORA-13764: Value "string" is illegal as a result percentage.
Cause: The user attempted to select data from a SQL Tuning Set using an invalid result percentage. The result percentage must be between 0 and 1.
Action: Correct the result percentage value and retry the operation.
ORA-13765: Value "string" is illegal for a result limit.
Cause: The user attempted to select data from a SQL Tuning Set using an invalid result limit. A result limit must be a positive interger.
Action: Correct the result limit value and retry the operation.
ORA-13766: A ranking measure is required.
Cause: The user attempted to select data from a SQL Tuning Set using a percentage argument without specifying a ranking measure.
Action: Add a ranking measure or remove the percentage argument and retry the operation.
ORA-13767: End snapshot ID must be greater than or equal to begin snapsho ID.
Cause: The user attempted to select data from the workload repository using an invalid snaphot ID range.
Action: Adjust the snapshot ID range and retry the operation.
ORA-13768: Snapshot ID must be between string and string.
Cause: The user attempted to select data from the workload repository using a snaphot ID which does not exist.
Action: Adjust the snapshot ID and retry the operation.
ORA-13769: Snapshots string and string do not exist.
Cause: The user attempted to select data from the workload repository using snapshots that do not exist.
Action: Check the snapshot identifiers and retry the operation.
ORA-13770: Baseline "string" does not exist.
Cause: The user attempted to access a baseline that does not exsit.
Action: Check the speelling of the baseline name and retry the operation.
ORA-13771: cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
Cause: Unexpected error from DBMS_LOCK.REQUEST.
Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services.
ORA-13772: unexpected deadlock on "SQL Tuning Set" "string" owned by user "string"
Cause: Unexpected error from DBMS_LOCK.REQUEST
Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services.
ORA-13773: insufficient privileges to select data from the cursor cache
Cause: The user attempted to perform an operation without having the appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE.
Action: Adjust the user"s privileges and retry the operation.
ORA-13774: insufficient privileges to select data from the workload repository
Cause: The user attempted to perform an operation without having the appropriate privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT.
Action: Adjust the user"s privileges and retry the operation.
ORA-13775: inconsistent datatype in input cursor
Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor. All rows in the cursor must match type SQLSET_ROW.
Action: Check the rows type in the cursor and retry the operation.
ORA-13776: User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
Cause: The user attempted to read a SQL tuning set belonging to someone else without having SELECT privilege on the DBA views
Action: User should be granted the privilege or only access his own STS
ORA-13777: invalid list of attribute names
Cause: The user specified an attribute element that is not valid. The only attributes that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of the names including EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN.
Action: Adjust the attribute list and retry the operation.
ORA-13778: no new name or owner specified for "SQL Tuning Set"
Cause: The user attempted to call remap_stgtab_sqlset without specifying either a new SQL tuning set name or a new SQL tuning set owner
Action: Specify at least one or the other argument as non-NULL
ORA-13779: invalid load option
Cause: The user attempted to call load_sqlset with a load option that is different than INSERT, UPDATE and MERGE.
Action: Adjust the load option and retry the operation.
ORA-13780: SQL statement does not exist.
Cause: The user attempted to tune a SQL statement that does not exist.
Action: Verify the sql_id and the plan hash value of the statement and retry the operation.
ORA-13783: invalid tuning scope
Cause: The user attempted to specify a tuning task scope that is invalid. The possible values are LIMITED or COMPREHENSIVE.
Action: Check the scope value and retry the operation.
ORA-13784: cannot accept SQL profiles for all statements in the "SQL Tuning Set"
Cause: The user attempted to accept SQL profiles for all statements in a SQL Tuning Set.
Action: Provide the object identifier corresponding to a statement in the SQL Tuning Set and retry the operation.
ORA-13785: missing target object for tuning task "string"
Cause: The user attempted to perform an operation on a task without specifying a target object or by using an invalid object identifier.
Action: Check the identifier of the object and retry the operation.
ORA-13786: missing SQL text of statement object "string" for tuning task "string"
Cause: The user attempted to accept SQL profile for an object that has not a SQL text associated to it.
Action: Check the identifier of the object and retry the operation.
ORA-13787: missing SQL profile for statement object "string" for tuning task "string"
Cause: The user attempted to accept a SQL profile for an object that has not a SQL profile associated to it.
Action: Check the identifier of the object and retry the operation.
ORA-13788: invalid recommendation type
Cause: The user passed an invalid recommendation type in the rec_type argument to script_tuning_task. Possible values are ALL or any subset of a comma-separated list of PROFILES, STATISTICS and INDEXES.
Action: Check the rec_type arg and retry the operation.
ORA-13789: invalid process action
Cause: The user passed an invalid action to process a SQL statement. Possible value is any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN.
Action: Check the action argument and retry the operation.
ORA-13790: invalid value for time limit
Cause: The user passed an invalid value for the time limit argument.
Action: Check the argument specified value and retry the operation.
ORA-13791: cannot resume a tuning task created to tune a single statement
Cause: The user attempted to resume a tuning task that was created to tune a single SQL statement. A task can be resumed only if it is used to tune a SQL Tuning Set.
Action: No action required.
ORA-13797: invalid SQL Id specified, string
Cause: Invalid SQL Id specified for conversion.
Action: Specify valid SQL Id.
ORA-13798: Parameter string cannot be NULL.
Cause: A call to GET_THRESHOLD procedure was made without a required parameter.
Action: Specify a valid value for this parameter.
ORA-13799: threshold not found
Cause: No threshold was found with the specified threshold key.
Action: No action required.
ORA-13800: concurrent DDL failure on SQL repository objects
Cause: A SQL repository object was the target of two concurrent DDL operations.
Action: Check the current state of the object and retry the operation that failed.
ORA-13801: invalid value for SQLTUNE_CATEGORY parameter
Cause: An invalid Oracle identifier was used as the value of the parameter.
Action: Specify the parameter conforming to the rules for Oracle identifiers.
ORA-13802: failed to purge SQL Tuning Base entry from sql$
Cause: An error occured while try to delete a SQL Tuning Base object.
Action: Look at the underlying error(s) on the error stack.
ORA-13825: missing SQL statement text for create SQL profile
Cause: No SQL text was provided to the create SQL profile operation.
Action: Retry with properly specified SQL text.
ORA-13826: empty SQL profile not allowed for create or update SQL profile
Cause: No attributes were specified to the create SQL profile operation.
Action: Retry with at least one hint specified.
ORA-13827: null or zero length attribute specified in SQL profile collection
Cause: One of the attributes within the SQL profile was not properly specified.
Action: Retry with a fully specified SQL profile.
ORA-13828: generated SQL profile name string already exists
Cause: A SQL profile already exists with the name generated by the system.
Action: Retry the operation as the generated name is time sensitive.
ORA-13829: SQL profile named string already exists
Cause: A SQL profile already exists with the name specified.
Action: Specify a different name or drop the existing SQL profile.
ORA-13830: SQL profile with category string already exists for this SQL statement
Cause: A SQL profile already exists for the given SQL statement and category.
Action: Drop or update the existing SQL profile.
ORA-13831: SQL profile name specified is invalid
Cause: An invalid SQL profile name was specified.
Action: Look for the underlying error on the error message stack.
ORA-13832: category name specified is invalid
Cause: An invalid category name swas pecified.
Action: Look for the underlying error on the error message stack.
ORA-13833: SQL profile named string doesn"t exist
Cause: A SQL profile name was specified that doesn"t exist.
Action: Verify the name of the SQL profile.
ORA-13834: name of SQL profile to be cloned must be provided
Cause: A SQL profile name was not provided as the from target of a clone SQL profile operation.
Action: Provide the name of the SQL profile being cloned.
ORA-13835: invalid attribute name specified
Cause: An invalid attribute name was specified for an alter SQL profile operation.
Action: Verify the name of the attribute.
ORA-13836: invalid attribute value specified
Cause: An invalid attribute value was specified for an alter SQL profile operation.
Action: Verify the attribute value.
ORA-13837: invalid HASH_VALUE
Cause: An invalid HASH_VALUE was passed to a create SQL profile operation
Action: Verify the HASH_VALUE.
ORA-13838: invalid ADDRESS value
Cause: An invalid ADDRESS value was passed to a create SQL profile operation.
Action: Verify the ADDRESS value.
ORA-13839: V$SQL row doesn"t exist with given HASH_VALUE and ADDRESS.
Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL profile operation doesn"t coorespond to an existing V$SQL entry.
Action: Verify the HASH_VALUE and ADDRESS in V$SQL.
ORA-13840: Concurrent DDL Error in create SQL profile operation.
Cause: A concurrent DDL operation was performed during a create or replace sql profile operation.
Action: Try operation again
ORA-13841: SQL profile named string already exists for a different signature/category pair
Cause: A SQL profile already exists with the name specified under a different signature/category pair so it cannot be replaced, even with FORCE specified.
Action: Specify a different name or drop the existing SQL profile.
ORA-13842: no SELECT privilege on DBA_SQL_PROFILES
Cause: A user has tried to perform an operation that requires SELECT privileges on the DBA_SQL_PROFILES view.
Action: Either perform the operation as another user or get the privilege
ORA-13843: no SQL profile with name like "string" exists for category like "string"
Cause: A user tried to perform an operation by specifying a profile name/ category filter that did not target any profiles
Action: Try a different filter after checking the profile name/category
ORA-13844: no new SQL profile name or category specified.
Cause: A user called remap_stgtab_sqlprof without specifying new values for the sql profile name or category. At least one is required.
Action: Specify either a new profile name, or a new category, or both
ORA-13850: Tracing for client identifier string is not enabled
Cause: Attempt to disable a client identifier tracing which was never enabled
Action: Supply correct client identifier
ORA-13851: Tracing for client identifier string is already enabled
Cause: Attempt to enable a client identifier tracing which has been already enabled
Action: Supply correct client identifier, or disable and re-enable tracing with different bind/wait options
ORA-13852: Tracing for service(module/action) string is not enabled
Cause: Attempt to disable a service-level tracing which was never enabled
Action: Supply correct service(module/action) name
ORA-13853: Tracing for service (module/action) string is already enabled
Cause: Attempt to enable a service-level tracing which has been already enabled
Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options
ORA-13854: Tracing for service(module/action) string on instance string is not enabled
Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
Action: Supply correct service(module/action) name
ORA-13855: Tracing for service (module/action) string on instance string is already enabled
Cause: Attempt to enable a service-level tracing which has been already enabled on a specific instance
Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options
ORA-13856: Service name must be specified
Cause: Omitting service name while enabling/disabling tracing or aggregation
Action: Supply the service name
ORA-13857: Invalid module name
Cause: Module name is too long (exceeding 48 characters)
Action: Supply correct name
ORA-13858: Invalid action name
Cause: Action name is too long (exceeding 32 characters)
Action: Supply correct name
ORA-13859: Action cannot be specified without the module specification
Cause: Action name is specified, but the module name is not
Action: Supply the module name
ORA-13860: Invalid service name
Cause: Service name is too long (exceeding 64 characters)
Action: Supply correct name
ORA-13861: Statistics aggregation for client identifier string is already enabled
Cause: Attempt to enable a client identifier aggregation which has been already enabled
Action: Supply correct client identifier
ORA-13862: Statistics aggregation for client identifier string is not enabled
Cause: Attempt to disable a client identifier statistics aggregation which was never enabled
Action: Supply correct client identifier
ORA-13863: Statistics aggregation for service(module/action) string is not enabled
Cause: Attempt to disable a service-level statistics aggregation which was never enabled
Action: Supply correct service(module/action) name
ORA-13864: Statistics aggregation for service (module/action) string is already enabled
Cause: Attempt to enable a service-level statistics aggregation which has been already enabled
Action: Supply correct service(module/action)
ORA-13865: Module name must be specified
Cause: Attempt to enable/disable a service-level statistics aggregation without a module specification
Action: Supply module name
ORA-13866: Client identifier must be specified
Cause: Omitting client identifier while enabling/disabling tracing or aggregation
Action: Supply the client identifier
ORA-13867: Database-wide SQL tracing is already enabled
Cause: Attempt to enable a database-level tracing which has been already enabled
Action: Disable and re-enable tracing with different bind/wait options
ORA-13868: Instance-wide SQL tracing on instance string is not enabled
Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
Action: No action required
ORA-13869: Instance-wide SQL tracing on instance string is already enabled
Cause: Attempt to enable an instance-level tracing which has been already enabled on a specific instance
Action: Disable and re-enable tracing with different bind/wait options
ORA-13870: Database-wide SQL tracing is not enabled
Cause: Attempt to disable a database-level tracing which was never enabled
Action: No action required
ORA-13871: Invalid instance name
Cause: Instance name is too long (exceeding 16 characters)
Action: Supply correct name
ORA-13900: missing or invalid parameter string
Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid.
Action: Specify a valid value for this parameter.
ORA-13901: Object string was not found.
Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object.
Action: Specify a valid object name.
ORA-13902: The specified file string is not a data file.
Cause: The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file.
Action: Specify a valid data file name.
ORA-13903: Invalid combination of string threshold value and operator.
Cause: A non-positive number was used for "Blocked User Session Count" metrics while operator contains equal.
Action: Use a positive number for the threshold value or use "greater than" operator.
ORA-13904: The file has been dropped and recreated during the procedure call.
Cause: The file on which threshold is specified was dropped and recreated during the procedure call.
Action: Retry this operation.
ORA-13905: Critical or warning threshold have incorrect values
Cause: The tablespace threshold values can be in the range 0 to 100 only.
Action: Check the threshold values
ORA-13906: The tablepace is not of the right type.
Cause: An attempt was made to set a threshold on dictionary-managed tablespaces.
Action: Check the tablespace type and reissue the command.
ORA-13907: Threshold value is invalid.
Cause: An attempt was made to specify an invalid value for critical or warning thresholds.
Action: Use non-negative integers only for threshold values.
ORA-13908: Invalid combination of metrics id and object type parameters.
Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters.
Action: Specify a valid combination of metrics id and object type parameters.
ORA-13909: Invalid combination of threshold value and operator.
Cause: An attempt was made to specify an invalid combination of threshold value and operator.
Action: Check the operator and threshold values and reissue statement.
ORA-13910: Parameter string cannot be NULL.
Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter.
Action: Specify a valid value for this parameter.
ORA-13911: Threshold not found
Cause: The threshold did not exist with the specified threshold key.
Action: No action required.
ORA-13912: Critical threshold value is less than warning threshold value.
Cause: An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value.
Action: Check the threshold values and reissue the statement.
ORA-13913: The threshold cannot be set when SYSAUX is offline.
Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was offline.
Action: Call SET_THRESHOLD procedure when SYSAUX is online.
ORA-13914: Threshold notification failed.
Cause: An error occurred when sending notification for this threshold.
Action: Make sure you have enough space on SYSAUX tablespace and retry this operation.
ORA-13915: Critical byte based free space threshold value is greater than warning threshold value.
Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based critical threshold value greater than the warning threshold value.
Action: Check the threshold values and reissue the statement.
ORA-13916: Invalid value "string" specified for parameter "string"
Cause: An invalid value was specified for the the given parameter.
Action: Correct the value being specified for the parameter.
ORA-13917: Posting system alert with reason_id string failed with code [string] [string]
Cause: Connection to the database is dead, or invalid parameter to alert routine.
Action: If this condition repeats, please contact Oracle Support.
ORA-13918: Updating system alert with reason_id string failed; previous alert not found
Cause: System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.
Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support.
ORA-13919: Cannot specify values for parameter "string" and for parameter "string"
Cause: Can only specify a value for one or the other.
Action: Pass just one of the parameters.
ORA-13951: MMON sub-action time limit exceeded
Cause: This is an internal Server Manageability Error
Action: Contact Oracle Support Services
ORA-14000: only one LOCAL clause may be specified
Cause: CREATE INDEX statement contained more than one LOCAL clause
Action: Specify LOCAL option at most once
ORA-14001: LOCAL clause contradicts previosly specified GLOBAL clause
Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause
Action: Specify LOCAL or GLOBAL clause, but not both
ORA-14002: only one GLOBAL clause may be specified
Cause: CREATE INDEX statement contained more than one GLOBAL clause
Action: Specify GLOBAL option at most once
ORA-14003: GLOBAL clause contradicts previosly specified LOCAL clause
Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause
Action: Specify GLOBAL or LOCAL clause, but not both
ORA-14004: missing PARTITION keyword
Cause: keyword PARTITION missing
Action: supply missing keyword
ORA-14005: missing RANGE keyword
Cause: keyword RANGE missing
Action: supply missing keyword
ORA-14006: invalid partition name
Cause: a partition name of the form <identifier> is expected but not present.
Action: enter an appropriate partition name.
ORA-14007: missing LESS keyword
Cause: keyword LESS missing
Action: supply missing keyword
ORA-14008: missing THAN keyword
Cause: keyword THAN missing
Action: supply missing keyword
ORA-14009: partition bound may not be specified for a LOCAL index partition
Cause: while parsing a CREATE INDEX statement to create a LOCAL partitioned index, <partition-description> of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table
Action: remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions
ORA-14010: this physical attribute may not be specified for an index partition
Cause: unexpected option was encountered while parsing physical attributes of an index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for Hash partitions
Action: remove invalid option(s) from the list of physical attributes of an index partition
ORA-14011: names assigned to resulting partitions must be distinct
Cause: Names of partitions resulting from splitting of an existing table or index partition are not distinct
Action: rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index
ORA-14012: resulting partition name conflicts with that of an existing partition
Cause: Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index
Action: rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index
ORA-14013: duplicate partition name
Cause: Name of a partition of a table or index being created is not unique
Action: rename partition(s) to ensure that their names are unique among partitions of the table or index being created
ORA-14014: maximum number of partitioning columns is 16
Cause: number of columns in a partitioning column list exceeded the legal limit of 16
Action: modify partitioning column list so that it consists of at most 16 columns
ORA-14015: too many partition descriptions
Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 1048575 (1024K-1).
Action: Reduce number of partitions to not exceed 1048575 (1024K -1).
ORA-14016: underlying table of a LOCAL partitioned index must be partitioned
Cause: User attempted to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned table.
Action: Correct the statement and reenter
ORA-14017: partition bound list contains too many elements
Cause: Partition bound list contained more elements than there are partitioning columns
Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index
ORA-14018: partition bound list contains too few elements
Cause: Partition bound list contained fewer elements than there are partitioning columns
Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index
ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or MAXVALUE)
Action: Ensure that all elements of partition bound list are of valid type
ORA-14020: this physical attribute may not be specified for a table partition
Cause: unexpected option was encountered while parsing physical attributes of a table partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for Hash partitions
Action: remove invalid option(s) from the list of physical attributes of a table partition
ORA-14021: MAXVALUE must be specified for all columns
Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns
Action: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns
ORA-14022: creation of LOCAL partitioned cluster indices is not supported
Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal
Action: Remove LOCAL along with <partition description>s, if any, from the CREATE INDEX statement.
ORA-14023: creation of GLOBAL partitioned cluster indices is not supported
Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal
Action: Remove PARTITION BY RANGE clause along with <partition description>s from the CREATE INDEX statement.
ORA-14024: number of partitions of LOCAL index must equal that of the underlying table
Cause: User attempted to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table.
Action: Correct the CREATE INDEX statement to specify a correct number of partitions
ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log
Cause: PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log
Action: Ensure that a definition of a MATERIALIZED VIEW does not include invalid options
ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive
Cause: definition of a table contained both PARTITION and CLUSTER clauses which is illegal
Action: Remove one of the conflicting clauses
ORA-14027: only one PARTITION clause may be specified
Cause: CREATE TABLE statement contained more than one PARTITION clause
Action: Specify PARTITION option at most once
ORA-14028: missing AT or VALUES keyword
Cause: keyword AT or VALUES missing
Action: supply missing keyword
ORA-14029: GLOBAL partitioned index must be prefixed
Cause: partitioning columns of a global partitioned index must form a prefix of the index" key columns
Action: Ensure that the GLOBAL partitioned index being created is prefixed
ORA-14030: non-existent partitioning column in CREATE TABLE statement
Cause: Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created.
Action: Ensure that all columns in the partitioning column list are columns of the table being created.
ORA-14031: partitioning column may not be of type LONG or LONG RAW
Cause: Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal.
Action: Ensure that no partitioning column is of type LONG or LONG RAW.
ORA-14032: partition bound of partition number string is too high
Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal.
Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.
ORA-14036: partition bound value too large for column
Cause: Length of partition bound value is longer than that of the corresponding partitioning column.
Action: Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns
ORA-14037: partition bound of partition "string" is too high
Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal.
Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.
ORA-14038: GLOBAL partitioned index must be prefixed
Cause: User attempted to create a GLOBAL non-prefixed partitioned index which is illegal
Action: If the user, indeed, desired to create a non-prefixed index, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed
ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE index
Cause: User attempted to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal
Action: If the user, indeed, desired to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index" partitioning columns form a subset of its key columns
ORA-14041: partition bound may not be specified for resulting partitions
Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, <partition-description> of a resulting partition was found to contain VALUES LESS THAN clause which is illegal
Action: remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition
ORA-14042: partition bound may not be specified for a partition being moved, modified or rebuilt
Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal
Action: remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt
ORA-14043: only one partition may be added
Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added
Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas
ORA-14044: only one partition may be moved
Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved
Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas
ORA-14045: only one partition may be modified
Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified
Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas
ORA-14046: a partition may be split into exactly two new partitions
Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split
Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split
ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal
Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement;
ORA-14048: a partition maintenance operation may not be combined with other operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (e.g. MOVE PARTITION) with some other operation (e.g. ADD PARTITION or PCTFREE which is illegal
Action: Ensure that a partition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will
ORA-14049: invalid ALTER TABLE MODIFY PARTITION option
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement for a Range or Composite Range partition.
Action: Specify only legal options.
ORA-14050: invalid ALTER INDEX MODIFY PARTITION option
Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement.
Action: Specify only legal options.
ORA-14051: invalid ALTER MATERIALIZED VIEW option
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW statement.
Action: Specify only legal options.
ORA-14052: partition-extended table name syntax is disallowed in this context
Cause: User attempted to use partition-extended table name syntax in illegal context (i.e. not in FROM-clause or INSERT, DELETE, or UPDATE statement)
Action: Avoid use of partition-extended table name in contexts other those mentioned above.
ORA-14053: illegal attempt to modify string in string statement
Cause: Certain attributes of objects (e.g. tables) may be specified at creation time, but may not be modified using ALTER statement. Unfortunately, user specified one of such attributes.
Action: Ensure that ALTER statement specifies new values only for attributes which may be changed once an object has been created
ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION option
Cause: Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE
Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION
ORA-14055: keyword REBUILD in ALTER INDEX REBUILD must immediately follow <index name>
Cause: ALTER INDEX statement contained REBUILD keyword following some index attributes (e.g. INITRANS.)
Action: Ensure that keyword REBUILD immediately follows the name of the index being altered
ORA-14056: partition number string: sum of PCTUSED and PCTFREE may not exceed 100
Cause: the sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100
ORA-14057: partition "string": sum of PCTUSED and PCTFREE may not exceed 100
Cause: the sum of PCTUSED and PCTFREE for a partition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100
ORA-14058: partition number string: INITRANS value must be less than MAXTRANS value
Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explcitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS
ORA-14059: partition "string": INITRANS value must be less than MAXTRANS value
Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explcitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS
ORA-14060: data type or length of a table partitioning column may not be changed
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition the table named in ALTER TABLE statement, which is illegal
Action: Avoid modifying data type and/or length of table partitioning column(s)
ORA-14061: data type or length of an index partitioning column may not be changed
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition some index defined on the table named in ALTER TABLE statement, which is illegal
Action: Avoid modifying data type and/or length of index partitioning column(s)
ORA-14062: one or more of table"s partitions reside in a read-only tablespace
Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more partitions of which reside in read-only tablespaces, which is illegal
Action: Avoid performing aformentioned operations on a partitioned table one or more partitions of which reside in read-only tablespaces
ORA-14063: Unusable index exists on unique/primary constraint key
Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable.
Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD
ORA-14064: Index with Unusable partition exists on unique/primary constraint key
Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index one or more partitions of which are marked Index Unusable.
Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION
ORA-14065: ALLOCATE STORAGE may not be specified for a partitioned table
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement.
ORA-14066: illegal option for a non-partitioned index-organized table
Cause: An attempt was made to issue a CREATE or ALTER TABLE command on a non-partitioned IOT, but the command contains an option that is legal only for partitioned index-organized tables. Such options are: ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT.
Action: Remove the illegal option(s) from the command.
ORA-14067: duplicate TABLESPACE_NUMBER specification
Cause: TABLESPACE_NUMBER clause was specified more than once for an table, index or an index partition
Action: Correct the code generating text of CREATE INDEX statement sent to the slaves
ORA-14068: TABLESPACE and TABLESPACE_NUMBER may not be both specified
Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, index or an index partition
Action: Correct the code generating text of CREATE INDEX statement sent to the slaves
ORA-14069: invalid TABLESPACE_NUMBER value
Cause: The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF
Action: Correct the code generating text of CREATE INDEX statement sent to the slaves
ORA-14070: option may be specified only for partitioned indices or with REBUILD
Cause: User issued ALTER INDEX statament containing an option which is legal only for partitioned indices or in conjunction with REBUILD against a non-partitioned index. Such options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clause
Action: Remove illegal option(s).
ORA-14071: invalid option for an index used to enforce a constraint
Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint.
Action: Choose one of the valid index options.
ORA-14072: fixed table may not be truncated
Cause: User attempted to truncate a fixed table which is illegal.
Action: Ensure that the table being truncated is not a fixed table.
ORA-14073: bootstrap table or cluster may not be truncated
Cause: User attempted to truncate a bootstrap table or cluster which is illegal
Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster)
ORA-14074: partition bound must collate higher than that of the last partition
Cause: Partition bound specified in ALTER TABLE ADD PARTITION statement did not collate higher than that of the table"s last partition, which is illegal.
Action: Ensure that the partition bound of the partition to be added collates higher than that of the table"s last partition.
ORA-14075: partition maintenance operations may only be performed on partitioned indices
Cause: Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, at best, meaningless
Action: Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned
ORA-14076: submitted alter index partition/subpartition operation is not valid for local partitioned index
Cause: User attempted to either drop, split, add or coalesce a partition or a subpartition of a local index which is illegal.
Action: Ensure that the index named in such statement is a global partitioned index.
ORA-14078: you may not drop the highest partition of a GLOBAL index
Cause: User attempted to drop highest partition of a GLOBAL index, which is illegal.
Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index.
ORA-14079: illegal option for a partition marked Index Unusable
Cause: ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal
Action: Ensure that only valid optins are specified
ORA-14080: partition cannot be split along the specified high bound
Cause: User attempted to split a partition along a bound which either collates higher than that of the partition to be split or lower than that of a partition immediately preceding the one to be split
Action: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher that that of a partition immediately preceding the one to be split
ORA-14081: new partition name must differ from the old partition name
Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name> which is identical to the name of the partition being renamed
Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index
ORA-14082: new partition name must differ from that of any other partition of the object
Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name> which is identical to the name of some existing partition of the object
Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index
ORA-14083: cannot drop the only partition of a partitioned table
Cause: A drop partition command is being executed when there is only one partition in the table
Action: Ensure that there is at least one partition. Drop table to remove all partitions
ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index
Cause: User attempted to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal.
Action: Reenter the statement without TABLESPACE DEFAULT clause.
ORA-14085: partitioned table cannot have column with LONG datatype
Cause: User tried to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table.
Action: LONG data types are not supported with partitioned tables. Create table without LONG column or change table to not partitioned. If adding column, do not use LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non partitioned table.
ORA-14086: a partitioned index may not be rebuilt as a whole
Cause: User attempted to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal
Action: Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and recreate the entire index
ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option
Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]
Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE PARTITION
ORA-14095: ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table
Cause: The table in the EXCHANGE operation is either clustered or partitioned
Action: Ensure that the table with which the partition is being exchanged for is not partitioned or clustered.
ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
Cause: The two tables specified in the EXCHANGE have different number of columns
Action: Ensure that the two tables have the same number of columns with the same type and size.
ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size
Action: Ensure that the two tables have the same number of columns with the same type and size.
ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
Cause: The two tables specified in the EXCHANGE have indexes which are not equivalent
Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same.
ORA-14099: all rows in table do not qualify for specified partition
Cause: There is at least one row in the non partitioned table which does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION
Action: Ensure that all the rows in the segment qualify for the partition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them.
ORA-14100: partition extended table name cannot refer to a remote object
Cause: User attempted to use partition-extended table name syntax in conjunction with remote object name which is illegal
Action: Correct the statement and reenter
ORA-14101: partition extended table name cannot refer to a synonym
Cause: User attempted to use partition-extended table name syntax in conjunction with synonym name which is illegal
Action: Correct the statement and reenter
ORA-14102: only one LOGGING or NOLOGGING clause may be specified
Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.
Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.
ORA-14103: LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed.
Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.
ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
Cause: CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal
Action: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.
ORA-14105: RECOVERABLE/UNRECOVERABLE may not be specified in this context
Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.
Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.
ORA-14106: LOGGING/NOLOGGING may not be specified for a clustered table
Cause: User attempted to specify LOGGING or NOLOGGING clausein CREATE TABLE or ALTER TABLE statement involving a clustered table
Action: Remove offending clause.
ORA-14107: partition specification is required for a partitioned object
Cause: parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects.
Action: supply missing parameter
ORA-14108: illegal partition-extended table name syntax
Cause: Partition to be accessed may only be specified using its name. User attempted to use a partition number or a bind variable.
Action: Modify statement to refer to a partition using its name
ORA-14109: partition-extended object names may only be used with tables
Cause: User attempted to use a partition-extended object name with an object which is not a table.
Action: Avoid using partition-extended name syntax with objects which are not tables
ORA-14110: partitioning column may not be of type ROWID
Cause: Partitioning column specified by the user was of type ROWID, which is illegal.
Action: Ensure that no partitioning column is of type ROWID.
ORA-14111: creation of a GLOBAL partitioned index on clustered tables is not supported
Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal.
Action: Remove PARTITION BY RANGE/HASH clause along with any partition descriptions to create a GLOBAL non-partitioned index on a clustered table
ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition
Cause: Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal
Action: Remove offending clause. Use LOGGING or NOLOGGING instead.
ORA-14113: partitioned table cannot have column with LOB datatype
Cause: User tried to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table.
Action: LOB data types are not supported with partitioned tables. Create table without LOB column or change table to not partitioned. If adding column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non partitioned table.
ORA-14114: partitioned table cannot have column with object, REF, nested table, array datatype
Cause: User tried to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table.
Action: object data types are not supported with partitioned tables. Create table without object column or change table to not partitioned. If adding column, do not use object datatypes. If modifying attributes of a column to change data type to object, it has to be a non partitioned table.
ORA-14115: partition bound of partition number string is too long
Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within legal limit.
ORA-14116: partition bound of partition "string" is too long
Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within legal limit.
ORA-14117: partition resides in offlined tablespace
Cause: User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.
Action: Bring tablespace online before attempting the operation.
ORA-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them.
Action: Ensure that the two tables do not have CHECK constraint defined on any column
ORA-14119: specified partition bound is too long
Cause: Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within legal limit.
ORA-14120: incompletely specified partition bound for a DATE column
Cause: An attempt was made to use a date expression whose format does not fully (i.e. day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT).
Action: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (i.e. day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (i.e. including the century) specification of the year, use TO_DATE() (e.g. TO_DATE("01-01-1999", "MM-DD-YYYY") to fully express the desired date.
ORA-14121: MODIFY DEFAULT ATTRIBUTES may not be combined with other operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal
Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will
ORA-14122: only one REVERSE or NOREVERSE clause may be specified
Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX statement.
Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement.
ORA-14123: duplicate NOREVERSE clause
Cause: NOREVERSE was specified more than once in ALTER INDEX statement.
Action: Remove all but one of the NOREVERSE clauses and reissue the statement.
ORA-14124: duplicate REVERSE clause
Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements.
Action: Remove all but one of the REVERSE clauses and reissue the statement.
ORA-14125: REVERSE/NOREVERSE may not be specified in this context
Cause: REVERSE/NOREVERSE clause is not allowed in this context.
Action: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement.
ORA-14126: only a <parallel clause> may follow description(s) of resulting partitions
Cause: Descriptions of partition(s) resulting from splitting of a table or index partition may be followed by an optional <parallel clause> which applies to the entire statement and which, in turn, may not be followed by any other clause.
Action: Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement.
ORA-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints.
Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.
ORA-14129: INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
Cause: Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command.
Action: Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used.
ORA-14130: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION
Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated.
Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes.
ORA-14131: enabled UNIQUE constraint exists on one of the tables
Cause: One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding.
Action: Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement.
ORA-14132: table cannot be used in EXCHANGE
Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply:

- it is a typed table

- it contains ADT columns

- it contains nested-table columns

- it contains REF columns

- it contains array columns

- it is an index-organized table

- it contains LOB columns

- it is a nested table

- it is created with row dependency and the partitioned table is not

- it is created without row dependency and the partitioned table is

Action: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.
ORA-14133: ALTER TABLE MOVE cannot be combined with other operations
Cause: An attempt was made to combine an ALTER TABLE MOVE statement with another operation, such as MODIFY.
Action: Make sure that MOVE is the only operation specified in ALTER TABLE statement;
ORA-14134: indexes cannot use both DESC and REVERSE
Cause: An attempt was made to make a reverse index with some index columns marked DESC.
Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC.
ORA-14135: a LOB column cannot serve as a partitioning column
Cause: An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column.
Action: Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB.
ORA-14136: ALTER TABLE EXCHANGE restricted by fine-grained security
Cause: User doing exchange does not have full table access due to VPD policies.
Action: Grant exempt priviliges to this user.
ORA-14137: Table in partially dropped state, submit DROP TABLE PURGE
Cause: An attempt was made to access a partitioned table in a partially dropped state.
Action: Submit DROP TABLE <table> PURGE to drop the table.
ORA-14138: An unexpected error encountered during drop table operation
Cause: Drop table encountered an unexpected error.
Action: a. Submit drop table <table> purge, or b. If the situation described in the next error on the stack can be corrected, do so. c. Contact Oracle Support.
ORA-14150: missing SUBPARTITION keyword
Cause: keyword SUBPARTITION missing
Action: supply missing keyword
ORA-14151: invalid table partitioning method
Cause: Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, or Composite Range/Hash (R+H).
Action: Specify one of valid partitioning methods
ORA-14152: invalid number of partitions specified in PARTITIONS clause
Cause: number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-1048575)
Action: Specify a number between 1 and 1024K-1 in the number-of-partitions clause
ORA-14153: only one of STORE IN or <partition-description> clause may be specified
Cause: both STORE IN and <partition-description> clauses were specified in a CREATE TABLE|INDEX command
Action: Remove one of offending clauses
ORA-14154: only one of STORE IN or <subpartition-description> clause may be specified
Cause: both STORE IN and <subpartition-description> clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a Composite Range partitioned object
Action: Remove one of offending clauses
ORA-14155: missing PARTITION or SUBPARTITION keyword
Cause: expect either PARTITION or SUBPARTITION keyword but none was supplied
Action: supply missing keyword
ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
Cause: number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-1048575)
Action: Specify a number between 1 and 1024K-1 in the number-of-subpartitions clause
ORA-14157: invalid subpartition name
Cause: a subpartition name of the form <identifier> is expected but not present.
Action: enter an appropriate subpartition name.
ORA-14158: too many subpartition descriptions
Cause: CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 1048575.
Action: Reduce number of subpartitions to not exceed 1024K-1.
ORA-14159: duplicate subpartition name
Cause: Name of a subpartition of a table or index being created is not unique
Action: rename subpartition(s) to ensure that their names are unique among subpartitions of the table or index being created
ORA-14160: this physical attribute may not be specified for a table subpartition
Cause: unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option
Action: remove invalid option(s)
ORA-14161: subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100
Cause: the sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100
ORA-14162: subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100
Cause: the sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100
ORA-14163: subpartition number string: INITRANS value must be less than MAXTRANS value
Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS
ORA-14164: subpartition "string": INITRANS value must be less than MAXTRANS value
Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS
ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal
Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will
ORA-14166: missing INTO keyword
Cause: keyword INTO missing
Action: supply missing keyword
ORA-14167: only one subpartition may be moved
Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to be moved
Action: Ensure that the statement describes exactly one subpartition to be moved and that it does not contain any commas
ORA-14168: only one subpartition may be modified
Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to be modified
Action: Ensure that the statement describes exactly one subpartition to be modified and that it does not contain any commas
ORA-14169: invalid ALTER TABLE MODIFY SUBPARTITION option
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement.
Action: Specify only legal options.
ORA-14170: cannot specify <partition-description> clause in CREATE TABLE|INDEX
Cause: User requested to generate default partition description(s) (possibly via PARTITIONS <number-of-partitions>) while at the same time specified <partition-description> clause which is illegal
Action: Remove one of offending clauses.
ORA-14171: cannot specify <subpartition-description> clause in CREATE|ALTER TABLE
Cause: User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified <subpartition-description> clause which is illegal
Action: Remove one of offending clauses.
ORA-14172: invalid ALTER TABLE EXCHANGE SUBPARTITION option
Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]
Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION
ORA-14173: illegal subpartition-extended table name syntax
Cause: Subpartition to be accessed may only be specified using its name. User attempted to use a subpartition number or a bind variable.
Action: Modify statement to refer to a subpartition using its name
ORA-14174: only a <parallel clause> may follow COALESCE PARTITION|SUBPARTITION
Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional <parallel clause>. No partition/subpartition attributes may be specified
Action: Ensure that no partition/subpartition attribute was specified.
ORA-14175: a subpartition maintenance operation may not be combined with other operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (e.g. MOVE SUBPARTITION) with some other operation (e.g. MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal
Action: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will
ORA-14176: this attribute may not be specified for a hash partition
Cause: An invalid option was encountered while parsing physical attributes of a partition of an object partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions.
Action: Remove the invalid option(s).
ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a range/list/composite range list partitioned table
Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index on range/list/composite range list partitioned table
ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes
Cause: STORE IN (DEFAULT) is valid only for local indexes.
Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove STORE IN clause and specify tablespaces individually for each index partition.
ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL index
Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range/System/Hash partitioned LOCAL index object, which is illegal.
Action: Replace TABLESPACE DEFAULT with TABLESPACE <ts_name> or remove it.
ORA-14185: incorrect physical attribute specified for this index partition
Cause: unexpected option was encountered while parsing physical attributes of a local index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions STORE IN () is also disallowed for all but Composite Range partitions
Action: remove invalid option(s) from the list of physical attributes of an index partition
ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table
Cause: User attempted to create a LOCAL partitioned index with a number of sub-partitions which is different from that of the underlying table.
Action: Correct the CREATE INDEX statement to specify a correct number of sub-partitions
ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table
Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with the underlying table. The partitioning types are mismatched.
Action: Correct the CREATE INDEX statement to ensure that the index partitionining method is consistent with that of the base table
ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index
Cause: User attempted to create a UNIQUE partitioned index whose sub-partitioning columns do not form a subset of its key columns which is illegal
Action: If the user, indeed, desired to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index" subpartitioning columns form a subset of its key columns
ORA-14189: this physical attribute may not be specified for an index subpartition
Cause: unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option
Action: remove invalid option(s)
ORA-14190: only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
Cause: One of three possible actions caused the error: 1) ENABLE ROW MOVEMENT was specified more than once. 2) DISABLE ROW MOVEMENT was specified more than once. 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified.
Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses; then, reissue the command.
ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.
ORA-14192: cannot modify physical index attributes of a Hash index partition
Cause: User attempted to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a Hash partitioned index
Action: Remove the physical attributes one is trying to modify
ORA-14193: invalid ALTER INDEX MODIFY SUBPARTITION option
Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement.
Action: Specify only legal options.
ORA-14194: only one subpartition may be rebuilt
Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt
Action: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas
ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.
ORA-14196: Specified index cannot be used to enforce the constraint.
Cause: The index specified to enforce the constraint is unsuitable for the purpose.
Action: Specify a suitable index or allow one to be built automatically.
ORA-14251: Specified subpartition does not exist
Cause: Subpartition not found for the object.
Action: Retry with correct subpartition name.
ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a Hash partition.
Action: Specify only legal options.
ORA-14253: table is not partitioned by Composite Range method
Cause: The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned by Composite Range method
Action: Ensure that the table is partitioned by Composite Range method
ORA-14254: cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a Range or Composite Range partitioned table which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION.
ORA-14255: table is not partitioned by Range, Composite Range or List method
Cause: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by Range, List or Composite Range method
Action: Ensure that the table is partitioned by Range, List or Composite Range method
ORA-14256: invalid resulting partition description(s)
Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or <subpartition-description> clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a Composite Range partitioned table which is illegal
Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range method
ORA-14257: cannot move partition other than a Range or Hash partition
Cause: User attempt to move a partition that is not a Range or Hash partition which is illegal
Action: Specify MOVE PARTITION for a Range or Hash partition only
ORA-14258: invalid partition description
Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or <subpartition-description> clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a Composite Range/Hash partitioned table which is illegal
Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range/Hash method
ORA-14259: table is not partitioned by Hash method
Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method
Action: Specify valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method
ORA-14260: incorrect physical attribute specified for this partition
Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING option to a Hash partition via ALTER TABLE ADD/MOVE PARTITION command which is illegal. Only TABLESPACE may be specified.
Action: Remove invalid option(s)
ORA-14261: partition bound may not be specified when adding this Hash partition
Cause: User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a Hash partitioned table which is illegal
Action: Remove VALUES LESS THAN clause from the description of partition being added
ORA-14262: new subpartition name must differ from the old subpartition name
Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying <new-subpartition-name> which is identical to the name of the subpartition being renamed
Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index
ORA-14263: new subpartition name must differ from that of any other subpartition of the object
Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying <new-subpartition-name> which is identical to the name of some existing subpartition of the object
Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index
ORA-14264: table is not partitioned by Composite Range method
Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method
Action: Ensure that the table is partitioned by Composite method
ORA-14265: data type or length of a table subpartitioning column may not be changed
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal
Action: Avoid modifying data type and/or length of table subpartitioning column(s)
ORA-14266: data type or length of an index subpartitioning column may not be changed
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal
Action: Avoid modifying data type and/or length of index subpartitioning column(s)
ORA-14267: cannot specify PARALLEL clause when adding a (Composite) Range partition
Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a Range or Composite Range partition which is illegal
Action: Remove the PARALLEL clause.
ORA-14268: subpartition "string" of the partition resides in offlined tablespace
Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.
Action: Bring tablespace online before attempting the operation.
ORA-14269: cannot exchange partition other than a Range or Hash partition
Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a Range or Hash partition which is illegal
Action: Specify EXCHANGE PARTITION for a Range or Hash partition only
ORA-14270: table is not partitioned by Range or Hash or List method
Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Range or Hash method which is illegal.
Action: Ensure that the table is partitioned by Range or Hash method
ORA-14271: table is not partitioned by Composite Range method
Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Composite Range method which is illegal.
Action: Ensure that the table is partitioned by Composite Range method
ORA-14272: only a partition with higher bound can be reused
Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal.
Action: Use the higher-bound partition to be the resulting partition or specify a new partition name
ORA-14273: lower-bound partition must be specified first
Cause: User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal
Action: Specify lower-bound partition then higher-bound partition
ORA-14274: partitions being merged are not adjacent
Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal
Action: Specify two partitions that are adjacent
ORA-14275: cannot reuse lower-bound partition as resulting partition
Cause: User attempt to reuse lower-bound partition of the partitions being merged which is illegal
Action: Specify new resulting partition name or reuse the higher-bound partition only
ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned
Action: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered.
ORA-14277: tables in EXCHANGE SUBPARTITION must have the same number of columns
Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns
Action: Ensure that the two tables have the same number of columns with the same type and size.
ORA-14278: column type or size mismatch in EXCHANGE SUBPARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size
Action: Ensure that the two tables have the same number of columns with the same type and size.
ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have indexes which are not equivalent
Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same.
ORA-14280: all rows in table do not qualify for specified subpartition
Cause: There is at least one row in the non partitioned table which does not qualify for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION
Action: Ensure that all the rows in the segment qualify for the subpartition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that subpartition to find out the invalid rows and delete them.
ORA-14281: CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them.
Action: Ensure that the two tables do not have CHECK constraint defined on any column
ORA-14282: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints.
Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.
ORA-14283: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated.
Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes.
ORA-14284: one or more of table"s subpartitions reside in a read-only tablespace
Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more subpartitions of which reside in read-only tablespaces, which is illegal
Action: Avoid performing aformentioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces
ORA-14285: cannot COALESCE the only partition of this hash partitioned table or index
Cause: A COALESCE PARTITION command was issued when there is only one partition in the table or index, which is illegal
Action: Ensure that there is at least one partition. Drop the table or index to remove all partitions.
ORA-14286: cannot COALESCE the only subpartition of this table partition
Cause: A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal
Action: Ensure that there is at least one subpartition. Drop partition to remove all subpartitions.
ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index
Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal
Action: REBUILD the index partition, a subpartition at a time
ORA-14288: index is not partitioned by Composite Range method
Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by Composite Range method
Action: none
ORA-14289: cannot make local index partition of Composite Range partitioned table unusable
Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal
Action: none
ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints.
Action: Ensure that the two tables do not have PRIMARY KEY constraints defined on any column or disable all PRIMARY KEY constraints on both tables. Then retry the operation.
ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table
Cause: A composite partition can only be exchanged with a partitioned table.
Action: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite.
ORA-14292: Partitioning type of table must match subpartitioning type of composite partition
Cause: When exchanging a partitioned table with a composite partition the partitioning type of the table must match the subpartitioning type of the composite partition.
Action: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition.
ORA-14293: Number of partitioning columns does not match number of subpartitioning columns
Cause: When exchanging a partitioned table with a composite partition the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition.
Action: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the the composite partition.
ORA-14294: Number of partitions does not match number of subpartitions
Cause: When exchanging a partitioned table with a composite partition the number of partitions of the table must match the number of subpartitions of the composite partition.
Action: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition.
ORA-14295: column type or size mismatch between partitioning columns and subpartitioning columns
Cause: When exchanging a partitioned table with a composite partition the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition.
Action: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition.
ORA-14296: Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. For index organized tables, either the block sizes of the index or the overflow (or both) do not match.
Action: Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. For index organized tables, ensure that the block sizes of both the index and the overflow of the two tables match.
ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The block sizes of a pair of corresponding LOB columns of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of corresponding pairs of LOB columns of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
ORA-14299: total number of partitions/subpartitions exceeds the maximum limit
Cause: The total number of combined fragments specified in partitions /subpartitions exceeds 1048575.
Action: Reissue the statement with fewer number of fragments
ORA-14301: table-level attributes must be specified before partition-level attributes
Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of LOB columns were encountered after processing partition-level attributes of LOB columns or while processing CREATE TABLE statement, table-level attributes of LOB columns were encountered after processing partition descriptions.
Action: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement.
ORA-14302: only one list of added-LOB-storage-clauses can be specified in a statement
Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list.
Action: Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement.
ORA-14303: partitions or subpartitions are not in the right order
Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal
Action: Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement.
ORA-14304: List partitioning method expects a single partitioning column
Cause: number of columns in a partitioning column list exceeded the legal limit of 1 for List partitioned objects
Action: modify partitioning column list so that it consists of at most 1 column
ORA-14305: List value "string" specified twice in partition "string"
Cause: A list value cannot be specified more that once
Action: Remove one of the specifications of the value
ORA-14306: List value "string" specified twice in partitions "string", "string"
Cause: A list value cannot be specified more that once
Action: Remove one of the specifications of the value
ORA-14307: partition contains too many list values
Cause: Partition list contains more than 524288 list values
Action: Reduce the number of values to not exceed 524288 values
ORA-14308: partition bound element must be one of: string, datetime or interval literal, number, or NULL
Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or NULL)
Action: Ensure that all elements of partition bound list are of valid type
ORA-14309: Total count of list values exceeds maximum allowed
Cause: Partitioned object contains more than 524288 list values
Action: Reduce number of values to less than 524288.
ORA-14310: VALUES LESS THAN or AT clause cannot be used with List partitioned tables
Cause: VALUES LESS THAN or AT clause can be used only with Range partitioned tables
Action: Use VALUES (<value list>) clause with List partitioned tables
ORA-14311: Expecting VALUES LESS THAN or AT clause
Cause: VALUES (<value list>) clause can be used only with List partitioned tables
Action: Use VALUES LESS THAN clause with Range partitioned tables
ORA-14312: Value string already exists in partition string
Cause: One of the list values in the ADD PARTITION or ADD VALUES statement already exists in another partition
Action: Remove the duplicate value from the statement and try again
ORA-14313: Value string does not exist in partition string
Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the partition
Action: Remove the value from the statement and try again
ORA-14314: resulting List partition(s) must contain atleast 1 value
Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value
Action: Ensure that each of the resulting partitions contains atleast 1 value
ORA-14315: cannot merge a partition with itself
Cause: The same partition name was specified twice for the merge operation
Action: Re-submit operation with 2 distinct partition names
ORA-14316: table is not partitioned by List method
Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects
Action: Re-issue the command against a List partitoned object.
ORA-14317: cannot drop the last value of partition
Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition
Action: Cannot execute the command, unless two or more values exist for partition
ORA-14318: DEFAULT partition must be last partition specified
Cause: A partition description follows the one describing the default partition
Action: Ensure that the DEFAULT partition is the last partition description
ORA-14319: DEFAULT cannot be specified with other values
Cause: DEFAULT keyword has been specified along with other values when specifying the values for a list partition
Action: Ensure that if DEFAULT is specified, it is the only value specified
ORA-14320: DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
Cause: DEFAULT keyword has been specified when doing a ADD VALUES or DROP VALUES or SPLIT partition or subpartition.
Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operation.
ORA-14321: cannot add/drop values to DEFAULT partition
Cause: A ADD/DROP VALUES operation is being done on the default partition
Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition
ORA-14322: DEFAULT partition already exists
Cause: A partition already exists with DEFAULT value
Action: none
ORA-14323: cannot add partition when DEFAULT partition exists
Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists
Action: Issue a SPLIT of the DEFAULT partition instead
ORA-14324: values being added already exist in DEFAULT partition
Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT partition
Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into the partition to which values need to be added
ORA-14325: only LOCAL indexes may be specified in this clause
Cause: A global index has been specified in the UPDATE INDEXES (..) clause
Action: Only specify local indexes when using this clause
ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified in the UPDATE INDEXES (..) clause
Action: Do not specify any of these indexes when using this clause
ORA-14327: Some index [sub]partitions could not be rebuilt
Cause: The first phase (partition DDL and index [sub]partition placement) completed successfully. During the second phase, some of the index [sub]partitions could not be rebuilt.
Action: .
ORA-14329: domain index [sub]partitions cannot be renamed in this clause
Cause: The user tried to rename a domain index [sub]partition in the UPDATE INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION operation. This is not allowed.
Action: Leave the name blank or use the same name.
ORA-14400: inserted partition key does not map to any partition
Cause: An attempt was made to insert a record into, a Range or Composite Range object, with a concatenated partition key that is beyond the concatenated partition bound list of the last partition -OR- An attempt was made to insert a record into a List object with a partition key that did not match the literal values specified for any of the partitions.
Action: Do not insert the key. Or, add a partition capable of accepting the key, Or add values matching the key to a partition specification
ORA-14401: inserted partition key is outside specified partition
Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement
Action: do not insert the key or insert it in another partition
ORA-14402: updating partition key column would cause a partition change
Cause: An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition
Action: Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key.
ORA-14403: cursor invalidation detected after getting DML partition lock
Cause: cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. This error is never returned to user, because is caught in opiexe() and the DML statement is retried.
Action: nothing to be done, error should never be returned to user
ORA-14404: partitioned table contains partitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace
Action: find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace
ORA-14405: partitioned index contains partitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.
Action: find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.
ORA-14406: updated partition key is beyond highest legal partition key
Cause: At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition.
Action: Do not update the key. Or, add a partition capable of accepting the key.
ORA-14407: partitioned table contains subpartitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace
Action: find tables with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move subpartitions to a different tablespace
ORA-14408: partitioned index contains subpartitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains indexes whose subpartitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.
Action: find indexes with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.
ORA-14409: inserted partition key is outside specified subpartition
Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated subpartition bound lists that delimit the subpartition named in the INSERT statement
Action: do not insert the key or insert it in another subpartition
ORA-14450: attempt to access a transactional temp table already in use
Cause: An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session.
Action: do not attempt to access the temporary table until the concurrent transaction has committed or aborted.
ORA-14451: unsupported feature with temporary table
Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause.
Action: do not do that.
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
Cause: An attempt was made to create, alter or drop an index on temporary table which is already in use.
Action: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions.
ORA-14453: attempt to use a LOB of a temporary table, whose data has alreadybeen purged
Cause: An attempt was made to use LOB from a temporary table whose data has been dropped either because table was transaction-specific and transaction has commited or aborted, table was truncated or session which created this LOB has ended.
Action: This LOB locator is invalid and cannot be used.
ORA-14454: attempt to reference temporary table in a referential integrity constraint
Cause: An attempt was made to reference temporary table in a referencial integrity constraint. This is not supported.
Action: Use triggers.
ORA-14455: attempt to create referential integrity constraint on temporary table
Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported.
Action: Use triggers.
ORA-14456: cannot rebuild index on a temporary table
Cause: An attempt was made to rebuild an index on a temp table.
Action: The index data is anyway lost at end of session/transaction.
ORA-14457: disallowed Nested Table column in a Temporary table
Cause: An attempt made to create a Nested Table column in a temporary table. This is not supported.
Action: Do not specify these datatypes for temporary tables.
ORA-14458: attempt was made to create a temporary table with INDEX organization
Cause: An attempt was made to create an Index Organized Temporary table. This is not supported.
Action: Create the table with HEAP organization and the primary key.
ORA-14459: missing GLOBAL keyword
Cause: keyword GLOBAL is missing while creating temporary table.
Action: supply keyword.
ORA-14460: only one COMPRESS or NOCOMPRESS clause may be specified
Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more than once, or both COMPRESS and NOCOMPRESS were specified.
Action: specify each desired COMPRESS or NOCOMPRESS clause option only once.
ORA-14461: cannot REUSE STORAGE on a temporary table TRUNCATE
Cause: REUSE STORAGE was specified with TRUNCATE on a temporary table. This is unsupported as it is meaningless.
Action: Specify DROP STORAGE instead (which is the default).
ORA-14500: LOCAL option not valid without partition name
Cause: Incorrect syntax specified
Action: Retry the command
ORA-14501: object is not partitioned
Cause: Table or index is not partitioned. Invalid syntax.
Action: Retry the command with correct syntax.
ORA-14503: only one partition name can be specified
Cause: More than one partition name has been specified for analyze
Action: Specify one partition name.
ORA-14504: syntax not supported for analyze
Cause: A partition/subpartition number or bind variable has been used
Action: Specify a valid partition/subpartition name.
ORA-14505: LOCAL option valid only for partitioned indexes
Cause: Incorrect syntax specified
Action: Retry the command
ORA-14506: LOCAL option required for partitioned indexes
Cause: Incorrect syntax specified
Action: Retry the command
ORA-14507: partition corrupt. all rows do not fall within partition bounds
Cause: The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation
Action: Delete rows in partition which do not qualify
ORA-14508: specified VALIDATE INTO table not found
Cause: The specified table either does not exist or user does not have the proper privleges.
Action: Specify the correct table to use.
ORA-14509: specified VALIDATE INTO table form incorrect
Cause: The specified table does not have the proper field definitions.
Action: Specify the correct table to use. See utlvalid.sql for more information.
ORA-14510: can specify VALIDATE INTO clause only for partitioned tables
Cause: The VALIDATE INTO has been specified for a non partitioned table or cluster or index.
Action: Use syntax correctly
ORA-14511: cannot perform operation on a partitioned object
Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes.
Action: Retry the command with correct syntax.
ORA-14512: cannot perform operation on a clustered object
Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes.
Action: Retry the command with correct syntax.
ORA-14513: partitioning column may not be of object datatype
Cause: Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal.
Action: Ensure that no partitioning column is an object datatype.
ORA-14514: LOCAL option not valid without subpartition name
Cause: Incorrect syntax specified
Action: Retry the command
ORA-14515: only one aubpartition name can be specified
Cause: More than one subpartition name has been specified for analyze
Action: Specify one subpartition name.
ORA-14516: subpartition corrupt. all rows do not fall within subpartition bounds
Cause: The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation
Action: Delete rows in subpartition which do not qualify
ORA-14517: subpartition of index "string.string" is in unusable state
Cause: An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation
Action: REBUILD the unusable index subpartition
ORA-14518: partition contains rows corresponding to values being dropped
Cause: table partition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and reissue statement
ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size.
Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size.
ORA-14520: Tablespace string block size [string] does not match existing object block size [string]
Cause: A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object"s default tablespace (or one of the object"s partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object"s partitions/subpartitions.
Action: Specify a tablespace of the same block size as the partitioned object.
ORA-14521: Default tablespace string block size [string] for string string does not match existing string block size [string]
Cause: A DDL statement was issued that would require creation of a new partition/subpartition in the object-level default tablespace of an existing partitioned object. However, the object-level default tablespace block size does not match the block size of the partitioned object.
Action: Either (1) Modify the default tablespace of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created.
ORA-14522: Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
Cause: A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object.
Action: Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created.
ORA-14523: Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
Cause: A DDL statement was issued that would require a partition/subpartition of a local index/LOB column to be co-located with the corresponding partition/subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column/local index are different.
Action: Either (1) Specify an object-level default tablespace (or partition-level default tablespace for the appropriate partition, if composite partitioning is used) for the partitioned local index/LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose block size does not match that of the base table.
ORA-14551: cannot perform a DML operation inside a query
Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave.
Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave.
ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML
Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement.
Action: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation.
ORA-14553: cannot perform a lob write operation inside a query
Cause: A lob write operation cannot be performed inside a query or a PDML slave.
Action: Ensure that the offending lob write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave.
ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
Cause: Cannot specify these clauses while specifying a template
Action: Correct the subpartition template clause.
ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table
Cause: SUBPARTITION TEMPLATE can be specified only for composite partitioned tables
Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or non-composite partitioned tables.
ORA-14603: [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
Cause: This syntax is valid only if subpartitioning dimension is hash
Action: none
ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
Cause: Once a subpartition template has been specified during a CREATE TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere else
Action: Remove either the SUBPARTITIONS | STORE IN or remove the SUBPARTITION TEMPLATE clause
ORA-14605: Name missing for subpartition / lob segment in template
Cause: A subpartition / lob segment was not specified a name in the template descriptions
Action: All subpartitions / lob segments must have names specified in the template
ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string
Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions
Action: Either specify tablespaces for all or for none of the subpartitions
ORA-14607: Tablespace was not specified for previous subpartitions in template but is specified for string
Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions
Action: Either specify tablespaces for all or for none of the subpartitions
ORA-14608: Tablespace was specified for the previous lob segments of column string in template but is not specified for string
Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column
Action: Either specify tablespaces for all or for none of the lob segments
ORA-14609: Tablespace was not specified for the previous lob segments of column string in template but is specified for string
Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column
Action: Either specify tablespaces for all or for none of the lob segments
ORA-14610: Lob attributes not specified for lob column string for subpartition string
Cause: Lob attributes of a column must be specified for all subpartitions or must not be specified at all
Action: Ensure lob attributes of a column are specified for all subpartitions or not specified at all
ORA-14611: Duplicate subpartition name string in template
Cause: A subpartition name cannot be duplicated within the template
Action: Rename one of the subpartitions.
ORA-14612: Duplicate lob segment name string for lob column string in template
Cause: Two lob segments of the same column were given the same name in the template
Action: Rename one of the lob segments
ORA-14613: Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
Cause: Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier
Action: Shorten either partition or template name.
ORA-14614: List value "string" specified twice in subpartition "string"
Cause: A list value cannot be specified more that once
Action: Remove one of the specifications of the value
ORA-14615: List value "string" specified twice in subpartitions "string", "string"
Cause: A list value cannot be specified more that once
Action: Remove one of the specifications of the value
ORA-14616: table is not subpartitioned by List method
Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD|DROP VALUES or ALTER TABLE DROP|SPLIT|MERGE SUBPARTITION can only be performed on List subpartitioned objects
Action: Re-issue the command against a List subpartitoned object.
ORA-14617: cannot add/drop values to DEFAULT subpartition
Cause: A ADD/DROP VALUES operation is being done on the default subpartition
Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition
ORA-14618: cannot drop the last value of subpartition
Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition
Action: Cannot execute the command, unless two or more values exist for subpartition
ORA-14619: resulting List subpartition(s) must contain at least 1 value
Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value
Action: Ensure that each of the resulting subpartitions contains atleast 1 value
ORA-14620: DEFAULT subpartition already exists
Cause: A subpartition already exists with DEFAULT value
Action: Remove the DEFAULT value from the list specified
ORA-14621: cannot add subpartition when DEFAULT subpartition exists
Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists
Action: Issue a SPLIT of the DEFAULT subpartition instead
ORA-14622: Value string already exists in subpartition string
Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition
Action: Remove the duplicate value from the statement and try again
ORA-14623: Value string does not exist in subpartition string
Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition
Action: Remove the value from the statement and try again
ORA-14624: DEFAULT subpartition must be last subpartition specified
Cause: A subpartition description follows the one describing the default subpartition
Action: Ensure that the DEFAULT subpartition is the last subpartition description
ORA-14625: subpartition contains rows corresponding to values being dropped
Cause: table subpartition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and reissue statement
ORA-14626: values being added already exist in DEFAULT subpartition
Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition
Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added
ORA-14627: Invalid operation was specified on a GLOBAL partitioned index
Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index
Action: Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned
ORA-14628: specification of bounds is inconsistent with LIST method
Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method
Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions
ORA-14629: cannot drop the only subpartition of a partition
Cause: A drop subpartition command is being executed when there is only one subpartition in the partition
Action: none
ORA-14630: subpartition resides in offlined tablespace
Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.
Action: Bring tablespace online before attempting the operation.
ORA-14631: the partition bounds do not match the subpartition bounds of the partition
Cause: When exchanging a partitioned table with a composite partition the bounds that describe the partitions of the table must match the bounds that describe the subpartitions of the composite partition.
Action: Ensure that the bounds describing partitions in the partitioned table is the same as the bounds of the subpartitions in the the composite partition.
ORA-14632: cannot specify PARALLEL clause when adding a List subpartition
Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL clause for a List subpartition of a Range/List partitioned object which is illegal
Action: Remove the PARALLEL clause.
ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table.
Action: Remove clause and reissue operation
ORA-14634: Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
Cause: During a split or a merge of a partition of a range list partitioned table you cannot specify any subpartitioning information for the resulting partition (s)
Action: Remove all subpartitioning information from the DDL.
ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS
Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE
Action: Ensure that the statement describes exactly one subpartition as the target that need to be MERGEd
ORA-14636: only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT
Action: Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation
ORA-14637: cannot merge a subpartition with itself
Cause: The same subpartition name was specified twice for the merge operation
Action: Re-submit operation with 2 distinct subpartition names within the same composite partition
ORA-14638: cannot MERGE subpartitions in different Range Composite partitions
Cause: Attempted to MERGE subpartitions in different Range Composite partitions
Action: Reissue the command after ensuring that the 2 subpartitions being merged lie in the same composite partition
ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition
Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method
Action: Reissue the command after ensuring that the SUBPARTITIONS clause is not specified, to specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause
ORA-14640: add/coalesce index partition operation is valid only for hash partitioned global indexes
Cause: User attempted to add or coalesce an index partition of a global index not partitioned by hash method.
Action: Issue the statement on a global index partitioned by hash method. or if the index is partitioned by range method consider using split/drop instead of add/coalesce.
ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed"
Action: Re-issue the stament after removing the STORE-IN clause
ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the INCLUDING INDEXES option has been specified and the tables have different hakan factors.
Action: Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable.
ORA-14643: Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
Cause: Either records_per_block has been minimized for one of the tables to be exchanged, but not the other, or the hakan factors for the tables to be exchanged are not equal.
Action: If records_per_block has been minimized for one of the tables, but not the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables, or perform alter table with the MINIMIZE RECORDS_PER_BLOCK for both tables. If the hakan factors do not match perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.
ORA-14644: table is not subpartitioned by Hash method
Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects
Action: Re-issue the command against a Hash subpartitoned object.
ORA-14645: STORE IN clause cannot be specified for Range List objects
Cause: A STORE IN clause was specified for Range List partitioned object
Action: Re-issue the command after removng the STORE IN clause
ORA-14646: Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
Cause: The first time a table is altered to include compression, it cannot have a usable bitmap index (partition). Subsequent alter table statements involving compression do not have this same restriction.
Action: A) Drop any bitmap indexes defined on the table, and re-create them once the operation is complete or, B) Mark all index fragments of all bitmap indexes defined on the table UNUSABLE and rebuild them once the operation is complete.
ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user
Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a non-SYS user, user should minimally have DML privileges
Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML privileges on object, or non-SYS user should connect as SYS
ORA-15000: command disallowed by current instance type
Cause: The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance.
Action: Connect to the correct instance type and re-issue the command.
ORA-15001: diskgroup "string" does not exist or is not mounted
Cause: An operation failed because the diskgroup specified does not exist or is not mounted by the current ASM instance.
Action: Verify that the diskgroup name used is valid, that the diskgroup exists, and that the diskgroup is mounted by the current ASM instance.
ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters
Cause: The LOCK_NAME_SPACE initialization parameter contained a value that is too long.
Action: Correct the LOCK_NAME_SPACE initialization parameter.
ORA-15003: diskgroup "string" already mounted in another lock name space
Cause: The diskgroup could not be mounted by the ASM instance because it was operating in a lockspace different than another existing
Action: Check the LOCK_NAME_SPACE initialization parameter value, or dismount the diskgroup from the other ASM instances.
ORA-15004: alias "string" does not exist
Cause: The specified alias did not exist within the diskgroup.
Action: Check the alias name and diskgroup name.
ORA-15005: name "string" is already used by an existing alias
Cause: An existing alias in the diskgroup used the same name.
Action: Select another alias name, or drop the existing alias.
ORA-15006: template "string" does not exist
Cause: The specified template did not exist within the diskgroup.
Action: Check the template name and diskgroup name.
ORA-15007: name is already used by an existing template
Cause: A template with the same name already exists.
Action: Select another template name, or drop the existing template.
ORA-15008: cannot drop system template
Cause: The specified template was created by the system and must always exist for proper operation.
Action: Select another template name.
ORA-15009: ASM disk "string" does not exist
Cause: The specified ASM disk was not found.
Action: Check the ASM disk name.
ORA-15010: name is already used by an existing ASM disk
Cause: The specified name was already used in this diskgroup.
Action: Specify a different ASM disk name.
ORA-15011: failure group "string" contains no members
Cause: The specified name did not match the failure group of any disks in the diskgroup. This usually indicates that the failure group name was specified incorrectly.
Action: Check the failure group name.
ORA-15012: ASM file "string" does not exist
Cause: The ASM file was not found.
Action: Check the ASM file name.
ORA-15013: diskgroup "string" is already mounted
Cause: An ALTER DISKGROUP MOUNT command specified the name of a diskgroup which is already mounted by the current ASM instance.
Action: Check the name of the diskgroup.
ORA-15014: location "string" is not in the discovery set
Cause: The operating system path specified was outside the set of disks that are discovered by the instance.
Action: Specify a operating system path within the set of disks that are discovered based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the ASM_DISKSTRING parameter.
ORA-15017: diskgroup "string" cannot be mounted
Cause: The specified diskgroup could not be mounted.
Action: Check for additional errors reported.
ORA-15018: diskgroup cannot be created
Cause: The specified diskgroup could not be created.
Action: Check for additional errors reported.
ORA-15019: discovered duplicate path "string" for "string"
Cause: The discovery encountered multiple paths to the same disk.
Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.
ORA-15020: discovered duplicate ASM disk "string"
Cause: The discovery encountered two disks claiming to be the same named ASM disk.
Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.
ORA-15021: parameter "string" is not valid in string instance
Cause: The specified parameter was not supported when starting an instance of this type.
Action: Delete the specified parameter from the INIT.ORA file.
ORA-15023: reached maximum allowable number of disks string
Cause: An attempt was made to add another disk to a diskgroup which already contains the maximum number of disks allowed.
Action: Consider dropping existing disks from the diskgroup before adding additional ones, or create a new diskgroup.
ORA-15024: discovered duplicately numbered ASM disk string
Cause: The discovery encountered two disks claiming to have the same ASM disk number.
Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.
ORA-15025: could not open disk "string"
Cause: The specified disk could not be opened.
Action: Check the additional error messages, if any.
ORA-15026: disk "string" is not an ASM disk
Cause: The disk did not contain a valid ASM disk header.
Action: Check to see if the data on the disk has been changed by some system administrator action.
ORA-15027: active use of diskgroup "string" precludes its dismount
Cause: An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup which had database client instances with open files in the diskgroup. Diskgroups cannot be dismounted until all open files in the diskgroup are closed by the database client instances.
Action: Stop all clients that are using this diskgroup and retry the ALTER DISKGROUP ... DISMOUNT command. The V$ASM_CLIENT fixed view in an ASM instance provides a list of its active database client instances.
ORA-15028: ASM file "string" not dropped; currently being accessed
Cause: An attempt was made to drop an ASM file, but the file was being accessed by one or more database instances and therefore could not be dropped.
Action: Shut down all database instances that might be accessing this file and then retry the drop command.
ORA-15029: disk "string" is already mounted by this instance
Cause: An attempt was made to add to a diskgroup a disk that was already mounted by the current instance as part of some (possibly other) diskgroup.
Action: Specify a different disk in the command. Note that not even the FORCE option can be used to correct the situation until the diskgroup containing the disk becomes dismounted by this instance.
ORA-15030: diskgroup name "string" is in use by another diskgroup
Cause: A CREATE DISKGROUP command specfied a diskgroup name that was already assigned to another diskgroup.
Action: Select a different name for the diskgroup.
ORA-15031: disk specification "string" matches no disks
Cause: The device specification string to a CREATE DISKGROUP command did not match any devices which could be discovered.
Action: Check the device specification string matches a disk on the system.
ORA-15032: not all alterations performed
Cause: At least one ALTER DISKGROUP action failed.
Action: Check the other messages issued along with this summary error.
ORA-15033: disk "string" belongs to diskgroup "string"
Cause: An attempt was made to ADD to a diskgroup a disk that was already part of another diskgroup, or an attempt was made to DROP / OFFLINE / ONLINE / CHECK a disk that was not part of the specified diskgroup.
Action: For ADD, check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. For the other commands, check the name of the specified disk.
ORA-15034: disk "string" does not require the FORCE option
Cause: An attempt was made to add the disk to the diskgroup using the FORCE option. The disk was not found to be in use at the present time, so the FORCE option was not permitted.
Action: Avoid gratuitous use of the FORCE option.
ORA-15035: no disks belong to diskgroup "string"
Cause: An attempt was made to mount a diskgroup for which no member disks were discovered.
Action: Specify a valid diskgroup name that contains disks.
ORA-15036: disk "string" is truncated
Cause: The size of the disk, as reported by the operating system, was smaller than the size of the disk as recorded in the disk header block on the disk.
Action: Check if the system configuration has changed.
ORA-15037: disk "string" is smaller than mimimum of string MBs
Cause: The size of the disk, as reported by the operating system, was too small to allow the disk to become part of the diskgroup.
Action: Check if the system configuration is correct.
ORA-15038: disk "string" size mismatch with diskgroup [string] [string] [string]
Cause: An attempt was made to mount into a diskgroup a disk whose recorded allocation unit size, metadata block size, or physical sector size was inconsistent with the other diskgroup members.
Action: Check if the system configuration has changed.
ORA-15039: diskgroup not dropped
Cause: An attempt to drop a diskgroup failed.
Action: See the associated messages for details about why the drop was not successful.
ORA-15040: diskgroup is incomplete
Cause: Some of the disks comprising a diskgroup were not present.
Action: Check the hardware to ensure that all disks are functional. Also check that the setting of the ASM_DISKSTRING initialization parameter has not changed.
ORA-15041: diskgroup space exhausted
Cause: The diskgroup ran out of space.
Action: Add more disks to the diskgroup, or delete some existing files.
ORA-15042: ASM disk "string" is missing
Cause: The specified disk, which is a necessary part of a diskgroup, could not be found on the system.
Action: Check the hardware configuration.
ORA-15043: ASM disk "string" is not a diskgroup member
Cause: The specified disk has been removed from the diskgroup, but a disk matching its name was found.
Action: Check the hardware configuration.
ORA-15044: ASM disk "string" is incorrectly named
Cause: Either the specified disk had its contents changed such that it no longer contained an ASM disk name in its header that matches the diskgroup information or its FAILGROUP information may have become inconsistent.
Action: Drop the disk from the diskgroup.
ORA-15045: ASM file name "string" is not in reference form
Cause: The ASM file name was not in a form that can be used to reference an existing file because a file/incarnation number or an alias name was not present or a template name was included.
Action: Correct the specified ASM file name.
ORA-15046: ASM file name "string" is not in single-file creation form
Cause: The ASM file name was not in a form that can be used to create an single file because a file/incarnation number was present.
Action: Correct the specified ASM file name.
ORA-15047: ASM file name "string" is not in multiple-file creation form
Cause: The ASM file name was not in a form that can be used to create multiple files because either a fully-qualified file name or an alias name was present.
Action: Correct the specified ASM file name.
ORA-15048: ASM internal files cannot be deleted
Cause: An attempt was made to delete a metadata file used by ASM to manage the diskgroup.
Action: Check the specified ASM file name.
ORA-15049: diskgroup "string" contains string error(s)
Cause: Errors were discovered by the ALTER DISKGROUP CHECK command.
Action: See the alert log for details of the errors.
ORA-15050: disk "string" contains string error(s)
Cause: Errors were discovered by the ALTER DISKGROUP CHECK DISK command.
Action: See the alert log for details of the errors.
ORA-15051: file "string" contains string error(s)
Cause: Errors were discovered by the ALTER DISKGROUP CHECK FILE command.
Action: See the alert log for details of the errors.
ORA-15052: ASM file name "string" is not in diskgroup "string"
Cause: The ASM file name did not contain a diskgroup name that specified the correct diskgroup as implied by the other arguments to the command.
Action: Correct the specified ASM file name or diskgroup name.
ORA-15053: diskgroup "string" contains existing files
Cause: An attempt was made to drop a diskgroup that still contains existing files.
Action: Specify the INCLUDING CONTENTS option to drop the diskgroup and all of its existing files.
ORA-15054: disk "string" does not exist in diskgroup "string"
Cause: An attempt was made to DROP (or CHECK) a disk that is not part of the specified diskgroup.
Action: Check the name of the specified disk and the specified diskgroup.
ORA-15055: unable to connect to ASM instance
Cause: When accessing a diskgroup for the first time, the database was unable to connect to the required ASM instance.
Action: Check the additional error messages. May need to configure correct ASM sid or make sure the database instance has OS privileges for ASM SYSDBA.
ORA-15056: additional error message
Cause: An operating system error occured.
Action: Correct the operating system error and retry the operation.
ORA-15057: specified size of string MB is larger than actual size of string MB
Cause: A disk size expression exceeded the amount of storage actually availalable, as reported by the operating system.
Action: Specify a valid size.
ORA-15058: disk "string" belongs to an incompatible diskgroup
Cause: An attempt was made to ADD to a diskgroup a disk which was already part of another diskgroup. The other diskgroup was written by a more recent software release.
Action: Check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check.
ORA-15059: invalid device type for ASM disk
Cause: The device type of the discovered disk was not valid for use as an ASM disk.
Action: Check the file path and retry or exclude it from the discovery set. See the accompanying operating system error for additional information.
ORA-15060: template "string" does not exist
Cause: A command specified a template name, either directly or as part of an ASM file name, which did not exist.
Action: Check the template specifier in the command.
ORA-15061: ASM operation not supported [string]
Cause: An ASM operation was attempted that is invalid or not supported by this version of the ASM instance.
Action: This is an internal error code that is used for maintaining compatibility between software versions and should never be visible to the user; contact Oracle support Services.
ORA-15062: ASM disk is globally closed
Cause: The disk to which the I/O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information.
Action: Bring the disk online for I/Os to get through.
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "string"
Cause: ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.
Action: Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.
ORA-15064: communication failure with ASM instance
Cause: There was a failure to communicate with the ASM instance, most likely because the connection went down.
Action: Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally.
ORA-15065: hash collision for diskgroup names "string" and "string"
Cause: There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names.
Action: Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided.
ORA-15066: offlining disk "string" may result in a data loss
Cause: Following I/O failures, the disks holding all copies of a data block were attempted to be taken offline.
Action: Check the accompanying error messages for more information on the reason for the disk I/O failures.
ORA-15067: command or option incompatible with diskgroup redundancy
Cause: An attempt was made to use a feature which is not permitted by the diskgroup"s redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes.
Action: Omit the option from the command.
ORA-15068: maximum number of diskgroups string already mounted
Cause: An attempt was made to mount more diskgroups than the instance is capable of mounting at one time.
Action: Dismount a mounted diskgroup and retry the command.
ORA-15069: ASM file "string" not accessible; timed out waiting for lock
Cause: An attempt was made to access an ASM file, but the file is currently being created, resized, or deleted and therefore cannot be accessed.
Action: No action required, or try again later, after the create or resize has completed.
ORA-15070: maximum number of files string exceeded in diskgroup "string"
Cause: The diskgroup ran out of space.
Action: Delete some existing ASM files or create files in a new diskgroup.
ORA-15071: ASM disk "string" is already being dropped
Cause: An attempt was made to drop a disk from a diskgroup which was already in the process of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly drop a disk from a diskgroup using the FORCE option which was already being forcibly dropped from the diskgroup.
Action: Check the ASM disk name and FORCE option as specified in the command.
ORA-15072: command requires at least string failure groups, discovered only string
Cause: An attempt was made to create either a normal redundancy diskgroup for which fewer than two failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three failure groups were both specified and discovered.
Action: Check the that the command does specify the required number of failure groups, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view will show which disks are discovered by ASM.
ORA-15073: diskgroup string is mounted by another ASM instance
Cause: An attempt was made to drop a diskgroup that is still mounted somewhere in the cluster by another instance.
Action: dismount the diskgroup from all nodes except the one performing the drop diskgroup command.
ORA-15074: diskgroup string requires rebalance completion
Cause: An attempt was made to repeatedly add or drop disks from a diskgroup. ASM could not perform the operation given the current state of the diskgroup.
Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow the rebalance to run to completion. Alternatively, invoke the ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to run to completion. After the rebalance has completed, retry the operation.
ORA-15075: disk(s) are not visible cluster-wide
Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration.
Action: Determine which disks are causing the problem from the GV$OSM_DISK fixed view. Check operating system permissions for the device and the storage sub-system configuration on each node in a RAC cluster that cannot identify the disk.
ORA-15076: Emulating I/O errors on the OSM disk
Cause: The disk to which the I/O request was issued is in an error emulation mode.
Action: Bring the disk online for I/Os to get through.
ORA-15077: could not locate ASM instance serving a required diskgroup
Cause: The instance failed to perform the specified operation because it could not locate a required ASM instance.
Action: Start an ASM instance and mount the required diskgroup.
ORA-15078: ASM diskgroup was forcibly dismounted
Cause: The diskgroup to which the I/O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be accessed.
Action: Mount the diskgroup to allow access again.
ORA-15079: ASM file is closed
Cause: The file to which the I/O request was issued was closed. This could have been a consequence of the diskgroup being dismounted.
Action: Make sure the diskgroup is mounted and the file is open.
ORA-15080: synchronous I/O operation to a disk failed
Cause: A synchronous I/O operation invoked on a disk has failed.
Action: Make sure that all the disks are operational.
ORA-15081: failed to submit an I/O operation to a disk
Cause: A submission of an I/O operation to a disk has failed.
Action: Make sure that all the disks are operational.
ORA-15082: ASM failed to communicate with database instance
Cause: There was a failure when ASM tried to communicate with a database instance (most likely because the connection went down).
Action: Check the accompanying error messages for more information on the reason for the failure. Note that the ASM instances may return this error when a database instance is terminated abnormally.
ORA-15083: failed to communicate with ASMB background process
Cause: A database instance failed to communicate with its ASMB background process when attempting to access an ASM file.
Action: Check the alert log for more information on the reason for the failure.
ORA-15090: handle string is not a valid descriptor
Cause: The file handle was not valid in this session.
Action: Submit a handle obtained from a successful call to DBMS_DISKGROUP.OPEN().
ORA-15091: operation incompatible with open handle in this session
Cause: The current session contained an open handle from the DBMS_DISKGROUP PL/SQL package which precluded performing the command.
Action: Close the hanlde with DBMS_DISKGROUP.CLOSE() before executing the command, or execute the command in a different session.
ORA-15092: I/O request size string is not a multiple of logical block size string
Cause: The length of the request was not a multiple of logical block size.
Action: Correct the error and retry the operation.
ORA-15093: buffer only contains string bytes, I/O requested is string bytes
Cause: The buffer supplied for write was too small to satisfy the request.
Action: Correct the error and retry the operation.
ORA-15094: attempted to write to file opened in read only mode
Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have write privileges.
Action: Obtain a file handle in read-write mode and retry the write operation.
ORA-15095: reached maximum ASM file size (string GB)
Cause: An ASM file creation or file resize operation exceeded the maximum file size permitted by ASM.
Action: Use smaller files.
ORA-15096: lost disk write detected
Cause: A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active.
Action: The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups.
ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance
Cause: A SHUTDOWN command was issued to an ASM instance that had one or more connected RDBMS instances.
Action: Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance.
ORA-15100: invalid or missing diskgroup name
Cause: The command did not specify a valid diskgroup name.
Action: Specify a valid diskgroup name.
ORA-15101: no action specified
Cause: The ALTER DISKGROUP command did not specify any alterations.
Action: Specify at least one operation clause.
ORA-15102: invalid POWER expression
Cause: The syntax of the POWER expression was invalid.
Action: Specify a valid POWER expression.
ORA-15103: conflicting or duplicate REPAIR options
Cause: The command specified conflicting or duplicate REPAIR keywords.
Action: Specify only one REPAIR action.
ORA-15104: conflicting CONTENTS options
Cause: The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options.
Action: Specify only one option.
ORA-15105: missing or invalid FAILGROUP name
Cause: The command did not specify a valid failure group name.
Action: Specify a valid failure group name.
ORA-15106: missing or invalid operating system disk locator string
Cause: The command did not specify a valid operating system path for the device as a string.
Action: Specify a valid operating system path for the device.
ORA-15107: missing or invalid ASM disk name
Cause: The command did not specify a valid ASM disk name identifier.
Action: Specify a valid ASM disk name identifier.
ORA-15108: missing or invalid template name
Cause: The command did not specify a valid template name identifier.
Action: Specify a valid template name identifier.
ORA-15109: conflicting protection attributes specified
Cause: The command contained an invalid combination of the UNPROTECTED, MIRROR, or PARITY keywords.
Action: Specify only one keyword.
ORA-15110: no diskgroups mounted
Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount any diskgroups.
Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the error.
ORA-15111: conflicting or duplicate STRIPE options
Cause: The command contained both a FINE and COARSE keyword, or contained the FINE keyword more than once, or contained the COARSE keyword more than once.
Action: Specify only one keyword.
ORA-15112: No diskgroups are currently mounted.
Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups upon which to operate. Either instance shutdown or an ALTER DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks.
Action: Mount the diskgroups on which you wish to operate or ignore the error.
ORA-15113: alias name "string" refers to a directory
Cause: The name specified referred to a directory in the alias directory and not a valid alias entry.
Action: Check the alias name and retry.
ORA-15114: missing or invalid ASM file name
Cause: The command did not specify a valid ASM file name identifier.
Action: Specify a valid ASM file name identifier.
ORA-15115: missing or invalid ASM disk size specifier
Cause: The command did not specify a valid ASM disk size.
Action: Specify a valid ASM disk size.
ORA-15116: invalid combination of ALTER DISKGROUP options
Cause: The ALTER DISKGROUP options may not be combined in this manner.
Action: Issue separate ALTER DISKGROUP commands to accomplish the desired action.
ORA-15117: command only operates on one diskgroup
Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command specified a list of diskgroups or the keyword ALL in a context where only a single diskgroup was permitted.
Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP commands to accomplish the desired action.
ORA-15120: ASM file name "string" does not begin with the ASM prefix character
Cause: A file name was specified to ASM which did not begin with the ASM prefix character (currently "+"). ASM uses the prefix to determine that a file specification is in fact an ASM file.
Action: Correct the file name specification.
ORA-15121: ASM file name "string" contains an invalid diskgroup name
Cause: A file name was specified that did not contain a valid diskgroup name. The diskgroup name follows immediately after the ASM prefix character. It must start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters "$" and "_".
Action: Correct the file name specification.
ORA-15122: ASM file name "string" contains an invalid file number
Cause: A numeric file name was specified which did not contain a valid ASM file number. The ASM file number follows immediately after the diskgroup name. It must be preceeded by a "." character, and contain only numeric characters.
Action: Correct the file name specification.
ORA-15123: ASM file name "string" contains an invalid incarnation number
Cause: A numeric file name was specified which did not contain a valid ASM incarnation number. The ASM incarnation number follows immediately after the ASM file number. It must be preceeded by a "." character, and contain only numeric characters.
Action: Correct the file name specification.
ORA-15124: ASM file name "string" contains an invalid alias name
Cause: A file name was specified which did not contain a valid ASM alias name. The ASM alias name, if present, follows immediately after the diskgroup name, in place of the ASM file number. It must be preceeded by a slash, start with an alphabetic character, and consist of up to 48 characters which are alphabetic, numeric, or the characters "$", "_", "-", or "#". A space can separate two parts of an alias name.
Action: Correct the file name specification.
ORA-15125: ASM file name "string" contains an invalid template name
Cause: A file name was specified to ASM which did not contain a valid template name. The template name, if present, follows immediately after the ASM incarnation number or the ASM alias name, if such is used in place of the ASM file number. It must be enclosed in parenthesis, start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters "$" and "_".
Action: Correct the file name specification.
ORA-15126: component within ASM file name "string" exceeds maximum length
Cause: The maximum identifier length of 30 characters was exceeded for the diskgroup name, template name, or alias name field within the ASM file name.
Action: Correct the file name specification.
ORA-15127: ASM file name "string" cannot use templates
Cause: A fully qualified ASM file name was specified. Such a specification does not permit the inclusion of a template name in the ASM file name.
Action: Correct the file name specification.
ORA-15128: ASM file name "string" exceeds maximum length string
Cause: The maximum ASM file name length of 256 characters was exceeded for the combination of diskgroup name, file number, template name, alias name plus punctuation within the ASM file name.
Action: Correct the file name specification.
ORA-15129: entry "string" does not refer to a valid directory
Cause: The entry indicated did not refer to a directory. Attempt was made to access the contents of this directory.
Action: Correct the error and try again.
ORA-15130: diskgroup "string" is being dismounted
Cause: The diskgroup is being dismounted by request or because an I/O error was encountered that could not be handled by taking the disks offline. A disk cannot be offlined whenever doing so could result in all copies of a redundant extent being unavailable.
Action: Repair the hardware problem and re-mount the diskgroup. Refer to the alert log to determine which disks have failed.
ORA-15131: block string of file string in diskgroup string could not be read
Cause: A block could not be read because the disk containing the block is either offline or an I/O error occured while reading the block. If this is mirrored file, then all disks that contain a copy of the block are either offline or received errors.
Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.
ORA-15132: block string of file string in diskgroup string could not be written
Cause: A block could not be written because the disk containing the block is either offline or an I/O error occured while writing the block. If this is mirrored file, then insufficient disks which contain a copy of the block are either offline or received errors.
Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.
ORA-15133: instance recovery required for diskgroup string
Cause: An instance in the cluster crashed making instance recovery necessary.
Action: None. This error should not normally be seen by an ASM client. ASM will trap this error and retry the operation after doing instance recovery automatically.
ORA-15150: instance lock mode "string" conflicts with other ASM instance(s)
Cause: Some other ASM instance used the lock name space in a conflicting mode.
Action: Shut down the other instance or start up in compatible mode. Alternatively, set the DB_UNIQUE_NAME initialization parameter to avoid the conflict.
ORA-15151: missing or invalid version number for rolling upgrade or downgrade
Cause: The command did not sepcify a valid version number.
Action: Correct the version number in the command. It should be of the form v#.#.#.#.# or other forms with fewer numbers delimited by a period. The version number must be different from the current software version of the instance.
ORA-15152: cluster in rolling upgrade
Cause: The cluster was already in the middle of rolling upgrade.
Action: Rolling upgrade needs to be stopped before attempting to start again.
ORA-15153: cluster not in rolling upgrade
Cause: The cluster was not in rolling upgrade.
Action: Start the rolling upgrade using the ALTER SYSTEM START ROLLING command.
ORA-15154: cluster rolling upgrade incomplete
Cause: The cluster was still performing rolling upgrade.
Action: Ensure that all the instances in the cluster are upgraded before retrying the command.
ORA-15155: version incompatible with the cluster
Cause: The current software version of the instance was incompatible with the other members of the cluster.
Action: Make sure that all the members of the cluster are at the same version. If you are attempting to perform rolling upgrade, execute ALTER SYSTEM START ROLLING command. Ensure that the version being upgraded to is compatible with the existing version of the cluster.
ORA-15156: cluster in rolling upgrade from version [string] to [string]
Cause: The current software version of the instance was incompatible with the rolling upgrade operation of the cluster.
Action: The version number of new member instance must be one of the two versions involved in the rolling upgrade.
ORA-15157: rolling upgrade or downgrade is not allowed
Cause: The cluster was not capable of handling ASM rolling upgrade or downgrade.
Action: The Oracle Cluster Services is using vendor clusterware. Oracle cannot perform rolling upgrade or downgrade using vendor cluster ware. Restart ASM instances using Oracle cluster ware and retry the operation.
ORA-15158: rolling upgrade prevented by string
Cause: One or more instances were blocking the rolling upgrade.
Action: Terminate or wait until the reported operation is complete before attempting the rolling upgrade to the cluster.
ORA-15162: cluster in rolling downgrade
Cause: The cluster was already in the middle of rolling downgrade.
Action: Rolling downgrade needs to be stopped before attempting to start again.
ORA-15163: cluster not in rolling downgrade
Cause: The cluster was not in rolling downgrade.
Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING command.
ORA-15164: cluster rolling downgrade incomplete
Cause: The cluster was still performing rolling downgrade.
Action: Ensure that all the instances in the cluster are downgraded before retrying the command.
ORA-15166: cluster in rolling downgrade from version [string] to [string]
Cause: The current software version of the instance was incompatible with the rolling downgrade operation of the cluster.
Action: The version number of new member instance must be one of the two versions involved in the rolling downgrade.
ORA-15168: rolling downgrade prevented by string
Cause: One or more instances were blocking the rolling downgrade.
Action: Terminate or wait until the reported operation is complete before attempting the rolling downgrade to the cluster.
ORA-15169: destination "string" is a subdirectory of "string"
Cause: Attempt to rename directory failed because the new directory name was a subdirectory of the original directory.
Action: Correct the path of the destination and try again.
ORA-15170: cannot add entry "string" in directory "string"
Cause: Other errors prevented directory/alias creation.
Action: Correct the errors and try again.
ORA-15171: invalid syntax in the alias path after "string"
Cause: An invalid alias/directory name syntax was specified.
Action: Correct the alias path and try again.
ORA-15173: entry "string" does not exist in directory "string"
Cause: The specified alias did not exist in the given directory.
Action: Correct the alias path and try again.
ORA-15175: cannot create alias for diskgroup metadata file "string"
Cause: An attempt was made to create an alias for a diskgroup metadata file.
Action: Correct the alias path and try again.
ORA-15176: file "string" already has an alias associated with it
Cause: An attempt was made to create an alias for a file that already had an existing alias.
Action: Correct the file name and try again or drop existing alias.
ORA-15177: cannot operate on system aliases
Cause: An attempt was made to modify a system alias.
Action: Correct the alias name and try again.
ORA-15178: directory "string" is not empty; cannot drop this directory
Cause: An attempt was made to drop a directory that contained valid entries.
Action: Correct the directory path or specify the FORCE option to drop a directory that is not empty.
ORA-15179: missing or invalid alias name
Cause: The command did not specify a valid alias identifier.
Action: Specify a valid alias identifier.
ORA-15180: Could not open dynamic library string, error [string]
Cause: The library was not accessible
Action: Correct the permissions of the library and try again.
ORA-15181: Symbol [string] not found in library string, error [string]
Cause: An error was encountered while loading the specified ASMLIB symbol.
Action: Correct the error reported and try again.
ORA-15182: ASMLIB [string] version mismatch, ORACLE version [string]
Cause: The ASMLIB version reported is not supported by the ORACLE binary.
Action: Install the correct library and try again.
ORA-15183: ASMLIB initialization error [string]
Cause: Unable to initialize the ASMLIB in ORACLE.
Action: Contact ASMLIB library vendor support with the error details.
ORA-15184: ASMLIB error could not be determined [string] [string]
Cause: An error was encountered which cannot be diagnosed further.
Action: Contact ASMLIB libary vendor for support.
ORA-15185: Could not close dynamic library string, error [string]
Cause: Could not close the dynamic library.
Action: Contact ASMLIB libary vendor for support.
ORA-15186: ASMLIB error function = [string], error = [string], mesg = [string]
Cause: An error occured during a call to function listed in the error.
Action: The detailed message associated with the error is listed along with the error. Correct the error and try again or contact ASMLIB library vendor for support.
ORA-15190: Internal ASM testing event number 15190
Cause: Set this event only under the supervision of Oracle development.
Action: The level controls which ASM disks encounter rebalance IO errors.
ORA-15191: Internal ASM testing event number 15191
Cause: Set this event only under the supervision of Oracle development.
Action: The level controls which ASM errors are emulated.
ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string]
Cause: ASM encountered an invalid disk header.
Action: Contact Oracle Support Services.
ORA-15193: Internal ASM tracing event number 15193
Cause: Set this event only under the supervision of Oracle development.
Action: None.
ORA-15194: Internal ASM-DB interaction testing event number 15194
Cause: Set this event only under the supervision of Oracle development.
Action: The level controls which ASM-DB operation is interuppted.
ORA-15195: Internal ASM testing event number 15195
Cause: Set this event only under the supervision of Oracle development.
Action: The level controls which ASM errors are simulated.
ORA-15196: invalid ASM block header [string:string] [string] [string] [string] [string != string]
Cause: ASM encountered an invalid metadata block.
Action: Contact Oracle Support Services.
ORA-15197: suppressing string additional ASM messages
Cause: The ASM command generated so many erorrs that this summary message was reported in place of many individual messages.
Action: If the command contained multiple actions, try separating each action into its own command and executing each command by itself. Otherwise, try not to generate so many errors.
ORA-15198: operation string is not yet available
Cause: An unimplemented operation was attempted.
Action: Consider upgrading to later releases as they become available.
ORA-15199: Internal ASM tracing event number 15199
Cause: Set this event only under the supervision of Oracle development.
Action: Traces execution of ASM. Level indicates verbosity of tracing.
ORA-15200: initialization parameter string (string) is not a power of two
Cause: The value specified for this initialization parameter was not a power of two.
Action: Correct the initialization parameter value and restart the instance.
ORA-15201: disk string contains a valid RDBMS file
Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ... ADD DISK command appeared to contain a file from an existing database. By default, ASM will not allow a diskgroup to be created using this disk, as a safeguard against damaging an existing database.
Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database is reused as part of an ASM diskgroup, specify the FORCE option to the ASM SQL command.
ORA-15202: cannot create additional ASM internal change segment
Cause: The mount of a diskgroup by an additional instance in a RAC cluster required more space for internal use by ASM than was available in the diskgroup.
Action: Delete unused files from the diskgroup or add additional disks to the diskgroup and retry the operation.
ORA-15203: diskgroup string contains disks from an incompatible version of ASM
Cause: Diskgroup was created by an ASM instance with a higher compatibility setting.
Action: Use an ASM instance with the appropriate software version to mount the diskgroup.
ORA-15204: database version string is incompatible with diskgroup string
Cause: The database compatibility of the diskgroup was advanced to a later version.
Action: Upgrade the database instance to appropriate version of ORACLE.
ORA-15205: requested mirror side unavailable
Cause: The requested mirror side of a block is either unallocated or allocated on a disk that has been dropped from the diskgroup.
Action: Resubmit the request or try another mirror side.
ORA-15206: duplicate diskgroup string specified
Cause: A command specified the same diskgroup twice.
Action: Specify each diskgroup only once.
ORA-16000: database open for read-only access
Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.
Action: In order to modify the database, it must first be shut down and re-opened for read-write access.
ORA-16001: database already open for read-only access by another instance
Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.
Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access.
ORA-16002: database already open for read-write access by another instance
Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.
Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access.
ORA-16003: standby database is restricted to read-only access
Cause: To ensure its integrity, a standby database can only be opened for read-only access.
Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY.
ORA-16004: backup database requires recovery
Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.
Action: Perform the necessary recovery and re-open for read-only access.
ORA-16005: database requires recovery
Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.
Action: Perform the necessary recovery and re-open for read-only access.
ORA-16006: audit_trail destination incompatible with database open mode
Cause: The audit_trail initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access.
Action: When the database is opened for read-only access, the audit_trail initialization parameter can only be set to "OS" or "NONE" (FALSE).
ORA-16007: invalid backup control file checkpoint
Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access.
Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.
ORA-16008: indeterminate control file checkpoint
Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access.
Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.
ORA-16009: remote archive log destination must be a STANDBY database
Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.
Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.
ORA-16011: Archivelog Remote File Server process in Error state
Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data.
Action: Correct the problem at the standby database site.
ORA-16012: Archive log standby database identifier mismatch
Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.
Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.
ORA-16013: log string sequence# string does not need archiving
Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.
Action: No action is required.
ORA-16014: log string sequence# string not archived, no available destinations
Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.
Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.
ORA-16015: log string sequence# string not archived, media recovery disabled
Cause: An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.
Action: Disable the standby destination or enable media recovery and retry.
ORA-16016: archived log for thread string sequence# string unavailable
Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file.
Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.
ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.
Action: Set the primary archive destination to a valid non-NULL value.
ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
Action: Eliminate any incompatible parameter definitions.
ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...10) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.
Action: Eliminate any incompatible parameter definitions.
ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.
Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16021: session string destination cannot be the same as session string destination
Cause: An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.
Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.
ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.
Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.
ORA-16023: system string destination cannot be the same as session string destination
Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.
Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.
ORA-16024: parameter string cannot be parsed
Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16025: parameter string contains repeated or conflicting attributes
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained either repeated attributes or attributes that conflicted with each other.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16026: parameter string contains an invalid attribute value
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid value.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16027: parameter string is missing a destination option
Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
Cause: With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.
Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.
Action: Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...10). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination
Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.
Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters.
ORA-16031: parameter string destination string exceeds string character limit
Cause: The value for the specified parameter contained a destination string that is too long.
Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.
ORA-16032: parameter string destination string cannot be translated
Cause: The value for the specified parameter contained a destination string that could not be translated.
Action: Use a valid destination string in the specified parameter.
ORA-16033: parameter string destination cannot be the same as parameter string destination
Cause: An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.
Action: Specify a different value for one of the archive log parameters.
ORA-16034: FROM parameter is incompatible with MANAGED recovery
Cause: Use of the FROM "location" parameter is not allowed when MANAGED recovery has been specified.
Action: Correct the syntax and retry the command.
ORA-16035: missing required keyword string
Cause: The indicated keyword is required but was not specified.
Action: Correct the syntax and retry the command.
ORA-16036: invalid MANAGED recovery CANCEL option
Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or IMMEDIATE following CANCEL.
ORA-16037: user requested cancel of managed recovery operation
Cause: The managed standby database recovery operation has been canceled per user request.
Action: No action is required.
ORA-16038: log string sequence# string cannot be archived
Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.
Action: No action is required.
ORA-16039: RFS request version mismatch
Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.
Action: Verify that compatible versions of Oracle are running on the primary and all standby sites.
ORA-16040: standby destination archive log file is locked
Cause: The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.
Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database.
ORA-16041: Remote File Server fatal error
Cause: The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.
Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action.
ORA-16042: user requested cancel immediate of managed recovery operation
Cause: The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state.
Action: No action is required.
ORA-16043: managed recovery session canceled
Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.
Action: More specific messages will accompany this message.
ORA-16044: destination string attribute cannot be specified at session level
Cause: An archive log destination attribute was attempted to be modified at the session level.
Action: Use the ALTER SYSTEM command to modify the destination attribute.
ORA-16045: circular archive log destination dependency chain
Cause: An archive log destination contains a dependency to another archive log destination that also contains a dependency.
Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.
ORA-16046: Archive log destination failed due to failed dependent destination
Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.
Action: No action required.
ORA-16047: DGID mismatch between destination setting and standby
Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.
Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.
ORA-16050: destination exceeded specified quota size
Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.
Action: No action is required.
ORA-16051: parameter string contains an invalid delay time
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16052: DB_UNIQUE_NAME attribute is required
Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled.
Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.
ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration
Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.
Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.
ORA-16055: FAL request rejected
Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.
Action: to solve the problem.
ORA-16056: backup control file archival requires proper syntax
Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.
Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.
ORA-16057: DGID from server not in Data Guard configuration
Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby.
Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby.
ORA-16058: standby database instance is not mounted
Cause: The RFS process on the standby database received an internal error.
Action: Check the standby alert log and RFS trace files for more information.
ORA-16059: Log file is empty or invalid next available block
Cause: Archiving not allowed of an empty or invalid log file.
Action: No action is required.
ORA-16060: Log file is current
Cause: The current log file cannot be archived using its file name.
Action: No action is required.
ORA-16061: Log file status has changed
Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.
Action: No action is required.
ORA-16062: DGID from standby not in Data Guard configuration
Cause: The Data Guard name from the standby is not in the Data Guard configuration of the server.
Action: In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server.
ORA-16063: remote archival is enabled by another instance
Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.
Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance.
ORA-16064: remote archival is disabled by another instance
Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.
Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance.
ORA-16065: remote archival disabled at standby destination
Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.
Action: If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur.
ORA-16066: remote archival disabled
Cause: An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.
Action: If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur.
ORA-16067: activation identifier mismatch in archive log string
Cause: The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.
Action: Locate the appropriate archive log for the database.
ORA-16068: redo log file activation identifier mismatch
Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.
Action: none
ORA-16069: Archive Log standby database activation identifier mismatch
Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.
Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.
ORA-16070: parameter string contains an invalid REGISTER attribute value
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).
Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.
ORA-16071: dependency archived log file not found string
Cause: The specified archived log file was not found at the indicated standby destination.
Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.
ORA-16072: a minimum of one standby database destination is required
Cause: No standby database archive log destinations were specified.
Action: Specify a standby archive log destination in the initialization parameter file.
ORA-16073: archiving must be enabled
Cause: Online log file archiving is disabled.
Action: Enable log file archiving.
ORA-16074: ARCH processes must be active
Cause: There are no active ARCH processes.
Action: It is required that at least one ARCH process be active.
ORA-16075: standby database destination mismatch
Cause: A standby database destination was specified that is not accessed by another instance.
Action: All database instances must access the same standby databases.
ORA-16076: unknown standby database destination
Cause: A standby database destination was specified that is not accessed by another instance.
Action: All database instances must access the same standby databases.
ORA-16078: media recovery disabled
Cause: The database is not in ARCHIVELOG mode.
Action: Place the database in ARCHIVELOG mode.
ORA-16079: standby archival not enabled
Cause: The standby database does not have archival enabled.
Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.
ORA-16080: invalid LogMiner session string for APPLY
Cause: Logical standby apply engine was started with an invalid LogMiner session identifier.
Action: Fix the problem with the LogMiner session or create a new session.
ORA-16081: insufficient number of processes for APPLY
Cause: Logical standby apply engine was started with fewer processes available than needed.
Action: Increase the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.
ORA-16082: logical standby is not initialized correctly
Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.
Action: Look in the trace file for more information.
ORA-16083: LogMiner session has not been created
Cause: Logical standby apply engine was started without creating a LogMiner session.
Action: Create a LogMiner session and restart the apply engine.
ORA-16084: an apply engine is already running
Cause: A logical standby apply engine was running when another was created.
Action: Shut down the previous apply engine before starting a new one.
ORA-16086: standby database does not contain available standby log files
Cause: The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files".
Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted.
ORA-16087: graceful switchover requires standby or current control file
Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file.
Action: Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.
ORA-16088: archive log has not been completely archived
Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a "current" log file.
Action: Specify a completed archive log.
ORA-16089: archive log has already been registered
Cause: An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.
Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.
ORA-16090: archive log to be replaced not created by managed standby process
Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.
Action: No user action required.
ORA-16091: dependent archive log destination already archived
Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived.
Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.
ORA-16092: dependent archive log destination is not active
Cause: An archive log destination contains a dependency to another archive log destination that is not active"
Action: The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.
ORA-16093: dependent archive log destination is not LGWR-enabled
Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process"
Action: The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process.
ORA-16094: database shutdown during archival operation
Cause: The database was shut down while an online log file archival was active.
Action: None required. The ARCH process is terminated.
ORA-16095: Dependent destination removal for inactivation
Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.
Action: None required.
ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
Cause: None
Action: Specify this command to prepare the primary database for switchover
ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
Cause: None
Action: Specify this command to prepare the standby database for switchover
ORA-16098: inaccessible standby database forced shutdown to protect primary
Cause: No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode.
Action: Specify an alternate standby archive log destination in the initialization parameter file.
ORA-16099: internal error ORA-00600 occurred at standby database
Cause: The RFS process on the standby database received an internal error.
Action: Check the standby alert log and RFS trace files for more information.
ORA-16100: not a valid Logical Standby database
Cause: This database has not been completely configured as a Logical Standby database.
Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.
ORA-16101: a valid start SCN could not be found
Cause: An SCN from which to start could not be found.
Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement.
ORA-16102: remote information is not available on the specified primary
Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.
Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.
ORA-16103: Logical Standby apply must be stopped to allow this operation
Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.
Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.
ORA-16104: invalid Logical Standby option requested
Cause: The option requested is not valid.
Action: Check spelling or refer to the Oracle8i SQL Reference manual for the correct statement syntax, then re-enter the request.
ORA-16105: Logical Standby is already running in background
Cause: A Logical Standby apply operation is already running.
Action: none
ORA-16107: all log data from primary has been processed
Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.
Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
ORA-16108: database is no longer a standby database
Cause: The current database has already been made a primary database.
Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
ORA-16109: failed to apply log data from previous primary
Cause: Log data from previous primary could not be completely applied.
Action: . Then, re-issue command.
ORA-16110: user procedure processing of logical standby apply DDL
Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.
Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.
ORA-16111: log mining and apply setting up
Cause: This logical standby process is setting up to begin processing changes.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16112: log mining and apply stopping
Cause: This logical standby process is cleaning up and stopping Logical Standby apply.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16113: applying change to table or sequence string
Cause: The process is applying changes to a specific schema object.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16114: applying DDL transaction with commit SCN string
Cause: The process is applying a DDL change that"s committed at the given SCN.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16115: %s\% of LogMiner dictionary loading is done
Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16116: no work available
Cause: The process is idle waiting for additional changes to be made available.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16117: processing
Cause: The process is performing its primary function and is not waiting on any significant event.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16119: building transaction at SCN string
Cause: The transaction being committed at the given SCN is being prepared for apply.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16120: dependencies being computed for transaction at SCN string
Cause: The transaction committed at the given SCN is being analyzed for dependencies.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16121: applying transaction with commit SCN string
Cause: The transaction committed at the given SCN is being applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16122: applying large dml transaction at SCN string
Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16123: transaction string string string is waiting for commit approval
Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16124: transaction string string string is waiting on another transaction
Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16125: large transaction string string string is waiting for more data
Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16126: loading table or sequence string
Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16127: stalled waiting for additional transactions to be applied
Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.
ORA-16128: User initiated stop apply successfully completed
Cause: Logical standby was shutdown in an orderly fashion.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16129: unsupported dml encountered
Cause: DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support.
Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.
ORA-16130: supplemental log information is missing from log stream
Cause: Supplemental logging is not enabled at the primary database.
Action: Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
ORA-16131: An error occurred during a Terminal Recovery of the standby.
Cause: An error occurred during a Terminal Recovery of the standby.
Action: Check the standby alert log additional information.
ORA-16132: An error occurred during activation of the standby.
Cause: An error occurred during activation of the standby database following a Terminal Recovery.
Action: Check the standby alert log additional information.
ORA-16133: Datafile string has incorrect terminal recovery stamp.
Cause: After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.
Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.
ORA-16134: invalid MANAGED recovery FINISH option
Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or NOWAIT following FINISH.
ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode.
Action: Make the modification before the database is opened by any instance.
ORA-16136: Managed Standby Recovery not active
Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.
Action: No action is necessary.
ORA-16137: No terminal recovery is required
Cause: All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required.
Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.
ORA-16138: end of log stream not received from primary
Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.
Action: Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.
ORA-16139: media recovery required
Cause: The database has not been recovered through the end of log stream. Graceful switchover is not possible.
Action: Ensure that the entire log stream has been applied. If appropriate, reissue the graceful switchover command.
ORA-16140: standby online logs have not been recovered
Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.
Action: To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE.
ORA-16143: RFS connections not allowed during or after terminal recovery
Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.
Action: The primary must not attempt to archive to the standby after a terminal recovery.
ORA-16145: archival for thread# string sequence# string in progress
Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived.
Action: Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.
ORA-16146: standby destination control file enqueue unavailable
Cause: The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.
Action: Check for and eliminate the standby destination archive log parameter in question.
ORA-16147: standby database referenced by multiple archive log destinations
Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.
Action: Remove one of the duplicate archive log destinations.
ORA-16148: user requested expiration of managed recovery operation
Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.
Action: No action is required.
ORA-16150: FINISH recovery performed on another, older standby database
Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.
Action: No action is required.
ORA-16151: Managed Standby Recovery not available
Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.
Action: Wait for the managed standby recovery session to end. Then retry the operation.
ORA-16152: standby database is in "no-data-loss" protected mode
Cause: The attempted database operation is not allowed while the standby database is in "no-data-loss" protected mode.
Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.
ORA-16154: suspect attribute: string
Cause: Use of the indicated attribute is illegal in the given context.
Action: Make the appropriate changes and reissue the statement.
ORA-16156: LGWR archive log dependency not allowed if database is standby protected
Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.
Action: Remove the LGWR archive log dependency and use normal LGWR archival instead.
ORA-16157: media recovery not allowed following successful FINISH recovery
Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.
Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
ORA-16159: Cannot change protected standby destination attributes
Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database.
Action: No action is required.
ORA-16160: Cannot change protected standby database configuration
Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary database is opened.
ORA-16161: Cannot mix standby and online redo log file members for group string
Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.
Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.
ORA-16162: Cannot add new standby databases to protected configuration
Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary database is opened.
ORA-16163: LGWR network server host attach error
Cause: The LGWR network server could not attach to remote host
Action: The alert log contains more problem-specific information
ORA-16164: LGWR network server host detach error
Cause: The LGWR network server could not detach from remote host
Action: The alert log contains more problem-specific information
ORA-16165: LGWR failed to hear from network server
Cause: The LGWR lost its connection to the network server
Action: The alert log contains more problem-specific information
ORA-16166: LGWR network server failed to send remote message
Cause: The LGWR network server could not communicate with the remote host
Action: The alert log contains more problem-specific information
ORA-16167: LGWR network server could not switch to non-blocking mode
Cause: The LGWR network server could not switch to non-blocking mode
Action: The alert log contains more problem-specific information
ORA-16168: LGWR network server could not switch to blocking mode
Cause: The LGWR network server could not switch to blocking mode
Action: The alert log contains more problem-specific information
ORA-16169: LGWR network server invalid parameters
Cause: The LGWR network server could not switch to blocking mode
Action: The alert log contains more problem-specific information
ORA-16170: Terminal recovery may have left the database in an inconsistent state
Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.
Action: Continue standby recovery with additional log shipping from primary.
ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string
Cause: See alert log for more details
Action: Copy missing archived logs from primary or another standby. Register the logs and re-issue the RECOVER...FINISH command. If the logs are not available, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files.
ORA-16172: archive logs detected beyond Terminal End-Of-Redo
Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.
Action: none
ORA-16173: incompatible archival network connections active
Cause: One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.
Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.
ORA-16174: user requested thread/sequence termination of managed recovery
Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.
Action: No action is required.
ORA-16175: cannot shut down database when media recovery is active
Cause: An attempt was made to shut down a standby database while media recovery was active.
Action: Cancel media recovery to proceed with the shutdown.
ORA-16176: background dictionary build cannot be running
Cause: The background process dedicated to dictionary build is active.
Action: wait and try it later.
ORA-16177: media recovery is not required
Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required.
Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.
ORA-16178: Cannot specify remote destinations in archivelog manual mode
Cause: The database is operating in ARCHIVELOG MANUAL mode. Remote archivelog destinations are not allowed in this mode.
Action: Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic archivelog mode, or defer the archivelog destinations that specify the SERVICE= attribute.
ORA-16179: incremental changes to "string" not allowed with SPFILE
Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.
Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM/SESSION SET command.
ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small
Cause: The max number of parallel servers available for Logical Standby is less than 5 becase of the limit imposed by the too small value of MAX_PARALLEL_SERVERS.
Action: Adjust the values of the initialization parameters PARALLEL_MAX_SERVERS to be at least 5.
ORA-16181: SGA specified for Logical Standby is too large
Cause: MAX_SGA is larger than the larger of initialization parameters SHARED_POOL_SIZE and SGA_TARGET.
Action: Specify the value of MAX_SGA to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75% or lower.
ORA-16182: Internal error on internal channel during remote archival
Cause: An internal error was encountered on the internal channel between LGWR and Network Server.
Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.
ORA-16184: DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_NAME string
Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.
Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.
ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive
Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive.
Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter.
ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID="*" qualifier
Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID="*" qualifier is required.
Action: Re-enter the command using the SID="*" qualifier.
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes.
Action: Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter.
ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.
Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings.
ORA-16191: Primary log shipping client not logged on standby
Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials.
Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE.
ORA-16192: Primary and standby network integrity mismatch
Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.
Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and/or standby.
ORA-16193: Primary and standby network encryption mismatch
Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.
Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and/or standby.
ORA-16194: Modifying DB_UNIQUE_NAME requires SID="*" qualifier
Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID="*" qualifier is required.
Action: Re-enter the command using the SID="*" qualifier.
ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.
Action: Explicitly define a valid DB_UNIQUE_NAME.
ORA-16196: database has been previously opened and closed
Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.
Action: Shut down the instance.
ORA-16197: Invalid DB_UNIQUE_NAME parameter specification
Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and "_", "$" and "#".
Action: Check the documentation and re-enter the parameter.
ORA-16198: Timeout incurred on internal channel during remote archival
Cause: A timeout was incurred during remote archival.
Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.
ORA-16199: Terminal recovery failed to recover to a consistent point
Cause: See alert log for more details
Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.
ORA-16200: Skip procedure requested to skip statement
Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16201: Skip procedure requested to apply statement
Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16202: Skip procedure requested to replace statement
Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16203: Unable to interpret skip procedure return values
Cause: The skip procedure returned conflicting or invalid values.
Action: Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.
ORA-16204: DDL successfully applied
Cause: A DDL statement has successfully commited on the logical standby database.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16205: DDL skipped due to skip setting
Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16206: database already configured as Logical Standby database
Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.
Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.
ORA-16207: Logical standby dictionary build not permitted.
Cause: A dictionary build is currently in progress. Only one build can be active at a time.
Action: Wait for the active build to complete before invoking a new build.
ORA-16208: Logical standby dictionary build failed to start.
Cause: Failure to start the logical standby dictionary build process (LSP1)"
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-16209: Logical standby dictionary build failed to complete.
Cause: The logical standby dictionary build process terminated abnormally."
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-16210: Logical standby coordinator process terminated with error
Cause: The logical standby coordinator process terminated abnormally."
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
ORA-16211: unsupported record found in the archived redo log
Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.
Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it"s unimportant.

2. ALTER DATABASE START LOGICAL STANDBY APPLY;

3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record.

4. Provide the log file to Oracle Support Services.

ORA-16212: number processes specified for APPLY is too great
Cause: Logical standby apply engine was started with more processes requested than are available.
Action: Adjust the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.
ORA-16213: ddl encountered, stopping apply engine
Cause: stop_on_ddl callout specified and DDL was encountered.
Action: Either disable stop_on_ddl callout or remove DDL.
ORA-16214: apply stalled for apply delay
Cause: A delay has been specified on the primary database for this destination.
Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET("APPLY_DELAY"); to override.
ORA-16215: history metadata inconsistency
Cause: internal error.
Action: This is an internal error. Contact Oracle support.
ORA-16216: Log stream sequence error
Cause: The log stream being processed did not follow the last processed stream.
Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream.
ORA-16217: prepare to switchover has not completed
Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.
Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby.
ORA-16218: This database is already preparing to switch over.
Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt.
Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.
ORA-16219: This database is not preparing to switch over.
Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.
Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.
ORA-16220: no failed transaction found
Cause: No failed transaction was found.
Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.
ORA-16221: history table synchronization error
Cause: internal error.
Action: This is an internal error. Contact Oracle support.
ORA-16222: automatic Logical Standby retry of last action
Cause: A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply.
Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16223: DDL skipped, unsupported in current version
Cause: The given DDL statement was not supported in the current version of Logical Standby and was skipped.
Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16224: Database Guard is enabled
Cause: Operation could not be performed because database guard is enabled
Action: Verify operation is correct and disable database guard
ORA-16225: Missing LogMiner session name for Streams
Cause: An attempt was made to register the log file for Streams without a specified LogMiner session name.
Action: Specify a valid LogMiner session name to which the log file will be registered.
ORA-16226: DDL skipped due to lack of support
Cause: Logical Standby does not support this type of DDL in this version, so the DDL is skipped.
Action: The DBA may apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details.
ORA-16227: DDL skipped due to missing object
Cause: A table or other database object upon which this DDL depends is not defined on the Logical Standby database.
Action: No action is necessary, this infomational statement is provided to record the event for diagnostic purposes.
ORA-16228: Insufficient recovery for logical standby
Cause: Insufficient amount of recovery was run for logical standby instantiation.
Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.
ORA-16229: PDML child string string string for parent string string string cannot be skipped.
Cause: A request was made to skip a parallel DML child transaction id. This is not supported.
Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.
ORA-16230: committing transaction string string string
Cause: Logical Standby apply was committing changes for the given transaction.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16231: DDL barrier
Cause: Logical Standby was holding back changes until dependent changes were applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16232: adding Logical Standby skip entry for table string.string
Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.
Action: To have Logical Standby maintain the table, import that table directly from the primary.
ORA-16233: The table string.string is unsupported now
Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.
Action: None.
ORA-16234: restarting to reset Logical Standby apply
Cause: Logical Standby encountered a work load that required a restart to properly reschedule.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16235: DDL skipped because import has occurred
Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16236: Logical Standby metadata operation in progress
Cause: The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished.
Action: Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation.
ORA-16237: SGA specified for Logical Standby is too small
Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.
Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes.
ORA-16238: attempt to use version 9 log
Cause: Version 9 log files are not supported.
Action: Use log files of a supported version.
ORA-16239: IMMEDIATE option not available without standby redo logs
Cause: The IMMEDIATE option cannot be used without standby redo logs.
Action: Do not specify the IMMEDIATE option unless standby redo logs are being used."
ORA-16240: Waiting for logfile (thread# string, sequence# string)
Cause: Reader process is idle waiting for additional logfile to be available.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16241: Waiting for gap logfile (thread# string, sequence# string)
Cause: Reader process is idle waiting for the logfile to fill the log sequence gap.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16242: Processing logfile (thread# string, sequence# string)
Cause: Reader process is processing the logfile.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16243: paging out string bytes of memory to disk
Cause: Builder process is paging out momery to free up space in lcr cache.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16244: taking checkpoint and paging out string bytes to disk
Cause: Builder process is taking a checkpoint to advance restart_scn
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16245: paging in transaction string, string, string
Cause: Builder process is paging in transactions from disk.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16246: User initiated abort apply successfully completed
Cause: SQL Apply was stopped using the abort option.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16247: DDL skipped on internal schema
Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = "INTERNAL SCHEMA".
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16248: RFS connections not permitted during Terminal Apply
Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.
Action: Permit any outstanding Logical Standby operations to complete.
ORA-16249: Terminal apply failed to complete during failover
Cause: The logical standby coordinator process terminated abnormally."
Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover.
ORA-16250: Failed to acquire starting scn of new log stream
Cause: The starting SCN for the new log stream could not be determined.
Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.
ORA-16251: LSP1 Background Build not permitted
Cause: The LSP1 background process is not permitted to start because it had previously been attempted.
Action: This is an internal error. Contact Oracle support.
ORA-16252: Rebuild operation not permitted
Cause: The REBUILD operation is not permitted.
Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.
ORA-16253: Logical Standby cannot start due to incomplete terminal apply
Cause: A previous ACTIVATE of the logical standby failed to complete.
Action: Reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command.
ORA-16254: change db_name to string in the client-side parameter file (pfile)
Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile).
Action: The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again.
ORA-16255: Log Auto Delete conflicts with another LogMiner session
Cause: Log Auto Delete cannot be on while another LogMiner session is running on the same database.
Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.
ORA-16256: Failure to complete standby redo logfile archival after failover
Cause: The standby redo logfiles processed during the failover of a logical standby were not archived.
Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.
ORA-16257: Switchover initiated stop apply successfully completed
Cause: SQL Apply was stopped because of a switchover.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16258: marking index unusable due to a constraint violation
Cause: A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.
Action: No action necessary. See alert log for index schema and name.
ORA-16259: Switchover to logical standby requires a log archive destination
Cause: A valid log archive destination was not found to which the local system could archive the EOR logfile. A minimum of one destination is required.
Action: Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation.
ORA-16260: Waiting to replace partial or corrupt logfile (thread# string, sequence# string)
Cause: LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered.
Action: No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file.
ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST
Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.
Action: No action is required.
ORA-16401: archivelog rejected by RFS
Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.
Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.
ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters.
Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error.
ORA-16403: shutdown in progress - remote connection is not permitted
Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.
Action: Wait for the remote instance to be restarted, or contact your DBA.
ORA-16406: Primary and standby database software version mismatch
Cause: The primary database and standby database Oracle software is not compatible.
Action: Install the correct Oracle software and try again.
ORA-16407: Standby database is in the future of the archive log
Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs.
Action: No action is required.
ORA-16408: Incompatible archival Redo Branch lineage
Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs.
Action: No action is required.
ORA-16409: Archive log switchover reference number mismatch
Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.
Action: No action is required.
ORA-16411: ONDEMAND archival requires active managed recovery operation
Cause: The use of the ONDEMAND attribute for a physical standby database destination requires that the managed recovery operation be active prior to establishing the network connection.
Action: Start the managed recovery operation on the standby database.
ORA-16412: ONDEMAND archival requires active SQL apply operation
Cause: The use of the ONDEMAND attribute for a logical standby database destination requires that the SQL apply operation be active prior to establishing the network connection.
Action: Start the SQL apply operation on the standby database.
ORA-16413: Unsupported database type for ONDEMAND archivelog destinations
Cause: The use of the ONDEMAND attribute for a standby database destination is supported for only physical and logical standby database types. Cross-Instance-Archival and repository database types are not valid for the ONDEMAND attribute.
Action: Verify the database corresponding to the archivelog destination is either a physical standby database or a logical standby database.
ORA-16416: Switchover target is not synchronized with the primary
Cause: The switchover target incurred an error or has a gap at the time the switchover operation was attempted.
Action: Allow the switchover target to become synchronized and then re-attempt the switchover.
ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required
Cause: Activation occurred after recovery from standby redo log files.
Action: Take a full database backup.
ORA-16501: the Data Guard broker operation failed
Cause: The Data Guard broker operation failed.
Action: See accompanying messages for details.
ORA-16502: the Data Guard broker operation succeeded with warnings
Cause: The Data Guard broker operation succeeded with warnings.
Action: See accompanying messages for details.
ORA-16503: site ID allocation failure
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16504: the Data Guard configuration already exists
Cause: A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration.
Action: Delete the existing configuration if you want to create a new configuration.
ORA-16505: site ID is invalid
Cause: The request contained an invalid site ID.
Action: Make the request again with a valid site iD.
ORA-16506: out of memory
Cause: Process exceeded private or shared memory limits.
Action: Check for memory leaks, increase system parameters and restart.
ORA-16507: unrecognized request identifier
Cause: The specified request identifier was not recognized by the Data Guard broker.
Action: Reissue the request using a valid request identifier.
ORA-16508: channel handle not initialized
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16509: the request timed out
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16510: messaging error using ksrwait
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16511: messaging error using ksrget
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16512: parameter exceeded maximum size limit
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16513: maximum requests exceeded
Cause: Non-blocking commands were issued but responses were not consumed or the commands did not complete.
Action: Read pending responses or delete outstanding requests and try again.
ORA-16514: the request was not found
Cause: An attempt was made to read a response but a matching request was not found.
Action: Verify request identifier is valid and references a previously issued request.
ORA-16515: no rcv channel
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16516: the current state is invalid for the attempted operation
Cause: The broker may return this error for switchover operations and for database state change operations. If this error is returned for a switchover operation, the broker has determined that either:

- The databases changing roles are offline.

- The primary database is not shipping log files.

- The standby database that will become the primary database is not applying log files. The broker returns this error for database state change operations if the database state specified is invalid.

Action: If this error is returned when attempting a switchover operation, make sure that:

- The databases changing roles are online.

- The primary database is shipping log files.

- The standby database is applying log files. If this error is returned when attempting a database state change operation, make sure you specify a valid state.

ORA-16517: the object handle is invalid
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16518: unable to allocate virtual instance id
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16519: the resource handle is invalid
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16520: unable to allocate resource id
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16521: unable to create generic template id
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16522: generic template not found
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16523: operation requires the client to connect to instance "string"
Cause: The switchover or failover operation requires the client to connect to the apply instance of the target database.
Action: Connect to the indicated instance and reissue the switchover or failover command.
ORA-16524: unsupported operation
Cause: A command or option is not supported in this release.
Action: Contact Oracle Support Services.
ORA-16525: the Data Guard broker is not yet available
Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start.
Action: If the broker has not been started, set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.
ORA-16526: unable to allocate task element
Cause: The Data Guard broker was unable to allocate memory for a request.
Action: Increase the size of your SGA.
ORA-16527: unable to allocate SGA heap
Cause: The Data Guard broker was unable to allocate a heap within the SGA.
Action: Increase SGA memory.
ORA-16528: unable to allocate PGA heap
Cause: No space in PGA to allocate heap
Action: Increase process virtual memory.
ORA-16529: bad sender id
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16530: invalid buffer or length
Cause: A NULL buffer or a length of zero is specified.
Action: Correct command parameters and retry.
ORA-16531: unable to post message
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16532: Data Guard broker configuration does not exist
Cause: A broker operation was requested that requires an already existing broker configuration.
Action: Create a Data Guard broker configuration prior to issuing other requests.
ORA-16533: inconsistent Data Guard broker state
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16534: no more requests accepted
Cause: The Data Guard broker returns this status when:

- A failover operation has been submitted or is currently is in progress.

- A switchover operation has been submitted or is currently is in progress.

- An instance restart is pending for one or more databases.

Action: Wait until the operation is complete and then reissue the request.
ORA-16535: CRS is preventing execution of a broker operation
Cause: A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker"s request on at least some of the instances, so the broker operation was canceled.
Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Then reissue the broker request.
ORA-16536: unknown object type
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16537: child count exceeded
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16538: no match on requested item
Cause: The Data Guard broker did not recognize the specified property or state name.
Action: Verify command parameters and reissue the request.
ORA-16539: task element not found
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16540: invalid argument
Cause: One of the arguments for the specified request was invalid for the request type.
Action: Verify arguments and then reissue the request.
ORA-16541: site is not enabled
Cause: The site specified in the request was not enabled.
Action: Select an enabled site and reissue the request.
ORA-16542: unrecognized operation
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16543: invalid request made to broker
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16544: modifying DG_BROKER_START requires SID="*" qualifier
Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID="*" qualifier was required in the command.
Action: Reenter the command using the SID="*" qualifier.
ORA-16545: unable to get response
Cause: The Data Guard broker was unable to return the result of a previous request.
Action: Contact Oracle Support Services.
ORA-16546: missing or invalid piece
Cause: The piece of the request to return was not specified or was invalid.
Action: Specify the piece of the response starting from 1.
ORA-16547: cannot disable the primary database
Cause: An attempt was made to explicitly disable broker management of the primary database.
Action: Broker management of the primary database cannot be explicitly disabled. Instead you must disable the entire broker configuration if you wish to disable the primary database.
ORA-16548: object not enabled
Cause: An attempt was made to modify or query a disabled Data Guard object, most likely a database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created. The broker also disables management of a database that lags behind in terms of DRC Unique ID sequence value. This value is updated after successful switchover and failover operations.
Action: If broker management of the database is disabled, enable it and reissue the request.
ORA-16549: invalid string
Cause: A request contained an invalid or NULL string value.
Action: Correct command parameters and retry.
ORA-16550: truncated result
Cause: A string property value was truncated due to insufficient buffer size.
Action: Specify a larger receive buffer.
ORA-16551: short string copied
Cause: A string property value that did not fill the receive buffer was placed in the receive buffer.
Action: This is an informational message only. It is not an error.
ORA-16552: an error occurred when generating the CLIENT OPERATION table
Cause: An error occurred while Data Guard broker was generating the CLIENT OPERATION table.
Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Customer Support.
ORA-16553: the Data Guard broker process (DMON) failed to shutdown
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16554: translation not valid
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16555: the Data Guard database is not active
Cause: An operation was attempted on a database that is currently not active (off path).
Action: Verify that the database is active.
ORA-16556: error message is in XML already
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16557: the database is already in use
Cause: An attempt was made to create a duplicate database in the broker configuration.
Action: Check the database to be added and be sure there are no duplicates.
ORA-16558: the database specified for switchover is not a standby database
Cause: An attempt was made to switchover to a database that is not a standby database.
Action: Locate an enabled standby database and select that database as the target of the switchover.
ORA-16559: out of memory at string
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16560: unable to convert document, syntax error at "string"
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16561: cannot remove an active instance
Cause: The instance to be removed is currently running.
Action: Shut down the instance and reissue the REMOVE command.
ORA-16562: intended_state not used here, syntax error at "string"
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16563: unable to add value, syntax error at "string"
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16564: lookup failed, syntax error at string
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16565: duplicate property, syntax error at "string"
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16566: unsupported document type
Cause: The XML document submitted is not supported.
Action: Correct the errors and submit the request again.
ORA-16567: Data Guard broker internal parser error at "string"
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16568: cannot set property string
Cause: The named property could not be modified. The property may not be editable or may not exist.
Action: Retry the operation with a valid property.
ORA-16569: Data Guard configuration is not enabled
Cause: The requested operation required that broker management of the Data Guard configuration must be enabled.
Action: Enable the Data Guard configuration and reissue the request.
ORA-16570: operation requires restart of database "string"
Cause: The Data Guard broker operation required a database to be shutdown and restarted.
Action: If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it.
ORA-16571: Data Guard configuration file creation failure
Cause: The Data Guard broker was unable to create the configuration file on permanent storage.
Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters and retry.
ORA-16572: Data Guard configuration file not found
Cause: The Data Guard broker configuration file was either unavailable or did not exist.
Action: Verify that the configuration file was successfully created. If the dg_broker_config_file[1|2] parameter was changed, ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.
ORA-16573: attempt to change configuration file for an enabled broker configuration
Cause: The Data Guard broker configuration file parameter was currently in use because broker management of the configuration was enabled. The attempt to alter that parameter was rejected.
Action: Disable the configuration and shut down the Data Guard broker before changing this value. Be sure to rename the configuration file at the OS level to match the new value before reenabling broker management of the configuration.
ORA-16574: switchover disallowed when required databases are offline
Cause: Switchover failed because the primary database and/or the designated standby database are offline.
Action: Check the states of the broker configuration, primary database and standby database. Set their states to ONLINE if necessary.
ORA-16575: request terminated at broker discretion
Cause: This status is returned when the broker terminates a user- initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.
Action: There is no action to be taken.
ORA-16576: failed to update Data Guard configuration file
Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.
Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters.
ORA-16577: corruption detected in Data Guard configuration file
Cause: The Data Guard broker detected errors while loading the configuration file.
Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters. Contact Oracle Support Services.
ORA-16578: failed to read Data Guard configuration file
Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.
Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters.
ORA-16579: bad Data Guard NetSlave state detected
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16580: bad Data Guard NetSlave network link
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16581: Data Guard NetSlave failed to send message to DRCX
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16582: could not edit instance specific property
Cause: The request intended to change an instance specific property, but specified a database with two or more instances.
Action: Specify a specific instance instead to change the property value.
ORA-16583: bad Data Guard Connection Process DRCX state
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16584: illegal operation on a standby site
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16585: illegal operation on a primary site
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16586: could not edit database property through instance
Cause: The request intended to change a database property but specified an instance.
Action: Specify the database instead to change the database property.
ORA-16587: ambiguous object specified to Data Guard broker
Cause: The request specified an object that the broker could not uniquely distinguish between other objects in the configuration.
Action: Try to further distinguish the object specified for the operation and reissue the request.
ORA-16588: no more internal buffers
Cause: See trace file.
Action: Contact Oracle Support Services.
ORA-16589: Data Guard Connection process detected a network transfer error
Cause: The Data Guard Connection process (DRCX) detected an error while transferring data from one database to another. This error is returned in the following situations:

- While transmitting the configuration file between databases, DRCX detected an inconsistency in the block count of the file.

- The DRCX process got an error while writing the configuration file.

Action: Contact Oracle Support Services.
ORA-16590: Data Guard configuration does not contain a primary database
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16591: unknown field "string" in document
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16592: missing field "string" in document
Cause: There was an error at the given token.
Action: Correct the errors and submit the request again.
ORA-16593: XML conversion failed
Cause: There was an error in the XML request document
Action: Correct the errors and submit the request again.
ORA-16594: %s process discovered that DMON process does not exist
Cause: The Data Guard broker process (DMON) that was expected to be running on this instance was found to be missing by the Data Guard NetSlave (NSV*) process(es).
Action: Check the Data Guard broker log and DMON process trace file to determine why the DMON process is missing.
ORA-16595: NetSlave process string failed to terminate
Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.
Action: Contact Oracle Support Services.
ORA-16596: object not part of the Data Guard broker configuration
Cause: A request was made on a database object that is not in the Data Guard broker configuration. The request cannot be completed.
Action: Reissue the request on a database object that is in the broker configuration.
ORA-16597: Data Guard broker detects two or more primary databases
Cause: The Data Guard broker detected two or more primary databases in the broker configuration and cannot continue.
Action: Contact Oracle Support Services.
ORA-16598: Data Guard broker detected a mismatch in configuration
Cause: The Data Guard broker detected a significant mismatch in configuration validation between two or more databases in the broker configuration. This can occur when the primary database has a stale broker configuration file.
Action: Contact Oracle Support Services.
ORA-16599: Data Guard broker detected a stale configuration
Cause: The Data Guard broker detected a stale configuration during initialization for this database.
Action: The broker will automatically resolve this situation once the primary database completes its initialization.
ORA-16600: failover operation can only be submitted at target database
Cause: This error is returned when a failover request specified a different database than the database to which the client is currently connected.
Action: Explicitly connect to the database to which you wish to failover and reissue the failover request.
ORA-16601: site contains required resources that are disabled
Cause: The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled.
Action: Enable all required resources and reissue the request.
ORA-16602: object must be disabled to perform this operation
Cause: An attempt was made to edit a database object that can only be done while broker management of that database is disabled.
Action: Disable broker management of the database and reissue the request.
ORA-16603: Data Guard broker detected a mismatch in configuration ID
Cause: The Data Guard broker for this database detected a mismatch in configuration Unique ID. This can occur if the original configuration was recreated while this database was disconnected from the network or the same database was added to two different broker configurations.
Action: Make sure the database belongs to only one broker configuration. Remove the Data Guard broker configuration files and restart the broker.
ORA-16604: unable to describe template using package "string"
Cause: The Data Guard broker was unable to execute the OnDescribe function in the named package.
Action: Verify that the named package is loaded on the primary database. Also verify that the OnDescribe function is in the package.
ORA-16605: unable to delete template, template is in use
Cause: The Data Guard broker was unable to delete the template because the template is still being used by one or more resources.
Action: Delete all resources using the template before deleting the template. You cannot delete the database template.
ORA-16606: unable to find property "string"
Cause: The named property does not exist.
Action: Specify a valid property name and reissue the request.
ORA-16607: one or more databases have failed
Cause: The Data Guard broker detected a failure for one or more databases in the Data Guard configuration.
Action: Locate the database(s) with a failure status and correct it.
ORA-16608: one or more databases have warnings
Cause: The Data Guard broker detected a warning status for one or more databases.
Action: Locate the database(s) with a warning status and correct it.
ORA-16611: operation aborted at user request
Cause: The Data Guard broker aborted an operation at the user"s request.
Action: No action required.
ORA-16612: string value too long for attribute "string"
Cause: The string value for the named attribute is too long.
Action: Use a shorter string.
ORA-16613: initialization in progress for database
Cause: The database received a directive to change its initialization state or a change in its configuration before it has completed initialization.
Action: Wait until the database has completed initialization before issuing requests to modify run-time state or configuration.
ORA-16614: object has an ancestor that is disabled
Cause: A request to enable an object that has an ancestor that is disabled was received by the broker. The broker has enabled management of the object to the extent that it can, but cannot fully enable the object until its ancestor is enabled.
Action: Determine the ancestor object that is disabled and enable that ancestor prior to enabling the child object.
ORA-16617: unknown object identifier specified in request
Cause: The Data Guard broker returned this error because the object identifier specified in the request was invalid or unknown. For example, this error is returned if an invalid or unknown database object identifier is specified in a request that requires a database object identifier.
Action: Verify that a valid object identifier was specified in the request and then reissue the request.
ORA-16618: response document of size "string" bytes is too large
Cause: The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard broker log.
Action: View the broker log for the given database directly.
ORA-16619: health check timed out
Cause: This status is returned when the Data Guard broker could not reach a standby database during a routine health check.
Action: This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame.
ORA-16620: one or more databases could not be contacted for a delete operation
Cause: The Data Guard broker could not reach one or more standby databases for either a delete database operation or a delete broker configuration operation.
Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database"s Data Guard broker log for to determine which standby databases could not be reached. Then for each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, dg_broker_start, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database"s dg_broker_config_file[1|2] parameter values and delete them.
ORA-16621: database name for ADD DATABASE must be unique
Cause: An attempt was made to add a database to the broker configuration that already includes a database with the specified name. The database names must be unique.
Action: Verify that you have specified a unique name for the new database you wish to add. This can be done by checking that there is no database with the same name. Also note that the database name must match the DB_UNIQUE_NAME initialization parameter of the database.
ORA-16622: two or more broker database objects resolve to one physical database
Cause: The Data Guard broker determined that there were multiple database objects referring to the same physical database.
Action: Examine the details of all databases in the broker configuration and verify that there are not two or more databases that indicate the same physical database. If you detect this situation, remove and readd the erroneously defined database(s) to resolve the ambiguity.
ORA-16623: stale DRC UID sequence number detected
Cause: The Data Guard broker detected a stale sequence value during its bootstrap or health check operations. The sequence value is changed each time a switchover or failover operation completes successfully. A database that is unavailable to participate in the switchover or failover operation will end up with a stale sequence number. Should the database attempt to rejoin the broker configuration, the broker will determine that the database missed a role change and will disable its management of that database. The broker disables the database since it may no longer be a viable standby database for the new primary database.
Action: Examine the broker configuration for databases that were disabled and which may require re-creation..
ORA-16624: broker protocol version mismatch detected
Cause: The broker detected a network protocol version number mismatch. This can happen if the databases in question are not at the same version of Oracle. The broker will disable management of the databases that do not have the same network protocol version number as the primary database.
Action: Examine the version of Oracle installed for all databases to make sure they are identical. Once the Oracle versions are the same for all databases, reenable the databases that had been disabled.
ORA-16625: cannot reach the database
Cause: The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database.
Action: Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database.
ORA-16626: failed to enable specified object
Cause: The broker failed to enable management of an object (most likely a standby database). You can expect to see this status when attempting to enable broker management of a standby database that:

- cannot locate itself in the broker configuration file.

- fails to distinguish itself from two or more databases in the configuration file.

- determines it was not part of a change of primary database due to failover.

Action: To correct the problem, try one of these actions:

- confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.

- confirm that you have not created two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not indicate the same physical database.

- if you had performed a failover and have re-created your old primary database (or a standby database that had to be re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files that are in use by the new primary database.

ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Cause: This status is returned in the following situations:

- The broker rejects an attempt to change the configuration"s overall protection mode since it could not find any online, enabled standby databases that support the proposed protection mode.

- The broker rejects an attempt to enable the configuration if it determines there are no online, enabled standby databases that support the overall protection mode.

- The broker rejects an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that can support the configuration"s overall protection mode.

- The broker rejects an attempt to set the configuration offline if doing so would violate the configuration"s overall protection mode.

- The broker rejects an attempt to set a standby database offline if doing so would violate the configuration"s overall protection mode.

- The broker rejects a switchover attempt if doing so would violate the configuration"s overall protection mode.

- The broker returns this error during a health check.

Action: - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.

- For enable failures, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.

- For delete and disable failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode.

- For state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE you may have to downgrade the protection mode setting to maximum performance beforehand.

- For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary database and a single standby database, ensure that the LogXptMode configuration property established for the primary database supports the overall protection mode. After the switchover, the old primary database will become the standby database and its LogXptMode configuration property setting must support the overall protection mode.

- For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.

ORA-16628: the broker protection mode is inconsistent with the database setting
Cause: The Data Guard broker protection mode saved in the broker"s configuration file was inconsistent with the actual database setting.
Action: Reset the protection mode through the Data Guard broker.
ORA-16629: database reports a different protection level from the protection mode
Cause: The actual protection level supported by the standby database was different from the protection mode set on the primary database. This was likely caused by redo transport problems.
Action: Check the database alert logs and Data Guard broker logs for more details. Check the redo transport status. Make sure at least one standby redo transport is supporting the protection mode and that the network to the standby database is working.
ORA-16630: that database property was deprecated
Cause: The property that was specified in the user operation was a deprecated property.
Action: Check the broker documentation to identify a replacement property or issue a SQL command to achieve the same result if no such replacement property exists.
ORA-16631: operation requires shutdown of database/instance "string"
Cause: The Data Guard broker operation requires a shutdown of the database or instance.
Action: If the client has not yet done so, please shutdown all Oracle instances for the database.
ORA-16632: instance being added to database profile
Cause: The Data Guard broker determined that an instance has successfully found its database profile within the broker configuration file, but yet lacks an instance-specific profile. The broker automatically creates an instance-specific profile and associates the instance with its database profile.
Action: No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance in broker activity.
ORA-16633: the only instance of the database cannot be removed
Cause: The instance to be removed was the only instance of the corresponding database that is known to the broker.
Action: Remove the corresponding database object from the broker configuration instead of that individual instance object of the database.
ORA-16635: NetSlave connection was broken in the middle of a transmission session
Cause: The Data Guard NetSlave process detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (e.g. the broker configuration file) to the remote database. This error implies the transmission has to be restarted from the beginning.
Action: In most cases, no user action is required. The Data Guard broker always tries to resend the data from the beginning. If the problem persists, the user will eventually see this error reported. This will indicate there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and address the actual problem.
ORA-16636: Fast-Start Failover target standby in error state, cannot stop observer
Cause: A STOP OBSERVER operation could not be completed when Fast-Start Failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.
Action: Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps you identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. You may correct the problem that is indicated by that information and retry the operation. Alternatively, you may forcibly disable Fast-Start Failover while connected to the primary database using the DISABLE FAST_START FAILOVER FORCE command in the DGMGRL CLI. You can then stop the observer regardless of the current state of the target standby database.
ORA-16637: an instance failed to access the Data Guard broker configuration
Cause: When an instance was started, the DMON process on the instance failed to access the Data Guard broker configuration. This can happen if the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters are not set up correctly to point to the broker configuration files shared among all instances.
Action: Set DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 to the correct file specifications that point to the broker configuration files shared among all instances. Bounce the DMON process by setting DG_BROKER_START initialization parameter to FALSE and then to TRUE.
ORA-16638: could not get the instance status
Cause: The broker failed to check whether the given instance was alive or not.
Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.
ORA-16639: specified instance inactive or currently unavailable
Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable.
Action: Ensure that the instance specified in the operation is running and then retry the operation.
ORA-16640: CRS warns that multiple instances may still be running
Cause: A broker operation was underway that required CRS to stop monitoring the instances of this database and to shut down all but one instance. Although instance monitoring has ceased, CRS cannot guarantee that only one instance remains running. The broker operation was canceled.
Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Then reissue the broker request.
ORA-16641: failure to acquire broker configuration metadata lock
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16642: db_unique_name mismatch
Cause: The expected db_unique_name value did not match the actual db_unique_name value for the database that the broker contacted using the connect identifier that was associated with that database.
Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database that the broker expects to find via that connect identifier matches the actual db_unique_name for that database.
ORA-16643: unable to determine location of broker configuration files
Cause: The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Action: Retry the operation and if the error persists, contact Oracle Support Services.
ORA-16644: apply instance not available
Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.
Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.
ORA-16645: unexpected new instance interrupted current operation
Cause: A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically.
Action: Reissue the operation after the new instance has joined the Data Guard configuration.
ORA-16646: Fast-Start Failover is disabled
Cause: The operation was not allowed because Fast-Start Failover is disabled.
Action: Enable Fast-Start Failover and retry the operation.
ORA-16647: could not start more than one observer
Cause: The observer could not start because there was another observer already observing the Data Guard configuration for which Fast-Start Failover may have been enabled.
Action: Stop the running observer. Retry the operation.
ORA-16648: a new observer registered with identifier string
Cause: The observer is registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a Fast-Start Failover.
Action: None
ORA-16649: database will open after Data Guard broker has evaluated Fast-Start Failover status
Cause: The database is being opened while Fast-Start failover is enabled. The message indicates that the Data Guard broker will first determine if conditions are suitable for opening; that is, a Fast-Start failover did not occur while the database was unavailable.
Action: No action is normally required. The Data Guard broker will continue opening the database after determining a Fast-Start failover did not occur. If there is a chance that a Fast-Start Failover did occur, the database will remain in the mounted state and will not open. In this case, check the target standby to see if a role transition took place.
ORA-16650: command incompatible when Fast-Start Failover is enabled
Cause: An attempt was made to issue a command which is not permitted when Fast-Start Failover is enabled. The command was not issued using the Data Guard broker.
Action: The attempted command must be issued using the Data Guard broker.
ORA-16651: requirements not met for enabling Fast-Start Failover
Cause: The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met:

- The Data Guard configuration must be in MaxAvailability protection mode.

- The LogXptMode property for both the primary database and the Fast-Start Failover target standby database must be SYNC.

- The primary database and the Fast-Start Failover target standby database must both have flashback enabled.

- No valid target standby database was specified in the primary database"s FastStartFailoverTarget property prior to the attempt to enable Fast-Start Failover, and more than one standby database exists in the Data Guard configuration.

Action: Retry the attempted command after correcting the issue:

- Set the Data Guard configuration to MaxAvailability protection mode.

- Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target standby database are SYNC.

- Ensure that both the primary database and the Fast-Start Failover target standby database have flashback enabled.

- Set the primary database"s FastStartFailoverTarget property to the db_unique_name value of the desired target standby database add the desired target standby database"s FastStartFailoverTarget property to the db_unique_name value of the primary database.

ORA-16652: Fast-Start Failover target standby database is disabled
Cause: The command to enable or disable Fast-Start Failover could not be completed because Data Guard broker management of the Fast-Start Failover target standby database is currently disabled.
Action: Enable broker management of the target standby database and reissue the command. If you are attempting to disable Fast-Start Failover when this error is reported, you may opt to disable Fast-Start Failover with the FORCE option. See the description for DGMGRL"s DISABLE FAST_START FAILOVER [FORCE] command for more information.
ORA-16653: failed to reinstate database
Cause: The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled.
Action: Additional information about this failure is recorded in the primary database"s and/or the specified database"s Data Guard broker log files. This information will be helpful in determining how to proceed.
ORA-16654: Fast-Start Failover is enabled
Cause: The attempted command was not allowed while Fast-Start Failover (FSFO) was enabled:

- The FastStartFailoverTarget property may not be modified.

- The LogXptMode property for either the primary database or the FSFO target standby database may not be modified.

- Neither the broker configuration or the FSFO target standby database may be disabled using the DGMGRL CLI"s DISABLE command.

- Neither the broker configuration or the FSFO target standby database may be removed using the DGMGRL CLI"s REMOVE command.

- The FAILOVER IMMEDIATE command is not allowed.

Action: Disable Fast-Start Failover, using the FORCE option if required. Then retry the attempted command.
ORA-16655: specified target standby database invalid
Cause: The attempted command was not allowed because Fast-Start Failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database.
Action: Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, you may disable Fast-Start Failover. You may then retry the command while specifying the originally specified target standby database.
ORA-16656: higher DRC UID sequence number detected
Cause: The Data Guard broker detected a higher sequence value during its bootstrap or health check operations. The sequence value is changed each time switchover or failover completes successfully.
Action: Additional information about this failure is recorded in the Data Guard "broker log" files, one for the primary database and one for each standby database in the Data Guard configuration. This information will be helpful in determining how best to proceed from this failure.
ORA-16657: reinstatement of database in progress
Cause: Reinstatement of this database was in progress.
Action: No action is necessary.
ORA-16658: unobserved Fast-Start Failover configuration
Cause: The Fast-Start Failover configuration was currently unobserved so failover was disallowed.
Action: Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable Fast-Start Failover to allow a failover in the absence of the observer process.
ORA-16659: failover operation in progress
Cause: A primary database that restarted contacted a standby database that is being failed over to.
Action: Shutdown the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to Fast-Start Failover, restarting the primary database after failover is complete will allow it to be automatically reinstated as a standby database to the new primary database.
ORA-16660: FSFO operation attempted in absence of a broker configuration
Cause: An attempt was made to enable or disable Fast-Start Failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands.
Action: 1) An attempt to enable or disable (non-FORCE) Fast-Start Failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database"s DMON process from the primary"s DMON process. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) You may use the FORCE option to override Fast-Start Failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that FSFO is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other at a later point in time and if the state of Fast-Start Failover had been altered at the primary database in the meantime.
ORA-16661: the standby database needs to be reinstated
Cause: A switchover or failover operatione has caused this database to require reinstatement.
Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database.
ORA-16700: the standby database has diverged from the primary database
Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option.
Action: Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to.
ORA-16701: generic resource guard request failed
Cause: Request to modify or query the resource failed.
Action: Check the Data Guard broker log for the reason for the failure, and reissue the request.
ORA-16702: generic resource guard warning
Cause: A request to modify or query the resource resulted in a warning.
Action: Check the Data Guard broker log for the reason for the warning, and if necessary reissue the request.
ORA-16703: cannot set property while the database is enabled
Cause: An attempt was made to change a database property while the database was enabled.
Action: Disable broker management of the database first, then update the property and reenable the database.
ORA-16704: cannot modify a read-only property
Cause: An attempt was made to change a read-only property.
Action: The property is controlled internally by the Data Guard broker and cannot be modified.
ORA-16705: internal error in resource guard
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16706: no resource guard is available
Cause: No resource guard is available to service the request.
Action: Contact Oracle Support Services.
ORA-16707: the value of the property string is invalid, valid values are string
Cause: An invalid property value was entered while broker management of the database was disabled.
Action: Reset the value to a correct one.
ORA-16708: the state supplied to resource guard is invalid
Cause: The state name specified is invalid for the database.
Action: Check the state name and reissue the request.
ORA-16709: standby archived log location settings conflict with flash recovery area
Cause: The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database.
Action: If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error.
ORA-16710: the resource guard is out of memory
Cause: The resource guard was unable to allocate memory while trying to service a request.
Action: Disable broker management of the configuration, shut down Oracle, increase SGA size, and restart.
ORA-16711: the resource guard index is out of bounds
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16712: the resource handle is invalid
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16713: the resource guard timed out while servicing the request
Cause: The resource guard timed out while servicing the request.
Action: Verify that the operation is valid for the database and then reissue the request.
ORA-16714: the value of property string is inconsistent with the database setting
Cause: The value of the specified configuration property is inconsistent with database in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property.
Action: Query property InconsistentProperties on the database to determine the inconsistent values. Reset the property to make it consistent with the database setting.
ORA-16715: redo transport-related property string of standby database "string" is inconsistent
Cause: The value of the specified redo transport-related configuration property of the given standby database is inconsistent with the primary database"s redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property.
Action: Query property InconsistentLogXptProps on the primary database to determine the inconsistent values. Reset the property on the standby database to make it consistent with the primary database"s redo transport setting.
ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed
Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed.
Action: Contact Oracle Support Services.
ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.
Action: Contact Oracle Support Services.
ORA-16718: failed to locate database object
Cause: The resource guard was unable to locate the database in the broker configuration.
Action: Add the database to the broker configuration and then reissue the request.
ORA-16719: unable to query V$ARCHIVE_DEST fixed view
Cause: The broker failed to query the V$ARCHIVE_DEST fixed view."
Action: Test and clear the problem using SQL*Plus.
ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available
Cause: All LOG_ARCHIVE_DEST_n initialization parameters are in use.
Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to setup the primary database"s redo transport.
ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters
Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters.
Action: Check the Data Guard broker log and Oracle alert logs for more details.
ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters.
Action: Check the Data Guard broker log and Oracle alert logs for more details.
ORA-16723: setting AlternateLocation property conflicts with the redo transport setting
Cause: The standby database is not using standby redo logs, and the redo transport service to the standby database is set with a nonzero value of ReopenSecs and a zero value of MaxFailure. In this case, the redo transport service will retry the standby destination indefinitely and never switch to the alternate destination.
Action: Any one of the following actions will solve the problem: (1) add standby redo logs to the standby database; (2) set ReopenSecs property to zero; (3) set MaxFailure property to a nonzero value. After executing one of the above actions, reset the AlternateLocation property.
ORA-16724: the intended state for the database has been set to OFFLINE
Cause: The intended state of the database has been set to offline.
Action: If broker management of the database is currently enabled, set the database"s state to online.
ORA-16725: the phase supplied to resource guard is invalid
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16726: the external condition supplied to resource guard is invalid
Cause: Internal error
Action: Contact Oracle Support Services.
ORA-16727: resource guard cannot close database
Cause: The resource guard could not close the database.
Action: Check if there any active sessions connect to the database, terminate them, then reissue the request.
ORA-16728: consistency check for property string found string error
Cause: The consistency check for the specified property failed due to the error shown.
Action: Check the error message and clear the error.
ORA-16729: validation of value for property string found string error
Cause: The property value validitation failed due to the error shown.
Action: Check the error message and clear the error.
ORA-16730: error executing dbms_logstdby.skip_txn procedure
Cause: Logical standby database package may not be installed.
Action: Install logical standby database packages and reissue the request.
ORA-16731: error executing dbms_logstdby.unskip_txn procedure
Cause: Logical standby database package may not be installed.
Action: Install logical standby database packages and reissue the request.
ORA-16732: error executing dbms_logstdby.skip procedure
Cause: Logical standby database package may not be installed.
Action: Install logical standby database packages and reissue the request.
ORA-16733: error executing dbms_logstdby.unskip procedure
Cause: Logical standby database package may not be installed.
Action: Install logical standby database packages and reissue the request.
ORA-16734: error executing dbms_logstdby.skip_error procedure
Cause: Logical standby database package may not be installed.
Action: Install logical standby database packages and reissue the request.
ORA-16735: error executing dbms_logstdby.unskip_error procedure
Cause: Logical standby database package may not be installed.
Action: Install logical standby database packages and reissue the request.
ORA-16736: unable to find the destination entry of standby database "string" in V$ARCHIVE_DEST
Cause: Either the standby destination was manually changed or deleted outside the Data Guard broker"s control, or no entry was available for Data Guard broker.
Action: Clean up the destination setting, remove the unused ones, and reset the redo transport service.
ORA-16737: the redo transport service for standby database "string" has an error
Cause: A communication problem with the standby database caused the redo transport to fail.
Action: Query the LogXptStatus property to see the error message. Check the Data Guard broker log and Oracle alert log for more details.
ORA-16738: redo tranport service for standby database "string" unexpectedly offline
Cause: The redo transport service for the standby database was offline instead of online.
Action: Check the Data Guard broker log for more details. If necessary, start the redo transport service.
ORA-16739: redo transport service for standby database "string" unexpectedly online
Cause: The redo transport service for the standby database was online instead of offline.
Action: Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database.
ORA-16740: redo transport service for standby database "string" incorrectly set to ALTERNATE
Cause: The redo transport service to the standby database is currently set to ALTERNATE when no other destination is set to alternate to this destination.
Action: Reset the database state to turn on redo transport again if necessary.
ORA-16741: the destination parameter of standby database "string" has incorrect syntax
Cause: The destination defined in the server parameter file of the primary database has incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled.
Action: Fix the syntax error in the primary database"s server parameter file or remove the entry from the server parameter file. Also Check the values of the redo transport-related properties for the specified standby database.
ORA-16742: the standby database "string" has exhausted its quota
Cause: The standby database has exhausted its quota for storing archived redo logs.
Action: Remove some archived logs from the standby database or increase its quota.
ORA-16743: the status of redo transport service for standby database "string" is unknown
Cause: The status of redo transport to the specified standby database could not be determined.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list.
Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.
ORA-16745: unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.
Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.
ORA-16746: resource guard encountered errors during database mount
Cause: The resource guard could not mount the database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16747: logical standby database guard could not be turned on
Cause: The resource guard could not turn on the logical standby database guard.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16748: resource guard encountered errors during database open
Cause: The resource guard could not open the database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16749: resource guard encountered errors in switchover to logical primary database
Cause: The resource guard was unable to switch a logical standby database to a primary database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16750: resource guard encountered errors while activating logical primary database
Cause: The resource guard could not activate a primary database from a logical standby database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16751: resource guard encountered errors in switchover to primary database
Cause: The resource guard was unable to switch a standby database to a primary database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16752: resource guard could not mount standby database
Cause: The resource guard could not mount the standby database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16753: resource guard could not open standby database
Cause: The resource guard could not open the standby database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16754: resource guard could not activate standby database
Cause: The resource guard could not activate the standby database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16755: failed to set initialization parameter
Cause: The ALTER SYSTEM SET or ALTER SYSTEM RESET command issued by the Data Guard broker failed.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16756: resource guard could not open standby database read-only
Cause: The resource guard could not open the standby database read-only.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16757: resource guard could not get property
Cause: The resource guard failed to get the specified property.
Action: Check the Data Guard broker log for more details.
ORA-16758: the specified apply instance is not running
Cause: The apply instance specified by the user is not running, so the Data Guard broker cannot move the apply service to that instance.
Action: Start the instance that you wish the apply service to upon and retry the command.
ORA-16759: resource guard unable to start SQL Apply with initial SCN
Cause: The resource guard failed to start SQL Apply with an initial SCN.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16760: resource guard could not start SQL Apply
Cause: The resource guard failed to start SQL Apply.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16761: resource guard could not stop SQL Apply
Cause: The resource guard failed to stop SQL Apply.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16762: invalid database state
Cause: Database was not in the intended state.
Action: Determine the reason for invalid state, and reissue the get status request.
ORA-16763: redo transport service for a standby database is online
Cause: The redo transport service for a standby database was online instead of offline.
Action: Query the StatusReport property of the primary database for more details. If necessary, stop the redo transport service for the database.
ORA-16764: redo transport service to a standby database is offline
Cause: The redo transport service to a standby database was offline instead of online.
Action: Query the StatusReport property of the primary database for more details. If necessary, start the redo transport service.
ORA-16765: Redo Apply is unexpectedly online
Cause: Redo Apply was online when it should be offline.
Action: If necessary, stop Redo Apply.
ORA-16766: Redo Apply unexpectedly offline
Cause: Redo Apply was offline when it should be online.
Action: If necessary, start Redo Apply.
ORA-16767: SQL Apply unexpectedly online
Cause: SQL Apply was online when it should be offline.
Action: If necessary, stop SQL Apply.
ORA-16768: SQL Apply unexpectedly offline
Cause: SQL Apply was offline when it should be online.
Action: If necessary, start SQL Apply.
ORA-16769: the physical standby database is open read-only
Cause: All instances in the physical standby database were put into a read-only state instead of LOG-APPLY-OFF.
Action: Issue the set state command to move the database to LOG-APPLY-OFF state.
ORA-16770: physical standby database not in read-only state
Cause: All instances in the physical standby database were put into a LOG-APPLY-OFF state instead of READ-ONLY.
Action: Issue the set state command to move the database to READ-ONLY state.
ORA-16771: failover to a physical standby database failed
Cause: In the failover operation, the step of converting the physical standby database to the primary database failed.
Action: Check the alert log and the Data Guard broker log for more details about the error.
ORA-16772: error switching over between primary and standby databases
Cause: There was an error during switchover of primary and standby databases.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16773: error starting Redo Apply
Cause: There was an error starting Redo Apply on a physical standby database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16774: error stopping Redo Apply
Cause: There was an error stopping Redo Apply on a physical standby database.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16775: target standby database in broker operation has potential data loss
Cause: The target standby database in the broker operation did not have all the redo logs from the primary database. The switchover or protection mode upgrade to maximum protection could not be performed.
Action: Query the SendQEntries monitorable property on the primary database to see which redo logs are missing. Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Perform log switches on the primary database in order to activate the redo log gap fetching mechanism. Once all redo logs are available on the target standby database, reissue the broker command.
ORA-16776: health check of the redo transport service failed
Cause: Due to some internal failure, the database resource guard could not complete the health check of the redo transport service.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST
Cause: Either a destination was manually deleted or no entry was available for Data Guard.
Action: Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset.
ORA-16778: redo transport error for one or more databases
Cause: The redo transport service was unable to send redo data to one or more standby databases.
Action: Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors.
ORA-16779: the destination parameter of a database is set incorrectly
Cause: The destination was defined in the LOG_ARCHIVE_DEST_n server parameter file with incorrect syntax. The Data Guard broker failed to update the destination when the redo transport was turned on.
Action: Check the Data Guard broker log to see which database has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties are correct.
ORA-16780: a database has exhausted its archived redo log storage quota
Cause: A database has exhausted its quota for storing archived redo logs.
Action: Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota.
ORA-16781: the status of redo transport service for a database is unknown
Cause: The redo transport service status to a standby database could not be determined.
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16782: instance not open for read and write access
Cause: An instance was left in a mounted mode and was not open for read and write access.
Action: Query the StatusReport property for more details. Open the instance manually or by reenabling the database through the Data Guard broker.
ORA-16783: instance string not open for read and write access
Cause: The instance was left in a mounted mode and was not open for read and write access.
Action: Open the instance manually or by reenabling the database through the Data Guard broker.
ORA-16784: the database name in Dependency property is incorrect
Cause: The database name, which should be the value of the DB_UNIQUE_NAME initialization parameter, specified in property Dependency is incorrect.
Action: Reset the Dependency property to the correct name of the database.
ORA-16785: the database is not in ARCHIVELOG mode
Cause: The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to be a primary database.
Action: Reset the database to ARCHIVELOG mode by issuing ALTER DATABASE ARCHIVELOG command.
ORA-16786: resource guard cannot access Data Guard broker metadata
Cause: The Data Guard broker configuration files did not exist or for some other reason the resource guard could not access the Data Guard broker configuration metadata.
Action: Check the Data Guard broker log for more details.
ORA-16788: unable to set one or more database configuration property values
Cause: This situation occurs when the database resource guard attempted to set database configuration property values into the database by issuing "ALTER SYSTEM" or "ALTER DATABASE" commands. Typical causes of this error are: a) The values of redo transport-related properties have syntax errors; b) The Value of LogArchiveTrace is out of range; c) Database initialization parameter STANDBY_FILE_MANAGEMENT cannot be set to AUTO because the database compatability is not set to 9.0.0.0.0 or higher.
Action: Check the Data Guard broker log to see which property has the problem and reset the property correctly.
ORA-16789: missing standby redo logs
Cause: Standby redo logs are missing and are needed for SYNC and ASYNC log transport modes.
Action: Check the Data Guard documentation to see how to create standby redo logs.
ORA-16790: the value of the configurable property is invalid
Cause: User entered an invalid property value.
Action: Reset the property to a correct value.
ORA-16791: unable to check the existence of the standby redo logs
Cause: The database may not be mounted, or the query of V$STANDBY_LOG failed.
Action: Bring the database to the mounted state and then query V$STANDBY_LOG to see if the problem has been corrected. Then retry the operation.
ORA-16792: configuration property value is inconsistent with database setting
Cause: The values of one or more configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker.
Action: Query property the InconsistentProperties on the database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters.
ORA-16793: logical standby database guard is unexpectedly off
Cause: The logical standby database guard was unexpectedly turned off.
Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error/warning is cleared.
ORA-16794: database guard is on for primary database
Cause: The database guard was turned on for the primary database.
Action: Issue the ALTER DATABASE GUARD NONE to turn off the guard and verify that Data Guard health check error/warning is cleared.
ORA-16795: database resource guard detects that database re-creation is required
Cause: In the act of failover or switchover, the database resource guard may have detected that re-creation of the database is necessary. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database. Until this error status is resolved for this database, information about this database and the broker configuration to which it belongs is unavailable to a broker client that is connected to this database. Therefore, all commands directed by that client to this database cannot be completed.
Action: Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. At this point you may connect to that standby database and resume issuing client commands. Alternatively, many client commands that cannot be completed at the standby database when in this error state can be completed successfully when issued to the primary database. In this case, simply reconnect to the primary database and retry the command.
ORA-16796: one or more properties could not be imported from the database
Cause: The broker was unable to import property values for the database being added to the broker configuration. This error indicates:

- the net-service-name specified in DGMGRL"s CREATE CONFIGURATION or ADD DATABASE command is not one that provides access to the database being added, or

- there are no instances running for the database being added.

Action: Remove the database from the configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make sure that the database to be added has at least one instance running and that the net-service-name provides access to the running instance. Then reissue the CREATE CONFIGURATION or ADD DATABASE command.
ORA-16797: database is not using a server parameter file
Cause: The database is not using a server parameter file or the resource guard was unable to access the server parameter file.
Action: Issue CREATE SPFILE=".." FROM PFILE="..."" command to create a server parameter file and then restart the database to use it.
ORA-16798: unable to complete terminal recovery on the standby database
Cause: Terminal recovery on the standby database failed during the failover operation.
Action: Check Data Guard broker log and alert logs to see more details on the reason of the failure.
ORA-16799: Redo Apply is offline
Cause: Either the Data Guard broker metadata indicates that Redo Apply is turned off, or the recovery process, MRP0, is not running. In either of the cases, Redo Apply-related properties cannot be set.
Action: Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property.
ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE
Cause: The redo transport service for a standby database is currently set to ALTERNATE when no other destination is set to alternate to this destination.
Action: Reset the database state to turn on redo transport again if necessary.
ORA-16801: redo transport-related property is inconsistent with database setting
Cause: The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker.
Action: Query property the InconsistentLogXptProps on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters.
ORA-16802: downgrading redo transport mode from SYNC disallowed
Cause: An attempt was made to downgrade the redo transport mode of a standby database from SYNC to ASYNC or ARCH when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This is not allowed, even if there are other standby databases with log transport modes set to SYNC to support the data protection mode.
Action: You can do one of the following if you need to downgrade the redo transport mode of the standby database: (1) Shut down all instances of the primary database and restart one instance with initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode, shutdown the instance, and restart all instances with CLUSTER_DATABASE set to TRUE. (2) Downgrade the protection mode to Maximum Performance mode first. Then downgrade the redo transport mode, then upgrade the protection mode again (which involves a shutdown and restart of the primary database). Note that the above only works when there exists at least one more standby database in the configuration that has the log transport mode set to SYNC.
ORA-16803: unable to query a database table or fixed view
Cause: Failed to query a database table or fixed view. The database may not be open or mounted.
Action: Check Data Guard broker log for more details.
ORA-16804: one or more configuration properties in metadata have invalid values
Cause: Data Guard broker health check detected that one or more configuration properties in the broker"s configuration metadata have invalid values. The property values have been changed while broker management of the database is disabled.
Action: Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker.
ORA-16805: change of LogXptMode property violates overall protection mode
Cause: The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database. The rejection was necessary to avoid violating the overall protection mode for the configuration.
Action: If the LogXptMode configuration property must be changed for the specified standby database, first downgrade the overall protection mode for the broker configuration. After that operation has completed, you will be able to change the LogXptMode configuration property for the standby database.
ORA-16806: supplemental logging is not turned on
Cause: Supplemental logging was not turned on while there is a logical standby database in the configuration. This could happen either on the primary or on the logical standby database that is being switched over to be the primary database.
Action: Check Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.
ORA-16807: unable to change database protection mode
Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed.
Action: Check the Oracle alert log and Data Guard broker log for more information.
ORA-16808: unable to resolve the full path name
Cause: An attempt to resolve the full path name from a string failed.
Action: Check the Data Guard broker log for the full error stack. This likely the result of an operating system error.
ORA-16809: multiple warnings detected for the database
Cause: The broker has detected multiple warnings for the database.
Action: Check the StatusReport monitorable property of the database specified.
ORA-16810: multiple errors or warnings detected for the database
Cause: The broker detected multiple errors or warnings for the database.
Action: Check the StatusReport monitorable property of the database specified.
ORA-16811: apply instance not recorded by the Data Guard broker
Cause: The broker has not registered an apply instance for a standby database.
Action: Reenable the standby database to clear the error.
ORA-16812: log apply service not running on apply instance recorded by the broker
Cause: Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon.
Action: Reenable the standby database to clear the error.
ORA-16813: log apply service not running on apply instance string recorded by the broker
Cause: Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon.
Action: Reenable the standby database to clear the error.
ORA-16814: incorrect redo transport setting for AlternateLocation for standby database
Cause: The Data Guard broker detected that an incorrect redo transport setting for a standby database"s AlternateLocation property. The incorrect setting could be one of the following: one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.
Action: Reenable the primary database to clear the error.
ORA-16815: incorrect redo transport setting for AlternateLocation for standby database "string"
Cause: The Data Guard broker detected that the redo transport setting for the standby database regarding its AlternateLocation property value is incorrect. The incorrect setting could be one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.
Action: Reenable the primary database to clear the error.
ORA-16816: incorrect database role
Cause: The Data Guard broker detected that this database object had a database role that was different from the recorded database role in the Data Guard Configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database.
Action: Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database object.
ORA-16817: unsynchronized Fast-Start Failover configuration
Cause: The Fast-Start Failover target standby database was not synchronized with the primary database. As a result, a Fast-Start Failover could not happen automatically in case of a primary database failure.
Action: Ensure that the Fast-Start Failover target standby database is running and that the primary database can ship redo logs to it. When the standby database has received all of the redo logs from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database.
ORA-16818: Fast-Start Failover suspended
Cause: The primary database was intentionally shutdown. As a result, a Fast-Start Failover could not happen automatically.
Action: Start up the primary database. This effectively restores the ability to automatically do a Fast-Start Failover in the event of a failure of the primary database.
ORA-16819: Fast-Start Failover observer not started
Cause: The observer for Fast-Start Failover was not started. As a result, Fast-Start Failover could not happen in the case of a primary database failure.
Action: Start the Fast-Start Failover observer by using, for example, the DGMGRL START OBSERVER command.
ORA-16820: Fast-Start Failover observer is no longer observing this database
Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:

- The node where the observer was running was not available.

- The network connection between the observer and this database was not available.

- Observer process was terminated unexpectedly.

Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL "STOP OBSERVER" command. Then restart the observer on another node. You may use the DGMGRL "START OBSERVER" command to start the observer on the other node.
ORA-16821: logical standby database dictionary not yet loaded
Cause: Logical standby apply had not finished loading the dictionary. This warning is flagged by the broker"s health check mechanism. This error is also flagged by failover and switchover if the target standby database has not loaded its dictionary.
Action: Start SQL Apply on the logical standby database and wait for it to reach the APPLYING state.
ORA-16822: new primary database not yet ready for standby database reinstatement
Cause: The new primary database, as a result of a logical failover operation, had not fully completed the failover steps. Subsequent reinstatement operations could not proceed until failover has completed on the new primary database.
Action: Wait until the completion of all failover steps on this new primary database and then retry the reinstate operation.
ORA-16823: redo transport mode is incompatible for current operation
Cause: The redo transport mode of this database was incompatible for this broker operation.
Action: Reset the LogXptMode database property for this database and retry the broker operation.
ORA-16824: Fast-Start Failover and other warnings detected for the database
Cause: The broker has detected multiple warnings for the database. At least one of the detected warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
ORA-16826: apply service state is inconsistent with the DelayMins property
Cause: This warning was caused by one of the following reasons:

1. Apply service was started without specifying the real time apply option or without the NODELAY option while DelayMins is zero.

2. Apply service was started with the real-time apply option or with the NODELAY option while DelayMins is greater than zero.

Action: Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property.
ORA-16950: Remote mapped cursors are not supported by this feature.
Cause: This cursor is a remote mapped cursor which could not be processed locally.
Action: Try to process this statement directly on the remote site.
ORA-16951: Too many bind variables supplied for this SQL statement.
Cause: Binding this SQL statement failed because too many bind variables were supplied.
Action: Pass the correct number of bind variables.
ORA-16952: Failed to bind this SQL statement.
Cause: Binding this SQL statement failed.
Action: Check if bind variables for that statement are properly specified.
ORA-16953: Type of SQL statement not supported.
Cause: This type of SQL statement could not be processed.
Action: none
ORA-16954: SQL parse error.
Cause: The specified SQL statement failed to be parsed.
Action: Check if syntax is correct and ensure that this statement can be parsed by the specified user name.
ORA-16955: Unknown error during SQL analyze.
Cause: The specified SQL statement failed to be analyzed.
Action: This is an internal error, please contact Oracle support.
ORA-16956: Only SELECT or DML statements are supported for test execute.
Cause: The specified SQL statement cannot be tested for execute.
Action: none
ORA-16957: SQL Analyze time limit interrupt
Cause: This is an internal error code used indicate that SQL analyze has reached its time limit.
Action: none
ORA-16958: DML statements running parallel are not supported for test execute.
Cause: The specified DML statement cannot be tested for execute because part of it is running parallel.
Action: none
ORA-17500: ODM err:string
Cause: An error returned by ODM library
Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance
ORA-17501: logical block size string is invalid
Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum
Action: check INIT.ORA file parameters
ORA-17502: ksfdcre:string Failed to create file string
Cause: file creation failed due to either insufficient OS permission or the file already exists
Action: check additional error messages
ORA-17503: ksfdopn:string Failed to open file string
Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.
Action: check additional error messages
ORA-17504: ksfddel:Failed to delete file string
Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file.
Action: check additional error messages
ORA-17505: ksfdrsz:string Failed to resize file to size string blocks
Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.
Action: check additional error messages
ORA-17506: I/O Error Simulation
Cause: The i/o request is marked with error because the i/o error simulation event is turned on.
Action: none
ORA-17507: I/O request size string is not a multiple of logical block size
Cause: i/o"s are done in multiple of logical block size
Action: Check additional error messages
ORA-17508: I/O request buffer ptr is not alligned
Cause: i/o request buffer should be alligned, check additional information for buffer ptr value
Action: Call Oracle Support Services
ORA-17509: Attempt to do i/o beyond block1 offset
Cause: When a file is identified with logical block size of 0, only i/o"s to block1 is allowed.
Action: check additional error messages and call Oracle Support Services
ORA-17510: Attempt to do i/o beyond file size
Cause: The i/o request points to a block beyond End Of File
Action: check additional error messages and call Oracle Support Services
ORA-17610: file "string" does not exist and no size specified
Cause: An attempt to create a file a file found neither an existing file nor a size for creating the file.
Action: Specify a size for the file.
ORA-17611: ksfd: file "string" cannot be accessed, global open closed
Cause: An attempt to write to a file which has gone offline/unidentified
Action: Check for other errno in the stack
ORA-17612: Failed to discover Oracle Disk Manager library, return value string
Cause: Discovery of the odm library by calling odm_discover() failed
Action: Contact your storage vendor who has provided the ODM library or call Oracle Support
ORA-17613: Failed to initialize Oracle Disk Manager library: string
Cause: ODM initialization for the thread failed due to insufficient previlige or memory.
Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library
ORA-17618: Unable to update block 0 to version 10 format
Cause: An attempt was made to update block 0 to version 10 format.
Action: Check additional error messages and call Oracle Support Services
ORA-17619: max number of processes using I/O slaves in a instance reached
Cause: An attempt was made to start large number of processes requiring I/O slaves.
Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.
ORA-17620: failed to register the network adapter with Oracle Disk Manager library: string
Cause: The ODM library returned an error while trying to register the network adapter.
Action: Make sure the network adapter name given in the fileio_network_adapters is a valid name, and that the Oracle user has the correct access privileges.
ORA-17621: failed to register the memory with Oracle Disk Manager library
Cause: The ODM library returned an error while trying to register the memory.
Action: Contact the Oracle Disk Manager Library provider.
ORA-17622: failed to deregister the memory with Oracle Disk Manager library
Cause: The ODM library returned an error while trying to deregister the memory.
Action: Contact the Oracle Disk Manager Library provider
ORA-17624: Failed to delete directory string
Cause: The directory that was being deleted is still in use or the process had insufficient permission to delete the directory.
Action: check additional error messages.
ORA-17626: ksfdcre: string file exists
Cause: trying to create a database file, but file by that name already exists
Action: verify that name is correct, specify REUSE if necessary
ORA-18000: invalid outline name
Cause: The parser detected a missing or invalid outline name
Action: none
ORA-18001: no options specified for ALTER OUTLINE
Cause: The parser detected that no clause was specified on the command Our performance tests, which are not typical as they exercise all branches of the code, have shown approximately a 30% performance increase line for ALTER OUTLINE.
Action: Re-issue the command, specifying a valid ALTER OUTLINE clause.
ORA-18002: the specified outline does not exist
Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.
Action: none
ORA-18003: an outline already exists with this signature
Cause: The signature generation algorithm generates signatures that are are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.
Action: Either re-issue the statement that led to the outline being created with some whitespace added or force the outline to be created in a different category.
ORA-18004: outline already exists
Cause: An outline already exists, either with the specified name, or for the specified SQL text.
Action: none
ORA-18008: cannot find OUTLN schema
Cause: The database creation script that creates this schema must not have been executed.
Action: Review the log files to see what happened when the database was created.
ORA-18009: one or more outline system tables do not exist
Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table
Action: Review the log files to see what happened when the database was created.
ORA-18010: command missing mandatory CATEGORY keyword
Cause: User failed to specify the CATEGORY keyword
Action: Re-issue the command with the CATEGORY keyword included
ORA-18015: invalid source outline signature
Cause: User imported an 8i outline into a 9i database without updating signatures
Action: execute dbms_outln.update_signatures
ORA-19000: missing RELATIONAL keyword
Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.
Action: Supply the RELATIONAL keyword in the storage clause
ORA-19001: Invalid storage option specified
Cause: An invalid storage option was specified for the XMLType.
Action: Supply a valid storage option.
ORA-19002: Missing XMLSchema URL
Cause: A XML schema URL must be specified in the storage option.
Action: Specify a URL for the XMLSchema.
ORA-19003: Missing XML root element name
Cause: A root element in the XMLSchema must be specified if the XML schema is given.
Action: Specify a root element in the XML schema.
ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
ORA-19005: Duplicate XMLType LOB storage option
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
ORA-19006: XMLType TYPE storage option not appropriate for storage type
Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option
Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column
ORA-19007: Schema string does not match expected string.
Cause: The given XML document conformed to a different schema than expected.
Action: Insert/Update only the XML documents that conform to that particular schema.
ORA-19008: Invalid version of the XMLType
Cause: An invalid version of the XMLType was found.
Action: This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database.
ORA-19009: Missing XMLSchema keyword
Cause: The XMLSchema keyword is missing
Action: Specify the XMLSchema URL and element name.
ORA-19010: Cannot insert XML fragments
Cause: XML fragments got from extractNode cannot be inserted into the database.
Action: Convert the fragment into a proper XML document before insertion.
ORA-19011: Character string buffer too small
Cause: The string result asked for is too big to return back
Action: Get the result as a lob instead
ORA-19012: Cannot convert XML fragment to the required datatype
Cause: A conversion to a datatype was requested which cannot be performed
Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.
ORA-19013: Cannot create VARRAY columns containing XMLType
Cause: An attempt was made to create a VARRAY column which contains a XMLType
Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead
ORA-19015: Invalid XML tag identifier (string)
Cause: An invalid XML identifer was detected during XML generation
Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification
ORA-19016: attributes cannot occur after element specifications
Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML
Action: Change the order of the types so that the attributes occur in the begining
ORA-19017: Attributes can only be simple scalars
Cause: Attribute values can only be simple scalar values
Action: Use only simple datatypes for attribute values
ORA-19018: Invalid character in XML tag "string"
Cause: A tag name was found to have an invalid XML character during XML generation.
Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.
ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
ORA-19020: invalid dereference of XMLType columns
Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table
Action: You can only dereference the attributes of a base table XMLType column
ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE
Cause: The first argument passed to the update value operator was not an XMLTYPE.
Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.
ORA-19024: Cursor expression must be named
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
ORA-19025: EXTRACTVALUE returns value of only one node
Cause: Given XPath points to more than one node.
Action: Rewrite the query so that exactly one node is returned.
ORA-19026: EXTRACTVALUE can only retrieve value of leaf node
Cause: Given XPath does not point to a leaf node.
Action: Rewrite the query so that a leaf node is returned.
ORA-19028: Invalid ADT parameter passed to toObject() function
Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.
Action: Pass an object of the correct type to toObject().
ORA-19029: Cannot convert the given XMLType to the required type
Cause: The passed in XMLType could not be convert to the required type
Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.
ORA-19030: Method invalid for non-schema based XML Documents.
Cause: The method can be invoked on only schema based xmltype objects.
Action: Don"t invoke the method for non schema based xmltype objects.
ORA-19031: XML element or attribute string does not match any in type string.string
Cause: The passed in XML tag does not match any in the object type
Action: Pass a valid canonical XML that can map to the given object type
ORA-19032: Expected XML tag string got string
Cause: When converting XML to object, a wrong tag name was present
Action: Pass a valid canonical XML that can map to the given object type
ORA-19033: schema specified in the XML document does not match the schema parameter
Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the "schema" parameter.
Action: Change the schema parameter to match the schema specified in the XML document.
ORA-19034: Type not supported during schema generation
Cause: The object type contained a type that is not supported for schema generation.
Action: Use a different type or do not generate a schema.
ORA-19035: Invalid select item of the query in newContextFromHierarchy()
Cause: The query does not have a number select item followed by an XMLType select item only.
Action: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType.
ORA-19036: Invalid query result set in newContextFromHierarchy()
Cause: The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query.
Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query.
ORA-19037: XMLType result can not be a fragment
Cause: The select item of the query in newContextFromHierarchy() is an XML fragment.
Action: Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment
ORA-19038: Invalid opertions on query context
Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().
Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().
ORA-19039: Keyword string reserved for future use
Cause: The keyword is reserved for future use as a builtin function.
Action: Change the name mentioned above to a different one.
ORA-19040: Element string does not match expected string.
Cause: The given XML document had a different root element than expected.
Action: Insert/Update only the XML documents that conform to that particular schema and element.
ORA-19041: Comment data cannot contain two consecutive "-"s
Cause: The given comment string expression has two consecutive "-"s.
Action: Modify comment string to eliminate one or both of the consevutive "-"s.
ORA-19042: Enclosing tag string cannot be xml in any case combination
Cause: The given enclosing tag matched "xml" in some case combination
Action: Modify the enclosing tag so that it is not xml in any case combination.
ORA-19043: Multiply nested XMLROOT function disallowed
Cause: An XMLROOT function has an operand that is also an XMLROOT function.
Action: Modify the query so that there are no multiply nested XMLROOT functions.
ORA-19044: character length specified for XMLSerialize is too small.
Cause: An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small.
Action: Modify the query so that the character length specified is larger.
ORA-19045: character set id specified for XMLSerialize not valid
Cause: An XMLSerialize function was called with an invalid value for the caracter set id.
Action: Modify the query so that the character set id is valid.
ORA-19100: PASSING or RETURNING keyword expected
Cause: The keyword PASSING or RETURNING was missing.
Action: Specify the PASSING or RETURNING keyword.
ORA-19101: CONTENT keyword expected
Cause: The keyword CONTENT was missing.
Action: Specify the CONTENT keyword.
ORA-19102: XQuery string literal expected
Cause: The string literal containing the XQuery expression was missing.
Action: Specify the XQuery expression as a string literal.
ORA-19103: VALUE keyword keyword
Cause: The keyword VALUE was missing.
Action: Specify the VALUE keyword.
ORA-19104: invalid XQueryX: missing attribute string
Cause: The XQueryX expression was not assigned the expected attribute.
Action: Specify a valid XQueryX.
ORA-19105: invalid XQueryX: expected text node - got string
Cause: The XQueryX expression did not contain a text node as expected.
Action: Specify a valid XQueryX.
ORA-19106: invalid XQueryX: expected string - got string
Cause: The XQueryX expression did not contain the node as expected.
Action: Specify a valid XQueryX.
ORA-19107: invalid XQueryX - unsupported construct - string
Cause: The given XQuery expression contains an unsupported construct.
Action: Specify a valid XQueryX.
ORA-19108: WHITESPACE keyword expected
Cause: The keyword WHITESPACE was missing.
Action: Specify the WHITESPACE keyword.
ORA-19109: RETURNING keyword expected
Cause: The keyword RETURNING was missing.
Action: Specify the RETURNING keyword.
ORA-19110: unsupported XQuery expression
Cause: The program specified an XQuery expression that is not supported.
Action: Rewrite the XQuery with a expression that is supported.
ORA-19111: error during evaluation of the XQuery expression
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
ORA-19112: error raised during evaluation: string
Cause: The error function was called during evaluation of the XQuery expression.
Action: Check the detailed error message for the possible causes.
ORA-19113: trace function called during evaluation: string
Cause: The trace function was called during evaluation of the XQuery expression.
Action: Check the log file for the trace message.
ORA-19114: error during parsing the XQuery expression: string
Cause: An error occurred during the parsing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
ORA-19115: too many context items specified
Cause: More than one context item was specified as input to the XMLQuery function.
Action: Specify a single context item for the XMLQuery function.
ORA-19116: too many xmlspace declarations
Cause: The query prolog contained multiple xmlspace declarations.
Action: Remove the duplicate xmlspace declarations.
ORA-19117: invalid redefinition of predefined namespace prefix "string"
Cause: The given predefined namespace was being redefined in a namespace declaration.
Action: Remove the namespace declaration that redefines the predefined namespace prefix.
ORA-19118: duplicate default namespace definition - string
Cause: More than one default namespace declaration used the given namespace URI.
Action: Remove the duplicate default namespace definition.
ORA-19121: duplicate attribute definition - string
Cause: More than one attribute with the same name.
Action: Remove the duplicate attribute definition.
ORA-19122: unsupported XQuery declaration
Cause: The program specified an XQuery declaration that is not supported.
Action: Rewrite the XQuery with a declaration that is supported.
ORA-19123: fn:zero-or-one() called with a sequence containing more than one item
Cause: sequence with more than one item was passed into fn:zero-or-one() function
Action: correct input argument to fn:zero-or-one() function
ORA-19124: fn:one-or-more() called with a sequence containing no items
Cause: sequence containing no items was passed into fn:one-or-more() function
Action: correct input argument to fn:one-or-more() function
ORA-19125: fn:exactly-one() called with a sequence containing zero or more than one item
Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function
Action: correct input argument to fn:exactly-one() function
ORA-19160: XP0003 - syntax error: invalid variable name string
Cause: The given XQuery variable does not begin with the "$" sign
Action: Fix the variable name to start with the "$" sign.
ORA-19161: XP0004 - XQuery type mismatch: invalid argument type "string" for function "string"
Cause: The type of the argument that was passed to the given function was not valid.
Action: Fix the argument to be of a type supported by the given function.
ORA-19162: XP0004 - XQuery type mismatch: invalid argument types "string", "string" for function "string"
Cause: The type of the arguments that were passed to the given function was not valid.
Action: Fix the arguments to be of a type appropriate for the given function.
ORA-19163: XP0004 - XQuery type mismatch: argument type mismatch: expected - "string" got - "string" for function "string"
Cause: The type of the arguments that were passed to the given function was not valid.
Action: Fix the arguments to be of a type appropriate for the given function.
ORA-19200: Invalid column specification
Cause: All input arguments must be valid columns
Action: Specify a valid list of columns
ORA-19201: Datatype not supported
Cause: The particular datatype is not supported in the XMLGEN operator
Action: Specify only supported datatypes as arguments to the XMLGEN operator
ORA-19202: Error occurred in XML processingstring
Cause: An error occurred when processing the XML function
Action: Check the given error message and fix the appropriate problem
ORA-19203: Error occurred in DBMS_XMLGEN processingstring
Cause: An error occurred when processing the DBMS_XMLGEN functions
Action: Check the given error message and fix the appropriate problem
ORA-19204: Non-scalar value "string" is marked as XML attribute
Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by "@". In this case, a non-scalar value was prefixed with "@"
Action: Remove the "@" sign, or make the value a scalar.
ORA-19205: Attribute "string" qualifies a non-scalar value in the select list
Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.
Action: Remove the "@" sign, or make the previous value a scalar.
ORA-19206: Invalid value for query or REF CURSOR parameter
Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.
Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.
ORA-19207: scalar parameter string of XMLELEMENT cannot have an alias.
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
Action: Remove the AS clause of the scalar element.
ORA-19208: parameter string of function string must be aliased
Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.
Action: Specify an alias for the expression using the AS clause.
ORA-19209: invalid or unsupported formatting argument
Cause: An invalid or unsupported formatting argument was supplied
Action: Change the formatting argument to legal supported values
ORA-19210: column "string", specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table "string"
Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.
Action: Change the column specified to be a column in the table
ORA-19211: column "string", specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
Cause: The column specified using setKeyColumn() was a non-scalar type column.
Action: Change the column specified to be a scalar column in the table
ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()
Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.
Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns
ORA-19221: XP0001 - XQuery static context component string not initialized
Cause: An unitialized static context component was encountered during the static analysis of the expression.
Action: initialize the given static context.
ORA-19222: XP0002 - XQuery dynamic context component string not initialized
Cause: An unitialized dynamic context component was encountered during the evaluation of the expression.
Action: Initialize the particular dynamic context component.
ORA-19223: XP0003 - syntax error in XQuery expression
Cause: The given XQuery expression contains syntax errors.
Action: Fix the syntax error in the XQuery expression.
ORA-19224: XP0004 - XQuery static type mismatch: expected - string got - string
Cause: The expression could not be used because it"s static type is not appropriate for the context in which it was used.
Action: Fix the expression to be of the required type or add appropriate cast functions around the expression.
ORA-19225: XP0005 - XQuery static type error: expected non empty type got empty sequence
Cause: The static type assigned to an expression other than the () expression must not be the empty type.
Action: Fix the expression so it does not return empty sequences.
ORA-19226: XP0006 - XQuery dynamic type mismatch: expected string got string
Cause: The expression could not be used because it"s dynamic type did not match the required type as specified by XQuery sequencetype matching rules.
Action: Fix the expression to return the expected type or use appropriate cast functions.
ORA-19227: XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content.
Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content.
ORA-19228: XP0008 - undeclared identifier: prefix "string" local-name "string"
Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context.
Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace.
ORA-19229: XP0009 - schema import not supported
Cause: A schema import was encountered in the query.
Action: remove the schema import.
ORA-19230: XP0010 - unsupported axis string
Cause: An unsupported axis was encountered in the given expression.
Action: Remove the unsupported axis from the expression.
ORA-19232: XQ0012 - imported schemas violate validity rules
Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification.
Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique -- that is, the pool of definitions must not contain two or more schema components with the same name and target namespace.
ORA-19233: XQ0013 - invalid pragma
Cause: A pragma was specified whose contents are invalid.
Action: Specify the pragma with the correct contents.
ORA-19234: XQ0014 - invalid or unsupported must-understand extension
Cause: The must-understand extension specified was either invalid or unsupported.
Action: remove the unsupported must-understand extension or fix the error.
ORA-19235: XQ0015 - unsupported must-understand extension
Cause: The XQuery flagger was enabled and the query contained a must-understand extension.
Action: remove the unsupported must-understand extension.
ORA-19236: XQ0016 - module declaration or import not supported
Cause: The given query had a module declaration or module import.
Action: Remove the import module or module declaration.
ORA-19237: XP0017 - unable to resolve call to function - string:string
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19238: XP0018 - focus not defined
Cause: The expression relied on the focus (context item, position and size) which was not defined.
Action: Define the focus for the expression.
ORA-19239: XP0019 - step expression must return sequence of nodes
Cause: The step expression returned a sequence containing an atomic value.
Action: Fix the path expression to return only nodes.
ORA-19240: XP0020 - context item must be node in an axis expression
Cause: The context item that was used in the axis epression is not a node.
Action: Change the context item to be a node.
ORA-19241: XP0021 - cast to type string failed
Cause: The value inside a cast expression could not be cast to the required type.
Action: Fix the input to the cast expression to be of a castable type.
ORA-19242: XQ0022 - namespace declaration attribute must be a literal
Cause: The namespace declaration attribute was not a literal string.
Action: Fix the namespace declaration to be a literal string.
ORA-19243: XQ0023 - invalid document node content in element constructor
Cause: The content sequence in an element constructor contained a document node.
Action: Change the content of the element constructor so that it does not contain a document node.
ORA-19244: XQ0024 - invalid attribute node in element constructor
Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node.
Action: Change the content sequence of the element constructor so that it does not contain the attribute node.
ORA-19245: XQ0025 - duplicate attribute name string
Cause: The content sequence of the element constructor contained more than one attribute that had the same name.
Action: Remove the duplicate attributes.
ORA-19246: XQ0026 - validation failed - element string not found in in-scope element declarations
Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations.
Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration.
ORA-19247: XQ0027 - validation error
Cause: An error was encountered during the validation of the expression.
Action: Fix the validation error.
ORA-19248: XQ0028 - invalid node in document constructor
Cause: The content sequence in a document constructor contained either a document or an attribute node.
Action: Fix the content so it does not contain any of the above node types.
ORA-19249: XP0029 - value does not match facet of the target type
Cause: The input value to a cast expression did not satisfy the facets of the target type.
Action: Fix the value to conform to the facets of the target type.
ORA-19250: XQ0030 - too many values to validate expression
Cause: The argument of a validate expression returned more than one element or document node.
Action: Fix the argument of the validate expression to return a single element or document node.
ORA-19251: XQ0031 - unsupported query version
Cause: The query version specified in the prolog was not supported.
Action: Supply the version of the query that is supported.
ORA-19252: XQ0032 - too many declarations for base URI
Cause: The query prolog contained multiple declarations for the base URI.
Action: Remove the duplicate definitions for the base URI.
ORA-19253: XQ0033 - too many declarations for namespace prefix string
Cause: The query prolog contained multiple declarations for the same namespace prefix.
Action: Remove the duplicate definitions for the namespace prefix.
ORA-19254: XQ0034 - too many declarations for function string
Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName.
Action: Remove the duplicate function definitions.
ORA-19255: XQ0035 - too many declarations of string in imported schemas
Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope.
Action: Fix the schema imports to remove the name conflict.
ORA-19256: XQ0036 - missing type definitions in imported module
Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module.
Action: Fix the module definintion to include the in-scope type definition.
ORA-19257: XQ0037 - function or variable string in module already defined
Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module.
Action: Remove the conflicting declarations.
ORA-19258: XQ0038 - unsupported or duplicate default collation specified
Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported.
Action: Remove the duplicate definition or specify a supported collation.
ORA-19259: XQ0039 - duplicate parameter name string in function declaration
Cause: The function declaration contained more than one parameter with the same name.
Action: Fix the function declaration to remove the duplicate parameters.
ORA-19260: XQ0040 - invalid namespace node in element constructor
Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node.
Action: Remove the namespace node in the element constructor.
ORA-19261: XQ0041 - non empty URI in QName
Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty.
Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part.
ORA-19262: XQ0042 - namespace constructor not inside an element constructor
Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor.
Action: Fix the namespace constructor to be inside an element constructor.
ORA-19263: XQ0043 - duplicate namespace prefix string
Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix.
Action: Remove the duplicate namespace definitions.
ORA-19264: XQ0044 - invalid namespace in attribute constructors
Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns).
Action: Change the namespace for the computed attribute constructor.
ORA-19265: XQ0045 - invalid or unknown prefix string in function declaration
Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local.
Action: Fix the function declaration to have the correct prefix.
ORA-19266: XQ0046 - invalid URI
Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema.
Action: Fix the URI.
ORA-19267: XQ0047 - module string not found
Cause: The module with the given target URI could not be found.
Action: Fix the prolog to import only available modules.
ORA-19268: XQ0048 - namespace string does not match target namespace string
Cause: The module contained a function or variable whose namespace did not match the target namespace of the module.
Action: Fix the namespace of the function or variable to match the target namespace of the module.
ORA-19269: XQ0049 - variable string defined multiple times
Cause: The module defined or imported the same variable multiple times.
Action: Fix the import or the module definition to remove duplicate definitions.
ORA-19270: XP0050 - treat failed - expected string got string
Cause: The type of the operand to the treat expression did not match the required type.
Action: Fix the input operand to be of the correct type.
ORA-19271: XP0051 - invalid atomic type definition
Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type.
Action: Use the correct atomic type name.
ORA-19272: XQ0052 - invalid atomic value in attribute or element constructor
Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string.
Action: Fix the content to contain atomic values that can be cast to a string.
ORA-19273: XQ0053 - empty string in namespace declaration
Cause: An empty string was used in a namespace declaration.
Action: Fix the namespace declaration to have a non-empty string.
ORA-19274: XQ0054 - variable initialization failed due to circularity
Cause: A circular definition was encountered when the variable was initialized.
Action: Remove the circularity in the initialization.
ORA-19275: XP0055 - schema path string not found in list of in-scope schema definitions
Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions.
Action: Include the appropriate schema that can be used to resolve the ElementTest.
ORA-19276: XP0005 - XPath step specifies an invalid element/attribute name: (string)
Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure.
Action: Correct the element or attribute name as the name may be mis-spelled.
ORA-19277: XP0005 - XPath step specifies an item type matching no node: (string)
Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure.
Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure.
ORA-19278: Invalid value: (string) for type: (string)
Cause: The value was invalid for the type.
Action: Correct the value or change the type.
ORA-19279: XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
Cause: The XQuery sequence passed in had more than one item.
Action: Correct the XQuery expression to return a single item sequence.
ORA-19280: XQuery dynamic type mismatch: expected atomic value - got node
Cause: A node was passed in to the expression where an atomic value was expected.
Action: Correct the XQuery expression to return an atomic value.
ORA-19281: XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration
Cause: The query prolog contained multiple inherit-namespaces declarations.
Action: Remove the duplicate inherit-namespaces declarations.
ORA-19282: XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
Cause: The query prolog contained multiple xmlspace declarations.
Action: Remove the duplicate xmlspace declarations.
ORA-19283: XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
Cause: The query contained a version declaration not supported by this implementation.
Action: Change the version declaration to 1.0 which is the version supported by this implementation.
ORA-19284: Encoding specification in version declaration not supported
Cause: The query contained an encoding specification.
Action: Remove the encoding specification.
ORA-19285: FODC0002 - error retrieving resource
Cause: The URI provided could not be resolved to a valid resource.
Action: Provide a valid URI for a resource.
ORA-19286: XP0017 - unable to resolve call to function - string
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19287: XP0017 - invalid number of arguments to function - string:string
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19288: XP0017 - invalid number of arguments to function - string
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19300: Error occurred in uri processingstring
Cause: An error occurred when processing the URL
Action: Check the given error message and fix the appropriate problem
ORA-19320: Host name not specified in HTTP URL
Cause: A host name was not specified in the HTTP url
Action: Specify a host name in the HTTP url when creating the URL string
ORA-19321: Could not open HTTP connection to host (string): port (string)
Cause: A HTTP connection could not be opened to the host
Action: Specify a valid host name and port to connect to
ORA-19322: An error occurred while reading from host (string): port (string)
Cause: An error occurred while reading from the HTTP host
Action: Specify a valid host name and port to read from
ORA-19323: Invalid url string
Cause: The URL must be a valid URL string
Action: Specify a valid url string
ORA-19330: Type "string"."string" not installed. Please install the type before using the CREATE_DBURI operator
Cause: The type required for the CREATE_DBURI operator has not been installed correctly.
Action: Read the installation notes to install the type correctly.
ORA-19331: Last argument to CREATE_DBURI operator must be a column
Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.
Action: Specify a valid column name in the query.
ORA-19332: Invalid column in the CREATE_DBURI operator
Cause: The argument to the CREATE_DBURI operator can only be a column.
Action: Specify a valid column name for the operator
ORA-19333: Invalid flags for the CREATE_DBURI operator
Cause: The flags argument given to the DBURI operator is invalid
Action: Specify a valid flag value (TEXT) for the DBURI operator
ORA-19334: Invalid column specification for CREATE_DBURI operator
Cause: All columns must be valid and pointing to the same table or view
Action: Specify valid list of columns that are from the same table or view.
ORA-19335: Invalid format type object
Cause: An invalid format type object was specified for the XML function
Action: Specify a valid format type object
ORA-19336: Missing XML root element
Cause: The XML being generated does not have an enclosing root element.
Action: The XML generated must have a root element
ORA-19361: ONLINE option not allowed with this type of index
Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index
Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option.
ORA-19371: invalid update option
Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE.
Action: Adjust the update option and retry the operation.
ORA-19372: invalid update condition
Cause: The user attempted to call load_sqlset with an invalid update condition.
Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation.
ORA-19373: invalid staging table or tablespace
Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace
Action: Check the arguments and try again.
ORA-19374: invalid staging table
Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table
Action: Provide a correct staging table or grant the appropriate privileges
ORA-19375: no CREATE TABLE privilege on schema "string"
Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema.
Action: Grant the privilege to the user and retry
ORA-19376: no privileges on tablespace provided or tablespace is offline
Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline
Action: Allocate space on the tablespace, bring it online, and retry
ORA-19377: no "SQL Tuning Set" with name like "string" exists for owner like "string"
Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively
Action: Provide a different filter after checking the state of the system
ORA-19378: invalid mode
Cause: The user specified an invalid mode argument to the capture function.
Action: Provide a mode argument that was defined in the dbmssqlt file
ORA-19379: invalid time_limit or repeat_interval
Cause: The user specified a NULL value for either the time_limit or the repeat_interval, or a repeat_interval that is greater than the time_limit
Action: Provide a non-null value and make sure time_limit >= repeat_interval
ORA-19380: invalid plan filter
Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function.
Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.
Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us