Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
These error messages can be returned by the application failover feature.
Cause: A failure occurred since the last fetch on this cursor. Failover was able to bring the cursor to its original state to allow continued fetches.
Action: This is an internally used error message and should not be seen by the user.
Cause: A failure occurred since the last fetch on this cursor. Failover was unable to bring the cursor to its original state to allow continued fetches.
Action: Re-execute the statement and start fetching from the beginning.
Cause: A failure occurred while a transaction was active on this connection.
Action: The client must roll back.
Cause: The connection to the database has been lost, and attempts to reconnect have failed.
Action: Manually reconnect.
Cause: The primary instance has died.
Action: This is an internally used error message and should not be seen by the user.
Cause: A failure occurred while a transaction was attempting to commit. Failover could not automatically determine instance status.
Action: Determine the transaction's status manually.
Cause: Failover was unable to generate a connect string for a backup instance.
Action: Report this error to Oracle support.
Cause: The connection was lost while doing a fetch.
Action: This is an internally used error message and should not be seen by the user.
Cause: The connection was lost while doing this call. It may not be safe to replay it after failover.
Action: Check to see if the results of the call have taken place, and then replay it if desired.
Cause: The connection was lost while issuing a rollback.
Action: If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine PENDING_TRANS$ to determine if ROLLBACK FORCE is required.
