ORA-12700 to ORA-19400

82 ORA-12700 to ORA-19400

ORA-12700: invalid NLS parameter value (string): Cause: An invalid or unknown NLS configuration parameter was specified.; Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
ORA-12701: CREATE DATABASE character set is not known: Cause: The character set specified when creating the database is unknown.; Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
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: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
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: Use character sets available on the system in the CONVERT function.
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: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.
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: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.
ORA-12707: error while getting create database NLS parameter string: Cause: Internal error; Action: Contact Oracle Support Services.
ORA-12708: error while loading create database NLS parameter string: Cause: Internal error; Action: Contact Oracle Support Services.
ORA-12709: error while loading create database character set: Cause: Internal error; Action: Contact Oracle Support Services.
ORA-12710: CREATE CONTROLFILE character set is not known: Cause: The character set specified when creating the control file is unknown.; Action: Specify a known character set.
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: Create the correct control file for machine and character set.
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 happened between CHAR and NCHAR either implicitly or explicitly, some characters were lost due to no mapping characters in the destination character set.; Action: Ensure that all the characters can be mapped to characters in the 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: Collation key creation failed.: Cause: The character argument of the collation-sensitive operator was too long or had too many decomposable characters to create a collation key in the available buffer space.; Action: Shorten the argument value if it was too long. The maximum allowed argument length depends on the collation, character set, and particular characters comprising the value but is at least 1500 bytes. To avoid the error due to decomposable characters, do not use collations based on UCA 6.2 (with a name starting with UCA0620) nor UCA collations DUCET or ROOT. Use collations based on a higher UCA version. Use ORADUCET in place of DUCET and ORAROOT in place of ROOT.
ORA-12743: An internal error occurred with the arguments string, string, and string.: Cause: An internal error in a globalization support function occurred.; 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-12746: unrecognized collation name "string": Cause: The name of the collation that you specified was not recognized by the Oracle Database, because the name was misspelled, or the collation was user-defined but not installed in the Oracle Home of the database instance, or because the directory specified in the ORA_NLS10 environment setting, either explicitly or defaulting to $ORACLE_HOME/nls/data (%ORACLE_HOME%\nls\data on Microsoft Windows), did not contain valid NLS data files.; Action: Specify a valid collation name or fix your database software configuration.
ORA-12747: unrecognized collation ID (string): Cause: The ID of the collation that you specified was not recognized by the Oracle Database, because it was incorrect, or the collation was user-defined but not installed in the Oracle Home of the database instance, or because the directory specified in the ORA_NLS10 environment setting, either explicitly or defaulting to $ORACLE_HOME/nls/data(%ORACLE_HOME%\nls\data on Microsoft Windows), did not contain valid NLS data files.; Action: Specify a valid collation ID or fix your database software configuration.
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-12757: instance does not currently know of requested service: Cause: The instance received a request to create a session. The request specified a service not currently associated with the instance. If an existing connection to the instance used this service, the service may have relocated to a different instance or may no longer exist.; Action: Ensure that the specified service is valid and reconnect.
ORA-12758: invalid options specified with ALTER SYSTEM KILL or ALTER SYSTEM DISCONNECT: Cause: DRAIN and POST_TRANSACTION were incompatible options.; Action: Use either DRAIN or POST_TRANSACTION or refer to the user manual for more options.
ORA-12774: error entering CDB sandbox string: string: Cause: An attempt to enter the sandbox for a multitenant container database (CDB) failed.; Action: Check the definition of the sandbox for the CDB.
ORA-12775: error entering PDB sandbox string: string: Cause: An attempt to enter the sandbox for a pluggable database (PDB) failed.; Action: Check the definition of the sandbox for the PDB.
ORA-12776: error exiting PDB sandbox string: string: Cause: An attempt to exit the sandbox for a pluggable database (PDB) failed.; Action: Resolve the problem indicated by the particular error.
ORA-12777: A non-continuable error encountered. Check the error stack for additional information [string], [string], [string], [string].: Cause: The error recorded before this error should not be cleared and should be re-signaled to the top-level error handler.; Action: See the previously recorded error. Contact DBA.
ORA-12778: path mismatch for string expected 'string' but found 'string': Cause: The path recorded in the SGA did not match the current value.; Action: Clear the SGA by shutting down the instance and then restart.
ORA-12781: Oracle Scheduler group private handle is not valid.: Cause: The Oracle Scheduler group private handle was not valid.; Action: This is an internal error.
ORA-12782: Oracle Scheduler group thread spawn failed.: Cause: The Oracle Scheduler group could not spawn new threads.; Action: This is an internal error.
ORA-12783: Oracle Scheduler group post for action (string) in (string) failed.: Cause: The Oracle Scheduler group could not post an action to a process.; Action: This is an internal error.
ORA-12784: Oracle Scheduler group post for action (string) failed due to invalid action group.: Cause: The specified action post failed as there is no action group instance.; Action: This is an internal error.
ORA-12785: Oracle Scheduler group start for action group (string) failed during (string) operation.: Cause: The specified action group start failed during the specified operation.; Action: This is an internal error.
ORA-12791: The oradism utility does not have proper permissions.: Cause: The oradism utility was not root owned and did not have proper permissions.; Action: Change oradism to root owned binary with permission 4750.
ORA-12792: Network transfer operation aborted due to TTC error string.: Cause: A Two-Task Common (TTC) error occurred during the network transfer operation.; Action: Check connectivity to the remote database and check the alert log for problems reported by TTC.
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: Cause: The parallel create index fastpath operation event has been set.; Action: set this event only under the supervision Oracle development
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 minus the number of reserved processes, string: Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES minus the number of reserved processes.; Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES minus the number of reserved processes 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-12875: PARALLEL_MAX_SERVERS cannot be set to 0 in CDB system: Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to 0 in the multitenant container database (CDB) system.; Action: Set the PARALLEL_MAX_SERVERS parameter to non-zero value to ensure CDB system performance.
ORA-12894: source should be a sparse file: Cause: The 'setsparseparent' command specified a source file that was not sparse.; Action: Use a sparse file as the source file.
ORA-12895: destination should be sparse: Cause: The 'setsparseparent' command specified a destination that was not backed by a sparse disk group.; Action: Use a destination backed by a sparse disk group.
ORA-12896: child string should be a sparse file: Cause: The 'setsparseparent' command specified a child file that was not sparse.; Action: Use a sparse file as the child file.
ORA-12897: failure to set parent to '%0!s' for a sparse file '%1!s': Cause: The 'setsparseparent' command was not successful.; Action: Examine the accompanying error messages for details.
ORA-12898: failure to set parent for the destination file: Cause: The parent information was not copied to the destination file.; Action: The 'setsparseparent' command can be used to set the parent.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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-12932: sending data for a nonlogged block fetch request failed: Cause: A request from a remote database in the same Oracle Data Guard configuration to send data blocks to avoid or replace soft corrupt blocks due to nonlogged operations failed. This error is accompanied by additional errors that indicate the reason for the failure.; Action: Use any additional errors reported to identify and rectify the the underlying issue.
ORA-12933: failed to connect while serving a nonlogged block fetch request: Cause: A request from a remote database in the same Oracle Data Guard configuration to send data blocks to avoid or replace soft corrupt blocks due to nonlogged operations could not connect to the requesting database. This error is accompanied by additional errors that indicate the reason for the failure.; Action: Use any additional errors reported to identify and rectify the the underlying issue.
ORA-12934: replace of nonlogged blocks in file string failed: Cause: The process performing replacement of nonlogged blocks failed to replace one or more blocks of the file indicated due to unexpected reasons such as a write failure reported by the operating system.; Action: Inspect any additional error messages and check the alert log for any messages related to Nonlogged Block Replacement (NBR).
ORA-12935: operation [string] to database (service 'string') failed (error string): Cause: The process performing replacement of nonlogged blocks received an error when attempting to connect (CONNECT) or make a fetch request (REQUEST) against the database identified by the given service. The database was expected to act as a source of replacement blocks.; Action: Use the reported error to identify the issue or inspect any additional error messages and check the alert log for any messages related to Nonlogged Block Replacement (NBR).
ORA-12936: timeout waiting for data blocks from database (service 'string'): Cause: The process performing replacement of nonlogged blocks waited too long for a request sent to the remote database for a range of blocks to be completed.; Action: Check connectivity to the remote database or check the alert log at the remote database for problems reported by a transport task process (TTnn).
ORA-12937: data blocks received for earlier recovery session (RCVID string): Cause: A database received data blocks requested by a recovery session that has now terminated. This error signals to the sending database that no more transfer requests should be made for the same RCVID.; Action: None required.
ORA-12938: out of memory for the data transfer cache: Cause: A request to use space in the data transfer cache was rejected because there was no free space left in the cache and space could not be freed up.; Action: Ensure that automatic SGA tuning is enabled using either MEMORY_TARGET or SGA_TARGET system parameters or specify a larger size for the system parameter DATA_TRANSFER_CACHE_SIZE.
ORA-12939: The Data Guard environment is incomplete.: Cause: A request to perform Nonlogged Block Replacement (NBR) recovery could not identify any other database in the Data Guard environment from which to request replacement blocks.; Action: Ensure there is a LOG_ARCHIVE_DEST_n parameter configured that identifies the primary or standby database from which requests for replacement blocks can be made.
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-12942: database incarnation at source does not match: Cause: A request to send data blocks to a recovery process failed because the source of the blocks is not on the same database incarnation as the site where the recovery is being performed.; Action: Use standard Oracle Data Guard procedures to synchronize the primary and standby databases. Standby media recovery automatically tries to resolve many of the remaining nonlogged blocks on the standby database. To resolve any remaining nonlogged blocks, use the RMAN RECOVER ... NONLOGGED BLOCK command.
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 automatic segment space management segment under concurrency
ORA-12953: enable space scan optimization for clusters
ORA-12954: The request exceeds the maximum allowed database size of 12 GB.: Cause: The 12 GB space limit of Oracle Database Express Edition was reached.; Action: Delete some files to create space or upgrade the database to the full edition.
ORA-12955: unable to acquire string extents from other instances of the cluster for temporary tablespace string: Cause: The current instance was out of space in the temporary segment belonging to the specified temporary tablespace and was unable to acquire unused extents from other instances of the cluster. This might happen when the system monitor process (SMON) on an instance was busy and was unable to cleanup unused extents from the temporary tablespace.; Action: 1) Check if the system monitor process (SMON) is busy or in a hung state on other instances of the cluster. 2) Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
ORA-12961: cannot open database in read/write mode on a read-only instance: Cause: An attempt was made to open the database on a read-only instance under the following two cases: 1) User explicitly specified read/write option in the SQL command. 2) User forgot to explicitly specify read-only in which case, read/write mode was assumed by default.; Action: Specify the open mode as read-only.
ORA-12962: cannot create database on a read-only instance: Cause: An attempt was made to create a database on a read-only instance.; Action: Create database should only be attempted from a read/write instance.
ORA-12963: A read-only instance cannot be the first instance to open a database.: Cause: A read-only instance was the first instance to try to open a database.; Action: A database must have been opened by at least one read/write instance for a read-only instance to be able to open it.
ORA-12964: All existing read/write instances have closed the database.: Cause: The last read/write instance holding the database open closed it.; Action: There has to be at least one read/write instance holding the database open for a read-only instance to hold it open.
ORA-12965: cannot mount an enabled thread on a read-only instance: Cause: An attempt was made to mount an enabled redo thread obtained as a user specified parameter.; Action: The parameter value should be changed to the thread number of a disabled thread.
ORA-12966: could not find a disabled redo thread to mount: Cause: There were no available disabled redo threads which could be used to mount on the current read-only instance.; Action: None
ORA-12967: read-only instance cannot mount a standby database: Cause: An attempt was made to mount a standby database on a read-only instance.; Action: This action is not allowed.
ORA-12968: delayed log flush should not be enabled in a read-only instance: Cause: The system parameter for ping with no log force feature was set to true.; Action: The parameter should be set to false on a read-only instance.
ORA-12969: invalid alter database option for read-only instance: Cause: An attempt was made to execute a disallowed ALTER DATABASE statement on a read-only instance.; Action: Only OPEN, CLOSE and CREATE TEMPFILE options are allowed for ALTER DATABASE statement on a read-only instance.
ORA-12970: cannot close PDB on all read/write instances while read-only instances exist: Cause: An attempt was made to close a pluggable database (PDB) on the last read/write instance while a read-only instance was holding it open.; Action: A PDB should be closed on all of the read-only instances before it can be closed on the last read/write instance.
ORA-12971: PDB is already online and enabled for ADG recovery.: Cause: An attempt was made to recover an online pluggable database (PDB) on an Active Data Guard (ADG).; Action: None
ORA-12972: cannot start PDB recovery on ADG: Cause: An attempt was made to recover a pluggable database (PDB) on an Active Data Guard (ADG) before the PDB creation was complete on the ADG, or while PDB side recovery was being canceled.; Action: Please try later.
ORA-12973: PDB recovery in progress on ADG instance string: Cause: An attempt was made to recover a pluggable database (PDB) which is being recovered.; Action: None
ORA-12974: PDB recovery not detected on ADG instance string: Cause: An attempt was made to cancel the recovery of a pluggable database (PDB) on an Active Data Guard (ADG) which did not have any recovery session in progress. There is nothing to cancel.; Action: None
ORA-12975: cannot start recovery while pluggable database (PDB) recovery in progress: Cause: An attempt was made to start an Active Data Guard (ADG) recovery while PDB recovery session in progress.; Action: Try again when PDB recovery session is finished.
ORA-12976: incorrect pluggable database name: Cause: A pluggable database name is incorrectly specified. There are two cases that this may occur: - Multiple pluggable database names were specified. - None or wrong pluggable database name was specified.; Action: Specify only one and correct pluggable database name.
ORA-12977: pluggable database (PDB) recovery was not active: Cause: An attempt was made to cancel a pluggable database level managed recovery but it was not active at the time. The pluggable database was online and was part of CDB-level Active Data Guard (ADG) recovery.; Action: None
ORA-12980: checkpoint option not allowed with SET UNUSED: Cause: An attempt was made to specify checkpoint option with SET UNUSED.; Action: Remove checkpoint option.
ORA-12981: cannot drop column from an object type table: Cause: An attempt was made to drop a column from an object type table.; Action: This action is not allowed.
ORA-12982: cannot drop column from a nested table: Cause: An attempt was made to drop a column from a nested table.; Action: This action is not allowed.
ORA-12983: cannot drop all columns in a table: Cause: An attempt was made to drop all columns in a table. A table must have at least one column. If you want to remove the entire table, use the DROP TABLE command instead.; Action: Ensure that 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: This action is not allowed.
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 was either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.; Action: Ensure 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 did not match.; Action: Ensure 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 was invalid.; Action: Ensure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004: The specified buffer size is invalid.: Cause: The specified buffer size for a function was invalid.; Action: This is an internal error. Contact Oracle Support.
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 was either less than 0 or greater than (2^ndim - 1).; Action: Ensure 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 had a bad component or did not match the specified format string.; Action: Ensure 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 was outside the range defined for that dimension.; Action: Ensure 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: Ensure that INTERIOR or BOUNDARY is used to describe the topology of the HHCODE.
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 was not supported for point data.; Action: Ensure 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 was invoked with two geometries where one geometry had an SRID and the other geometry did not have an SRID.; Action: Ensure 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-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-13056: Spatial Reference ID (SRID) does not exist: NULL.: Cause: The operation required a valid SRID but none was specified.; Action: Contact Oracle Support Services.
ORA-13057: Spatial Reference ID (SRID) number does not exist.: Cause: The specified SRID is not known.; Action: Ensure that the specified SRID was valid.
ORA-13058: Spatial Reference ID (SRID) does not exist.: Cause: The SRID for the operation could not be determined.; Action: Ensure that the SRID for the operation is valid.
ORA-13059: invalid WRK_TBLSPC parameter: Cause: An invalid "WRK_TBLSPC" parameter value was specified.; Action: Ensure that the specified "WRK_TBLSPC" exists and is accessible to the current user.
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: Ensure 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 and tg_layer_id values stored in the feature table did not match the values stored in the topology relationship information table (xxx_RELATION$).; Action: Ensure 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: Ensure 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: Ensure that both of 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-13078: cannot commit a distributed transaction involving spatial index: Cause: An attempt was made to commit changes to a spatial table in a distributed transaction, but spatial indexes are not supported in distributed transactions.; Action: Perform all transactional changes to spatial tables (tables containing spatial geometry columns) in a local non-distributed transaction. For more information about this restriction, refer to the Oracle Spatial Data and Graph documentation.
ORA-13079: invalid schema name: Cause: The specified schema name was invalid.; Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the schema name is valid.
ORA-13080: invalid index name: Cause: The specified spatial index name was invalid.; Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the spatial index name is valid.
ORA-13081: invalid index table name: Cause: The specified index table name was invalid.; Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index table name is valid. The index table name typically starts with "MDRT_" prefix.
ORA-13082: invalid index partition name: Cause: The specified index partition name was invalid.; Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index partition name was valid.
ORA-13083: invalid index parameters: Cause: The specified index parameter or parameter combination was invalid.; Action: Check the list of index parameters to ensure that they are correctly specified and valid for the corresponding index operation.
ORA-13084: invalid table type: index organization not supported: Cause: An attempt was made to create the spatial index on an index- organized table (IOT).; Action: Spatial indexes cannot be created on index-organized tables.
ORA-13085: invalid column name: Cause: The specified column name was invalid.; Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index column name is valid. If the column name is a function, ensure the function name is properly spelled and case-sensitive.
ORA-13086: geometry cannot be an optimized geodetic MBR: Cause: An attempt was made to use optimized geodetic minimum bounding rectangles (MBR).; Action: The object tracker cannot be used on objects that are composed of optimized MBRs.
ORA-13087: incorrect number of query columns: Cause: The number of table columns specified for the PointInPolygon() function was incorrect.; Action: Ensure that there are at least two columns specified, and that the first two columns are of the NUMBER type, representing the X and Y coordinates.
ORA-13088: SQL cursor rows have been pre-fetched: Cause: It has been detected that 1 or more rows have been pre-fetched from the specified query cursor.; Action: One or more rows were pre-fetched from the specified query cursor.
ORA-13089: invalid tolerance: Cause: The specified tolerance value was invalid.; Action: The tolerance value must be greater than 0.0.
ORA-13090: geometry must be 2D: Cause: The specified geometry is not two-dimensional.; Action: Ensure the geometry is two-dimensional.
ORA-13091: unable to process query on geodetic MBR: Cause: The operation is not valid using geodetic MBRs.; Action: Ensure the geometry is not using geodetic MBRs.
ORA-13092: unable to process query: Cause: The operation failed.; Action: Contact Oracle Support Services.
ORA-13093: polygon Rings exceeded half the area of earth: Cause: The polygon ring size exceeded half the area of the earth.; Action: Contact Oracle Support Services.
ORA-13094: invalid cursor: Cause: The specified query cursor was invalid.; Action: Contact Oracle Support Services.
ORA-13095: Element number is wrong: Cause: The specified element number is incorrect.; Action: Ensure the specified element number is valid for the geometry.
ORA-13096: Wrong geometry type: Cause: The specified geometry type is incorrect.; Action: Ensure the specified geometry type (GTYPE) is valid for the geometry.
ORA-13097: wrong element type: Cause: The specified element type is incorrect.; Action: Ensure the specified element type (GTYPE) is valid for the geometry.
ORA-13098: more elements than specified: Cause: There are more elements than were specified.; Action: Ensure the specified number of elements is valid for the geometry.
ORA-13099: wrong RING topology: Cause: The geometry ring topology (inner or outer) is wrong.; Action: Contact Oracle Support Services.
ORA-13100: feature does not exist: Cause: The feature does not exist.; Action: Contact Oracle Support Services.
ORA-13101: invalid ptn_type parameter: Cause: An incorrect ptn_type parameter was specified.; Action: Ensure the ptn_type parameter value is correct.
ORA-13102: invalid ptn_capacity parameter: Cause: An incorrect ptn_capacity parameter was specified.; Action: Ensure the ptn_capacity parameter value is correct.
ORA-13103: invalid numdim parameter: Cause: An incorrect numdim parameter was specified.; Action: Ensure the numdim parameter value is correct.
ORA-13104: null values not allowed in input data: Cause: Null values cannot be specified in the supplied input data.; Action: Ensure that all null-values have been removed from the data.
ORA-13105: invalid Parameters for Partition_Table: Cause: One or more parameters for the Partition_Table() function are invalid.; Action: Ensure that the identified parameters are correctly specified.
ORA-13106: invalid MASK parameter: Cause: The specified MASK parameter was invalid.; Action: Ensure that the MASK parameter values are correctly specified.
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 did not exist.; Action: Check the spatial data dictionary to ensure 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: Ensure that 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 was not greater than or equal to zero.; Action: Ensure 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 contained rows.; Action: Ensure 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 did 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: Ensure 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 was supplied for a layer in the USER_SDO_GEOM_METADATA view.; Action: Check the tolerance specified to ensure that 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: Ensure 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-13238: spatial journal cache enabled; query requires transaction commit: Cause: The spatial transaction journal cache was enabled. When enabled, spatial functions that require use of the spatial index could not be used when uncommitted transaction data existed.; Action: Commit or roll back the current transaction, or flush the spatial transaction journal cache using the PL/SQL "SDO_UTIL.INVALIDATE_GTT_CACHE" procedure.
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: Ensure 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 on a column that was not of type SDO_GEOMETRY.; Action: A spatial index can only be created on a column of type SDO_GEOMETRY. Ensure that 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 the ARC_TOLERANCE specification and ensure that 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: Ensure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.
ORA-13294: cannot transform geometry containing circular arcs: Cause: An attempt was made to transform a 3-point representation of a circular arc without distortion.; Action: Ensure that 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: Referencing system (LRS) concatenation involving LRS polygons is not supported.; Action: Check the geometry and element types to ensure that the concatenate operation is not called with a polygon type.
ORA-13338: failure in reversing LRS polygon/collection geometry: Cause: Reversing a referencing system (LRS) polygon or collection geometry produced an invalid geometry.; Action: Check the geometry type to ensure that 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 had a geometry with a different dimensions than the dimensions specified for the layer.; Action: Ensure 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 had a geometry with a different SRID than the SRID specified for the layer.; Action: Ensure 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 were not used consistently.; Action: Ensure 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 had orientation specified while some other element had no orientation specified (4-digit etype).; Action: Ensure that all of 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: Ensure that 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: Ensure that 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: invalid %0!s parameter%1!s: Cause: The operation failed because the input parameter was invalid.; Action: Correct the parameter and try again.
ORA-13394: Parameter string is NULL or empty.: Cause: The operation failed because the input parameter was NULL or was an empty array.; Action: Correct the parameter and try again.
ORA-13395: Parameter %0!s has NULL or empty element at index %1!s.: Cause: The operation failed because one of the array elements was NULL or was an empty string.; Action: Correct the parameter and try again.
ORA-13396: Parameter %0!s has invalid element at index %1!s.: Cause: The operation failed because one of the array elements was invalid.; Action: Correct the parameter and try again.
ORA-13397: inconsistent dimension sizes in the input GeoRaster objects: Cause: The input GeoRaster objects had different spatial or band dimension sizes.; Action: Check the dimension sizes of the input GeoRaster objects and ensure that they have the same dimension size.
ORA-13398: invalid expression parameter: string: Cause: The expression parameter did not conform to the raster algebra expression definition.; Action: Check the raster algebra language definition in the documentation and ensure that the expression parameter conforms to the definition.
ORA-13399: invalid condition parameter: string: Cause: The condition parameter did not conform to the raster algebra boolean expression definition.; Action: Check the raster algebra language definition in the documentation and ensure that the condition parameter conforms to the definition.
ORA-13400: invalid elevationParam parameter: string: Cause: The elevationParam parameter had an invalid specification.; Action: Check the documentation and ensure that the elevationParam parameter is correct.
ORA-13401: GeoRaster object (RDT=%0!s, RID=%1!s) already exists.: Cause: There were duplicate entries of RASTER_DATA_TABLE (RDT) and RASTER_ID (RID) columns in the USER_SDO_GEOR_SYSDATA view, or the operation was inserting a duplicate entry of (RASTER_DATA_TABLE, RASTER_ID) into USER_SDO_GEOR_SYSDATA view.; Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID pairs are unique in the USER_SDO_GEOR_SYSDATA view, or insert a GeoRaster object with a unique (RASTER_DATA_TABLE, RASTER_ID) value.
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 the rasterType formats supported by GeoRaster.
ORA-13403: invalid rasterDataTable specification: string: Cause: The raster data table (RDT) name specified for a GeoRaster object was invalid because of one of the following reasons: - RDT name was not a simple SQL name or was longer than 128 bytes. - RDT name was not unique among RDT names in the database. - RDT did not exist or was not visible from the current schema. - RDT was not defined in the same schema as the GeoRaster object table. - RDT was not an object table of SDO_RASTER type or a relational table with the same columns as the attributes of the SDO_RASTER type.; Action: Check the rasterDataTable specification and ensure that all relevant raster data table requirements are met.
ORA-13404: invalid ultCoord parameter specification: Cause: The specified array for the ultCoord parameter had the wrong length or had an invalid value.; Action: Check the documentation and ensure that the ultCoord parameter is correct.
ORA-13405: invalid string parameter: Cause: The input array for the dimension size had NULL or invalid value, or the array length was not equal to the number of dimensions of the GeoRaster object.; Action: Check the documentation and ensure that the parameter is correct.
ORA-13406: NULL or invalid GeoRaster object for output: Cause: The GeoRaster object for output was NULL or had NULL rasterDataTable or rasterID attribute.; Action: Ensure that the GeoRaster object for output has been initialized properly.
ORA-13407: invalid storage parameter: string: Cause: The storage parameter contained an invalid keyword or value.; Action: Check the documentation and ensure that the storage parameter is correct.
ORA-13408: invalid blockSize storage parameter: Cause: The blockSize storage parameter had the wrong length or contained an invalid value.; Action: Check the documentation and ensure that the blockSize storage parameter is correct.
ORA-13409: invalid pyramidLevel parameter: Cause: The specified pyramidLevel parameter value was either less than 0 or greater than the maximum pyramid level of the corresponding GeoRaster object.; Action: Ensure that the pyramidLevel parameter specifies a valid pyramid level value for the GeoRaster object.
ORA-13410: invalid layerNumbers or bandNumbers: string: Cause: The layerNumbers or bandNumbers parameter was in the wrong format or had the wrong values.; Action: Check the documentation and ensure that the layerNumbers or bandNumbers parameter is valid.
ORA-13411: The specified string is outside the source GeoRaster object.: Cause: The minimal bounding rectangle (MBR) of the specified area had no intersection with the MBR of the source GeoRaster object.; Action: Check the coordinates of the specified area to ensure that it overlaps with the source GeoRaster object.
ORA-13412: invalid scale parameter: string: Cause: The scale parameter contained an invalid specification.; Action: Check the documentation and ensure that the scale parameter is correct.
ORA-13413: invalid resampling parameter: Cause: The specified resampling method or the NODATA option was invalid.; Action: Check the documentation for the correct resampling parameter options.
ORA-13414: invalid pyramid parameter: string: Cause: The specified pyramid parameter was invalid.; Action: Check the documentation and ensure that the pyramid parameter is correct.
ORA-13415: invalid or out of scope point specificationstring: Cause: The point position specified by the ptGeom or <rowNumber, colNumber> parameter combination was invalid or out of scope.; Action: Ensure that the parameters 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 single-point geometry parameter: Cause: The geometry parameter did not specify a valid single-point geometry.; Action: Specify a valid single-point geometry.
ORA-13417: invalid layerNumber or bandNumber parameter: Cause: The layerNumber or the bandNumber parameter was either less than 0 or greater than the number of bands in the GeoRaster object.; Action: Specify a valid layerNumber or bandNumber parameter.
ORA-13418: cannot set GeoRaster metadatastring: Cause: A parameter for set metadata operations had an invalid value.; Action: Check the documentation for information about the parameters.
ORA-13419: cannot perform mosaic or append operation: string: Cause: An attempt to perform a mosaic or append operation failed due to one of the following reasons: - The input GeoRaster object had no spatial extent. - The cropArea or outResolutions was out of scope. - The mosaicParam parameter had invalid keyword or value. - The table and column specification did not match or was invalid.; Action: Check the error message for details.
ORA-13420: The SRID of the geometry parameter is not NULL.: Cause: The input geometry was not in the GeoRaster cell space, which required a NULL Spatial Reference ID (SRID) value.; Action: Ensure that the geometry parameter has a NULL SRID.
ORA-13421: invalid cell value: string: Cause: The cell value was out of range.; Action: Ensure that the cell value is in the range as designated by the cellDepth definition of the specified GeoRaster object.
ORA-13422: invalid cursor string: Cause: The GeoRaster cursor did not return GeoRaster object, or was empty, or returned a NULL GeoRaster object.; Action: Ensure that the GeoRaster cursor returns non-NULL GeoRaster objects.
ORA-13423: invalid cell coordinate parameter: Cause: The cell coordinate array parameter had the wrong length or had NULL ordinate elements.; Action: Ensure that the cell coordinate parameter is valid.
ORA-13424: The GeoRaster object is not spatially referenced.: Cause: The GeoRaster object was not spatially referenced, or the model space Spatial Reference ID (SRID) was NULL.; Action: Check the GeoRaster object metadata to ensure it is spatially referenced and its model space SRID is set. Refer to the documentation for more details on Georeferencing.
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: Ensure that the parameter that specifies the background filling value is valid. The size of the array must equal either 1 (the value is for all bands) or the exact band dimension size in the output GeoRaster object. The element values must be valid cell values as determined by the cell depth.
ORA-13426: invalid window or cropArea parameter: Cause: The specified cell space coordinate array length was not 4, or had NULL or an invalid element.; Action: Specify the parameter using the cell space coordinate of the two corners of the window. Check the documentation for details.
ORA-13427: invalid bitmap mask: Cause: The bitmap mask was invalid due to one of the following reasons: - The bitmap mask cell depth was not 1-bit. - The bitmap mask had more than one band. - The bitmap mask was a blank GeoRaster object.; Action: Check the documentation and ensure that the bitmap mask is valid.
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 input or output GeoRaster object has NULL attribute.: Cause: The metadata, rasterType, or rasterID attribute of the GeoRaster object was NULL.; Action: Ensure that the GeoRaster object has non-NULL attributes.
ORA-13431: GeoRaster metadata error: invalid rasterType: Cause: The rasterType metadata of the GeoRaster object was inconsistent with the rasterType attribute of the GeoRaster object.; Action: Ensure that the rasterType metadata and the rasterType attribute of the GeoRaster object have the same value.
ORA-13432: GeoRaster metadata error: 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 in the GeoRaster metadata.; Action: Call SDO_GEOR.setBlankCellValue to add blankCellValue to the metadata whenever the isBlank element value is TRUE. Also, ensure 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 error: invalid defaultRed, defaultGreen or defaultBlue value: 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 error: invalid cellRepresentation: Cause: The cellRepresentation type was not supported.; Action: Check the documentation for supported cellRepresentation types.
ORA-13435: GeoRaster metadata error: invalid defaultPyramidLevel: Cause: The defaultPyramidLevel in the GeoRaster object metadata was either less than 0 or greater than the maximum pyramid level.; Action: Use SDO_GEOR.setDefaultPyramidLevel function to set the proper default pyramid level.
ORA-13436: GeoRaster metadata error: invalid dimensionSize: Cause: The dimensionSize in the GeoRaster object metadata was missing or had more values than required.; Action: Ensure that the dimensionSize is set in the GeoRaster metadata and has a value for each dimension.
ORA-13437: GeoRaster metadata error: invalid blocking metadata: Cause: One of the elements in the blocking metadata was missing or had an invalid value.; Action: Check the documentation for details.
ORA-13438: GeoRaster metadata error: invalid pyramidType value: Cause: The specified pyramid type was not supported.; Action: Check the documentation for supported pyramid types.
ORA-13439: GeoRaster metadata error: invalid pyramid maxLevel: Cause: The specified maxLevel was 0 or 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 error: invalid compressionType: Cause: The specified compression type was not supported.; Action: Check the documentation for supported compression types.
ORA-13441: GeoRaster metadata SRS error: string: Cause: There were NULL or invalid values in the polynomialModel element in the spatial reference system (SRS) metadata.; Action: Check the documentation and ensure that a valid polynomialModel element is specified.
ORA-13442: GeoRaster object not registered: string: Cause: There was no entry for the specified GeoRaster object in the ALL_SDO_GEOR_SYSDATA view.; Action: Check if the GeoRaster object has been inserted into a GeoRaster table: 1. If not inserted, insert it into the GeoRaster table and try again. 2. If inserted, check if the GeoRaster DML trigger has been created on the GeoRaster table: a. If not created, use SDO_GEOR_UTL.createDMLTrigger to create the DML trigger, then register the GeoRaster object using SDO_GEOR_ADMIN.registerGeoRasterObjects. b. If created, register the GeoRaster object using SDO_GEOR_ADMIN.registerGeoRasterObjects.
ORA-13443: GeoRaster metadata error: NULL or invalid values in layerInfo: Cause: There were NULL or invalid component values in the statisticsDataset, histogram, colorMap, or grayScale metadata.; Action: Check the documentation and ensure that all of the component values are valid.
ORA-13444: cannot perform mergeLayers operation: string: 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: Ensure that 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: GeoRaster metadata error: NULL or invalid NODATA value: Cause: There was an invalid NODATA value or value range in the metadata.; Action: Ensure that 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 error: invalid TRS: Cause: The GeoRaster Temporal Reference System (TRS) was not supported.; Action: Set isReferenced to FALSE.
ORA-13447: GeoRaster metadata error: invalid BRS: Cause: The GeoRaster Band Reference System (BRS) was not supported.; Action: Set isReferenced to FALSE.
ORA-13448: GeoRaster metadata error: invalid spectralExtent: 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 error: invalid ULTCoordinate value: Cause: The GeoRaster metadata ULTCoordinate on band dimension was not 0.; Action: Check the documentation for restrictions.
ORA-13450: GeoRaster metadata error: invalid layerInfo: Cause: The GeoRaster metadata 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 error: invalid scaling function: Cause: The scaling function had a zero denominator.; Action: Ensure that the scaling function denominator is not zero.
ORA-13452: GeoRaster metadata error: invalid bin function: 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 error: invalid number of layers or invalid layerNumber: 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 metadatastring is invalid against its XML schema.: Cause: The GeoRaster metadata was invalid against its XML schema.; Action: Run the schemaValidate routine to find the errors.
ORA-13455: GeoRaster metadata error: invalid beginDateTime or endDateTime: Cause: The beginDateTime value was later than the endDateTime value in the GeoRaster metadata.; Action: Ensure 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 at 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: not rectified: Cause: The polynomial model specified by the Spatial Reference System (SRS) 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: not affine transform: Cause: The polynomial model specified by the Spatial Reference System (SRS) was not a six-parameter transformation, or the six-parameter transformation was not valid.; Action: Check the documentation and ensure that the polynomial model is a valid six-parameter affine transformation.
ORA-13460: GeoRaster metadata SRS error: SRID=0: Cause: The referenced GeoRaster object had a zero model space Spatial Reference ID (SRID).; Action: Set or specify the model space SRID to be a nonzero number.
ORA-13461: GeoRaster metadata SRS error: invalid rational polynomial model: Cause: One of the polynomial definitions in the Spatial Reference System (SRS) of the GeoRaster object had invalid pType, nVars, or order.; Action: Check the documentation and ensure the polynomial definition is correct.
ORA-13462: invalid GeoRaster object (RDT=%0!s, RID=%1!s): %2!s: Cause: The GeoRaster object with the specified rasterDataTable (RDT) and rasterID (RID) attributes had invalid band dimension size.; Action: Check the documentation for the requirements of the band dimension size in the input GeoRaster object.
ORA-13463: error exporting GeoRaster data: string: Cause: An error occurred while exporting GeoRaster data from the database.; Action: Check the error message for details.
ORA-13464: error loading GeoRaster data: string: Cause: An 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: string: Cause: The specified table or column did not exist, or the column was not a GeoRaster column.; Action: Ensure that the specified table exists and the specified column is a GeoRaster column.
ORA-13466: compression or decompression error: string: Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details.; Action: For compression, ensure that the GeoRaster object is valid, and also its metadata is valid for the specified compression format. Use SDO_GEOR.changeFormatCopy to transform the GeoRaster object to an appropriate format, or apply another compression method.
ORA-13467: GeoRaster metadata error: unsupported cellDepth string: Cause: The cellDepth specified in the GeoRaster metadata was not supported.; Action: Check the documentation for the supported cellDepth in the GeoRaster object.
ORA-13468: invalid blockMBR: Cause: Invalid blockMBR geometries were stored in the raster data table.; Action: Ensure that the blockMBR geometries stored in the raster data table are valid, or call the SDO_GEOR.generateBlockMBR() package to regenerate the blockMBR geometries.
ORA-13469: cannot perform updateRaster operation: string: Cause: The data of the source GeoRaster object had different cell depth, or different spatial reference system, or different number of bands from that of the target GeoRaster object.; Action: Ensure that the source and the target GeoRaster objects have the same cell depth, same number of bands 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: parameter %0!s not in format of %1!s: Cause: The specified parameter was not in the proper format.; Action: Check the documentation for the proper format of the parameter.
ORA-13471: string not coordinate referenced: Cause: The GeoRaster object was not georeferenced or had NULL Spatial Reference ID (SRID).; Action: Ensure that the GeoRaster object is georeferenced.
ORA-13472: invalid geometry parameterstring: Cause: The geometry parameter did not specify a valid geometry.; Action: Specify a valid 2D or 3D geometry. If the model Spatial Reference ID (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: string: Cause: The specified rasterSpec parameter was missing or contained an invalid value.; Action: Check the documentation and ensure that the rasterSpec parameter contains only valid keywords and values.
ORA-13474: invalid rasterDataTable attribute: string: Cause: The rasterDataTable attribute of the GeoRaster object was not valid due to one of the following reasons: - It contained a period separator. - Some of the alphanumeric characters were not uppercase.; Action: Ensure that the rasterDataTable attribute meets the above requirements.
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: Parameter %0!s and %1!s did not match.: Cause: The lengths of the two arrays were not the same or did not meet the length requirement.; Action: Check the documentation and ensure the two parameters meet the length requirement.
ORA-13477: invalid GCP georeferencing specification: string: Cause: The Ground Control Point (GCP) georeferencing failed due to one of the following reasons: - The specified functional fitting method was not supported. - The number of GCPs was insufficient. - Some GCPs were invalid. - 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-13479: reprojection infeasible: Cause: Reprojection from source to destination projection produced a large distortion.; Action: Check the destination projection and ensure that it is suitable for the area covered by the source GeoRaster object. Check the GeoRaster documentation for more information about reprojection.
ORA-13480: invalid bitmap mask parameter: Cause: The input bitmap mask parameter did not meet the requirements for the operation due to one of the following reasons: - The bitmap mask had invalid pyramid type or max pyramid level. - The spatial dimension sizes of the bitmap mask was different from that of the input GeoRaster object. - The spatial resolution of the bitmap mask was different from that of the input GeoRaster object. - The model coordinate location of the bitmap mask was different from that of the input GeoRaster object.; Action: Check the documentation for the requirements on bitmap mask.
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-13485: invalid compressParam parameter: string: Cause: The compressParam parameter contained an invalid keyword or value.; Action: Check the documentation and ensure that the compressParam parameter is correct.
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 string not defined in the database: Cause: The specified Spatial Reference ID (SRID) was not found in the Oracle Spatial CS_SRS table.; 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-13489: cannot process the image: string: Cause: There was an error when processing the image in the GeoRaster object.; Action: Check the error message and take the appropriate action or contact Oracle Support Services for further assistance.
ORA-13490: cannot enable GeoRaster: string: Cause: The session user did not have the CREATE TRIGGER privilege or did not own the current schema.; Action: Ensure that the current session user has the required privileges and the session user name is the same as the current schema name.
ORA-13497: string: Cause: This is an internal GeoRaster error.; Action: Contact Oracle Support Services. You may want to ensure that 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 Oracle 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: The SYSAUX DATAFILE clause is not specified.: Cause: If the DATAFILE clause was specified, then a data file for SYSAUX must be specified, unless using Oracle Managed Files (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 an operation with an invalid start and end snapshot pair.; Action: Choose a valid start and end snapshot pair: - Ensure end snapshot is greater than start snapshot. - Ensure start and end snapshots exist.
ORA-13509: error encountered during processing an AWR table: Cause: Error occurred when processing an AWR table due to an underlying error.; Action: Check the full error stack for root cause. Correct problem and retry the operation.
ORA-13510: Retention number string is outside valid range of string to string.: Cause: The specified RETENTION setting was outside supported range.; Action: Specify a valid RETENTION value 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: database ID string does not exist in AWR: Cause: The operation failed because the specified database ID did not exist in the Automatic Workload Repository (AWR).; Action: Specify a valid 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 existed in the Automatic 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 Automatic 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 specified to modify baseline window size (string, string): Cause: Invalid input was specified to the routine modifying the the baseline window size.; Action: Check the arguments 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 Automatic 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 name [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: baseline template (string) is a directory: Cause: The operation failed because the specified baseline template name was a directory.; Action: Check the baseline template name and retry the operation.
ORA-13555: purge operation failed - [string]: Cause: The purge operation failed due to the reason described in the error message.; Action: Correct the stated problem and retry the operation.
ORA-13556: snapshot on remote sources not enabled: Cause: The current database was not set up for snapshots on remote databases. See the description in the error message.; Action: Correct the system settings and retry the operation.
ORA-13557: reset operation failed - [string]: Cause: The Automatic Workload Repository (AWR) reset operation failed due to the reason described in the error message.; Action: Correct the stated problem and retry the operation.
ORA-13558: remote database registration mismatch; database ID (string): Cause: The remote Automatic Workload Repository (AWR) operation failed because the remote database did not match the local registration data. The operation was aborted because it was meant for another database ID. Either the database or the remote database ID changed and needs to be updated or registered in the repository.; Action: Ensure that the database links for the affected database are still valid and point to the registered database. Use any additional errors reported to identify and rectify the the underlying issue. Correct the mismatch or unregister and register the affected database ID.
ORA-13559: CPU time or run time policy violation - string: Cause: The operation ran longer than the expected time.; Action: If this error persists, contact Oracle Support Services.
ORA-13560: SYSAUX tablespace cannot be brought offline; shut down if necessary: Cause: An attempt was made to bring a SYSAUX tablespace offline.; Action: Shut down the database if necessary and do a recovery.
ORA-13561: cannot drop SYSAUX tablespace: Cause: An attempt was made to drop a SYSAUX tablespace.; Action: None
ORA-13562: AWR operation failed because tablespace (string) is invalid.: Cause: The operation failed because the tablespace was invalid for the Automatic Workload Repository (AWR) or was not available.; Action: Provide a valid tablespace, ensure that the tablespace is available and retry the operation.
ORA-13563: AWRHub functionality is disabled.: Cause: The operation failed because the Automatic Workload Repository (AWR) Hub feature was disabled.; Action: Enable AWRHub functionality and retry the operation.
ORA-13564: The database is already registered as a string.: Cause: The operation failed because the database was already registered as a hub server or a source database.; Action: Reconfigure the existing Automatic Workload Repository Hub (AWRHub) setting and retry the operation.
ORA-13565: The database is not registered as a string.: Cause: The operation failed because the database was not registered as a hub server or a source database.; Action: Configure the database as a hub server or source database and retry the operation.
ORA-13566: failure to create a subdirectory under directory [string]: Cause: The operation failed because the system could not create a subdirectory under the specified mailbox directory.; Action: Check the operating system privileges to allow the database system to create subdirectories under the specified mailbox directory.
ORA-13567: DBID (%0!s) of source (%1!s) or the server DBID (%2!s) were already registered in AWRHub.: Cause: The operation failed because either the DBID of the specified source or the specified server DBID was already registered in Automatic Workload Repository Hub (AWRHub).; Action: Unregister the existing DBID and retry the operation.
ORA-13568: DBID (%0!s) of source (%1!s) is not registered in AWRHub: Cause: The database identifier (DBID) of the source was not registered in the Automatic Workload Repository Hub (AWRHub).; Action: Register the source and retry the operation.
ORA-13570: unable to read label file (%0!s) in the directory (%1!s): Cause: The operation failed because the database could not read the label file in the specified directory.; Action: Check the operating system privileges or the presence of the file or both.
ORA-13571: AWR import or export operation failed: string: Cause: The Automatic Workload Repository (AWR) import or export operation failed due to some errors. The possible causes were: - The specified database directory object was invalid. - The specified dump file existed in the specified directory. - The specified dump file did not exist in the specified directory. - Data Pump job encountered some errors. - The operation exceeded the maximum number of retries.; Action: In the log file, check the conditions and errors mentioned in the Cause, correct the problem, and retry the command.
ORA-13572: input parameters to AWRHub operation are invalid: string: Cause: The input parameters to the Automatic Workload Repository (AWR) Hub were invalid.; Action: Correct the input parameters and retry the operation.
ORA-13573: Package (string) is being processed by AWRHub.: Cause: The specified package was reported to Automatic Workload Repository Hub (AWRHub) previously. It was already being processed by AWRHub.; Action: None
ORA-13574: Input parameters to AWR operation are invalid: string: Cause: The input parameters to the Automatic Workload Repository (AWR) operation were invalid.; Action: Correct the input parameters and retry the operation.
ORA-13575: Import operation failed. Version string is outside the supported range [string, string].: Cause: The Automatic Workload Repository (AWR) version that exported the data was out of the range of the supported versions that could be imported in the local AWR.; Action: None
ORA-13576: The AWRHub creation operation failed: The specified mailbox is not dedicated for AWRHub: Cause: The Automatic Workload Repository Hub (AWRHub) creation operation failed because the specified mailbox is not empty.; Action: Cleanup the specified mailbox and retry the command.
ORA-13577: The operation at the AWRHub source database failed because the registration is not active: Cause: The registration of the Automatic Workload Repository Hub (AWRHub) source database was not active.; Action: Wait until the registration is active and retry the command.
ORA-13578: parameter [string] does not allow NULL values: Cause: A NULL value was provided for the specified parameter but the parameter only allows non-NULL values.; Action: Provide a non-NULL value for the specified parameter.
ORA-13579: Source database registration failed: string: Cause: The Automatic Workload Repository Hub (AWRHub) source registration failed due to some errors. A possible cause was that the specified mailbox was not associated with an existing AWRHub Server.; Action: Create a AWRHub server using specified directory as a mailbox before source registration
ORA-13580: Source database unregistration failed: string: Cause: The Automatic Workload Repository Hub (AWRHub) source unregistration failed due to some errors. A possible cause was that a registration request for this source was still pending.; Action: Retry the operation when AWRHub server has no pending registration requests from this source.
ORA-13581: Request timed out: AWRHub Server did not respond after number seconds: Cause: The request failed due to a timeout error. A possible cause was that Automatic Workload Repository Hub (AWRHub) server was not available to complete the request at this time.; Action: Retry the operation after the AWRHub server is available.
ORA-13582: Unregistration failed: AWR snapshots exist for this DBID: Cause: The unregistration failed due to the existence of Automatic Workload Repository (AWR) snapshots for this database identifier (DBID).; Action: Take one of the following actions: - Check if the DBID is correct and retry the operation. - Ensure that this DBID has no remaining snapshots and retry the operation. - Use the FORCE parameter to remove existing snapshots.
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-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-13722: invalid input value for procedure argument string: Cause: An invalid value was passed an input for a procedure argument.; Action: Pass a valid value to the procedure.
ORA-13723: input value for procedure argument string exceeds maximum allowed length of string: Cause: The string input value was too long for the specific procedure argument.; Action: Pass a valid value to the procedure.
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-13760: This operation is not supported from a physical standby database.: Cause: An attempt was made to run an operation that is not supported from a physical standby database.; Action: Run this operation from a primary database.
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-13782: The argument string to this API is only allowed for tasks created in a physical standby database.: Cause: "An attempt was made to pass an argument that is valid only for a physical standby database. "; Action: Remove the invalid argument and re-run the API.
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-13792: This operation requires a database link.: Cause: An attempt was made to execute an operation from a physical standby database that requires a valid database link to access a primary database.; Action: Provide a valid database link to access a primary database.
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 occurred while try to delete a SQL Tuning Base object.; Action: Look at the underlying error(s) on the error stack.
ORA-13803: invalid SQL workload snapshot short interval: Cause: An invalid value was passed for the parameter.; Action: Short snasphot interval should be less than the long snapshot interval.
ORA-13804: invalid SQL workload snapshot long interval: Cause: An invalid value was passed for the parameter.; Action: Snapshot long interval should be greater than the snapshot short interval.
ORA-13810: The FORCED_TRACKING parameter can only have values of N or Y.: Cause: An invalid value was passed for the parameter.; Action: Check the value and input the correct value.
ORA-13811: A database operation is already monitoring this session.: Cause: An attempt was made to start a database operation in a session that was already being monitored.; Action: No action required.
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-13814: database operation name is invalid: Cause: The database operation name provided was invalid.; Action: Supply a database operation name not exceeding 30 characters.
ORA-13815: database operation execution ID is invalid: Cause: The database operation execution ID provided was invalid.; Action: Supply a database operation execution ID greater than 0.
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: Supply a name not exceeding 30 characters or look for the underlying error on the error message stack.
ORA-13832: category name specified is invalid: Cause: An invalid category name was specified.; Action: Supply a category name not exceeding 30 characters or 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-13848: Database link provided for the task operation was different than the one used with task creation API.: Cause: All SQL tuning advisor APIs executed from a physical standby database are required to use the same database link.; Action: Retry the operation by providing the database link used for task creation.
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: Ensure that 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 "%0!s" specified for parameter "%1!s".: Cause: An invalid value was specified for the given parameter.; Action: Correct the value specified for the parameter and retry.
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: Unknown string: Cause: Passed an unknown component, report, or transformation to the framework.; Action: Give a different name
ORA-13972: Unknown string for this 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: Unknown string for this 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: Ensure 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 ensure that 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: An invalid tag name was provided to the report framework common tag callout function.; Action: Check the function input and try again.
ORA-13991: failed to stop report capture on all instances: 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 or subpartition of the object.: Cause: ALTER TABLE RENAME PARTITION or ALTER INDEX RENAME PARTITION specifying a new-partition-name which is identical to the name of an existing partition or subpartition of the object was specified.; Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition or subpartition 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 statement, 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: Ensure that the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION statement.
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: Ensure 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: An 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 Hash, Interval, Autolist, Composite Range Hash, Composite Interval, Composite Autolist partition.; Action: Remove the invalid options 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 partition method: Cause: One of the following occurred: - The table in a subpartition maintenance operation (ALTER TABLE [EXCHANGE | MODIFY | MOVE | TRUNCATE] SUBPARTITION or ALTER TABLE MODIFY PARTITION [ADD | COALESCE] SUBPARTITION) was not partitioned by the composite partition method. - The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation was partitioned by a method other than the composite method. - The table in the ALTER TABLE MODIFY SUBPARTITION [UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES] statement was not partitioned by the composite partition method which is illegal.; Action: Ensure that the table is partitioned by composite partition 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 the range, list, composite range, or composite list method.; Action: The ALTER TABLE [SPLIT | DROP] PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for a 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 a partition which is a composite partition: Cause: An attempt was made to move a partition that was a composite partition.; Action: Move the subpartitions one-by-one to move the composite partition.
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 partition or subpartition of the object.: Cause: ALTER TABLE RENAME SUBPARTITION or ALTER INDEX RENAME SUBPARTITION specifying new-subpartition-name which is identical to the name of an existing partition or subpartition of the object was specified.; Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing partition or subpartition of a given table or index.
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) partition: Cause: The ALTER TABLE ADD PARTITION statement with PARALLEL clause for a partition or composite partition method other than HASH was issued.; 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 14271, 00000, "free error number"
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 partitioned index: Cause: An attempt was made to rebuild a partition of a composite partitioned index which is illegal.; Action: REBUILD the index partition one subpartition at a time.
ORA-14288: index is not partitioned by composite partition 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 was not partitioned by the composite partition method.; Action: REBUILD the index partition one at a time.
ORA-14289: cannot make local index partition of composite partitioned table unusable: Cause: An attempt was made to rebuild a partition of a composite partitioned index which is illegal.; Action: REBUILD the index partition one subpartition at a time.
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 or creating partitioned table exceeds the maximum limit: Cause: The total number of new fragments for adding partitions or for creating a partitioned table exceeded 125000.; Action: Reissue the statement with a fewer number of new fragments.
ORA-14337: index is not partitioned by range, list, composite range, or composite list method: Cause: The index was not partitioned by the range, list, composite range, or composite list method.; Action: The ALTER INDEX [SPLIT | DROP] PARTITION or ALTER INDEX MERGE PARTITIONS command is only valid for an index partitioned by range, list, composite range, or composite list methods. Ensure that the index is partitioned appropriately.
ORA-14339: JavaScript Object Notation (JSON) LOB column can only be used to partition a table with JSON_VALUE operator: Cause: An attempt was made to create a partitioned table using a virtual column as a partitioning key column that references a JavaScript Object Notation (JSON) LOB column but does not contain a JSON_VALUE operator.; Action: Ensure that the virtual column used as a partition key column contains a JSON_VALUE operator if it references a JSON LOB column.
ORA-14340: online DDL rolled back due to DML conflict: Cause: The online build journal became inconsistent with ongoing DML and could not be used successfully to complete the online DDL.; Action: Reissue the online DDL.
ORA-14341: cannot exchange a composite partition with a composite partitioned table: Cause: A composite partition can only be exchanged with a single-level partitioned table.; Action: Ensure that the table that is exchanged is a single-level partitioned table.
ORA-14342: JavaScript Object Notation (JSON) type column can only be used to partition a table with JSON_VALUE operator: Cause: An attempt was made to create a partitioned table using a virtual column as a partitioning key column that references a JavaScript Object Notation (JSON) type column but does not contain a JSON_VALUE operator.; Action: Ensure that the virtual column used as a partition key column contains a JSON_VALUE operator if it references a JSON type column.
ORA-14350: check constraint condition has an invalid reference: Cause: An attempt was made to construct a check constraint condition with an invalid reference, such as a hidden column created for a virtual column, or a guard column.; Action: Remove the invalid reference from the check constraint condition.
ORA-14351: expression edition column is not supported for a hybrid table: Cause: An attempt was made to create or alter a hybrid table with an edition expression column.; Action: Do not specify an edition expression column in the statement.
ORA-14352: must contain at least one internal partition: Cause: An attempt was made to create a hybrid table containing external partitions only.; Action: Ensure that there is at least one internal partition in the statement.
ORA-14353: operation not supported for an external partition in a hybrid-partitioned table: Cause: An attempt was made to perform an operation on an external partition in a hybrid-partitioned table, that was not supported.; Action: Do not perform the unsupported operation.
ORA-14354: operation not supported for a hybrid-partitioned table: Cause: An attempt was made to perform an operation on a hybrid-partitioned table that was not supported.; Action: Do not perform the unsupported operation.
ORA-14355: cannot use bind variables in the access parameters clause: Cause: An attempt was made to use a bind variable in the access parameters clause of an inline external table query.; Action: Remove the bind variable or surround the access parameters clause in single quotes.
ORA-14356: cannot update a join view using UPDATE FROM clause: Cause: An UPDATE statement with a FROM clause was specified, where the update target was a join view.; Action: Provide an update target that is a table, single-table view, or a materialized view.
ORA-14357: updated column must come from the target table: Cause: An UPDATE statement with a FROM clause was specified where a column on the left side of the SET clause was not a column of the table to be updated.; Action: Specify a column from the table to be updated.
ORA-14358: cannot delete a join view using DELETE FROM clause: Cause: A DELETE statement with a FROM clause was specified, where the delete target was a join view.; Action: Provide a delete target that is a table, single-table view, or a materialized view.
ORA-14359: The operation was unable to obtain a consistent set of rows that needed to be modified.: Cause: A consistent set of rows needing modifications could not be obtained as the WHERE clause was non-deterministic and also, large concurrent DML possibly modified WHERE clause columns. The WHERE clause was non-deterministic because it contained an operand that, when given the same input parameters, did not always return the same output value.; Action: Remove any non-deterministic operand in the WHERE clause and reissue the DML.
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 ensure that the new partition key is within the range containing the old partition key.
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 string: 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-14424: CREATE TABLE FOR EXCHANGE cannot be used with certain types of tables.: Cause: An attempt was made to use the CREATE TABLE FOR EXCHANGE statement on a table type (for example, cluster, temporary, index-organized table (IOT), external tables) that was not allowed.; Action: Do not specify the FOR EXCHANGE clause with certain types of tables (for example, cluster, temporary, indexed-organized table (IOT), external tables).
ORA-14425: CREATE TABLE AS SELECT disallowed along with the CREATE TABLE FOR EXCHANGE clause.: Cause: An attempt was made to combine the CREATE TABLE FOR EXCHANGE clause with a CREATE TABLE AS SELECT.; Action: Execute a CREATE TABLE FOR EXCHANGE followed by an INSERT AS SELECT into the table.
ORA-14426: Online DDL's cannot be used inside an autonomous transaction.: Cause: An attempt was made to use online DDL's inside an autonomous transaction.; Action: Using online DDL's inside an autonomous transaction is not allowed. Remove the ONLINE keyword from the statement.
ORA-14427: table does not support modification to a partitioned state DDL string: Cause: An alter table modification to a partitioned state DDL 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 DDL is only supported for heap tables that are non-partitioned.; Action: Do not use the modification to a partitioned state DDL on a partitioned table.
ORA-14428: TBL$OR$IDX$PART$NUM query on remote object not supported: Cause: A TBL$OR$IDX$PART$NUM query on a remote object was attempted.; Action: Do not use TBL$OR$IDX$PART$NUM query on remote objects.
ORA-14429: System partitioning is not allowed in modification to a partitioned state DDL.: Cause: An attempt was made to convert a non-partitioned table to system partitioned table, which is illegal.; Action: Specify a different partitioning method in the modification to a partitioned state DDL.
ORA-14430: An alter table modification to a partitioned state DDL cannot be combined with other operations.: Cause: An attempt was made to combine an alter table modification to partitioned state DDL with another operation, which is illegal.; Action: Ensure that the modification to partitioned state operation is the only one specified in the alter table DDL.
ORA-14431: A system-generated column is not allowed as a partitioning column.: Cause: The partitioning column specified by the user was a system-generated column, which is illegal.; Action: Ensure that the partitioning column is not a system-generated column.
ORA-14432: System partitioning is not allowed in the CREATE TABLE FOR EXCHANGE DDL statement.: Cause: An attempt was made to create a system partitioned table using the CREATE TABLE FOR EXCHANGE DDL statement, which is illegal.; Action: Specify a different partitioning method in the CREATE TABLE FOR EXCHANGE DDL statement.
ORA-14433: Reference partitioning is not allowed in the online version of modification to a partitioned state DDL.: Cause: An attempt was made to convert a non-partitioned table to a reference partitioned table using the online version of the DDL, which is not allowed.; Action: Remove the ONLINE keyword from the statement.
ORA-14434: non-existent partitioning column in ALTER TABLE statement: Cause: The partitioning column specified in the ALTER TABLE statement was not one of the columns of the table being altered.; Action: Ensure that all columns in the partitioning column list are columns of the table being altered.
ORA-14435: partition bound specified when adding this system partition: Cause: The user specified either a VALUES LESS THAN clause or a VALUES (<values_list>) clause when adding a partition to a system partitioned table, which is not allowed.; Action: Remove the VALUES LESS THAN clause and VALUES (<values_list>) clause from the partition being added.
ORA-14436: During the modification to a partitioned state DDL, it is illegal to specify SUBPARTITIONS or STORE IN clause once a SUBPARTITION TEMPLATE has been specified.: Cause: The user specified either a SUBPARTITIONS or a STORE IN clause along with a subpartition template when modifiying a table to partitioned state, which is not allowed.; Action: Remove either the SUBPARTITIONS | STORE IN clause or remove the SUBPARTITION TEMPLATE clause.
ORA-14437: Multiple DEFAULT partitions are not allowed in a system partitioned table.: Cause: The SET DEFAULT clause was specified for multiple partitions in a system partitioned table, which is not allowed.; Action: Remove all but one of the SET DEFAULT clauses.
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: cannot use LOB from purged temporary table: Cause: An attempt was made to use a LOB from a temporary table whose data has been purged because: 1.The table was transaction-specific and the transaction was COMMITTED or ABORTED. 2.The table was truncated or the session that created the LOB ended.; Action: Select a LOB locator with valid data.
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 was already in use by the parent transaction.; Action: Ensure that 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-14466: Data in a read-only partition or subpartition cannot be modified.: Cause: An attempt was made to modify data residing in a read-only partition or subpartition.; Action: Modify this partition or subpartition to read/write or do not make the modification.
ORA-14467: This option cannot be issued with the READ ONLY or READ WRITE clause.: Cause: An attempt was made to issue a READ ONLY or READ WRITE clause combined with the ONLINE or the INCLUDING ROWS clause.; Action: Issue the READ ONLY or READ WRITE clause with the ONLINE or the INCLUDING ROWS clause in separate statements.
ORA-14468: invalid INCLUDING ROWS WHERE ... clause: Cause: An invalid INCLUDING ROWS WHERE ... clause was specified. The INCLUDING ROWS WHERE ... clause has the following restrictions: - It can only refer to the target table of the DDL. - It cannot have subselect queries. - It cannot refer to the SYSDATE function. - It cannot refer to the ROWNUM pseudo column or the ROWID column.; Action: Rewrite the WHERE clause so that it does not have the restrictions previously listed.
ORA-14469: ALTER TABLE MOVE INCLUDING ALL LOBS cannot be used with certain types of tables.: Cause: An attempt was made to use the ALTER TABLE MOVE INCLUDING ALL LOBS statement on a table type (for example, cluster, temporary, index-organized table (IOT) or external tables) that was not allowed.; Action: Do not specify the INCLUDING ALL LOBS clause with certain types of tables (for example, cluster, temporary, indexed-organized table (IOT) or external tables).
ORA-14470: Invalid usage of the fast modification to nonpartitioned state DDL.: Cause: An attempt was made to use the fast modification to nonpartitioned state DDL with an unsupported condition. The ALTER TABLE MODIFY NONPARTITIONED FAST DDL has the following restrictions: - Only heap tables are supported. - Partitioned tables can have only one fragment. - Tables cannot be reference partitioned or have any reference partitioned children.; Action: Ensure that all of the conditions for the fast modification to nonpartitioned state DDL are satisfied.
ORA-14471: Invalid usage of the fast modification to partitioned state DDL.: Cause: An attempt was made to use the fast modification to partitioned state DDL with an unsupported condition. The ALTER TABLE MODIFY PARTITION BY FAST DDL has the following restrictions: - Only heap tables are supported. - Partition definition can have only one fragment. - Storage parameters of any segment cannot be changed. - Including ROWS clause is not supported. - Online version of this DDL is not supported.; Action: Ensure that all of the conditions for the fast modification to partitioned state DDL are satisfied.
ORA-14472: Non-prefixed indexes need to be unusable for fast modification to partitioned state DDL.: Cause: An attempt was made to use the fast modification to partitioned state DDL with a usable non-prefixed index.; Action: All non-prefixed indexes need to be made unusable before the fast modification to partitioned state DDL can be executed.
ORA-14473: Mapping table cannot be dropped while there are failed online partition maintenance operations that must be cleaned up.: Cause: An attempt was made to directly drop the mapping table while there were failed online partition maintenance operations for cleanup.; Action: Clean up failed online partition maintenance operations using the PL/SQL package CLEANUP_ONLINE_OP. Clean up procedure will internally take care of dropping the mapping table.
ORA-14474: invalid usage of the modification to nonpartitioned state DDL: Cause: An attempt was made to use the modification to nonpartitioned state DDL with an unsupported condition. The ALTER TABLE MODIFY NONPARTITIONED DDL has the following restrictions: - A table must be partitioned. - Only heap tables are supported. - Tables cannot be reference partitioned or have any reference partitioned children. - A table cannot have any domain indexes or bitmap join indexes.; Action: Ensure that all of the conditions for the modification to nonpartitioned state DDL are satisfied.
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: The table partition is corrupt. All rows do not fall within the partition bounds.: Cause: The partition contained some rows that should belong to some other partition. This could occur because an EXCHANGE PARTITION operation was done without validation.; Action: Delete the rows that do not qualify being in this partition.
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-14540: An Online DDL or a DDL with the UPDATE INDEXES clause cannot be used with auto-commit turned off for the DDL.: Cause: An attempt was made to use an online DDL or a DDL with the UPDATE INDEXES clause when auto-commit was turned off for the DDL.; Action: Enable auto-commit and then retry the DDL.
ORA-14541: A JSON column cannot serve as a partitioning column.: Cause: An attempt was made to specify a column of JavaScript Object Notation (JSON) type partitioning or subpartitioning column.; Action: Ensure that no partitioning or subpartitioning column is of type JSON.
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-14570: unable to extend the log for use on persistent memory storage: Cause: A log that was stored on disk and moved to persistent memory storage must be increased in size by a block. The attempt to extend the file has failed.; Action: Migrate the log by recreating the log on persistent memory and not by copying it from disk to persistent memory.
ORA-14571: The control file cache must either be enabled on all instances or disabled on all instances.: Cause: The control file cache must be either enabled or disabled in all instances.; Action: Contact Oracle Customer Support.
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, Interval, Autolist, Composite Range Hash, Composite Interval, Composite Autolist table or partition: Cause: Specifying a STORE-IN clause during creation or altering of a Range, Composite Range List partitioned table was not allowed.; Action: Re-issue the statement 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 string aggregate: Cause: An attempt was made to use the aggregate with a value that was too long.; Action: Limit the size of the 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-14698: MAX_STRING_SIZE migration to STANDARD is not allowed due to column string in object string.string.: 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-14699: long bind value is too large for column: Cause: An attempt was made to bind a value larger than 4000 bytes for insert or update of a VARCHAR2, NVARCHAR2, or RAW column, and the value was too large for the destination column.; Action: Either make the destination column larger, or reduce the size of the bind value.
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-14710: domain index "string" found for table "string"."string" for EXCHANGE CASCADE: Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command was attempted for the specified table. However, there was a domain index on the specified table.; Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option or ensure that there is no domain index on the specified table.
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 the interval or by the autolist method.: Cause: The table was not partitioned by the interval or by the autolist method.; Action: ALTER TABLE SET STORE IN is only valid for interval or autolist partitioned tables. Ensure that the table is partitioned by an interval or by an autolist method.
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.; 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 [sub]partition cannot be specified for INTERVAL [sub]partitioned objects.: Cause: An attempt was made to create a [sub]partition with a MAXVALUE highbound on an INTERVAL [sub]partitioned object.; Action: Do not create a [sub]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: Partitions cannot be truncated, dropped or merged with mixed syntax.: Cause: An attempt was made to truncate, drop or merge partitions with mixed syntax.; Action: Do not use mixed syntax to truncate, drop or merge partitions.
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 [sub]partition or autolist [sub]partition nested table or XMLType with object-relational storage: Cause: Interval [sub] partition or autolist [sub]partition was not supported for nested table and XMLType with object-relational storage.; Action: Use a list or range partition instead.
ORA-14770: An XML virtual column whose expression includes EXTRACTVALUE operator cannot be used for the partitioning key during interval [sub]partition.: Cause: Interval [sub]partition was not supported with an XML virtual column whose expression includes the EXTRACTVALUE operator.; Action: Use XMLCAST and XMLQUERY operators to define the virtual column expression for the partitioning key during interval [sub]partition.
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: table does not support string string: Cause: An ALTER TABLE MOVE PARTITION ONLINE or ALTER TABLE MODIFY PARTITION INDEXING or ALTER TABLE SPLIT PARTITION ONLINE statement was issued on a table that was either not a heap-organized table or had an object type, domain index or bitmap join index defined on it. Or, the source table of the split online has reference partitioned child tables. This operation is only supported for heap-organized tables.; Action: Do not use the ONLINE keyword or the INDEXING clause.
ORA-14809: schema does not support string: Cause: An ALTER TABLE MOVE PARTITION ONLINE or an ALTER TABLE MODIFY PARTITION INDEXING statement was issued on a table owned by SYS, SYSTEM, PUBLIC, OUTLN, or XDB.; Action: Do not use the ONLINE keyword or the INDEXING clause.
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 DDL with the INCLUDING ROWS clause is not supported under supplemental logging.: Cause: An online DDL with an INCLUDING ROWS clause was issued on a table while supplemental logging was enabled.; Action: Do not use the ONLINE keyword.
ORA-14812: Operations on partitions through DBMS_LOB package are not permitted during a concurrent online move of the partition.: Cause: A DBMS_LOB operation was issued on a Large Object (LOB) while an ALTER TABLE MOVE PARTITION ONLINE was executing concurrently on the partition containing the LOB.; Action: Reissue the DBMS_LOB operation after MOVE PARTITION ONLINE has completed.
ORA-14813: ONLINE MOVE OR SPLIT PARTITION not supported while there are too many table segments and index segments: Cause: An ALTER TABLE MOVE or SPLIT PARTITION ONLINE command was issued on a table while the number of table segments multiplied by the number of index segments exceeded the maximum allowed.; Action: Do not use the ONLINE keyword.
ORA-14850: Adding a partition with DEFAULT high value is not permitted on Autolist partitioned objects.: Cause: An attempt was made to add a DEFAULT partition to an Autolist partitioned object.; Action: Do not perform the operation on an Autolist partitioned object. Insert a row to create the new partition.
ORA-14851: DEFAULT [sub]partition cannot be specified for AUTOLIST [sub]partitioned objects.: Cause: An attempt was made to create a [sub]partition with a DEFAULT high value on an AUTOLIST [sub]partitioned object.; Action: Do not create a [sub]partition with a DEFAULT high value.
ORA-14852: SET [SUB]PARTITIONING AUTOMATIC is not legal on this table.: Cause: SET [SUB]PARTITIONING AUTOMATIC clause was specified. ALTER TABLE SET [SUB]PARTITIONING AUTOMATIC is only legal on a list partitioned table. Additionally, this table cannot have a DEFAULT partition.; Action: Use SET [SUB]PARTITIONING AUTOMATIC only on a valid table.
ORA-14853: An invalid option was specified for the SET [SUB]PARTITIONING clause.: Cause: SET [SUB]PARTITIONING clause was used with an invalid option. The only valid options are AUTOMATIC and MANUAL.; Action: Use valid options.
ORA-14854: SET [SUB]PARTITIONING MANUAL is not legal on this table.: Cause: SET [SUB]PARTITIONING MANUAL clause was specified. ALTER TABLE SET [SUB]PARTITIONING MANUAL is only legal on a list partitioned table. Additionally, this table cannot have a DEFAULT partition.; Action: Use SET [SUB]PARTITIONING MANUAL only on a valid table.
ORA-14855: Table is already a list partitioned table.: Cause: An attempt to specify SET [SUB]PARTITIONING MANUAL on a list (sub)partitioned table failed. SET [SUB]PARTITIONING MANUAL is used to convert an autolist (sub)partitioned table to a list (sub)partitioned table.; Action: Use SET [SUB]PARTITIONING MANUAL on an autolist (sub)partitioned table.
ORA-14856: Table is already an autolist partitioned table.: Cause: An attempt to specify SET [SUB]PARTITIONING AUTOLIST on an autolist (sub)partitioned table failed. SET [SUB]PARTITIONING AUTOLIST is used to convert a list (sub)partitioned table to an autolist (sub)partitioned table.; Action: Use SET [SUB]PARTITIONING AUTOLIST on an autolist (sub)partitioned table.
ORA-14857: Subpartition template is expected when creating an autolist subpartitioned table.: Cause: An attempt was made to create an autolist subpartitioned table without a subpartition template.; Action: Use a subpartition template when creating an autolist subpartitioned table.
ORA-14858: Set empty template is not legal on an autolist subpartitioned table.: Cause: An attempt was made to set an empty subpartition template for an autolist subpartitioned table.; Action: Convert this table to a list subpartitioned table before set empty template.
ORA-14870: Range subpartitioned table with INTERVAL clause has more than one column.: Cause: An attempt was made to create an interval subpartitioned table with more than one subpartitioning column.; Action: Use a single subpartitioning column.
ORA-14871: Subpartition template is expected when creating an interval subpartitioned table.: Cause: An attempt was made to create an interval subpartitioned table without a subpartition template.; Action: Use a subpartition template when creating an interval subpartitioned table.
ORA-14872: ADD SUBPARTITION is not permitted on interval subpartitioned objects.: Cause: ALTER TABLE ADD SUBPARTITION was attempted on an interval subpartitioned object.; Action: Do not add a subpartition on an interval subpartitioned object. Insert a row to create the new subpartition.
ORA-14873: Set empty template is not legal on an interval subpartitioned table.: Cause: An attempt was made to set an empty subpartition template for an interval subpartitioned table.; Action: Convert this table to a range subpartitioned table before set empty template.
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 Transaction Guard.: 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-14913: Invalid logical transaction ID detected.: Cause: The logical transaction was marked invalid.; Action: Verify your configuration. Transaction Guard does not support XA transactions that use the two-phase commit protocol.
ORA-14914: cannot invoke set failpoint: Cause: An invalid parameter was specified.; Action: Specify a valid parameter.
ORA-14915: cannot invoke set failpoint: Cause: An invalid database session was specified.; Action: Specify a valid database session.
ORA-14916: Switch service by DRCP clients is not supported by Transaction Guard.: Cause: The Database Resident Connection Pooling (DRCP) client tried to switch services while Transaction Guard was enabled.; Action: None
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-14955: Transaction Guard has detected that committed transactions are lost.: Cause: Committed transactions could be lost if: i) COMMIT options were changed from the default to non-durable settings: NOLOGGING was in use, COMMIT_WAIT=nowait or COMMIT_LOGGING=batch. ii) Accessing an Oracle Data Guard secondary site before redo apply completed. iii) Flashback of the database. iv) Incomplete media recovery.; Action: i) If committed transactions cannot be lost, do not change the settings COMMIT_WAIT, or COMMIT_LOGGING from their defaults (these parameters have no default values but behave as FORCE_WAIT and IMMEDIATE, respectively, if not set). ii) Allow media recovery or redo apply to complete before opening a database to users. iii) Do not use NOLOGGING in high availability environments. Media recovery is not possible through the NOLOGGING operation. Data could be lost unless recovered from other sources. iv) Ensure media recovery runs to completion.
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: disk group "string" does not exist or is not mounted: Cause: An operation failed because the specified disk group did not exist or was not mounted by the current Oracle ASM instance.; Action: Verify the following: * That the disk group name used is valid * That the disk group exists, and * That the disk group is mounted by the current Oracle 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 disk group.; Action: Check the template name and disk group 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: system template cannot be dropped: Cause: An attempt was made to drop the system template.; Action: Ensure that the template to be dropped is not the system template because it is required for proper operation. Select a non-system template and retry the operation.
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 cannot be found.: Cause: The Oracle ASM instance could not locate the specified file.; Action: Check that the file name is correct, the file exists in the specified location, and proper privileges are granted to the user. Retry the operation.
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: Disk group string cannot be mounted.: Cause: The disk group could not be mounted by the ASM instance because 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: Disk group cannot be created.: Cause: The disk group could not be created.; Action: Check the Oracle Automatic Storage Management (ASM) alert log and additional reported errors.
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: The disk specification 'string' matches no disks.: Cause: The instance was unable to discover any disks in the mentioned device specification path.; Action: Ensure that the disk 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 as well as the alert log.
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 to string MB from string MB.: 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' size string MB is smaller than minimum of string MB: 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, logical 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 disk group, 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: Oracle ASM file name 'string' is not in multiple file creation form: Cause: The Oracle Automatic Storage Management (Oracle ASM) file name was not in a form that could be used to create multiple files because either a fully qualified file name or an alias name was specified.; Action: Correct the specified Oracle ASM file name.
ORA-15048: Oracle ASM internal files cannot be deleted.: Cause: An attempt was made to delete a metadata file used by Oracle ASM to manage the disk group.; Action: Check the specified Oracle 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: Oracle ASM file name string is not in disk group string.: Cause: The Oracle Automatic Storage Management (Oracle ASM) file name did not contain a disk group name that specified the correct disk group as implied by the other arguments to the command.; Action: Correct the specified Oracle ASM file name or disk group 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 relational database management system (RDBMS) instance was unable to connect to the required ASM instance when accessing a disk group.; Action: Check the additional error messages. Configure the correct ASM system identifier (SID) or ensure that the RDBMS instance has operating system privileges for ASM SYSDBA.
ORA-15056: additional error message: Cause: An operating system error occurred.; 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 Oracle ASM instance. This occurred because the connection between the database instance and the Oracle ASM instance was lost.; Action: Check the accompanying error messages for more information on the failure. Note that database instances will always return this error when the ASM instance is terminated.
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 disk group's redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY disk group, using the FAILGROUP clause with an EXTERNAL REDUNDANCY disk group, using invalid template attributes, or mounting a HIGH or EXTERNAL redundancy disk group for recovery. An attempt (without force option) was made to drop disks or fail groups that leads to fewer number fail groups than the minimal requirement (3 for NORMAL and FLEX and 5 for HIGH redundancy disk group).; Action: Omit the option from the command. Check if the disk group has minimum number of fail groups including quorum fail group after the successful execution of the SQL.
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: Time-out waiting for lock on ASM file 'string': Cause: An attempt was made to access an Oracle ASM file. But the file could not be accessed because the file was either being created, resized, or deleted.; Action: No action required. Try accessing the file 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 disk group. To start an ASM instance, relink the ORACLE binary with ASM_ON or explicitly set the INSTANCE_TYPE initialization parameter to ASM. Ensure that there is a local ASM instance available, or a remote ASM instance accessible through the Oracle ASM listeners. Examine any accompanying errors in the stack to understand the possible reasons for this failure. Fix them and retry starting the database instance.
ORA-15078: Oracle ASM disk group was forcibly dismounted: Cause: The Oracle Automatic Storage Management (Oracle ASM) disk group was dismounted (with the ALTER DISKGROUP DISMOUNT FORCE statement), and therefore it could not be accessed.; Action: Mount the disk group using the ALTER DISKGROUP MOUNT statement to allow access to the disk group again.
ORA-15079: Oracle ASM file is closed: Cause: The Oracle Automatic Storage Management (Oracle ASM) file, to which the I/O request was issued, was closed. This could have been a consequence of the disk group being dismounted.; Action: Ensure that the disk group that contains the file is mounted.
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: Ensure that all of the disks are operational.
ORA-15081: failed to submit an I/O operation to a disk: Cause: Submission of an I/O operation to a disk has failed.; Action: Ensure that all of 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: Time-out during communication with ASMB background process: Cause: The database instance failed to communicate with the ASMB background process.; Action: Check the alert log and trace files for more information on a possible reason for the failure. If assistance is needed, contact Oracle Support Services.
ORA-15084: Oracle ASM disk "string" is offline and cannot be dropped.: Cause: An attempt was made to drop a disk that was offline.; Action: Check the Oracle Automatic Storage Management (Oracle 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 an inconsistent sector size value.; Action: Use disks with a sector size consistent with disk group sector size, or ensure that 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 LSCT 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. Alternatively, set the compatible.rdbms attribute of the disk group to a value greater than or equal to 12.1 to allow for larger disk sizes.
ORA-15100: invalid or missing disk group name: Cause: The command did not specify a valid disk group name. Disk group names should start with a letter, and can only contain alphanumeric characters and the underscore character.; Action: Specify a valid disk group 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: Oracle ASM disk group string was forcibly dismounted.: Cause: The Oracle Automatic Storage Management (Oracle ASM) disk group to which the I/O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE statement) so that it could not be accessed.; Action: Mount the disk group using the ALTER DISKGROUP MOUNT statement to allow access to the disk group 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: Oracle ASM file name 'string' does not begin with the Oracle ASM prefix character: Cause: An Oracle Automatic Storage Management (Oracle ASM) file name was specified that did not begin with the Oracle ASM prefix character (currently '+'). Oracle ASM uses the prefix to determine that a file specification is in fact an Oracle ASM file.; Action: Correct the file name specification.
ORA-15121: Oracle ASM file name 'string' contains an invalid disk group name.: Cause: A file name was specified that did not contain a valid disk group name. The disk group name follows immediately after the Oracle Automatic Storage Management (Oracle 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: Oracle ASM file name 'string' contains an invalid file number: Cause: A numeric file name was specified that did not contain a valid Oracle Automatic Storage Management (Oracle ASM) file number. The Oracle ASM file number followed immediately after the disk group name. It must be preceded by a '.' character and contain only numeric characters.; Action: Correct the file name specification.
ORA-15123: Oracle ASM file name 'string' contains an invalid incarnation number: Cause: A numeric file name was specified that did not contain a valid Oracle Automatic Storage Management (Oracle ASM) incarnation number. The Oracle ASM incarnation number followed immediately after the Oracle ASM file number. It must be preceded 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: Oracle ASM file name 'string' contains an invalid template name: Cause: A file name was specified to Oracle Automatic Storage Management (Oracle ASM) that did not contain a valid template name. The template name, if present, follows immediately after the Oracle ASM incarnation number or the Oracle ASM alias name, if such is used in place of the Oracle ASM file number. It must be enclosed in parenthesis, start with an alphabetic character, and consist of up to 30 characters that are alphabetic, numeric, or the characters '$' and '_'.; Action: Correct the file name specification.
ORA-15126: component in Oracle ASM file name 'string' exceeds maximum length: Cause: The disk group name, template name, or alias name fields in the Oracle Automatic Storage Management (Oracle ASM) file name exceeded the maximum identifier length of 48 characters.; Action: Correct the file name specification.
ORA-15127: Oracle ASM file name 'string' cannot use templates.: Cause: A fully qualified Oracle Automatic Storage Management (Oracle ASM) file name was specified. This specification did not permit the inclusion of a template name in the Oracle ASM file name.; Action: Correct the file name specification.
ORA-15128: Oracle ASM file name 'string' exceeds maximum length string.: Cause: The maximum Oracle Automatic Storage Management (Oracle ASM) file name length of 256 characters was exceeded for the combination of disk group name, file number, template name, alias name, plus punctuation within the Oracle 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 occurred 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 occurred 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: Ensure that all of the members of the cluster are at the same version. If you are attempting to perform a rolling upgrade, execute the ALTER SYSTEM START ROLLING statement. 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-15165: rolling migration not allowed with the versions specified: Cause: One of the following requirements were not met: - The From version is not compatible. - The To version is less than or equal to the From version. - Neither the From nor the To version matches the current version. - The From version is less than 12.1.0.2.0.; Action: Ensure that the From and the To versions specified are legitimate.
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-15167: command requires at least string failure groups; found only string: Cause: An attempt to convert disk group redundancy failed because of insufficient failure groups.; Action: Add enough failure groups to the disk group and then retry converting the disk group redundancy to flex.
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 occurred 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 not yet available in this version: Cause: An unimplemented operation was attempted.; Action: If this operation is required, then upgrade to a release where the operation is supported.
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 disk group 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: Ensure that all connected clients are at the target compatibility level or higher.
ORA-15232: command requires all disks in diskgroup string to be online: 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 disk group compatibility due to [string].: Cause: Disk group compatibility could not be advanced because of errors.; Action: Check the alert log for more information on the reason for the error.
ORA-15234: Diskgroup COMPATIBLE.RDBMS parameter value (string) exceeds COMPATIBLE.ASM parameter value (string).: Cause: Attempted to advance the COMPATIBLE.RDBMS parameter value for the diskgroup beyond the COMPATIBLE.ASM parameter.; Action: Make sure the COMPATIBLE.ASM parameter setting is at the same or higher compared to the COMPATIBLE.RDBMS parameter for the diskgroup.
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: Attempts to set the specified attribute failed with an error.; Action: Examine the underlying error(s) on the error stack. If necessary, contact Oracle Support Services.
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 online or being brought online.: Cause: An attempt was made to bring a disk online that was either already online or was 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 was already defined 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 user that was provided 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' already in use: Cause: This user identification number was already in use internally by Oracle Automatic Storage Management (Oracle ASM).; Action: Choose a different user identification number and retry the operation.
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 disk group requires at least one regular disk.: Cause: Attempted to create an external redundancy disk group with only quorum disks.; Action: Specify at least one regular disk to create an external redundancy disk group.
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-15282: Cluster Synchronization Services operation 'string' failed with error 'string'.: Cause: This is an internal error.; Action: Check the accompanying error messages. Contact Oracle Support Services.
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 specified 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: Oracle ASM instance software version string less than client version string: Cause: The Oracle ASM instance software version was less than the client version.; Action: Upgrade the Oracle ASM instance software or use a client version that matches the Oracle ASM version. Check the alert log for more information regarding 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 %0!s of the open file '%1!s': Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on an open file. These commands require the file to be closed.; Action: Close the file and then retry the operation.
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 update Oracle ASM internal files: Cause: An attempt was made to change Oracle Automatic Storage Management (Oracle ASM) metadata used to manage the disk group. This was not allowed.; Action: Check the specified Oracle ASM file name to ensure a file name with a file number greater than or equal to 256 is selected.
ORA-15306: ASM password file update failed on node string: Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE command failed on the specified 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: A process from a prior instantiation of this client was not fenced.; Action: Ensure that all processes belonging to the client instance have 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 password file string.: Cause: Attempted to run an unsupported operation 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 a valid password file name and retry the operation.
ORA-15326: specified input string is not an ASM file: Cause: The attributes could not be obtained because the specified input was 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: Oracle ASM proxy instance ORACLE_SID string does not start with string.: Cause: The Oracle ASM proxy instance was started with an invalid ORACLE_SID prefix.; Action: Start the Oracle 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 available on all client instances: Cause: An ALTER DISKGROUP ADD DISK statement specified a disk that could not be discovered by all client instances.; Action: Check the Oracle ASM and client alert logs for more information. Check operating system permissions for the device and the storage subsystem configuration on all instances.
ORA-15334: volume background process terminated with error: Cause: A volume background process terminated with an error.; Action: Restart the Oracle Automatic Storage Management (Oracle ASM) instance where the issue occurred. If the issue persists, contact Oracle Support Services.
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 value of 1 in STRIPE_COLUMNS and specified the STRIPE_WIDTH argument.; Action: If striping is required, then set STRIPE_COLUMNS to a value greater than 1. If striping is not required, then 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: Oracle ASM client instance string reconnection refused: Cause: The client was not an orphaned client and is not a legitimate candidate to reconnect to Oracle ASM.; Action: Shut down and restart the remote client so that it is considered a new client in the cluster.
ORA-15339: client instance string has been fenced by Oracle ASM: Cause: Oracle ASM had already fenced this client.; Action: Shutdown and restart the remote client instance to be registered as a new client in the cluster.
ORA-15340: unable to create member cluster 'string': Cause: Creation of the member 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 member cluster 'string': Cause: Deletion of the member 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 Automatic Storage Management (ASM) client was not registered with this instance.; Action: Check the Oracle ASM instance alert log, the client alert log and trace files, and any accompanying error messages for more information on the reason for the failure.
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 the Automatic Storage Management (ASM) file string was aborted.: Cause: The client process attempting to create or open the ASM file was terminated or interrupted.; Action: Use the alert log to identify any issues encountered. Correct the cause of the issue and retry. If the issue persists, contact Oracle Support.
ORA-15347: The logical block size %0!s of Automatic Storage Management (ASM) file '%1!s' is too small for disk group sector size %2!s.: Cause: Attempted to create a file on Oracle ASM whose logical block size was less than the sector size of the disk group.; Action: Check if the system configuration has changed. Correct the error and retry.
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 either Oracle Local Repository (OLR) was not available or AFD disk string attribute did not exist.; Action: Check that Oracle Clusterware is properly configured using 'ocrcheck -local' command.
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: Ensure that 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: File "string" can not be created on a sparse disk group.: Cause: An attempt was made to create a fine-grained striping file on a sparse disk group. 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 member cluster 'string': Cause: Looking up of the member cluster failed.; Action: Execute the 'asmcmd lscc' command to list all of the configured member clusters. If the member cluster listed in the message is not present, it might have been forcibly deleted. Refer to the product documentation for more information. If the member 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 #.#.#.#.# or other forms with fewer numbers delimited by a period.
ORA-15364: member cluster version string is incompatible with storage server version string: Cause: The specified member cluster version was not supported by the Storage Server.; Action: Upgrade or downgrade the storage server to a version that is compatible with member cluster and retry the operation. Install a member cluster using a supported version. Refer to product documentation for a complete list of supported releases.
ORA-15365: member cluster 'string' already configured: Cause: The specified member cluster was already configured.; Action: Execute the 'asmcmd lscc' command to list all of the configured member clusters. Reexecute the command with a member cluster name that has not already been configured.
ORA-15366: unable to delete configuration for member cluster 'string' because the directory 'string' was not empty: Cause: Deleting the member cluster configuration failed because some files were present.; Action: Deinstall the member cluster and rerun the command. If the command fails again, execute the 'asmcmd rmcc <member_cluster_name> -f' command to force deletion of the configuration for the member cluster.
ORA-15367: member cluster 'string' not configured: Cause: The specified member cluster was not configured.; Action: Execute the 'asmcmd lscc' command to list all of the configured member clusters. Reexecute the command with a member 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: Oracle Call Interface (OCI) call returned 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: Check the alert log and trace file for more information on this failure. Solve any issues and retry the operation. If the issue persists, contact Oracle Support Services.
ORA-15370: database version needs to be 12.1 or higher to access a disk group number higher than 63: Cause: An attempt was made to access a disk group number greater than 63 with a database version lower than 12.1.; Action: Upgrade the database to version 12.1 or higher and retry the operation.
ORA-15371: The command is not supported on a member cluster.: Cause: An attempt was made to run a command that is not supported on a member cluster.; Action: Rerun the command on the storage server.
ORA-15372: Client version string not supported by the Oracle ASM instance.: Cause: The software version of the client instance was not supported by the release of the Oracle ASM instance.; Action: Upgrade the client instance to a later release that is compatible with the Oracle ASM instance and retry the operation. Refer to product documentation for a complete list of supported releases.
ORA-15373: SYSDG, SYSKM, SYSRAC, and SYSBACKUP administrative privileges cannot be granted on an ASM instance.: Cause: An attempt was made to grant or revoke SYSDG, SYSKM, SYSRAC, or SYSBACKUP administrative privileges to a user on an ASM instance.; Action: Do not attempt to grant SYSDG, SYSKM, SYSRAC, or SYSBACKUP administrative privileges on an ASM instance.
ORA-15374: invalid cluster configuration: Cause: The client instance detected an invalid configuration.; Action: Install and configure Oracle Grid Infrastructure and retry the operation. Refer to product documentation for more information.
ORA-15375: Physical sector size (string) cannot be smaller than the logical sector size (string).: Cause: An attempt was made to create or modify a disk group with a physical sector size value smaller than its logical sector size value.; Action: Review the SQL statement and fix any discrepancies.
ORA-15376: The existence of native disk 'string' does not allow disk group string from changing sector sizes. Sector size of native disk is string.: Cause: An attemp was made to change the physical or logical sector size value. Changing the sector size value is not allowed when there are native disks (physical sector equal to logical sector size) in the disk group, because this could cause invalid I/O operations.; Action: Drop the native disks or replace them for disks that support sector size emulation.
ORA-15377: Block size (string) for file 'string' is incompatible with the selected sector size (string).: Cause: The operation could not be completed because the sector size was incompatible for the specified file.; Action: Re-create or migrate the file to a block size that is compatible with the desired sector size, and redo the operation.
ORA-15378: Grid Naming Service operation failed with error string.\nstring: Cause: This is an internal error.; Action: Check the accompanying error messages. Contact Oracle Support Services.
ORA-15379: Cluster Credentials operation failed with error string.\nstring: Cause: This is an internal error.; Action: Check the accompanying error messages. Contact Oracle Support Services.
ORA-15380: invalid file group name specifier: Cause: The file group name specified was invalid.; Action: Specify a valid file group name.
ORA-15381: missing or invalid file group client specifier: Cause: The command did not specify a valid file group client string.; Action: Specify a valid file group client string with alphanumeric characters.
ORA-15382: invalid file group client name specifier: Cause: The file group name specified was invalid.; Action: Specify a valid file group name.
ORA-15383: invalid file group property 'string': Cause: An invalid property was specified for the Oracle Automatic Storage Management (Oracle ASM) file group.; Action: Check the Oracle documentation for valid Oracle ASM file group properties. The correct format of a valid Oracle ASM file group property is either file 'type.property_name' or 'property_name'.
ORA-15384: invalid file type 'string': Cause: An invalid file type was specified for the Oracle Automatic Storage Management (Oracle ASM) file group property.; Action: Check the documentation for valid Oracle ASM file types.
ORA-15385: file group 'string' does not exist: Cause: The specified file group did not exist within the disk group.; Action: Specify a file group that exists within the disk group.
ORA-15386: file group 'string' already exists in disk group 'string': Cause: A file group with the same name already exists.; Action: Select another file group name, or drop the existing file group. While creating non-CDB, multitenant container database (CDB), or pluggable database (PDB), manually create a file group for this non-CDB, multitenant container database (CDB), or pluggable database (PDB).
ORA-15387: existing files are associated with file group 'string': Cause: An attempt was made to drop a file group that contained existing files.; Action: Specify the CASCADE option to drop the file group and all of the associated files.
ORA-15388: A file type cannot be specified for file group property 'string'.: Cause: The specified file group property affects the file group itself or all files in the file group. It is not specific to a type of file.; Action: Remove the file type from the property name.
ORA-15389: missing or invalid file group property specification: Cause: The command did not specify a valid file group property name or a valid file group property value.; Action: Specify a valid file group property name and value pair.
ORA-15390: invalid value for file group property 'string': Cause: An invalid value was specified for the Oracle Automatic Storage Management (Oracle ASM) file group property.; Action: Check the documentation for acceptable values for this Oracle ASM file group property.
ORA-15391: cannot drop the default file group: Cause: The specified file group was created by the system and must always exist for proper operation.; Action: Specify another file group name.
ORA-15392: cannot alter the default file group: Cause: The specified file group was created by the system and must remain set to the default values for proper operation.; Action: Specify another file group name.
ORA-15393: File number 'number' does not exist in file group 'string'.: Cause: The specified file did not exist within the file group.; Action: Check the file number and the file group number.
ORA-15394: duplicate file group property 'string' specified: Cause: A command specified the same file group property more than once for the same file type.; Action: Specify only one file group property for each file type.
ORA-15395: file group redundancy incompatible with file type: Cause: An attempt was made to move a file to a file group with an incompatible redundancy specification, or to change the redundancy specification of a file group in a way that was incompatible with existing files in that file group.; Action: Specify a valid redundancy property for the file group. Only write-once files, such as the offline archive log and backup set, support parity protection. Other types of files must be configured with as unprotected, mirror or high redundancy. The file group redundancy can be changed from a parity protection scheme to unprotected, mirror, or high, and conversely, as long as the file group does not contain any files.
ORA-15396: command operates on only one file group property: Cause: More than one file group property was specified in the ADD FILEGROUP or MODIFY FILEGROUP statement.; Action: Specify only one file group property per statement.
ORA-15397: command requires all disks in disk group string to be online: Cause: The file group redundancy could not be changed to UNPROTECTED because some disks were offline.; Action: Retry the command after the offline disks are dropped.
ORA-15398: file group property 'string' is read-only: Cause: The specified file group property could not be changed.; Action: Retry the command providing a nonread-only file group property.
ORA-15399: New RDBMS compatibility '%0!s' exceeds client COMPATIBLE setting '%1!s'.: Cause: The specified value for the COMPATIBLE.RDBMS attribute exceeded the database COMPATIBLE setting for one or more clients.; Action: Verify the COMPATIBLE setting for each client of this disk group.
ORA-15400: not running on supported Oracle Automatic Storage Management (Oracle 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 partition string in Oracle ASM appliance 'string' contains more than one disk.: Cause: An attempt was made to add a disk to a slot and a partition number in the Oracle 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 and the partition number. 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-15421: string is not supported when the disk group is mounted for recovery.: Cause: The disk group was mounted for recovery preventing the requested operation.; Action: Dismount the disk group, remount it in normal mode and retry the operation.
ORA-15422: Disks 'string' and 'string', in failure group 'string' of disk group 'string', do not belong to the same cell: Cause: It was detected that disks from different cells belong to the same failure group.; Action: Make the necessary disk swaps so only disks from the same cell belong to the same failure group.
ORA-15423: Disk 'string' in failure group 'string' and disk 'string' in failure group 'string' of disk group 'string' belong to the same cell: Cause: It was detected that disks from the same cell belong to different failure groups.; Action: Make the necessary disk swaps so disks from the same cell are not shared between different failure groups.
ORA-15425: DB_UNIQUE_NAME conflict across clusters: Cause: The DB_UNIQUE_NAME parameter was specified with duplicate, conflicting or invalid attributes.; Action: Specify a different DB_UNIQUE_NAME.
ORA-15426: Slot string partition string in Oracle ASM appliance 'string' contains more than one disk.: Cause: An attempt was made to add a disk to a slot and a partition number in the Oracle ASM appliance that already had a disk (possibly OFFLINE) associated with it.; Action: Check the appliance configuration and retry the operation after inserting disks in the appropriate slots. If the disk that exists in the specified slot and the partition is dropping, then wait for the rebalance operation to finish before retrying the operation, or use FORCE to drop the existing disk and then retry the operation. Note that with FORCE drop, the redundancy of the diskgroup may be compromised until the rebalance operation completes. If the disk that exists in the specified slot and the partition is OFFLINE, then use REPLACE disk to replace the disk.
ORA-15430: missing or invalid quota group name: Cause: The command did not specify a valid quota group name.; Action: Specify a valid quota group name.
ORA-15431: missing or invalid quota group property: Cause: The command did not specify a valid quota group property.; Action: Specify a valid quota group property.
ORA-15432: missing or invalid quota: Cause: The command did not specify a valid quota limit for the quota group.; Action: Specify a valid quota limit.
ORA-15433: missing or invalid file group name: Cause: The command did not specify a valid file group name.; Action: Specify a valid file group name.
ORA-15434: quota group string already exists in disk group string: Cause: The specified quota group already existed in the disk group.; Action: Specify a different quota group name.
ORA-15435: quota group string does not exist in disk group string: Cause: The specified quota group did not exist in the disk group.; Action: Specify a valid quota group name.
ORA-15436: invalid operation on quota group string: Cause: The specified operation was not permitted on the quota group.; Action: Check the quota group specified in the command.
ORA-15437: insufficient quota available in quota group string: Cause: The specified quota group did not have sufficient quota available to permit the operation.; Action: Specify a quota group with enough available quota or increase the quota limit of the specified quota group.
ORA-15438: Quota group string has one or more file groups associated.: Cause: One or more file groups were associated with the specified quota group and, therefore, the operation was not permitted.; Action: Drop the file groups or move the file groups to a different quota group.
ORA-15440: Volume I/O background process (VIO0) terminated with an error: Cause: A volume I/O background process terminated with an error.; Action: The process will restart automatically, no action is needed. If the issue persists, check the log files for the cause. Contact Oracle Support Services if additional assistance is needed.
ORA-15442: The ASM rebalance phase string does not exist.: Cause: The specified ASM rebalance phase did not exist.; Action: Specify a valid rebalance phase.
ORA-15443: The ASM rebalance phase string cannot be skipped.: Cause: The specified ASM rebalance phase cannot be skipped.; Action: Specify a valid rebalance phase to skip.
ORA-15444: Volume string must be online and mounted to complete the operation.: Cause: The operation could not be completed with the volume offline or dismounted.; Action: Ensure that the volume is online or mounted, and retry the operation.
ORA-15445: Volume string does not allow sector size migration.: Cause: Sector size migration was not allowed because either of the following existed in the disk group: * Oracle ACFS accelerator volumes, or * Volumes associated with an Oracle ACFS accelerator, or * Non-Oracle ACFS volumes; Action: Move the volume to a different disk group, and retry the operation.
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 an alphabet: Cause: The first letter of the volume name was not an alphabetic character.; Action: Specify an alphabetic character as the first letter of the volume name.
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 and 8K.
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 value and retry the operation.
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: Specify 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: Specify 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 disk group string is currently being accessed.: Cause: An attempt was made to change a volume that 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. The following restrictions apply: - An unprotected redundancy volume cannot be added to a normal or high redundancy disk group. - A mirror or high redundancy volume cannot be added to an external redundancy disk group. - A mirror volume cannot be added to a high 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: USAGESTRING is greater than string characters: Cause: The optional attribute --USAGESTRING specified while updating Oracle ADVM attributes was too long.; Action: Select a smaller value for the --USAGESTRING attribute and retry the operation.
ORA-15476: Oracle ACFS volumes must be resized with the 'acfsutil size' operating system command.: Cause: An attempt was made to resize an Oracle ASM Dynamic Volume Manager (Oracle ADVM) volume that contained an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) file system using SQL statements.; 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: Verify if the Oracle Automatic Storage Management (ASM) volume driver is loaded. If the Oracle ASM volume driver is loaded, then check the alert log to identify the reason for failure and perform the necessary action to prevent such failures in the future.
ORA-15478: The Oracle Automatic Storage Management Cluster File System (ACFS) background process terminated with an error.: Cause: The Oracle ACFS background process terminated with an error.; Action: Wait for process restart. If the error persists, contact Oracle Support Services.
ORA-15479: Oracle Automatic Storage Management (Oracle ASM) disk group does not support volumes.: Cause: Volumes were not supported. A typical example was having disks, such as Network File System (NFS) in the disk group that was not supported by volumes.; Action: Remove unsupported disks in the disk group.
ORA-15480: Error reported by the Oracle Automatic Storage Management (ASM) volume driver.: Cause: An error was reported by the Oracle ASM volume driver.; Action: Check the operating system log files to identify the reason for the error. Perform the action or actions to prevent future errors.
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 or remove device file for volume string on diskgroup string: Cause: The driver was improperly installed.; Action: Check the alert log for information on the failure of device file creation. 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 disk group exceeds the maximum of string: Cause: A volume was added on a disk group that already contained the maximum number allowed.; Action: Remove one or more volumes from the disk group.
ORA-15486: internal error while altering volume: Cause: An internal Oracle Automatic Storage Management (Oracle 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: Oracle Automatic Storage Management (ASM) volume string is open on node string.: Cause: The ASM volume was not closed prior to instance termination on the specified node.; Action: Close the ASM volume either via unmount or node restart and retry.
ORA-15489: conflicting volume already open on this node: Cause: An Oracle Automatic Storage Management (Oracle ASM) volume was not closed prior to an instance shutdown on the specified node. It conflicted with the volume that was to be enabled.; Action: Close the Oracle ASM volume either using UNMOUNT or node restart and retry the operation.
ORA-15490: not all instances could add or drop the volume: Cause: The Oracle Automatic Storage Management (Oracle ASM) volume could not be added or dropped on all instances.; Action: See the alert log for the reason the volume could not be added or dropped.
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: Specify a smaller volume size and retry the operation.
ORA-15497: Volume string uses a metadata block size (string) smaller than the specified sector size (string).: Cause: The Oracle ACFS volume had a metadata block size incompatible with the specified sector size.; Action: Migrate Oracle ACFS to a larger metadata block size before changing the sector size.
ORA-15498: Volume name string collides with existing volume(s) string string.: Cause: The operation attempted to create a block device and a raw device with the volume name <vol_name>-<dg_num>, which conflicted with an existing volume name.; Action: Choose another name for the volume (no leading 'r' is recommended).
ORA-15499: VMB process terminated with error: Cause: The volume membership (VMB) process terminated with an 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 encountered ORA-string error.: Cause: One of the parallel preprocessing workers ended unexpectedly while processing the workload.; Action: Find the root cause or preprocess the workload using a single 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 error.: Cause: An error occurred during parallel preprocessing.; Action: Find the root cause or preprocess the workload using a single 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-15523: Failed to create subpath string under path string.: Cause: Either the path does not exist, is inaccessible, or the subpath specification is invalid.; Action: Verify that the path exists and is accessible, the subpath specification is valid, and retry the command.
ORA-15525: a user call cannot be replayed because not enough information was captured; extra details: string: Cause: An attempt to replay a user call failed because the workload was captured with an old version of Oracle. The information needed for replay was not recorded.; Action: Capture the workload using a newer version of Oracle or use the replay filters to skip the user call.
ORA-15526: failed to validate user password for capture: Cause: One of the following occurred: 1- The password was not specified for the encrypted capture. 2- The password did not match the one used for the encrypted capture. 3- The specified password was for an unencrypted capture.; Action: For scenario 1 or 2 stated in the Cause, provide the correct password for the encrypted capture. For scenario 3, do not specify the client single sign-on (SSO) wallet path.
ORA-15527: failed to retrieve password for Database Replay from Oracle Wallet: Cause: Either the Database Replay identifier was not found in the Oracle Wallet or the password was not set.; Action: Set the password for the Database Replay identifier in the Oracle Wallet.
ORA-15528: failed to encrypt a workload capture: "string": Cause: An attempt to encrypt a workload capture failed. Possible reasons are included in the error message.; Action: Fix the issue and retry.
ORA-15529: failed to decrypt a workload capture: "string": Cause: An attempt to decrypt a workload capture failed. Possible reasons are included in the error message.; Action: Fix the issue and retry.
ORA-15530: Directory contains a capture recorded with a newer Oracle release.: Cause: The capture was recorded with a newer Oracle release.; Action: Retry with a newer release of Oracle.
ORA-15531: workload capture encountered unexpected error: string: Cause: Workload capture encountered an unexpected error.; Action: Check the server trace files to address the reported error.
ORA-15532: workload replay encountered unexpected error: string: Cause: Workload replay encountered an unexpected error.; Action: Check the server trace files to address the reported error.
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 an existing work directory, or ensure that the user has access privileges.
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. Ensure that the replay user can access SYS-owned objects and has been granted the 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-15570: Directory object "string" does not exist.: Cause: The directory object did not exist.; Action: Ensure that the specified directory object exists.
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: corrupt workload capture files: Cause: The captured workload contained one or more corrupt recording files.; Action: Check the alert log for lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing. The files will be replayed up to the point of the corruption. You could also remove the corrupt files and run DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE again. In this case, no workload from the corrupt files is 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-15606: Reserved autotask operations only allowed in root.: Cause: An attempt was made to issue a reserved autotask operation in a pluggable database.; Action: Switch to CDB$ROOT and issue the operation.
ORA-15607: Autonomous task could not be scheduled. Reason: "string".: Cause: An attempt was made to schedule a manual Autonomous task but the operation failed. The possible causes were: - The task was disabled. - The task was currently running in another process. - The number of concurrently running autonomous tasks exceeded max limit.; Action: Check the task status in adb_task views. Ensure that: - The task is enabled. - The task is not currently running in another process. - The number of concurrently running autonomous tasks is within max limit. Then, retry the operation.
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-15704: This operation is not supported for Oracle RAS users.: Cause: An attempt was made to execute an unsupported operation. This operation is not supported for Oracle Real Application Security (Oracle RAS) users.; Action: Retry the operation as a non-Oracle RAS user.
ORA-15705: staging table does not exist: Cause: An attempt was made to use a staging table that did not exist.; Action: Verify the name of the staging table and retry the operation.
ORA-15706: concurrent execution of the task terminated unexpectedly: Cause: Parallel slaves have died unexpectedly.; Action: Check your system for anomalies and resume the executing task.
ORA-15738: Default parameters for SPA Quick Check are not set.: Cause: The required default parameters for SQL Performance Analyzer Quick Check (SPA Quick Check) were not set.; Action: Set default values for all of the required SPA Quick Check parameters 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-15748: invalid container name specified: Cause: The container name specified for this API was invalid. When this API is run at the multitenant container database (CDB) root, the acceptable container names are any valid containers in that CDB. When it is run in a pluggable database, the only acceptable container name is its own name.; Action: Specify a valid container name.
ORA-15750: current node is not configured for remote operations: Cause: An attempt to perform a Remote Management Framework (RMF) operation failed because the node performing the operation was not yet configured for remote operations.; Action: Configure the node and retry the operation.
ORA-15751: The RMF operation failed.: Cause: An attempt to perform a Remote Management Framework (RMF) operation failed because an unexpected error condition happened.; Action: Retry the operation and contact Oracle Support Services if the condition persists.
ORA-15755: current node is already configured for remote operations: Cause: An attempt to configure a node failed because the node was already configured for Remote Management Framework (RMF) operations.; Action: Unconfigure the node and retry the operation.
ORA-15761: not registered in an RMF topology: Cause: An attempt to perform a Remote Management Framework (RMF) operation failed because the node performing the operation was not registered in a topology.; Action: Register the node in a topology or create a new topology and retry the operation.
ORA-15764: concurrent RMF operation is in progress: Cause: An attempt to perform a Remote Management Framework (RMF) operation failed because another conflicting operation was already running.; Action: Retry after the conflicting operation has finished.
ORA-15766: already registered in an RMF topology: Cause: An attempt to register the specified node failed because the node was already registered in a Remote Management Framework (RMF) topology.; Action: Ensure that the specified node name matches the node to be registered and that the database link connects to the intended node. Unregister the specified node before registering it into another topology.
ORA-15767: RMF topology [string] does not exist.: Cause: A topology with the specified topology name was not created in the Remote Management Framework (RMF).; Action: Verify that the topology name is valid and retry the operation.
ORA-15768: RMF topology [string] already exists.: Cause: A topology with the specified topology name was already created in the Remote Management Framework (RMF).; Action: Verify that the topology name is valid and retry the operation. Specify a different topology name that has not been used yet.
ORA-15769: node [string] is not registered in RMF topology [string]: Cause: A node with the specified node name was not registered in the specified Remote Management Framework (RMF) topology.; Action: Ensure that the specified node name and topology name is correct, and that the specified node is currently registered in the specified topology.
ORA-15770: node [string] is already registered in RMF topology [string]: Cause: A node with the specified node name was already registered in the specified Remote Management Framework (RMF) topology.; Action: Ensure that the specified node is not currently registered in the specified topology and that the node to be registered in the specified topology is configured with a unique name.
ORA-15771: parameter [string] is invalid: string: Cause: The value for the specified parameter was invalid.; Action: Provide a value that fulfills the requirements specified in the error message.
ORA-15772: parameter [string] exceeds string characters: Cause: The value for the specified string parameter was too long.; Action: Provide a value for the specified parameter that has a length below the character limit specified in the error message.
ORA-15773: parameter [string] does not allow NULL values: Cause: A NULL value was provided for the specified parameter but the parameter only allows non-NULL values.; Action: Provide a non-NULL value for the specified parameter.
ORA-15774: parameter [string] conflicts with the value in the remote node [string]: Cause: An attempt to perform a Remote Management Framework (RMF) operation failed because the specified parameter was different from the actual value stored in the node performing the operation.; Action: Ensure that the database link connects to the intended node and that the specified parameter matches the value configured in the node that will perform the operation.
ORA-15775: database not open in read/write mode: Cause: An attempt to perform a Remote Management Framework (RMF) operation failed because the node was not open in read/write mode.; Action: Ensure that the node performing the operation is open in the correct mode and retry the operation.
ORA-15776: candidate target missing links to source nodes: Cause: An attempt to perform a Remote Management Framework (RMF) destination switch failed because the candidate target couldn't find a link to one or more nodes in the topology.; Action: Ensure the candidate target has an RMF link to every node participating in the topology and retry the operation. If the current RMF destination node is no longer available or the missing links cannot be created at this moment, retry the operation with FORCE_SWITCH to bypass this check.
ORA-15777: remote node registration could not be completed: Cause: An attempt to register a node in a Remote Management Framework (RMF) topology failed because the remote node could not obtain the registration information from the RMF destination node.; Action: Ensure that the provided database links are valid and correspond to the intended nodes. Check for additional error messages, if any, to to determine the exact cause of the problem and correct the error. Unregister the node from the topology and retry the operation.
ORA-15900: AWR Analytics operation failed: string: Cause: An attempt to perform an Automated Workload Repository (AWR) Analytics Framework operation failed because an unexpected error condition happened.; Action: Correct the indicated problem and retry the operation. Contact Oracle Support Services if the condition persists.
ORA-15901: error encountered during SQL execution: Cause: An error occurred when performing an Automated Workload Repository (AWR) Application Framework operation due to an underlying SQL execution error.; Action: Retry the operation and contact Oracle Support Services if the condition persists.
ORA-15902: parameter [string] is invalid: string: Cause: The value for the specified parameter was invalid.; Action: Provide a value that fulfills the requirements specified in the error message.
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 required recovery, and therefore could not be opened for read-only access by this instance.; Action: If the database was terminated abnormally (possibly using a shutdown abort), the database first needs to be opened in read/write mode. Otherwise, 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: Either the redo transport destination could not accept redo data because it was not a valid redo transport destination type, or the connection was SYNC for Zero Data Loss Recovery Appliance (ZDLRA) destination.; Action: Verify that all redo transport destinations are either standby databases or downstream capture databases, or change the ZDLRA destination to not use SYNC.
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 target physical standby, snapshot standby, or far sync did not match that of the primary database. See the alert log file for additional information.; Action: Ensure that the database identifier of each physical standby, snapshot standby, and far sync 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 specified 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 already dependent on it.; Action: Ensure that no redo transport destination is dependent on any destination that is already 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: Ensure that 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: Cannot archive an empty or invalid log file.: Cause: Attempted to archive an empty or invalid log file. See trace file or alert log file for additional information.; Action: No action needed.
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-16064: Data Guard network decompression failed.: Cause: The incoming network buffer containing compressed redo could not be decompressed. See the alert log for additional information.; Action: As a workaround, disable compression on the database that is sending this redo, then call Oracle Support Services.
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 was already registered.: Cause: Attempted to register an archive log that matched a branch, thread, and sequence entry in the control file.; Action: Use 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 process.; 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 recovery is not active.: Cause: Attempted to cancel a managed recovery session but no managed recovery session was active.; Action: No action needed.
ORA-16137: invalid state change to a managed alternate destination: Cause: An attempt was made to explicitly change the state of a destination participating in an internally managed set of alternate destinations. For example, a destination in the ALTERNATE state was explicitly ENABLED. Doing so will thwart the internal mechanisms to manage these cooperating destinations.; Action: The destination must be reset before making this state change.
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: string control file enqueue unavailable: Cause: The control file enqueue was currently unavailable.; Action: No Action is required. The operation will be attempted 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: The RECOVER...FINISH request is not allowed due to gap in thread string, sequences string-string.: Cause: The specified RECOVER...FINISH request is not allowed due to a gap in redo. See the alert log for additional information.; 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 redo log files missing on the standby.
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 were inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.; Action: Ensure that 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 apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details.
ORA-16227: DDL skipped due to missing object: Cause: A table or other database object upon which this DDL depended was not defined on the Logical Standby database.; Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16228: Insufficient recovery for logical standby: Cause: Insufficient amount of recovery was run for logical standby instantiation.; Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.
ORA-16229: PDML child string string string for parent string string string cannot be skipped.: Cause: A request was made to skip a parallel DML child transaction id. This is not supported.; Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.
ORA-16230: committing transaction string string string: Cause: Logical Standby apply was committing changes for the given transaction.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16231: Zero Data Loss Recovery Appliance (ZDLRA) is shutdown.: Cause: ZDLRA was shutdown, and is not accessible for 10 minutes.; Action: Automatic attempts to access the ZDLRA occurs every 10 minutes or the LOG_ARCHIVE_DEST_STATE_n parameter can be set to ENABLE to clear the error state.
ORA-16232: adding Logical Standby skip entry for table string.string: Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.; Action: To have Logical Standby maintain the table, import that table directly from the primary.
ORA-16233: The table string.string is unsupported now: Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.; Action: None
ORA-16234: restarting to reset Logical Standby apply: Cause: Logical Standby encountered a work load that required a restart to properly reschedule.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16235: DDL skipped because import has occurred: Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16236: Logical Standby metadata operation in progress: Cause: The requested operation failed because an incompatible Logical Standby metadata operation such as DBMS_LOGSTDBY.SET_TABLESPACE, DBMS_LOGSTDBY.APPLY_SET or DBMS_LOGSTDBY.INSTANTIATE_TABLE was still running.; Action: Wait for the incompatible Logical Standby metadata operation to finish, then reenter or respecify the operation.
ORA-16237: SGA specified for Logical Standby is too small: Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.; Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes.
ORA-16238: attempt to use version 9 log: Cause: Version 9 log files are not supported.; Action: Use log files of a supported version.
ORA-16239: IMMEDIATE option not available without standby redo logs: Cause: The IMMEDIATE option cannot be used without standby redo logs.; Action: Do not specify the IMMEDIATE option unless standby redo logs are being used.
ORA-16240: Waiting for log file (thread# string, sequence# string): Cause: Process is idle waiting for additional log file to be available.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16241: Waiting for gap log file (thread# string, sequence# string): Cause: Reader process was idle waiting for the log file to fill the log sequence gap.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16242: Processing log file (thread# string, sequence# string): Cause: Reader process was processing the log file.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16243: paging out string bytes of memory to disk: Cause: Builder process is paging out momery to free up space in lcr cache.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16245: change db_name to string in the server-side parameter file (SPFILE): Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a modifiable server parameter file (SPFILE).; Action: The server-side parameter file must be modified so that db_name is set to the given name before mounting the database again. You must do this by executing CREATE PFILE FROM SPFILE, editing the resulting text parameter file, and then executing CREATE SPFILE FROM PFILE.
ORA-16246: User initiated abort apply successfully completed: Cause: SQL Apply was stopped using the abort option.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16247: DDL skipped on internal schema: Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = 'INTERNAL SCHEMA'.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16248: RFS connections not permitted during Terminal Apply: Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.; Action: Permit any outstanding Logical Standby operations to complete.
ORA-16249: Terminal apply failed to complete during failover: Cause: The logical standby coordinator process terminated abnormally."; Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover.
ORA-16250: Failed to acquire starting scn of new log stream: Cause: The starting SCN for the new log stream could not be determined.; Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.
ORA-16251: LSP1 Background Build not permitted: Cause: The LSP1 background process is not permitted to start because it had previously been attempted.; Action: This is an internal error. Contact Oracle support.
ORA-16252: Rebuild operation not permitted: Cause: The REBUILD operation is not permitted.; Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.
ORA-16253: Logical standby cannot start due to a prior, incomplete operation: Cause: A failure during a prior failover or configuration-related operation left the logical standby in an inconsistent state.; Action: Identify and reissue the operation before attempting to restart the logical standby apply engine.
ORA-16254: change db_name to string in the client-side parameter file (pfile): Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile).; Action: The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again.
ORA-16255: Log Auto Delete conflicts with another LogMiner session: Cause: Log Auto Delete cannot be on while another LogMiner session is running on the same database.; Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.
ORA-16256: Failure to complete standby redo log file archival after failover: Cause: The standby redo log files processed during the failover of a logical standby were not archived.; Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.
ORA-16257: Switchover initiated stop apply successfully completed: Cause: SQL Apply was stopped because of a switchover.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16258: marking index unusable due to a constraint violation: Cause: A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.; Action: No action necessary. See alert log for index schema and name.
ORA-16259: Switchover to logical standby requires a log archive destination: Cause: A valid log archive destination was not found to which the local system could archive the end of redo (EOR) log file. A minimum of one destination is required.; Action: Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before reissuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation.
ORA-16260: Waiting to replace partial or corrupt log file (thread# string, sequence# string): Cause: LogMiner Reader process reached the end of a partial log file or encountered a corrupted block. It is now waiting for the log file to be recovered and reregistered.; Action: No action necessary. Once the fetch archive log (FAL) archiver replaces the log file, standby will automatically restart to process the replaced file.
ORA-16261: Identification key mismatch for table "string"."string".: Cause: Internal error in SQL Apply.; Action: Contact Oracle Support Services.
ORA-16262: Invalid value specified for Logical Standby parameter: Cause: The value specified in APPLY_SET is invalid for the parameter.; Action: Specify correct parameter value. Please refer to documentation on DBMS_LOGSTDBY PL/SQL package for details.
ORA-16263: Dynamic parameters can only be set on SQL apply instance: Cause: Attempt to set a Logical standby dynamic parameter on an instacne other than where SQL apply coordinator is running.; Action: Connect to the instance where SQL apply coordinator is running and reissue the statement.
ORA-16264: invalid value for PREPARE_SERVERS parameter: Cause: attempt to set PREPARE_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.; Action: set PREPARE_SERVERS parameter to a non zero value and or increase MAX_SERVERS parameter accordingly.
ORA-16265: Unsupported PL/SQL procedure encountered: Cause: Apply encountered an unsupported procedure from an Oracle supplied PL/SQL package that is otherwise supported; Action: Either add a skip rule for this procedure or manually apply the procedure and restart apply skipping the failed transaction Please refer to documentation on the PL/SQL package for details.
ORA-16266: Cannot instantiate a Logical Standby from another Logical Standby: Cause: An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported.; Action: Instantiate a Logical Standby database only from a Primary Database.
ORA-16267: Cannot instantiate a Logical Standby during a switchover: Cause: An instantiation of a Logical Standby has been attempted for a primary database that is in the middle of a switchover.; Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel the switchover, and attempt the instantiation again.
ORA-16268: user procedure processing of logical standby apply PL/SQL: Cause: A user-provided stored procedure was called to inspect a PL/SQL statement prior to the statement 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-16269: PL/SQL procedure skipped due to failure on primary database: Cause: Because the PL/SQL procedure failed when executed on the primary database, it could not be executed on the standby database.; Action: This informational statement is provided to record the event for diagnostic purposes. The failed PL/SQL procedure needs to be investigated to ensure it did not commit interesting data before it failed.
ORA-16270: PL/SQL procedure skipped due to unmaintained standby objects: Cause: Because the PL/SQL procedure manipulated objects not being maintained by the standby database, it was skipped.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16271: PL/SQL successfully applied: Cause: A PL/SQL procedure was successfully applied on the logical standby database.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16272: PL/SQL procedure skipped due to skip setting: Cause: A setting in the logical standby skip table indicated that this PL/SQL procedure should always be skipped.; Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16273: invalid value for APPLY_SERVERS parameter: Cause: attempt to set APPLY_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.; Action: set APPLY_SERVERS parameter to a non zero value or increase MAX_SERVERS parameter accordingly.
ORA-16274: failure to perform operation on all Oracle RAC instances: Cause: One or more instances encountered an error while performing an operation.; Action: Ensure every instance in the Oracle RAC meets the requirements for the operation, and retry the operation.
ORA-16275: prior failed CTAS detected and pre-existing table dropped: Cause: During the processing of a CTAS operation, an existing empty table with the same name and attributes as the CTAS source table was found, and the table was dropped.; Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16276: specified database link does not correspond to primary database: Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did not link to the primary database for this logical standby database.; Action: Specify a database link that corresponds to the primary database for this logical standby database. The link should have privileges to read and lock the table being instantiated, as well as the SELECT_CATALOG_ROLE.
ORA-16277: specified table is not supported by logical standby database: Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate an unsupported table on the logical standby database. Tables with unsupported data types cannot be replicated to a logical standby database.; Action: Specify a table which is not listed in the DBA_LOGSTDBY_UNSUPPORTED_TABLE view.
ORA-16278: specified table has a multi-object skip rule defined: Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE must not have any skip rules defined with wildcard characters.; Action: Remove or rewrite any skip rules defined for the specified table so that they no longer contain wildcard characters, or no longer affect the specified table.
ORA-16279: supplied dblink does not have sufficient privileges: Cause: A dblink was specified that lacked one or more of the CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles or that connects to a user with insufficient privileges to lock the table.; Action: Grant the necessary privileges to the dblink and the user to which the dblink connects and retry the operation.
ORA-16280: cannot change master key on a logical standby database: Cause: An attempt was made to change the master key for transparent data encryption on a logical standby database.; Action: Set GUARD to NONE and reissue the command. This prevents you from replicating tables with encrypted columns from the primary database.
ORA-16281: missing identification key for table "string"."string".: Cause: No identification key was created for specified table.; Action: Create a primakey key or unique index for specified table.
ORA-16282: operation not permitted during rolling upgrade: Cause: An operation was attempted that is not supported during a rolling upgrade.; Action: Retry the operation upon completion of the upgrade.
ORA-16283: operation not permitted on non-apply instance: Cause: An operation was attempted that is not supported since it requires a running logical apply on the local instance.; Action: Retry the operation on the instance on which the apply engine is running.
ORA-16284: timed out waiting for an in-progress operation to complete: Cause: An operation timed out waiting for another operation to complete.; Action: Retry the operation when the in-progress operation has completed.
ORA-16285: operation not permitted due to inconsistent role state: Cause: A prior attempt to change the role of this database has failed before the new role state could be fully committed.; Action: Retry the previously attempted role-related operation before attempting the current operation.
ORA-16286: operation not permitted due to lack of synchronized destination: Cause: A synchronized log archive destination was not found to which the end-of-redo log file could be archived.; Action: Before re-attempting the operation, wait at least one minute for the Remote File Server to automatically recover any missing log files or manually recover and register any missing log files with logical standby.
ORA-16287: operation not permitted due to active apply state: Cause: An operation was attempted that was not supported while the logical standby database had an active apply state.; Action: Confirm the procedures used to configure the logical standby database. Procedures which attempt to reconfigure a logical standby database for a new primary database may encounter this error if an error in a preliminary step was encountered.
ORA-16288: DDL skipped due to missing edition "string": Cause: The edition in which the DDL was performed on the primary did not exist on the standby database.; Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16289: unable to access Pluggable Database "string": Cause: Logical standby attempted to access a Pluggable Database that did not exist.; Action: Create or plug in the specified Pluggable Database or add an appropriate skip rule and then restart logical standby.
ORA-16290: cannot alter the session logical replication state within a transaction: Cause: A transaction was already in progress.; Action: Commit or rollback the transaction and then reexecute.
ORA-16291: operation not permitted due to incomplete setup: Cause: An operation was denied due to the logical standby being in a transitional state.; Action: Perform any multistep procedures such as instantiation, switchover, or failover to completion as written in the documentation.
ORA-16292: cannot replicate ALTER TABLE ADD COLUMN with sequence default value: Cause: The logical standby database attempted to replicate an unsupported DDL statement. The DDL added a column with a sequence as the default with compatiblity set to a release earlier than 12.2.0.2.0.; Action: The table must be re-instantiated from the primary database using DBMS_LOGSTDBY.INSTANTIATE_TABLE().
ORA-16293: cannot replicate a failed ALTER TABLE ADD COLUMN: Cause: The logical standby database attempted to replicate a failed ALTER TABLE ADD COLUMN for an identity column, but the operation could not be rolled back on the target.; Action: The added columns must be dropped from the table on the target before restarting apply, or the table must be reinstantiated.
ORA-16294: operation not allowed on a LogMiner table: Cause: An attempt was made to use the SQL command ALTER TABLE or DROP TABLE on a table used for LogMiner metadata.; Action: Connect as SYS to perform this operation.
ORA-16295: cannot create a synonym with same name as LogMiner table: Cause: An attempt was made to create a synonym with the same name as a table used by LogMiner.; Action: Choose a different name for the synonym.
ORA-16300: LSBY architected tracing event
ORA-16302: extended data type support is not supported for specified table: Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that was not supported for such an operation. The table either does not have a primary key or it has a data type not supported by this procedure.; Action: Specify a table for which support exists in EDS_ADD_TABLE.
ORA-16303: specified table already has extended data type support: Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that already had EDS added on the local database.; Action: None
ORA-16304: procedure must first be called on primary database: Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical standby database without having first called it on the primary database.; Action: Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and then retry on the standby.
ORA-16305: procedure not supported on a logical standby: Cause: A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical standby database which can only be called on a primary database; Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database
ORA-16306: specified table does not have a primary key: Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that did not have a primary key.; Action: Add a primary key and retry the operation.
ORA-16307: TSE key string successfully applied: Cause: An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully committed on the logical standby database.; Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16308: specified table has extended data type support: Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table that is being maintained by extended data type support.; Action: Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation.
ORA-16309: extended data type support evolve operation not yet started: Cause: A call was made to finish an extended data type support evolve operation without having first started the operation.; Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with START option and then retry.
ORA-16310: extended data type support evolve operation in progress: Cause: An extended data type support evolve operation was started but not yet completed.; Action: Wait a few seconds and retry the command if automatic evolve has been enabled or call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with the FINISH option and then retry.
ORA-16311: materialized view log already exists: Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table with a LOB that requires the creation of a specifically-defined materialized view log but one already exists.; Action: Drop the existing materialized view log and retry the operation.
ORA-16330: error in container "string": Cause: An operation was attempted on a container and an error occurred.; Action: Address the failure condition and then retry.
ORA-16331: container "string" is not open: Cause: An operation was attempted on a container. However, the container was not open.; Action: Open the container and then retry.
ORA-16332: logical standby encountered non-fatal error ORA-string during DDL execution: Cause: Logical standby apply encountered a non-fatal error during DDL execution and continued to process subsequent transactions.; Action: This error is informational only. No user action is required.
ORA-16333: _MAX_LOG_LOOKBACK parameter not sufficiently larger than MAX_SGA: Cause: _MAX_LOG_LOOKBACK or MAX_SGA parameter was set to a value that will lead to decreased performance.; Action: Reset parameters such that _MAX_LOG LOOKBACK is at least 5 times the value of MAX_SGA.
ORA-16334: skip procedure does not exist: Cause: The specified skip procedure did not exist.; Action: Ensure that the specified skip procedure exists and is accessible by the calling user.
ORA-16393: Redo log management parameter setting is invalid.: Cause: The value specified for the redo log management parameter had invalid attributes or was not specified with SID='*' in a cluster configuration.; Action: Check the documentation regarding the correct specification for redo log management.
ORA-16395: ADG standby session terminated: Cause: ADG standby session was stopped because server detected that the primary database connection associated with redirected statement execution is lost.; Action: Reconnect to ADG standby database and re-run the statement.
ORA-16397: statement redirection from Oracle Active Data Guard standby database to primary database failed: Cause: The statement redirection failed because of one of the following reasons: 1. The primary database connect string was not established. 2. The primary database could not be reached. 3. The undo-mode or incarnation were not the same. 4. The current user and logged-in user were not the same. 5. Redirecting PL/SQL execution having bind variable was not supported.; Action: Run the statement after fixing the condition that caused the failure.
ORA-16398: online log has been reused and archived log cannot be found: Cause: ASYNC redo transport was unable to find either an online log or archived redo log that represents the current live redo sequence number.; Action: No action is required.
ORA-16399: current redo has moved to a new branch: Cause: A new branch was detected by ASYNC redo transport. No further redo will be transferred from the old branch. ASYNC redo transport will commence on the new branch.; Action: No action is required.
ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST: Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.; Action: No action is required.
ORA-16401: archive log rejected by Remote File Server (RFS): Cause: An attempt was made to re-archive an existing archive log.; Action: See alert log and trace file for more details. No action is necessary. This is an informational statement provided to record the event for diagnostic purposes.
ORA-16402: TRANSPORT=ONDEMAND is unsupported.: Cause: The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was specified on the primary database.; Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16403: shut down in progress - remote connection is not permitted: Cause: A redo transport session could not be started because the database was shutting down.; Action: Wait for the remote instance to be restarted, or contact your DBA.
ORA-16406: primary and standby database software version mismatch: Cause: The primary and standby databases were not running compatible versions of Oracle server software.; Action: Install the correct Oracle server software and try again.
ORA-16407: An archive log from an earlier redo branch has been rejected: Cause: An archive log from a redo branch that is earlier than the one that the standby database is currently applying was rejected.; Action: No action is required.
ORA-16408: Archive log from an incompatible redo branch has been rejected.: Cause: An archive log from a redo branch was rejected. The redo branch was incompatible with the standby database where it was attempted to be applied.; Action: No action is required.
ORA-16409: archive log switchover reference number mismatch: Cause: The archive log switchover reference numbers of the primary and standby database did not match. Remote archival of redo log files is not allowed to incompatible standby database instances.; Action: No action is required.
ORA-16411: TRANSPORT=ONDEMAND is unsupported: Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.; Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16412: TRANSPORT=ONDEMAND is unsupported: Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.; Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16413: TRANSPORT=ONDEMAND is unsupported: Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.; Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16416: no viable stringswitchover targets available: Cause: Switchover failed because standby databases of the appropriate type were not available.; Action: Check the alert log for errors, correct the problem, and retry the switchover.
ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required: Cause: Activation occurred after recovery from standby redo log files.; Action: Take a full database backup.
ORA-16419: Snapshot standby must be converted to a physical standby database.: Cause: The database was not a physical standby database.; Action: Convert to physical standby database and retry the operation.
ORA-16420: fast-start failover target cannot be converted to snapshot standby: Cause: The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.; Action: Choose another physical standby database and retry the operation.
ORA-16424: RECOVER FINISH cannot complete due to a redo gap.: Cause: RECOVER FINISH failed because there was a redo gap on the standby database.; Action: Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE to perform an immediate failover with some data loss.
ORA-16425: a RECOVER FINISH failed because recovery incarnation string is not the target incarnation string: Cause: RECOVER FINISH failed because a new incarnation existed on the physical standby database. This situation could happen if two failures occurred in a short time and the current failover target was still in the previous incarnation.; Action: Issue real-time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
ORA-16426: recovery requested an incorrect log from which to recover redo: Cause: Media recovery selected an incorrect log. See the alert log file for additional information.; Action: Verify that the appropriate log has been properly registered and restart media recovery.
ORA-16427: Redo gap is too large to resolve.: Cause: The redo transport lag at this database was too large for automatic redo gap detection to take place.; Action: Re-create this standby database from a current backup copy of the primary database.
ORA-16431: cannot expand control file: Cause: Additional redo log threads were added on the primary database after the standby control file was created.; Action: Shut down the standby database and replace the control file with a new standby control file from the primary database or change the COMPATIBLE parameter to 10.2.0 or above and restart the standby database.
ORA-16432: inconsistent set of logs applied at a standby database: Cause: Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.; Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
ORA-16433: The database or pluggable database must be opened in read/write mode.: Cause: An attempt was made to open the database or pluggable database in read-only mode after an operation that requires the database or pluggable database be opened in read/write mode.; Action: Open the database in read/write mode. The database can then be opened in read-only mode.
ORA-16434: archive log for branch string thread string sequence string cannot be queued: Cause: An archive log needed by the standby database to resolve a redo gap was not found on the source database. This is a fatal situation during a switchover or far sync instance assisted failover because the source database waits for the target standby to be clear of all archive log gaps before allowing the operation to proceed. If a redo gap cannot be resolved during these operations, the operation cannot succeed so it must be failed.; Action: If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the local destination on the source database but no longer exists at that location on disk, the archived log can be copied back to that location to allow gap processing to automatically resolve the gap. If the specified log has been purged from V$ARCHIVED_LOG, the archived log can be copied to disk on either the source or destination database and registered using the ALTER DATABASE REGISTER OR REPLACE LOGFILE command.
ORA-16436: an ALTER DATABASE...RECOVER FINISH request could not start: Cause: ALTER DATABASE...RECOVER FINISH failed to start because the standby database was missing redo changes below the checkpoint of data files or because there was no standby redo log file available to create an EOR log. See the trace file for additional information.; Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead or add one or more standby redo logs and retry command.
ORA-16437: No active coordinator RFS for current operation: Cause: The coordinator Remote File Server (RFS) for this parallel archival either abnormally terminated or ran down before this subordinate RFS could begin its leg of the operation.; Action: No explicit user action is required.
ORA-16438: Switchover to primary cannot be executed at this time: Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details.; Action: Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
ORA-16439: Standby not ready to receive redo at this time: Cause: A logical standby or down stream capture database was not in a state where it could accept a request to receive redo from another database. This was likely due to the database not being open.; Action: See the database alert log at the receiving side of the transfer for details of why the database was not ready. If the database was mounted but not open, open it to clear the problem. The initialization parameter LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be set to ENABLE.
ORA-16440: Control file is corrupt.: Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file was corrupt.; Action: Restore the current control file at the primary database and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16441: Current log string for thread string sequence string is invalid.: Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo log file was corrupt.; Action: Restore the current log at the primary database, and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16442: an ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied: Cause: The target standby database did not apply all received redo.; Action: Allow the target standby database to apply all redo and then reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.
ORA-16443: could not switch out of log string thread string: Cause: ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the current log.; Action: This can happen if there are one or more errors during archival of the current log at the primary database. Reissue ALTER SYSTEM FLUSH REDO TO STANDBY after resolving the archiving errors.
ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file.: Cause: A flush redo operation discovered SCNs greater than a previously failed flush redo operation.; Action: This can happen if there are one or more errors that have corrupted the control file or online redo logs. In these cases, flush redo operation is not possible.
ORA-16445: Database has to be mounted and cannot be open: Cause: ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be mounted, but not opened.; Action: Mount the database and then reissue the operation.
ORA-16446: Target database was not a standby database: Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target database is not a standby database.; Action: Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and specify a standby database as the target database.
ORA-16447: Redo apply was not active at the target standby database: Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is not active at the target database.; Action: Start redo apply at the standby database and reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement with the NO CONFIRM APPLY clause.
ORA-16448: media recovery is still active after string seconds: Cause: The media recovery did not stop after the timeout.; Action: See the trace file for more information. Once the media recovery process is no longer active, retry the command.
ORA-16449: incomplete redo thread enable operation: Cause: The switchover operation could not continue because it failed to disable a thread that was left in an incomplete thread enable state.; Action: Check alert log for more details.
ORA-16451: A remote archival request has timed out.: Cause: When opening or closing a database instance, the database may wait for up to 1 minute for pending remote archival requests to be performed before proceeding with the operation. This error was reported because that time limit was exceeded.; Action: This is an informational message so no action is required.
ORA-16454: standby redo log could not be selected: Cause: Selection of SRL (standby redo log) failed. Possible causes: * insufficient SRL files, * the SRL size did not match the source database online redo log (ORL) size, * the SRL block size did not match the source database ORL block size.; Action: Examine the trace file for additional information and ensure that: * the SRL size and block size match the ORL size and block size at the source, and * there are sufficient SRL files for each thread at the source.
ORA-16455: switchover to standby failed: Cause: An attempt to switchover to a physical standby database failed.; Action: Check alert log for more details. Issue the SHUTDOWN ABORT command on the database before issuing another ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command.
ORA-16456: switchover to standby in progress or completed: Cause: The requested operation was not allowed because a switchover to standby operation was either in progress or had completed.; Action: Issue the SHUTDOWN ABORT command on the database after switchover operation completes.
ORA-16459: recovery already beyond standby failover: Cause: Redo Apply stopped because it detected that it had proceeded beyond a standby failover operation.; Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end-of-redo (EOR) logs corresponding to the failover operation from the new primary database and register all these logs at the target database. Restart Redo Apply.
ORA-16461: database not flashed back or recovered to a consistent point: Cause: ALTER DATABASE CONVERT TO STANDBY command failed because either the database was not properly flashed back to STANDBY_BECAME_PRIMARY_SCN, or at least one of the online data files was not current.; Action: Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the ALTER DATABASE CONVERT TO STANDBY command.
ORA-16463: invalid target database name: Cause: ALTER DATABASE FAILOVER TO <target_db_name> or ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command failed because the target_db_name was invalid. The target_db_name must be the same as the name of the database on which the SQL command is issued.; Action: Change the target database name and reissue the command.
ORA-16464: operation must be initiated on a physical standby database: Cause: An attempt was made to issue the ALTER DATABASE FAILOVER TO <target_db_name> or the ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command on a database other than a physical standby database.; Action: Issue the command on a physical standby database.
ORA-16465: operation must be initiated on an open primary database: Cause: An attempt was made to issue the ALTER DATABASE SWITCHOVER TO <target_db_name> [VERIFY] or ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command on a database other than an open primary database.; Action: Issue the command on an open primary database.
ORA-16466: invalid switchover target: Cause: The switchover target was not a valid, enabled, or active standby database.; Action: Fix the problem in the switchover target and reissue the command.
ORA-16467: switchover target is not synchronized: Cause: The switchover target was not synchronized with the primary database.; Action: Wait until the switchover target is synchronized with the primary database, then reissue the command.
ORA-16468: error connecting to switchover target string: Cause: The primary database could not connect to the switchover target.; Action: Check the alert log for detailed errors.
ORA-16469: switchover target version number is lower than 12: Cause: The switchover target version number was lower than 12.; Action: Upgrade the switchover target to a higher release.
ORA-16470: Redo Apply is not running on switchover target: Cause: The switchover target was not running Redo Apply.; Action: Start Redo Apply on the switchover target and reissue the command.
ORA-16471: cannot convert switchover target string to a primary database: Cause: Switchover failed because the switchover target could not convert to a primary database.; Action: Check the database role of the switchover target. If the switchover target database role is standby, do one of the following: - Fix the problem shown in the alert log. - Issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command to convert the switchover target to a primary database. - If the problem in the switchover target cannot be fixed, issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command on the old primary database to convert the old primary database back to a primary database. If the switchover target database role is primary, the switchover has completed. Open the switchover target and startup the old primary database to finish the switchover process.
ORA-16472: failover failed due to data loss: Cause: The database was in MaxAvailability or MaxProtection mode but terminal recovery finished with data loss.; Action: For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY DATABASE command.
ORA-16473: database is not in limbo: Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE statement could not proceed because the database was in an active state.; Action: Ensure that the SWITCHOVER_STATUS column in the V$DATABASE view has the value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed standby recovery and reissue the statement after the SWITCHOVER_STATUS column value changes to one of the above values.
ORA-16474: target_db_name not found in a LOG_ARCHIVE_DEST_n parameter: Cause: ALTER DATABASE SWITCHOVER TO <target_db_name> or ALTER SYSTEM FLUSH REDO TO <target_db_name> statement failed because the target_db_name was not defined in a LOG_ARCHIVE_DEST_n parameter.; Action: Ensure that the target_db_name is defined in a LOG_ARCHIVE_DEST_n parameter.
ORA-16475: succeeded with warnings, check alert log for more details: Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> VERIFY command succeeded but with warnings.; Action: Check alert log for more details.
ORA-16476: far sync instance does not allow string operation: Cause: The specified operation was invalid on a far sync instance.; Action: Do not attempt the specified operation on a far sync instance.
ORA-16477: destination is being serviced by another viable source: Cause: An attempt was made by a far sync to perform gap analysis with a remote destination that already had connectivity with a different viable source of redo.; Action: No action is required. This error is informational and is used by the far sync to remain idle with respect to this destination until it establishes connectivity with the primary database.
ORA-16478: cannot locate far sync connect string: Cause: The connect string for the far sync that was flagged as the source of redo for this database could not be located.; Action: Define a LOG_ARCHIVE_DEST_n parameter on the standby for the far sync using the SERVICE attribute to define the connect string for the far sync. This destination should be set to the DEFER state using the corresponding LOG_ARCHIVE_DEST_STATE_n parameter. Once the connect string is defined, retry the failover operation. Note that while using the FORCE option on the failover command allows the operation to proceed and bypass the far sync, this choice increases the potential for data loss.
ORA-16479: cannot connect to the far sync: Cause: An attempt was made to connect to the far sync to facilitate the failover operation; but the connection attempt failed.; Action: Ensure that the far sync is mounted. Check the alert log and trace files on both the current database and the far sync for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync; but bypassing the far sync increases the potential for data loss.
ORA-16480: operational error during far sync assisted failover: Cause: After successfully connecting to the far sync instance, an error was encountered when polling the far sync for progress.; Action: Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync; but bypassing the far sync increases the potential for data loss.
ORA-16481: destination error during far sync assisted failover: Cause: After successfully connecting to the far sync, an error was encountered when managing the failover target destination on the far sync.; Action: Check the alert log and traces of both the current database and the far sync for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync; but bypassing the far sync increases the potential for data loss.
ORA-16482: a role transition is in progress: Cause: The operation failed because a role transition was in progress.; Action: None
ORA-16483: unable to set a LOG_ARCHIVE_DEST_n parameter to the switchover target: Cause: An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the switchover target failed.; Action: Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover target.
ORA-16484: compatibility setting is too low: Cause: The compatibility setting of the primary database was higher than the standby database. The transported redo log could not be applied.; Action: Check the compatibility setting on the primary and standby database, and increase the compatibility setting in the initialization parameter file on the standby database accordingly.
ORA-16485: protection mode modification not allowed at this time: Cause: This exception occurred because of one of the following circumstances: * If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter was not defined, the protection mode could not be modified if any instance of the database was open. See the Data Guard documentation for details on the DG_CONFIG attribute. * If the current instance was not open, the protection mode could not be modified if any other instance was open. * Once the database instance was opened, you could not upgrade the protection mode from MAXIMUM PERFORMANCE mode directly to MAXIMUM PROTECTION mode even if the DG_CONFIG attribute was defined. You must first upgrade to MAXIMUM AVAILABILITY mode and then wait until there was at least one synchronized destination before attempting to move to MAXIMUM PROTECTION mode. You cannot upgrade the protection mode from MAXIMUM AVAILABILITY mode to MAXIMUM PROTECTION mode unless there was at least one synchronized destination. See the Data Guard documentation on how to determine if there are any synchronized destinations.; Action: Retry the operation after any potential issues described in the Cause have been addressed.
ORA-16486: a redo log is rejected by the destination: Cause: The destination was not allowed to receive this redo log.; Action: Ensure the source database is registered at the destination, the destination is up and running, and storage is available. Examine the trace file of the Remote File Server (RFS) process and the database's alert log file for additional information.
ORA-16487: the destination database is not writable: Cause: The destination database was in read-only mode.; Action: Ensure the destination database is open for write.
ORA-16488: cannot create a bookkeeping entry in database: Cause: The destination database failed to create an entry in the table used to track the redo log file or the database.; Action: See the trace file of the Remote File Server (RFS) process. Ensure that table space is available in your database.
ORA-16489: cannot register the redo log at the destination database: Cause: Registering the redo log file to the destination database failed.; Action: Examine the trace file of the Remote File Server (RFS) process. Ensure that space is available in your database.
ORA-16491: operation not allowed due to insufficient online redo log files string: Cause: A minimum of two online redo log files per active thread were not supplied.; Action: Add the required redo log files and reissue the command.
ORA-16492: switchover target local destination has error: Cause: The switchover target local destination either exceeded quota size or had an error.; Action: Fix the problem in the switchover target and reissue the command.
ORA-16493: using SYSDBA, SYSOPER, SYSDG, or SYSBKUP user for redo shipping to Recovery Appliance is not supported: Cause: An attempt was made to use a SYSDBA, SYSOPER, SYSDG, or SYSBKUP user to ship redo logs to a Recovery Appliance.; Action: Use a user without the SYSDBA, SYSOPER, SYSDG, or SYSBKUP privilege to ship redo logs to a Recovery Appliance.
ORA-16494: process started from pluggable database (PDB): Cause: The Remote File Server (RFS) process or the Remote Message Interface (RMI) process or the Fetch Archive Log (FAL) process was started from a Pluggable Database (PDB).; Action: Check the service name that the RFS or RMI or FAL client connected to and ensure the service is not from a PDB.
ORA-16495: using the Fast Recovery Area to receive redo log files on a Recovery Appliance is not supported: Cause: An attempt was made to use the Fast Recovery Area to store a redo log file on a Zero Data Loss Recovery Appliance.; Action: Do not configure the Fast Recovery Area as a destination for redo log files on the Zero Data Loss Recovery Appliance. Refer to the documentation for more details.
ORA-16496: corruption in network metadata packet: Cause: Invalid or corrupt metadata was encountered in a network packet.; Action: No user action is required.
ORA-16497: LOG_ARCHIVE_DEST_string DELAY attribute is not 0: Cause: The DELAY attribute was not 0 for the LOG_ARCHIVE_DEST_n parameter. Since the DELAY attribute delays standby database recovery, the switchover will be prolonged by that amount of time.; Action: Remove the DELAY attribute from the LOG_ARCHIVE_DEST_n parameter, then reissue the command.
ORA-16498: Cancellation of managed recovery operation cannot be performed: Cause: Cancellation of managed recovery was invoked when the Oracle Active Data Guard (Oracle ADG) instance recovery was running.; Action: None
ORA-16501: The Oracle Data Guard broker operation failed.: Cause: The Oracle Data Guard broker operation failed.; Action: See accompanying messages for details.
ORA-16502: The Oracle Data Guard broker operation succeeded with warnings.: Cause: The Oracle Data Guard broker operation succeeded with warnings.; Action: See accompanying messages for details.
ORA-16503: cannot exceed the maximum number of members in this configuration: Cause: The Oracle Data Guard broker configuration already contained the maximum number of members that could be configured and managed by the broker.; Action: Select and remove an existing member from the broker configuration, then reissue the command to add another member to the configuration. The maximum number of members permitted in a broker configuration is 253.
ORA-16504: The Oracle Data Guard broker configuration already exists.: Cause: A request to create or import an Oracle Data Guard broker configuration was made while connected to a database that was part of an existing configuration.; Action: To create or import a new configuration, the existing configuration must be deleted.
ORA-16506: out of memory: Cause: Process exceeded private or shared memory limits.; Action: Check for memory leaks, increase system parameters, and restart.
ORA-16509: request timed out: Cause: The Oracle Data Guard broker timed out the request.; Action: Check the Oracle Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.
ORA-16513: maximum requests exceeded: Cause: The maximum number of requests that the broker can service on the database instance was exceeded.; Action: Wait for the broker to complete processing the requests before issuing more requests.
ORA-16516: current state is invalid for the attempted operation: Cause: The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either: - The databases changing roles were shut down. - The primary database was not shipping redo data. - The standby database that will become the primary database was not applying redo data. If this error was returned for database state change operations, the database state specified was invalid.; Action: If this error is returned when attempting a switchover operation, ensure that: - The databases changing roles are started. - The primary database is shipping redo data. - The standby database is applying redo data. If this error is returned when attempting a database state change operation, ensure that a valid database state is specified.
ORA-16521: Service name specified in connect identifier connects to a PDB.: Cause: The connect identifier that was specified resulted in a connection to a pluggable database (PDB) and not to the multitenant container database root.; Action: Check the connect identifier and confirm that it specifies a service name that results in a connection to the multitenant container database root.
ORA-16522: The configuration is part of the Global Data Services pool.: Cause: The attempted command was not allowed because the configuration was part of a Global Data Services pool.; Action: Remove the configuration from the Global Data Services pool using GDSCTL. Then, retry the broker command. If the command was attempting to repair a database, then disable or remove the individual database from the configuration and fix the issue. After the problem is resolved, re-enable the database, or add the database back to the configuration if it had been removed.
ORA-16523: operation requires the client to connect to instance "string": Cause: The switchover or failover operation required the client to connect to the apply instance of the target database.; Action: Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.
ORA-16524: unsupported command, option, or argument: Cause: A command, option, or fast-start failover condition argument was specified that is not supported in this release.; Action: If trying to enable or disable a fast-start failover condition, try a different Oracle error number. Otherwise, contact Oracle Support Services.
ORA-16525: The Oracle Data Guard broker is not yet available.: Cause: The Oracle Data Guard broker process was either not yet started, was initializing, or failed to start.; Action: If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Oracle Data Guard log for possible errors. Otherwise, retry the operation.
ORA-16526: Unable to allocate memory to process request.: Cause: Oracle Data Guard broker was unable to allocate memory for a request.; Action: Increase the size of the System Global Area (SGA).
ORA-16530: invalid buffer or length: Cause: A NULL buffer or a length of zero was specified.; Action: Correct the command parameters and retry the command.
ORA-16532: Oracle Data Guard broker configuration does not exist.: Cause: The broker operation could not be performed because the broker configuration did not exist.; Action: Create a Data Guard broker configuration prior to attempting the operation. If only one instance of an Oracle Real Application Cluster (RAC) database reports this error, verify that the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to shared file locations accessible to all RAC instances.
ORA-16534: switchover, failover or convert operation in progress: Cause: The Oracle Data Guard broker returned this status because a switchover, failover or convert operation was in progress. The broker could not accept new commands until the operation finished.; Action: Wait until the operation is complete and reissue the command.
ORA-16535: Oracle Restart or Oracle Clusterware prevented completion of broker operation.: Cause: The broker could not complete the operation because Oracle Restart (for single instance databases) or Oracle Clusterware (for Oracle RAC databases) could not stop services or instances on this database.; Action: Check the Oracle Data Guard broker log file for more information and stop the appropriate services or instances using SRVCTL. Then retry the broker operation.
ORA-16538: no match on requested item: Cause: The Oracle Data Guard broker did not recognize the specified property or state name, or a fast-start failover condition was specified that is not enabled.; Action: Verify the command parameters and reissue the command.
ORA-16540: invalid argument: Cause: One of the arguments for the specified command was invalid.; Action: Verify the arguments and then reissue the command.
ORA-16541: member is not enabled: Cause: An attempt was made to modify or query a disabled member. This error is also returned when an attempt is made to enable, modify, or query a member that the broker has disabled because of a switchover or failover operation. The broker disables its management of a member when it detects that the database needs to be re-created because of a failover or switchover operation.; Action: If broker management of the member is disabled, re-create it if necessary, enable it and reissue the command.
ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier: Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID='*' qualifier was required in the command.; Action: Reenter the command using the SID='*' qualifier.
ORA-16547: Cannot disable or remove the primary database.: Cause: An attempt was made to disable broker management of the primary database or remove the primary database from the broker configuration while the configuration was enabled.; Action: To disable the primary database, disable the configuration. To remove the primary database, remove the configuration.
ORA-16549: invalid string: Cause: An invalid or NULL string value was specified.; Action: Correct the command parameters and retry.
ORA-16550: truncated result: Cause: A string property value was truncated due to insufficient buffer size.; Action: Specify a larger receive buffer.
ORA-16551: short string copied - information only - no action required: Cause: A string property value that did not fill the receive buffer was placed in the receive buffer.; Action: No action needed; this situation did not cause the software to stop. This is an informational message only.
ORA-16552: error occurred while generating directives for client: Cause: The client could not provide the required assistance to the broker because of the accompanying error.; Action: See the accompanying error message for more information and follow the directions provided in the Action of that message. Then, retry the operation.
ORA-16555: Member is not active.: Cause: Attempted an operation on an inactive member.; Action: Verify that the member is active and retry.
ORA-16556: observer version mismatch: Cause: This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.; Action: Use a version of the observer that is compatible with the Oracle database server to be observed.
ORA-16557: Member already exists in the configuration.: Cause: Attempted to create a duplicate member in the Oracle Data Guard broker configuration, or to add a duplicate instance (SID) for an existing member in the configuration.; Action: Check the configuration to avoid duplicate members.
ORA-16558: database specified for switchover is not a standby database: Cause: An attempt was made to switchover to a database that was not a standby database.; Action: Locate an enabled standby database and select that database as the target of the switchover.
ORA-16561: cannot remove an active instance: Cause: The instance to be removed was running.; Action: Shut down the instance and reissue the REMOVE command.
ORA-16568: cannot set property string: Cause: The specified property could not be modified because it was either a monitorable property or a property that did not exist.; Action: Retry the command with a valid configurable property.
ORA-16569: Oracle Data Guard configuration is not enabled: Cause: The requested operation required that broker management of the Data Guard configuration must be enabled.; Action: Enable the Oracle Data Guard configuration and reissue the command.
ORA-16570: database needs restart: Cause: The Oracle Data Guard broker operation required this database instance to be shut down and restarted.; Action: If DGMGRL or Enterprise Manager has not already done so, shut down the Oracle instance and then restart it.
ORA-16571: Oracle Data Guard configuration file creation failure: Cause: The Oracle Data Guard broker was unable to create the configuration file on permanent storage.; Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
ORA-16572: Oracle Data Guard configuration file not found: Cause: The Oracle Data Guard broker configuration file was either unavailable or did not exist.; Action: Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. For a RAC database, ensure that these initialization parameters are set to file locations that are shared by all instances of the RAC database.
ORA-16573: attempt to change or access configuration file for an enabled broker configuration: Cause: The operation was rejected because the Oracle Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example: - An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running. - Non-broker access (such as DBMS_FILE_TRANSFER) to the configuration files was attempted. See the alert log for additional information.; Action: Disable the broker configuration and shut down the Oracle Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.
ORA-16574: Switchover is disallowed when required databases are shut down.: Cause: Switchover failed because either the primary database or the designated standby database was shut down.; Action: Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that the designated standby database is applying the redo data received from the primary database.
ORA-16575: LOG_ARCHIVE_DEST_n parameter conflicts with the new member to be added: Cause: One or more LOG_ARCHIVE_DEST_n initialization parameters on existing members were already set for the new member to be added when attempting to add a standby database, far sync instance, Recovery Appliance, or external destination to the configuration.; Action: Clear the LOG_ARCHIVE_DEST_n initialization parameter that specifies the standby database, far sync instance, Recovery Appliance, or external destination to be added.
ORA-16576: Failed to update Data Guard broker configuration file.: Cause: The broker failed updating the Oracle Data Guard broker configuration file on permanent storage.; Action: Verify that sufficient space exists on the device containing the the configuration files and the files specified by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters permit read and write access.
ORA-16577: corruption detected in Data Guard configuration file: Cause: The Oracle Data Guard broker detected errors while loading the configuration file.; Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.
ORA-16578: failed to read Oracle Data Guard configuration file: Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.; Action: Verify that sufficient space exists on the device containing the the configuration files and the files specified by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters permit read and write access.
ORA-16582: cannot change instance-specific property: Cause: An attempt was made to change an instance-specific property for a member that had more than one instance.; Action: Retry the command and identify a specific instance whose property value is to be changed.
ORA-16584: operation cannot be performed on a standby database: Cause: The database specified for the operation was a standby database, or the operation was attempted on a standby database.; Action: Check the database type and retry the operation. If the command must be executed on a primary database, connect to the primary database and retry the operation.
ORA-16585: This operation cannot be performed on a primary database.: Cause: The database specified for the operation was a primary database, or the operation was attempted on a primary database.; Action: Check the database type and retry the operation. If the command must be executed on a standby database, then connect to a standby database and retry the operation.
ORA-16586: Cannot change member property with EDIT INSTANCE command.: Cause: Attempted to change a member level property using an EDIT INSTANCE command instead of an EDIT DATABASE, EDIT FAR_SYNC, or EDIT RECOVERY_APPLIANCE command.; Action: Use the EDIT DATABASE, EDIT FAR_SYNC, or EDIT RECOVERY_APPLIANCE command to change member level properties.
ORA-16587: Ambiguous member specified to Oracle Data Guard broker.: Cause: A member was specified that the broker could not uniquely distinguish from other members in the configuration.; Action: Try to further distinguish the member specified for the operation and retry the command.
ORA-16589: Oracle Data Guard broker detected network transfer error: Cause: The Oracle Data Guard broker detected an error while transferring data from one member to another. This may happen when either: - The broker detects an inconsistency in the block count of the configuration file when the file is transmitted between members. - The broker encounters an error when writing the configuration file. - A broker member receives an incorrect message from another member.; Action: Contact Oracle Support Services.
ORA-16594: DMON background process is not running: Cause: The Oracle Data Guard broker background process, DMON, was not running.; Action: Check the Oracle Data Guard broker log file and DMON process trace file to determine why the DMON process is not running.
ORA-16595: process string failed to terminate: Cause: The specified process did not terminate at the request of the Data Guard broker.; Action: Contact Oracle Support Services.
ORA-16596: member not part of the Oracle Data Guard broker configuration: Cause: The specified member was not in the Oracle Data Guard broker configuration.; Action: Retry the command with a member that is in the broker configuration.
ORA-16597: Oracle Data Guard broker detects two or more primary databases: Cause: The Oracle Data Guard broker detected two or more primary databases in the broker configuration and could not continue.; Action: Contact Oracle Support Services.
ORA-16598: Oracle Data Guard broker detected a mismatch in configuration: Cause: The Oracle Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more members in the broker configuration. This can occur when the primary database has stale broker configuration files.; Action: Contact Oracle Support Services.
ORA-16599: Oracle Data Guard broker detected a stale configuration: Cause: The Oracle Data Guard broker detected a stale configuration during initialization for this member.; Action: The broker will automatically resolve this situation once the primary database completes its initialization.
ORA-16600: not connected to target standby database: Cause: The switchover or failover command failed because the client was not connected to the target standby database of the failover or switchover command.; Action: Explicitly connect to the standby database that is to become the the new primary and retry the failover or switchover command.
ORA-16602: member must be disabled to perform this operation: Cause: An attempt was made to edit a member property while the member was enabled.; Action: Disable the member and retry the command.
ORA-16603: The member is part of another Oracle Data Guard broker configuration.: Cause: The member was part of another Oracle Data Guard broker configuration. This could occur if the original configuration was re-created while this member was disconnected from the network or the same member was added to two different Oracle Data Guard broker configurations.; Action: Ensure that the member belongs to only one broker configuration. Shut down the broker by setting the DG_BROKER_START initialization parameter to 'false'. Then, remove the Oracle Data Guard broker configuration files. Finally, restart the broker by setting the DG_BROKER_START initialization parameter to 'true'.
ORA-16604: Data Guard broker configuration file inaccessible: Cause: The Oracle Data Guard broker was unable to access the configuration file specified by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.; Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16606: unable to find property "string": Cause: The specified property did not exist.; Action: Specify a valid property name and reissue the command.
ORA-16607: One or more members have failed.: Cause: A failure was detected for one or more members in the Oracle Data Guard broker configuration.; Action: Locate the member or members with a failure status and correct it.
ORA-16608: one or more members have warnings: Cause: A warning was detected for one or more members in the Data Guard broker configuration.; Action: Locate the member or members with a warning status and correct it.
ORA-16609: Database is being disabled.: Cause: Attempted a command on a database that was being disabled. For example, attempted to reinstate the old primary database, the database that was the primary database prior to the most recent failover, before it was ready to be reinstated.; Action: Wait for Oracle Data Guard broker to disable the database then retry the command.
ORA-16610: Oracle Data Guard broker command "string" in progress.: Cause: Specified Data Guard broker command was already running and could not be completed.; Action: Wait for the specified command to finish and then retry.
ORA-16611: command aborted at user request: Cause: The command was aborted at the user's request.; Action: No action required.
ORA-16612: string value too long for attribute "string": Cause: The string value for the named attribute was too long.; Action: Specify a shorter string value.
ORA-16613: Oracle Data Guard broker initialization in progress for member.: Cause: A request was made that required access to the Oracle Data Guard broker configuration before it had completed initialization.; Action: Wait until the Oracle Data Guard broker has completed initialization, then reissue the command.
ORA-16614: Oracle Data Guard broker configuration is disabled: Cause: An attempt to enable a member failed because the Oracle Data Guard broker configuration was disabled.; Action: Enable the Oracle Data Guard broker configuration and issue the DGMGRL CLI SHOW CONFIGURATION command to see if there are any members that are still disabled. If the member you tried to enable is still disabled, issue the DGMGRL CLI SHOW command to check the status of the member. If the member is a database whose status indicates that the database needs to be reinstated, then issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database. If the member does not require reinstatement, then issue the DGMGRL CLI ENABLE command to enable the member.
ORA-16617: unknown object identifier specified in request: Cause: Object identifier specified in the request was invalid or unknown.; Action: Verify that a valid object identifier is specified and reissue the command.
ORA-16619: condition for fast-start failover is already enabled: Cause: The condition specified for fast-start failover was already enabled.; Action: No action is required. Use the DGMGRL CLI SHOW FAST_START FAILOVER command to view the conditions that are enabled.
ORA-16620: one or more members could not be reached for a remove operation: Cause: One or more members could not be reached for either a DGMGRL CLI REMOVE DATABASE, REMOVE FAR_SYNC or a REMOVE CONFIGURATION command.; Action: This typically indicates a network problem where the member is unable to respond to the primary database. If this is the case, examine the primary database Data Guard broker log file to determine which members could not be reached. For each mmeber not reached, connect to that member and shut down the broker by setting the DG_BROKER_START initialization parameter to 'false'. After the broker has been shut down for the member, locate the Data Guard broker configuration files from the member's DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them. Then restart the broker by setting DG_BROKER_START to 'true'.
ORA-16621: member name for ADD command must be unique: Cause: An attempt was made to add a member to the broker configuration that already included a member with the specified name. The member names must be unique.; Action: Verify that a unique name is specified for the new member to be added. Also, the member name must match the DB_UNIQUE_NAME initialization parameter of the member.
ORA-16622: two or more broker member objects resolve to the same member: Cause: Multiple member objects referred to the same member.; Action: Examine the details of all members in the broker configuration and verify that two or more members are not referring to the same member. If two or more members in the broker configuration have the same value for the DGConnectIdentifier configurable property, either: - Remove and re-add the incorrectly defined member or members to resolve the ambiguity. - Ensure that the DGConnectIdentifier configurable property for each member allows the broker to properly connect to that member.
ORA-16623: member detected role change: Cause: A successful switchover or failover operation had been completed and was detected during member startup or broker health check. If this member was a database that was unavailable during a switchover or failover operation, it may not be a viable standby database for the new primary database and was disabled by the Oracle Data Guard broker.; Action: Connect to the new primary database and examine the broker configuration for databases that were disabled and that may require reinstatement or re-creation.
ORA-16624: broker protocol version mismatch detected: Cause: A network protocol version number mismatch was detected. This could happen if the members in the broker configuration were not running the same version of Oracle. The broker would disable members that were not running the same version of Oracle as the primary database if this situation was detected.; Action: Examine the version of Oracle installed on all members in the broker configuration to ensure they are identical. Once all of the members in the broker configuration are running the same version of Oracle, reenable the members that were disabled.
ORA-16625: cannot reach member "string": Cause: The command could not be executed because the member noted in the error text was not reachable.; Action: See accompanying messages for more information. Check the network connections to the specified member. After ensuring connectivity, retry the command.
ORA-16626: failed to enable specified member: Cause: This status was returned when attempting to enable a member that: - Could not locate itself in the broker configuration file. - Failed to distinguish itself from two or more members in the configuration file. - Determined it missed a role change within the configuration.; Action: To correct the problem, try one of these actions: - Confirm that the host and SID names for the member exactly match the values in the HOST_NAME and INSTANCE_NAME columns of the V$INSTANCE view. - Confirm that two or more members do not have the same connect identifier. That is, multiple members in the broker configuration should not reach the same member. - If a failover has been performed and the old primary database has been re-created (or a standby database has been re-created), then ensure that the Oracle Data Guard broker configuration files have been removed for that database. Do not remove the configuration files that are in use by the new primary database.
ORA-16627: No member available to support the protection mode.: Cause: Either there were no members in the configuration whose redo transport mode supported the desired protection mode, or an operation was attempted that resulted in no remaining members to support the protection mode.; Action: Ensure that at least one database supports the protection mode. For example, if the desired protection mode is maximum protection mode, ensure at least one enabled database has a redo transport mode set to SYNC mode.
ORA-16628: broker protection mode inconsistent with the database setting: Cause: The Oracle Data Guard broker protection mode saved in the broker configuration file was inconsistent with the actual database setting.; Action: Reset the protection mode through the Oracle Data Guard broker.
ORA-16629: database reports a different protection level from the protection mode: Cause: The current database protection level was different from the configured protection mode. This was typically caused if there were redo transport problems or if the primary database was not open.; Action: Ensure the following: - Check the database alert log files and Data Guard broker log files for more details. - Check the redo transport status. - That one standby database supports the configured protection mode - That the network to that standby database is working properly. - That the primary database is open.
ORA-16630: configurable property has been deprecated: Cause: The property that was specified in the command was deprecated.; Action: Check the broker documentation to identify a replacement property.
ORA-16631: operation requires shutdown of database or instance "string": Cause: The Oracle Data Guard broker operation required a shutdown of the database or instance.; Action: If database or instance has not been shutdown by the DGMGRL CLI or Enterprise Manager, shutdown the database or instance manually.
ORA-16632: instance being added to member profile: Cause: The Oracle Data Guard broker determined that an instance successfully found its member profile within the broker configuration file, but lacked an instance-specific profile. The broker automatically created an instance-specific profile and associated the instance with its database profile.; Action: No user action is required. The broker will automatically associate the instance with its member profile and incorporate the instance into broker activity.
ORA-16633: The only instance of a member cannot be removed.: Cause: The instance to be removed was the only instance of the corresponding member that was known to the broker.; Action: Remove the corresponding member from the broker configuration instead of the individual instance of the member.
ORA-16635: Network connection failed during transmission.: Cause: The Oracle Data Guard broker detected a connection failure to a member in the broker configuration. This failure happened in the middle of a transmission session.; Action: In most cases, no action is required. The Oracle Data Guard broker tries to resend the data. The error indicates a problem in the network communication between broker managed members. If this persists, contact Oracle Support Services.
ORA-16636: Fast-start failover target standby in error state. Cannot stop observer.: Cause: A STOP OBSERVER operation could not be completed when fast-start failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.; Action: Additional information about this failure is recorded in the Oracle Data Guard broker log file for the primary database. This information helps to identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. If the problem can be corrected by the information in the broker log file, retry the operation. Alternatively, fast-start failover may be forcibly disabled by connecting to the primary database and issuing the DISABLE FAST_START FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover has been forcibly disabled, the observer can be stopped regardless of the current state of the target standby database.
ORA-16637: maximum number of Oracle error numbers for fast-start failover already reached: Cause: The broker could not enable any more Oracle error numbers for initiating a fast-start failover.; Action: Use the DGMGRL CLI SHOW FAST_START FAILOVER command to help identify an Oracle error number that can be disabled before attempting to enable an additional error number for initiating a fast-start failover.
ORA-16638: Could not obtain instance status.: Cause: The broker could not determine whether the specified instance was running.; Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so. Otherwise, contact Oracle Support Services.
ORA-16639: specified instance inactive or currently unavailable: Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable.; Action: Ensure that the instance specified in the operation is running and then retry the operation.
ORA-16642: DB_UNIQUE_NAME mismatch.: Cause: The DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value for the member that the broker contacted using the connect identifier associated with that member.; Action: Verify that the connect identifier correctly connects to the intended member. Verify that the name of the member the broker expects to find by that connect identifier matches the actual DB_UNIQUE_NAME for that member.
ORA-16643: Unable to determine location of broker configuration files.: Cause: Oracle Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.; Action: Retry the operation. If the error persists, contact Oracle Support Services.
ORA-16644: apply instance not available: Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.; Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.
ORA-16645: startup of an instance not part of the broker configuration interrupted current operation: Cause: The startup of an instance, that was not part of the broker configuration prevented the operation from completing.; Action: Restart the operation after the new instance has joined the Data Guard configuration.
ORA-16646: Fast-start failover is disabled.: Cause: This operation was not allowed because fast-start failover was disabled.; Action: Enable fast-start failover and retry the command.
ORA-16647: maximum number of observers has already been started: Cause: The attempt to start an observer failed because the maximum number of observers was already running. For Oracle Database releases earlier than 12.2, only a single observer can be started. For Oracle Database releases 12.2 and later, a maximum of three observers can be started.; Action: Stop one of the existing observers and retry the command.
ORA-16648: A new observer registered with identifier string.: Cause: An observer was registered with the Oracle Data Guard broker and will begin observing the Oracle Data Guard configuration for conditions that warrant doing a fast-start failover.; Action: No actions needed.
ORA-16649: Data Guard prevented this database from opening.: Cause: The primary database could not be opened because one of the following reasons. A fast-start failover has occurred, and there was another primary. Data Guard had detected a possible fast-start failover but could not contact the observer or target standby to verify. The database was configured for maximum protection and no standby database was available to support the protection mode.; Action: Check if a failover did occur. If it did, reinstate the database. If the failover did not occur and fast-start failover is enabled, ensure that connectivity exists between the primary database and either the observer or the target standby database, then retry opening the database.
ORA-16650: unrecognized object specified: Cause: An unrecognized database or far sync instance was specified in the command.; Action: Try the command again using a valid object name. Use the SHOW CONFIGURATION command to identify the members in the configuration.
ORA-16651: upgrade to maximum protection mode not possible: Cause: An upgrade to maximum protection mode was attempted when the current protection mode was maximum performance mode.; Action: To upgrade the protection mode to maximum protection mode, first upgrade the protection mode to maximum availability mode, then upgrade the protection mode to maximum protection mode.
ORA-16652: fast-start failover target standby database is disabled: Cause: The command to enable or disable fast-start failover could not be run because the Data Guard broker management of the fast-start failover target standby database was disabled.; Action: Enable broker management of the target standby database and rerun the command. If an attempt was made to disable fast-start failover when this error was reported, then disable fast-start failover forcibly using the DGMGRL DISABLE FAST_START FAILOVER FORCE command. Refer to the documentation for more information.
ORA-16653: Oracle Data Guard broker failed to reinstate database.: Cause: The Data Guard broker failed to reinstate the database because the reinstatement could not be completed or the database was already reinstated.; Action: Additional information about the failure is recorded in the primary database or the specified database Data Guard broker log files. This information helps determine how to proceed.
ORA-16654: fast-start failover is enabled: Cause: The attempted command was not allowed while fast-start failover was enabled. This occurred because: - The FastStartFailoverTarget property may not be modified. - The LogXptMode property for either the primary database or the fast-start failover target standby database may not be modified. - The protection mode of the configuration may not be modified. - Neither the broker configuration nor the fast-start failover target standby database was disabled using the DGMGRL CLI DISABLE command. - Neither the broker configuration nor the fast-start failover target standby database was removed using the DGMGRL CLI REMOVE command. - The FAILOVER IMMEDIATE command was not allowed. - The DG_BROKER_START initialization parameter may not be set to FALSE.; Action: Disable fast-start failover, using the FORCE option if required. Then retry the attempted command.
ORA-16655: specified standby database not the current fast-start failover target standby: Cause: The attempted command was not allowed because fast-start failover was enabled for this Data Guard broker configuration and the standby database specified in the command was not the current fast-start failover target standby associated with the current primary database.; Action: Retry the attempted command by specifying the current fast-start failover target standby database. Alternatively, disable fast-start failover and retry the command using the originally specified target standby database.
ORA-16656: Oracle Data Guard broker detected role change.: Cause: The Oracle Data Guard broker detected a role change during database startup or health check.; Action: Additional information about this failure is recorded in the Oracle Data Guard broker log files, one for the primary database and one for each standby database in the Oracle Data Guard configuration. This information is helpful in determining how best to resolve this failure.
ORA-16657: Reinstatement of database in progress.: Cause: Reinstatement of this database was in progress.; Action: None
ORA-16658: unobserved fast-start failover configuration: Cause: The fast-start failover configuration was currently unobserved therefore failover was disallowed.; Action: Ensure that the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable fast-start failover to perform a failover in the absence of the observer process.
ORA-16659: Failover operation is in progress.: Cause: A primary database that restarted contacted a standby database while the failover is active to that standby database.; Action: Shut down the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database.
ORA-16660: Fast-start failover operation attempted in absence of a broker configuration.: Cause: Attempted to enable or disable fast-start failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands.; Action: 1) Attempts to enable or disable (non-FORCE) fast-start failover at this standby database will be rejected until the broker configuration details are available to the standby database from the primary database. This typically occurs when the standby database is successfully recreated or flashed back, and then re-enabled on the primary database. 2) Use the FORCE option to override fast-start failover enabled on the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, the status message is only a warning. Note that fast-start failover is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other and if the state of fast-start failover has been altered at the primary database in the meantime.
ORA-16661: the standby database needs to be reinstated: Cause: A role change has caused this database to require reinstatement.; Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. Reinstate the database as soon as possible, because the database will have to be re-created if another role change occurs while it is in this state.
ORA-16662: Network timeout when contacting a member.: Cause: Oracle Data Guard broker attempted to contact a member and failed because there was no response from the member within timeout specifiedby the CommunicationTimeout configuration property.; Action: Check the Oracle Data Guard broker log file for the details of the failure. Fix the problem and retry.
ORA-16664: unable to receive the result from a member: Cause: During execution of a command, a member in the Oracle Data Guard broker configuration failed to return a result.; Action: Check Oracle Data Guard broker log files for the details of the failure. Ensure network communication is working properly amongst the members of the configuration. Fix any possible network problems and reissue the command.
ORA-16665: time out waiting for the result from a member: Cause: The Oracle Data Guard broker was forced to time out a network connection to a remote member because: - The network call to the remote member did not complete in a timely manner. - The remote member was unable to execute the command due to an instance failure.; Action: Check Data Guard broker log files for the details of the failure. If the network call did not complete in a timely manner, increase the CommunicationTimeout configuration property value and reissue the command.
ORA-16666: Unable to initiate fast-start failover on a bystander standby database.: Cause: The request to initiate a fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made on a bystander standby database.; Action: Call DBMS_DG.INITIATE_FS_FAILOVER on either the primary or fast-start failover target standby database.
ORA-16667: request Oracle Data Guard broker client to reissue command: Cause: The Oracle Data Guard broker operation required that the same command be issued again from the client.; Action: If DGMGRL or Enterprise Manager has not already done so, reissue the same command to the Oracle Data Guard broker manually.
ORA-16668: operation cannot be performed on the fast-start failover target standby database: Cause: The database specified for the operation was the fast-start failover target standby database.; Action: Retry the operation on a different database. Alternatively, disable fast-start failover, and retry the operation.
ORA-16671: instance-specific property must be set uniquely for instances of an Oracle RAC database: Cause: An attempt was made to set an instance-specific property to the same value for all instances of an Oracle RAC database for a property whose value must be unique for each instance.; Action: Use the EDIT INSTANCE command and specify the SID of each instance whose instance-specific property value is to be changed.
ORA-16672: switchover not permitted to standby database with non-zero DelayMins property value: Cause: Switchover was attempted to a standby database that had a non-zero value for its DelayMins configurable property.; Action: For switchover to a standby database, set the DelayMins configurable property to zero for the standby database, wait for its apply lag to become zero seconds, and then retry the switchover command.
ORA-16673: A member is running a different Oracle version from that of the primary database version.: Cause: The standby member was running a different version of Oracle than the primary database.; Action: Ensure that all members of the configuration are running the same versions of Oracle.
ORA-16674: standby database type has changed: Cause: An attempt to enable a database whose standby type changed from physical or snapshot to logical (or vice versa) was disallowed.; Action: If the intention is to retain the database conversion to the new type, the database must be removed and added back into the configuration in order to obtain the correct values for database properties specific to the new standby type.
ORA-16675: Database instance restart required for the property value modification to take effect.: Cause: One or more properties that correspond to static initialization parameters were modified, but the database instances were not restarted. Or, a static initialization parameter that corresponds to a broker property was modified using an ALTER SYSTEM SQL*Plus statement.; Action: Restart the database instances for the modified property values to take effect. If the error persists after having restarted the instance, use the DGMGRL CLI or Enterprise Manager to modify the property to which the static initialization parameter corresponds.
ORA-16676: RedoRoutes property for two or more members contains a circular route: Cause: The value of a RedoRoutes property for two or more members was set such that a member that sent redo also received redo data data in the same route. For example, A sends to B, B sends to C, and C sends to A.; Action: Correct the setting of the RedoRoutes propety on one or more members to eliminate the circular route.
ORA-16677: Member has the same or higher priority than other members specified in the RedoRoutes group.: Cause: A standby database with the same or higher priority than other members in the group was specified in the RedoRoutes property.; Action: Check the Oracle Data Guard broker log file for the reason for the failure and reissue the command. Ensure that a standby database was not specified to have the same or higher priority than other members in the group for the RedoRoutes property.
ORA-16678: unrecognized or duplicate attribute specified: Cause: The specified value contained an unrecognized or duplicated attribute.; Action: Ensure the property string does not contain any undefined or duplicate attributes. See the Oracle Data Guard broker documentation for supported attributes.
ORA-16679: one or more disallowed keywords found: Cause: The specified value contained one or more disallowed keywords.; Action: See the Oracle Data Guard broker documentation for the supported keywords.
ORA-16680: value contains unbalanced set of parentheses: Cause: The specified value contained an unbalanced set of parentheses or a missing set of parentheses.; Action: Ensure the parentheses are correctly matched and specify parentheses when required. See the Oracle Data Guard broker documentation for more information.
ORA-16681: Value does not contain a colon.: Cause: The specified value did not contain a colon (:).; Action: Include the colon (:) in the value.
ORA-16682: value contains duplicate databases or far sync instances: Cause: The specified value contained the same database or far sync instance multiple times.; Action: Ensure that a database or far sync instance is specified only once.
ORA-16683: disallowed, empty substring specified in property value: Cause: The value specified contained a disallowed, empty string or substring, e.g. "()".; Action: Remove the disallowed empty strings and retry the command.
ORA-16684: maximum number of destinations exceeded: Cause: The value specified for the RedoRoutes property contained more than the maximum of 30 destinations.; Action: Ensure that no more than 30 destinations are specified.
ORA-16685: database does not receive redo data: Cause: The RedoRoutes property for all members of the configuration were set such that this database did not receive redo data. Or, the transport state of the database that sends redo data to this database was not valid.; Action: Check the setting of the RedoRoutes property for all members of the configuration. Ensure that at least one member's RedoRoutes property value is set to ship redo data to this database. Also check the transport state of the database that sends redo data to this database.
ORA-16686: member may not receive redo data if redo source is an alternate destination: Cause: This member may not receive redo data if the redo source is an alternate destination that does not ship redo to this database.; Action: Ensure that any alternates for the redo source for this member includes this member in its redo destination list.
ORA-16687: member has multiple redo sources: Cause: Two or more members had their RedoRoutes property set to ship redo data to the same member.; Action: Examine the RedoRoutes property values for all members to see which members are shipping redo data to the same member. Change the value of the RedoRoutes property for those members so that only one of them sends redo to the member that had multiple redo sources.
ORA-16688: command cannot be issued on a disabled member: Cause: The command was issued on a member that was disabled.; Action: Connect to an enabled member of the configuration and retry the command.
ORA-16689: invalid sender specified for RedoRoutes property: Cause: A far sync instance or a recovery appliance was specified as the redo source in a RedoRoutes property rule.; Action: Check the setting of the RedoRoutes property and confirm that a far sync instance or a recovery appliance is not specified as the redo source in the RedoRoutes property rule.
ORA-16690: invalid destination specified for RedoRoutes: Cause: A destination specified in a RedoRoutes rule either appeared in the primary setting of the same rule or was the same member whose RedoRoutes property was being changed.; Action: Ensure that any destination specified in a RedoRoutes rule does not appear in the primary setting of the same rule and is not the member whose RedoRoutes property is being changed.
ORA-16691: cannot remove a configuration member that is specified in a RedoRoutes property: Cause: An attempt was made to remove a database or far sync instance that was specified in another configuration member's RedoRoutes property.; Action: First remove the database or far sync instance from all other member's RedoRoutes property values. Then retry the remove command.
ORA-16692: operation disallowed for a member that is currently shipping redo to another member: Cause: An attempt was made to remove, disable, or convert (physical standby database) a member that currently shipped redo data to another member.; Action: Modify the value of the RedoRoutes property for the member to be removed, disabled, or converted (physical standby database) to not ship redo data for the current primary database and then retry the operation.
ORA-16693: requirements not met for enabling fast-start failover: Cause: The attempt to enable fast-start failover could not be completed because one or more requirements were not met: - The effective redo transport mode for both the primary database and the fast-start failover target standby database must be set to either SYNC or FASTSYNC if the configuration protection mode was set to MaxAvailability mode. - The effective redo transport mode for both the primary database and the fast-start failover target standby database must be set to either SYNC if the configuration protection mode was set to MaxProtection mode. - The effective redo transport mode for both the primary database and the fast-start failover target standby database must be set to ASYNC if the configuration protection mode was set to MaxPerformance mode. - No valid target standby database was specified in the primary database FastStartFailoverTarget property prior to the attempt to enable fast-start failover, and more than one standby database existed in the Oracle Data Guard configuration. - fast-start failover target standby database did not receive redo data directly from the primary database when the protection mode was set to MaxPerformance. - The primary database has multiple routes to the fast-start failover target standby database. - Logical standby databases could not be the fast-start failover targets because the configuration protection mode was set to MaxProtection.; Action: Retry the command after correcting the issue: - Ensure that the effective redo transport mode for both the primary database and the fast-start failover target standby database are either SYNC or FASTSYNC if the configuration protection mode is set to MaxProtection or MaxAvailability. - Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to ASYNC if the configuration protection mode is set to MaxPerformance. - Ensure the RedoRoutes property of the primary includes the name of the fast-start failover target standby database when the protection mode is set to MaxPerformance. - Ensure the RedoRoutes property of the primary database has only one route to the fast-start failover target standby database.
ORA-16694: one or more databases involved in switchover need to be restarted: Cause: An error occurred during the restart of either the old or new primary databases or both in a switchover operation.; Action: Manually restart both the old and new primary databases, including all their Oracle RAC instances if it is an Oracle RAC database.
ORA-16695: a RedoRoutes rule requires asynchronous redo transport mode: Cause: The member could not receive redo data from its source because the source was either a standby database or far sync instance, but the redo transport was not set to asynchronous mode. Standby databases and far sync instances cannot send redo data in synchronous mode. The asynchronous transport mode must be set in either the RedoRoutes parameter of the source member or in the LogXptMode configurable property of the receiving member.; Action: Set the LogXptMode configurable property for the receiving member to ASYNC before changing the RedoRoutes configurable property of the standby database or far sync instance that is to send redo data. Or, specify ASYNC in the RedoRoutes configurable property of either the sending standby database or far sync instance to override the value specified in the LogXptMode configurable property of the receiving member.
ORA-16696: cannot enable the member because its redo source is disabled: Cause: An attempt was made to enable a member, but its redo source was disabled.; Action: Check that the redo source configured for this member (primary, database, physical standby database, or far sync instance) is enabled. If the redo source is disabled, enable it first and then retry the command.
ORA-16697: current role of the member only allows a LOCAL rule in RedoRoutes property: Cause: A logical or snapshot standby database was specified as a redo data source in a RedoRoutes configurable property rule.; Action: Logical and snapshot standbys cannot be configured as a redo source. The only valid rules a logical or snapshot standby database can contain are those that specify LOCAL or its database unique name value in the redo source field of a redo routing rule. Check that the member for which you are setting the RedoRoutes configurable property is a primary database, physical standby database, or a far sync instance. Note that a Oracle Zero Data Loss Recovery Appliance cannot be a redo source.
ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set: Cause: One or more LOG_ARCHIVE_DEST_n initialization parameters that contain a SERVICE attribute for another member in the configuration were set on the new member when attempting to add a standby database or far sync instance to the configuration.; Action: Clear all LOG_ARCHIVE_DEST_n initialization parameters that contain a SERVICE attribute for another member in the configuration on the new member to be added.
ORA-16699: Connect identifier was not specified.: Cause: The connect identifier was not specified for the member being added to the configuration.; Action: Retry the ADD command with a connect identifier for the member to be added.
ORA-16700: The standby database has diverged from the primary database.: Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option. Or, a role change to a logical standby database was performed.; Action: Re-create the standby database from the primary database or flashback the standby database to the same point the primary database had been flashed back to. If the roles are switched back to the original primary database, then no action is necessary.
ORA-16701: Oracle Data Guard broker command failed.: Cause: The command to modify or query the member failed.; Action: Check the Oracle Data Guard broker log file for the reason for the failure and reissue the command.
ORA-16702: Oracle Data Guard broker command warning: Cause: The command to modify or query the member resulted in a warning.; Action: Check the Oracle Data Guard broker log file for the warning and, if necessary, reissue the command.
ORA-16703: cannot set property while the member is enabled: Cause: An attempt was made to change a member property while the member was enabled.; Action: Disable the member first, update the property, and then reenable the member.
ORA-16704: standby database not valid for primary database: Cause: The standby database was not added to the Oracle Data Guard broker configuration because it was not a valid standby database for the primary database.; Action: Add a database to the Oracle Data Guard broker configuration that is a valid standby database to the primary database.
ORA-16706: Oracle Data Guard broker worker process not available: Cause: The Oracle Data Guard broker worker process was not available to service the request.; Action: Contact Oracle Support Services.
ORA-16707: The value of property string is invalid. Valid values are string.: Cause: An invalid property value was specified while broker management of the member was disabled.; Action: Reset the property to a valid value.
ORA-16708: the state supplied to broker is invalid: Cause: The state name specified was invalid for the database.; Action: Check the state name and reissue the command.
ORA-16709: Standby archived log location settings conflict with database recovery area.: Cause: The StandbyArchiveLocation or AlternateLocation property was set to USE_DB_RECOVERY_FILE_DEST, but the initialization parameter DB_RECOVERY_FILE_DEST did not specify a valid destination.; Action: Use a value other than USE_DB_RECOVERY_FILE_DEST for StandbyArchiveLocation or AlternateLocation, or set up a valid database recovery area by setting DB_RECOVERY_FILE_DEST to a valid destination.
ORA-16710: snapshot standby database should be converted back to a physical standby database as soon as possible: Cause: A failover causes this snapshot standby database to enter a state that requires it to be re-created if another failover occurs before it is converted back to a physical standby database.; Action: Reenable the snapshot standby database if it is disabled and convert it back to a physical standby database as soon as possible because the snapshot standby database will have to be re-created if another failover occurs while it is in this state.
ORA-16713: The Oracle Data Guard broker command timed out.: Cause: The Oracle Data Guard broker timed out a health check, get property, or set property command because it took longer than the number of seconds specified by the OperationTimeout configuration property to complete.; Action: Enable support level tracing (the TraceLevel configuration property should be set to SUPPORT) and then examine the Data Guard broker log files for warnings or errors to see what may be causing the operation to be timed out.
ORA-16714: the value of property string is inconsistent with the member setting: Cause: The value of the specified configuration property was inconsistent with member's in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property.; Action: Query the InconsistentProperties property on the member to determine the which properties are set inconsistently and set the properties to make them consisent.
ORA-16715: redo transport-related property string of member "string" is inconsistent: Cause: The value of the specified redo transport-related configuration property of the given member was inconsistent with the primary database redo transport service setting. This may be caused by a change in an initialization parameter that corresponds to a configuration property.; Action: Query the InconsistentLogXptProps property on the primary database to determine which redo transport properties are set inconsistently. Reset the properties on the member to make them consistent with the primary database redo transport settings.
ORA-16716: Unable to clear the LOG_ARCHIVE_DEST_n initialization parameter.: Cause: An attempt to clear the LOG_ARCHIVE_DEST_n initialization parameter failed.; Action: Check the Oracle Data Guard broker log files and the Oracle Database alert log for more information. Resolve any errors and retry the operation. If the problem persists, contact Oracle Support.
ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed: Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.; Action: Contact Oracle Support Services.
ORA-16718: Failed to locate member.: Cause: Oracle Data Guard broker was unable to locate the member in the broker configuration.; Action: Add the member to the broker configuration and retry the command.
ORA-16719: unable to query V$ARCHIVE_DEST fixed view: Cause: The broker failed to query the V$ARCHIVE_DEST fixed view."; Action: Test and clear the problem using SQL*Plus.
ORA-16720: No LOG_ARCHIVE_DEST_n initialization parameters are available.: Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use, or all initialization parameters from LOG_ARCHIVE_DEST_1 through LOG_ARCHIVE_DEST_10 that can support SYNC were in use.; Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that Oracle Data Guard broker can use them to set up the primary database redo transport.
ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters: Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters: Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log files for more details.
ORA-16723: setting AlternateLocation property conflicts with the redo transport setting: Cause: The standby database was not using standby redo logs, and the redo transport service to the standby database is set to a nonzero value for the ReopenSecs property and a value of zero for the MaxFailure property. In this case, the redo transport service will attempt to send redo data to the standby database indefinitely and never switch to the alternate destination.; Action: Any one of the following actions will solve the problem: - add standby redo logs to the standby database. - set ReopenSecs property to zero. - set MaxFailure property to a nonzero value. After performing one of the above actions, reset the standby database AlternateLocation property.
ORA-16724: Cannot resolve gap for one or more members.: Cause: Primary database could not resolve a gap request from one or more members.; Action: To identify the member with the unresolvable gap, check the status of the primary database using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. Copy the missing archived log files from backups or from another member in the configuration that has the files for the member with missing files.
ORA-16727: Cannot close database.: Cause: Oracle Data Guard broker could not close the database.; Action: Terminate all active sessions connected to the database and retry.
ORA-16728: Consistency check for property string found string error.: Cause: Consistency check for specified property caused the specified error.; Action: Check the error message, clear the error, and retry.
ORA-16729: Found error string when validating value for property string.: Cause: An error was encountered while validating the specified value for the configurable property.; Action: Check the error message, clear the error, and retry.
ORA-16730: SQL Apply was not started.: Cause: SQL Apply was not started because there were no pluggable databases opened in read/write mode.; Action: Open at least one pluggable database in read/write mode. Oracle Data Guard will automatically start SQL Apply.
ORA-16731: No pluggable databases are opened in read/write mode.: Cause: Operation failed because there were no pluggable databases opened in read/write mode.; Action: Open at least one pluggable database in read/write mode and retry.
ORA-16732: Oracle Clusterware is restarting the database instance: Cause: The Oracle Data Guard broker operation required this database instance to be shut down and restarted.; Action: If Oracle Clusterware has not already done so, shut down the Oracle instance and then restart it. No action is required if this error was returned from DBMS_DRS.SWITCHOVER and Oracle Clusterware has restarted the database. If this error was returned by DBMS_DRS.CONVERT_TO_PHYSICAL or DBMS_DRS.REINSTATE, wait for the database to start, and wait for the broker to complete initialization using DBMS_DRS.WAIT(WAIT_BOOT, wait time in seconds). Then, for reinstate and convert operations, retry the operation.
ORA-16734: An archive location property is empty while its alternate location property has a non-empty value.: Cause: The ArchiveLocation property value was empty while the AlternateLocation property had a non-empty value. Or, the the StandbyArchiveLocation property value was empty while the StandbyAlternateLocation had a non-empty value.; Action: Ensure that the member's ArchiveLocation property is set to a valid directory location that is different than the value specified for the AlternateLocation property. Or, ensure that the StandbyArchiveLocation property is set to a valid directory location that is different that the value specified for the the StandbyAlternateLocation property.
ORA-16735: primary redo generation suspended: Cause: Redo generation on the primary database was suspended because either the fast-start failover target was unavailable or the network connection between both databases was disrupted.; Action: Ensure that the fast-start failover target standby database is running and the network connection between both databases is restored.
ORA-16736: unable to find the destination entry of member "string" in V$ARCHIVE_DEST: Cause: Either the destination was manually changed or deleted out of Oracle Data Guard broker, or no entry was available for the Oracle Data Guard broker to use.; Action: Clean up the destination setting, remove the unused settings, and reset the redo transport service.
ORA-16737: the redo transport service for member "string" has an error: Cause: A communication problem with the member caused the redo transport to fail.; Action: Query the LogXptStatus property to see the error message. Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16738: redo transport service for member "string" is not running: Cause: The redo transport service for the specified member was not running.; Action: Check the Oracle Data Guard broker log file or the Oracle alert log file for more details. If necessary, start the redo transport service for the member.
ORA-16739: Redo transport service for member "string" is unexpectedly running.: Cause: The redo transport service for the member was expected to be stopped but was found running.; Action: Check the Oracle Data Guard broker log file for more details. If necessary, stop the redo transport service for the member.
ORA-16740: Redo transport service for member "string" incorrectly set as alternate.: Cause: The redo transport service for a member was set as alternate when no other member was set as an alternate for this member.; Action: Re-enable the member or the entire configuration to allow the correct configuration property settings to be propagated to the initialization parameters.
ORA-16741: The LOG_ARCHIVE_DEST_N initialization parameter value for member "string" contains incorrect syntax.: Cause: The value of a LOG_ARCHIVE_DEST_N initialization parameter that was defined in the server parameter file of the primary database contained incorrect syntax. The Data Guard broker was unable to change its value when the redo transport services were enabled.; Action: Fix the syntax error in the primary database server parameter file or remove the entry from the server parameter file. Also, check the values of the redo transport-related properties for the specified member.
ORA-16742: The member "string" exceeded its archived log storage quota.: Cause: The member exceeded its quota for stored archived redo logs.; Action: Remove some archived redo logs from the member or increase its quota.
ORA-16743: cannot determine status of redo transport service for member "string": Cause: The status of redo transport to the specified member could not be determined.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16744: The DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full.: Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Oracle Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list.; Action: Remove unused entries in the DG_CONFIG list, then re-enable the member.
ORA-16745: unable to add DB_UNIQUE_NAME "string" into the DG_CONFIG list because it is full: Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Oracle Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.; Action: Remove some unused entries in the DG_CONFIG list then reenable the member.
ORA-16746: Oracle Data Guard broker cannot mount the database.: Cause: The Oracle Data Guard broker failed to mount the database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16747: logical standby database guard could not be turned on: Cause: The Oracle Data Guard broker could not turn on the logical standby database guard.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16748: Oracle Data Guard broker cannot open the primary database: Cause: The Oracle Data Guard broker failed to open the primary database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16749: The member is disabled manually.: Cause: The Oracle Data Guard broker configuration member was disabled manually.; Action: Enable the Oracle Data Guard broker configuration member.
ORA-16750: failed to activate logical standby database: Cause: The Oracle Data Guard broker failed to activate a logical standby database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16751: failed to enable supplemental logging: Cause: The Oracle Data Guard broker failed to enable supplemental logging during a switchover to a physical standby database in a configuration that also contained logical standby databases.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16753: Oracle Data Guard broker cannot open standby database: Cause: The Oracle Data Guard broker failed to open the standby database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16754: failed to activate physical standby database: Cause: The Oracle Data Guard broker failed to activate the physical standby database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16755: Failed setting an initialization parameter.: Cause: The Oracle Data Guard broker failed to set an initialization parameter using either the ALTER SYSTEM SET or ALTER SYSTEM RESET command.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16757: unable to get the value of this property: Cause: The Oracle Data Guard broker failed to get the value for the specified property because the value for the specified property is not available for the current database role.; Action: If the value of the specified property is not available for the current role of the database, specify this property for a database for which the value is available. Otherwise, check the Oracle Data Guard broker log file for more details.
ORA-16758: The specified apply instance is not running.: Cause: Oracle Data Guard broker could not start Apply services on the specified instance because the instance was not running.; Action: Start the instance and then retry the command.
ORA-16759: cannot start SQL Apply with initial SCN: Cause: The Oracle Data Guard broker failed to start SQL Apply with an initial system change number (SCN).; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16760: Cannot start SQL Apply.: Cause: Oracle Data Guard broker failed to start SQL Apply.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details. If needed, contact Oracle Support Services.
ORA-16761: cannot stop SQL Apply: Cause: The Oracle Data Guard broker failed to stop the SQL Apply service.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16762: invalid database state: Cause: Database was not in the intended state.; Action: Determine the reason why the database is not running in the intended state and reissue the command.
ORA-16763: redo transport service for a member is running: Cause: The redo transport service for a member was running.; Action: For more details, check the status of the primary database using either Oracle Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If necessary, stop the redo transport service to the member.
ORA-16764: redo transport service to a member is not running: Cause: The redo transport service to a member was not running.; Action: For more details, check the status of the primary database using either Oracle Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If necessary, start the redo transport service to the member.
ORA-16765: Redo Apply is running: Cause: Redo Apply was running when it should have been stopped.; Action: If necessary, stop Redo Apply.
ORA-16766: Redo Apply is stopped.: Cause: Redo Apply was stopped when it should have been running.; Action: Check the alert log to see why Redo Apply terminated, correct any problems that may exist, and restart Redo Apply by setting the physical standby database state to APPLY-ON.
ORA-16767: SQL Apply is running: Cause: The Oracle Data Guard broker expected SQL Apply to have been stopped but detected that SQL Apply was still running.; Action: This normally occurs because SQL Apply was stopped using the Oracle Data Guard broker but restarted again outside of the Oracle Data Guard broker, for example through SQL*Plus. Stop SQL Apply using SQL*Plus and retry the required action using the Oracle Data Guard broker.
ORA-16768: SQL Apply is stopped.: Cause: SQL Apply was stopped when it should have been running.; Action: Check the alert log to see why SQL Apply terminated, correct any problems that may exist, and restart SQL Apply by setting the logical standby database state to APPLY-ON.
ORA-16769: The physical standby database is open in read-only mode.: Cause: All instances of the physical standby database were put into a read-only state instead of APPLY-OFF.; Action: Use the EDIT DATABASE SET STATE command to set the database to the APPLY-OFF state. Retry the operation.
ORA-16770: Redo Apply not started since physical standby database is opening: Cause: Redo Apply services could not be started on the physical standby database because it was being opened. The Oracle Data Guard broker will start Redo Apply services once the physical standby database has been opened.; Action: No action required.
ORA-16771: failover to a physical standby database failed: Cause: The Oracle Data Guard broker encountered errors when converting a physical standby database to a primary database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16772: switchover to a standby database failed: Cause: The Oracle Data Guard broker encountered errors when switching over to the specified standby database.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16773: cannot start Redo Apply: Cause: The Oracle Data Guard broker failed to start Redo Apply.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details. If the database is already open, the broker will not start Redo Apply if the Oracle Active Data Guard option is not enabled.
ORA-16774: cannot stop Redo Apply: Cause: The Oracle Data Guard broker failed to stop the Redo Apply service.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16775: target standby database in broker operation has potential data loss: Cause: The target standby database specified for the broker operation did not have all the redo data from the primary database.; Action: Confirm that the redo transport service on the primary database is functioning correctly by checking its status using either Oracle Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. Reissue the broker command once all redo data are available on the target standby database.
ORA-16776: Health check of the redo transport service failed.: Cause: The Oracle Data Guard broker could not complete the health check for the redo transport service.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details on why the health check detected errors. These logs should contain other error messages that indicate the cause of the problem.
ORA-16777: Unable to find the destination entry of a member in V$ARCHIVE_DEST.: Cause: Either a destination (LOG_ARCHIVE_DEST_N initialization parameter) was manually deleted or no LOG_ARCHIVE_DEST_N initialization parameter was available to set up redo transport for the member.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details. If there are sufficient LOG_ARCHIVE_DEST_N initialization parameters available, re-enable the configuration using the DGMGRL CLI ENABLE CONFIGURATION command to ensure all members are receiving redo data. If there are an insufficient number of LOG_ARCHIVE_DEST_N initialization parameters available, consider using the RedoRoutes property to take advantage of available LOG_ARCHIVE_DEST_N initialization parameters on other members so that all members are receiving redo data.
ORA-16778: Redo transport error occurred for one or more members.: Cause: The redo transport service was unable to send redo data to one or more members.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details. These logs should contain other errors messages that indicate the cause of the problem. Also, query the LogXptStatus property to see the errors affecting the redo transport service.
ORA-16779: The LOG_ARCHIVE_DEST_n initialization parameter of a member is set incorrectly.: Cause: The LOG_ARCHIVE_DEST_n initialization parameter value in the server parameter file contained incorrect syntax. The Oracle Data Guard broker failed to update the destination when the redo transport service was enabled.; Action: Check the Oracle Data Guard broker log file to see which member has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties is correct.
ORA-16780: A member exceeded its archived redo log storage quota.: Cause: A member exceeded its archived redo log storage quota.; Action: Check the Oracle Data Guard broker log file to see which member has the problem. Remove older archived redo logs or increase the member's archived redo log storage quota.
ORA-16781: cannot determine status of redo transport service for member: Cause: The status of redo transport to the specified member could not be determined.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more details.
ORA-16782: instance not open for read/write access: Cause: The database was mounted on an instance but not opened for read/write access.; Action: For more details, check the status of the database using either Oracle Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If possible, open the instance manually.
ORA-16783: Cannot resolve gap for member string.: Cause: The primary database could not resolve a gap request from the specified members.; Action: Copy the missing archived redo log files either from a backup or from another member in the configuration that has the missing files for the members.
ORA-16784: member name specified by Dependency property is incorrect: Cause: The member name that should be the value of the DB_UNIQUE_NAME initialization parameter specified in the Dependency property was incorrect.; Action: Reset the Dependency property to the correct name of the member.
ORA-16785: The database is in NOARCHIVELOG mode.: Cause: The database was in NOARCHIVELOG mode when it was either a primary database or when it was a standby database that was being switched over to be a primary database.; Action: Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG command.
ORA-16786: unable to access Oracle Data Guard broker configuration files: Cause: The Oracle Data Guard broker configuration files did not exist or could not be accessed.; Action: Check the Oracle Data Guard broker log file for more details.
ORA-16788: unable to set one or more member configurable property values: Cause: This situation occurred when the broker attempted to set member configurable property values into the member by issuing ALTER SYSTEM or ALTER DATABASE commands. Typical causes of this error are: - The values of redo transport-related properties contain syntax syntax errors. - The value of the LogArchiveTrace property was out of range.; Action: Check the Oracle Data Guard broker log file to see which property has the problem and set the property to the correct value.
ORA-16789: Standby redo logs are configured incorrectly.: Cause: Standby redo logs were not configured, or were configured incorrectly for the member.; Action: Standby redo logs are required when the redo transport mode is set to SYNC or ASYNC. Check the Oracle Data Guard documentation for more information on the correct configuration of standby redo logs.
ORA-16790: The value of the configurable property is invalid.: Cause: Either an invalid property value was entered, or a reset was attempted for a property that had no broker default value.; Action: Set the property to a valid value.
ORA-16791: Unable to check the existence of the standby redo logs.: Cause: The standby redo logs were not found or did not exist.; Action: Ensure the member is mounted and query the V$STANDBY_LOG fixed view to check if the problem is corrected. Retry the command.
ORA-16792: Configurable property value is inconsistent with member setting.: Cause: The value of one or more configurable properties were inconsistent with the in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Oracle Data Guard broker.; Action: Query the InconsistentProperties property on the member or check the Oracle Data Guard broker log file to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the member or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters.
ORA-16793: Logical standby database guard is off.: Cause: The logical standby database was turned off.; Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Oracle Data Guard health check error or warning has cleared.
ORA-16794: database guard is on for primary database: Cause: The database guard was turned on for the primary database.; Action: Issue the ALTER DATABASE GUARD NONE command to turn off the guard and verify that Data Guard health check error or warning is cleared.
ORA-16795: The standby database needs to be re-created.: Cause: A switchover or failover operation caused this database to require re-creation.; Action: Re-create (or flashback) the standby database. Connect to the primary database in the broker configuration and re-enable broker management of that database. Once enabled, connect to the standby database and manage it with the broker. Some client commands cannot be completed on the standby database when in this error state. These commands can be completed successfully on the primary database. Retry the command on the primary database.
ORA-16796: One or more properties could not be imported from the member.: Cause: The broker was unable to import property values for the member being added to the broker configuration. This error indicates: The Oracle Net service name specified in DGMGRL CREATE CONFIGURATION, ADD DATABASE, ADD FAR_SYNC, or ADD RECOVERY_APPLIANCE command was not one that provides access to the member being added. There were no instances running for the member being added.; Action: Remove the member from the configuration using the REMOVE CONFIGURATION, REMOVE DATABASE, REMOVE FAR_SYNC, or REMOVE RECOVERY_APPLIANCE command. Ensure that the member to be added has at least one instance running and that the Oracle Net service name provides access to the running instance. Also, check the broker log file for additional information. Then, reissue the CREATE CONFIGURATION, ADD DATABASE, ADD FAR_SYNC, or ADD RECOVERY_APPLIANCE command.
ORA-16797: member is not using a server parameter file: Cause: The member was not using a server parameter file or the broker was unable to access the server parameter file.; Action: Issue the CREATE SPFILE='..' FROM PFILE='...' command to create a server parameter file and then restart the member to use it.
ORA-16798: unable to complete recovery during failover: Cause: The physical standby database could not complete recovery during failover.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log files to see more details on the reason for the failure.
ORA-16799: Redo Apply is not running: Cause: Either the Oracle Data Guard broker configuration indicated that Redo Apply was turned off, or the MRP0 recovery process was not running. As a result, Redo Apply-related properties could not be set.; Action: Turn on Redo Apply through Oracle Data Guard broker and rerun the command to set the Redo Apply-related properties.
ORA-16800: Redo transport service for a standby database incorrectly set as alternate: Cause: The redo transport service for a member was set as an alternate destination when no other member is set as an alternate destination for this member.; Action: Re-enable the standby database or the entire configuration to allow the correct configuration property settings to be propagated to the initialization parameters.
ORA-16801: Redo transport-related property is inconsistent with member setting.: Cause: The values of one or more redo transport-related configuration properties were inconsistent with the in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Oracle Data Guard broker.; Action: Query the InconsistentLogXptProps property on the primary database or check the Oracle Data Guard broker log file to find which properties are set inconsistently. Reset these properties to make them consistent. Alternatively, enable the member or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters.
ORA-16802: Database role change operation permitted only by Data Guard broker when fast-start failover is enabled.: Cause: Fast-start failover was enabled and a role change was not initiated from a Data Guard broker interface.; Action: Use a Data Guard broker interface to perform a role change.
ORA-16803: Unable to query a database table or fixed view.: Cause: Querying a database table or fixed view failed. The database may not be opened or mounted.; Action: Check the Oracle Data Guard broker log file for more details.
ORA-16804: one or more configuration properties have invalid values: Cause: Oracle Data Guard broker health check detected that one or more configuration properties in the broker configuration had invalid values. The property values were changed while broker management of the member was disabled.; Action: Check Data Guard broker log file for more details on which properties have invalid values and reset them through the Oracle Data Guard broker.
ORA-16806: Supplemental logging is not turned on.: Cause: Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to become the primary database.; Action: Check the Oracle Data Guard broker log file for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS statement to add supplemental logging.
ORA-16807: unable to change configuration protection mode: Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed.; Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for more information.
ORA-16808: primary database is not open: Cause: A prior attempt to open the primary database was disallowed because the primary had shut itself down earlier after being isolated from both the fast-start failover observer and the target standby database for more than FastStartFailoverThreshold seconds. It was assumed that a fast-start failover was underway. Since that time, re-contact with either the observer or the target standby database indicates that no such failover had actually occurred. The primary database can now be opened.; Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN command.
ORA-16809: Multiple warnings detected for the member.: Cause: The broker detected multiple warnings for the member.; Action: Get a detailed status report by checking the status of the member specified using either Enterprise Manager or the DGMGRL CLI SHOW command.
ORA-16810: multiple errors or warnings detected for the member: Cause: The broker detected multiple errors or warnings for the member.; Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW command.
ORA-16811: Apply instance not recorded by the Oracle Data Guard broker.: Cause: The broker did not register an Apply instance for a standby database.; Action: Reenable the standby database to clear the error.
ORA-16812: log apply service not running on apply instance recorded by the broker: Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.; Action: Reenable the standby database to clear the error.
ORA-16813: log apply service not running on apply instance string recorded by the broker: Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.; Action: Reenable the standby database to clear the error.
ORA-16814: Duplicate name specified for observer.: Cause: The observer was not started because an observer with that name was already started.; Action: Use the DGMGRL CLI SHOW OBSERVER command to check the names of the observers that have already been started. Retry the START OBSERVER command with an unused observer name.
ORA-16815: member does not need to be reinstated: Cause: The member specified was either already reinstated or does not need to be reinstated.; Action: No action necessary. Any stale reinstate required status will be cleared after the next health check has completed.
ORA-16816: incorrect database role: Cause: The Oracle Data Guard broker detected that the specified database had a different database role from the one that was recorded in the Oracle Data Guard broker configuration. This could be the result of a failed switchover or failover operation, or a switchover or failover operation performed with SQL*Plus.; Action: Check the Oracle Data Guard broker documentation to see how to recover from failed role change operations, or from role changes that were performed using SQL*Plus for databases managed by Oracle Data Guard broker.
ORA-16817: unsynchronized fast-start failover configuration: Cause: The fast-start failover target standby database was not synchronized with the primary database. As a result, a fast-start failover could not happen automatically in case of a primary database failure.; Action: Ensure that the fast-start failover target standby database is running and that the primary database can ship redo data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases will then be synchronized. The Oracle Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database.
ORA-16818: fast-start failover suspended: Cause: The primary database was intentionally shut down. As a result, the fast-start failover could not take place automatically.; Action: Start the primary database. This effectively restores the ability to automatically perform a fast-start failover in the event of a failure of the primary database.
ORA-16819: fast-start failover observer not started: Cause: The observer for fast-start failover was not started. As a result, fast-start failover could not happen in the case of a primary database failure.; Action: Start the fast-start failover observer by using, for example, the DGMGRL START OBSERVER command.
ORA-16820: fast-start failover observer is no longer observing this database: Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were: - The host where the observer was running was not available. - The network connection between the observer and this database was not available. - The observer process was terminated unexpectedly.; Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Oracle Data Guard configuration and issuing the DGMGRL STOP OBSERVER command, and then start a new observer on another host using the DGMGRL START OBSERVER command.
ORA-16821: Logical standby database dictionary not loaded.: Cause: The logical standby database did not load the dictionary. This status may be returned when attempting to switchover or failover to a logical standby database that did not load its dictionary.; Action: Start SQL Apply on the logical standby database, if it is not already running. Wait for it to reach the APPLYING state.
ORA-16822: New primary database not ready for standby database reinstatement.: Cause: The new primary database, as a result of a logical standby database failover operation, did not fully complete the failover operation.; Action: Wait until the failover operation has completed on the new primary database. Retry the reinstate operation.
ORA-16823: redo transport mode is incompatible for current operation: Cause: The redo transport mode of this member was incompatible for this broker operation.; Action: Reset the LogXptMode member property for this member and retry the broker operation.
ORA-16824: multiple warnings, including fast-start failover-related warnings, detected for the database: Cause: The broker detected multiple warnings for the database. At least one of these warnings may have prevented fast-start failover from occurring.; Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.
ORA-16825: Multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database.: Cause: The broker detected multiple errors or warnings for the database. At least one of these errors or warnings may have prevented a fast-start failover from occurring.; Action: To get a detailed status report, check the status of the database specified using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.
ORA-16826: apply service state is inconsistent with the DelayMins property: Cause: This warning was caused by one of the following reasons: - The apply service was started without specifying the real-time apply option or without the NODELAY option when the DelayMins property was set to zero. - The apply service was started with the real-time apply option or with the NODELAY option when the DelayMins property was set to a value greater than zero.; Action: Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property.
ORA-16827: Flashback Database is disabled: Cause: The broker detected that the Flashback Database feature was disabled. With Flashback Database disabled, the broker would not be able to: - reinstate a database that required reinstatement. - convert a physical standby database to a snapshot standby database. - convert a snapshot standby database to a physical standby database. Flashback Database may been disabled manually with the ALTER DATABASE FLASHBACK DATABASE OFF command or automatically by the database in the event of an error.; Action: Check the database alert log to determine whether Flashback Database was disabled due to errors and then correct the problem. If Flashback Database had been manually disabled, reenable Flashback Database with the ALTER DATABASE FLASHBACK DATABASE ON command. If, after enabling Flashback Database, the database still cannot be reinstated or converted, you must re-create the database from a copy of the primary database.
ORA-16828: invalid value specified for REDO_TRANSPORT_USER initialization parameter: Cause: An invalid value was specified for the REDO_TRANSPORT_USER initialization parameter. The length of the user name exceeded 30 characters.; Action: Check the documentation and specify a new value for the REDO_TRANSPORT_USER initialization parameter.
ORA-16829: fast-start failover configuration is lagging: Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.; Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully transmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.
ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down: Cause: The primary database was isolated from both the observer and target standby database for longer than the seconds specified by the FastStartFailoverThreshold property. A fast-start failover probably occurred. If the FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker will shut down the primary database in this situation.; Action: Ensure one instance of this database is running and the database is mounted on that instance so that the broker may reinstate the old primary database.
ORA-16831: operation not allowed on this member: Cause: The Oracle Data Guard broker operation was not allowed for the specified member of the Oracle Data Guard broker configuration.; Action: Check the documentation for the Oracle Data Guard broker command and then reissue the command with the correct member.
ORA-16832: user-configurable fast-start failover initiated: shutting down: Cause: The broker initiated a fast-start failover to the target standby database because a user-configurable condition was detected on the primary database. In addition, the broker shut down the primary database.; Action: Correct the problem on the old primary database that caused the broker to initiate a fast-start failover, then reinstate the old primary database.
ORA-16833: No such pluggable database at this database: Cause: There was no pluggable database of the given name at the given container database.; Action: Provide the correct pluggable database name or container database name and reissue the command.
ORA-16834: Specified pluggable database is not a standby pluggable database.: Cause: The specified pluggable database name was not a standby pluggable database.; Action: Provide the correct pluggable database name or container database name and retry.
ORA-16835: Source pluggable database was dropped: Cause: The source pluggable database for this standby pluggable database was dropped.; Action: Consider immediate failover to make this a native pluggable database, or remove this standby pluggable database.
ORA-16836: Source pluggable database was unplugged.: Cause: The source pluggable database for this standby pluggable database was unplugged.; Action: Consider immediate failover to make this a native pluggable database, or remove this standby pluggable database.
ORA-16837: Standby pluggable database is not applying redo data.: Cause: Standby pluggable database was not applying redo data.; Action: Ensure recovery was started and is running. Use the EDIT PLUGGABLE DATABASE SET STATE=APPLY-ON to start Redo Apply. If this does not resolve the issue, switch logs at the source database.
ORA-16838: Source pluggable database is not opened in READ WRITE mode.: Cause: The source pluggable database was not opened in READ WRITE mode.; Action: Open the source pluggable database in READ WRITE mode and reissue the command.
ORA-16839: Pluggable database must be in mounted mode.: Cause: Cannot remove the pluggable database which was in open mode.; Action: Close the pluggable database and reissue the command.
ORA-16840: Target pluggable database is not recovering current redo data.: Cause: Target pluggable database was not recovering current redo data from source pluggable database.; Action: Start recovery at the target pluggable database using EDIT PLUGGABLE DATABASE pluggable database name at CDB SET STATE=APPLY-ON;
ORA-16841: Target pluggable database has not applied all redo.: Cause: The target pluggable database had not completed applying all the redo data.; Action: If the target pluggable database is still applying, allow it to apply all the redo and reissue the command. If apply has stopped, check why it has stopped and rectify the situation before proceeding.
ORA-16842: Multitenant container database name specified is incorrect.: Cause: A multitenant container database name was incorrectly specified.; Action: Specify the correct multitenant container database name.
ORA-16844: database does not have a valid fast-start failover target standby database: Cause: Fast-start failover was enabled and the current primary database did not have a value set for the FastStartFailoverTarget configurable property or the value specified for this property was not a valid fast-start failover target standby database.; Action: Disable fast-start failover or ensure that the primary database has a valid fast-start failover target standby database specified by setting the FastStartFailoverTarget configurable property value to a valid standby database.
ORA-16845: unsupported attribute specified for the local destination property: Cause: The value specified for a local destination property contained unsupported attributes.; Action: Ensure that the value specified for the ArchiveLocation, AlternateLocation, StandbyArchiveLocation, or StandbyAlternateLocation property does not contain the SERVICE, ALTERNATE, or VALID_FOR attribute.
ORA-16846: ArchiveLocation and StandbyArchiveLocation should specify different destinations.: Cause: An attempt was made to set the ArchiveLocation and StandbyArchiveLocation configurable properties to the same destination.; Action: Ensure that the ArchiveLocation and StandbyArchiveLocation configurable properties specify different destinations.
ORA-16847: A previous switchover from this database failed with error string.: Cause: A previous switchover operation from this database failed.; Action: Fix the underlying problem and reissue the switchover command again.
ORA-16848: A previous switchover to this database failed with error string.: Cause: A previous switchover operation to this database failed.; Action: Fix the underlying problem and reissue the switchover command again.
ORA-16849: A previous switchover from this database was interrupted and aborted.: Cause: A previous switchover operation from this database was interrupted. The interruption may have been caused by a stalled switchover.; Action: Check the Oracle Data Guard broker log file and the Oracle log file for more information, fix the underlying problem, and then reissue the switchover command.
ORA-16850: A previous switchover to this database was interrupted and aborted.: Cause: A previous switchover operation to this database was interrupted by the user. The interruption may be caused by a stalled switchover.; Action: Check the Oracle Data Guard broker log file and the Oracle log file for more information, fix the underlying problem, and then reissue the switchover command.
ORA-16851: A previous failover to this database failed with error string.: Cause: A previous failover operation to this database failed.; Action: Check the Oracle Data Guard broker log file and the Oracle log file for more information, fix the underlying problem and then reissue the failover command.
ORA-16852: A previous failover to this database was interrupted and aborted.: Cause: A previous failover operation to this database was interrupted because the operation may have stalled.; Action: Check the Oracle Data Guard broker log file and the Oracle log file for more information, fix the underlying problem, and then reissue the failover command.
ORA-16853: apply lag has exceeded specified threshold: Cause: The current apply lag exceeded the value specified by the ApplyLagThreshold configurable property. It may be caused either by a large transport lag or poor performance of apply services on the standby database.; Action: Check for gaps (missing archive log files) on the standby database. If no gap is present, tune the apply services following Maximum Availability Architecture best practice guidelines.
ORA-16854: apply lag could not be determined: Cause: Apply lag could not be determined because either apply services were not running or there was no connectivity between the redo source and standby database.; Action: Start apply services if they are not running. Also, ensure that there is network connectivity between the redo source and standby databases and the redo source is sending redo data to the standby.
ORA-16855: transport lag has exceeded specified threshold: Cause: The current transport lag exceeded the value specified by the TransportLagThreshold configurable property. This error is caused by either poor network performance between the redo source and the member or a network disconnection.; Action: Check the network connection between the redo source and the member. If they are connected, check the network performance between the redo source and the member and tune it according to the Maximum Availability Architecture best practice guidelines.
ORA-16856: transport lag could not be determined: Cause: Transport lag could not be determined because there was no connectivity between the redo source and the member.; Action: Ensure that there is network connectivity between the redo source and the members and that the redo source is working properly.
ORA-16857: member disconnected from redo source for longer than specified threshold: Cause: The amount of time the member was disconnected from the redo source exceeded the value specified by the TransportDisconnectedThreshold configurable database property. It is caused by a lack of network connectivity between the redo source and the member.; Action: Ensure that there is network connectivity between the redo source and the member and that the redo source is working properly.
ORA-16858: last communication time from redo source could not be determined: Cause: The member was never contacted by the redo source.; Action: Ensure that there is network connectivity between the redo source and the member and that the redo source is working properly.
ORA-16859: request terminated because delete, disable, or failover operation is in progress: Cause: The broker terminated a request because it was processing a delete, disable, or failover operation.; Action: Wait for the operation to complete and then retry the request.
ORA-16860: Cannot remove the local configuration when it references a remote configuration.: Cause: The local configuration could not be removed because it was associated with one or more remote configurations.; Action: First, remove all the remote configurations using the REMOVE CONFIGURATION <config_name> command. Then, retry the remove operation for the local configuration using the REMOVE CONFIGURATION command.
ORA-16861: ExternalDestination property requires DB_UNIQUE_NAME attribute: Cause: The value specified for the ExternalDestination property did not contain the DB_UNIQUE_NAME attribute.; Action: Ensure that DB_UNIQUE_NAME is specified as the value for the ExternalDestination property.
ORA-16862: unsupported attribute specified for the ExternalDestination property: Cause: The value specified for the ExternalDestination property contained unsupported attributes.; Action: Ensure that the value specified for the ExternalDestination property does not contain any of these attributes: LOCATION, ALTERNATE, MAX_FAILURE, SYNC, TEMPLATE, MANDATORY, DELAY, NET_TIMEOUT, and VALID_FOR.
ORA-16863: A member whose MaxFailure property is set to zero cannot be part of a RedoRoutes group.: Cause: A member was specified to be part of a RedoRoutes group when the MaxFailure configurable property was set to zero.; Action: Set the MaxFailure property to a nonzero value and retry the command.
ORA-16864: The MaxFailure property cannot be set to zero for a member that is part of a RedoRoutes group.: Cause: An attempt was made to set the MaxFailure configurable property to zero when it was part of a RedoRoutes group.; Action: Set the MaxFailure configurable property to a nonzero value.
ORA-16865: database is closing or is not mounted on the instance: Cause: The Data Guard broker health check was unable to complete because the database was closing or was not mounted on the instance.; Action: No action is required if the database is closing. Mount the database if it is not yet mounted on the instance.
ORA-16866: database converted to transient logical standby database for rolling database maintenance: Cause: This database was converted to a transient logical standby database because a rolling database maintenance operation was in progress.; Action: No action is required. The database will be converted to a primary database when the DBMS_ROLLING.SWITCHOVER procedure is executed or to a physical standby database when the DBMS_ROLLING.FINISH procedure is executed.
ORA-16867: cannot remove a database that is specified in a FastStartFailoverTarget configuration property: Cause: An attempt was made to remove a database that was specified in the FastStartFailoverTarget configuration property of another database.; Action: First, remove the database from all other database's FastStartFailoverTarget configuration property values. Then, retry the REMOVE command.
ORA-16868: Fast-start failover target standby database not viable.: Cause: The fast-start failover target standby database was not viable. As a result, a fast-start failover to this database could not happen automatically.; Action: After the standby database has been re-created from a copy of the new primary database, disable and then reenable the standby database.
ORA-16869: fast-start failover target not initialized: Cause: The standby database was not ready to be a fast-start failover target standby database. Consequently, fast-start failover could not be initiated to this database in the event of a primary database failure.; Action: Ensure that the network connection between the primary and the fast-start failover target standby is functioning properly.
ORA-16871: fast-start failover target switch is not supported: Cause: Automatic switch of the fast-start failover target was not possible because the release of the observer was earlier than 12.2. Consequently, the fast-start failover target switch will not occur even though the primary database has more than one fast-start failover target configured.; Action: Upgrade the Oracle client home to release 12.2 and then stop and restart the observer using the DGMGRL CLI in that Oracle home.
ORA-16872: AlternateLocation and StandbyAlternateLocation should specify different destinations.: Cause: An attempt was made to set the AlternateLocation and StandbyAlternateLocation configurable properties to the same destination.; Action: Ensure that the AlternateLocation and StandbyAlternateLocation configurable properties specify different destinations.
ORA-16873: The observer with the specified name is not started.: Cause: The operation was not allowed because the observer corresponding to the specified name was not started.; Action: Issue the command again after ensuring that the observer corresponding to the specified name is started.
ORA-16874: The specified observer host is invalid.: Cause: The operation was not allowed because there was no registered observer running on the specified host.; Action: Issue the command again after ensuring that there is a registered observer running on the specified host.
ORA-16875: master observer switch is in progress: Cause: The operation was not allowed because a master observer switch was already in progress.; Action: Wait for a few seconds and retry the operation.
ORA-16876: observer name not specified: Cause: The operation was not allowed because an observer name was not specified and there was more than one observer registered.; Action: Retry the command and be sure to specify the observer name or use the term ALL when more than one observer is registered.
ORA-16877: no registered observers: Cause: The operation was not allowed because there were no registered observers.; Action: None
ORA-16878: master observer cannot be stopped: Cause: The master observer cannot be stopped when another observer is registered.; Action: Use the SET MASTEROBSERVER command to establish another observer as the master observer. Then use the STOP OBSERVER command to stop the former master observer.
ORA-16879: fast-start failover cannot be initiated by a non-master observer: Cause: Fast-start failover was initiated by a non-master observer. This can occur if Data Guard Broker starts to switch master observer when fast-start failover is being initiated.; Action: Check the DRC log files of the primary database to see why a master observer switch occurred.
ORA-16880: fast-start failover target switch is in progress: Cause: The operation was not allowed because a fast-start failover target switch was already in progress.; Action: Wait for a few seconds and retry the operation.
ORA-16881: standby database is not protecting the current primary database during rolling database maintenance: Cause: This standby database was a member of the leading group standby databases protecting the future primary database, or was a member of the trailing group standby databases protecting the original primary database during the rolling database maintenance operation.; Action: This issue will be resolved once all the databases have completed the maintenance operation and the DBMS_ROLLING.FINISH procedure is executed.
ORA-16882: rolling database maintenance processing is managing apply services: Cause: Apply services were stopped because a rolling database maintenance operation was in progress.; Action: No action is required. Apply services will be restarted by Oracle.
ORA-16883: unable to translate the DGConnectIdentifier property to a valid connect identifier: Cause: One or more members in the Data Guard configuration could not resolve the connect identifier specified by the DGConnectIdentifier property. The connectivity between the members could not be established for this reason. This might be caused by a missing or invalid tnsnames.ora entry, or an invalid connect descriptor, a missing naming method in sqlnet.ora, or another naming issue.; Action: Use the command VALIDATE NETWORK CONFIGURATION FOR ALL in DGMGRL and verify which database or instance could not resolve the connect identifier. Fix the problem depending on the naming method used in your environment.
ORA-16884: The specified observer name is invalid.: Cause: A reserved keyword (ALL or NONAME) was specified for the observer name for the START OBSERVER command.; Action: Specify a name other than ALL or NONAME and retry the command.
ORA-16885: A member whose RedoCompression property is set to LZO cannot receive redo data in SYNC or FASTSYNC mode.: Cause: A member was specified to receive redo data in SYNC or FASTSYNC mode when the RedoCompression configurable property was set to LZO.; Action: Set the RedoCompression property to a value other than LZO and then retry the command.
ORA-16886: The RedoCompression property cannot be set to LZO for a member that receives redo data in SYNC or FASTSYNC mode.: Cause: An attempt was made to set the RedoCompression configurable property to LZO when it receives redo data in SYNC or FASTSYNC mode.; Action: Set the RedoCompression configurable property to a value other than LZO and then retry the command.
ORA-16887: failed to import Oracle Data Guard broker configuration file: Cause: Fast-start failover was not initiated, even though a condition warranting failover was discovered, because it was enabled in observe-only mode.; Action: In this mode, the observer will only indicate that a fast-start failover would have been initiated. If a fast-start failover is desired, disable fast-start failover to exit the observe-only mode and then re-enable it using the DGMGRL CLI DISABLE FAST_START FAILOVER and ENABLE FAST_START FAILOVER commands.
ORA-16889: Fast-start failover must be disabled before changing between standard and observe-only modes.: Cause: Either the ENABLE FAST_START FAILOVER command was issued when fast- start failover was enabled in observe-only mode, or the ENABLE FAST_START FAILOVER OBSERVE ONLY command was issued when fast-start failover was enabled in standard mode.; Action: Disable fast-start failover using the DISABLE FAST_START FAILOVER command in DGMGRL, and then reissue the command that failed.
ORA-16890: database does not have a valid fast-start failover target standby database in observe-only mode: Cause: Fast-start failover was enabled in observe-only mode and the current primary database did not have a value set for the FastStartFailoverTarget configurable property or the value specified for this property was not a valid fast-start failover target standby database.; Action: Disable fast-start failover or ensure that the primary database has a valid fast-start failover target standby database specified by setting the FastStartFailoverTarget configurable property value to a valid standby database.
ORA-16891: unsynchronized fast-start failover configuration in observe-only mode: Cause: The fast-start failover target standby database was not synchronized with the primary database in observe-only mode. However, manual failover is still allowed in observe-only mode.; Action: Ensure that the fast-start failover target standby database is running and that the primary database can ship redo data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases are synchronized.
ORA-16892: fast-start failover configuration is lagging in observe-only mode: Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property in observe-only mode. However, manual failover is still allowed in observe-only mode.; Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully transmitting redo data. If this condition persists, consider raising the value of the FastStartFailoverLagLimit configuration property.
ORA-16893: Oracle Data Guard broker configuration does not exist in the remote database.: Cause: A broker operation was requested that required a broker configuration to be available at the remote database.; Action: Create an Oracle Data Guard broker configuration at the remote database prior to performing other broker operations for the remote database.
ORA-16894: invalid Oracle Data Guard broker configuration metadata: Cause: This was an internal error.; Action: Contact Oracle Support Services.
ORA-16895: Configuration could not be added because it contains one or more standby databases.: Cause: An attempt was made to add a configuration when one or more configurations already contain one or more standby members.; Action: Remove all members, except the primary database, from both configurations and retry the command.
ORA-16896: configuration name mismatch: Cause: The expected configuration name value did not match the actual configuration name that the broker contacted using the connect identifier that was associated with that configuration.; Action: Verify that the connect identifier correctly connects to the intended configuration. Verify that the name of the configuration the broker expects to find by that connect identifier matches the actual name of the configuration.
ORA-16897: start database to mount mode: Cause: This error was returned by DBMS_DRS.SWITCHOVER because the database must be started to the mount mode to complete the switchover operation. Or, the error was returned from DBMS_DRS.REINSTATE or DBMS_DRS.CONVERT_TO_PHYSICAL when the database must be started to the mount mode to perform the operation.; Action: Start the database to the mount mode, wait for the database to start, and wait for the broker to complete initialization using DBMS_DRS.WAIT(WAIT_BOOT, wait time in seconds). Then, for reinstate and convert operations, retry the operation.
ORA-16898: start database to open mode: Cause: This error was returned by DBMS_DRS.SWITCHOVER because the database must be started to the open mode to complete the switchover operation.; Action: Start the database to the open mode to complete the switchover operation.
ORA-16899: Operation requires a connection to the primary database.: Cause: The operation was rejected because it required a connection to the primary database.; Action: Connect to the primary database and retry the operation.
ORA-16900: change of LogXptMode or RedoRoutes property violates overall protection mode: Cause: The broker did not allow the attempt to change the LogXptMode or RedoRoutes configurable property for the standby database or far sync instance because, if allowed, the overall protection mode for the configuration would have been violated.; Action: If the LogXptMode or RedoRoutes configuration property must be changed for the specified standby database or far sync instance, first downgrade the overall protection mode for the broker configuration. After that operation has completed, the LogXptMode or RedoRoutes configuration property for the standby database can be changed.
ORA-16901: A rolling database maintenance operation is in progress.: Cause: The attempted operation was not allowed because a rolling database maintenance operation was in progress.; Action: Wait for the rolling database maintenance operation to complete. Then retry the operation.
ORA-16902: The specified standby database is not a valid fast-start failover target.: Cause: The attempted operation was not allowed because the specified database is not a valid fast-start failover target because of one of the following reasons: - The specified database was not a physical standby database or logical standby database. - The effective redo transport mode for the standby database was not set to SYNC or FASTSYNC if the protection mode was set to maximum availability mode. - The effective redo transport mode for the standby database was not set to SYNC if the protection mode was set to maximum protection mode. - The effective redo transport mode for the standby database was not set to ASYNC if the protection mode was set to maximum performance mode. - The standby database was not configured to receive redo data directly from the primary database when the protection mode was set to maximum performance mode. - The primary database had one more than one rule in its RedoRoutes property to the standby database. - The specified standby database was a logical standby database when the protection mode was set to maximum protection mode. - The standby database was disabled. - Redo transport-related properties of the standby database were inconsistent with the database settting. - The specified standby database's FastStartFailoverTarget property did not specify the primary database when the standby is a logical standby database.; Action: Check that the specified standby database meets the requirements listed in the Cause section of this error message.
ORA-16903: change of FastStartFailoverLagLimit property violates configuration protection mode: Cause: The attempt to set the FastStartFailoverLagLimit property could not be completed. The new value for the FastStartFailoverLagLimit property did not meet one or more of the following requirements: - The property must be non-zero when the configuration protection mode is set to MaxPerformance mode. - The property must be zero when the configuration protection mode is set to MaxProtection mode.; Action: Check the above requirements and retry the operation.
ORA-16904: Member may be a primary database or is receiving redo data from another primary database.: Cause: A role change operation may have resulted in this member either becoming a primary database or was receiving redo data from a standby database that became a primary database.; Action: Evaluate all members' roles in the configuration and confirm which database should be the primary database before taking further action.
ORA-16905: The member was not enabled yet.: Cause: The Oracle Data Guard broker configuration member was added to the configuration, but not enabled yet.; Action: Enable the Oracle Data Guard broker configuration member.
ORA-16906: The member was shutdown.: Cause: The Oracle Data Guard broker configuration member was shutdown.; Action: This status will be changed when the member is restarted.
ORA-16907: syntax error for the PreferredObserverHosts property: Cause: The change to the PreferredObserverHosts property was disallowed because the new value contained syntax errors.; Action: Check the syntax of the PreferredObserverHosts property and retry the operation.
ORA-16908: The observer is not available for master observer.: Cause: The observer was not available to become the master observer.; Action: Check if the observer's host was specified in the PreferredObserverHosts property of the primary database.
ORA-16909: Operation not allowed when configuration contains a remote configuration.: Cause: Adding a remote configuration or a standby database was not allowed when configuration already contained a remote configuration.; Action: None
ORA-16910: inconsistency detected for one or more pluggable databases: Cause: There was an inconsistency in the Data Guard status for one or more Data Guard pluggable databases.; Action: Use the SHOW PLUGGABLE DATABASE command to determine which protected pluggable databases have an inconsistency. Also check the Oracle alert log files to see more details.
ORA-16911: Redo data from new source database has not been registered.: Cause: Redo data from the new source database was not registered for this standby pluggable database.; Action: Ensure the previous role change command completed successfully. If there had been any errors, address the issue and complete the role change. If this still does not address the issue, try restarting recovery. Use the EDIT PLUGGABLE DATABASE SET STATE=APPLY-ON to start Redo Apply and switch logs at the source database.
ORA-16912: Target pluggable database may have been removed or a role change may have occurred.: Cause: Either a pluggable database switchover or failover occurred, resulting in this pluggable database not having an active target standby pluggable database; or the target standby pluggable database was removed.; Action: If a role change has occurred, after determining which pluggable database is the current source and status of the previous source pluggable database, proceed as follows: - If it is already in the standby role and a switchover has occurred, address the issues that resulted in Redo Apply failing to start and then start Redo Apply. - If it is already in the standby role and a failover has occurred, verify that the issues that necessitated the failover have been addressed and then start Redo Apply services. - If the previous source pluggable database is still in the primary role, and a failover immediate has occurred, address the issues that necessitated the failover, drop the previous source pluggable database, and add it back as the target standby database using the ADD PLUGGABLE DATABASE command, and then start Redo Apply services. Note that Redo Apply can be started using the EDIT PLUGGABLE DATABASE SET STATE=APPLY-ON command.
ORA-16913: cannot remove a remote configuration that sends or receives redo data: Cause: An attempt was made to remove a remote configuration that sent or received redo data.; Action: First, clear redo transport using EDIT CONFIGURATION config name CLEAR AS SOURCE command. Then, retry REMOVE CONFIGURATION config name command.
ORA-16914: Redo Apply has not been started at the standby pluggable database.: Cause: Redo Apply was not started on the standby pluggable database.; Action: To start Redo Apply on all standby pluggable databases, use the ENABLE DATABASE command. To start Redo Apply on a single standby pluggable database, use the EDIT PLUGGABLE DATABASE SET STATE=APPLY-ON command.
ORA-16916: The specified fast-start failover condition is disabled.: Cause: The specified fast-start failover condition or Oracle error number was already disabled.; Action: This is an informational message, no additional action is required.
ORA-16917: Fast-start failover lag limit value is greater than fast-start failover threshold value.: Cause: The FastStartFailoverLagLimit configuration property was set to a value that is greater than the FastStartFailoverThreshold configuration property.; Action: No corrective action is required. Just be aware that this can result in situations where the original primary database may continue to commit transactions, up to the specified lag limit, even after failover has been initiated to the target standby database.
ORA-16950: Remote mapped cursors are not supported by this feature.: Cause: This cursor is a remote mapped cursor which could not be processed locally.; Action: Try to process this statement directly on the remote site.
ORA-16951: Too many bind variables supplied for this SQL statement.: Cause: Binding this SQL statement failed because too many bind variables were supplied.; Action: Pass the correct number of bind variables.
ORA-16952: Failed to bind this SQL statement.: Cause: Binding this SQL statement failed.; Action: Check if bind variables for that statement are properly specified.
ORA-16953: Type of SQL statement not supported.: Cause: This type of SQL statement could not be processed.; Action: n/a
ORA-16954: SQL parse error.: Cause: The specified SQL statement failed to be parsed.; Action: Check if syntax is correct and ensure that this statement can be parsed by the specified user name.
ORA-16955: Unknown error during SQL analyze.: Cause: The specified SQL statement failed to be analyzed.; Action: This is an internal error, please contact Oracle support.
ORA-16956: Only SELECT or DML statements are supported for test execute.: Cause: The specified SQL statement cannot be tested for execute.; Action: n/a
ORA-16957: SQL Analyze time limit interrupt: Cause: This is an internal error code used indicate that SQL analyze has reached its time limit.; Action: n/a
ORA-16958: DML statements running parallel are not supported for test execute.: Cause: The specified DML statement cannot be tested for execute because part of it is running parallel.; Action: n/a
ORA-16959: Statement type has been disabled for SQL Analyze: Cause: The system attempted to analyze a type of statement that was disabled by the current feature.; Action: Try a different feature capable of analyzing this statement type.
ORA-16960: SQL Analyze could not reproduce the desired plan.: Cause: SQL Analyze failed to reproduce a particular plan using an outline.; Action: Check the outline data.
ORA-16961: SQL statement with SQL patch is ignored: Cause: SQL statements with SQL patches are not supported by SQL tuning advisor.; Action: Check the SQL patch information. Rerun SQL repair advisor on that SQL statement for a potential better SQL patch.
ORA-16962: SQL statement attempted to begin an autonomous transaction: Cause: The SQL statement being analyzed attempted to begin an autonomous transaction, which is not supported.; Action: Analyze another statement or remove the autonomous transaction from the current statement.
ORA-16963: The given user or schema is not supported by this feature.: Cause: The SQL statement being analyzed had a parsing user or schema which is not currently supported for SQL Analyze.; Action: Analyze another statement.
ORA-17359: Object store file is too large string string string.: Cause: The operation encountered a file on the object store that exceeds the maximum size for Swift API Dynamic Large Object (DLO) file or files.; Action: Retry the write operation with a file smaller than the first argument in the error code. Split exports using DBMS_CLOUD or Data Pump into multiple smaller files to avoid the limitation.
ORA-17500: ODM err:string: Cause: An error returned by ODM library; Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance
ORA-17501: logical block size string is invalid: Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum; Action: check INIT.ORA file parameters
ORA-17502: ksfdcre:string Failed to create file string: Cause: file creation failed due to either insufficient OS permission or the file already exists; Action: check additional error messages
ORA-17503: ksfdopn:string Failed to open file string: Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.; Action: check additional error messages
ORA-17504: ksfddel:Failed to delete file string: Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file.; Action: check additional error messages
ORA-17505: ksfdrsz:string Failed to resize file to size string blocks: Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.; Action: check additional error messages
ORA-17506: I/O error simulation: Cause: The I/O request was marked with an error because the I/O error simulation event was turned on.; Action: n/a
ORA-17507: I/O request size string is not a multiple of logical block size.: Cause: I/O's were done in a multiple of the logical block size.; Action: Check additional error messages.
ORA-17508: I/O request buffer pointer is not aligned.: Cause: I/O request buffer was not aligned. Check additional information for a buffer pointer value.; Action: Contact Oracle Support Services.
ORA-17509: An attempt to do I/O beyond block1 offset.: Cause: When a file is identified with logical block size of 0, only I/O's to block1 is allowed.; Action: Check additional error messages and contact Oracle Support Services.
ORA-17510: Attempt to do I/O beyond file size string.: Cause: Attempted to do I/O beyond the end of the file.; Action: Check additional error messages, as well as the alert log and trace files to locate and solve the issue. If the error persists, contact Oracle Support.
ORA-17512: Block Verification Failed: Cause: Block Verification after a read operation on a database file failed since the block is media corrupt.; Action: check additional error messages in the trace file and call Oracle Support Services
ORA-17513: dNFS package call failed: Cause: An attempt was made to call a Direct NFS (dNFS) package in a non-dNFS environment.; Action: Ensure that dNFS is enabled and the file can be accessed using dNFS.
ORA-17514: Access to clonedb bitmap file failed: Cause: Accessing the bitmap block file in clonedb environment has encountered an error; Action: check additional error messages in the trace file and call Oracle Support Services
ORA-17515: Creation of clonedb failed using snapshot file string: Cause: Creating a data file in a CloneDB environment failed.; Action: Ensure that the snapshot file passed to CloneDB is not from another CloneDB instance and call Oracle Support Services for further assistance.
ORA-17516: dNFS asynchronous I/O failure: Cause: The asynchronous I/O request failed due to storage server reboot.; Action: Ensure that the storage server does not reboot repeatedly during database operations.
ORA-17517: Database cloning using storage snapshot failed on file string:string: Cause: An invocation of the storage clone command was returned with an error.; Action: Ensure that all necessary steps are performed for storage cloning and check the Oracle trace file for additional information.
ORA-17518: backup file string cannot be found: Cause: Access to the specified backup file was required for Instant Restore.; Action: Ensure that the path and file name are correct for the backup file and the path to the backup file can be accessed from the node of the instance.
ORA-17519: Reason(string): data file string cannot be prepared: Cause: The snapshot layer could not prepare the specified data file.; Action: Ensure that the file does not already exist, is already part of a clone setup, or is being repopulated by an Instant Restore background process. Ensure that the path specified is accessible and writable by the instance.
ORA-17520: data file string cannot be added to repopulation: Cause: Instant Restore could not add the file to the repopulation work queue.; Action: The repopulation process may be working on too many files for the system. Try waiting for some files to complete and try again.
ORA-17521: Instant Restore is not enabled: Cause: The initialization parameters for Instant Restore were not set.; Action: Ensure that Instant Restore initialization parameters are set as required for this feature.
ORA-17522: file string is already being repopulated: Cause: The file was already being repopulated from a previous restore.; Action: Ensure that the file completes restore before you start another restore.
ORA-17523: Instance number cannot spawn repopulation (RPOP) process: Cause: The instance had too many running processes.; Action: Ensure that the maxmimum number of processes initialization parameter is set properly for this feature.
ORA-17524: Repopulation cannot take place - no RPOP processes: Cause: The maxmimum processes initialization parameter was not set properly.; Action: Ensure that the maxmimum number of processes initialization parameter is set properly for this feature. Check the alert log for other related errors.
ORA-17525: Database clone using storage snapshot not supported on file string: Cause: Cloning a database using storage level snapshot is not supported on the underlying storage.; Action: Use storage product that has snapshot based cloning support for Oracle.
ORA-17526: Block size of file string is too small string. Must be >= string.: Cause: Files with block sizes smaller than a minimum size cannot be used for clones backed by snapshot file.; Action: Use files with larger block size.
ORA-17527: Creation of a snapshot failed because the destination string was not a sparse disk group.: Cause: Creating a snapshot failed because the destination disk group was not a sparse disk group.; Action: Ensure that the CREATE_FILE_DEST clause passed to the snapshot copy is in a sparse disk group.
ORA-17528: A read-only file or a file opened read-only cannot be written to: string.: Cause: The file was read-only or was opened read-only and an attempt was made to write to the file, or there was an internal error.; Action: If the file is a parent of a snapshot, then you cannot open read/write, drop or unplug the database. Otherwise, look at the trace file and contact Oracle Support Services.
ORA-17529: creation of compressed file failed: Cause: An attempt was made to create a compressed file on an instance that was not a CloneDB instance.; Action: Set CLONEDB parameter to TRUE and retry the operation.
ORA-17530: snapshot (parent), string, modified after clone (child) created, string: Cause: The snapshot referred to by the clone was incompatible with what the clone was created.; Action: Locate the appropriate snapshot and place it in the named location.
ORA-17531: snapshot (parent)=string modification time string is different from snapshot creation time string recorded in file string: Cause: The clone (child) referred to a snapshot at a specific point in time. The snapshot (parent) currently in that place is at the wrong time.; Action: Locate the appropriate snapshot (parent) and place it in the named location.
ORA-17532: snapshot (parent)=string checkpoint SCN string is different from snapshot checkpoint SCN string recorded in file string: Cause: The clone (child) referred to an SCN at a specific point in time. The snapshot (parent) currently in that place is at the wrong SCN.; Action: Locate the appropriate snapshot (parent) and place it in the named location.
ORA-17533: sparse merge copy operation failure because string and string do not share a valid relationship: Cause: Files specified with the 'sparse_merge_begin' and 'sparse_merge_end' options did not share a valid relationship.; Action: Check additional error messages.
ORA-17534: sparse merge copy operation failure because request to change file access permissions for file string failed: Cause: File access permissions for the file could not be modified.; Action: Check additional error messages.
ORA-17535: sparse merge copy operation failure because it tried to merge to the base parent string: Cause: The sparse merge copy operation was not successful because it tried to merge to the base parent.; Action: Check additional error messages.
ORA-17536: error in creation of database snapshot at SCN string: Cause: There was an error in creating a snapshot of the database files.; Action: Check additional error messages.
ORA-17537: ksfdreopn:string Failed to reopen file string with logical sector size string: Cause: File reopen failed due to either an invalid logical sector size argument or the file size was not a multiple of the given logical sector size.; Action: Check for additional error messages.
ORA-17538: DBMS_DNFS.CLONEDB_RENAMEFILE src or dest is NULL: Cause: The string given as input for the src and/or destination filenames to the DBMS_DNFS.CLONEDB_RENAMEFILE procedure is/are NULL.; Action: Pass a non NULL input string for both src and dest filenames.
ORA-17539: DBMS_DNFS.CLONEDB_RENAMEFILE src or dest has zero length: Cause: The string given as input for the src and/or destination filenames to the DBMS_DNFS.CLONEDB_RENAMEFILE procedure is/are the empty string.; Action: Pass a non-empty input string for both src and dest filenames.
ORA-17610: file 'string' does not exist and no size specified: Cause: An attempt to create a file found neither an existing file nor a size for creating the file.; Action: Specify a size for the file.
ORA-17611: ('string')file 'string' cannot be accessed because it was closed by the background process: Cause: An attempt was made to access the file which went offline or was unidentified.; Action: Check for other errors in the stack.
ORA-17612: Failed to discover Oracle Disk Manager library, return value string: Cause: Discovery of the odm library by calling odm_discover() failed; Action: Contact your storage vendor who has provided the ODM library or call Oracle Support
ORA-17613: Failed to initialize Oracle Disk Manager library: string: Cause: Initialization of the Oracle Disk Manager (ODM) for the thread failed due to insufficient privilege or memory.; Action: Ensure that there is enough system resources available for the Oracle process and that it has access to the ODM library.
ORA-17618: Unable to update block 0 to version 10 format: Cause: An attempt was made to update block 0 to version 10 format.; Action: Check additional error messages and call Oracle Support Services
ORA-17619: max number of processes using I/O slaves in a instance reached: Cause: An attempt was made to start large number of processes requiring I/O slaves.; Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.
ORA-17620: failed to register the network adapter with Oracle Disk Manager library: string: Cause: The Oracle Disk Manager (ODM) library returned an error while trying to register the network adapter.; Action: Ensure that the network adapter name specified in the FILEIO_NETWORK_ADAPTERS initialization parameter is a valid name, and that the Oracle user has the correct access privileges.
ORA-17621: failed to register the memory with Oracle Disk Manager library: Cause: The ODM library returned an error while trying to register the memory.; Action: Contact the Oracle Disk Manager Library provider.
ORA-17622: failed to deregister the memory with Oracle Disk Manager library: Cause: The ODM library returned an error while trying to deregister the memory.; Action: Contact the Oracle Disk Manager Library provider
ORA-17624: Failed to delete directory string: Cause: The directory that was being deleted is still in use or the process had insufficient permission to delete the directory.; Action: check additional error messages.
ORA-17626: ksfdcre: string file exists: Cause: trying to create a database file, but file by that name already exists; Action: verify that name is correct, specify REUSE if necessary
ORA-17627: string: Cause: An error returned by OCI while sending/receiving message from remote instance; Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance
ORA-17628: Oracle error string returned by remote Oracle server: Cause: Oracle server on the remote instance has returned an error.; Action: Look at remote instance alert log/trace file for more information and take appropriate action or contact Oracle Support Services for further assistance
ORA-17629: Cannot connect to the remote database server: Cause: Connecting to the remote server specified by database connect string for netowrk file transfer failed.; Action: Check additional error messages
ORA-17630: Mismatch in the remote file protocol version client string server string: Cause: Cannot communicate with the remote database server as there is a mismatch in the Oracle file protocol version.; Action: Check additional error messages
ORA-17631: dbname 'string' specified by remote server does not match the instance name 'string': Cause: The dbname specified by the remote server is not intended for this instance.; Action: Check the dbname specified in the command of the remote instance and look for further error messages.
ORA-17632: file 'string' is a formatted ASM disk: Cause: An attempt to create a datafile on a device that was formatted for ASM disk failed.; Action: Check that the device specified is not an ASM disk. If you would like to use the disk for datafiles, please clear the disk before you retry the operation.
ORA-17633: Operation not supported as one of the servers involved is not capable of performing the requested operation: Cause: An attempt was made to perform an operation involving two Oracle servers where both servers did not have the capability required for carrying out the operation. It is likely that one of the servers needs a patch or an upgrade to successfully participate in the operation.; Action: Apply the required fix or update on the lower version server. Contact Oracle Support Services for further assistance.
ORA-17634: network file transfer operation aborted: Cause: An error occurred during network file transfer operation.; Action: Check addtional error messages.
ORA-17635: failure in obtaining physical sector size for 'string': Cause: An error occurred while determining the physical sector size from the underlying storage (ASM/ODM/OSD).; Action: Check additional error messages.
ORA-17636: Invalid sparse block format (string). Start block=string. Error=string. File=string: Cause: An error occurred while reading the block on sparse media.; Action: Contact Oracle Support Services.
ORA-17637: failed to change permission on file 'string': Cause: An error occurred while changing permission on a database file.; Action: Verify that Oracle user has ownership on the database file.
ORA-17638: Error in accessing a compressed file string. 'string'.: Cause: An error occurred while accessing a compressed file.; Action: Verify that the Oracle user has permission to access the compressed file.
ORA-17639: Snapshot backing file not read-only 'string'.: Cause: An error occurred while opening the snapshot backing file.; Action: Verify that the backing file has not changed since the creation of the snapshot file and set the backing file permissions to read-only.
ORA-17640: SQL statement execution failed: Cause: The remote SQL statement execution failed on primary database.; Action: Check for the required privileges to run the SQL statement.
ORA-17641: event to release BCT enqueue on Oracle RAC environment with internal error: Cause: An attempt was made to release the enqueue after getting an internal error "krcrfr_nohist". This happens if any bitmap is not keeping in with its oldest_low_krcfde on Oracle RAC environment with block change tracking (BCT) enabled.; Action: None
ORA-17642: failed to get permission on file 'string': Cause: An error occurred while getting permission on a database file.; Action: Verify that the database file exists.
ORA-17643: error while creating or opening destination file 'string': Cause: The destination file or the path provided already existed or could not be accessed.; Action: If the destination file exists, delete the file and retry. Alternately, try with a different destination filename or provide a different path.
ORA-17644: clonedb_renamefile interface is not supported in a multitenant container database.: Cause: An attempt was made to clone a file using clonedb_renamefile interface in a multitenant container database (CDB).; Action: Use the snapshot copy option while creating the pluggable database.
ORA-17675: execution of OFS procedure failed with error:'string': Cause: Either the procedure was called on a platform where Oracle File System (OFS) is not supported or an invalid file system type was provided.; Action: Check additional error messages in the trace file.
ORA-17676: Failed to mount 'string' with error:'string': Cause: Mounting database file system failed with an error.; Action: Check additional error messages in the trace file.
ORA-17677: failed to unmount 'string' with error:'string': Cause: Unmounting database file system failed with an error.; Action: Check additional error messages in the trace file.
ORA-17678: failed to mount 'string' with error:'string': Cause: Mounting of the database file system failed with an error.; Action: Check additional error messages in the trace file.
ORA-17679: failed to makefs 'string' with error:'string': Cause: Either an invalid file system creation option was specified, the file system already existed, or a failure to create the tables occurred.; Action: Check additional error messages in the trace file.
ORA-17680: failed to destroy database file system 'string' with error:'string': Cause: Either the database file system was invalid, it was still busy, it did not exist, or some other error has occurred.; Action: Check additional error messages in the trace file.
ORA-17681: cannot connect to the remote database server: Cause: An attempt was made to connect to the remote server using a shared server connection. This is not supported.; Action: Verify the connect string and use a dedicated server to connect to remote database.
ORA-17682: invalid or missing object store credential: string: Cause: An I/O operation was attempted on a file located in the object store which requires credentials to perform. Valid credentials were not available to perform the operation.; Action: Retry the operation and specify a valid object store credential or set a default credential as a database property.
ORA-18000: invalid outline name: Cause: The parser detected a missing or invalid outline name; Action: reissue the command, specifying a valid outline name.
ORA-18001: no options specified for ALTER OUTLINE: Cause: The parser detected that no clause was specified on the command Our performance tests, which are not typical as they exercise all branches of the code, have shown approximately a 30% performance increase line for ALTER OUTLINE.; Action: Re-issue the command, specifying a valid ALTER OUTLINE clause.
ORA-18002: the specified outline does not exist: Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.; Action: Check for the existence of the outline and try again.
ORA-18003: an outline already exists with this signature: Cause: The signature generation algorithm generates signatures that are are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.; Action: Either re-issue the statement that led to the outline being created with some whitespace added or force the outline to be created in a different category.
ORA-18004: outline already exists: Cause: An outline already exists, either with the specified name, or for the specified SQL text.; Action: Try again with another name.
ORA-18005: CREATE ANY OUTLINE privilege is required for this operation: Cause: CREATE ANY OUTLINE privilege was required for the attempted operation.; Action: Make sure you have CREATE ANY OUTLINE privilege and retry the operation.
ORA-18006: DROP ANY OUTLINE privilege is required for this operation: Cause: DROP ANY OUTLINE privilege was required for the attempted operation.; Action: Make sure you have DROP ANY OUTLINE privilege and retry the operation.
ORA-18007: ALTER ANY OUTLINE privilege is required for this operation: Cause: ALTER ANY OUTLINE privilege was required for the attempted operation.; Action: Make sure you have ALTER ANY OUTLINE privilege and retry the operation.
ORA-18008: cannot find OUTLN schema: Cause: The database creation script that creates this schema must not have been executed.; Action: Review the log files to see what happened when the database was created.
ORA-18009: one or more outline system tables do not exist: Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table; Action: Review the log files to see what happened when the database was created.
ORA-18010: command missing mandatory CATEGORY keyword: Cause: User failed to specify the CATEGORY keyword; Action: Re-issue the command with the CATEGORY keyword included
ORA-18011: the outline specified in the FROM clause does not exist
ORA-18012: select_catalog_role role is required for this operation
ORA-18013: timed out while waiting for resource string
ORA-18014: deadlock detected while waiting for resource string
ORA-18015: invalid source outline signature: Cause: User imported an 8i outline into a 9i database without updating signatures; Action: execute dbms_outln.update_signatures
ORA-18100: XUST0001 - Updating expression in a wrong position: Cause: An updating expression was used in a position other than one of the following: - The topmost expression in the body of a query. - The MODIFY clause of a TRANSFORM expression. - The RETURN clause of a FLWOR expression. - The RETURN clauses of a TYPESWITCH expression in which every RETURN clause contains an updating expression, an empty expression ( ), or a call to the fn:error function. - The THEN and ELSE clauses of a conditional statement in which both the then and else clauses contain either an updating expression, an empty expression ( ), or a call to the fn:error function. - An operand of a comma expression in which each operand is either an updating expression, an empty expression ( ), or a call to the fn:error function. - The content of a parenthesized expression. - The body of a function declaration in which the keyword UPDATING is specified.; Action: None
ORA-18101: XUST0002 - Non-updating expression in a wrong position: Cause: A non-updating expression other than an empty expression ( ) or a call to the fn:error function was used in one of the following positions: - The MODIFY clause of a TRANSFORM expression. - The top-level expression in the body of a function declaration in which the keyword UPDATING is specified.; Action: None
ORA-18102: XUST0003 - Repeated revalidation declaration: Cause: Prolog contained more than one revalidation declaration.; Action: None
ORA-18103: XUTY0004 - Invalid attribute node in the insertion sequence: Cause: The insertion sequence of an INSERT expression contained an attribute following a node that was not an attribute node.; Action: None
ORA-18104: XUTY0005 - invalid target expression for INSERT: Cause: In an INSERT expression where INTO, AS FIRST INTO, or AS LAST INTO was specified, the target expression returned a nonempty result that did not consist of a single element or document node.; Action: Specify a valid target expression for INSERT.
ORA-18105: XUTY0006 - Invalid target expression is used for INSERT.: Cause: Attempted an INSERT expression where BEFORE or AFTER was specified, the target expression returned a nonempty result that did not consist of an element, text, comment, or processing instruction node.; Action: Specify a valid target expression for INSERT.
ORA-18106: XUTY0007 - Invalid target expression for DELETE: Cause: The target expression of a DELETE expression did not return a sequence of zero or more nodes.; Action: None
ORA-18107: XUTY0008 - Invalid target expression for REPLACE: Cause: In a REPLACE expression, the target expression returned a nonempty result that did not consist of a single element, attribute, text,; Action: None
ORA-18108: XUDY0009 - Invalid target expression for REPLACE: Cause: In a REPLACE expression where VALUE OF was not specified, the node returned by the target expression did not have a parent.; Action: None
ORA-18109: XUTY0010 - Invalid replacement sequence for REPLACE: Cause: In a REPLACE expression where VALUE OF was not specified and the target was an element, text, comment, or processing instruction node, the replacement sequence did not consist of zero or more element, text, comment, or processing instruction nodes.; Action: None
ORA-18110: XUTY0011 - Invalid replacement sequence for REPLACE: Cause: In a REPLACE expression where VALUE OF was not specified and the target is an attribute node, the replacement sequence did not consist of zero or more attribute nodes.; Action: None
ORA-18111: XUTY0012 - Invalid target expression for RENAME: Cause: In a RENAME expression, the target expression returned a nonempty result that did not consist of a single element, attribute, or processing instruction node.; Action: None
ORA-18112: XUTY0013 - Invalid COPY expression for TRANSFORM: Cause: In a TRANSFORM expression, a source expression in the copy clause did not return a single node.; Action: None
ORA-18113: XUDY0014 - Modified node was not created by the COPY clause: Cause: In a TRANSFORM expression, the MODIFY clause modified a node that was not created by the COPY clause.; Action: None
ORA-18114: XUDY0015 - Duplicate RENAME for the same target node: Cause: A node was the target of more than one RENAME expression within the same query.; Action: None
ORA-18115: XUDY0016 - Duplicate REPLACE for the same target node: Cause: A node was the target of more than one REPLACE expression (without VALUE OF being specified) within the same query.; Action: None
ORA-18116: XUDY0017 - Duplicate REPLACE for the same target node: Cause: A node was the target of more than one REPLACE VALUE OF expression within the same query.; Action: None
ORA-18117: XUDY0018 - External not updating function returns an updated value: Cause: A function that was declared to be external but not updating returned a nonempty pending update list.; Action: None
ORA-18118: XUDY0019 - External updating function returns an invalid value: Cause: A function that was declared to be both external and updating returned a nonempty data model instance.; Action: None
ORA-18119: XUDY0020 - Deleted node has no parent: Cause: Node was deleted that had no parent before execution of the query began.; Action: None
ORA-18120: XUDY0021 - The result XDM instance violates XDM constraints: Cause: XDM instance resulting from applying all the updates in a query violated constraint specified in [XQuery/XPath Data Model (XDM)]. In this case, none of the updates in the query were made effective.; Action: None
ORA-18121: XUTY0022 - Invalid attribute insertion into a document node: Cause: INSERT expression specified the insertion of an attribute node into a document node.; Action: None
ORA-18122: XUDY0023 - Updating expression introduces a namespace conflict.: Cause: An INSERT, REPLACE, or RENAME expression affected an element node by introducing a new namespace binding that conflicted with one of the existing namespace bindings.; Action: None
ORA-18123: XUDY0024 - Updating expression introduces a namespace conflict: Cause: Effect of a set of updating expressions introduced conflicting namespace bindings into an element node.; Action: None
ORA-18124: XUDY0025 - Invalid QName for processing instruction RENAME: Cause: Target of a RENAME expression was a processing instruction node, and the new name expression returned a QName with a nonempty namespace prefix.; Action: None
ORA-18125: XUST0026 Revalidation mode string is not supported: Cause: Revalidation declaration in a Prolog specified a revalidation mode that is not supported by the current implementation.; Action: None
ORA-18126: XUDY0027 - invalid target expression: Cause: The target expression of an INSERT, REPLACE, or RENAME expression was evaluated to an empty sequence.; Action: Specify a valid target expression.
ORA-18127: XUST0028 - Updating function should not have a return type: Cause: Function declaration specified both UPDATING and a return type.; Action: None
ORA-18128: XUDY0029 - INSERT expression target node doesn't have a parent: Cause: In an INSERT expression where BEFORE or AFTER was specified, a node returned by the target expression did not have a parent.; Action: None
ORA-18129: XUDY0030 - Invalid insertion of an attribute node: Cause: INSERT expression specified the insertion of an attribute node before or after a child of a document node.; Action: None
ORA-18130: FOUP0001 - Invalid 'fn:put' first operand: Cause: The first operand of fn:put was not a node of a supported kind.; Action: None
ORA-18131: FOUP0002 - Invalid 'fn:put' second operand: Cause: The second operand of fn:put was not a valid lexical representation of the xs:anyURI type.; Action: None
ORA-18150: SQL input value cannot be modified in updating expression: Cause: Updating expression was specified as top-level XMLQuery expression.; Action: Use XQuery TRANSFORM expression to copy input value and modify it.
ORA-18160: FTST0001 - FTMildNot operator not supported: Cause: An attempt was made to use the mild not option when the FTMildNot operator was not supported. An implementation that does not support the FTMildNot operator must raise a static error if a full-text query contains a mild not.; Action: Do not use the FTMildNot full-text query operator.
ORA-18161: FTST0002 - FTUnaryNot operator not supported: Cause: An implementation that enforces one of the restrictions on FTUnaryNot must raise a static error if a full-text query does not obey the restriction.; Action: Do not use the FTUnaryNot full-text query operator.
ORA-18162: FTST0003 - FTUnit and FTBigUnit not supported: Cause: An implementation that does not support one or more of the choices on FTUnit and FTBigUnit must raise a static error if a full-text query contains one of those choices.; Action: Do not use the FTUnit or FTBigUnit option.
ORA-18163: FTST0004 - FTScope not supported: Cause: An implementation that does not support the FTScope operator must raise a static error if a full-text query contains a scope.; Action: Do not use the FTScope full-text query operator.
ORA-18164: FTST0005 FTTimes not supported: Cause: An implementation that does not support the FTTimes operator must raise a static error if a full-text query contains a times.; Action: Do not use the FTTimes full-text query operator.
ORA-18165: FTST0006 FTStopwordOption not supported: Cause: An implementation that restricts the use of FTStopwordOption must raise a static error if a full-text query contains a stop word option that does not meet the restriction.; Action: Do not use the FTStopwordOption full-text query operator.
ORA-18166: FTST0007 FTIgnoreOption not supported: Cause: An implementation that restricts the use of FTIgnoreOption must raise a static error if a full-text query contains an ignore option that does not meet the restriction.; Action: Do not use the FTIgnoreOption full-text query operator.
ORA-18167: FTST0008 stop word list not found: Cause: It was a static error if, during the static analysis phase, the query was found to contain a stop word option that referred to a stop word list that was not found in the statically known stop word lists.; Action: Ensure that the stop word list exists.
ORA-18168: FTST0009 language option not supported: Cause: It may be a static error if, during the static analysis phase, the query is found to contain a language identifier in a language option that the implementation does not support. The implementation may choose not to raise this error and instead provide some other implementation-defined behavior.; Action: Do not use the language full-text query option.
ORA-18169: FTST0010 FTOrder not succeeding FTWindow or FTDistance operator: Cause: It is a static error if, during the static analysis phase, an expression is found to use an FTOrder operator that does not appear directly succeeding an FTWindow or an FTDistance operator and the implementation enforces this restriction.; Action: Do not use the FTOrder succeeding FTWindow or FTDistance full-text query operator.
ORA-18170: FTST0011 FTWindow and FTDistance restriction: Cause: An implementation may restrict the use of FTWindow and FTDistance to an FTOr that is either a single FTWords or a combination of FTWords involving only the operators && and ||. If it a static error if, during the static analysis phase, an expression is found that violates this restriction and the implementation enforces this restriction.; Action: Follow FTWindow and FTDistance restriction.
ORA-18171: FTST0012 FTContent not supported: Cause: An implementation that does not support the FTContent operator must raise a static error if a full-text query contains one.; Action: Do not use FTContent full-text query operator.
ORA-18172: FTST0013 more than one language encountered: Cause: It is a static error if, during the static analysis phase, an implementation that restricts the use of FTLanguageOption to a single language, encounters more than one distinct language option.; Action: Do not use more than one language in FTLanguag full-text option.
ORA-18173: FTST0014 score computation restriction: Cause: An implementation may constrain the form of the expression used to compute scores. It is a static error if, during the static analysis phase, such an implementation encounters a scoring expression that does not meet the restriction.; Action: n/a
ORA-18174: FTST0015 FTCaseOption restriction: Cause: It is a static error if, during the static analysis phase, an implementation that restricts the choices of FTCaseOption encounters the "lowercase" or "uppercase" option.; Action: n/a
ORA-18175: FTDY0016 weights invalid: Cause: It is a dynamic error if an implementation that does not support negative weights encounters a weight expression that does not meet the restriction.; Action: Do not use invalid weights value.
ORA-18176: FTDY0017 mild not selection containings StringExclude: Cause: It is a dynamic error if an implementation encounters a mild not selection, one of whose operands evaluates to an AllMatches that contains a StringExclude; Action: n/a
ORA-18177: XQuery full text expression 'string' cannot be evaluated using XML full-text index: Cause: There was no XML full-text index to evaluate the XQuery full text expression filtering XML documents that were stored in an XMLType table or column.; Action: Create an XML full-text index on the XML documents stored in an XMLType table or column and ensure that the XQuery full text expression can be evaluated by an XML full-text index.
ORA-18178: XMLTYPE input to XMLTABLE row expression must use PASSING BY REF clause.: Cause: The XMLTABLE column expression used the XMLTYPE(SEQUENCE) BY REF clause but the XMLType input to the XMLTABLE row expression was not using the PASSING BY REF clause.; Action: Specify the PASSING BY REF clause for XMLTYPE input to the XMLTABLE row expression.
ORA-18179: XMLTABLE column expression must be specified using XMLTYPE(SEQUENCE) BY REF clause.: Cause: The output of the XMLTABLE column expression was passed to an XMLTABLE row expression with PASSING BY REF clause.; Action: Specify the XMLTABLE column expression using the XMLTYPE(SEQUENCE) BY REF clause.
ORA-18180: wrong argument is passed to XMLTABLE row expression using PASSING BY REF clause: Cause: An XML document that was not stored in an XMLType table or column was passed to an XMLTABLE row expression using the PASSING BY REF clause.; Action: Ensure that only XML documents that are stored in an XMLType table or column can be passed in as input to XMLTABLE row expression using the PASSING BY REF clause.
ORA-18181: XQuery full text expression option 'string' is not supported: Cause: An attempt was made to use an XQuery full text expression option that is not supported.; Action: Avoid using an XQuery full text expression option which is not supported.
ORA-18182: FTST0018 unknown thesaurus is used: Cause: During the static analysis phase, the query was found to contain a thesaurus option that referred to a thesaurus that was not found in the statically known thesauri. This is a static error.; Action: Avoid using unknown thesaurus.
ORA-18183: FTST0019 more than one match option of any given match option group is used within a single FTMatchOptions.: Cause: Within the single FTMatchOptions, there was more than one match option of any given match option group. This is a static error.; Action: Avoid using more than one match option of any given match option group is used within a single FTMatchOptions.
ORA-18184: FTDY0020 a query string violates wildcard syntax when wildcards is in effect: Cause: Because wildcards were in effect, the query string violated wildcard syntax. This is a dynamic error.; Action: Fix wildcard syntax when wildcards is in effect.
ORA-18185: query is not parsed correctly: Cause: The query string was not parsed correctly.; Action: Check the syntax of the query string.
ORA-18201: The input MDX string is empty.: Cause: The input MDX (MultiDimensional eXpression) string was empty.; Action: Correct the input MDX (MultiDimensional eXpression) string.
ORA-18202: MDX parser error at line string, column string: string.: Cause: The input MDX (MultiDimensional eXpression) query had invalid syntax.; Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
ORA-18203: The MDX string string is not currently supported.: Cause: The input MDX (MultiDimensional eXpression) query contained an unsupported feature.; Action: Modify the MDX (MultiDimensional eXpression) query to use only supported features.
ORA-18204: The identifier at line string, column string has no closing right bracket (]) character.: Cause: The delimited identifier had no closing right bracket (]) character.; Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
ORA-18205: Invalid arguments for function string.: Cause: The function had invalid arguments.; Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
ORA-18220: The type of the expression in string is string. string is expected.: Cause: The MDX (MultiDimensional eXpression) query had the wrong expression type.; Action: Use an expression with a valid type.
ORA-18221: The argument string in string has different hierarchies.: Cause: An argument had different hierarchies.; Action: Use uniform hierarchies.
ORA-18222: hierarchy string already appears in string: Cause: A hierarchy was repeated.; Action: Use unique hierarchies.
ORA-18223: Invalid identifier for dimension "string".: Cause: More than one hierarchy existed for dimension.; Action: Specify the hierarchy with the dimension.
ORA-18224: invalid cube identifier "string": Cause: The cube identifier was specified incorrectly.; Action: Specify a valid cube identifier.
ORA-18225: The type of argument string of string is string. string is expected.: Cause: An argument of the function had the wrong type.; Action: Use an argument with a valid type.
ORA-18226: argument string does not contain the hierarchy "string" in argument string in string: Cause: The hierarchy in one argument did not exist in the SET argument.; Action: Use an expression with the hierarchy from the set in the SET argument.
ORA-18227: The index is out of range in string.: Cause: The index was out of range.; Action: Use an index within the range.
ORA-18228: The set of argument string of string contains multiple hierarchies. Only one hierarchy is expected.: Cause: The set argument had more than one hierarchy.; Action: Use a SET argument that contains only one hierarchy.
ORA-18229: The hierarchy string is used more than once in arguments of string.: Cause: The hierarchy was used more than once.; Action: Use arguments that contain different hierarchies.
ORA-18230: The member identifier "string" cannot be resolved.: Cause: The member identifier could not be resolved.; Action: Use a valid member identifier.
ORA-18231: The StrToMember argument must be a member identifier when CONSTRAINED is specified.: Cause: The StrToMember argument was not a member identifier and the CONSTRAINED option was specified.; Action: Replace the argument with a member identifier or remove the CONSTRAINED option.
ORA-18232: A set with the name "string" has already been defined.: Cause: More than one set was defined with the same name.; Action: Rename the set so that it has a unique name within the WITH clause of the multidimensional expression (MDX) query.
ORA-18233: The set "string" has a cycle.: Cause: The set definition referenced itself either directly or indirectly using another referenced set.; Action: Change the definition of the set so that it does not directly or indirectly refer to itself.
ORA-18234: The calculated member "string" has the same name as an existing member.: Cause: The name specified for the calculated member was not unique, and matched with another identified member in the hierarchy.; Action: Change the name of the calculated member so that it is unique within the specified hierarchy.
ORA-18235: The calculated member "string" must be a member identifier qualified by hierarchy.: Cause: The calculated member identifier was not a valid member identifier or did not contain a hierarchy qualification.; Action: Change the calculated member identifier so that it is a valid member identifier qualifying the hierarchy.
ORA-18236: The calculated member "string" has a cycle.: Cause: The calculated member referenced itself either directly or indirectly using another referenced calculated member.; Action: Change the definition of the calculated member so that it does not directly or indirectly refer to itself.
ORA-18237: A calculated member with the name "string" has already been defined.: Cause: More than one calculated member was defined with the same name.; Action: Rename the calculated member so that it has a unique name in the WITH clause of the multidimensional expression (MDX) query.
ORA-18238: invalid index "string" for the specified axis: Cause: The index used for a specified axis was invalid (the index for the axis was either not distinct or followed a missing index value).; Action: Correct the semantic error for the MDX (Multidimensional Expression) query.
ORA-18239: There are no available hierarchies to initialize the empty set.: Cause: The empty set could not be initialized because there were no available hierarchies.; Action: Provide valid edges to extract the hierarchies to set the empty set.
ORA-18250: The input parameter to the MDX PL/SQL function is invalid.: Cause: The input parameter in the PL/SQL function was invalid.; Action: Correct the input parameter in the PL/SQL function.
ORA-18252: There are no active MDX queries.: Cause: Either an MDX (MultiDimensional eXpression) query was not executed or all executed queries were closed.; Action: Execute an MDX (MultiDimensional eXpression) query.
ORA-18253: invalid queryID: string: Cause: The MDX (MultiDimensional eXpression) query did not exist in the session with the given queryID.; Action: Specify a valid queryID obtained by calling dbms_mdx_odbo.execute.
ORA-18254: invalid cellRange size: string given, string expected: Cause: The size of the cellRange sequence was not 2 times the number of axes.; Action: Specify a cellRange that has the correct number of elements.
ORA-18255: Invalid cellRange: start (string) is greater than end (string) for axis string: Cause: The start was greater than end for a particular axis in the cellRange.; Action: Specify start less than or equal to end for each axis in the cellRange.
ORA-18256: Invalid axisIndex: string: Cause: The axisIndex was out of range.; Action: Specify an axisIndex greater than or equal to 0 and less than the number of axes.
ORA-18257: The classification value for "string" for measure "string" is invalid for MDX.: Cause: The classification value was invalid for MultiDimensional eXpression.; Action: Replace the Classification value.
ORA-18258: The MDX Slicer contains more than one row.: Cause: The set defining the Slicer resulted in more than one row.; Action: Correct the Slicer portion of the MultiDimensional eXpression query.
ORA-18259: The MDX Schema Rowset type request is invalid.: Cause: The MDX (MultiDimensional eXpression) Schema Rowset type was not a valid value.; Action: Valid MDX (MultiDimensional eXpression) schema Rowset types are between 1 and 10.
ORA-18260: The MDX Schema Rowset Restrictions array and Empty array are not the same size.: Cause: The MultiDimensional eXpression Schema Rowset Restrictions array and the Empty array were not the same size.; Action: Correct the sizes of the Restriction and Empty arrays.
ORA-18261: The TREE_OP restriction value is invalid.: Cause: The given TREE_OP restriction value was invalid.; Action: Provide a valid TREE_OP restriction value.
ORA-18262: invalid empty value: Cause: A value in the given empty list was invalid.; Action: Provide a valid empty value.
ORA-18263: invalid object name and log number combination: Cause: The object name and log number combination did not match the value returned by DBMS_HIERARCHY.VALIDATE_HIERARCHY or VALIDATE_CUBE.; Action: Provide a valid combination of object name and log number and reexecute.
ORA-18264: The 'queryProperties' sequence has an invalid length.: Cause: The 'queryProperties' sequence had an odd number of elements.; Action: Ensure that the 'queryProperties' sequence is either empty or contains an even number of elements.
ORA-18265: key column (%0!s) from table %1!s with value (%2!s) not in dimension (%3!s) star table key column: Cause: There was a row in the fact table with a key column value that was not in the corresponding dimension star table key column.; Action: Ensure that each fact table key column value has a corresponding row in the dimension star table key column.
ORA-18266: analytic view key (string) with value (string) does not determine attribute "string" in hierarchy lowest level key: Cause: The attribute reference found on the analytic view keys could not determine the level key column value of the lowest level in the hierarchy.; Action: Ensure that the attribute reference found on the analytic view key determines the level key column value of the lowest level in the hierarchy.
ORA-18267: key (string) with value (string) for level "string" does not determine attribute "string": Cause: There were rows with the level key column value where the number of distinct values of the attribute column and alternate key attribute were not zero or one.; Action: Ensure that the number of distinct values of the attribute column and alternate key attribute is zero or one for each level key column value.
ORA-18268: alternate key (string) with value (string) for level "string" does not determine level key column "string" value: Cause: There were rows with the alternate key attribute that had non-unique level key values.; Action: Ensure that the alternate key attribute rows all have the same level key value.
ORA-18269: key or alternate key attribute "string" has string NULL values: Cause: A level key column value was defined as NULL when it should be NOT NULL.; Action: Do not define a level key column value to NULL when it should be the NOT NULL value.
ORA-18270: key or alternate key attributes "string" and "string" for level "string" have string mismatched NULL values: Cause: There was a mismatch in the number of NULL values for a SKIP WHEN NULL level.; Action: Ensure that for each SKIP WHEN NULL level, either all level key column values and alternate key attributes are NULL, or all of the level key column values and alternate key attributes are not NULL.
ORA-18271: invalid value for VisualMode query property: Cause: A non-integer value, a negative value, or a value greater than 2 was specified for the VisualMode query property.; Action: Specify an integer value of 0, 1, or 2 for the VisualMode query property.
ORA-18272: analytic view join key (string) with value (string) not unique in dimension star table: Cause: An analytic view join key did not determine all rows in the dimension star table.; Action: Ensure that the analytic view join key determines all rows in the dimension star table.
ORA-18273: analytic view does not contain cache: Cause: An attempt was made to create a materialized view SQL statement for an analytic view that did not contain a cache.; Action: Modify the analytic view to contain a cache or specify an analytic view with a cache.
ORA-18274: invalid analytic view cache index: Cause: The specified analytic view cache index was invalid.; Action: Specify a valid cache index.
ORA-18275: invalid log table format: Cause: The format of the table did not match the default log table.; Action: Ensure that the table provided has a correct definition.
ORA-18276: invalid log table version, upgrade is required: Cause: There was a mismatch in the log table format that corresponds with an older version of the table.; Action: Call DBMS_HIERARCHY.UPGRADE_VALIDATE_LOG_TABLE in order to upgrade to the latest format and retry the operation.
ORA-18277: analytic view key (string) with value (string) for mesaure string contains non-numeric data which cannot be implicitly converted to number: Cause: There was data for a measure with a non-numeric data type with an aggregation method that required implicit conversion to number.; Action: Either correct the data in the fact table column so that all rows are able to be implicitly converted to number, or change the data type or aggregation method.
ORA-18278: key (%0!s) with value (%1!s) for level "%2!s" has non-deterministic order by attribute values: Cause: The order by of the attribute dimension for the level did not result in a deterministic order.; Action: Ensure that the order by of the attribute dimension for the level results in a deterministic order.
ORA-18279: analytic view has been modified: Cause: The analytic view for the MDX query was modified.; Action: Reexecute the MDX query.
ORA-18280: The REFERENCES clause for analytic view dimension "string" is invalid.: Cause: The attributes in the REFERENCES clause must be comprised of either a key or alternate key of a level.; Action: Correct the REFERENCES clause for the analytic view dimension to include a key or alternate key of a level.
ORA-18281: cyclic reference detected for calculated measure "string": Cause: A cyclic reference for a calculated measure was detected.; Action: Correct the cyclic reference for the calculated measure.
ORA-18282: invalid join condition detected on join path "string": Cause: An invalid join condition was detected.; Action: Ensure that each side of the join condition comes from a different source.
ORA-18283: invalid join path reference "string" detected on hierarchy "string": Cause: An invalid join path reference was detected.; Action: Ensure that the join path on the hierarchy refers to a join path on the attribute dimension.
ORA-18284: invalid join paths detected on attribute dimension "string": Cause: Invalid join paths were detected on the attribute dimension.; Action: Ensure that every dimension source is reachable starting with any source and applying join paths of the visited sources.
ORA-18285: Cycle in join paths detected using join path "string" when visiting source "string".: Cause: The current join paths defined for the attribute dimension produced a cycle.; Action: Ensure that every join path contains a single unique path and includes every dim source of every level in the hierarchy exactly once.
ORA-18286: invalid SKIP WHEN NULL specification on a calculation expression detected on hierarchy string: Cause: An invalid SKIP WHEN NULL specification was detected on the calculation expression.; Action: Ensure that SKIP WHEN NULL is only specified on skip level hierarchies.
ORA-18287: invalid level name "string" detected on a calculation expression: Cause: An invalid level name specification was detected on the calculation expression.; Action: Ensure the level exists on the hierarchy specified in the calculation expression.
ORA-18288: parent-child hierarchy "string" detected on a calculation expression level specification: Cause: A parent-child hierarchy was detected on the calculation expression level specification.; Action: Ensure that the level specification on the calculation expression does not reference a parent-child hierarchy.
ORA-18289: parent-child member literal expression detected for level-based hierarchy string: Cause: A parent-child member literal expression was detected for a level-based hierarchy.; Action: Ensure that the parent-child member literal expression is used with a parent-child hierarchy.
ORA-18290: positional member key mismatch detected between member literal expression and hierarchy level "string" on hierarchy "string": Cause: The number of member keys on the member literal expression did not match with those on the corresponding level.; Action: Ensure that the number of member keys on the member literal expression match with those on the corresponding level.
ORA-18291: named member key mismatch detected between member literal expression and hierarchy level "string" on hierarchy "string": Cause: The member keys on the member literal expression did not match those on the corresponding level.; Action: Ensure that the member keys on the member literal expression match those on the corresponding level.
ORA-18292: invoker's rights specified on object referenced within a derived analytic view: Cause: Invoker's rights were specified on an object referenced within a derived analytic view.; Action: Ensure that no object referenced within a derived analytic view has invoker's rights specified.
ORA-18293: aggregation function string used outside of a window expression: Cause: An aggregation function was specified outside of a window expression.; Action: Ensure that an aggregation function is always specified inside of a window expression.
ORA-18294: invalid data type detected on attribute "string": Cause: An invalid data type was detected on an attribute.; Action: Ensure that the attributes are not of LOB, BFILE, or LONG data type.
ORA-18295: duplicate hierarchy string detected in a calculation expression: Cause: The same cube hierarchy was named more than once in the calculation expression.; Action: Specify each cube hierarchy only once in the calculation expression.
ORA-18296: ambiguously defined hierarchy string detected in a calculation expression: Cause: An ambiguously defined hierarchy was detected in a calculation expression.; Action: Qualify the hierarchy with the attribute dimension name.
ORA-18297: invalid data type detected on base measure "string" for use with aggregation operator "string": Cause: An invalid data type was detected on a base measure for use with its specified aggregation operator.; Action: Ensure that the data type of the base measure is valid with the aggregation operator on the base measure.
ORA-18298: The REFERENCES clause for the analytic view dimension "string" does not determine the lowest level of every hierarchy.: Cause: The REFERENCES clause specified for the analytic view dimension was invalid.; Action: The REFERENCES clause must specify the fact key that joins to the attribute defined in the attribute dimension.
ORA-18299: level "string": data type of string expression is invalid: Cause: The specified hierarchical attribute of the specified level had an invalid data type.; Action: Ensure that all attributes of the specified type are character expressions using the same character set.
ORA-18300: level "string": character set of string expression does not match level "string": Cause: The specified hierarchical attribute of the specified level used a character set that did not match the character set of other levels.; Action: Ensure that all attributes of the specified type are character expressions using the same character set. An explicit ALL clause may need to be specified if the default character set of the ALL attributes does not match the character set used in other levels.
ORA-18301: Attribute dimension "string"."string" does not exist.: Cause: The attribute dimension did not exist or the user did not have the required privileges.; Action: Check the spelling of the attribute dimension and ensure that the user has the required privileges.
ORA-18302: Hierarchy "string"."string" does not exist.: Cause: The hierarchy did not exist or the user did not have the required privileges.; Action: Check the spelling of the hierarchy and ensure that the required privileges are granted to the user.
ORA-18303: The REFERENCES clause for the analytic view dimension "string" refers to a level key where the level is marked as SKIP WHEN NULL.: Cause: The REFERENCES clause specified for the analytic view dimension was invalid.; Action: Correct the REFERENCES clause for the analytic view dimension or remove the SKIP WHEN NULL from the attribute dimension level.
ORA-18304: non-measure "string" reference in calculated measure "string": Cause: A non-measure was referenced in a calculated measure.; Action: Ensure that only a measure is referenced in a calculated measure.
ORA-18305: non-aggregation user-defined function string detected in window calculated measure: Cause: A non-aggregation user-defined function was specified for a window calculated measure.; Action: Ensure that a valid user-defined aggregation function is specified for a window calculated measure.
ORA-18306: invalid depth expression specified in a calculated measure: Cause: An invalid depth expression was specified in a calculated measure.; Action: Ensure that the depth expression evaluates to a positive integer no greater than the number of levels in the hierarchy.
ORA-18307: analytic view "string"."string" does not exist: Cause: The analytic view did not exist or the user did not have the required privileges.; Action: Check the spelling of the analytic view and ensure that the required privileges are granted.
ORA-18308: Source "string" cannot be reached using all join paths.: Cause: A source could not be reached using the current join paths defined for the attribute dimension.; Action: Ensure that every join path includes every dim source of every level in the hierarchy exactly once.
ORA-18309: Hierarchy "string"."string" does not reference the attribute dimension "string"."string".: Cause: The hierarchy did not reference the attribute dimension specified.; Action: Ensure that the hierarchy specified is based on the attribute dimension.
ORA-18310: The attribute dimension has no level specification.: Cause: The attribute dimension did not have a level specification.; Action: Specify at least one level in the attribute dimension.
ORA-18312: Dynamic caching is not enabled.: Cause: Analytic View (AV) dynamic caching initialization parameter was not set.; Action: Enable Dynamic AV caching using the appropriate initialization parameter.
ORA-18313: member set expression is not allowed: Cause: A member set expression was specified when a single member expression was expected.; Action: Specify a single member expression.
ORA-18340: Attribute "string" referenced in a key on level "string" does not exist.: Cause: The level key did not reference a valid attribute in the dimension.; Action: Reference an existing attribute in the level key.
ORA-18341: Determined attribute "string" referenced on level "string" does not exist.: Cause: The determined attribute did not reference a valid attribute in the dimension.; Action: Reference an existing attribute in the level.
ORA-18342: Level "string" does not have a member name.: Cause: The level did not have a member name.; Action: Specify a member name for this multi-attribute key level.
ORA-18343: Default measure "string" does not exist.: Cause: The default measure did not reference a valid measure in the Analytic View.; Action: Modify the Analytic View to reference an existing measure.
ORA-18344: Attribute "string" cannot be named using an Oracle reserved word.: Cause: The attribute was named using an Oracle reserved word.; Action: Use a name for the attribute that is not an Oracle reserved word.
ORA-18345: Duplicate metadata object string.: Cause: A duplicate metadata object was specified.; Action: Remove or rename the duplicate metadata object specification.
ORA-18346: Cube hierarchy "string" cannot be set as the default.: Cause: Another default cube hierarchy was specified within the same cube dimension.; Action: Set only one default cube hierarchy within a cube dimension.
ORA-18347: Duplicate level key "string" was detected in level "string".: Cause: A duplicate level key was specified.; Action: Remove or replace the duplicate level key specification.
ORA-18348: invalid hierarchical attribute name "string" specified: Cause: The hierarchical attribute was not defined in the attribute dimension.; Action: Use a hierarchical attribute that is already defined in the attribute dimension.
ORA-18349: Invalid skip level specification on attribute dimension "string".: Cause: The attribute dimension was defined with an invalid skip level specification.; Action: At least one level on the attribute dimension must be NOT NULL.
ORA-18350: Attribute "string" referenced in the ORDER BY clause on level "string" does not exist.: Cause: The specified ORDER BY clause did not reference a valid attribute in the dimension.; Action: Reference an existing attribute in the dimension.
ORA-18351: Cyclic-determined attribute reference detected for level "string".: Cause: A cyclic-determined attribute reference for a level was detected.; Action: Correct the cyclic-determined attribute reference for the level.
ORA-18352: Invalid expression (string) detected on a measure.: Cause: An invalid expression was detected on a measure. A nested select could not be used in an analytic view base measure expression.; Action: An offset expression or member key expression cannot contain a column expression or be an analytic view SQL calculation expression. Ensure the expression does not contain a nested select.
ORA-18353: invalid ALL member name "string" detected on a hierarchy dimension "string": Cause: An invalid ALL member name was detected on a hierarchy dimension.; Action: Ensure that the ALL member name is a constant expression.
ORA-18356: duplicate level name "string" found in Cache Level List: Cause: A duplicate level was found in the level list for an Analytic View Cache Level Group.; Action: Ensure that each Analytic View Cache Level Group contains a distinct list of levels.
ORA-18357: duplicate measure name in Cache Measure List "string": Cause: A duplicate measure was found in the measure list for an Analytic View Cache Level Group.; Action: Ensure that each Analytic View Cache Level Group contains a distinct list of measures.
ORA-18358: Cache Level List hierarchy not found "string".: Cause: A hierarchy specified in the level list for an Analytic View Cache Level Group was not found.; Action: Ensure that each specified hierarchy in the Analytic View Cache Level Group is defined within the Analytic View.
ORA-18359: Cache Level List dimension not found "string".: Cause: A dimension specified in the level list for an Analytic View Cache Level Group was not found.; Action: Ensure that each specified dimension in the Analytic View Cache Level Group is defined within the Analytic View.
ORA-18360: duplicate hierarchy found in Cache Level List string: Cause: Multiple levels for the same hierarchy were found in the level list for an Analytic View Cache Level Group.; Action: Ensure that each Analytic View Cache Level Group contains only one level per hierarchy.
ORA-18361: duplicate Cache Object found in Analytic View Cache: Cause: A duplicate Analytic View Cache Level Group and Measure List combination was found in the Analytic View Cache.; Action: Ensure that for each Measure List the Analytic View Cache Level Group Lists are unique.
ORA-18362: The level type of level "string" is inconsistent with the dimension type.: Cause: The level type was inconsistent with the dimension type.; Action: Ensure the level type is consistent with the dimension type.
ORA-18363: Key "%0!s" is a subset of another key at level "%1!s".: Cause: One of the keys used was a subset of a key at the same level.; Action: An alternate key cannot be a subset of a key at the same level, and a key cannot be a subset of an alternate key at the same level.
ORA-18364: invalid calculated measure clause "string" detected in measure "string": Cause: Invalid syntax was specified for a calculated measure.; Action: Ensure that the syntax is correct.
ORA-18365: invalid argument count on window function "%0!s" detected in calculated measure "%1!s": Cause: An invalid argument count on a window function was specified for a calculated measure.; Action: Ensure that a valid argument count for a window function is specified for a calculated measure.
ORA-18366: The aggregation operator on measure "string" is not allowed in a dynamic level group cache.: Cause: An invalid aggregation operator was specified on a measure in a dynamic level grouping cache.; Action: Remove the measure from the dynamic level group cache or change the aggregation operator.
ORA-18367: The aggregation operator on measure "string" is not allowed in a dynamic across all levels cache.: Cause: An invalid aggregation operator on a measure was specified in a dynamic across all levels cache.; Action: Remove the measure from the dynamic across all levels cache or change the aggregation operator.
ORA-18368: The attribute "string" is not used in the attribute dimension.: Cause: The specified attribute was not used as either a KEY, ALTERNATE KEY, or in the DETERMINES clause of at least one level.; Action: Ensure that all attributes are used as either a KEY, ALTERNATE KEY, or in the DETERMINES clause of at least one level.
ORA-18369: level grouping cache not found or is ambiguous: Cause: The level grouping cache specified in the ALTER statement was not found because it did not exist or there was more than one level grouping cache that matched with the specified level grouping cache.; Action: Ensure that the specified level grouping cache in the ALTER statement is defined in the analytic view and is valid.
ORA-18370: The HIERARCHIES clause may only be specified for cubes.: Cause: A HIERARCHIES clause was used on a table or other non-cube object.; Action: Remove the HIERARCHIES clause.
ORA-18371: invalid cube hierarchy qualification: Cause: Cube hierarchies may only be qualified by dimension in the HIERARCHIES clause.; Action: Remove the additional qualification.
ORA-18372: syntax error in HIERARCHIES list: Cause: Illegal syntax was found in the HIERARCHIES clause.; Action: Ensure that the HIERARCHIES clause only contains a comma delimited list of cube hierarchies enclosed in parentheses.
ORA-18373: missing hierarchy name: Cause: No hierarchy was specified in the HIERARCHIES clause.; Action: Specify at least one hierarchy in the HIERARCHIES clause enclosed in parentheses.
ORA-18374: duplicate hierarchies in HIERARCHIES clause: Cause: The same cube hierarchy was named more than once in the HIERARCHIES clause.; Action: Specify each cube hierarchy only once in the HIERARCHIES clause.
ORA-18375: Cube columns cannot be directly or indirectly referenced in ANSI named column joins.: Cause: A cube column was referenced in an ANSI NATURAL JOIN or USING clause.; Action: Use the ANSI ON clause or Oracle join syntax.
ORA-18376: A hierarchy or analytic view is not allowed here.: Cause: A hierarchy or analytic view was specified in an incorrect location in a statement.; Action: Ensure that the name is correct or remove it.
ORA-18377: Comments on columns of analytic view objects are not supported.: Cause: A comment for a column of an analytic view object was specified.; Action: Do not define comments for columns of analytic views. Use classifications instead.
ORA-18378: calculated measure "string" in cache measure list: Cause: Calculated measures were specified in the cache measure list.; Action: Remove calculated measures from the cache measure list.
ORA-18379: The query hint must start with "/*+".: Cause: Invalid syntax was found in the query hint session parameter.; Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
ORA-18380: the query hint must end with "*/: Cause: Invalid syntax was found in the query hint session parameter.; Action: Ensure that the hint session parameter provided is valid SQL hint syntax.
ORA-18381: the query hint cannot contain any occurrences of "*/" within the text: Cause: Illegal syntax was found in the query hint session parameter.; Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
ORA-18382: analytic view cache "string" does not exist: Cause: Analytic view cache for avmdx_op read did not exist.; Action: Change avmdx_op to read_or_write.
ORA-18383: av_cache can only be specified for analytic views: Cause: The av_cache option was specified for an object that was not an analytic view.; Action: Remove the av_cache option.
ORA-18384: asymmetric condition is currently not supported for derived analyic view: Cause: An asymmetric condition was specified for derived analyic view.; Action: Remove the asymmetric condition.
ORA-18385: recursive WITH clause not allowed in a derived analytic view: Cause: Recursive WITH clause was used in a derived analytic view.; Action: Do not use recursive WITH clause in a derived analytic view.
ORA-18386: CONNECT BY cannot be used with an analytic view or hierarchy.: Cause: The CONNECT BY clause was used in a query from an analytic view or hierarchy.; Action: Enclose the analytic view or hierarchy within a SQL view and use CONNECT BY over the view.
ORA-18387: The FACT ROWS clause may only be specified for analytic views.: Cause: A FACT ROWS clause was specified for an object that was not an analytic view.; Action: Remove the FACT ROWS clause.
ORA-18388: Invalid usage of analytic view aggregation function.: Cause: An analytic view aggregation function was used in the wrong context.; Action: Remove the analytic view aggregation function.
ORA-18389: Aggregation table string is already used as a table in the object.: Cause: The aggregation table specified was already used in the object.; Action: Specify an aggregation table that is not used as a table in the object.
ORA-18390: The FACT ROWS clause cannot be specified for analytic views with any dense dimensions.: Cause: A FACT ROWS clause was specified for an analytic view with at least one dense dimension.; Action: Remove the FACT ROWS clause or change the dimension to be sparse.
ORA-18400: Snowflake table key (string) with value (string) cannot be found in joining table using join path ("string").: Cause: There was a row in a snow flake table with a key column value that was not in the corresponding joining table key column.; Action: Ensure that each snow flake key column value has a corresponding row in the table key column that you are trying to join.
ORA-18401: Many-to-many join caused by key (string) with value (string) using join path ("string").: Cause: There was a key value in the snow flake table that was causing a many-to-many relation between two tables.; Action: Ensure that for a given one-to-many relation the values of the keys are unique.
ORA-18402: Analytic view key (%0!s) with value (%1!s) for measure %2!s contains numeric data which cannot be used with COUNT DISTINCT operator.: Cause: There was non-integer numeric data or numeric data that is out of a valid range for a measure with the COUNT DISTINCT aggregation method; Action: Either correct the data in the fact table column so that all rows are integers and are in a valid range, or change the COUNT DISTINCT aggregation method.
ORA-18450: operation not supported in the middle of a transaction: Cause: The call was made in the middle of a transaction.; Action: Commit or rollback the transaction.
ORA-18451: operation not supported when flashback enabled: Cause: The call was made while flashback was enabled.; Action: Disable flashback.
ORA-18452: unable to retrieve materialized view SQL for dimension "string" because the cache star type is not MATERIALIZED: Cause: An attempt was made to retrieve materialized view SQL for a non-MATERIALIZED dimension.; Action: Alter the dimension so that the cache star type is MATERIALIZED or select a dimension with a MATERIALIZED cache star type.
ORA-18453: extra row for keys (string) with values (string) in aggregation table (string): Cause: An aggregation table key value did not match the source data.; Action: Ensure that the aggregation table rows match the source data.
ORA-18454: missing row for keys (string) with values (string) in aggregation table (string): Cause: An aggregation table key value did not match the source data.; Action: Ensure that the aggregation table rows match the source data.
ORA-18455: invalid action column value for keys (string) with values (string) in change tracking table (string): Cause: A change tracking table key value did not have a valid value for the action column.; Action: Ensure that all action column values in the change tracking table are either I or D.
ORA-18456: invalid row for keys (string) with values (string) in change tracking table (string): Cause: A change tracking table key value row was invalid because it had an I action row that did not match a row in the fact table or a D action row in the change tracking table.; Action: Ensure that all I action change tracking table rows have a corresponding row in the fact table or a corresponding D action change tracking row.
ORA-18500: table has missing or invalid column "string": Cause: The table had a missing or invalid column.; Action: Ensure that the table has the correct columns.
ORA-18501: The query transform cannot be enabled because there is more than one source for the analytic view dimension "string".: Cause: An attempt was made to enable query transform on a snowflake schema.; Action: Limit the number of sources to one for analytic view dimensions when enabling an analytic view for query transform.
ORA-18502: cannot enable query transform because fact source is joined to distinct members of analytic view dimension "string": Cause: An attempt was made to enable query transform with a REFERENCES DISTINCT clause in which the fact and dimension tables did not match.; Action: Match the source of the dimension to the source of the fact when enabling an analytic view for query transform.
ORA-18503: Cannot enable query transform because NORELY was specified and a remote source was detected on "string" in the analytic view.: Cause: An attempt was made to enable query transform NORELY with a remote source.; Action: Specify RELY or do not use remote sources when enabling an analytic view for query transform.
ORA-18504: invalid measure in filter fact clause: Cause: A base measure that was built over an expression that was not a single column was used in the filter fact clause of the derived analytic view.; Action: Ensure that the base measures used in the derived analytic view filter fact clause have a single column expression.
ORA-18505: invalid analytic view dimension "string": Cause: The specified analytic view dimension did not exist in the base analytic view.; Action: Ensure that the specified analytic view dimension exists in the base analytic view.
ORA-18521: analytic view auto caching is not enabled.: Cause: Analytic View (AV) autonomous caching initialization parameter was not set.; Action: Enable AV autonomous caching using the appropriate initialization parameter.
ORA-18551: One or more editioned attribute dimension, hierarchy, or analytic view objects exist that cannot be downgraded.: Cause: There were editioned attribute dimension, hierarchy, or analytic view objects that are not supported in the selected release for downgrade.; Action: Prior to downgrade, drop the editioned attribute dimension, hierarchy, or analytic view objects that cannot be downgraded to the selected release.
ORA-18571: An analytic view dimension may not be specified as dense when the cache clause has been included.: Cause: A dimension has been specified as dense and the cache clause has been included.; Action: Mark all dimensions as sparse or remove the cache clause.
ORA-18572: Either all or none of the Analytic View Caches are required to have a change tracking table.: Cause: Either all or none of the analytic view caches were required to have a change tracking table.; Action: Ensure that either all or none of the analytic view caches have a change tracking table.
ORA-18573: analytic view which uses a change tracking table cannot have a cube source column named "ACTION$": Cause: An analytic view with a change tracking table could not have a cube source column named action$.; Action: Rename the cube source column name or remove the change tracking table.
ORA-18574: analytic view which uses a change tracking table has a measure "string" based on an expression that is not a single column: Cause: An analytic view with a change tracking table could not have a non column expression measure.; Action: Either remove the non column measure from the cache or remove the change tracking table.
ORA-18575: analytic view which uses a change tracking table has a measure "string" with invalid aggregation operator "string": Cause: An analytic view with a change tracking table used an invalid aggregation operator.; Action: Either change the aggregation opeator or remove the change tracking table.
ORA-19000: missing RELATIONAL keyword: Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.; Action: Supply the RELATIONAL keyword in the storage clause
ORA-19001: Invalid storage option specified: Cause: An invalid storage option was specified for the XMLType.; Action: Supply a valid storage option.
ORA-19002: XML Schema URL is missing in storage option.: Cause: An XML Schema URL was not specified in the storage option.; Action: Specify a URL for the XML Schema.
ORA-19003: Missing XML root element name: Cause: A root element in the XMLSchema must be specified if the XML schema is given.; Action: Specify a root element in the XML schema.
ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option: Cause: A duplicate storage option for the XMLType column was specified; Action: Specify a single storage option for an XMLType column
ORA-19005: Duplicate XMLType LOB storage option: Cause: A duplicate storage option for the XMLType column was specified; Action: Specify a single storage option for an XMLType column
ORA-19006: XMLType TYPE storage option not appropriate for storage type: Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option; Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column
ORA-19007: Schema string does not match expected string.: Cause: The given XML document conformed to a different schema than expected.; Action: Insert/Update only the XML documents that conform to that particular schema.
ORA-19008: invalid version of XMLTYPE instance: Cause: An invalid version of XMLTYPE instance was found.; Action: This is possibly due to data corruption, an internal error, or running an older client against a newer version of the database. Ensure that the version of the client can understand the XMLTYPE instance in the database. Contact Oracle Support Services if the error persists.
ORA-19009: Missing XMLSchema keyword: Cause: The XMLSchema keyword is missing; Action: Specify the XMLSchema URL and element name.
ORA-19010: Cannot insert XML fragments: Cause: XML fragments got from extractNode cannot be inserted into the database.; Action: Convert the fragment into a proper XML document before insertion.
ORA-19011: Character string buffer too small: Cause: The string result asked for is too big to return back; Action: Get the result as a lob instead
ORA-19012: Cannot convert XML fragment to the required datatype: Cause: A conversion to a datatype was requested which cannot be performed; Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.
ORA-19013: Cannot create VARRAY columns containing XMLType: Cause: An attempt was made to create a VARRAY column which contains a XMLType; Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead
ORA-19015: Invalid XML tag identifier (string): Cause: An invalid XML identifer was detected during XML generation; Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification
ORA-19016: Attributes cannot occur after element specifications.: Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML.; Action: Change the order of the types so that the attributes occur in the beginning.
ORA-19017: Attributes can only be simple scalars: Cause: Attribute values can only be simple scalar values; Action: Use only simple datatypes for attribute values
ORA-19018: Invalid character in XML tag 'string': Cause: A tag name was found to have an invalid XML character during XML generation.; Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.
ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML: Cause: The value of context passed to GETXML was invalid.; Action: Rewrite the query so that the value of context passed to GETXML is valid.
ORA-19020: invalid dereference of XMLType columns: Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table; Action: You can only dereference the attributes of a base table XMLType column
ORA-19022: Unoptimized XML construct detected.: Cause: The XMLOptimizationCheck variable was enabled and an unrewritten XML construct was detected. This prevents execution of the XML construct.; Action: Ensure that the XML construct is being optimized. See the trace file for further information. Disable the XMLOptimizationCheck variable if you want the unoptimized XML operation to be executed.
ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE: Cause: The first argument passed to the update value operator was not an XMLTYPE.; Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.
ORA-19024: Cursor expression must be named: Cause: The value of context passed to GETXML was invalid.; Action: Rewrite the query so that the value of context passed to GETXML is valid.
ORA-19025: EXTRACTVALUE cannot extract values of multiple nodes: Cause: The specified XPATH expression pointed to more than one node.; Action: Correct the XPATH expression so that it points to exactly one node.
ORA-19026: EXTRACTVALUE can only retrieve value of leaf node: Cause: Given XPath does not point to a leaf node.; Action: Rewrite the query so that a leaf node is returned.
ORA-19028: Invalid ADT parameter passed to toObject() function: Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.; Action: Pass an object of the correct type to toObject().
ORA-19029: Cannot convert the given XMLType to the required type: Cause: The passed in XMLType could not be convert to the required type; Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.
ORA-19030: Method invalid for non-schema based XML Documents.: Cause: The method can be invoked on only schema based xmltype objects.; Action: Don't invoke the method for non schema based xmltype objects.
ORA-19031: XML element or attribute string does not match any in type string.string: Cause: The passed in XML tag does not match any in the object type; Action: Pass a valid canonical XML that can map to the given object type
ORA-19032: Expected XML tag, got no content.: Cause: During a conversion attempt of XML to object, there was a wrong tag name that was present.; Action: Pass a valid canonical XML that can map to the given object type.
ORA-19033: schema mismatch: schema specified in the XML document does not match the schema parameter: Cause: When creating schema-based XML, the schema specified in the XML document was different from the schema that was passed in the 'schema' parameter.; Action: Change the schema parameter to match the schema specified in the XML document.
ORA-19034: Type not supported during schema generation: Cause: The object type contained a type that is not supported for schema generation.; Action: Use a different type or do not generate a schema.
ORA-19035: Invalid select item of the query in newContextFromHierarchy(): Cause: The query did not have a number select item followed by an XMLType select item only.; Action: Ensure that the result set of the query used in the newContextFromHierarchy() function has only two selected items: the first item must be number type and the second item must be XMLType.
ORA-19036: Invalid query result set in newContextFromHierarchy(): Cause: The result set of the query used in the newContextFromHierarchy() function did not have the same property as the result set generated by a CONNECT BY query.; Action: Ensure that the query used in the newContextFromHierarchy() function is a CONNECT BY query or that the query returns a result set having the same property as the result set generated by a CONNECT BY query.
ORA-19037: XMLType result can not be a fragment: Cause: The select item of the query in the newContextFromHierarchy() function was an XML fragment.; Action: Ensure that the select item of the query in the newContextFromHierarchy() function is not an XML fragment.
ORA-19038: Invalid opertions on query context: Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().; Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().
ORA-19039: Keyword string reserved for future use: Cause: The keyword is reserved for future use as a builtin function.; Action: Change the name mentioned above to a different one.
ORA-19040: Element string does not match expected string.: Cause: The given XML document had a different root element than expected.; Action: Insert/Update only the XML documents that conform to that particular schema and element.
ORA-19041: Comment data cannot contain two consecutive '-'s: Cause: The given comment string expression has two consecutive '-'s.; Action: Modify comment string to eliminate one or both of the consevutive '-'s.
ORA-19042: Enclosing tag string cannot be xml in any case combination: Cause: The given enclosing tag matched 'xml' in some case combination; Action: Modify the enclosing tag so that it is not xml in any case combination.
ORA-19043: Multiply nested XMLROOT function disallowed: Cause: An XMLROOT function has an operand that is also an XMLROOT function.; Action: Modify the query so that there are no multiply nested XMLROOT functions.
ORA-19044: character length specified for XMLSerialize is too small.: Cause: An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small.; Action: Modify the query so that the character length specified is larger.
ORA-19045: character set id specified for XMLSerialize not valid: Cause: An XMLSerialize function was called with an invalid value for the caracter set id.; Action: Modify the query so that the character set id is valid.
ORA-19046: Out-of-line tables cannot be shared by two top-level tables (table "string"."string" and the current table being created).: Cause: An attempt was made to share an out-of-line table between two top-level tables.; Action: Use the existing top-level XML table.
ORA-19047: Cannot specify storage for individual VARRAYS: Cause: An attempt was made to combine storage specification for a particular VARRAY with STORE ALL VARRAYS clause.; Action: Either specify storage for individual VARRAYs or use the STORE ALL VARRAYS clause.
ORA-19048: cannot specify VARRAY storage in tableProps: Cause: An attempt was made to store all VARRAYs as tables or LOBs in tableProps.; Action: Do not specify VARRAY store as tables or LOBs in tableProps.
ORA-19051: Cannot use fast path insert for XMLType tables.: Cause: Error while trying to insert into an XMLType table using fast path insert.; Action: Set event 19049 to disable fast path insert and try again.
ORA-19055: Unsupported use of DISABLE XML EXCHANGE: Cause: The option, DISABLE XML EXCHANGE, was specified in a CREATE TABLE statement.; Action: Do not specify DISABLE XML EXCHANGE in a CREATE TABLE statement.
ORA-19057: Internal error: binary XML [string]: Cause: The operation failed due to an internal error.; Action: This is an internal error. Contact Oracle Support Services.
ORA-19058: Enabling XML exchange may cause data corruption.: Cause: An attempt was made to enable XML exchange for a binary XML column or table with a conflicting binary XML column or table.; Action: Use the XML exchange option only if at least one of the two involved tables is empty.
ORA-19059: XML exchange has not been enabled.: Cause: An attempt was made to disable XML exchange on a table that does not have XML exchange enabled.; Action: Use the disable XML exchange option only if the table already has XML exchange enabled.
ORA-19060: operation disallowed on XML token set object: Cause: An attempt was made to perform a disallowed operation on a token set object for binary XML support.; Action: Do not perform the attempted operation on an XML token set object.
ORA-19061: Granular Token Set operations are not supported for tables.: Cause: An attempt was made to perform some Granular Token Set related operations on a non-binary XML table or on an older binary XML table.; Action: Do not perform the attempted operation unless tables support Granular Token Set options.
ORA-19062: XML exchange is already enabled.: Cause: An attempt was made to enable XML exchange on a table that had XML exchange already enabled.; Action: Use the disable XML exchange option only if the table has XML exchange disabled.
ORA-19063: Granular token table does not support schema-based storage.: Cause: An attempt was made to use granular token tables with schema-based storage.; Action: Use non-schema based storage for granular token tables.
ORA-19064: Tablespace has XML token set objects used in another tablespace.: Cause: The tablespace contained an XML token set object that was used by a binary XML table in a different tablespace and dropping it would cause some data to be lost.; Action: Move the XML token set object to a different tablespace.
ORA-19065: cannot drop tablespace with XML token set while XDB tablespace is offline: Cause: The tablespace contained an XML token set object but the metadata could not be read since the XDB default tablespace was offline. By dropping the tablespace, some data may be lost.; Action: Bring XDB default tablespace online.
ORA-19066: XML EXCHANGE is not enabled between the two tables.: Cause: The two tables specified in the EXCHANGE had different XML token sets. By exchanging partitions, some data might get corrupted.; Action: Enable XML EXCHANGE between the tables.
ORA-19067: Unable to create binary granular token on user default tablespace.: Cause: The user default tablespace was full.; Action: Increase the size of the user default tablespace.
ORA-19068: Disabling XML EXCHANGE creates token tables in the SYSTEM tablespace.: Cause: Either the table was in SYSTEM tablespace or it was partitioned and the default tablespace was SYSTEM. Granular token tables are forbidden on SYSTEM tablespace.; Action: Move the table to a different tablespace or change the default tablespace if the table is partitioned.
ORA-19069: Table is already exchanging XML with itself.: Cause: An XML exchange was performed with the same table.; Action: Do not enable XML exchange with the same table.
ORA-19070: cannot enable XML EXCHANGE in this type of table: Cause: XML EXCHANGE was not allowed in global temporary tables or external tables.; Action: Do not use a global temporary table or external table.
ORA-19071: Table does not have an XMLType stored as BINARY XML.: Cause: The table was not an XMLTable or did not have an XMLType column stored as BINARY XML.; Action: Use an XMLType or XMLTable stored as BINARY XML.
ORA-19072: Only STORE AS CLOB is supported with XMLType on the sharded table.: Cause: STORE AS CLOB was not specified with XMLType on the sharded table.; Action: Specify the STORE AS CLOB clause in the query.
ORA-19073: unsupported column type for granular token set enabled table: Cause: An attempt was made to add or modify a column with an unsupported type for a granular token set enabled table.; Action: Do not use user-defined Abstract Data Types (ADTs) or an ANYDATA column with granular token sets.
ORA-19074: Table does not have a granular token set.: Cause: The table was not used with a granular token set.; Action: Use an XMLType stored as BINARY XML with a granular token set.
ORA-19075: Failed to move the token table indexes. Run dbms_csx_admin.RebuildTokenTablesIndexes before using the table.: Cause: An attempt to move the indexes to the given tablespace failed.; Action: Run dbms_csx_admin.RebuildTokenTablesIndexes.
ORA-19076: cannot move the XML token set to tablespace where the table owner does not have privileges: Cause: The table owner did not have privileges in the given tablespace.; Action: Use a tablespace where the table owner has privileges.
ORA-19078: invalid binary XML document: Cause: The binary XML document was corrupt.; Action: Rebuild the binary XML document or contact Oracle Support Services.
ORA-19079: Only STORE AS TRANSPORTABLE BINARY XML is supported with XMLTYPE on a sharded table.: Cause: STORE AS TRANSPORTABLE BINARY XML was not specified with XMLTYPE on a sharded table.; Action: Specify STORE AS TRANSPORTABLE BINARY XML clause in the query.
ORA-19080: This sharding operation is not supported for XMLType.: Cause: XMLType support for a specific operation in sharding was not available.; Action: None
ORA-19081: internal error 'string' received from XML processor: Cause: An internal error was received during an XML operation.; Action: This is an internal error. Contact Oracle Support Services.
ORA-19082: Operation supported only for transportable binary XML.: Cause: XMLType column was not a transportable binary XML.; Action: Use XMLType column stored as transportable binary XML.
ORA-19083: XML Search Index supported only for Transportable Binary XML.: Cause: An attempt was made to create an XML Search Index on an XMLType column that was not stored as transportable binary XML.; Action: Use XMLType column stored as transportable binary XML.
ORA-19100: PASSING or RETURNING keyword expected: Cause: The keyword PASSING or RETURNING was missing.; Action: Specify the PASSING or RETURNING keyword.
ORA-19101: CONTENT keyword expected: Cause: The keyword CONTENT was missing.; Action: Specify the CONTENT keyword.
ORA-19102: XQuery string literal expected: Cause: The string literal containing the XQuery expression was missing.; Action: Specify the XQuery expression as a string literal.
ORA-19103: VALUE keyword keyword: Cause: The keyword VALUE was missing.; Action: Specify the VALUE keyword.
ORA-19104: invalid XQueryX: missing attribute string: Cause: The XQueryX expression was not assigned the expected attribute.; Action: Specify a valid XQueryX.
ORA-19105: invalid XQueryX: expected text node - got string: Cause: The XQueryX expression did not contain a text node as expected.; Action: Specify a valid XQueryX.
ORA-19106: invalid XQueryX: expected string - got string: Cause: The XQueryX expression did not contain the node as expected.; Action: Specify a valid XQueryX.
ORA-19107: invalid XQueryX - unsupported construct - string: Cause: The given XQuery expression contains an unsupported construct.; Action: Specify a valid XQueryX.
ORA-19108: WHITESPACE keyword expected: Cause: The keyword WHITESPACE was missing.; Action: Specify the WHITESPACE keyword.
ORA-19109: RETURNING keyword expected: Cause: The keyword RETURNING was missing.; Action: Specify the RETURNING keyword.
ORA-19110: unsupported XQuery expression: Cause: The specified expression in the XQuery was not supported.; Action: Rewrite the XQuery using the supported expressions.
ORA-19111: error during evaluation of the XQuery expression: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19112: error raised during evaluation: string: Cause: The error function was called during evaluation of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19113: trace function called during evaluation: string: Cause: The trace function was called during evaluation of the XQuery expression.; Action: Check the log file for the trace message.
ORA-19114: XPST0003 - error during parsing the XQuery expression: string: Cause: An error occurred during the parsing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19115: too many context items specified: Cause: More than one context item was specified as input to the XMLQuery function.; Action: Specify a single context item for the XMLQuery function.
ORA-19116: too many xmlspace declarations: Cause: The query prolog contained multiple xmlspace declarations.; Action: Remove the duplicate xmlspace declarations.
ORA-19117: XQST0070 - invalid redefinition of predefined namespace prefix 'string': Cause: The given predefined namespace was being redefined in a namespace declaration.; Action: Remove the namespace declaration that redefines the predefined namespace prefix.
ORA-19118: XQST0066 - duplicate default namespace definition - string: Cause: More than one default namespace declaration used the given namespace URI.; Action: Remove the duplicate default namespace definition.
ORA-19121: duplicate attribute definition - string: Cause: More than one attribute with the same name.; Action: Remove the duplicate attribute definition.
ORA-19122: unsupported XQuery declaration: Cause: The program specified an XQuery declaration that is not supported.; Action: Rewrite the XQuery with a declaration that is supported.
ORA-19123: FORG0003: fn:zero-or-one() called with a sequence containing more than one item: Cause: sequence with more than one item was passed into fn:zero-or-one() function; Action: correct input argument to fn:zero-or-one() function
ORA-19124: FORG0004: fn:one-or-more() called with a sequence containing no items: Cause: sequence containing no items was passed into fn:one-or-more() function; Action: correct input argument to fn:one-or-more() function
ORA-19125: FORG0005: fn:exactly-one() called with a sequence containing zero or more than one item: Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function; Action: correct input argument to fn:exactly-one() function
ORA-19126: XQUERY extension expression contains neither a PRAGMA that is recognized by the implementation nor an expression enclosed in curly braces.: Cause: Either no expression was enclosed in curly braces for the extension expression or the PRAGMA content was not recognized.; Action: Correct the input for the extension expression.
ORA-19127: XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19128: XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19129: XQST0069: A static error is raised if a Prolog contains more than one empty order declaration: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19130: XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19131: XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19132: XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19133: XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19134: XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.): Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19135: XQST0075: An implementation that does not support the validation feature must raise a static error if it encounters a validate expression.: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes and act accordingly.
ORA-19136: XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19137: XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19138: invalid target type of cast or castable expression: Cause: A target type of a cast or castable expression was not a valid atomic type.; Action: Ensure that a cast or castable expression is an atomic type that is in the schema types in-scope and it is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator "?".
ORA-19139: XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces.: Cause: An error occurred while processing the XQuery expression.; Action: Check the detailed error message for the possible causes and act accordingly.
ORA-19140: XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19141: XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19142: FONC0001 = FONC0001: undefined context item: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19143: XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19145: XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19146: XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19147: XQST0089: It is a static error if a variable bound in a FOR clause of a FLWOR expression and its associated positional variable do not have distinct names (expanded QNames).: Cause: An error occurred while processing the XQuery expression.; Action: Check the detailed error message for the cause and act accordingly.
ORA-19148: XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19149: XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19150: XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19151: XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 ... Mi ... M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.): Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19152: FOCH0001 = FOCH0001: codepoint not valid: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19153: FOCH0002: unsupported collation: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19154: FOCH0003: unsupported normalization form: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19155: FOCH0004: collation does not support collation units: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19156: FODC0001: no context document: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19157: FODC0002: error retrieving resource: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19158: FODC0004: invalid argument to fn:collection(): Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19159: FODC0005: invalid argument to fn:doc: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19160: XPST0003 - syntax error: invalid variable name string: Cause: The given XQuery variable does not begin with the '$' sign; Action: Fix the variable name to start with the "$" sign.
ORA-19161: XPTY0004 - XQuery type mismatch: invalid argument type 'string' for function 'string': Cause: The type of the argument that was passed to the given function was not valid.; Action: Fix the argument to be of a type supported by the given function.
ORA-19162: XPTY0004 - XQuery type mismatch: invalid argument types 'string', 'string' for function 'string': Cause: The type of the arguments that were passed to the given function was not valid.; Action: Fix the arguments to be of a type appropriate for the given function.
ORA-19163: XPTY0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function 'string': Cause: The type of the arguments that were passed to the given function was not valid.; Action: Fix the arguments to be of a type appropriate for the given function.
ORA-19164: XQST0085 - It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1].: Cause: There was a zero-length URI in namespace declaration.; Action: Fix the namespace declaration.
ORA-19165: FONS0003: no prefix defined for namespace: Cause: There was a zero-length URI in namespace declaration.; Action: Fix the namespace declaration.
ORA-19166: FONS0003: FONS0004: no namespace found for prefix: Cause: There was a zero-length URI in namespace declaration.; Action: Fix the namespace declaration.
ORA-19167: FONS0005: base uri not defined in the static context: Cause: There was a zero-length URI in namespace declaration.; Action: Fix the namespace declaration.
ORA-19168: FORG0002: invalid argument to fn:resolve-uri(): Cause: There was a zero-length URI in namespace declaration.; Action: Fix the namespace declaration.
ORA-19169: FORG0006: invalid argument type in 'string': Cause: There was a zero-length URI in namespace declaration.; Action: Fix the namespace declaration.
ORA-19171: FORG0007: invalid argument to aggregate function: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19172: FORG0008: both arguments to fn:dateTime have a specified timezone: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19173: FORG0009: error in resolving a relative URI against a base URI in fn:resolve-uri: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19174: FORX0001: invalid regular expression flags: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19175: FORX0002: invalid regular expression: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19176: FORX0003: regular expression matches zero-length string: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19177: FORX0004: invalid replacement string: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19178: FOTY0001: type error: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19179: FOTY0011: Type error. Context item is not a node: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19180: FOTY0012: argument node does not have a typed value: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19181: FOTY0014: type exception: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19182: FORT0001: invalid number of parameters: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19183: FOTY0002: type definition not found: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19184: FOTY0021: invalid node type: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19185: FOAR0002: numeric operation overflow/unflow: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19186: FOCA0001: input value too large for decimal: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19187: FOCA0002: invalid lexical value: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19188: FOCA0003: input value too large for integer: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19189: FOCA0005: NaN supplied as float/double value: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19190: FOER0000: Unidentified error: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19191: FOAR0001: division by zero: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19192: XQST0047: It is a static error if multiple module imports in the same Prolog specify the same target namespace: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19193: XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19194: XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string "?>": Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19195: invalid policy in function ora:contains: Cause: An invalid policy was specified in the ora:contains XQuery function.; Action: Either rename the policy name, policy schema name, or do not specify any policy to pick up the default policy.
ORA-19196: XMLType table or view is not allowed with this form of fn:collection: Cause: The table or view specified in fn:collection was of XMLType.; Action: XMLType table or view is not allowed in the form of fn:collection('oradb:/schema/table/ROW/column'). It has to be a relational table or view.
ORA-19197: Column not found or invalid column type with this form of fn:collection: Cause: The column to be retrieved was not found or was not of XMLType.; Action: The column to be retrieved in the form of fn:collection('oradb:/schema/table/ROW/column') or fn:collection('oradb:/schema/table/ROW[predicate]/column') has to be of XMLType.
ORA-19198: Column not found or invalid column specified in the predicate with this form of fn:collection: Cause: The column specified in the predicate was not found or was not allowed.; Action: The column specified in the predicate in the form of fn:collection('oradb:/schema/table/ROW[predicate]/column') cannot be of XMLType.
ORA-19199: too many levels of nesting: Cause: An XQuery expression contained too many levels of nesting parentheses.; Action: Reduce the level of nesting parentheses.
ORA-19200: invalid column specification: Cause: Not all input arguments were valid columns.; Action: Specify a valid list of columns.
ORA-19201: Datatype not supported: Cause: The particular datatype is not supported in the XMLGEN operator; Action: Specify only supported datatypes as arguments to the XMLGEN operator
ORA-19202: error occurred in XML processingstring: Cause: An error occurred when processing the XML function.; Action: Check the given error message and fix the underlying issue.
ORA-19203: Error occurred in DBMS_XMLGEN processingstring: Cause: An error occurred when processing the DBMS_XMLGEN functions; Action: Check the given error message and fix the appropriate problem
ORA-19204: Non-scalar value 'string' is marked as XML attribute: Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'; Action: Remove the '@' sign, or make the value a scalar.
ORA-19205: Attribute 'string' qualifies a non-scalar value in the select list: Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.; Action: Remove the '@' sign, or make the previous value a scalar.
ORA-19206: invalid value for query or REF CURSOR parameter: Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query or REF CURSOR.; Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.
ORA-19207: The scalar parameter string to XMLELEMENT cannot have an alias.: Cause: The scalar parameter to XMLELEMENT was qualified with an alias.; Action: Remove the AS clause of the scalar element.
ORA-19208: Parameter string of function string must be aliased.: Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.; Action: Specify an alias for the expression by using the AS clause.
ORA-19209: invalid or unsupported formatting argument: Cause: An invalid or unsupported formatting argument was supplied; Action: Change the formatting argument to legal supported values
ORA-19210: Column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'.: Cause: The column specified using setKeyColumn() or setUpdateColumn() did not exist in the table.; Action: Specify a table column instead.
ORA-19211: column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type: Cause: The column specified using setKeyColumn() was a non-scalar type column.; Action: Change the column specified to be a scalar column in the table
ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML(): Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.; Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns
ORA-19213: error occurred in XML processing at linesstring: Cause: An error occurred when processing the specified lines in an XML function.; Action: Check the error message and fix the problem.
ORA-19214: XMLAGG expression not allowed with window functions or first and last expressions: Cause: An attempt was made to use an XMLAGG expression with window functions or first and last expressions.; Action: Do not use window functions or first and last expressions with the XMLAGG expression.
ORA-19221: XPST0001 - XQuery static context component string not initialized: Cause: An unitialized static context component was encountered during the static analysis of the expression.; Action: initialize the given static context.
ORA-19222: XPDY0002 - XQuery dynamic context component string not initialized: Cause: An unitialized dynamic context component was encountered during the evaluation of the expression.; Action: Initialize the particular dynamic context component.
ORA-19223: XPST0003 - syntax error in XQuery expression: Cause: The given XQuery expression contains syntax errors.; Action: Fix the syntax error in the XQuery expression.
ORA-19224: XPTY0004 - XQuery static type mismatch: expected - string got - string: Cause: The expression could not be used because it's static type is not appropriate for the context in which it was used.; Action: Fix the expression to be of the required type or add appropriate cast functions around the expression.
ORA-19225: XPST0005 - XQuery static type error: expected non empty type got empty sequence: Cause: The static type assigned to an expression other than the () expression must not be the empty type.; Action: Fix the expression so it does not return empty sequences.
ORA-19226: XPTY0006 - XQuery dynamic type mismatch: expected string got string: Cause: The expression could not be used because it's dynamic type did not match the required type as specified by XQuery sequencetype matching rules.; Action: Fix the expression to return the expected type or use appropriate cast functions.
ORA-19227: XPTY0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.: Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content.; Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content.
ORA-19228: XPST0008 - undeclared identifier: prefix 'string' local-name 'string': Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context.; Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace.
ORA-19229: XQST0009 - schema import not supported: Cause: A schema import was encountered in the query.; Action: remove the schema import.
ORA-19230: XPST0010 - unsupported axis string: Cause: An unsupported axis was encountered in the given expression.; Action: Remove the unsupported axis from the expression.
ORA-19231: XPST0011 -
ORA-19232: XQST0012 - imported schemas violate validity rules: Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification.; Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique -- that is, the pool of definitions must not contain two or more schema components with the same name and target namespace.
ORA-19233: XQST0013 - invalid pragma: Cause: A pragma was specified whose contents are invalid.; Action: Specify the pragma with the correct contents.
ORA-19234: XQST0014 - invalid or unsupported must-understand extension: Cause: The must-understand extension specified was either invalid or unsupported.; Action: remove the unsupported must-understand extension or fix the error.
ORA-19235: XQST0015 - unsupported must-understand extension: Cause: The XQuery flagger was enabled and the query contained a must-understand extension.; Action: remove the unsupported must-understand extension.
ORA-19236: XQST0016 - module declaration or import not supported: Cause: The given query had a module declaration or module import.; Action: Remove the import module or module declaration.
ORA-19237: XPST0017 - unable to resolve call to function - string:string: Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.; Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19238: XPTY0018 - It is a type error if the result of the last step in a path expression contains both nodes and atomic values: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19239: XPTY0019 - It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value: Cause: The step expression returned a sequence containing an atomic value.; Action: Fix the path expression to return only nodes.
ORA-19240: XPTY0020 - context item must be node in an axis expression: Cause: The context item that was used in the axis epression is not a node.; Action: Change the context item to be a node.
ORA-19241: XPDY0021 - cast to type string failed: Cause: The value inside a cast expression could not be cast to the required type.; Action: Fix the input to the cast expression to be of a castable type.
ORA-19242: XQST0022 - namespace declaration attribute must be a literal: Cause: The namespace declaration attribute was not a literal string.; Action: Fix the namespace declaration to be a literal string.
ORA-19243: XQTY0023 - invalid document node content in element constructor: Cause: The content sequence in an element constructor contained a document node.; Action: Change the content of the element constructor so that it does not contain a document node.
ORA-19244: XQTY0024 - invalid attribute node in element constructor: Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node.; Action: Change the content sequence of the element constructor so that it does not contain the attribute node.
ORA-19245: XQDY0025 - duplicate attribute name string: Cause: The content sequence of the element constructor contained more than one attribute that had the same name.; Action: Remove the duplicate attributes.
ORA-19246: validation failed - element string not found in in-scope element declarations: Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations.; Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration.
ORA-19247: XQDY0027 - validation error: Cause: An error was encountered during the validation of the expression.; Action: Fix the validation error.
ORA-19248: XQTY0028 - invalid node in document constructor: Cause: The content sequence in a document constructor contained either a document or an attribute node.; Action: Fix the content so it does not contain any of the above node types.
ORA-19249: XQDY0029 - value does not match facet of the target type: Cause: The input value to a cast expression did not satisfy the facets of the target type.; Action: Fix the value to conform to the facets of the target type.
ORA-19250: XQTY0030 - too many values to validate expression: Cause: The argument of a validate expression returned more than one element or document node.; Action: Fix the argument of the validate expression to return a single element or document node.
ORA-19251: XQST0031 - unsupported query version: Cause: The query version specified in the prolog was not supported.; Action: Supply the version of the query that is supported.
ORA-19252: XQST0032 - too many declarations for base URI: Cause: The query prolog contained multiple declarations for the base URI.; Action: Remove the duplicate definitions for the base URI.
ORA-19253: XQST0033 - too many declarations for namespace prefix string: Cause: The query prolog contained multiple declarations for the same namespace prefix.; Action: Remove the duplicate definitions for the namespace prefix.
ORA-19254: XQST0034 - too many declarations for function string: Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName.; Action: Remove the duplicate function definitions.
ORA-19255: XQST0035 - too many declarations of string in imported schemas: Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope.; Action: Fix the schema imports to remove the name conflict.
ORA-19256: XQST0036 - missing type definitions in imported module: Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module.; Action: Fix the module definintion to include the in-scope type definition.
ORA-19257: XQST0037 - function or variable string in module already defined: Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module.; Action: Remove the conflicting declarations.
ORA-19258: XQST0038 - unsupported or duplicate default collation specified: Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported.; Action: Remove the duplicate definition or specify a supported collation.
ORA-19259: XQST0039 - duplicate parameter name string in function declaration: Cause: The function declaration contained more than one parameter with the same name.; Action: Fix the function declaration to remove the duplicate parameters.
ORA-19260: XQST0040 - invalid namespace node in element constructor: Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node.; Action: Remove the namespace node in the element constructor.
ORA-19261: XQDY0041 - non empty URI in QName: Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty.; Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part.
ORA-19262: XQST0042 - namespace constructor not inside an element constructor: Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor.; Action: Fix the namespace constructor to be inside an element constructor.
ORA-19263: XQST0043 - duplicate namespace prefix string: Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix.; Action: Remove the duplicate namespace definitions.
ORA-19264: XQDY0044 - invalid namespace in attribute constructors: Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns).; Action: Change the namespace for the computed attribute constructor.
ORA-19265: XQST0045 - invalid or unknown prefix string in function declaration: Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local.; Action: Fix the function declaration to have the correct prefix.
ORA-19266: XQST0046 - invalid URI: Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema.; Action: Fix the URI.
ORA-19267: module string not found: Cause: The module with the given target URI could not be found.; Action: Fix the prolog to import only available modules.
ORA-19268: XQST0048 - namespace string does not match target namespace string: Cause: The module contained a function or variable whose namespace did not match the target namespace of the module.; Action: Fix the namespace of the function or variable to match the target namespace of the module.
ORA-19269: XQST0049 - variable string defined multiple times: Cause: The module defined or imported the same variable multiple times.; Action: Fix the import or the module definition to remove duplicate definitions.
ORA-19270: XPDY0050 - treat failed - expected string got string: Cause: The type of the operand to the treat expression did not match the required type.; Action: Fix the input operand to be of the correct type.
ORA-19271: XPST0051 - invalid atomic type definition: Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type.; Action: Use the correct atomic type name.
ORA-19272: XQDY0052 - invalid atomic value in attribute or element constructor: Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string.; Action: Fix the content to contain atomic values that can be cast to a string.
ORA-19273: XQST0053 - empty string in namespace declaration: Cause: An empty string was used in a namespace declaration.; Action: Fix the namespace declaration to have a non-empty string.
ORA-19274: XQST0054 - variable initialization failed due to circularity: Cause: A circular definition was encountered when the variable was initialized.; Action: Remove the circularity in the initialization.
ORA-19275: XQST0055 - schema path string not found in list of in-scope schema definitions: Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions.; Action: Include the appropriate schema that can be used to resolve the ElementTest.
ORA-19276: XPST0005 - XPATH step specified an invalid element/attribute name: (string).: Cause: The XPATH step specified an invalid element or attribute name that did not match any nodes according to the input XML schema or structure.; Action: Correct the element or attribute name, because the name may have been misspelled.
ORA-19277: XPST0005 - XPath step specifies an item type matching no node: (string): Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure.; Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure.
ORA-19278: Invalid value: (string) for type: (string): Cause: The value was invalid for the type.; Action: Correct the value or change the type.
ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence: Cause: The XQuery sequence passed in had more than one item.; Action: Correct the XQuery expression to return a single item sequence.
ORA-19280: XQuery dynamic type mismatch: expected atomic value - got node: Cause: A node was passed in to the expression where an atomic value was expected.; Action: Correct the XQuery expression to return an atomic value.
ORA-19281: XQST0055 - It is a static error if a Prolog contains more than one copy-namespaces declaration: Cause: The query prolog contained multiple copy-namespaces declarations.; Action: Remove the duplicate copy-namespaces declarations.
ORA-19282: XQST0068 - It is a static error if a Prolog contains more than one xmlspace declaration: Cause: The query prolog contained multiple xmlspace declarations.; Action: Remove the duplicate xmlspace declarations.
ORA-19283: XQST0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.: Cause: The query contained a version declaration not supported by this implementation.; Action: Change the version declaration to 1.0 which is the version supported by this implementation.
ORA-19284: Encoding specification in version declaration not supported: Cause: The query contained an encoding specification.; Action: Remove the encoding specification.
ORA-19285: FODC0002 - error retrieving resource: Cause: The URI provided could not be resolved to a valid resource.; Action: Provide a valid URI for a resource.
ORA-19286: XPST0017 - unable to resolve call to function - string: Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.; Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19287: XPST0017 - invalid number of arguments to function - string:string: Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.; Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19288: XPST0017 - invalid number of arguments to function - string: Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.; Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
ORA-19289: XQST0034 - function string:string declared or defined multiple times: Cause: Multiple functions declared or imported by a module had the same expanded QName and the same number of arguments.; Action: Fix the function declaraction or definition to remove duplicates.
ORA-19290: XQST0069 - more than one empty order declaration declared in the prolog: Cause: A prolog had more than one empty order declaration.; Action: Fix the prolog to have just one empty order declaration.
ORA-19291: XPST0081 - specified QName cannot be expanded into a namespace URI: Cause: The namespace prefix of the QName could not be expanded into a namespace URI by using the statically known namespaces.; Action: Use a namespace prefix that can be resolved into a namespace URI from the statically known namespaces.
ORA-19292: XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19293: XQST0058: It is a static error if multiple schema imports specify the same target namespace: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19294: XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19295: XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI): Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19296: XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19297: XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to "XML" (in any combination of upper and lower case: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19298: XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19299: XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration: Cause: An error occurred during the processing of the XQuery expression.; Action: Check the detailed error message for the possible causes.
ORA-19300: An error occurred in URI processing of string.: Cause: An error occurred when processing the Uniform Resource Identifier (URI).; Action: Check all error messages, fix the appropriate problem, and retry the operation. If the problem persists, contact Oracle Support.
ORA-19320: Host name not specified in HTTP URL: Cause: A host name was not specified in the HTTP url; Action: Specify a host name in the HTTP url when creating the URL string
ORA-19321: Could not open HTTP connection to host (string): port (string): Cause: A HTTP connection could not be opened to the host; Action: Specify a valid host name and port to connect to
ORA-19322: An error occurred while reading from host (string): port (string): Cause: An error occurred while reading from the HTTP host; Action: Specify a valid host name and port to read from
ORA-19323: Invalid url string: Cause: The URL must be a valid URL string; Action: Specify a valid url string
ORA-19330: Type 'string'.'string' not installed. Please install the type before using the CREATE_DBURI operator: Cause: The type required for the CREATE_DBURI operator has not been installed correctly.; Action: Read the installation notes to install the type correctly.
ORA-19331: Last argument to CREATE_DBURI operator must be a column: Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.; Action: Specify a valid column name in the query.
ORA-19332: Invalid column in the CREATE_DBURI operator: Cause: The argument to the CREATE_DBURI operator can only be a column.; Action: Specify a valid column name for the operator
ORA-19333: invalid flags for CREATE_DBURI operator: Cause: An invalid flags argument was given to the CREATE_DBURI operator.; Action: Specify a valid flag value (TEXT) for the CREATE_DBURI operator.
ORA-19334: Invalid column specification for CREATE_DBURI operator: Cause: All columns must be valid and pointing to the same table or view; Action: Specify valid list of columns that are from the same table or view.
ORA-19335: Invalid format type object: Cause: An invalid format type object was specified for the XML function; Action: Specify a valid format type object
ORA-19336: Missing XML root element: Cause: The XML being generated does not have an enclosing root element.; Action: The XML generated must have a root element
ORA-19361: ONLINE option not allowed with this type of index: Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index; Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option.
ORA-19371: invalid update option: Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE.; Action: Adjust the update option and retry the operation.
ORA-19372: invalid update condition: Cause: The user attempted to call load_sqlset with an invalid update condition.; Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation.
ORA-19373: invalid staging table or tablespace: Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace; Action: Check the arguments and try again.
ORA-19374: invalid staging table: Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table; Action: Provide a correct staging table or grant the appropriate privileges
ORA-19375: no CREATE TABLE privilege on schema "string": Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema.; Action: Grant the privilege to the user and retry
ORA-19376: no privileges on tablespace provided or tablespace is offline: Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline; Action: Allocate space on the tablespace, bring it online, and retry
ORA-19377: no "SQL Tuning Set" with name like "string" exists for owner like "string": Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively; Action: Provide a different filter after checking the state of the system
ORA-19378: invalid mode: Cause: The user specified an invalid mode argument to the capture function.; Action: Provide a mode argument that was defined in the dbmssqlt file
ORA-19379: invalid time_limit or repeat_interval: Cause: Either a NULL value was specified for the time_limit or the repeat_interval value, or the repeat_interval value was greater than the time_limit value.; Action: Provide a non-NULL value and ensure that time_limit value is greater than or equal to the repeat_interval value.
ORA-19380: invalid plan filter: Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function.; Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.
ORA-19381: cannot create staging table in SYS schema: Cause: The user attempted to create a staging table in the sys schema; Action: Create the table in another schema.
ORA-19384: cannot pack into staging table from previous version: Cause: An attempt was made to perform a pack operation on a staging table from a previous version.; Action: Create a staging table in the current version and retry the operation.
ORA-19385: staging table is empty: Cause: An attempt was made to perform an operation on an empty staging table.; Action: Check the staging table to ensure that it has rows.
ORA-19386: target object already exists for tuning task "string": Cause: An attempt was made to set a target object for a tuning task when one had already been set.; Action: Create a new task if another target object is needed.
ORA-19387: "SQL Tuning Set" "string" belongs to another tuning task: Cause: The user attempted to tune a task-managed SQL Tuning Set belonging to one task within the scope of another task.; Action: Check the SQL Tuning Set and retry the operation.
ORA-19388: operation not supported for "SQL Tuning Set" type: Cause: The attempted operation was unsupported for the type of the given SQL Tuning Set.; Action: Check the SQL Tuning Set and retry the operation.
ORA-19389: LOB types are not supported for SQL binds: Cause: A LOB type was provided in a SQL bind list.; Action: Replace the LOB binds with legal bind types or try another SQL.
ORA-19390: The profile type is not valid: Cause: The profile type is not valid.; Action: Check the available profile types.
ORA-19400: System type conflict with object SYS.string: Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly.; Action: Remove the conflicting object and rerun migration.