ORA-16262: Invalid value specified for Logical
Standby parameter
Cause:
The value specified in APPLY_SET is invalid for the parameter.
Action:
Specify correct parameter value. Please refer to documentation on DBMS_LOGSTDBY
PL/SQL package for details.
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.
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.
ORA-16400: quota attributes are not allowed with
DB_RECOVERY_FILE_DEST
Cause:
Quota attributes for the destination parameters are not allowed when the
parameter DB_RECOVERY_FILE_DEST is defined.
Action:
No action is required.
ORA-16401: archivelog rejected by RFS
Cause:
An attempt was made to re-archive an existing archivelog. This usually happens
because either a multiple primary database or standby database(s) or both are
trying to archive to this standby database.
Action:
See 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.
ORA-16402: ONDEMAND archival requires FAL_CLIENT
and FAL_SERVER support
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the
primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the
corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER
initialization parameters.
Action:
Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are
explicitly specified on the standby database that received this error.
ORA-16403: shutdown in progress - remote connection
is not permitted
Cause:
The SHUTDOWN command was used to shut down a running remote primary or standby
ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.
Action:
Wait for the remote instance to be restarted, or contact your DBA.
ORA-16406: Primary and standby database software
version mismatch
Cause:
The primary database and standby database Oracle software is not compatible.
Action:
Install the correct Oracle software and try again.
ORA-16407: Standby database is in the future of the
archive log
Cause:
An archive log, from a different Redo Branch, was received by a standby
database that has applied Redo in the future of Redo contained within the
archive log. The standby database has rejected the REDO Branch archive logs.
Action:
No action is required.
ORA-16408: Incompatible archival Redo Branch lineage
Cause:
An archive log, from an incompatible different Redo Branch, was received by a
standby database. The standby database has rejected the Redo Branch archive
logs.
Action:
No action is required.
ORA-16409: Archive log switchover reference number
mismatch
Cause:
The archive log switchover reference numbers of the Primary and Standby
database do not match. Remote archival of redo log files is not allowed to
incompatible STANDBY database instances.
Action:
No action is required.
ORA-16411: ONDEMAND archival requires active
managed recovery operation
Cause:
The use of the ONDEMAND attribute for a physical standby database destination
requires that the managed recovery operation be active prior to establishing
the network connection.
Action:
Start the managed recovery operation on the standby database.
ORA-16412: ONDEMAND archival requires active SQL
apply operation
Cause:
The use of the ONDEMAND attribute for a logical standby database destination
requires that the SQL apply operation be active prior to establishing the
network connection.
Action:
Start the SQL apply operation on the standby database.
ORA-16413: Unsupported database type for ONDEMAND
archivelog destinations
Cause:
The use of the ONDEMAND attribute for a standby database destination is
supported for only physical and logical standby database types.
Cross-Instance-Archival and repository database types are not valid for the
ONDEMAND attribute.
Action:
Verify the database corresponding to the archivelog destination is either a
physical standby database or a logical standby database.
ORA-16416: Switchover target is not synchronized
with the primary
Cause:
The switchover target incurred an error or has a gap at the time the switchover
operation was attempted.
Action:
Allow the switchover target to become synchronized and then re-attempt the
switchover.
ORA-16417: Activation occurred after recovery from
standby redo log files; a full database backup is required
Cause:
Activation occurred after recovery from standby redo log files.
Action:
Take a full database backup.
ORA-16419: Snapshot standby must be converted from
physical standby
Cause:
The database is not physical standby.
Action:
Convert to physical standby and retry the operation.
ORA-16420: fast-start failover target cannot be
converted to snapshot standby
Cause:
The database chosen for conversion to a snapshot standby was the fast-start
failover target standby database.
Action:
Choose another physical standby database and retry the operation.
ORA-16424: Terminal recovery cannot start due to
GAP on Physical Standby
Cause:
Terminal Recovery failed because of gap behind the start point of standby
recovery.
Action:
Issue ALTER DATABASE ACTIVATE STANDBY DATABASE
ORA-16425: Terminal recovery branch string
older than target branch string
Cause:
Terminal Recovery failed because of new branch on Physical Standby.
Action:
Issue 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 terminal recovery. Otherwise, issue ALTER DATABASE ACTIVATE
STANDBY DATABASE
ORA-16426: log requested by recovery is not the
correct log
Cause:
Media recovery has selected an incorrect log
Action:
Verify that the proper log has been properly registered and restart media
recovery.
ORA-16427: Potential archive log gap too large to
service
Cause:
Standby destination is too far behind the primary database for automatic
archive log gap detection/resolution to take place.
Action:
Standby database should be recreated with a recent backup copy of the primary
database.
ORA-16431: Cannot expand control file
Cause:
More threads were added on the primary database after this standby control file
was created.
Action:
Shut down the standby database, either replace the control file with a new
standby control file from primary database or change the COMPATIBLE parameter
to 10.2.0 or above, and restart the standby database.
ORA-16432: inconsistent set of terminal logs
detected
Cause:
Media Recovery stopped because it detected an inconsistency between the first
log in the new incarnation and the state of the previous incarnation. If this
database is a bystander standby database, this is most likely because there was
a failover operation, and this database applied terminal logs generated from
that failover operation for some redo threads but applied corresponding logs
from the old primary database of that failover operation for some other redo
threads.
Action:
Flashback or restore this database to before the standby_became_primary_scn of
that failover operation and restart media recovery. The
standby_became_primary_scn of the failover operation can be obtained from
V$DATABASE on the new primary.
ORA-16433: The database has not been opened in
read-write mode
Cause:
When a physical standby database is converted to a read-write database or there
was a failed open resetlogs attempt, the database should be opened in
read-write mode to have correct file access information in the controlfile.
Action:
Open the database in read-write mode and reissue the command.
ORA-16438: Switchover to primary cannot be executed
at this time
Cause:
ALTER 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.
Action:
Wait 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.
ORA-16501: the Data Guard broker operation failed
Cause:
The Data Guard broker operation failed.
Action:
See accompanying messages for details.
ORA-16502: the Data Guard broker operation
succeeded with warnings
Cause:
The Data Guard broker operation succeeded with warnings.
Action:
See accompanying messages for details.
ORA-16504: the Data Guard configuration already
exists
Cause:
A request to create a Data Guard configuration was made while connected to a
database that is part of an existing configuration.
Action:
To create a new configuration, the existing configuration must be deleted.
ORA-16505: site ID is invalid
Cause:
The request contained an invalid site ID.
Action:
Make the request again with a valid site ID.
ORA-16506: out of memory
Cause:
Process exceeded private or shared memory limits.
Action:
Check for memory leaks, increase system parameters and restart.
ORA-16507: unrecognized request identifier
Cause:
The specified request identifier was not recognized by the Data Guard broker.
Action:
Reissue the request using a valid request identifier.
ORA-16509: request timed out
Cause:
The Data Guard broker timed out out the request.
Action:
Check the Data Guard broker log file for more information. Ensure that the
network connections between the databases are functioning properly and retry
the request.
ORA-16513: maximum requests exceeded
Cause:
The maximum number of requests that the broker can service
Action:
Wait for the broker to complete processing the requests before issuing more
requests.
ORA-16514: request was not found
Cause:
An attempt was made to read a response but a matching request was not found.
Action:
Verify request identifier is valid and that it references a previously issued
request.
ORA-16516: current state is invalid for the
attempted operation
Cause:
The 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 are shut down.
- The primary
database is not shipping redo data.
- The standby
database that will become the primary database is not applying redo data. If
this error was returned for database state change operations, the database
state specified was invalid.
Action:
If this error is returned when attempting a switchover operation, make sure
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, make sure a valid database state is specified.
ORA-16523: operation requires the client to connect
to instance "string"
Cause:
The switchover or failover operation required the client to connect to the
apply instance of the target database.
Action:
Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER
command.
ORA-16524: unsupported operation
Cause:
A command or option was not supported in this release.
Action:
Contact Oracle Support Services.
ORA-16525: the Data Guard broker is not yet available
Cause:
The Data Guard broker process was either not yet started, was initializing, or
failed to start.
Action:
If 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 Data Guard log for possible
errors. Otherwise, retry the operation.
ORA-16526: unable to allocate task element
Cause:
The Data Guard broker was unable to allocate memory for a request.
Action:
Increase the size of the SGA.
ORA-16527: unable to allocate broker SGA memory
Cause:
The Data Guard broker was unable to allocate memory within the SGA.
Action:
Increase the size of the SGA memory.
ORA-16528: unable to allocate PGA memory
Cause:
There was insufficient space in PGA to allocate memory.
Action:
Increase process virtual memory.
ORA-16530: invalid buffer or length
Cause:
A NULL buffer or a length of zero was specified.
Action:
Correct the command parameters and retry the command.
ORA-16532: Data Guard broker configuration does not
exist
Cause:
A broker operation was requested that required a broker configuration to
already be created.
Action:
Create a Data Guard broker configuration prior to performing other broker
operations.
ORA-16534: no more requests accepted
Cause:
The Data Guard broker returned this status because either:
- A failover
operation was submitted or was in progress.
- A switchover
operation was submitted or was in progress.
- An instance
restart was pending for one or more databases.
Action:
Wait until the operation is complete and reissue the request.
ORA-16535: CRS is preventing execution of a broker
operation
Cause:
The broker was unable to have CRS stop management of all of the instances of
this database.
Action:
Suspend CRS management of this database using the SRVCTL STOP DATABASE -D
<name> -O NONE command. Then reissue the broker request.
ORA-16541: database is not enabled
Cause:
The database specified in the request was not enabled.
Action:
Select an enabled database and reissue the request.
ORA-16544: modifying DG_BROKER_START requires
SID='*' qualifier
Cause:
The 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.
Action:
Reenter the command using the SID='*' qualifier.
ORA-16545: unable to get response
Cause:
The Data Guard broker was unable to return the result of a previous request.
Action:
Contact Oracle Support Services.
ORA-16546: missing or invalid value
Cause:
The value of the request to return was not specified or was invalid.
Action:
Specify the value of the response starting from one.
ORA-16547: cannot disable or delete the primary
database
Cause:
An attempt was made to disable broker management of the primary database or
delete the primary database from the broker configuration while the
configuration was enabled.
Action:
If 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 delete the primary database from
the broker configuration while the configuration is enabled, you must instead
delete the entire broker configuration.
ORA-16548: database not enabled
Cause:
An attempt was made to modify or query a disabled database. This error is also
returned on an attempt to enable, modify, or query a database that the broker
has disabled because of a switchover or failover operation. The broker disables
its management of a database when it detects that the database needs to be
re-created because of a failover or switchover operation.
Action:
If broker management of the database is disabled, enable it and reissue the
request.
ORA-16549: invalid string
Cause:
An invalid or NULL string value was specified.
Action:
Correct command parameters and retry.
ORA-16550: truncated result
Cause:
A string property value was truncated due to insufficient buffer size.
Action:
Specify a larger receive buffer.
ORA-16551: short string copied
Cause:
A string property value that did not fill the receive buffer was placed in the
receive buffer.
Action:
This is an informational message only.
ORA-16552: an error occurred when generating the
CLIENT OPERATION table
Cause:
An error occurred while Data Guard broker was generating the CLIENT OPERATION
table.
Action:
See the next error message for more detailed information. Execute the action
described in the next error or contact Oracle Support Services.
ORA-16555: database is not active
Cause:
An operation was attempted on a database that was not active. not active.
Action:
Verify that the database is active and retry the operation.
ORA-16556: observer version mismatch
Cause:
This 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.
Action:
Use a version of the observer that is compatible with the Oracle database
server to be observed.
ORA-16557: database is already in use
Cause:
An attempt was made to create a duplicate database in the broker configuration.
Action:
Check the database to be added to ensure there are no duplicates.
ORA-16558: database specified for switchover is not
a standby database
Cause:
An attempt was made to switchover to a database that was not a standby
database.
Action:
Locate an enabled standby database and select that database as the target of
the switchover.
ORA-16561: cannot remove an active instance
Cause:
The instance to be removed was running.
Action:
Shut down the instance and reissue the REMOVE command.
ORA-16568: cannot set property string
Cause:
The specified property could not be modified because it was either a
monitorable property or a property that did not exist.
Action:
Retry the command with a valid configurable property.
ORA-16569: Data Guard configuration is not enabled
Cause:
The requested operation required that broker management of the Data Guard
configuration must be enabled.
Action:
Enable the Data Guard configuration and reissue the request.
ORA-16570: database needs restart
Cause:
The Data Guard broker operation required this database instance to be shut down
and restarted.
Action:
If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle
instance and then restart it.
ORA-16571: Data Guard configuration file creation
failure
Cause:
The Data Guard broker was unable to create the configuration file on permanent
storage.
Action:
Verify space, permissions and file name as indicated by the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
ORA-16572: Data Guard configuration file not found
Cause:
The Data Guard broker configuration file was either unavailable or did not exist.
Action:
Verify 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.
ORA-16573: attempt to change or access
configuration file for an enabled broker configuration
Cause:
The operation was rejected because the 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.
Action:
Disable the broker configuration and shut down the 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.
ORA-16574: switchover disallowed when required
databases are shut down
Cause:
Switchover failed because either the primary database or the designated standby
database were shut down.
Action:
Ensure 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.
ORA-16575: request terminated at broker discretion
Cause:
This error was returned when the broker terminated a command because it was
processing a failover command.
Action:
Wait for failover to complete and then retry the command.
ORA-16576: failed to update Data Guard
configuration file
Cause:
A failure was encountered while the broker was updating the Data Guard broker
configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16577: corruption detected in Data Guard
configuration file
Cause:
The Data Guard broker detected errors while loading the configuration file.
Action:
Verify space, permissions and file name as indicated by the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support
Services.
ORA-16578: failed to read Data Guard configuration
file
Cause:
A failure was encountered while the broker was reading the configuration file
on permanent storage.
Action:
Verify space, permissions and file name as indicated by the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16582: cannot change instance-specific property
Cause:
An attempt was made to change an instance-specific property for a database that
had more than one instance.
Action:
Retry the command and identify a specific instance whose property value is to
be changed.
ORA-16586: cannot change database property with
EDIT INSTANCE command
Cause:
An attempt was made to change a database property using an EDIT INSTANCE
command instead of an EDIT DATABASE command.
Action:
Use an EDIT DATABASE command to change database properties.
ORA-16587: ambiguous object specified to Data Guard
broker
Cause:
An object was specified that the broker could not uniquely distinguish from
other objects in the configuration.
No hay comentarios:
Publicar un comentario