Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

 

LISTE CODE ERREURS ORACLE.

 

ORA-16800 ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE
Cause  The redo transport service for a standby database is currently set to ALTERNATE when no other destination is set to alternate to this destination.
Action  Reset the database state to turn on redo transport again if necessary.

 

ORA-16801 ORA-16801: redo transport-related property is inconsistent with database setting
Cause  The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker.
Action  Query property the InconsistentLogXptProps on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters.

 

ORA-16802 ORA-16802: downgrading redo transport mode from SYNC disallowed
Cause  An attempt was made to downgrade the redo transport mode of a standby database from SYNC to ASYNC or ARCH when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This is not allowed, even if there are other standby databases with log transport modes set to SYNC to support the data protection mode.
Action  You can do one of the following if you need to downgrade the redo transport mode of the standby database: (1) Shut down all instances of the primary database and restart one instance with initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode, shutdown the instance, and restart all instances with CLUSTER_DATABASE set to TRUE. (2) Downgrade the protection mode to Maximum Performance mode first. Then downgrade the redo transport mode, then upgrade the protection mode again (which involves a shutdown and restart of the primary database). Note that the above only works when there exists at least one more standby database in the configuration that has the log transport mode set to SYNC.

 

ORA-16803 ORA-16803: unable to query a database table or fixed view
Cause  Failed to query a database table or fixed view. The database may not be open or mounted.
Action  Check Data Guard broker log for more details.

 

ORA-16804 ORA-16804: one or more configuration properties in metadata have invalid values
Cause  Data Guard broker health check detected that one or more configuration properties in the broker"s configuration metadata have invalid values. The property values have been changed while broker management of the database is disabled.
Action  Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker.

 

ORA-16805 ORA-16805: change of LogXptMode property violates overall protection mode
Cause  The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database. The rejection was necessary to avoid violating the overall protection mode for the configuration.
Action  If the LogXptMode configuration property must be changed for the specified standby database, first downgrade the overall protection mode for the broker configuration. After that operation has completed, you will be able to change the LogXptMode configuration property for the standby database.

 

ORA-16806 ORA-16806: supplemental logging is not turned on
Cause  Supplemental logging was not turned on while there is a logical standby database in the configuration. This could happen either on the primary or on the logical standby database that is being switched over to be the primary database.
Action  Check Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.

 

ORA-16807 ORA-16807: unable to change database protection mode
Cause  An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed.
Action  Check the Oracle alert log and Data Guard broker log for more information.

 

ORA-16808 ORA-16808: unable to resolve the full path name
Cause  An attempt to resolve the full path name from a string failed.
Action  Check the Data Guard broker log for the full error stack. This likely the result of an operating system error.

 

ORA-16809 ORA-16809: multiple warnings detected for the database
Cause  The broker has detected multiple warnings for the database.
Action  Check the StatusReport monitorable property of the database specified.

 

ORA-16810 ORA-16810: multiple errors or warnings detected for the database
Cause  The broker detected multiple errors or warnings for the database.
Action  Check the StatusReport monitorable property of the database specified.

 

ORA-16811 ORA-16811: apply instance not recorded by the Data Guard broker
Cause  The broker has not registered an apply instance for a standby database.
Action  Reenable the standby database to clear the error.

 

ORA-16812 ORA-16812: log apply service not running on apply instance recorded by the broker
Cause  Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon.
Action  Reenable the standby database to clear the error.

 

ORA-16813 ORA-16813: log apply service not running on apply instance string recorded by the broker
Cause  Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon.
Action  Reenable the standby database to clear the error.

 

ORA-16814 ORA-16814: incorrect redo transport setting for AlternateLocation for standby database
Cause The Data Guard broker detected that an incorrect redo transport setting for a standby database"s AlternateLocation property. The incorrect setting could be one of the following: one of the following:
(1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting;
(2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting;
(3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute;
(4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE;
(5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.
Action  Reenable the primary database to clear the error.

 

ORA-16815 ORA-16815: incorrect redo transport setting for AlternateLocation for standby database "string"
Cause The Data Guard broker detected that the redo transport setting for the standby database regarding its AlternateLocation property value is incorrect. The incorrect setting could be one of the following:
(1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting;
(2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting;
(3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute;
(4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE;
(5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.
Action  Reenable the primary database to clear the error.

 

ORA-16816 ORA-16816: incorrect database role
Cause  The Data Guard broker detected that this database object had a database role that was different from the recorded database role in the Data Guard Configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database.
Action  Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database object.

 

ORA-16817 ORA-16817: unsynchronized Fast-Start Failover configuration
Cause  The Fast-Start Failover target standby database was not synchronized with the primary database. As a result, a Fast-Start Failover could not happen automatically in case of a primary database failure.
Action  Ensure that the Fast-Start Failover target standby database is running and that the primary database can ship redo logs to it. When the standby database has received all of the redo logs from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database.

 

ORA-16818 ORA-16818: Fast-Start Failover suspended
Cause  The primary database was intentionally shutdown. As a result, a Fast-Start Failover could not happen automatically.
Action  Start up the primary database. This effectively restores the ability to automatically do a Fast-Start Failover in the event of a failure of the primary database.

 

ORA-16819 ORA-16819: Fast-Start Failover observer not started
Cause  The observer for Fast-Start Failover was not started. As a result, Fast-Start Failover could not happen in the case of a primary database failure.
Action  Start the Fast-Start Failover observer by using, for example, the DGMGRL START OBSERVER command.

 

ORA-16820 ORA-16820: Fast-Start Failover observer is no longer observing this database
Cause  A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:
Action  Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL "STOP OBSERVER" command. Then restart the observer on another node. You may use the DGMGRL "START OBSERVER" command to start the observer on the other node.

 

ORA-16821 ORA-16821: logical standby database dictionary not yet loaded
Cause  Logical standby apply had not finished loading the dictionary. This warning is flagged by the broker"s health check mechanism. This error is also flagged by failover and switchover if the target standby database has not loaded its dictionary.
Action  Start SQL Apply on the logical standby database and wait for it to reach the APPLYING state.

 

ORA-16822 ORA-16822: new primary database not yet ready for standby database reinstatement
Cause  The new primary database, as a result of a logical failover operation, had not fully completed the failover steps. Subsequent reinstatement operations could not proceed until failover has completed on the new primary database.
Action  Wait until the completion of all failover steps on this new primary database and then retry the reinstate operation.

 

ORA-16823 ORA-16823: redo transport mode is incompatible for current operation
Cause  The redo transport mode of this database was incompatible for this broker operation.
Action  Reset the LogXptMode database property for this database and retry the broker operation.

 

ORA-16824 ORA-16824: Fast-Start Failover and other warnings detected for the database
Cause  The broker has detected multiple warnings for the database. At least one of the detected warnings may prevent a Fast-Start Failover from occurring.
Action  Check the StatusReport monitorable property of the database specified.

 

ORA-16825 ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause  The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action  Check the StatusReport monitorable property of the database specified.

 

ORA-16826 ORA-16826: apply service state is inconsistent with the DelayMins property
Cause  This warning was caused by one of the following reasons:
Action  Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property.

 

ORA-16950 ORA-16950: Remote mapped cursors are not supported by this feature.
Cause  This cursor is a remote mapped cursor which could not be processed locally.
Action  Try to process this statement directly on the remote site.

 

ORA-16951 ORA-16951: Too many bind variables supplied for this SQL statement.
Cause  Binding this SQL statement failed because too many bind variables were supplied.
Action  Pass the correct number of bind variables.

 

ORA-16952 ORA-16952: Failed to bind this SQL statement.
Cause  Binding this SQL statement failed.
Action  Check if bind variables for that statement are properly specified.

 

ORA-16953 ORA-16953: Type of SQL statement not supported.
Cause  This type of SQL statement could not be processed.
Action  none

 

ORA-16954 ORA-16954: SQL parse error.
Cause  The specified SQL statement failed to be parsed.
Action  Check if syntax is correct and ensure that this statement can be parsed by the specified user name.

 

ORA-16955 ORA-16955: Unknown error during SQL analyze.
Cause  The specified SQL statement failed to be analyzed.
Action  This is an internal error, please contact Oracle support.

 

ORA-16956 ORA-16956: Only SELECT or DML statements are supported for test execute.
Cause  The specified SQL statement cannot be tested for execute.
Action  none

 

ORA-16957 ORA-16957: SQL Analyze time limit interrupt
Cause  This is an internal error code used indicate that SQL analyze has reached its time limit.
Action  none

 

ORA-16958 ORA-16958: DML statements running parallel are not supported for test execute.
Cause  The specified DML statement cannot be tested for execute because part of it is running parallel.
Action  none

 

ORA-17500 ORA-17500: ODM err:string
Cause  An error returned by ODM library
Action  Look at error message and take appropriate action or contact Oracle Support Services for further assistance

 

ORA-17501 ORA-17501: logical block size string is invalid
Cause  logical block size for oracle files must be a multiple of the physical block size, and less than the maximum
Action  check INIT.ORA file parameters

 

ORA-17502 ORA-17502: ksfdcre:string Failed to create file string
Cause  file creation failed due to either insufficient OS permission or the file already exists
Action  check additional error messages

 

ORA-17503 ORA-17503: ksfdopn:string Failed to open file string
Cause  file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.
Action  check additional error messages

 

ORA-17504 ORA-17504: ksfddel:Failed to delete file string
Cause  The file that was being deleted is still in use or the process has insufficient permission to delete file.
Action  check additional error messages

 

ORA-17505 ORA-17505: ksfdrsz:string Failed to resize file to size string blocks
Cause  There is insufficient space left on the device or the process has insufficient permission to resize file.
Action  check additional error messages

 

ORA-17506 ORA-17506: I/O Error Simulation
Cause  The i/o request is marked with error because the i/o error simulation event is turned on.
Action  none

 

ORA-17507 ORA-17507: I/O request size string is not a multiple of logical block size
Cause  i/o"s are done in multiple of logical block size
Action  Check additional error messages

 

ORA-17508 ORA-17508: I/O request buffer ptr is not alligned
Cause  i/o request buffer should be alligned, check additional information for buffer ptr value
Action  Call Oracle Support Services

 

ORA-17509 ORA-17509: Attempt to do i/o beyond block1 offset
Cause  When a file is identified with logical block size of 0, only i/o"s to block1 is allowed.
Action  check additional error messages and call Oracle Support Services

 

ORA-17510 ORA-17510: Attempt to do i/o beyond file size
Cause  The i/o request points to a block beyond End Of File
Action  check additional error messages and call Oracle Support Services

 

ORA-17610 ORA-17610: file "string" does not exist and no size specified
Cause  An attempt to create a file a file found neither an existing file nor a size for creating the file.
Action  Specify a size for the file.

 

ORA-17611 ORA-17611: ksfd: file "string" cannot be accessed, global open closed
Cause  An attempt to write to a file which has gone offline/unidentified
Action  Check for other errno in the stack

 

ORA-17612 ORA-17612: Failed to discover Oracle Disk Manager library, return value string
Cause  Discovery of the odm library by calling odm_discover() failed
Action  Contact your storage vendor who has provided the ODM library or call Oracle Support

 

ORA-17613 ORA-17613: Failed to initialize Oracle Disk Manager library: string
Cause  ODM initialization for the thread failed due to insufficient previlige or memory.
Action  Make sure there is enough system resources available for the oracle process and it has access to the ODM library

 

ORA-17618 ORA-17618: Unable to update block 0 to version 10 format
Cause  An attempt was made to update block 0 to version 10 format.
Action  Check additional error messages and call Oracle Support Services

 

ORA-17619 ORA-17619: max number of processes using I/O slaves in a instance reached
Cause  An attempt was made to start large number of processes requiring I/O slaves.
Action  There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.

 

ORA-17620 ORA-17620: failed to register the network adapter with Oracle Disk Manager library: string
Cause  The ODM library returned an error while trying to register the network adapter.
Action  Make sure the network adapter name given in the fileio_network_adapters is a valid name, and that the Oracle user has the correct access privileges.

 

ORA-17621 ORA-17621: failed to register the memory with Oracle Disk Manager library
Cause  The ODM library returned an error while trying to register the memory.
Action  Contact the Oracle Disk Manager Library provider.

 

ORA-17622 ORA-17622: failed to deregister the memory with Oracle Disk Manager library
Cause  The ODM library returned an error while trying to deregister the memory.
Action  Contact the Oracle Disk Manager Library provider

 

ORA-17624 ORA-17624: Failed to delete directory string
Cause  The directory that was being deleted is still in use or the process had insufficient permission to delete the directory.
Action  check additional error messages.

 

ORA-17626 ORA-17626: ksfdcre: string file exists
Cause  trying to create a database file, but file by that name already exists
Action  verify that name is correct, specify REUSE if necessary

 

ORA-18000 ORA-18000: invalid outline name
Cause  The parser detected a missing or invalid outline name
Action  none

 

ORA-18001 ORA-18001: no options specified for ALTER OUTLINE
Cause  The parser detected that no clause was specified on the command Our performance tests, which are not typical as they exercise all branches of the code, have shown approximately a 30% performance increase line for ALTER OUTLINE.
Action  Re-issue the command, specifying a valid ALTER OUTLINE clause.

 

ORA-18002 ORA-18002: the specified outline does not exist
Cause  Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.
Action  none

 

ORA-18003 ORA-18003: an outline already exists with this signature
Cause  The signature generation algorithm generates signatures that are are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.
Action  Either re-issue the statement that led to the outline being created with some whitespace added or force the outline to be created in a different category.

 

ORA-18004 ORA-18004: outline already exists
Cause  An outline already exists, either with the specified name, or for the specified SQL text.
Action  none

 

ORA-18008 ORA-18008: cannot find OUTLN schema
Cause  The database creation script that creates this schema must not have been executed.
Action  Review the log files to see what happened when the database was created.

 

ORA-18009 ORA-18009: one or more outline system tables do not exist
Cause  Either the database creation script that creates these tables was not executed or a user accidently deleted the table
Action  Review the log files to see what happened when the database was created.

 

ORA-18010 ORA-18010: command missing mandatory CATEGORY keyword
Cause  User failed to specify the CATEGORY keyword
Action  Re-issue the command with the CATEGORY keyword included

 

ORA-18015 ORA-18015: invalid source outline signature
Cause  User imported an 8i outline into a 9i database without updating signatures
Action  execute dbms_outln.update_signatures

 

ORA-19000 ORA-19000: missing RELATIONAL keyword
Cause  The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.
Action  Supply the RELATIONAL keyword in the storage clause

 

ORA-19001 ORA-19001: Invalid storage option specified
Cause  An invalid storage option was specified for the XMLType.
Action  Supply a valid storage option.

 

ORA-19002 ORA-19002: Missing XMLSchema URL
Cause  A XML schema URL must be specified in the storage option.
Action  Specify a URL for the XMLSchema.

 

ORA-19003 ORA-19003: Missing XML root element name
Cause  A root element in the XMLSchema must be specified if the XML schema is given.
Action  Specify a root element in the XML schema.

 

ORA-19004 ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option
Cause  A duplicate storage option for the XMLType column was specified
Action  Specify a single storage option for an XMLType column

 

ORA-19005 ORA-19005: Duplicate XMLType LOB storage option
Cause  A duplicate storage option for the XMLType column was specified
Action  Specify a single storage option for an XMLType column

 

ORA-19006 ORA-19006: XMLType TYPE storage option not appropriate for storage type
Cause  The TYPE option can only be used in case of OBJECT RELATIONAL storage option
Action  Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column

 

ORA-19007 ORA-19007: Schema string does not match expected string.
Cause  The given XML document conformed to a different schema than expected.
Action  Insert/Update only the XML documents that conform to that particular schema.

 

ORA-19008 ORA-19008: Invalid version of the XMLType
Cause  An invalid version of the XMLType was found.
Action  This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database.

 

ORA-19009 ORA-19009: Missing XMLSchema keyword
Cause  The XMLSchema keyword is missing
Action  Specify the XMLSchema URL and element name.

 

ORA-19010 ORA-19010: Cannot insert XML fragments
Cause  XML fragments got from extractNode cannot be inserted into the database.
Action  Convert the fragment into a proper XML document before insertion.

 

ORA-19011 ORA-19011: Character string buffer too small
Cause  The string result asked for is too big to return back
Action  Get the result as a lob instead

 

ORA-19012 ORA-19012: Cannot convert XML fragment to the required datatype
Cause  A conversion to a datatype was requested which cannot be performed
Action  The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.

 

ORA-19013 ORA-19013: Cannot create VARRAY columns containing XMLType
Cause  An attempt was made to create a VARRAY column which contains a XMLType
Action  You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead

 

ORA-19015 ORA-19015: Invalid XML tag identifier (string)
Cause  An invalid XML identifer was detected during XML generation
Action  Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification

 

ORA-19016 ORA-19016: attributes cannot occur after element specifications
Cause  Attributes specified using the "@" identifier can only occur before any other element definition when creating XML
Action  Change the order of the types so that the attributes occur in the begining

 

ORA-19017 ORA-19017: Attributes can only be simple scalars
Cause  Attribute values can only be simple scalar values
Action  Use only simple datatypes for attribute values

 

ORA-19018 ORA-19018: Invalid character in XML tag "string"
Cause  A tag name was found to have an invalid XML character during XML generation.
Action  Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.

 

ORA-19019 ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML
Cause  The value of context passed to GETXML was invalid.
Action  Rewrite the query so that the value of context passed to GETXML is valid.

 

ORA-19020 ORA-19020: invalid dereference of XMLType columns
Cause  An attempt was made to dereference the attributes of an XMLType column which is not part of a base table
Action  You can only dereference the attributes of a base table XMLType column

 

ORA-19023 ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE
Cause  The first argument passed to the update value operator was not an XMLTYPE.
Action  Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.

 

ORA-19024 ORA-19024: Cursor expression must be named
Cause  The value of context passed to GETXML was invalid.
Action  Rewrite the query so that the value of context passed to GETXML is valid.

 

ORA-19025 ORA-19025: EXTRACTVALUE returns value of only one node
Cause  Given XPath points to more than one node.
Action  Rewrite the query so that exactly one node is returned.

 

ORA-19026 ORA-19026: EXTRACTVALUE can only retrieve value of leaf node
Cause  Given XPath does not point to a leaf node.
Action  Rewrite the query so that a leaf node is returned.

 

ORA-19028 ORA-19028: Invalid ADT parameter passed to toObject() function
Cause  The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.
Action  Pass an object of the correct type to toObject().

 

ORA-19029 ORA-19029: Cannot convert the given XMLType to the required type
Cause  The passed in XMLType could not be convert to the required type
Action  Binary XMLtype instances or other objects cannot be converted to the required object or collection types.

 

ORA-19030 ORA-19030: Method invalid for non-schema based XML Documents.
Cause  The method can be invoked on only schema based xmltype objects.
Action  Don"t invoke the method for non schema based xmltype objects.

 

ORA-19031 ORA-19031: XML element or attribute string does not match any in type string.string
Cause  The passed in XML tag does not match any in the object type
Action  Pass a valid canonical XML that can map to the given object type

 

ORA-19032 ORA-19032: Expected XML tag string got string
Cause  When converting XML to object, a wrong tag name was present
Action  Pass a valid canonical XML that can map to the given object type

 

ORA-19033 ORA-19033: schema specified in the XML document does not match the schema parameter
Cause  When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the "schema" parameter.
Action  Change the schema parameter to match the schema specified in the XML document.

 

ORA-19034 ORA-19034: Type not supported during schema generation
Cause  The object type contained a type that is not supported for schema generation.
Action  Use a different type or do not generate a schema.

 

ORA-19035 ORA-19035: Invalid select item of the query in newContextFromHierarchy()
Cause  The query does not have a number select item followed by an XMLType select item only.
Action  Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType.

 

ORA-19036 ORA-19036: Invalid query result set in newContextFromHierarchy()
Cause  The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query.
Action  Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query.

 

ORA-19037 ORA-19037: XMLType result can not be a fragment
Cause  The select item of the query in newContextFromHierarchy() is an XML fragment.
Action  Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment

 

ORA-19038 ORA-19038: Invalid opertions on query context
Cause  SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().
Action  SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().

 

ORA-19039 ORA-19039: Keyword string reserved for future use
Cause  The keyword is reserved for future use as a builtin function.
Action  Change the name mentioned above to a different one.

 

ORA-19040 ORA-19040: Element string does not match expected string.
Cause  The given XML document had a different root element than expected.
Action  Insert/Update only the XML documents that conform to that particular schema and element.

 

ORA-19041 ORA-19041: Comment data cannot contain two consecutive "-"s
Cause  The given comment string expression has two consecutive "-"s.
Action  Modify comment string to eliminate one or both of the consevutive "-"s.

 

ORA-19042 ORA-19042: Enclosing tag string cannot be xml in any case combination
Cause  The given enclosing tag matched "xml" in some case combination
Action  Modify the enclosing tag so that it is not xml in any case combination.

 

ORA-19043 ORA-19043: Multiply nested XMLROOT function disallowed
Cause  An XMLROOT function has an operand that is also an XMLROOT function.
Action  Modify the query so that there are no multiply nested XMLROOT functions.

 

ORA-19044 ORA-19044: character length specified for XMLSerialize is too small.
Cause  An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small.
Action  Modify the query so that the character length specified is larger.

 

ORA-19045 ORA-19045: character set id specified for XMLSerialize not valid
Cause  An XMLSerialize function was called with an invalid value for the caracter set id.
Action  Modify the query so that the character set id is valid.

 

Haut de Page www.dba-ora.fr

Partager cette page

Repost 0
Published by