Database Error Messages

This is an ACCHK message. Possible causes are:

• This a JDBC application and the replay driver or JDBC consolidated data source are not used.
• There is an UNRESTORABLE session state in the login trigger or label when using Transparent Application Continuity.
• The application is using XA.
• A transaction processing monitor is in use with two-phase commit.
• The client disabled replay.

For JDBC, either use the replay driver or consolidated data source:

• The "consolidated data source" (i.e. oracle.jdbc.datasource.impl.OracleDataSource).
• The "replay data source" (i.e. oracle.jdbc.replay.OracleDataSourceImpl).

Ensure that there is no UNRESTORABLE state being created by the login trigger when using Transparent Application Continuity. Also, ensure that your application is not attempting to use Oracle Application Continuity with XA or other restricted options.

Possible causes are:

• The replay driver was not used.
• There was UNRESTORABLE session state in the login trigger or label.
• A transaction processing monitor was in use with two-phase commit.
• The client disabled replay.

Use the replay driver or validate trigger checking for restorable state if using FAILOVER_TYPE = AUTO or check if the application is explicitly disabling replay or using Oracle XA Library.

Possible causes are:

• The replay driver was not used.
• There was UNRESTORABLE session state in the login trigger or label.
• A transaction processing monitor was in use with two-phase commit.
• The client disabled replay.

Use the replay driver or validate trigger checking for restorable state if using FAILOVER_TYPE = AUTO or check if the application is explicitly disabling replay or using Oracle XA Library.