RDBPROD: Recovery Process Fails With RDMS-F-PARTDTXNERR After Node Failed
(Doc ID 1354424.1)
Last updated on OCTOBER 27, 2017
Applies to:
Oracle Rdb Server on OpenVMS - Version 7.0.6 and laterHP OpenVMS Alpha
HP OpenVMS VAX
HP OpenVMS Itanium
Symptoms
One node of a cluster failed while a database was active on that node. It was necessary to recover the database on another node.
A recovery process failed and as a result the database was inaccessible.
When the recovery process failed, a bugcheck dump was produced. Each subsequent attempt to access the database created another bugcheck dump.
The initial bugcheck dump summary looked like:
Alpha OpenVMS 7.3-2
Oracle Rdb Server 7.0.6.3
Got a RDMDBRBUG.DMP
Database Recovery (DBR) process bugchecked
RDMS-F-PARTDTXNERR, error when trying to participate in a distributed transaction
SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Exception occurred at DBR$DDTM_RESOLVE + 0000039C
Oracle Rdb Server 7.0.6.3
Got a RDMDBRBUG.DMP
Database Recovery (DBR) process bugchecked
RDMS-F-PARTDTXNERR, error when trying to participate in a distributed transaction
SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Exception occurred at DBR$DDTM_RESOLVE + 0000039C
Subsequent dumps looked like:
Alpha OpenVMS 7.3-2
Oracle Rdb Server 7.0.6.3
Got a RDMDBRBUG.DMP
Database Recovery (DBR) process bugchecked
RDMS-F-PARTDTXNERR, error when trying to participate in a distributed transaction
SYSTEM-W-NOSUCHFILE, no such file
Exception occurred at DBR$DDTM_RESOLVE + 0000039C
Oracle Rdb Server 7.0.6.3
Got a RDMDBRBUG.DMP
Database Recovery (DBR) process bugchecked
RDMS-F-PARTDTXNERR, error when trying to participate in a distributed transaction
SYSTEM-W-NOSUCHFILE, no such file
Exception occurred at DBR$DDTM_RESOLVE + 0000039C
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 |
| Cause |
| Solution |
| References |