ORA-46000 to ORA-46988

89 ORA-46000 to ORA-46988

ORA-46000: invalid option to apply XS Data Security: Cause: The input value was not a valid option to apply XS Data Security.; Action: Use a valid option to apply XS Data Security.
ORA-46001: argument string is not valid for XS Data Security policies: Cause: An illegal argument value was used with DBMS_RLS to apply XS Data Security.; Action: Use the XS_DATA_SECURITY API to apply XS Data Security.
ORA-46003: Column "string" is not valid in data security policy for "string": Cause: An invalid column was specified in the data security policy.; Action: Correct the column name in the policy.
ORA-46004: XS Data Security policy is not applied on string.string: Cause: A table without an XS Data Security policy applied was specified.; Action: Specify a table with one XS Data Security policy applied.
ORA-46005: multiple XS Data Security policies applied on string.string: Cause: A table with more than one XS Data Security policy applied was specified.; Action: Specify a table with one XS Data Security policy applied.
ORA-46006: cannot mix VPD column and XS column constraint policies: Cause: The object was protected by both VPD (Virtual Private Database) column security and XS column constraint policies.; Action: Disable or drop either the VPD or XS column policies.
ORA-46007: no XS Data Security policy associated with string.string: Cause: A table not associated with an XS Data Security policy was specified.; Action: Specify a table associated with an XS Data Security policy.
ORA-46008: multiple XS Data Security policies associated with string.string: Cause: A table associated with more than one XS Data Security policy was specified.; Action: Specify a table associated with one XS Data Security policy.
ORA-46019: User-built Static ACL Materialized View does not exist: Cause: A non-existing user-built Static ACL Materialized View was specified; Action: Create a user-built Static ACL Materialized View with the specified name or use system-built Static ACL views
ORA-46020: User-built Static ACL Materialized View has invalid schema: Cause: A user-built Static ACL Materialized View was specified but with an incorrect schema; Action: Create a user-built Static ACL Materialized View with at least the required columns with correct names and types
ORA-46021: Invalid refresh mode specified for Static ACL Materialized View: Cause: The refresh mode specified for the Materialized View supporting static ACLs is invalid.; Action: Specify either "ON DEMAND" or "ON COMMIT" for parameter refresh_mode
ORA-46022: Invalid name specified for user-built Static ACL Materialized View: Cause: The name specified for the Static ACL Materialized View (ACLMV) is reserved for system-built ACLMVs.; Action: Rename the user-built Static ACL Materialized View
ORA-46023: Application Session affinity is not the same as when the cursor was parsed.: Cause: The security context was changed and was different from the time the cursor was parsed.; Action: Make sure the security context is the same as when the cursor was parsed.
ORA-46024: The policy schema differs from the object schema for Static ACL Materialized View based XDS policy.: Cause: The specified object schema was different from the policy schema.; Action: Make sure the object and the policy have the same schema.
ORA-46025: no static rule specified in applied policy: Cause: The policy applied on the table did not contain any static rules.; Action: Ensure the applied policy has at least one static rule.
ORA-46026: creation of static ACL materialized view (MV) failed: Cause: Creation of the static access control list (ACL) materialized view (MV) failed.; Action: Check the trace file for detailed error information.
ORA-46050: Oracle Real Application Security internal error.: Cause: There was an Oracle Database Real Application Security internal error.; Action: None
ORA-46051: invalid application user specified: Cause: An invalid application user was specified.; Action: Check the user name and execute the function or procedure again.
ORA-46052: invalid session ID specified: Cause: An invalid XS Security session ID was specified.; Action: Check the session ID and execute the function or procedure again.
ORA-46053: invalid cookie specified: Cause: An invalid XS Security session cookie was specified.; Action: Check the session cookie and execute the function or procedure again.
ORA-46054: invalid namespace specified: Cause: An invalid XS session application namespace or system-defined namespace was specified. Certain operations are not allowed on the system-defined namespace.; Action: Check the namespace and execute the function or procedure again.
ORA-46055: invalid role specified: Cause: An invalid application role was specified.; Action: Check the role and execute the function or procedure again.
ORA-46056: invalid namespace or attribute specified: Cause: An invalid XS Security application namespace or attribute was specified.; Action: Check the namespace and attribute, and execute the function or procedure again.
ORA-46057: namespace already exists: Cause: The specified XS Security application namespace was already in existence.; Action: Execute the function or procedure with a different namespace.
ORA-46058: attribute string is invalid: Cause: An invalid XS Security application namespace attribute was specified.; Action: Check the attribute and execute the function or procedure.
ORA-46059: Invalid ACL identifier specified: Cause: The specified ACL identifier is invalid.; Action: Check the ACL identifier, and execute the function or procedure again with a valid ACL ID.
ORA-46060: user name not specified: Cause: An application user was not specified.; Action: Execute the function or procedure with a user name.
ORA-46061: session ID not specified: Cause: XS Security session ID was not specified.; Action: Execute the function or procedure with a session ID.
ORA-46062: Namespace not specified: Cause: XS Security application namespace was not specified.; Action: Execute the function or procedure with a namespace.
ORA-46063: not attached to XS Security session: Cause: There was no attachment to an XS Security session.; Action: Attach to an XS Security session and execute the function or procedure.
ORA-46064: attribute name not specified: Cause: XS Security application namespace attribute name was not specified.; Action: Execute the function or procedure with an attribute name.
ORA-46065: attribute value not specified: Cause: XS Security application namespace attribute value was not specified.; Action: Execute the function or procedure with an attribute value.
ORA-46066: inactivity timeout not specified: Cause: XS Security session inactivity timeout was not specified.; Action: Execute the function or procedure with an inactivity timeout value.
ORA-46067: cookie not specified: Cause: XS Security session cookie was not specified.; Action: Execute the function or procedure with a cookie value.
ORA-46068: role not specified: Cause: XS Security role was not specified.; Action: Execute the function or procedure with a Role value.
ORA-46069: operation disallowed in an application session: Cause: Operations were blocked when an application session was attached.; Action: Try the operation later after the application session is detached.
ORA-46070: insufficient privileges: Cause: An attempt was made to execute an XS Security session function or procedure without the appropriate privilege.; Action: Ask the administrator to perform the operation or to grant the appropriate privilege.
ORA-46071: Error occured in event handler string: Cause: An error or exception was returned by the error handling function invoked as part of the current operation.; Action: Check the trace files to identify the source of the error in the event handling function. Attempt the operation again after the error has been resolved. Also, abort attach session since the changes made to the session by the event handler might not have been recorded because of the error.
ORA-46072: Column width too small: Cause: The size of the column or variable used to store the output of this function or procedure is too small.; Action: Increase the size of the column or variable and try again.
ORA-46073: cookie already in use by another session: Cause: The specified XS Security session cookie was used by another XS Security session.; Action: Execute the function or procedure with a different cookie.
ORA-46074: session ID mismatch: Cause: The specified session ID does not match the attached session ID.; Action: Execute the function or procedure without a session ID or with a matching attached session.
ORA-46075: already attached to an application user session: Cause: The current database session is already attached to an application user session.; Action: Detach from the current application user session before attaching to the new application user session.
ORA-46076: The specified name length not within valid range.: Cause: The length of the name was shorter or longer than allowed limits.; Action: Try again with a new name with a length less than the maximum or or more than the minimum allowed.
ORA-46077: Length of value too large: Cause: The specified attribute value is too large.; Action: Execute the function or procedure again with a smaller attribute value.
ORA-46078: Invalid event type specified: Cause: The event type specified is invalid.; Action: Reattempt the operation with an invalid event type.
ORA-46079: invalid external principal specified: Cause: An XS Security principal already existed with same name.; Action: Specify another external principal and try again.
ORA-46080: User status is currently inactive: Cause: User was marked inactive.; Action: Change status in enterprise directory to active and try again.
ORA-46081: User's password has expired: Cause: User password was expired.; Action: Change the user's password and update status to active.
ORA-46082: User's account was locked: Cause: The user's account is locked.; Action: Update user's status to Active in Enterprise Directory and try again.
ORA-46083: Cannot update the GUID of the principal: Cause: The GUID of the principal existed or the external source was not set.; Action: None
ORA-46084: cannot update or delete system-seeded XS objects.: Cause: An attempt was made to update or delete system-seeded XS objects.; Action: Do not attempt to update or delete system-seeded XS objects.
ORA-46085: Cannot add a proxy user when there was no proxy roles.: Cause: An attempt was made to add a proxy user to a target user when proxy roles did not exist.; Action: Verify the proxy roles and try again.
ORA-46086: Cannot detach from a direct-login XS session: Cause: An attempt was made to detach from an XS session created by a direct password login.; Action: To detach and destroy the XS session, logout of the DB session.
ORA-46087: Switching users not allowed for a proxy session: Cause: An attempt was made to switch users within a proxy session.; Action: Switch back to original user and try again.
ORA-46088: operation disallowed in application session: Cause: The specified operation was not allowed in an application session.; Action: None
ORA-46089: Unsupported verifier type: Cause: This verifier was not currently supported.; Action: Execute again with a different verifier type.
ORA-46090: Requested event handler not registered for the event: Cause: An attempt was made to update or delete nonregistered event handler.; Action: Please verify event handler name.
ORA-46091: Requested event handler already registered for the event: Cause: An attempt was made to re-register an event handler.; Action: Please verify event handler name.
ORA-46092: Requested event handler does not exist: Cause: An attempt was made to register a nonexistent event handler.; Action: Please verify event handler name or create the event handler.
ORA-46093: Cannot destroy a direct-login XS session: Cause: An attempt was made to destroy an XS session created by a direct password login.; Action: To destroy the XS session, logout of the DB session.
ORA-46094: XS user not effective: Cause: An attempt was made to create an XS session by a user that is not effective.; Action: To create the XS session, contact the administrator to check the effective dates on the user.
ORA-46095: Invalid error code supplied: Cause: An error code with an illegal value was supplied.; Action: Use an error code from the range of valid values.
ORA-46096: An attribute in a namespace cannot have both default value and first read event set.: Cause: Both default value and first read were specfied in namespace template.; Action: Specify either default value or first read for the attribute in the namespace, but not both.
ORA-46097: The string did not exist in the string.: Cause: An attempt was made to delete an XS artifact which was not in existence within the scope.; Action: Check if the XS artifact was created or referenced within the scope.
ORA-46098: The string already exists in the string.: Cause: An attempt was made to create or refer to an XS artifact which was already in existence within the scope.; Action: Check if the XS artifact name is unique within the scope.
ORA-46099: Feature unsupported or not implemented: Cause: This feature was not supported or implemented.; Action: None
ORA-46100: XS session operations are disallowed during the execution of a definer's rights program unit.: 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.; Action: Change the program unit to invoker's rights.
ORA-46101: Circular definition for aggregate privilege string in security class string: Cause: Definition of an aggregate privilege contained itself.; Action: Fix the aggregate privilege definition.
ORA-46102: Privilege string aggregated in security class string is not found: Cause: Definition of an aggregate privilege contained a privilege that is not defined in this or parent security classes.; Action: Fix the aggregate privilege definition.
ORA-46103: Circular definition for security class string: Cause: Security class definition inherited from itself through circular definition.; Action: Fix the security class definition.
ORA-46104: Security class string cannot inherit from base security classes: Cause: Definition of a security class specified an internal base security class as a parent security class.; Action: Remove the internal base security class from the "inherits-from" list.
ORA-46105: unable to load security class string: Cause: The specified security class did not exist.; Action: Create the security class.
ORA-46106: Missing parent security class for security class string: Cause: The specified security class did not have any parent security class.; Action: Add a parent security class using "inherits-from" tag.
ORA-46107: Privilege string not found in the associated security classes: Cause: The specified privilege did not exist in the security classes that were associated with the ACLs.; Action: Use a security class that contains the specified privilege.
ORA-46108: Invalid security class targetNamespace or name.: 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.; Action: Provide valid targetNamespace and name attributes.
ORA-46109: Duplicate definition for privilege string in security class string.: Cause: The privilege name in the security class was previously defined in another security class.; Action: Provide a unique name for the privilege.
ORA-46111: Security Class string specified in the ACL string does not exist.: Cause: An invalid security class was specified in the ACL.; Action: Specify a valid security class.
ORA-46112: Duplicate security class name string under targetnamespace string: Cause: The security class name under the targetnamespce was also used for another security class.; Action: Provide a unique name for the security class.
ORA-46114: ACL name string not found.: Cause: An invalid ACL name was used as one of the operator parameters.; Action: Specify a valid ACL name.
ORA-46115: error raised during evaluation of a data realm: Cause: During SQL execution, evaluation of a data realm failed with an error.; Action: Find the cause of the error from the error stack.
ORA-46116: The ACL string is referenced by a namespace template.: Cause: An attempt was made to delete an access control list (ACL) which was referenced by a namespace template.; Action: Delete the namespace template first if the ACL needs to be deleted.
ORA-46117: The ACL string is set on a user or dynamic role.: Cause: An attempt was made to delete an access control list (ACL) that was set on a user or dynamic role.; Action: Set the ACL on the user or dynamic role to NULL, or delete the user or dynamic role if the ACL needs to be deleted.
ORA-46118: ACL string schema must be SYS.: Cause: An attempt was made to use an access control list (ACL) whose schema was not SYS.; Action: Check and use an ACL whose schema is SYS.
ORA-46119: ACL must not be NULL.: Cause: An attempt was made to specify a NULL value for an access control list (ACL).; Action: Remove the NULL parameter, or specify an existing ACL.
ORA-46200: Attribute cannot be deleted. The attribute is seeded from the template.: Cause: An attempt was made to delete an attribute that was seeded from the template from which this namespace was created.; Action: Attempt to delete only custom attributes.
ORA-46201: Attribute string already exists in namespace string.: Cause: An attempt was made to create an attribute that already exists within the given namespace.; Action: Make sure the attribute name is unique within the namespace.
ORA-46202: handler specified in the namespace template does not exist: Cause: An attempt was made to create a namespace template with an invalid handler function.; Action: Specify a valid handler function in the template.
ORA-46203: handler is not specified in the namespace template: 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.; Action: Specify a valid handler function in the template.
ORA-46204: Multiple UID or GUID specified for the resource.: Cause: An attempt was made to create a resource with multiple UIDs or GUIDs specified in the document.; Action: Provide, at most, one UID or GUID for the resource in the document.
ORA-46205: User with empty GUID cannot create session.: Cause: An attempt was made by an user with an empty GUID to create a session.; Action: Update the GUID for the user.
ORA-46206: Negative inactivity timeout value not allowed.: Cause: An attempt was made to set the inactivity timeout time to a negative value.; Action: Specify a non-negative inactivity timeout value.
ORA-46207: During global callback execution, string is not allowed.: Cause: An attempt was made to execute a disallowed session operation during global callback execution.; Action: Remove the invalid session operation from callback function.
ORA-46208: Circular callback call caused by string: Cause: Circular callback call caused an infinite chain of callback function executions.; Action: Check the event handling functions to identify the source of the circular callback call. Attempt the operation again after the error has been resolved.
ORA-46209: User switch is disallowed for administrative operation.: Cause: An attempt was made to switch user with administrative operation.; Action: Attach the application session to a database session first.
ORA-46210: Source user is not anonymous in user assignment operation.: Cause: An attempt was made to assign user to a named user.; Action: Change source user to the anonymous user first.
ORA-46211: XS entity name length not within valid range.: Cause: An attempt was made to create an XS entity with a name length less than the minimum or more than the maximum allowed.; Action: Ensure the name length is in the valid range (between 1 and 128).
ORA-46212: XS entity with this name already exists.: Cause: An attempt was made to create an XS entity with a name that already belongs to another entity.; Action: Use a different name and try again.
ORA-46213: An unexpected constraint violation occurred during creation of an XS entity.: Cause: An attempt was made to create an XS entity resulting in an unexpected constraint violation.; Action: Check with the DBA or security administrator for resolution.
ORA-46214: Deletion of the XS entity is not allowed while dependencies exist.: Cause: An attempt was made to delete an XS entity with dependent entities in the system.; Action: Remove the dependencies and try again.
ORA-46215: XS entity by the name string did not exist.: Cause: A reference was made to an XS entity that did not exist.; Action: Review the entity reference and try again.
ORA-46216: XS entities are not related.: Cause: An attempt was made to remove a relation that did not exist.; Action: Review the entity reference and try again.
ORA-46217: Operation is not allowed.: Cause: An unexpected operation was performed.; Action: Check with the DBA or security administrator for resolution.
ORA-46218: Unauthorized proxy user: Cause: The current user was not an authorized proxy user of the client user during a switching user operation.; Action: Add the current user as a proxy user of the client user.
ORA-46219: Role version numbers mismatch in server and mid-tier.: Cause: There was another mid-tier attached to the server session with a different set of roles.; Action: Reattach the session supplying the current set of roles.
ORA-46220: database is in readable standby mode; changes will not be saved: Cause: An attempt was made to change an application session in readable standby mode.; Action: None
ORA-46221: cannot modify an application user that is currently connected: Cause: An attempt was made to modify an application user that is currently logged on.; Action: Make sure the application user is logged off, then repeat the command.
ORA-46222: Real Application principal name string conflicts with another user or role name.: Cause: There was already a user or role with that name.; Action: Specify a different user or role name.
ORA-46230: XS administrative operation failed.: Cause: An unexpected error occurred during the requested XS administrative operation.; Action: None
ORA-46231: Granted role is not a regular role.: Cause: A nonregular role was granted to a principal.; Action: Grant a regular role to a principal.
ORA-46232: Circular grant for role: Cause: The role was granted from itself through circular operation.; Action: Fix the role grant operation.
ORA-46233: Circular definition for ACL string: Cause: The ACL was inherited from itself through circular definition.; Action: Fix the ACL definition.
ORA-46235: Policy parameter string did not exist.: Cause: The policy parameter did not exist.; Action: Review the parameter definition and try again.
ORA-46236: Invalid policy parameter type: Cause: Invalid parameter type was specified.; Action: Use the correct parameter type.
ORA-46237: Mid-tier cache synchronization failed: Cause: An unexpected error occurred during mid-tier cache synchronization.; Action: None
ORA-46238: Database user or role 'string' does not exist: Cause: An invalid database user or role was specified as the principal name.; Action: Make sure the database principal is a valid database user or role.
ORA-46239: Key manager not initialized.: Cause: A request to sign the message could not be processed because the key manager was not initialized.; Action: Reinitialize the key manager and resubmit the request.
ORA-46240: Application proxy user is already configured with a schema.: Cause: An attempt was made to add a schema to an application proxy user that already was configured with a schema.; Action: Remove the schema configuration of the application proxy user and try again.
ORA-46241: Application proxy user is not configured with the schema.: Cause: An attempt was made to remove a schema from an application proxy user that was not configured.; Action: None
ORA-46242: Granting a role to XSGUEST is not allowed.: Cause: An attempt was made to grant a role to the XSGUEST seeded user.; Action: None
ORA-46243: The dispatcher's session does not exist.: Cause: The dispatcher's session timed out due to inactivity.; Action: Increase the inactivity timeout for the dispatcher's session.
ORA-46244: The request is not signed by the dispatcher.: Cause: A request was made without the dispatcher's signature. The server is configured to accept requests signed by the dispatcher only.; Action: Ask the administrator to configure the mid-tier allowing the dispatcher signature. Or, ask the administrator to configure the server to not be in dispather-only mode.
ORA-46245: Invalid session or namespace request: Cause: The request message was corrupt.; Action: Check with the DBA or security administrator for resolution.
ORA-46246: session operation failed: 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.; Action: None
ORA-46247: detach completed; session changes are not saved: 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.; Action: None
ORA-46248: This type of database link is not supported.: Cause: An attempt was made to use an unsupported database link type in an XS Data Security session.; Action: Use a supported database link type.
ORA-46250: Invalid value for argument 'string': Cause: Input value was not valid for the procedure.; Action: Use a valid option.
ORA-46251: Value for argument 'string' out of range: Cause: Input value was out of range.; Action: Use a value within allowed range.
ORA-46252: Cannot complete the operation, overlapping job already exists: Cause: Cleanup job already existed which spanned the given audit trail type.; Action: Drop the existing job.
ORA-46253: Cannot complete the operation, overlapping property already exists: Cause: The property already exists which spans the given audit trail type.; Action: Clear the existing property.
ORA-46254: 'string' already exists: Cause: The value being set already existed.; Action: Delete the existing entry.
ORA-46255: Incorrect job name specified: Cause: The job did not exist or was not created by DBMS_AUDIT_MGMT package.; Action: Create the job using DBMS_AUDIT_MGMT package.
ORA-46256: Internal error: Audit Table not partitioned: Cause: Invalid operation on a non partitioned table.; Action: Contact Oracle Support Services.
ORA-46257: Property 'string' cannot be cleared: Cause: The property could not be cleared.; Action: None. The property can only be set or reset.
ORA-46258: Cleanup not initialized for the audit trail: Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP was not called for the erroring audit trail.; Action: Invoke the procedure, DBMS_AUDIT_MGMT.INIT_CLEANUP.
ORA-46260: Error during audit trail cleanup: Cause: The audit trail cleanup operation could not be completed.; Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
ORA-46261: Error during audit trail cleanup, internal error: Cause: The audit trail cleanup could not be completed because of an internal error.; Action: Contact Oracle Support Services.
ORA-46262: Audit table(s) cannot be moved to 'string' tablespace: Cause: The tablespace was either unavailable or did not have enough space to accomodate the audit table being moved.; Action: Make sure that the tablespace is online and has enough space for the audit tables being moved.
ORA-46263: The audit trail is already initialized for cleanup: Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP was already invoked for the audit trail type.; Action: None
ORA-46264: Error during DBMS_AUDIT_MGMT operation: Cause: Could not complete the DBMS_AUDIT_MGMT operation.; Action: Check the PL/SQL error stack and trace files for a possible error. Fix the cause and retry the operation. If the error is internal or if there is no error, contact Oracle Support Services.
ORA-46265: Subset of audit trail is already initialized: Cause: Audit Trail was initialized which spans the given audit trail type.; Action: Use DBMS_AUDIT_MGMT.DEINIT_CLEANUP to deinitialize conflicting audit trail types.
ORA-46266: Missing value for argument 'string' in Oracle RAC enabled database: 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.; Action: Input a valid Oracle RAC instance number for which the configuration must be done.
ORA-46267: Insufficient space in 'string' tablespace, cannot complete operation: 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.; Action: Turn on tracing using DBMS_AUDIT_MGMT.SET_DEBUG_LEVEL to find the amount of space required. Then, allocate that space in the destination tablespace, even if destination tablespace datafile has AUTOEXTEND option turned on. And then, retry the operation.
ORA-46268: Conflicting operation on audit table(s): 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.; Action: Wait until the execution of one of the API's completes and try executing the API again.
ORA-46269: Conflicting operation on audit files: 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.; Action: Wait until the execution of one of the API's complete and try executing the API again.
ORA-46271: Error during DBMS_AUDIT_MGMT operation; database I/O suspended: Cause: An I/O attempt occurred during DBMS_AUDIT_MGMT operation and the database I/O was suspended.; Action: Retry the operation after resuming database I/O suspension. If database I/O is not suspended, contact Oracle Support Services.
ORA-46272: Subset of audit trail is already deinitialized: Cause: Audit trail was deinitialized which spans the given audit trail type.; Action: Use DBMS_AUDIT_MGMT.INIT_CLEANUP to initialize conflicting audit trail types.
ORA-46273: DBMS_AUDIT_MGMT operation failed in one of the PDB: Cause: The executed DBMS_AUDIT_MGMT operation failed in one of the PDB.; Action: Check the trace files for the PDB information where the operation failed. Fix the cause and retry the operation. If the error is internal or if there is no error, contact Oracle Support Services.
ORA-46274: Error during DBMS_AUDIT_MGMT operation; tablespace 'string' not available: Cause: The tablespace associated with Unified Audit Trail is either invalid or is offline.; Action: Check if the tablespace is valid and make sure the tablespace is online and writable.
ORA-46275: Conflicting operations on 'string' table: 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.; Action: Wait for the completion of the conflicting SA_SYSDBA procedure and try executing the DBMS_AUDIT_MGMT API again.
ORA-46276: DBMS_AUDIT_MGMT operation on unified audit trail failed: Cause: Audit records were not generated in the unified audit trail.; Action: Generate audit records in the unified audit trail and retry the operation.
ORA-46277: Conflicting operation on 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.; Action: Wait until the execution of one of the API's complete and try executing the API again.
ORA-46278: Conflicting operation using DBMS_AUDIT_MGMT routines: 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.; Action: Wait until the execution of one of the API's completes and try executing the API again.
ORA-46279: Input value for argument 'string' exceeds the maximum length.: Cause: The identifier name generated after concatenating with 'AMGT$DP$' exceeded 30 or 128 bytes.; Action: Specify a value which does not exceed the maximum length after concatenation. 46340 - 46500 Use for Auditing
ORA-46340: Command cannot have both BY user-list and IN SESSION session-information clauses together: Cause: BY user-list clause was supplied with IN SESSION session-information clause in the command.; Action: Use either BY user-list or IN SESSION session-information clause.
ORA-46341: ALL STATEMENTS option cannot be supplied with BY SESSION clause: 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.; Action: Specify BY ACCESS instead of BY SESSION.
ORA-46342: NOAUDIT command cannot be executed with IN SESSION clause: Cause: An attempt was made to use IN SESSION session-information clause in NOAUDIT command.; Action: None
ORA-46343: Cannot drop AUDSYS user: Cause: An attempt was made to drop the AUDSYS user that hosts the audit trail.; Action: None
ORA-46350: Audit policy string already applied with the BY clause.: Cause: An attempt was made to apply audit policy with the EXCEPT clause which was already applied with the BY clause.; Action: Remove audit policy using the NOAUDIT command.
ORA-46351: Audit policy string already applied with the EXCEPT clause.: Cause: An attempt was made to apply audit policy with the BY clause which was already applied with the EXCEPT clause.; Action: Remove audit policy using the NOAUDIT command.
ORA-46352: NOAUDIT command with the EXCEPT clause is not allowed.: Cause: An attempt was made to remove audit policy using NOAUDIT command with the EXCEPT clause.; Action: Remove audit policy selectively using NOAUDIT command with the BY clause.
ORA-46353: missing or invalid audit policy name.: Cause: A valid audit policy name was expected.; Action: Specify a valid audit policy name.
ORA-46354: missing or invalid audit context or attribute name.: Cause: A valid context or attribute name was expected.; Action: Specify a valid context attribute name.
ORA-46355: missing or invalid privilege audit option.: Cause: Creating or altering the audit policy was attempted with an invalid system privilege audit option.; Action: Use a valid system privilege audit option.
ORA-46356: missing or invalid action audit option.: Cause: Creating or altering the audit policy was attempted with an invalid action audit option.; Action: Use a valid action audit option.
ORA-46357: Audit policy string not found.: Cause: The specified audit policy object did not exist in the database.; Action: Use the correct audit policy name and try again.
ORA-46358: Audit policy string already exists.: Cause: The specified audit policy object already existed in the database.; Action: Use a different name and try again.
ORA-46359: Invalid auditing option for string.: Cause: Creating or altering the audit policy was attempted with an invalid audit option for the object.; Action: Use a valid audit option for the object.
ORA-46360: Same auditing option cannot be both added and dropped in audit policy.: Cause: Altering the audit policy was attempted for adding and dropping the same auditing option in the audit policy.; Action: Choose either to add or drop the audit option.
ORA-46361: Audit policy cannot be dropped as it is currently enabled.: Cause: An attempt was made to drop the audit policy which is currently enabled.; Action: Disable the audit policy before dropping.
ORA-46362: Could not translate variable ORACLE_BASE.: Cause: An attempt to obtain the value for ORACLE_BASE failed.; Action: Make sure the variable is set.
ORA-46363: Audit directory 'string' not found.: Cause: Could not find the specified audit directory.; Action: Make sure the audit directory is created.
ORA-46364: Audit directory 'string' could not be created.: Cause: Could not create the specified audit directory.; Action: Make sure the Oracle process has permissions to create the audit directory.
ORA-46365: Audit file 'string' could not be created.: Cause: Could not create the specified audit file.; Action: Make sure the Oracle process has permissions to create the audit files in the audit directory.
ORA-46366: File 'string' is not a recognized Oracle audit file.: Cause: The file found in Oracle audit directory was not a valid Oracle audit file.; Action: Remove the file from the audit directory and try the action again.
ORA-46367: Database is not opened for write; cannot complete operation.: Cause: An operation requiring the database to be open in read/write mode was attempted.; Action: Open the database in read/write mode.
ORA-46368: Audit policy does not have a simple rule condition.: Cause: Creating or altering the audit policy was attempted with a complex audit condition.; Action: Use a simple rule expression for audit policy condition.
ORA-46369: An error occurred while evaluating audit policy condition.: Cause: Check the error stack for detailed error information.; Action: Fix the errors in the error stack and retry the operation.
ORA-46370: cannot connect as AUDSYS user: Cause: An attempt was made to connect to the database as AUDSYS user.; Action: Do not connect to the database as AUDSYS user.
ORA-46372: audit file 'string' not found: Cause: An operation was attempted on the audit file which was not available in the audit directory.; Action: Make sure the file exists in the $ORACLE_BASE/audit/$ORACLE_SID directory.
ORA-46373: Audit policy 'string' must have at least one audit option.: Cause: An attempt was made to create, alter or enable the empty audit policy.; Action: Use at least one audit option in the audit policy.
ORA-46374: error during AUDIT or NOAUDIT of audit policy in an Oracle RAC enabled database: Cause: The operation could not be completed on one or more Oracle RAC instances.; Action: Check the trace file for more information. Ensure every instance in Oracle RAC is operational and retry the operation.
ORA-46376: FGA policy owner 'string' is not available: Cause: An attempt to import Fine-Grained Audit (FGA) policy failed because the specified FGA policy owner has not been imported.; Action: Perform the import of the specified user schema and retry the operation.
ORA-46377: Auditing cannot be configured on the specified system privilege.: Cause: An attempt was made to configure auditing on the system privilege which is not supported by the audit facility.; Action: None
ORA-46378: Cannot use bind variable in VERSIONS clause when the object has FGA policy defined on it.: Cause: The object being accessed had a fine-grained audit (FGA) policy defined on it and the VERSIONS clause contained a bind variable.; Action: Rewrite the query without the use of a bind variable in the VERSIONS clause.
ORA-46379: generation of audit session ID failed with error 'number': Cause: An error was encountered while generating the audit session ID.; Action: Retry the operation and, if the error persists, contact Oracle Support Services.
ORA-46380: invalid usage of EXCEPT clause: 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; Action: Do not use the EXCEPT clause here.
ORA-46381: audit configuration using global roles is not supported: Cause: A global role was found in the enablement list.; Action: Remove the global role from the enablement list and retry the operation.
ORA-46382: must disable unified audit policy on this role first: 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.; Action: Use NOAUDIT POLICY command to disable the unified audit policy on users to whom this role is directly granted.
ORA-46383: incorrect order of unified audit options: Cause: The order in which audit options were mentioned was incorrect.; Action: Make sure privilege audit options are followed by action audit options which in turn should be followed by role audit options.
ORA-46384: incorrect order of unified audit policy clause: Cause: The order in which ADD, DROP or CONDITION clauses were mentioned was incorrect.; Action: Make sure the ADD clause is followed by the DROP clause which in turn should be followed by the CONDITION clause.
ORA-46385: DML and DDL operations are not allowed on table "string"."string".: Cause: A DML or DDL operation was attempted on a unified auditing internal table.; Action: No action required. Only Oracle is allowed to perform such operations on a unified auditing internal table.
ORA-46386: error during TRANSFER_UNIFIED_AUDIT_RECORDS operation: Cause: Either the database was not open in the read/write mode, or the transfer of the unified audit records was already in progress.; Action: Open the database in read/write mode and rerun the TRANSFER_UNIFIED_AUDIT_RECORDS operation after the ongoing transfer process finishes.
ORA-46387: Cannot perform this operation on unified audit internal table: Cause: An attempt was made to perform an operation that is not allowed on a non-partitioned unified audit internal table.; Action: No action required. This operation can only be performed on partitioned unified audit internal table.
ORA-46388: unified audit files space usage in container is too high: Cause: Space usage by unified audit files in the current container has exceeded the value of MAX_AUDIT_STORAGE for the container.; Action: Create some space by deleting the old audit records using DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL or open the container in the read/write mode and execute DBMS_AUDIT_MGMT.LOAD_UNIFIED_AUDIT_FILES.
ORA-46500: User is not a common user.: 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.; Action: Specify a common user.
ORA-46501: Object is not a common object.: 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.; Action: Specify a common object.
ORA-46503: not connected to a pluggable database: 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.; Action: Connect or switch session to a pluggable database to create local audit policy or configuration.
ORA-46504: AUDIT command cannot specify ON object and CONTAINER clauses together.: 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.; Action: Do not specify the CONTAINER clause while configuring object auditing using SQL AUDIT command.
ORA-46505: Role is not a common role.: 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.; Action: Specify a common role.
ORA-46506: FGA handler schema is not common user.: Cause: An attempt was made to create fine-grained Audit (FGA) policy on common object and associated handler schema is not common user.; Action: Specify FGA handler schema as common userappropriately.
ORA-46507: FGA object name is not a common object.: 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.; Action: Specify a common object.
ORA-46508: not connected to root container: 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).; Action: Connect to the root and create FGA policies on object-linked common objects.
ORA-46600: invalid ADMINISTER KEY MANAGEMENT command
ORA-46601: missing KEYSTORE, ENCRYPTION, KEY, or TAG keyword
ORA-46602: missing OPEN or CLOSE keyword
ORA-46603: invalid ADMINISTER KEY MANAGEMENT CREATE command
ORA-46604: invalid or missing keystore file name: Cause: The required keystore file name was invalid or missing.; Action: Specify a valid keystore file name.
ORA-46605: master key identifier is invalid or missing
ORA-46606: tag is invalid or missing
ORA-46607: client secret is invalid or missing
ORA-46608: client identifier is invalid or missing
ORA-46609: export or import secret is invalid or missing
ORA-46610: expecting SELECT query that returns the master key identifiers
ORA-46612: import file name is invalid or missing
ORA-46614: export file name is invalid or missing
ORA-46615: missing WITH or CONTAINER keyword
ORA-46616: master key is invalid or missing
ORA-46617: master key identifier is invalid or missing
ORA-46620: backup for the keystore cannot be taken: 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.; Action: Either specify an ASM path name for the backup location if the keystore location is an ASM path or specify a non-ASM path name for the backup location if the keystore location is not an ASM path.
ORA-46621: no backup identifier specified: Cause: Backup identifier was not specified.; Action: Provide a valid backup identifier.
ORA-46622: location of the backed up keystore is incorrect: Cause: Keystore location where the backup was to be created was incorrect.; Action: Provide a valid location to backup the keystore.
ORA-46623: cannot create the keystore file name: Cause: Keystore name could not be formed possibly due to the incorrectly specified keystore location.; Action: Verify the location to where the keystore can be backed up.
ORA-46624: cannot find the source keystore: Cause: The source keystore for which the backup was requested was not found.; Action: Verify that the source keystore exists and try again.
ORA-46625: backup keystore already exists: Cause: A backup of the keystore of the same name already existed in the given location.; Action: Change the location of the backup keystore or the backup identifier of the backup keystore and try again.
ORA-46626: cannot create a backup of the keystore: Cause: The backup of the keystore could not be created.; Action: Check the trace file for more information and try again.
ORA-46627: keystore password mismatch: Cause: The keystore password specified did not match that of the keystore that was open.; Action: Specify the correct keystore password.
ORA-46628: cannot alter the software keystore password: Cause: An attempt was made to alter the software keystore password.; Action: Check the viability of the keystore and replace the keystore from the backup if required and try to alter the keystore password.
ORA-46629: keystore was not open after the alter keystore operation: Cause: The keystore password was changed. However, the keystore was closed during this operation.; Action: Reopen the keystore with the new password.
ORA-46630: keystore cannot be created at the specified location: Cause: Keystore could not be created at the specified location because a keystore of the same type already exited.; Action: Specify a different location to create the keystore. If no keystore exists and the operation is failing, check the trace file and try again.
ORA-46631: keystore needs to be backed up: Cause: The keystore was not backed up. For this operation to proceed, the keystore must be backed up.; Action: Backup the keystore and try again.
ORA-46632: password-based keystore does not exist: Cause: Password-based keystore was missing for this operation. Auto login keystore can be created from a password-based keystore only.; Action: Specify a location where the password-based keystore exists.
ORA-46633: creation of a password-based keystore failed: 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.; Action: Check the trace file for more information, create permissions on the specified location, or specify a different location and try again.
ORA-46634: creation of a local auto login keystore failed: 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.; Action: Check the trace file for more information, specify the correct password for the password-based keystore, create permissions on the specified location, or specify a different location and try again.
ORA-46635: creation of an auto login keystore failed: 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.; Action: Check the trace file for more information, specify the correct password for the password-based keystore, create permissions on the specified location, or specify a different location and try again.
ORA-46636: cannot add second keystore to the target keystore: Cause: The second keystore could not be added to the target keystore.; Action: Check trace files for more information. Delete the target keystore and try merging the two keystores again.
ORA-46637: cannot add first keystore to the target keystore: Cause: The first keystore could not be added to the target keystore.; Action: Check trace files for more information. Delete the target keystore and try merging the two keystores again.
ORA-46638: merging of the two keystores failed: Cause: The two keystores could not be merged.; Action: Check trace files for more information. If the target keystore is corrupted, replace it from the backup and try merging the two keystores again.
ORA-46639: backup of keystore failed during migration: Cause: Keystore location was not configured correctly in the sqlnet.ora file.; Action: Keystore location is missing or not correct in the sqlnet.ora file. Specify the correct keystore location for migration and backup.
ORA-46640: incorrect file name for exporting keys: Cause: The file name of the file to which keys from the keystore will be written was incorrect or invalid.; Action: Verify the file name. Ensure that both the full path and the file name are provided.
ORA-46641: incorrect file name for importing keys: Cause: The file name of the file from which the keys will be read and saved in the keystore was incorrect or invalid.; Action: Verify the file name. Ensure that both the full path and the file name are provided.
ORA-46642: key export destination file already exists: Cause: The file name specified as the export destination for keys exported from the keystore was already in existence.; Action: Specify a different file name that does not exist.
ORA-46643: file from which keys are to be imported does not exist: Cause: The specified file from which the keys are to be imported into the keystore did not exist.; Action: Specify the name of a file that contains keys exported from the keystore.
ORA-46644: creation or open of file to store the exported keys failed: 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.; Action: Verify that the file name is valid and that the Oracle process has sufficient privilege to create, open and write to the file.
ORA-46645: open of file from which keys are to be imported 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.; Action: Verify that the file name is valid and that the Oracle process has sufficient privilege to read the file.
ORA-46646: file from which keys are to be imported is invalid or lacks needed file permission: 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.; Action: Specify a valid file, containing keys which were previously exported from the keystore. Also, ensure that the file has read and write access permission.
ORA-46647: specified protection differs from that specified in the file: 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.; Action: Provide a valid protection option, ensuring that it is the same protection option that was in the file from which the keys are to be imported.
ORA-46648: cannot commit the keys to the keystore: Cause: The operation of writing the keys to the keystore failed.; Action: Verify that the keystore is not corrupt. Copy the keystore from the backup if it is corrupt. Retry the command.
ORA-46649: master key with the specified identifier does not exist: Cause: Master key with the specified identifier does not exist in the keystore.; Action: Specify a valid master key identifier for the SQL command and retry the command.
ORA-46650: cannot retrieve information for a master key identifier: Cause: The master key or the master key information associated with a specified master key identifier did not exist.; Action: Check the contents of the trace file to identify the faulty master key identifier. Either fix or drop the faulty master key, then retry the command.
ORA-46651: cannot create a master key: Cause: Master key creation failed.; Action: Check the trace file for errors and retry the command.
ORA-46652: cannot create tag for the master key: Cause: Creation of the tag for the specified master key failed.; Action: Check the contents of the trace file for errors and retry the command.
ORA-46653: cannot retrieve master key information: Cause: Retrieval of the master key information for the specified master key identifier failed.; Action: Check the contents of the trace file for errors and retry the command.
ORA-46654: cannot add the imported keys to the keystore: Cause: The operation of writing the imported keys to the keystore failed.; Action: Check the contents of the trace file for more information on the cause of the failure and retry the command.
ORA-46655: no valid keys in the file from which keys are to be imported: Cause: The specified keystore, from which keys are to be imported, did not contain any valid keys.; Action: None
ORA-46656: operation not valid for container database: Cause: The specified operation was not supported for the container database.; Action: None
ORA-46657: the source keystores are the same: Cause: The specified source keystores to be merged were the same. There is no need to merge these keystores.; Action: Check the locations and types of the specified keystores. Specify the correct path and types for the source keystores, if necessary.
ORA-46658: keystore not open in the container: Cause: The keystore was not open in the container.; Action: Open the keystore in the container.
ORA-46659: master keys for the given PDB not found: Cause: The master keys for the specified pluggable database (PDB) could not be retrieved.; Action: Check if the master keys were generated for the specified PDB and retry the command.
ORA-46660: the source and target keystores are the same: Cause: The specified source and target keystores to be merged were the same. There is no need to merge these keystores.; Action: Check the locations and types of the specified keystores. Specify the correct path and types for the source and target keystores, if necessary.
ORA-46661: keystore not open in root container: Cause: The root container keystore was not open.; Action: Open the root container keystore.
ORA-46662: master keys not created for all PDBs: Cause: Creation of the master key failed for one or more pluggable databases (PDBs).; Action: Check the trace files for errors. Create the keys in PDBs where the operation failed or retry the command.
ORA-46663: master keys not created for all PDBs for REKEY: Cause: Creation of the master key failed for one or more pluggable databases (PDBs) and as such REKEY failed for these PDBs.; Action: Check the trace files for errors. REKEY the keys in PDBs where the master keys could not be created or retry the command.
ORA-46664: master keys not created for any PDBs during REKEY: Cause: Creation of the master key failed for all pluggable databases (PDBs).; Action: Check the contents of the trace file for more information on the cause of the failure and retry the command.
ORA-46665: master keys not activated for all PDBs during REKEY: Cause: Activation of the master key failed for one or more pluggable databases (PDBs) and as such REKEY failed for these PDBs.; Action: Check the trace files for errors. Activate the keys in PDBs where the master keys were created but not activated or retry the command.
ORA-46666: master keys not created or activated for all PDBs during REKEY: 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.; Action: Check the trace files for errors. REKEY the PDBs where the master keys could not be created. Activate the keys in PDBs where the master keys were created but not activated or retry the command.
ORA-46667: client not found in the keystore: Cause: An entry with the given client name was not found in the keystore.; Action: Add the secret for the given client to the keystore, if required.
ORA-46668: client already exists in the keystore: Cause: An entry with the given client name was already in existence in the keystore.; Action: Delete or update the entry with the client name.
ORA-46669: the target keystore does not exist: Cause: The location specified for the target keystore did not contain a valid keystore, or target keystore did not have valid file permissions.; Action: Specify a different location for the target keystore where it exists. Also, check the file permissions of the target keystore.
ORA-46670: client secret keystore operation failed: Cause: The client secret keystore add, update or delete operation failed.; Action: Open the keystore and retry the client secret keystore operation.
ORA-46671: master key not set in root container: Cause: Master key was not set in the root container.; Action: Set the Master key in the root container.
ORA-46672: backup keystore file name could not be stored: Cause: The file name of the keystore backup could not be recorded in props$.; Action: Open the keystore and retry the backup operation.
ORA-46673: write to the export file failed: Cause: Oracle was unable to write an entry to the export file.; Action: Check the trace file for more information and retry the operation. If there is no trace information and trying the operation again fails, contact Oracle Support Services.
ORA-46674: read from the export file failed: Cause: Oracle was unable to read an entry from the export file.; Action: Check the trace file for more information and retry the operation. If there is no trace information and trying the operation again fails, contact Oracle Support Services.
ORA-46675: write of keys for export failed: Cause: Oracle was unable to write an entry for export.; Action: Check the trace file for more information and retry the operation. If there is no trace information and trying the operation again fails, contact Oracle Support Services.
ORA-46676: read of keys for import failed: Cause: Oracle was unable to read an entry for import.; Action: Check the trace file for more information and retry the operation. If there is no trace information and trying the operation again fails, contact Oracle Support Services.
ORA-46677: specified backup identifier exceeds maximum length: Cause: The backup identifier within the ASM file name of the keystore exceeded the maximum length of 12 characters.; Action: Specify a backup identifier that does not exceed the limit.
ORA-46678: cannot encrypt an identity column created with GENERATED BY DEFAULT or GENERATED ALWAYS: Cause: An attempt was made to encrypt an identity column created with GENERATED BY DEFAULT or GENERATED ALWAYS keywords.; Action: An identity column created with the GENERATED BY DEFAULT or GENERATED ALWAYS keywords cannot be encrypted.
ORA-46679: missing or invalid master key encryption algorithm: Cause: An encryption algorithm for the master key was missing or invalid in the user command.; Action: Specify a valid algorithm: 'AES256', 'ARIA256', 'SEED128', or 'GOST256'.
ORA-46680: master keys of the container database must be exported: Cause: The master keys of the container database were not exported.; Action: Export the master keys of the container database before unplugging the container database.
ORA-46681: reverse migration failed for PDB: Cause: Reverse migration failed for one or more pluggable databases (PDB).; Action: Check the trace files for errors. Retry the command.
ORA-46683: addition of master key string not supported with CONTAINER=ALL: 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.; Action: Retry the operation without CONTAINER=ALL clause.
ORA-46684: master key identifier exists in the keystore: Cause: An attempt was made to add a master key with a master key identifier that was already present in the keystore.; Action: Specify a different value for the master key identifier in the master key string.
ORA-46685: invalid master key identifier or master key value: 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.; Action: Specify a correct value for the master key identifier or master key in the master key string.
ORA-46686: missing or invalid master key string: Cause: The master key string was missing or invalid.; Action: Specify the correct master key string.
ORA-46687: operation not supported for HSM: Cause: The specified operation is not supported with Hardware Security Module (HSM).; Action: Check the trace file for more details.
ORA-46688: cannot move a master key: Cause: The master key could not be moved out of the keystore.; Action: Check whether the specified master key identifiers are valid, and if they are found in the V$ENCRYPTION_KEYS view. Container keys can be moved from the CDB$ROOT only when the container is unplugged and dropped from the CDB. Check the trace file for additional errors if needed. Retry the command.
ORA-46689: specified master key identifier does not exist in the keystore: Cause: An attempt was made to move a master key that did not exist in the keystore.; Action: Check if the master key identifier exists in the keystore by querying the V$ENCRYPTION_KEYS view.
ORA-46690: could not create wallet: 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.; Action: Check the permissions for the Oracle user on the directory or check if the directory exists.
ORA-46691: The value of the KEYSTORE_CONFIGURATION attribute is invalid.: Cause: An attempt was made to set or use an invalid value for the KEYSTORE_CONFIGURATION attribute of the TDE_CONFIGURATION instance initialization parameter.; Action: Use a valid value for the KEYSTORE_CONFIGURATION attribute of the TDE_CONFIGURATION instance initialization parameter. When using WALLET_ROOT, set the TDE_CONFIGURATION instance initialization parameter correctly in both the root and in the pluggable database. A value must be provided for the TDE_CONFIGURATION instance initialization parameter if a value is provided for the WALLET_ROOT instance initialization parameter, in order to fully specify the keystore configuration of the CDB$ROOT and of the pluggable database (either both parameters must be present, or both must be absent). For an ADMINISTER KEY MANAGEMENT ISOLATE KEYSTORE operation, the KEYSTORE_CONFIGURATION attribute of the CDB$ROOT must have the value FILE. For an ADMINISTER KEY MANAGEMENT ISOLATE KEYSTORE operation, if a value for the KEYSTORE_CONFIGURATION attribute is set in the pluggable database, it must have the value FILE. If the TDE_CONFIGURATION instance initialization parameter is not set in the pluggable database, the isolation operation automatically sets its KEYSTORE_CONFIGURATION attribute to FILE.
ORA-46692: cannot close wallet: Cause: An attempt was made to close the wallet when it was in use.; Action: Close the wallet in any pluggable database that is configured with an isolated wallet. Alternatively, use the FORCE KEYSTORE CLOSE clause of the ADMINISTER KEY MANAGEMENT command.
ORA-46693: The WALLET_ROOT location is missing or invalid.: Cause: An attempt was made to perform a keystore operation when the instance initialization parameter WALLET_ROOT was missing or invalid.; Action: Start the database after setting the WALLET_ROOT instance initialization parameter to the directory where all of the wallets are stored.
ORA-46694: The keys are already in the root keystore.: 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.; Action: No action is required. Check the value of the TDE_CONFIGURATION instance initialization parameter of your system and ensure that you are issuing the ADMINISTER KEY MANAGEMENT UNITE KEYSTORE command in the correct pluggable database.
ORA-46695: The value of the TDE_CONFIGURATION instance initialization parameter is invalid.: Cause: An attempt was made to set or use an invalid value for the TDE_CONFIGURATION instance initialization parameter.; Action: Use a valid value for the TDE_CONFIGURATION instance initialization parameter. The KEYSTORE_CONFIGURATION attribute must be present and must have a valid value. During recovery, the CONTAINER attribute can also be specified and its value must be a valid container name. The CONTAINER attribute can only be be specified when the TDE_CONFIGURATION instance initialization parameter is modified in the CDB$ROOT, not when it is modified in a pluggable database.
ORA-46696: A master key is required by another pluggable database.: 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.; Action: Before attempting to isolate the keys of a pluggable database, perform an ADMINISTER KEY MANAGEMENT SET KEY command on each pluggable database that requires the master key, in order to remove any dependency on the master key being isolated. Alternately, include the FORCE clause and issue the ADMINISTER KEY MANAGEMENT FORCE ISOLATE KEYSTORE command, which causes the master keys of the pluggable database to be copied to the isolated keystore rather than moved to it, so that the keys remain available to any pluggable database that requires them.
ORA-46697: Keystore password required.: Cause: The keystore password clause was not provided for this SQL command.; Action: Retry the command with a keystore password clause.
ORA-46698: CDB$ROOT is not open.: Cause: CDB$ROOT was not open.; Action: Open the CDB$ROOT and retry the command.
ORA-46699: cannot create a keystore: 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).; Action: Open the pluggable database in read/write mode or configure the pluggable database as ISOLATED, and retry the ADMINISTER KEY MANAGEMENT CREATE KEYSTORE command.
ORA-46700: failed to copy or move wallet: Cause: An attempt was made to either copy or move the isolated wallet of the pluggable database (PDB) that was plugged.; Action: Ensure that the source wallet location and the file specified in XML exist on disk and are accessible from this database. Also, ensure that WALLET_ROOT is set and the directory specified in WALLET_ROOT exists on the disk.
ORA-46701: failed to delete source wallet: Cause: An attempt was made to delete the source wallet file during the pluggable database (PDB) plug with MOVE clause.; Action: Ensure that the source wallet file and the directory allow deletion of the wallet.
ORA-46900: unsupported proxy authentication: Cause: A proxy authentication was attempted using an administrative privilege.; Action: Authenticate without any administrative privilege if proxy authentication is desired.
ORA-46951: unsupported format for password file 'string': 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.; Action: Re-create the password file and grant the administrative privileges to users appropriately.
ORA-46952: standby database format mismatch for password file 'string': 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.; Action: Re-create the password file on the standby database using the same password file format as that of the primary database. Ensure that the password file format used on the standby database matches that of the primary database.
ORA-46953: The password file is not in the 12.2 format.: 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.; Action: Create the password file in 12.2 format or migrate the existing password file to 12.2 format, then retry the operation.
ORA-46981: Access to service string from string was denied.: Cause: Access to this service from this location was not allowed.; Action: Contact Oracle Support Services.
ORA-46987: Access control propagation failed (error=number).: Cause: The executed DBMS_SFW_ACL_ADMIN operation failed.; Action: Retry the operation.
ORA-46988: Access control propagation timed out.: Cause: The executed DBMS_SFW_ACL_ADMIN operation timed out.; Action: Retry the operation.