Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Troubleshoot and Support > Support issues and limitations > Database issues and limitations
Oracle Transaction Exception
When virtual member manager is reinstalled, the Oracle XA transaction log is not cleaned up correctly.
If you receive the following exception when using the database repository, the tranlog directory might not have been deleted during the reinstallation.
WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@48857464. The error code was XAER_RMERR. The exception stack trace follows: javax.transaction.xa.XAException at oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:626) at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.recover(WSRdbXaResourceImpl.java:955) at com.ibm.ws.Transaction.JTA.XARminst.recover(XARminst.java:137) at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:626) at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java:512) at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java:1794) at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2263)
Solution
- Search for tranlog directories on the entire machine. Do a complete search of the machine not just the current WAS directory.
- Delete the contents of the tranlog directories.
If possible, first delete the contents of the current WAS tranlog directory and test if that corrects the problem.
Parent topic: Database issues and limitations