Oracle Error Messages: 04/11/12

Wednesday, 11 April 2012

ORA-22871: ALTER TYPE with REPLACE is not allowed for pure incomplete types

ORA-22871: ALTER TYPE with REPLACE is not allowed for pure incomplete types

Cause: An attempt to perform ALTER TYPE with REPLACE option for a pure incomplete type

Action: Completely define the original type, before using the ALTER TYPE with REPLACE option.

ORA-22870: ALTER TYPE with REPLACE option a non-object type

ORA-22870: ALTER TYPE with REPLACE option a non-object type

Cause: attempt to perform ALTER TYPE with REPLACE option a non-object type

Action: drop the non-object type first, then re-create it as an object type

ORA-22869: depth of type dependency hierarchy exceeds maximum limit

ORA-22869: depth of type dependency hierarchy exceeds maximum limit

Cause: The type dependency hierarchy was structured to have depth greater than 1,024

Action: Re-structure the type dependency hierarchy to a shorter depth.

ORA-22868: table with LOBs contains segments in different tablespaces

ORA-22868: table with LOBs contains segments in different tablespaces

Cause: An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment.

Action: Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace.

ORA-22866: default character set is of varying width

ORA-22866: default character set is of varying width

Cause: A character LOB was defined but the default character set is not fixed width.

Action: Ensure that the character set is of fixed width before defining character LOBs.

ORA-22865: more than one column specified

ORA-22865: more than one column specified

Cause: An attempt was made to specify multiple columns where only one is allowed.

Action: Specify a single column and retry the operation.

ORA-22864: cannot ALTER or DROP LOB indexes

ORA-22864: cannot ALTER or DROP LOB indexes

Cause: An attempt was made to ALTER or DROP a LOB index.

Action: Do not operate directly on the system-defined LOB index. Perform operations on the corresponding LOB column.

ORA-22863: synonym for datatype string.string not allowed

ORA-22863: synonym for datatype string.string not allowed

Cause: A synonym specification for a datatype is not supported

Action: do not use the synonym for the datatype

ORA-22862: specified object identifier doesn t match existing object identifier

ORA-22862: specified object identifier doesn t match existing object identifier

Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name.

Action: Specify the correct object identifier or leave it out of the statement.

ORA-22861: invalid user-defined type

ORA-22861: invalid user-defined type

Cause: An attempt was made to create a column or object table of a non- existent type.

Action: Specify a valid type in the table or column definition.

ORA-22860: object type expected

ORA-22860: object type expected

Cause: An attempt was made to create an object table using a non- object type, or to create a column that is a REF to a non-object type.

Action: Use a valid object type in the table or column definition.

ORA-22859: invalid modification of columns

ORA-22859: invalid modification of columns

Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type.

Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.

ORA-22858: invalid alteration of datatype

ORA-22858: invalid alteration of datatype

Cause: An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type.

Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.

ORA-22857: cannot modify columns of object tables

ORA-22857: cannot modify columns of object tables

Cause: An attempt was made to alter the object table by modifing existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type.

Action: Create a new type with the desired attribute types and use it to create an object table. The new object table will have the desired columns.

ORA-22856: cannot add columns to object tables

ORA-22856: cannot add columns to object tables

Cause: An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type.

Action: Create a new type with additional attributes, and use the new type to create an object table. The new object table will have the desired columns.

ORA-22855: optional name for LOB storage segment incorrectly specified

ORA-22855: optional name for LOB storage segment incorrectly specified

Cause: The optional name for LOB storage segment was specified with multiple columns in the column list.

Action: Specify each column LOB storage only with optional name(s).

ORA-22854: invalid option for LOB storage index

ORA-22854: invalid option for LOB storage index

Cause: A valid LOB store index option was not specified.

Action: Specify one of (INITRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index.

ORA-22853: invalid LOB storage option specification

ORA-22853: invalid LOB storage option specification

Cause: A LOB storage option was not specified

Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX as part of the LOB storage clause.

ORA-22852: invalid PCTVERSION LOB storage option value

ORA-22852: invalid PCTVERSION LOB storage option value

Cause: The specified PCTVERSION LOB storage option value must be an integer.

Action: Choose an appropriate integer value and retry the operation.

ORA-22851: invalid CHUNK LOB storage option value

ORA-22851: invalid CHUNK LOB storage option value

Cause: The specified CHUNK LOB storage option value must be an integer.

Action: Choose an appropriate integer value and retry the operation.

ORA-22850: duplicate LOB storage option specificed

ORA-22850: duplicate LOB storage option specificed

Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once.

Action: Specify all LOB storage options only once.

ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)

ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)

Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where the LOB size was bigger than the buffer limit for CHAR and RAW types. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes.

Action: Do one of the following: 1. Make the LOB smaller before performing the conversion, for example, by using SUBSTR on CLOB 2. Use DBMS_LOB.SUBSTR to convert CLOB to CHAR or BLOB to RAW.

ORA-22833: Must cast a transient type to a persistent type

ORA-22833: Must cast a transient type to a persistent type

Cause: An attempt was made to use the transient type in the query result.

Action: Cast the transient type to a structurally equivalent persistent type.

ORA-22828: input pattern or replacement parameters exceed 32K size limit

ORA-22828: input pattern or replacement parameters exceed 32K size limit

Cause: Value provided for the pattern or replacement string in the form of VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit.

Action: Use a shorter pattern or process a long pattern string in multiple passes.

ORA-22826: cannot construct an instance of a non instantiable type

ORA-22826: cannot construct an instance of a non instantiable type

Cause: An attempt was made to use a non instantiable type as a constructor.

Action: None.

ORA-22819: scope of input value does not correspond to the scope of the target

ORA-22819: scope of input value does not correspond to the scope of the target

Cause: An attempt to operate on a REF value scoped to a different table than the expected one

Action: Use a ref which is scoped to the expected table and retry the operation

ORA-22818: subquery expressions not allowed here

ORA-22818: subquery expressions not allowed here

Cause: An attempt was made to use a subquery expression where these are not supported.

Action: Rewrite the statement without the subquery expression.

ORA-22817: subquery not allowed in the default clause

ORA-22817: subquery not allowed in the default clause

Cause: An attempt was made to use a subquery in the column default clause expression.

Action: Remove the subquery from the default clause.

ORA-22816: unsupported feature with RETURNING clause

ORA-22816: unsupported feature with RETURNING clause

Cause: RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and INSTEAD OF Triggers.

Action: Use separate select statement to get the values.

ORA-22814: attribute or element value is larger than specified in type

ORA-22814: attribute or element value is larger than specified in type

Cause: Value provided for the object type attribute or collection element exceeded the size specified in the type declaration.

Action: Choose another value and retry the operation.

ORA-22813: operand value exceeds system limits

ORA-22813: operand value exceeds system limits

Cause: Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size might be too big for available memory.

Action: Choose another value and retry the operation.

ORA-22812: cannot reference nested table column s storage table

ORA-22812: cannot reference nested table column s storage table

Cause: An attempt to access the nested table column s storage table is not allowed in the given context.

Action: Issue the statement against the parent table containing the nested table column.

ORA-22810: cannot modify object attributes with REF dereferencing

ORA-22810: cannot modify object attributes with REF dereferencing

Cause: An attempt was made to modify the attributes an object by dereferencing a REF column in an UPDATE statement.

Action: Update the table containing the object that the REF points to, or change the REF column to an object type column.

ORA-22809: nonexistent attribute

ORA-22809: nonexistent attribute

Cause: An attempt was made to access a non-existent attribute of an object type.

Action: Check the attribute reference to see if it is valid. Then retry the operation.

ORA-22808: REF dereferencing not allowed

ORA-22808: REF dereferencing not allowed

Cause: An attempt was made to access an object type s attributes by dereferencing a REF item.

Action: Make the item an object type instead of a REF to an object type.

ORA-22807: cannot resolve to a scalar type or a collection type

ORA-22807: cannot resolve to a scalar type or a collection type

Cause: Invalid use of a non-scalar (for example, object type) item.

Action: Change the item s data type and retry the operation.

ORA-22806: not an object or REF

ORA-22806: not an object or REF

Cause: An attempt was made to extract an attribute from an item that is neither an object nor a REF.

Action: Use an object type or REF type item and retry the operation.

ORA-22805: cannot insert NULL object into object tables or nested tables

ORA-22805: cannot insert NULL object into object tables or nested tables

Cause: An attempt was made to insert a NULL object into an object table or a Nested Table.

Action: Ensure that a non-NULL object is inserted into the table or insert an object with attributes whose values are NULL.

ORA-22804: remote operations not permitted on object tables or user-defined type columns

ORA-22804: remote operations not permitted on object tables or user-defined type columns

Cause: An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY.

Action: none

ORA-22803: object type contains zero attributes

ORA-22803: object type contains zero attributes

Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context.

Action: specify a valid object type

ORA-22801: invalid object row variable

ORA-22801: invalid object row variable

Cause: The specified object row variable is not available in the scope of name resolution.

Action: Verify the specified object row variable is correct, or use an object row variable visible in scope.

ORA-22800: invalid user-defined type

ORA-22800: invalid user-defined type

Cause: An attempt was made to use an incomplete type as a constructor.

Action: Complete the type definition before using it in a query.

ORA-22634: Error adding new instance to AnyDataSet

ORA-22634: Error adding new instance to AnyDataSet

Cause: Current instance in the AnyDataSet has not been fully constructed.

Action: Make sure that the current instance is fully constructed before adding new instance.

ORA-22633: Error freeing AnyDataSet

ORA-22633: Error freeing AnyDataSet

Cause: AnyDataSet that is passed in may not be valid.

Action: Check all the AnyDataSet parameters.

ORA-22632: AnyDataSet parameter is not valid for the current operation

ORA-22632: AnyDataSet parameter is not valid for the current operation

Cause: The AnyDataSet parameter is null or it is somehow invalid for the current operation.

Action: Check the documentation for the current operation.

ORA-22631: attribute (string( is is not well-formed or does not match the type

ORA-22631: attribute (string( is is not well-formed or does not match the type

Cause: Passing an attribute that is not well-formed or does not match the input type.

Action: Make sure the attribute is well-formed and matches the type specified.

ORA-22630: attribute (string( is null or it is not well-formed

ORA-22630: attribute (string( is null or it is not well-formed

Cause: Passing an attribute that is null or not well-formed

Action: Make sure the attribute is not null or is well-formed.

ORA-22629: OCIAnyData is null

ORA-22629: OCIAnyData is null

Cause: Attempting an operation that is not valid on null OCIAnyData

Action: Make sure OCIAnyData is not null.

ORA-22628: OCIAnyData already constructed

ORA-22628: OCIAnyData already constructed

Cause: Attempt to add attributes to OCIAnyData that is already constructed.

Action: Use the OCIAnyData that is initialized but not yet constructed.

ORA-22627: tc (string( must be that of object or varray or nested table

ORA-22627: tc (string( must be that of object or varray or nested table

Cause: Type code is not that of object or varray or nested table

Action: Make sure the type code is OCI_TYPECODE_OBJECT or OCI_ TYPECODE_VARRAY or OCI_TYPECODE_TABLE

ORA-22626: Type Mismatch while constructing or accessing OCIAnyData

ORA-22626: Type Mismatch while constructing or accessing OCIAnyData

Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute.

Action: Make sure the type supplied matches the type of object to to be constucted or accessed.

ORA-22625: OCIAnyData is not well-formed

ORA-22625: OCIAnyData is not well-formed

Cause: Attempt to use the OCIAnyData without initializing constructing it.

Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is adding attributes. Use OCIAnyDataEndConstruct to complete the construction. Or use OCIAnyDataConvert to do the construction. MAke sure it is properly constructed before accessing attributes.

ORA-22621: error transfering an object from the agent

ORA-22621: error transfering an object from the agent

Cause: Any error returned from pickler routines on the agent side.

Action: Contact Oracle Support.

ORA-22620: buffer size too small to hold the value

ORA-22620: buffer size too small to hold the value

Cause: Buffer size is not enough to hold the value. Most likely while doing the character set conversion, a bigger buffer is needed.

Action: Pass in a bigger buffer. If the client character set format differs from that of server, doing the conversion may result in 4X expansion.