Oracle 11g Error Codes and Solution Suggestions from ORA-16300 to ORA-16500

Posted on by Fatih Acar

Oracle 11g Error Codes and Solution Suggestions from ORA-16300 to ORA-16500

ORA-16302: extended data type support is not supported for specified table
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that was not supported for such an operation. The table either does not have a primary key or it has a data type not supported by this procedure.
Action: Specify a table for which support exists in EDS_ADD_TABLE.
ORA-16303: specified table already has extended data type support
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that already had EDS added on the local database.
Action: None
ORA-16304: procedure must first be called on primary database
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical standby database without having first called it on the primary database.
Action: Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and then retry on the standby.
ORA-16305: procedure not supported on a logical standby
Cause: A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical standby database which can only be called on a primary database
Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database
ORA-16306: specified table does not have a primary key
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that did not have a primary key.
Action: Add a primary key and retry the operation.
ORA-16307: TSE key string successfully applied
Cause: An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully committed on the logical standby database.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16308: specified table has extended data type support
Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table that is being maintained by extended data type support.
Action: Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation.
ORA-16311: materialized view log already exists
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table with a LOB that requires the creation of a specifically-defined materialized view log but one already exists.
Action: Drop the existing materialized view log and retry the operation.
ORA-16332: logical standby encountered non-fatal error ORA-string during DDL execution
Cause: Logical standby apply encountered a non-fatal error during DDL execution and continued to process subsequent transactions.
Action: This error is informational only. No user action is required.
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: archive log rejected by Remote File Server (RFS)
Cause: An attempt was made to re-archive an existing archive log.
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: TRANSPORT=ONDEMAND is unsupported.
Cause: The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16403: shut down in progress – remote connection is not permitted
Cause: A redo transport session could not be started because the database was shutting down.
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 and standby databases were not running compatible versions of Oracle server software.
Action: Install the correct Oracle server software and try again.
ORA-16407: An archive log from an earlier redo branch has been rejected
Cause: An archive log from a redo branch that is earlier than the one that the standby database is currently applying was rejected.
Action: No action is required.
ORA-16408: An archive log from an incompatible redo branch has been rejected.
Cause: An archive log from a redo branch that is incompatible with the one that the standby database is currently applying was rejected.
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 did not match. Remote archival of redo log files is not allowed to incompatible standby database instances.
Action: No action is required.
ORA-16411: TRANSPORT=ONDEMAND is unsupported
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16412: TRANSPORT=ONDEMAND is unsupported
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16413: TRANSPORT=ONDEMAND is unsupported
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16416: No viable stringswitchover targets available
Cause: Switchover failed because no standby databases of the appropriate type were available.
Action: Check the alert log for errors, correct the problem and retry the switchover.
ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required
Cause: Activation occurred after recovery from standby redo log files.
Action: Take a full database backup.
ORA-16419: Snapshot standby must be converted to a physical standby database.
Cause: The database was not a physical standby database.
Action: Convert to physical standby database and retry the operation.
ORA-16420: fast-start failover target cannot be converted to snapshot standby
Cause: The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.
Action: Choose another physical standby database and retry the operation.
ORA-16424: RECOVER FINISH cannot complete due to a redo gap.
Cause: RECOVER FINISH failed because there was a redo gap on the standby database.
Action: Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE to perform an immediate failover with some data loss.
ORA-16425: RECOVER FINISH cannot be issued when recovery branch string is not the target branch string.
Cause: RECOVER FINISH failed because a new branch existed on the physical standby database.
Action: Issue real-time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
ORA-16426: Recovery requested an incorrect log from which to apply redo data.
Cause: Media recovery selected an incorrect log.
Action: Verify that the appropriate log has been properly registered and restart media recovery.
ORA-16427: Redo gap is too large to resolve.
Cause: The redo transport lag at this database was too large for automatic redo gap detection to take place.
Action: Re-create this standby database from a current backup copy of the primary database.
ORA-16431: cannot expand control file
Cause: Additional redo log threads were added on the primary database after the standby control file was created.
Action: Shut down the standby database and replace the control file with a new standby control file from the primary database or change the COMPATIBLE parameter to 10.2.0 or above and restart the standby database.
ORA-16432: inconsistent set of logs applied at a standby database
Cause: Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
ORA-16433: The database must be opened in read/write mode.
Cause: An attempt was made to open the database in read-only mode after an operation that requires that the database be opened in read/write mode.
Action: Open the database in read/write mode. The database can then be opened in read-only mode.
ORA-16434: Archive log for branch string thread string sequence string cannot be queued.
Cause: An archive log needed by the standby database to resolve a redo gap was not found on the primary database. This is a fatal situation during a switchover because the primary database waits for the target standby to be clear of all archive log gaps before allowing the switchover to proceed. If a redo gap cannot be resolved, the switchover cannot succeed.
Action: If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the local destination on the primary database but no longer exists in that location on disk, the archived log can be copied back to that location to allow gap processing to automatically resolve the gap. If the specified log has been purged from V$ARCHIVED_LOG, the archived log can be copied to disk on either the primary or standby database and registered using the ALTER DATABASE REGISTER OR REPLACE LOGFILE command.
ORA-16436: ALTER DATABASE … RECOVER FINISH could not start
Cause: ALTER DATABASE … RECOVER FINISH failed to start because the standby database was missing redo changes below the checkpoint of data files.
Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead.
ORA-16437: No active coordinator RFS for current operation
Cause: The coordinator Remote File Server (RFS) for this parallel archival either abnormally terminated or ran down before this subordinate RFS could begin its leg of the operation.
Action: No explicit user action is required.
ORA-16438: Switchover to primary cannot be executed at this time
Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details.
Action: Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
ORA-16439: Standby not ready to receive redo at this time
Cause: A logical standby or down stream capture database was not in a state where it could accept a request to receive redo from another database. This was likely due to the database not being open.
Action: See the database alert log at the receiving side of the transfer for details of why the database was not ready. If the database was mounted but not open, open it to clear the problem. The initialization parameter LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be set to ENABLE.
ORA-16440: Control file is corrupt.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file was corrupt.
Action: Restore the current control file at the primary database and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16441: Current log string for thread string sequence string is invalid.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo log file was corrupt.
Action: Restore the current log at the primary database, and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16442: ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied.
Cause: The target standby database did not apply all received redo.
Action: Allow the target standby database to apply all redo and then reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.
ORA-16443: could not switch out of log string thread string
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the current log.
Action: This can happen if there are one or more errors during archival of the current log at the primary database. Reissue ALTER SYSTEM FLUSH REDO TO STANDBY after resolving the archiving errors.
ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file.
Cause: A flush redo operation discovered SCNs greater than a previously failed flush redo operation.
Action: This can happen if there are one or more errors that have corrupted the control file or online redo logs. In these cases, flush redo operation is not possible.
ORA-16445: Database has to be mounted and cannot be open
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be mounted, but not opened.
Action: Mount the database and then reissue the operation.
ORA-16446: Target database was not a standby database
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target database is not a standby database.
Action: Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and specify a standby database as the target database.
ORA-16447: Redo apply was not active at the target standby database
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is not active at the target database.
Action: Start redo apply at the standby database and reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement with the NO CONFIRM APPLY clause.
ORA-16448: Primary database corruption has been detected by standby database.
Cause: The primary database became corrupted.
Action: Identify the extent of the corruption on both the primary and standby database and take remedial action.
ORA-16449: incomplete redo thread enable operation
Cause: The switchover operation could not continue because it failed to disable a thread that was left in an incomplete thread enable state.
Action: Check alert log for more details.
ORA-16451: A remote archival request has timed out.
Cause: When opening or closing a database instance, the database may wait for up to 1 minute for pending remote archival requests to be performed before proceeding with the operation. This error was reported because that time limit was exceeded.
Action: This is an informational message so no action is required.
ORA-16455: switchover to standby failed
Cause: An attempt to switchover to a physical standby database failed.
Action: Check alert log for more details. Issue the SHUTDOWN ABORT command on the database before issuing another ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command.
ORA-16456: switchover to standby in progress or completed
Cause: The requested operation was not allowed because a switchover to standby operation was either in progress or had completed.
Action: Issue the SHUTDOWN ABORT command on the database after switchover operation completes.

Leave a Reply

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

Time limit is exhausted. Please reload CAPTCHA.