Oracle Database Errors or Warnings from Error ORA-16738 to ORA-16747

SQLServerF1

ORA-16738: redo transport service for database “string” is not running
Cause: The redo transport service for the specified standby database was not running.
Action: Check the Data Guard broker log and/or the alert log for more details. If necessary, start the redo transport service for the standby database.
ORA-16739: redo transport service for standby database “string” is running
Cause: The redo transport service for the standby database was running.
Action: Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database.
ORA-16740: redo transport service for standby database “string” incorrectly set to ALTERNATE
Cause: The redo transport service to the standby database was set to ALTERNATE when no other destination was set to alternate to this destination.
Action: Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters.

ORA-16741: the destination parameter of standby database “string” has incorrect syntax
Cause: The destination defined in the server parameter file of the primary database had incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled.
Action: Fix the syntax error in the primary database server parameter file or remove the entry from the server parameter file. Also, check the values of the redo transport-related properties for the specified standby database.
ORA-16742: the standby database “string” has exhausted its quota
Cause: The standby database exhausted its quota for storing archived redo logs.
Action: Remove some archived redo logs from the standby database or increase its quota.
ORA-16743: cannot determine status of redo transport service for standby database “string”
Cause: The status of redo transport to the specified standby database could not be determined.
Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list.
Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.
ORA-16745: unable to add DB_UNIQUE_NAME “string” into the DG_CONFIG list because it is full
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.
Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.
ORA-16746: Data Guard broker cannot mount the database
Cause: The Data Guard broker failed to mount the database.”
Action: Check the Data Guard broker log and Oracle alert log for more details.
ORA-16747: logical standby database guard could not be turned on
Cause: The Data Guard broker could not turn on the logical standby database guard.
Action: Check the Data Guard broker log and Oracle alert log for more details.

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