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