ORA-41001 to ORA-42911

91 ORA-41001 to ORA-42911

ORA-41001: session id list not specified: Cause: An attempt to migrate was made, which failed because the session id list specified was null.; Action: Check the session id list, and try again with a valid value.
ORA-41002: destination instance not specified: Cause: An attempt to migrate was made, which failed because the destination instance specified was null.; Action: Check the destination instance , and try again with a valid value.
ORA-41003: client id not specified: Cause: An attempt to migrate was made, which failed because the client id specified was null.; Action: Check the client id, and try again with a valid value.
ORA-41004: percentage not specified: Cause: An attempt to migrate was made, which failed because the percentage specified was null.; Action: Check the percentage, and try again with a valid value.
ORA-41005: session id list not specified: Cause: An attempt to cancel migration was made, which failed because the session id list specified was null.; Action: Check the session id list, and try again with a valid value.
ORA-41006: session id not specified: Cause: An attempt to get migration status was made, which failed because the session id specified was null.; Action: Check the session id, and try again with a valid value.
ORA-41007: sid field is null: Cause: A session id instance passed into a dbms_tsm procedure or function had a null sid field.; Action: Check the session id, and try again with a valid value.
ORA-41008: serial# field is null: Cause: A session id instance passed into a dbms_tsm procedure or function had a null serial# field.; Action: Check the session id, and try again with a valid value.
ORA-41009: Session with session number string, serial number string does not exist: Cause: An attempt to migrate was made, which failed because of invalid session number and/or serial number.; Action: Check the session number and serial number and try again.
ORA-41010: No more memory to hold connection state information: Cause: An attempt to reference more connections than configured; Action: Check the connection information and try again.
ORA-41011: migrate operation for session id string, serial number string failed: Cause: A migration related operation failed because of contention between sessions.; Action: Check the additional error codes for more information, and retry the operation later.
ORA-41012: session number string, serial number string cannot be migrated: Cause: The specified session could not be migrated by using the transparent session migration due to its current state.; Action: Verify the session number and serial number, and try again.
ORA-41013: instance name not specified: Cause: An attempt to migrate was made, which failed because the instance name specified was null.; Action: Check the instance name, and try again with a valid value.
ORA-41014: session number string with serial number string is already being migrated: Cause: An attempt was made to migrate a session that was already being migrated.; Action: Check the session number and serial number and try again.
ORA-41015: destination connect string not specified: Cause: A migration attempt was made, which failed because the connect string specified was null.; Action: Check the connect string and try again.
ORA-41016: Session recreation failed: Cause: Session recreation failed at the destination instance.; Action: Check session state and try migration again
ORA-41017: Session prepare failed for session number string, serial number string: Cause: A migration attempt was made, which failed because session prepare failed.; Action: Retry migration again after checking all arguments.
ORA-41019: Session begin at the destination instance failed: Cause: Session begin failed at the destination instance because the shadow connection could not be established.; Action: Check the connect string and try beginning the session again.
ORA-41020: invalid value "string" specified for parameter "string": Cause: An invalid value was specified for the the given parameter.; Action: Correct the value being specified for the parameter.
ORA-41021: OCI error during transparent session migration: Cause: An OCI operation failed during transparent session migration.; Action: Check the OCI error signalled, and take corrective action.
ORA-41022: instance name not specified: Cause: An attempt to recover after instance death was made, which failed because the instance name specified was null.; Action: Check the instance name, and try again with a valid value.
ORA-41023: death time not specified: Cause: An attempt to recover after instance death was made, which failed because the death time specified was null.; Action: Check the death time, and try again with a valid value.
ORA-41024: Cursor needs to be parsed again: Cause: An SQL operation failed because the cursor state was lost.; Action: Reissue all operations starting from parse.
ORA-41025: sid field string is invalid: Cause: A session id instance passed into a dbms_tsm procedure or function had an invalid sid field.; Action: Check the session id, and try again with a valid value.
ORA-41026: serial# field string is invalid: Cause: A session id instance passed into a dbms_tsm procedure or function had an invalid serial# field.; Action: Check the serial#, and try again with a valid value.
ORA-41027: Error status string during OCI operation at string: Cause: An OCI operation failed during transparent session migration.; Action: Check the OCI error signalled, and take corrective action.
ORA-41028: Session id not specified: Cause: An attempt to migrate was made, which failed during migration because the session id specified by the client was null.; Action: Check the session id, and try again with a valid value.
ORA-41029: Destination session id not specified for sid string serial# string: Cause: An attempt to migrate was made, which failed during migration because the destination session id specified by the client was null.; Action: Check the session id, and try again with a valid value.
ORA-41030: Session id not specified: Cause: An attempt to migrate was made, which failed during migration because the session id specified by the client was null.; Action: Check the session id, and try again with a valid value.
ORA-41031: Destination session key not specified for sid string serial# string: Cause: An attempt to migrate was made, which failed during migration because the destination session key specified by the client was null.; Action: Check the session id, and try again with a valid value.
ORA-41100: Oracle Cluster Registry operation failed with event string.: Cause: The Portable Clusterware/Oracle Cluster Registry stack returned an error.; Action: Check if the Portable Clusterware stack is properly brought up.
ORA-41101: The database: string has already been designated as Cluster Director.: Cause: An attempt was made to designate multiple databases as the Cluster Director.; Action: Undesignate the existing Cluster Director before Designating a new one.
ORA-41102: No database has currently been designated as Cluster Director.: Cause: An attempt was made to query/undesignate a Cluster Director when no database has been designated as Cluster Director.; Action: n/a
ORA-41103: Only the designated Cluster Director: string can undesignate itself.: Cause: An attempt was made to undesignate the current Cluster Director by a database that is not the Cluster Director.; Action: Login to the currently designated Cluster Director to perform the undesignation.
ORA-41104: The database: string is the Cluster Director.: Cause: An attempt was made to control the Cluster Director on a database that is not the Cluster Director.; Action: Log in to the currently designated Cluster Director to perform the control operation.
ORA-41105: The Cluster Director is not stopped.: Cause: An attempt was made to control the Cluster Director before the Cluster Director was stopped.; Action: Use dbms_cluster_director.stop to stop the Cluster Director and retry the control operation.
ORA-41106: invalid argument string: value is null: Cause: An attempt to read the scan hostname or port failed; Action: Verify pcw is running and scan is configured. Run grdcscan read_config to verify or grdcscan set_config host:port to set scan name and port.
ORA-41107: invalid argument: service string cannot be found: Cause: The program attempted to access a nonexistent or deleted service.; Action: Check to make sure the service has been properly created.
ORA-41108: Posting system alert with reason_id string failed with code [string] [string]: Cause: Internal Error: An attempt to post a system alert failed.; Action: If this condition repeats, please contact Oracle Support.
ORA-41109: Updating system alert with reason_id string failed; previous alert not found: Cause: System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.; Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support.
ORA-41110: The Director has blocked this instance. Cannot start [string]: Cause: An attempt to start services on an instance that will be shutdown; Action: Start the services on another available instance
ORA-41201: Session state not capturable due to reason (string, string): Cause: Session state capture was initiated when session state could not be captured.; Action: Check session state status and make sure session state can be captured.
ORA-41202: Session state capture or restore failed: Cause: Capture or restore operation failed.; Action: Check session state status and failure reason for details.
ORA-41203: Invalid session state operation: Cause: Invalid session state operation was issued.; Action: Check if session status was valid for the current operation.
ORA-41204: Session capture in progress: Cause: Session state capture was initiated and could not perform the requested operation.; Action: Wait for the current capture to complete or abort it.
ORA-41205: Invalid parameter for session state capture or restore: Cause: Invalid parameter was passed to session state capture or restore interface.; Action: Correct the invalid parameter(s).
ORA-41206: Session capture or restore internal error KPCSFR-string: Cause: Internal operation error was encountered.; Action: Turn on related trace for details and report it as a bug.
ORA-41207: Cannot restore session state due to reason (string, string): Cause: Session state restore was initiated when session was not ready for state restore.; Action: Restore session state immediately after logging into a session or perform necessary operations to make the session ready for restore; for example, commit current transaction, or close BFiles.
ORA-41208: OCI error during session state capture and restore: Cause: An OCI operation failed during an internal operation of session state capture and restore.; Action: Check the OCI error signaled and take corrective action.
ORA-41209: OCI operation failed at string due to ORA-string: Cause: An OCI operation failed during an internal operation of session state capture and restore.; Action: Check the OCI error signaled and take corrective action.
ORA-41210: Failed to resolve session state directory object: Cause: Session state directory object passed to capture or restore was incorrect.; Action: Verify session state directory object and retry.
ORA-41211: Failed to insert capture or restore record: Cause: An error occurred while capture or restore record was being stored into the database.; Action: Check the error signaled and take corrective action.
ORA-41251: Failed to restore session state from a file (error code number): Cause: Session state file may be corrupted.; Action: Ensure that the file is a session state file.
ORA-41252: Failed to switch to new session in SSCR: Cause: This is the generic internal error number for the SSCR exceptions. This indicates that the SSCR has encountered an exceptional condition.; Action: Report as a bug.
ORA-41253: Failed to access session state file: Cause: An error was encountered while reading from or writing to session state capture file.; Action: Check the error stack for the actual error number and turn on tracing if necessary.
ORA-41254: Invalid session state file: string: Cause: An invalid session state file was used in session state restore operation.; Action: Check if the session state file is a valid file created by session capture.
ORA-41255: Package not supported: string: Cause: The specified package is not supported.; Action: Do not call the package functions and procedures.
ORA-41300: File driver is not initialized: Cause: An attempt was made to operate on the uninitialized file driver.; Action: Initialize the file driver using the OCIServerAttach function.
ORA-41301: failed to write data to file: Cause: You may not have sufficient privileges or quotas for this action.; Action: Ensure that you have sufficient privileges and quotas for this action.
ORA-41302: failed to read data from file: Cause: The file may not exist or you do not have privileges for this action.; Action: Ensure that the file exists and that you have sufficient privileges for this action.
ORA-41303: Received partial data from file: Cause: This is the generic internal error number for file driver exceptions. This indicated that file driver encountered an exception condition.; Action: Report as a bug.
ORA-41304: Failed to connect to file driver: Cause: The connect string may be incorrect.; Action: Ensure that the connect string is correct.
ORA-41305: Failed to open file: Cause: You may not have sufficient privileges for this action.; Action: Ensure that the file exists and that you have sufficient privileges for this action.
ORA-41400: Bind character set (string) does not match database character set (string): Cause: In this recursive OCI call, the bind character set was different from the current database character set. This is usually caused by database character set change.; Action: Be sure to obtain bind data in database character set and do rebind in the current environment.
ORA-41401: Define character set (string) does not match database character set (string): Cause: In this recursive OCI call, the define character set was different from the current database character set. This is usually caused by database character set change.; Action: Be sure to do redefine in the current environment.
ORA-41402: SCNs not valid after failover; failover cannot continue: Cause: SCNs for replay are not valid on target database. The system change numbers (SCN) recorded during the original execution were not valid on the new database after failover. This might happen if the new database was opened with RESETLOGS option, or if the new database was set up to allow significant lag in replication. The failover could not continue.; Action: Check the SCNs on target and source, and whether RESETLOGS was used when opening the target database.
ORA-41403: failed over to older server; failover cannot continue (string, string, string): Cause: Target database version is older than source database version. Failover replay was enabled for a service in which some standby databases were older than the original server and could not replay work from the original server.; Action: Keep standby database current with primary.
ORA-41404: invalid replay context: Cause: Application Continuity protocol was violated.; Action: Contact Oracle Support Services.
ORA-41405: Failed over to older server; failover cannot continue (string, string).: Cause: Target database version is older than source database version. Failover replay was enabled for a service in which some standby databases were older than the original server and could not replay work from the original server.; Action: Keep standby database current with primary.
ORA-41406: driver disabled replay due to an unsupported call: Cause: Application replay encountered a command that was not supported for replay, and so replay was disabled. Client driver has initiated disable.; Action: Check the user call that disabled. TAC will enable when possible.
ORA-41407: SQL command not supported for replay; replay disabled: Cause: Application replay encountered a command that was not supported for replay, and so replay was disabled. Server has initiated disable.; Action: Check the user call that disabled. TAC will enable when possible.
ORA-41408: embedded COMMIT in last call; failover cannot continue: Cause: The Oracle server process failed after committing a transaction but COMMIT was embedded in a stored procedure. Failover cannot continue.; Action: Do not resubmit, your transaction committed.
ORA-41409: cannot replay committed transaction; failover cannot continue: Cause: The Oracle server process failed after committing a transaction in the current request. Failover cannot continue.; Action: Do not resubmit, your transaction committed.
ORA-41410: call committed a transaction and started a new transaction; failover cannot continue: Cause: The Oracle server process failed after committing a transaction in the current request. Your request has more than one transaction. Failover cannot continue.; Action: Do not resubmit, your transaction committed. Structure your application to have one commit per request. Consider using TAC.
ORA-41411: too many round trips in request; replay disabled: Cause: The Oracle server process failed after executing a single request with more than 65535 round trips from the client to the server.; Action: Do not resubmit. Reduce application calls per request, for example, use an array fetch or set a prefetch size.
ORA-41412: results changed during replay; failover cannot continue: Cause: Replay terminated as results differed from original execution. Failover cannot continue.; Action: User may resubmit request.
ORA-41413: too much data in call capture; replay disabled: Cause: The Oracle server process failed after executing a request with a complex call whose capture had too much data, therefore, replaying of the request was not possible.; Action: Resubmit and reduce application calls per request.
ORA-41414: could not allocate memory for call capture; replay disabled: Cause: The Oracle server process encountered a memory allocation failure while executing the replay of the request, therefore replaying of the request was not possible.; Action: Resubmit and reduce application calls per request.
ORA-41415: duplicate or conflicting KEEP or NOKEEP specifications: Cause: Duplicate KEEP or NOKEEP was specified, or both KEEP and NOKEEP were specified.; Action: Remove the duplicate or conflicting specification.
ORA-41417: invalid use of DBMS_APP_CONT_PRVT: [string] [string] [mode=string] [string] [string] [string] [string] [string]: Cause: Application continuity protocol was violated.; Action: Contact Oracle Support Services.
ORA-41418: Replay context is corrupt. Reason: [string], [string], [string], [string]: Cause: The replay context was not valid.; Action: Check your network configuration and hardware.
ORA-41420: block size cannot be zero: Cause: The block size sent by remote server was zero.; Action: Specify a valid block size as documented in the Oracle Database Administration Guide when creating data files. If displayed as an error, this represents a DBMS_FILE_TRANSFER protocol violation which should be reported to Oracle Support Services.
ORA-41421: database request ended: Cause: The application ended its database request or released the connection to the connection pool, thereby disabling replay mode.; Action: Review your results to see if your last request completed successfully.
ORA-41422: unsupported use of an incoming database link connection from a background, JOBQ slave or PQ slave: Cause: A background, JOBQ slave or PQ slave attempted to use an incoming database link connection and such usage is not supported.; Action: Contact Oracle Support Services.
ORA-41424: initial session state mismatch during replay: Cause: The initial session state at replay did not match the state at the beginning of the request.; Action: Review this request to see if the request committed, and if not whether it is safe to resubmit.
ORA-41425: replay disabled for a global transaction that uses Two-Phase Commit (2PC) managed by external Transaction Processing Monitor (TPM): Cause: The request was unable to replay because it was part of a Two-Phase Commit (2PC) transaction managed by the Transaction Processing Monitor (TPM).; Action: To use AC determine if the application can use local or one-phase transactions.
ORA-41426: could not determine session state information: Cause: Unable to obtain session state classification information.; Action: Check alert log for more details.
ORA-41427: client session environment missmatch at replay: Cause: The client session environment could not be restored to the original values.; Action: Check the setting of failover_restore on your service.
ORA-41428: initial session state could not be verified during replay: Cause: The client session environment could not be verified for a failover of the first statement in a series.; Action: Upgrade to a driver with full support for TAC.
ORA-41429: non-replayable side effect on failed connection: Cause: The application executed an operation with side effects, which disabled Application Continuity for this request.; Action: Review this request to see if the request committed, and if not whether it is safe to resubmit wth this side effect.
ORA-41430: connection test not found or is predefined: Cause: An attempt was made to enable or disable a connection test that did not exist or to delete a predefined connection test.; Action: Query the view DBA_CONNECTION_TESTS to see which connection tests exist and add the connection test, if needed. Predefined connection tests can be disabled but not deleted.
ORA-41431: Application Continuity does not support ISOLATION_LEVEL=SERIALIZABLE; failover cannot continue.: Cause: Application Continuity does not support ISOLATION_LEVEL=SERIALIZABLE.; Action: Consider using SELECT FOR UPDATE instead of serializable transactions.
ORA-41432: An open transaction is detected when attempting to start a request or at the end of a request.: Cause: It is illegal to have an open transaction when starting a new request or at the end of a request.; Action: Commit or rollback the open transaction in the previous request or in the callback for session setup or failover. It is illegal to have an open transaction at the end of a labeling or failover callback
ORA-41434: transaction replay disabled by unsupported value in call to string: Cause: The application passed to an Oracle Call Interface (OCI) function an argument value that was not supported with transactional failover.; Action: Manually recover the pending transaction. / Note: following reserved for special situations to aid diag
ORA-41435: transaction replay disabled by call to string: Cause: The application called an Oracle Call Interface (OCI) function that was not supported with transactional failover.; Action: Manually recover the pending transaction.
ORA-41437: session template could not be applied: Cause: The provided session template did not exist or was corrupt.; Action: Create a new session.
ORA-41438: cannot get service parameter (string): Cause: Unable to get the value of the service attribute at session creation; Action: Check session has been created with the service set
ORA-41440: unsupported session template usage: Cause: An application attempted to apply a template produced by a newer server on a server that does not support session templates.; Action: Do not configure a service to use session templates if some of the databases providing the service do not support templates.
ORA-41444: new DRCP session no longer supports Transaction Guard: Cause: The initial session for this connection supported Transaction Guard, but a new session created for the latest request did not. The connection was aborted, to avoid potential misuse of Transaction Guard functionality.; Action: Ensure that Transaction Guard service settings are consistently configured.
ORA-41445: not able to read reset session state value: Cause: Reset Session State parameter has not been included in the service.; Action: Include a valid value for the Reset Session State parameter.
ORA-41446: The driver is not supported for resetting state at request boundaries: Cause: The driver did not support RESET_STATE.; Action: - To use RESET_STATE, upgrade to a driver that supports RESET_STATE. - To continue without RESET_STATE capability (do not use this if applications are depending on the session state being cleared): - Use a different service that does not have RESET_STATE enabled. - Set RESET_STATE = NONE on the current service.
ORA-41448: could not verify commit status due to database mismatch (CDB root or non-CDB): Cause: The application attempted to obtain the commit status of a transaction on a database logically different from where it was first started.; Action: Check the status of this transaction manually.
ORA-41449: could not verify commit status due to invalid recovery System Change Number (SCN): Cause: The application attempted to obtain the commit status of a transaction on a database with SCN at which recovery could not be performed.; Action: Check the status of this transaction manually.
ORA-41450: could not verify commit status due to incomplete recovery information: Cause: The application attempted to obtain the commit status of a transaction on a database that was open read-only but with unspecified System Change Number (SCN). The actual SCN may be beyond the current, and recovery may yield erroneous results.; Action: Check the status of this transaction manually.
ORA-41451: Logical Transaction Identifier (LTXID) from too old a version of database: Cause: The application was passing in an old LTXID whose format the current database no longer supported.; Action: No action needed. The connection now has a current LTXID.
ORA-41452: Application Continuity is disabled due to lack of support by the client driver.: Cause: The client driver did not fully support Application Continuity.; Action: Upgrade to a driver with full support for Application Continuity.
ORA-41453: Application Continuity is disabled due to unsupported use of SESSION_STATE_CONSISTENCY by the client driver.: Cause: The client driver did not fully support the service attribute SESSION_STATE_CONSISTENCY.; Action: Set the service attribute SESSION_STATE_CONSISTENCY to DYNAMIC, or upgrade to a driver with full support of the SESSION_STATE_CONSISTENCY service attribute.
ORA-41454: Application Continuity could not be enabled because Transaction Guard was not enabled in the session.: Cause: Application Continuity was disabled by the server because Transaction Guard was disabled in the session.; Action: Upgrade to a client driver with full support for Application Continuity and ensure that all services used in the application are configured to enable Transaction Guard.
ORA-41455: Transparent Application Continuity is disabled due to lack of support by the client driver.: Cause: The client driver did not fully support Transparent Application Continuity.; Action: Use Application Continuity, or upgrade to a driver with full support for Transparent Application Continuity.
ORA-41456: Replay is disabled because the old client driver does not support Transparent Application Continuity.: Cause: The replay was disabled because the old client driver did not support Transparent Application Continuity.; Action: Upgrade your client to a version that fully supports Transparent Application Continuity.
ORA-41457: The client driver disabled replay.: Cause: The client driver encountered a call that it could not replay. Therefore, it disabled replay for that call.; Action: Take the necessary corrective action.
ORA-41458: A SELECT using AS OF could not execute at replay.: Cause: During replay of this SELECT statement, PL/SQL was encountered.; Action: Revise the SELECT statement to exclude PL/SQL in the FETCH.
ORA-41459: The request has committed and cannot reenable with FAILOVER_TYPE = TRANSACTION.: Cause: A commit completed in this request and there were subsequent calls after this commit.; Action: Use one commit per request, and also check that connections are being returned to the pool between requests. You could also use Transparent Application Continuity (FAILOVER_TYPE = AUTO).
ORA-41460: The request cannot reenable replay because of unrestorable session state with FAILOVER_TYPE = AUTO.: Cause: The session contained unrestorable session state.; Action: Consider using RESET_STATE = LEVEL1 or FAILOVER_TYPE = TRANSACTION.
ORA-41461: The request cannot reenable replay because of open cursors with FAILOVER_TYPE = AUTO.: Cause: There were open cursors that prevented Transparent Application Continuity from reenabling replay.; Action: Return cursors to the statement cache at the end of the request, so that a fetch cannot inadvertently leak to a later request. Use RESET_STATE = LEVEL1 to close cursors between the requests or use FAILOVER_TYPE = TRANSACTION.
ORA-41462: Application Continuity is not enabled.: Cause: A connection pool was not used with Application Continuity.; Action: Use a connection pool and return the connection to the pool or connect to a service that has FAILOVER_TYPE = AUTO.
ORA-41463: The application has request boundaries but Application Continuity is not enabled.: Cause: Possible causes are: - The replay driver was not used. - There was UNRESTORABLE session state in the login trigger or label. - A transaction processing monitor was in use with two-phase commit. - The client disabled replay.; Action: Use the replay driver or validate trigger checking for restorable state if using FAILOVER_TYPE = AUTO or check if the application is explicitly disabling replay or using Oracle XA Library.
ORA-41464: Application Continuity could not restore the original session.: Cause: The server process failed and the original session state could not be restored as part of the failover.; Action: Clear the session states before returning connections to the connection pool.
ORA-41465: Client driver does not support implicit request boundaries.: Cause: Application is using a client driver that doesn't fully support implicit request boundaries.; Action: Upgrade to a driver that fully supports implicit request boundaries.
ORA-41467: Application Continuity could not restore tagged session during failover.: Cause: At checkout, client received a previously tagged session. But that session experienced an outage and Application Continuity replay was attempted, but could not confirm restoration of the tagged state.; Action: One or more of the following: (1) use Transparent Application Continuity (2) register a Transparent Application Failover callback (3) do not use tags (4) resubmit failed work.
ORA-41468: execution failed due to unstable dependencies: Cause: Cursor execution could not proceed because a referenced object was modified.; Action: Retry the SQL statement when the referenced objects are not being modified.
ORA-41469: failover was rejected due to incompatible checksum version: Cause: The failover request attempted to use a higher checksum version that the old server does not support.; Action: Ensure that all Oracle RAC instances are patched to the same level.
ORA-41470: fetch tried on dead connection: Cause: A fetch was attempted on a dead connection.; Action: Check for a failed error on previous call. Discard the connection and reconnect. 41471 and 41472 both indicate that client receives unexpected replay context in function kpuxcAppContCtlRecv. The difference is that: 41471 is for standard case which is what we expect since it is raised by unsupported metadata call to OCIAttrGet and we could ignore it while 41472 is for non-standard case which means client receives unexpected replay context but the reason is not clear.
ORA-41471: transaction replay disabled by unsupported metadata call to OCIAttrGet: Cause: Application Continuity was disabled by an unsupported metadata call in the request.; Action: Manually recover the pending transaction
ORA-41472: transaction replay disabled by unsupported metadata call.: Cause: Application Continuity was disabled by an unsupported metadata call in the request.; Action: Manually recover the pending transaction
ORA-41473: Allocated call should already be processed.: Cause: This call may have missed the enqueueing process.; Action: Contact Oracle Support Services.
ORA-41474: Application Continuity is disabled due to unsupported client driver.: Cause: The client driver did not fully support Application Continuity.; Action: Upgrade to a driver with full support of Application Continuity.
ORA-41475: Application Continuity is disabled due to switching from a non-Application Continuity service.: Cause: The client session environment could not be verified for a failover of the first statement in a series, since the session was started with a service that does not support Application Continuity.; Action: To use Application Continuity with ALTER SESSION SET CONTAINER SERVICE, configure all services with Application Continuity.
ORA-41477: invalid LOB locator.: Cause: This LOB locator was generated on logical primary database during database rolling upgrade. It can't be used on a new database.; Action: Reload this LOB locator from the current database.
ORA-41479: OCI_ATTR_PING_INTERVAL was set via pooled service context obtained by OCISessionGet or OCILogon2.: Cause: After checking out session from session pool, OCI_ATTR_PING_INTERVAL was set via service context handle.; Action: Set OCI_ATTR_PING_INTERVAL via session pool handle.
ORA-41480: Request was not made between request begin and request end.: Cause: OCI Request was not made between OCIRequestBegin and OCIRequestEnd, or OCISessionGet and OCISessionRelease, or OCILogon2 and OCILogoff.; Action: put OCI requests between OCIRequestBegin and OCIRequestEnd, or OCISessionGet and OCISessionRelease, or OCILogon2 and OCILogoff.
ORA-41481: Request begin or request end call was called inappropriately.: Cause: OCIRequestBegin was called when a database request was already active or a pooled service context obtained by OCISessionGet or OCILogon2; Action: Do not call OCIRequestBegin when OCISessionGet or OCIlogon2 in session pool mode or OCIRequestBegin was already called.
ORA-41482: Null attribute address for attribute string: Cause: Null attribute address was provided for OCIAttrSet/Get.; Action: Provide valid attribute address
ORA-41483: cannot change session state consistency in client for failover type string: Cause: An attempt was made to change session state consistency, but the current failover type does not allow consistency changes.; Action: OCIAttrSet() only supports changing session state consistency for failover type AUTO. Setup a valid failover type and session state consistency combination using the DBMS_SERVICE package.
ORA-41484: cannot change session state consistency in client to value string: Cause: An invalid session state consistency value was set for the current failover type.; Action: OCIAttrSet() only supports session state consistency values OCI_SESSSTATECONS_AUTO and OCI_SESSSTATECONS_HYBRID. Setup a valid value for session state consistency.
ORA-41485: Failover is not enabled.: Cause: The connection did not connect to a service with failover enabled.; Action: Connect to a service with failover enabled.
ORA-41601: invalid property for the rule class: Cause: An invalid property was specified for the rule class.; Action: Correct the rule class properties and try again.
ORA-41602: insufficient privileges: Cause: The user does not have required privileges on the object.; Action: Obtain the required privileges and try again.
ORA-41603: invalid privilege type: Cause: An attempt was made to grant an invalid privilege on a rule class.; Action: Correct the privilege name and try again.
ORA-41604: cannot revoke a privilege that was not granted: Cause: An attempt was made to revoke a privilege that was never granted.; Action: None
ORA-41605: schema extended name not allowed: string: Cause: An attempt was made to specify a schema extended name for an event structure, a rule class, or an action call-back procedure.; Action: Specify the object name with out a schema extension.
ORA-41606: rule class name already used by an existing object: Cause: An attempt was made to create a rule class with a name that is already used by an existing object.; Action: Specify a different name for the rule class and try again.
ORA-41607: rule class creation failed with string: Cause: rule class creation failed with a recursive error.; Action: Correct the rule class specification and try again.
ORA-41608: rule class does not exist: Cause: An attempt was made to access a rule class that does not exist or is not accessible.; Action: Correct the rule class name and try again.
ORA-41609: invalid name for the rule class: Cause: An invalid name was specified for the rule class.; Action: Correct the rule class name and try again.
ORA-41610: callback procedure name already used for an existing object: Cause: An attempt was made to create a callback procedure with a name that is already used for an existing object.; Action: Choose another name for the callback procedure.
ORA-41611: rule identifier "string" not unique in the rule class: Cause: An attempt was made to use a duplicate rule identifier.; Action: Choose a unique identifier for the rule and try again.
ORA-41612: scalar values expected for action preferences: Cause: Incorrect values were specified for the action preferences.; Action: Correct the action preferences values and try again.
ORA-41613: invalid action preference for rule class: string: Cause: An attempt was made to use an invalid action preference.; Action: Correct the input and try again.
ORA-41614: missing action preference value: Cause: Values for one or more action preferences were not specified.; Action: Specify values for all relevant action preferences.
ORA-41615: too many values in action preference list: Cause: Too many entries were specified in the action preference values list. The action preference values list should not have more entries than the action preference names list.; Action: Correct the input and try again.
ORA-41616: rule class's action callback procedure may have errors: Cause: The operation failed because the action callback procedure associated with the rule class has compilation errors.; Action: Recompile the action callback procedure and try the operation again.
ORA-41617: action preference name "string" collides with an event attribute name: Cause: An attempt was made to create an action preference with the same name as an attribute in the event structure.; Action: Choose a different name for action preference and try again.
ORA-41618: specified rule does not exist: Cause: Invalid rule identifier was used to operate on a rule definition.; Action: Use a valid rule identifier.
ORA-41619: rule manager feature currently not supported: Cause: An attempt was made to use a rule manager feature that is currently not supported.; Action: No action necessary. This is an informational message only.
ORA-41620: invalid ordering property for the rule class: Cause: An attempt was made to specify an invalid ordering property for the rule class.; Action: Make sure that the attributes listed in the ordering property are all part of the rule class/event structure definition with appropriate extended names.
ORA-41621: error in ordering property :string: Cause: An attempt was made to specify an invalid ordering property for the rule class.; Action: Make sure that the attributes listed in the ordering property are all part of the rule class/event structure definition with appropriate extended names.
ORA-41622: invalid primitive event object in rule class properties : string: Cause: In the rule class properties, the name used for one or the primitive event objects was not found in the corresponding composite event structure.; Action: Correct the name of the primitive event object in the rule class properties and try again.
ORA-41623: conflicting values for autocommit and duration properties: Cause: An attempt was made to create a rule class with autocommit enabled when the duration of events is set to TRANSACTION.; Action: Turn autocommit off or choose a different duration policy.
ORA-41624: invalid duration policy for primitive object in a composite event: Cause: An attempt was made to specify a SESSION or TRANSACTION duration policy for the primitive objects.; Action: Correct the rule class properties and try again.
ORA-41625: event structure string does not exist: Cause: The object type that represents the event structure was not created in the user's schema.; Action: Create the object type with the event structure's name and try again.
ORA-41626: invalid XML element "string" in rule class properties: Cause: An invalid XML element was used in the properties specification for the rule class.; Action: Use the correct (case-sensitive) tags in the properties.
ORA-41627: event structure object type in inconsistent state: Cause: The object type specified for the event structure was in an inconsistent state.; Action: Fix the object type and try again.
ORA-41628: invalid usage of "string" attribute in "string" element: Cause: An invalid or unsupported XML attribute was used in the rule class properties.; Action: Use the correct (case-sensitive) tags in the properties.
ORA-41629: event structure for simple events cannot be reused for composite events: Cause: An attempt was made to reuse an object type (event structure) for composite events when it is already configured for simple events.; Action: Drop the attribute set associated with the object and try again.
ORA-41630: invalid value for "string" attribute in the rule class properties: Cause: An invalid value was specified for an attribute in the rule class properties.; Action: Correct the value and try again.
ORA-41631: invalid text node or child element for "string" element in properties: Cause: An attempt was made to specify a child element or a text node in invalid position in the rule class properties specification.; Action: Correct the rule class properties and try again.
ORA-41632: invalid value for the "string" attribute: Cause: An attempt was made to assign an invalid value for an attribute in the rule class properties.; Action: See the documentation.
ORA-41633: specified rule class configuration not supported: "string": Cause: An attempt was made to use an unsupported configuration for the rule class.; Action: Remove the specified tag in the properties and try again.
ORA-41634: invalid duration specification in rule properties: "string": Cause: Invalid value was specified for the duration attribute in the rule class properties.; Action: Correct the value and try again.
ORA-41635: invalid unit of time used in duration specification: Cause: An attempt was made to use an invalid unit of time for the rule class's duration specification. Valid units are : minutes, hours, and days.; Action: Correct the duration specification and try again.
ORA-41636: invalid duration specification at the primitive event level: Cause: An attempt was made to specify a duration policy for the primitive events when the composite event was configured with TRANSACTION or SESSION duration policy.; Action: Correct the rule class properties and try again.
ORA-41637: missing primitive event name: Cause: The name attribute of the object element in the rule class properties was not specified. This is a required value.; Action: Specify the name of the primitive event and try again.
ORA-41638: invalid attribute for "string" element in rule condition: Cause: An attempt was made to specify an invalid attribute for an XML element in the rule condition.; Action: Correct the rule condition and try again.
ORA-41639: invalid child node in "string" element: Cause: An attempt was made to specify an invalid child element or text node for an XML element in the rule condition.; Action: Correct the rule condition and try again.
ORA-41640: invalid element "string" in the rule condition: Cause: An attempt was made to use an invalid element or a valid element in invalid position in the rule condition.; Action: Correct the rule condition and try again.
ORA-41641: invalid or empty rule condition: Cause: An attempt was made to specify an invalid or empty rule condition.; Action: Correct the input and try again.
ORA-41642: Missing "string" element in the rule condition: Cause: The rule condition was specified without a required element.; Action: Correct the rule condition and try again.
ORA-41643: invalid attribute for the "string" element in the rule condition: Cause: An attempt was made to specify an invalid attribute for an element in the rule condition.; Action: Correct the rule condition and try again.
ORA-41644: invalid use of "string" attribute in rule condition: Cause: An attempt was made to specify an invalid attribute for an element in the rule condition.; Action: Correct the rule condition and try again.
ORA-41645: duplicate tag "string" in rule condition: Cause: An attempt was made to specify the same XML tag in more than one positions within a single rule condition.; Action: Remove the duplicate reference to the tag and try again.
ORA-41646: missing "string" attribute for "string" element in the rule condition: Cause: One of the required attributes was not specified in the rule condition.; Action: Correct the rule condition and try again.
ORA-41647: negation not allowed in rule conditions with "any" semantics: Cause: An attempt was made to specify a "not" element within an "any" element in the rule condition.; Action: Correct the rule condition and try again.
ORA-41648: invalid sequence of child elements in "string" element: Cause: An attempt was made to specify an invalid sequence of elements within a parent element.; Action: Correct the rule condition and try again.
ORA-41649: invalid rule condition for a rule class involving composite events: Cause: An attempt was made to add an invalid rule condition to a rule set defined for composite events.; Action: Correct the input and try again.
ORA-41650: invalid composite event structure: Cause: A composite event structure may only have attributes that are either table aliases or of an object type that is defined in the owner's schema.; Action: Ensure that the event structure has no scalar attributes and all the embedded types in it are defined in the owner's schema.
ORA-41651: Event structure object type has one or more dependent objects: Cause: An attempt was made to configure an object type that has one or more dependents as a event structure. The object type cannot be modified due to the dependent objects.; Action: Create a new object type for the event structure and try again.
ORA-41652: invalid value for the equal attribute in the rule condition: Cause: An invalid value is assigned to the equal attribute in the rule condition.; Action: Correct the input and try again.
ORA-41653: inconsistent value for the "count" attribute of the "any" element: Cause: The value specified for the "count" attribute of the "any" element is greater than or equal to the the number of primitive events appearing in the rule condition.; Action: Specify a smaller value for the "any" element's "count" attribute.
ORA-41654: insufficient number of primitive events for the use of "sequence": Cause: An attempt was made to use "sequence" attribute when there is an insufficient number of primitive events in the rule conditions.; Action: Remove the sequence specification.
ORA-41655: rule condition construct not supported: string: Cause: An attempt was made to use a rule condition construct that is not supported in the current release.; Action: Modify the rule condition.
ORA-41656: insufficient number of child elements in "string" element.: Cause: An attempt was made to use fewer than two elements within an "and" or "notany" element.; Action: Specify at least two elements within the parent element.
ORA-41657: rule class internal objects cannot be dropped: Cause: An attempt was made to drop an internal object that is required for a rule class.; Action: Drop the rule class associated with this object.
ORA-41658: invalid value for the "count" attribute in the "any" element: Cause: An invalid value is assigned to the count attribute in the rule condition. The values should be a positive integer that is smaller than the number of object elements within the "any" element.; Action: Correct the input and try again.
ORA-41659: invalid primitive event "string" for the rule class: Cause: An attempt was made to use an invalid primitive event in a rule condition.; Action: Correct the input and try again.
ORA-41660: ordering property for the rule class is too long: Cause: An attempt was made to configure the rule class with an ordering property that is longer than 240 characters.; Action: Correct the input and try again.
ORA-41661: the system generated rule class package has errors: Cause: An attempt was made to use a rule class configuration that was not supported.; Action: File a bug.
ORA-41662: number of primitive events in the composite event exceeds maximum limit: Cause: An attempt was made to create a composite event structure with more than 32 primitive events.; Action: Use a composite event that consists of fewer primitive events.
ORA-41663: invalid use of "equal" or "sequence" attribute with a single event: Cause: An attempt was made to use "equal" or "sequence" attribute when the "count". attribute in a rule condition with "any" semantics is set to 1.; Action: Remove the "equal" and "sequence" specifications.
ORA-41664: invalid consumption policy for the primitive event: Cause: An attempt was made to use EXCLUSIVE consumption policy for a primitive event when the composite event is configured for RULE consumption policy.; Action: Correct the rule class properties and try again.
ORA-41665: conflicting values for duration, consumption, and autocommit policies: Cause: An attempt was made to use an EXCLUSIVE consumption policy with no autocommit and a duration other than TRANSACTION or SESSION.; Action: Modify the rule class properties and try again. Autocommit should be set to YES when the consumption policy is EXCLUSIVE.
ORA-41666: XML schema validation failed when validating against string: Cause: The user input has undefined element or attribute according to the provided XML schema definition.; Action: Correct the user inputs and try again.
ORA-41667: rule class results view name already used for an existing object: Cause: An attempt was made to use a duplicate name for the rule class results view.; Action: Use a different name for the rule class results view.
ORA-41668: invalid operation for the rule class: Cause: An attempt was made to use an invalid operation for the rule class.; Action: No action necessary. This is an informational message only.
ORA-41669: invalid list of primitive event identifiers: Cause: An attempt was made to pass an empty list of primitive event identifiers to the CONSUME_PRIM_EVENTS API.; Action: Correct the input and try again.
ORA-41670: duplicate or invalid event name in equal specification: Cause: An attempt was made to specify a duplicate or invalid primitive event for the rule class's equal property.; Action: Correct the input and try again.
ORA-41671: duplicate table names in the event structure with table aliases: Cause: The table used for an event structure has the same name as another table or a primitive event type in the event structure.; Action: Use an event structure with distinct table names for table aliases.
ORA-41672: invalid rowid passed in for "string" table: Cause: An attempt was made to pass a NULL or invalid rowid for a table in the event structure.; Action: Correct the input and try again.
ORA-41673: sequence attribute not allowed in rule conditions using table aliases: Cause: An attempt was made to use sequence attribute in a rule condition that is defined using table aliases. Sequence usage is not permitted for the lack of timestamp attribute.; Action: Correct the input and try again.
ORA-41674: dmlevents policy allowed only for event structures with table aliases: Cause: An attempt was made to use the dmlevents policy for an event structure with no table alias constructs.; Action: Correct the rule class properties and try again.
ORA-41675: schema for data tables does not match that of the rule class: Cause: An attempt was made to use the dmlevents policy for a rule class that refers to table residing in different schema. To use the dmlevents policy, the table associated with table aliases in the event structure and the rule class should exist in the same schema.; Action: Remove dmlevents specification from rule class properties.
ORA-41676: invalid use of dmlevents policy for primitive event: Cause: An attempt was made to use the dmlevents policy for a primitive event defined with more than one table alias attribute.; Action: Remove the dmlevents specification from the rule class properties.
ORA-41677: DML event trigger creation failed with string: Cause: Triggers could not be created on the data table to track DML events.; Action: Remove the dmlevents specification from the rule class properties.
ORA-41678: conflicting values for the autocommit and dmlevents policies: Cause: An attempt was made to use dmlevents policy in combination with autocommit set to YES. This combination is not allowed.; Action: Set autocommit to NO and try again.
ORA-41679: dmlevents specification only allowed with table alias attributes: Cause: An attempt was made to use the dmlevents policy for an event structure not containing any table alias attributes.; Action: Remove the dmlevents specification from the rule class properties.
ORA-41680: Rules Manager background process string does not exist: Cause: An attempt was made to use a Scheduler process that does not exist.; Action: Execute EXFSYS.RLM$CREATE_SCHEDULER_JOBS procedure as a privileged user.
ORA-41681: clean up of expired events failed: Cause: The background process that cleans up the expired events failed for a rule class.; Action: Invoke EXFSYS.DBMS_RLMGR_UTL.CLEANUP_EVENTS API for the exact nature of the problem.
ORA-41682: invalid rule class package: Cause: An attempt was made to use a rule class package with invalid signature or permissions.; Action: Drop the rule class and recreate it.
ORA-41683: unable to lock a rule in the rule class: Cause: A rule matching the current event is locked by another session.; Action: Reissue the command after committing the other sessions.
ORA-41684: invalid value for the RLM$ENABLED column: Cause: An attempt was made to insert or update a value other than 'Y' or 'N' into the RLM$ENABLED column of a rule class table.; Action: Retry the DML statement with a value of 'Y' or 'N' for the RLM$ENABLED column.
ORA-41685: invalid window specification for the collection element: Cause: An invalid attribute value was specified for the "windowlen" or the "windowsize" attribute. The value specified for the "windowlen" attribute should be a number indicating the number of days or a fraction of a day. The value specified for the "windowsize" attribute should be an integer which indicates number of items in the collection. The maximum value allowed for the window specification is 64000.; Action: Correct the input and try again.
ORA-41686: use of "collection" invalid for the primitive event: Cause: An attempt was made to define a rule condition with "collection" element when the corresponding event was not configured for collections of events.; Action: Correct the rule condition and try again.
ORA-41687: attribute "string" not allowed in the "groupby" specification: Cause: The attributes listed in the "groupby" specification in a rule condition were not a subset of the attributes specified in the rule class properties.; Action: Correct the "groupby" specification for the rule condition and try again.
ORA-41688: invalid value for the "groupby" attribute: Cause: An invalid value was specified for the "groupby" attribute.; Action: Correct the input and try again.
ORA-41689: invalid collection specification in the rule condition: Cause: An attempt was made to insert a rule condition with invalid collection element specification.; Action: Correct the input and try again.
ORA-41690: maximum number of grouping expressions for a rule class exceeded: Cause: An attempt was made to specify more than 32 expressions for the "groupby" clause in rule class properties.; Action: Use fewer than 32 expressions for the "groupby" clause.
ORA-41691: invalid aggregate specification: string: Cause: The aggregate operation specified in the rule condition was invalid.; Action: Correct the input and try again.
ORA-41692: unsupported aggregate operator in the having/compute clause: string: Cause: An attempt was made to use an unsupported aggregate operator in the having or the compute clause in the rule condition.; Action: Correct the input and try again.
ORA-41693: invalid attribute or data type for an aggregate operator: string: Cause: An attempt was made to apply an aggregate operator on an invalid attribute or an attribute with invalid or unsupported data type in the aggregate operator. Only NUMBER and DATE attributes are allowed in the aggregate operators.; Action: Correct the input and try again.
ORA-41694: invalid equal specification around: string: Cause: An attempt was made to specify an invalid equal clause for a rule condition or the rule class properties.; Action: Correct the input and try again.
ORA-41695: equal specification should have a minimum of two elements: Cause: An attempt was made to specify fewer than two elements in the equal clause for a rule condition or the rule class properties.; Action: Correct the input and try again.
ORA-41696: invalid operator in the having clause: string: Cause: An attempt was made to use an invalid relational operator in the having clause of the rule condition.; Action: Correct the input and try again.
ORA-41697: attribute prefix missing in aggregate specification: string: Cause: An attempt was made to specify an aggregate predicate across multiple primitive event types with no attribute prefix.; Action: Correct the input and try again.
ORA-41698: invalid use of "string" attribute in aggregate predicate: Cause: An attempt was made to use an attribute where a literal is expected in the aggregate predicate in the rule condition.; Action: Correct the input and try again.
ORA-41699: maximum number of aggregate operations per rule condition exceeded: Cause: An attempt was made to specify more than 5 aggregate operations in a rule condition.; Action: Correct the input an try again.
ORA-41700: a conditions table already exists for the event structure: Cause: A table storing the primitive rule conditions was already assigned to the event structure.; Action: No action necessary. This is an informational message only.
ORA-41701: conditions table with a rule class association cannot be truncated or dropped: Cause: An attempt was made to truncate or drop a conditions table when one or more rule classes are associated to it through the event structure.; Action: Drop the rule class before truncating or dropping the conditions table.
ORA-41702: invalid conditions table: Cause: An attempt was made to use an invalid conditions table.; Action: Correct the input and try again.
ORA-41703: invalid child node in "object" element with "ref" attribute: Cause: An attempt was made to use both a condition and a "ref" attribute in the "object" element.; Action: Remove the "ref" attribute.
ORA-41704: invalid condition reference: "string": Cause: An attempt was made to use a reference to a nonexistent conditions table or a condition.; Action: Ensure that the conditions table exists for the primitive event and the value specified for the "ref" attribute of the "object" element is valid.
ORA-41705: conditions table cannot be dropped with DROP TABLE command: Cause: An attempt was made to drop a conditions table with a DROP TABLE command.; Action: Use DBMS_RLMGR.DROP_CONDITIONS_TABLE instead.
ORA-41706: a condition referenced in rule conditions may not be deleted: Cause: An attempt was made to delete a condition when one or more rule conditions refer to it.; Action: Delete the rules before deleting the conditions.
ORA-41707: unsupported construct with collection events: "string": Cause: An attempt was made to define a collection rule condition with unsupported constructs.; Action: Correct the input and try again.
ORA-41708: the identifier for the shared condition may not be modified: Cause: An attempt was made to update the identifier of a row stored in the conditions table.; Action: Insert a row with the new identifier instead.
ORA-41710: invalid use of aggregate operator for a noncollection event: Cause: An attempt was made to specify an aggregate operator on an event that is not identified as collection.; Action: Correct the input and try again.
ORA-41711: invalid attribute in the rule condition's having clause: Cause: An invalid attribute is used in the specification for the having clause of the rule condition.; Action: Correct the input and try again.
ORA-41712: missing groupby specification for the collection "string": Cause: An attempt was made to use a collection element with no groupby specification in the rule condition.; Action: Correct the input and try again.
ORA-41713: invalid use of "windowlen" and "windowsize" attributes: Cause: An attempt was made to use the windowlen and windowsize attributes within the same collection element.; Action: Correct the input and try again.
ORA-41714: invalid use of window specification with SESSION/TRANSACTION duration: Cause: An attempt was made to use the windowlen or windowsize attributes when the events are configured for SESSION or TRANSACTION duration.; Action: Remove the window specification and try again.
ORA-41721: invalid use of DMLEVENTS and CNFEVENTS in rule class properties: Cause: An attempt was made to specify both the DMLEVENTS and CNFEVENTS for the same rule class.; Action: Remove either the DMLEVENTS or the CNFEVENTS specification.
ORA-41722: insufficient privileges for database change notification: Cause: An attempt was made to use CNFEVENTS property with insufficient privileges.; Action: Grant CHANGE NOTIFICATION privilege and EXECUTE privilege on DBMS_CHANGE_NOTIFICATION to the user and try again.
ORA-41800: too many notifications with the notification ID "string": Cause: Multiple pluggable databases (PDBs) shared the same notification ID.; Action: Set a secondary ID attribute in NOTIFICATIONID for the procedure.
ORA-41801: invalid PDB "string" for procedure string: Cause: The specified pluggable database (PDB) name was not found in the multitenant container database (CDB).; Action: Set the correct PDB name for the procedure.
ORA-41802: invalid JSON format for NOTIFICATION: Cause: An incorrect JavaScript Object Notation (JSON) string was set as the NOTIFICATION parameter.; Action: Check and correct the JSON format.
ORA-41803: value of NOTIFICATION parameter string is empty: Cause: The value of the required non-null parameter was empty.; Action: Check the value of the specified parameter to guarantee not NULL.
ORA-41804: NOTIFICATION parameter string not set: Cause: The specified parameter was not set.; Action: Set the required parameter with a non-null value.
ORA-41805: NOTIFICATION or NOTIFICATIONID is NULL: Cause: The specified parameter was not set.; Action: Set the required NOTIFICATION or NOTIFICATIONID for DBMS_NOTIFICATIONS.
ORA-41806: exceeded the maximum number of secondary ID parameters for NOTIFICATIONID: Cause: Too many specified secondary ID parameters were set.; Action: Reset the NOTIFICATIONID parameter and set fewer secondary ID parameters.
ORA-41807: primary ID or secondary ID parameter not set for NOTIFICATIONID: Cause: A primary or secondary ID parameter was not set.; Action: Set a valid primary or secondary ID based on DB_NOTIFICATIONS view.
ORA-41808: insufficient privileges for the DBMS_NOTIFICATIONS action: Cause: The user did not have sufficient privileges to execute the procedure.; Action: Grant the DBA privilege or NOTIFICATIONS_ADMIN privilege and try again.
ORA-41931: underlying object number does not exists: Cause: The underlying graph object defined in the graph does not exist.; Action: Execute create or replace on the graph.
ORA-42000: invalid online redefinition column mapping for table "string"."string": Cause: An attempt was made to change the logical structure of a materialized view log, queue table, or a partition by specifying a non-NULL column mapping during online redefinition.; Action: Pass a NULL column mapping parameter.
ORA-42002: partition "string" of table "string"."string" not being redefined: Cause: An attempt was made to redefine a partition which is not involved in this redefinition.; Action: Pass a valid partition name.
ORA-42003: partition must be specified for this redefinition: Cause: A partition was involved in this redefinition but was not specified.; Action: Specify the partition involved in this redefinition.
ORA-42004: redefinition not instantiated: Cause: An attempt was made to complete an instantiation-deferred redefinition without invoking dbms_redefinition.sync_interim_table.; Action: Invoke dbms_redefinition.sync_interm_table to instantiate this redefinition.
ORA-42005: invalid type of redefinition method: Cause: An unknown redefinition method was used.; Action: Use one of the supported redefinition methods: o dbms_redefinition.cons_use_pk o dbms_redefinition.cons_use_rowid
ORA-42006: dependent object registration not supported during a partition redefinition: Cause: An attempt was made to register dependent objects when redefining a partition.; Action: Do not invoke dbms_redefinition.register_dependent_object during a partition redefinition.
ORA-42007: dependent object unregistration not supported during a partition redefinition: Cause: An attempt was made to unregister dependent objects when redefining a partition.; Action: Do not invoke dbms_redefinition.unregister_dependent_object during a partition redefinition.
ORA-42008: error occurred while instantiating the redefinition: Cause: An error occurred while instantiating the online redefinition which requires aborting the redefinition.; Action: Correct the error, abort, and restart the online redefinition.
ORA-42009: error occurred while synchronizing the redefinition: Cause: An error occurred while synchronizing the online redefinition.; Action: Correct the error and continue the online redefinition.
ORA-42010: error occurred while synchronizing the redefinition: Cause: An error occurred while synchronizing the online redefinition which requires aborting the redefinition.; Action: Correct the error, abort, and restart the online redefinition.
ORA-42011: error occurred while completing the redefinition: Cause: An error occurred while completing the online redefinition.; Action: Correct the error and continue the online redefinition.
ORA-42012: error occurred while completing the redefinition: Cause: An error occurred while completing the online redefinition which requires aborting the redefinition.; Action: Correct the error, abort, and restart the online redefinition.
ORA-42013: interim table of an AQ IOT table should be an IOT table: Cause: An attempt was made to create a table that is not an index-organized table (IOT) as the interim table of an AQ IOT table (history, time management, or dequeue).; Action: Ensure that the interim table is created as an IOT table.
ORA-42014: online redefinition unable to lock AQ objects: Cause: An online redefinition of an AQ table was unable to lock all related AQ objects.; Action: Abort and retry the redefinition.
ORA-42015: online redefinition unable to log changes made to AQ tables: Cause: An online redefinition of an AQ table was unable to log changes made to AQ tables during the redefinition.; Action: Abort and retry the redefinition.
ORA-42016: shape of interim table does not match specified column mapping: Cause: The number of columns, or the type or the length semantics of a column, in the interim table did not match the specified column mapping.; Action: Ensure that the interim table matches the column mapping by either modifying the column mapping string or altering the interim table's column definition(s).
ORA-42017: interim table of an AQ table should not be an AQ table: Cause: An attempt was made to create an AQ table as an interim table of an online redefined AQ table.; Action: Ensure that the interim table is not created as an AQ table.
ORA-42018: partition cannot be redefined online because of index organization incompatibility: Cause: interim table is incompatible with partition being redefined because one or more of the following apply: - one is index-organized and the other is not - one has IOT overflow segment and the other does not - one has IOT mapping table and the other does not; Action: Ensure that the interim table is compatible with the partition being redefined.
ORA-42019: partition cannot be redefined online because of incompatible partitioning of interim table: Cause: both original and interim tables are partitioned, or original table is composite-partitioned but interim table is non-partitioned.; Action: Ensure that the interim table has compatible partitioning with the original table. For example, if the original table is partitioned, the interim table should be non-partitioned. If the original table is composite-partitioned, the interim table should be partitioned.
ORA-42020: partition cannot be redefined online because of unsupported type of interim table: Cause: An unsupported type of interim table was provided during the partition redefinition. Currently the following types of interim tables are not supported: - a nested table or has nested-table columns - an external table - part of cluster - contains LOB shared segments; Action: Do not use unsupported types of interim tables.
ORA-42021: partition cannot be redefined online because of incompatible row dependencies: Cause: original/interim table was created with row dependency and interim/original table was not.; Action: Ensure that both tables are created with same row dependency properties.
ORA-42022: partition cannot be redefined online because of presence of nested columns: Cause: An attempt was made to online redefine a partition with nested table columns.; Action: Do not attempt to online redefine a partition with nested table columns.
ORA-42023: compatibility of AQ table must be release 8.1.x or later: Cause: An attempt was made to perform online redefinition on an AQ table that was created with compatibility prior to release 8.1.x.; Action: Ensure that the AQ table is created with the COMPATIBLE parameter set to release 8.1.x or later before attempting online redefinition.
ORA-42024: interim table of an AQ table can not be a partitioned table: Cause: An attempt was made to use a partitioned table as an interim table.; Action: Ensure that the interim table is not a partitioned table.
ORA-42025: redefinition of CONS_USE_ROWID method cannot be used to redefine an AQ IOT table: Cause: An attempt was made to use method of DBMS_REDEFINITION.CONS_USE_ROWID to redefine an AQ IOT table.; Action: Ensure that method of DBMS_REDEFINITION.CONS_USE_PK is used to redefine an AQ IOT table.
ORA-42026: duplicated rows detected while instantiating the redefinition: Cause: Duplicated rows are detected during instantiation of the redefinition.; Action: Abort the redefinition, turn off the optimistic ascending SCN optimization, and restart the redefinition.
ORA-42027: cannot redefine an object online that is not a table: Cause: An attempt was made to redefine an object online that is not a table.; Action: Ensure that the object being redefined online is a table.
ORA-42028: materialized view log "string"."string" does not exist: Cause: An attempt was made to register a nonexistent materialized view log as a dependent object.; Action: Invoke DBMS_REDEFINITION.REGISTER_DEPENDENT_OBJECT on a valid materialized view log.
ORA-42029: cannot online redefine table "string"."string" at this time: Cause: An attempt was made to redefine a table which is incompatible with another ongoing redefinition.; Action: Do not perform the redefinition operation on this table or wait until the incompatible ongoing redefinition has completed.
ORA-42030: cannot online redefine table "string"."string" with commit SCN-based MV log: Cause: An attempt was made to redefine a table which had a commit SCN-based materialzed view log defined on it.; Action: Do not attempt to online redefine a table that has a commit SCN-based materialzed view log defined on it.
ORA-42031: interim table cannot have a commit SCN-based MV log defined on it: Cause: An attempt was made to use an interim table which had a commit SCN-based materialzed view log defined on it.; Action: Ensure that the interim table does not have a commit SCN-based materialzed view log defined on it.
ORA-42032: cannot online redefine table "string"."string" with Flashback Data Archive enabled: Cause: An attempt was made to redefine a table which had Flashback Data Archive enabled.; Action: Do not attempt to online redefine a table that has Flashback Data Archive enabled.
ORA-42033: interim table "string"."string" cannot have Flashback Data Archive enabled: Cause: An attempt was made to redefine a table with an interim table which had Flashback Data Archive enabled.; Action: Do not attempt to online redefine a table with an interim table which has Flashback Data Archive enabled.
ORA-42034: cannot online redefine table "string"."string" which is a CDC table: Cause: An attempt was made to redefine a table which is a CDC table.; Action: Do not attempt to online redefine a table that is a CDC table.
ORA-42035: cannot online redefine IOT table "string"."string" with CONS_USE_ROWID: Cause: An attempt was made to redefine an IOT table with CONS_USE_ROWID.; Action: Do not attempt to online redefine an IOT table with CONS_USE_ROWID.
ORA-42036: cannot online redefine temporary table "string"."string": Cause: An attempt was made to redefine a temporary table.; Action: Do not attempt to online redefine a temporary table.
ORA-42037: cannot online redefine table "string"."string" with IOT overflow segment: Cause: An attempt was made to redefine a table with IOT overflow segment.; Action: Do not attempt to online redefine a table with IOT overflow segment.
ORA-42038: cannot online redefine table "string"."string" with a CDC log defined on it: Cause: An attempt was made to redefine a table with a CDC log defined on it.; Action: Do not attempt to online redefine a table with a CDC log defined on it.
ORA-42039: cannot online redefine table "string"."string" with FGA enabled: Cause: An attempt was made to redefine a table with Fine Grained Auditing (FGA) or Row Level Security (RLS) enabled.; Action: Do not attempt to online redefine a table with Fine Grained Auditing (FGA) or Row Level Security (RLS) enabled.
ORA-42040: cannot online redefine table "string"."string" with column of binary XML type: Cause: An attempt was made to redefine a table with a column of binary XML type.; Action: Do not attempt to online redefine a table with a column of binary XML type.
ORA-42041: cannot online redefine table "string"."string" with nested table columns: Cause: An attempt was made to redefine a table with nested table columns.; Action: Do not attempt to online redefine a table with nested table columns.
ORA-42042: time out in acquiring DML lock during online redefinition: Cause: During FINISH_REDEF_TABLE procedure, the elapsed time waiting to acquire a table or partition DML lock on the original table exceeds the timeout the user specified.; Action: Rerun FINISH_REDEF_TABLE procedure to continue the process.
ORA-42043: CONS_VPD_AUTO is only applicable to null column mapping: Cause: An attempt was made to specify CONS_VPD_AUTO for non-null column mapping other than null column mapping. CONS_VPD_AUTO can only be specified for null column mapping.; Action: Set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
ORA-42044: cannot redefine table with non-null VPD policy predicate against the table owner or redefinition invoker: Cause: Virtual Private Database (VPD) policies with non-null predicate against the table owner or redefinition invoker existed on the original table.; Action: Drop the VPD policies with non-null predicate against the table owner or redefinition invoker. Restart online redefinition.
ORA-42045: COPY_VPD_OPT cannot be set to CONS_VPD_NONE with VPD policies on table "string"."string".: Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_NONE. COPY_VPD_OPT cannot be set to CONS_VPD_NONE with Virtual Private Database (VPD) policies on the original table.; Action: Set COPY_VPD_OPT to CONS_VPD_AUTO or CONS_VPD_MANUAL.
ORA-42046: COPY_VPD_OPT cannot be set to string with VPD policies on interim table "string"."string".: Cause: An attempt was made to set the COPY_VPD_OPT value to either CONS_VPD_NONE or CONS_VPD_AUTO. Cannot set the COPY_VPD_OPT value to CONS_VPD_NONE or CONS_VPD_AUTO with Virtual Private Database (VPD) policies on the interim table.; Action: Set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
ORA-42047: The specified value for COPY_VPD_OPT is invalid.: Cause: An unknown COPY_VPD_OPT value was used.; Action: Use one of the supported COPY_VPD_OPT values: o DBMS_REDEFINITION.CONS_VPD_NONE o DBMS_REDEFINITION.CONS_VPD_AUTO o DBMS_REDEFINITION.CONS_VPD_MANUAL
ORA-42048: Automatic copying of VPD policies with application context is not supported in online redefinition.: Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_AUTO for Virtual Private Database (VPD) policies with application context. Automatic copying of VPD policies with application context is not supported in online redefinition.; Action: Drop VPD policies with application context or set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
ORA-42049: cannot online redefine multiple tables and multiple partitions: Cause: An online redefinition procedure was passed multiple original tables and multiple partitions to redefine.; Action: Do not attempt to online redefine multiple tables at the same time as multiple partitions.
ORA-42050: COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL when redefining a partition.: Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_MANUAL. COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL when redefining a partition.; Action: Set COPY_VPD_OPT to CONS_VPD_NONE or CONS_VPD_AUTO.
ORA-42051: duplicate partition names in partition name list: Cause: An online redefinition procedure was passed a partition name list containing duplicates.; Action: Ensure that all names in the partition name list are unique.
ORA-42052: interim table cannot have materialized view or zonemap defined on it: Cause: An attempt was made to redefine a table with an interim table on which a materialized view or zonemap was defined.; Action: Remove all materialized views and zonemaps defined on the interim table and retry online redefinition, or do not attempt online redefinition.
ORA-42053: cannot online redefine table "string"."string" with OLS/XDS enabled: Cause: An attempt was made to redefine a table with Oracle Label Security (OLS) or Extensible Data Security (XDS) enabled.; Action: Do not attempt to online redefine a table with Oracle Label Security (OLS) or Extensible Data Security (XDS) enabled.
ORA-42054: cannot online redefine table "string"."string" with UXI XML index: Cause: An attempt was made to redefine a table with XML indexes having an Unstructured XMLIndex (UXI) component.; Action: Do not attempt to online redefine a table with XML indexes having an Unstructured XMLIndex (UXI) component.
ORA-42056: interim table cannot be a system-partitioned table: Cause: An attempt was made to redefine a table with an interim table that was a system-partitioned table.; Action: Use an interim table whose partition type is supported.
ORA-42057: cannot use lock free finish redef for current redefinition: Cause: An attempt was made to enable lock free finish redef for current redefinition, but lock free was not feasible.; Action: Refer to the documentation for restrictions.
ORA-42058: unsupported UPDATE statement: Cause: The UPDATE statement passed to DBMS_REDEFINITION.EXECUTE_UPDATE was not supported.; Action: Refer to the documentation for restrictions and supported types.
ORA-42059: cannot update a table with a DML trigger on UPDATE: Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with a trigger on UPDATE, which is not supported.; Action: Drop the DML trigger.
ORA-42060: cannot update a table with a nested table column: Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with a nested table column, which is not supported.; Action: Refer to the documentation for restrictions.
ORA-42061: cannot update a typed table or a table with an ADT column: Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a typed table or a table with an ADT column, which is not supported.; Action: Refer to the documentation for restrictions.
ORA-42062: cannot update a table with a partition extended name: Cause: An attempt was made to pass an UPDATE statement with a partition extended name to the DBMS_REDEFINITION.EXECUTE_UPDATE method, which is not supported.; Action: Refer to the documentation for restrictions.
ORA-42064: invalid UPDATE statement string: Cause: An attempt was made to pass an invalid UPDATE statement to the DBMS_REDEFINITION.EXECUTE_UPDATE method.; Action: Pass a valid UPDATE statement to the DBMS_REDEFINITION.EXECUTE_UPDATE method.
ORA-42065: REDEF_TABLE() does not support redefining AQ table: Cause: An attempt was made to redefine an Advanced Queueing (AQ) table with the REDEF_TABLE() procedure.; Action: Do not attempt to redefine an AQ table using REDEF_TABLE().
ORA-42066: illegal redefinition for a clustered table: Cause: An attempt was made to redefine a clustered table to modify the tablespace or compression type with the REDEF_TABLE() procedure.; Action: Do not attempt to specify a new tablespace or compression type.
ORA-42067: invalid column mapping with invisible columns on original or interim table: Cause: There was an invalid column mapping with invisible columns on the original or interim table.; Action: Invisible columns in the column mapping string must be invisible on both the original and interim table.
ORA-42068: rollback unsupported with COPY_VPD_OPT option: Cause: ENABLE_ROLLBACK and COPY_VPD_OPT were both set to TRUE.; Action: Either unset ENABLE_ROLLBACK or COPY_VPD_OPT.
ORA-42069: rollback unsupported: Cause: Tables in the redefinition are either an object, advanced queue or index-organized table.; Action: Currently ROLLBACK is unsupported on such tables.
ORA-42070: wrong usage of DBMS_REDEFINITION.ROLLBACK: Cause: ENABLE_ROLLBACK was not set to TRUE during START_REDEF_TABLE.; Action: Restart START_REDEF_TABLE with ENABLE_ROLLBACK set to TRUE and then use ROLLBACK.
ORA-42071: rollback unsupported with NO-DML lock option: Cause: ENABLE_ROLLBACK was set to TRUE along with DML_LOCK_TIMEOUT set to -1.; Action: Either unset ENABLE_ROLLBACK or DML_LOCK_TIMEOUT.
ORA-42072: REDEF_TABLE() does not support a table with LONG column.: Cause: An attempt was made to redefine a table that has a LONG column with the REDEF_TABLE() procedure.; Action: Do not attempt to redefine a table with LONG column using REDEF_TABLE().
ORA-42073: cannot online redefine external table or fixed table: Cause: An attempt was made to redefine an external table or a fixed table.; Action: Do not attempt to online redefine an external table or a fixed table.
ORA-42074: Cannot update a table with VPD policy: Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with Virtual Private Database (VPD) policy.; Action: Refer to the documentation for restrictions.
ORA-42075: wrong usage of parameter, DISABLE_ROLLBACK in FINISH_REDEF_TABLE: Cause: ENABLE_ROLLBACK was not set to TRUE during START_REDEF_TABLE.; Action: Rerun FINISH_REDEF_TABLE with DISABLE_ROLLBACK set to FALSE.
ORA-42076: DBMS_REDEFINITION does not support a table on single table hash clusters.: Cause: An attempt was made to use DBMS_REDEFINITION on a table on single table hash clusters.; Action: Do not attempt to use DBMS_REDEFINITION to operate on a table that is on single table hash clusters.
ORA-42077: unsupported column type found in VPD protected object: Cause: An attempt was made with Oracle Virtual Private Database (VPD) policy to enforce column security on a column with unsupported operator type.; Action: Refer to the documentation for restrictions.
ORA-42078: DBMS_REDEFINITION does not support a clustered table without cluster index or with virtual cluster index: Cause: An attempt was made to use the DBMS_REDEFINITION package on a clustered table without a cluster index or with a virtual cluster index.; Action: Create a regular cluster index and rerun the DBMS_REDEFINITION procedure.
ORA-42079: wrong usage of DBMS_REDEFINITION.FINISH_REDEF_TABLE: Cause: Rollback was initiated as part of the previous call to FINISH_REDEF_TABLE.; Action: Use ROLLBACK or ABORT_ROLLBACK to end redefinition.
ORA-42080: wrong usage of DBMS_REDEFINITION.ABORT_ROLLBACK: Cause: ABORT_ROLLBACK was called without starting the rollback operation.; Action: Use ABORT_REDEF_TABLE instead of ABORT_ROLLBACK.
ORA-42081: wrong usage of DBMS_REDEFINITION.ABORT_REDEF_TABLE: Cause: ABORT_REDEF_TABLE was called when ROLLBACK was active.; Action: Use ABORT_ROLLBACK instead of ABORT_REDEF_TABLE.
ORA-42082: cannot update a table with a hidden column: Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with a hidden column, which is not supported.; Action: Refer to the documentation for restrictions.
ORA-42083: cannot online redefine table "string"."string" with staging log: Cause: An attempt was made to redefine a table that had a staging log.; Action: Do not attempt to online redefine a table that has a staging log.
ORA-42084: cannot online redefine table that has inconsistent sharing with interim table: Cause: An attempt was made to redefine a table that had inconsistent sharing with an interim table.; Action: Do not attempt to online redefine a table that has inconsistent sharing with an interim table, ensure that there is consistent sharing.
ORA-42086: cannot enable ROLLBACK on a table with row movement enabled: Cause: An attempt was made to enable ROLLBACK on a table with row movement enabled in the redefinition.; Action: Currently, ROLLBACK is unsupported on such tables.
ORA-42087: cannot enable ROLLBACK on a nested table: Cause: An attempt was made to enable ROLLBACK on a nested table.; Action: Currently, ROLLBACK is unsupported on such tables.
ORA-42088: cannot enable ROLLBACK on a clustered table: Cause: An attempt was made to enable ROLLBACK on a clustered table.; Action: Currently, ROLLBACK is unsupported on such tables.
ORA-42089: ROLLBACK unsupported with specified column mapping string: Cause: The specified column mapping string included an identity column.; Action: ROLLBACK is unsupported with column mapping string.
ORA-42090: cannot use EXECUTE_UPDATE when the statement contains ROWID: Cause: An attempt was made to use EXECUTE_UPDATE when the update statement contained ROWID.; Action: Execute the update statement directly.
ORA-42091: shape of interim table does not match original table: Cause: An attempt was made to online redef a table when either the original table or the interim table did not have ROW ARCHIVAL.; Action: Remove ROW ARCHIVAL from the tables or add it to both tables.
ORA-42092: cannot add, remove or modify columns of Automatic CDR enabled table "string"."string" with online redefinition: Cause: Cannot add, remove, or modify columns with Automatic Conflict Detection and Resolution (ACDR) enabled using online redefinition.; Action: Do not attempt to add, remove, or modify a column on a table with Automatic Conflict Detection and Resolution (ACDR) enabled using online redefinition. Use ALTER TABLE instead.
ORA-42093: cannot online redefine table "string"."string" which is a delete tombstone table: Cause: An attempt was made to redefine a delete tombstone table.; Action: Do not attempt to online redefine a delete tombstone table.
ORA-42094: interim table of an AQ table can not have deferred segment: Cause: An attempt was made to use a deferred segment table as an interim table.; Action: Ensure that the interim table is not a deferred segment table.
ORA-42095: REDEF_TABLE() does not support a table in the join of a bitmap index: Cause: An attempt was made to redefine a table that was in the join of a bitmap index with the REDEF_TABLE() procedure.; Action: Do not attempt to redefine a table in the join of a bitmap index using REDEF_TABLE().
ORA-42287: cannot rename user on whose type a table depends: Cause: An attempt was made to rename a user whose schema contained a type on which some table depends. The operation may not proceed as it would render the table invalid causing loss of data.; Action: Drop table(s) dependent on types belonging to the schema of the user being renamed.
ORA-42288: may not create a schema synonym for the specified schema: Cause: An attempt was made to create a schema synonym for one of the reserved schemas (such as SYS or SYSTEM.); Action: Schema synonyms for this schema may not be created.
ORA-42289: may not rename specified user: Cause: An attempt was made to rename one of the following: - reserved user (such as SYS or SYSTEM) - an administrative user - a common user - a locked user account; Action: This user may not be renamed.
ORA-42290: specified schema does not exist: Cause: An attempt was made to create a schema synonym for a schema which did not exist.; Action: Correct the input and try again.
ORA-42291: schema synonym 'string' does not exist: Cause: The named schema synonym did not exist.; Action: Verify you are using the correct schema synonym name.
ORA-42292: RENAME TO already specified: Cause: The RENAME TO clause was specified twice.; Action: Use only one RENAME TO clause.
ORA-42293: user name conflicts with another user, role or schema synonym name: Cause: There was already a user, role or schema synonym with that name.; Action: Specify a different user name.
ORA-42294: role name conflicts with another user, role or schema synonym name: Cause: There was already a user, role or schema synonym with that name.; Action: Specify a different role name.
ORA-42295: schema synonym name conflicts with another user, role or schema synonym name: Cause: There was already a user, role or schema synonym with that name.; Action: Specify a different schema synonym name or use CREATE OR REPLACE SCHEMA SYNONYM.
ORA-42296: user, role or schema synonym 'string' does not exist: Cause: There was no user, role, or schema synonym by that name.; Action: Respecify the name.
ORA-42297: cannot drop a schema synonym for a schema of a user who is currently connected: Cause: An attempt was made to drop a schema synonym for a schema of a user who was logged on.; Action: Make sure user is logged off, then repeat command.
ORA-42298: cannot rename a user that is currently connected: Cause: An attempt was made to rename a user that was logged on.; Action: Make sure user is logged off, then repeat command.
ORA-42299: internal error occurred while dropping user: Cause: An internal error occurred while trying to drop a user.; Action: Contact the database administrator.
ORA-42300: an Editioning view is already defined on this table: Cause: An attempt was made to create an Editioning view on a table on which another Editioning view is already defined in the same Edition. This violates a restriction that at most one Editioning view may be associated with any base table in a given Edition.; Action: Create the new view as a regular view or, if the view being created is really intended to be an Editioning view associated with this table, drop the existing Editioning view before creating the new one.
ORA-42301: definition of an Editioning view may not refer to a synonym: Cause: An attempt was made to create an Editioning view referring to a synonym, which is not supported.; Action: Do not create an Editioning view if you want the view to refer to a synonym.
ORA-42302: definition of an Editioning view may not refer to remote tables: Cause: An attempt was made to create an Editioning view referring to remote tables, which is not supported.; Action: Do not create an Editioning view if you want the view to refer to a remote table.
ORA-42303: duplicate column reference in a definition of an Editioning view: Cause: An attempt was made create an Editioning view referencing the same column of a base table more than once, which is not supported.; Action: Do not create an Editioning view if you have multiple columns referring to the same column of the base table.
ORA-42304: base table and the Editioning view must belong to the same schema: Cause: An attempt was made to create an Editioning view in a schema different from that of the base table.; Action: Create an Editioning view in the same schema as the base table.
ORA-42305: only an Editioning view may replace an Editioning view: Cause: An attempt was made to replace an Editioning view with a view which is not an Editioning view or vice versa.; Action: Ensure that either both or neither of the views involved are Editioning views.
ORA-42306: a CrossEdition trigger may not be created on an Editioning view: Cause: An attempt was made to create a CrossEdition trigger on an Editioning view, which is not supported.; Action: Instead of creating a CrossEdition trigger on an Editioning view, create it on the Editioning view's underlying table.
ORA-42307: columns of an Editioning view may only refer to base table columns: Cause: An attempt was made to define an Editioning view containing a column referring to an entity other than a base table column (for example, a PL/SQL function without a parameter), which is not supported.; Action: Ensure that every column of an Editioning view refers to a column of a base table.
ORA-42308: view string.string is already in read-only mode: Cause: An attempt was made to set a read-only table in read-only mode.; Action: This DDL can only be executed on a read/write view.
ORA-42309: view string.string is already in read/write mode: Cause: An attempt was made to set a read/write view in read/write mode.; Action: This DDL can only be executed on a read-only view.
ORA-42310: Implementation restriction: this operation is only permitted on Editioning views: Cause: The view being altered was not an Editioning view. In this release, an ALTER VIEW READ ONLY, or ALTER VIEW READ WRITE operation is only permitted on Editioning views.; Action: Ensure that the view is an Editioning view.
ORA-42311: This operation is not permitted on Editioning views with compilation errors: Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not permitted on Editioning views which have compilation errors.; Action: Resolve the compilation errors.
ORA-42313: This operation is not supported on Editioning views marked invalid: Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not permitted on Editioning views which are marked invalid.; Action: Recompile the Editioning view to ensure that it is valid.
ORA-42314: editioning view cannot be owned by a non-editioned user: Cause: An attempt was made to create an editioning view in a schema where views were not editionable.; Action: Enable editions for the user for views and then create the editioning view.
ORA-42399: cannot perform a DML operation on a read-only view: Cause: An attempt was made to insert, delete, or update row(s) of a view created with read-only option. DML operations on such views are explicitly prohibited.; Action: Perform the desired DML operation on the view's underlying base table or issue ALTER VIEW ... READ WRITE command to make the view updatable.
ORA-42400: invalid object type for vertex or edge table definition: Cause: Vertex or edge tables were not defined from tables or materialized views.; Action: Use a schema object of the correct type to define an edge or vertex table of a property graph.
ORA-42401: invalid table for vertex or edge table definition: Cause: An object table, an XML table, or a dblink was used to define a vertex or edge table of a property graph.; Action: Use tables that are not an object, XML table, or dblink to any tables to define an edge or vertex table of a property graph.
ORA-42402: cannot infer key for graph element table string: Cause: Either a primary key or a unique and non-null key constraint was missed.; Action: Create a primary key or unique and non-null key constraint, or explicitly list the primary key columns using the KEY clause.
ORA-42403: ambiguous key for graph element table string: Cause: More than one unique and not null key constraints existed.; Action: Explicitly list key column names.
ORA-42404: graph element table name string already defined: Cause: Graph element table name was already defined in the graph.; Action: Specify a different graph element table name using the AS clause in the vertex table or edge table definition.
ORA-42405: Referenced vertex table string does not exist.: Cause: The vertex table name used in the SOURCE or DESTINATION clause did not exist.; Action: Use an existing vertex table name from the graph.
ORA-42406: columns used to define edge relationship must be NOT NULL in ENFORCED MODE: Cause: ENFORCED MODE was specified but a column used to define the foreign key of the edge table, or a referenced key to a vertex table allowed NULL values.; Action: Use columns that are NOT NULL for defining a foreign key or referenced key, or specify the TRUSTED MODE instead.
ORA-42407: duplicate property name in label string : string: Cause: The specified property name was already used to define another property in this label.; Action: Use a different property name.
ORA-42408: default label already defined: Cause: A default label was already defined.; Action: Use the LABEL clause to specify a different name.
ORA-42409: label string already defined: Cause: A label with this name was already defined differently.; Action: Use a different label name or specify the same property names.
ORA-42410: inconsistent property definition: string: Cause: A property name was defined differently for the same graph element table.; Action: Change the definition of properties to be consistent.
ORA-42411: column of data type string cannot be graph element table key: Cause: The type of a column was not allowed as key.; Action: Use a column with a data type that is allowed as key only.
ORA-42412: type mismatch between vertex key column string and edge key: Cause: The data type of an edge foreign key column and vertex referenced column were incompatible.; Action: Use edge and vertex columns with compatible data types.
ORA-42413: cannot infer edge relationship for edge table string: Cause: Zero or more than one foreign key constraints existed between the edge table and its vertex tables.; Action: Create a foreign key constraint, or explicitly specify the foreign and referenced keys between the edge table and the referenced table.
ORA-42414: cannot use mixed type for property string.string: Cause: The option DISALLOW MIXED TYPE was set but multiple definitions of the same property exposed column expressions that had different data types.; Action: Use the ALLOW MIXED TYPE option, or wrap the exposed column expression in casts so that all definitions of the property have the same data type.
ORA-42415: missing key column in edge reference definition: Cause: A different number of key columns were defined.; Action: Specify the same number of key columns for edge and vertex tables.
ORA-42416: duplicate column name string in key definition: Cause: The specified column name was already used in a key definition.; Action: Remove the duplicate column name from the list of columns in the KEY clause.
ORA-42417: option string already set: Cause: The same graph option was set multiple times.; Action: Remove the duplicate setting of the option.
ORA-42418: missing property graph option: Cause: An argument was missing in the OPTIONS clause.; Action: Pass a property graph option as an argument.
ORA-42419: At least one property graph option must be declared.: Cause: The OPTIONS clause required at least one option declaration.; Action: Declare at least one property graph option.
ORA-42420: invalid property graph option: Cause: An argument passed to the OPTIONS clause was not a valid property graph option.; Action: Use a valid property graph option.
ORA-42421: property graph does not exist: Cause: The specified property graph did not exist.; Action: Check the property graph name passed as argument.
ORA-42422: missing definition of properties: Cause: Arguments defining a column expression exposed as properties were missing in the PROPERTIES clause.; Action: Declare at least one column expression exposed as a property.
ORA-42423: invalid property graph label property definition: Cause: The specified property expression for a label property defintion was invalid.; Action: Use either a column name or SQL operator to define the property.
ORA-42424: expression based label property definition must use the AS clause: Cause: The AS clause was not used to specify a property name for an expression in vertex or edge table definition.; Action: Use the AS clause to specify a name for the property defined using an expression.
ORA-42425: column expression to define property is too long: Cause: The SQL text of the column expression used to define the property was too long.; Action: Use less SQL text for the column expression to define the property.
ORA-42426: duplicate column name string in EXCEPT clause: Cause: The column name was already referenced in an EXCEPT clause.; Action: Remove the duplicate column name from the list of columns in the EXCEPT clause.
ORA-42427: not a property graph: Cause: The specified object was not a property graph.; Action: Use a property graph object.
ORA-42428: no longer a valid graph element table: Cause: The object defining the graph element table was no longer valid.; Action: Revalidate the property graph or alter the property graph to change the invalid graph element table.
ORA-42429: property graph not allowed here: Cause: A property graph was specified incorrectly in a statement.; Action: Ensure that the name is correct or remove it.
ORA-42430: invalid identifier for property graph name or owner: Cause: An invalid identifier was specified as the property graph name or owner.; Action: Provide a valid identifier as the property graph name or owner. A valid property graph or owner identifier must start with a letter, be less than or equal to 128 bytes in length, and contain only alphanumeric characters or the special characters $, _, and #. It may not be a reserved word.
ORA-42431: ambiguous edge relationship for graph edge table string: Cause: More than one foreign key constraint existed between the edge table and a referenced vertex table.; Action: Explicitly declare the edge relationship using the KEY...REFERENCES clause.
ORA-42432: missing ENABLE VALIDATE constraint on graph element table string for ENFORCED MODE: Cause: Enforced mode was specified but no primary key or unique key constraint in the enable and validate state was found.; Action: Use the TRUSTED MODE, or define an ENABLE VALIDATE constraint for a primary key or a not null unique key clause.
ORA-42433: object used for vertex or edge table definition is not in a valid state: Cause: The object used to define a vertex or edge table was not in a valid state.; Action: Use a schema object in a valid state to define an edge or vertex table of a property graph.
ORA-42434: columns used to define graph element table key must be NOT NULL in ENFORCED MODE: Cause: Enforced mode was specified but a column used to define the key of a graph element table was nullable.; Action: Use columns that are NOT NULL for defining key columns, or specify the TRUSTED MODE instead.
ORA-42435: invalid SQL data type for property: Cause: An invalid SQL data type was used to define the property.; Action: Define the property using a column expression that has a valid SQL data type.
ORA-42436: Join group does not exist: Cause: The target join group does not exists.; Action: Create the join group in order to alter/drop it.
ORA-42437: remote object cannot be used to define graph element tables: Cause: A remote object was used to define a graph element table.; Action: Change the property graph definition to only use local objects.
ORA-42438: remote property graph cannot be used as a graph argument to DDL commands for creating, altering or dropping property graph: Cause: A remote property graph was used as argument to a DDL statement for creating, altering, or dropping a property graph.; Action: Connect to the remote database to perform the operation locally.
ORA-42800: The specified attribute association ("string", "string") is already attached to existing shared context-sensitive policies with the specified policy function string.string.: Cause: An attempt was made to add an attribute association which was already attached to shared context-sensitive policies with the specified policy function. All shared context-sensitive policies with a common policy function need to have the same set of attribute associations. Attribute associations of an existing shared context-sensitive policy which is using the specified policy function will be automatically added to the new policy.; Action: Retry the operation without specifying the attribute association.
ORA-42801: Value is not set for context attribute ("string", "string") which is associated with the Row Level Security (RLS) policy "string".: Cause: The value was not set for every attribute association of the shared context-sensitive policy. The value must be set for every attribute association of the shared context-sensitive policy.; Action: Set the value for the context attribute and retry the operation.
ORA-42802: Could not read attribute associations from an existing shared context-sensitive policy which is using the specified policy function.: Cause: An existing shared context-sensitive policy using the specified policy function was dropped from another session.; Action: Re-issue the command.
ORA-42803: Cannot use bind variable in VERSIONS clause when the object has a Row-Level Security (RLS) policy defined on it.: Cause: The object being accessed had a Row-Level Security (RLS) policy defined on it and the VERSIONS clause contained a bind variable.; Action: Rewrite the query without the use of bind variable in the VERSIONS clause.
ORA-42804: The operation can disclose rows protected by VPD policy.: Cause: The object being accessed had a Virtual Private Database (VPD) policy defined on it and the DML which is executed could disclose rows protected by the VPD policy.; Action: Define VPD policy with the specific statement type.
ORA-42805: The number of VPD policies on an object exceed the maximum number that is allowed.: Cause: A maximum of 255 Virtual Private Database (VPD) policies that can be enforced on an object was exceeded.; Action: Drop an existing policy before creating a new policy.
ORA-42900: OLS policy creation not allowed in application root.: Cause: Oracle Label Security (OLS) policy creation was attempted in application root.; Action: Switch to an application pluggable database to create an OLS policy.
ORA-42901: Cannot apply OLS policy on common or application objects.: Cause: An attempt was made to enforce Oracle Label Security (OLS) policy on common or application objects.; Action: Apply OLS policy on local objects only.
ORA-42902: cannot use virtual column as OLS policy column: Cause: An attempt was made to use the virtual column as an Oracle Label Security (OLS) policy column.; Action: Use another column or update the user table.
ORA-42903: Cannot assign OLS authorizations to common or application users.: Cause: An attempt was made to assign Oracle Label Security (OLS) authorizations to common or application users.; Action: Assign OLS authorizations to local users only.
ORA-42904: full table access is restricted by Oracle Label Security: Cause: The user did not have permission to bypass reads for Oracle Label Security policies.; Action: Grant appropriate privileges, or change the policy configurations.
ORA-42905: Oracle Label Security is not supported for an external table.: Cause: An attempt was made to enforce Oracle Label Security (OLS) policy to external tables.; Action: OLS is not supported for external tables.
ORA-42906: Cannot assign a non-existing OLS data label as row label.: Cause: An attempt was made to assign a non-existing Oracle Label Security (OLS) data label as a row label in an OLS-OID configuration.; Action: Ensure that the row label is a valid data label.
ORA-42907: cannot apply OLS policy with labeling function.: Cause: An attempt was made to enforce Oracle Label Security (OLS) policy with labeling function when Oracle Database Vault operations control was enabled.; Action: Apply OLS policy without the labeling function.
ORA-42908: cannot be executed by an Oracle Real Application Security user: Cause: An attempt was made to execute Oracle Label Security (OLS) API by an Oracle Real Application Security (RAS) user.; Action: Execute as a database user with necessary privileges and roles.
ORA-42909: cannot be executed outside datapump export: Cause: An attempt was made to execute the function outside datapump export.; Action: Do not execute outside datapump export.
ORA-42910: cannot be processed because user session label is modified: Cause: An attempt was made to alter the user session after the session label changed.; Action: Do not process after modifying the user session label.
ORA-42911: cannot administer Oracle Label Security policy: Cause: An attempt was made to administer Oracle Label Security (OLS) policy by an admin user within cloud database.; Action: Administer OLS policy using a designated OLS administrative user.