Oracle Database Errors or Warnings from Error ORA-16100 to ORA-16110
ORA-16100: not a valid Logical Standby database
Cause: This database has not been completely configured as a Logical Standby database.
Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.
ORA-16101: a valid start SCN could not be found
Cause: An SCN from which to start could not be found.
Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement.
ORA-16102: remote information is not available on the specified primary
Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.
Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.
ORA-16103: Logical Standby apply must be stopped to allow this operation
Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.
Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.
ORA-16104: Invalid Logical Standby parameter
Cause: The specified parameter is not valid.
Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package documentation for the correct statement syntax.
ORA-16105: Logical Standby is already running in background
Cause: A Logical Standby apply operation is already running.
ORA-16107: all log data from primary has been processed
Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.
Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
ORA-16108: database is no longer a standby database
Cause: The current database has already been made a primary database.
Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
ORA-16109: failed to apply log data from previous primary
Cause: Log data from previous primary could not be completely applied.
Action: . Then, re-issue command.
ORA-16110: user procedure processing of logical standby apply DDL
Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.
Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.
Above are list of Oracle Database Errors or Warnings from Error ORA-16100 to ORA-16110 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.