Cause: The input value was not a valid option to apply XS Data Security.

Cause: An illegal argument value was used with DBMS_RLS to apply XS Data Security.

Cause: An invalid column was specified in the data security policy.

Cause: A table without an XS Data Security policy applied was specified.

Cause: A table with more than one XS Data Security policy applied was specified.

Cause: The object was protected by both VPD (Virtual Private Database) column security and XS column constraint policies.

Cause: A table not associated with an XS Data Security policy was specified.

Cause: A table associated with more than one XS Data Security policy was specified.

Cause: A non-existing user-built Static ACL Materialized View was specified

Cause: A user-built Static ACL Materialized View was specified but with an incorrect schema

Cause: The refresh mode specified for the Materialized View supporting static ACLs is invalid.

Cause: The name specified for the Static ACL Materialized View (ACLMV) is reserved for system-built ACLMVs.

Cause: The security context was changed and was different from the time the cursor was parsed.

Cause: The specified object schema was different from the policy schema.

Cause: The policy applied on the table did not contain any static rules.

Cause: Creation of the static access control list (ACL) materialized view (MV) failed.

Cause: There was an Oracle Database Real Application Security internal error.

Cause: An invalid application user was specified.

Cause: An invalid XS Security session ID was specified.

Cause: An invalid XS Security session cookie was specified.

Cause: An invalid XS session application namespace or system-defined namespace was specified. Certain operations are not allowed on the system-defined namespace.

Cause: An invalid application role was specified.

Cause: An invalid XS Security application namespace or attribute was specified.

Cause: The specified XS Security application namespace was already in existence.

Cause: An invalid XS Security application namespace attribute was specified.

Cause: The specified ACL identifier is invalid.

Cause: An application user was not specified.

Cause: XS Security session ID was not specified.

Cause: XS Security application namespace was not specified.

Cause: There was no attachment to an XS Security session.

Cause: XS Security application namespace attribute name was not specified.

Cause: XS Security application namespace attribute value was not specified.

Cause: XS Security session inactivity timeout was not specified.

Cause: XS Security session cookie was not specified.

Cause: XS Security role was not specified.

Cause: Operations were blocked when an application session was attached.

Cause: An attempt was made to execute an XS Security session function or procedure without the appropriate privilege.

Cause: An error or exception was returned by the error handling function invoked as part of the current operation.

Cause: The size of the column or variable used to store the output of this function or procedure is too small.

Cause: The specified XS Security session cookie was used by another XS Security session.

Cause: The specified session ID does not match the attached session ID.

Cause: The current database session is already attached to an application user session.

Cause: The length of the name was shorter or longer than allowed limits.

Cause: The specified attribute value is too large.

Cause: The event type specified is invalid.

Cause: An XS Security principal already existed with same name.

Cause: User was marked inactive.

Cause: User password was expired.

Cause: The user's account is locked.

Cause: The GUID of the principal existed or the external source was not set.

Cause: An attempt was made to update or delete system-seeded XS objects.

Cause: An attempt was made to add a proxy user to a target user when proxy roles did not exist.

Cause: An attempt was made to detach from an XS session created by a direct password login.

Cause: An attempt was made to switch users within a proxy session.

Cause: The specified operation was not allowed in an application session.

Cause: This verifier was not currently supported.

Cause: An attempt was made to update or delete nonregistered event handler.

Cause: An attempt was made to re-register an event handler.

Cause: An attempt was made to register a nonexistent event handler.

Cause: An attempt was made to destroy an XS session created by a direct password login.

Cause: An attempt was made to create an XS session by a user that is not effective.

Cause: An error code with an illegal value was supplied.

Cause: Both default value and first read were specfied in namespace template.

Cause: An attempt was made to delete an XS artifact which was not in existence within the scope.

Cause: An attempt was made to create or refer to an XS artifact which was already in existence within the scope.

Cause: This feature was not supported or implemented.

Cause: An attempt was made to do an XS session operation that could modify the current security context inside a definer's rights program unit.

Cause: Definition of an aggregate privilege contained itself.

Cause: Definition of an aggregate privilege contained a privilege that is not defined in this or parent security classes.

Cause: Security class definition inherited from itself through circular definition.

Cause: Definition of a security class specified an internal base security class as a parent security class.

Cause: The specified security class did not exist.

Cause: The specified security class did not have any parent security class.

Cause: The specified privilege did not exist in the security classes that were associated with the ACLs.

Cause: The security class targetNamespace attribute was either null or was longer than 4000 characters. Or, the security class name attribute was either null or was longer than 1024 characters.

Cause: The privilege name in the security class was previously defined in another security class.

Cause: An invalid security class was specified in the ACL.

Cause: The security class name under the targetnamespce was also used for another security class.

Cause: An invalid ACL name was used as one of the operator parameters.

Cause: During SQL execution, evaluation of a data realm failed with an error.

Cause: An attempt was made to delete an access control list (ACL) which was referenced by a namespace template.

Cause: An attempt was made to delete an access control list (ACL) that was set on a user or dynamic role.

Cause: An attempt was made to use an access control list (ACL) whose schema was not SYS.

Cause: An attempt was made to specify a NULL value for an access control list (ACL).

Cause: An attempt was made to delete an attribute that was seeded from the template from which this namespace was created.

Cause: An attempt was made to create an attribute that already exists within the given namespace.

Cause: An attempt was made to create a namespace template with an invalid handler function.

Cause: An attempt was made to create a template or a custom attribute with events specified. However, a handler function was not specified in the template.

Cause: An attempt was made to create a resource with multiple UIDs or GUIDs specified in the document.

Cause: An attempt was made by an user with an empty GUID to create a session.

Cause: An attempt was made to set the inactivity timeout time to a negative value.

Cause: An attempt was made to execute a disallowed session operation during global callback execution.

Cause: Circular callback call caused an infinite chain of callback function executions.

Cause: An attempt was made to switch user with administrative operation.

Cause: An attempt was made to assign user to a named user.

Cause: An attempt was made to create an XS entity with a name length less than the minimum or more than the maximum allowed.

Cause: An attempt was made to create an XS entity with a name that already belongs to another entity.

Cause: An attempt was made to create an XS entity resulting in an unexpected constraint violation.

Cause: An attempt was made to delete an XS entity with dependent entities in the system.

Cause: A reference was made to an XS entity that did not exist.

Cause: An attempt was made to remove a relation that did not exist.

Cause: An unexpected operation was performed.

Cause: The current user was not an authorized proxy user of the client user during a switching user operation.

Cause: There was another mid-tier attached to the server session with a different set of roles.

Cause: An attempt was made to change an application session in readable standby mode.

Cause: An attempt was made to modify an application user that is currently logged on.

Cause: There was already a user or role with that name.

Cause: An unexpected error occurred during the requested XS administrative operation.

Cause: A nonregular role was granted to a principal.

Cause: The role was granted from itself through circular operation.

Cause: The ACL was inherited from itself through circular definition.

Cause: The policy parameter did not exist.

Cause: Invalid parameter type was specified.

Cause: An unexpected error occurred during mid-tier cache synchronization.

Cause: An invalid database user or role was specified as the principal name.

Cause: A request to sign the message could not be processed because the key manager was not initialized.

Cause: An attempt was made to add a schema to an application proxy user that already was configured with a schema.

Cause: An attempt was made to remove a schema from an application proxy user that was not configured.

Cause: An attempt was made to grant a role to the XSGUEST seeded user.

Cause: The dispatcher's session timed out due to inactivity.

Cause: A request was made without the dispatcher's signature. The server is configured to accept requests signed by the dispatcher only.

Cause: The request message was corrupt.

Cause: An attempt was made to either update an XS Data Security session which did not exist, or to create an XS Data Security session which already existed, or to attach a direct-login XS Data Security session.

Cause: The XS Data Security session is detached successfully, but session changes are not saved due to updating an XS Data Security session which did not exist.

Cause: An attempt was made to use an unsupported database link type in an XS Data Security session.

Cause: Input value was not valid for the procedure.

Cause: Input value was out of range.

Cause: Cleanup job already existed which spanned the given audit trail type.

Cause: The property already exists which spans the given audit trail type.

Cause: The value being set already existed.

Cause: The job did not exist or was not created by DBMS_AUDIT_MGMT package.

Cause: Invalid operation on a non partitioned table.

Cause: The property could not be cleared.

Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP was not called for the erroring audit trail.

Cause: The audit trail cleanup operation could not be completed.

Cause: The audit trail cleanup could not be completed because of an internal error.

Cause: The tablespace was either unavailable or did not have enough space to accomodate the audit table being moved.

Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP was already invoked for the audit trail type.

Cause: Could not complete the DBMS_AUDIT_MGMT operation.

Cause: Audit Trail was initialized which spans the given audit trail type.

Cause: The DBMS_AUDIT_MGMT API was executed in an Oracle RAC enabled database and AUDIT_TRAIL_TYPE was one of AUDIT_TRAIL_OS or AUDIT_TRAIL_XML. But, Oracle RAC instance number for which DBMS_AUDIT_MGMT API was run, was not supplied.

Cause: Could not complete the operation because the DBMS_AUDIT_MGMT API involved movement of one or more audit tables and there was not enough space in the destination tablespace.

Cause: Audit tables were being operated by more than one DBMS_AUDIT_MGMT API from different sessions. The simultaneous execution of the following API with one another and with itself can cause the conflict: INIT_CLEANUP, DEINIT_CLEANUP, SET_AUDIT_TRAIL_LOCATION and MOVE_DBAUDIT_TABLES.

Cause: Audit files were being operated by more than one DBMS_AUDIT_MGMT API from different sessions. The simultaneous execution of the CLEAN_AUDIT_TRAIL API with itself can cause the conflict.

Cause: An I/O attempt occurred during DBMS_AUDIT_MGMT operation and the database I/O was suspended.

Cause: Audit trail was deinitialized which spans the given audit trail type.

Cause: The executed DBMS_AUDIT_MGMT operation failed in one of the PDB.

Cause: The tablespace associated with Unified Audit Trail is either invalid or is offline.

Cause: Audit trail table was being operated by more than one API from different sessions. The simultaneous execution of DBMS_AUDIT_MGMT.INIT_CLEANUP or DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION with SA_SYSDBA.CREATE_POLICY or SA_SYSDBA.DROP_POLICY can cause the conflict.

Cause: Audit records were not generated in the unified audit trail.

Cause: Unified audit trail is being operated by more than one DBMS_AUDIT_MGMT API from different sessions. The simultaneous execution of the following API with one another and with itself can cause the conflict: FLUSH_UNIFIED_AUDIT_TRAIL, LOAD_UNIFIED_AUDIT_FILES, CLEAN_AUDIT_TRAIL, and SET_AUDIT_TRAIL_LOCATION.

Cause: One of the following API's was concurrently executed with itself or with another API in separate sessions causing a conflict: - SET_LAST_ARCHIVE_TIMESTAMP - CLEAR_LAST_ARCHIVE_TIMESTAMP - CLEAN_AUDIT_TRAIL - SET_AUDIT_TRAIL_PROPERTY - CLEAR_AUDIT_TRAIL_PROPERTY.

Cause: The identifier name generated after concatenating with 'AMGT$DP$' exceeded 30 or 128 bytes.

Cause: BY user-list clause was supplied with IN SESSION session-information clause in the command.

Cause: An attempt was made to use ALL STATEMENTS audit option with BY SESSION clause. ALL STATEMENTS audit option can be configured with BY ACCESS only.

Cause: An attempt was made to use IN SESSION session-information clause in NOAUDIT command.

Cause: An attempt was made to drop the AUDSYS user that hosts the audit trail.

Cause: An attempt was made to apply audit policy with the EXCEPT clause which was already applied with the BY clause.

Cause: An attempt was made to apply audit policy with the BY clause which was already applied with the EXCEPT clause.

Cause: An attempt was made to remove audit policy using NOAUDIT command with the EXCEPT clause.

Cause: A valid audit policy name was expected.

Cause: A valid context or attribute name was expected.

Cause: Creating or altering the audit policy was attempted with an invalid system privilege audit option.

Cause: Creating or altering the audit policy was attempted with an invalid action audit option.

Cause: The specified audit policy object did not exist in the database.

Cause: The specified audit policy object already existed in the database.

Cause: Creating or altering the audit policy was attempted with an invalid audit option for the object.

Cause: Altering the audit policy was attempted for adding and dropping the same auditing option in the audit policy.

Cause: An attempt was made to drop the audit policy which is currently enabled.

Cause: An attempt to obtain the value for ORACLE_BASE failed.

Cause: Could not find the specified audit directory.

Cause: Could not create the specified audit directory.

Cause: Could not create the specified audit file.

Cause: The file found in Oracle audit directory was not a valid Oracle audit file.

Cause: An operation requiring the database to be open in read/write mode was attempted.

Cause: Creating or altering the audit policy was attempted with a complex audit condition.

Cause: Check the error stack for detailed error information.

Cause: An attempt was made to connect to the database as AUDSYS user.

Cause: An operation was attempted on the audit file which was not available in the audit directory.

Cause: An attempt was made to create, alter or enable the empty audit policy.

Cause: The operation could not be completed on one or more Oracle RAC instances.

Cause: An attempt to import Fine-Grained Audit (FGA) policy failed because the specified FGA policy owner has not been imported.

Cause: An attempt was made to configure auditing on the system privilege which is not supported by the audit facility.

Cause: The object being accessed had a fine-grained audit (FGA) policy defined on it and the VERSIONS clause contained a bind variable.

Cause: An error was encountered while generating the audit session ID.

Cause: Use of the EXCEPT clause and the USERS WITH GRANTED ROLES clause in the same AUDIT and NOAUDIT statements was not a valid combination

Cause: A global role was found in the enablement list.

Cause: The role being altered to IDENTIFIED GLOBALLY has unified audit policy enabled on users to whom it is directly granted. Audit configuration using global role is not supported.

Cause: The order in which audit options were mentioned was incorrect.

Cause: The order in which ADD, DROP or CONDITION clauses were mentioned was incorrect.

Cause: A DML or DDL operation was attempted on a unified auditing internal table.

Cause: Either the database was not open in the read/write mode, or the transfer of the unified audit records was already in progress.

Cause: An attempt was made to perform an operation that is not allowed on a non-partitioned unified audit internal table.

Cause: Space usage by unified audit files in the current container has exceeded the value of MAX_AUDIT_STORAGE for the container.

Cause: An attempt was made to alter or drop an Oracle predefined policy.

Cause: An attempt was made to use a tablespace which is of type TEMPORARY, UNDO or LOST WRITE PROTECTION.

Cause: An attempt was made to move the audit files to a disk group without configuring one for auditing.

Cause: An attempt was made to apply the common audit configuration to a local user. Common audit configuration can be applied only to common users.

Cause: Object audit option for the common audit policy was specified on a local object. A common audit policy can have object audit options on common objects only.

Cause: An attempt was made to create a local audit policy or configuration while not connected to a pluggable database. Local audit policy or configuration can be created only when connected to a pluggable database.

Cause: An attempt was made to specify the CONTAINER clause with the AUDIT command while configuring object auditing. The CONTAINER clause is not supported for object auditing using the SQL AUDIT command.

Cause: An attempt was made to apply the common audit configuration to a local role. Common audit configuration can be applied to common roles only.

Cause: An attempt was made to create fine-grained Audit (FGA) policy on common object and associated handler schema is not common user.

Cause: An attempt was made to create common fine-grained Audit (FGA) policy on a local object. A common FGA policy can only be configured on common object.

Cause: An attempt was made to create a Fine-Grained Auditing (FGA) policy on an object-linked common object from within a pluggable database (PDB).

Cause: The required keystore file name was invalid or missing.

Cause: Either the specified backup location was not an ASM path name when the configured keystore location was an ASM path or the specified backup location was an ASM path name when the configured keystore location was not an ASM path.

Cause: Backup identifier was not specified.

Cause: Keystore location where the backup was to be created was incorrect.

Cause: Keystore name could not be formed possibly due to the incorrectly specified keystore location.

Cause: The source keystore for which the backup was requested was not found.

Cause: A backup of the keystore of the same name already existed in the given location.

Cause: The backup of the keystore could not be created.

Cause: The keystore password specified did not match that of the keystore that was open.

Cause: An attempt was made to alter the software keystore password.

Cause: The keystore password was changed. However, the keystore was closed during this operation.

Cause: The keystore could not be created at the specified location because a keystore of the same type already existed.

Cause: The keystore was not backed up. For this operation to proceed, the keystore must be backed up.

Cause: Password-based keystore was missing for this operation. Auto login keystore can be created from a password-based keystore only.

Cause: Password-based keystore could not be created at the specified location due to either incorrect file permissions for Oracle on the specified location or due to the nonexistence of the specified location.

Cause: The local auto login keystore could not be created at the specified location due to the incorrect password specified for the password-based keystore or due to incorrect file permissions for Oracle on the specified location or due to the nonexistence of the specified location.

Cause: The auto login keystore could not be created at the specified location due to the incorrect password specified for the password-based keystore or due to incorrect file permissions for Oracle on the specified location or due to the nonexistence of the specified location.

Cause: The second keystore could not be added to the target keystore.

Cause: The first keystore could not be added to the target keystore.

Cause: The two keystores could not be merged.

Cause: Keystore location was not configured correctly in the sqlnet.ora file.

Cause: The file name of the file to which keys from the keystore will be written was incorrect or invalid.

Cause: The file name of the file from which the keys will be read and saved in the keystore was incorrect or invalid.

Cause: The file name specified as the export destination for keys exported from the keystore was already in existence.

Cause: The specified file from which the keys are to be imported into the keystore did not exist.

Cause: Creation or opening of the file specified as the key export destination, where the keys exported from the keystore were to be written, failed.

Cause: The file specified as the key import source, from which the keys were to be imported into the keystore, could not be opened.

Cause: The file specified as the key import source, from which the keys were to be imported, was not a valid file or does not have the needed file access permission.

Cause: The file specified as the key import source, from which the keys are to be imported, had different protection from what was specified in the SQL command.

Cause: The operation of writing the keys to the keystore failed.

Cause: Master key with the specified identifier does not exist in the keystore.

Cause: The master key or the master key information associated with a specified master key identifier did not exist.

Cause: Master key creation failed.

Cause: Creation of the tag for the specified master key failed.

Cause: Retrieval of the master key information for the specified master key identifier failed.

Cause: The operation of writing the imported keys to the keystore failed.

Cause: The specified keystore, from which keys are to be imported, did not contain any valid keys.

Cause: The specified operation was not supported for the container database.

Cause: The specified source keystores to be merged were the same. There is no need to merge these keystores.

Cause: The keystore was not open in the container.

Cause: The master keys for the specified pluggable database (PDB) could not be retrieved.

Cause: The specified source and target keystores to be merged were the same. There is no need to merge these keystores.

Cause: The root container keystore was not open.

Cause: Creation of the master key failed for one or more pluggable databases (PDBs).

Cause: Creation of the master key failed for one or more pluggable databases (PDBs) and as such REKEY failed for these PDBs.

Cause: Creation of the master key failed for all pluggable databases (PDBs).

Cause: Activation of the master key failed for one or more pluggable databases (PDBs) and as such REKEY failed for these PDBs.

Cause: Creation of the master key failed for one or more pluggable databases (PDBs). Further, activation of one or more created master keys also failed for some PDBs and as such REKEY failed on these PDBs.

Cause: An entry with the given client name was not found in the keystore.

Cause: An entry with the given client name was already in existence in the keystore.

Cause: The location specified for the target keystore did not contain a valid keystore, or target keystore did not have valid file permissions.

Cause: The client secret keystore add, update or delete operation failed.

Cause: Master key was not set in the root container.

Cause: The file name of the keystore backup could not be recorded in props$.

Cause: Oracle was unable to write an entry to the export file.

Cause: Oracle was unable to read an entry from the export file.

Cause: Oracle was unable to write an entry for export.

Cause: Oracle was unable to read an entry for import.

Cause: The backup identifier within the ASM file name of the keystore exceeded the maximum length of 12 characters.

Cause: An attempt was made to encrypt an identity column created with GENERATED BY DEFAULT or GENERATED ALWAYS keywords.

Cause: An encryption algorithm for the master key was missing or invalid in the user command.

Cause: The master keys of the container database were not exported.

Cause: Reverse migration failed for one or more pluggable databases (PDB).

Cause: An attempt was made to add a master key with the same master key identifier to more than one container database. A user specified master key string with a master key identifier can be added to a single container only.

Cause: An attempt was made to add a master key with a master key identifier that was already present in the keystore.

Cause: The master key identifier or master key value was invalid. To be valid, the values supplied for both the master key identifier and the master key value must be hex-encoded and must have the following properties: - For a master key value to be valid, its length must be a valid key length for the specified encryption algorithm. - For a master key identifier to be valid, it must have a length of 16 bytes. - For a master key identifier to be valid, it must have a non-zero value.

Cause: The master key string was missing or invalid.

Cause: The specified operation is not supported with Hardware Security Module (HSM).

Cause: The master key could not be moved out of the keystore.

Cause: An attempt was made to move a master key that did not exist in the keystore.

Cause: The new wallet used to store the keys to be moved could not be created. The cause could be the lack of permission to write to the directory for the Oracle user or the directory did not exist.

Cause: An attempt was made to set or use an invalid value for the KEYSTORE_CONFIGURATION attribute of the TDE_CONFIGURATION instance initialization parameter.

Cause: An attempt was made to close the wallet when it was in use.

Cause: An attempt was made to perform a keystore operation when the instance initialization parameter WALLET_ROOT was missing or invalid.

Cause: An attempt was made to unite an isolated keystore with the root keystore, but the keys of the isolated keystore were already present in the root keystore.

Cause: An attempt was made to set or use an invalid value for the TDE_CONFIGURATION instance initialization parameter.

Cause: An attempt was made to isolate a master key when it was still required by another pluggable database. Another pluggable database might still require the master key if the pluggable databases were clones of each other.

Cause: The keystore password clause was not provided for this SQL command.

Cause: CDB$ROOT was not open.

Cause: A keystore could not be created. A combination of the following conditions prevented the operation: 1. The pluggable database was not open in read/write mode. Note that the pluggable database needs to be open in read/write mode for the KEYSTORE_MODE configuration of the pluggable database to be automatically changed to ISOLATED during the ADMINISTER KEY MANAGEMENT CREATE KEYSTORE command. 2. The KEYSTORE_MODE configuration of the pluggable database was UNITED (rather than ISOLATED).

Cause: An attempt was made to either copy or move the isolated wallet of the pluggable database (PDB) that was plugged.

Cause: An attempt was made to delete the source wallet file during the pluggable database (PDB) plug with MOVE clause.

Cause: An attempt was made to switch over the PKCS#11 library and there was trouble finding or loading the new library.

Cause: The switch over command was executed on a system with an unsupported configuration of the Oracle Advanced Security Transparent Data Encryption (TDE) keystore.

Cause: A proxy authentication was attempted using an administrative privilege.

Cause: An attempt was made to use the Oracle password file which is not in legacy or in release 12.1 or higher format. The password file is either not present or may have become corrupt.

Cause: An attempt was made to apply password file changes made on the primary database to the password file of the standby database, but there was a password file format mismatch which prevented the operation.

Cause: An attempt was made to perform one of the following operations, but none of these operations are allowed while the password file is in LEGACY or in release 12.1 format. - Attempting to grant an administrative privilege to an external user (a user created as IDENTIFIED EXTERNALLY). - Attempting to change the authentication type of an administrative-privileged user from PASSWORD to EXTERNAL. - When a common user has an administrative privilege granted in a pluggable database (PDB) but no longer exists in the CDB$ROOT container, attempting to create this common user again in the root as IDENTIFIED EXTERNALLY.

Cause: Access to this service from this location was not allowed.

Cause: The executed DBMS_SFW_ACL_ADMIN operation failed.

Cause: The executed DBMS_SFW_ACL_ADMIN operation timed out.