Oracle Error Messages: 05/27/12

Sunday 27 May 2012

ORA-31222: DBMS_LDAP: PL or SQL - Invalid LDAP SSL authentication mode.

ORA-31222: DBMS_LDAP: PL or SQL - Invalid LDAP SSL authentication mode.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the LDAP sslauth value that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31221: DBMS_LDAP: PL or SQL - Invalid LDAP SSL wallet passwd.

ORA-31221: DBMS_LDAP: PL or SQL - Invalid LDAP SSL wallet passwd.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the LDAP sslpasswd value that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31220: DBMS_LDAP: PL or SQL - Invalid LDAP SSL wallet location.

ORA-31220: DBMS_LDAP: PL or SQL - Invalid LDAP SSL wallet location.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the LDAP sslwrl value that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31219: DBMS_LDAP: PL or SQL - Invalid LDAP notypes.

ORA-31219: DBMS_LDAP: PL or SQL - Invalid LDAP notypes.

Cause: There has been an error in the DBMS_LDAP explode_dn or explode_rdn operation.

Action: Please check the LDAP notypes value that you use for LDAP explode_dn or explode_rdn operation, or report the error number and description to Oracle Support.

ORA-31218: DBMS_LDAP: PL or SQL - Invalid LDAP deleteoldrdn.

ORA-31218: DBMS_LDAP: PL or SQL - Invalid LDAP deleteoldrdn.

Cause: There has been an error in the DBMS_LDAP rename_s operation.

Action: Please check the LDAP deleteoldrdn value that you use for LDAP rename_s operation, or report the error number and description to Oracle Support.

ORA-31217: DBMS_LDAP: PL or SQL - Invalid LDAP newparent.

ORA-31217: DBMS_LDAP: PL or SQL - Invalid LDAP newparent.

Cause: There has been an error in the DBMS_LDAP rename_s operation.

Action: Please check the LDAP newparent value that you use for LDAP rename_s operation, or report the error number and description to Oracle Support.

ORA-31216: DBMS_LDAP: PL or SQL - Invalid LDAP rdn.

ORA-31216: DBMS_LDAP: PL or SQL - Invalid LDAP rdn.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the LDAP rdn value that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31215: DBMS_LDAP: PL or SQL - Invalid LDAP mod value.

ORA-31215: DBMS_LDAP: PL or SQL - Invalid LDAP mod value.

Cause: There has been an error in the DBMS_LDAP populate_mod_array operation.

Action: Please check the LDAP mod value that you use for LDAP populate_mod_ array operation, or report the error number and description to Oracle Support.

ORA-31214: DBMS_LDAP: PL or SQL - Invalid LDAP mod type.

ORA-31214: DBMS_LDAP: PL or SQL - Invalid LDAP mod type.

Cause: There has been an error in the DBMS_LDAP populate_mod_array operation.

Action: Please check the LDAP mod type that you use for LDAP populate_mod_ array operation, or report the error number and description to Oracle Support.

ORA-31213: DBMS_LDAP: PL or SQL - Invalid LDAP mod option.

ORA-31213: DBMS_LDAP: PL or SQL - Invalid LDAP mod option.

Cause: There has been an error in the DBMS_LDAP populate_mod_array operation.

Action: Please check the LDAP mod option that you use for LDAP populate_ mod_array operation, or report the error number and description to Oracle Support.

ORA-31212: DBMS_LDAP: PL or SQL - Invalid LDAP mod_array.

ORA-31212: DBMS_LDAP: PL or SQL - Invalid LDAP mod_array.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the LDAP mod_array that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31211: DBMS_LDAP: PL or SQL - Invalid LDAP entry dn.

ORA-31211: DBMS_LDAP: PL or SQL - Invalid LDAP entry dn.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the entry dn that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31210: DBMS_LDAP: PL or SQL - LDAP get_dn error.

ORA-31210: DBMS_LDAP: PL or SQL - LDAP get_dn error.

Cause: There has been an error in the DBMS_LDAP get_dn operation.

Action: Please check the LDAP get_dn, or report the error number and description to Oracle Support.

ORA-31209: DBMS_LDAP: PL or SQL - LDAP count_entry error.

ORA-31209: DBMS_LDAP: PL or SQL - LDAP count_entry error.

Cause: There has been an error in the DBMS_LDAP count_entry operation.

Action: Please check the LDAP count_operation, or report the error number and description to Oracle Support.

ORA-31208: DBMS_LDAP: PL or SQL - Invalid LDAP Message.

ORA-31208: DBMS_LDAP: PL or SQL - Invalid LDAP Message.

Cause: There has been an error in the DBMS_LDAP operation.

Action: Please check the LDAP message that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31207: DBMS_LDAP: PL or SQL - Invalid LDAP search time value.

ORA-31207: DBMS_LDAP: PL or SQL - Invalid LDAP search time value.

Cause: There has been an error in the DBMS_LDAP search operation.

Action: Please check the search time value that you use for search, or report the error number and description to Oracle Support.

ORA-31206: DBMS_LDAP: PL or SQL - Invalid LDAP search scope.

ORA-31206: DBMS_LDAP: PL or SQL - Invalid LDAP search scope.

Cause: There has been an error in the DBMS_LDAP search operation.

Action: Please check the search scope that you use for search, or report the error number and description to Oracle Support.

ORA-31205: DBMS_LDAP: PL or SQL - Invalid LDAP Auth method.

ORA-31205: DBMS_LDAP: PL or SQL - Invalid LDAP Auth method.

Cause: There has been an error in the DBMS_LDAP bind operation.

Action: Please check the authentication credentials that you use for binding, or report the error number and description to Oracle Support.

ORA-31204: DBMS_LDAP: PL or SQL - Invalid LDAP Session.

ORA-31204: DBMS_LDAP: PL or SQL - Invalid LDAP Session.

Cause: There has been an error in the DBMS_LDAP bind operation.

Action: Please check the session handler that you use for binding, or report the error number and description to Oracle Support.

ORA-31203: DBMS_LDAP: PL or SQL - Init Failed.

ORA-31203: DBMS_LDAP: PL or SQL - Init Failed.

Cause: There has been an error in the DBMS_LDAP Init operation.

Action: Please check the host name and port number, or report the error number and description to Oracle Support.

ORA-31202: DBMS_LDAP: LDAP client or server error: string

ORA-31202: DBMS_LDAP: LDAP client or server error: string

Cause: There is a problem either on the LDAP server or on the client.

Action: Please report this error to the LDAP server administrator or your Database administrator.

ORA-31201: DBMS_LDAP: generic error: string

ORA-31201: DBMS_LDAP: generic error: string

Cause: There has been an error in the DBMS_LDAP package.

Action: Please report the error number and description to Oracle Support.

ORA-31199: Warning in processing file string

ORA-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. or or or or or or or or or or or or or or or or or or or or or or or or or or DBMS_ LDAP OiD messages

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

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

ORA-31197: Error in processing file string

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

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

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

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

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

ORA-31194: Resource string is already deleted

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

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

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

Cause: Either one of the following is the cause:

Action: Avoid using these features.

ORA-31192: Resource string has not been checked out

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

ORA-31191: Resource string is already checked out

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

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

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

ORA-31187: Cannot Add Node string (type= string ) to Simple Type Node string

ORA-31187: Cannot Add Node string (type= string ) to Simple Type Node string

Cause: Trying to add attribute or element nodes to a simple type against the schema definition. Simple types can have only special attribute like namespaces, xsi:nil etc.

Action: Use a valid node for the operation.

ORA-31186: Document contains too many nodes

ORA-31186: Document contains too many nodes

Cause: Unable to load the document because it has exceeded the maximum allocated number of DOM nodes.

Action: Reduces the size of the document.

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

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

ORA-31183: Node type string cannot be converted to desired type

ORA-31183: Node type string cannot be converted to desired type

Cause: The given node s type cannot be converted correctly for this operation. For example, a DOM Element cannot be converted to Document Fragment

Action: Pass a valid node type for the conversion.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ORA-31159: XML DB is in an invalid state

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

ORA-31158: schema string currently being referenced

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

ORA-31157: Invalid Content-Type charset

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

ORA-31155: attribute string not in XDB namespace

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

ORA-31154: invalid XML document

ORA-31154: invalid XML document

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

Action: Fix the errors identified and try again.

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

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

ORA-31151: Cyclic definition encountered for string: string

ORA-31151: Cyclic definition encountered for string: string

Cause: The schema definition for this type has cycles.

Action: Remove cyclic definition and re-compile schema.

ORA-31122: The string operator has incorrect RHS value

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