Error: ORA-16810: multiple errors or warnings detected for the database – Fix
this section demonstrates how to use the SHOW command and monitorable database properties to identify
and resolve a failure situation.
1 Check the configuration status.
broker configuration is an aggregated status of all databases and instances in
the broker configuration. You can check the configuration status first to
determine whether or not any further action needs to be taken. If the
configuration status is SUCCESS, everything in the
broker configuration is working fine. However, if you see the following error,
it means something is wrong in the configuration:
to continue on to Step 2 to determine the actual failure.
2 Check the database status.
database has the failure, you need to go through all of the databases in the
configuration one by one. In this example, the error happens to be on the
primary database SALESPRD:
the following output:
3 Check the StatusReport monitorable database property.
ORA-16810, you can use the StatusReport monitorable database property to identify each of the
errors or warnings:
4 Check the LogXptStatus monitorable database property.
ORA-16737 in the previous status report in Step 3. To identify the exact log
transport error, you can use LogXptStatus monitorable database property:
reason why redo transport services failed. To fix this error, start the
listener for the physical standby database SALESDR.
5 Check the InconsistentProperties monitorable database
ORA-16714 reported in Step 3. To identify the inconsistent values for
property LogArchiveTrace, you can use the InconsistentProperties monitorable database property:
current database memory value (255) is different from both the server parameter
file (SPFILE) value (0) and Data Guard broker’s property value (0). If you
decide the database memory value is correct, you can update Data Guard broker’s
property value using the following command:
command, Data Guard broker also updates the spfile value for you so that value
for LogArchiveTrace is kept consistent.
6 Check the InconsistentLogXptProps monitorable database
see in the status report returned in Step 3 is ORA-16715. To identify the
inconsistent values for the redo transport configurable database
property, ReopenSecs, you can use the InconsistentLogXptProps monitorable database property.
memory value (600) is different from the Data Guard broker’s property value
(300). If you think the broker’s property value is correct, you can fix the
inconsistency by re-editing the property of the standby database with the same
value, as shown in the following example:
You can also reenable
the standby database or reset the primary database state to TRANSPORT-ON to fix the inconsistency, but re-editing the property is the