Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16400 to ORA-16600
- ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST
Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.
Action: No action is required.
Cause: An attempt was made to re-archive an existing archive log.
Action: See alert log and trace file for more details. No action is necessary. This is an informational statement provided to record the event for diagnostic purposes.
Cause: The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause: A redo transport session could not be started because the database was shutting down.
Action: Wait for the remote instance to be restarted, or contact your DBA.
Cause: The primary and standby databases were not running compatible versions of Oracle server software.
Action: Install the correct Oracle server software and try again.
Cause: An archive log from a redo branch that is earlier than the one that the standby database is currently applying was rejected.
Action: No action is required.
Cause: An archive log from a redo branch that is incompatible with the one that the standby database is currently applying was rejected.
Action: No action is required.
Cause: The archive log switchover reference numbers of the primary and standby database did not match. Remote archival of redo log files is not allowed to incompatible standby database instances.
Action: No action is required.
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause: Switchover failed because no standby databases of the appropriate type were available.
Action: Check the alert log for errors, correct the problem and retry the switchover.
- ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required
Cause: Activation occurred after recovery from standby redo log files.
Action: Take a full database backup.
Cause: The database was not a physical standby database.
Action: Convert to physical standby database and retry the operation.
Cause: The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.
Action: Choose another physical standby database and retry the operation.
Cause: RECOVER FINISH failed because there was a redo gap on the standby database.
Action: Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE to perform an immediate failover with some data loss.
- ORA-16425: RECOVER FINISH cannot be issued when recovery branch string is not the target branch string.
Cause: RECOVER FINISH failed because a new branch existed on the physical standby database.
Action: Issue real-time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
Cause: Media recovery selected an incorrect log.
Action: Verify that the appropriate log has been properly registered and restart media recovery.
Cause: The redo transport lag at this database was too large for automatic redo gap detection to take place.
Action: Re-create this standby database from a current backup copy of the primary database.
Cause: Additional redo log threads were added on the primary database after the standby control file was created.
Action: Shut down the standby database and replace the control file with a new standby control file from the primary database or change the COMPATIBLE parameter to 10.2.0 or above and restart the standby database.
Cause: Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
Cause: An attempt was made to open the database or pluggable database in read-only mode after an operation that requires the database or pluggable database be opened in read/write mode.
Action: Open the database in read/write mode. The database can then be opened in read-only mode.
Cause: An archive log needed by the standby database to resolve a redo gap was not found on the source database. This is a fatal situation during a switchover or far sync instance assisted failover because the source database waits for the target standby to be clear of all archive log gaps before allowing the operation to proceed. If a redo gap cannot be resolved during these operations, the operation cannot succeed so it must be failed.
Action: If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the local destination on the source database but no longer exists at that location on disk, the archived log can be copied back to that location to allow gap processing to automatically resolve the gap. If the specified log has been purged from V$ARCHIVED_LOG, the archived log can be copied to disk on either the source or destination database and registered using the ALTER DATABASE REGISTER OR REPLACE LOGFILE command.
Cause: ALTER DATABASE … RECOVER FINISH failed to start because the standby database was missing redo changes below the checkpoint of data files.
Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead.
Cause: The coordinator Remote File Server (RFS) for this parallel archival either abnormally terminated or ran down before this subordinate RFS could begin its leg of the operation.
Action: No explicit user action is required.
Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details.
Action: Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
Cause: A logical standby or down stream capture database was not in a state where it could accept a request to receive redo from another database. This was likely due to the database not being open.
Action: See the database alert log at the receiving side of the transfer for details of why the database was not ready. If the database was mounted but not open, open it to clear the problem. The initialization parameter LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be set to ENABLE.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file was corrupt.
Action: Restore the current control file at the primary database and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo log file was corrupt.
Action: Restore the current log at the primary database, and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
Cause: The target standby database did not apply all received redo.
Action: Allow the target standby database to apply all redo and then reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the current log.
Action: This can happen if there are one or more errors during archival of the current log at the primary database. Reissue ALTER SYSTEM FLUSH REDO TO STANDBY after resolving the archiving errors.
- ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file.
Cause: A flush redo operation discovered SCNs greater than a previously failed flush redo operation.
Action: This can happen if there are one or more errors that have corrupted the control file or online redo logs. In these cases, flush redo operation is not possible.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be mounted, but not opened.
Action: Mount the database and then reissue the operation.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target database is not a standby database.
Action: Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and specify a standby database as the target database.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is not active at the target database.
Action: Start redo apply at the standby database and reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement with the NO CONFIRM APPLY clause.
Cause: The switchover operation could not continue because it failed to disable a thread that was left in an incomplete thread enable state.
Action: Check alert log for more details.
Cause: When opening or closing a database instance, the database may wait for up to 1 minute for pending remote archival requests to be performed before proceeding with the operation. This error was reported because that time limit was exceeded.
Action: This is an informational message so no action is required.
Cause: An attempt to switchover to a physical standby database failed.
Action: Check alert log for more details. Issue the SHUTDOWN ABORT command on the database before issuing another ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command.
Cause: The requested operation was not allowed because a switchover to standby operation was either in progress or had completed.
Action: Issue the SHUTDOWN ABORT command on the database after switchover operation completes.
Cause: Redo Apply stopped because it detected that it had proceeded beyond a standby failover operation.
Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end-of-redo (EOR) logs corresponding to the failover operation from the new primary database and register all these logs at the target database. Restart Redo Apply.
Cause: ALTER DATABASE CONVERT TO STANDBY command failed because either the database was not properly flashed back to STANDBY_BECAME_PRIMARY_SCN, or at least one of the online data files was not current.
Action: Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the ALTER DATABASE CONVERT TO STANDBY command.
Cause: ALTER DATABASE FAILOVER TO <target_db_name> or ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command failed because the target_db_name was invalid. The target_db_name must be the same as the name of the database on which the SQL command is issued.
Action: Change the target database name and reissue the command.
Cause: An attempt was made to issue the ALTER DATABASE FAILOVER TO <target_db_name> or the ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command on a database other than a physical standby database.
Action: Issue the command on a physical standby database.
Cause: An attempt was made to issue the ALTER DATABASE SWITCHOVER TO <target_db_name> [VERIFY] or ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command on a database other than an open primary database.
Action: Issue the command on an open primary database.
Cause: The switchover target was not a valid, enabled, or active standby database.
Action: Fix the problem in the switchover target and reissue the command.
Cause: The switchover target was not synchronized with the primary database.
Action: Wait until the switchover target is synchronized with the primary database, then reissue the command.
Cause: The primary database could not connect to the switchover target.
Action: Check the alert log for detailed errors.
Cause: The switchover target version number was lower than 12.
Action: Upgrade the switchover target to a higher release.
Cause: The switchover target was not running Redo Apply.
Action: Start Redo Apply on the switchover target and reissue the command.
Cause: Switchover failed because the switchover target could not convert to a primary database.
Action: Check the database role of the switchover target. If the switchover target database role is standby, do one of the following: – Fix the problem shown in the alert log. – Issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command to convert the switchover target to a primary database. – If the problem in the switchover target cannot be fixed, issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command on the old primary database to convert the old primary database back to a primary database. If the switchover target database role is primary, the switchover has completed. Open the switchover target and startup the old primary database to finish the switchover process.
Cause: The database was in MaxAvailability or MaxProtection mode but terminal recovery finished with data loss.
Action: For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY DATABASE command.
Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE statement could not proceed because the database was in an active state.
Action: Ensure that the SWITCHOVER_STATUS column in the V$DATABASE view has the value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed standby recovery and reissue the statement after the SWITCHOVER_STATUS column value changes to one of the above values.
Cause: ALTER DATABASE SWITCHOVER TO <target_db_name> or ALTER SYSTEM FLUSH REDO TO <target_db_name> statement failed because the target_db_name was not defined in the LOG_ARCHIVE_DEST_n parameter.
Action: Ensure that the target_db_name is defined in the LOG_ARCHIVE_DEST_n parameter.
Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> VERIFY command succeeded but with warnings.
Action: Check alert log for more details.
Cause: The specified operation was invalid on a far sync instance.
Action: Do not attempt the specified operation on a far sync instance.
Cause: An attempt was made by a far sync instance to perform gap analysis with a remote destination that already had connectivity with a different viable source of live redo.
Action: No action is required. This exception code is informational and is used by the far sync instance to remain idle with respect to this destination until it establishes connectivity with the primary database.
Cause: The connect string for the far sync instance that is flagged as the source of live redo for this database could not be located.
Action: Define a LOG_ARCHIVE_DEST_n parameter for the far sync instance using the SERVICE attribute to define the connect string for the far sync instance destination. This destination should be set to DEFER using the corresponding LOG_ARCHIVE_DEST_STATE_n parameter. Once the connect string is defined, retry the failover operation. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause: An attempt was made to connect to the far sync instance to help facilitate the failover operation but the connection attempt failed.
Action: Ensure that the far sync instance is mounted. Check the alert log and trace files on both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause: After successfully connecting to the far sync instance, an error was encountered when polling the far sync instance for progress.
Action: Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause: After successfully connecting to the far sync instance, an error was encountered when managing the failover target destination on the far sync instance.
Action: Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause: The operation failed because a role transition was in progress.
Action: None
Cause: An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the switchover target failed.
Action: Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover target.
Cause: The compatibility setting in the redo log transported to this standby database exceeded the current compatibility setting.
Action: Check the compatibility setting on the primary and standby database, and increase the compatibility setting in the initialization parameter file on the standby database accordingly.
Cause: A copy of this redo log was already received at the destination.
Action: None
Cause: The destination was not allowed to receive this redo log.
Action: Ensure the source database is registered at the destination, the destination is up and running, and storage is available.
Cause: The destination database was in read-only mode.
Action: Ensure the destination database is open for write.
Cause: The destination database failed to create an entry in the table used to track the redo log file.
Action: Examine the trace file of the Remote File Server (RFS) process. Ensure that space is available in your database.
Cause: Registering the redo log file to the destination database failed.
Action: Examine the trace file of the Remote File Server (RFS) process. Ensure that space is available in your database.
Cause: A minimum of two online redo log files per active thread were not supplied.
Action: Add the required redo log files and reissue the command.
Cause: The switchover target local destination either exceeded quota size or had an error.
Action: Fix the problem in the switchover target and reissue the command.
- ORA-16493: using SYSDBA, SYSOPER, SYSDG, or SYSBKUP user for redo shipping to Recovery Appliance is not supported
Cause: An attempt was made to use a SYSDBA, SYSOPER, SYSDG, or SYSBKUP user to ship redo logs to a Recovery Appliance.
Action: Use a user without the SYSDBA, SYSOPER, SYSDG, or SYSBKUP privilege to ship redo logs to a Recovery Appliance.
Cause: The Remote File Server (RFS) process or Remote Message Interface (RMI) process or Fetch Archive Log (FAL) process was started from the PDB.
Action: Check the service name that the RFS or RMI or FAL client connected to. Ensure the service is not from PDB.
- ORA-16495: Using fast recovery area to receive redo log files on Recovery Appliance is not supported.
Cause: An attempt was made to use fast recovery area to receive redo log file on a Recovery Appliance.
Action: Do not configure fast recovery area for receiving redo log files on a Recovery Appliance.
Cause: Invalid or corrupt metadata was encountered in a network packet.
Action: No user action is required.
Cause: The DELAY attribute was not 0 for the LOG_ARCHIVE_DEST_n parameter. Since the DELAY attribute delays standby database recovery, the switchover will be prolonged by that amount of time.
Action: Remove the DELAY attribute from the LOG_ARCHIVE_DEST_n parameter, then reissue the command.
Cause: Cancellation of managed recovery was invoked when the Oracle Active Data Guard (Oracle ADG) instance recovery was running.
Action: None
Cause: The Oracle Data Guard broker operation failed.
Action: See accompanying messages for details.
Cause: The Oracle Data Guard broker operation succeeded with warnings.
Action: See accompanying messages for details.
Cause: The Oracle Data Guard broker configuration already contained the maximum number of members that could be configured and managed by the broker.
Action: Select and remove an existing member from the broker configuration, then reissue the command to add another member to the configuration. Note that when COMPATIBLE is set lower than 11.2.0.0.0, the broker can configure and manage up to 10 databases. When COMPATIBLE is set to 11.2.0.0.0 but less than 12.0.0.0.0, this limit is increased to 31. When COMPATIBLE is set to 12.0.0.0.0 or higher, this limit is increased to 254.
Cause: A request to create an Oracle Data Guard configuration was made while connected to a database that is part of an existing configuration.
Action: To create a new configuration, the existing configuration must be deleted.
Cause: Process exceeded private or shared memory limits.
Action: Check for memory leaks, increase system parameters and restart.
Cause: The Oracle Data Guard broker timed out the request.
Action: Check the Oracle Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.
Cause: The maximum number of requests that the broker can service on the database instance was exceeded.
Action: Wait for the broker to complete processing the requests before issuing more requests.
Cause: The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either: – The databases changing roles were shut down. – The primary database was not shipping redo data. – The standby database that will become the primary database was not applying redo data. If this error was returned for database state change operations, the database state specified was invalid.
Action: If this error is returned when attempting a switchover operation, ensure that: – The databases changing roles are started. – The primary database is shipping redo data. – The standby database is applying redo data. If this error is returned when attempting a database state change operation, ensure that a valid database state is specified.
Cause: The connect identifier specified resulted in a connection to a pluggable database and not to the multitenant container database root.
Action: Check the connect identifier and confirm that it specifies a service name that results in a connection to the multitenant container database root.
Cause: The attempted command was not allowed because the configuration was part of a Global Data Services pool.
Action: Remove the configuration from the Global Data Services pool using GDSCTL. Then, retry the broker command. If the command was attempting to repair a database, disable or remove the individual database from the configuration and fix the issue. After the issue is resolved, reenable the database, or add the database back to the configuration if it had been removed.
Cause: The switchover or failover operation required the client to connect to the apply instance of the target database.
Action: Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.
Cause: A command, option, or fast-start failover condition argument was specified that is not supported in this release.
Action: If trying to enable or disable a fast-start failover condition, try a different Oracle error number. Otherwise, contact Oracle Support Services.
Cause: The Oracle Data Guard broker process was either not yet started, was initializing, or failed to start.
Action: If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Oracle Data Guard log for possible errors. Otherwise, retry the operation.
Cause: The Oracle Data Guard broker was unable to allocate memory for a request.
Action: Increase the size of the System Global Area (SGA).
Cause: The Oracle Data Guard broker was unable to allocate memory within the System Global Area (SGA).
Action: Increase the size of the System Global Area (SGA) memory.
Cause: There was insufficient space in Program Global Area (PGA) to allocate memory.
Action: Increase process virtual memory.
Cause: A NULL buffer or a length of zero was specified.
Action: Correct the command parameters and retry the command.
Cause: A broker operation was requested that required a broker configuration to already be created.
Action: Create a Data Guard broker configuration prior to performing other broker operations. If only one instance of a RAC database is reporting this error, ensure that the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to file locations that are shared by all instances of the RAC database.
Cause: The Oracle Data Guard broker returned this status because a switchover, failover or convert operation was in progress. The broker could not accept new commands until the operation finished.
Action: Wait until the operation is complete and reissue the command.
Cause: The broker could not complete the operation because Oracle Restart (for single instance databases) or Oracle Clusterware (for RAC databases) could not stop services or instances on this database.
Action: Check the Oracle Data Guard broker log file for more information and stop the appropriate services or instances using SRVCTL. Then retry the broker operation.
Cause: The Oracle Data Guard broker did not recognize the specified property or state name, or a fast-start failover condition was specified that is not enabled.
Action: Verify the command parameters and reissue the command.
Cause: One of the arguments for the specified command was invalid.
Action: Verify the arguments and then reissue the command.
Cause: The member specified in the command was not enabled.
Action: Select an enabled member and reissue the command.
Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID=’*’ qualifier was required in the command.
Action: Reenter the command using the SID=’*’ qualifier.
Cause: An attempt was made to disable broker management of the primary database or remove the primary database from the broker configuration while the configuration was enabled.
Action: If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to remove the primary database from the broker configuration while the configuration is enabled, you must instead remove the entire broker configuration.
Cause: An attempt was made to modify or query a disabled member. This error is also returned on an attempt to enable, modify, or query a member that the broker has disabled because of a switchover or failover operation. The broker disables its management of a member when it detects that the database needs to be re-created because of a failover or switchover operation.
Action: If broker management of the member is disabled, enable it and reissue the command.
Cause: An invalid or NULL string value was specified.
Action: Correct command parameters and retry.
Cause: A string property value was truncated due to insufficient buffer size.
Action: Specify a larger receive buffer.
Cause: A string property value that did not fill the receive buffer was placed in the receive buffer.
Action: This is an informational message only.
Cause: The operation could not be completed because the broker required assistance from the client that it was unable to provide because of the accompanying error.
Action: See the accompanying error message for more information and follow the directions provided in the Action section of that message. Then retry the operation.
Cause: An operation was attempted on a member that was not active.
Action: Verify that the member is active and retry the operation.
Cause: This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.
Action: Use a version of the observer that is compatible with the Oracle database server to be observed.
Cause: An attempt was made to create a duplicate member in the broker configuration, or to add a duplicate instance (SID) for an existing member in the broker configuration.
Action: Check the member to be added to ensure there are no duplicates.
Cause: An attempt was made to switchover to a database that was not a standby database.
Action: Locate an enabled standby database and select that database as the target of the switchover.
Cause: The instance to be removed was running.
Action: Shut down the instance and reissue the REMOVE command.
Cause: The specified property could not be modified because it was either a monitorable property or a property that did not exist.
Action: Retry the command with a valid configurable property.
Cause: The requested operation required that broker management of the Data Guard configuration must be enabled.
Action: Enable the Oracle Data Guard configuration and reissue the command.
Cause: The Oracle Data Guard broker operation required this database instance to be shut down and restarted.
Action: If DGMGRL or Enterprise Manager has not already done so, shut down the Oracle instance and then restart it.
Cause: The Oracle Data Guard broker was unable to create the configuration file on permanent storage.
Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
Cause: The Oracle Data Guard broker configuration file was either unavailable or did not exist.
Action: Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. For a RAC database, ensure that these initialization parameters are set to file locations that are shared by all instances of the RAC database.
Cause: The operation was rejected because the Oracle Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example: – An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running. – Non-broker access (such as DBMS_FILE_TRANSFER) to the configuration files was attempted. See the alert log for additional information.
Action: Disable the broker configuration and shut down the Oracle Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.
Cause: Switchover failed because either the primary database or the designated standby database were shut down.
Action: Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database.
Cause: One or more LOG_ARCHIVE_DEST_n initialization parameters on existing members were already set for the new member to be added when attempting to add a standby database, far sync instance, Backup Appliance, or external destination to the configuration.
Action: Clear the LOG_ARCHIVE_DEST_n initialization parameter that specifies the standby database, far sync instance, Backup Appliance, or external destination to be added.
Cause: A failure was encountered while the broker was updating the Oracle Data Guard broker configuration file on permanent storage.
Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Cause: The Oracle Data Guard broker detected errors while loading the configuration file.
Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.
Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.
Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Cause: An attempt was made to change an instance-specific property for a member that had more than one instance.
Action: Retry the command and identify a specific instance whose property value is to be changed.
Cause: The database specified for the operation was a standby database, or the operation was attempted on a standby database.
Action: Check the database type and retry the operation. If the command must be executed on a primary database, connect to the primary database and retry the operation.
Cause: The database specified for the operation was a primary database, or the operation was attempted on a primary database.
Action: Check the database type and retry the operation. If the command must be executed on a standby database, connect to a standby database and retry the operation.
Cause: An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command.
Action: Use the EDIT DATABASE command to change database properties.
Cause: An object was specified that the broker could not uniquely distinguish from other objects in the configuration.
Action: Try to further distinguish the object specified for the operation and reissue the command.
Cause: The Oracle Data Guard broker detected an error while transferring data from one member to another. This may happen when either: – The broker detects an inconsistency in the block count of the configuration file when the file is transmitted between members. – The broker encounters an error when writing the configuration file. – A broker member receives an incorrect message from another member.
Action: Contact Oracle Support Services.
Cause: The Oracle Data Guard broker background process, DMON, was not running.
Action: Check the Oracle Data Guard broker log file and DMON process trace file to determine why the DMON process is not running.
Cause: The specified process did not terminate at the request of the Data Guard broker.
Action: Contact Oracle Support Services.
Cause: The specified member was not in the Oracle Data Guard broker configuration.
Action: Retry the command with a member that is in the broker configuration.
Cause: The Oracle Data Guard broker detected two or more primary databases in the broker configuration and could not continue.
Action: Contact Oracle Support Services.
Cause: The Oracle Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more members in the broker configuration. This can occur when the primary database has stale broker configuration files.
Action: Contact Oracle Support Services.
Cause: The Oracle Data Guard broker detected a stale configuration during initialization for this member.
Action: The broker will automatically resolve this situation once the primary database completes its initialization.
Cause: The failover command failed because the client was not connected to the target standby database.
Action: Explicitly connect to the standby database to be failed over to and retry the failover command.