ORA-53000 to ORA-54047

92 ORA-53000 to ORA-54047

ORA-53000: document type "<varname>string</varname>" is invalid: Cause: An invalid document type was specified.; Action: See the ORDDCM_DOCUMENT_TYPES view for a list of valid document types.
ORA-53001: <varname>TAG</varname> and <TAG_RANGE> tag values are null: Cause: An invalid attribute was found in the private dictionary document. The values specified by the <varname>TAG</varname> and <TAG_RANGE> tags were null.; Action: A private attribute definition must contain either a non-null <varname>TAG</varname> value or a non-null <TAG_RANGE> value. Correct the values and try the operation again. See the private dictionary schema (ordcmpv.xsd) listed in the Oracle Multimedia documentation for more information.
ORA-53002: document name "<varname>string</varname>" already inserted: Cause: The specified document name was found in the repository.; Action: Specify a unique document name and try again. See the ORDDCM_DOCUMENTS view for a list of document names.
ORA-53003: document <varname>string</varname> does not exist: Cause: The specified document name was not found in the repository.; Action: Correct the value and try again. See the ORDDCM_DOCUMENTS view for a list of documents in the repository.
ORA-53004: The value of tag <varname>VR</varname> "<varname>string</varname>" is invalid.: Cause: An invalid value for the <varname>VR</varname> tag was found in the dictionary document.; Action: Correct the value and try again. The value of the <varname>VR</varname> tag must either be a value defined by DICOM or an Oracle extension. See the data type schema (ordcmdt.xsd) listed in the Oracle Multimedia documentation for a list of valid <varname>VR</varname> tag values.
ORA-53005: tag references found in document: <varname>string</varname>: Cause: The delete operation failed because some tags in the dictionary document were being referenced by the listed document.; Action: To perform the delete operation, follow these steps: 1. Export the listed document to a file. 2. Delete the listed document from the repository. 3. Remove the referencing tags from the exported document. 4. Insert the updated document into the repository. 5. Repeat the delete operation.
ORA-53006: wild card characters are not allowed in <TAG_RANGE> tags: Cause: A <TAG_RANGE> tag containing wild card characters 'x' or 'X' was found in the dictionary document.; Action: Remove the wild card characters from <TAG_RANGE> tag and try again. See the Oracle Multimedia documentation for information about the private dictionary schema (ordcmpv.xsd).
ORA-53007: The document type STANDARD_DICTIONARY is not loaded.: Cause: The standard dictionary document was not found.; Action: Load the standard dictionary document (ordcmsd.xml). This is an installation error. Contact Oracle Support Services.
ORA-53008: The <varname>NAMESPACE</varname> tag value is not a registered schema.: Cause: The schema URL specified by the value of the <varname>NAMESPACE</varname> tag was not a registered Oracle XML DB schema.; Action: Specify a registered schema URL value. See the ALL_XML_SCHEMAS view for a list of registered schemas. See the Oracle XML DB Developers's Guide for information about registering schemas. See the Oracle Multimedia documentation for information about the mapping document schema (ordcmmp.xsd).
ORA-53009: cannot find the <ROOT_ELEM_TAG> tag value in the metadata schema: Cause: The value of the <ROOT_ELEM_TAG> tag was not found in the metadata schema specified by the value of the <varname>NAMESPACE</varname> tag.; Action: Correct the value and try again. You can either specify a valid value for the <ROOT_ELEM_TAG> tag or clear the value of the <varname>NAMESPACE</varname> tag. See the Oracle Multimedia documentation for information about the mapping document schema (ordcmmp.xsd).
ORA-53010: The value of the <varname>VR</varname> tag is null.: Cause: A null <varname>VR</varname> tag was found in the dictionary document.; Action: Correct the value and try again. If the value of the <varname>VR</varname> tag is null, then the value of the <varname>RETIRED</varname> tag must be set to true. See the Oracle Multimedia documentation for information about the standard dictionary schema (ordcmsd.xsd) and the private dictionary schema (ordcmpv.xsd).
ORA-53011: cannot find the <MAPPED_ELEM> tag value in the metadata schema: Cause: The value of the <MAPPED_ELEM> tag was not found in the metadata schema specified by the value of the <varname>NAMESPACE</varname> tag.; Action: Correct the value and try again. You can either specify a valid value for the <MAPPED_ELEM> tag or clear the value of the <varname>NAMESPACE</varname> tag. See the Oracle Multimedia documentation for information on the mapping document schema (ordcmmp.xsd).
ORA-53012: cannot find the <UNMAPPED_ELEM> tag value in the metadata schema: Cause: The value of the <UNMAPPED_ELEM> tag was not found in the metadata schema specified by the value of the <varname>NAMESPACE</varname> tag.; Action: Correct the value and try again. You can either specify a valid value for the <UNMAPPED_ELEM> tag or clear the value of the <varname>NAMESPACE</varname> tag. See the Oracle Multimedia documentation for information about the mapping document schema (ordcmmp.xsd).
ORA-53013: cannot find the <ATTRIBUTE_TAG> value: <varname>string</varname> in the dictionaries: Cause: The value of the specified <ATTRIBUTE_TAG> tag was not found in the standard or private dictionaries.; Action: Correct the tag and/or the definer name value and try again. The value of the <ATTRIBUTE_TAG> tag must refer to a tag and definer name specified in the data dictionaries.
ORA-53014: The runtime preference table is not empty: Cause: The function was unable to process due to an internal error.; Action: Contact Oracle Support Services.
ORA-53015: An internal dictionary attributes table is empty: Cause: This document could not be processed due to an internal error.; Action: Contact Oracle Support Services.
ORA-53016: null input argument: <varname>string</varname>: Cause: The function was unable to process due to an internal error; Action: Contact Oracle Support Services.
ORA-53017: The installation file <varname>string</varname> has an incorrect document type: Cause: An incorrect document type was specified for this file during installation. The function was unable to process due to an internal error.; Action: Contact Oracle Support Services.
ORA-53018: document <varname>string</varname> contains an unsupported encrypt action attribute: Cause: The operation failed because an unsupported encrypt action; Action: Change the value of the action attribute to none, remove or replace
ORA-53019: cannot delete installation document: <varname>string</varname>: Cause: The document could not be deleted because it was an installation document.; Action: See the ORDDCM_DOCUMENTS view for a list of the documents in the repository.
ORA-53020: invalid external reference in the constraint document: <varname>string</varname>: Cause: The referenced external rule or macro could not be found in the repository.; Action: Insert the referenced documents first and try again.
ORA-53021: cannot insert a rule or macro <varname>string</varname> that was already inserted: Cause: The rules or macros existed in the repository.; Action: Insert a new rule or macro.
ORA-53022: rules or macros in the constraint document <varname>string</varname> do not exist: Cause: The rules or macros did not exist in the repository.; Action: Delete or update an existing rule or macro.
ORA-53023: cannot delete or update a referenced rule or macro <varname>string</varname>: Cause: Because the rules or macros were referenced by other rules or macros, they could not be deleted or updated.; Action: Delete the referencing rules or macros first and try again.
ORA-53024: error processing constraint document: <varname>string</varname>: Cause: An error occurred while processing the constraint document.; Action: If the error described in the message can be corrected, do so; otherwise, contact Oracle Support Services.
ORA-53025: invalid constraint document: <varname>string</varname>: Cause: The constraint document was invalid.; Action: Correct the error described in the message and try again.
ORA-53026: failed to insert the constraint <varname>string</varname> to the database: Cause: An error occurred while trying to insert the constraint document into the database.; Action: Contact Oracle Support Services.
ORA-53027: invalid invocation of a macro <varname>string</varname> that is partially defined: Cause: Constraint rules could not invoke partially defined constraint macros.; Action: Ensure that all dependent constraint macros are inserted into the repository, then try the operation again.
ORA-53031: unable to export or import data model: <varname>string</varname>: Cause: An error occurred during export or import data model.; Action: If the error described in the message can be corrected, do so; otherwise, contact Oracle Support Services.
ORA-53032: The default preference document cannot be found.: Cause: The delete operation failed due to an internal error.; Action: When a user-defined preference document is deleted, the default values are restored from the Oracle default preference document. The default preference document is loaded during installation. If this document cannot be found, it is an unrecoverable error. Contact Oracle Support Services.
ORA-53033: The default UID Definition document cannot be found.: Cause: The delete operation failed due to an internal error.; Action: When a user-defined UID Definition document is deleted, the default values are restored from the Oracle default UID Definition document. The default UID Definition document is loaded during installation. If this document cannot be found, it is an unrecoverable error. Contact Oracle Support Services.
ORA-53034: document <varname>string</varname> contains an unsupported action attribute: Cause: The operation failed because an unsupported action attribute was found in the specified anonymity document.; Action: Change the value of the action attribute to none, remove or replace
ORA-53035: The rows for the mapping document (<varname>string</varname>) do not exist.: Cause: The delete operation failed due to an internal error.; Action: Contact Oracle Support Services.
ORA-53036: An internal table for the mapping document (<varname>string</varname>) is empty.: Cause: The function failed due to an internal error.; Action: Contact Oracle Support Services.
ORA-53037: invalid range tag, <START_TAG> <varname>string</varname> must be less than <END_TAG> <varname>string</varname>: Cause: The operation failed because an invalid range tag was specified.; Action: Correct the value and try the operation again.
ORA-53038: The data type name for tag: <varname>string</varname> cannot be found.: Cause: The function failed due to an internal error.; Action: Contact Oracle Support Services.
ORA-53039: user-defined preference document: <varname>string</varname> already exists: Cause: The insert operation failed because only one user-defined preference document is allowed.; Action: To change an existing user-defined preference document, follow these steps: 1. Export the specified document to a file. 2. Delete the specified document from the repository. 3. Make changes to the exported document. 4. Insert the updated document into the repository. To add a new user-defined preference document, follow these steps: 1. Delete the specified document from the repository. 2. Insert the new document into the repository.
ORA-53040: user-defined UID definition document: <varname>string</varname> already exists: Cause: The insert operation failed because only one user-defined UID definition document is allowed.; Action: To change an existing user-defined UID definition document, follow these steps: 1. Export the specified document to a file. 2. Delete the specified document from the repository. 3. Make changes to the exported document. 4. Insert the updated document into the repository. To add a new user-defined UID definition document, follow these steps: 1. Delete the specified document from the repsitory. 2. Insert the new document into the repository.
ORA-53041: The tag value for a replace action attribute is null.: Cause: The operation failed because a null tag value was found for a replace action attribute in the anonymity document; Action: Either add a non-null tag value for each replace action attribute
ORA-53042: tag <varname>string</varname> is referenced by document: <varname>string</varname>: Cause: The insert operation failed because the specified tag in the dictionary document was being referenced by the listed document.; Action: To perform the insert operation, follow these steps 1. Export the listed document to a file. 2. Delete the listed document from the repository. 3. Remove the specified tag from the exported document. 4. Insert the updated document into the repository. 5. Repeat the insert operation.
ORA-53043: tag <varname>string</varname> is referenced by unknown document: Cause: The operation failed because a tag in the specified dictionary document was being referenced by another document in the repository.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53044: invalid tag: <varname>string</varname>: Cause: The operation failed because the specified tag was invalid.; Action: The tag must match the regular expression ([0-9a-fA-FxX]{8}). Correct the tag format and try the operation again. See the dictionary schemas (ordcmsd.xsd, ordcmpv.xsd) listed in the Oracle Multimedia documentation for more information.
ORA-53045: invalid tag: <varname>string</varname>: Cause: The operation failed because the specified tag was invalid.; Action: The tag must match the regular expression ([0-9a-fA-F]{8}). Correct the tag format and try the operation again. See the dictionary schemas (ordcmsd.xsd, ordcmpv.xsd) listed in the Oracle Multimedia documentation for more information.
ORA-53046: tag: <varname>string</varname> collides with existing tag: <varname>string</varname> in document: <varname>string</varname>: Cause: The operation failed because the specified tag collided with an existing tag in the specified document.; Action: Tag collisions are not allowed in the dictionary documents. Correct the specified tag in the document and try the operation again.
ORA-53047: internal error: <varname>string</varname>: Cause: This document could not be processed due to an internal error.; Action: Contact Oracle Support Services.
ORA-53048: definer name DICOM is not allowed in a private dictionary: Cause: The operation failed because the definer name DICOM was found in the private dictionary.; Action: Correct the definer name and try the operation again.
ORA-53049: unsupported <ATTRIBUTE_TAG> tag value: <varname>string</varname>: Cause: The operation failed because the locator path with FIELD_TAG was not supported in the <ATTRIBUTE_TAG> tag in the anonymity document.; Action: Remove the FIELD_TAG in the locator path and try the operation again. See the Oracle Multimedia documentation for more information about locator path syntax.
ORA-53050: The data model is being edited by another user.: Cause: The operation failed because the data model was being edited by another user.; Action: The data model can be edited by only one administrator at a time.
ORA-53051: no editDataModel session found: Cause: The operation failed because there was no editDataModel session.; Action: Call the editDataModel procedure first and try the operation again.
ORA-53052: lock release returned error: <varname>string</varname>: Cause: The operation succeeded, but an error occurred while releasing a lock.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53053: lock request error: <varname>string</varname>: Cause: The operation failed because an exclusive lock could not be acquired.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53054: An editDataModel session already exists.: Cause: The editDataModel procedure was called more than once in the same session.; Action: Continue the insert or delete operations, call rollbackDataModel to rollback the data model changes, or call publishDataModel to publish the data model changes.
ORA-53055: empty data model table: Cause: The operation failed because the data model table was empty.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53056: unrecognized preference parameter name: <varname>string</varname>: Cause: The operation failed because the parameter name was invalid.; Action: Correct the value and try the operation again. See the preference schema (ordcmpf.xsd) listed in the Oracle Multimedia documentation for more information.
ORA-53057: invalid preference parameter value: <varname>string</varname>: Cause: The operation failed because the parameter value was invalid.; Action: Correct the value and try the operation again. See the preference schema (ordcmpf.xsd) listed in the Oracle Multimedia documentation for more information.
ORA-53058: The <ATTRIBUTE_TAG> value:<varname>string</varname> is not a simple tag.: Cause: The operation failed because the value of the specified <ATTRIBUTE_TAG> tag contained wild card characters 'x' or 'X'.; Action: Only simple tags that match the regular expression [0-9A-F]{8}(\(.*\))? are allowed in the <ATTRIBUTE_TAG> tag. For example: 00080096(DICOM), 00080096 and so on. Correct the tag format and try the operation again. See the schemas ordcmdt.xsd, ordcmmp.xsd, and ordcman.xsd listed in the Oracle Multimedia documentation for more information.
ORA-53059: document name: <varname>string</varname> is too long: Cause: A document name with more than 100 characters was specified.; Action: Use a shorter document name and try the operation again.
ORA-53060: <varname>string</varname> is not a standard attribute tag: Cause: The operation failed because the specified standard dictionary attribute tag did not have an even group number.; Action: A standard dictionary attribute tag represents a two-byte hexadecimal number (group number followed by element number) and must match the regular expression [0-9a-fA-FxX]{3}[02468aceACExX]{1}[0-9a-fA-FxX]{4}. Correct the attribute tag format and try the operation again.
ORA-53061: document name <varname>string</varname> contains reserved prefix - ORD: Cause: The operation failed because the specified document name contained the ORD prefix that is reserved for Oracle Multimedia documents.; Action: Remove the ORD prefix from the document name and try the operation again.
ORA-53062: invalid model name: <varname>string</varname>: Cause: The operation failed because the specified model name was invalid.; Action: The model name DEFAULT is the only value that is supported in this release. Remove the model name or replace it with the value DEFAULT and try the operation again.
ORA-53063: invalid exportOption: <varname>string</varname>: Cause: The specified value for the exportOption parameter was not valid.; Action: Valid values for the exportOption parameter are USER, ALL, or ORACLE. The default value is USER. Remove the specified value for the exportOption parameter or replace it with a valid value for this parameter.
ORA-53064: no user-defined documents to export: Cause: The value USER was specified for the exportOption parameter, but there were no user-defined documents in the repository.; Action: Valid values for the exportOption parameter are USER, ALL, or ORACLE. Specify another valid value for the exportOption parameter.
ORA-53065: stored tag list document: <varname>string</varname> already exists: Cause: The operation failed because only one stored tag list document is allowed.; Action: To change an existing stored tag list document, follow these steps: 1. Export the specified document to a file. 2. Delete the specified document from the repository. 3. Make changes to the exported document. 4. Insert the updated document into the repository. To add a new stored tag list document, follow these steps: 1. Delete the specified document from the repository. 2. Insert the new document into the repository.
ORA-53066: invalid manifest file: <varname>string</varname> or directory: <varname>string</varname>: Cause: The specified manifest file name or directory name was invalid.; Action: Confirm that the manifest file and the directory exist, and that the names are valid.
ORA-53067: validation failed for manifest file: <varname>string</varname>: Cause: The specified manifest file did not conform to the XML schema ordcmmft.xsd.; Action: Ensure that the manifest file conforms to the XML schema ordcmmft.xsd.
ORA-53068: cannot import data model because user-defined documents exist: Cause: User-defined documents were found in the repository.; Action: First export all user-defined documents in the repository so they can be saved, then delete all user-defined documents in the repository before importing a data model.
ORA-53069: doc version:<varname>string</varname> in <varname>string</varname> is not <= repos version:<varname>string</varname>: Cause: The document version of the specified document was not compatible with the repository version.; Action: You cannot import this data model into this version of the repository. Either upgrade or import a data model that is compatible with your repository version. See the Oracle Multimedia documentation for more information about document versioning considerations for the importDataModel procedure.
ORA-53070: manifest file:<varname>string</varname> does not contain all the Oracle documents: Cause: The specified manifest file did not contain the complete set of Oracle-defined documents that were included in the database release.; Action: A manifest file can contain all user-defined documents, all Oracle-defined documents, or both. Confirm that the manifest file includes all the documents listed in the orddcm_dbrelease_docs information view or no Oracle-defined documents. See the Oracle Multimedia documentation for more information on manifest files.
ORA-53071: tag: <varname>string</varname> from <varname>string</varname> is not listed in the stored tag list document: Cause: The specified document contained a tag that was not included in the stored tag list document.; Action: If the preference parameter MANDATE_ATTR_TAGS_IN_STL is set to true the stored tag list document must contain all the tags used by the constraint and mapping documents. Change the preference parameter value to false, or add the listed tag to the stored tag list document. See the Oracle Multimedia documentation for more information on stored tag list documents.
ORA-53072: even group number is not allowed in private tag: <varname>string</varname>: Cause: The operation failed because the specified private dictionary attribute tag contained an even group number.; Action: A dictionary attribute tag represents a two-byte hexadecimal number (a group number followed by an element number). Even group numbers are reserved for the DICOM Standard dictionary. Thus, the group number of a private dictionary attribute tag must be an odd number. Replace the even group number with an odd number in the specified attribute tag, and try the operation again.
ORA-53073: invalid docSet: <varname>string</varname>: Cause: The specified value for the docSet parameter was not valid.; Action: Valid values for the docSet parameter are USER, ALL, or ORACLE. The default value is USER. Remove the specified value for the docSet parameter, or replace it with a valid value.
ORA-53074: namespace value is too long: Cause: A namespace value longer than 700 characters was specified in the mapping document.; Action: Use a shorter namespace value and try the operation again.
ORA-53075: null ROOT_ELEM_TAG tag value: Cause: The value of the ROOT_ELEM_TAG tag was null or all spaces.; Action: Correct the value and try again.
ORA-53076: attempt to modify data model repository during rolling upgrade: Cause: An attempt was made to modify the Digital Imaging and Communications in Medicine (DICOM) data model in an administrator editing session during a rolling upgrade.; Action: Wait for the rolling upgrade to complete, then try the operation again. If a DICOM administrator editing session was in progress when the rolling upgrade was started, execute the rollbackDataModel() procedure to end the DICOM administrator session. Then, after the rolling upgrade completes, execute the editDataModel() procedure to restart the session.
ORA-53100: The repository data model is in invalid state.: Cause: Error detected while loading the data model from the repository.; Action: Contact Oracle Support Services.
ORA-53111: The repository data model is not loaded.: Cause: The operation failed because the ord_dicom.setDataModel procedure was not called to load the repository data model.; Action: Call the ord_dicom.setDataModel procedure first and try the operation again.
ORA-53112: unable to load repository: <varname>string</varname>: Cause: The ord_dicom.setDataModel procedure failed to load the repository due to the listed error.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53122: invalid document type : <varname>string</varname>: Cause: The ord_dicom.setDataModel procedure failed to load the repository because an invalid document type was found.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53124: cannot find VR number for data type: <varname>string</varname>: Cause: The VR number for the listed data type could not be found in the lookup table.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53125: invalid range tag: <varname>string</varname>: Cause: The ord_dicom.setDataModel procedure failed to load the repository because an invalid range tag was found in the dictionary table.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53126: assertion failure: <varname>string</varname>: Cause: The operation failed because an assertion error had occurred.; Action: This is an internal error. Contact Oracle Support Services.
ORA-53200: Argument <varname>string</varname> is null.: Cause: The argument was expecting a non-null value, but the value of the passed argument was null.; Action: Check your program and ensure that the caller of the routine does not pass a null argument value.
ORA-53201: Argument <varname>string</varname> is null or invalid.: Cause: The argument was expecting a non-null, valid value, but the value of the passed argument was null or invalid.; Action: Check your program and ensure that the caller of the routine does not pass a null or invalid argument value.
ORA-53202: internal error, argument [<varname>string</varname>]: Cause: The internal argument was invalid.; Action: Contact Oracle Support Services.
ORA-53203: security violation: Cause: A possible security violation was detected.; Action: Check the alert log and trace file for more information.
ORA-53210: unable to read empty DICOM object: Cause: There was no data in the specified DICOM object.; Action: See the Oracle Multimedia documentation for information about loading DICOM object data into the database.
ORA-53211: unable to read invalid ORDDicom object: Cause: The value of the source attribute or the extension attribute of the ORDDicom object was null.; Action: See the Oracle Multimedia documentation for information about creating a valid ORDDicom object.
ORA-53212: unable to read invalid ORDImage object: attribute <varname>string</varname> is null: Cause: The ORDImage object was invalid.; Action: See the Oracle Multimedia documentation for information about creating a valid ORDImage object.
ORA-53213: cannot access DICOM data with invalid source type: Cause: An invalid source type was stored in the source attribute of the ORDDicom object.; Action: See the Oracle Multimedia documentation for information about the supported source types for DICOM data.
ORA-53214: cannot access DICOM image data with invalid source type: Cause: An invalid source type was stored in the source attribute of the ORDImage object.; Action: See the Oracle Multimedia documentation for information about the supported source types for DICOM image data.
ORA-53215: cannot access ORDDataSource object with invalid source type: Cause: An invalid source type was stored in the ORDDataSource object. Or, an error occurred while trying to retrieve a BFILE while the object status was local.; Action: See the Oracle Multimedia documentation for information about the supported source types.
ORA-53216: cannot export the ORDDataSource object with an external source: Cause: The source of the ORDDataSource object was not local.; Action: Import the data before calling the export procedure. Or, get the data directly from the external source.
ORA-53217: The source LOB locator is null.: Cause: The source BLOB locator or BFILE locator was null.; Action: Correct the statement to pass an initialized LOB locator.
ORA-53230: unable to write to an invalid destination ORDDicom object: Cause: The value of the source attribute or the extension attribute of the destination ORDDicom object was null.; Action: See the Oracle Multimedia documentation for information about constructing a valid ORDDicom object.
ORA-53231: unable to write to a nonlocal destination ORDDicom object: Cause: The source attribute of the destination ORDDicom object was not local.; Action: See the Oracle Multimedia documentation for information about constructing a local ORDDicom object.
ORA-53232: unable to write to an invalid destination ORDImage object: Cause: The value of the source attribute of the destination ORDImage object was null.; Action: See the Oracle Multimedia documentation for information about constructing a valid ORDImage object.
ORA-53233: unable to write to a nonlocal destination ORDImage object: Cause: The source attribute of the destination ORDImage object was not local.; Action: See the Oracle Multimedia documentation for information about constructing a local ORDImage object.
ORA-53234: The destination BLOB locator is null.: Cause: The destination BLOB locator was null.; Action: Correct the statement to pass an initialized BLOB locator.
ORA-53250: Mapping document does not exist.: Cause: The specified mapping document did not exist.; Action: Check the installed mapping documents, and correct the statement to pass the name of an installed mapping document.
ORA-53251: Anonymity document does not exist.: Cause: The specified anonymity document did not exist.; Action: Check the installed anonymity definition documents, and correct the statement to pass the name of an installed anonymity definition document.
ORA-53252: Constraint does not exist.: Cause: The specified constraint did not exist.; Action: Check the installed constraints, and correct the statement to pass an installed constraint name.
ORA-53253: The metadata for the new DICOM object is invalid.: Cause: The metadata for the new DICOM object did not conform to the default metadata schema (ordcmmd.xsd).; Action: Check the metadata argument to ensure it has the correct namespace and conforms to the default metadata schema (ordcmmd.xsd). See the Oracle Multimedia documentation for information about the default metadata schema (ordcmmd.xsd).
ORA-53254: The SOP INSTANCE UID for the new DICOM object is invalid.: Cause: The SOP INSTANCE UID for the new DICOM object was invalid.; Action: See the Oracle Multimedia documentation for information about creating a valid SOP INSTANCE UID.
ORA-53255: cannot import from a null or invalid source type: Cause: A null or invalid source type was specified in the import procedure.; Action: See the Oracle Multimedia documentation for information about the supported source types for the DICOM object.
ORA-53256: cannot export to a null or invalid destination data type: Cause: A null or invalid destination data type was specified in the export procedure.; Action: See the Oracle Multimedia documentation for information about the supported destination data types for the DICOM object.
ORA-53257: Attribute does not exist.: Cause: The specified attribute did not exist.; Action: Ensure that the attribute name is valid.
ORA-53258: Metadata attribute is not available.: Cause: The value of the metadata attribute of the ORDDicom object was null.; Action: Call the setProperties method first.
ORA-53259: cannot extract metadata that conforms to the schema definition: Cause: The extracted metadata did not conform to its schema definition.; Action: Check the metadata schema definition, the mapping document and the parameters for the extractMetadata method to ensure that they are correct. See the Oracle Multimedia documentation for information about creating repository documents and extracting metadata.
ORA-53400: Missing DICOM magic number.: Cause: The DICOM object did not contain the DICOM magic number "dicm" required by part 10 of the DICOM standard.; Action: Fix the DICOM object or the DICOM object source, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53402: Missing DICOM header.: Cause: The DICOM object did not contain the file preamble.; Action: Fix the DICOM object or the DICOM object source, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53404: Missing the mandatory DICOM attribute <varname>string</varname>.: Cause: One or more mandatory DICOM attributes were missing from the DICOM object.; Action: Fix the DICOM object or the DICOM object source, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53406: The DICOM object contains invalid attribute value <varname>string</varname>.: Cause: The DICOM object did not conform to the DICOM standard and contained invalid attribute values.; Action: Fix the DICOM object or the DICOM object source, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53408: The DICOM object encoding is wrong <varname>string</varname>.: Cause: The DICOM object did not conform to the DICOM standard's binary encoding rules.; Action: Determine if the DICOM object is corrupt. If the DICOM object is not corrupt, verify whether it conforms to the binary encoding rules in the DICOM standard. If the DICOM object is corrupt, fix it if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53410: The attribute <varname>string</varname> does not conform to the VM rule.: Cause: The DICOM object either contained an attribute that did not conform to the DICOM value multiplicity rule or was missing an attribute that was required by the DICOM standard.; Action: Determine if the DICOM object conforms to the DICOM standard. If it does, verify if the data dictionary matches the DICOM object or is more recent than the DICOM object. If the data dictionary is obsolete, update it using the ORD_DICOM_ADMIN repository API, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53412: The DICOM object contains an invalid VR value <varname>string</varname>.: Cause: The DICOM object with explicit value representation encoding had attribute VR values that did not match their definitions in the data dictionary.; Action: Determine if the DICOM object conforms to the DICOM standard. If it does, verify if the data dictionary matches the DICOM object or is more recent than the DICOM object. If the data dictionary is obsolete, update it using the ORD_DICOM_ADMIN repository API, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53414: The DICOM object contains undefined values <varname>string</varname>.: Cause: The DICOM object had attribute values that were expected to be part of the data model.; Action: Determine if the DICOM object conforms to the DICOM standard. If it does, verify if the data model matches the DICOM object or is more recent than the DICOM object. If the data model is obsolete, update it using the ORD_DICOM_ADMIN repository API, if possible. Otherwise, update the DICOM preference document to ignore this category of error.
ORA-53430: The DICOM object contains unsupported values <varname>string</varname>.: Cause: This type of DICOM object is not supported by the current release.; Action: Check for software updates, and contact Oracle Support Services for information about feature enhancements.
ORA-53432: The DICOM object attribute <varname>string</varname> has invalid definer name.: Cause: A private attribute definer for a private attribute contained in this DICOM object had invalid characters.; Action: Determine if the DICOM object is corrupt. If the DICOM object conforms to the DICOM standard, contact Oracle Support Services.
ORA-53434: Not a DICOM object.: Cause: The binary object is not a DICOM object.; Action: Determine if the DICOM object is corrupt. If the DICOM object conforms to the DICOM standard, contact Oracle Support Services.
ORA-53500: Not a DICOM image.: Cause: The binary object was not a DICOM image.; Action: Determine if the DICOM object is an image. Only DICOM images can be processed with image processing functions.
ORA-53502: Image processing failure.: Cause: An error occurred when processing a DICOM image.; Action: Determine if the DICOM image is corrupt, and if it is supported by the current release.
ORA-53800: The DICOM object does not contain attribute <varname>string</varname>.: Cause: The DICOM object did not contain the attribute that was required for conformance validation.; Action: Determine if the locator path is properly constructed. All attributes used in the locator path must be defined in the DICOM standard, and must not be retired. All attributes except the last attribute in the locator path must be of sequence type. If the locator path is correct, verify if the DICOM data dictionary is up to date. If the data dictionary is obsolete, update it using the ORD_DICOM_ADMIN repository API.
ORA-53801: cannot apply conformance validation on DICOM attribute <varname>string</varname>.: Cause: The content length of the attribute exceeded the value of the XML_SKIP_ATTR parameter that was defined in the preference document.; Action: Remove the attribute from the constraint rule or increase the value of the XML_SKIP_ATTR parameter that is defined in the preference document. Then, attempt the operation again.
ORA-53802: cannot perform conformance validation because recursion level exceeds MAX_RECURSION_DEPTH: Cause: When evaluating the recursive constraint on the DICOM object, the number of levels of recursion exceeded the value of the MAX_RECURSION_DEPTH parameter that was defined in the preference document.; Action: Ensure that the constraint definition is correct. If necessary, increase the value of the MAX_RECURSION_DEPTH parameter that is defined in the preference document. Then, attempt the operation again.
ORA-53810: error logging conformance validation messages: Cause: An error occurred while trying to log conformance validation messages.; Action: Ensure that the constraint rule definition does not contain any ACTION elements if the isConformanceValid method is called from a SQL query. If this error persists, contact Oracle Support Services.
ORA-53820: Invalid locator path <varname>string</varname>: Cause: A locator path for an attribute was invalid.; Action: Please verify the locator path is properly constructed. All attribute used in the locator path must be defined in the DICOM standard and must not be retired. An attribute that is not the last one of the locator path must be a sequence type. If the locator path is correct, please verify the DICOM data dictionary is up-to-date. If the data dictionary is obsolete, please use the ORD_DICOM_ADMIN API to update the data dictionary.
ORA-53900: I/O failure <varname>string</varname>.: Cause: A device I/O failure occurred when attempting to read from and write to a DICOM object.; Action: Check the permissions and privileges that have been granted for I/O operations.
ORA-53910: SQL error <varname>string</varname>.: Cause: An error occurred when attempting to run a SQL command.; Action: If you are using a JDBC connection string, ensure that the connection string is valid. Check the user account to see if it is locked. Ensure that the listener and the database server are running. And ensure that the setDataModel() function has been invoked before any other DICOM functions are called.
ORA-53920: XML error <varname>string</varname>.: Cause: An error occurred when attempting to read from and write to XML metadata.; Action: Ensure that Oracle XDB and all related schemas are properly installed.
ORA-53930: XSLT error <varname>string</varname>.: Cause: An error occurred while attempting to process XML metadata.; Action: Ensure that Oracle XDB and all related schemas are properly installed. And, verify that the mapping and anonymity documents are valid.
ORA-53940: make anonymous error <varname>string</varname>.: Cause: An error occurred while attempting to make DICOM object anonymous.; Action: Ensure that the anonymity document content is valid.
ORA-53980: unimplemented feature: <varname>string</varname>: Cause: The specified feature is not implemented.; Action: Contact Oracle Support Services.
ORA-53990: internal error <varname>string</varname>.: Cause: An internal error occurred while attempting to process a DICOM object.; Action: Contact Oracle Support Services, and supply them with a script that can be duplicated as well as the DICOM object that caused this error.
ORA-53991: cannot move tablespace because tables are being used: Cause: The operation failed because Oracle Multimedia tables were being used.; Action: End all sessions using Oracle Multimedia tables and try again.
ORA-54000: Virtual column feature not yet implemented: Cause: Feature has not been implemented.; Action: Feature is being implemented.
ORA-54001: <varname>string</varname>: invalid identifier specified for virtual column expression: Cause: Column expression referenced a column that does not exist in the table.; Action: Rewrite column expression to reference only scalar columns in the table.
ORA-54002: only pure functions can be specified in a virtual column expression: Cause: Column expression contained a function whose evaluation is non-deterministic.; Action: Rewrite column expression to reference only pure functions.
ORA-54003: specified data type is not supported for a virtual column: Cause: Only scalar data types are supported for virtual columns. LONG, BLOB, REF, and BFILE data types are not supported for virtual columns.; Action: Specify the expression column with a supported scalar data type.
ORA-54004: resultant data type of virtual column is not supported: Cause: The data type of the underlying expression is not supported. Only scalar data types are supported for virtual columns. LONG, BLOB, REF, and BFILE data types are not supported for virtual columns.; Action: Specify the expression of virtual column to return a supported scalar data type.
ORA-54005: keyword VIRTUAL cannot be specified here: Cause: The keyword VIRTUAL was either repeated or incorrectly specified.; Action: Remove the keyword from the specified syntax.
ORA-54006: keyword VISIBLE cannot be specified here: Cause: The keyword VISIBLE was either repeated or incorrectly specified.; Action: Remove the keyword from the specified syntax.
ORA-54007: keyword HIDDEN cannot be specified here: Cause: The keyword HIDDEN was either repeated or incorrectly specified.; Action: Remove the keyword from the specified syntax.
ORA-54008: expression column is not supported for an index organized table: Cause: Attempt to create/alter an index organized table with an expression column; Action: These columns are not supported, change the DDL.
ORA-54009: expression column is not supported for an external table: Cause: Attempt to create/alter an external table with an expression column; Action: These columns are not supported, change the DDL.
ORA-54010: expression column is not supported for a temporary table: Cause: Attempt to create/alter a temporary table with an expression column; Action: These columns are not supported, change the DDL.
ORA-54011: expression column is not supported for a clustered table: Cause: Attempt to create/alter a clustered table with an expression column; Action: These columns are not supported, change the DDL.
ORA-54012: virtual column is referenced in a column expression: Cause: This virtual column was referenced in an expression of another virtual column; Action: Ensure the column expression definition for any virtual column does not refer to any virtual column
ORA-54013: INSERT operation disallowed on virtual columns: Cause: Attempted to insert values into a virtual column; Action: Re-issue the statment without providing values for a virtual column
ORA-54014: Resulting table from a CTAS operation contains virtual column(s): Cause: Table being created by a CTAS operation contains a virtual column definition; Action: Remove the virtual column definition from the table being created
ORA-54015: Duplicate column expression was specified: Cause: Expression of the virtual column being added/created conflicts with an existing/previously specified functional index expression or virtual column expression; Action: Change the expression of the virtual column os there are no duplicate expressions
ORA-54016: Invalid column expression was specified: Cause: Virtual column expression is not a valid arithmetic expression. it probably refers to another column in the table; Action: Change the expression of the virtual column
ORA-54017: UPDATE operation disallowed on virtual columns: Cause: Attempted to update values of a virtual column; Action: Re-issue the statment without setting values for the virtual column
ORA-54018: A virtual column exists for this expression: Cause: Specified index expression matches an existing virtual column"; Action: Re-issue the statment by replacing the index expression with the matching virtual column
ORA-54019: Virtual column expression cannot be changed because it is a partitioning column: Cause: Attempted to modify the expression of a virtual column that was also a partitioning column.; Action: This is not supported.
ORA-54020: Virtual column expression cannot be changed because it is a subpartitioning column: Cause: Attempted to modify the expression of a virtual column that was also a subpartitioning column.; Action: This is not supported.
ORA-54021: Cannot use PL/SQL expressions in partitioning or subpartitioning columns: Cause: Attempted to partition a table on a virtual column that contained PL/SQL expressions.; Action: This is not supported.
ORA-54022: Virtual column expression cannot be changed because an index is defined on column: Cause: Attempted to change the expression of a virtual column that was indexed.; Action: Alter index unsable. Change expression and then rebuild index.
ORA-54023: Virtual column expression cannot be changed because a constraint is defined on column: Cause: Attempted to change the expression of a virtual column that had a constraint defined on it.; Action: Drop constraint and then change expression.
ORA-54024: expression column is not supported for an organization cube table: Cause: Attempted to create or alter an organization cube table with an expression column; Action: These columns are not supported, change the DDL.
ORA-54025: Virtual column cannot have a default value: Cause: Attempted to alter a virtual column to have a default value.; Action: This is not valid, change the DDL.
ORA-54026: Real column cannot have an expression: Cause: Attempted to alter a real column to have an expression.; Action: This is not valid, change the DDL.
ORA-54027: cannot modify data-type of virtual column: Cause: Attempted to change the data-type of virtual column without modifying the underlying expression; Action: change the underlying expression to be compatible with the data-type change
ORA-54028: cannot change the HIDDEN/VISIBLE property of a virtual column: Cause: Attempted to change the HIDDEN/VIRTUAL property of a virtual column; Action: re-issue the DDL without the virtual column property change
ORA-54029: Virtual column cannot be updated in trigger body: Cause: Attempted to change the value of virtual column in a trigger body"; Action: This is not valid, change the trigger definition.
ORA-54030: datatype mismatch between virtual column and expression: Cause: virtual column expression was changed after column was created"; Action: change the underlying expression to return datatype that conforms to the virtual column
ORA-54031: column to be dropped or modified is used in a virtual column expression: Cause: Attempted to drop or modify a column that was used in a virtual column expression.; Action: Drop the virtual column first or change the virtual column expression to eliminate dependency on the column to be dropped.
ORA-54032: column to be renamed is used in a virtual column expression: Cause: Attempted to rename a column that was used in a virtual column expression.; Action: Drop the virtual column first or change the virtual column expression to eliminate dependency on the column to be renamed.
ORA-54033: column to be modified is used in a virtual column expression: Cause: Attempted to modify the data type of a column that was used in a virtual column expression.; Action: Drop the virtual column first or change the virtual column expression to eliminate dependency on the column to be modified.
ORA-54034: virtual columns not allowed in functional index expressions: Cause: An attempt was made to create a functional index with an expression defined on one or more virtual columns.; Action: Specify the index expression using only regular columns.
ORA-54035: keyword HIDDEN cannot be specified here: Cause: Attempted to specify HIDDEN key word for a virtual column; Action: This is not supported.
ORA-54036: cannot define referential constraint with ON DELETE SET NULL clause on virtual column: Cause: Attempted to specify ON DELETE SET NULL clause for a referential integrity constraint on a virtual column.; Action: Reissue the statement without specifying ON DELETE SET NULL clause.
ORA-54037: table must have at least 1 column that is not virtual: Cause: An attempt was made to create a table with only virtual columns.; Action: Include at least 1 column that is not virtual in the table being created.
ORA-54038: Virtual column cannot be encrypted: Cause: An attempt was made to create or alter a virtual column to have encryption.; Action: Encryption is unnecessary for a virtual column as the data is not stored on disk.
ORA-54039: table must have at least one column that is not invisible: Cause: An attempt was made to create or alter a table to have only invisible columns.; Action: Include at least one column that is not invisible in the table being created or altered.
ORA-54040: Visibility of a system-generated column cannot be changed.: Cause: An attempt was made to alter the visibility of a system-generated column.; Action: This is not supported.
ORA-54041: Visibility of an abstract data type column cannot be changed.: Cause: An attempt was made to alter the visibility of an abstract data type column.; Action: Specify the column visibility change with a supported data type.
ORA-54042: Invisible column is not supported on this type of table.: Cause: An attempt was made to create or alter the visibility of a column on an unsupported table type. Invisible columns are only supported for heap and index-organized tables (IOT).; Action: These columns are not supported, change the DDL.
ORA-54043: Including column of an IOT cannot be an invisible column.: Cause: An attempt was made to alter the visibility of the included column of an index-organized table (IOT).; Action: This is not supported.
ORA-54044: Visibility of a column having a column-level object privilege cannot be changed.: Cause: An attempt was made to alter the visibility of a column with a column-level object privilege.; Action: Revoke the column-level object privilege before making the column invisible.
ORA-54045: An invisible column cannot be granted a column-level object privilege.: Cause: An attempt was made to grant a column-level object privilege to an invisible column.; Action: Modify the column to make it visible and then grant the column-level object privilege.
ORA-54046: Column visibility modifications cannot be combined with any other modified column DDL option.: Cause: An attempt was made to combine the modification of the visibility of a column with other modified column property changes.; Action: Separate column visibility modifications into a standalone DDL.
ORA-54047: virtual columns not allowed for XMLType tables with object-relational storage: Cause: An attempt was made to create an object-relational XMLType table with virtual columns.; Action: Do not create virtual columns for XMLType tables with object-relational storage . This feature is not available.