Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.

ORA-12701 CREATE DATABASE character set is not known

Cause: The character set specified in the CREATE DATABASE command does not exist on the system.

Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.

ORA-12702 invalid NLS parameter string used in SQL function

Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.

Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.

ORA-12703 this character set conversion is not supported

Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.

Action: Use character sets available on the system in the CONVERT function.

ORA-12704 character set mismatch

Cause: One of the following:

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

An NLSPARAMS operand is not in the database character set.

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

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

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

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

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

Action: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.

ORA-12705 invalid or unknown NLS parameter value specified

Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.

Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.

ORA-12706 this CREATE DATABASE character set is not allowed

Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.

Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.

ORA-12707 error while getting create database NLS parameter string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-12708 error while loading create database NLS parameter string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-12709 error while loading create database character set

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-12710 CREATE CONTROLFILE character set is not known

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

Action: Specify a known character set.

ORA-12711 this CREATE CONTROLFILE character set is not allowed

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

Action: Create the correct control file for machine and character set.

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

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

Action: Specify a superset character set.

ORA-12713 Character data loss in NCHAR/CHAR conversion

Cause: When character set conversion 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 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 export/import.

ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists

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

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

ORA-12718 operation requires connection as SYS

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

Action: Connect as user 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-12800 system appears too busy for parallel query execution

Cause: Load on the system is too high to perform parallel queries.

Action: Re-execute serially or wait until the system load is reduced.

ORA-12801 error signaled in parallel query server string

Cause: A parallel query server reached an exception condition.

Action: Check the following error message for the cause.

ORA-12802 parallel query server lost contact with coordinator

Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.

Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.

ORA-12803 parallel query server lost contact with another server

Cause: A parallel query server lost contact with another server.

Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.

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.

Cause: A parallel statement failed because all ITLS in the current block are occupied by siblings of the same transaction.

Action: Increase the value of MAXTRANS of the block or reduce the degree of parallelism for the statement. Re-execute the statement. Report suspicious events in the trace file to Oracle Support Services if the 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 successfully 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.

Action: Re-define 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 User's Guide and Reference 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 the 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, 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, Y, or both.

Cause: Another error will accompany this message that will indicate the problem.

Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.

ORA-13040 failed to subdivide tile

Cause: This is an internal error.

Action: Note any accompanying errors and contact Oracle Support Services.

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

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

Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which 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.

Cause: An error was encountered reading the layer meta data 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, then contact Oracle Support Services.

ORA-13044 the specified tile size exceeds the maximum resolution

Cause: The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data.

Action: See the Oracle Spatial User's Guide and Reference 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 lesser 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 was specified for an SDO_GEOM function.

Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.

Action: Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Retry the operation.

ORA-13048 recursive SQL fetch error

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13049 unable to determine tolerance value from table layer_SDODIM

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

Action: Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE.

ORA-13050 unable to construct spatial object

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13051 failed to initialize spatial object

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13052 unsupported geometric type for geometry string.string

Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge.

Action: Check the Oracle Spatial User's Guide and Reference 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 User's Guide and Reference 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 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. Retry the operation.

ORA-13108 spatial table string not found

Cause: The specified spatial table does not exist.

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

Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, such as: 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: Document messages and contact Oracle Support Services.

ORA-13145 failed to generate range list

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

ORA-13146 could not find table substitution variable string

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

Action: The substitution variable string 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: Document messages and contact Oracle Support Services.

ORA-13148 failed to generate SQL filter

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

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

Cause: This is an internal error.

Action: Document messages and 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 insert a record into the exception table.

Action: Fix any other errors reported.

ORA-13152 invalid HHCODE type

Cause: The 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 highwater mark must be greater than or equal to zero.

Action: Make sure that the highwater 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 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 procedure. If the procedure does not return any errors, then note any accompanying errors and contact Oracle Support Services.

ORA-13213 failed to generate spatial index for window object

Cause: Another error, indicating the real cause of the problem, should accompany this error.

Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.

ORA-13214 failed to compute supercell for window object

Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.

Cause: An add_index parameter is 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 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. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which 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: Re-define the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial User's Guide and Reference 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: 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: A Spatial function with unit parameter is 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: A Spatial function is called with two geometries with two 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: 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 Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or latitude/longitude plus measure).

ORA-13332 invalid LRS point

Cause: Given 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 additional measure dimension.

ORA-13333 invalid LRS measure

Cause: The given measure for linear referencing was out of range.

Action: Re-define the given measure.

ORA-13334 LRS segments not connected

Cause: The given geometric segments were 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 given geometric segments 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).

Cause: No room for measure dimension in the given diminfo or the given standard geometry is not a point a linestring.

Action: Check if the diminfo dimensions are less than 3 or given geometry type is point or linestring.

ORA-13337 failure in concatenating LRS polygons

Cause: LRS concatenation involving LRS polygons is not supported.

Action: Check geometry and element type to make sure the concatenate operation is not called with a polygon type.

ORA-13338 failure in reversing LRS polygon/collection geometry

Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry as this operation is not well defined for polygon geometry.

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

ORA-13339 LRS Polygon clipping across multiple rings

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

Action: Polygon clipping only allowed 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, then set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, then remove the extraneous coordinates from its definition.

ORA-13341 a line geometry has less than two coordinates

Cause: A geometry, specified as being a line, has less 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 less than three coordinates

Cause: A geometry, specified as being an arc, has less 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 less than four coordinates

Cause: A geometry, specified as being a polygon, has less 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 less than five coordinates

Cause: A geometry, specified as being an arcpolygon, has less than six 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 less than five coordinates

Cause: A geometry, specified as being a compound polygon, has less 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 or 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, ensuring 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 description 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 description 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 SDO_GEOMETRY 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 SDO_GEOMETRY 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 2 points: lower left and upper right.

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

ORA-13358 circle type does not contain 3 points

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

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

ORA-13359 extent does not have an area

Cause: The 2 points representing the extent are identical.

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

Action: Verify that the format version is supported or the format is valid.

ORA-13462 invalid tie point

Cause: One of the tie points is invalid.

Action: Verify that the tie points used are valid (for example all raster tie points are >= 0).

ORA-13463 unsupported GeoTIFF geometry definition

Cause: The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported.

Action: Verify that the GeoTIFF format version is supported and the format is valid.

ORA-13464 unsupported conversion

Cause: The format specified for conversion is not supported. In GeoTIFF, only a limited number of tags/keys combinations are supported for conversion.

Action: Verify that the GeoTIFF format version is supported and conversion to the desired format is available.

ORA-13465 invalid destination window

Cause: The window specified as destination in the command is not valid.

Action: Verify that the window definition is correct.

ORA-14000 only one LOCAL clause may be specified

Cause: CREATE INDEX statement contained more than one LOCAL clause.

Action: Specify LOCAL option at most once.

ORA-14001 LOCAL clause contradicts previosly specified GLOBAL clause

Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause.

Action: Specify LOCAL or GLOBAL clause, but not both.

ORA-14002 only one GLOBAL clause may be specified

Cause: CREATE INDEX statement contained more than one GLOBAL clause.

Action: Specify GLOBAL option at most once.

ORA-14003 GLOBAL clause contradicts previosly specified LOCAL clause

Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause.

Action: Specify GLOBAL or LOCAL clause, but not both.

ORA-14004 missing PARTITION keyword

Cause: Keyword PARTITION missing.

Action: Supply missing keyword.

ORA-14005 missing RANGE keyword

Cause: Keyword RANGE missing.

Action: Supply missing keyword.

ORA-14006 invalid partition name

Cause: A partition name of the form identifier is expected but not present.

Action: Enter an appropriate partition name.

ORA-14007 missing LESS keyword

Cause: Keyword LESS missing.

Action: Supply missing keyword.

ORA-14008 missing THAN keyword

Cause: Keyword THAN missing.

Action: Supply missing keyword.

ORA-14009 partition bound may not be specified for a LOCAL index partition

Cause: While parsing a CREATE INDEX statement to create a LOCAL partitioned index, partition_description of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table.

Action: Remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions.

ORA-14010 this physical attribute may not be specified for an index partition

Cause: Unexpected option was encountered while parsing physical attributes of an index partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for hash partitions.

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

ORA-14011 names assigned to resulting partitions must be distinct

Cause: Names of partitions resulting from splitting of an existing table or index partition are not distinct.

Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.

ORA-14012 resulting partition name conflicts with that of an existing partition

Cause: Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index.

Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.

ORA-14013 duplicate partition name

Cause: Name of a partition of a table or index being created is not unique.

Action: Rename partition(s) to ensure that their names are unique among partitions of the table or index being created.

ORA-14014 maximum number of partitioning columns is 16

Cause: Number of columns in a partitioning column list exceeded the legal limit of 16.

Action: Modify partitioning column list so that it consists of at most 16 columns.

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

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

Cause: Unexpected option was encountered while parsing physical attributes of a table partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for hash partitions.

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

ORA-14021 MAXVALUE must be specified for all columns

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

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

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

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

Action: Remove LOCAL along with partition_descriptions, if any, from the CREATE INDEX statement.

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

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

Action: Remove PARTITION BY RANGE clause along with partition_descriptions from the CREATE INDEX statement.

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

Cause: An attempt was made 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 is missing.

Action: Supply missing keyword.

ORA-14029 GLOBAL partitioned index must be prefixed

Cause: The partitioning columns of a global partitioned index did not contain a prefix of the index's key columns.

Action: Ensure that the GLOBAL partitioned index being created is prefixed and retry the operation.

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: An attempt was made to create a GLOBAL non-prefixed partitioned index which is illegal.

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

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

Cause: An attempt was made to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal.

Action: If you want 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's 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: The ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.

Action: Ensure that a partition maintenance operation is the sole operation specified in an 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) can be combined.

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: An attempt was made to use partition-extended table name syntax in illegal context (that is, 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 (for example, 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 the value of INITRANS (whether specified explicitly 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 the value of INITRANS (whether specified explicitly 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 aforementioned 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: An attempt was made 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 index-organized table, 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 options from the command.

ORA-14067 duplicate TABLESPACE_NUMBER specification

Cause: TABLESPACE_NUMBER clause was specified more than once for a table, an 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, an 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 statement 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: An attempt was made 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: An attempt was made 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: An attempt was made 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 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: An attempt was made to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal.

Action: Re-enter the statement without TABLESPACE DEFAULT clause.

ORA-14085 partitioned table cannot have column with LONG datatype

Cause: An attempt was made 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: An attempt was made 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 re-create 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} INDEXES][{WITH|WITHOUT} VALIDATION].

Action: Ensure that no options besides INCLUDING INDEXES or EXCLUDING INDEXES are specified with ALTER TABLE EXCHANGE PARTITION.

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size.

Action: Ensure that the two tables have the same number of columns with the same type and size.

ORA-14098 index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

Cause: The two tables specified in the EXCHANGE have indexes which are not equivalent.

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

ORA-14099 all rows in table do not qualify for specified partition

Cause: There is at least one row in the non-partitioned table which does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION.

Action: Ensure that all the rows in the segment qualify for the partition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them.

Cause: An attempt was made to use partition-extended table name syntax in conjunction with remote object name which is illegal.

Action: Correct the statement and re-enter it.

ORA-14101 partition extended table name cannot refer to a synonym

Cause: An attempt was made to use partition-extended table name syntax in conjunction with synonym name which is illegal.

Action: Correct the statement and re-enter it.

ORA-14102 only one LOGGING or NOLOGGING clause may be specified

Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.

Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.

ORA-14103 LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE

Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed.

Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.

ORA-14104 RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices

Cause: CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal.

Action: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.

ORA-14105 RECOVERABLE/UNRECOVERABLE may not be specified in this context

Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.

Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.

ORA-14106 LOGGING/NOLOGGING may not be specified for a clustered table

Cause: An attempt was made to specify LOGGING or NOLOGGING clause in CREATE TABLE or ALTER TABLE statement involving a clustered table.

Action: Remove offending clause.

ORA-14107 partition specification is required for a partitioned object

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

Action: Supply the missing parameter.

ORA-14108 illegal partition-extended table name syntax

Cause: Partition to be accessed may only be specified using its name. An attempt was made to use a partition number or a bind variable.

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

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

Cause: An attempt was made 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 GLOBAL partitioned indices 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() clause along with (partition_list) 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: An attempt was made 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: An attempt was made to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table.

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

ORA-14115 partition bound of partition number string is too long

Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K).

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

ORA-14116 partition bound of partition "string" is too long

Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K).

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

ORA-14117 partition resides in offlined tablespace

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

Action: Bring the tablespace online before attempting the operation.

ORA-14118 CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them.

Action: Ensure that the two tables do not have CHECK constraint defined on any column.

ORA-14119 specified partition bound is too long

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

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

ORA-14120 incompletely specified partition bound for a DATE column

Cause: An attempt was made to use a date expression whose format does not fully (that is, 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 (that is, day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (that is, including the century) specification of the year, use TO_DATE() (for example, 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 (for example, 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 65535 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: Expected either the PARTITION or SUBPARTITION keyword but neither was supplied.

Cause: Name of a subpartition of a table or index being created is not unique.

Action: Rename the 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: An unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option.

Action: Remove the 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: The 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: The 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: An ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (for example, 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 the 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 a table 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 table which is hash or composite partitioned

Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a table which is range or list partitioned.

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

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

Cause: An attempt was made to specify TABLESPACE DEFAULT for a partition of a range/system/hash-partitioned LOCAL index object, which is illegal.

Cause: An unexpected option was encountered while parsing physical attributes of a local index partition; valid options for range 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 the 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: An attempt was made to create a LOCAL partitioned index with a number of subpartitions which is different from that of the underlying table.

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

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

Cause: An attempt was made to create a LOCAL partitioned index that is not equipartitioned with the underlying table. The partitioning types are mismatched.

Action: Correct the CREATE INDEX statement to ensure that the index partitioning 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: An attempt was made to create a UNIQUE partitioned index whose subpartitioning columns do not form a subset of its key columns which is illegal.

Action: If you want 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's subpartitioning columns form a subset of its key columns.

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

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

Action: Remove the invalid option(s).

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

Cause: One of the following:

ENABLE ROW MOVEMENT was specified more than once.

DISABLE ROW MOVEMENT was specified more than once.

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 and 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 or 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.

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 aforementioned 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 partitioned table

Cause: A COALESCE PARTITION command was issued when there is only one partition in the table which is illegal.

Action: Ensure that there is at least one partition. Drop table 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: Descriptions of partitions or subpartitions in an ALTER TABLE ADD COLUMN statement were ordered differently from the DDL order of partitions or subpartitions.

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 DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operations.

ORA-14321 cannot add/drop values to DEFAULT partition

Cause: An ADD/DROP VALUES operation is being performed on the default partition.

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

ORA-14322 DEFAULT partition already exists

Cause: A partition already exists with DEFAULT value.

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

Action: No action required.

ORA-14404 partitioned table contains partitions in a different tablespace

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

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

ORA-14405 partitioned index contains partitions in a different tablespace

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

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

ORA-14406 updated partition key is beyond highest legal partition key

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

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

ORA-14407 partitioned table contains subpartitions in a different tablespace

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

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

ORA-14408 partitioned index contains subpartitions in a different tablespace

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

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

ORA-14409 inserted partition key is outside specified subpartition

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

Action: Do not insert the key or insert it in another subpartition.

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

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

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

ORA-14451 unsupported feature with temporary table

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

Action: No action required.

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 already been 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 committed 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 TEMPLATEs can only be specified for composite partitioned tables.

Action: Do not use SUBPARTITION TEMPLATEs 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.

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 indexes defined on it or is referenced by a constraint.

Action: Bring the 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 are the same as the bounds of the subpartitions in 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, then perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.

ORA-14644 table is not subpartitioned by Hash method

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

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

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

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

Action: Re-issue the command after removing the STORE IN clause.

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 reopened for read-write access.

ORA-16001 database already open for read-only access by another instance

Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.

Action: This instance must be opened for read-write access, or all other instances must first be shut down and reopened for read-only access.

ORA-16002 database 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 reopened 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: reissue 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 a 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 a 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-16010 remote archive log destination database is opened for update

Cause: The database associated with the archive log destination service name is opened for update access. Remote archival of redo log files to standby databases opened for update access is not allowed.

Action: Shut down the standby destination instance and re-open for read-only access or simply leave the standby instance mounted and unopened.

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 LOG_ARCHIVE_DUPLEX_DEST parameter was set to a non-NULL value when the primary archive destination was explicitly set to NULL.

Action: Set the primary archive destination to a valid non-NULL value.

ORA-16018 cannot use string with LOG_ARCHIVE_DEST_n

Cause: One of the following events caused an incompatibility:

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST initialization parameter was in use when a LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) was encountered while fetching initialization parameters.

An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.

A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM statement was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter.

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:

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST initialization parameter was in use when the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) was encountered while fetching initialization parameters.

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST initialization parameter was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION statement to define a value for the specified LOG_ARCHIVE_DEST_n parameter.

An ALTER SYSTEM ARCHIVE LOG START TO statement was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.

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 the LOG_ARCHIVE_DEST initialization parameter to NULL when the LOG_ARCHIVE_DUPLEX_DEST initialization parameter is non-NULL.

Action: Either set the LOG_ARCHIVE_DEST initialization parameter to a non-NULL value, or set the LOG_ARCHIVE_DUPLEX_DEST initialization parameter 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 parameter (n = 1, 2, ... 10) 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 statement. 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 parameter (n = 1, 2, ... 10) 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.

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 parameter (n = 1, 2, ... 10) failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attribute.

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, 2, ... 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 the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.

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

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 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 parent archive log destination cannot be a standby database. It must be a local archive log destination.

Action: Change the parent archive log destination from referencing a standby database to referencing a local archive log repository.

ORA-16048 enable simulated error on archive log write

Cause: Causes an I/O error to be signalled during the writing of an archival operation.

Action: No action required.

ORA-16049 simulated error on archive log write

Cause: I/O error returned for a simulated archival failure during an archival operation.

Action: No action required.

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.

Cause: A gap sequence is detected on the standby database while it was trying to perform managed standby recovery. The fetching of the gap sequence fails. The failures are logged in the alert log on the primary database.

Action: Check the alert log on primary and standby database. Take appropriate action to make the gap sequence available again. Managed standby recovery on the standby database cannot proceed further until the standby database is able to get the gap sequence redo log files.

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

ORA-16069 Archive Log standby database activation identifier mismatch

Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

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 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 statement 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 statement 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 statement 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: No action 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.

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 Oracle9i SQL Reference 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 LOGFILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this statement.

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.

Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.

Action: No action required; 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 required; 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 required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16113 applying change to table or sequence object number string

Cause: The process is applying changes to a specific schema object.

Action: No action required; 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 required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16115 loading Log Miner dictionary data

Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.

Action: No action required; 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 required; 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 required; 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 required; 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 required; 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 required; 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 required; 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 required; 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 required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16125 large transaction stringstringstring is waiting on another transaction

Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16126 loading table or sequence object number string

Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.

Action: No action required; 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 required; this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, then increase available SGA or the number of apply processes.

ORA-16128 User initiated shut down successfully completed

Cause: Logical standby was shutdown in an orderly fashion.

Action: No action required; 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 the RECOVER MANAGED STANDBY DATABASE statement.

Cause: A terminal recovery (initiated by the RECOVER MANAGED STANDBY FINISH command) could not find the current log for the requested thread and sequence.

Action: Check that the standby current logs are in the correct location.

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

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 required. 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, re-issue the graceful switchover command.

ORA-16140 standby online logs have not been recovered

Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.

Action: To recover the standby online logs issue the following command:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;

Then re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE statement. To activate the standby without recovering the online logs, issue the following command:

ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE;

ORA-16143 RFS connections not allowed during or after terminal recovery

Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.

Action: The primary must not attempt to archive to the standby after a terminal recovery.

ORA-16145 archival for thread# string sequence# string in progress

Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived.

Action: Verify that archival of the indicated log file has completed and re-issue the RECOVER STANDBY DATABASE command.

ORA-16146 standby destination control file enqueue unavailable

Cause: The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.

Action: Check for and eliminate the standby destination archive log parameter in question.

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 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 re-issue the statement.

ORA-16154 suspect attribute: string

Cause: Use of the indicated attribute is illegal in the given context.

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

ORA-16160 Cannot change protected standby database configuration

Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16161 Cannot mix standby and online redo log file members for group string

Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.

Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.

ORA-16162 Cannot add new standby databases to protected configuration

Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16163 LGWR network server host attach error

Cause: The LGWR network server could not attach to remote host.

Action: The alert log contains more problem-specific information.

ORA-16164 LGWR network server host detach error

Cause: The LGWR network server could not detach from remote host.

Action: The alert log contains more problem-specific information.

ORA-16165 LGWR failed to hear from network server

Cause: The LGWR lost its connection to the network server.

Action: The alert log contains more problem-specific information.

ORA-16166 LGWR network server failed to send remote message

Cause: The LGWR network server could not communicate with the remote host.

Action: The alert log contains more problem-specific information.

ORA-16167 LGWR network server could not switch to non-blocking mode

Cause: The LGWR network server could not switch to non-blocking mode.

Action: The alert log contains more problem-specific information.

ORA-16168 LGWR network server could not switch to blocking mode

Cause: The LGWR network server could not switch to blocking mode.

Action: The alert log contains more problem-specific information.

ORA-16169 LGWR network server invalid parameters

Cause: The LGWR network server could not switch to blocking mode.

Action: The alert log contains more problem-specific information.

ORA-16170 Parallel terminal recovery may lose more data than necessary

Cause: Serial terminal recovery can always recover the standby database to the last consistent point in the redo stream. Parallel terminal recovery cannot.

Action: Retry with serial terminal recovery.

ORA-16171 RECOVER...FINISH not allowed due to gap for the 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, then issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP statement 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 to the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.

ORA-16173 incompatible archival network connections active

Cause: One of two situations can cause this error:

An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected.

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.

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, then 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, then check the trace file for the mentioned process until the root message is found.

ORA-16210 Logical standby coordinator process terminated with error

Cause: The logical standby coordinator process terminated abnormally.

Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then 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:

Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it's unimportant.

ALTER DATABASE START LOGICAL STANDBY APPLY;

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

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

Cause: The broker will return this error for switchover operations and for resource state change operations. If this error is returned for a switchover operation, then the broker has determined that either:

The sites changing roles are offline.

The primary database is not shipping log files.

The standby database that will become the primary is not applying log files.

The broker returns this error for resource state change operations if the resource state specified is invalid for the resource.

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

The sites 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 resource state change operation, then make sure you specify a valid state for the resource.

ORA-16517 the object handle is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16518 unable to allocate virtual instance id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16519 the resource handle is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16520 unable to allocate resource id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16521 unable to create generic template id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16522 generic template not found

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16523 property count exhausted

Cause: Total number of resource properties exceeded the limit.

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, then set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, then 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: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16530 invalid buffer or length

Cause: A NULL buffer or a length of zero was specified.

Action: Correct command parameters and retry.

ORA-16531 unable to post message

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16532 Data Guard configuration does not exist

Cause: The Data Guard configuration does not exist.

Action: Create a DRC prior to issuing other requests.

ORA-16533 inconsistent Data Guard broker state

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16534 no more requests accepted

Cause: The Data Guard broker returns this status when:

A failover operation has been submitted or is currently in progress

A switchover operation has been submitted or is currently in progress

An instance restart is pending for one or more sites

Action: Wait until the operation is complete and then re-issue the request.

ORA-16535 failover request rejected

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16536 unknown object type

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16537 child count exceeded

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16538 no match on requested item

Cause: The Data Guard broker did not recognize the specified property or state name.

Action: Verify command parameters and re-issue the request.

ORA-16539 task element not found

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16540 invalid argument

Cause: One of the arguments for the specified request is invalid for the request type. In the case of failover, the failover level must be specified. That is, a graceful failover or a forced failover.

Action: Verify arguments and then re-issue the request.

ORA-16541 site is not enabled

Cause: The site specified in the request is not enabled.

Action: Select an enabled site and re-issue the request.

ORA-16542 unrecognized operation

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16543 invalid request made to broker

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16544 unable to make request

Cause: The Data Guard broker was unable to accept the request.

Action: Contact Oracle Support Services.

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

Action: Specify the piece of the response starting from 1.

ORA-16547 unable to delete request

Cause: The Data Guard broker was unable to delete the given request.

Action: Contact Oracle Support Services.

ORA-16548 the resource is not enabled

Cause: An attempt was made to modify or query a disabled Data Guard resource. This error is also returned on an attempt to enable, modify, or query a resource that the broker has permanently disabled. A permanently disabled resource cannot be re-enabled. The broker permanently disables site resources when it detects that the database on that site needs to be reinstantiated. The broker also permanently disables sites that lag behind in terms of DRC Unique ID sequence value.

Action: If the resource is not permanently disabled, enable the resource and re-issue the request.

ORA-16549 invalid string

Cause: A request contains 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 recieve buffer.

ORA-16551 short string copied

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16552 the Data Guard broker process (DMON) failed to start

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16553 the Data Guard broker process (DMON) failed to shutdown

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16554 translation not valid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16555 the Data Guard resource is not active

Cause: An operation was attempted on a resource that is currently not active (off path).

Action: Verify that the resource is active.

ORA-16557 the resource is already in use

Cause: An attempt was made to create a duplicate resource.

Action: Check the resource to be added and be sure there are no duplicates.

ORA-16558 the site specified for switchover is not a standby

Cause: An attempt was made to switchover to a site that is not a standby site.

Action: Locate an enabled standby site and select that site as the target of the switchover.

ORA-16559 out of memory at string

Cause: This is an 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 resubmit the request.

ORA-16561 must use ONLINE parent state, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

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 resubmit the request.

ORA-16563 unable to add value, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16564 lookup failed, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16565 duplicate property, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16566 unsupported document type

Cause: The submitted XML document is not supported.

Action: Correct the errors and resubmit the request.

ORA-16567 Data Guard broker internal parser error at "string"

Cause: This is an 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 requires the Data Guard configuration to be enabled.

Action: Enable the Data Guard configuration and re-issue the request.

ORA-16570 Operation requires restart of site "string"

Cause: Some Data Guard broker operations require the given site to be shut down and restarted.

Action: If the client has not already done so, then shut down the Oracle instance at the given site 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] parameter and retry.

ORA-16572 Data Guard configuration file not found

Cause: The Data Guard broker configuration file is either unavailable or does not exist.

Action: Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1 | 2] parameter was changed, then ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.

ORA-16573 attempt to change configuration file in an enabled DRC

Cause: An attempt was made to change the Data Guard broker configuration file parameter while a DRC was enabled.

Action: Disable the configuration and shut down the Data Guard broker before changing this value. Also be sure to rename the file at the operating system level.

Action: Check the states of the configuration, primary site, primary database resource, standby site, and standby database resource. 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: No action required.

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.

Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.

Action: Contact Oracle Support Services.

ORA-16596 site is not a member of the Data Guard configuration

Cause: A request was made on a site that is not a member of the Data Guard configuration.

Action: Re-issue the request on a site that is a part of the configuration.

ORA-16597 Data Guard broker detects two or more primaries

Cause: The Data Guard broker has detected two or more primaries in the configuration and cannot continue.

Action: Contact Oracle Support Services.

ORA-16598 The Data Guard broker has detected a mismatch in configuration

Cause: The Data Guard broker on this site has detected a mismatch in configuration generation. This can occur when the primary site has a stale configuration.

Action: Contact Oracle Support Services.

ORA-16599 The Data Guard broker has detected a stale configuration

Cause: The Data Guard broker has detected a stale configuration during initialization on this site.

Action: The broker will automatically resolve this situation once the primary site completes its initialization.

ORA-16600 Failover operation can only be submitted on target site

Cause: This error is returned when a failover request specifies a different site than the site the client is currently connected to.

Action: Explicitly connect to the site you wish to failover to and re-issue 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 re-issue the request.

ORA-16602 resource must be disabled to perform this operation

Cause: An attempt was made to modify a resource that can only be changed while that resource is disabled.

Action: Disable the resource and re-issue the request.

ORA-16603 Data Guard broker detected mismatch in configuration ID

Cause: The Data Guard broker on this site has detected a mismatch in configuration Unique ID. This can occur if the original configuration was re-created while this site was disconnected from the network or the same site was added to two different configurations.

Action: Make sure the site belongs to only one configuration. Remove Data Guard broker configuration files and restart the server.

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 site. 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 re-issue the request.

ORA-16607 one or more sites have failed

Cause: The Data Guard broker detected a failure on one or more sites.

Action: Locate the sites with a failure status and correct it.

ORA-16608 one or more sites have warnings

Cause: The Data Guard broker detected a warning status on one or more sites.

Action: Locate the sites with a warning status and correct it.

ORA-16609 one or more resources have failed

Cause: The Data Guard Broker detected a failure on one or more resources on a site.

Action: Locate the resources with a failure status and correct it.

ORA-16610 one or more resources have warnings

Cause: The Data Guard broker detected a warning status on one or more resources on a site.

Action: Locate the resources 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 site

Cause: The site received a directive to change its initialization state or a change in its configuration before it has completed initialization.

Action: Wait until the site 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 server. The Data Guard broker has enabled 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 returns this error when the object identifier specified in the request is invalid or unknown. For example, this error is returned if an invalid or unknown site object identifier is specified in a request that requires a site object identifier.

Action: Verify that a valid object identifier was specified in the request and then re-issue 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 console log.

Action: View the console log on the given site directly.

ORA-16619 Health Check timed out

Cause: This status is returned when the Data Guard broker could not reach a standby site during routine health check.

Action: This typically indicates a network problem where the standby site is unable to respond to the primary within the predefined time frame.

ORA-16620 one or more sites could not be contacted for a delete operation

Cause: This status is returned when the Data Guard broker could not reach one or more standby sites for either a delete site or a delete configuration operation.

Action: This typically indicates a network problem where the standby site is unable to respond to the primary. In the event of this situation, examine the Data Guard broker log file on the primary site to determine which standby sites could not be reached. Then for each standby site not reached, connect to that site and shut down the broker by setting the DG_BROKER_START initialization parameter to false. After the broker has been shut down on the standby site, locate the Data Guard broker configuration files from the standby site's DG_BROKER_CONFIG_FILE[1 | 2] parameter values and delete them.

ORA-16621 host and SID names for create site must be unique

Cause: This status is returned when an attempt is made to add a site whose host and SID names match those of an existing site.

Action: Verify that you have specified a unique host and SID name pair for the new site you wish to add. This can be done by checking that there are no sites with the same host and SID names.

ORA-16622 two or more Broker sites resolve to the same physical site

Cause: This status is returned when the Broker determines that there are multiple site objects referring to the same physical or material site.

Action: Examine the host names, SID names, and connect descriptors of all sites in the configuration and verify that there are not two or more sites that refer to the same physical site. If you detect this situation, then correct the site definition to eliminate the ambiguity.

ORA-16623 stale DRC UID sequence number detected

Cause: This status is returned when the Broker detects a stale sequence value during bootstrap or during health check. The sequence value is changed each time a role change occurs. A site that is unavailable for the role change operation will end up with a stale sequence number. Should that site attempt to rejoin the configuration, the broker will determine that it missed a role change and disable that site. The broker permanently disables the site since it may no longer be a viable standby site for the new primary.

Action: Examine the configuration and the sites that were permanently disabled to determine if they require manual intervention.

ORA-16624 broker protocol version mismatch detected

Cause: This status is returned when the Broker detects a network protocol version number mismatch. This can happen if the sites in question are not running the same release of Oracle. The broker will permanently disable the sites that do not have the same network protocol version number as the primary.

Action: Examine the release of Oracle installed on all sites to make sure they are identical. Once the Oracle releases are the same on all sites, delete and re-add the sites that were permanently disabled.

ORA-16625 cannot reach the primary site

Cause: This status is returned when the Broker rejects a write operation requested by the client when the primary site is not reachable from the site the request is made. All write operations made to the DataGuard configuration must be processed by the primary site.

Action: Check your network connection from the site your client is connected to, to the primary site. Alternatively, you can connect your client to a different site in the DataGuard Configuration and try your request again.

ORA-16626 failed to enable specified object

Cause: This status is returned when the broker fails to enable an object (most typically a standby site). You can expect to see this status when attempting to enable a standby site that:

Cannot locate itself in the configuration

Fails to distiguish itself from two or more site objects in the configuration

Determines it was not part of a change of primary due to failover

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

Confirm that the host and SID names you specified when you created the site exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.

Confirm that you have not created two or more sites with the same connect descriptor. That is, the site objects should not lead you to the same material site.

If you had performed a failover and have re-instantiated your old primary site (or standby site that had to be reinstantiated), then make sure the Data Guard Broker configuration files have been removed from that site. Do NOT remove the configuration files that are in use by the new primary.

ORA-16627 no standby databases support overall 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, managed standby databases that support the proposed protection mode.

The Broker rejects an attempt to enable the configuration if it determines that there are no online managed standby databases that support the overall protection mode.

The Broker rejects an attempt to disable or delete a site or database resource, that if disabled or deleted, would result in no standby databases that 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 site or 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, then 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 the 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 and a single standby, then ensure that the LogXptMode configuration property established for the primary site supports the overall protection mode. After the switchover the old primary will become the standby 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

ORA-16629 database reports a different protection level from the protection mode

Cause: The actual protection level supported by the standby database is different from the protection mode set on the primary. This is likely caused by the log transport problems.

Action: Check the database alert logs and Data Guard Broker console logs for more details. Check the log transport status. Make sure at least one standby log transport is supporting the protection mode and that the network to the standby has no problems.

ORA-16701 generic resource guard request failed

Cause: Request to modify or query the resource failed.

Action: Check the Data Guard console log for the reason for the failure, and re-issue the request.

ORA-16702 generic resource manager warning

Cause: Request to modify or query the resource resulted in a warning.

Action: Check the console log for the reason for the warning, and re-issue the request if necessary.

ORA-16703 status of request is unknown

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16704 a previous set state operation is pending

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16705 severe internal error in resource guard

Cause: This is an 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 supplied to resource guard is invalid

Cause: The value specified in the request is invalid.

Action: Check value and re-issue the request.

ORA-16708 the state supplied to resource guard is invalid

Cause: The state name specified is invalid for the resource.

Action: Check the state name and re-issue the request.

ORA-16709 the resource guard is busy and cannot service the request

Cause: Request to resource guard failed because the guard is busy.

Action: Wait for resource guard to finish previous request and then re-issue the request.

ORA-16710 the resource guard is out of memory

Cause: The resource guard was unable to allocate memory while trying to service a request.

ORA-16777 Unable to find the destination entry of a site in V$ARCHIVE_DEST

Cause: Some destination may be manually deleted, or no entry is available for Data Guard.

Action: Check the Data Guard console log and Oracle Alert log for further details. One may need to reset log transport service.

ORA-16778 The log transport service for some site has an error

Cause: Some problem in communicating with a standby site causes the log transport to fail.

Action: Check the Data Guard console log and Oracle Alert log for further details. Query the LogXptStatus property to see the error message.

ORA-16779 The destination parameter of some site has wrong syntax

Cause: The destination is defined in the initialization parameter file with wrong syntax, and the Data Guard broker fails to update the destination when the log transport is turned on.

Action: Check the Data Guard console log to see which site has the problem. Fix the syntax error in the initialization parameter file or remove the entry. Check if the syntax of the log transport related properties are correct.

ORA-16780 Some site has used up its quota

Cause: Some site has used up its quota for storing archived redo logs.

Action: Check the Data Guard console log to see which site has the problem. Remove some archived logs at the standby site or increase its quota.

ORA-16781 The status of log transport service for some site is unknown

Cause: The Data Guard broker configuration files do not exist or the resource guard cannot access the Data Guard metadata.

Action: Check the Data Guard console log for further details.

ORA-16788 Unable to set one or more database configuration property values

Cause: This situation occurs when database resource guard attempts to set database configuration property values into the database by issuing ALTER SYSTEM or ALTER DATABASE statements. Typical causes of this error are:

The values of log transport related properties have syntax errors

The Value of LogArchiveTrace is out of range

Database initialization parameter STANDBY_FILE_MANAGEMENT cannot be set to AUTO because the database compatability is not set to 9.0.0.0.0 or higher.

Action: Check the Data Guard console log to see which property has the problem and reset the property correctly.

Cause: The database may not be mounted, or the query of V$STANDBY_LOG failed.

Action: Bring the database to an online state, or fix the problem during the query of V$STANDBY_LOG.

ORA-16792 Some configurable property value is inconsistent with the database setting

Cause: The values of one or more configurable properties are inconsistent with database in-memory settings or SPFILE settings. This may be caused by a user operation on database outside of the Data Guard broker control.

Action: Query property InconsistentProperties on the site or check the Data Guard console log to find which properties are inconsistent. Reset these properties to make them consistent with the database settings.

ORA-16793 Logical Standby Database Guard is unexpectedly OFF

Cause: The logical standby database guard is OFF.

Action: Issue the ALTER DATABASE GUARD ALL statement to turn the guard ON and verify that Data Guard health check error/warning is cleared.

ORA-16794 Database Guard is ON for primary database

Cause: Primary database has database guard ON, which is not normal.

Action: Issue the ALTER DATABASE GUARD NONE statement to turn the guard OFF and verify that Data Guard health check error/warning is cleared.

Cause: In the act of failover or switchover, the database resource guard may detect that reinstantiation of the database is necessary due to the impending role change. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database.

Action: Reinstantiate the database on the site indicated by the broker and then re-add that site to your broker configuration.

ORA-16796 One or more property cannot be imported from database

Cause: Importing existing database settings into the Data Guard properties failed for one or more properties. The cause may be that the database is not mounted or open, or the connection to the standby database being imported is down.

Action: Check the Data Guard console log to find more details about the problem.

ORA-16797 SPFILE is missing in the Data Guard Broker environment

Cause: Server parameter file is not being used in the database, or the resource guard failed to retrieve the status of the SPFILE.

Action: Issue a CREATE SPFILE='...' FROM PFILE='...' statement to create an SPFILE, and restart the database to use the SPFILE.

ORA-16798 Unable to complete terminal recovery on the standby

Cause: Terminal recovery on the standby failed during the graceful failover operation.

Action: Check Data Guard console log and alert logs to see more details on the reason of the failure.

ORA-16799 Physical apply service is offline

Cause: Either the Data Guard metadata indicates the physical apply service is turned off, or the recovery process MRP0 is not running. In either of the cases, physical apply related properties cannot be set.

Action: Turn on the physical apply service through Data Guard broker, then reset the physical apply related property again.

ORA-16800 Log transport service for some site is incorrectly set to ALTERNATE

Cause: Log transport service for some site is currently set to ALTERNATE while no other destinations is set to alternate to this site.

Action: Check the Data Guard console log for further details. Reset database state to turn on log transport again if necessary.

ORA-16801 Some log transport related property is inconsistent

Cause: The values of one or more log transport related configurable properties of a standby database resource are inconsistent with the primary's log transport service settings. This may be caused by a user operation on database outside of the Data Guard broker control.

Action: Query property InconsistentLogXptProps on the primary or Check the Data Guard console log to find which properties are inconsistent. Reset these properties on the appropriate standby to make them consistent with the primary's log transport settings.

ORA-16802 Cannot set property 'Alternate' to the primary site name

Cause: Data Guard Broker does not allow the primary site to be an alternate archival destination for a standby site.

Action: Set property Alternate to empty or to the name of a standby site.

ORA-16803 Unable to query a database table or fixed view

Cause: Failed to query a database table or fixed view. The database may not be open or mounted.

Action: Check Data Guard console log for more details.

ORA-16804 One or more configuration properties in metadata have invalid values

Cause: Data Guard Broker health check detects that one or more configuration properties in metadata have invalid values. They may be entered during the disabled period of database resource or through other means.

Action: Check Data Guard console log for more details on which properties have invalid values and reset them through Data Guard Broker.

Cause: The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database resource. The rejection was necessary since doing so would violate the overall protection mode for the configuration.

Action: If the LogXptMode configuration property must be changed for the specified standby database resource, then first downgrade the overall protection mode for the configuration. After that operation has completed, you will be able to change the LogXptMode configuration property for the standby database resource.

ORA-16806 Supplemental logging is not turned on

Cause: Supplemental logging is not turned on while there is a logical standby database in the configuration. This could happen either6854// on the primary or on the logical standby that is being switched over to the primary.

Cause: The database environment could not be allocated and initialized.

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

ORA-16902 Unable to allocate handle

Cause: The database handles could not be allocated.

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

ORA-16903 Unable to connect to database

Cause: The specified database was unreachable because it does not exist or was not started.

Action: Correct the request or start the database and try again.

ORA-16904 Unable to set attribute

Cause: The server attributes could not be set.

Action: check additional error messages.

ORA-16905 Failed.

Cause: The given action failed.

Action: check additional error messages.

ORA-16906 Unable to accept commands: no memory

Cause: No memory was available for the program.

Action: Increase memory and try again.

ORA-16907 missing field

Cause: A required field was missing.

Action: Type "help" for syntax and try again.

ORA-16908 Unknown option: "string"

Cause: The given option is not supported.

Action: Try again using the proper command line syntax.

ORA-16909 Fatal Error. quitting...

Cause: A fatal error was encountered.

Action: See additional error messages and contact Oracle Support Services.

ORA-16910 unable to issue command to server

Cause: Commands cannot be issued to the server.

Action: See additional error messages and contact Oracle Support Services.

ORA-16911 Warning:

Cause: An action succeeded with warnings.

Action: See error message and take appropriate action.

ORA-16912 Unknown command "string". Try "help"

Cause: An unknown command was issued.

Action: Try again using a valid command.

ORA-16914 Missing connect string. Try "help"

Cause: The connect string for the database is missing.

Action: Try the command again with a valid connect string.

ORA-16916 Missing site. Try "help"

Cause: The site name is missing.

Action: Try the command again using correct syntax.

ORA-16917 Missing XML document. Try "help"

Cause: The XML document argument was missing.

Action: Try the command again using correct syntax.

ORA-16939 Could not start up "string" as primary

Cause: The named site could not be started in the primary role.

Action: See additional messages.

ORA-16940 Started "string" as new primary

Cause: The named site was started as the new primary site.

Action: No action is required.

ORA-16942 Could not start up "string" as standby

Cause: The named site could not be started in the standby role.

Action: See additional messages..

ORA-16943 Started "string" as standby

Cause: The named site was started as the new primary site.

Action: No action required.

ORA-16944 Failover succeeded. New primary is "string"

Cause: The failover operation succeeded.

Action: No action required.

ORA-16945 Syntax error before or at "string"

Cause: The given command could not be processed because a syntax error occurred at the named token.

Action: Try the command again using valid syntax.

ORA-16946 Site "string" was not found

Cause: The named site could not be found.

Action: Try the command again using a valid site.

ORA-16947 "string" does not run in the primary role

Cause: The named resource does not run in the primary role.

Action: Try the command again using a resource that runs in the primary role.

ORA-16948 "string" does not run in the standby role

Cause: The named resource does not run in the standby role.

Action: Try the command again using a resource that runs in the standby role.

ORA-16949 Resource "string" was not found

Cause: The named resource was not found.

Action: Try the command again using a valid resource.

ORA-16950 Unable to retrieve "string" for editing

Cause: The named object could not be retrieved for editing.

Action: Contact Oracle Support Services.

ORA-16951 manager information not found

Cause: The manager information could not be retrieved for a generic resource.

Action: Contact Oracle Support Services.

ORA-16952 unable to describe configuration

Cause: The configuration could not be described.

Action: The framework could not be contacted. Check to see that the DMON process is running.

ORA-16953 site or resource "string" does not exist

Cause: The named site or resource does not exist.

Action: Try the command again using a valid site or resource.

ORA-16954 a resource cannot run on multiple sites this way

Cause: An attempt was made to create a resource that depends on multiple sites. This is not possible using one command.

Action: Issue the command twice; one with the first site and the second using the second site.

ORA-16955 unable to create or locate template

Cause: The template could not be found.

Action: See additional error messages.

ORA-16956 missing template name

Cause: The template name was omitted from the command.

Action: Try the command again using a valid template name.

ORA-16957 template "string" was not found

Cause: The named template could not be found.

Action: Try the command again using a valid template name.

ORA-16958 unable to convert document

Cause: The document could not be converted.

Action: Contact Oracle Support Services.

ORA-16959 NULL answer from framework

Cause: No answer came from the framework.

Action: The framework is not available. Check to see that the DMON process exists.

ORA-16960 status not available

Cause: The status could not be retrieved.

Action: The framework is not available. Check to see that the DMON process exists.

ORA-16991 ambiguous resource name

Cause: The named resource exists on more than one site.

Action: The request must be more specific. Issue the command again using the ON SITE clause.

ORA-16992 You must restart site "string" manually.

Cause: The operation was successfully completed, and it requires a restart of given site. However, DGMGRL was unable to perform an automatic restart. The user has to shutdown and startup the site manually.

Action: Shut down the given site and start it up.

ORA-17500 ODM err:string

Cause: An error returned by ODM library

Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance.

ORA-17501 logical block size string is invalid

Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum

Action: check parameters in the initialization parameter file.

ORA-17502 ksfdcre: string Failed to create file string

Cause: file creation failed due to either insufficient OS permission or the file already exists

Action: check additional error messages

ORA-17503 ksfdopn: string Failed to open file string

Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.

Action: check additional error messages

ORA-17504 ksfddel:Failed to delete file string

Cause: The file thats being deleted is still in use or the process has insufficient permission to delete file.

Action: check additional error messages

ORA-17505 ksfdrsz: string Failed to resize file to size number blocks

Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.

Action: check additional error messages

ORA-17506 I/O Error Simulation

Cause: The i/o request is marked with error because the i/o error simulation event is turned on.

Action: none

ORA-17507 I/O request size string is not a multiple of logical block size

Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option

Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column

ORA-19007 Schema and element do not match

Cause: The schema and element specified in the inserted data does not match that of the column

Action: Insert/Update only the XML documents that conform to that particular schema and element.

ORA-19008 Invalid version of the XMLType

Cause: An invalid version of the XMLType was found.

Action: This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database.

ORA-19009 Missing XMLSchema keyword

Cause: The XMLSchema keyword is missing

Action: Specify the XMLSchema URL and element name.

ORA-19010 Cannot insert XML fragments

Cause: XML fragments got from extractNode cannot be inserted into the database.

Action: Convert the fragment into a proper XML document before insertion.

ORA-19011 Character string buffer too small

Cause: The string result asked for is too big to return back

Action: Get the result as a lob instead

ORA-19012 Cannot convert XML fragment to the required datatype

Cause: A conversion to a datatype was requested which cannot be performed

Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.

ORA-19013 Cannot create VARRAY columns containing XMLType

Cause: An attempt was made to create a VARRAY column which contains a XMLType