As you know, the problem with using load balancing at the Oracle level with WebSphere AS is that when a RAC instance...
fails, the WebSphere application may attempt to recover a transaction branch from the failing node and leave it hanging.
The setting up of singleton services forces single connections but you still need to point them to individual instances and use DTP to synchronize the transaction IDs.
The only way I know of to continue to use load balancing at the Oracle level is to catch the associated errors (ORA-01591 and/or ORA-24756) and rollback the in-doubt transactions with code.
The dba_2pc_pending view contains the pending transaction IDs.
I know this sounds messy but unless someone knows of a better workaround, this is the best I can come up with.
Dig Deeper on Oracle database availability
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.