Oracle Database Errors or Warnings from Error ORA-16263 to ORA-16272

SQLServerF1

ORA-16263: Dynamic parameters can only be set on SQL apply instance
Cause: Attempt to set a Logical standby dynamic parameter on an instacne other than where SQL apply coordinator is running.
Action: Connect to the instance where SQL apply coordinator is running and re-issue the statement.
ORA-16264: invalid value for PREPARE_SERVERS parameter
Cause: attempt to set PREPARE_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.
Action: set PREPARE_SERVERS parameter to a non zero value and or increase MAX_SERVERS parameter accordingly.
ORA-16265: Unsupported PL/SQL procedure encountered
Cause: Apply encountered an unsupported procedure from an Oracle supplied PL/SQL package that is otherwise supported
Action: Either add a skip rule for this procedure or manually apply the procedure and restart apply skipping the failed transaction Please refer to documentation on the PL/SQL package for details.

ORA-16266: Cannot instantiate a Logical Standby from another Logical Standby
Cause: An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported.
Action: Instantiate a Logical Standby database only from a Primary Database.
ORA-16267: Cannot instantiate a Logical Standby during a switchover
Cause: An instantiation of a Logical Standby has been attempted for a primary database that is in the middle of a switchover.
Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel the switchover, and attempt the instantiation again.
ORA-16268: user procedure processing of logical standby apply PL/SQL
Cause: A user-provided stored procedure was called to inspect a PL/SQL statement prior to the statement 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.

ORA-16269: PL/SQL procedure skipped due to failure on primary database
Cause: Because the PL/SQL procedure failed when executed on the primary database, it could not be executed on the standby database.
Action: This informational statement is provided to record the event for diagnostic purposes. The failed PL/SQL procedure needs to be investigated to ensure it did not commit interesting data before it failed.
ORA-16270: PL/SQL procedure skipped due to unmaintained standby objects
Cause: Because the PL/SQL procedure manipulated objects not being maintained by the standby database, it was skipped.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
ORA-16271: PL/SQL successfully applied
Cause: A PL/SQL procedure was successfully applied on the logical standby database.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
ORA-16272: PL/SQL procedure skipped due to skip setting
Cause: A setting in the logical standby skip table indicated that this PL/SQL procedure should always be skipped.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

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