ORA-30960: The entity is neither an XPATH nor a NAMESPACE.

ORA-30960: The entity is neither an XPATH nor a NAMESPACE.

Cause: The given string had invalid syntax.

Action: Check the syntax for XPATH and NAMESPACE.

ORA-30959: The indexed column is not stored in CLOB.

ORA-30959: The indexed column is not stored in CLOB.

Cause: An attempt was made to create an XML Index on an OR-XMLType column.

Action: Re-create the XML Index on a CLOB-XMLType column.

ORA-30957: cannot downgrade because there are XML indexes

ORA-30957: cannot downgrade because there are XML indexes

Cause: An attempt was made to downgrade a database that has XML indexes.

Action: Drop all XML indexes before attempting the downgrade.

ORA-30956: invalid option for XML Index

ORA-30956: invalid option for XML Index

Cause: Unexpected error.

Action: File a bug.

ORA-30953: XML minoccurs value (string) violated

ORA-30953: XML minoccurs value (string) violated

Cause: An attempt was made to delete more than the required minimum number of elements (specified by the minoccurs facet) from an XML document.

Action: Do not attempt to delete more than the required minimum number of elements that must be present from the XML document. or or or or or or Errors 30955 to 30989 reserved for XML Index

ORA-30952: illegal configuration of HTTP or HTTPS in xdbconfig.xml

ORA-30952: illegal configuration of HTTP or HTTPS in xdbconfig.xml

Cause: An attempt was made to update xdbconfig.xml when either 1) a value was specified for http2-port but not for http2-protocol (or vice versa), OR 2) http-port and http2-port were set to the same value.

Action: Specify values for both elements http2-port and http2-protocol, AND set different values for http-port and http2-port.

ORA-30951: Element or attribute at Xpath string exceeds maximum length

ORA-30951: Element or attribute at Xpath string exceeds maximum length

Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document.

Action: Do not attempt to add a node exceeding the maximum length to XML documents.

ORA-30946: XML Schema Evolution warning: temporary tables not cleaned up

ORA-30946: XML Schema Evolution warning: temporary tables not cleaned up

Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful

Action: If the user needs to remove the temporary tables, use the mapping table to get the temporary table names and drop them. or or or or or End of XML Schema Evolution errors (30942 to 30950 reserved)

ORA-30945: Could not create mapping table string

ORA-30945: Could not create mapping table string

Cause: A mapping table could not be created during XML schema evolution. For more information, see the more specific error below this one

Action: Ensure that a table with the given name does not exist and retry the operation

ORA-30944: Error during rollback for XML schema string table string column string

ORA-30944: Error during rollback for XML schema string table string column string

Cause: The given XMLType table or column which conforms to the given schema had errors during a rollback of XML schema evolution. For more information, see the more specific error below this one

Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action

ORA-30943: XML Schema string is dependent on XML schema string

ORA-30943: XML Schema string is dependent on XML schema string

Cause: Not all dependent schemas were specified and or or the schemas were not specified in dependency order, i.e., if schema S1 is dependent on schema S, S must appear before S1.

Action: Include the previously unspecified schema in the list of schemas and or or correct the order in which the schemas are specified. Then retry the operation.

ORA-30942: XML Schema Evolution error for schema string table string column string

ORA-30942: XML Schema Evolution error for schema string table string column string

Cause: The given XMLType table or column which conforms to the given schema had errors during evolution. For more information, see the more specific error below this one

Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action

ORA-30941: Cannot specify empty URI for non-default namespace string

ORA-30941: Cannot specify empty URI for non-default namespace string

Cause: An attempt was made to insert a namespace declaration for a non-default namespace using an empty URI string.

Action: Specify a non-empty URI for namespace declarations other than the default namespace. or or or or or or Errors 30942 to 30950 reserved for XML Schema Evolution

ORA-30940: Cannot resolve prefix string for QName node string

ORA-30940: Cannot resolve prefix string for QName node string

Cause: An attempt was made to store a QName value without having a valid namespace in scope for that prefix.

Action: Declare the namespace for the prefix used

ORA-30939: Order violation: Element string may not follow element string

ORA-30939: Order violation: Element string may not follow element string

Cause: The XML schema specifies a content model that is sequential, where the order of nodes in the instance must follow the order specified by the schema, and this instance relies on the schema validity to avoid maintaining instance order information

Action: Insert elements only in the order specified in the schema

ORA-30938: No prefix defined for namespace string (particle string)

ORA-30938: No prefix defined for namespace string (particle string)

Cause: An XML namespace mapping (xmlns:lamp;lt;lamp;nbsp;prefixlamp;gt;=lamp;lt;lamp;nbsp;namespace URLlamp;gt;) must be defined for each particle (element or attribute) stored in an schema-constrained XMLType document.

Action: Add an xmlns attribute definition (attribute name= xmlns:prefix and value= namespace URL ) to the current XMLType document. The safest place to add this attribute is in the root node of the document to ensure that the mapping will be in scope.

ORA-30937: No schema definition for string (namespace string ) in parent string

ORA-30937: No schema definition for string (namespace string ) in parent string

Cause: The schema definition for the parent node being processed does not allow for the specified child node in its content model. Note that any typecasting via xsi:type must occur before the schema definitions for the new type can be used.

Action: Only insert elements and attributes declared in the schema. Check to make sure that xsi:type (if used) is specified first.

ORA-30936: Maximum number (string) of string XML node elements exceeded

ORA-30936: Maximum number (string) of string XML node elements exceeded

Cause: An attempt was made to insert more than the allowed number of elements (specified by the maxoccurs facet) into an XML document.

Action: Do not attempt to add more than the maximum number of elements to XML documents.

ORA-30935: XML maxoccurs value (string) exceeded

ORA-30935: XML maxoccurs value (string) exceeded

Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document.

Action: Do not insert more than maxoccurs values into the document.

ORA-30934: string (string node) cannot be inserted in parent string (string node)

ORA-30934: string (string node) cannot be inserted in parent string (string node)

Cause: The schema does not allow a child node of this type to be inserted into a parent node of this type. For example, only element nodes may only be inserted into a document

Action: Insert only child nodes that make sense for this node type

ORA-30933: Element string may not appear at this point within parent string

ORA-30933: Element string may not appear at this point within parent string

Cause: The ordering specified by the content model of the parent does not allow for this element to occur at this position.

Action: Reorder the child elements to conform with the content model of the parent element

ORA-30932: Reference node string not contained in specified parent node string

ORA-30932: Reference node string not contained in specified parent node string

Cause: When using a reference node, it must have the specified parent node

Action: Use a node in the specified parent as the reference

ORA-30931: Element string cannot contain mixed text

ORA-30931: Element string cannot contain mixed text

Cause: XML elements must be declared mixed to contain multiple text nodes

Action: Declare this element type as mixed in its schema

ORA-30930: NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn

ORA-30930: NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn

Cause: CONNECT_BY_ISCYCLE was specifed in a query which does not have the NOCYCLE keyword.

Action: Remove CONNECT_BY_ISCYCLE or add NOCYCLE.

ORA-30929: ORDER SIBLINGS BY clause not allowed here

ORA-30929: ORDER SIBLINGS BY clause not allowed here

Cause: ORDER SIBLINGS BY clause is specifed in a query which doesn t have CONNECT BY clause.

Action: Remove ORDER SIBLINGS BY clause or add CONNECT BY clause.

ORA-30928: Connect by filtering phase runs out of temp tablespace

ORA-30928: Connect by filtering phase runs out of temp tablespace

Cause: It is probably caused by the fact that there is a loop in the data.

Action: Please retry the query with the NO_FILTERING hint. If the same error still occurs, then increase temp tablespace.

ORA-30927: Unable to complete execution due to failure in temporary table transformation

ORA-30927: Unable to complete execution due to failure in temporary table transformation

Cause: In memory temporary tables we create are aged out of shared pool before we are able to grab them again.

Action: Reduce activities that use a lot of shared pool space or wait for a while, then retry.

ORA-30926: unable to get a stable set of rows in the source tables

ORA-30926: unable to get a stable set of rows in the source tables

Cause: A stable set of rows could not be got because of large dml activity or a non-deterministic where clause.

Action: Remove any non-deterministic where clauses and reissue the dml.

ORA-30772: opaque types do not have default constructors

ORA-30772: opaque types do not have default constructors

Cause: Constructor invocation did not succeed, since no user-defined constructors were defined for the opaque type, and since opaque types do not have default constructors.

Action: Add user-defined constructors to opaque type, or specify a member or static method for the opaque type.

ORA-30771: Cannot add more than one referential constraint on REF column string

ORA-30771: Cannot add more than one referential constraint on REF column string

Cause: Multiple referential constraints were specified for a single REF column.

Action: Remove the additional referential constraints and retry the operation.

ORA-30770: Cannot specify storage options for fixed size opaque type

ORA-30770: Cannot specify storage options for fixed size opaque type

Cause: Storage clause was specified during table creation for a fixed size opaque type.

Action: Do not provide storage option clause.

ORA-30768: Cannot evaluate pipelined function

ORA-30768: Cannot evaluate pipelined function

Cause: Pipelined functions can only be used in a TABLE expression in the from clause.

Action: Use a non-pipelined function instead.

ORA-30767: OID type mismatch

ORA-30767: OID type mismatch

Cause: An attempt was made to modify the scope for a REF column to a table whose object identifier s type is different from that of the original scoped table.

Action: none

ORA-30766: cannot modify scope for a REF column with a REFERENCES constraint

ORA-30766: cannot modify scope for a REF column with a REFERENCES constraint

Cause: An attempt was made to modify the scope for a REF column with a REFERENCES constraint.

Action: Drop the REFERENCES constraint, and retry the operation.

ORA-30765: cannot modify scope for an unscoped REF column

ORA-30765: cannot modify scope for an unscoped REF column

Cause: An attempt was made to modify the scope for an unscoped REF column.

Action: Use an ALTER TABLE ADD SCOPE FOR command instead.

ORA-30757: cannot access type information

ORA-30757: cannot access type information

Cause: Either a subtype was created and operations performed with this new type while the session was in progress, or the type information was unpinned from the object cache.

Action: Commit necessary changes, end the user session, reconnect again and re-try the object operations. If problem persists, contact your Oracle Support representative.

ORA-30756: cannot create column or table of type that contains a supertype attribute

ORA-30756: cannot create column or table of type that contains a supertype attribute

Cause: The user tried to create a column or table of an object type that contains a supertype attribute. This is not supported because it leads to infinite recursion in our current storage model. Note that creating a column of a type implies that we create columns corresponding to all subtype attributes as well.

Action: Change the type definition to contain a supertype REF attribute instead of the supertype object attribute.

ORA-30755: error during expansion of view hierarchy

ORA-30755: error during expansion of view hierarchy

Cause: There was an error while trying to expand a view hierarchy. This could be due to invalid subviews (or subviews with errors)

Action: Ensure that all subviews are valid e.g. alter view ... compile and retry the operation.

ORA-30754: column or table string stores objects of only one type

ORA-30754: column or table string stores objects of only one type

Cause: The user is trying to perform an operation that is not allowed on object column or table that is enabled to store instances of a single type.

Action: None

ORA-30753: column or table string is substitutable

ORA-30753: column or table string is substitutable

Cause: The user is performing an operation that is not allowed on substitutable column or table.

Action: None.

ORA-30752: column or table string is not substitutable

ORA-30752: column or table string is not substitutable

Cause: The user is performing an operation that is not allowed on non substitutable column or table.

Action: None.

ORA-30751: cannot disable column string from storing objects of type string.string

ORA-30751: cannot disable column string from storing objects of type string.string

Cause: The user is trying to drop a type from being stored in a substitutable column or table. This error is raised due to one of the following reasons : dropped.

Action: Fix the cause of the error and retry the operation.

ORA-30750: cannot enable column string to store objects of type string.string

ORA-30750: cannot enable column string to store objects of type string.string

Cause: The user is trying to enable a column to store instances of a subtype. The error is raised due to one of the following :

Action: Fix the cause of the error and retry the operation.

ORA-30749: column string not enabled to store objects of type string.string

ORA-30749: column string not enabled to store objects of type string.string

Cause: The user is trying to disable a column from storing instances of a type for which it is already enabled.

Action: None

ORA-30748: column string already enabled to store objects of type string.string

ORA-30748: column string already enabled to store objects of type string.string

Cause: The user is trying to enable a column to store instances of a type for which it is already enabled.

Action: None

ORA-30747: cannot create substitutable tables or columns of non final type string.string

ORA-30747: cannot create substitutable tables or columns of non final type string.string

Cause: The user tried to create substitutable table or column of a non final type. This operation is not currently supported.

Action: Change the statement to create a non substitutable table or column.

ORA-30746: error occured while trying to drop column string in table string

ORA-30746: error occured while trying to drop column string in table string

Cause: The user tried to drop a subtype with VALIDATE option which tried to check for stored instances of the type in the stated table

Action: Delete all instances of this subtype and then drop the type.

ORA-30745: error occured while trying to add column string in table string

ORA-30745: error occured while trying to add column string in table string

Cause: The user tried to add a subtype which tried to alter the tables dependent on the supertype.

Action: Ensure that the table will not exceed the columnlimit on adding this subtype.

ORA-30744: string is not an object table

ORA-30744: string is not an object table

Cause: The specified object is not an object table.

Action: Specify an object table and retry the operation.

ORA-30743: string is not an object view

ORA-30743: string is not an object view

Cause: The specified object is not an object view.

Action: Specify an object view and retry the operation.

ORA-30742: cannot grant SELECT privilege WITH HIERARCHY OPTION on this object

ORA-30742: cannot grant SELECT privilege WITH HIERARCHY OPTION on this object

Cause: The user tried to grant SELECT privilege WITH HIERARCHY OPTION on an object that is not one of the following : object table of non final type, object view of non final type.

Action: Ensure that the SELECT privilege WITH HIERARCHY OPTION is granted on a valid object.

ORA-30741: WITH HIERARCHY OPTION can be specified only for SELECT privilege

ORA-30741: WITH HIERARCHY OPTION can be specified only for SELECT privilege

Cause: The user tried to specify WITH HIERARCHY OPTION for a privilege other than SELECT privilege.

Action: Ensure that the HIERARCHY OPTION is specified only with the SELECT privilege

ORA-30740: cannot grant UNDER privilege on this object

ORA-30740: cannot grant UNDER privilege on this object

Cause: The user tried to grant UNDER privilege on an object that is not one of the following : non final object type, object table of non final type, object view of non final type.

Action: Ensure that the UNDER privilege is granted on a valid object.

ORA-30739: cannot drop a table that has subtables

ORA-30739: cannot drop a table that has subtables

Cause: The user tried to drop a table that has subtables defined under it.

Action: Drop all subtables before trying this operation.

ORA-30738: object string does not exist in schema string

ORA-30738: object string does not exist in schema string

Cause: The specified object does not exist.

Action: Ensure that the specified object exists and retry the operation.

ORA-30737: cannot create subtable of a type which is not a subtype of the type of the supertable

ORA-30737: cannot create subtable of a type which is not a subtype of the type of the supertable

Cause: An attempt was made to create a subtable(subview) of a type which is not a subtype of the type of the super object.

Action: Change the type of the subtable to be a subtype of the superobject s type and then retry the operation.

ORA-30736: objects in a table or view hierarchy have to be in the same schema

ORA-30736: objects in a table or view hierarchy have to be in the same schema

Cause: An attempt was made to create a subtable(subview) under a supertable(superview) located in another schema.

Action: Connect as schema owner of the superobject and retry the operation.

ORA-30735: cannot create multiple subtables of the same type under a supertable

ORA-30735: cannot create multiple subtables of the same type under a supertable

Cause: An attempt was made to create under a supertable (superview), a subtable(subview) of the same type as another existing subtable (subview).

Action: Drop the existing subtable(subview) and retry the operation.

ORA-30734: cannot specify scope constraint on ref column with rowid

ORA-30734: cannot specify scope constraint on ref column with rowid

Cause: An attempt was made to specify scope constraint on a REF column with the rowid constraint.

Action: Remove the scope constraint and then retry the operation.

ORA-30733: cannot specify rowid constraint on scoped ref column

ORA-30733: cannot specify rowid constraint on scoped ref column

Cause: An attempt was made to specify rowid constraint on a scoped REF column.

Action: Remove the rowid constraint and then retry the operation.