Oracle Database Errors or Warnings from Error ORA-16273 to ORA-16282


ORA-16273: invalid value for APPLY_SERVERS parameter
Cause: attempt to set APPLY_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.
Action: set APPLY_SERVERS parameter to a non zero value or increase MAX_SERVERS parameter accordingly.
ORA-16274: failure to perform DDL on all RAC instances
Cause: One or more instances encountered an error while performing an operation.
Action: Ensure every instance in the RAC meets the requirements for the operation, and retry the operation.
ORA-16275: prior failed CTAS detected and pre-existing table dropped
Cause: During the processing of a CTAS operation, an existing empty table with the same name and attributes as the CTAS source table was found, and the table was dropped.
Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16276: specified database link does not correspond to primary database
Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did not link to the primary database for this logical standby database.
Action: Specify a database link that corresponds to the primary database for this logical standby database. The link should have privileges to read and lock the table being instantiated, as well as the SELECT_CATALOG_ROLE.
ORA-16277: specified table is not supported by logical standby database
Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate an unsupported table on the logical standby database. Tables with unsupported data types cannot be replicated to a logical standby database.
Action: Specify a table which is not listed in the DBA_LOGSTDBY_UNSUPPORTED_TABLE view.
ORA-16278: specified table has a multi-object skip rule defined
Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE must not have any skip rules defined with wildcard characters.
Action: Remove or rewrite any skip rules defined for the specified table so that they no longer contain wildcard characters, or no longer affect the specified table.

ORA-16279: Supplied dblink must have CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles
Cause: A dblink was specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE that lacked one or more of the CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles.
Action: Grant the CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles to the specified dblink, and retry the operation.
ORA-16280: cannot change master key on a logical standby database
Cause: An attempt was made to change the master key for transparent data encryption on a logical standby database.
Action: Set GUARD to NONE and reissue the command. This prevents you from replicating tables with encrypted columns from the primary database.
ORA-16281: missing identification key for table “string”.”string”.
Cause: No identification key was created for specified table.
Action: Create a primakey key or unique index for specified table.
ORA-16282: operation not permitted during rolling upgrade
Cause: An operation was attempted that is not supported during a rolling upgrade.
Action: Retry the operation upon completion of the upgrade.

Above are list of Oracle Database Errors or Warnings from Error ORA-16273 to ORA-16282 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.

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 *