Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: An invalid NLS initialization parameter was specified.
Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
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.
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.
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.
Cause: One of the following:
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.
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.
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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The character set specified when creating the control file is unknown.
Action: Specify a known character set.
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.
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.
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.
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.
Cause: The character set specified is not allowed for this operation or is invalid.
Action: Ensure that the specified character set is valid.
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.
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.
Cause: This command can only be run when connecting as user SYS.
Action: Connect as user SYS to run this command.
Cause: This command can only be run when the database is in RESTRICTED mode.
Action: Ensure that the system is in RESTRICTED mode.
Cause: This command can only be run when the database is in EXCLUSIVE mode.
Action: Ensure that the system is in EXCLUSIVE mode.
Cause: This command can only be run when there are no other sessions active.
Action: Ensure there are no other connections to the database.
Cause: Load on the system is too high to perform parallel queries.
Action: Re-execute serially or wait until the system load is reduced.
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause.
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.
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: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.
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.
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.
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.
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.
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.
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: The parallel create index fastpath operation event has been set.
Action: Set this event only under the supervision Oracle development.
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
Cause: An unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
Cause: Invalid value for DEGREE was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: Specify each desired PARALLEL clause option only once.
Cause: The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.
Action: Respecify with an explicit degree of parallelism.
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit degree of parallelism.
Cause: The parallel query server was hung and subsequently killed.
Action: Re-execute the query and report suspicious events in the trace file to Oracle Support Services if the error persists.
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.
Action: Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.
Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.
Action: Do not use PDML at remote sites.
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.
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.
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.
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.
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.
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance 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.
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.
Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.
Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.
Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.
Action: Commit/roll back the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.
Cause: Transaction in progress.
Action: Commit or roll back the transaction and then re-execute.
Cause: Schema modified during the parse phase of parallel processing.
Action: No action required.
Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire.
Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the PDML again.
Cause: A locally managed database must have a temporary tablespace other than SYSTEM tablespace.
Action: Specify the default temporary tablespace when creating a locally managed database.
Cause: In a locally managed database, default temporary tablespace must be TEMPORARY type.
Action:
Cause: In a dictionary-managed database, default temporary tablespace must be SYSTEM or TEMPORARY type.
Action:
Cause: An attempt was made to assign a temporary tablespace to be a user's default tablespace.
Action: Assign a permanent tablespace to be the default tablespace.
Cause: An attempt was made to assign a permanent tablespace to be a user's temporary tablespace.
Action: Assign a temporary tablespace to be user's temporary tablespace.
Cause: An attempt was made to assign a dictionary managed tablespace to be a user's temporary tablespace.
Action: Assign a locally managed temporary tablespace to be the user's temporary tablespace.
Cause: An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.
Action: Create a locally managed tablespace.
Cause: An attempt was made to migrate a locally managed tablespace to dictionary managed type when the database has a locally managed SYSTEM tablespace.
Action: Such an operation cannot be issued.
Cause: An attempt was made to alter a dictionary managed tablespace to read write in a database whose SYSTEM tablespace is locally managed. This tablespace can only be dropped.
Action: Such an operation cannot be issued.
Cause: The ALTER DATABASE FORCE LOGGING statement failed because the database is already in force logging mode.
Action: No action required.
Cause: The ALTER DATABASE NO FORCE LOGGING statement failed because the database is not in force logging mode.
Action: No action required.
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING statement running in the system.
Action: Contact the database administrator who is responsible for the concurrent statement.
Cause: An attempt to alter the specified temporary tablespace failed because the tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by issuing an ALTER TABLESPACE NO FORCE LOGGING statement.
Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.
Action: No action required.
Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.
Action: No action required.
Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.
Action: Remove all but one of the FORCE LOGGING options.
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove the checkpoint option.
Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
Cause: An attempt was made to drop a column from a nested table.
Action: This action is not allowed.
Cause: An attempt was made to drop all columns in a table.
Action: Make sure at least one column remains in the table after the drop column operation.
Cause: An attempt was made to drop a column used as the partitioning key.
Action: This action is not allowed.
Cause: An attempt was made to drop column from a partition/subpartition on a read-only tablespace.
Action: Set the tablespace to read write and resubmit statement.
Cause: An attempt was made to access a table with columns in partially dropped state (that is, drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.
Cause: An attempt was made to combine drop column with other ALTER TABLE operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed.
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement.
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.
Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.
Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.
Action: Bring the tablespace online and resubmit statement.
Cause: An attempt was made to repeat the drop column option in a single statement.
Action: Separate drop column options into different statements and resubmit statements.
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.
Action: Cannot submit this statement.
Cause: An attempt was made to drop a virtual column generated by the system.
Action: This action is not allowed.
Cause: An attempt was made to drop a primary key column from an index- organized table.
Action: This action is not allowed.
Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.
Cause: The specified range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Support Services.
Cause: An error occurred in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
Cause: A character that is not in the range [0-9] or [A-Fa-f] was detected.
Action: Verify that all characters in a string are in the range [0-9] or [A-Fa-f].
Cause: Part of the specified date format is invalid.
Action: Verify that the date format is valid.
Cause: The specified date string has a bad component or does not match the specified format string.
Action: Make sure that the components of the date string are valid and that the date and format strings match.
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
Cause: A specified dimension value is outside the range defined for that dimension.
Action: Make sure that all values to be encoded are within the defined dimension range.
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.
Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
Cause: The number of values used to define the window does not correspond to the window type.
Action: Verify that the number of values used to define the window is correct for the window type and number of dimensions.
Cause: The partition common code was not correctly decoded.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
Cause: Vertex coordinates lie outside the valid range for the specified dimension.
Action: Re-define vertex coordinates within specified boundaries.
Cause: A vertex coordinate has a NULL value.
Action: Re-define vertex coordinate to have a non-NULL value.
Cause: The coordinates defining a geometric element are not connected.
Action: Re-define coordinates for the geometric element.
Cause: The coordinates defining a polygonal geometric element represent crossing segments.
Action: Re-define the coordinates for the polygon.
Cause: An interior element of a geometric object interacts with the exterior element of that object.
Action: Re-define coordinates for the geometric elements.
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
Action: Re-define the coordinates for the polygon.
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
Action: Re-define the coordinates of the polygon.
Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.
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.
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.
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
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.
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.
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.
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.
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.
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.
Action: Verify that the geometries have valid data.
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.
Action: Verify that the geometries have valid data.
Cause: The specified geometry function is not supported for Point data.
Action: Make sure that the specified geometry function is not called on point data.
Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.
Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.
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.
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
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.
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL.
Action: Verify that the SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial User's Guide and Reference. Retry the operation.
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.
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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: An invalid number of arguments was specified for an SDO_GEOM function.
Action: Refer to the Oracle Spatial User's Guide and Reference for a description of the syntax and semantics of the relevant 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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
Cause: The specified spatial table does not exist.
Action: Check the Spatial Data option data dictionary to make sure that the table is registered.
Cause: The specified spatial table is registered in the Spatial Data option data dictionary.
Action: Remove the existing table from the Spatial Data option data dictionary or use a different name.
Cause: The specified spatial table is not partitioned.
Action: Check the Spatial Data option data dictionary and make sure that a high water mark is set.
Cause: The specified spatial table does not have a partition key defined.
Action: Check the Spatial Data option data dictionary and make sure that the table is partitioned.
Cause: The specified count mode is not valid.
Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.
Cause: The specified Oracle table does not exist.
Action: Check the Oracle7 data dictionary and make sure that the table exists.
Cause: The specified tablespace does not exist.
Action: Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.
Cause: The specified tablespace is already allocated to the spatial table.
Action: Allocate another tablespace name to the table.
Cause: The specified tablespace is not allocated to the specified spatial table.
Action: Allocate the tablespace to the spatial table.
Cause: The specified partition does not exist.
Action: Verify the name of the partition by checking the Spatial Data option data dictionary.
Cause: Identical source and target tablespaces were specified when trying to move partition.
Action: Specify different source and target tablespaces if you wish to move a partition.
Cause: The creation of a child partition failed.
Action: Check for other errors that accompany this error and correct them first.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified column is already defined for the spatial table.
Action: Use a different column name.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE or VIEW.
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, such as: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.
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.
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.
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
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.
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
Cause: The specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
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.
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
Cause: The number of dimensions specified is out of range.
Action: The number of dimensions must be between 1 and 32.
Cause: The specified table has rows in it.
Action: Make sure that the table to be registered is empty.
Cause: The specified Oracle error was encountered.
Action: Correct the Oracle error.
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
Cause: The specified table already exists.
Action: Drop the specified table.
Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.
Action: Make sure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Retry the operation.
Cause: The specified element could not be read from the layer_SDOGEOM table.
Action: Verify that the specified element exists in the table. Retry the operation.
Cause: The geometry type in the layer_SDOGEOM table is unsupported.
Action: Modify the geometry type to be one of the supported types.
Cause: Initialization of the tessellation package failed.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: There was insufficient memory to read the geometry from the database.
Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table.
Action: Verify that the geometry is valid and within the defined domain.
Cause: Internal error in some Spatial Cartridge stored procedure.
Action: Record the sequence of procedure calls or events that preceeded this error and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.
Action: Check the Spatial Cartridge User Guide for the number, syntax, and semantics of expected parameters for spatial index creation.
Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.
Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.
Cause: An error was encountered while trying to read USER_SDO_GEOM_METADATA table.
Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.
Cause: An error was encountered while trying to create the index table.
Action: Check that user has create table privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check to make sure that the parameters passed in the parameter string are all valid.
Cause: An internal error was encountered while creating the spatial index.
Action: Contact Oracle Support Services with the exact error text.
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
Cause: An internal error was encountered.
Action: Contact Oracle Support Services with the exact error text.
Cause: An internal error was encountered while trying to read SDO_INDEX_METADATA table.
Action: Contact Oracle Support Services. Note this and accompanying error numbers.
Cause: An error was encountered while trying to insert data into the index table. Likely causes are:
Action: Check the accompanying error messages.
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.
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.
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.
Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.
Action: Verify that the geometry is valid and within the defined domain.
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.
Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.
Action: Check the Oracle Spatial User's Guide and Reference for the number, syntax, and semantics of expected parameters for spatial alter index command.
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.
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.
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.
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.
Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
Cause: There are duplicate entries for the given table and column value pair in the SDO_GEOM_METADATA table
Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the SDO_GEOME_METADATA table.
Cause: An index name was specified which is longer than the supported length of the spatial index name.
Action: Check the supported size of the index name and reduce the size of the index name.
Cause: An index table name was specified which is longer than the supported length of the spatial index table name.
Action: Check the supported size of the index table name and reduce the size of the index name.
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.
Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.
Action: Verify that two compatible indexes are used for the spatial join operator. Indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values.
Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.
Action: Make sure that the index is created on a column of type SDO_GEOMETRY.
Cause: The specified temporary table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.
Cause: The specified index table either already exists or there is not enough tablespace. Otherwise, contact Oracle Support Services.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.
Cause: This feature assumes a minimum of 64 KB memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional inserts for the rest.
Cause: The specified sequence number exists.
Action: Delete the sequence object or contact Oracle Support Services.
Cause: The index table is either deleted or corrupted.
Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.
Cause: An internal error occurred in R-tree processing.
Action: Contact Oracle Support Services with message text.
Cause: An inconsistency was encountered during concurrent updates possibly due to the use of serializable isolation level.
Action: Change the isolation level to "read committed" using alter session or contact Oracle Support Services with the message text.
Cause: An error occurred in reading the dimensionality parameter.
Action: Check the documentation for a valid range and specify the dimensionality as a parameter.
Cause: An error occurred because of too few values in query mbr.
Action: Omit the dimensionality or use the dimensionality of the query.
Cause: An error occurred because the dimensionality specified in the CREATE INDEX does not match that of the data.
Action: Change it to the data dimensionality.
Cause: An error occurred in reading the information for the specified table and column in USER_SDO_GEOM_METADATA table.
Action: Insert appropriate row specifying the tolerance.
Cause: Currently, an n-d R-tree only supports sdo_filter operator.
Action: Check the documentation for querytype parameters for sdo_filter or contact Oracle Support Services.
Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.
Action: Contact Oracle Support Services with the exact error text.
Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.
Action: Check that the specified feature and geometry table names are correct and then verify that the current user has at least SELECT privilege on those tables.
Cause: The specified entry already exists in the metadata table.
Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.
Cause: Data migration source table layer_SDOGEOM does not exist.
Action: Ensure that the specified layername is correct and that the corresponding spatial layer tables exist in the current schema.
Cause: The specified geometry table does not exist in the current schema.
Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.
Cause: The specified table does not have a column of type SDO_GEOMETRY.
Action: Alter or recreate the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.
Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.
Action: Alter the column definition to be of type SDO_GEOMETRY.
Cause: The specified table does not contain a GID column.
Action: Confirm that the GID columnname was correctly specified and that it exists in the specified table.
Cause: GID column is not of type NUMBER.
Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.
Cause: An OCI error occurred or the user has insufficient quota in the active tablespace or the rollback segments are too small.
Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.
Cause: There was an error reading the geometry data from the layer_SDOGEOM table.
Action: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, then run VALIDATE_GEOMETRY on the specified layer.
Cause: There is no entry in USER_SDO_GEOM_METADATA for the specified geometry table.
Action: Insert an entry for the destination geometry table with the dimension information obtained from the source layer_SDODIM table.
Cause: An internal error occurred.
Action: Contact Oracle Support Services with the exact error message text.
Cause: An OCI error occurred while processing the layer or geometry tables.
Action: Take the appropriate steps to correct the OCI specific error.
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
Cause: The specified object failed the geometric integrity checks performed by VALIDATE_GEOMETRY.
Action: Consult the Oracle Spatial User's Guide and Reference for information on the geometric integrity checks performed by VALIDATE_GEOMETRY and correct the geometry definition if required.
Cause: The layer_SDODIM table does not exist.
Action: Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema.
Cause: A Spatial operator was invoked with a window geometry with an SRID and the layer without an SRID or window has no SRID and the layer has an SRID.
Action: Make sure that the layer and window both have an SRID or they both do not have an SRID.
Cause: A spatial index create was invoked on a column that is not of type SDO_GEOMETRY.
Action: Spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column has SDO_GEOMETRY type.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error or SRID does not match a table entry.
Action: Check that a valid SRID is being used.
Cause: Parsing error on source or destination coordinate system WKT or incompatible coordinate systems.
Action: Check validity of WKT for table entries and the legitimacy of the requested transformation.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: A coordinate pair was out of valid range for a conversion/projection.
Action: Check that data to be transformed is consistent with the desired conversion/projection.
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.
Action:
Cause: An internal error while transforming points.
Action: Check the accompanying error messages.
Cause: Spatial function called with an unknown UNIT.
Action: Check the supported units by Spatial and call the spatial function with the correct UNIT parameter.
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
Action: Check unit specification and respecify it.
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.
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.
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.
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.
Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.
Action: Check WKT in CS_SRS table for Earth radius and inverse flattening.
Cause: Low level coordinate transformation error trap.
Action: Check the accompanying error messages.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: The MASK you passed to RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial User's Guide and Reference for a list of supported masks.
Cause: The given LRS segment was not a valid linestring.
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).
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.
Cause: The given measure for linear referencing was out of range.
Action: Re-define the given measure.
Cause: The given geometric segments were not connected.
Action: Check the start/end points of the given geometric segments.
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.
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.
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.
Cause: Clipping (dynseg) a polygon across multiple rings.
Action: Polygon clipping only allowed for a single ring.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
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.
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.
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.
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.
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.
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.
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
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.
Cause: Circle type should be represented by 3 distinct points on the circumference.
Action: Confirm that there are only 3 points for circle type.
Cause: The 2 points representing the extent are identical.
Action: Confirm that the 2 points describing the extent type are distinct.
Cause: This subtype is not allowed within the ETYPE specified.
Action: Refer to Oracle Spatial User's Guide and Reference for type definitions.
Cause: The compound type declare more sub-elements than actually defined.
Action: Confirm that the number of sub-elements is consistent with the compound type declaration.
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
Cause: Spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.
Action: Make sure that all geometries in a layer have the same dimensions and they match the dimensions in the SDO_DIM_ARRAY object for the layer in USER_SDO_GEOM_METADATA.
Cause: Spatial layer has a geometry with a different SRID than the SRID specified for the layer.
Action: Make sure that all geometries in a layer have the same SRID and the SRIDs match the SRID in USER_SDO_GEOM_METADATA for the layer.
Cause: In the Spatial geometry, interior and exterior rings are not used consistently.
Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.
Cause: In a spatial geometry, the exterior and/or interior rings are not oriented correctly.
Action: The exterior rings should be oriented counter clock-wise and interior rings should be oriented clock wise.
Cause: In a polygon type geometry, there is more than one exterior ring.
Action: Set the type to be multi-polygon if more than one exterior is present in the geometry.
Cause: A 4 digit etype for non polygon type element is used or the orientation is not a valid orientation for interior/exterior rings of the polygon.
Cause: Only Non-geodetic 3D linestring geometry (made of line segments) are supported for 3D LRS package.
Action: Check the geometry and element types and SRID.
Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in dim_info_array.
Action: Check geometry gtype and its dim_info_array.
Cause: Modifying the metadata after the index is created will cause inconsistency between geometry gtype and diminfo.
Action: Modify(or Prepare) metadata before creating index on sdo_geometry column.
Cause: Element type extent for a polygon geometry is not supported for geodetic data.
Action: Convert the extent type polygon to a regular 5 point polygon and set etype accordingly.
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
Cause: The layer has a type that is different or inconsistent with the type of the current geometry.
Action: Change the geometry type to agree with the layer type or change the layer type to agree with the geometry type.
Cause: An invalid type name is specified for the layer gtype constraint.
Action: Consult the Oracle Spatial User's Guide and Reference to get a list of valid layer gtypes that can be used in defining a layer gtype constraint.
Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4 digit etype).
Action: Make sure all the polygon elements have orientation specified using the 4 digit etype notation.
Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the given geometry.
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the given geometry.
Cause: This is an internal Oracle GeoImage error.
Action: Contact Oracle Support Services.
Cause: The GeoImage format is not supported.
Action: Confirm that the GeoImage format is valid and supported.
Cause: The object specified as the destination is NULL.
Action: Confirm that the object specified as the destination is not NULL.
Cause: The source GeoImage has a NULL geometry.
Action: Verify that the geometry of the source GeoImage is not NULL.
Cause: An attempt has been made to modify a GeoImage which is not stored in the database.
Action: Import the GeoImage in order to modify it.
Cause: The object specified as the source is NULL.
Action: Confirm that the object specified as the source is not NULL.
Cause: The image processing command specified is not supported for a GeoImage.
Action: Consult the Oracle interMedia User's Guide and Reference to verify which image processing commands are supported within an Oracle GeoImage method.
Cause: The GeoImage space type qualifier is invalid.
Action: Use a valid space type qualifier (RASTER or MODEL).
Cause: The table name parameter is NULL.
Action: Verify that the parameter used for the table name is not NULL.
Cause: The table specified does not exist.
Action: Verify that the table name used is valid and the table exists.
Cause: The column name parameter is NULL.
Action: Verify that the parameter used for the column name is not NULL.
Cause: The column specified does not exist.
Action: Verify that the column name used is valid and the column exists.
Cause: The ROWID value used is not valid.
Action: Verify that the ROWID value used is valid.
Cause: The GeoImage in the table could not be selected.
Action: Verify that the GeoIMage is present in the table and the supplied parameters are valid.
Cause: The table containing the GeoImage could not be updated.
Action: Verify that the table exists and is valid.
Cause: The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain.
Action: Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain specified.
Cause: The SDO_GEOMETRY value used is not valid.
Action: Verify that the SDO_GEOMETRY is valid. Consult the Oracle Spatial User's Guide and Reference for a list of valid geometries.
Cause: The raster to model space transformation associated with a GeoImage is undefined.
Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.
Cause: The model to raster space transformation associated with a GeoImage is undefined.
Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.
Cause: A latitude value outside the valid range [-90,90] has been used.
Action: Verify that the GeoImage geometry definition is within the domain.
Cause: The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated.
Action: Verify that the transformation is supported and that the GeoImage format is valid.
Cause: The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated.
Action: Verify that the transformation is supported and that the GeoImage format is valid.
Cause: The LOB used for the source is not initialized.
Action: Verify that the source is properly initialized.
Cause: The LOB used for the source is empty.
Action: Verify that the source is properly initialized and data has been imported into it.
Cause: The LOB used for the destination is not initialized.
Action: Verify that the destination is properly initialized.
Cause: The LOB used for the destination is empty.
Action: Verify that the destination is properly initialized and data has been imported into it.
Cause: The raster origin specified is not supported.
Action: Verify that the origin specified is supported.
Cause: The value specified for the raster origin is invalid.
Action: Verify that the value used to specify the raster origin is valid and supported.
Cause: The source does not exist or cannot be accessed.
Action: Verify that the source specification is correct and accessible.
Cause: The specified operation is not supported on the particular geoimage type.
Action: Verify that the operation is supported.
Cause: The model specified for the definition of the coordinate system is not supported.
Action: Verify that the model value is correct.
Cause: The geometry used to crop a GeoImage is NULL.
Action: Verify that the geometry used for the crop operation is not NULL.
Cause: The parameters used in the scale operation are invalid.
Action: Verify that the scaling parameters are greater than zero.
Cause: The scale mode used in the scale operation is invalid.
Action: Consult the Oracle interMedia User's Guide and Reference for a list of valid scale mode qualifiers.
Cause: The format specified for conversion is invalid or unsupported.
Action: Verify that the conversion format specified is valid.
Cause: The tag or key is invalid.
Action: Verify that the format version is supported or the format is valid.
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).
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.
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.
Cause: The window specified as destination in the command is not valid.
Action: Verify that the window definition is correct.
Cause: CREATE INDEX statement contained more than one LOCAL clause.
Action: Specify LOCAL option at most once.
Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause.
Action: Specify LOCAL or GLOBAL clause, but not both.
Cause: CREATE INDEX statement contained more than one GLOBAL clause.
Action: Specify GLOBAL option at most once.
Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause.
Action: Specify GLOBAL or LOCAL clause, but not both.
Cause: Keyword PARTITION missing.
Action: Supply missing keyword.
Cause: Keyword RANGE missing.
Action: Supply missing keyword.
Cause: A partition name of the form identifier is expected but not present.
Action: Enter an appropriate partition name.
Cause: Keyword LESS missing.
Action: Supply missing keyword.
Cause: Keyword THAN missing.
Action: Supply missing keyword.
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.
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.
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.
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.
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.
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.
Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 65535.
Action: Reduce the number of partitions to not exceed 65535.
Cause: An attempt was made to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned table.
Action: Correct the statement and re-enter it.
Cause: Partition bound list contained more elements than there are partitioning columns.
Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index.
Cause: Partition bound list contained fewer elements than there are partitioning columns.
Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index.
Cause: Partition bound list contained an element of invalid type (that is, not a number, non-empty string, datetime or interval literal, or MAXVALUE).
Action: Ensure that all elements of partition bound list are of valid type.
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.
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.
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.
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.
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.
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.
Cause: Definition of a table contained both PARTITION and CLUSTER clauses which is illegal.
Action: Remove one of the conflicting clauses.
Cause: CREATE TABLE statement contained more than one PARTITION clause.
Action: Specify PARTITION option at most once.
Cause: Keyword AT or VALUES is missing.
Action: Supply missing keyword.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal.
Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement.
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.
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.
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.
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.
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.
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.
Cause: Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE.
Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION.
Cause: ALTER INDEX statement contained REBUILD keyword following some index attributes (for example, INITRANS).
Action: Ensure that keyword REBUILD immediately follows the name of the index being altered.
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.
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.
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.
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.
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition the table named in ALTER TABLE statement, which is illegal.
Action: Avoid modifying data type and/or length of table partitioning column(s).
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition some index defined on the table named in ALTER TABLE statement, which is illegal.
Action: Avoid modifying data type and/or length of index partitioning column(s).
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.
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.
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 one or more partitions of which are marked Index Unusable.
Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION.
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement.
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.
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.
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.
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.
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).
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.
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.
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).
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.
Cause: Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, at best, meaningless.
Action: Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned.
Cause: An attempt was made to drop or split a partition of a LOCAL index which is illegal.
Action: Ensure that the index named in such statement is a GLOBAL partitioned index.
Cause: An attempt was made to drop highest partition of a GLOBAL index, which is illegal.
Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index.
Cause: ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal.
Action: Ensure that only valid options are specified.
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.
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.
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.
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.
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.
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.
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.
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 table in the EXCHANGE operation is either clustered or partitioned.
Action: Ensure that the table with which the partition is being exchanged for is not partitioned or clustered.
Cause: The two tables specified in the EXCHANGE have different number of columns.
Action: Ensure that the two tables have the same number of columns with the same type and size.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Partitioning column specified by the user was of type ROWID, which is illegal.
Action: Ensure that no partitioning column is of type ROWID.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: NOREVERSE was specified more than once in ALTER INDEX statement.
Action: Remove all but one of the NOREVERSE clauses and reissue the statement.
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.
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.
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: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints.
Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.
Cause: Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command.
Action: Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used.
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.
Cause: One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding.
Action: Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement.
Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply:
Action: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.
Cause: An attempt was made to combine an ALTER TABLE MOVE statement with another operation, such as MODIFY.
Action: Make sure that MOVE is the only operation specified in ALTER TABLE statement.
Cause: An attempt was made to make a reverse index with some index columns marked DESC.
Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC.
Cause: An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column.
Action: Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB.
Cause: User doing exchange does not have full table access due to VPD policies.
Action: Grant exempt priviliges to this user.
Cause: Keyword SUBPARTITION missing.
Action: Supply the missing parameter.
Cause: Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, or composite range/hash (R+H).
Action: Specify one of valid partitioning methods.
Cause: number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-65535).
Action: Specify a number between 1 and 65535 in the number-of-partitions clause.
Cause: Both STORE IN and partition_description clauses were specified in a CREATE TABLE|INDEX command.
Action: Remove one of offending clauses.
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.
Cause: Expected either the PARTITION or SUBPARTITION keyword but neither was supplied.
Action: Supply the missing keyword.
Cause: Number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-65535).
Action: Specify a number between 1 and 65535 in the number-of-subpartitions clause.
Cause: A subpartition name of the form identifier is expected but not present.
Action: Enter an appropriate subpartition name.
Cause: CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 65535.
Action: Reduce the number of subpartitions to not exceed 65535.
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.
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).
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.
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.
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.
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.
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.
Cause: Keyword INTO missing.
Action: Supply the missing keyword.
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.
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.
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement.
Action: Specify only legal options.
Cause: User requested to generate default partition description(s) (possibly via PARTITIONS number_of_partitions) while at the same time specified partition_description clause which is illegal.
Action: Remove one of offending clauses.
Cause: User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified subpartition_description clause which is illegal.
Action: Remove one of offending clauses.
Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION].
Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION.
Cause: Subpartition to be accessed may only be specified using its name. An attempt was made to use a subpartition number or a bind variable.
Action: Modify statement to refer to a subpartition using its name.
Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional parallel_clause. No partition/subpartition attributes may be specified.
Action: Ensure that no partition/subpartition attribute was specified.
Cause: An ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (for example, MOVE SUBPARTITION) with some other operation (for example, MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal.
Action: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will.
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).
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.
Cause: An attempt was made to specify TABLESPACE DEFAULT for a partition of a range/system/hash-partitioned LOCAL index object, which is illegal.
Action: Replace TABLESPACE DEFAULT with TABLESPACE ts_name or remove it.
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.
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.
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.
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.
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).
Cause: One of the following:
Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses and then reissue the command.
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.
Cause: An attempt was made to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a hash-partitioned index.
Action: Remove the physical attributes one is trying to modify.
Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement.
Action: Specify only legal options.
Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt.
Action: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas.
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.
Cause: Subpartition not found for the object.
Action: Retry with correct subpartition name.
Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a hash partition.
Action: Specify only legal options.
Cause: The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned by composite range method.
Action: Ensure that the table is partitioned by composite range method.
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a range or composite range partitioned table which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION.
Cause: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by range, list, or composite range method.
Action: Ensure that the table is partitioned by range, list, or composite range method.
Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a composite range-partitioned table which is illegal.
Action: Remove the invalid clause(s), or ensure that the table is partitioned by composite range method.
Cause: An attempt was made to move a partition that is not a range or hash partition which is illegal.
Action: Specify MOVE PARTITION for a range or hash partition only.
Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a composite range/hash-partitioned table which is illegal.
Action: Remove the invalid clause(s), or ensure that the table is partitioned by composite range/hash method.
Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method.
Action: Specify a valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method.
Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING option to a hash partition via ALTER TABLE ADD/MOVE PARTITION command which is illegal. Only TABLESPACE may be specified.
Action: Remove the invalid option(s).
Cause: User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a hash-partitioned table which is illegal.
Action: Remove the VALUES LESS THAN clause from the description of partition being added.
Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of the subpartition being renamed.
Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index.
Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of some existing subpartition of the object.
Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index.
Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method.
Action: Ensure that the table is partitioned by Composite method.
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal.
Action: Avoid modifying data type and/or length of table subpartitioning column(s).
Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal.
Action: Avoid modifying data type and/or length of index subpartitioning column(s).
Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a range or composite range partition which is illegal.
Action: Remove the PARALLEL clause.
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.
Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a range or hash partition which is illegal.
Action: Specify EXCHANGE PARTITION for a range or hash partition only.
Cause: The table in ALTER TABLE MODIFY PARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by range or hash method which is illegal.
Action: Ensure that the table is partitioned by range or hash method.
Cause: The table in ALTER TABLE MODIFY SUBPARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by composite range method which is illegal.
Action: Ensure that the table is partitioned by composite range method.
Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal.
Action: Use the higher-bound partition to be the resulting partition or specify a new partition name.
Cause: User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal.
Action: Specify lower-bound partition then higher-bound partition.
Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal.
Action: Specify two partitions that are adjacent.
Cause: User attempt to reuse lower-bound partition of the partitions being merged which is illegal.
Action: Specify new resulting partition name or reuse the higher-bound partition only.
Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned.
Action: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered.
Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns.
Action: Ensure that the two tables have the same number of columns with the same type and size.
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size.
Action: Ensure that the two tables have the same number of columns with the same type and size.
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.
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: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them.
Action: Ensure that the two tables do not have CHECK constraint defined on any column.
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints.
Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.
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.
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.
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.
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: An attempt was made to rebuild a partition of a composite range-partitioned index which is illegal.
Action: REBUILD the index partition, a subpartition at a time.
Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by composite range method.
Action: No action required.
Cause: An attempt was made to rebuild a partition of a composite range partitioned index which is illegal.
Action: No action required.
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints.
Action: Ensure that the two tables do not have PRIMARY KEY constraints defined on any column or disable all PRIMARY KEY constraints on both tables. Then retry the operation.
Cause: A composite partition can only be exchanged with a partitioned table.
Action: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite.
Cause: When exchanging a partitioned table with a composite partition, the partitioning type of the table must match the subpartitioning type of the composite partition.
Action: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition.
Cause: When exchanging a partitioned table with a composite partition, the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition.
Action: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the composite partition.
Cause: When exchanging a partitioned table with a composite partition, the number of partitions of the table must match the number of subpartitions of the composite partition.
Action: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition.
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.
Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
Cause: The block sizes of a pair of corresponding LOB columns of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of corresponding pairs of LOB columns of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of LOB columns were encountered after processing partition-level attributes of LOB columns or while processing CREATE TABLE statement, table-level attributes of LOB columns were encountered after processing partition descriptions.
Action: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement.
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.
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.
Cause: Number of columns in a partitioning column list exceeded the legal limit of 1 for list partitioned objects.
Action: Modify partitioning column list so that it consists of at most 1 column.
Cause: A list value cannot be specified more that once.
Action: Remove one of the specifications of the value.
Cause: A list value cannot be specified more that once.
Action: Remove one of the specifications of the value.
Cause: Partition list contains more than 65535 list values.
Action: Reduce the number of values to not exceed 65535 values.
Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or NULL).
Action: Ensure that all elements of partition bound list are of valid type.
Cause: Partitioned object contains more than 65535 list values.
Action: Reduce number of values to less than 65535.
Cause: VALUES LESS THAN or AT clause can be used only with range partitioned tables.
Action: Use VALUES (<value list>) clause with list partitioned tables.
Cause: VALUES (<value list>) clause can be used only with list partitioned tables.
Action: Use VALUES LESS THAN clause with range partitioned tables.
Cause: One of the list values in the ADD PARTITION or ADD VALUES statement already exists in another partition.
Action: Remove the duplicate value from the statement and try again.
Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the partition.
Action: Remove the value from the statement and try again.
Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value.
Action: Ensure that each of the resulting partitions contains at least 1 value.
Cause: The same partition name was specified twice for the merge operation.
Action: Re-submit operation with 2 distinct partition names.
Cause: ALTER TABLE ADD|DROP VALUES can only be performed on list partitioned objects.
Action: reissue the command against a list partitoned object.
Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition.
Action: Cannot execute the command, unless two or more values exist for partition.
Cause: A partition description follows the one describing the default partition.
Action: Ensure that the DEFAULT partition is the last partition description.
Cause: DEFAULT keyword has been specified along with other values when specifying the values for a list partition.
Action: Ensure that if DEFAULT is specified, it is the only value specified.
Cause: DEFAULT keyword has been specified when performing an ADD VALUES, DROP VALUES, SPLIT partition, or subpartition.
Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operations.
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.
Cause: A partition already exists with DEFAULT value.
Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists.
Action: Issue a SPLIT of the DEFAULT partition instead.
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.
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.
Cause: The concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement.
Action: Do not insert the key or insert it in another partition.
Cause: An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition.
Action: Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key.
Cause: Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement.
Action: No action required.
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.
Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.
Action: Find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.
Cause: At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition.
Action: Do not update the key. Or, add a partition capable of accepting the key.
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.
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.
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.
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.
Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause.
Action: No action required.
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.
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.
Action: This LOB locator is invalid and cannot be used.
Cause: An attempt was made to reference temporary table in a referential integrity constraint. This is not supported.
Action: Use triggers.
Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported.
Action: Use triggers.
Cause: An attempt was made to rebuild an index on a temporary table.
Action: The index data is anyway lost at end of session/transaction.
Cause: An attempt made to create a VARRAY or Nested Table column in a temporary table. This is not supported.
Action: Do not specify these datatypes for temporary tables.
Cause: An attempt was made to create an Index Organized Temporary table. This is not supported.
Action: Create the table with HEAP organization and the primary key.
Cause: Keyword GLOBAL is missing while creating temporary table.
Action: Supply the missing keyword.
Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more than once, or both COMPRESS and NOCOMPRESS were specified.
Action: Specify each desired COMPRESS or NOCOMPRESS clause option only once.
Cause: Incorrect syntax specified.
Action: Retry the command.
Cause: Table or index is not partitioned. Invalid syntax.
Action: Retry the command with correct syntax.
Cause: More than one partition name has been specified for analyze.
Action: Specify one partition name.
Cause: A partition/subpartition number or bind variable has been used.
Action: Specify a valid partition/subpartition name.
Cause: Incorrect syntax specified.
Action: Retry the command.
Cause: Incorrect syntax specified.
Action: Retry the command.
Cause: The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation.
Action: Delete rows in partition which do not qualify.
Cause: The specified table either does not exist or user does not have the proper privileges.
Action: Specify the correct table to use.
Cause: The specified table does not have the proper field definitions.
Action: Specify the correct table to use. See UTLVALID.SQL for more information.
Cause: The VALIDATE INTO has been specified for a non-partitioned table or cluster or index.
Action: Use the syntax correctly.
Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes.
Action: Retry the command with correct syntax.
Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes.
Action: Retry the command with correct syntax.
Cause: Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal.
Action: Ensure that no partitioning column is an object datatype.
Cause: Incorrect syntax specified.
Action: Retry the command.
Cause: More than one subpartition name has been specified for analyze.
Action: Specify one subpartition name.
Cause: The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation.
Action: Delete rows in subpartition which do not qualify.
Cause: An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation.
Action: REBUILD the unusable index subpartition.
Cause: A table partition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and reissue statement.
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.
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.
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.
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.
Cause: Cannot specify these clauses while specifying a template.
Action: Correct the subpartition template clause.
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: This syntax is valid only if subpartitioning dimension is hash.
Cause: Once a subpartition template has been specified during CREATE TABLE, it is illegal to specify SUBPARTITIONS or STORE IN anywhere else.
Action: Remove either SUBPARTITIONS or STORE IN, or remove the SUBPARTITION TEMPLATE clause.
Cause: A subpartition / lob segment was not specified a name in the template descriptions.
Action: All subpartitions / lob segments must have names specified in the template.
Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions.
Action: Either specify tablespaces for all or for none of the subpartitions.
Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions.
Action: Either specify tablespaces for all or for none of the subpartitions.
Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column.
Action: Either specify tablespaces for all or for none of the lob segments.
Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column.
Action: Either specify tablespaces for all or for none of the lob segments.
Cause: Lob attributes of a column must be specified for all subpartitions or must not be specified at all.
Action: Ensure lob attributes of a column are specified for all subpartitions or not specified at all.
Cause: A subpartition name cannot be duplicated within the template.
Action: Rename one of the subpartitions.
Cause: Two lob segments of the same column were given the same name in the template.
Action: Rename one of the lob segments.
Cause: Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier.
Action: Shorten either the partition name or the template name.
Cause: A list value cannot be specified more than once.
Action: Remove one of the specifications of the value.
Cause: A list value cannot be specified more than once.
Action: Remove one of the specifications of the value.
Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD | DROP VALUES or ALTER TABLE DROP | SPLIT | MERGE SUBPARTITION can only be performed on List subpartitioned objects.
Action: Re-issue the command against a List subpartitioned object.
Cause: An ADD/DROP VALUES operation is being performed on the default subpartition.
Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition.
Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition.
Action: Cannot execute the command, unless two or more values exist for subpartition.
Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value.
Action: Ensure that each of the resulting subpartitions contains at least 1 value.
Cause: A subpartition already exists with DEFAULT value.
Action: Remove the DEFAULT value from the specified list.
Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists.
Action: Issue a SPLIT of the DEFAULT subpartition instead.
Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition.
Action: Remove the duplicate value from the statement and try again.
Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition.
Action: Remove the value from the statement and try again.
Cause: A subpartition description follows the one describing the default subpartition.
Action: Ensure that the DEFAULT subpartition is the last subpartition description.
Cause: Table subpartition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and re-issue the statement.
Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition.
Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added.
Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index.
Action: Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned.
Cause: An operation such as ALTER TABLE SPLIT | ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method.
Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions.
Cause: A drop subpartition command is being executed when there is only one subpartition in the partition.
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.
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: An ALTER TABLE ADD SUBPARTITION statement was issued with a PARALLEL clause for a List subpartition of a Range/List partitioned object. This is not allowed.
Action: Remove the PARALLEL clause.
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table.
Action: Remove clause and re-issue the operation.
Cause: During a split or a merge of a partition of a range list partitioned table, you cannot specify any subpartitioning information for the resulting partitions.
Action: Remove all subpartitioning information from the DDL.
Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE.
Action: Ensure that the statement describes exactly one subpartition as the target that needs to be MERGEd.
Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT.
Action: Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation.
Cause: The same subpartition name was specified twice for the merge operation.
Action: Re-submit operation with 2 distinct subpartition names within the same composite partition.
Cause: An attempt was made to MERGE subpartitions in different Range Composite partitions.
Action: Re-issue the command after ensuring that the 2 subpartitions being merged lie within the same composite partition.
Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method.
Action: Re-issue the command after ensuring that the SUBPARTITIONS clause is not specified. To specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause.
Cause: User attempted to drop or split a subpartition of a LOCAL index which is illegal.
Action: Issue the statement on a table subpartition instead.
Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed.
Action: Re-issue the statement after removing the STORE-IN clause.
Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the INCLUDING INDEXES option has been specified and the tables have different hakan factors.
Action: Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable.
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.
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.
Cause: A STORE IN clause was specified for Range List partitioned object.
Action: Re-issue the command after removing the STORE IN clause.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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: Disable the standby destination or enable media recovery and retry.
Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file.
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.
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.
Cause: One of the following events caused an incompatibility:
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.LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.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.
Cause: One of the following events caused an incompatibility:
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.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.LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.LOG_ARCHIVE_DEST_n parameter.Action: Eliminate any incompatible parameter definitions.
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.
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.
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.
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.
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.
Cause: The value for the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) contained either repeated attributes or attributes that conflicted with each other.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
Cause: The value for the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) contained a REOPEN attribute with an invalid numeric value. The valid range is 0 - 65535.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
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.
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: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.
Action: Define one or more log archive destinations using the LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n parameters (n = 1, 2, ... 10). Then, change the value of 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.
Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1, 2, ... 10) parameters.
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.
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.
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.
Cause: Use of the FROM 'location' parameter is not allowed when MANAGED recovery has been specified.
Action: Correct the syntax and retry the command.
Cause: The indicated keyword is required but was not specified.
Action: Correct the syntax and retry the command.
Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or IMMEDIATE following CANCEL.
Cause: The managed standby database recovery operation has been canceled per user request.
Action: No action is required.
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.
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.
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.
Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database.
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.
Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.
Action: More specific messages will accompany this message.
Cause: An archive log destination attribute was attempted to be modified at the session level.
Action: Use the ALTER SYSTEM command to modify the destination attribute.
Cause: An archive log destination contains a dependency to another archive log destination that also contains a dependency.
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.
Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.
Action: No action required.
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.
Cause: Causes an I/O error to be signalled during the writing of an archival operation.
Action: No action required.
Cause: I/O error returned for a simulated archival failure during an archival operation.
Action: No action required.
Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.
Action: No action required.
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
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.
Cause: The FAL server on the primary database has problem archiving a redo log file requested by the standby database. The cause for this failure is logged in the alert log file.
Action: Check the alert log on the primary database. Take the appropriate action to solve the problem. Re-issue Managed Standby Recovery on the standby database again.
Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.
Action: Check the alert log on the primary database. Take the appropriate action to solve the problem.
Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.
Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.
Cause: An attempt was made to perform an online log file archival using a current control file. However, the USING BACKUP CONTROLFILE syntax was specified.
Action: If the archival operation is correct when using a current control file, then the USING BACKUP CONTROLFILE syntax is not required.
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.
Cause: Archiving not allowed of an empty or invalid log file.
Action: No action required.
Cause: The current log file cannot be archived using its file name.
Action: No action required.
Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.
Action: No action required.
Cause: Archiving not allowed of current log file.
Action: Check the alert log and archive trace files for additional information.
Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.
Action: Set the REMOTE_ARCHIVE_ENABLE parameter to true and restart this instance.
Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.
Action: Set the REMOTE_ARCHIVE_ENABLE parameter to false and restart this instance.
Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.
Action: If appropriate, change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to true and restart the standby database instance before further REDO log file archivals occur.
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.
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.
Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.
Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.
Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an operating system-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).
Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.
Cause: The specified archived log file was not found at the indicated standby destination.
Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.
Cause: No standby database archive log destinations were specified.
Action: Specify a standby archive log destination in the initialization parameter file.
Cause: Online log file archiving is disabled.
Action: Enable log file archiving.
Cause: There are no active ARCH processes.
Action: It is required that at least one ARCH process be active.
Cause: A standby database destination was specified that is not accessed by another instance.
Action: All database instances must access the same standby databases.
Cause: A standby database destination was specified that is not accessed by another instance.
Action: All database instances must access the same standby databases.
Cause: The database is not in ARCHIVELOG mode.
Action: Place the database in ARCHIVELOG mode.
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.
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.
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.
Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.
Action: Look in the trace file for more information.
Cause: Logical standby apply engine was started without creating a LogMiner session.
Action: Create a LogMiner session and restart the apply engine.
Cause: A logical standby apply engine was running when another was created.
Action: Shut down the previous apply engine before starting a new one.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The database was shut down while an online log file archival was active.
Action: No action required. The ARCH process is terminated.
Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.
Action: No action required.
Cause: No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode.
Action: Specify an alternate standby archive log destination in the initialization parameter file.
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.
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.
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.
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.
Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.
Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or re-specify the operation.
Cause: The option requested is not valid.
Action: Check spelling or refer to the Oracle9i SQL Reference for the correct statement syntax, then re-enter the request.
Cause: A Logical Standby apply operation is already running.
Action: no action required.
Cause: On the primary system, the log stream has been ended by the ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY statement.
Action: Issue one of the following statements to make this standby a primary or resume applying changes from a new primary:
ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
Cause: The current database has already been made a primary database.
Action: Issue the following statements to make this primary a standby:
ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
Cause: Log data from previous primary could not be completely applied.
Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, re-issue command.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Supplemental logging is not enabled at the primary database.
Action: Issue the following statement to enable supplemental logging:
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
Cause: An error occurred during a Terminal Recovery of the standby.
Action: Check the standby alert log additional information.
Cause: An error occurred during activation of the standby database following a Terminal Recovery.
Action: Check the standby alert log additional information.
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.
Cause: A mode other than NOWAIT follows the FINISH keyword in the RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or NOWAIT following FINISH.
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.
Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.
Action: No action 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.
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.
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.
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;
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.
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.
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: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.
Action: Remove one of the duplicate archive log destinations.
Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.
Action: No action required.
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.
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.
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.
Cause: Use of the indicated attribute is illegal in the given context.
Action: Make the appropriate changes and re-issue the statement.
Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.
Action: Remove the LGWR archive log dependency and use normal LGWR archival instead.
Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.
Action: Issue one of these operations following a FINISH recovery:
ALTER DATABASE OPEN READ ONLY; ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
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.
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.
Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.
Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.
Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary database is opened.
Cause: The LGWR network server could not attach to remote host.
Action: The alert log contains more problem-specific information.
Cause: The LGWR network server could not detach from remote host.
Action: The alert log contains more problem-specific information.
Cause: The LGWR lost its connection to the network server.
Action: The alert log contains more problem-specific information.
Cause: The LGWR network server could not communicate with the remote host.
Action: The alert log contains more problem-specific information.
Cause: The LGWR network server could not switch to non-blocking mode.
Action: The alert log contains more problem-specific information.
Cause: The LGWR network server could not switch to blocking mode.
Action: The alert log contains more problem-specific information.
Cause: The LGWR network server could not switch to blocking mode.
Action: The alert log contains more problem-specific information.
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.
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.
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.
Cause: One of two situations can cause this error:
An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.
Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.
Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.
Action: No action required.
Cause: An attempt was made to shut down a standby database while media recovery was active.
Action: Cancel media recovery to proceed with the shutdown.
Cause: See alert log for more details.
Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, then contact Oracle Support Services.
Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.
Action: No action required; this informational statement is provided to record the event for diagnostic purposes.
Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.
Action: No action required; this informational statement is provided to record the event for diagnostic purposes.
Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.
Action: No action required; this informational statement is provided to record the event for diagnostic purposes.
Cause: The skip procedure returned conflicting or invalid values.
Action: Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE, and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.
Cause: A DDL statement has successfully committed on the logical standby database.
Action: No action required; this informational statement is provided to record the event for diagnostic purposes.
Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped.
Action: No action required; this informational statement is provided to record the event for diagnostic purposes.
Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.
Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.
Cause: A dictionary build is currently in progress. Only one build can be active at a time.
Action: Wait for the active build to complete before invoking a new build.
Cause: Failure to start the logical standby dictionary build process (LSP1).
Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found.
Cause: The logical standby dictionary build process terminated abnormally.
Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found.
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.
Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.
Action:
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;current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record.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.
Cause: stop_on_ddl callout specified and DDL was encountered.
Action: Either disable stop_on_ddl callout or remove DDL.
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 Data Guard broker operation failed.
Action: See other messages for details.
Cause: The Data Guard broker operation succeeded with warnings.
Action: See other messages for details.
Cause: Number of sites in the Data Guard configuration has exceeded the limit.
Action: Delete unused sites.
Cause: A request to create a Data Guard configuration was made on a site that is part of an existing configuration.
Action: Delete the existing configuration if you desire to create a new configuration.
Cause: The request contained an invalid site ID.
Action: Make the request again with a valid site ID.
Cause: Process exceeded private or shared memory limits.
Action: Check for memory leaks, increase system parameters, and restart.
Cause: The specified request identifier was not recognized by the Data Guard broker.
Action: Re-issue the request using a valid request identifier.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: Non-blocking commands were issued but responses are not read or the commands did not complete execution.
Action: Read pending responses or delete outstanding requests and try again.
Cause: An attempt was made to read a response but a matching request was not found.
Action: Verify request identifier is valid and references a previously issued request.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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 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:
If this error is returned when attempting a resource state change operation, then make sure you specify a valid state for the resource.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: Total number of resource properties exceeded the limit.
Cause: A command or option is not supported in this release.
Action: Contact Oracle Support Services.
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.
Cause: The Data Guard broker was unable to allocate memory for a request.
Action: Increase the size of your SGA.
Cause: The Data Guard broker was unable to allocate a heap within the SGA.
Action: Increase SGA memory.
Cause: No space in PGA to allocate heap.
Action: Increase process virtual memory.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: A NULL buffer or a length of zero was specified.
Action: Correct command parameters and retry.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Data Guard configuration does not exist.
Action: Create a DRC prior to issuing other requests.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Data Guard broker returns this status when:
Action: Wait until the operation is complete and then re-issue the request.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Data Guard broker did not recognize the specified property or state name.
Action: Verify command parameters and re-issue the request.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
Cause: The site specified in the request is not enabled.
Action: Select an enabled site and re-issue the request.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Data Guard broker was unable to accept the request.
Action: Contact Oracle Support Services.
Cause: The Data Guard broker was unable to return the result of a previous request.
Action: Contact Oracle Support Services.
Cause: The piece of the request to return was not specified or is invalid.
Action: Specify the piece of the response starting from 1.
Cause: The Data Guard broker was unable to delete the given request.
Action: Contact Oracle Support Services.
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.
Cause: A request contains an invalid or NULL string value.
Action: Correct command parameters and retry.
Cause: A string property value was truncated due to insufficient buffer size.
Action: Specify a larger recieve buffer.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: An operation was attempted on a resource that is currently not active (off path).
Action: Verify that the resource is active.
Cause: An attempt was made to create a duplicate resource.
Action: Check the resource to be added and be sure there are no duplicates.
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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: The submitted XML document is not supported.
Action: Correct the errors and resubmit the request.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
Cause: The requested operation requires the Data Guard configuration to be enabled.
Action: Enable the Data Guard configuration and re-issue the request.
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.
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.
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.
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.
Cause: Switchover fails because the primary database resource and/or the designated standby database resource are offline.
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.
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.
Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.
Action: Contact Oracle Support Services.
Cause: The Data Guard broker detected errors while loading the configuration file.
Action: Contact Oracle Support Services.
Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Data Guard broker was unable to update the configuration file on a particular site.
Action: Verify that your Oracle Net connections are operational between the Data Guard sites.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: See trace file.
Action: Contact Oracle Support Services.
Cause: The Data Guard Connection Process (DRCX) detected an error while transferring data from one site to another. This error is returned in the following situations:
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error at the given token.
Action: Correct the errors and resubmit the request.
Cause: There was an error in the XML request document.
Action: Correct the errors and resubmit the request.
Cause: The Data Guard NetSlave (NSV*) processes discovered that the Data Guard broker process (DMON) is not running.
Action: Check the Data Guard console log and DMON process trace file to determine why the DMON process is missing.
Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.
Action: Contact Oracle Support Services.
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.
Cause: The Data Guard broker has detected two or more primaries in the configuration and cannot continue.
Action: Contact Oracle Support Services.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The named property does not exist.
Action: Specify a valid property name and re-issue the request.
Cause: The Data Guard broker detected a failure on one or more sites.
Action: Locate the sites with a failure status and correct it.
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.
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.
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.
Cause: The Data Guard broker aborted an operation at the user's request.
Action: No action required.
Cause: The string value for the named attribute is too long.
Action: Use a shorter string.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:
Action: To correct the problem, try one of these actions:
HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.Cause: This status is returned in the following situations:
Action:
Cause: The Data Guard Broker protection mode saved in metadata is inconsistent with the actual database setting.
Action: Reset the protection mode through the Data Guard Broker.
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.
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.
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.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: No resource guard is available to service the request.
Action: Contact Oracle Support Services.
Cause: The value specified in the request is invalid.
Action: Check value and re-issue the request.
Cause: The state name specified is invalid for the resource.
Action: Check the state name and re-issue 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.
Cause: The resource guard was unable to allocate memory while trying to service a request.
Action: Disable the configuration, shutdown oracle, increase SGA size, and restart.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The resource guard timed out while servicing the request.
Action: Verify that the operation is valid for the resource and then re-issue the request.
Cause: The resource guard exceeded its retry limit while trying to service a request.
Action: Verify that the resource is operational and then re-issue the request.
Cause: The resource guard could not execute the request since the logical standby database requires instantiation.
Action: Instantiate logical standby on the site and then re-issue the request.
Cause: An attempt to clear the LOG_ARCHIVE_DEST initialization parameter failed.
Action: Contact Oracle Support Services.
Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST initialization parameter failed.
Action: Contact Oracle Support Services.
Cause: The resource guard was unable to locate the database resource in the configuration.
Action: Add the database resource and then re-issue the request.
Cause: A SQL statement to query V$ARCHIVE_DEST failed.
Action: Test and clear the problem using SQL*Plus.
Cause: All LOG_ARCHIVE_DEST_n parameters have been defined.
Action: Set some of the LOG_ARCHIVE_DEST_n parameters to an empty string.
Cause: An attempt of setting some of the LOG_ARCHIVE_DEST_n parameters failed.
Action: Check the Data Guard console log and database alert logs for further details.
Cause: An attempt of setting some of the LOG_ARCHIVE_DEST_STATE_n parameters failed.
Action: Check the Data Guard console log and database alert logs for further details.
Cause: The resource guard was unable to locate a connect descriptor to a certain standby site in V$ARCHIVE_DEST.
Action: Check the Data Guard console log for further details. One may need to reset log transport service.
Cause: The intended state of the resource has been set to offline.
Action: If resource is managed, change intended state to online.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The resource guard could not close the database.
Action: If there are any active sessions connected to the database, then terminate them and re-issue the request.
Cause: The resource guard could not set the log archive destination.
Action: Check the Data Guard console log and the Oracle Alert log for further details.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Logical standby package may not be installed.
Action: Install logical standby packages and re-issue the request.
Cause: Resource guard could not set the standby log archive destination parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set the log archive format parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set the database file name convert parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set log file name convert parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set log archive trace parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set the control files parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set lock name trace parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set FAL client parameter.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not set FAL server.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not dismount database.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not mount database.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not turn on the logical standby guard.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not open database.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not prepare to switch to logical primary.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not activate logical primary.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not prepare to switch to primary.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not mount standby.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not open standby database.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not activate standby.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not dismount standby.
Action: Check the Data Guard console log for further details.
Cause: Resource guard could not open standby read-only.
Action: Check the Data Guard console log for further details.
Cause: Resource guard failed to get property.
Action: Check the Data Guard console log for further details.
Cause: Resource guard failed to verify property.
Action: Check the Data Guard console log for further details.
Cause: Resource guard failed to start logical apply engine with an initial SCN.
Action: Check the Data Guard console log for further details.
Cause: Resource guard failed to start logical apply engine.
Action: Check the Data Guard console log for further details.
Cause: Resource guard failed to stop logical apply engine correctly.
Action: Check the Data Guard console log for further details.
Cause: Database is not in the intended state.
Action: Determine the reason for invalid state, and re-issue get status request.
Cause: Log transport service for some site is online when it should be offline.
Action: Check the Data Guard console log for further details. If necessary, stop the log transport service for the site.
Cause: Log transport service for some site is offline when it should be online.
Action: Check the Data Guard console log for further details. If necessary, start the log transport service.
Cause: Physical apply service is online when it should be offline.
Action: If necessary, stop the physical apply service.
Cause: Physical apply service is offline when it should be online.
Action: If necessary, start the physical apply service.
Cause: Logical apply service is online when it should be offline.
Action: If necessary, stop the logical apply service.
Cause: Logical apply service is offline when it should be online.
Action: If necessary, start the logical apply service.
Cause: There was an error executing dbms_logstdby$apply_set procedure.
Action: Check the values for the property, and set configuration property again.
Cause: There was an error executing dbms_logstdby$apply_unset procedure.
Action: Check the values for the property, and set configuration set property again.
Cause: There was an error starting the archival processes.
Action: Check the Data Guard console log for further details.
Cause: There was an error during switchover of primary and standby databases.
Action: Check the Data Guard console log for further details.
Cause: There was an error in starting the physical apply service (MRP process).
Action: Check the Data Guard console log for further details.
Cause: There was an error in stopping the physical apply service (MRP process).
Action: Check the Data Guard console log for further details.
Cause: The physical apply service terminated prematurely with an error.
Action: Check the Data Guard console log and Oracle Alert log for further details.
Cause: Due to some internal failure, the database resource guard cannot complete the health check of the log transport service.
Action: Check the Data Guard console log and Oracle Alert log for further details.
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.
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.
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.
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.
Cause: Log transport to some site has an unknown status.
Action: Check the Data Guard console log and Oracle Alert log for further details.
Cause: Log transport cannot be turned on because some critical property values cannot be retrieved from Data Guard metadata.
Action: Check the Data Guard console log and Oracle Alert log for further details.
Cause: Log transport cannot be turned on because some critical property has not been set.
Action: Check the Data Guard console log to see which property has not been set, and set it properly.
Cause: Site name provided in property Dependency or Alternate is wrong.
Action: Reset property to the correct name of the site.
Cause: The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to the primary database.
Action: Reset the primary database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG statement.
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.
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:
Action: Check the Data Guard console log to see which property has the problem and reset the property correctly.
Cause: Standby redo logs are missing when needed for certain log transport modes.
Action: Check the Data Guard documentation to create standby redo logs on the standby.
Cause: An invalid property value was entered.
Action: Reset the value to a correct one.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Action: Check Data Guard console log for more details. Issue ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.
Cause: An attempt to issue an ALTER DATABASE SET STANDBY TO ... statement failed.
Action: Check database alter logs and Data Guard console logs for more information.
Cause: The client could not be initialized.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The database environment could not be allocated and initialized.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The database handles could not be allocated.
Action: This is an internal error. Contact Oracle Support Services.
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.
Cause: The server attributes could not be set.
Action: check additional error messages.
Cause: The given action failed.
Action: check additional error messages.
Cause: No memory was available for the program.
Action: Increase memory and try again.
Cause: A required field was missing.
Action: Type "help" for syntax and try again.
Cause: The given option is not supported.
Action: Try again using the proper command line syntax.
Cause: A fatal error was encountered.
Action: See additional error messages and contact Oracle Support Services.
Cause: Commands cannot be issued to the server.
Action: See additional error messages and contact Oracle Support Services.
Cause: An action succeeded with warnings.
Action: See error message and take appropriate action.
Cause: An unknown command was issued.
Action: Try again using a valid command.
Cause: The connect string for the database is missing.
Action: Try the command again with a valid connect string.
Cause: The site name is missing.
Action: Try the command again using correct syntax.
Cause: The XML document argument was missing.
Action: Try the command again using correct syntax.
Cause: The named site could not be started in the primary role.
Action: See additional messages.
Cause: The named site was started as the new primary site.
Action: No action is required.
Cause: The named site could not be started in the standby role.
Action: See additional messages..
Cause: The named site was started as the new primary site.
Action: No action required.
Cause: The failover operation succeeded.
Action: No action required.
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.
Cause: The named site could not be found.
Action: Try the command again using a valid site.
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.
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.
Cause: The named resource was not found.
Action: Try the command again using a valid resource.
Cause: The named object could not be retrieved for editing.
Action: Contact Oracle Support Services.
Cause: The manager information could not be retrieved for a generic resource.
Action: Contact Oracle Support Services.
Cause: The configuration could not be described.
Action: The framework could not be contacted. Check to see that the DMON process is running.
Cause: The named site or resource does not exist.
Action: Try the command again using a valid site or resource.
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.
Cause: The template could not be found.
Action: See additional error messages.
Cause: The template name was omitted from the command.
Action: Try the command again using a valid template name.
Cause: The named template could not be found.
Action: Try the command again using a valid template name.
Cause: The document could not be converted.
Action: Contact Oracle Support Services.
Cause: No answer came from the framework.
Action: The framework is not available. Check to see that the DMON process exists.
Cause: The status could not be retrieved.
Action: The framework is not available. Check to see that the DMON process exists.
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.
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.
Cause: An error returned by ODM library
Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance.
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.
Cause: file creation failed due to either insufficient OS permission or the file already exists
Action: check additional error messages
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
Cause: The file thats being deleted is still in use or the process has insufficient permission to delete file.
Action: check additional error messages
Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.
Action: check additional error messages
Cause: The i/o request is marked with error because the i/o error simulation event is turned on.
Action: none
Cause: i/o's are done in multiple of logical block size
Action: Check additional error messages
Cause: i/o request buffer should be alligned, check additional information for buffer ptr value
Action: Contact Oracle Support Services.
Cause: When a file is identified with logical block size of 0, only i/o's to block1 is allowed.
Action: check additional error messages and contact Oracle Support Services.
Cause: The i/o request points to a block beyond End Of File
Action: check additional error messages and contact Oracle Support Services.
Cause: An attempt to create a file a file found neither an existing file nor a size for creating the file.
Action: Specify a size for the file.
Cause: An attempt to write to a file which has gone offline/unidentified.
Action: Check for other errno in the stack.
Cause: The parser detected a missing or invalid outline name.
Action: reissue the command, specifying a valid outline name.
Cause: The parser detected that no clause was specified on the command.
Action: reissue the command, specifying a valid ALTER OUTLINE clause.
Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.
Action: Check for the existence of the outline and try again.
Cause: The signature generation algorithm generates signatures that are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.
Action: Either reissue the statement that led to the outline being created with some white space added or force the outline to be created in a different category.
Cause: An outline already exists, either with the specified name, or for the specified SQL text.
Action: Try again with another name.
Cause: Create any outline privilege is required for the attempted operation.
Action: Make sure you have create any outline privilege and retry the operation.
Cause: Drop any outline privilege is required for the attempted operation.
Action: Make sure you have drop any outline privilege and retry the operation.
Cause: Alter any outline privilege is required for the attempted operation.
Action: Make sure you have alter any outline privilege and retry the operation.
Cause: The database creation script that creates this schema must not have been executed.
Action: Review the log files to see what happened when the database was created.
Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table.
Action: Review the log files to see what happened when the database was created.
Cause: User failed to specify the CATEGORY keyword.
Action: reissue the command with the CATEGORY keyword included.
Cause: User imported an 8i outline into a 9i database without updating signatures.
Action: Execute dbms_outln.update_signatures.
Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.
Action: Supply the RELATIONAL keyword in the storage clause
Cause: An invalid storage option was specified for the XMLType.
Action: Supply a valid storage option.
Cause: A XML schema URL must be specified in the storage option.
Action: Specify a URL for the XMLSchema.
Cause: A root element in the XMLSchema must be specified if the XML schema is given.
Action: Specify a root element in the XML schema.
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
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
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.
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.
Cause: The XMLSchema keyword is missing
Action: Specify the XMLSchema URL and element name.
Cause: XML fragments got from extractNode cannot be inserted into the database.
Action: Convert the fragment into a proper XML document before insertion.
Cause: The string result asked for is too big to return back
Action: Get the result as a lob instead
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.
Cause: An attempt was made to create a VARRAY column which contains a XMLType
Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead
Cause: An invalid XML identifier was detected during XML generation.
Action: Fix the offending tag so it does not contain characters or symbols that are not allowed by the XML specification.
Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML.
Action: Change the order of the types so that the attributes occur at the beginning.
Cause: Attribute values can only be simple scalar values.
Action: Use only simple datatypes for attribute values.
Cause: A tag name was found to have an invalid XML character during XML generation.
Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table.
Action: You can only dereference the attributes of a base table XMLType column.
Cause: The first argument passed to the update value operator was not an XMLTYPE.
Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
Cause: Given XPath points to more than one node.
Action: Rewrite the query so that exactly one node is returned.
Cause: Given XPath does not point to a leaf node.
Action: Rewrite the query so that a leaf node is returned.
Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.
Action: Pass an object of the correct type to toObject().
Cause: The passed in XMLType could not be converted to the required type.
Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.
Cause: The method can be invoked on only schema based xmltype objects.
Action: Don't invoke the method for non schema based xmltype objects.
Cause: The passed in XML tag does not match any in the object type.
Action: Pass a valid canonical XML that can map to the given object type.
Cause: When converting XML to object, a wrong tag name was present.
Action: Pass a valid canonical XML that can map to the given object type
Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the 'schema' parameter.
Action: Change the schema parameter to match the schema specified in the XML document.
Cause: The object type contained a type that is not supported for schema generation.
Action: Use a different type or do not generate a schema.
Cause: All input arguments must be valid columns
Action: Specify a valid list of columns
Cause: The particular datatype is not supported in the XMLGEN operator
Action: Specify only supported datatypes as arguments to the XMLGEN operator
Cause: An error occurred when processing the XML function
Action: Check the given error message and fix the appropriate problem
Cause: An error occurred when processing the DBMS_XMLGEN functions
Action: Check the given error message and fix the appropriate problem
Cause: Only scalar values (that is values which are not of object or collection type) can be marked as XML attribute, that is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'.
Action: Remove the '@' sign, or make the value a scalar.
Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.
Action: Remove the '@' sign, or make the previous value a scalar.
Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query or REF CURSOR.
Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
Action: Remove the AS clause of the scalar element.
Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.
Action: Specify an alias for the expression using the AS clause.
Cause: An invalid or unsupported formatting argument was supplied.
Action: Change the formatting argument to legal supported values.
Cause: An error occurred when processing the URL
Action: Check the given error message and fix the appropriate problem
Cause: A host name was not specified in the HTTP url
Action: Specify a host name in the HTTP url when creating the URL string
Cause: A HTTP connection could not be opened to the host
Action: Specify a valid host name and port to connect to
Cause: An error occurred while reading from the HTTP host
Action: Specify a valid host name and port to read from
Cause: The URL must be a valid URL string
Action: Specify a valid url string
Cause: The type required for the CREATE_DBURI operator has not been installed correctly.
Action: Read the installation notes to install the type correctly.
Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.
Action: Specify a valid column name in the query.
Cause: The argument to the CREATE_DBURI operator can only be a column.
Action: Specify a valid column name for the operator
Cause: The flags argument given to the DBURI operator is invalid
Action: Specify a valid flag value (TEXT) for the DBURI operator
Cause: All columns must be valid and pointing to the same table or view
Action: Specify valid list of columns that are from the same table or view.
Cause: An invalid format type object was specified for the XML function
Action: Specify a valid format type object
Cause: The XML being generated does not have an enclosing root element.
Action: The generated XML must have a root element.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|