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.