Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

 

LISTE CODE ERREURS ORACLE.

 

ORA-16600 ORA-16600: failover operation can only be submitted at target database
Cause  This error is returned when a failover request specified a different database than the database to which the client is currently connected.
Action  Explicitly connect to the database to which you wish to failover and reissue the failover request.

 

ORA-16601 ORA-16601: site contains required resources that are disabled
Cause  The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled.
Action  Enable all required resources and reissue the request.

 

ORA-16602 ORA-16602: object must be disabled to perform this operation
Cause  An attempt was made to edit a database object that can only be done while broker management of that database is disabled.
Action  Disable broker management of the database and reissue the request.

 

ORA-16603 ORA-16603: Data Guard broker detected a mismatch in configuration ID
Cause  The Data Guard broker for this database detected a mismatch in configuration Unique ID. This can occur if the original configuration was recreated while this database was disconnected from the network or the same database was added to two different broker configurations.
Action  Make sure the database belongs to only one broker configuration. Remove the Data Guard broker configuration files and restart the broker.

 

ORA-16604 ORA-16604: unable to describe template using package "string"
Cause  The Data Guard broker was unable to execute the OnDescribe function in the named package.
Action  Verify that the named package is loaded on the primary database. Also verify that the OnDescribe function is in the package.

 

ORA-16605 ORA-16605: unable to delete template, template is in use
Cause  The Data Guard broker was unable to delete the template because the template is still being used by one or more resources.
Action  Delete all resources using the template before deleting the template. You cannot delete the database template.

 

ORA-16606 ORA-16606: unable to find property "string"
Cause  The named property does not exist.
Action  Specify a valid property name and reissue the request.

 

ORA-16607 ORA-16607: one or more databases have failed
Cause  The Data Guard broker detected a failure for one or more databases in the Data Guard configuration.
Action  Locate the database(s) with a failure status and correct it.

 

ORA-16608 ORA-16608: one or more databases have warnings
Cause  The Data Guard broker detected a warning status for one or more databases.
Action  Locate the database(s) with a warning status and correct it.

 

ORA-16611 ORA-16611: operation aborted at user request
Cause  The Data Guard broker aborted an operation at the user"s request.
Action  No action required.

 

ORA-16612 ORA-16612: string value too long for attribute "string"
Cause  The string value for the named attribute is too long.
Action  Use a shorter string.

 

ORA-16613 ORA-16613: initialization in progress for database
Cause  The database received a directive to change its initialization state or a change in its configuration before it has completed initialization.
Action  Wait until the database has completed initialization before issuing requests to modify run-time state or configuration.

 

ORA-16614 ORA-16614: object has an ancestor that is disabled
Cause  A request to enable an object that has an ancestor that is disabled was received by the broker. The broker has enabled management of the object to the extent that it can, but cannot fully enable the object until its ancestor is enabled.
Action  Determine the ancestor object that is disabled and enable that ancestor prior to enabling the child object.

 

ORA-16617 ORA-16617: unknown object identifier specified in request
Cause  The Data Guard broker returned this error because the object identifier specified in the request was invalid or unknown. For example, this error is returned if an invalid or unknown database object identifier is specified in a request that requires a database object identifier.
Action  Verify that a valid object identifier was specified in the request and then reissue the request.

 

ORA-16618 ORA-16618: response document of size "string" bytes is too large
Cause  The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard broker log.
Action  View the broker log for the given database directly.

 

ORA-16619 ORA-16619: health check timed out
Cause  This status is returned when the Data Guard broker could not reach a standby database during a routine health check.
Action  This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame.

 

ORA-16620 ORA-16620: one or more databases could not be contacted for a delete operation
Cause  The Data Guard broker could not reach one or more standby databases for either a delete database operation or a delete broker configuration operation.
Action  This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database"s Data Guard broker log for to determine which standby databases could not be reached. Then for each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, dg_broker_start, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database"s dg_broker_config_file[1|2] parameter values and delete them.

 

ORA-16621 ORA-16621: database name for ADD DATABASE must be unique
Cause  An attempt was made to add a database to the broker configuration that already includes a database with the specified name. The database names must be unique.
Action  Verify that you have specified a unique name for the new database you wish to add. This can be done by checking that there is no database with the same name. Also note that the database name must match the DB_UNIQUE_NAME initialization parameter of the database.

 

ORA-16622 ORA-16622: two or more broker database objects resolve to one physical database
Cause  The Data Guard broker determined that there were multiple database objects referring to the same physical database.
Action  Examine the details of all databases in the broker configuration and verify that there are not two or more databases that indicate the same physical database. If you detect this situation, remove and readd the erroneously defined database(s) to resolve the ambiguity.

 

ORA-16623 ORA-16623: stale DRC UID sequence number detected
Cause  The Data Guard broker detected a stale sequence value during its bootstrap or health check operations. The sequence value is changed each time a switchover or failover operation completes successfully. A database that is unavailable to participate in the switchover or failover operation will end up with a stale sequence number. Should the database attempt to rejoin the broker configuration, the broker will determine that the database missed a role change and will disable its management of that database. The broker disables the database since it may no longer be a viable standby database for the new primary database.
Action  Examine the broker configuration for databases that were disabled and which may require re-creation..

 

ORA-16624 ORA-16624: broker protocol version mismatch detected
Cause  The broker detected a network protocol version number mismatch. This can happen if the databases in question are not at the same version of Oracle. The broker will disable management of the databases that do not have the same network protocol version number as the primary database.
Action  Examine the version of Oracle installed for all databases to make sure they are identical. Once the Oracle versions are the same for all databases, reenable the databases that had been disabled.

 

ORA-16625 ORA-16625: cannot reach the database
Cause  The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database.
Action  Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database.

 

ORA-16626 ORA-16626: failed to enable specified object
Cause  The broker failed to enable management of an object (most likely a standby database). You can expect to see this status when attempting to enable broker management of a standby database that:
Action  To correct the problem, try one of these actions:

 

ORA-16627 ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Cause  This status is returned in the following situations:
Action  - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.

 

ORA-16628 ORA-16628: the broker protection mode is inconsistent with the database setting
Cause  The Data Guard broker protection mode saved in the broker"s configuration file was inconsistent with the actual database setting.
Action  Reset the protection mode through the Data Guard broker.

 

ORA-16629 ORA-16629: database reports a different protection level from the protection mode
Cause  The actual protection level supported by the standby database was different from the protection mode set on the primary database. This was likely caused by redo transport problems.
Action  Check the database alert logs and Data Guard broker logs for more details. Check the redo transport status. Make sure at least one standby redo transport is supporting the protection mode and that the network to the standby database is working.

 

ORA-16630 ORA-16630: that database property was deprecated
Cause  The property that was specified in the user operation was a deprecated property.
Action  Check the broker documentation to identify a replacement property or issue a SQL command to achieve the same result if no such replacement property exists.

 

ORA-16631 ORA-16631: operation requires shutdown of database/instance "string"
Cause  The Data Guard broker operation requires a shutdown of the database or instance.
Action  If the client has not yet done so, please shutdown all Oracle instances for the database.

 

ORA-16632 ORA-16632: instance being added to database profile
Cause  The Data Guard broker determined that an instance has successfully found its database profile within the broker configuration file, but yet lacks an instance-specific profile. The broker automatically creates an instance-specific profile and associates the instance with its database profile.
Action  No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance in broker activity.

 

ORA-16633 ORA-16633: the only instance of the database cannot be removed
Cause  The instance to be removed was the only instance of the corresponding database that is known to the broker.
Action  Remove the corresponding database object from the broker configuration instead of that individual instance object of the database.

 

ORA-16635 ORA-16635: NetSlave connection was broken in the middle of a transmission session
Cause  The Data Guard NetSlave process detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (e.g. the broker configuration file) to the remote database. This error implies the transmission has to be restarted from the beginning.
Action  In most cases, no user action is required. The Data Guard broker always tries to resend the data from the beginning. If the problem persists, the user will eventually see this error reported. This will indicate there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and address the actual problem.

 

ORA-16636 ORA-16636: Fast-Start Failover target standby in error state, cannot stop observer
Cause  A STOP OBSERVER operation could not be completed when Fast-Start Failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.
Action  Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps you identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. You may correct the problem that is indicated by that information and retry the operation. Alternatively, you may forcibly disable Fast-Start Failover while connected to the primary database using the DISABLE FAST_START FAILOVER FORCE command in the DGMGRL CLI. You can then stop the observer regardless of the current state of the target standby database.

 

ORA-16637 ORA-16637: an instance failed to access the Data Guard broker configuration
Cause  When an instance was started, the DMON process on the instance failed to access the Data Guard broker configuration. This can happen if the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters are not set up correctly to point to the broker configuration files shared among all instances.
Action  Set DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 to the correct file specifications that point to the broker configuration files shared among all instances. Bounce the DMON process by setting DG_BROKER_START initialization parameter to FALSE and then to TRUE.

 

ORA-16638 ORA-16638: could not get the instance status
Cause  The broker failed to check whether the given instance was alive or not.
Action  See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.

 

ORA-16639 ORA-16639: specified instance inactive or currently unavailable
Cause  An attempt was made to perform an operation on an instance that was not running or was unavailable.
Action  Ensure that the instance specified in the operation is running and then retry the operation.

 

ORA-16640 ORA-16640: CRS warns that multiple instances may still be running
Cause  A broker operation was underway that required CRS to stop monitoring the instances of this database and to shut down all but one instance. Although instance monitoring has ceased, CRS cannot guarantee that only one instance remains running. The broker operation was canceled.
Action  Suspend CRS management of this database using SRVCTL STOP DATABASE -D 'name' -O NONE. Then reissue the broker request.

 

ORA-16641 ORA-16641: failure to acquire broker configuration metadata lock
Cause  Internal error
Action  Contact Oracle Support Services.

 

ORA-16642 ORA-16642: db_unique_name mismatch
Cause  The expected db_unique_name value did not match the actual db_unique_name value for the database that the broker contacted using the connect identifier that was associated with that database.
Action  Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database that the broker expects to find via that connect identifier matches the actual db_unique_name for that database.

 

ORA-16643 ORA-16643: unable to determine location of broker configuration files
Cause  The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Action  Retry the operation and if the error persists, contact Oracle Support Services.

 

ORA-16644 ORA-16644: apply instance not available
Cause  The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.
Action  Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.

 

ORA-16645 ORA-16645: unexpected new instance interrupted current operation
Cause  A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically.
Action  Reissue the operation after the new instance has joined the Data Guard configuration.

 

ORA-16646 ORA-16646: Fast-Start Failover is disabled
Cause  The operation was not allowed because Fast-Start Failover is disabled.
Action  Enable Fast-Start Failover and retry the operation.

 

ORA-16647 ORA-16647: could not start more than one observer
Cause  The observer could not start because there was another observer already observing the Data Guard configuration for which Fast-Start Failover may have been enabled.
Action  Stop the running observer. Retry the operation.

 

ORA-16648 ORA-16648: a new observer registered with identifier string
Cause  The observer is registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a Fast-Start Failover.
Action  None

 

ORA-16649 ORA-16649: database will open after Data Guard broker has evaluated Fast-Start Failover status
Cause  The database is being opened while Fast-Start failover is enabled. The message indicates that the Data Guard broker will first determine if conditions are suitable for opening; that is, a Fast-Start failover did not occur while the database was unavailable.
Action  No action is normally required. The Data Guard broker will continue opening the database after determining a Fast-Start failover did not occur. If there is a chance that a Fast-Start Failover did occur, the database will remain in the mounted state and will not open. In this case, check the target standby to see if a role transition took place.

 

ORA-16650 ORA-16650: command incompatible when Fast-Start Failover is enabled
Cause  An attempt was made to issue a command which is not permitted when Fast-Start Failover is enabled. The command was not issued using the Data Guard broker.
Action  The attempted command must be issued using the Data Guard broker.

 

ORA-16651 ORA-16651: requirements not met for enabling Fast-Start Failover
Cause  The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met:
Action  Retry the attempted command after correcting the issue:

 

ORA-16652 ORA-16652: Fast-Start Failover target standby database is disabled
Cause  The command to enable or disable Fast-Start Failover could not be completed because Data Guard broker management of the Fast-Start Failover target standby database is currently disabled.
Action  Enable broker management of the target standby database and reissue the command. If you are attempting to disable Fast-Start Failover when this error is reported, you may opt to disable Fast-Start Failover with the FORCE option. See the description for DGMGRL"s DISABLE FAST_START FAILOVER [FORCE] command for more information.

 

ORA-16653 ORA-16653: failed to reinstate database
Cause  The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled.
Action  Additional information about this failure is recorded in the primary database"s and/or the specified database"s Data Guard broker log files. This information will be helpful in determining how to proceed.

 

ORA-16654 ORA-16654: Fast-Start Failover is enabled
Cause  The attempted command was not allowed while Fast-Start Failover (FSFO) was enabled:
Action Disable Fast-Start Failover, using the FORCE option if required. Then retry the attempted command.

 

ORA-16655 ORA-16655: specified target standby database invalid
Cause  The attempted command was not allowed because Fast-Start Failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database.
Action  Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, you may disable Fast-Start Failover. You may then retry the command while specifying the originally specified target standby database.

 

ORA-16656 ORA-16656: higher DRC UID sequence number detected
Cause  The Data Guard broker detected a higher sequence value during its bootstrap or health check operations. The sequence value is changed each time switchover or failover completes successfully.
Action  Additional information about this failure is recorded in the Data Guard "broker log" files, one for the primary database and one for each standby database in the Data Guard configuration. This information will be helpful in determining how best to proceed from this failure.

 

ORA-16657 ORA-16657: reinstatement of database in progress
Cause  Reinstatement of this database was in progress.
Action  No action is necessary.

 

ORA-16658 ORA-16658: unobserved Fast-Start Failover configuration
Cause  The Fast-Start Failover configuration was currently unobserved so failover was disallowed.
Action  Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable Fast-Start Failover to allow a failover in the absence of the observer process.

 

ORA-16659 ORA-16659: failover operation in progress
Cause  A primary database that restarted contacted a standby database that is being failed over to.
Action  Shutdown the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to Fast-Start Failover, restarting the primary database after failover is complete will allow it to be automatically reinstated as a standby database to the new primary database.

 

ORA-16660 ORA-16660: FSFO operation attempted in absence of a broker configuration
Cause  An attempt was made to enable or disable Fast-Start Failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands.
Action 1) An attempt to enable or disable (non-FORCE) Fast-Start Failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database"s DMON process from the primary"s DMON process. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database.
2) You may use the FORCE option to override Fast-Start Failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that FSFO is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other at a later point in time and if the state of Fast-Start Failover had been altered at the primary database in the meantime.

 

ORA-16661 ORA-16661: the standby database needs to be reinstated
Cause  A switchover or failover operatione has caused this database to require reinstatement.
Action  Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database.

 

Haut de Page www.dba-ora.fr

Partager cette page

Repost 0
Published by