Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located.

Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify the correct directory path/values in the environment variables.

ORA-12706: this CREATE DATABASE character set is not allowed

Cause: It is not allowed to create a database on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Action: none

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

Cause: Internal error

Action: none

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

Cause: Internal error

Action: none

ORA-12709: error while loading create database character set

Cause: Internal error

Action: none

ORA-12710: CREATE CONTROLFILE character set is not known

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

Action: none

ORA-12711: this CREATE CONTROLFILE character set is not allowed

Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Action: none

ORA-12712: new character set must be a superset of old character set

Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.

Action: Specify a superset character set.

ORA-12713: Character data loss in NCHAR/CHAR conversion

Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.

Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE.

ORA-12714: invalid national character set specified

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set

Action: Ensure that the specified national character set is valid

ORA-12715: invalid character set specified

Cause: The character set specified is not allowed for this operation or is invalid

Action: Ensure that the specified character set is valid

ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists

Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated

Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as import/export

ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists

Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode when converting to a multibyte character set and must be migrated.

Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. The above type data can be migrated by methods such as import/export.

ORA-12718: operation requires connection as SYS

Cause: This command can only be run when connecting as SYS

Action: Connect as SYS to run this command

ORA-12719: operation requires database is in RESTRICTED mode

Cause: This command can only be run when the database is in RESTRICTED mode

Action: Ensure that the system is in RESTRICTED mode

ORA-12720: operation requires database is in EXCLUSIVE mode

Cause: This command can only be run when the database is in EXCLUSIVE mode

Action: Ensure that the system is in EXCLUSIVE mode

ORA-12721: operation cannot execute when other sessions are active

Cause: This command can only be run when there are no other sessions active

Action: Ensure there are no other connections to the database

ORA-12722: regular expression internal error

Cause: A regular expression internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.

ORA-12723: regular expression too complex

Cause: The regular expression was too complex and could not be parsed.

Action: This is an internal error. Contact Oracle Support Services.

ORA-12724: regular expression corrupt

Cause: The regular expression contained an incorrect sequence of metacharacters.

Action: Ensure the metacharacters are correctly positioned.

ORA-12725: unmatched parentheses in regular expression

Cause: The regular expression did not have balanced parentheses.

Action: Ensure the parentheses are correctly balanced.

ORA-12726: unmatched bracket in regular expression

Cause: The regular expression did not have balanced brackets.

Action: Ensure the brackets are correctly balanced.

ORA-12727: invalid back reference in regular expression

Cause: A back references was found before a sub-expression.

Action: Ensure a valid sub-expression is being referenced.

ORA-12728: invalid range in regular expression

Cause: An invalid range was found in the regular expression.

Action: Ensure a valid range is being used.

ORA-12729: invalid character class in regular expression

Cause: An unknown character class was found in the regular expression.

Action: Ensure a valid characters class is being used.

ORA-12730: invalid equivalence class in regular expression

Cause: An unknown equivalence class was found in the regular expression.

Action: Ensure a valid equivalence class is being used.

ORA-12731: invalid collation class in regular expression

Cause: An unknown collation class was found in the regular expression.

Action: Ensure a valid collation class is being used.

ORA-12732: invalid interval value in regular expression

Cause: An invalid interval value was found in the regular expression.

Action: Ensure a valid interval value is being used.

ORA-12733: regular expression too long

Cause: The operation failed because the regular expression it used exceeds the maximum supported size.

Action: Use a shorter regular expression.

ORA-12734: Instant Client Light: unsupported client national character set string

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

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.

Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.

ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string

Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.

Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.

ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified

Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.

Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.

ORA-12813: value for PARALLEL or DEGREE must be greater than 0

Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.

Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.

ORA-12814: only one CACHE or NOCACHE clause may be specified

Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.

Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.

ORA-12815: value for INSTANCES must be greater than 0

Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT

Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.

ORA-12817: parallel query option must be enabled

Cause: A parallel query option feature has been invoked but this option has not been enabled.

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.

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

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

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: Note any accompanying errors and contact Oracle Support Services.

ORA-13041: failed to compare tile with element string.string.string

Cause: The spatial relationship between a generated tile and the specified element could not be determined.

Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13041 and contact Oracle Support Services.

ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination

Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the <layer>_SDOLAYER table. The most likely cause is that the columns are NULL.

Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial documentation. Then retry the operation.

ORA-13043: failed to read metadata from the <layer>_SDOLAYER table

Cause: An error was encountered reading the layer metadata from the <layer>_SDOLAYER table.

Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, contact Oracle Support Services.

ORA-13044: the specified tile size is smaller than the tolerance

Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as specified in the layer metadata.

Action: See the Oracle Spatial documentation for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a smaller tile size value than the current one.

ORA-13045: invalid compatibility flag

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13046: invalid number of arguments

Cause: An invalid number of arguments were specified for an SDO_GEOM function.

Action: See the Oracle Spatial documentation for a description of the syntax and semantics of the relevant SDO_GEOM function.

Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer <layer>.

Action: Verify that the <layer>_SDODIM table has a valid value for the column SDO_TOLERANCE.

ORA-13050: unable to construct spatial object

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13051: failed to initialize spatial object

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13052: unsupported geometric type for geometry string.string

Cause: The geometry type for a specific instance in a <layer>_SDOGEOM table is not among the set of geometry types supported by Oracle Spatial.

Action: Check the Oracle Spatial documentation for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.

ORA-13053: maximum number of geometric elements in argument list exceeded

Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.

Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it in as an argument in a call to the SDO_GEOM function.

ORA-13054: recursive SQL parse error

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13055: Oracle object string does not exist in specified table

Cause: The requested object is not present in the specified table.

Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Then retry the operation.

ORA-13060: topology with the name string already exists

Cause: The specified topology name was not unique in the database.

Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology name and that the procedure is invoked from the correct schema.

ORA-13061: topology with the name string does not exist

Cause: The specified topology did not exist in the database.

Action: Verify that the current procedure/function call specifies the correct schema and topology name.

ORA-13062: topology IDs do not match in the feature table and the topology

Cause: The specified topology ID in the feature table did not match the topology ID stored in the topology metadata.

Action: Verify that the specified topology ID matches the topology ID stored in the topology metadata.

Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same topology.

Action: Make sure both the parameters to the operator are from the same topology. If this is not possible, consider using a signature of the operator that does not use two SDO_TOPO_GEOMETRY parameters.

ORA-13068: wrong table or column name in SDO_TOPO_GEOMETRY constructor

Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name.

Action: Fix the parameters in the call and try again.

ORA-13108: spatial table string not found

Cause: The specified spatial table does not exist.

Action: Check the Spatial data dictionary to make sure that the table is registered.

ORA-13109: spatial table string exists

Cause: The specified spatial table is registered in the Spatial data dictionary.

Action: Remove the existing table from the Spatial data dictionary or use a different name.

ORA-13110: cannot drop topology with associated topo_geometry tables

Cause: The drop_topology procedure was invoked for a topology that has assocated topo_geometry layers with it.

Action: Delete the topo_geometry layers from the topology before dropping the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete topo_geometry layers from the topology.

ORA-13111: cannot add topo_geometry layer [string] to topology

Cause: It was not possible to add the specified topo_geometry layer to the topology.

Action: Make sure the topo_geometry layer table exists in the database.

ORA-13112: cannot delete topo_geometry layer [string] from topology

Cause: It was not possible to delete the specified topo_geometry layer from the topology.

Action: Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry layer is part of the topology. Only those topo_geometry layers which are part of the topology can be deleted from it.

ORA-13113: invalid tg_layer_id in sdo_topo_geometry constructor

Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor.

Action: Valid layer_ids are obtained by adding a topo_geometry layer to the topology. Check USER_SDO_TOPO_METADATA to find out the layer_id for an existing topo_geometry layer.

ORA-13114: [string]_NODE$ table does not exist

Cause: The NODE$ table for the topology did not exist in the database.

Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.

ORA-13115: [string]_EDGE$ table does not exist

Cause: The EDGE$ table for the topology did not exist in the database.

Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.

ORA-13116: [string]_FACE$ table does not exist

Cause: The FACE$ table for the topology did not exist in the database.

Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.

ORA-13117: [string]_RELATION$ table does not exist

Cause: The RELATION$ table for the topology did not exist in the database.

Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.

ORA-13118: invalid node_id [string]

Cause: A topology node operation was invoked with an invalid node_id.

Action: Check the topology node$ table to see if the specified node_id exists in the topology.

ORA-13119: invalid edge_id [string]

Cause: A topology edge operation was invoked with an invalid edge_id.

Action: Check the topology edge$ table to see if the specified edge_id exists in the topology.

ORA-13120: invalid face_id [string]

Cause: A topology face operation was invoked with an invalid face_id.

Action: Check the topology face$ table to see if the specified face_id exists in the topology.

ORA-13121: layer type type mismatch with topo_geometry layer type

Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type specified for the layer.

Action: Check the USER_SDO_TOPO_METADATA view to see the layer type for the layer and use it in the constructor.

ORA-13122: invalid topo_geometry specified

Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was not valid.

Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object.

ORA-13123: invalid <TOPOLOGY> name specified

Cause: The create_topo operation requires a unique TOPOLOGY name, that already does not exist in the database.

Action: Check to see if there is already an entry in the USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE) with this topology name.

ORA-13124: unable to determine column id for column string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13125: partition key is already set

Cause: A partition key is already set for the spatial table.

Action: Only one partition key can be specified per spatial table.

ORA-13126: unable to determine class for spatial table string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13127: failed to generate target partition

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13128: current tiling level exceeds user specified tiling level

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13129: HHCODE column string not found

Cause: The specified spatial column does not exist.

Action: Verify that the specified column is a spatial column by checking the Spatial data dictionary.

Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.

ORA-13142: invalid PROXIMITY window definition

Cause: The PROXIMITY window specified is not correctly defined.

Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.

ORA-13143: invalid POLYGON window definition

Cause: The POLYGON window specified is not correctly defined.

Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.

ORA-13144: target table string not found

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13145: failed to generate range list

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13146: could not find table substitution variable string

Cause: The partition name substitution variable %s was not found in the SQL filter.

Action: The substitution variable %s must be in the SQL filter to indicate where that partition name should be placed.

ORA-13147: failed to generate MBR

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13148: failed to generate SQL filter

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13149: failed to generate next sequence number for spatial table string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13150: failed to insert exception record

Cause: Operation failed to insert a record into the exception table.

Action: Fix any other errors reported.

ORA-13151: failed to remove exception record

Cause: Operation failed to remove a record from the exception table.

Action: Fix any other errors reported.

ORA-13152: invalid HHCODE type

Cause: Specified HHCODE type is not valid.

Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.

ORA-13153: invalid high water mark specified

Cause: The high water mark must be greater than or equal to zero.

Action: Make sure that the high water mark is an integer greater than or equal to zero.

ORA-13154: invalid precision specified

Cause: The precision specified is out of range.

Action: The precision must be an integer greater than or equal to zero.

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.

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.

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.

Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified, and it should not be less than the tolerance specified for the geometry.

Action: Check ARC_TOLERANCE specification and make sure it is correct.

ORA-13293: cannot specify unit for geometry without a georeferenced SRID

Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID.

Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.

ORA-13294: cannot transform geometry containing circular arcs

Cause: It is impossible to transform a 3-point representation of a circular arc without distortion.

Action: Make sure a geometry does not contain circular arcs.

ORA-13295: geometry objects are in different coordinate systems

Cause: An Oracle Spatial function was called with two geometries that have different SRIDs.

Action: Transform geometry objects to be in the same coordinate system and call the spatial function.

ORA-13296: incorrect coordinate system specification

Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.

Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse flattening.

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

Action: Check the geometry type to make sure this operation is called on non-polygon geometries.

ORA-13339: LRS polygon clipping across multiple rings

Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.

Action: Polygon clipping is allowed only for a single ring.

ORA-13340: a point geometry has more than one coordinate

Cause: A geometry, specified as being a point, has more than one coordinate in its definition.

Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, remove the extraneous coordinates from its definition.

ORA-13341: a line geometry has fewer than two coordinates

Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition.

Action: A line must consist of at least two distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13342: an arc geometry has fewer than three coordinates

Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition.

Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13343: a polygon geometry has fewer than four coordinates

Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition.

Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13344: an arcpolygon geometry has fewer than five coordinates

Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition.

Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13345: a compound polygon geometry has fewer than five coordinates

Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition.

Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13346: the coordinates defining an arc are collinear

Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.

Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the line type.

ORA-13347: the coordinates defining an arc are not distinct

Cause: Two or more of the three points defining an arc are the same.

Action: Alter the definition of the arc to ensure that three distinct coordinate values are used.

ORA-13348: polygon boundary is not closed

Cause: The boundary of a polygon does not close.

Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.

ORA-13349: polygon boundary crosses itself

Cause: The boundary of a polygon intersects itself.

Action: Correct the geometric definition of the object.

ORA-13350: two or more rings of a complex polygon touch

Cause: The inner or outer rings of a complex polygon touch.

Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object.

ORA-13351: two or more rings of a complex polygon overlap

Cause: The inner or outer rings of a complex polygon overlap.

Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object.

ORA-13352: the coordinates do not describe a circle

Cause: The set of coordinates used to describe a circle are incorrect.

Action: Confirm that the set of coordinates actually represent points on the circumference of a circle.

ORA-13353: ELEM_INFO_ARRAY not grouped in threes

Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer elements than expected.

Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.

ORA-13354: incorrect offset in ELEM_INFO_ARRAY

Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition references an invalid array subscript in SDO_ORDINATE_ARRAY.

Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.

ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions specified

Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.

Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.

ORA-13356: adjacent points in a geometry are redundant

Cause: There are repeated points in the sequence of coordinates.

Action: Remove the redundant point.

ORA-13357: extent type does not contain 2 points

Cause: Extent type should be represented by two points: lower left and upper right.

Action: Confirm that there are only two points for an extent type.

ORA-13358: circle type does not contain 3 points

Cause: Circle type should be represented by three distinct points on the circumference.

Action: Confirm that there are only three points for a circle type.

ORA-13359: extent does not have an area

Cause: The two points representing the extent are identical.

Action: Confirm that the two points describing the extent type are distinct.

ORA-13360: invalid subtype in a compound type

Cause: This subtype is not allowed within the ETYPE specified.

Action: Check the Oracle Spatial documentation for type definitions.

ORA-13361: not enough sub-elements within a compound ETYPE

Cause: The compound type declare more sub-elements than actually defined.

Action: Confirm that the number of sub-elements is consistent with the compound type declaration.

ORA-13362: disjoint sub-element in a compound polygon

Cause: Compound polygon must describe an enclosed area.

Action: Confirm that all sub-elements are connected.

ORA-13363: no valid ETYPE in the geometry

Cause: None of the ETYPEs within the geometry is supported.

Action: Confirm that there is at least one valid ETYPE.

ORA-13364: layer dimensionality does not match geometry dimensions

Cause: The spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.

Action: Make sure that all geometries in a layer have the same dimensions and that they match the dimensions in the SDO_DIM_ARRAY object for the layer in the USER_SDO_GEOM_METADATA view.

ORA-13365: layer SRID does not match geometry SRID

Cause: The spatial layer has a geometry with a different SRID than the SRID specified for the layer.

Action: Make sure that all geometries in a layer have the same SRID and that the SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view.

ORA-13366: invalid combination of interior exterior rings

Cause: In an Oracle Spatial geometry, interior and exterior rings are not used consistently.

Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.

ORA-13367: wrong orientation for interior/exterior rings

Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly.

Action: Be sure that the exterior rings are oriented counterclockwise and the interior rings are oriented clockwise.

ORA-13368: simple polygon type has more than one exterior ring

Cause: In a polygon geometry there is more than one exterior ring.

Action: Set the type to be multipolygon if more than one exterior ring is present in the geometry.

ORA-13369: invalid value for etype in the 4-digit format

Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is not a valid orientation for interior/exterior rings of the polygon.

Action: Correct the geometry definition.

ORA-13370: failure in applying 3D LRS functions

Cause: Only non-geodetic 3D line string geometries (made of line segments) are supported for 3D LRS functions.

Action: Check the geometry and element types and the SRID values.

ORA-13371: invalid position of measure dimension

Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in the dim_info_array.

Action: Check the geometry"s gtype and its position in the dim_info_array.

ORA-13372: failure in modifying metadata for a table with spatial index

Cause: Modifying the metadata after the index is created will cause an inconsistency between the geometry"s gtype and diminfo.

Action: Modify (or Prepare) metadata before creating an index on the SDO_GEOMETRY column.

ORA-13373: invalid line segment in geodetic data

Cause: A geodetic line segment was not less than half of a great circle.

Action: Densify the line by adding points.

ORA-13374: SDO_MBR not supported for geodetic data

Cause: The SDO_MBR functionality is not supported for geodetic data.

Action: Find an alternative function that can be used in this context.

ORA-13375: the layer is of type [string] while geometry inserted has type [string]

Cause: The layer has a type that is different or inconsistent with the type of the current geometry.

Action: Change the geometry type to agree with the layer type, or change the layer type to agree with the geometry type.

ORA-13376: invalid type name specified for layer_gtype parameter

Cause: An invalid type name is specified for the layer_gtype constraint.

Action: See the Spatial documentation for of valid keywords that can be used in defining a layer_gtype constraint.

ORA-13377: invalid combination of elements with orientation

Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4-digit etype).

Action: Make sure all the polygon elements have orientation specified using the 4-digit etype notation.

ORA-13378: invalid index for element to be extracted

Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.

Action: Make sure the parameters to the extract function are in the valid range for the geometry.

ORA-13379: invalid index for sub-element to be extracted

Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.

Action: Make sure the parameters to the extract function are in the valid range for the geometry.

ORA-13380: network not found

Cause: The specified network was not found in the network metadata.

Action: Insert the network information in the USER_SDO_NETWORK_METADATA view.

ORA-13381: table:string not found in network:string

Cause: The specified table was not found in the network metadata.

Action: Insert the table information in the USER_SDO_NETWORK_METADATA view.

ORA-13382: geometry metadata (table:string column:string) not found in spatial network:string

Cause: The specified geometry metadata was not found in the spatial network metadata.

Action: Insert the spatial metadata information in the USER_SDO_NETWORK_METADATA view.

ORA-13383: inconsistent network metadata: string

Cause: There was an inconsistency between the network metadata and the node/link information.

Action: Check the network metadata and the node/link information.

ORA-13384: error in network schema: string

Cause: The network table(s) did not have required column(s)

Action: Check the network schema.

ORA-13385: error in network manager: [string]

Cause: There was an internal error in network manager.

Action: Contact Oracle Customer Support for more help.

ORA-13386: commit/rollback operation error: [string]

Cause: The index-level changes were not fully incorporated as part of the commit or rollback operation.

Action: Correct the specified error and use the following statement: ALTER INDEX <index-name> PARAMETERS ("index_status=synchronize");

ORA-13387: sdo_batch_size for array inserts should be in the range [number,number]

Cause: The specified value for sdo_batch_size was too high or too low.

Action: Change the value to be in the specified range.

ORA-13388: invalid value for dst_spec parameter

Cause: The dst_spec parameter was specified in the wrong format.

Action: Check the documentation for this parameter.

ORA-13389: unable to compute buffers or intersections in analysis function

Cause: There was an internal error in computing the buffers or intersections in the specified spatial analysis function.

Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA view before invoking the spatial analysis function.

ORA-13390: error in spatial analysis and mining function: [string]

Cause: There was an internal error in the specified analysis function.

Action: Contact Oracle Customer Support for more help.

ORA-13401: duplicate entry for string in USER_SDO_GEOR_SYSDATA view

Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in two or more rows in the USER_SDO_GEOR_SYSDATA view.

Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the USER_SDO_GEOR_SYSDATA view contain the correct information, and that the value pair is unique for each row.

ORA-13402: the rasterType is null or not supported

Cause: The specified rasterType was null or not supported.

Action: Check the documentation for the rasterType number and/or formats supported by GeoRaster.

ORA-13403: invalid rasterDataTable specification: string

Cause: Each GeoRaster object must have an associated raster data table whose name is unique among raster data table names in the database. If the GeoRaster object is not empty and not blank, the raster data table must exist, be visible in the current schema, be defined in the same schema as the GeoRaster data table, and be an object table of SDO_RASTER type. However, one or more of these requirements were not met.

Action: Check the rasterDataTable specification and ensure that all relevant raster data table requirements are met.

ORA-13404: invalid ultCoordinate parameter

Cause: The ultCoordinate array parameter had the wrong length or contained an invalid value.

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

ORA-13405: null or invalid dimensionSize parameter

Cause: The dimensionSize array parameter was null, had the wrong length, or contained an invalid value.

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

ORA-13406: null or invalid GeoRaster object for output

Cause: The GeoRaster object for output was null or invalid.

Action: Make sure the GeoRaster object for output has been initialized properly.

ORA-13407: invalid storage parameter

Cause: The storage parameter contained an invalid specification.

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

ORA-13408: invalid blockSize storage parameter

Cause: The blockSize storage parameter had the wrong length or contained invalid value.

Action: Check the documentation, and make sure the blockSize storage parameter is correct.

ORA-13409: null or invalid pyramidLevel parameter

Cause: The specified pyramidLevel parameter was null or invalid.

Action: Make sure the pyramidLevel parameter specifies a valid pyramid level value for the GeoRaster object.

ORA-13410: invalid layerNumbers or bandNumbers parameter

Cause: The layerNumbers or bandNumbers parameter was invalid.

Action: Check the documentation and make sure the layerNumbers or bandNumbers parameter is valid.

ORA-13411: subset results in null data set

Cause: The intersection of cropArea and source GeoRaster object was null.

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

ORA-13412: invalid scale parameter

Cause: The scale parameter was invalid.

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

ORA-13413: null or invalid resampling parameter

Cause: The resampling parameter was null or invalid.

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

ORA-13414: invalid pyramid parameter

Cause: The pyramid parameter was invalid.

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

ORA-13415: invalid or out of scope point specification

Cause: The point position specified by the <ptGeom, layerNumber> or <rowNumber, colNumber, bandNumber> parameter combination was invalid or out of scope.

Action: Make sure the parameter(s) specify a valid point that is or can be translated into a cell position inside the cell space of the GeoRaster object.

ORA-13416: invalid geometry parameter

Cause: The geometry parameter did not specify a valid single-point geometry.

Cause: Too many subLayers were defined for the GeoRaster object, or layerNumber or layerDimensionOrdinate was not assigned correctly.

Action: The total number of logical layers cannot exceed the total number of physical layers, and each logical layer must be assigned a valid physical layer number following the same order. Check the documentation for more details.

ORA-13454: GeoRaster metadata is invalid

Cause: The GeoRaster metadata was invalid against its XML Schema.

Action: Run the schemaValidate routine to find the errors.

ORA-13455: GeoRaster metadata TRS error

Cause: The beginDateTime value was later than the endDateTime value.

Action: Make sure that the beginDateTime value is not later than the endDateTime value.

ORA-13456: GeoRaster cell data error

Cause: There was error in the GeoRaster cell data.

Action: The GeoRaster object is invalid.

ORA-13457: GeoRaster cell data error

Cause: There was error in the cell data of the pyramids.

Action: Delete the pyramids and re-generate them.

ORA-13458: GeoRaster metadata SRS error

Cause: The polynomial model did not match the requirements of a rectified GeoRaster object.

Action: Check the documentation for the requirements of the polynomial model for a rectified GeoRaster object, or set isRectified to be false.

ORA-13459: GeoRaster metadata SRS error

Cause: The polynomial model was not an six-parameter transformation, or the six-parameter transformation was not valid.

Action: Check the documentation and make sure the polynomial model is a valid six-parameter affine transformation.

ORA-13460: GeoRaster metadata SRS error

Cause: The referenced GeoRaster object had a zero model space SRID or the specified model space SRID was zero.

Action: Set or specify the model space SRID to be a nonzero number.

ORA-13461: the interleaving type is not supported

Cause: The interleaving type of the GeoRaster object was not supported.

Action: Check the documentation for the interleaving types supported by GeoRaster. Use SDO_GEOR.changeFormat to transform the image to a supported interleaving type.

ORA-13462: invalid blocking specification

Cause: The specified blocking configuration was invalid.

Action: Block size must always be a power of 2.

ORA-13463: error retrieving GeoRaster data: string

Cause: An internal error occurred while retrieving GeoRaster data from the database.

Action: Check the error message for details.

ORA-13464: error loading GeoRaster data: string

Cause: An internal error occurred while loading GeoRaster data into the database.

Action: Check the error message for details.

ORA-13465: null or invalid table or column specification

Cause: The specified table or column did not exist, or the column was not a GeoRaster column.

Action: Make sure the specified table exists and the specified column is a GeoRaster column.

ORA-13466: format not appropriate for specified compression method

Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported by the specified compression.

Action: Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormat to transform the GeoRaster object to an appropriate format, or apply another compression method.

ORA-13467: unsupported GeoRaster metadata specification: string

Cause: The GeoRaster metadata specification is not supported.

Action: Check the documentation for the supported GeoRaster metadata specifications.

ORA-13480: the Source Type is not supported

Cause: The specified source type was not supported.

Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster.

ORA-13481: the destination type is not supported

Cause: The specified destination type was not supported.

Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster.

ORA-13482: GeoRaster object is not initialized for the image

Cause: No GeoRaster object has been initialized for the specified image.

Action: Initialize a GeoRaster object to hold this image before loading it into the database. Check the documentation for details.

ORA-13483: insufficient memory for the specified GeoRaster data

Cause: There was insufficient memory to hold the specified GeoRaster data for this operation.

Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock the GeoRaster data into smaller sized blocks. Check the documentation for details.

ORA-13484: the file format and/or compression type is not supported

Cause: The file format and/or compression type was not supported.

Action: Check the documentation for formats that are currently supported by GeoRaster.

ORA-13485: error occurred during compression or decompression: string

Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details.

Action: Check that the GeoRaster object is valid, that its metadata is valid for the specified compression format, and that valid parameters are passed into the compression or decompression operation.

ORA-13497: %s

Cause: This is an internal GeoRaster error.

Action: Contact Oracle Support Services. You may want to make sure the GeoRaster object is valid before you do so.

ORA-13498: %s

Cause: An error related to an external plugin was encountered in the GeoRaster component.

Action: Check the documentation for the external plugin, or contact the plugin provider and supply the exact error text.

ORA-13499: %s

Cause: This is an internal Spatial error.

Action: Contact Oracle Support Services.

ORA-13500: SYSAUX DATAFILE clause specified more than once

Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause.

Action: Specify at most one SYSAUX DATAFILE clause.

ORA-13501: Cannot drop SYSAUX tablespace

Cause: Tried to drop SYSAUX tablespace

Action: None

ORA-13502: Cannot rename SYSAUX tablespace

Cause: An attempt to rename the SYSAUX tablespace failed.

Action: No action required.

ORA-13503: Creating SYSAUX tablespace with invalid attributes

Cause: An attempt to create the SYSAUX tablespace with invalid attributes.

Cause: The operation failed because AWR is not available. The possible causes are: AWR schema not yet created; AWR not enabled; AWR schema not initialized; or database not open or is running in READONLY or STANDBY mode.

Action: check the above conditions and retry the operation.

ORA-13517: Baseline (id = string) does not exist

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

Action: check the baseline id and retry the operation.

ORA-13518: Invalid database id (string)

Cause: The operation failed because the specified database ID does not exist in the Workload Repository.

Action: check the database id and retry the operation.

ORA-13519: Database id (string) exists in the workload repository

Cause: The operation failed because the specified database ID already exists in the Workload Repository.

Action: check the database id and retry the operation.

ORA-13520: Database id (string) not registered, Status = string

Cause: The operation failed because the specified database ID was not registered in the Workload Repository properly.

Action: check the status of database id and retry the operation.

ORA-13521: Unregister operation on local Database id (string) not allowed

Cause: The operation failed because the local database ID cannot be unregistered from the Workload Repository.

Action: check the database id and retry the operation.

ORA-13523: unable to allocate required space for return type

Cause: Out of memory to allocate the space for the return variable for an external procedure.

Action: Try operation again.

ORA-13524: error encountered while retrieving baseline information

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

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

Action: check the baseline name and retry the operation.

ORA-13527: invalid baseline name

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

Action: check the baseline name and retry the operation.

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

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

Action: check the baseline name and retry the operation.

ORA-13529: Error occurred when flushing AWR table group

Cause: An error occurred during the flushing of a table group. Because of the error in the group, we are unable to flush this table.

Action: Check the error associated with the table group.

ORA-13530: invalid TOPNSQL string, must be in the range (string, string)

Cause: The user has specified a TOPNSQL setting that is not in the supported range of (MIN, MAX).

Action: Choose a valid TOPNSQL setting and retry the operation.

ORA-13600: error encountered in Advisor string

Cause: An error occurred in the Advisor. This message will be followed by a second message giving more details about the nature of the error.

Action: See the Advisor documentation for an explanation of the second error message.

ORA-13601: The specified Advisor string does not exist.

Cause: The user specified an advisor name that has not be defined in the advisor repository.

Action: Correct the advisor name and retry the operation.

ORA-13602: The specified parameter string is not valid for task or object string.

Cause: The user attempted to access a task parameter that does not exist for the specified advisor object. The parameter may be misspelled or the user has selected a parameter that is not supported by the particular advisor.

Action: Validate the parameter name and retry the operation.

ORA-13603: The specified parameter string cannot be fetched as a numeric value for task or object string.

Cause: The user attempted to retrieve a string parameter as a numeric value.

Action: Check the datatype for the task parameter and retry the operation.

ORA-13604: The specified parameter string cannot be fetched as a SQL table.

Cause: The user attempted to retrieve a non-table parameter as a table name.

Action: Check the datatype for the task parameter and retry the operation.

ORA-13605: The specified task or object string does not exist for the current user.

Cause: The user attempted to reference an advisor task or object using a name that does not exist in the Advisor repository.

Action: Adjust the name and retry the operation.

ORA-13606: the specified task parameter element string is out of range for parameter string.

Cause: The user attempted to reference an invalid parameter element.

Action: Adjust the element offset and retry the operation.

ORA-13607: The specified task or object string already exists

Cause: The user attempted to create the specified task or object using a name that already exists in the Advisor repository. Task names must be unique to the database user.

Action: Adjust the name and retry the operation.

ORA-13608: The task or object name string is invalid.

Cause: The user attempted to specify a task name that contains invalid characters or an invalid wildcard specifier.

Action: Adjust the name and retry the operation.

ORA-13609: The specified task string must be executing to be cancelled or interrupted.

Cause: The user attempted to cancel or interrupt a task that is not currently executing.

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

ORA-13610: The directive string does not exist for task string.

Cause: The user attempted to access a task directive that does not exist.

Action: Validate the directive and retry the operation.

ORA-13611: The command string is not a valid advisor command.

Cause: The user attempted to specify a command that does not exist.

Action: Validate the command and retry the operation.

ORA-13612: The recommendation action string,string is not valid for task string.

Cause: The user attempted to access a recommendation action that does not exist in the task.

Action: Validate the recommendation-action and retry the operation.

ORA-13613: The requested operation is not supported for this advisor object.

Cause: The user attempted to perform an operation that is not supported for the particular advisor or task type.

Action: Validate the task or object and retry the operation.

ORA-13614: The template string is not compatible with the current advisor.

Cause: The user attempted to create a new task or object using an existing task or object that was not created by the same advisor.

Action: Validate the template and retry the operation.

ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters.

Cause: The user attempted to create a new task or object using a name that is too long.

Action: Shorten the name and retry the operation.

ORA-13616: The current user string has not been granted the ADVISOR privilege.

Cause: The user attempted an advisor operation that requires privilege.

Action: Adjust the user"s privileges and retry the operation.

ORA-13617: The specified task string already executing

Cause: The user attempted to execute a task that is currently executing.

Action: Wait for the task to finish before attempting any further task activities.

ORA-13618: The specified value is not a valid value for procedure argument string.

Cause: The user executed a procedure but failed to provide correct values for the argument.

Action: Correct the procedure arguments and retry the operation.

ORA-13619: The procedure argument string is greater than the maximum allowable length of string characters.

Cause: The user attempted to pass a character argument that is too long.

Action: Shorten the specified character argument and retry the operation.

ORA-13620: The task or object string is read-only and cannot be deleted or modified.

Cause: The user attempted to perform an operation that will update or delete a read-only task or object.

Action: Adjust the READ_ONLY property for the object and retry the operation.

ORA-13621: The task_or object string is marked as a template and cannot perform the requested operation.

Cause: The user attempted perform an unsupported operation on a task or object that is identified as a template.

Action: Choose a different object and retry the operation.

ORA-13622: invalid recommendation annotation

Cause: The user attempted to mark a recommendation using an invalid annotation. Valid annotation actions are ACCEPT, REJECT and IGNORE.

Action: Correct the action and retry the operation.

ORA-13623: The recommendation string is not valid for task string.

Cause: The user attempted to access a recommendation that does not exist in the task.

Action: Validate the recommendation and retry the operation.

ORA-13624: The task string is executing and cannot be deleted or modified.

Cause: The user attempted to access a task that currently executing.

Action: Wait for the task to complete and retry the operation.

ORA-13625: %s is an invalid advisor object type.

Cause: The user has specified an invlaid object type.

Action: Refre to dba_advisor_object_types for all valid object types

ORA-13626: The specified object string is not valid for task string.

Cause: The user specified an non-existent object for the task

Action: Choose a different object and retry the operation.

ORA-13627: Setting of parameter string is disallowed until the task is reset.

Cause: The user attempted to set the value of a parameter before the task was reset. This parameter cannot be changed until the task is reset.

Action: Reset the task and retry the operation.

ORA-13628: Insufficient privileges to access the task belonging to the specified user

Cause: The user could not access dba_* views.

Action: Retry operation as owner of the task or after granting new privileges.

ORA-13629: The task or object string is being used by another operation.

Cause: The user attempted to access a task or object that is locked by another session.

Action: Wait for the task or object activity to complete and retry the operation.

Cause: The parameter was not set to an acceptable value for this particular mode of analysis.

Action: Set the parameter to a valid value and retry.

ORA-13707: Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.

Cause: Either the start or the end snaphots was missing or purged or had encountered errors while creating them.

Action: Verify that AWR is done taking these two snapshots, or Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the start/end snapshots. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that has valid start and end snapshots.

ORA-13708: Some snapshots in the range [string, string] were purged before the analysis was complete.

Cause: One or both of the snapshots have been purged from AWR.

Action: Verify that the AWR auto purging is not trying to purge these snapshots and re-run ADDM.

ORA-13709: Required parameter "string" must be set before execution.

Cause: The parameter needs to be set before running the ADDM

Action: Set the parameter to a valid value and retry.

ORA-13710: Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.

Cause: Invalid interaction between two parameter values.

Action: Set at least one of the values so the value of the first parameter is higher than the value of the second parameter.

ORA-13711: Some snapshots in the range [string, string] are missing key statistics.

Cause: Some AWR tables encountered errors while creating one or more snapshots in the given range. The data present in one or more of these missing tables is necessary to perform an ADDM analysis.

Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the given snapshot range. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that does not include any incomplete snapshots.

ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".

Cause: ADDM analysis can only be performed on AWR snapshots taken in the current release.

Action: One can still generate AWR and ASH reports using ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots to analyze the data in them.

ORA-13750: User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.

Cause: The user attempted an SQL Tuning Set operation that requires a specific privilege.

Action: Adjust the user"s privileges and retry the operation.

ORA-13751: "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".

Cause: The user attempted to access a SQL Tuning Set that does not exist or the user does have permission to access the SQL Tuning Set

Action: Check the existence of the "SQL Tuning Set" or adjust the user"s privileges and retry the operation.

ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.

Cause: The attempted to create a SQL Tuning Set in another schema without having the right privilege.

Action: Connect as SYS or adjust the user"s privilege and retry the operation.

Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services.

ORA-13773: insufficient privileges to select data from the cursor cache

Cause: The user attempted to perform an operation without having the appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE.

Action: Adjust the user"s privileges and retry the operation.

ORA-13774: insufficient privileges to select data from the workload repository

Cause: The user attempted to perform an operation without having the appropriate privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT.

Action: Adjust the user"s privileges and retry the operation.

ORA-13775: inconsistent datatype in input cursor

Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor. All rows in the cursor must match type SQLSET_ROW.

Action: Check the rows type in the cursor and retry the operation.

ORA-13776: User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.

Cause: The user attempted to read a SQL tuning set belonging to someone else without having SELECT privilege on the DBA views

Action: User should be granted the privilege or only access his own STS

ORA-13777: invalid list of attribute names

Cause: The user specified an attribute element that is not valid. The only attributes that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of the names including EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN.

Action: Adjust the attribute list and retry the operation.

ORA-13778: no new name or owner specified for "SQL Tuning Set"

Cause: The user attempted to call remap_stgtab_sqlset without specifying either a new SQL tuning set name or a new SQL tuning set owner

Action: Specify at least one or the other argument as non-NULL

ORA-13779: invalid load option

Cause: The user attempted to call load_sqlset with a load option that is different than INSERT, UPDATE and MERGE.

Action: Adjust the load option and retry the operation.

ORA-13780: SQL statement does not exist.

Cause: The user attempted to tune a SQL statement that does not exist.

Action: Verify the sql_id and the plan hash value of the statement and retry the operation.

ORA-13783: invalid tuning scope

Cause: The user attempted to specify a tuning task scope that is invalid. The possible values are LIMITED or COMPREHENSIVE.

Action: Check the scope value and retry the operation.

ORA-13784: cannot accept SQL profiles for all statements in the "SQL Tuning Set"

Cause: The user attempted to accept SQL profiles for all statements in a SQL Tuning Set.

Action: Provide the object identifier corresponding to a statement in the SQL Tuning Set and retry the operation.

ORA-13785: missing target object for tuning task "string"

Cause: The user attempted to perform an operation on a task without specifying a target object or by using an invalid object identifier.

Cause: The user attempted to accept a SQL profile for an object that has not a SQL profile associated to it.

Action: Check the identifier of the object and retry the operation.

ORA-13788: invalid recommendation type

Cause: The user passed an invalid recommendation type in the rec_type argument to script_tuning_task. Possible values are ALL or any subset of a comma-separated list of PROFILES, STATISTICS and INDEXES.

Action: Check the rec_type arg and retry the operation.

ORA-13789: invalid process action

Cause: The user passed an invalid action to process a SQL statement. Possible value is any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN.

Action: Check the action argument and retry the operation.

ORA-13790: invalid value for time limit

Cause: The user passed an invalid value for the time limit argument.

Action: Check the argument specified value and retry the operation.

ORA-13791: cannot resume a tuning task created to tune a single statement

Cause: The user attempted to resume a tuning task that was created to tune a single SQL statement. A task can be resumed only if it is used to tune a SQL Tuning Set.

Action: No action required.

ORA-13797: invalid SQL Id specified, string

Cause: Invalid SQL Id specified for conversion.

Action: Specify valid SQL Id.

ORA-13798: Parameter string cannot be NULL.

Cause: A call to GET_THRESHOLD procedure was made without a required parameter.

Action: Specify a valid value for this parameter.

ORA-13799: threshold not found

Cause: No threshold was found with the specified threshold key.

Action: No action required.

ORA-13800: concurrent DDL failure on SQL repository objects

Cause: A SQL repository object was the target of two concurrent DDL operations.

Action: Check the current state of the object and retry the operation that failed.

ORA-13801: invalid value for SQLTUNE_CATEGORY parameter

Cause: An invalid Oracle identifier was used as the value of the parameter.

Action: Specify the parameter conforming to the rules for Oracle identifiers.

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

Action: Ensure that all elements of partition bound list are of valid type

ORA-14020: this physical attribute may not be specified for a table partition

Cause: unexpected option was encountered while parsing physical attributes of a table partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for Hash partitions

Action: remove invalid option(s) from the list of physical attributes of a table partition

ORA-14021: MAXVALUE must be specified for all columns

Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns

Action: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns

ORA-14022: creation of LOCAL partitioned cluster indices is not supported

Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal

Action: Remove LOCAL along with <partition description>s, if any, from the CREATE INDEX statement.

ORA-14023: creation of GLOBAL partitioned cluster indices is not supported

Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal

Action: Remove PARTITION BY RANGE clause along with <partition description>s from the CREATE INDEX statement.

ORA-14024: number of partitions of LOCAL index must equal that of the underlying table

Cause: User attempted to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table.

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

ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log

Cause: PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log

Action: Ensure that a definition of a MATERIALIZED VIEW does not include invalid options

ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive

Cause: definition of a table contained both PARTITION and CLUSTER clauses which is illegal

Action: Remove one of the conflicting clauses

ORA-14027: only one PARTITION clause may be specified

Cause: CREATE TABLE statement contained more than one PARTITION clause

Action: Specify PARTITION option at most once

ORA-14028: missing AT or VALUES keyword

Cause: keyword AT or VALUES missing

Action: supply missing keyword

ORA-14029: GLOBAL partitioned index must be prefixed

Cause: partitioning columns of a global partitioned index must form a prefix of the index" key columns

Action: Ensure that the GLOBAL partitioned index being created is prefixed

ORA-14030: non-existent partitioning column in CREATE TABLE statement

Cause: Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created.

Action: Ensure that all columns in the partitioning column list are columns of the table being created.

ORA-14031: partitioning column may not be of type LONG or LONG RAW

Cause: Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal.

Action: Ensure that no partitioning column is of type LONG or LONG RAW.

ORA-14032: partition bound of partition number string is too high

Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal.

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

ORA-14036: partition bound value too large for column

Cause: Length of partition bound value is longer than that of the corresponding partitioning column.

Action: Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns

ORA-14037: partition bound of partition "string" is too high

Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal.

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

ORA-14038: GLOBAL partitioned index must be prefixed

Cause: User attempted to create a GLOBAL non-prefixed partitioned index which is illegal

Action: If the user, indeed, desired to create a non-prefixed index, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed

ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE index

Cause: User attempted to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal

Action: If the user, indeed, desired to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index" partitioning columns form a subset of its key columns

ORA-14041: partition bound may not be specified for resulting partitions

Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, <partition-description> of a resulting partition was found to contain VALUES LESS THAN clause which is illegal

Action: remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition

ORA-14042: partition bound may not be specified for a partition being moved, modified or rebuilt

Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal

Action: remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt

ORA-14043: only one partition may be added

Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added

Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas

ORA-14044: only one partition may be moved

Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved

Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas

ORA-14045: only one partition may be modified

Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified

Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas

ORA-14046: a partition may be split into exactly two new partitions

Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split

Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split

ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations

Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal

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

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

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

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

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

ORA-14081: new partition name must differ from the old partition name

Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name> which is identical to the name of the partition being renamed

Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index

ORA-14082: new partition name must differ from that of any other partition of the object

Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name> which is identical to the name of some existing partition of the object

Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index

ORA-14083: cannot drop the only partition of a partitioned table

Cause: A drop partition command is being executed when there is only one partition in the table

Action: Ensure that there is at least one partition. Drop table to remove all partitions

ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index

Cause: User attempted to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal.

Action: Reenter the statement without TABLESPACE DEFAULT clause.

ORA-14085: partitioned table cannot have column with LONG datatype

Cause: User tried to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table.

Action: LONG data types are not supported with partitioned tables. Create table without LONG column or change table to not partitioned. If adding column, do not use LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non partitioned table.

ORA-14086: a partitioned index may not be rebuilt as a whole

Cause: User attempted to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal

Action: Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and recreate the entire index

ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option

Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]

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.

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

ORA-14107: partition specification is required for a partitioned object

Cause: parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects.

Action: supply missing parameter

ORA-14108: illegal partition-extended table name syntax

Cause: Partition to be accessed may only be specified using its name. User attempted to use a partition number or a bind variable.

Action: Modify statement to refer to a partition using its name

ORA-14109: partition-extended object names may only be used with tables

Cause: User attempted to use a partition-extended object name with an object which is not a table.

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

ORA-14110: partitioning column may not be of type ROWID

Cause: Partitioning column specified by the user was of type ROWID, which is illegal.

Action: Ensure that no partitioning column is of type ROWID.

ORA-14111: creation of a GLOBAL partitioned index on clustered tables is not supported

Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal.

Action: Remove PARTITION BY RANGE/HASH clause along with any partition descriptions to create a GLOBAL non-partitioned index on a clustered table

ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition

Cause: Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal

Action: Remove offending clause. Use LOGGING or NOLOGGING instead.

ORA-14113: partitioned table cannot have column with LOB datatype

Cause: User tried to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table.

Action: LOB data types are not supported with partitioned tables. Create table without LOB column or change table to not partitioned. If adding column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non partitioned table.

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.

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.

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: Specify a number between 1 and 1024K-1 in the number-of-partitions clause

ORA-14153: only one of STORE IN or <partition-description> clause may be specified

Cause: both STORE IN and <partition-description> clauses were specified in a CREATE TABLE|INDEX command

Action: Remove one of offending clauses

ORA-14154: only one of STORE IN or <subpartition-description> clause may be specified

Cause: both STORE IN and <subpartition-description> clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a Composite Range partitioned object

Action: Remove one of offending clauses

ORA-14155: missing PARTITION or SUBPARTITION keyword

Cause: expect either PARTITION or SUBPARTITION keyword but none was supplied

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: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will

ORA-14176: this attribute may not be specified for a hash partition

Cause: An invalid option was encountered while parsing physical attributes of a partition of an object partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions.

Action: Remove the invalid option(s).

ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table

Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a range/list/composite range list partitioned table

Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index on range/list/composite range list partitioned table

ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes

Cause: STORE IN (DEFAULT) is valid only for local indexes.

Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove STORE IN clause and specify tablespaces individually for each index partition.

ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL index

Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range/System/Hash partitioned LOCAL index object, which is illegal.

Cause: unexpected option was encountered while parsing physical attributes of a local index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions STORE IN () is also disallowed for all but Composite Range partitions

Action: remove invalid option(s) from the list of physical attributes of an index partition

ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table

Cause: User attempted to create a LOCAL partitioned index with a number of sub-partitions which is different from that of the underlying table.

Action: Correct the CREATE INDEX statement to specify a correct number of sub-partitions

ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table

Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with the underlying table. The partitioning types are mismatched.

Action: Correct the CREATE INDEX statement to ensure that the index partitionining method is consistent with that of the base table

ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index

Cause: User attempted to create a UNIQUE partitioned index whose sub-partitioning columns do not form a subset of its key columns which is illegal

Action: If the user, indeed, desired to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index" subpartitioning columns form a subset of its key columns

ORA-14189: this physical attribute may not be specified for an index subpartition

Cause: unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option

Action: remove invalid option(s)

ORA-14190: only one ENABLE/DISABLE ROW MOVEMENT clause can be specified

Cause: One of three possible actions caused the error: 1) ENABLE ROW MOVEMENT was specified more than once. 2) DISABLE ROW MOVEMENT was specified more than once. 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified.

Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses; then, reissue the command.

ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object

Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION.

ORA-14255: table is not partitioned by Range, Composite Range or List method

ORA-14268: subpartition "string" of the partition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.

Action: Bring tablespace online before attempting the operation.

ORA-14269: cannot exchange partition other than a Range or Hash partition

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

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

ORA-14270: table is not partitioned by Range or Hash or List method

Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Range or Hash method which is illegal.

Action: Ensure that the table is partitioned by Range or Hash method

ORA-14271: table is not partitioned by Composite Range method

Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Composite Range method which is illegal.

Action: Ensure that the table is partitioned by Composite Range method

ORA-14272: only a partition with higher bound can be reused

Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal.

Action: Use the higher-bound partition to be the resulting partition or specify a new partition name

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.

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.

Cause: When exchanging a partitioned table with a composite partition the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition.

Action: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition.

Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. For index organized tables, either the block sizes of the index or the overflow (or both) do not match.

Action: Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. For index organized tables, ensure that the block sizes of both the index and the overflow of the two tables match.

Action: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement.

ORA-14302: only one list of added-LOB-storage-clauses can be specified in a statement

Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list.

Action: Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement.

ORA-14303: partitions or subpartitions are not in the right order

Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal

Action: Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement.

Action: Ensure that all elements of partition bound list are of valid type

ORA-14309: Total count of list values exceeds maximum allowed

Cause: Partitioned object contains more than 524288 list values

Action: Reduce number of values to less than 524288.

ORA-14310: VALUES LESS THAN or AT clause cannot be used with List partitioned tables

Cause: VALUES LESS THAN or AT clause can be used only with Range partitioned tables

Action: Use VALUES (<value list>) clause with List partitioned tables

ORA-14311: Expecting VALUES LESS THAN or AT clause

Cause: VALUES (<value list>) clause can be used only with List partitioned tables

Action: Use VALUES LESS THAN clause with Range partitioned tables

ORA-14312: Value string already exists in partition string

Cause: One of the list values in the ADD PARTITION or ADD VALUES statement already exists in another partition

Action: Remove the duplicate value from the statement and try again

ORA-14313: Value string does not exist in partition string

Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the partition

Action: Remove the value from the statement and try again

ORA-14314: resulting List partition(s) must contain atleast 1 value

Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value

Action: Ensure that each of the resulting partitions contains atleast 1 value

ORA-14315: cannot merge a partition with itself

Cause: The same partition name was specified twice for the merge operation

Action: Re-submit operation with 2 distinct partition names

ORA-14316: table is not partitioned by List method

Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects

Action: Re-issue the command against a List partitoned object.

ORA-14317: cannot drop the last value of partition

Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition

Action: Cannot execute the command, unless two or more values exist for partition

ORA-14318: DEFAULT partition must be last partition specified

Cause: A partition description follows the one describing the default partition

Action: Ensure that the DEFAULT partition is the last partition description

ORA-14319: DEFAULT cannot be specified with other values

Cause: DEFAULT keyword has been specified along with other values when specifying the values for a list partition

Action: Ensure that if DEFAULT is specified, it is the only value specified

ORA-14320: DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT

Cause: DEFAULT keyword has been specified when doing a ADD VALUES or DROP VALUES or SPLIT partition or subpartition.

Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operation.

ORA-14321: cannot add/drop values to DEFAULT partition

Cause: A ADD/DROP VALUES operation is being done on the default partition

Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition

ORA-14322: DEFAULT partition already exists

Cause: A partition already exists with DEFAULT value

Action: none

ORA-14323: cannot add partition when DEFAULT partition exists

Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists

Action: Issue a SPLIT of the DEFAULT partition instead

ORA-14324: values being added already exist in DEFAULT partition

Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT partition

Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into the partition to which values need to be added

ORA-14325: only LOCAL indexes may be specified in this clause

Cause: A global index has been specified in the UPDATE INDEXES (..) clause

Action: Only specify local indexes when using this clause

ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause

Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified in the UPDATE INDEXES (..) clause

Action: Do not specify any of these indexes when using this clause

ORA-14327: Some index [sub]partitions could not be rebuilt

Cause: The first phase (partition DDL and index [sub]partition placement) completed successfully. During the second phase, some of the index [sub]partitions could not be rebuilt.

Action: .

ORA-14329: domain index [sub]partitions cannot be renamed in this clause

Cause: The user tried to rename a domain index [sub]partition in the UPDATE INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION operation. This is not allowed.

Action: Leave the name blank or use the same name.

ORA-14400: inserted partition key does not map to any partition

Cause: An attempt was made to insert a record into, a Range or Composite Range object, with a concatenated partition key that is beyond the concatenated partition bound list of the last partition -OR- An attempt was made to insert a record into a List object with a partition key that did not match the literal values specified for any of the partitions.

Action: Do not insert the key. Or, add a partition capable of accepting the key, Or add values matching the key to a partition specification

ORA-14401: inserted partition key is outside specified partition

Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement

Cause: cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. This error is never returned to user, because is caught in opiexe() and the DML statement is retried.

Action: nothing to be done, error should never be returned to user

ORA-14404: partitioned table contains partitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace

Action: find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace

ORA-14405: partitioned index contains partitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.

Action: find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.

Cause: At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition.

Action: Do not update the key. Or, add a partition capable of accepting the key.

ORA-14407: partitioned table contains subpartitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace

Action: find tables with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move subpartitions to a different tablespace

ORA-14408: partitioned index contains subpartitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains indexes whose subpartitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.

Action: find indexes with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.

ORA-14409: inserted partition key is outside specified subpartition

Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated subpartition bound lists that delimit the subpartition named in the INSERT statement

Action: do not insert the key or insert it in another subpartition

ORA-14450: attempt to access a transactional temp table already in use

Cause: An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session.

Action: do not attempt to access the temporary table until the concurrent transaction has committed or aborted.

ORA-14451: unsupported feature with temporary table

Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause.

Action: do not do that.

ORA-14452: attempt to create, alter or drop an index on temporary table already in use

Cause: An attempt was made to create, alter or drop an index on temporary table which is already in use.

Action: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions.

ORA-14453: attempt to use a LOB of a temporary table, whose data has alreadybeen purged

Cause: An attempt was made to use LOB from a temporary table whose data has been dropped either because table was transaction-specific and transaction has commited or aborted, table was truncated or session which created this LOB has ended.

Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size.

Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size.

Cause: A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object"s default tablespace (or one of the object"s partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object"s partitions/subpartitions.

Action: Specify a tablespace of the same block size as the partitioned object.

Cause: A DDL statement was issued that would require creation of a new partition/subpartition in the object-level default tablespace of an existing partitioned object. However, the object-level default tablespace block size does not match the block size of the partitioned object.

Action: Either (1) Modify the default tablespace of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created.

Cause: A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object.

Action: Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created.

Cause: A DDL statement was issued that would require a partition/subpartition of a local index/LOB column to be co-located with the corresponding partition/subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column/local index are different.

Action: Either (1) Specify an object-level default tablespace (or partition-level default tablespace for the appropriate partition, if composite partitioning is used) for the partitioned local index/LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose block size does not match that of the base table.

ORA-14551: cannot perform a DML operation inside a query

Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave.

Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave.

ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML

Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement.

Action: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation.

ORA-14553: cannot perform a lob write operation inside a query

Cause: A lob write operation cannot be performed inside a query or a PDML slave.

Action: Ensure that the offending lob write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave.

ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template

Cause: Cannot specify these clauses while specifying a template

Action: Correct the subpartition template clause.

ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table

Cause: SUBPARTITION TEMPLATE can be specified only for composite partitioned tables

Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or non-composite partitioned tables.

Cause: A drop subpartition command is being executed when there is only one subpartition in the partition

Action: none

ORA-14630: subpartition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.

Action: Bring tablespace online before attempting the operation.

ORA-14631: the partition bounds do not match the subpartition bounds of the partition

Cause: When exchanging a partitioned table with a composite partition the bounds that describe the partitions of the table must match the bounds that describe the subpartitions of the composite partition.

Action: Ensure that the bounds describing partitions in the partitioned table is the same as the bounds of the subpartitions in the the composite partition.

Cause: Either records_per_block has been minimized for one of the tables to be exchanged, but not the other, or the hakan factors for the tables to be exchanged are not equal.

Action: If records_per_block has been minimized for one of the tables, but not the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables, or perform alter table with the MINIMIZE RECORDS_PER_BLOCK for both tables. If the hakan factors do not match perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.

ORA-14644: table is not subpartitioned by Hash method

Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects

Action: Re-issue the command against a Hash subpartitoned object.

ORA-14645: STORE IN clause cannot be specified for Range List objects

Cause: A STORE IN clause was specified for Range List partitioned object

Cause: The first time a table is altered to include compression, it cannot have a usable bitmap index (partition). Subsequent alter table statements involving compression do not have this same restriction.

Action: A) Drop any bitmap indexes defined on the table, and re-create them once the operation is complete or, B) Mark all index fragments of all bitmap indexes defined on the table UNUSABLE and rebuild them once the operation is complete.

ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user

Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a non-SYS user, user should minimally have DML privileges

Cause: The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance.

Action: Connect to the correct instance type and re-issue the command.

ORA-15001: diskgroup "string" does not exist or is not mounted

Cause: An operation failed because the diskgroup specified does not exist or is not mounted by the current ASM instance.

Action: Verify that the diskgroup name used is valid, that the diskgroup exists, and that the diskgroup is mounted by the current ASM instance.

Cause: The LOCK_NAME_SPACE initialization parameter contained a value that is too long.

Action: Correct the LOCK_NAME_SPACE initialization parameter.

ORA-15003: diskgroup "string" already mounted in another lock name space

Cause: The diskgroup could not be mounted by the ASM instance because it was operating in a lockspace different than another existing

Action: Check the LOCK_NAME_SPACE initialization parameter value, or dismount the diskgroup from the other ASM instances.

ORA-15004: alias "string" does not exist

Cause: The specified alias did not exist within the diskgroup.

Action: Check the alias name and diskgroup name.

ORA-15005: name "string" is already used by an existing alias

Cause: An existing alias in the diskgroup used the same name.

Action: Select another alias name, or drop the existing alias.

ORA-15006: template "string" does not exist

Cause: The specified template did not exist within the diskgroup.

Action: Check the template name and diskgroup name.

ORA-15007: name is already used by an existing template

Cause: A template with the same name already exists.

Action: Select another template name, or drop the existing template.

ORA-15008: cannot drop system template

Cause: The specified template was created by the system and must always exist for proper operation.

Action: Select another template name.

ORA-15009: ASM disk "string" does not exist

Cause: The specified ASM disk was not found.

Action: Check the ASM disk name.

ORA-15010: name is already used by an existing ASM disk

Cause: The specified name was already used in this diskgroup.

Action: Specify a different ASM disk name.

ORA-15011: failure group "string" contains no members

Cause: The specified name did not match the failure group of any disks in the diskgroup. This usually indicates that the failure group name was specified incorrectly.

Action: Check the failure group name.

ORA-15012: ASM file "string" does not exist

Cause: The ASM file was not found.

Action: Check the ASM file name.

ORA-15013: diskgroup "string" is already mounted

Cause: An ALTER DISKGROUP MOUNT command specified the name of a diskgroup which is already mounted by the current ASM instance.

Action: Check the name of the diskgroup.

ORA-15014: location "string" is not in the discovery set

Cause: The operating system path specified was outside the set of disks that are discovered by the instance.

Action: Specify a operating system path within the set of disks that are discovered based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the ASM_DISKSTRING parameter.

ORA-15017: diskgroup "string" cannot be mounted

Cause: The specified diskgroup could not be mounted.

Action: Check for additional errors reported.

ORA-15018: diskgroup cannot be created

Cause: The specified diskgroup could not be created.

Action: Check for additional errors reported.

ORA-15019: discovered duplicate path "string" for "string"

Cause: The discovery encountered multiple paths to the same disk.

Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.

ORA-15020: discovered duplicate ASM disk "string"

Cause: The discovery encountered two disks claiming to be the same named ASM disk.

Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.

ORA-15021: parameter "string" is not valid in string instance

Cause: The specified parameter was not supported when starting an instance of this type.

Action: Delete the specified parameter from the INIT.ORA file.

ORA-15023: reached maximum allowable number of disks string

Cause: An attempt was made to add another disk to a diskgroup which already contains the maximum number of disks allowed.

Action: Consider dropping existing disks from the diskgroup before adding additional ones, or create a new diskgroup.

ORA-15024: discovered duplicately numbered ASM disk string

Cause: The discovery encountered two disks claiming to have the same ASM disk number.

Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.

ORA-15025: could not open disk "string"

Cause: The specified disk could not be opened.

Action: Check the additional error messages, if any.

ORA-15026: disk "string" is not an ASM disk

Cause: The disk did not contain a valid ASM disk header.

Action: Check to see if the data on the disk has been changed by some system administrator action.

ORA-15027: active use of diskgroup "string" precludes its dismount

Cause: An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup which had database client instances with open files in the diskgroup. Diskgroups cannot be dismounted until all open files in the diskgroup are closed by the database client instances.

Action: Stop all clients that are using this diskgroup and retry the ALTER DISKGROUP ... DISMOUNT command. The V$ASM_CLIENT fixed view in an ASM instance provides a list of its active database client instances.

ORA-15028: ASM file "string" not dropped; currently being accessed

Cause: An attempt was made to drop an ASM file, but the file was being accessed by one or more database instances and therefore could not be dropped.

Action: Shut down all database instances that might be accessing this file and then retry the drop command.

ORA-15029: disk "string" is already mounted by this instance

Cause: An attempt was made to add to a diskgroup a disk that was already mounted by the current instance as part of some (possibly other) diskgroup.

Action: Specify a different disk in the command. Note that not even the FORCE option can be used to correct the situation until the diskgroup containing the disk becomes dismounted by this instance.

ORA-15030: diskgroup name "string" is in use by another diskgroup

Cause: A CREATE DISKGROUP command specfied a diskgroup name that was already assigned to another diskgroup.

Action: Select a different name for the diskgroup.

ORA-15031: disk specification "string" matches no disks

Cause: The device specification string to a CREATE DISKGROUP command did not match any devices which could be discovered.

Action: Check the device specification string matches a disk on the system.

ORA-15032: not all alterations performed

Cause: At least one ALTER DISKGROUP action failed.

Action: Check the other messages issued along with this summary error.

ORA-15033: disk "string" belongs to diskgroup "string"

Cause: An attempt was made to ADD to a diskgroup a disk that was already part of another diskgroup, or an attempt was made to DROP / OFFLINE / ONLINE / CHECK a disk that was not part of the specified diskgroup.

Action: For ADD, check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. For the other commands, check the name of the specified disk.

ORA-15034: disk "string" does not require the FORCE option

Cause: An attempt was made to add the disk to the diskgroup using the FORCE option. The disk was not found to be in use at the present time, so the FORCE option was not permitted.

Action: Avoid gratuitous use of the FORCE option.

ORA-15035: no disks belong to diskgroup "string"

Cause: An attempt was made to mount a diskgroup for which no member disks were discovered.

Action: Specify a valid diskgroup name that contains disks.

ORA-15036: disk "string" is truncated

Cause: The size of the disk, as reported by the operating system, was smaller than the size of the disk as recorded in the disk header block on the disk.

Action: Check if the system configuration has changed.

ORA-15037: disk "string" is smaller than mimimum of string MBs

Cause: The size of the disk, as reported by the operating system, was too small to allow the disk to become part of the diskgroup.

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

Action: Check if the system configuration has changed.

ORA-15039: diskgroup not dropped

Cause: An attempt to drop a diskgroup failed.

Action: See the associated messages for details about why the drop was not successful.

ORA-15040: diskgroup is incomplete

Cause: Some of the disks comprising a diskgroup were not present.

Action: Check the hardware to ensure that all disks are functional. Also check that the setting of the ASM_DISKSTRING initialization parameter has not changed.

ORA-15041: diskgroup space exhausted

Cause: The diskgroup ran out of space.

Action: Add more disks to the diskgroup, or delete some existing files.

ORA-15042: ASM disk "string" is missing

Cause: The specified disk, which is a necessary part of a diskgroup, could not be found on the system.

Action: Check the hardware configuration.

ORA-15043: ASM disk "string" is not a diskgroup member

Cause: The specified disk has been removed from the diskgroup, but a disk matching its name was found.

Action: Check the hardware configuration.

ORA-15044: ASM disk "string" is incorrectly named

Cause: Either the specified disk had its contents changed such that it no longer contained an ASM disk name in its header that matches the diskgroup information or its FAILGROUP information may have become inconsistent.

Action: Drop the disk from the diskgroup.

ORA-15045: ASM file name "string" is not in reference form

Cause: The ASM file name was not in a form that can be used to reference an existing file because a file/incarnation number or an alias name was not present or a template name was included.

Action: Correct the specified ASM file name.

ORA-15046: ASM file name "string" is not in single-file creation form

Cause: The ASM file name was not in a form that can be used to create an single file because a file/incarnation number was present.

Action: Correct the specified ASM file name.

ORA-15047: ASM file name "string" is not in multiple-file creation form

Cause: The ASM file name was not in a form that can be used to create multiple files because either a fully-qualified file name or an alias name was present.

Action: Correct the specified ASM file name.

ORA-15048: ASM internal files cannot be deleted

Cause: An attempt was made to delete a metadata file used by ASM to manage the diskgroup.

Cause: A disk size expression exceeded the amount of storage actually availalable, as reported by the operating system.

Action: Specify a valid size.

ORA-15058: disk "string" belongs to an incompatible diskgroup

Cause: An attempt was made to ADD to a diskgroup a disk which was already part of another diskgroup. The other diskgroup was written by a more recent software release.

Action: Check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check.

ORA-15059: invalid device type for ASM disk

Cause: The device type of the discovered disk was not valid for use as an ASM disk.

Action: Check the file path and retry or exclude it from the discovery set. See the accompanying operating system error for additional information.

ORA-15060: template "string" does not exist

Cause: A command specified a template name, either directly or as part of an ASM file name, which did not exist.

Action: Check the template specifier in the command.

ORA-15061: ASM operation not supported [string]

Cause: An ASM operation was attempted that is invalid or not supported by this version of the ASM instance.

Action: This is an internal error code that is used for maintaining compatibility between software versions and should never be visible to the user; contact Oracle support Services.

ORA-15062: ASM disk is globally closed

Cause: The disk to which the I/O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information.

Action: Bring the disk online for I/Os to get through.

ORA-15063: ASM discovered an insufficient number of disks for diskgroup "string"

Cause: ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.

Action: Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.

ORA-15064: communication failure with ASM instance

Cause: There was a failure to communicate with the ASM instance, most likely because the connection went down.

Action: Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally.

ORA-15065: hash collision for diskgroup names "string" and "string"

Cause: There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names.

Action: Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided.

ORA-15066: offlining disk "string" may result in a data loss

Cause: Following I/O failures, the disks holding all copies of a data block were attempted to be taken offline.

Action: Check the accompanying error messages for more information on the reason for the disk I/O failures.

ORA-15067: command or option incompatible with diskgroup redundancy

Cause: An attempt was made to use a feature which is not permitted by the diskgroup"s redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes.

Action: Omit the option from the command.

ORA-15068: maximum number of diskgroups string already mounted

Cause: An attempt was made to mount more diskgroups than the instance is capable of mounting at one time.

Cause: An attempt was made to access an ASM file, but the file is currently being created, resized, or deleted and therefore cannot be accessed.

Action: No action required, or try again later, after the create or resize has completed.

ORA-15070: maximum number of files string exceeded in diskgroup "string"

Cause: The diskgroup ran out of space.

Action: Delete some existing ASM files or create files in a new diskgroup.

ORA-15071: ASM disk "string" is already being dropped

Cause: An attempt was made to drop a disk from a diskgroup which was already in the process of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly drop a disk from a diskgroup using the FORCE option which was already being forcibly dropped from the diskgroup.

Action: Check the ASM disk name and FORCE option as specified in the command.

Cause: An attempt was made to create either a normal redundancy diskgroup for which fewer than two failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three failure groups were both specified and discovered.

Action: Check the that the command does specify the required number of failure groups, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view will show which disks are discovered by ASM.

ORA-15073: diskgroup string is mounted by another ASM instance

Cause: An attempt was made to drop a diskgroup that is still mounted somewhere in the cluster by another instance.

Action: dismount the diskgroup from all nodes except the one performing the drop diskgroup command.

ORA-15074: diskgroup string requires rebalance completion

Cause: An attempt was made to repeatedly add or drop disks from a diskgroup. ASM could not perform the operation given the current state of the diskgroup.

Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow the rebalance to run to completion. Alternatively, invoke the ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to run to completion. After the rebalance has completed, retry the operation.

ORA-15075: disk(s) are not visible cluster-wide

Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration.

Action: Determine which disks are causing the problem from the GV$OSM_DISK fixed view. Check operating system permissions for the device and the storage sub-system configuration on each node in a RAC cluster that cannot identify the disk.

ORA-15076: Emulating I/O errors on the OSM disk

Cause: The disk to which the I/O request was issued is in an error emulation mode.

Action: Bring the disk online for I/Os to get through.

ORA-15077: could not locate ASM instance serving a required diskgroup

Cause: The instance failed to perform the specified operation because it could not locate a required ASM instance.

Action: Start an ASM instance and mount the required diskgroup.

ORA-15078: ASM diskgroup was forcibly dismounted

Cause: The diskgroup to which the I/O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be accessed.

Action: Mount the diskgroup to allow access again.

ORA-15079: ASM file is closed

Cause: The file to which the I/O request was issued was closed. This could have been a consequence of the diskgroup being dismounted.

Action: Make sure the diskgroup is mounted and the file is open.

ORA-15080: synchronous I/O operation to a disk failed

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

Action: Make sure that all the disks are operational.

ORA-15081: failed to submit an I/O operation to a disk

Cause: A submission of an I/O operation to a disk has failed.

Action: Make sure that all the disks are operational.

ORA-15082: ASM failed to communicate with database instance

Cause: There was a failure when ASM tried to communicate with a database instance (most likely because the connection went down).

Action: Check the accompanying error messages for more information on the reason for the failure. Note that the ASM instances may return this error when a database instance is terminated abnormally.

ORA-15083: failed to communicate with ASMB background process

Cause: A database instance failed to communicate with its ASMB background process when attempting to access an ASM file.

Action: Check the alert log for more information on the reason for the failure.

ORA-15090: handle string is not a valid descriptor

Cause: The file handle was not valid in this session.

Action: Submit a handle obtained from a successful call to DBMS_DISKGROUP.OPEN().

ORA-15091: operation incompatible with open handle in this session

Cause: The current session contained an open handle from the DBMS_DISKGROUP PL/SQL package which precluded performing the command.

Action: Close the hanlde with DBMS_DISKGROUP.CLOSE() before executing the command, or execute the command in a different session.

Cause: A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active.

Action: The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups.

ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance

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

Action: Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance.

Cause: The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options.

Action: Specify only one option.

ORA-15105: missing or invalid FAILGROUP name

Cause: The command did not specify a valid failure group name.

Action: Specify a valid failure group name.

ORA-15106: missing or invalid operating system disk locator string

Cause: The command did not specify a valid operating system path for the device as a string.

Action: Specify a valid operating system path for the device.

ORA-15107: missing or invalid ASM disk name

Cause: The command did not specify a valid ASM disk name identifier.

Action: Specify a valid ASM disk name identifier.

ORA-15108: missing or invalid template name

Cause: The command did not specify a valid template name identifier.

Action: Specify a valid template name identifier.

ORA-15109: conflicting protection attributes specified

Cause: The command contained an invalid combination of the UNPROTECTED, MIRROR, or PARITY keywords.

Action: Specify only one keyword.

ORA-15110: no diskgroups mounted

Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount any diskgroups.

Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the error.

ORA-15111: conflicting or duplicate STRIPE options

Cause: The command contained both a FINE and COARSE keyword, or contained the FINE keyword more than once, or contained the COARSE keyword more than once.

Action: Specify only one keyword.

ORA-15112: No diskgroups are currently mounted.

Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups upon which to operate. Either instance shutdown or an ALTER DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks.

Action: Mount the diskgroups on which you wish to operate or ignore the error.

ORA-15113: alias name "string" refers to a directory

Cause: The name specified referred to a directory in the alias directory and not a valid alias entry.

Action: Check the alias name and retry.

ORA-15114: missing or invalid ASM file name

Cause: The command did not specify a valid ASM file name identifier.

Action: Specify a valid ASM file name identifier.

ORA-15115: missing or invalid ASM disk size specifier

Cause: The command did not specify a valid ASM disk size.

Action: Specify a valid ASM disk size.

ORA-15116: invalid combination of ALTER DISKGROUP options

Cause: The ALTER DISKGROUP options may not be combined in this manner.

ORA-15120: ASM file name "string" does not begin with the ASM prefix character

Cause: A file name was specified to ASM which did not begin with the ASM prefix character (currently "+"). ASM uses the prefix to determine that a file specification is in fact an ASM file.

Action: Correct the file name specification.

ORA-15121: ASM file name "string" contains an invalid diskgroup name

Cause: A file name was specified that did not contain a valid diskgroup name. The diskgroup name follows immediately after the ASM prefix character. It must start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters "$" and "_".

Action: Correct the file name specification.

ORA-15122: ASM file name "string" contains an invalid file number

Cause: A numeric file name was specified which did not contain a valid ASM file number. The ASM file number follows immediately after the diskgroup name. It must be preceeded by a "." character, and contain only numeric characters.

Action: Correct the file name specification.

ORA-15123: ASM file name "string" contains an invalid incarnation number

Cause: A numeric file name was specified which did not contain a valid ASM incarnation number. The ASM incarnation number follows immediately after the ASM file number. It must be preceeded by a "." character, and contain only numeric characters.

Action: Correct the file name specification.

ORA-15124: ASM file name "string" contains an invalid alias name

Cause: A file name was specified which did not contain a valid ASM alias name. The ASM alias name, if present, follows immediately after the diskgroup name, in place of the ASM file number. It must be preceeded by a slash, start with an alphabetic character, and consist of up to 48 characters which are alphabetic, numeric, or the characters "$", "_", "-", or "#". A space can separate two parts of an alias name.

Action: Correct the file name specification.

ORA-15125: ASM file name "string" contains an invalid template name

Cause: A file name was specified to ASM which did not contain a valid template name. The template name, if present, follows immediately after the ASM incarnation number or the ASM alias name, if such is used in place of the ASM file number. It must be enclosed in parenthesis, start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters "$" and "_".

Cause: The maximum identifier length of 30 characters was exceeded for the diskgroup name, template name, or alias name field within the ASM file name.

Action: Correct the file name specification.

ORA-15127: ASM file name "string" cannot use templates

Cause: A fully qualified ASM file name was specified. Such a specification does not permit the inclusion of a template name in the ASM file name.

Action: Correct the file name specification.

ORA-15128: ASM file name "string" exceeds maximum length string

Cause: The maximum ASM file name length of 256 characters was exceeded for the combination of diskgroup name, file number, template name, alias name plus punctuation within the ASM file name.

Action: Correct the file name specification.

ORA-15129: entry "string" does not refer to a valid directory

Cause: The entry indicated did not refer to a directory. Attempt was made to access the contents of this directory.

Action: Correct the error and try again.

ORA-15130: diskgroup "string" is being dismounted

Cause: The diskgroup is being dismounted by request or because an I/O error was encountered that could not be handled by taking the disks offline. A disk cannot be offlined whenever doing so could result in all copies of a redundant extent being unavailable.

Action: Repair the hardware problem and re-mount the diskgroup. Refer to the alert log to determine which disks have failed.

ORA-15131: block string of file string in diskgroup string could not be read

Cause: A block could not be read because the disk containing the block is either offline or an I/O error occured while reading the block. If this is mirrored file, then all disks that contain a copy of the block are either offline or received errors.

Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.

ORA-15132: block string of file string in diskgroup string could not be written

Cause: A block could not be written because the disk containing the block is either offline or an I/O error occured while writing the block. If this is mirrored file, then insufficient disks which contain a copy of the block are either offline or received errors.

Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.

ORA-15133: instance recovery required for diskgroup string

Cause: An instance in the cluster crashed making instance recovery necessary.

Action: None. This error should not normally be seen by an ASM client. ASM will trap this error and retry the operation after doing instance recovery automatically.

Cause: Some other ASM instance used the lock name space in a conflicting mode.

Action: Shut down the other instance or start up in compatible mode. Alternatively, set the DB_UNIQUE_NAME initialization parameter to avoid the conflict.

ORA-15151: missing or invalid version number for rolling upgrade or downgrade

Cause: The command did not sepcify a valid version number.

Action: Correct the version number in the command. It should be of the form v#.#.#.#.# or other forms with fewer numbers delimited by a period. The version number must be different from the current software version of the instance.

ORA-15152: cluster in rolling upgrade

Cause: The cluster was already in the middle of rolling upgrade.

Action: Rolling upgrade needs to be stopped before attempting to start again.

ORA-15153: cluster not in rolling upgrade

Cause: The cluster was not in rolling upgrade.

Action: Start the rolling upgrade using the ALTER SYSTEM START ROLLING command.

ORA-15154: cluster rolling upgrade incomplete

Cause: The cluster was still performing rolling upgrade.

Action: Ensure that all the instances in the cluster are upgraded before retrying the command.

ORA-15155: version incompatible with the cluster

Cause: The current software version of the instance was incompatible with the other members of the cluster.

Action: Make sure that all the members of the cluster are at the same version. If you are attempting to perform rolling upgrade, execute ALTER SYSTEM START ROLLING command. Ensure that the version being upgraded to is compatible with the existing version of the cluster.

ORA-15156: cluster in rolling upgrade from version [string] to [string]

Cause: The current software version of the instance was incompatible with the rolling upgrade operation of the cluster.

Action: The version number of new member instance must be one of the two versions involved in the rolling upgrade.

ORA-15157: rolling upgrade or downgrade is not allowed

Cause: The cluster was not capable of handling ASM rolling upgrade or downgrade.

ORA-15200: initialization parameter string (string) is not a power of two

Cause: The value specified for this initialization parameter was not a power of two.

Action: Correct the initialization parameter value and restart the instance.

ORA-15201: disk string contains a valid RDBMS file

Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ... ADD DISK command appeared to contain a file from an existing database. By default, ASM will not allow a diskgroup to be created using this disk, as a safeguard against damaging an existing database.

Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database is reused as part of an ASM diskgroup, specify the FORCE option to the ASM SQL command.

ORA-15202: cannot create additional ASM internal change segment

Cause: The mount of a diskgroup by an additional instance in a RAC cluster required more space for internal use by ASM than was available in the diskgroup.

Action: Delete unused files from the diskgroup or add additional disks to the diskgroup and retry the operation.

ORA-15203: diskgroup string contains disks from an incompatible version of ASM

Cause: Diskgroup was created by an ASM instance with a higher compatibility setting.

Action: Use an ASM instance with the appropriate software version to mount the diskgroup.

ORA-15204: database version string is incompatible with diskgroup string

Cause: The database compatibility of the diskgroup was advanced to a later version.

Action: Upgrade the database instance to appropriate version of ORACLE.

ORA-15205: requested mirror side unavailable

Cause: The requested mirror side of a block is either unallocated or allocated on a disk that has been dropped from the diskgroup.

Action: Resubmit the request or try another mirror side.

ORA-15206: duplicate diskgroup string specified

Cause: A command specified the same diskgroup twice.

Action: Specify each diskgroup only once.

ORA-16000: database open for read-only access

Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.

Action: In order to modify the database, it must first be shut down and re-opened for read-write access.

ORA-16001: database already open for read-only access by another instance

Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.

Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access.

ORA-16002: database already open for read-write access by another instance

Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.

Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access.

ORA-16003: standby database is restricted to read-only access

Cause: To ensure its integrity, a standby database can only be opened for read-only access.

Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY.

ORA-16004: backup database requires recovery

Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

ORA-16005: database requires recovery

Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

Cause: The audit_trail initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access.

Action: When the database is opened for read-only access, the audit_trail initialization parameter can only be set to "OS" or "NONE" (FALSE).

ORA-16007: invalid backup control file checkpoint

Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

ORA-16008: indeterminate control file checkpoint

Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

ORA-16009: remote archive log destination must be a STANDBY database

Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16011: Archivelog Remote File Server process in Error state

Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data.

Action: Correct the problem at the standby database site.

ORA-16012: Archive log standby database identifier mismatch

Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16013: log string sequence# string does not need archiving

Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.

Action: No action is required.

ORA-16014: log string sequence# string not archived, no available destinations

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.

Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.

Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.

ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination

Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.

Action: Set the primary archive destination to a valid non-NULL value.

ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST

Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.

Action: Eliminate any incompatible parameter definitions.

ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...10) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.

Action: Eliminate any incompatible parameter definitions.

ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST

Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.

Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16021: session string destination cannot be the same as session string destination

Cause: An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.

Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.

ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL

Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.

Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.

ORA-16023: system string destination cannot be the same as session string destination

Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.

Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.

ORA-16024: parameter string cannot be parsed

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained either repeated attributes or attributes that conflicted with each other.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16026: parameter string contains an invalid attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid value.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16027: parameter string is missing a destination option

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires

Cause: With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.

Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.

Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.

Cause: The value for the specified parameter contained a destination string that is too long.

Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.

ORA-16032: parameter string destination string cannot be translated

Cause: The value for the specified parameter contained a destination string that could not be translated.

Action: Use a valid destination string in the specified parameter.

ORA-16033: parameter string destination cannot be the same as parameter string destination

Cause: An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.

Action: Specify a different value for one of the archive log parameters.

ORA-16034: FROM parameter is incompatible with MANAGED recovery

Cause: Use of the FROM "location" parameter is not allowed when MANAGED recovery has been specified.

Action: Correct the syntax and retry the command.

ORA-16035: missing required keyword string

Cause: The indicated keyword is required but was not specified.

Action: Correct the syntax and retry the command.

ORA-16036: invalid MANAGED recovery CANCEL option

Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.

Action: Specify either nothing or IMMEDIATE following CANCEL.

ORA-16037: user requested cancel of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user request.

Action: No action is required.

ORA-16038: log string sequence# string cannot be archived

Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.

Action: No action is required.

ORA-16039: RFS request version mismatch

Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.

Action: Verify that compatible versions of Oracle are running on the primary and all standby sites.

ORA-16040: standby destination archive log file is locked

Cause: The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.

Cause: The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.

Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action.

Cause: The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state.

Action: No action is required.

ORA-16043: managed recovery session canceled

Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.

Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.

Action: No action required.

ORA-16047: DGID mismatch between destination setting and standby

Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.

Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.

ORA-16050: destination exceeded specified quota size

Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16052: DB_UNIQUE_NAME attribute is required

Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled.

Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.

ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration

Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.

Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.

ORA-16055: FAL request rejected

Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.

Action: to solve the problem.

ORA-16056: backup control file archival requires proper syntax

Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.

Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.

ORA-16057: DGID from server not in Data Guard configuration

Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby.

Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby.

ORA-16058: standby database instance is not mounted

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16059: Log file is empty or invalid next available block

Cause: Archiving not allowed of an empty or invalid log file.

Action: No action is required.

ORA-16060: Log file is current

Cause: The current log file cannot be archived using its file name.

Action: No action is required.

ORA-16061: Log file status has changed

Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.

Action: No action is required.

ORA-16062: DGID from standby not in Data Guard configuration

Cause: The Data Guard name from the standby is not in the Data Guard configuration of the server.

Action: In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server.

ORA-16063: remote archival is enabled by another instance

Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance.

ORA-16064: remote archival is disabled by another instance

Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance.

Action: If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur.

ORA-16066: remote archival disabled

Cause: An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.

Action: If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur.

ORA-16067: activation identifier mismatch in archive log string

Cause: The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.

Action: Locate the appropriate archive log for the database.

ORA-16068: redo log file activation identifier mismatch

Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.

Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).

Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.

ORA-16071: dependency archived log file not found string

Cause: The specified archived log file was not found at the indicated standby destination.

Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16076: unknown standby database destination

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16078: media recovery disabled

Cause: The database is not in ARCHIVELOG mode.

Action: Place the database in ARCHIVELOG mode.

ORA-16079: standby archival not enabled

Cause: The standby database does not have archival enabled.

Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.

ORA-16080: invalid LogMiner session string for APPLY

Cause: Logical standby apply engine was started with an invalid LogMiner session identifier.

Action: Fix the problem with the LogMiner session or create a new session.

ORA-16081: insufficient number of processes for APPLY

Cause: Logical standby apply engine was started with fewer processes available than needed.

Action: Increase the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16082: logical standby is not initialized correctly

Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.

Action: Look in the trace file for more information.

ORA-16083: LogMiner session has not been created

Cause: Logical standby apply engine was started without creating a LogMiner session.

Action: Create a LogMiner session and restart the apply engine.

ORA-16084: an apply engine is already running

Cause: A logical standby apply engine was running when another was created.

Action: Shut down the previous apply engine before starting a new one.

ORA-16086: standby database does not contain available standby log files

Cause: The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files".

Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted.

ORA-16087: graceful switchover requires standby or current control file

Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file.

Action: Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.

ORA-16088: archive log has not been completely archived

Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a "current" log file.

Action: Specify a completed archive log.

ORA-16089: archive log has already been registered

Cause: An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.

Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.

ORA-16090: archive log to be replaced not created by managed standby process

Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.

Action: No user action required.

ORA-16091: dependent archive log destination already archived

Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived.

Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.

ORA-16092: dependent archive log destination is not active

Cause: An archive log destination contains a dependency to another archive log destination that is not active"

Action: The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.

ORA-16093: dependent archive log destination is not LGWR-enabled

Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process"

Action: The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process.

ORA-16094: database shutdown during archival operation

Cause: The database was shut down while an online log file archival was active.

Action: None required. The ARCH process is terminated.

ORA-16095: Dependent destination removal for inactivation

Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.

Action: None required.

ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY

Cause: None

Action: Specify this command to prepare the primary database for switchover

ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY

Cause: None

Action: Specify this command to prepare the standby database for switchover

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16100: not a valid Logical Standby database

Cause: This database has not been completely configured as a Logical Standby database.

Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.

ORA-16101: a valid start SCN could not be found

Cause: An SCN from which to start could not be found.

Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement.

ORA-16102: remote information is not available on the specified primary

Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.

Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.

ORA-16103: Logical Standby apply must be stopped to allow this operation

Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.

Action: Check spelling or refer to the Oracle8i SQL Reference manual for the correct statement syntax, then re-enter the request.

ORA-16105: Logical Standby is already running in background

Cause: A Logical Standby apply operation is already running.

Action: none

ORA-16107: all log data from primary has been processed

Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.

Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;

ORA-16108: database is no longer a standby database

Cause: The current database has already been made a primary database.

Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;

ORA-16109: failed to apply log data from previous primary

Cause: Log data from previous primary could not be completely applied.

Action: . Then, re-issue command.

ORA-16110: user procedure processing of logical standby apply DDL

Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.

Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.

ORA-16111: log mining and apply setting up

Cause: This logical standby process is setting up to begin processing changes.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16112: log mining and apply stopping

Cause: This logical standby process is cleaning up and stopping Logical Standby apply.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16113: applying change to table or sequence string

Cause: The process is applying changes to a specific schema object.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16114: applying DDL transaction with commit SCN string

Cause: The process is applying a DDL change that"s committed at the given SCN.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16115: %s\% of LogMiner dictionary loading is done

Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16116: no work available

Cause: The process is idle waiting for additional changes to be made available.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16117: processing

Cause: The process is performing its primary function and is not waiting on any significant event.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16119: building transaction at SCN string

Cause: The transaction being committed at the given SCN is being prepared for apply.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16120: dependencies being computed for transaction at SCN string

Cause: The transaction committed at the given SCN is being analyzed for dependencies.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16121: applying transaction with commit SCN string

Cause: The transaction committed at the given SCN is being applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16122: applying large dml transaction at SCN string

Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16124: transaction stringstringstring is waiting on another transaction

Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16125: large transaction stringstringstring is waiting for more data

Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16126: loading table or sequence string

Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16127: stalled waiting for additional transactions to be applied

Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.

ORA-16128: User initiated stop apply successfully completed

Cause: Logical standby was shutdown in an orderly fashion.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16129: unsupported dml encountered

Cause: DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support.

Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.

ORA-16131: An error occurred during a Terminal Recovery of the standby.

Cause: An error occurred during a Terminal Recovery of the standby.

Action: Check the standby alert log additional information.

ORA-16132: An error occurred during activation of the standby.

Cause: An error occurred during activation of the standby database following a Terminal Recovery.

Action: Check the standby alert log additional information.

ORA-16133: Datafile string has incorrect terminal recovery stamp.

Cause: After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.

Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.

ORA-16134: invalid MANAGED recovery FINISH option

Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.

Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode.

Action: Make the modification before the database is opened by any instance.

ORA-16136: Managed Standby Recovery not active

Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.

Action: No action is necessary.

ORA-16137: No terminal recovery is required

Cause: All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required.

Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.

ORA-16138: end of log stream not received from primary

Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.

Action: Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.

ORA-16139: media recovery required

Cause: The database has not been recovered through the end of log stream. Graceful switchover is not possible.

Action: Ensure that the entire log stream has been applied. If appropriate, reissue the graceful switchover command.

ORA-16140: standby online logs have not been recovered

Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.

Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.

Action: No action is required.

ORA-16151: Managed Standby Recovery not available

Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.

Action: Wait for the managed standby recovery session to end. Then retry the operation.

ORA-16152: standby database is in "no-data-loss" protected mode

Cause: The attempted database operation is not allowed while the standby database is in "no-data-loss" protected mode.

Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.

ORA-16154: suspect attribute: string

Cause: Use of the indicated attribute is illegal in the given context.

Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.

ORA-16159: Cannot change protected standby destination attributes

Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database.

Action: No action is required.

ORA-16160: Cannot change protected standby database configuration

Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16161: Cannot mix standby and online redo log file members for group string

Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.

Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.

Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16163: LGWR network server host attach error

Cause: The LGWR network server could not attach to remote host

Action: The alert log contains more problem-specific information

ORA-16164: LGWR network server host detach error

Cause: The LGWR network server could not detach from remote host

Action: The alert log contains more problem-specific information

ORA-16165: LGWR failed to hear from network server

Cause: The LGWR lost its connection to the network server

Action: The alert log contains more problem-specific information

ORA-16166: LGWR network server failed to send remote message

Cause: The LGWR network server could not communicate with the remote host

Action: The alert log contains more problem-specific information

ORA-16167: LGWR network server could not switch to non-blocking mode

Cause: The LGWR network server could not switch to non-blocking mode

Action: The alert log contains more problem-specific information

ORA-16168: LGWR network server could not switch to blocking mode

Cause: The LGWR network server could not switch to blocking mode

Action: The alert log contains more problem-specific information

ORA-16169: LGWR network server invalid parameters

Cause: The LGWR network server could not switch to blocking mode

Action: The alert log contains more problem-specific information

ORA-16170: Terminal recovery may have left the database in an inconsistent state

Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

Cause: See alert log for more details

Action: Copy missing archived logs from primary or another standby. Register the logs and re-issue the RECOVER...FINISH command. If the logs are not available, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files.

ORA-16172: archive logs detected beyond Terminal End-Of-Redo

Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.

Action: none

ORA-16173: incompatible archival network connections active

Cause: One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.

Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.

Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action is required.

ORA-16175: cannot shut down database when media recovery is active

Cause: An attempt was made to shut down a standby database while media recovery was active.

Action: Cancel media recovery to proceed with the shutdown.

ORA-16176: background dictionary build cannot be running

Cause: The background process dedicated to dictionary build is active.

Action: wait and try it later.

ORA-16177: media recovery is not required

Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required.

Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.

Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.

Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings.

ORA-16191: Primary log shipping client not logged on standby

Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials.

Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE.

ORA-16192: Primary and standby network integrity mismatch

Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.

Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and/or standby.

ORA-16193: Primary and standby network encryption mismatch

Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.

Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and/or standby.

ORA-16194: Modifying DB_UNIQUE_NAME requires SID="*" qualifier

Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID="*" qualifier is required.

Action: Re-enter the command using the SID="*" qualifier.

ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.

Action: Explicitly define a valid DB_UNIQUE_NAME.

ORA-16196: database has been previously opened and closed

Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.

Action: Shut down the instance.

ORA-16197: Invalid DB_UNIQUE_NAME parameter specification

Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and "_", "$" and "#".

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-16211: unsupported record found in the archived redo log

Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.

Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it"s unimportant.

2. ALTER DATABASE START LOGICAL STANDBY APPLY;

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

4. Provide the log file to Oracle Support Services.

ORA-16212: number processes specified for APPLY is too great

Cause: Logical standby apply engine was started with more processes requested than are available.

Action: Adjust the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16213: ddl encountered, stopping apply engine

Cause: stop_on_ddl callout specified and DDL was encountered.

Action: Either disable stop_on_ddl callout or remove DDL.

ORA-16214: apply stalled for apply delay

Cause: A delay has been specified on the primary database for this destination.

Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET("APPLY_DELAY"); to override.

ORA-16215: history metadata inconsistency

Cause: internal error.

Action: This is an internal error. Contact Oracle support.

ORA-16216: Log stream sequence error

Cause: The log stream being processed did not follow the last processed stream.

Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream.

ORA-16217: prepare to switchover has not completed

Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.

Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby.

ORA-16218: This database is already preparing to switch over.

Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt.

Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.

ORA-16219: This database is not preparing to switch over.

Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.

Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.

Cause: A request was made to skip a parallel DML child transaction id. This is not supported.

Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.

ORA-16230: committing transaction stringstringstring

Cause: Logical Standby apply was committing changes for the given transaction.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16231: DDL barrier

Cause: Logical Standby was holding back changes until dependent changes were applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16232: adding Logical Standby skip entry for table string.string

Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.

Action: To have Logical Standby maintain the table, import that table directly from the primary.

ORA-16233: The table string.string is unsupported now

Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.

Action: None.

ORA-16234: restarting to reset Logical Standby apply

Cause: Logical Standby encountered a work load that required a restart to properly reschedule.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16235: DDL skipped because import has occurred

Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16236: Logical Standby metadata operation in progress

Cause: The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished.

Action: Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation.

ORA-16237: SGA specified for Logical Standby is too small

Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.

Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes.

ORA-16238: attempt to use version 9 log

Cause: Version 9 log files are not supported.

Action: Use log files of a supported version.

ORA-16239: IMMEDIATE option not available without standby redo logs

Cause: The IMMEDIATE option cannot be used without standby redo logs.

Action: Do not specify the IMMEDIATE option unless standby redo logs are being used."

ORA-16240: Waiting for logfile (thread# string, sequence# string)

Cause: Reader process is idle waiting for additional logfile to be available.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16241: Waiting for gap logfile (thread# string, sequence# string)

Cause: Reader process is idle waiting for the logfile to fill the log sequence gap.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16242: Processing logfile (thread# string, sequence# string)

Cause: Reader process is processing the logfile.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16243: paging out string bytes of memory to disk

Cause: Builder process is paging out momery to free up space in lcr cache.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16244: taking checkpoint and paging out string bytes to disk

Cause: Builder process is taking a checkpoint to advance restart_scn

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16245: paging in transaction string, string, string

Cause: Builder process is paging in transactions from disk.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16246: User initiated abort apply successfully completed

Cause: SQL Apply was stopped using the abort option.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16247: DDL skipped on internal schema

Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = "INTERNAL SCHEMA".

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16248: RFS connections not permitted during Terminal Apply

Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.

Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover.

ORA-16250: Failed to acquire starting scn of new log stream

Cause: The starting SCN for the new log stream could not be determined.

Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.

ORA-16251: LSP1 Background Build not permitted

Cause: The LSP1 background process is not permitted to start because it had previously been attempted.

Action: This is an internal error. Contact Oracle support.

ORA-16252: Rebuild operation not permitted

Cause: The REBUILD operation is not permitted.

Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.

Cause: LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered.

Action: No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file.

ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST

Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.

Action: No action is required.

ORA-16401: archivelog rejected by RFS

Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.

Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.

Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters.

Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error.

ORA-16403: shutdown in progress - remote connection is not permitted

Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.

Action: Wait for the remote instance to be restarted, or contact your DBA.

ORA-16406: Primary and standby database software version mismatch

Cause: The primary database and standby database Oracle software is not compatible.

Action: Install the correct Oracle software and try again.

ORA-16407: Standby database is in the future of the archive log

Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs.

Action: No action is required.

ORA-16408: Incompatible archival Redo Branch lineage

Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs.

Action: No action is required.

ORA-16409: Archive log switchover reference number mismatch

Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Cause: The use of the ONDEMAND attribute for a standby database destination is supported for only physical and logical standby database types. Cross-Instance-Archival and repository database types are not valid for the ONDEMAND attribute.

Action: Verify the database corresponding to the archivelog destination is either a physical standby database or a logical standby database.

ORA-16416: Switchover target is not synchronized with the primary

Cause: The switchover target incurred an error or has a gap at the time the switchover operation was attempted.

Action: Allow the switchover target to become synchronized and then re-attempt the switchover.

ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required

Cause: The broker may return this error for switchover operations and for database state change operations. If this error is returned for a switchover operation, the broker has determined that either:

- The databases changing roles are offline.

- The primary database is not shipping log files.

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

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

- The databases changing roles are online.

- The primary database is shipping log files.

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

ORA-16517: the object handle is invalid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16518: unable to allocate virtual instance id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16519: the resource handle is invalid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16520: unable to allocate resource id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16521: unable to create generic template id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16522: generic template not found

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16523: operation requires the client to connect to instance "string"

Cause: The switchover or failover operation requires the client to connect to the apply instance of the target database.

Action: Connect to the indicated instance and reissue the switchover or failover command.

ORA-16524: unsupported operation

Cause: A command or option is not supported in this release.

Action: Contact Oracle Support Services.

ORA-16525: the Data Guard broker is not yet available

Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start.

Action: If the broker has not been started, set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.

ORA-16526: unable to allocate task element

Cause: The Data Guard broker was unable to allocate memory for a request.

Action: Increase the size of your SGA.

ORA-16527: unable to allocate SGA heap

Cause: The Data Guard broker was unable to allocate a heap within the SGA.

Action: Increase SGA memory.

ORA-16528: unable to allocate PGA heap

Cause: No space in PGA to allocate heap

Action: Increase process virtual memory.

ORA-16529: bad sender id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16530: invalid buffer or length

Cause: A NULL buffer or a length of zero is specified.

Action: Correct command parameters and retry.

ORA-16531: unable to post message

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16532: Data Guard broker configuration does not exist

Cause: A broker operation was requested that requires an already existing broker configuration.

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

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

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

Action: Wait until the operation is complete and then reissue the request.

ORA-16535: CRS is preventing execution of a broker operation

Cause: A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker"s request on at least some of the instances, so the broker operation was canceled.

Cause: The Data Guard broker did not recognize the specified property or state name.

Action: Verify command parameters and reissue the request.

ORA-16539: task element not found

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16540: invalid argument

Cause: One of the arguments for the specified request was invalid for the request type.

Action: Verify arguments and then reissue the request.

ORA-16541: site is not enabled

Cause: The site specified in the request was not enabled.

Action: Select an enabled site and reissue the request.

ORA-16542: unrecognized operation

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16543: invalid request made to broker

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16544: modifying DG_BROKER_START requires SID="*" qualifier

Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID="*" qualifier was required in the command.

Action: Reenter the command using the SID="*" qualifier.

ORA-16545: unable to get response

Cause: The Data Guard broker was unable to return the result of a previous request.

Action: Contact Oracle Support Services.

ORA-16546: missing or invalid piece

Cause: The piece of the request to return was not specified or was invalid.

Action: Specify the piece of the response starting from 1.

ORA-16547: cannot disable the primary database

Cause: An attempt was made to explicitly disable broker management of the primary database.

Action: Broker management of the primary database cannot be explicitly disabled. Instead you must disable the entire broker configuration if you wish to disable the primary database.

ORA-16548: object not enabled

Cause: An attempt was made to modify or query a disabled Data Guard object, most likely a database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created. The broker also disables management of a database that lags behind in terms of DRC Unique ID sequence value. This value is updated after successful switchover and failover operations.

Action: If broker management of the database is disabled, enable it and reissue the request.

ORA-16549: invalid string

Cause: A request contained an invalid or NULL string value.

Action: Correct command parameters and retry.

ORA-16550: truncated result

Cause: A string property value was truncated due to insufficient buffer size.

Action: Specify a larger receive buffer.

ORA-16551: short string copied

Cause: A string property value that did not fill the receive buffer was placed in the receive buffer.

Action: This is an informational message only. It is not an error.

ORA-16552: an error occurred when generating the CLIENT OPERATION table

Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Customer Support.

ORA-16553: the Data Guard broker process (DMON) failed to shutdown

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16554: translation not valid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16555: the Data Guard database is not active

Cause: An operation was attempted on a database that is currently not active (off path).

Action: Verify that the database is active.

ORA-16556: error message is in XML already

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16557: the database is already in use

Cause: An attempt was made to create a duplicate database in the broker configuration.

Action: Check the database to be added and be sure there are no duplicates.

ORA-16558: the database specified for switchover is not a standby database

Cause: An attempt was made to switchover to a database that is not a standby database.

Action: Locate an enabled standby database and select that database as the target of the switchover.

ORA-16559: out of memory at string

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16560: unable to convert document, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16561: cannot remove an active instance

Cause: The instance to be removed is currently running.

Action: Shut down the instance and reissue the REMOVE command.

ORA-16562: intended_state not used here, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16563: unable to add value, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16564: lookup failed, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16565: duplicate property, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and submit the request again.

ORA-16566: unsupported document type

Cause: The XML document submitted is not supported.

Action: Correct the errors and submit the request again.

ORA-16567: Data Guard broker internal parser error at "string"

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16568: cannot set property string

Cause: The named property could not be modified. The property may not be editable or may not exist.

Action: Retry the operation with a valid property.

ORA-16569: Data Guard configuration is not enabled

Cause: The requested operation required that broker management of the Data Guard configuration must be enabled.

Action: Enable the Data Guard configuration and reissue the request.

ORA-16570: operation requires restart of database "string"

Cause: The Data Guard broker operation required a database to be shutdown and restarted.

Action: If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it.

ORA-16571: Data Guard configuration file creation failure

Cause: The Data Guard broker was unable to create the configuration file on permanent storage.

Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters and retry.

ORA-16572: Data Guard configuration file not found

Cause: The Data Guard broker configuration file was either unavailable or did not exist.

Action: Verify that the configuration file was successfully created. If the dg_broker_config_file[1|2] parameter was changed, ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.

Cause: The Data Guard broker configuration file parameter was currently in use because broker management of the configuration was enabled. The attempt to alter that parameter was rejected.

Action: Disable the configuration and shut down the Data Guard broker before changing this value. Be sure to rename the configuration file at the OS level to match the new value before reenabling broker management of the configuration.

Action: Check the states of the broker configuration, primary database and standby database. Set their states to ONLINE if necessary.

ORA-16575: request terminated at broker discretion

Cause: This status is returned when the broker terminates a user- initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.

Action: There is no action to be taken.

ORA-16576: failed to update Data Guard configuration file

Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.

Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters.

Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.

Action: Contact Oracle Support Services.

ORA-16596: object not part of the Data Guard broker configuration

Cause: A request was made on a database object that is not in the Data Guard broker configuration. The request cannot be completed.

Action: Reissue the request on a database object that is in the broker configuration.

ORA-16597: Data Guard broker detects two or more primary databases

Cause: The Data Guard broker detected two or more primary databases in the broker configuration and cannot continue.

Action: Contact Oracle Support Services.

ORA-16598: Data Guard broker detected a mismatch in configuration

Cause: The Data Guard broker detected a significant mismatch in configuration validation between two or more databases in the broker configuration. This can occur when the primary database has a stale broker configuration file.

Action: Contact Oracle Support Services.

ORA-16599: Data Guard broker detected a stale configuration

Cause: The Data Guard broker detected a stale configuration during initialization for this database.

Action: The broker will automatically resolve this situation once the primary database completes its initialization.

ORA-16600: failover operation can only be submitted at target database

Cause: This error is returned when a failover request specified a different database than the database to which the client is currently connected.

Action: Explicitly connect to the database to which you wish to failover and reissue the failover request.

ORA-16601: site contains required resources that are disabled

Cause: The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled.

Action: Enable all required resources and reissue the request.

ORA-16602: object must be disabled to perform this operation

Cause: An attempt was made to edit a database object that can only be done while broker management of that database is disabled.

Action: Disable broker management of the database and reissue the request.

ORA-16603: Data Guard broker detected a mismatch in configuration ID

Cause: The Data Guard broker for this database detected a mismatch in configuration Unique ID. This can occur if the original configuration was recreated while this database was disconnected from the network or the same database was added to two different broker configurations.

Action: Make sure the database belongs to only one broker configuration. Remove the Data Guard broker configuration files and restart the broker.

ORA-16604: unable to describe template using package "string"

Cause: The Data Guard broker was unable to execute the OnDescribe function in the named package.

Action: Verify that the named package is loaded on the primary database. Also verify that the OnDescribe function is in the package.

ORA-16605: unable to delete template, template is in use

Cause: The Data Guard broker was unable to delete the template because the template is still being used by one or more resources.

Action: Delete all resources using the template before deleting the template. You cannot delete the database template.

ORA-16606: unable to find property "string"

Cause: The named property does not exist.

Action: Specify a valid property name and reissue the request.

ORA-16607: one or more databases have failed

Cause: The Data Guard broker detected a failure for one or more databases in the Data Guard configuration.

Action: Locate the database(s) with a failure status and correct it.

ORA-16608: one or more databases have warnings

Cause: The Data Guard broker detected a warning status for one or more databases.

Action: Locate the database(s) with a warning status and correct it.

ORA-16611: operation aborted at user request

Cause: The Data Guard broker aborted an operation at the user"s request.

Action: No action required.

ORA-16612: string value too long for attribute "string"

Cause: The string value for the named attribute is too long.

Action: Use a shorter string.

ORA-16613: initialization in progress for database

Cause: The database received a directive to change its initialization state or a change in its configuration before it has completed initialization.

Action: Wait until the database has completed initialization before issuing requests to modify run-time state or configuration.

ORA-16614: object has an ancestor that is disabled

Cause: A request to enable an object that has an ancestor that is disabled was received by the broker. The broker has enabled management of the object to the extent that it can, but cannot fully enable the object until its ancestor is enabled.

Action: Determine the ancestor object that is disabled and enable that ancestor prior to enabling the child object.

ORA-16617: unknown object identifier specified in request

Cause: The Data Guard broker returned this error because the object identifier specified in the request was invalid or unknown. For example, this error is returned if an invalid or unknown database object identifier is specified in a request that requires a database object identifier.

Action: Verify that a valid object identifier was specified in the request and then reissue the request.

ORA-16618: response document of size "string" bytes is too large

Cause: The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard broker log.

Action: View the broker log for the given database directly.

ORA-16619: health check timed out

Cause: This status is returned when the Data Guard broker could not reach a standby database during a routine health check.

Action: This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame.

ORA-16620: one or more databases could not be contacted for a delete operation

Cause: The Data Guard broker could not reach one or more standby databases for either a delete database operation or a delete broker configuration operation.

Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database"s Data Guard broker log for to determine which standby databases could not be reached. Then for each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, dg_broker_start, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database"s dg_broker_config_file[1|2] parameter values and delete them.

ORA-16621: database name for ADD DATABASE must be unique

Cause: An attempt was made to add a database to the broker configuration that already includes a database with the specified name. The database names must be unique.

Action: Verify that you have specified a unique name for the new database you wish to add. This can be done by checking that there is no database with the same name. Also note that the database name must match the DB_UNIQUE_NAME initialization parameter of the database.

ORA-16622: two or more broker database objects resolve to one physical database

Cause: The Data Guard broker determined that there were multiple database objects referring to the same physical database.

Action: Examine the details of all databases in the broker configuration and verify that there are not two or more databases that indicate the same physical database. If you detect this situation, remove and readd the erroneously defined database(s) to resolve the ambiguity.

ORA-16623: stale DRC UID sequence number detected

Cause: The Data Guard broker detected a stale sequence value during its bootstrap or health check operations. The sequence value is changed each time a switchover or failover operation completes successfully. A database that is unavailable to participate in the switchover or failover operation will end up with a stale sequence number. Should the database attempt to rejoin the broker configuration, the broker will determine that the database missed a role change and will disable its management of that database. The broker disables the database since it may no longer be a viable standby database for the new primary database.

Action: Examine the broker configuration for databases that were disabled and which may require re-creation..

ORA-16624: broker protocol version mismatch detected

Cause: The broker detected a network protocol version number mismatch. This can happen if the databases in question are not at the same version of Oracle. The broker will disable management of the databases that do not have the same network protocol version number as the primary database.

Action: Examine the version of Oracle installed for all databases to make sure they are identical. Once the Oracle versions are the same for all databases, reenable the databases that had been disabled.

ORA-16625: cannot reach the database

Cause: The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database.

Action: Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database.

ORA-16626: failed to enable specified object

Cause: The broker failed to enable management of an object (most likely a standby database). You can expect to see this status when attempting to enable broker management of a standby database that:

- cannot locate itself in the broker configuration file.

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

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

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

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

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

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

ORA-16627: operation disallowed since no standby databases would remain to support protection mode

Cause: This status is returned in the following situations:

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

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

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

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

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

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

- The broker returns this error during a health check.

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

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

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

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

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

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

ORA-16628: the broker protection mode is inconsistent with the database setting

Cause: The Data Guard broker protection mode saved in the broker"s configuration file was inconsistent with the actual database setting.

Action: Reset the protection mode through the Data Guard broker.

ORA-16629: database reports a different protection level from the protection mode

Cause: The actual protection level supported by the standby database was different from the protection mode set on the primary database. This was likely caused by redo transport problems.

Action: Check the database alert logs and Data Guard broker logs for more details. Check the redo transport status. Make sure at least one standby redo transport is supporting the protection mode and that the network to the standby database is working.

ORA-16630: that database property was deprecated

Cause: The property that was specified in the user operation was a deprecated property.

Action: Check the broker documentation to identify a replacement property or issue a SQL command to achieve the same result if no such replacement property exists.

ORA-16631: operation requires shutdown of database/instance "string"

Cause: The Data Guard broker operation requires a shutdown of the database or instance.

Action: If the client has not yet done so, please shutdown all Oracle instances for the database.

ORA-16632: instance being added to database profile

Cause: The Data Guard broker determined that an instance has successfully found its database profile within the broker configuration file, but yet lacks an instance-specific profile. The broker automatically creates an instance-specific profile and associates the instance with its database profile.

Action: No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance in broker activity.

ORA-16633: the only instance of the database cannot be removed

Cause: The instance to be removed was the only instance of the corresponding database that is known to the broker.

Action: Remove the corresponding database object from the broker configuration instead of that individual instance object of the database.

ORA-16635: NetSlave connection was broken in the middle of a transmission session

Cause: The Data Guard NetSlave process detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (e.g. the broker configuration file) to the remote database. This error implies the transmission has to be restarted from the beginning.

Action: In most cases, no user action is required. The Data Guard broker always tries to resend the data from the beginning. If the problem persists, the user will eventually see this error reported. This will indicate there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and address the actual problem.

Cause: A STOP OBSERVER operation could not be completed when Fast-Start Failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.

Action: Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps you identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. You may correct the problem that is indicated by that information and retry the operation. Alternatively, you may forcibly disable Fast-Start Failover while connected to the primary database using the DISABLE FAST_START FAILOVER FORCE command in the DGMGRL CLI. You can then stop the observer regardless of the current state of the target standby database.

Cause: When an instance was started, the DMON process on the instance failed to access the Data Guard broker configuration. This can happen if the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters are not set up correctly to point to the broker configuration files shared among all instances.

Action: Set DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 to the correct file specifications that point to the broker configuration files shared among all instances. Bounce the DMON process by setting DG_BROKER_START initialization parameter to FALSE and then to TRUE.

ORA-16638: could not get the instance status

Cause: The broker failed to check whether the given instance was alive or not.

Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.

ORA-16639: specified instance inactive or currently unavailable

Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable.

Action: Ensure that the instance specified in the operation is running and then retry the operation.

ORA-16640: CRS warns that multiple instances may still be running

Cause: A broker operation was underway that required CRS to stop monitoring the instances of this database and to shut down all but one instance. Although instance monitoring has ceased, CRS cannot guarantee that only one instance remains running. The broker operation was canceled.

Cause: The expected db_unique_name value did not match the actual db_unique_name value for the database that the broker contacted using the connect identifier that was associated with that database.

Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database that the broker expects to find via that connect identifier matches the actual db_unique_name for that database.

ORA-16643: unable to determine location of broker configuration files

Cause: The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.

Action: Retry the operation and if the error persists, contact Oracle Support Services.

ORA-16644: apply instance not available

Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.

Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.

ORA-16645: unexpected new instance interrupted current operation

Cause: A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically.

Action: Reissue the operation after the new instance has joined the Data Guard configuration.

ORA-16646: Fast-Start Failover is disabled

Cause: The operation was not allowed because Fast-Start Failover is disabled.

Action: Enable Fast-Start Failover and retry the operation.

ORA-16647: could not start more than one observer

Cause: The observer could not start because there was another observer already observing the Data Guard configuration for which Fast-Start Failover may have been enabled.

Action: Stop the running observer. Retry the operation.

ORA-16648: a new observer registered with identifier string

Cause: The observer is registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a Fast-Start Failover.

Action: None

ORA-16649: database will open after Data Guard broker has evaluated Fast-Start Failover status

Cause: The database is being opened while Fast-Start failover is enabled. The message indicates that the Data Guard broker will first determine if conditions are suitable for opening; that is, a Fast-Start failover did not occur while the database was unavailable.

Action: No action is normally required. The Data Guard broker will continue opening the database after determining a Fast-Start failover did not occur. If there is a chance that a Fast-Start Failover did occur, the database will remain in the mounted state and will not open. In this case, check the target standby to see if a role transition took place.

ORA-16650: command incompatible when Fast-Start Failover is enabled

Cause: An attempt was made to issue a command which is not permitted when Fast-Start Failover is enabled. The command was not issued using the Data Guard broker.

Action: The attempted command must be issued using the Data Guard broker.

ORA-16651: requirements not met for enabling Fast-Start Failover

Cause: The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met:

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

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

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

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

Action: Retry the attempted command after correcting the issue:

- Set the Data Guard configuration to MaxAvailability protection mode.

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

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

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

ORA-16652: Fast-Start Failover target standby database is disabled

Cause: The command to enable or disable Fast-Start Failover could not be completed because Data Guard broker management of the Fast-Start Failover target standby database is currently disabled.

Action: Enable broker management of the target standby database and reissue the command. If you are attempting to disable Fast-Start Failover when this error is reported, you may opt to disable Fast-Start Failover with the FORCE option. See the description for DGMGRL"s DISABLE FAST_START FAILOVER [FORCE] command for more information.

ORA-16653: failed to reinstate database

Cause: The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled.

Action: Additional information about this failure is recorded in the primary database"s and/or the specified database"s Data Guard broker log files. This information will be helpful in determining how to proceed.

ORA-16654: Fast-Start Failover is enabled

Cause: The attempted command was not allowed while Fast-Start Failover (FSFO) was enabled:

- The FastStartFailoverTarget property may not be modified.

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

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

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

- The FAILOVER IMMEDIATE command is not allowed.

Action: Disable Fast-Start Failover, using the FORCE option if required. Then retry the attempted command.

ORA-16655: specified target standby database invalid

Cause: The attempted command was not allowed because Fast-Start Failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database.

Action: Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, you may disable Fast-Start Failover. You may then retry the command while specifying the originally specified target standby database.

ORA-16656: higher DRC UID sequence number detected

Cause: The Data Guard broker detected a higher sequence value during its bootstrap or health check operations. The sequence value is changed each time switchover or failover completes successfully.

Action: Additional information about this failure is recorded in the Data Guard "broker log" files, one for the primary database and one for each standby database in the Data Guard configuration. This information will be helpful in determining how best to proceed from this failure.

ORA-16657: reinstatement of database in progress

Cause: Reinstatement of this database was in progress.

Action: No action is necessary.

ORA-16658: unobserved Fast-Start Failover configuration

Cause: The Fast-Start Failover configuration was currently unobserved so failover was disallowed.

Action: Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable Fast-Start Failover to allow a failover in the absence of the observer process.

ORA-16659: failover operation in progress

Cause: A primary database that restarted contacted a standby database that is being failed over to.

Action: Shutdown the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to Fast-Start Failover, restarting the primary database after failover is complete will allow it to be automatically reinstated as a standby database to the new primary database.

ORA-16660: FSFO operation attempted in absence of a broker configuration

Cause: An attempt was made to enable or disable Fast-Start Failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands.

Action: 1) An attempt to enable or disable (non-FORCE) Fast-Start Failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database"s DMON process from the primary"s DMON process. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) You may use the FORCE option to override Fast-Start Failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that FSFO is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other at a later point in time and if the state of Fast-Start Failover had been altered at the primary database in the meantime.

ORA-16661: the standby database needs to be reinstated

Cause: A switchover or failover operatione has caused this database to require reinstatement.

Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database.

ORA-16700: the standby database has diverged from the primary database

Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option.

Action: Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to.

ORA-16701: generic resource guard request failed

Cause: Request to modify or query the resource failed.

Action: Check the Data Guard broker log for the reason for the failure, and reissue the request.

ORA-16702: generic resource guard warning

Cause: A request to modify or query the resource resulted in a warning.

Action: Check the Data Guard broker log for the reason for the warning, and if necessary reissue the request.

ORA-16703: cannot set property while the database is enabled

Cause: An attempt was made to change a database property while the database was enabled.

Action: Disable broker management of the database first, then update the property and reenable the database.

ORA-16704: cannot modify a read-only property

Cause: An attempt was made to change a read-only property.

Action: The property is controlled internally by the Data Guard broker and cannot be modified.

ORA-16705: internal error in resource guard

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16706: no resource guard is available

Cause: No resource guard is available to service the request.

Action: Contact Oracle Support Services.

ORA-16707: the value of the property string is invalid, valid values are string

Cause: An invalid property value was entered while broker management of the database was disabled.

Cause: The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database.

Action: If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error.

ORA-16710: the resource guard is out of memory

Cause: The resource guard was unable to allocate memory while trying to service a request.

Action: Verify that the operation is valid for the database and then reissue the request.

ORA-16714: the value of property string is inconsistent with the database setting

Cause: The value of the specified configuration property is inconsistent with database in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property.

Action: Query property InconsistentProperties on the database to determine the inconsistent values. Reset the property to make it consistent with the database setting.