Database - RAC/Scalability (MOSC)

MOSC Banner

Application Continuity not working as expected

edited Dec 12, 2017 5:23PM in Database - RAC/Scalability (MOSC) 2 commentsAnswered ✓

I have a 2 instance 12.1.0.2.170418 RAC database called "alwayson" on RHEL 6 servers.

My database service is created with this syntax:

srvctl add service -d alwayson -s alwayson_sv -preferred alwayson1 -available alwayson2 -failovertype TRANSACTION -replay_init_time 300 -failoverretry 30 -failoverdelay 3 -commit_outcome TRUE

In my test, I created a small table, insert a row, failover the service and shutdown the alwayson1 instance, then attempt to commit the transaction on the failed-over session.

QUESTION: Why am I getting "ORA-25402: transaction must roll back" on failed-over transaction.  What's the point if you can't seamlessly continue a transaction?

SQL> select instance_name from v$instance;

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center