Oracle Database Errors or Warnings from Error ORA-16715 to ORA-16727

SQLServerF1

ORA-16715: redo transport-related property string of standby database “string” is inconsistent
Cause: The value of the specified redo transport-related configuration property of the given standby database was inconsistent with the primary database redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property.
Action: Query the InconsistentLogXptProps property on the primary database to determine which redo transport properties are set inconsistently Reset the properties on the standby database to make them consistent with the primary database redo transport settings.
ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed
Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed.
Action: Contact Oracle Support Services.
ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.
Action: Contact Oracle Support Services.

ORA-16718: failed to locate database
Cause: The Data Guard broker was unable to locate the database in the broker configuration.
Action: Add the database to the broker configuration and then reissue the command.
ORA-16719: unable to query V$ARCHIVE_DEST fixed view
Cause: The broker failed to query the V$ARCHIVE_DEST fixed view.”
Action: Test and clear the problem using SQL*Plus.
ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available
Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use.
Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to setup the primary database redo transport.

ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters
Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters.
Action: Check the Data Guard broker log and Oracle alert logs for more details.
ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters.
Action: Check the Data Guard broker log and Oracle alert logs for more details.
ORA-16723: setting AlternateLocation property conflicts with the redo transport setting
Cause: The standby database was not using standby redo logs, and the redo transport service to the standby database is set to a nonzero value for the ReopenSecs property and a value of zero for the MaxFailure property. In this case, the redo transport service will attempt to send redo data to the standby database indefinitely and never switch to the alternate destination.
Action: Any one of the following actions will solve the problem:
– add standby redo logs to the standby database.

– set ReopenSecs property to zero.

– set MaxFailure property to a nonzero value. After performing one of the above actions, reset the standby database AlternateLocation property.

ORA-16727: cannot close database
Cause: The Data Guard broker could not close the database.
Action: Terminate any active sessions connected to the database and then reissue the request.

Above are list of Oracle Database Errors or Warnings from Error ORA-16715 to ORA-16727 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 *