Oracle Database Errors or Warnings from Error ORA-16400 to ORA-16411

SQLServerF1

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.
ORA-16401: archivelog rejected by RFS
Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.
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.
ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters.
Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error.

ORA-16403: shutdown in progress – remote connection is not permitted
Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.
Action: Wait for the remote instance to be restarted, or contact your DBA.
ORA-16406: Primary and standby database software version mismatch
Cause: The primary database and standby database Oracle software is not compatible.
Action: Install the correct Oracle software and try again.
ORA-16407: Standby database is in the future of the archive log
Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs.
Action: No action is required.

ORA-16408: Incompatible archival Redo Branch lineage
Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs.
Action: No action is required.
ORA-16409: Archive log switchover reference number mismatch
Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.
Action: No action is required.
ORA-16411: ONDEMAND archival requires active managed recovery operation
Cause: The use of the ONDEMAND attribute for a physical standby database destination requires that the managed recovery operation be active prior to establishing the network connection.
Action: Start the managed recovery operation on the standby database.

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