Oracle 11g Error Codes and Solution Suggestions from ORA-22300 to ORA-22700
- ORA-22303: type “string”.”string” not found
- Cause: The user is trying to obtain information for a type that cannot be found.
- Action: Check that the schema is correct and that the type has been created correctly.
- ORA-22304: input type is not an object type
- Cause: The user is trying to obtain the supertype information for a non-object type.
- Action: Pass in only an object type.
- ORA-22305: attribute/method/parameter “string” not found
- Cause: Type element with the given name is not found in the type.
- Action: Check to make sure that the type element exists.
- ORA-22306: type “string“.”string” already exists
- Cause: The user is trying to create a type that already exists.
- Action: Check to make sure that the type has not been created prior to this.
- ORA-22307: operation must be on a user-defined type
- Cause: attempt to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type.
- Action: Check to make sure that only user-defined types are being operated on.
- ORA-22308: operation not allowed on evolved type
- Cause: An attempt was made to replace a type whose attribute definition been been altered.
- Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE REPLACE.
- ORA-22309: attribute with name “string” already exists
- Cause: The user is attempting to create an object type where more than one attributes have the same name.
- Action: Check to make sure that all attribute names are unique.
- ORA-22310: ALTER TYPE error. Refer to table “string“.”string” for errors
- Cause: An invalid alter type statement was submitted.
- Action: Correct the errors listed in specified table and resubmit statement.
- ORA-22311: type for attribute “string” does not exist
- Cause: The type of the attribute does not exist.
- Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute’s type in the DDL transaction.
- ORA-22312: must specify either CASCADE or INVALIDATE option
- Cause: An attempt was made to alter a type which has a dependent type or table without specifying the CASCADE or INVALIDATE option.
- Action: Resubmit the statement with either the CASCADE or INVALIDATE option. Specify CASCADE if you want to cascade the type change to dependent types and tables; otherwise, specify INVALIDATE to invalidate all dependents.
- ORA-22313: cannot use two versions of the same type “string“
- Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type.
- Action: Check that the libraries being linked with this application and use the same versions of the type.
- ORA-22314: method information mismatch in ALTER TYPE
- Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported.
- Action: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods.
- ORA-22315: type “string” does not contain a map or order function
- Cause: The input type does not contain a map or order function so one cannot be returned.
- Action: Add a map or order function to the type or catch this error.
- ORA-22316: input type is not a collection type
- Cause: The user is trying to obtain information for collection types on a non-named collection type.
- Action: Use a named collection type for the function.
- ORA-22317: typecode string is not legal as a number type
- Cause: The user is trying to use a number typecode that is not valid.
- Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.
- ORA-22318: input type is not an array type
- Cause: The user is trying to obtain the number of elements for a non-array type.
- Action: Pass in only a named collection type which is an array.
- ORA-22319: type attribute information altered in ALTER TYPE
- Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added.
- Action: Check that all type alterations are legal.
- ORA-22320: missing user version string
- Cause: The VERSION option is specified without a user version string.
- Action: Resubmit the statement with the version string following the VERSION keyword.
- ORA-22321: method does not return any result
- Cause: OCITypeResult() was called on a method that does not return any results.
- Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly.
- ORA-22322: error table “string“.”string” has incorrect structure
- Cause: The specified error table does not have the expected table structure.
- Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure to create an error table, then resubmit the statement using the new error table.
- ORA-22323: error table “string“.”string” does not exist
- Cause: The error table does not exist.
- Action: Resubmit the statement with a correct error table name.
- ORA-22324: altered type has compilation errors
- Cause: The use of the ALTER TYPE statement caused a compilation error.
- Action: Correct the error reported and resubmit the statement.
- ORA-22326: cannot change a type to FINAL if it has subtypes
- Cause: An attempt was made to change a type with subtypes to FINAL.
- Action: Drop all subtypes of the target type before changing it to FINAL.
- ORA-22327: cannot change a type to NOT INSTANTIABLE if it has dependent tables
- Cause: An attempt was made to change a type with dependent tables to NOT INSTANTIABLE.
- Action: Drop all dependent tables of the target type and resubmit the statement.
- ORA-22328: object “string“.”string” has errors. string
- Cause: Altering the target type causes errors in its dependent object.
- Action: Correct the problem in the dependent object and resubmit the statement.
- ORA-22329: cannot alter a non-object type
- Cause: An attempt was made to execute ALTER TYPE on a non-object type.
- Action: Drop the non-object type first, then re-create it as an object type.
- ORA-22330: cannot alter a type that is not valid
- Cause: An attempt was made to perform ALTER TYPE on an invalid type.
- Action: Use the CREATE OR REPLACE TYPE command to modify the type.
- ORA-22331: cannot alter an incomplete type
- Cause: An attempt was made to perform ALTER TYPE on an incomplete type.
- Action: Use CREATE TYPE to completely define the original type before executing the ALTER TYPE.
- ORA-22332: a dependent object in schema “string” has errors. string
- Cause: Altering the target type causes errors in its dependent object.
- Action: Correct the problem in the dependent object and resubmit the statement.
- ORA-22333: cannot reset type “string“.”string” due to invalid dependent types and tables
- Cause: An attempt was made to reset the type version with invalid dependent types and tables.
- Action: Use the ALTER TYPE COMPILE statement to compile all invalid dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA to upgrade all the dependent tables then resubmit the statement.
- ORA-22334: cannot reset type “string“.”string“. Dependent tables must be upgraded to latest version
- Cause: An attempt was made to reset the type version when the data in the dependent table has not been upgraded to the latest type version.
- Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement.
- ORA-22335: The client cannot work with an altered type
- Cause: A pre 8.2 client has requested a type that has been altered on the server.
- Action: Only 8.2 or higher clients could access altered types
- ORA-22336: table contained 8.0 image format, must specify INCLUDING DATA
- Cause: One of the following: 1) An attempt was made to alter a type with a dependent table in 8.0 image format and the NOT INCLUDING TABLE DATA option was specified. 2) An attempt was made to upgrade a table in 8.0 image format with the NOT INCLUDING DATA option specified.
- Action: Resubmit the statement with INCLUDING DATA option.
- ORA-22337: the type of accessed object has been evolved
- Cause: The type of the accessed object has been altered and the client’s object is based on an earlier type definition.
- Action: The user needs to exit application and modify application to accommodate the type change. From SQL/PLUS, reconnect and resubmit statement.
- ORA-22338: must specify CASCADE INCLUDING DATA when altering the final property
- Cause: An attempt was made to alter the final property of a type with dependent table(s) without specifying the CASCADE INCLUDING DATA . option.
- Action: Resubmit the statement with the CASCADE INCLUDING DATA option.
- ORA-22339: cannot alter to not final since its attribute column is substitutable
- Cause: An attempt was made to alter a type to not final when its embedded attribute is defined as substitutable in some tables. Note, this is a restriction in 9.0 version because when a type is altered to not final, column of that type is set to not substitutable at all levels; thus, it is an error if one of its embedded attribute column is already marked substitutable.
- Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS for all columns of non final type. Then resubmit the ALTER TYPE statement.
- ORA-22340: cannot string type “string“.”string“. Dependent tables must be upgraded to latest version
- Cause: An attempt was made to reset the version, drop or alter a type when the data in dependent table has not been upgraded to the latest version.
- Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement.
- ORA-22341: cannot assign supertype instance to subtype
- Cause: An attempt was made to assign or copy a supertype instance to a container (destination) that can only hold a subtype instance.
- Action: Make sure the runtime type of the source of the assignment or copy is the same type as the destination or is a subtype of the destination type
- ORA-22342: dependent VARRAY column exceeds the maximum inline column size
- Cause: An attempt was made to alter a type (add or modify attribute) which causes the size of its dependent VARRAY column to exceed the maximum inline column size. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created.
- Action: Specify the VARRAY column to be stored as LOB at the table level when the table is created.
- ORA-22343: Compilation error for type invalidated by ALTER TYPE
- Cause: Compilation failed for a type which was invalidated by ALTER TYPE. We throw this error and rollback the compilation effort so that the user may be able to fix whatever is causing the compilation error and try again. It is important that we do not chnage status here and modify the dependency information as this will affect the creation of versions.
- Action: Check what is causing teh compilation error and correct it and try again.
- ORA-22344: can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
- Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change.
- Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT FINAL change.
- ORA-22345: recompile type string.string before attempting this operation
- Cause: An attempt was made to perform an operation which requires the specified datatype to be valid, but the datatype is invalid
- Action: Recompile the specified type and retry the operation
- ORA-22346: Type has cyclical dependency. Should use CASCADE option
- Cause: An attempt was made to alter a type which has a cyclical dependency, with invalidate option.
- Action: Give CASCADE option instead of INVALIDATE
- ORA-22347: No changes to type specified for ALTER TYPE
- Cause: The ALTER TYPE does not contain any changes to the type.
- Action: If any change is required for the type, modify the ALTER TYPE to specify the change. Else no need for the ALTER.
- ORA-22348: The object type DDL is not supported in Editioned schema
- Cause: The object type DDL was not supported in an Editioned schema.
- Action: Do not perform this DDL on an Editioned schema object.
- ORA-22350: Incomplete opaque type cannot be used here
- Cause: An incomplete SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being used inappropriately.
- Action: Check the documentation for correct usage.
- ORA-22369: invalid parameter encountered in method string
- Cause: An invalid parameter is being passed to this method of SYS.AnyType ,SYS.AnyData or SYS.AnyDataSet
- Action: Check the parameters being passed to this method and make sure that the parameters are allowed.
- ORA-22370: incorrect usage of method string
- Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being used inappropriately.
- Action: Check the documentation for correct usage.
- ORA-22371: Table contains data of type string.string, version string, which does not exist
- Cause: Some of the older versions of the type may have got deleted because one or more of the types it were referencing was dropped.
- Action: These data could not be read as the whole ADT. Read the data at individual scalar attribute level.
- ORA-22372: Event for type dictionary upgrade
- Cause: This is an internally used event for type dictionary upgrades from 8.0 to 8.1.
- Action: None
- ORA-22373: Older version hashcode encountered
- Cause: An older version HC is encountered when creating a new version hahscode. Currently this is handled internally.
- Action: None
- ORA-22374: cannot reset the version of a type with table dependents
- Cause: The type for which reset version was requested has table dependents.
- Action: None
- ORA-22375: Event to check for subtypes in complete type tree
- Cause: This event is used to check for subtypes in complete type tree without any restriction on depth in the fix for bug# 12430142.
- Action: None
- ORA-22600: encountered 8.0.2 (Beta) VARRAY data that cannot be processed
- Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data.
- Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data. There is no provided script or tool to help automate this conversion.
- ORA-22601: pickler TDS context [string] is not initialized
- Cause: Attempt to use the pickler TDS context without initializing it.
- Action: Use OCIPicklerTdsCtxInit to initialize the context.
- ORA-22602: pickler TDS handle [string] is not well-formed
- Cause: Attempt to use the pickler TDS handle without initializing/ constructing it.
- Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed.
- ORA-22603: cannot add an attribute to the already generated TDS handle
- Cause: Attempt to add an attribute to the already constructed TDS.
- Action: Use a TDS handle that is initialized but not yet constructed.
- ORA-22604: TDS handle already generated
- Cause: Attempt to geneate TDS that is already genearated.
- Action: Use a TDS handle that is initialized but not yet generated.
- ORA-22605: FDO handle [string] is not initialized
- Cause: Attempt to use an uninitialized FDO handle.
- Action: Use OCIPicklerFdoInit to initialize FDO handle”.
- ORA-22606: pickler image handle [string] is not well-formed
- Cause: Attempt to use the image handle without initializing/ constructing it.
- Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed.
- ORA-22607: image handle already generated
- Cause: Attempt to geneate image that is already genearated.
- Action: Use a image handle that is initialized but not yet generated.
- ORA-22608: cannot add an attribute to the already generated image handle
- Cause: Attempt to add an attribute to the already constructed image.
- Action: Use a image handle that is initialized but not yet constructed.
- ORA-22609: error string during initialization of FDO
- Cause: Error during FDO initialization.
- Action: Take an action based on the specified error.
- ORA-22610: error while adding a scalar to the image handle
- Cause: Error while adding a scalar attribute to the image handle
- Action: Make sure image handle is initialized before adding scalar
- ORA-22611: TDS version is not recognized
- Cause: Incorrect TDS handle is passed
- Action: Make sure image handle is initialized with the correct TDS
- ORA-22612: TDS does not describe a collection TDS
- Cause: collection construct/access routines are being on an image but the TDS does not describe that a collection TDS
- Action: Make sure a collection TDS is used before invoking collection routines on the image handle
- ORA-22613: buflen does not match the size of the scalar
- Cause: buflen is incorrect
- Action: Make sure buflen is correct and matches the size of the scalar
- ORA-22614: error while construction the collection in the image
- Cause: Error during the construction of collection
- Action: Make sure image handle is initialized and OCIPicklerImageCollBegin is called to begin collection
- ORA-22615: attribute is not a collection
- Cause: collection routine is invoked upon a non-collection attribute
- Action: Make sure attribute is a collection
- ORA-22616: image is not of Oracle 8.1 format
- Cause: The function being invoked is applicable only for 8.1 images
- Action: Make sure image is of 8.1 format
- ORA-22617: error while accessing the image handle collection
- Cause: Error while accessing collection in the image handle
- Action: Make sure image is initialized correctly and the collection is constructed properly.
- ORA-22618: attribute is a BAD NULL in the image handle
- Cause: attribute in question is probably the attribute of a null embedded image
- Action: Make sure attribute number is valid or it is NULL or NOT NULL.
- ORA-22619: all collection elements have already been accessed
- Cause: Accessing a collection element after all the collection elements are already accessed
- Action: This function should not be invoked any more.
- 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.
- 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-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-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-22627: tc [string] must be that of object/varray/nested table
- Cause: Type code is not that of object/varray/nested table
- Action: Make sure the type code is OCI_TYPECODE_OBJECT or OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE
- 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-22629: OCIAnyData is null
- Cause: Attempting an operation that is not valid on null OCIAnyData
- Action: Make sure OCIAnyData is not null.
- 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-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-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-22633: Error freeing AnyDataSet
- Cause: AnyDataSet that is passed in may not be valid.
- Action: Check all the AnyDataSet parameters.
- 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-22635: time stamp with time zone type not supported
- Cause: OCIAnyData did not support conversion of time stamp with time zone when the version of time zone files differ.
- Action: Use same version of time zone files.