Oracle Error Messages: 09/27/11

RMAN-00551: initialization of parser package failed

RMAN-00551: initialization of parser package failed

Cause: The parser package initialization routine returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00550: parser package failed to load

RMAN-00550: parser package failed to load

Cause: lpmloadpkg() return an error indication.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

OCI-31199: Warning in processing file string

OCI-31199: Warning in processing file string

Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully.

Action: This is primarily an informational message. Look at the next error on the stack to obtain further information.

OCI-31198: Mismatch in number of bytes transferred due to non-binary mode

OCI-31198: Mismatch in number of bytes transferred due to non-binary mode

Cause: An error occurred while reading the specifed file. The most probable cause is that the transfer was initiated in ASCII mode.

Action: Ensure that the transfer mode is set to BINARY

OCI-31197: Error in processing file string

OCI-31197: Error in processing file string

Cause: An error occurred while operating on the specifed file. The possible causes are the file header is corrupt or check the next error on stack

Action: Ensure that the specified file is correct. Look at the next error on the stack and take appropriate action.

OCI-31196: XML nodes over string in size cannot be printed

OCI-31196: XML nodes over string in size cannot be printed

Cause: An attempt was made to use an XML Text Node with a size greater than 64K, or an XML Comment Node with a size greater than 4K. These cannot be printed. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.

Action: Use getClobVal() or getStringVal() to print the Document.

OCI-31195: XML node string (type=string) does not support this operation

OCI-31195: XML node string (type=string) does not support this operation

Cause: The given node s type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.

Action: Use a valid node type for the operation.

OCI-31194: Resource string is already deleted

OCI-31194: Resource string is already deleted

Cause: Access a version-controlled resource that is already deleted.

Action: Remove the cyclic definitions in the type and retry compilation.

OCI-31193: This versioning feature isn t supported for resource string

OCI-31193: This versioning feature isn t supported for resource string

Cause: Either one of the following is the cause:

Action: Avoid using these features.

OCI-31192: Resource string has not been checked out

OCI-31192: Resource string has not been checked out

Cause: Either one of the following is the cause: to the workspace by any user in a workspace

Action: checked in the resource from the workspace before checking out

OCI-31191: Resource string is already checked out

OCI-31191: Resource string is already checked out

Cause: Either one of the following is the cause: by the same of different user.

Action: checked in the resource from the workspace before checking out

OCI-31190: Resource string is not a version-controlled resource

OCI-31190: Resource string is not a version-controlled resource

Cause: Either one of the following is the cause: - Checkout is requested for a resource that isn t under version control . Only version-controlled resource can be checked out.

Action: put the resource under version-control before checking out.

OCI-31185: DOM Nodes do not belong to the same DOM Document

OCI-31185: DOM Nodes do not belong to the same DOM Document

Cause: The specified PL or SQL DOM Node does not belong to the parent DOM Document of the referring DOM Node.

Action: Ensure that both the DOM Nodes are part of the same DOM Document.

OCI-31182: Too many PL or SQL DOM handles specified

OCI-31182: Too many PL or SQL DOM handles specified

Cause: An attempt was made to create a PL or SQL DOM handle that exceeded the maximum allowable number of PL or SQL DOM handles.

Action: Free PL or SQL DOM handles and try the operation again.

OCI-31181: PL or SQL DOM handle accesses node that is no longer available

OCI-31181: PL or SQL DOM handle accesses node that is no longer available

Cause: The specified pl or sql handle is referencing a node in a DOM Document that is no longer available.

Action: Ensure that the pl or sql handle for the target node is valid and try the operation again.

OCI-31180: DOM Type mismatch in invalid PL or SQL DOM handle

OCI-31180: DOM Type mismatch in invalid PL or SQL DOM handle

Cause: The specified PL or SQL DOM handle is referencing a DOM Node whose DOM Type that does not match the one available in the session. This could happen because the pl or sql handle was reused, or the original document is no longer available.

Action: Ensure that the pl or sql handle for the target node is valid and try the operation again.

OCI-31168: Node localname and namespace values should be less than 64K

OCI-31168: Node localname and namespace values should be less than 64K

Cause: An attempt was made to specify an XML Node with localname or namespace value greater than or equal to 64K. This is not supported.

Action: Node localnames and namespace values should be under 64K. or or or or or or 31180 - 31189 reserved for PL or SQL DOM API

OCI-31167: XML nodes over 64K in size cannot be inserted

OCI-31167: XML nodes over 64K in size cannot be inserted

Cause: An attempt was made to insert an XML Text Node with a size greater than 64K. This is not supported.

Action: Create text nodes under 64K.

OCI-31165: cannot load object-relational XML attribute using direct path

OCI-31165: cannot load object-relational XML attribute using direct path

Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column either contains an out-of-line partitioned table or the table itself is partitioned by one of the attributes of xmltype. This type of table cannot be loaded with direct path.

Action: Perform the load with conventional path mode.

OCI-31164: cannot load object-relational XML attribute using direct path

OCI-31164: cannot load object-relational XML attribute using direct path

Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column contains a type with subtypes. This type of attribute cannot be loaded with direct path.

Action: Perform the load with conventional path mode.

OCI-31163: element or attribute string has invalid attribute value string (should be string )

OCI-31163: element or attribute string has invalid attribute value string (should be string )

Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type

Action: Remove the mismatched attribute values from the offending element or attribute

OCI-31162: element or attribute string has no SQLType specified

OCI-31162: element or attribute string has no SQLType specified

Cause: Schema registration was invoked with GENTYPES=false without specifying a SQLType for some element or attribute

Action: Specify a SQLType for the offending element or attribute and register the schema again

OCI-31161: element or attribute string cannot be stored out of line

OCI-31161: element or attribute string cannot be stored out of line

Cause: An element or attribute of a simple type has SQLInline=false

Action: Remove the SQLInline=false qualification for the offending element or attribute

OCI-31160: max substitution group size string exceeded by string (string) for head element string (string)

OCI-31160: max substitution group size string exceeded by string (string) for head element string (string)

Cause: The maximum limit on nested substitution groups has been exceeded by an element.

Action: Delete specified schema and re-register it after removing the offending substitution element.

OCI-31159: XML DB is in an invalid state

OCI-31159: XML DB is in an invalid state

Cause: XML DB s internal tables are in an invalid state, probably because the database was not upgraded or the upgrade was not successful

Action: Ensure that the database is upgraded successfully. If the problem persists, contact Oracle Support

OCI-31158: schema string currently being referenced

OCI-31158: schema string currently being referenced

Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope.

Action: Ensure all references to this schema in this session are released and try the operation again.

OCI-31157: Invalid Content-Type charset

OCI-31157: Invalid Content-Type charset

Cause: HTTP Content-Type header had a charset that Oracle does not understand.

Action: Fix the Content-Type header in the HTTP request.

OCI-31155: attribute string not in XDB namespace

OCI-31155: attribute string not in XDB namespace

Cause: The specified attribute should be prefixed with XDB s namespace.

Action: Ensure that all XDB specified attributes are prefixed with XDB s namespace and try again.

OCI-31154: invalid XML document

OCI-31154: invalid XML document

Cause: The XML document is invalid with respect to its XML Schema.

Action: Fix the errors identified and try again.

OCI-31153: Cannot create schema URL with reserved prefix http: or or xmlns.oracle.com or xdb or schemas or

OCI-31153: Cannot create schema URL with reserved prefix http: or or xmlns.oracle.com or xdb or schemas or

Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL.

Action: Modify the prefix to a different one.

OCI-31151: Cyclic definition encountered for string: string

OCI-31151: Cyclic definition encountered for string: string

Cause: The schema definition for this type has cycles.

Action: Remove cyclic definition and re-compile schema.

OCI-31122: The string operator has incorrect RHS value

OCI-31122: The string operator has incorrect RHS value

Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE

Action: Specify value on the right hand side that evaluate to TRUE or or or or or or 31151 - 31189 reserved for XML Schema Compiler

OCI-31121: The string operator can not be FALSE

OCI-31121: The string operator can not be FALSE

Cause: The value of the operator that is specified is FALSE

Action: Specify an operator that evaluates to TRUE

OCI-31116: Tablespace not specified correctly

OCI-31116: Tablespace not specified correctly

Cause: XDB cannot be moved to the specified tablespace.

Action: Specify a valid tablespace.

OCI-31115: XDB configuration error: string

OCI-31115: XDB configuration error: string

Cause: An error related to XDB configuration has occurred.

Action: Make sure the configuration resource contains valid data.

OCI-31114: XDB configuration has been deleted or is corrupted

OCI-31114: XDB configuration has been deleted or is corrupted

Cause: The XDB configuration resource has been deleted or corrupted.

Action: Reinstall XDB, or reinsert a valid configuration document.

OCI-31112: fail to string for string port using xdb configuration

OCI-31112: fail to string for string port using xdb configuration

Cause: port number for the defined presentation is not valid

Action: Either the port number is already in use or it is protected. Specify another port number.

OCI-31111: table string cannot be hierarchically enabled

OCI-31111: table string cannot be hierarchically enabled

Cause: Trigger lamp;lt;lamp;nbsp;tabnamelamp;gt;_xdb_pitrigger already exists

Action: Delete all rows in the hierarchical index and then rebuild it.

OCI-31105: User does not own lock string

OCI-31105: User does not own lock string

Cause: The lock to be unlocked is not owned by the user.

Action: none

OCI-31104: Cannot find lock with token string on string for unlock

OCI-31104: Cannot find lock with token string on string for unlock

Cause: The lock may have been unlock or it may have expired.

Action: No action needed. Unlock already successful.

OCI-31103: Resource locked in shared mode. Cannot add exclusive lock

OCI-31103: Resource locked in shared mode. Cannot add exclusive lock

Cause: The resource is locked in shared mode. Cannot add a shared lock.

Action: Try locking in shared mode or unlocking the existing lock.

OCI-31102: Already locked in exclusive mode. Cannot add lock.

OCI-31102: Already locked in exclusive mode. Cannot add lock.

Cause: The resource is already locked in exclusive mode. Cannot add another lock.

Action: Unlock the existing lock.

OCI-31101: Token string not given while locking resource string

OCI-31101: Token string not given while locking resource string

Cause: Locking attempted on resource when the pricipal already owns a lock given by the token above.

Action: Reattempt the lock with the token.

OCI-31100: XDB Locking Internal Error

OCI-31100: XDB Locking Internal Error

Cause: An XDB Locking Internal error has occurred.

Action: Contact Oracle Support.

OCI-31099: XDB Security Internal Error

OCI-31099: XDB Security Internal Error

Cause: An XDB Security internal error has occurred.

Action: Contact Oracle Support. or or or or or or 31100 - 31110 reserved for WebDAV compliant resource locks

OCI-31097: Hierarchical Index not empty

OCI-31097: Hierarchical Index not empty

Cause: An attempt was made to rebuild the hierarchical index which is not empty.

Action: Delete all rows in the hierarchical index and then rebuild it.

OCI-31096: validation failed for schema

OCI-31096: validation failed for schema

Cause: The XML Schema could not be validated.

Action: Make sure that the SQLType and other datatype mapping is valid.

OCI-31095: cannot generate string : string.string already exists

OCI-31095: cannot generate string : string.string already exists

Cause: The type or table name specified in the XML schema document cannot be generated because it is already being used.

Action: Use different names for types or tables or use the NOGEN mode so that schema compiler does not generate new types or tables.

OCI-31094: incompatible SQL type string for attribute or element string

OCI-31094: incompatible SQL type string for attribute or element string

Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.

Action: Make sure that the specified SQL types are compatible with the declared XML datatypes.

OCI-31093: null or invalid value specified for parameter : string

OCI-31093: null or invalid value specified for parameter : string

Cause: The argument value passed for the given parameter is null or invalid.

Action: Make sure that all the input argument values are valid.

OCI-31092: invalid SQL name string

OCI-31092: invalid SQL name string

Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.

Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. This implies that the database length and other restrictions on names be satisfied.

OCI-31091: empty string specified as a SQL name

OCI-31091: empty string specified as a SQL name

Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.

Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. Otherwise, remove such attributes from the schema and try again.

OCI-31090: invalid database schema name string

OCI-31090: invalid database schema name string

Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema

Action: Make sure that all database user or schema names specified in the XML schema document refer to existing database users or schemas.

OCI-31089: schema string does not target namespace string

OCI-31089: schema string does not target namespace string

Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces.

Action: Make sure that all schemas referenced via include definitions target the same namespace as the parent schema. Further make sure that the namespace specified in the import definition matches the actual target namespace of the specified schema.

OCI-31088: object string . string depends on the schema

OCI-31088: object string . string depends on the schema

Cause: An attempt was made to delete a schema which has dependent objects.

Action: Either drop the dependent objects prior to deleting the schema or use the CASCADE or FORCE options.

OCI-31087: insufficient privileges to delete schema string

OCI-31087: insufficient privileges to delete schema string

Cause: An attempt was made to delete a schema resource without sufficient privileges.

Action: Make sure that the user has sufficient privileges to delete the schema.

OCI-31086: insufficient privileges to register global schema string

OCI-31086: insufficient privileges to register global schema string

Cause: An attempt was made to register a global schema without sufficient privileges.

Action: Make sure that the user has sufficient privileges to register a global schema.