69 ORA-12700 to ORA-19400

ORA-12700: invalid NLS parameter value (string)

Cause: An invalid or unknown NLS configuration parameter was specified.

Action: n/a

ORA-12701: CREATE DATABASE character set is not known

Cause: The character set specified when creating the database is unknown.

Action: n/a

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: n/a

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: n/a

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: n/a

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: n/a

ORA-12707: error while getting create database NLS parameter string

Cause: Internal error

Action: n/a

ORA-12708: error while loading create database NLS parameter string

Cause: Internal error

Action: n/a

ORA-12709: error while loading create database character set

Cause: Internal error

Action: n/a

ORA-12710: CREATE CONTROLFILE character set is not known

Cause: The character set specified when creating the control file is unknown.

Action: n/a

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: n/a

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-12738: Express Instant Client: unsupported client national character set string

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets.

Action: Do not use Express Instant Client for this character set

ORA-12739: Express Instant Client: unsupported client character set string

Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets.

Action: Do not use Express Instant Client for this character set

ORA-12740: Express Instant Client: unsupported server national character set string

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets.

Action: Do not use Express Instant Client for this character set

ORA-12741: Express Instant Client: unsupported server character set string

Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets.

Action: Do not use Express Instant Light for this character set

ORA-12742: unable to create the collation key

Cause: The character argument of a collation-sensitive operator was too long or it had too many decomposable characters to create a collation key for it in the available buffer space.

Action: Shorten the argument value or, if using a UCA-based collation, increase the ratio of characters with short or no Unicode decomposition to characters with long Unicode decomposition in the value.

ORA-12743: internal LX error code, arguments: [string], [string], [string]

Cause: This is an internal error in a globalization support function.

Action: Contact Oracle Support Services.

ORA-12744: Character set string is not allowed as a database character set.

Cause: An attempt was made to create or alter a database using a client-only or conversion-only character set.

Action: Specify a supported database character set.

ORA-12752: An instance-critical process has terminated.

Cause: An unexpected error was encountered by an instance-critical process.

Action: Contact Oracle Support Services.

ORA-12753: The Oracle home user ID does not match the effective user ID of the local client which connected to the Oracle instance.

Cause: The user ID that is the owner of the Oracle home directory was not the same as the effective user ID of the local client that connected to the Oracle instance.

Action: Run the local client that connects to Oracle instance with the same user ID as the owner of the Oracle home.

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-12816: parallel create index fastpath operation
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 (requested string, available string, parallel_min_percent string)

Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than the minimum number of slaves were acquired

Action: Either reexecute the query with a 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-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-12874: parallel execution monitor terminated with error

Cause: The parallel execution monitor process died.

Action: Wait for the process to restart.

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: n/a

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: n/a

ORA-12903: default temporary tablespace must be an ONLINE tablespace
ORA-12904: default temporary tablespace cannot be altered to PERMANENT type
ORA-12905: default temporary tablespace cannot be brought OFFLINE
ORA-12906: cannot drop default temporary tablespace
ORA-12907: tablespace string is already the default temporary tablespace
ORA-12908: cannot specify SYSTEM as default temporary tablespace when creating database
ORA-12909: TEMPORARY keyword expected
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 shrink permanent or dictionary managed tablespace

Cause: An attempt was made to shrink a permanent tablespace or a dictionary managed tablespace.

Action: Check the tablespace type and issue the statement only on locally managed temporary tablespaces.

ORA-12917: Invalid option specified for default permanent tablespace
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: n/a

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: n/a

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: n/a

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: n/a

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-12928: ENCRYPTION option already specified

Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more than once.

Action: Remove all but one of the ENCRYPTION options.

ORA-12931: FORCE LOGGING or SET STANDBY NOLOGGING already specified

Cause: FORCE LOGGING or SET STANDBY NOLOGGING options were specified more than once.

Action: Remove all but one of the FORCE LOGGING or SET STANDBY NOLOGGING options.

ORA-12940: Not enough space in DBVerify text buffer

Cause: DBVerify ran out of text buffer. The error was trapped internally by the system. DBVerify would return the result in text buffer and then resume checking.

Action: None

ORA-12941: DBVerify exception

Cause: DBVerify encountered run-time error. The error signal was trapped internally by the system.

Action: None

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: n/a

ORA-12952: Control space growth in ASSM segment under concurrency
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: n/a

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-12998: Ignore errors during drop column from atb.c
ORA-12999: cannot DROP or SET UNUSED a column that has been set unused

Cause: An attempt was made to DROP or SET UNUSED a column that has already been 'set unused'.

Action: Use the DROP UNUSED COLUMNS option to remove the column.

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-13069: incorrect degree value for SDO_GEOMETRY object

Cause: An incorrect degree value <=1 was passed for a Non-Uniform Rational B-Spline curve.

Action: Correct the degree value for the Non-Uniform Rational B-Spline curve.

ORA-13070: incorrect number of control points for SDO_GEOMETRY object

Cause: An incorrect number of control points was passed for a Non-Uniform Rational B-Spline curve.

Action: Correct the number of control points for the Non-Uniform Rational B-Spline curve.

ORA-13071: incorrect control points, degree for SDO_GEOMETRY object

Cause: An incorrect number of control points and degree was passed for a Non-Uniform Rational B-Spline curve.

Action: Ensure that the number of control points is greater than the degree for a Non-Uniform Rational B-Spline curve.

ORA-13072: incorrect number of knots for SDO_GEOMETRY object

Cause: An incorrect number of knot values was passed for a Non-Uniform Rational B-Spline curve.

Action: Correct the number of knot values passed for the Non-Uniform Rational B-Spline curve.

ORA-13073: incorrect control point weight value for a SDO_GEOMETRY object

Cause: An incorrect value was passed for the weight of a control point of a Non-Uniform Rational B-Spline curve.

Action: Ensure all weight values for control points are positive.

ORA-13074: incorrect knot value for SDO_GEOMETRY object

Cause: An incorrect knot value was passed for a Non-Uniform Rational B-Spline curve.

Action: Ensure the knot values passed for the Non-Uniform Rational B-Spline curve are in non-decreasing order.

ORA-13075: incorrect knot value sequence for SDO_GEOMETRY object

Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational B-Spline curve.

Action: Ensure the knot values passed for the Non-Uniform Rational B-Spline curve have no more than a sequence of 'k' consecutive identical values or no more than 'k + 1' consecutive same values at the beginning or end of Non-Uniform Rational B-Spline curve.

ORA-13076: incorrect knot value sequence for SDO_GEOMETRY object

Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational B-Spline curve.

Action: Ensure the knot value sequence passed for the Non-Uniform Rational B-Spline curve is a normalized vector beginning at zero and ending at one.

ORA-13077: incorrect start or end point for subelement of a compound curve

Cause: The end point of a subelement for a compound curve was not equal to the start point of the next subelement, or the start point of a subelement was not equal to the end point of the previous subelement and one of the subelements was a NURBS curve.

Action: Ensure that the end point of each subelement is equal to the start point of the next subelement and that the start point of each subelement is equal to the end point of the previous subelement when one of the subelements is a NURBS curve.

ORA-13107: operation not supported for Non-Uniform Rational B-Spline type

Cause: This operation cannot be executed for Non-Uniform Rational B-Spline curves.

Action: Specify a geometry that does not contain a Non-Uniform Rational B-Spline curve type.

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

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

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

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-13391: string

Cause: An attempt was made to violate GeoRaster management restrictions.

Action: Check the documentation for more detailed information.

ORA-13392: status report error: string

Cause: There was an error on status report related operation.

Action: Check the error message for details.

ORA-13393: null or invalid string parameter

Cause: The operation failed because the input parameter was null or invalid.

Action: Correct the parameter and try again.

ORA-13397: different dimension sizes in the input GeoRaster objects

Cause: The two input GeoRaster objects had different dimension sizes.

Action: Check the documentation and make sure the dimension size is same for both input GeoRaster objects.

ORA-13398: invalid expression parameter: string

Cause: The expression parameter was not a valid math expression.

Action: Check the documentation and make sure the expression parameter is correct.

ORA-13399: invalid condition parameter: string

Cause: The condition parameter was not a valid boolean expression.

Action: Check the documentation and make sure the condition parameter is correct.

ORA-13400: duplicate entry for string in USER_SDO_GEOR_SYSDATA view

Cause: The current operation caused a duplicate RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view.

Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view is unique.

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 parameterstring

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 parameterstring

Cause: The scale parameter contained an invalid specification.

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 mosaic operation: string

Cause: An attempt to perform a mosaic operation failed.

Action: Check the error message 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 definition 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: invalid background filling value parameter

Cause: The background filling value parameter was invalid either because the array had the wrong size or because some of the element values were invalid.

Action: Make sure the parameter that specifies the background filling value is valid. The size of the array must equal to either 1 (the value is for all bands) or the exact band dimension size. The element values must be valid cell values as determined by the cell depth.

ORA-13426: invalid window parameter

Cause: The specified window parameter was invalid.

Action: Specify a valid window parameter. Check the documentation for details.

ORA-13427: invalid bitmap mask

Cause: The bitmap mask was not a valid 1BIT GeoRaster object, or it had the wrong dimension sizes.

Action: Make sure the bitmap mask is a valid 1BIT GeoRaster object with only one band, and the row and column dimension sizes of the bitmap mask are the same as those of the target GeoRaster object.

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: NULL or invalid blankCellValue

Cause: The blankCellValue element could not be found in the metadata of a blank GeoRaster object, or the specified blankCellValue element value was NULL or invalid.

Action: Call SDO_GEOR.setBlankCellValue to add blankCellValue to the metadata whenever the isBlank element value is TRUE, and make sure that the specified blankCellValue element value is not NULL and is in the range as designated by the cellDepth definition of the GeoRaster object.

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

Cause: The specified error relates to the polynomialModel element in the Spatial Reference System (SRS) metadata.

Action: Check the documentation and make sure that a valid polynomial model is specified.

ORA-13442: GeoRaster object not registered: string

Cause: There was no sysdata entry for the specified GeoRaster object.

Action: Make sure that a sysdata entry has been inserted for the specified GeoRaster object.

ORA-13443: null or invalid values in string

Cause: There were null or invalid component values in the specified metadata.

Action: Check the documentation and make sure that all the component values are valid.

ORA-13444: cannot perform mergeLayers operation

Cause: The two GeoRaster objects whose layers are to be combined together either had different row or column dimension sizes, or their georeferencing information did not match.

Action: Make sure the objects have the same row and column dimension sizes. If neither is georeferenced, their ULTCoordinate values must be the same. Otherwise, they must be both georeferenced and cover the same area in the model space.

ORA-13445: NULL or invalid NODATA value or value range

Cause: There was invalid NODATA value or value range in the metadata, or the specified NODATA value or value range was invalid.

Action: Make sure the NODATA value or value range is not NULL and is completely contained in the range as designated by the cellDepth definition of the specified GeoRaster object.

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

Cause: There was an error in the original GeoRaster cell data or in the cell data of the pyramids.

Action: If the error is related to the original GeoRaster cell data, the GeoRaster object is invalid and has to be deleted or manually repaired. If the error is related to pyramids, delete the pyramids and regenerate them.

ORA-13457: bitmap mask cell data error: string

Cause: There was an error in the cell data of an original bitmap mask or in the cell data of the pyramids of a bitmap mask.

Action: If the error is related to an original bitmap mask, remove the bitmap mask. If the error is related to the pyramids of a bitmap mask, delete the pyramids and regenerate 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.changeFormatCopy to transform the image to a supported interleaving type.

ORA-13462: invalid blocking specification

Cause: The specified blocking configuration was invalid.

Action: Check the documentation for the blocking specification supported by GeoRaster.

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

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 for the specified compression.

Action: Check the error message for details. Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormatCopy 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-13468: invalid blockMBR

Cause: Invalid blockMBR geometries were stored in the raster data table.

Action: Make sure the blockMBR geometries stored in the raster data table are valid, or call SDO_GEOR.generateBlockMBR() to regenerate the blockMBR geometries.

ORA-13469: cannot perform updateRaster operation

Cause: The data of the source GeoRaster object could not be used to update that of the target GeoRaster object.

Action: Make sure the source and the target GeoRaster objects have the same cell depth, and that both objects are either georeferenced or not georeferenced at all. If both are georeferenced, they should be in the same coordinate system and have the same spatial resolutions.

ORA-13470: target and source layers or bands mismatched

Cause: The number of specified target layers or bands and source layers or bands did not match.

Action: When updating layers or bands of a target GeoRaster object to reflect the associated layers or bands of the source GeoRaster object, specify the same number of layers or bands for both the source and the target objects. Check the documentation for details.

ORA-13471: unable to determine the owner of string

Cause: The owner of the specified raster data table could not be determined.

Action: Make sure the GeoRaster object that refers to the raster data table has been registered by inserting the object into a GeoRaster table.

ORA-13472: invalid geometry parameter

Cause: The geometry parameter did not specify a valid geometry.

Action: Specify a valid 2D or 3D geometry. If the model SRID is null or indicates a 2D coordinate system, the geometry must be 2D. If the model SRID indicates a 3D coordinate system, the geometry must either be a 3D geometry or a 2D geometry that can be converted to 3D with the specified vertical axis (or vertical SRID) and ellipsoidal parameters.

ORA-13473: invalid rasterSpec parameter

Cause: The rasterSpec parameter contained an invalid specification.

Action: Check the documentation and make sure the rasterSpec parameter contains only valid keywords and values.

ORA-13474: invalid rasterDataTable name: string

Cause: The rasterDataTable name was not a valid nonquoted identifier, it contained a period separator, or not all of the alphanumeric characters were uppercase.

Action: Ensure that the table name is a valid nonquoted identifier without any period separators, and that all the alphanumeric characters are uppercase.

ORA-13475: invalid GeoRaster object for output

Cause: The output GeoRaster object had the same RASTER_DATA_TABLE and RASTER_ID combination as that of an input GeoRaster object.

Action: Ensure that the output GeoRaster object is different from any of the input GeoRaster objects.

ORA-13476: invalid or out of scope point specification

Cause: The point position specified by the point geometry parameter or the rowNumber/colNumber parameter combination was null or out of scope.

Action: Ensure that the parameters specify a valid point that translates or can be translated into a cell position inside the cell space of the GeoRaster object.

ORA-13477: invalid GCP georeferencing specification: string

Cause: The specified functional fitting method was not supported, the number of GCPs was insufficient, some GCPs were invalid, or the distribution of the GCPs led to no solution or an unstable solution.

Action: Check the GeoRaster documentation for the supported functional fitting methods and the requirements of GCPs.

ORA-13478: the target SRID is the same as the source GeoRaster object's SRID

Cause: The target SRID was not different from the source GeoRaster object's SRID.

Action: Specify a different valid SRID for the target GeoRaster object.

ORA-13479: cannot reproject

Cause: Reprojection from source to destination projection produced a large distortion.

Action: Check the destination projection and make sure it is suitable for the area covered by the source GeoRaster object. Check the GeoRaster documentation for more information about reprojection.

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 or compression type is not supported: string

Cause: The file format 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-13486: invalid or insufficient GeoTIFF metadata to georeference the GeoRaster object: string

Cause: The GeoTIFF metadata of the specified input image contained invalid or insufficient information to georeference the GeoRaster object.

Action: Check the error message for details.

ORA-13487: SRID not found for source coordinate system metadata

Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the source coordinate system metadata.

Action: Add a user-defined coordinate reference system for this coordinate system, as explained in the Oracle Spatial documentation.

ORA-13488: cannot perform transformation: string

Cause: An attempt to perform a transformation operation failed.

Action: Check the error message for details.

ORA-13497: string

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

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

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

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-13531: SQL Text was purged from AWR before the operation completed

Cause: A SQL was purged from AWR before the operation completed.

Action: Retry the operation.

ORA-13532: SQL ID [string] already exists

Cause: The operation failed because the specified SQL ID already existed in the repository.

Action: Check the SQL ID and retry the operation.

ORA-13533: invalid SQL ID

Cause: The operation failed because the specified SQL ID was invalid.

Action: Check the SQL ID and retry the operation.

ORA-13534: Current SQL count(string) reached maximum allowed (string)

Cause: The operation failed because the maximum allowed colored SQL was exceeded.

Action: Check the count for colored SQL.

ORA-13535: name (string) is already used by an existing baseline template

Cause: The operation failed because the specified baseline template name already existed in the Workload Repository.

Action: Check the baseline template name and retry the operation.

ORA-13536: baseline template (string) does not exist

Cause: The operation failed because the specified baseline template name did not exist in the Workload Repository.

Action: Check the baseline template name and retry the operation.

ORA-13537: invalid input for create baseline template (string, string)

Cause: Invalid input was specified for the create baseline template routine.

Action: Check the argument displayed in the error message text.

ORA-13538: invalid value for baseline expiration (string)

Cause: An invalid value was specified for the expiration of a baseline. The expiration is specified in number of days, and the expiration must be at least one day.

Action: Check the value for expiration.

ORA-13539: invalid input for modify baseline window size (string, string)

Cause: Invalid input was specified for the modify baseline window size routine.

Action: Check the argument displayed in the error message text.

ORA-13540: operation not allowed on system moving window baseline (string)

Cause: The requested operation was not allowed on the system moving window baseline.

Action: Retry the operation with another baseline name.

ORA-13541: system moving window baseline size (string) greater than retention (string)

Cause: The system moving window baseline size must be less than the retention setting. The specified window size or retention violate this.

Action: Check the moving window baseline size or retention.

ORA-13542: baseline ID (string) does not exist

Cause: The operation failed because the specified baseline ID did not exist in the Workload Repository.

Action: Check the baseline ID and retry the operation.

ORA-13543: error encountered while retrieving baseline template information

Cause: A read error occurred during the OCI operation to retrieve the baseline template information.

Action: Check associated error. Correct problem and retry the operation.

ORA-13544: error encountered while automatically generating a baseline

Cause: An error occurred while automatically generating a baseline based on the template information.

Action: Look in the trace file for more error information.

ORA-13545: invalid baseline template name

Cause: The operation failed because the specified baseline template name was an invalid identifier.

Action: Check the baseline template name and retry the operation.

ORA-13546: Error encountered during maintenance of Adaptive Thresholds

Cause: Error occurred during OCI operation due to underlying error.

Action: Check associated OCI error. Correct problem and retry the operation.

ORA-13547: Unable to drop baseline since it is in use by string

Cause: The system is not able to drop the baseline since the baseline is in use by a functionality that depends on its existence.

Action: Note the name of the functionality using the baseline, and check if the functionality still needs the baseline.

ORA-13548: Unable to find valid snapshot IDs for the inputted baseline time range

Cause: The system is not able to find valid snapshot IDs for the inputted time range while attempting to create a baseline.

Action: Check that the inputted time range has at least two valid snapshots. The dba_hist_snapshot displays the snapshot id and time information.

ORA-13549: invalid input for create baseline with time range (string)

Cause: Invalid time input was specified for the create baseline routine.

Action: Check the argument displayed in the error message text.

ORA-13550: value "string" of length (string) exceeded maximum length (string) for parameter [string]

Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) registration routine.

Action: Check the argument displayed in the error message text.

ORA-13551: source database same [string] not found in AWR

Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) operation.

Action: Check the argument displayed in the error message text.

ORA-13552: parameter [string] of value [string] mismatched with AWR registered value [string]

Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) operation.

Action: Check the argument displayed in the error message text.

ORA-13553: operation failed - missing parameter [string]

Cause: The required parameter was missing for the Automatic Workload Repository (AWR) operation.

Action: Check the parameter name displayed in the error message text.

ORA-13554: failed to stop report capture on all instances

Cause: The API 'finish_report_capture' ran successfully on %d instances only.

Action: Check if all instances are active and running.

ORA-13600: error encountered in Advisor\nstring

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 specified name string is invalid.

Cause: An attempt was made to specify a name for a task, object, execution or directive instance, which contained 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: string 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 most recent execution of task string contains no 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-13645: The specified execution string does not exist for this task.

Cause: You attempted to reference an advisor task execution using a name that did not exist.

Action: Adjust the name and retry the operation.

ORA-13646: The specified execution string already exists

Cause: You attempted to perform a new execution using a name that already exists for the specified task. Execution names must be unique within the same task.

Action: Adjust the name and retry the operation.

ORA-13647: Setting of parameter string is disallowed during task execution.

Cause: You attempted to set the value of a parameter while the task was being executed. This parameter cannot be changed until the task finishes its execution.

Action: Verify the status of the task and retry the operation.

ORA-13648: The specified execution type does not exist for this advisor.

Cause: You attempted to use an advisor task execution type using a name that did not exist.

Action: Adjust the name and retry the operation.

ORA-13649: The type of execution is not specified for this advisor or task.

Cause: You attempted to execute a task for a multi-execution task advisor without specifying the type of execution to perform.

Action: Set the execution type and retry the operation.

ORA-13650: The specified object does not exist for this execution.

Cause: You attempted to associate an object to a task execution that id not contain the object.

Action: Adjust the execution name and object ID, and then retry the operation.

ORA-13651: The specified list of execution parameters is invalid.

Cause: The list did not include pairs of (parameter_name, parameter_value) where every parameter is a valide task parameter. Duplicates are not allowed.

Action: Adjust the content of the list, and then retry the operation.

ORA-13652: Cannot set execution parameters for this advisor

Cause: You attempted to set execution parameters for an advisor that did not support multiple executions of its tasks.

Action: Adjust the property of the advisor, and then retry the operation.

ORA-13653: The directive with definition id string was not found.

Cause: An invalid directive identifier was specified to advisor framework.

Action: User should specify a correct identifier number and retry the operation.

ORA-13654: The directive with instance id of string was not found.

Cause: An invalid instance identifier was specified to advisor framework.

Action: User should specify a correct instance identifier number and retry the operation.

ORA-13655: The directive document contains a syntax error and cannot be loaded.

Cause: An attempt was made to load an XML-based directive that does not conform to the documented DTD.

Action: Reformat the directive according the documented DTD.

ORA-13656: The parameter was not found in directive string.

Cause: The specified parameter name could not be located within the directive XML document.

Action: Verify the existence of the parameter in the specified directive.

ORA-13657: The filter Xpath specification has invalid syntax.

Cause: The specified filter could not be compiled within the directive XML document.

Action: Verify the syntax of the filter and retry the operation.

ORA-13658: The specified directive already has an instance

Cause: An attempt was made to create multiple instances of a directive when not permitted

Action: Verify the parent directive identifier and the instance name.

ORA-13659: A directive with domain "string" and name "string" already exists for advisor string.

Cause: The specified directive is not unique among the directives.

Action: Choose a directive name and domain that is distinct for the associated advisor.

ORA-13660: A directive instance with the name "string" already exists.

Cause: The specified directive instance is not unique among instances for this directive.

Action: Choose an instance name that is distinct for the associated directive.

ORA-13661: A directive instance with the name "string" was not found.

Cause: An attempt was made to update or delete a non-existent directive instance.

Action: Verify the parent directive identifier and the instance name.

ORA-13662: The specified value provided for parameter string is not valid for this task.

Cause: The supplied parameter value was not valid for the current task configuration.

Action: Retry by supplying valid value. Check the current task configuration.

ORA-13663: The task string contains no results for execution string.

Cause: An attempt was made to create a report or script from an execution that had not been successfully completed.

Action: Run a new execution and then retry the operation.

ORA-13664: A task-managed "SQL Tuning Set" already exists for task "string".

Cause: An attempt was made to create a task-managed SQL Tuning Set for a task that already had one.

Action: Create a new task to use a different SQL Tuning Set.

ORA-13665: Execution names are not correctly ordered.

Cause: The supplied execution names were not properly ordered by execution start date.

Action: Retry by supplying a valid order.

ORA-13666: Task ID string does not exist.

Cause: The supplied task ID was invalid.

Action: Check the task ID and try again.

ORA-13667: Execution ID string does not exist.

Cause: The supplied execution ID was invalid.

Action: Check the execution ID and try again.

ORA-13668: The current operation was aborted because it was blocking another session.

Cause: The task or object operation interrupted itself when it detected that it was blocking some other session.

Action: Retry the operation when the conflicting operations are not running.

ORA-13669: Execution provided has type "string", expected "string".

Cause: An execution was provided whose type did not match the one expected by the API.

Action: Check the execution name, and try again.

ORA-13670: No execution of type string exists for task provided.

Cause: No execution of the required type existed for the given advisor task.

Action: Check the task, and try again.

ORA-13699: Advisor feature is not currently implemented.

Cause: An attempt was made to execute an unsupported advisor operation.

Action: Verify the availability of the operation.

ORA-13700: Reserved for ADDM tracing.
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-13713: Finding name "string" does not exist. Look in DBA_ADVISOR_FINDING_NAMES for all valid values

Cause: Attempt to refer to an advisor's finding name that does not exist.

Action: Specify a valid value. The list of all valid values is in DBA_ADVISOR_FINDING_NAMES

ORA-13714: "string" is not a valid SQL_ID value

Cause: The specified value of SQL_ID was not properly formatted.

Action: Specify a valid value consisting of a 13 character string with characters from '0' to '9' and from 'a' to 'z'.

ORA-13715: "string" is not recognized by ADDM as a parameter name

Cause: The specified value for a system parameter was not recognized by ADDM.

Action: Specify a value that appears in the NAME column of V$PARAMETER.

ORA-13716: Diagnostic Package License is needed for using this feature.

Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Diagnostic Package was disabled.

Action: Modify the parameter value if the Diagnostic Package License was purchased.

ORA-13717: Tuning Package License is needed for using this feature.

Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Tuning Package was disabled.

Action: Modify the parameter value if the Tuning Package License was purchased.

ORA-13718: Tuning Package License or Real Application Testing Option is needed for using this feature.

Cause: The specified package license and option were not installed.

Action: Consider purchasing and installing either the missing package licence or option. If the tuning package license was purchased, then check the value of system parameter CONTROL_MANAGEMENT_PACK_ACCESS.

ORA-13719: Imported AWR snapshots are from a database with an incompatible character set.

Cause: ADDM analysis was attempted on imported Automatic Workload Repository (AWR) snapshots with incompatible character set.

Action: Perform ADDM analysis using a database with the same version and character set as the original database.

ORA-13720: dimension name provided is too long

Cause: Active Session History (ASH) dimension name provided was longer than the limit of 30 characters.

Action: Correct the dimension name and retry the operation.

ORA-13721: dimension name provided is invalid

Cause: Active Session History (ASH) dimension name provided was invalid.

Action: Correct the dimension name and retry the operation.

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

Action: Check the attribute in the ranking measure 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 begin snapshot 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-13781: cannot perform test-execute and explain plan operations on the automatic SQL tuning task

Cause: The user attempted to test-execute or generate explain plans for a SQL workload using the automatic SQL tuning task.

Action: Verify the name of the tuning task 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 "string"

Cause: An attempt was made to accept SQL profiles for all statements in the input workload.

Action: Provide the object identifier corresponding to a statement in the workload 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 task created to process a single statement

Cause: An attempt was made to resume a task that was created for a single SQL statement. A task can be resumed only if it is used for a SQL Tuning Set.

Action: No action required.

ORA-13793: invalid comparison metric

Cause: An invalid metric to compare SQL performance was specified.

Action: Use execution statistics to compare the result of two executions and optimizer_cost to analyze performance of two explain plan actions.

ORA-13794: execution type mismatch

Cause: An attempt was made to analyze the performance of a SQL workload using two executions that were generated using two different actions.

Action: check the name and type of task executions to analyze and retry the operation.

ORA-13795: missing task execution

Cause: An insufficient number of valid task executions to analyze the performance of a SQL workload were specified.

Action: run the task to generate two executions of the same type and retry the operation.

ORA-13796: invalid value string specified for problem type

Cause: An invalid problem type was specified to the SQL diagnosis advisor. Problem type should be one of the PROBLEM_TYPE_* defined in 'admin/dbmsdiag.sql'.

Action: Specify valid problem type.

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-13810: FORCE_TRACKING parameter can only be values of NO_FORCE_TRACKING or FORCE_TRACKING

Cause: The wrong value was passed in for the parameter.

Action: Check the value and input the correct value.

ORA-13811: error encountered during the start of the operation

Cause: An internal error was encountered.

Action: Check the alert log and report to Oracle Support Services.

ORA-13812: current session does not have database operation monitored

Cause: An attempt was made to end a database operation that did not exist.

Action: Check if the database operation is being monitored.

ORA-13813: database operation name or execution ID does not match

Cause: The database operation name or execution ID did not match.

Action: Call the interface with the right database operation name and execution ID.

ORA-13825: missing SQL statement text

Cause: No SQL text was provided to the create SQL profile or patch operation.

Action: Retry with properly specified SQL text.

ORA-13826: empty SQL profile or patch not allowed

Cause: No attributes were specified to the create SQL profile or patch operation.

Action: Retry with at least one hint specified.

ORA-13827: null or zero length attribute not allowed

Cause: One of the attributes within the SQL profile or patch was not properly specified.

Action: Retry with a fully specified SQL profile or patch.

ORA-13828: generated SQL profile or patch name string already exists

Cause: A SQL profile or patch already exists with the name generated by the system.

Action: Retry the operation as the generated name is time sensitive.

ORA-13829: SQL profile or patch named string already exists

Cause: A SQL profile or patch already exists with the name specified.

Action: Specify a different name or drop the existing SQL profile or patch.

ORA-13830: SQL profile or patch with category string already exists for this SQL statement

Cause: A SQL profile or patch already exists for the given SQL statement and category.

Action: Drop or update the existing SQL profile or patch.

ORA-13831: SQL profile or patch name specified is invalid

Cause: An invalid SQL profile or patch 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 or patch named string doesn't exist

Cause: A SQL profile or patch name was specified that doesn't exist.

Action: Verify the name of the SQL profile or patch.

ORA-13834: name of SQL profile or patch to be cloned must be provided

Cause: A SQL profile or patch name was not provided as the from target of a clone SQL profile or patch operation.

Action: Provide the name of the SQL profile or patch being cloned.

ORA-13835: invalid attribute name specified

Cause: An invalid attribute name was specified for an alter SQL profile or patch 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 or patch 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-13845: invalid SQL profile XML specification provided

Cause: The supplied XML specification for the SQL profile did not adhere to the proper schema.

Action: Check the syntax and try again.

ORA-13846: Cannot create SQL plan baseline on the given plan

Cause: There are either multiple plans exist for the given value or the plan is not reproducible.

Action: Call Oracle Support.

ORA-13847: The plan with plan hash value string does not exist

Cause: The give plan does not exist.

Action: Check the available plans.

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 tablespace 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-13920: Threshold cannot be set when database is in read-only mode.

Cause: SET_THRESHOLD procedure was called when database was open in read-only mode.

Action: Call SET_THRESHOLD procedure when database is open in read/write mode.

ORA-13951: MMON sub-action time limit exceeded

Cause: MMON sub-action did not complete within the system specified time frame.

Action: None

ORA-13970: Invalid name of "string" given

Cause: Passed an invalid component, report, or transformation name to the framework. Names must be alphanumeric and can contain the underscore (_) character.

Action: Try again with a valid name

ORA-13971: string "string" unknown

Cause: Passed an unknown component, report, or transformation to the framework.

Action: Give a different name

ORA-13972: string "string" unknown for string "string"

Cause: An object with the first name is unknown within the naming scope of the second name

Action: Change the parameters passed in or register the proper object

ORA-13973: string unknown for string "string"

Cause: An object is unknown within the given naming scope

Action: Change the parameters passed in or register the proper object

ORA-13974: string with name "string" already exists

Cause: An object with the given name already exists

Action: Give a different name

ORA-13975: string with name "string" already exists for string "string"

Cause: An object with the first name already exists within the naming scope of the second name

Action: Give a different name

ORA-13976: Improperly-formed report tag

Cause: The top-level report tag was not built properly

Action: Make sure that the report tag is built using the common tag library function

ORA-13977: Invalid content type

Cause: An invalid content type was passed to the register format API

Action: Correct your code to use the values in dbmsrep.sql

ORA-13978: Invalid reference string parameter or value

Cause: An invalid parameter/value was passed to a dbms_report API

Action: Ensure that the parameter names and values are alphanumeric.

ORA-13979: Filename too long

Cause: An invalid file name was passed to STORE_FILE

Action: Ensure that the filename is less than 500 bytes

ORA-13980: Invalid file URL

Cause: A URL with invalid syntax was provided, either directly to the function or via an XML IMPORT or INCLUDE.

Action: Check the URL.

ORA-13981: Invalid file URL or path prefix

Cause: Either a URL or path prefix with invalid syntax was provided.

Action: Check the URL

ORA-13982: Could not find file at URL provided

Cause: The file requested could not be found in the given location.

Action: Check the URL provided.

ORA-13983: Missing body tag from HTML

Cause: An HTML document was passed to the function missing its body tag.

Action: Check the HTML source.

ORA-13984: Invalid reference string

Cause: The given reference string could not be parsed.

Action: Check the reference string syntax.

ORA-13985: Invalid URL provided to servlet

Cause: An invalid URL was provided to the servlet.

Action: Check the URL.

ORA-13986: Error \string received from XPath engine

Cause: An error was received from the xpath library during an xpath operation.

Action: Check xmlerr.h to understand the cause of the error.

ORA-13987: Invalid input to build common <string> tag

Cause: Invalid input was given when attempting to build a common tag.

Action: Check the function input to make sure all necessary information is given.

ORA-13988: Invalid input given to variable argument list report function.

Cause: An invalid parameter was provided to one of the report framework variable argument list functions.

Action: Check the function input and try again.

ORA-13989: Invalid input given to structured argument list report function.

Cause: An invalid parameter was provided to one of the report framework structured argument list functions.

Action: Check the function input and try again.

ORA-13990: Invalid tag name given to common tag callout function.

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 descriptions, 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 descriptions 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 and editioning views

Cause: An attempt was made to use a partition-extended object name with an object which was not a table or an editioning view.

Action: Avoid using partition-extended name syntax with objects which are not tables or editioning views

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 is a temporary 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-14139: table string.string is already in read-only mode

Cause: an attempt was made to set a read-only table in read-only mode

Action: this DDL can only be executed on a read/write table

ORA-14140: table string.string is already in read/write mode

Cause: an attempt was made to set a read/write table in read/write mode

Action: this DDL can only be executed on a read-only table

ORA-14141: ALTER INDEX VISIBLE|INVISIBLE may not be combined with other operations

Cause: ALTER INDEX statement attempted to combine a VISIBLE|INVISIBLE operation with some other operation which is illegal

Action: Ensure that VISIBLE|INVISIBLE operation is the sole operation specified in ALTER INDEX statement

ORA-14142: ALTER INDEX VISIBLE|INVISIBLE may not be used with certain types of index

Cause: Using the ALTER INDEX VISIBLE|INVISIBLE statement on certain types of indexes (IOT-TOP, Cluster indexes) is illegal.

Action: Remove the option VISIBLE|INVISIBLE.

ORA-14143: CREATE INDEX INVISIBLE may not be used with this type of index

Cause: Certain types of indexes (IOT-TOP, Cluster indexes) cannot be created invisible.

Action: Remove the option INVISIBLE

ORA-14145: only one UNUSABLE clause may be specified

Cause: UNUSABLE was specified more than once.

Action: Remove all but one of the UNUSABLE clauses and reissue the statement.

ORA-14146: Old CONNECT BY does not support partitioned tables

Cause: The query used the old CONNECT BY clause on a partitioned object.

Action: Disable old CONNECT BY by disabling the _old_connect_by_enabled parameter.

ORA-14147: There is an existing VISIBLE index defined on the same set of columns.

Cause: An attempt was made to define more than one VISIBLE index on the same set of columns. There can be only one VISIBLE index on the same set of columns. Hence ALTER INDEX VISIBLE was not supported on this index.

Action: Make all the indexes defined on the same set of columns as INVISIBLE and then reexecute this DDL.

ORA-14148: DML and DDL operations are not directly allowed on the guard-column.

Cause: An attempt was made to execute a DML or a DDL directly on the guard-column.

Action: This is not supported.

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, LIST, SYSTEM, or Composite Range-Hash/List/Range (R+H/L/R).

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, PARTITIONS, SUBPARTITION, or SUBPARTITIONS keyword

Cause: The keyword PARTITION,PARTITIONS, SUBPARTITION, or SUBPARTITIONS was expected but none were supplied.

Action: Supply the 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 <(sub)partition-description> clause in CREATE TABLE or CREATE INDEX

Cause: A request was made to generate default partition description(s) (possibly via PARTITIONS number-of-partitions) while at the same time specified <(sub)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-14179: An unsupported partitioning method was specified in this context.

Cause: An attempt was made to specify an unsupported partitioning method in this context.

Action: Remove the invalid option.

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 EXTENT may not be specified for composite partitioned object

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a composite partitioned index which is illegal.

Action: Remove the illegal option. If you want to add storage to individual [sub]partitions,the ALLOCATE EXTENT clause may be specified with ALTER TABLE OR INDEX MODIFY [SUB]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-14201: specified subpartition bound is too long

Cause: Length of a linear key representation of a high bound of a table subpartition being added or along which an existing table or index subpartition is being split exceeded the legal limit (4K).

Action: Change the representation of a subpartition high bound to bring its length within legal limit.

ORA-14202: subpartition bound of subpartition "string" is too high

Cause: High bound of the specified subpartition displayed in this message did not collate lower than that of the subsequent subpartition.

Action: Ensure that high bound of every subpartition (except for the last one) collates lower than that of a subsequent subpartition.

ORA-14203: subpartition bound of subpartition "string" is too long

Cause: Length of linear key representation of a high bound of the specified subpartition displayed in this message exceeded the legal limit (4K).

Action: Change the representation of a subpartition high bound to bring its length within legal limit.

ORA-14204: subpartition bound of subpartition number string is too high

Cause: High bound of the specified subpartition displayed in this message did not collate lower than that of the subsequent subpartition.

Action: Ensure that high bound of every subpartition (except for the last one) collates lower than that of a subsequent subpartition.

ORA-14205: subpartition bound of subpartition number string is too long

Cause: Length of linear key representation of a high bound of the specified subpartition displayed in this message exceeded the legal limit (4K).

Action: Change the representation of a subpartition high bound to bring its length within legal limit.

ORA-14206: table is not subpartitioned by List or Range methods

Cause: A subpartition maintenance operation such as ALTER TABLE DROP|SPLIT|MERGE SUBPARTITION can only be performed on List or Range subpartitioned objects

Action: Issue the command only against a List or Range subpartitioned object.

ORA-14207: maximum number of subpartitioning columns is 16

Cause: number of columns in a subpartitioning column list exceeded the legal limit of 16

Action: modify subpartitioning column list so that it consists of at most 16 columns

ORA-14208: lower-bound subpartition must be specified first

Cause: A higher-bound subpartition was specified before the lower-bound subpartition in ALTER TABLE MERGE SUBPARTITIONS statement.

Action: Specify lower-bound subpartition first and then higher-bound subpartition

ORA-14209: subpartitions being merged are not adjacent

Cause: Attempted to merge two subpartitions that are not adjacent to each other.

Action: Specify two subpartitions that are adjacent

ORA-14210: cannot reuse lower-bound subpartition as resulting subpartition

Cause: Attempted to reuse the lower-bound subpartition of the subpartitions being merged.

Action: Specify new resulting subpartition name or reuse the higher-bound subpartition only

ORA-14211: subpartition bound must collate higher than that of the last subpartition

Cause: Subpartition bound specified in ALTER TABLE MODIFY PARTITION ADD SUBPARTITION statement did not collate higher than that of the partition's last subpartition.

Action: Ensure that the subpartition bound of the subpartition to be added collates higher than that of the table partition's last subpartition.

ORA-14212: subpartition cannot be split along the specified high bound

Cause: Attempted to split a subpartition along a bound which either collates higher than that of the subpartition to be split or lower than that of a subpartition immediately preceding the one to be split

Action: Ensure that the bound along which a subpartition is to be split collates lower than that of the subpartition to be split and higher than that of a subpartition immediately preceding the one to be split

ORA-14213: VALUES LESS THAN or AT clause cannot be used for List subpartitioned tables

Cause: VALUES LESS THAN or AT clause was used for List subpartitioned tables

Action: Use VALUES (value list) clause for List subpartitioned tables

ORA-14214: VALUES (value list) cannot be used for Range subpartitioned tables

Cause: VALUES (value list) clause was used for Range subpartitioned tables

Action: Use VALUES LESS THAN or AT clause with Range subpartitioned tables

ORA-14215: subpartition bound list contains too many elements

Cause: Subpartition bound list contained more elements than there are subpartitioning columns

Action: Ensure that the number of elements in subpartition bound list is equal to the number of subpartitioning columns of the table or index

ORA-14216: subpartition bound list contains too few elements

Cause: Subpartition bound list contained fewer elements than there are subpartitioning 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-14217: VALUES (value list) clause expected

Cause: VALUES (value list) clause was not specified for the list subpartition being added

Action: Specify a VALUES (value list) clause

ORA-14218: Invalid operation for object without a segment

Cause: The object (table or index or lob) did not have a segment.

Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command.

ORA-14220: Invalid operation for object without a segment

Cause: Attempted to modify storage or allocate an extent for an object (table or LOB or index) without a segment.

Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command.

ORA-14221: Dictionary managed tablespace cannot be used for this operation

Cause: Attempted to create an index or add a LOB column in a dictionary managed tablespace to a table without a segment.

Action: Specify a locally managed tablespace OR create segments for the table with the ALTER TABLE ALLOCATE EXTENT command.

ORA-14223: Deferred segment creation is not supported for this table

Cause: The SEGMENT CREATION DEFERRED clause was specified in the CREATE TABLE statement.

Action: Remove the SEGMENT CREATION DEFERRED clause.

ORA-14224: Deferred segment creation is not supported for this schema

Cause: The SEGMENT CREATION DEFERRED clause was specified in the CREATE TABLE statement.

Action: Remove the SEGMENT CREATION DEFERRED clause.

ORA-14225: The INDEXING clause is not supported for this table.

Cause: The INDEXING clause was specified for an unsupported table type.

Action: Remove the INDEXING clause from the statement.

ORA-14226: unique index may not be PARTIAL

Cause: INDEXING PARTIAL was specified during creation or modification of a unique index.

Action: Remove the INDEXING PARTIAL clause from the statement.

ORA-14227: INDEXING may be specified only when the underlying table is partitioned

Cause: INDEXING FULL or INDEXING PARTIAL was specified during CREATE INDEX or ALTER INDEX when the base table was not partitioned.

Action: Remove the INDEXING clause from the statement.

ORA-14228: INDEXING may not be specified for this index

Cause: INDEXING FULL or INDEXING PARTIAL was specified during CREATE INDEX or ALTER INDEX for an unsupported index type.

Action: Remove the INDEXING clause from the statement.

ORA-14229: cannot modify the indexing attribute of a composite partition

Cause: An attempt was made to perform ALTER TABLE MODIFY PARTITION INDEXING [ON|OFF] on a composite table partition.

Action: Run ALTER TABLE MODIFY SUBPARTITION INDEXING [ON|OFF] on each subpartition individually.

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, List, Composite Range or Composite List method

Cause: The table was not partitioned by Range, List, Composite Range or Composite List method.

Action: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by Range, List, Composite Range or Composite List methods. Ensure that the table is partitioned appropriately.

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, List, System, or Hash partition

Cause: User attempt to move a partition that is not a Range,List,System, or Hash partition which is illegal

Action: Specify MOVE PARTITION for a Range,List,System, 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,List,System, or Hash partition

Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a Range,List,System, or Hash partition which is illegal

Action: Specify EXCHANGE PARTITION for a Range,List,System, or Hash partition only

ORA-14270: table is not partitioned by Range, System, 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,List,System, or Hash method which is illegal.

Action: Ensure that the table is partitioned by Range,List,System, 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: n/a

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: n/a

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-14300: partitioning key maps to a partition outside maximum permitted number of partitions

Cause: The row inserted had a partitioning key that maps to a partition number greater than 1048575

Action: Ensure that the partitioning key falls within 1048575 partitions or subpartitions.

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 partitioned 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: n/a

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: Search the alert log for the string DBMS_INDEX_UTL. Check the error associated with each of the [sub]partitions that could not be rebuilt and take the appropriate corrective 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-14330: Cannot drop a partition of a global hash-partitioned index

Cause: An attempt was made to drop a partition of a hash-partitioned global index.

Action: Try COALESCE PARTITION instead.

ORA-14331: cannot drop all [sub]partitions of a partitioned table

Cause: An attempt was made to drop all partitions of a partitioned table.

Action: Try DROP TABLE instead.

ORA-14332: duplicate partition or subpartition names specified

Cause: The list of partitions contained duplicate partition or subpartition names.

Action: Ensure that list of partition or subpartition names are distinct.

ORA-14333: subpartition names specified are across multiple partitions

Cause: The specified subpartitions did not belong to the same partition.

Action: Ensure that all subpartitions specified belong to the same partition.

ORA-14334: guard column expected

Cause: There was no guard column or the NOT NULL constraint was not specified for this column.

Action: Add a guard column or NOT NULL constraint for column.

ORA-14335: number of new fragments for adding partitions exceeds the maximum limit

Cause: The total number of new fragments for adding partitions exceeded 125000.

Action: Reissue the statement with a fewer number of new fragments.

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-14411: The DDL cannot be run concurrently with other DDLs

Cause: Another conflicting DDL was already running.

Action: Retry after the conflicting DDL has finished.

ORA-14413: ALTER INDEX UNUSABLE ONLINE cannot be used with certain types of indexes.

Cause: An attempt was made to use the ALTER INDEX UNUSABLE ONLINE statement on an index type (for example, indexed-organized table (IOT), cluster, LOB, domain indexes) that was not allowed.

Action: Using the ALTER INDEX UNUSABLE ONLINE statement on certain types of indexes (for example, indexed-organized table (IOT), cluster, LOB, domain indexes) is illegal. Remove the ONLINE keyword from the statement.

ORA-14414: DROP INDEX ONLINE cannot be used with certain types of indexes.

Cause: An attempt was made to use the DROP INDEX ONLINE statement on an index type (for example, indexed-organized table (IOT), cluster, LOB, domain indexes) that was not allowed.

Action: Using the DROP INDEX ONLINE statement on certain types of indexes (for example, indexed-organized table (IOT), cluster, LOB, domain indexes) is illegal. Remove the ONLINE keyword from the statement.

ORA-14415: index in partially dropped state, submit DROP INDEX

Cause: An attempt was made to access an index in a partially dropped state.

Action: Submit the DROP INDEX index statement to drop the index.

ORA-14416: Online DDL's cannot be used with certain types of tables.

Cause: An attempt was made to use the DROP INDEX ONLINE, ALTER TABLE DROP CONSTRAINT ONLINE, or ALTER TABLE SET UNUSED COLUMN ONLINE statement on an table type (for example, cluster, temporary, index-organized table (IOT), external tables) that was not allowed.

Action: Using online DDL's like DROP INDEX ONLINE, ALTER TABLE DROP CONSTRAINT ONLINE, or ALTER TABLE SET UNUSED COLUMN ONLINE statement on certain types of tables (for example, cluster, temporary, indexed-organized table (IOT), external tables) is illegal. Remove the ONLINE keyword from the statement.

ORA-14417: Online DDL's cannot be used with deferrable constraints.

Cause: An attempt was made to use the DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE statement on constraint states (for example, deferrable, deferred) that was not allowed.

Action: Using DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE statement on constraints that are deferrable or deferred is illegal. Remove the ONLINE keyword from the statement.

ORA-14418: Online DDL's cannot be used with this constraint type.

Cause: An attempt was made to use the DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE statement on a constraint type other than check, primary key, unique, referential, or not null constraint.

Action: Using DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE statement on any other constraint types excluding check, primary key, unique, referential, or not null constraints is illegal. Remove the ONLINE keyword from the DDL.

ORA-14419: DROP CONSTRAINT ONLINE does not support the CASCADE option.

Cause: An attempt was made to use the CASCADE option with DROP CONSTRAINT ONLINE statement.

Action: Using the CASCADE option with the DROP CONSTRAINT ONLINE statement is illegal. Remove the CASCADE keyword from the statement. Drop the child key constraint in a separate DROP CONSTRAINT ONLINE statement on the child table.

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-14462: cannot TRUNCATE temporary table in an autonomous transaction which is already in use by the parent transaction

Cause: An attempt was made to TRUNCATE a temporary table in an autonomous transaction which is already in use by the parent transaction.

Action: Make sure the temporary table is not being used by the parent transaction before trying to TRUNCATE in an autonomous transaction.

ORA-14463: OPERATIONS keyword not specified

Cause: OPERATIONS keyword was not specified in the Compression Clause.

Action: specify OPERATIONS in the Compression Clause.

ORA-14464: Compression Type not specified

Cause: Compression Type was not specified in the Compression Clause.

Action: specify Compression Type in the Compression Clause.

ORA-14465: Fast-Split is not possible on these partitions

Cause: The Fast-Split event was forced in this session.

Action: Disable the event that forces Fast-Split.

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-14530: row mismatches found in table string.string and index string.string

Cause: rows in table and index inconsistent

Action: run complete analyze to determine corrupt rows

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-14554: cannot perform requested operation during database startup

Cause: Requested operation requires the Cost Based Optimizer(CBO) which is not available during database startup. Features like partitioning, IOTs, grouping sets, and flashback cursor require the CBO.

Action: Retry the query after the database is open.

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: n/a

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-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-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, was performed on a non-List subpartitioned object.

Action: Reissue the command against a List subpartitioned 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: n/a

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 subpartitioned 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-14647: cannot MERGE subpartitions in different list composite partitions

Cause: An attempt was made to MERGE subpartitions in different list composite partitions.

Action: Reissue the command after ensuring that the two subpartitions being merged lie in the same composite partition.

ORA-14650: operation not supported for reference-partitioned tables

Cause: Attempted to perform an operation on a reference-partitioned table that was not supported.

Action: Do not perform the unsupported operation.

ORA-14651: reference partitioning constraint is not supported

Cause: The specified partitioning constraint was not supported for reference-partitioned tables. The partitioning constraint must be enabled, validated, and not deferrable. The partitioning constraint must not have ON DELETE SET NULL semantics.

Action: Correct the statement to specify a supported partitioning constraint.

ORA-14652: reference partitioning foreign key is not supported

Cause: The specified partitioning foreign key was not supported for reference-partitioned tables. All columns of the partitioning foreign key must be constrained NOT NULL with enabled, validated, and not deferrable constraints. Furthermore, a virtual column cannot be part of the partitioning foreign key.

Action: Correct the statement to specify a supported partitioning foreign key.

ORA-14653: parent table of a reference-partitioned table must be partitioned

Cause: Attempted to create a reference-partitioned table with a non-partitioned parent table.

Action: Correct the statement and reenter.

ORA-14654: number of partitions of reference-partitioned table must equal that of the parent table

Cause: Attempted to create a reference-partitioned table with a number of partitions which was different from that of the parent table.

Action: Correct the CREATE TABLE statement to specify a correct number of partitions.

ORA-14655: reference partitioning constraint not found

Cause: Partitioning constraint specified in CREATE TABLE ... PARTITION BY REFERENCE was not one of the referential constraints on the table being created.

Action: Ensure that the specified partitioning constraint is one of the referential constraints on the table being created.

ORA-14656: cannot drop the parent of a reference-partitioned table

Cause: Attempted to drop the parent of a reference-partitioned table.

Action: Drop all reference-partitioned child tables before dropping the parent table.

ORA-14657: cannot cascade row migration to reference-partitioned child table

Cause: Update of a parent key may require migration of rows in reference-partitioned child tables, however this is not supported because the parent key was not suitably indexed.

Action: Replace the existing index on the parent key with a unique index that does not contain any columns in addition to the parent key.

ORA-14658: specified dependent table is not affected by this operation

Cause: A table has been specified in the DEPENDENT TABLES clause that is not a reference-partitioned table affected by the operation.

Action: Correct the statement and reenter.

ORA-14659: Partitioning method of the parent table is not supported

Cause: An attempt was made to create a reference-partitioned table with an interval partitioned parent table.

Action: Do not create a reference-partitioned table with an interval partitioned parent table.

ORA-14660: parent table of a reference-partitioned table cannot be index-organized

Cause: Attempted to create a reference-partitioned table with a index-organized parent table.

Action: Correct the statement and reenter.

ORA-14661: row movement must be enabled

Cause: Attempted to disable row movement for a reference-partitioned table, although row movement was enabled for its parent table.

Action: Disable row movement for parent table before disabling row movement for the reference-partitioned table.

ORA-14662: row movement cannot be enabled

Cause: Attempted to enable row movement for a partitioned table, although row movement was disabled for a reference-partitioned child table.

Action: Enable row movement for reference-partitioned child tables before enabling row movement for the parent table.

ORA-14663: reference partitioning parent key is not supported

Cause: Parent key of the reference-partitioned table's partitioning constraint contained virtual columns.

Action: Correct the statement to specify a partitioning constraint with supported parent key and reenter.

ORA-14664: Cannot use PL/SQL expressions in reference partitioning parent key

Cause: Parent key of the reference partitioned table's partitioning constraint contained a virtual column that referenced a PL/SQL expression.

Action: Correct the statement to specify a partitioning constraint with supported parent key and reenter.

ORA-14665: Cannot use expressions involving ROWID data type in reference partitioning parent key

Cause: Parent key of the reference partitioned table's partitioning constraint contained a virtual column that involved the ROWID data type.

Action: Correct the statement to specify a partitioning constraint with supported parent key and reenter.

ORA-14666: Cannot use expressions involving BLOB or CLOB data types in reference partitioning parent key

Cause: Parent key of the reference partitioned table's partitioning constraint contained a virtual column that involved a BLOB or CLOB data type.

Action: Correct the statement to specify a partitioning constraint with supported parent key and reenter.

ORA-14667: Cannot use expressions involving object data types in reference partitioning parent key

Cause: Parent key of the reference partitioned table's partitioning constraint contained a virtual column that involved an object data type (object, REF, nested table, array).

Action: Correct the statement to specify a partitioning constraint with supported parent key and reenter.

ORA-14668: Cannot drop a unique or primary key referenced by the partitioning constraint of a reference-partitioned table.

Cause: An attempt was made to drop a unique or primary key referenced by the partitioning constraint of a reference-partitioned table.

Action: Drop all reference-partitioned child tables before dropping the unique or primary key of the parent table.

ORA-14669: interval partition of reference-partitioned table must correspond to interval partition of the parent table

Cause: An attempt was made to create a reference-partitioned table with an interval partiton that does not pair with an interval partition in the parent table.

Action: Correct the CREATE TABLE statement to specify a correct number of partitions.

ORA-14670: there is no usable index on the reference partitioning parent key

Cause: An attempt was made to run an operation on a reference partitioned table that requires a usable index on the reference partitioning parent key, but no such index exists.

Action: Create a usable index on the reference partitioning parent key, or rebuild the existing unusable index on the reference partitioning parent key.

ORA-14690: value too long for MIN or MAX aggregate

Cause: An attempt was made to use a MIN or MAX aggregate with a value that was too long.

Action: Limit the size of MIN and MAX aggregate inputs to 32763 bytes.

ORA-14691: Extended character types are not allowed in this table.

Cause: An attempt was made to create VARCHAR2 or NVARCHAR2 columns larger than 4000 bytes, or a RAW column larger than 2000 bytes, in a cluster, clustered table or index-organized table.

Action: Correct the statement and reenter.

ORA-14692: STORE AS clause is not allowed for extended character type column

Cause: An attempt was made to use the STORE AS clause to specify storage attributes for an extended character type column.

Action: Correct the statement and reenter.

ORA-14693: The MAX_STRING_SIZE parameter must be EXTENDED.

Cause: An attempt was made to set the MAX_STRING_SIZE parameter to STANDARD in a database that has been created with, or migrated to, the EXTENDED setting.

Action: Set MAX_STRING_SIZE to EXTENDED and retry.

ORA-14694: database must in UPGRADE mode to begin MAX_STRING_SIZE migration

Cause: An attempt was made to update the MAX_STRING_SIZE parameter to EXTENDED when the database was not in UPGRADE mode.

Action: Restart the database in UPGRADE mode, modify the parameter, run the utl32k.sql script in $ORACLE_HOME/rdbms/admin, and restart the database in normal mode.

ORA-14695: MAX_STRING_SIZE migration is incomplete

Cause: An attempt was made to open the database in normal mode before the MAX_STRING_SIZE migration process completed.

Action: Restart the database in UPGRADE mode, run the utl32k.sql script in $ORACLE_HOME/rdbms/admin, and restart the database in normal mode.

ORA-14696: MAX_STRING_SIZE migration is incomplete for pluggable database string

Cause: An attempt was made to open the database in normal mode before the MAX_STRING_SIZE migration process completed for the specified pluggable database.

Action: Restart the database in UPGRADE mode, run the utl32k.sql script in $ORACLE_HOME/rdbms/admin in the specified pluggable database, and restart the database in normal mode.

ORA-14697: This connection does not support bind variables larger than 4000 bytes for SQL statements.

Cause: An attempt was made to use a bind variable larger than 4000 bytes for a SQL statement when the client initially connected to a container with STANDARD MAX_STRING_SIZE, and then within the same session switched to a container with EXTENDED MAX_STRING_SIZE.

Action: Initialize a new connection for the container with EXTENDED MAX_STRING_SIZE and retry.

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-14701: partition-extended name or bind variable must be used for DMLs on tables partitioned by the System method

Cause: User attempted not to use partition-extended syntax for a table partitioned by the System method

Action: Must use of partition-extended syntax in contexts mentioned above.

ORA-14702: The partition number is invalid or out-of-range

Cause: Attempted to use nonnumerical value or the number was out of range of the partitions.

Action: Use a valid partition number.

ORA-14703: The AFTER clause can be used to ADD PARTITION only to a System Partitioned table.

Cause: The table is not partitioned by the System method

Action: Skip the AFTER clause.

ORA-14704: Create table as select disallowed for SYSTEM patitioned tables

Cause: User attempted to create a SYSTEM partitioned table by doing a create table as select.

Action: Do a create table followed by an insert as select into each partition.

ORA-14705: unique or primary keys referenced by enabled foreign keys in table "string"."string"

Cause: An attempt was made to truncate a table with unique or primary keys referenced by enabled foreign keys in another table.

Action: Before performing the TRUNCATE operation on the table, disable the foreign key constraints in other tables. You can see what constraints exist in a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = :1;

ORA-14706: multiple child tables reference constraint "string" in table "string"." string"

Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command found that the specified parent key in the specified table was referenced by partitioning constraints in multiple reference partitioned child tables.

Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option. The CASCADE option is not supported if a parent key in the reference partitioned table hierarchy is referened by multiple partitioning constraints.

ORA-14707: no match found for table "string"." string" for EXCHANGE CASCADE

Cause: There was no table matching the specified table in the ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command.

Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option or ensure that exactly one table matches the specified table.

ORA-14708: multiple matches found for table "string"." string" for EXCHANGE CASCADE

Cause: There were multiple tables matching the specified table in the ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command.

Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option or ensure that exactly one table matches the specified table.

ORA-14709: index mismatch for table "string"."string" in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION command was attempted for the specified table, however, the exchange table did not have equivalent indexes.

Action: Ensure that the indexes for the two tables have indexes which follow this rule: For every nonpartitioned index for the nonpartitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. To be identical, the column position type and size have to be the same.

ORA-14750: Range partitioned table with INTERVAL clause has more than one column

Cause: You attempted to create an interval partitioned table with more than one partitioning column.

Action: Use a single partitioning column.

ORA-14751: Invalid data type for partitioning column of an interval partitioned table

Cause: You attempted to use interval partitioning on a table partitioned on a column of data type other than number or date/time.

Action: Use only number or date/time columns as partitioning columns for interval partitioned tables.

ORA-14752: Interval expression is not a constant of the correct type

Cause: You attempted to use either a nonconstant interval or an interval whose data type does not correspond to the partitioning column

Action: Use only constant expressions for the interval. If the data type of partitioning column is numeric, the interval must be a numeric constant. If the data type is of type date/time, the interval must be a constant of interval type

ORA-14753: Interval cannot be zero

Cause: The interval mapped to zero.

Action: You must use a nonzero interval.

ORA-14754: Interval string is too long

Cause: The interval string was too long

Action: Specify interval using a shorter string

ORA-14755: Invalid partition specification for FOR VALUES clause.

Cause: The [SUB]PARTITION FOR VALUES (...) clause can only take constants. In addition it takes as many arguments as there are partitioning columns and the values must be coercible to the partitioning columns.

Action: Specify a valid FOR VALUES clause.

ORA-14756: Table is not partitioned by Interval method.

Cause: The table was not partitioned by Interval method.

Action: ALTER TABLE SET STORE IN is only valid for Interval partitioned tables. Ensure that the table by Interval.

ORA-14757: Table is already a range partitioned table

Cause: SET INTERVAL () is used to convert an interval partitioned table to a range partitioned table. It is not legal on a range partitioned table

Action: Use SET INTERVAL () only on an interval partitioned table.

ORA-14758: Last partition in the range section cannot be dropped

Cause: An attempt was made to drop the last range partition of an interval partitioned table.

Action: Do not attempt to drop this partition.

ORA-14759: SET INTERVAL is not legal on this table.

Cause: SET INTERVAL clause was specified. ALTER TABLE SET INTERVAL is only legal on a range partitioned table with a single partitioning column. Additionally, this table cannot have a maxvalue partition and cannot be the parent table for any reference partitioned tables.

Action: Use SET INTERVAL only on a valid table.

ORA-14760: ADD PARTITION is not permitted on Interval partitioned objects

Cause: ALTER TABLE ADD PARTITION was attempted on an Interval partitioned object.

Action: Do not perform the operation on an Interval partitioned object. Insert a row to create the new partition.

ORA-14761: MAXVALUE partition cannot be specified for Interval partitioned objects

Cause: An attempt was made to create a partition with a MAXVALUE highbound on an Interval partitioned object.

Action: Do not create a partition with a MAXVALUE highbound.

ORA-14762: Domain index creation on interval partitioned tables is not permitted

Cause: An attempt was made to create a domain index on an interval partitioned table.

Action: Do not create a domain index on an interval partitioned table.

ORA-14763: Unable to resolve FOR VALUES clause to a partition number

Cause: Could not determine the partition corresponding to the FOR VALUES clause.

Action: Remove bind variables and dependencies on session parameters from the values specified in the FOR VALUES clause.

ORA-14764: FOR VALUES clause cannot be specified for only one partition

Cause: An attempt was made to specify the FOR VALUES clause for only one of the two partitions being merged.

Action: Specify a FOR VALUES clause for each of the two partitions being merged or do not specify the FOR VALUES clause for either.

ORA-14765: Cannot create a partition while doing a create index

Cause: An attempt was made to create a partition concurrently with index creation.

Action: Retry the statement after the index build is finished.

ORA-14766: Unable to obtain a stable metadata snapshot

Cause: This operation was not able to obtain a stable snapshot of the interval partitioning metadata.

Action: Retry the statement.

ORA-14767: Cannot specify this interval with existing high bounds

Cause: The interval specified conflicts with the existing high bound for the last partition. The combination might lead to invalid dates for high bounds in the future.

Action: If this is a CREATE TABLE, try specifying a different high bound value for the last partition, or a different interval. If this is an ALTER TABLE SET INTERVAL, please choose either a different interval, or, modify the table to change the high bound for the last partition.

ORA-14769: cannot interval partition nested table or XMLType with object-relational storage

Cause: Interval partition was not supported for nested table and XMLType with object-relational storage.

Action: Use a list or range partition instead.

ORA-14801: Hash composite partitioning is not supported

Cause: An attempt was made to partition a table using a Hash composite method.

Action: Do not partition the table by a Hash composite method.

ORA-14802: Specified operation is not permitted on Hash composite partitioned objects

Cause: An unsupported operation was attempted on a Hash composite partitioned object.

Action: Do not perform the operation on a Hash composite partitioned object.

ORA-14803: partition bound may not be specified for hash subpartitioned tables

Cause: A VALUES LESS THAN or VALUES clause was specified with a subpartition description.

Action: Remove the VALUES LESS THAN or VALUES clause from the subpartition description.

ORA-14804: A partition must be split into two or more partitions

Cause: An ALTER TABLE SPLIT PARTITION contained a description for only one resulting partition.

Action: Specify at least 2 resulting partitions.

ORA-14805: last resulting partition cannot contain bounds

Cause: An ALTER TABLE SPLIT PARTITION contained a description for the last partition which included the bounds.

Action: Do not specify bounds for the last resulting partition.

ORA-14806: merging more than two partitions or subpartitions is only supported for heap tables

Cause: An ALTER TABLE MERGE PARTITIONS or MERGE SUBPARTITIONS with more than two source partitions or subpartitions was issued. Merging more than two partitions or subpartitions is only supported for heap tables.

Action: Specify exactly two partitions or subpartitions to merge.

ORA-14807: merging partitions or subpartitions using name TO name syntax is only supported for range partitioned tables

Cause: An ALTER TABLE MERGE PARTITIONS pname TO pname or an ALTER TABLE MERGE SUBPARTITIONS subpname TO subpname was issued. This is only supported for range partitions or subpartitions.

Action: Specify all the partitions or subpartitions to be merged.

ORA-14808: ONLINE MOVE PARTITION is not supported for this table

Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a table that was either not a heap table or had an object type, domain index or bitmap join index defined on it. This operation is only supported for heap tables.

Action: Do not use the ONLINE keyword.

ORA-14809: ONLINE MOVE PARTITION not supported for this schema

Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a table owned by SYS, SYSTEM, PUBLIC, OUTLN or XDB.

Action: Do not use the ONLINE keyword.

ORA-14810: ONLINE MOVE PARTITION not supported while database is not open or in migrate mode

Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a table while the database was not open or was in migrate mode.

Action: Do not use the ONLINE keyword.

ORA-14811: ONLINE MOVE PARTITION not supported under supplemental logging

Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a table while supplemental logging was enabled.

Action: Do not use the ONLINE keyword.

ORA-14812: DBMS_LOB operations not allowed on partition while it is being moved online

Cause: A DBMS_LOB operation was issued on a LOB while an ALTER TABLE MOVE PARTITION ONLINE was concurrently executing on the partition containing the LOB.

Action: Reissue DBMS_LOB operation after MOVE PARTITION ONLINE has completed.

ORA-14900: The logical transaction ID is no longer valid.

Cause: The logical transaction ID has been purged and the commit failed.

Action: Reconnect and re-run the transaction.

ORA-14901: Commits during replay are not permitted.

Cause: The transaction tried to commit during replay.

Action: Contact Oracle Support Services.

ORA-14902: Instance has not been configured for application continuity.

Cause: The partition of the transaction history table had not been created.

Action: Contact Oracle Support Services.

ORA-14903: Corrupt logical transaction detected.

Cause: The logical transaction was corrupt. The size was incorrect.

Action: Verify your network configuration.

ORA-14904: Corrupt logical transaction ID detected.

Cause: The logical transaction was corrupt. The database ID was incorrect.

Action: Verify your network configuration.

ORA-14905: Serializable transactions cannot be replayed.

Cause: The transaction tried to replay a serializable transaction.

Action: This is not supported.

ORA-14906: Get LTXID outcome operation is not permitted on the current session.

Cause: The transaction tried to execute get LTXID outcome on the current session.

Action: Check the parameters used to invoke get LTXID outcome.

ORA-14907: Cannot execute get LTXID outcome for the transaction of another user.

Cause: The transaction tried to execute get LTXID outcome for a different user session.

Action: Check the parameters used to invoke get LTXID outcome.

ORA-14908: Cannot invoke get LTXID outcome while a transaction is open.

Cause: Get LTXID outcome could not be executed because a transaction was open.

Action: Invoke get LTXID outcome after the transaction has been completed.

ORA-14909: Current session has been blocked by another user with the same user name using GET_LTXID_OUTCOME.

Cause: Could not commit after GET_LTXID_OUTCOME was invoked.

Action: Contact Oracle Support Services.

ORA-14910: Sessions with SYSDBA privilege are not allowed to connect to a service that has commit outcome enabled.

Cause: A session with SYSDBA privilege tried to connect to a service that has commit outcome enabled.

Action: Connect without the SYSDBA privilege.

ORA-14911: XA transactions are not supported by Transaction Guard.

Cause: The transaction tried to commit an XA transaction.

Action: This is not supported.

ORA-14912: Transactions by DRCP clients are not supported by Transaction Guard.

Cause: The Database Resident Connection Pooling (DRCP) client tried to commit a transaction while Transaction Guard was enabled.

Action: This is not supported.

ORA-14950: Force outcome failed. Client transaction is too old.

Cause: The client transaction had been commited or forced earlier.

Action: None

ORA-14951: Force outcome failed. Client transaction is ahead of server logical transaction ID.

Cause: The client transaction had not been seen by the server and could not be forced. This can happen if the server is restored or a flashback operation has been executed.

Action: None

ORA-14952: Force outcome failed. General error occurred.

Cause: The force outcome operation failed. See previous error for the reason.

Action: None

ORA-14953: Invalid partition ID specified.

Cause: The partition IDs of the transaction history table were not consecutive.

Action: Specify the next higer partition ID.

ORA-14954: Invalid tablespace name specified.

Cause: The tablespace did not exist.

Action: Specify an existing tablespace.

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 ASM instance which had already mounted the diskgroup.

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 'string' 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" does not exist in diskgroup "string"

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: path '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-15015: Specified path 'string' conflicts with path 'string'

Cause: The ASM instance previously discovered specified disk with an ASM library using a different path.

Action: Use the discovery string of the ASM library to add the disk.

ORA-15016: inconsistent respecification of path 'string'

Cause: The specified path was provided more than once with different properties.

Action: Do not provide a path more than once. Alternatively, provide consistent properties.

ORA-15017: diskgroup "string" cannot be mounted

Cause: The disk group could not be mounted by the ASM instance either of an IO error or due to other reasons explained in alert log or trace files.

Action: Check for additional errors reported. Correct the error and retry the operation.

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-15022: unable to load an Oracle ASM library

Cause: An Oracle instance attempted to load an Oracle ASM library which could not be discovered.

Action: Check other error messages to determine why Oracle is unable to retrieve the library path from the Oracle ASM instance.

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: ASM discovered two disks claiming to have the same ASM disk number in the same disk group.

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. If the database instance is running as an Operating System (OS) user different from that of the ASM instance, then the permissions on the database oracle binary may be incorrect.

Action: Check the additional error messages, if any. If the database instance is running as an OS user different from that of the ASM instance, use the "srvctl" command to stop and restart the database to fix the permissions.

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 clients with open files in the diskgroup. Diskgroups cannot be dismounted until all open files in the diskgroup are closed.

Action: Stop all clients that are using this diskgroup and retry the ALTER DISKGROUP ... DISMOUNT command. Query the V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list active clients.

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 clients and therefore could not be dropped.

Action: Stop all clients that are using this file and retry the drop command. Query the V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list active clients.

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 (or REPLACE with) 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 and REPLACE, 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' mismatch on 'string' with target disk group [string] [string]

Cause: An attempt was made to mount into a disk group a disk whose recorded allocation unit size, metadata block size, physical sector size, or creation time stamp was inconsistent with the other disk group members.

Action: Check if the system configuration has changed. Verify disk discovery string.

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. Alternatively, for normal or high redundancy diskgroups, use MOUNT FORCE to offline missing disks as part of mounting the diskgroup.

ORA-15041: diskgroup "string" space exhausted

Cause: At least one disk in the diskgroup is out of space.

Action: If all disks are evenly balanced, add more disks to the diskgroup,

ORA-15042: ASM disk "string" is missing from group number "string"

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 alter 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: The RDBMS instance was unable to connect to the required ASM instance when accessing a disk group.

Action: Check the additional error messages. May need to configure correct ASM sid or make sure the RDBMS 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 available, 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" in group "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 or replace a disk that 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 that 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 regular failure groups, discovered only string

Cause: An attempt was made to create either a normal redundancy diskgroup for which fewer than two regular failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three regular failure groups were both specified and discovered, or an external redundancy diskgroup for which only quorum disks 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. Note that a quorum failure group will not be used as a regular failure group. An external redundancy diskgroup requires at least one regular disk.

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 string is not visible on instance number string

Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered.

Action: Check operating system permissions for the device and the storage subsystem configuration on the specified node.

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: If you want to start a database instance, start an ASM instance and mount the required diskgroup. If you want to start an ASM instance, relink the ORACLE binary with ASM_ON or explicitly set INSTANCE_TYPE initialization parameter to ASM.

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 failed to string block string of disk string in disk group string

Cause: A synchronous I/O operation invoked on a disk has failed.

Action: Make sure that all of 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 client

Cause: There was a failure or time out when ASM tried to communicate with a connected RDBMS or Oracle ASM Dynamic Volume Manager (Oracle ADVM) client.

Action: Check the accompanying error messages and alert logs for more information on the reason for the failure. Check system specific logs (/var/log/messages on Linux, Event Log on Windows) for Oracle ADVM messages.

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-15084: ASM disk "string" is offline and cannot be dropped.

Cause: An attempt was made to drop a disk that is offline.

Action: Check the ASM disk name as specified in the command; or, if needed, use the DROP DISK FORCE option.

ORA-15085: disk "string" has inconsistent sector size (expected string, actual string) with disk group "string"

Cause: An attempt to mount a disk group failed because a disk reported inconsistent sector size value.

Action: Use disks with sector size consistent with disk group sector size, or make sure the operating system can accurately report the disk sector size.

ORA-15086: Diskgroup sector size must be specified.

Cause: The _disk_sector_size_override parameter was used but the sector disk value was not specified in the command.

Action: Specify the sector size value, or do not set (or do not set to TRUE) the _disk_sector_size_override parameter.

ORA-15087: disk 'string' is formatted as an ext2/ext3 or OCFS2 file system.

Cause: A signature was found on the specified disk indicating that it is in use by an existing ext2/ext3 or OCFS2 file system.

Action: Adjust discovery string and device permissions to exclude previously formatted disks from discovery.

ORA-15088: diskgroup creation incomplete

Cause: A previous failure during diskgroup creation left the diskgroup in an inconsistent state.

Action: Issue DROP DISKGROUP ... FORCE INCLUDING CONTENTS to clean up the failed creation, then re-create the diskgroup.

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: 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) for this disk group\n

Cause: An ASM file creation or file resize operation exceeded the maximum file size permitted by ASM for this disk group.

Action: Use smaller files. Alternatively, set the disk group attribute compatible.rdbms >= 11.1 if not set already.

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 client (process string)

Cause: A SHUTDOWN command was issued to an ASM instance that had one or more connected clients.

Action: Stop all clients that are using this ASM instance and retry the SHUTDOWN command. 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. One of the active clients has been listed in the error message. Query the V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list all active clients.

ORA-15098: file type not recognized by ASM instance

Cause: An attempt was made by DB instance to create a file for a file type that is not recognized by current version of ASM instance.

Action: Upgrade ASM to higher version that recognizes this file type.

ORA-15099: disk 'string' is larger than maximum size of string MBs

Cause: The specified size of the disk was too big to allow the disk to become part of the diskgroup.

Action: Specify a smaller disk size than the maximum allowed size.

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 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-15118: ASM diskgroup 'string' 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-15119: too many disk groups (string); maximum allowed string

Cause: An attempt was made to mount more than the maximum allowed number of disk groups.

Action: Do not attempt to mount more than the maximum allowed number of disk groups. Check ASM instance parameters.

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 48 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-15134: mirror resilvering not supported for string

Cause: The specified device requires oracle to take mirror resilvering responsiblity. ASM does not resilver logical volume manager (lvm) based mirrors.

Action: Disable lvm-based mirroring or set the parameter _asm_allow_lvm_resilvering to TRUE. One might experience performance degradation when lvm-based resilvering is enabled with ASM.

ORA-15135: The string cluster is not in rolling patch state. The patch level [string] of instance string is not the same as the current cluster patch level [string].

Cause: During startup, this instance found one or more other instances running at a different patch level, and the cluster was not in rolling patch state. Startup of this instance failed.

Action: The patch level of this instance differs from the cluster patch level. If the intention is to patch the cluster using the rolling option, then set the cluster in rolling patch state using the 'crsctl start rollingpatch' command from an active node, and restart Oracle Clusterware on this node. If the intention is to patch the cluster in a non-rolling manner, and the patch has been applied on the local node, then stop all of the active nodes in the cluster that have a patch level that does not match the patch level of the current node. Use the 'crsctl query crs softwarepatch host' command to retrieve the configured patch level of a node. If the intention is to patch the cluster in a non-rolling manner, and the patch has not been applied on the local node, then apply the requisite patch, and restart Oracle Clusterware on this node. Patches applied on a node can be obtained by issuing the the 'crsctl query crs releasepatch' command.

ORA-15136: cluster in rolling patch from patch level [string] to [string]

Cause: The current patch level of the instance was incompatible with the rolling patch operation of the cluster.

Action: The patch level of the new member instance must be one of the two patch levels involved in the rolling patch operation.

ORA-15137: The string cluster is in rolling patch state.

Cause: The cluster was already in the middle of rolling patch.

Action: Rolling patch needs to be stopped before attempting to start again.

ORA-15138: cluster rolling patch incomplete

Cause: The cluster was still performing rolling patch.

Action: Ensure that all of the instances in the cluster are patched before retrying the command.

ORA-15139: patch level of string instances differ in cluster

Cause: Not all of the instances in the cluster had the same set of patches.

Action: Ensure that all of the instances in the cluster have the same patches before retrying the command. Find the configured patch level on a node using the 'crsctl query crs softwarepatch' command.

ORA-15140: rolling patch prevented by string

Cause: One or more instances were blocking the rolling patch.

Action: Terminate or wait until the reported operation is complete before attempting the rolling patch to the cluster.

ORA-15141: The string cluster is not in either rolling upgrade or rolling patch state.

Cause: The ALTER SYSTEM STOP ROLLING MIGRATION or ALTER SYSTEM STOP ROLLING PATCH command was executed when the cluster was not in either the rolling upgrade or rolling patch state.

Action: The system has to be set to rolling upgrade or rolling patch state before attempting to execute the command.

ORA-15142: either MIGRATION or PATCH keyword expected

Cause: The keyword was missing.

Action: Supply the missing keyword.

ORA-15143: either APPLY or ROLLBACK keyword expected

Cause: The keyword was missing.

Action: Supply the missing keyword.

ORA-15144: disk 'string' is about to fail

Cause: An attempt was made to ADD (or REPLACE) a failing disk to a disk group.

Action: Specify a different disk in the command. Note that not even the FORCE option can be used to add the disk to the disk group.

ORA-15145: ASM disk 'string' is online and cannot be replaced.

Cause: The REPLACE DISK operation specified a disk which is online.

Action: Check to confirm that the ASM disk is offline. Online disks can be replaced while maintaining redundancy by issuing ADD and DROP disk commands in a single SQL statement.

ORA-15146: Rolling migration or patching operation failed

Cause: Operation failed due to temporary issue.

Action: Retry the command.

ORA-15147: failed to start the instance

Cause: The instance could not be started during rolling upgrade from ASM instance versions prior to 12.1.0.0.0

Action: Complete the rolling upgrade process and start the instance.

ORA-15148: Too many CRS users are created.

Cause: The number of CRS users has reached its limit of 999. The situation is unexpected.

Action: Check to see why so many CRS users are created.

ORA-15149: another ASM instance found running on the host

Cause: Another ASM instance found on the host. Only one ASM instance is supported on a host.

Action: Shut down the other instance before starting this ASM instance.

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 migration

Cause: The command did not specify 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: The string cluster is in rolling upgrade state.

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: The string cluster is not in rolling upgrade state. The version [string] of instance string is not the same as the current cluster version [string].

Cause: During startup, this instance found one or more other instances running at a different version, and the cluster was not in rolling upgrade state. Startup of this instance failed.

Action: The version of this instance differs from the cluster version. If the intention is to upgrade the cluster using the rolling option, then set the cluster in rolling upgrade state using the 'crsctl start rollingupgrade' command from an active node, and restart Oracle Clusterware on this node. If the intention is to upgrade the cluster in a non-rolling manner, and the local node has already been upgraded, then stop all of the active nodes in the cluster that have an older version than the current node. Use the 'crsctl query crs softwareversion host' command to retrieve the configured version of a node. If the intention is to upgrade the cluster in a non-rolling manner, and the local node has not been upgraded yet, then upgrade the node by running the rootupgrade.sh script.

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 migration is not allowed

Cause: The cluster was not capable of handling ASM rolling migration.

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-15160: rolling migration internal fatal error in module string,string

Cause: Rolling migration experienced a fatal error.

Action: Please contact Oracle support services.

ORA-15161: invalid SYS_CLUSTER_PROPERTIES parameter

Cause: The parameter passed in for SYS_CLUSTER_PROPERTIES is invalid

Action: Pass in the correct parameter, refer to user documentation for a list of allowed parameter values.

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 is not in the rolling downgrade to string

Cause: The cluster was not in the rolling downgrade.

Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING MIGRATION command from another ASM instance and restart this instance.

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-15174: unable to create alias name

Cause: An attempt to create an alias name for an ASM file failed.

Action: Check the alert logs and trace files of the Oracle ASM instance for more information on the failure, as well as checking the accompanying error messages.

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: Check the configuration of ASMLIB or deinstall ASMLIB if not used.

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-15187: Incompatible RDBMS operation [string] pushed to storage

Cause: RDBMS to storage version mismatched with incompatibility operation.

Action: Upgrade RDBMS to match storage version.

ORA-15188: process terminated due to an ASMLIB error

Cause: A process was terminated as a result of an ASMLIB error.

Action: See the alert log for more information. Reconnect to the database or the ASM instance. If the process termination resulted in instance termination, restart the instance.

ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string]

Cause: ASM encountered an invalid disk header.

Action: Contact Oracle Support Services.

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-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 or foreign volume

Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ... ADD DISK command appeared to contain a file from an existing database or a foreign volume. By default, as a safeguard against damaging an existing database or foreign volume, ASM does not allow a disk group to be created using this disk.

Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database or unmounted foreign volume is reused as part of an ASM disk group, specify the FORCE option to the ASM SQL command. See the alert log for more information.

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 COMPATIBLE parameter for the RDBMS instance is less than the value of the compatible.rdbms attribute for the disk group.

Action: Update the COMPATIBLE parameter for RDBMS instance to a version greater than or equal to compatible.rdbms version. The compatible attributes for diskgroups cannot be lowered.

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-15210: conflicting or duplicate PERMISSION options

Cause: The PERMISSION clause contained the USER, GROUP, or OTHER keyword more than once.

Action: Specify each keyword, at most, once.

ORA-15211: conflicting or duplicate OWNERSHIP options

Cause: The OWNERSHIP clause contained either the OWNER or the GROUP keyword more than once.

Action: Specify each keyword, at most, once.

ORA-15212: missing or invalid OWNER or GROUP name

Cause: The command did not specify a valid name for either the OWNER or the GROUP keyword.

Action: Specify a valid name for either the OWNER or the GROUP keyword.

ORA-15213: command operates on only one attribute

Cause: More than one disk group attribute was specified in the ALTER DISKGROUP statement.

Action: Specify only one disk group attribute per ALTER DISKGROUP statement.

ORA-15214: missing or invalid attribute specification

Cause: The command did not specify a valid attribute name or a valid attribute value.

Action: Specify a valid attribute name and value pair.

ORA-15215: missing or invalid user name

Cause: The command did not specify a valid user name.

Action: Specify a valid user name.

ORA-15216: missing or invalid user group name

Cause: The command did not specify a valid user group name.

Action: Specify a valid user group name.

ORA-15217: missing or invalid timeout value after DROP AFTER

Cause: The command did not specify a valid timeout value after the DROP AFTER clause.

Action: Specify a valid timeout value after the DROP AFTER clause.

ORA-15218: timeout value exceeded range

Cause: The OFFLINE timeout value exceeded the range of 0-136 years, inclusive. 136 years are 49674 days, 1192176 hours, and 71530560 minutes.

Action: Specify a timeout value within the range of 0-136 years, inclusive.

ORA-15219: conflicting or duplicate disk region options

Cause: The command contained one or more of the following: - both the HOT and the COLD keywords - both the MIRRORHOT and the MIRRORCOLD keywords - the HOT keyword more than once - the COLD keyword more than once - the MIRRORHOT keyword more than once - the MIRRORCOLD keyword more than once

Action: Specify either the HOT or the COLD keyword and either the MIRRORHOT or the MIRRORCOLD keyword, at most, once.

ORA-15220: invalid file attribute specification

Cause: The keyword UNPROTECTED, MIRROR, HIGH, FINE, or COARSE was specified in a MODIFY FILE clause. These file attributes are immutable once a file is created.

Action: Specify a disk region keyword; for example, HOT, COLD, MIRRORHOT, or MIRRORCOLD.

ORA-15221: ASM operation requires compatible.asm of string or higher

Cause: The ASM operation specified requires a higher disk group attribute value for compatible.asm.

Action: Set the disk group attribute compatible.asm to or above the requested version.

ORA-15222: ASM disk "string" is offline and cannot be renamed.

Cause: An attempt was made to rename a disk that is offline.

Action: Check the ASM disk name as specified in the command.

ORA-15223: conflicting disk operations for string

Cause: An attempt was made to ADD and DROP the specified ASM disk in the same statement.

Action: Revise the statement to specify distinct ASM disks in the ADD disk and DROP disk clauses.

ORA-15224: disk "string" is already provisioned for ASM

Cause: An attempt was made to label a disk that is already provisioned for ASM.

Action: Check the ASM disk name as specified in the command.

ORA-15225: label name 'string' is already in use

Cause: A LABEL SET command specified a label name that was already used by another ASM disk.

Action: Select a different name for the label.

ORA-15226: label name 'string' is not used by ASM

Cause: A LABEL CLEAR command specified a label name that was not used by ASM.

Action: Select a different name for the label.

ORA-15227: could not perform label set/clear operation

Cause: An error occurred while setting/clearing the ASM label.

Action: Look at the underlying error(s) on the error stack. Check other messages in the trace files for more information.

ORA-15230: diskgroup 'string' does not require the FORCE option

Cause: An attempt was made to MOUNT or DROP a disk group with the FORCE option.

Action: MOUNT and DROP diskgroup with the FORCE option are only permitted if the diskgroup cannot be mounted normally.

ORA-15231: advancing diskgroup compatibility would exclude connected clients

Cause: Disk group compatibility could not be advanced because connected clients were at a lower compatibility than the target value.

Action: Make sure all connected clients are at target compatibility level or higher.

ORA-15232: cannot advance diskgroup compatibility due to offline disks

Cause: Disk group compatibilty could not be advanced because some disks are offline.

Action: Retry the command after offline disks are dropped.

ORA-15233: cannot advance diskgroup compatibility due to [string]

Cause: Disk group compatibilty could not be advanced because of errors.

Action: Check the alert log for more information on the reason for the failure.

ORA-15234: target RDBMS compatibility (string) exceeds ASM compatibility (string)

Cause: An attempt was made to advance RDBMS compatibility beyond the disk group's ASM compatibility.

Action: Advance ASM compatibility before advancing RDBMS compatibility.

ORA-15235: diskgroup string mount mode conflicts with existing mount

Cause: The mode specified in the diskgroup mount command conflicted with the mode in which it was mounted on some other instance.

Action: Specify a compatible mode in the diskgroup mount command.

ORA-15236: diskgroup string mounted in restricted mode

Cause: The specified diskgroup was mounted in restricted mode prohibiting client access.

Action: Dismount the diskgroup and remount it in appropriate mode.

ORA-15237: invalid attribute string to CREATE DISKGROUP command

Cause: An invalid attribute was specified with the CREATE DISKGROUP command.

Action: Check the valid attributes for CREATE DISKGROUP command and specify a valid one.

ORA-15238: string is not a valid value for attribute string

Cause: The specified value was not valid for the attribute.

Action: Check the attribute name and value.

ORA-15239: allocation unit size higher than string requires RDBMS compatibility string

Cause: The allocation unit size requested exceeded the limit imposed by the RDBMS compatibility setting.

Action: Use a smaller allocation unit size or specify a higher RDBMS compatibility setting.

ORA-15240: attribute name string is invalid

Cause: The attribute name was not valid or was not recognized.

Action: Check the attribute name.

ORA-15241: attribute string is read only

Cause: The attribute value is read-only and cannot be changed.

Action: None. The attribute value cannot be changed.

ORA-15242: could not set attribute string

Cause: An error occurred while setting the attribute.

Action: Look at the underlying error(s) on the error stack.

ORA-15243: string is not a valid version number

Cause: The given version number was invalid, or not valid in this context.

Action: Verify that the version number is valid and is appropriate for this command. Check for additional errors reported.

ORA-15244: new compatibility setting less than current [string]

Cause: The compatibility setting was invalid. The compatibility setting can only be advanced.

Action: Check the version number.

ORA-15245: ASM disk string is already being brought online

Cause: An attempt was made to bring online a disk that is already being brought online.

Action: Change the ONLINE statement to exclude the disk.

ORA-15246: cannot bring ASM disk string both online and then offline in the same statement

Cause: An attempt was made to bring the specified disk both online and offline in the same statement.

Action: Revise the statement to either bring the disk online or take the disk offline.

ORA-15247: cannot specify both WAIT and NOWAIT options in the same statement

Cause: An attempt was made to specify both WAIT and NOWAIT options in the same statement.

Action: Revise the statement and include at most one option.

ORA-15248: ASM attributes feature not enabled

Cause: The ASM attributes feature was not enabled.

Action: Advance disk group ASM compatibility to version 11.1.0 or newer.

ORA-15249: could not locate ASM attribute string

Cause: The specified attribute could not be accessed.

Action: Check the attribute name and examine underlying error(s) on the error stack.

ORA-15250: insufficient diskgroup space for rebalance completion

Cause: The command attempted to reduce the available diskgroup space below the current space used.

Action: Consult V$ASM_DISK to determine the space requirements for the diskgroup contents, and repeat the command after making the required storage available.

ORA-15251: only restricted mount is allowed in the ASM instance

Cause: The ASM instance was started in restricted mode, and an attempt was made to mount a diskgroup in non-restricted mode.

Action: Start the ASM instance in non-restricted mode and mount the diskgroup again, or mount the diskgroup in restricted mode.

ORA-15252: user name 'string' does not exist in OS user dictionary

Cause: The specified user name was not a valid operating system user.

Action: Specify a valid operating system user.

ORA-15253: user group name 'string' exceeds limit of string characters

Cause: The length of the specified user group name exceeded the maximum limit.

Action: Reduce the length of the user group name to a value within the limit.

ORA-15254: user group 'string' already exists in disk group

Cause: The specified user group name already existed in the disk group.

Action: Specify a different user group name.

ORA-15255: user group 'string' does not exist in disk group 'string'

Cause: The specified user group name did not exist in the disk group.

Action: Specify a valid user group name.

ORA-15256: user 'string' is already a member of user group 'string'

Cause: The specified user was already a member of the specified user group.

Action: Specify either an alternate user or an alternate user group.

ORA-15257: exceeded string number of members per user group

Cause: The maximum number of members per user group was exceeded.

Action: Delete existing members of the user group to create space.

ORA-15258: user group entry number must be between string and string, inclusive

Cause: The specified user group entry number was beyond the acceptable range.

Action: Specify a valid value for the user group entry number.

ORA-15259: user 'string' is not a member of user group 'string'

Cause: The specified user was not a member of the specified user group.

Action: Specify either an alternate user or an alternate user group.

ORA-15260: permission denied on ASM disk group

Cause: An attempt was made to perform an operation on an ASM disk group without the appropriate privileges.

Action: Ask the ASM administrator to perform the operation or grant the required privileges.

ORA-15261: user 'string' already exists in disk group 'string'

Cause: The specified UID already existed in the disk group.

Action: Specify a different UID.

ORA-15262: user 'string' does not exist in disk group 'string'

Cause: The specified UID did not exist in the disk group.

Action: Specify a user with a valid UID.

ORA-15263: user name 'string' exceeds limit of string characters

Cause: The length of the specified user name exceeded the maximum limit.

Action: Reduce the length of the user name to a value within the limit.

ORA-15264: Operating system function returned error string

Cause: An operating system error occurred.

Action: Correct the operating system error and retry the operation.

ORA-15265: user identification number not in range of [string,string]

Cause: The operating system user identification number exceeded the maximum value.

Action: Change the user identification number to a value within the accepted range.

ORA-15266: user identification number 'string' is not allowed

Cause: This user identification number is used internally by ASM.

Action: Please choose a different user identification number.

ORA-15268: internal Oracle file string already exists.

Cause: File was already in existence.

Action: This is an internal error. Contact Oracle Support Services.

ORA-15269: group identification number not in range of [string,string]

Cause: The operating system group identification number exceeded the maximum value.

Action: Change the group identification number to a value within the accepted range.

ORA-15270: disk string is not a quorum disk

Cause: The specified disk was not a quorum disk.

Action: Retry the operation without the quorum attribute for the disk.

ORA-15271: failgroup string is a quorum failgroup

Cause: The specified failgroup was a quorum failgroup.

Action: Retry the operation with the quorum attribute for the failgroup.

ORA-15272: failgroup string is not a quorum failgroup

Cause: The specified failgroup was not a quorum failgroup.

Action: Retry the operation without the quorum attribute for the failgroup.

ORA-15273: Could not create the required number of voting files.

Cause: The required number of voting files could not be created. See accompanying messages for possible causes.

Action: See accompanying messages for possible actions.

ORA-15274: Not enough failgroups (string) to create voting files

Cause: The number of failgroups required for this redundancy were not present in the diskgroup to create voting files.

Action: Retry the operation after creating new failgroup(s).

ORA-15275: Not enough contiguous space (string AUs) in disk string to allocate a voting file

Cause: The specified disk did not have enough space to allocate a voting file on it.

Action: Ensure that there is at least 1 disk with the required space in atleast the required number of failgroups for the diskgroup.

ORA-15276: ASM diskgroup string has cluster voting files

Cause: An attempt was made to drop a diskgroup that contained cluster voting files.

Action: Move the cluster voting files out of the diskgroup and retry the operation.

ORA-15277: disk string is a quorum disk

Cause: The specified disk was a quorum disk.

Action: Retry the operation with the quorum attribute for the disk.

ORA-15278: external redundancy diskgroup requires at least one regular disk

Cause: An attempt was made to create an external redundancy diskgroup with only quorum disks.

Action: Specify atleast one regular disk to create an external redundancy diskgroup.

ORA-15279: user 'string' is currently being deleted

Cause: The specified user was in the process of being deleted and could not be used.

Action: Either abandon this operation or specify a different user.

ORA-15280: user 'string' owns existing files

Cause: An attempt was made to drop a user that still owns existing files.

Action: Specify the CASCADE option to drop the user and all of the owned files.

ORA-15281: not all specified disks were brought ONLINE

Cause: Some of the disks specified either experienced I/O errors while being brought ONLINE, or were simultaneously brought OFFLINE or dropped in another session, or were full.

Action: Query V$ASM_DISK or use ASMCMD LSDSK to determine which disks were not brought ONLINE. Inspect any additional error messages and the alert log to determine the exact cause. If some of the disks failed, either fix the cause of the failures or drop the disks. If some of the disks are full, either free space in the disk group or add new disks to the diskgroup.

ORA-15283: ASM operation requires compatible.rdbms of string or higher

Cause: The ASM operation specified requires a higher disk group attribute value for compatible.rdbms.

Action: Set the disk group attribute compatible.rdbms to or above the requested version.

ORA-15284: ASM terminated ALTER DISKGROUP ONLINE

Cause: None of the disks specified by ALTER DISKGROUP ONLINE could be brought ONLINE.

Action: Inspect additional error messages and the alert log to determine why the specified disks cannot be brought ONLINE.

ORA-15285: disk 'string' violates disk group attribute string

Cause: Including the specifed disk would violate a restriction imposed by the specified disk group attribute.

Action: Retry the operation while omitting the offending disk or change the attribute.

ORA-15286: could not set disk group attribute string due to offline disks

Cause: The specified disk group attribute could not be set because the disk group includes offline disks.

Action: Retry the operation after the offline disks in this disk group are dropped or brought online.

ORA-15287: could not set disk group attribute string due to incompatible disks

Cause: The specified disk group attribute could not be set because the disk group includes disks that conflict with the new value.

Action: Retry the operation after dropping the conflicting disks in this disk group.

ORA-15288: disk(s) require disk group attribute string clause

Cause: Some of the disks specified by the command also require the specified disk group attribute to be stated.

Action: Retry the command including an ATTRIBUTE clause for the required disk group attribute. Alternatively, omit the disks that require setting the disk group attribue. See the alert log for additional information on the disks that require setting the disk group attribute.

ORA-15289: disk string is limited to string MB on instance string

Cause: An ALTER DISKGROUP ADD DISK or RESIZE DISK command specified a disk with a size greater than the specified instance could use.

Action: Check the storage subsystem configuration on the specified node.

ORA-15290: operation not permitted on offline disk string

Cause: An attempt was made to specify an operation that is only permitted on disks that are online. The specified disk was not online.

Action: Online the disk or wait for online to complete before retrying the operation.

ORA-15291: ASM could not add disk "string" to disk group "string"

Cause: An attempt was made to add a disk to a disk group while the distribution of disks in failure groups was too uneven.

Action: Add or drop disks to or from failure groups to balance their distribution in all failure groups and retry the operation.

ORA-15292: Disk name string is being used by another disk

Cause: The specified disk name could not be reused because an 11.1.0.6.0 or earlier database instance had it cached in memory.

Action: Do one of the following - Specify a different name for the disk. - Wait for the rebalance to complete successfully. - Identify the database instance with the problem and shut it down before retrying the command.

ORA-15293: operation disallowed by ASM_POWER_LIMIT

Cause: This operation required data movement in order to complete successfully. However, ASM_POWER_LIMIT was set to zero, thereby preventing this operation.

Action: Repeat the operation after setting ASM_POWER_LIMIT to a non-zero value.

ORA-15294: SYSASM privilege not allowed on database instance

Cause: The SYSASM privilege was not allowed on this database instance; it is allowed only on an ASM instance.

Action: Use either the SYSDBA or the SYSOPER privilege.

ORA-15295: ASM instance software version string less than client version string

Cause: The ASM instance software version was less than the client version.

Action: Upgrade the ASM instance software. Check the alert log for more information on the reason for the failure.

ORA-15298: possible lost disk write detected during crash recovery

Cause: ASM crash recovery read a block who's version was older than expected.

Action: None. End users will not see this error. ASM automatically traps this error and attempts a fallback recovery.

ORA-15299: FINE striping not allowed for the Staleness Registry

Cause: An SQL command attempted to set the striping attribute of the ASM_STALE template to FINE striping.

Action: Do not modify the striping attribute of the ASM_STALE template.

ORA-15300: File string is incompatible with this operation

Cause: The file type was incompatible with the operation.

Action: Use another file of the correct type.

ORA-15301: cannot change string of the open file 'string'

Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on an open file.

Action: Close the file and retry the SQL command.

ORA-15302: active use of files owned by user 'string' precludes its drop

Cause: A DROP USER command specified a user owning files that were in use.

Action: Close all files owned by this user.

ORA-15303: Voting files could not be created in diskgroup string due to small Allocation Unit size

Cause: An attempt was made to create voting files in a diskgroup with a small Allocation Unit size.

Action: Create voting files in a different diskgroup whose Allocation Unit size is at least 1 mega byte.

ORA-15304: operation requires ACCESS_CONTROL.ENABLED attribute to be TRUE

Cause: An attempt was made to run an operation that required the ACCESS_CONTROL.ENABLED attribute to be set to TRUE, but its existing state was FALSE.

Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE and retry the operation.

ORA-15305: cannot operate on ASM internal files

Cause: An attempt was made to operate on Automatic Storage Management (ASM) metadata used to manage the diskgroup.

Action: Check the specified ASM file name.

ORA-15306: ASM password file update failed on at least one node

Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE command failed on at least one node of the Automatic Storage Management (ASM) cluster.

Action: Check the ASM alert logs for more information.

ORA-15307: disk string not discoverable by CSS; diskgroup string has CSS voting files

Cause: An attempt was made to add a disk which cannot be discovered by Cluster Synchronization Services (CSS). CSS has voting files in the disk group and will not be able to use the new disk if CSS cannot discover the disks.

Action: Update the Automatic Storage Management (ASM) disk string in the Grid Plug and Play (GPnP) profile to include the specified disk and retry the operation. Alternatively, migrate the CSS voting files out of the diskgroup and retry the operation

ORA-15308: could not access ASM SPFILE in RDBMS instance

Cause: A relational database management system (RDBMS) instance attempted to access an Automatic Storage Management (ASM) SPFILE.

Action: Connect to an ASM instance and reissue the command. Alternatively, specify an RDBMS SPFILE.

ORA-15309: could not access database SPFILE in ASM instance

Cause: An Automatic Storage Management (ASM) instance attempted to access a relational database management system (RDBMS) SPFILE.

Action: Connect to an RDBMS instance and reissue the command. Alternatively, specify an ASM SPFILE.

ORA-15310: process terminated due to signal

Cause: A process was terminated as a result of a signal in the I/O path.

Action: Reconnect to the database or the ASM instance. If the process termination resulted in instance termination, restart the instance.

ORA-15311: process terminated due to fenced I/O

Cause: A process was terminated because it was fenced from doing any more I/Os.

Action: Reconnect to the database or the ASM instance. If the process termination resulted in instance termination, restart the instance.

ORA-15312: invalid file type

Cause: Automatic Storage Management (ASM) could not determine the type of file.

Action: The file specified is not supported with Automatic Storage Management (ASM). Specify a supported file type for the operation.

ORA-15313: Oracle ASM disk string cannot be resized under string M

Cause: An Oracle ASM disk resize command specified a size that was less than the size required to support the voting file present on the disk.

Action: Increase the size specified for the disk.

ORA-15315: Write errors in disk group string could lead to inconsistent ASM metadata.

Cause: One or more failures occurred while writing ASM metadata to disk.

Action: Repair the hardware problem and remount the disk group. Check the accompanying errors and alert log for the disks which reported the error.

ORA-15316: Previous client instance string has not fully exited.

Cause: One or more processes from a prior instantiation of this client were not fenced.

Action: Make sure all processes belonging to the client instance exited. Check the client alert log and the trace file of the process that terminated the instance.

ORA-15317: user identification number 'string' does not exist in operating system user dictionary

Cause: The specified user identification number did not belong to a valid operating system user.

Action: Specify a valid operating system user.

ORA-15318: disks in disk group string cannot be resized

Cause: Execution of ASM Storage Reclamation Utility script was incomplete on the specified disk group.

Action: Execute ASM Storage Reclamation utility on the disk group to complete the operation.

ORA-15319: ownership assignment of files to user 'string' precludes its drop

Cause: A DROP USER command specified a user currently being assigned as the owner of one or more files with a SET OWNERSHIP command.

Action: Wait for the SET OWNERSHIP command to complete and then retry the DROP USER command

ORA-15320: cannot drop user 'string' that has been assigned as the owner of one or more open files

Cause: A SET OWNERSHIP command assigned this user as the owner of one or more files which were open at the time of assignment, and hence this user cannot be dropped due to possible inconsistencies in file ownerships.

Action: Restart all ASM client instances of the cluster in a rolling manner.

ORA-15321: cannot set attribute with connected clients

Cause: The disk group attribute could not be set because there were connected clients.

Action: Shut down connected clients and retry the command. Query the V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list active clients.

ORA-15322: cannot drop the owner 'string' of user group 'string' in disk group 'string'

Cause: An attempt was made to drop the owner of a user group from the group's member list.

Action: Specify a user group member who is not the owner of the user group.

ORA-15323: ASM password update has failed on local node

Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE command failed on the local node of the Automatic Storage Management (ASM) cluster.

Action: Check the ASM alert logs for more information.

ORA-15324: requested operation is not allowed on the password file string

Cause: An attempt was made to run an operation that is not supported on password files.

Action: Specify a new file name or a file with the correct file type and retry the operation.

ORA-15325: file string is not a valid password file

Cause: An attempt was made to open a file that had a type different from the password file.

Action: Specify correct password file name and retry the operation.

ORA-15326: specified input string is a not an ASM file

Cause: The attributes could not be obtained as the specified input is either a disk group or a directory.

Action: Specify a valid Automatic Storage Management (ASM) file name.

ORA-15327: remote ASM is not enabled

Cause: An operation was requested that requires remote ASM to be enabled.

Action: Enable remote ASM.

ORA-15328: user identification string 'string' exceeds limit of string characters

Cause: The user identification string provided for this operation exceeded the maximum number of characters allowed.

Action: Provide a user identification string of shorter length.

ORA-15329: cluster identification string 'string' exceeds limit of string characters

Cause: The cluster identification string provided for this operation exceeded the maximum number of characters allowed.

Action: Provide a cluster identification string of shorter length.

ORA-15330: ASM user name format requires COMPATIBLE.ASM of string or higher

Cause: The ASM user name format specified requires a higher disk group attribute value for COMPATIBLE.ASM.

Action: Set the disk group attribute COMPATIBLE.ASM to or above the requested version.

ORA-15331: ASM proxy instance ORACLE_SID string does not start with string

Cause: The ASM proxy instance was started with an invalid ORACLE_SID prefix.

Action: Start the ASM proxy instance with an ORACLE_SID that begins with the correct prefix.

ORA-15332: ASM proxy instance cannot connect to an ASM server

Cause: The ASM proxy instance could not find an ASM server to connect to during startup.

Action: Verify that an ASM server instance is running and accessible in the cluster and restart the proxy instance.

ORA-15333: disk is not visible on client instance

Cause: An ALTER DISKGROUP ADD DISK statement specified a disk that could not be discovered by all ASM client instances.

Action: Check the ASM alert logs for more information. Check operating system permissions for the device and the storage subsystem configuration.

ORA-15334: VUBG process terminated with error

Cause: The volume background process terminated with error.

Action: Warm start instance.

ORA-15335: ASM metadata corruption detected in disk group 'string'

Cause: A corruption was detected reading a block. It may be recoverable.

Action: The corruption could be the result of a storage problem, a configuration issue, or a software bug. Check the alert log for the result of the recovery attempt. If unsuccessful, contact Oracle Support Services with the incident information.

ORA-15336: STRIPE_WIDTH cannot be set when STRIPE_COLUMNS equals 1

Cause: An ADD VOLUME command specified a STRIPE_COLUMNS equal to 1 and specified the STRIPE_WIDTH argument.

Action: If striping is required, set STRIPE_COLUMNS to greater than 1. If striping is not required, do not set STRIPE_WIDTH.

ORA-15337: invalid or missing database name

Cause: You did not specify a valid database name for this command.

Action: Specify a valid database name.

ORA-15338: ASM client instance string reconnection refused

Cause: The client was not found as an orphaned client and hence is not a legitimate candidate to reconnect to Oracle ASM.

Action: Shut down and restart the remote client to be considered as a new client in the cluster.

ORA-15339: ASM client instance string has been fenced by ASM

Cause: Oracle ASM has already fenced this client.

Action: Shut down and restart the remote client to be considered as a new client in the cluster.

ORA-15340: unable to create Client Cluster 'string'

Cause: Creation of the Client Cluster failed.

Action: Check the alert logs and trace files of the Oracle ASM instance for more information on the reason for the failure, as well as checking the accompanying error messages.

ORA-15341: unable to delete Client Cluster 'string'

Cause: Deletion of the Client Cluster failed.

Action: Check the alert logs and trace files of the Oracle ASM instance for more information on the reason for the failure, as well as checking the accompanying error messages.

ORA-15343: Feature string ASM is not enabled

Cause: An operation was requested that requires Oracle Flex ASM to be enabled.

Action: Enable Oracle Flex ASM.

ORA-15344: client string not found

Cause: The specified Oracle ASM client was not registered with this instance.

Action: Check the alert logs and trace files of the client for more information on the reason for the failure, as well as the accompanying error messages.

ORA-15345: disconnected client instance(s) detected

Cause: One or more ASM client instances were not connected to an ASM instance.

Action: Check that all of the ASM client instances are connected to an ASM instance and retry the operation.

ORA-15346: process attempting to identify or create ASM file string was aborted

Cause: The client process attempting to identify or create the ASM file terminated or was interrupted.

Action: Correct the cause of the process interruption and retry the operation.

ORA-15347: logical block size string of ASM file 'string' is too small for disk group sector size string

Cause: An attempt was made to create a file on ASM whose logical block size was less than the sector size for the disk group.

Action: Check if the system configuration has changed. Correct the error and retry the operation.

ORA-15348: ASMLIB misconfiguration error [string]

Cause: ASMLIB was found in more than one location.

Action: Check the configuration of ASMLIB and ensure that only one library is configured.

ORA-15349: failed to set or get AFD_DISKSTRING parameter

Cause: The operation failed because Oracle Local Repository (OLR) was not available.

Action: Check that Oracle Clusterware is properly configured.

ORA-15350: invalid SYS_ASMFD_PROPERTIES parameter

Cause: The parameter passed in for SYS_ASMFD_PROPERTIES was invalid.

Action: Pass in the correct parameter. Refer to the product documentation for a list of allowed parameter values.

ORA-15351: I/O request issued to a sparse grid disk failed because the disk was out of space.

Cause: The sparse grid disk was out of space.

Action: Add more space to the disk group by adding more disks or add more space to existing disks by resizing them.

ORA-15352: invalid client name string specified

Cause: The client name passed in was invalid.

Action: Pass in a valid client name. The valid client name is of format instance name:dbunique name:cluster name or instance name:dbunique name

ORA-15353: disk 'string' cannot be added to disk group 'string'

Cause: The disk type did not match the disk group sparse type.

Action: Make sure the disk type matches the disk group sparse type.

ORA-15354: failed to format grid disk "string"

Cause: The grid disk format command failed.

Action: Check the grid disk logs and take corrective actions.

ORA-15357: Can not create file "string" on a sparse disk group

Cause: An attempt was made to create fine-grained striping files on sparse disk groups. Fine-grained striping files cannot be created on sparse disk groups.

Action: Create the file on a regular disk group, or create a coarse-grained striping file on a sparse disk group.

ORA-15358: query for materialized space to sparse grid disk "string" of disk group "string" has failed

Cause: The query for materialized space to the cell server has failed.

Action: Check the ASM and cell alert logs and take corrective actions.

ORA-15359: could not perform label scan operation

Cause: An error occurred while scanning for ASM label.

Action: Look at the underlying errors on the error stack. Check other messages in the trace files for more information.

ORA-15360: could not perform label filter operation

Cause: An error occurred while setting AFD filter status.

Action: Look at the underlying errors on the error stack. Check other messages in the trace files for more information.

ORA-15361: unable to find Client Cluster 'string'

Cause: Looking up of the Client Cluster failed.

Action: Execute the 'asmcmd lscc' command to list all of the configured Client Clusters. If the Client Cluster listed in the message is not present, it might have been forcibly deleted. Refer to the product documentation for more information. If the Client Cluster listed in the message was present, contact Oracle Support Services.

ORA-15362: invalid cluster name 'string' specified

Cause: An invalid cluster name was supplied.

Action: Specify a cluster name which is at least one character but no more than 15 characters in length. The cluster name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.

ORA-15363: invalid version number 'string' specified

Cause: The command did not specify 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.

ORA-15364: Client Cluster version string is incompatible with Storage Server version string

Cause: The specified Client Cluster version was not supported by the Storage Server.

Action: Upgrade or downgrade the Storage Server to a version that is compatible with Client Cluster and retry the operation. Install a Client Cluster using a supported version. Refer to product documentation for a complete list of supported releases.

ORA-15365: Client Cluster 'string' already configured

Cause: The specified Client Cluster was already configured.

Action: Execute the 'asmcmd lscc' command to list all of the configured Client Clusters. Reexecute the command with a Client Cluster name that has not already been configured.

ORA-15366: unable to delete configuration for Client Cluster 'string' because the directory 'string' was not empty

Cause: Deleting the Client Cluster configuration failed because some files were present.

Action: Deinstall the Client Cluster and rerun the command. If the command fails again, execute the 'asmcmd rmcc <client_cluster_name> -f' command to force deletion of the configuration for the Client Cluster.

ORA-15367: Client Cluster 'string' not configured

Cause: The specified Client Cluster was not configured.

Action: Execute the 'asmcmd lscc' command to list all of the configured Client Clusters. Reexecute the command with a Client Cluster name that is configured.

ORA-15368: Oracle Cluster Registry operation failed with error string.\nstring

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-15369: OCI invalid handle string

Cause: An Oracle Call Interface (OCI) call returned the OCI_INVALID_HANDLE return code and did not store the error on the stack.

Action: Contact Oracle Support Services.

ORA-15371: The command is not supported on a Client Cluster.

Cause: An attempt was made to run a command that is not supported on a Client Cluster.

Action: Rerun the command on the Storage Server.

ORA-15400: not running on supported ASM appliance

Cause: An attempt was made to initialize the server code as an appliance when it was not running a supported appliance configuration.

Action: Check the appliance configuration and retry the operation.

ORA-15401: command not supported on ASM appliance 'string'

Cause: An attempt was made to run an operation that is not supported by the specified appliance.

Action: Check the documentation to see which operations are allowed or disallowed for the specified appliance.

ORA-15402: insufficient number of disks to support ASM appliance 'string'

Cause: An attempt was made to do an operation that resulted in insufficient number of disks required for the specified appliance.

Action: Check the appliance configuration and retry the operation after inserting disks in the appropriate slots.

ORA-15403: unable to read an ASM appliance configuration file

Cause: Oracle ASM was unable to read an appliance configuration file.

Action: Check the operating system error messages to determine the identity of the configuration file. Then, fix the configuration file.

ORA-15404: Oracle ASM could not add disk "string" to disk group "string" on appliance string

Cause: There were too many dropping or offline disks in the specified disk group.

Action: Wait for the drop and rebalance operations to complete, or online the offline disks and wait for the online to complete. Then, retry the operation.

ORA-15405: Slot string in Oracle ASM appliance 'string' contains more than one disk

Cause: An attempt was made to add a disk to a slot in the ASM appliance that already had a disk (possibly OFFLINE) associated with it.

Action: Use FORCE to drop the disk that exists in the specified slot. Then, retry the operation.

ORA-15406: ASM disk string is being replaced.

Cause: An attempt was made to either online or replace a disk that was already being replaced, probably by another instance.

Action: Change the ONLINE statement to exclude the disk.

ORA-15407: Disk specification 'string' matches multiple disks.

Cause: More than one disk is discovered matching the specified disk string.

Action: Change the disk string to specify one and only one disk.

ORA-15408: Replacement disk 'string' for 'string' must be at least string MB.

Cause: The replacement disk must be at least of the same size of the old disk.

Action: Use a larger physical disk to replace.

ORA-15409: All disks in disk group string are not of the same type.

Cause: An attempt was made to add disks of a different type to the disk group under appliance mode.

Action: Check if all the disks in the disk group are of the same type. Do not add flash and hard disks to the same disk group.

ORA-15410: Disks in disk group string do not have equal size.

Cause: The disks in the disk group were not of equal size.

Action: Ensure that all disks in the disk group are of equal size. If adding new disks to the disk group, their size must be equal to the size of the existing disks in the disk group. If resizing, all disks in the disk group must be resized to the same size.

ORA-15411: Failure groups in disk group string have different number of disks.

Cause: An attempt was made to enable appliance mode with a different number of disks in each failure group.

Action: Check if all failure groups have an equal number of disks and try again.

ORA-15412: Operation on disk group string is incompatible under appliance mode.

Cause: An attempt was made to do an operation that resulted in dropping all disks in a failure group or creating a new failure group.

Action: Disable appliance mode, perform the operation and reenable appliance mode. WARNING: To reenable appliance mode, ensure the following constraints are met: * There are a sufficient number of disks in each failure group. * All failure groups have an equal number of disks. * There are no offline disks in the disk group. * Every disk in the disk group is of the same type (flash or hard disk). * All disks in the disk group have an equal size.

ORA-15413: Appliance mode is disabled.

Cause: Appliance mode could not be set because it was explicitly disabled.

Action: Enable appliance mode and appliance partnering parameters.

ORA-15414: Appliance mode requires at least string failure groups and either string or string disks in all failure groups.

Cause: Appliance mode could not be enabled because it did not meet the minimum requirements.

Action: Check if there are sufficient failure groups and a sufficient number of disks in each failure group.

ORA-15415: could not retrieve appliance properties for disk group string

Cause: Some of the appliance properties were invalid. This could be due to a cell software downgrade after setting the 'appliance.mode' attribute.

Action: Check the cell software on all of the cells or disable appliance mode.

ORA-15416: ASM disk string in disk group string is offline.

Cause: An offline disk prevented the current ADD or DROP operation.

Action: Drop the offline disk or online the offline disk or disable appliance mode.

ORA-15418: Appliance mode is not supported for compatible.asm string.

Cause: Appliance mode could not be enabled for the current value of the compatible.asm attribute.

Action: Disable appliance mode if it is enabled or advance compatible.asm to a version that supports appliance mode.

ORA-15419: disk group string is not mounted in restricted mode

Cause: The specified disk group was not mounted in restricted mode prohibiting the requested operation.

Action: Dismount the disk group, remount it in restricted mode and retry the operation.

ORA-15420: Operation on disk group string is disabled.

Cause: The current operation could not be completed because the disk group is in the middle of an appliance migration.

Action: Wait for the migration to complete and then retry the command.

ORA-15440: VIO0 process terminated with error

Cause: A volume IO background process terminated with error.

Action: Wait for the process to restart.

ORA-15450: invalid volume name specifier

Cause: The volume name specified was invalid

Action: Specify a valid volume name.

ORA-15451: missing or invalid volume size specifier

Cause: The volume size specified was invalid.

Action: Specify a valid volume size.

ORA-15452: missing or invalid stripe width specifier

Cause: The volume stripe width specified was invalid.

Action: Specify a valid volume stripe width.

ORA-15453: invalid STRIPE_COLUMNS specifier

Cause: An ADD VOLUME command did not specify a valid number of stripe columns.

Action: Specify a valid number of stripe columns.

ORA-15454: ALTER DISKGROUP ALL cannot use single volume names

Cause: An ALTER DISKGROUP ALL command specified a single volume or a list of volumes

Action: Use the ALL keyword when specifying volumes on multiple diskgroups.

ORA-15455: FORCE option cannot be used when specifying ALL volumes

Cause: The FORCE option was used to disable ALL volumes.

Action: Use FORCE option to disable one volume at a time.

ORA-15456: missing or invalid volume usage specifier

Cause: The command did not specify a valid volume usage string.

Action: Specify a valid volume usage string with alphanumeric characters.

ORA-15457: first letter of the volume name is not alphabetic

Cause: A volume name was specified with a nonalphabetic first character.

Action: Set the first character of the volume name to be alphabetic.

ORA-15458: invalid character in volume name

Cause: A volume name was specified with an invalid character.

Action: Use a volume name with only alphanumeric characters.

ORA-15459: STRIPE_WIDTH of string is not a power of two

Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was not a power of two.

Action: Select a STRIPE_WIDTH that is a power of two; for example, 4K, 8K, etc.

ORA-15460: volume name 'string' is already in use

Cause: An ADD VOLUME command specified a volume name that was already used by another volume.

Action: Select a different name for the volume.

ORA-15461: STRIPE_WIDTH of string bytes is less than the minimum of string bytes

Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too small.

Action: Select a larger STRIPE_WIDTH.

ORA-15462: STRIPE_WIDTH of string bytes is greater than the maximum of string bytes

Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too large.

Action: Select a smaller STRIPE_WIDTH.

ORA-15463: volume size of stringK is less than the minimum of stringM

Cause: The volume size specified was too small.

Action: Select a larger volume size.

ORA-15464: STRIPE_COLUMNS of string is greater than the maximum of string

Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was that was too large.

Action: Select a smaller STRIPE_COLUMNS value.

ORA-15465: STRIPE_COLUMNS of string is less than the minimum of string

Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was too small.

Action: Select a larger STRIPE_COLUMNS value.

ORA-15466: volume 'string' in disk group 'string' does not exist

Cause: The command specified a volume name that does not exist.

Action: Ensure a valid volume name is used.

ORA-15467: volume operation is already in progress

Cause: Another command was currently operating on a volume.

Action: Wait a short time before retrying the command.

ORA-15468: volume 'string' in diskgroup 'string' is currently being accessed

Cause: An attempt was made to communicate with the volume driver. The volume was being accessed by another application and, therefore, could not be changed.

Action: Shut down all applications that might be accessing this volume and then retry the command.

ORA-15469: VBG process terminated with error

Cause: A volume background process terminated with error.

Action: Wait for process to restart.

ORA-15470: VDBG process terminated with error

Cause: The volume driver background process terminated with error.

Action: Warm start instance.

ORA-15471: volume redundancy incompatible with disk group redundancy

Cause: An ADD VOLUME command specified a volume redundancy that was incompatible with the redundancy of the disk group.

Action: Specify a valid volume redundancy. An unprotected redundancy volume cannot be added to a normal or high redundancy disk group, and a mirror or high redundancy volume cannot be added to an external redundancy disk group.

ORA-15472: volume library cannot be loaded. Platform may not support volume creation.

Cause: The volume library could not be loaded. Either the platform does not support volume operations, or there is a problem with the library.

Action: Ensure that the platform supports volumes. If the platform does support volumes, check the alert log for library loading failure information.

ORA-15473: access to a volume's storage through an unsupported interface

Cause: An attempt was made to access or modify a volume's storage through an unsupported interface.

Action: Use supported interfaces for access to volume devices.

ORA-15474: volume name is greater than string characters

Cause: An ADD VOLUME command specified a volume name that was too long.

Action: Select a smaller volume name.

ORA-15475: usage string is greater than string characters

Cause: The usage string specified was too long.

Action: Select a smaller usage string.

ORA-15476: ACFS volumes must be resized with the 'acfsutil size' operating system command.

Cause: An attempt was made using SQL to resize an ADVM volume that contains an ACFS file system.

Action: Use the 'acfsutil size' operating system command to resize the volume.

ORA-15477: cannot communicate with the volume driver

Cause: An attempt was made to communicate with the volume driver.

Action: Check that the ASM volume driver is loaded. If so, check the alert log to identify the reason for failure and take necessary action to prevent such failures in the future.

ORA-15478: ACFS process terminated with error

Cause: The ACFS background process terminated with error

Action: Wait for process restart

ORA-15479: ASM diskgroup does not support volumes

Cause: Volumes were not supported. A common example is having disks, such as NFS, in the diskgroup that are not supported by volumes.

Action: Remove unsupported disks in the diskgroup.

ORA-15480: error reported in the ASM volume driver

Cause: An error was reported in the ASM volume driver.

Action: Check the operating system log files to identify the reason for the failure and take necessary action to prevent such failures in the future.

ORA-15481: missing or invalid volume mountpath specifier

Cause: A invalid volume mountpath string was specified.

Action: Specify a valid volume mountpath string with alphanumeric characters.

ORA-15482: failed to create/remove device file for volume string on diskgroup string

Cause: Improper driver installation.

Action: Check the alert log for device file creation failure information. Reload the driver using the supported installation method.

ORA-15483: volume driver version is not compatible with the ASM instance

Cause: The version of the ASM volume driver was not supported by ASM.

Action: Update the volume driver or the ASM instance.

ORA-15484: volume 'string' contains string error(s)

Cause: Errors were returned by the ALTER DISKGROUP CHECK VOLUME command.

Action: See the alert log for details of the errors.

ORA-15485: number of volumes in diskgroup exceeds the maximum of string

Cause: A volume was added on a diskgroup that already contained the maximum number allowed.

Action: Remove volumes on the diskgroup.

ORA-15486: internal error while altering volume

Cause: An internal ASM error occurred while altering a volume.

Action: See the alert log for details of the error.

ORA-15487: cannot shutdown the ASM instance with an open ASM volume

Cause: One or more ASM volumes were found to be open during shutdown.

Action: Close the ASM volume and retry the shutdown.

ORA-15488: volume string is open on instance string

Cause: ASM volume was not closed prior to instance termination on node specified.

Action: Close the ASM volume either via unmount or node restart and retry the operation

ORA-15489: conflicting volume already open on this node

Cause: An ASM volume was not closed prior to instance shutdown on node specified. It is conflicting with the volume that is to be enabled.

Action: Close the ASM volume either via unmount or node restart and retry the operation.

ORA-15490: not all instances could add/drop the volume

Cause: The ASM volume cannot be added/dropped on all instances.

Action: See the alert log for the reason the volume could not be added/droped.

ORA-15491: volume redundancy conflicts with disk region options

Cause: Non-mirrored volumes erroneously contained the MIRRORHOT or MIRRORCOLD keyword.

Action: Remove the MIRRORHOT or MIRRORCOLD keywords from non-mirrored volumes.

ORA-15492: command or option incompatible with ASM volumes

Cause: An attempt was made to use a feature which is not compatible with existing ASM volumes. A common example is adding a disk to the diskgroup that is unsupported by ASM volumes.

Action: Omit the option from the command.

ORA-15493: target ADVM compatibility (string) exceeds ASM compatibility (string)

Cause: An attempt was made to advance ADVM compatibility beyond the disk group's ASM compatibility.

Action: Advance ASM compatibility before advancing ADVM compatibility.

ORA-15494: compatible.advm must be string or higher

Cause: An attempt was made to set the ADVM compatibility to a version that was lower than the minimum supported.

Action: Set ADVM compatibility to at least the minimum supported version.

ORA-15495: ASM operation requires compatible.advm of string or higher

Cause: The ASM operation specified required a higher disk group attribute value for compatible.advm.

Action: Set the disk group attribute compatible.advm to or above the requested version.

ORA-15496: volume size is greater than the maximum of stringT

Cause: The volume size specified was too large.

Action: Select a smaller volume size.

ORA-15497: diskgroup uses a sector size that is incompatible with volumes

Cause: The diskgroup used a sector size that was not 512 bytes.

Action: Create the volume in a diskgroup with a sector size of 512 bytes.

ORA-15498: Volume name 'string' would collide with existing volume(s) 'string string'.

Cause: A volume name was specified that would conflict with existing volume device(s). A volume '<vol_name>-<dg_num>' is the name of the block device. Additionally, a raw device named 'r<vol_name>-<dg_num>' is also created. Since that name already existed, a name collision occurred.

Action: Choose another name for the volume (no leading 'r' is recommended).

ORA-15499: Volume Membership (VMB) process terminated with error

Cause: The volume driver background process terminated with error.

Action: Warm start the instance.

ORA-15501: cannot start workload capture on instance string

Cause: Given instance encountered unexpected errors while trying to start the workload capture.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15502: cannot stop workload capture on instance string

Cause: Given instance encountered unexpected errors while trying to stop the workload capture.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15503: cannot startup instance when procedures in "DBMS_WORKLOAD_CAPTURE" or "DBMS_WORKLOAD_REPLAY" are in the middle of their execution

Cause: The new instance could not be started because the database was executing a procedure in either the DBMS_WORKLOAD_CAPTURE or DBMS_WORKLOAD_REPLAY package.

Action: Start the new instance after such procedures in the given packages have finished execution.

ORA-15504: cannot start workload capture because instance string not present in RESTRICTED SESSION mode

Cause: The NO_RESTART_MODE option in DBMS_WORKLOAD_CAPTURE.START_CAPTURE was FALSE, therefore all the active instances were expected to be in the RESTRICTED SESSION mode.

Action: Start all instances using STARTUP RESTRICT or execute ALTER SYSTEM ENABLE RESTRICTED SESSION on all active instances before issuing DBMS_WORKLOAD_CAPTURE.START_CAPTURE.

ORA-15505: cannot start workload capture because instance string encountered errors while accessing directory "string"

Cause: Given instance could not access the specified CAPTURE directory or the specified CAPTURE directory already had a workload capture in it.

Action: Provide a directory object that is valid, empty and accessible from all the instances in the database cluster.

ORA-15506: cannot prepare instance string for replay

Cause: Given instance encountered unexpected errors while trying to prepare for a workload replay.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15507: cannot start workload replay on instance string

Cause: Given instance encountered unexpected errors while trying to start a workload replay.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15508: cannot cancel workload replay on instance string

Cause: Given instance encountered unexpected errors while trying to cancel a workload replay.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15509: workload replay has been cancelled

Cause: Workload replay was cancelled.

Action: Restart the workload replay.

ORA-15510: cannot perform operation when "STATISTICS_LEVEL" is "BASIC"

Cause: The STATISTICS_LEVEL initialization parameter was set to BASIC.

Action: Change the STATISTICS_LEVEL initialization parameter setting to either TYPICAL or ALL.

ORA-15511: cannot process workload capture because no user sessions were recorded

Cause: No user sessions were recorded in the given workload capture. Processing this capture failed because no user workload was captured.

Action: Capture a workload in which at least one user session connects and performs some operations.

ORA-15512: directory "string" does not contain a valid processed workload capture

Cause: One or more files created by DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE were missing.

Action: Process the workload capture using DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE and then retry the command.

ORA-15513: cannot access the input directory

Cause: Given input directory is either invalid or inaccessible.

Action: Verify that the input directory is valid and accessible and then retry the command.

ORA-15514: cannot find a match for the remote procedure call during replay

Cause: The corresponding PL/SQL program was either dropped or modified.

Action: Verify that the corresponding PL/SQL program is defined the same way during replay as it was defined during workload capture.

ORA-15515: error while replaying remote procedure call: "string.string.string"

Cause: Error encountered during the replay of a remote procedure call.

Action: Correct the cause of the preceding error and restart workload replay.

ORA-15516: parallel preprocessing worker hit error ORA-string

Cause: One of the parallel preprocessing workers died unexpectedly while processing the workload.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15517: cannot start parallel preprocessing worker

Cause: One of the parallel preprocessing workers could not be started.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15518: parallel preprocessing encountered an unexpected error

Cause: An unexpected error occured during parallel preprocessing.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15519: cannot access database link "string" because it is disabled

Cause: For security considerations, access to external databases via database links were disabled during workload replay.

Action: Use advanced parameter for Database Replay to enable database links during workload replay.

ORA-15520: Directory is corrupted. Two WMD files are found at "string" and "string"

Cause: Two WMD files were found in the directory.

Action: Check that the WMD files in capture directory were not modified, moved, duplicated or deleted.

ORA-15521: failed to create file "string" during workload processing

Cause: An attempt was made to create a file during workload processing without the proper file permissions.

Action: Correct the file permissions and try again.

ORA-15522: failed to generate a workload capture subset: "string"

Cause: An attempt to generate a workload capture subset failed. Possible reasons are included in the error message.

Action: Correct the issue and try again.

ORA-15551: workload replay client cannot connect to database server

Cause: The server connection identifier was invalid.

Action: Restart the client with correct server connection identifier.

ORA-15552: workload replay client cannot login to database server

Cause: 1) the replay client used an invalid username or password; 2) the replay user does not have the privilege to switch user; 3) the recorded username does not exist in the replay database.

Action: 1) restart replay client with correct username and password 2) grant user switching prvilege to the replay user 3) verify whether the replay database was restored properly

ORA-15553: workload replay client cannot execute the DBMS_WORKLOAD_REPLAY package

Cause: Workload Replay Client's replay user did not have EXECUTE permission on the DBMS_WORKLOAD_REPLAY package.

Action: Grant execute permission on the DBMS_WORKLOAD_REPLAY package to replay user and restart the Workload Replay Client.

ORA-15554: cannot start workload replay client because the database server is not in PREPARE mode

Cause: The Workload Replay Client could not connect to the database server because the database server was not in the PREPARE mode.

Action: Put the database in PREPARE mode by using DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY, and restart the Workload Replay Client.

ORA-15555: workload replay client encountered unexpected error: "string"

Cause: Workload Replay Client encountered an unexpected error.

Action: Check the Workload Replay Client's log files and the database server alert log to diagnose the problem.

ORA-15556: invalid input specified to the workload replay client; type 'wrc HELP=Y' for help

Cause: Invalid input was specified.

Action: Use the Workload Replay Client's HELP=Y option to know more about valid input options.

ORA-15557: workload replay client cannot access the replay directory or the database version do not match the preprocessing one

Cause: The Workload Replay Client could not access the directory that contained the workload to be replayed, or the workload was preprocessed by a different version of the database.

Action: Restart the workload replay after specifying the correct replay directory, or preprocess it with the correct database.

ORA-15558: replay thread encountered unexpected error

Cause: A single replay thread got disconnected from the server due to an unexpected error.

Action: Check the Workload Replay Client's log files and the database server alert log to diagnose the problem.

ORA-15559: workload replay client cannot open workload capture file

Cause: The Workload Replay Client could not access one or more workload capture files from the replay directory.

Action: Restart the workload replay after copying all the workload capture files to the replay directory.

ORA-15560: workload replay client cannot access the work directory

Cause: The Workload Replay Client could not access the work directory to write log files for debug information.

Action: Restart the Workload Replay Client after specifying the correct work directory.

ORA-15561: workload replay client cannot connect to the remapped connection with conn_id : string

Cause: The specified connection is invalid or the specified host is inaccessible.

Action: Test the specified connection using other methods and redefine the connection remapping, if necessary. Consult the view DBA_WORKLOAD_CONNECTION_MAP to inspect connection remappings.

ORA-15562: workload replay client cannot read the DBA_WORKLOAD_CONNECTION_MAP view

Cause: The DBA_WORKLOAD_CONNECTION_MAP view did not exist or was not accessible.

Action: Re-create the workload capture and replay views. For additional information, see the documentation.

ORA-15563: workload replay client cannot spawn new threads

Cause: The Workload Replay Client does not have enough resource (CPU or memory) to spawn new threads.

Action: Restart the workload replay after allocating more resource (CPU and memory) to the Workload Replay Client or use more hosts as replay clients to drive the workload.

ORA-15564: contents of the replay directory provided to the workload replay client do not match with the replay directory provided to the database server

Cause: The processed workload capture files given to the workload replay client directory did not match the contents of the replay directory given as input to DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY.

Action: Provide the same processed workload capture files to both the database server and all the workload replay clients and restart the replay. If the same workload capture files were processed more than once, provide a copy of the latest processed workload capture files to all the workload replay clients and the database server.

ORA-15566: workload replay client cannot replay user call in the current version

Cause: The workload replay client encountered a user call in the captured workload that was not supported for replay in the current version.

Action: Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details about the call that encountered this error. Refer to the documentation for more details on the types of workload that are not supported in the current version.

ORA-15567: replay user string encountered an error during a sanity check

Cause: The replay user encountered an error when accessing internal objects for Database Replay or switching user.

Action: Set up the replay user appropriately at the replay database. Make sure the replay user can access SYS-owned objects and has BECOME USER privilege.

ORA-15568: login of user string during workload replay failed with ORA-string

Cause: The recorded user did not exist in the replay database or encountered other problems during log in.

Action: Check the returned error number and set up the recorded user appropriately at the replay database.

ORA-15569: timeout encountered during the replay of a recorded user call

Cause: The replay of a recorded user call was terminated since it was significantly slower than the workload capture.

Action: Find the root cause for the performance issue. Or, use DBMS_WORKLOAD_REPLAY API to disable the timeout check if the replay is expected to be slower.

ORA-15590: encountered incomplete workload capture files

Cause: The captured workload contained one or more incomplete recording files. This can happen when the original workload capture's FINISH_CAPTURE command timed out while waiting for all the active sessions to close their workload capture files.

Action: Incomplete capture files will not interfere with the processing and replaying of the captured workload. This is simply a warning message to point out that some database calls might not have been recorded due to FINISH_CAPTURE command timing out. For a list of the incomplete files, check the alert log for lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing.

ORA-15591: encountered corrupt workload capture files

Cause: The captured workload contained one or more corrupt recording files.

Action: For a list of the incomplete files, check the alert log for lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing. The corrupt files will be replayed up to the point of the corruption. Alternatively, it is possible to remove the corrupt files and run DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE again. In this case, no workload from the corrupt files will be replayed.

ORA-15601: Invalid value specified for parameter "string"

Cause: An invalid value was specified for the given parameter.

Action: Correct the value being specified for the parameter.

ORA-15602: Parameter "string" cannot be NULL.

Cause: An attempt was made to call a procedure without a required parameter.

Action: Specify a valid value for this parameter.

ORA-15603: Action cannot be performed when database is in read-only mode.

Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database was open in read-only mode.

Action: Retry when database is open in read/write mode.

ORA-15604: Initialization parameters prevent client from being enabled.

Cause: An attempt was made to enable a client that was disabled for automatic execution by an initialization parameter.

Action: Check the related client parameters and try again.

ORA-15605: "string" is not a Maintenance Window

Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of the MAINTENANCE_WINDOW_GROUP.

Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call.

ORA-15700: SQL limit already reached by prior task execution

Cause: An attempt was made to resume the execution of a task when the prior execution already reached the SQL limit.

Action: Task execution is complete. Examine the report to review Advisor's recommendations.

ORA-15701: All "SQL Tuning Set(s)" with name like "string" and owner like "string" are empty

Cause: An attempt was made to pack one or more SQL Tuning Sets, none * of which contained any statements.

Action: Check the input and try again.

ORA-15702: duplicate values for plan line ID in input collection

Cause: An invalid input was provided containing duplicate values for plan line IDs causing the load of the statement to fail.

Action: Check the input and try again.

ORA-15703: invalid version number "number" for SQL tuning set staging table

Cause: An invalid version number was provided for a staging table used to pack a SQL tuning set.

Action: Check the input and try again.

ORA-15739: invalid name "string" for SQL Performance Analyzer task

Cause: An invalid SQL Performance Analyzer task name was used.

Action: Check the name of the SQL Performance Analyzer task to ensure that it is correct.

ORA-15740: parameter "string" not set for SQL Performance Analyzer task "string"

Cause: Could not find the specified parameter name for the SQL Performance Analyzer task.

Action: Check that the specified parameter exists for the SQL Performance Analyzer task so that the parameter is set.

ORA-15741: no COMPARE_PERFORMANCE execution exists for SQL Performance Analyzer task "string"

Cause: Could not find an execution of type COMPARE_PERFORMANCE for specified SQL Performance Analyzer task.

Action: Ensure that the given SQL Performance Analyzer task has at least one execution of type COMPARE_PERFORMANCE.

ORA-15742: specified execution name "string" is not a valid COMPARE_PERFORMANCE execution for SQL Performance Analyzer task "string".

Cause: The specified execution name was not a valid execution of type COMPARE_PERFORMANCE for the SQL Performance Analyzer task.

Action: Ensure that a valid COMPARE_PERFORMANCE execution name is used for the SQL Performance Analyzer task.

ORA-15743: need to specify the object ID if the tuning task is on a SQL set.

Cause: There could be multiple objects in the SQL tuning task. Specify which one.

Action: Add object ID to the interface.

ORA-15744: The directory name is null.

Cause: The directory name for finding the SQL traces was null.

Action: Create the directory.

ORA-15745: The plan type is not valid.

Cause: The specified plan type was not valid

Action: Check the existing plan types and specify the right one.

ORA-15746: Missing EXECUTE privilege on DBMS_AUTO_SQLTUNE.

Cause: The current user was missing the necessary privileges to execute the API.

Action: Grant the privilege and try again.

ORA-15747: The previous Oracle Data Masking job is unfinished. "string" table is not empty.

Cause: The previously executed Oracle Data masking job was not successfully completed.

Action: Execute Oracle Data masking cleanup.

ORA-16000: database or pluggable database open for read-only access

Cause: The database or pluggable database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error.

Action: In order to modify the database or pluggable database, it must first be shut down and reopened 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 reopened for read-only access.

ORA-16002: database or pluggable database already open for read/write access by another instance

Cause: The database or pluggable 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 reopened for read/write access.

ORA-16003: standby database is restricted to read-only access

Cause: An attempt was made to open a physical standby database in read/write mode.

Action: Reissue the ALTER DATABASE OPEN specifying READ ONLY.

ORA-16004: backup database required recovery

Cause: The database could not be opened for read-only access by this instance because it requires recovery.

Action: Perform the necessary recovery and reopen 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 reopen for read-only access.

ORA-16006: A remote archival request was aborted due to database shutdown.

Cause: When opening or closing a database instance, the database may wait for pending remote archival requests to complete before proceeding with the operation. This error was reported because a shutdown was detected.

Action: This is an informational message so no action is required.

ORA-16007: invalid backup control file checkpoint

Cause: The database could not be opened for read-only access because its control file did not contain a valid control file checkpoint.

Action: Open the database for read/write access to create a valid control file checkpoint. The database can then be opened 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 using the CREATE CONTROLFILE statement. Therefore, a control file checkpoint could not be calculated and the database could not be opened for read-only access.

Action: First, open the database for read/write access. This creates a valid control file checkpoint. Then, reopen the database for read-only access.

ORA-16009: invalid redo transport destination

Cause: The redo transport destination could not accept redo data because it was not a valid redo transport destination type.

Action: Verify that all redo transport destinations are either standby databases or downstream capture databases.

ORA-16011: Remote File Server process is in Error state.

Cause: The Remote File Server (RFS) process at the specified redo transport destination experienced an unrecoverable error and was unable to receive further redo data.

Action: Correct the problem at the redo transport destination.

ORA-16012: database identifier mismatch

Cause: The database identifier of a physical standby database did not match that of the primary database.

Action: Ensure that the database identifier of each physical standby database matches that of the primary database.

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 archival failed because there were no archive log destinations specified, or all destinations are in an error state.

Action: Verify that archive log destinations are specified or take the necessary step to correct any errors that may have occurred.

ORA-16015: Log string sequence# string was not archived.

Cause: An attempt was made to archive the named log to a destination, but the operation did not succeed because the destination was not in ARCHIVELOG mode.

Action: Enable ARCHIVELOG mode at all destinations and retry.

ORA-16016: archived log for thread string sequence# string unavailable

Cause: Redo apply timed out waiting for the requested archived log file.

Action: Verify that the primary database is still archiving redo data to the standby database and reissue the RECOVER STANDBY DATABASE 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...31) 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...31) 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: fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST

Cause: The number of archive log destinations that could be used was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.

Action: Either adjust 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...31) 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...31) 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...31) 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...31) 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...31) 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: An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...31) 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...31). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16030: session specific change to the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter 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...31) 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: Recovery could not be started.

Cause: Database recovery could not be started because the FROM and MANAGED STANDBY DATABASE clauses were both specifed when attempting to start recovery.

Action: Retry the command with either the FROM or MANAGED STANDBY DATABASE clause, but not both.

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

Cause: A mode other than IMMEDIATE followed 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 redo transport destination failed because of an Oracle software version mismatch at the destination.

Action: Verify that a compatible version of Oracle software is running at the redo transport destination.

ORA-16040: Destination archive log file is locked.

Cause: The target archive log file was locked. This indicates that the file is being archived to another Remote File Server (RFS) process.

Action: Ensure that each remote redo transport destination uses a unique network service name.

ORA-16041: Remote File Server fatal error

Cause: The Remote File Server (RFS) process at a redo transport destination encountered a fatal error and was no longer available. Further redo transmission to this destination may not be possible.

Action: Refer to the appropriate RFS trace file located at the redo transport destination for details regarding the error encountered and take corrective action.

ORA-16042: user requested cancel immediate of redo apply

Cause: Redo apply was 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: Redo apply has been canceled.

Cause: Redo apply was 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 attempt was made to modify a redo transport destination attribute using the ALTER SESSION command.

Action: Use the ALTER SYSTEM command to modify the destination attribute.

ORA-16045: circular redo transport destination dependency chain

Cause: An attempt was made to make a redo transport destination dependent on a redo transport destination that was dependent on it.

Action: Ensure that no redo transport destination is dependent on any destination that is dependent on it.

ORA-16046: Redo transport destination failed due to failed dependent destination.

Cause: The redo transport destination was dependent upon another destination, which failed. Therefore, this destination failed.

Action: No action required.

ORA-16047: DGID mismatch between destination setting and target database

Cause: The DB_UNIQUE_NAME specified for the destination did not match the DB_UNIQUE_NAME at the target database.

Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter 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...31) 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: DB_UNIQUE_NAME attribute was not specified. The value of the LOG_ARCHIVE_DEST_n parameter for each remote redo transport destination must contain the DB_UNIQUE_NAME attribute if the LOG_ARCHIVE_CONFIG parameter value contains the DG_CONFIG attribute.

Action: Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME for the destination.

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: Fetch archive log (FAL) server rejected a redo gap fetch request from the client. This may have various causes.

Action: Check the alert log on the primary database. Take the appropriate 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: Use the USING BACKUP CONTROLFILE clause to perform an online log file archival using a backup control file.

ORA-16057: server not in Data Guard configuration

Cause: The primary database or fetch archive log (FAL) server was not found in the Data Guard configuration of the standby database.

Action: Add the database unique name of the primary database or FAL server to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.

ORA-16058: standby database instance is not mounted

Cause: The Remote File Server (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: empty log file or invalid next available block

Cause: An attempt was made to archive an empty or invalid log file.

Action: No action is required.

ORA-16060: Log file is current.

Cause: An attempt was made to archive current log file.

Action: No action is required.

ORA-16061: Log file status has changed.

Cause: 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: standby database not in Data Guard configuration

Cause: The standby database was not found in the Data Guard configuration of the server.

Action: Add the database unique name of the standby database to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.

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: n/a

ORA-16069: activation identifier mismatch

Cause: Redo transport failed because the activation identifier of the primary and physical standby databases did not match. This can happen if the physical standby database was not created from a backup of the primary database.

Action: Create a valid configuration and re-try the failed operation.

ORA-16070: parameter string contains an invalid REGISTER attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31) 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: Archived log file string was not found at dependency destination.

Cause: The specified archived log file was not found at a redo tranpsort destination on which other destinations are dependent.

Action: Verify that all redo transport destinations that are dependent upon another destination or upon which other destinations are dependent are configured correctly.

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: No ARCH processes are active.

Cause: All ARCH processes have stopped.

Action: Restart the instance.

ORA-16075: standby database destination mismatch

Cause: Another instance had access to a standby database destination that this instance did not. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this may be due to a standby database becoming unavailable recently.

Action: Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.

ORA-16076: unknown standby database destination

Cause: A standby database destination was specified that was not accessed by another instance. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this mismatch may be due to a standby database having been restarted recently.

Action: Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.

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 did not have archival enabled.

Action: In order to allow the standby database to access the standby log files, the standby database must be in ARCHIVELOG mode.

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 or the MAX_SERVERS 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: Redo data cannot be written to the standby redo log

Cause: The primary database was in MAXIMUM PROTECTION or MAXIMUM AVAILABILITY mode, but redo data could not be written to the standby redo log at the standby database(s).

Action: Check the Remote File Server (RFS) trace file for specific errors and reconfigure the standby redo log as appropriate.

ORA-16087: Switchover requires standby or current control file.

Cause: An attempt was made to perform a switchover operation using a backup or clone control file.

Action: Convert the backup control file into a current control file prior to attempting a switchover operation. A clone control file cannot be used for a 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 shut down during archival operation.

Cause: The database was shut down while an online log file archival was active.

Action: None required.

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 switch the primary database to the physical standby role.

ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY

Cause: None

Action: Specify this command to switch the physical standby database to the primary role.

ORA-16098: Primary database has been shut down to prevent data loss.

Cause: The primary database was shut down because it was operating in maximum protection mode and no suitable standby databases were available to protect the primary database from data loss.

Action: Diagnose and correct whatever errors exist in the configuration or configure the primary database for maximum availability or maximum performance mode.

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 parameter

Cause: The specified parameter is not valid.

Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package documentation for the correct statement syntax.

ORA-16105: Logical Standby is already running in background

Cause: A Logical Standby apply operation is already running.

Action: None

ORA-16106: loading previously applied transaction information

Cause: Logical Standby coordinator was performing a scan to identify previously applied transactions.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

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: Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, reissue 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: string\% 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: One or more DMLs to an unsupported table were encountered and skipped.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. Optionally, check the DBA_LOGSTDBY_EVENTS view for more information including the impacted table owner and name.

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-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: An error has occurred while performing a switchover.

Action: If you were switching a primary database to the standby role, the conversion was successful, but one or more errors occurred after the conversion completed. See the alert log for more information. You can proceed with switching the target standby database to the primary role, but you must address the errors reported at the old primary database before it can protect the new primary database. If you encountered this error while switching a physical standby database to the primary role, the switchover did not succeed because additional redo must be applied. Verify that redo apply is active and wait until the SWITCHOVER_STATUS column of the V$DATABASE dynamic performance view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying the switchover.

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 reissue 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: stringcontrol file enqueue unavailable

Cause: The control file enqueue is currently unavailable.

Action: No Action is required. We will try to re-fetch it at a later time.

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 did not match the other member types. This problem typically occurs when adding a standby log file member to an online redo log file 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 reissue 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: n/a

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 manual archiving mode

Cause: The database is operating in manual archiving 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 of processes specified is too large

Cause: The number of server processes available for Logical Standby is currently limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048.

Action: Retry with a lower value.

ORA-16181: SGA specified for Logical Standby is too large

Cause: MAX_SGA is larger than 75% of the larger of initialization parameters SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.

Action: Specify the value of MAX_SGA to be less than 75% of the maximum of SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.

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 of processes specified for SQL 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 or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view. If you did not specify MAX_SERVERS, but instead specified PREPARE_SERVERS and APPLY_SERVERS through the dbms_logstdby.apply_set procedure, you will need to decrease either one or both of them.

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 log file 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 Capture

Cause: An attempt was made to register the log file for Capture 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