Oracle Database Errors or Warnings from Error ORA-16213 to ORA-16220
ORA-16213: ddl encountered, stopping apply engine
Cause: stop_on_ddl callout specified and DDL was encountered.
Action: Either disable stop_on_ddl callout or remove DDL.
ORA-16214: apply stalled for apply delay
Cause: A delay has been specified on the primary database for this destination.
Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET(‘APPLY_DELAY’); to override.
ORA-16215: history metadata inconsistency
Cause: internal error.
Action: This is an internal error. Contact Oracle support.
ORA-16216: Log stream sequence error
Cause: The log stream being processed did not follow the last processed stream.
Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream.
ORA-16217: prepare to switchover has not completed
Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.
Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby.
ORA-16218: This database is already preparing to switch over.
Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt.
Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.
ORA-16219: This database is not preparing to switch over.
Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.
Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.
ORA-16220: no failed transaction found
Cause: No failed transaction was found.
Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.
Above are list of Oracle Database Errors or Warnings from Error ORA-16213 to ORA-16220 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.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.