Tuxedo Application Trying To Detect And Handle DB Connection Problems In XA Child Service
(Doc ID 1546203.1)
Last updated on AUGUST 11, 2020
Applies to:
Oracle Tuxedo - Version 12.1.1 and laterInformation in this document applies to any platform.
Symptoms
Once a "LIBTUX_CAT:481: ERROR: Service xa_start returned XAER_RMERR" occurs we can not then get the service to restart.
xa_NULL01012013.trc has:
103945.xx.0: ORA-00028: your session has been killed
ULOG.010113 has the following for the same time period:
103945.TuxMachineName!SERVERXASVC.xx.3646215968.0: gtrid x0 x515efda2 x1b9: TRACE:xa: { xa_start(0x0x872ad0, 0, 0x200000)
103945.TuxMachineName!SERVERXASVC.xx.3646215968.0: gtrid x0 x515efda2 x1b9: TRACE:xa: } xa_start = -3
103945.TuxMachineName!SERVERXASVC.xx.3646215968.0: gtrid x0 x515efda2 x1b9: LIBTUX_CAT:481: ERROR: Service xa_start returned XAER_RMERR
103945.TuxMachineName!SERVERXASVC.xx.3646215968.0: gtrid x0 x515efda2 x1b9: TRACE:xa: } xa_start = -3
103945.TuxMachineName!SERVERXASVC.xx.3646215968.0: gtrid x0 x515efda2 x1b9: LIBTUX_CAT:481: ERROR: Service xa_start returned XAER_RMERR
and nothing is shown in the ULOG related to the subsequent xa_NULL01012013.trc ORA-01012 errors:
104031.xx.0: ORA-01012: not logged on Process ID: xxx Session ID: 75 Serial number: 747
104031.xx.0: xaostart: OCITransStart rtn 1012
104056.xx.0: ORA-01012: not logged on Process ID: xxx Session ID: 75 Serial number: 747
104056.xx.0: xaostart: OCITransStart rtn 1012
104031.xx.0: xaostart: OCITransStart rtn 1012
104056.xx.0: ORA-01012: not logged on Process ID: xxx Session ID: 75 Serial number: 747
104056.xx.0: xaostart: OCITransStart rtn 1012
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |