{"id":2256,"date":"2016-09-21T21:19:34","date_gmt":"2016-09-21T18:19:34","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2256"},"modified":"2017-02-15T21:20:31","modified_gmt":"2017-02-15T18:20:31","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-16400-to-ora-16600","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-16400-to-ora-16600\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16400 to ORA-16600"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16400 to ORA-16600<\/strong><\/p>\n

\n
ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16401: archive log rejected by Remote File Server (RFS)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to re-archive an existing archive log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16402: TRANSPORT=ONDEMAND is unsupported.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was specified on the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16403: shut down in progress – remote connection is not permitted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A redo transport session could not be started because the database was shutting down.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the remote instance to be restarted, or contact your DBA.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16406: primary and standby database software version mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The primary and standby databases were not running compatible versions of Oracle server software.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Install the correct Oracle server software and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16407: An archive log from an earlier redo branch has been rejected<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log from a redo branch that is earlier than the one that the standby database is currently applying was rejected.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-16408: An archive log from an incompatible redo branch has been rejected.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log from a redo branch that is incompatible with the one that the standby database is currently applying was rejected.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16409: archive log switchover reference number mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16411: TRANSPORT=ONDEMAND is unsupported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16412: TRANSPORT=ONDEMAND is unsupported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16413: TRANSPORT=ONDEMAND is unsupported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16416: No viable\u00a0string<\/i>switchover targets available<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Switchover failed because no standby databases of the appropriate type were available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log for errors, correct the problem and retry the switchover.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Activation occurred after recovery from standby redo log files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Take a full database backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16419: Snapshot standby must be converted to a physical standby database.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was not a physical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Convert to physical standby database and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16420: fast-start failover target cannot be converted to snapshot standby<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Choose another physical standby database and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16424: RECOVER FINISH cannot complete due to a redo gap.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RECOVER FINISH failed because there was a redo gap on the standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE to perform an immediate failover with some data loss.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16425: RECOVER FINISH cannot be issued when recovery branch\u00a0string<\/i>\u00a0is not the target branch\u00a0string<\/i>.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RECOVER FINISH failed because a new branch existed on the physical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16426: Recovery requested an incorrect log from which to apply redo data.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Media recovery selected an incorrect log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the appropriate log has been properly registered and restart media recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16427: Redo gap is too large to resolve.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The redo transport lag at this database was too large for automatic redo gap detection to take place.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-create this standby database from a current backup copy of the primary database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16431: cannot expand control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Additional redo log threads were added on the primary database after the standby control file was created.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16432: inconsistent set of logs applied at a standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Redo 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Determine 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16433: The database or pluggable database must be opened in read\/write mode.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to open the database or pluggable database in read-only mode after an operation that requires the database or pluggable database be opened in read\/write mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Open the database in read\/write mode. The database can then be opened in read-only mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16434: archive log for branch\u00a0string<\/i>\u00a0thread\u00a0string<\/i>\u00a0sequence\u00a0string<\/i>\u00a0cannot be queued<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log needed by the standby database to resolve a redo gap was not found on the source database. This is a fatal situation during a switchover or far sync instance assisted failover because the source database waits for the target standby to be clear of all archive log gaps before allowing the operation to proceed. If a redo gap cannot be resolved during these operations, the operation cannot succeed so it must be failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the local destination on the source database but no longer exists at 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 source or destination database and registered using the ALTER DATABASE REGISTER OR REPLACE LOGFILE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16436: ALTER DATABASE … RECOVER FINISH could not start<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE … RECOVER FINISH failed to start because the standby database was missing redo changes below the checkpoint of data files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16437: No active coordinator RFS for current operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No explicit user action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16438: Switchover to primary cannot be executed at this time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16439: Standby not ready to receive redo at this time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16440: Control file is corrupt.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file was corrupt.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the current control file at the primary database and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16441: Current log\u00a0string<\/i>\u00a0for thread\u00a0string<\/i>\u00a0sequence\u00a0string<\/i>\u00a0is invalid.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo log file was corrupt.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the current log at the primary database, and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16442: ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The target standby database did not apply all received redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Allow the target standby database to apply all redo and then reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16443: could not switch out of log\u00a0string<\/i>\u00a0thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the current log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A flush redo operation discovered SCNs greater than a previously failed flush redo operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16445: Database has to be mounted and cannot be open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be mounted, but not opened.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount the database and then reissue the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16446: Target database was not a standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target database is not a standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and specify a standby database as the target database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16447: Redo apply was not active at the target standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is not active at the target database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Start 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16449: incomplete redo thread enable operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover operation could not continue because it failed to disable a thread that was left in an incomplete thread enable state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check alert log for more details.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16451: A remote archival request has timed out.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an informational message so no action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16455: switchover to standby failed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to switchover to a physical standby database failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check alert log for more details. Issue the SHUTDOWN ABORT command on the database before issuing another ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16456: switchover to standby in progress or completed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The requested operation was not allowed because a switchover to standby operation was either in progress or had completed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue the SHUTDOWN ABORT command on the database after switchover operation completes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16459: recovery already beyond standby failover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Redo Apply stopped because it detected that it had proceeded beyond a standby failover operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Determine 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 database and register all these logs at the target database. Restart Redo Apply.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16461: database not flashed back or recovered to a consistent point<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE CONVERT TO STANDBY command failed because either the database was not properly flashed back to STANDBY_BECAME_PRIMARY_SCN, or at least one of the online data files was not current.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the ALTER DATABASE CONVERT TO STANDBY command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16463: invalid target database name<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE FAILOVER TO <target_db_name> or ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command failed because the target_db_name was invalid. The target_db_name must be the same as the name of the database on which the SQL command is issued.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change the target database name and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16464: operation must be initiated on a physical standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to issue the ALTER DATABASE FAILOVER TO <target_db_name> or the ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command on a database other than a physical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue the command on a physical standby database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16465: operation must be initiated on an open primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to issue the ALTER DATABASE SWITCHOVER TO <target_db_name> [VERIFY] or ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command on a database other than an open primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue the command on an open primary database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16466: invalid switchover target<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover target was not a valid, enabled, or active standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Fix the problem in the switchover target and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16467: switchover target is not synchronized<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover target was not synchronized with the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait until the switchover target is synchronized with the primary database, then reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16468: error connecting to switchover target\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The primary database could not connect to the switchover target.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log for detailed errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16469: switchover target version number is lower than 12<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover target version number was lower than 12.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Upgrade the switchover target to a higher release.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16470: Redo Apply is not running on switchover target<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover target was not running Redo Apply.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Start Redo Apply on the switchover target and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16471: cannot convert switchover target\u00a0string<\/i>\u00a0to a primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Switchover failed because the switchover target could not convert to a primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the database role of the switchover target. If the switchover target database role is standby, do one of the following: – Fix the problem shown in the alert log. – Issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command to convert the switchover target to a primary database. – If the problem in the switchover target cannot be fixed, issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE command on the old primary database to convert the old primary database back to a primary database. If the switchover target database role is primary, the switchover has completed. Open the switchover target and startup the old primary database to finish the switchover process.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16472: failover failed due to data loss<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was in MaxAvailability or MaxProtection mode but terminal recovery finished with data loss.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY DATABASE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16473: database is not in limbo<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE statement could not proceed because the database was in an active state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the SWITCHOVER_STATUS column in the V$DATABASE view has the value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed standby recovery and reissue the statement after the SWITCHOVER_STATUS column value changes to one of the above values.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16474: target_db_name not found in the LOG_ARCHIVE_DEST_n parameter<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE SWITCHOVER TO <target_db_name> or ALTER SYSTEM FLUSH REDO TO <target_db_name> statement failed because the target_db_name was not defined in the LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the target_db_name is defined in the LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16475: succeeded with warnings, check alert log for more details<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The ALTER DATABASE SWITCHOVER TO <target_db_name> VERIFY command succeeded but with warnings.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check alert log for more details.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16476: far sync instance does not allow\u00a0string<\/i>\u00a0operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified operation was invalid on a far sync instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt the specified operation on a far sync instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16477: destination is being serviced by another viable source<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made by a far sync instance to perform gap analysis with a remote destination that already had connectivity with a different viable source of live redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required. This exception code is informational and is used by the far sync instance to remain idle with respect to this destination until it establishes connectivity with the primary database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16478: cannot locate far sync instance connect string<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The connect string for the far sync instance that is flagged as the source of live redo for this database could not be located.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Define a LOG_ARCHIVE_DEST_n parameter for the far sync instance using the SERVICE attribute to define the connect string for the far sync instance destination. This destination should be set to DEFER using the corresponding LOG_ARCHIVE_DEST_STATE_n parameter. Once the connect string is defined, retry the failover operation. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16479: cannot connect to the far sync instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to connect to the far sync instance to help facilitate the failover operation but the connection attempt failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the far sync instance is mounted. Check the alert log and trace files on both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16480: operational error during far sync instance assisted failover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0After successfully connecting to the far sync instance, an error was encountered when polling the far sync instance for progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16481: destination error during far sync instance assisted failover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0After successfully connecting to the far sync instance, an error was encountered when managing the failover target destination on the far sync instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16482: a role transition is in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation failed because a role transition was in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-16483: unable to set a LOG_ARCHIVE_DEST_n parameter to the switchover target<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the switchover target failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover target.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16484: compatibility setting is too low<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The compatibility setting in the redo log transported to this standby database exceeded the current compatibility setting.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the compatibility setting on the primary and standby database, and increase the compatibility setting in the initialization parameter file on the standby database accordingly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16485: redo log is already received at destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A copy of this redo log was already received at the destination.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-16486: redo log is rejected by the destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The destination was not allowed to receive this redo log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure the source database is registered at the destination, the destination is up and running, and storage is available.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16487: the destination database is not writable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The destination database was in read-only mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure the destination database is open for write.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16488: cannot create a bookkeeping entry in database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The destination database failed to create an entry in the table used to track the redo log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine the trace file of the Remote File Server (RFS) process. Ensure that space is available in your database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16489: cannot register the redo log at the destination database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Registering the redo log file to the destination database failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine the trace file of the Remote File Server (RFS) process. Ensure that space is available in your database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16491: operation not allowed due to insufficient online redo log files\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A minimum of two online redo log files per active thread were not supplied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add the required redo log files and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16492: switchover target local destination has error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover target local destination either exceeded quota size or had an error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Fix the problem in the switchover target and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16493: using SYSDBA, SYSOPER, SYSDG, or SYSBKUP user for redo shipping to Recovery Appliance is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use a SYSDBA, SYSOPER, SYSDG, or SYSBKUP user to ship redo logs to a Recovery Appliance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a user without the SYSDBA, SYSOPER, SYSDG, or SYSBKUP privilege to ship redo logs to a Recovery Appliance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16494: process started from pluggable database (PDB)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Remote File Server (RFS) process or Remote Message Interface (RMI) process or Fetch Archive Log (FAL) process was started from the PDB.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the service name that the RFS or RMI or FAL client connected to. Ensure the service is not from PDB.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16495: Using fast recovery area to receive redo log files on Recovery Appliance is not supported.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use fast recovery area to receive redo log file on a Recovery Appliance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not configure fast recovery area for receiving redo log files on a Recovery Appliance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16496: corruption in network metadata packet<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Invalid or corrupt metadata was encountered in a network packet.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No user action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16497: LOG_ARCHIVE_DEST_string<\/i>\u00a0DELAY attribute is not 0<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The DELAY attribute was not 0 for the LOG_ARCHIVE_DEST_n parameter. Since the DELAY attribute delays standby database recovery, the switchover will be prolonged by that amount of time.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove the DELAY attribute from the LOG_ARCHIVE_DEST_n parameter, then reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16498: Cancellation of managed recovery operation cannot be performed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Cancellation of managed recovery was invoked when the Oracle Active Data Guard (Oracle ADG) instance recovery was running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-16501: The Oracle Data Guard broker operation failed.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker operation failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying messages for details.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16502: The Oracle Data Guard broker operation succeeded with warnings.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker operation succeeded with warnings.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying messages for details.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16503: cannot exceed the maximum number of members in this configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker configuration already contained the maximum number of members that could be configured and managed by the broker.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Select and remove an existing member from the broker configuration, then reissue the command to add another member to the configuration. Note that when COMPATIBLE is set lower than 11.2.0.0.0, the broker can configure and manage up to 10 databases. When COMPATIBLE is set to 11.2.0.0.0 but less than 12.0.0.0.0, this limit is increased to 31. When COMPATIBLE is set to 12.0.0.0.0 or higher, this limit is increased to 254.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16504: The Oracle Data Guard configuration already exists.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A request to create an Oracle Data Guard configuration was made while connected to a database that is part of an existing configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0To create a new configuration, the existing configuration must be deleted.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16506: out of memory<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Process exceeded private or shared memory limits.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check for memory leaks, increase system parameters and restart.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16509: request timed out<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker timed out the request.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the Oracle Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16513: maximum requests exceeded<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The maximum number of requests that the broker can service on the database instance was exceeded.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the broker to complete processing the requests before issuing more requests.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16516: current state is invalid for the attempted operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either: – The databases changing roles were shut down. – The primary database was not shipping redo data. – The standby database that will become the primary database was not applying redo data. If this error was returned for database state change operations, the database state specified was invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If this error is returned when attempting a switchover operation, ensure that: – The databases changing roles are started. – The primary database is shipping redo data. – The standby database is applying redo data. If this error is returned when attempting a database state change operation, ensure that a valid database state is specified.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16521: Service name specified in connect identifier connects to a pluggable database.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The connect identifier specified resulted in a connection to a pluggable database and not to the multitenant container database root.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the connect identifier and confirm that it specifies a service name that results in a connection to the multitenant container database root.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16522: configuration is part of Global Data Services pool<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The attempted command was not allowed because the configuration was part of a Global Data Services pool.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove the configuration from the Global Data Services pool using GDSCTL. Then, retry the broker command. If the command was attempting to repair a database, disable or remove the individual database from the configuration and fix the issue. After the issue is resolved, reenable the database, or add the database back to the configuration if it had been removed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16523: operation requires the client to connect to instance “string<\/i>“<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The switchover or failover operation required the client to connect to the apply instance of the target database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16524: unsupported command, option, or argument<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A command, option, or fast-start failover condition argument was specified that is not supported in this release.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If trying to enable or disable a fast-start failover condition, try a different Oracle error number. Otherwise, contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16525: The Oracle Data Guard broker is not yet available.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker process was either not yet started, was initializing, or failed to start.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Oracle Data Guard log for possible errors. Otherwise, retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16526: unable to allocate memory to process request<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker was unable to allocate memory for a request.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the size of the System Global Area (SGA).<\/span><\/span><\/p>\n

\n
<\/a> ORA-16527: unable to allocate broker System Global Area (SGA) memory<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker was unable to allocate memory within the System Global Area (SGA).<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the size of the System Global Area (SGA) memory.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16528: unable to allocate Program Global Area (PGA) memory<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0There was insufficient space in Program Global Area (PGA) to allocate memory.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase process virtual memory.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16530: invalid buffer or length<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A NULL buffer or a length of zero was specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the command parameters and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16532: Oracle Data Guard broker configuration does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A broker operation was requested that required a broker configuration to already be created.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create a Data Guard broker configuration prior to performing other broker operations. If only one instance of a RAC database is reporting this error, ensure that the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to file locations that are shared by all instances of the RAC database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16534: switchover, failover or convert operation in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker returned this status because a switchover, failover or convert operation was in progress. The broker could not accept new commands until the operation finished.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait until the operation is complete and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16535: Oracle Restart or Oracle Clusterware prevented completion of broker operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The broker could not complete the operation because Oracle Restart (for single instance databases) or Oracle Clusterware (for RAC databases) could not stop services or instances on this database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the Oracle Data Guard broker log file for more information and stop the appropriate services or instances using SRVCTL. Then retry the broker operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16538: no match on requested item<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker did not recognize the specified property or state name, or a fast-start failover condition was specified that is not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify the command parameters and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16540: invalid argument<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One of the arguments for the specified command was invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify the arguments and then reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16541: member is not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The member specified in the command was not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Select an enabled member and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16544: modifying DG_BROKER_START requires SID=’*’ qualifier<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID=’*’ qualifier was required in the command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reenter the command using the SID=’*’ qualifier.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16547: cannot disable or remove the primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to disable broker management of the primary database or remove the primary database from the broker configuration while the configuration was enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to remove the primary database from the broker configuration while the configuration is enabled, you must instead remove the entire broker configuration.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16548: member not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to modify or query a disabled member. This error is also returned on an attempt to enable, modify, or query a member that the broker has disabled because of a switchover or failover operation. The broker disables its management of a member when it detects that the database needs to be re-created because of a failover or switchover operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If broker management of the member is disabled, enable it and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16549: invalid string<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An invalid or NULL string value was specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct command parameters and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16550: truncated result<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A string property value was truncated due to insufficient buffer size.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a larger receive buffer.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16551: short string copied<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A string property value that did not fill the receive buffer was placed in the receive buffer.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an informational message only.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16552: error occurred while generating directives for client<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation could not be completed because the broker required assistance from the client that it was unable to provide because of the accompanying error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See the accompanying error message for more information and follow the directions provided in the Action section of that message. Then retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16555: member is not active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was attempted on a member that was not active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the member is active and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16556: observer version mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a version of the observer that is compatible with the Oracle database server to be observed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16557: member is already in use<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to create a duplicate member in the broker configuration, or to add a duplicate instance (SID) for an existing member in the broker configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the member to be added to ensure there are no duplicates.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16558: database specified for switchover is not a standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to switchover to a database that was not a standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Locate an enabled standby database and select that database as the target of the switchover.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16561: cannot remove an active instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The instance to be removed was running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down the instance and reissue the REMOVE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16568: cannot set property\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified property could not be modified because it was either a monitorable property or a property that did not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the command with a valid configurable property.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16569: Oracle Data Guard configuration is not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The requested operation required that broker management of the Data Guard configuration must be enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enable the Oracle Data Guard configuration and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16570: database needs restart<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker operation required this database instance to be shut down and restarted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If DGMGRL or Enterprise Manager has not already done so, shut down the Oracle instance and then restart it.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16571: Oracle Data Guard configuration file creation failure<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker was unable to create the configuration file on permanent storage.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16572: Oracle Data Guard configuration file not found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker configuration file was either unavailable or did not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. For a RAC database, ensure that these initialization parameters are set to file locations that are shared by all instances of the RAC database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16573: attempt to change or access configuration file for an enabled broker configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation was rejected because the Oracle Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example: – An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running. – Non-broker access (such as DBMS_FILE_TRANSFER) to the configuration files was attempted. See the alert log for additional information.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Disable the broker configuration and shut down the Oracle Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16574: switchover disallowed when required databases are shut down<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Switchover failed because either the primary database or the designated standby database were shut down.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16575: LOG_ARCHIVE_DEST_n parameter conflicts with the new member to be added<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One or more LOG_ARCHIVE_DEST_n initialization parameters on existing members were already set for the new member to be added when attempting to add a standby database, far sync instance, Backup Appliance, or external destination to the configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Clear the LOG_ARCHIVE_DEST_n initialization parameter that specifies the standby database, far sync instance, Backup Appliance, or external destination to be added.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16576: failed to update Data Guard broker configuration file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A failure was encountered while the broker was updating the Oracle Data Guard broker configuration file on permanent storage.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16577: corruption detected in Data Guard configuration file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker detected errors while loading the configuration file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16578: failed to read Data Guard configuration file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A failure was encountered while the broker was reading the configuration file on permanent storage.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16582: cannot change instance-specific property<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change an instance-specific property for a member that had more than one instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the command and identify a specific instance whose property value is to be changed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16584: operation cannot be performed on a standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database specified for the operation was a standby database, or the operation was attempted on a standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the database type and retry the operation. If the command must be executed on a primary database, connect to the primary database and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16585: operation cannot be performed on a primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database specified for the operation was a primary database, or the operation was attempted on a primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the database type and retry the operation. If the command must be executed on a standby database, connect to a standby database and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16586: cannot change database property with EDIT INSTANCE command<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the EDIT DATABASE command to change database properties.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16587: ambiguous object specified to Data Guard broker<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An object was specified that the broker could not uniquely distinguish from other objects in the configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Try to further distinguish the object specified for the operation and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16589: Oracle Data Guard broker detected network transfer error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker detected an error while transferring data from one member to another. This may happen when either: – The broker detects an inconsistency in the block count of the configuration file when the file is transmitted between members. – The broker encounters an error when writing the configuration file. – A broker member receives an incorrect message from another member.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16594: DMON background process is not running<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker background process, DMON, was not running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the Oracle Data Guard broker log file and DMON process trace file to determine why the DMON process is not running.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16595: process\u00a0string<\/i>\u00a0failed to terminate<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified process did not terminate at the request of the Data Guard broker.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16596: member not part of the Oracle Data Guard broker configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified member was not in the Oracle Data Guard broker configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the command with a member that is in the broker configuration.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16597: Oracle Data Guard broker detects two or more primary databases<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker detected two or more primary databases in the broker configuration and could not continue.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16598: Oracle Data Guard broker detected a mismatch in configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more members in the broker configuration. This can occur when the primary database has stale broker configuration files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16599: Oracle Data Guard broker detected a stale configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Oracle Data Guard broker detected a stale configuration during initialization for this member.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The broker will automatically resolve this situation once the primary database completes its initialization.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16600: not connected to target standby database for failover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The failover command failed because the client was not connected to the target standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Explicitly connect to the standby database to be failed over to and retry the failover command.<\/span><\/span><\/p>\n

\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16400 to ORA-16600 ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST Cause:\u00a0Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined. Action:\u00a0No action is required. ORA-16401: archive log rejected by Remote File Server (RFS) Cause:\u00a0An attempt was made to re-archive an…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[54],"class_list":["post-2256","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-Ao","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2256","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=2256"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2256\/revisions"}],"predecessor-version":[{"id":2257,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2256\/revisions\/2257"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2256"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2256"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2256"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}