Cause: Invalid delta update operation was issued on LOB. This includes operation beyond LOB length; move operation with destination offset inside move interval.
Action: Check operation parameters for validity.
ORA-44001: invalid schema
Cause: The schema for the given schema name did not exist.
Action: Provide a valid schema name.
ORA-44002: invalid object name
Cause: The input parameter string was not a qualified SQL identifier of an existing SQL object.
Action: Make sure the string matches an existing SQL object that is accessible by the current schema.
ORA-44003: invalid SQL name
Cause: The input parameter string was not a valid simple SQL name.
Action: Check with the DBMS_ASSERT spec to verify that the parameter string is a valid simple SQL name.
ORA-44004: invalid qualified SQL name
Cause: The input parameter string was not a valid qualified SQL name.
Action: Check with the DBMS_ASSERT spec to verify that the parameter string is a valid qualified SQL name. /////////////////////////////////////////////////////////////////////////// Reserving 44101 - 44200 for UTL_MAIL errors ///////////////////////////////////////////////////////////////////////////
ORA-44101: invalid priority
Cause: The priority level given by the user was invalid.
Action: See UTL_MAIL for valid priority values and change the priority parameter accordingly. /////////////////////////////////////////////////////////////////////////// Reserving 44201 - 44300 for Shared Cursor (KKS) errors ///////////////////////////////////////////////////////////////////////////
ORA-44203: timeout waiting for lock on cursor
Cause: A timeout occured while waiting for a cursor to be compiled. This is usually caused by the SQL parse requiring access to system resources which are locked by concurrently executing sessions.
Action: Investigate possible causes of resource contention. If neccessary, contact support for additional information on how to diagnose this problem. /////////////////////////////////////////////////////////////////////////// Reserving 44301 - 44320 for DBMS_SERVICES errors ///////////////////////////////////////////////////////////////////////////
ORA-44301: NULL service name is not permitted
Cause: The service name argument was found to be NULL.
Action: Provide a non-NULL service name.
ORA-44302: NULL network name is not permitted
Cause: The network name argument was found to be NULL.
Action: Provide a non-NULL network name.
ORA-44303: service name exists
Cause: This service name was already in existence.
Action: Provide a new unique service name.
ORA-44304: service string does not exist
Cause: The specified service was not in existence.
Action: Provide a valid service name.
ORA-44305: service string is running
Cause: The specified service was running.
Action: This message is informational only.
ORA-44306: service name exceeds maximum length of string
Cause: The service name was too long.
Action: Use a shorter service name.
ORA-44307: network name too long
Cause: The network name, excluding the domain, was too long.
Action: Use a shorter network name.
ORA-44310: maximum number of services exceeded
Cause: The maximum number of services has been reached.
Action: None
ORA-44311: service string not running
Cause: The specified service was not running.
Action: This message is informational only.
ORA-44312: database closed
Cause: The database was closed.
Action: Open the database and retry the operation.
ORA-44313: instance name invalid
Cause: The instance name argument was not valid.
Action: Provide a valid instance name.
ORA-44314: network name already exists
Cause: The network name was already in existence.
Action: Use an alternate network name.
ORA-44315: all service attributes null
Cause: All attributes specified were null.
Action: At least one attribute must be non-null.
ORA-44316: invalid argument
Cause: Invalid argument supplied.
Action: Supply a valid argument.
ORA-44317: database open read-only
Cause: The database is open read-only.
Action: Close the database and reopen it read/write before trying again.
ORA-44318: exceeded maximum SERVICE_NAMES length
Cause: The total length of all running service network names exceeded the maximum allowable length.
Action: Stop another service to start this one.
ORA-44321: cannot read command line from trace file string
Cause: Trace file could not be read.
Action: Make sure trace file exists and contains valid raw trace data.
ORA-44322: invalid file name 'string'
Cause: A NULL or zero length file name was specified.
Action: Correct the file name to be a nonzero length string.
ORA-44323: negative <count> 'number' to string option
Cause: The given count was a nonpositive number.
Action: Provide a positive count number.
ORA-44324: no <count> argument to string option
Cause: Count number was missing for the option.
Action: Provide a count number to the option.
ORA-44325: no entry points found in trace file string
Cause: The given trace symbol was not found.
Action: None
ORA-44326: no <symbol> argument to string option
Cause: <symbol> argument to -[un]trace option was missing.
Action: Provide <symbol> argument to -[un]trace option.
ORA-44327: no <filename> argument to string option
Cause: <filename> argument to the option was missing.
Action: Provide <filename> argument to the option.
ORA-44328: unsupported version number: string
Cause: Version of the trace file was not supported.
Action: Provide supported version of trace file.
ORA-44403: invalid value specified for flag parameter
Cause: Mutually exclusive values were specified for the flag parameter.
Action: Internal error. Contact Oracle Support Services.
ORA-44404: upicui2 client function requires Oracle server of 10.2 or higher
Cause: A 10.2 or higher client is being used with an older Oracle server.
Action: Use an Oracle server with the same version as the client.
ORA-44411: Invalid ACL: START_DATE cannot be larger than END_DATE for all ACE
Cause: The END_DATE was smaller than the START_DATE in one of the ACE's in this ACL.
Action: Set all END_DATE to be larger than or equal to the START_DATE in each of the ACE's in this ACL.
ORA-44412: Invalid ACL: Cyclic ACL inheritance is not allowed
Cause: A cycle was formed by ACL inheritance.
Action: Check the ACL inheritance and break the cycle by removing some ACL inheritance.GG function exceeds system limits.
ORA-44413: Invalid ACL: Security class of parent ACL must be an ancestor of security class of child ACL
Cause: Security class of parent ACL was not an ancestor of security class of child ACL
Action: Change the security class of parent ACL to be an ancestor of security class of child ACL.
ORA-44414: Invalid ACL: Parent ACL 'string' does not exist
Cause: The path to the parent ACL was not a valid resource.
Action: Change the parent ACL of this resource or create the parent ACL at the specified location.
ORA-44415: Invalid ACL: Undefined privileges
Cause: An undefined privilege was found in an ACE in the ACL.
Action: Make sure the privilege is defined in the security class as specified in the ACL.
ORA-44416: Invalid ACL: Unresolved principal 'string'
Cause: An unresolved principal is found in an ACE in the ACL.
Action: Make sure the principal is a valid user or role in the system.
ORA-44417: Invalid ACL: Invalid ACLID
Cause: The specified ACLID did not point to a valid ACL document.
Action: Make sure the ACLID points to a valid ACL document.
ORA-44421: cannot DISALLOW NONSCHEMA without a SCHEMA clause
Cause: If no SCHEMA clause (explicit schema or ANYSCHEMA) was specified, nonschema data cannot be disallowed.
Action: Remove DISALLOW NONSCHEMA or add some SCHEMA clause.
ORA-44422: nonschema XML disallowed for this column
Cause: An attempt was made to insert nonschema based XML documents in a binary XML column that disallows nonschema data.
Action: Insert only schema-based documents or alter the column to ALLOW NONSCHEMA data.
ORA-44423: XML Schema registered for BINARY cannot be used for CLOB/OBJ-REL
Cause: An attempt was made to use a XML Schema registered for binary usage as part of a CLOB or OBJ-REL clause.
Action: Specify a schema registered for CLOB or OBJ-REL use. Else specify BINARY XML storage for column.
ORA-44424: BINARY XML storage requires XML Schema registered for BINARY usage
Cause: An attempt was made to specify BINARY XML storage using an XML schema not registered for BINARY.
Action: Specify a schema registered for BINARY usage. Else specify CLOB or OBJ-REL storage for column.
ORA-44501: QMEL: Too much concurrency.
Cause: Too much concurrency
Action: Transient error, try again.
ORA-44502: QMEL: Lock not found.
Cause: Lock not found
Action: Check arguments
ORA-44503: QMEL: Lock Denied.
Cause: Lock denied
Action: None
ORA-44504: Resource Locked by Implicit Lock
Cause: The resource is locked by an implicit lock
Action: Implicit locks are normally caused by NFS locks. Refer to XDB Protocol guide for removing/obtaining information about implicit locks.
ORA-44505: QMEL: Invalid arguments.
Cause: Arguments to QMEL are not correct.
Action: None
ORA-44700: Language 'string' is not a valid language for a translation
Cause: Invalid language.
Action: The language must conform to IETF RFC 3066.
ORA-44701: Language not found for translation
Cause: The document had multiple translations and one of them did not have the xml:lang attribute.
Action: All translations must have the xml:lang attribute when multiple translations are present.
ORA-44702: Multiple translations found for language 'string'
Cause: The document had multiple translations for a language.
Action: The document must contain only one translation per language for every translated element.
ORA-44703: Multiple source language translations found
Cause: The document had multiple source language translations.
Action: The document must contain only one source language translation for every translated element.
ORA-44704: XPath 'string' does not uniquely identify a translated element
Cause: The given XPath pointed to multiple translated elements.
Action: The given XPath must uniquely identify a translated element.
ORA-44705: Must have xdb:maxOccurs='1' for translated elements
Cause: The value of xdb:maxOccurs was not '1' for a translated element.
Action: The value of xdb:maxOccurs must be '1' for a translated element.
ORA-44706: Must have xsd:maxOccurs='unbounded' for translated elements
Cause: The value of xsd:maxOccurs was not 'unbounded' for a translated element.
Action: The value of xsd:maxOccurs must be 'unbounded' for a translated element.
ORA-44707: No source language translation found
Cause: The document had no source language translation for a translated element.
Action: The document must contain exactly one source language translation for every translated element.
ORA-44708: Translations not supported for object relational storage
Cause: The storage type of the schema was object relational.
Action: Register the schema with storage type as clob or binary xml.
ORA-44709: Invalid schema definition for translated element
Cause: The schema definition for a translated element was invalid.
Action: A translated element must be a complex type with simple content which is a restriction or extension of xs:string.
ORA-44710: Malformed XLIFF document: string
Cause: The XLIFF document was malformed.
Action: Fix the error and try again.
ORA-44711: XPath refers to an untranslatable element
Cause: XPath pointed to an untranslatable element.
Action: XPath for this operation must refer to a translatable element.
ORA-44712: Invalid XPath in XLIFF document used for merging
Cause: XPath within trans-unit/id attribute was invalid.
Action: XPath within trans-unit/id attribute must point to a set of translations, not to a particular translation.
ORA-44713: XPath does not select all translations
Cause: XPath did not select all translations for a particular element.
Action: XPath must point to a set of translations, not to a particular translation.
ORA-44730: XML Index string is not usable at the moment
Cause: The async XML Index could not be used since ORACLE is not open for query.
Action: Try the same query again when ORACLE is open for query, or use NO_XMLINDEX_REWRITE hint.
ORA-44731: Path string cannot be removed from the repository XML Index
Cause: The repository XML Index indexed one of the parent folders of the resource identified by given path.
Action: Try removing the parent folder from the repository XML Index.
ORA-44732: Path string cannot be removed from the repository XML Index
Cause: The repository XML Index did not index the resource identified by given path.
Action: Try removing a resource that is indexed by the repository XML Index.
ORA-44733: The repository XML Index cannot be dropped directly
Cause: DROP INDEX could not be used on the repository XML Index.
Action: Try using DBMS_XDB_ADMIN.DROPREPOSITORYXMLINDEX.
ORA-44751: XML schema enumeration index is out of range
Cause: The enumeration item corresponding to the enumeration index could not be found in the XML schema.
Action: If the XML schema has been evolved, try restarting the client that performed the evolution.
ORA-44752: New element 'string' in complex type 'string' has the same qualified name as another element
Cause: The new element that was added to a complex type by in-place XML schema evolution had the same qualified name as another element in the same complex type or in one of its ancestor complex types.
Action: Try adding an element with a different qualified name.
ORA-44753: Change to minOccurs attribute of element 'string' is illegal
Cause: The value of attribute minOccurs on an element could not be increased by in-place XML schema evolution.
Action: Do not increase the value of attribute minOccurs.
ORA-44754: Change to maxOccurs attribute of element 'string' is illegal
Cause: The value of attribute maxOccurs on an element could not be decreased by in-place XML schema evolution.
Action: Do not decrease the value of attribute maxOccurs.
ORA-44755: Change to complexType property of element 'string' is illegal
Cause: The complexType property on an element could not be changed by in-place XML schema evolution.
Action: Do not change the complexType property.
ORA-44756: Change to SQLType attribute of element 'string' is illegal
Cause: The SQLType property on an element in a binary XML schema could not be changed by in-place XML schema evolution.
Action: Do not change the SQLType property.
ORA-44800: Number of classifiers cannot be NULL
Cause: The num_classifiers argument was found to be NULL.
Action: Provide a non-NULL num_classifiers.
ORA-44801: NULL classifier list not permitted
Cause: The wlm_classifiers argument was found to be NULL.
Action: Provide a non-NULL wlm_classifiers.
ORA-44802: No new plan (classifier list) has been submitted
Cause: No new plan was created before submission.
Action: Create a new plan, followed by adding classifier & PC lists.
ORA-44803: Plan is in transition (about to be activated)
Cause: New plan was attempted to be created before activating the current plan.
Action: Completely submit the current plan and activate it.
ORA-44804: Plan is not created yet
Cause: A new plan was not created before submitting the Classifier and Performance Class lists.
Action: Call dbms_wlm.create_plan first to create the plan.
ORA-44805: No classifier is present
Cause: The classifier list contained no classifiers.
Action: Check the syntax of the classifier list.
ORA-44806: Extra classifiers are present in list
Cause: More classifiers were present in the list than specified.
Action: Only include the number of classifiers less than or equal to num_classifiers mentioned in dbms_wlm.create_plan.
ORA-44807: Peformance Class name is too large
Cause: The Performance Class name was larger than 32 bytes.
Action: Rename the Performance Class to fit within 32 bytes.
ORA-44808: Work Request Class name is too large
Cause: The Work Request Class name was larger than 32 bytes.
Action: Rename the Work Request Class to fit within 32 bytes.
ORA-44809: No expression is present for classifier
Cause: This classifiers contained no expression. It should contain one more more expressions.
Action: Check syntax in the classifier list.
ORA-44810: No parameter is present for expression
Cause: This expression contained no paramaters or attribute values. It should contain one or more attribute values. Attributes can be SERVICE, MODULE, ACTION, PROGRAM or USER.
Action: Check syntax in the classifier list.
ORA-44811: Service name is too large
Cause: The service name mentioned in the parameter list was too large.
Action: Check the service name.
ORA-44812: Module name is too large
Cause: The module name mentioned in the parameter list was too large.
Action: Check the module name.
ORA-44813: Action name is too large
Cause: The action name mentioned in the parameter list was too large.
Action: Check the action name.
ORA-44814: Program name is too large
Cause: The program name mentioned in the parameter list was too large.
Action: Check the program name.
ORA-44815: User name is too large
Cause: The user name mentioned in the parameter list was too large.
Action: Check the user name.
ORA-44816: Number of Performance Classes is less than specified
Cause: The number of Performance Classes submitted were less than what was specified.
Action: Submit the full list of Performance Classes.
ORA-44817: Classifier list is too large
Cause: The length of the classifier list was greater than 2048 bytes.
Action: Break the list into two lists before submission.
ORA-44818: General failure
Cause: There was an unknown failure.
Action: Contact Oracle Support Services.
ORA-44819: Execution of this WLM function is denied
Cause: Either a WLM plan was being loaded from another instance, or the strict order of the PL/SQL calls for loading WLM plan was not followed.
Action: Check if another session is also concurrently trying to load a WLM plan. If that is not true, check the order in which you are making these PL/SQL calls to load your WLM plan.
ORA-44820: Number of Work Request Classes is less than specified
Cause: The number of Work Request Classes submitted were less than what was specified.
Action: Submit the full list of Work Request Classes.
ORA-44821: Number of classifiers is too large
Cause: A very large number ( > 1024) of classifiers were requested.
Action: Submit a smaller ( < 1024) number of classifiers. /////////////////////////////////////////////////////////////////////////// 44901 - 44950 reserved for XML DB LINKS related error codes. ///////////////////////////////////////////////////////////////////////////
ORA-44901: Unable to resolve symbolic link "string"
Cause: The system is unable to resolve the specified symbolic link.
Action: Check the definition of the symbolic link to ensure that this refers to a valid resource.
ORA-44902: Too many steps in resolving symbolic link "string"
Cause: This error is raised when the system is unable to fully resolve a path with symbolic links within a reasonable number of steps. It could be due to cycles in definitions of symbolic links or very long chains of symbolic links to symbolic links.
Action: Remove any cycles in symbolic link definitions. If there are no cycles, reduce the length of chains of symbolic links to symbolic links.
ORA-44903: Cannot create hard link to specified resource
Cause: The system cannot create a hard link to the specified resource.
Action: Check the configuration parameter(s) to verify the restrictions on creating hard links to folder or non-folder resources.
ORA-44904: target path in document link exceeds maximum length
Cause: Target path length exceeds the maximum which can be stored to disk.
Action: Reduce target path to smaller length
ORA-44905: extended link type not supported
Cause: XLink type attribute is extended.
Action: Remove extended link, or replace with simple link.
ORA-44906: unable to resolve target in document link
Cause: target path does not resolve to valid resource.
Action: check validity of target path.
ORA-44907: can not delete with incoming hard document links
Cause: there is a hard document link with this resource as the target.
Action: query DOCUMENT_LINKS view to see which resource has a hard link to this resource. Change the document link in the source resource accordingly.
ORA-44908: found a loop in XInclude elements while expanding string
Cause: There is a loop in XInclude elements within the document.
Action: Remove the loop in XInclude elements.
ORA-44909: href attribute is required within XInclude element
Cause: The href attribute is missing within XInclude element.
Action: Add the href attribute.
ORA-44910: xpointer not supported within XInclude element
Cause: The xpointer attribute is specified within XInclude element.
Action: Remove the xpointer attribute.
ORA-44911: exceeded maximum depth of nested xinclude expansion
Cause: The depth of nested xinclude expansion has exceeded system limit.
Action: Reduce the depth of nested xinclude expansion.
ORA-44912: invalid or unsupported xpath expression string
Cause: The specified xpath is either invalid or unsupported in this context.
Action: Change the xpath expression.
ORA-44913: error while processing XInclude string
Cause: There was an error while processing the specified XInclude.
Action: Ensure that the XInclude attributes are correct.
