96 ORA-53000 to ORA-54056
- ORA-53000: document type "string" is invalid
-
Cause: An invalid document type was specified.
- ORA-53001: TAG and <TAG_RANGE> tag values are null
-
Cause: An invalid attribute was found in the private dictionary document. The values specified by the TAG and <TAG_RANGE> tags were null.
- ORA-53002: document name "string" already inserted
-
Cause: The specified document name was found in the repository.
- ORA-53003: document string does not exist
-
Cause: The specified document name was not found in the repository.
- ORA-53004: The value of tag VR "string" is invalid.
-
Cause: An invalid value for the VR tag was found in the dictionary document.
- ORA-53005: tag references found in document: string
-
Cause: The delete operation failed because some tags in the dictionary document were being referenced by the listed document.
- 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.
- ORA-53007: The document type STANDARD_DICTIONARY is not loaded.
-
Cause: The standard dictionary document was not found.
- ORA-53008: The NAMESPACE tag value is not a registered schema.
-
Cause: The schema URL specified by the value of the NAMESPACE tag was not a registered Oracle XML DB schema.
- 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 NAMESPACE tag.
- ORA-53010: The value of the VR tag is null.
-
Cause: A null VR tag was found in the dictionary document.
- 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 NAMESPACE tag.
- 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 NAMESPACE tag.
- ORA-53013: cannot find the <ATTRIBUTE_TAG> value: string in the dictionaries
-
Cause: The value of the specified <ATTRIBUTE_TAG> tag was not found in the standard or private dictionaries.
- ORA-53014: The runtime preference table is not empty
-
Cause: The function was unable to process due to an internal error.
- ORA-53015: An internal dictionary attributes table is empty
-
Cause: This document could not be processed due to an internal error.
- ORA-53016: null input argument: string
-
Cause: The function was unable to process due to an internal error
- ORA-53017: The installation file string 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.
- ORA-53018: document string contains an unsupported encrypt action attribute
-
Cause: The operation failed because an unsupported encrypt action
- ORA-53019: cannot delete installation document: string
-
Cause: The document could not be deleted because it was an installation document.
- ORA-53020: invalid external reference in the constraint document: string
-
Cause: The referenced external rule or macro could not be found in the repository.
- ORA-53021: cannot insert a rule or macro string that was already inserted
-
Cause: The rules or macros existed in the repository.
- ORA-53022: rules or macros in the constraint document string do not exist
-
Cause: The rules or macros did not exist in the repository.
- ORA-53023: cannot delete or update a referenced rule or macro string
-
Cause: Because the rules or macros were referenced by other rules or macros, they could not be deleted or updated.
- ORA-53024: error processing constraint document: string
-
Cause: An error occurred while processing the constraint document.
- ORA-53025: invalid constraint document: string
-
Cause: The constraint document was invalid.
- ORA-53026: failed to insert the constraint string to the database
-
Cause: An error occurred while trying to insert the constraint document into the database.
- ORA-53027: invalid invocation of a macro string that is partially defined
-
Cause: Constraint rules could not invoke partially defined constraint macros.
- ORA-53031: unable to export or import data model: string
-
Cause: An error occurred during export or import data model.
- ORA-53032: The default preference document cannot be found.
-
Cause: The delete operation failed due to an internal error.
- ORA-53033: The default UID Definition document cannot be found.
-
Cause: The delete operation failed due to an internal error.
- ORA-53034: document string contains an unsupported action attribute
-
Cause: The operation failed because an unsupported action attribute was found in the specified anonymity document.
- ORA-53035: The rows for the mapping document (string) do not exist.
-
Cause: The delete operation failed due to an internal error.
- ORA-53036: An internal table for the mapping document (string) is empty.
-
Cause: The function failed due to an internal error.
- ORA-53037: invalid range tag, <START_TAG> string must be less than <END_TAG> string
-
Cause: The operation failed because an invalid range tag was specified.
- ORA-53038: The data type name for tag: string cannot be found.
-
Cause: The function failed due to an internal error.
- ORA-53039: user-defined preference document: string already exists
-
Cause: The insert operation failed because only one user-defined preference document is allowed.
- ORA-53040: user-defined UID definition document: string already exists
-
Cause: The insert operation failed because only one user-defined UID definition document is allowed.
- 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
- ORA-53042: tag string is referenced by document: string
-
Cause: The insert operation failed because the specified tag in the dictionary document was being referenced by the listed document.
- ORA-53043: tag string 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.
- ORA-53044: invalid tag: string
-
Cause: The operation failed because the specified tag was invalid.
- ORA-53045: invalid tag: string
-
Cause: The operation failed because the specified tag was invalid.
- ORA-53046: tag: string collides with existing tag: string in document: string
-
Cause: The operation failed because the specified tag collided with an existing tag in the specified document.
- ORA-53047: internal error: string
-
Cause: This document could not be processed due to an internal error.
- 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.
- ORA-53049: unsupported <ATTRIBUTE_TAG> tag value: string
-
Cause: The operation failed because the locator path with FIELD_TAG was not supported in the <ATTRIBUTE_TAG> tag in the anonymity document.
- 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.
- ORA-53051: no editDataModel session found
-
Cause: The operation failed because there was no editDataModel session.
- ORA-53052: lock release returned error: string
-
Cause: The operation succeeded, but an error occurred while releasing a lock.
- ORA-53053: lock request error: string
-
Cause: The operation failed because an exclusive lock could not be acquired.
- ORA-53054: An editDataModel session already exists.
-
Cause: The editDataModel procedure was called more than once in the same session.
- ORA-53055: empty data model table
-
Cause: The operation failed because the data model table was empty.
- ORA-53056: unrecognized preference parameter name: string
-
Cause: The operation failed because the parameter name was invalid.
- ORA-53057: invalid preference parameter value: string
-
Cause: The operation failed because the parameter value was invalid.
- ORA-53058: The <ATTRIBUTE_TAG> value:string 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'.
- ORA-53059: document name: string is too long
-
Cause: A document name with more than 100 characters was specified.
- ORA-53060: string is not a standard attribute tag
-
Cause: The operation failed because the specified standard dictionary attribute tag did not have an even group number.
- ORA-53061: document name string contains reserved prefix - ORD
-
Cause: The operation failed because the specified document name contained the ORD prefix that is reserved for Oracle Multimedia documents.
- ORA-53062: invalid model name: string
-
Cause: The operation failed because the specified model name was invalid.
- ORA-53063: invalid exportOption: string
-
Cause: The specified value for the exportOption parameter was not valid.
- 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.
- ORA-53065: stored tag list document: string already exists
-
Cause: The operation failed because only one stored tag list document is allowed.
- ORA-53066: invalid manifest file: string or directory: string
-
Cause: The specified manifest file name or directory name was invalid.
- ORA-53067: validation failed for manifest file: string
-
Cause: The specified manifest file did not conform 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.
- ORA-53069: doc version:string in string is not <= repos version:string
-
Cause: The document version of the specified document was not compatible with the repository version.
- ORA-53070: manifest file:string 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.
- ORA-53071: tag: string from string 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.
- ORA-53072: even group number is not allowed in private tag: string
-
Cause: The operation failed because the specified private dictionary attribute tag contained an even group number.
- ORA-53073: invalid docSet: string
-
Cause: The specified value for the docSet parameter was not valid.
- ORA-53074: namespace value is too long
-
Cause: A namespace value longer than 700 characters was specified in the mapping document.
- ORA-53075: null ROOT_ELEM_TAG tag value
-
Cause: The value of the ROOT_ELEM_TAG tag was null or all spaces.
- 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.
- ORA-53100: The repository data model is in invalid state.
-
Cause: Error detected while loading the data model from the repository.
- 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.
- ORA-53112: unable to load repository: string
-
Cause: The ord_dicom.setDataModel procedure failed to load the repository due to the listed error.
- ORA-53122: invalid document type : string
-
Cause: The ord_dicom.setDataModel procedure failed to load the repository because an invalid document type was found.
- ORA-53124: cannot find VR number for data type: string
-
Cause: The VR number for the listed data type could not be found in the lookup table.
- ORA-53125: invalid range tag: string
-
Cause: The ord_dicom.setDataModel procedure failed to load the repository because an invalid range tag was found in the dictionary table.
- ORA-53126: assertion failure: string
-
Cause: The operation failed because an assertion error had occurred.
- ORA-53200: Argument string is null.
-
Cause: The argument was expecting a non-null value, but the value of the passed argument was null.
- ORA-53201: Argument string 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.
- ORA-53202: internal error, argument [string]
-
Cause: The internal argument was invalid.
- ORA-53203: security violation
-
Cause: A possible security violation was detected.
- ORA-53204: internal interface called
-
Cause: An internal interface was called.
- ORA-53210: unable to read empty DICOM object
-
Cause: There was no data in the specified DICOM object.
- 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.
- ORA-53212: unable to read invalid ORDImage object: attribute string is null
-
Cause: The ORDImage object was invalid.
- 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.
- 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.
- 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.
- ORA-53216: cannot export the ORDDataSource object with an external source
-
Cause: The source of the ORDDataSource object was not local.
- ORA-53217: The source LOB locator is null.
-
Cause: The source BLOB locator or BFILE locator was null.
- 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.
- ORA-53231: unable to write to a nonlocal destination ORDDicom object
-
Cause: The source attribute of the destination ORDDicom object was not local.
- 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.
- ORA-53233: unable to write to a nonlocal destination ORDImage object
-
Cause: The source attribute of the destination ORDImage object was not local.
- ORA-53234: The destination BLOB locator is null.
-
Cause: The destination BLOB locator was null.
- ORA-53250: Mapping document does not exist.
-
Cause: The specified mapping document did not exist.
- ORA-53251: Anonymity document does not exist.
-
Cause: The specified anonymity document did not exist.
- ORA-53252: Constraint does not exist.
-
Cause: The specified constraint did not exist.
- 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).
- 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.
- ORA-53255: cannot import from a null or invalid source type
-
Cause: A null or invalid source type was specified in the import procedure.
- 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.
- ORA-53257: Attribute does not exist.
-
Cause: The specified attribute did not exist.
- ORA-53258: Metadata attribute is not available.
-
Cause: The value of the metadata attribute of the ORDDicom object was null.
- ORA-53259: cannot extract metadata that conforms to the schema definition
-
Cause: The extracted metadata did not conform to its schema definition.
- 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.
- ORA-53402: Missing DICOM header.
-
Cause: The DICOM object did not contain the file preamble.
- ORA-53404: Missing the mandatory DICOM attribute string.
-
Cause: One or more mandatory DICOM attributes were missing from the DICOM object.
- ORA-53406: The DICOM object contains invalid attribute value string.
-
Cause: The DICOM object did not conform to the DICOM standard and contained invalid attribute values.
- ORA-53408: The DICOM object encoding is wrong string.
-
Cause: The DICOM object did not conform to the DICOM standard's binary encoding rules.
- ORA-53410: The attribute string 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.
- ORA-53412: The DICOM object contains an invalid VR value string.
-
Cause: The DICOM object with explicit value representation encoding had attribute VR values that did not match their definitions in the data dictionary.
- ORA-53414: The DICOM object contains undefined values string.
-
Cause: The DICOM object had attribute values that were expected to be part of the data model.
- ORA-53430: The DICOM object contains unsupported values string.
-
Cause: This type of DICOM object is not supported by the current release.
- ORA-53432: The DICOM object attribute string has invalid definer name.
-
Cause: A private attribute definer for a private attribute contained in this DICOM object had invalid characters.
- ORA-53434: Not a DICOM object.
-
Cause: The binary object is not a DICOM object.
- ORA-53500: Not a DICOM image.
-
Cause: The binary object was not a DICOM image.
- ORA-53502: Image processing failure.
-
Cause: An error occurred when processing a DICOM image.
- ORA-53800: The DICOM object does not contain attribute string.
-
Cause: The DICOM object did not contain the attribute that was required for conformance validation.
- ORA-53801: cannot apply conformance validation on DICOM attribute string.
-
Cause: The content length of the attribute exceeded the value of the XML_SKIP_ATTR parameter that was defined in the preference document.
- 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.
- ORA-53810: error logging conformance validation messages
-
Cause: An error occurred while trying to log conformance validation messages.
- ORA-53820: Invalid locator path string
-
Cause: A locator path for an attribute was invalid.
- ORA-53900: I/O failure string.
-
Cause: A device I/O failure occurred when attempting to read from and write to a DICOM object.
- ORA-53910: SQL error string.
-
Cause: An error occurred when attempting to run a SQL command.
- ORA-53920: XML error string.
-
Cause: An error occurred when attempting to read from and write to XML metadata.
- ORA-53930: XSLT error string.
-
Cause: An error occurred while attempting to process XML metadata.
- ORA-53940: make anonymous error string.
-
Cause: An error occurred while attempting to make DICOM object anonymous.
- ORA-53980: unimplemented feature: string
-
Cause: The specified feature is not implemented.
- ORA-53990: internal error string.
-
Cause: An internal error occurred while attempting to process a DICOM object.
- ORA-53991: cannot move tablespace because tables are being used
-
Cause: The operation failed because Oracle Multimedia tables were being used.
- ORA-54000: Virtual column feature not yet implemented
-
Cause: Feature has not been implemented.
- ORA-54001: string: invalid identifier specified for virtual column expression
-
Cause: Column expression referenced a column that does not exist 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.
- 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.
- 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.
- ORA-54005: keyword VIRTUAL cannot be specified here
-
Cause: The keyword VIRTUAL was either repeated or incorrectly specified.
- ORA-54006: keyword VISIBLE cannot be specified here
-
Cause: The keyword VISIBLE was either repeated or incorrectly specified.
- ORA-54007: keyword HIDDEN cannot be specified here
-
Cause: The keyword HIDDEN was either repeated or incorrectly specified.
- 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
- ORA-54009: expression column is not supported for an external table
-
Cause: Attempt to create/alter an external table with an expression column
- ORA-54010: expression column is not supported for a temporary table
-
Cause: Attempt to create/alter a temporary table with an expression column
- ORA-54011: expression column is not supported for a clustered table
-
Cause: Attempt to create/alter a clustered table with an expression column
- ORA-54012: virtual column is referenced in a column expression
-
Cause: This virtual column was referenced in an expression of another virtual column
- ORA-54013: INSERT operation disallowed on virtual columns
-
Cause: Attempted to insert values into 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
- 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
- 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
- ORA-54017: UPDATE operation disallowed on virtual columns
-
Cause: Attempted to update values of a virtual column
- ORA-54018: A virtual column exists for this expression
-
Cause: Specified index expression matches an existing 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.
- 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.
- 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.
- 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.
- 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.
- 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
- ORA-54025: Virtual column cannot have a default value
-
Cause: Attempted to alter a virtual column to have a default value.
- ORA-54026: Real column cannot have an expression
-
Cause: Attempted to alter a real column to have an expression.
- ORA-54027: cannot modify data-type of virtual column
-
Cause: Attempted to change the data-type of virtual column without modifying the underlying expression
- ORA-54028: cannot change the HIDDEN/VISIBLE property of a virtual column
-
Cause: Attempted to change the HIDDEN/VIRTUAL property of a virtual column
- ORA-54029: Virtual column cannot be updated in trigger body
-
Cause: Attempted to change the value of virtual column in a trigger body"
- ORA-54030: datatype mismatch between virtual column and expression
-
Cause: virtual column expression was changed after column was created"
- 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.
- 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.
- 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.
- 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.
- ORA-54035: keyword HIDDEN cannot be specified here
-
Cause: Attempted to specify HIDDEN key word for a virtual column
- 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.
- 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.
- ORA-54038: Virtual column cannot be encrypted
-
Cause: An attempt was made to create or alter a virtual column to have encryption.
- 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.
- 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.
- 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.
- 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).
- 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).
- 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.
- 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.
- 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.
- 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.
- ORA-54048: Column expression modifications cannot be combined with any other column DDL operation.
-
Cause: An attempt was made to combine the modification of the expression of a column with other column operations.
- ORA-54049: expression edition column is not supported for an external table
-
Cause: An attempt was made to create or alter an external table with an edition expression column.
- ORA-54050: Unsupported type or attribute on redacted column.
-
Cause: An attempt was made to alter a column with a redaction policy, so as to give that column an unsupported type or attribute. Virtual columns are not supported by data redaction. Columns with the INVISIBLE attribute are not supported by data redaction (this applies to both user-specified hidden columns and system-generated hidden columns). Vector encoded columns are not supported by data redaction.
- ORA-54051: System-generated virtual column cannot be a primary key.
-
Cause: An attempt was made to specify a system-generated virtual column * as a primary key.
- ORA-54052: System-generated functional index virtual column cannot be renamed.
-
Cause: An attempt was made to rename a system-generated functional index virtual column.
- ORA-54053: The visibility of a column from a table owned by a SYS user cannot be changed.
-
Cause: An attempt was made to alter the visibility of a column from a table owned by SYS user.
- ORA-54054: System-generated virtual column or guard column cannot be in a constraint.
-
Cause: An attempt was made to add a constraint containing the system generated virtual column or guard column.
- ORA-54055: In-Memory virtual column expression cannot refer to a system-generated or hidden column.
-
Cause: An attempt was made to create a virtual column expression on a system-generated or hidden column.
- ORA-54056: unsupported operation on sensitive column
-
Cause: An attempt was made to either alter the visibility of a sensitive column or change the sensitive column to vector encode.