Oracle Database Errors or Warnings from Error ORA-16812 to ORA-16820

SQLServerF1

ORA-16812: log apply service not running on apply instance recorded by the broker
Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.
Action: Reenable the standby database to clear the error.
ORA-16813: log apply service not running on apply instance string recorded by the broker
Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.
Action: Reenable the standby database to clear the error.
ORA-16814: incorrect redo transport setting for AlternateLocation for standby database
Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:
– The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.

– The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.

– The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute.

– The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.

– The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error.

Action: Reenable the primary database to clear the error.

ORA-16815: incorrect redo transport setting for AlternateLocation for standby database “string”
Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:
– The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.

– The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.

– The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute.

– The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.

– The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error.

Action: Reenable the primary database to clear the error.
ORA-16816: incorrect database role
Cause: The Data Guard broker detected that the specified database had a database role that was different from the database role recorded in the Data Guard configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database.
Action: Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database.
ORA-16817: unsynchronized fast-start failover configuration
Cause: The fast-start failover target standby database was not synchronized with the primary database. As a result, a fast-start failover could not happen automatically in case of a primary database failure.
Action: Ensure that the fast-start failover target standby database is running and that the primary database can ship redo data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then fail over automatically to the standby database in the event of loss of the primary database.

ORA-16818: fast-start failover suspended
Cause: The primary database was intentionally shutdown. As a result, a fast-start failover could not happen automatically.
Action: Start the primary database. This effectively restores the ability to automatically perform a fast-start failover in the event of a failure of the primary database.
ORA-16819: fast-start failover observer not started
Cause: The observer for fast-start failover was not started. As a result, fast-start failover could not happen in the case of a primary database failure.
Action: Start the fast-start failover observer by using, for example, the DGMGRL START OBSERVER command.
ORA-16820: fast-start failover observer is no longer observing this database
Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:
– The host where the observer was running was not available.

– The network connection between the observer and this database was not available.

– The observer process was terminated unexpectedly.

Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL STOP OBSERVER command. Then, restart the observer on another host. Finally, use the DGMGRL START OBSERVER command to start the observer on the other host.

Above are list of Oracle Database Errors or Warnings from Error ORA-16812 to ORA-16820 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *