ORA User initiated shut down successfully completed Cause: Logical standby was shutdown in an orderly fashion. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. ORA supplemental log information is missing from log stream Cause: Supplemental logging is not enabled at the primary database. Cause: An error occurred during a Terminal Recovery of the standby.
Action: Check the standby alert log additional information. ORA An error occurred during activation of the standby. Cause: An error occurred during activation of the standby database following a Terminal Recovery. ORA Datafile string has incorrect terminal recovery stamp. Cause: After activation of a standby database following a terminal recovery recovery of standby using current logs , recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.
Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery. ORA terminal recovery could not find log for thread string seq string. Action: Check that the standby current logs are in the correct location. ORA Managed Standby Recovery not active Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.
ORA No terminal recovery is required Cause: All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required. The standby database may be activated as a new primary or may continue as a standby. ORA end of log stream not received from primary Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible. Action: Verify that the primary log stream has been terminated.
Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command. ORA media recovery required Cause: The database has not been recovered through the end of log stream.
Graceful switchover is not possible. Action: Ensure that the entire log stream has been applied. If appropriate, re-issue the graceful switchover command. ORA standby online logs have not been recovered Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs. Action: The primary must not attempt to archive to the standby after a terminal recovery.
ORA archival for thread string sequence string in progress Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived. This indicates that the target destination is the primary database itself.
Action: Check for and eliminate the standby destination archive log parameter in question. ORA standby database referenced by multiple archive log destinations Cause: Multiple archive log destinations reference the same standby database, using different service names.
Action: Remove one of the duplicate archive log destinations. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.
Action: Wait for the managed standby recovery session to end. ORA standby database is in 'no-data-loss' protected mode Cause: The attempted database operation is not allowed while the standby database is in 'no-data-loss' protected mode. ORA suspect attribute: string Cause: Use of the indicated attribute is illegal in the given context.
Action: Make the appropriate changes and re-issue the statement. ORA LGWR archive log dependency not allowed if database is standby protected Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files. Another media recovery is not allowed.
ORA Cannot change protected standby database configuration Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary database is opened. ORA Cannot mix standby and online redo log file members for group string Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group. ORA Cannot add new standby databases to protected configuration Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.
Action: The alert log contains more problem-specific information. ORA Parallel terminal recovery may lose more data than necessary Cause: Serial terminal recovery can always recover the standby database to the last consistent point in the redo stream.
Parallel terminal recovery cannot. Action: Retry with serial terminal recovery. Action: Copy missing archived logs from primary or another standby. ORA incompatible archival network connections active Cause: One of two situations can cause this error: An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected.
An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server RFS process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.
Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation. ORA cannot shut down database when media recovery is active Cause: An attempt was made to shut down a standby database while media recovery was active. Action: Cancel media recovery to proceed with the shutdown. ORA Terminal recovery failed to recover to a consistent point Cause: See alert log for more details.
Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, then contact Oracle Support Services. ORA Skip procedure requested to skip statement Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.
ORA Skip procedure requested to apply statement Cause: Logical standby called a skip procedure that requested for a particular statement to be applied. ORA Skip procedure requested to replace statement Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement. ORA Unable to interpret skip procedure return values Cause: The skip procedure returned conflicting or invalid values.
A Logical Standby database is not capable of processing the requested operation. Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request. ORA Logical standby dictionary build not permitted. Cause: A dictionary build is currently in progress. Only one build can be active at a time.
Action: Wait for the active build to complete before invoking a new build. ORA Logical standby dictionary build failed to start. Cause: Failure to start the logical standby dictionary build process LSP1. Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages.
Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found. ORA Logical standby dictionary build failed to complete. Cause: The logical standby dictionary build process terminated abnormally.
ORA Logical standby coordinator process terminated with error Cause: The logical standby coordinator process terminated abnormally. ORA unsupported record found in the archived redo log Cause: Log apply services encountered a record in the archived redo log that could not be interpreted. Provide the log file to Oracle Support Services. ORA apply stalled for apply delay Cause: A delay has been specified on the primary database for this destination.
Action: See other messages for details. Action: Delete unused sites. ORA the Data Guard configuration already exists Cause: A request to create a Data Guard configuration was made on a site that is part of an existing configuration.
Action: Delete the existing configuration if you desire to create a new configuration. Action: Make the request again with a valid site ID.
ORA out of memory Cause: Process exceeded private or shared memory limits. Action: Check for memory leaks, increase system parameters, and restart. ORA unrecognized request identifier Cause: The specified request identifier was not recognized by the Data Guard broker. Action: Re-issue the request using a valid request identifier.
ORA channel handle not initialized Cause: This is an internal error. Action: Contact Oracle Support Services. ORA the request timed out Cause: This is an internal error. ORA messaging error using ksrwait Cause: This is an internal error. ORA messaging error using ksrget Cause: This is an internal error. ORA parameter exceeded maximum size limit Cause: This is an internal error. ORA maximum requests exceeded Cause: Non-blocking commands were issued but responses are not read or the commands did not complete execution.
Action: Read pending responses or delete outstanding requests and try again. ORA the 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 references a previously issued request. ORA no rcv channel Cause: This is an internal error.
ORA the resource state is invalid for the attempted operation Cause: The broker will return this error for switchover operations and for resource state change operations.
If this error is returned for a switchover operation, then the broker has determined that either: The sites changing roles are offline. The primary database is not shipping log files. The standby database that will become the primary is not applying log files.
The broker returns this error for resource state change operations if the resource state specified is invalid for the resource. Action: If this error is returned when attempting a switchover operation, then make sure that: The sites changing roles are online. The primary database is shipping log files. The standby database is applying log files. If this error is returned when attempting a resource state change operation, then make sure you specify a valid state for the resource.
ORA the object handle is invalid Cause: This is an internal error. ORA unable to allocate virtual instance id Cause: This is an internal error. ORA the resource handle is invalid Cause: This is an internal error. ORA unable to allocate resource id Cause: This is an internal error. ORA unable to create generic template id Cause: This is an internal error. ORA generic template not found Cause: This is an internal error.
ORA property count exhausted Cause: Total number of resource properties exceeded the limit. ORA unsupported operation Cause: A command or option is not supported in this release.
ORA the Data Guard broker is not yet available Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start. If the broker failed to start, then check the Data Guard log for possible errors.
Otherwise, retry the operation. Action: Increase the size of your SGA. Action: Increase SGA memory. Action: Increase process virtual memory. ORA bad sender id Cause: This is an internal error. Action: Correct command parameters and retry. ORA unable to post message Cause: This is an internal error. Action: Create a DRC prior to issuing other requests. ORA no more requests accepted Cause: The Data Guard broker returns this status when: A failover operation has been submitted or is currently in progress A switchover operation has been submitted or is currently in progress An instance restart is pending for one or more sites Action: Wait until the operation is complete and then re-issue the request.
ORA failover request rejected Cause: This is an internal error. ORA unknown object type Cause: This is an internal error. ORA child count exceeded Cause: This is an internal error. ORA no match on requested item Cause: The Data Guard broker did not recognize the specified property or state name. Action: Verify command parameters and re-issue the request. ORA task element not found Cause: This is an internal error. ORA invalid argument Cause: One of the arguments for the specified request is invalid for the request type.
In the case of failover, the failover level must be specified. That is, a graceful failover or a forced failover. Action: Verify arguments and then re-issue the request. ORA site is not enabled Cause: The site specified in the request is not enabled. Action: Select an enabled site and re-issue the request. ORA unrecognized operation Cause: This is an internal error. ORA invalid request made to broker Cause: This is an internal error.
ORA missing or invalid piece Cause: The piece of the request to return was not specified or is invalid. Action: Specify the piece of the response starting from 1. This error is also returned on an attempt to enable, modify, or query a resource that the broker has permanently disabled.
A permanently disabled resource cannot be re-enabled. The broker permanently disables site resources when it detects that the database on that site needs to be reinstantiated. Action: If the resource is not permanently disabled, enable the resource and re-issue the request. ORA truncated result Cause: A string property value was truncated due to insufficient buffer size.
Action: Specify a larger recieve buffer. ORA short string copied Cause: This is an internal error. ORA translation not valid Cause: This is an internal error. ORA the Data Guard resource is not active Cause: An operation was attempted on a resource that is currently not active off path. Action: Verify that the resource is active. ORA the resource is already in use Cause: An attempt was made to create a duplicate resource. Action: Check the resource to be added and be sure there are no duplicates.
ORA the site specified for switchover is not a standby Cause: An attempt was made to switchover to a site that is not a standby site. Action: Locate an enabled standby site and select that site as the target of the switchover.
ORA out of memory at string Cause: This is an internal error. ORA unable to convert document, syntax error at "string" Cause: There was an error at the given token. Action: Correct the errors and resubmit the request. ORA unable to add value, syntax error at "string" Cause: There was an error at the given token.
ORA lookup failed, syntax error at string Cause: There was an error at the given token. ORA duplicate property, syntax error at "string" Cause: There was an error at the given token. ORA cannot set property string Cause: The named property could not be modified. The property may not be editable or may not exist. Action: Retry the operation with a valid property. Action: Enable the Data Guard configuration and re-issue the request.
ORA Operation requires restart of site "string" Cause: Some Data Guard broker operations require the given site to be shut down and restarted. Action: If the client has not already done so, then shut down the Oracle instance at the given site and then restart it.
ORA Data Guard configuration file creation failure Cause: The Data Guard broker was unable to create the configuration file on permanent storage. Action: Verify that the configuration file was successfully created. Action: Disable the configuration and shut down the Data Guard broker before changing this value. Also be sure to rename the file at the operating system level. Action: Check the states of the configuration, primary site, primary database resource, standby site, and standby database resource.
ORA request terminated at broker discretion Cause: This status is returned when the Broker terminates a user-initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status. ORA 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.
ORA failed to read Data Guard configuration file Cause: A failure was encountered while the broker was reading the configuration file on permanent storage. ORA illegal operation on a standby site Cause: This is an internal error. ORA illegal operation on a primary site Cause: This is an internal error.
ORA Data Guard broker unable to update configuration on site Cause: The Data Guard broker was unable to update the configuration file on a particular site. ORA ambiguous object handle Cause: This is an internal error. ORA no more internal buffers Cause: See trace file. This error is returned in the following situations: While transmitting the configuration file between sites, DRCX detected an inconsistency in the block count of the file.
The DRCX process got an error while writing the configuration file. ORA unknown field "string" in document Cause: There was an error at the given token. ORA missing field "string" in document Cause: There was an error at the given token. ORA site is not a member of the Data Guard configuration Cause: A request was made on a site that is not a member of the Data Guard configuration.
Action: Re-issue the request on a site that is a part of the configuration. ORA Data Guard broker detects two or more primaries Cause: The Data Guard broker has detected two or more primaries in the configuration and cannot continue.
This can occur when the primary site has a stale configuration. Action: The broker will automatically resolve this situation once the primary site completes its initialization.
ORA Failover operation can only be submitted on target site Cause: This error is returned when a failover request specifies a different site than the site the client is currently connected to. Action: Explicitly connect to the site you wish to failover to and re-issue the failover request.
ORA 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 re-issue the request. ORA resource must be disabled to perform this operation Cause: An attempt was made to modify a resource that can only be changed while that resource is disabled. Action: Disable the resource and re-issue the request. This can occur if the original configuration was re-created while this site was disconnected from the network or the same site was added to two different configurations.
Action: Make sure the site belongs to only one configuration. Remove Data Guard broker configuration files and restart the server. ORA 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 site. Also verify that the OnDescribe function is in the package. ORA 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 unable to find property "string" Cause: The named property does not exist. Action: Specify a valid property name and re-issue the request.
Action: Locate the sites with a failure status and correct it. ORA one or more sites have warnings Cause: The Data Guard broker detected a warning status on one or more sites. Action: Locate the sites with a warning status and correct it. Action: Locate the resources with a failure status and correct it. ORA one or more resources have warnings Cause: The Data Guard broker detected a warning status on one or more resources on a site.
Action: Locate the resources with a warning status and correct it. ORA string value too long for attribute "string" Cause: The string value for the named attribute is too long. Action: Use a shorter string. ORA initialization in progress for site Cause: The site received a directive to change its initialization state or a change in its configuration before it has completed initialization.
Action: Wait until the site has completed initialization before issuing requests to modify run-time state or configuration. ORA 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 server. The Data Guard broker has enabled 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 Unknown object identifier specified in request Cause: The Data Guard broker returns this error when the object identifier specified in the request is invalid or unknown. For example, this error is returned if an invalid or unknown site object identifier is specified in a request that requires a site object identifier. Action: Verify that a valid object identifier was specified in the request and then re-issue the request.
ORA 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 console log. Action: View the console log on the given site directly. Action: This typically indicates a network problem where the standby site is unable to respond to the primary within the predefined time frame. ORA one or more sites could not be contacted for a delete operation Cause: This status is returned when the Data Guard broker could not reach one or more standby sites for either a delete site or a delete configuration operation.
Action: This typically indicates a network problem where the standby site is unable to respond to the primary. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command. Cause: An error has occurred while performing a switchover. Action: If you were switching a primary database to the standby role, the conversion was successful, but one or more errors occurred after the conversion completed.
See the alert log for more information. You can proceed with switching the target standby database to the primary role, but you must address the errors reported at the old primary database before it can protect the new primary database.
If you encountered this error while switching a physical standby database to the primary role, the switchover did not succeed because additional redo must be applied. Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs. Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.
Action: The primary must not attempt to archive to the standby after a terminal recovery. Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived. Cause: The control file enqueue is currently unavailable. Action: No Action is required. We will try to re-fetch it at a later time. Cause: Multiple archive log destinations reference the same standby database, using different service names.
This is not allowed. Action: Remove one of the duplicate archive log destinations. Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected. Action: Wait for the managed standby recovery session to end.
Then retry the operation. Cause: Use of the indicated attribute is illegal in the given context. Action: Make the appropriate changes and reissue the statement.
Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files. Another media recovery is not allowed. Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode. Action: The standby database must be added to the configuration before the primary database is opened.
Cause: An attempt was made to add a log file member that did not match the other member types. This problem typically occurs when adding a standby log file member to an online redo log file group, or adding an online redo log file member to a standby redo log file group. Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.
Action: The alert log contains more problem-specific information. Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread s open.
Action: Continue standby recovery with additional log shipping from primary. Cause: See alert log for more details. Action: Copy missing archived logs from primary or another standby. Cause: One of two situations can cause this error: 1 An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. An active Remote File Server RFS process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.
Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation. Cause: An attempt was made to shut down a standby database while media recovery was active. Action: Cancel media recovery to proceed with the shutdown. Cause: The background process dedicated to dictionary build is active.
Action: wait and try it later. All known archived logs have been applied. Managed recovery is not required.
The standby database may be activated as a new primary or may continue as a standby. Cause: The database is operating in manual archiving mode. Remote archivelog destinations are not allowed in this mode. Cause: The number of server processes available for Logical Standby is currently limited to LogMiner processes and apply processes or a total of Action: Retry with a lower value. Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.
The settings for this parameter must be exactly the same for all instances. Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials. Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password.
Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary. Action: Check sqlnet.
Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary. Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime. Action: Shut down the instance. Action: Check the documentation and re-enter the parameter. Cause: A timeout was incurred during remote archival. Action: Try to resolve the problem.
Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support. Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied. Unlock 1 Answer and 1 Comment. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial.
What do I get with a subscription? With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need.
Who are the certified experts? Due to Missing Parenthesis Sometimes, you may not notice that there's one parenthesis is missing from the connect descriptor, usually it's the right side one. Best explanation.. Ed Chen July 10, at am. My pleasure! Jay Imerman September 16, at pm. Ed Chen September 17, at am.
Thanks for your input. Csipak Attila November 18, at pm. Ed Chen November 19, at am.
0コメント