EPAP | PDB write transaction is rejected because of open transaction. Req: "begin_txn(type write)" || Rsp: "rsp (rc 1005..)" (Doc ID 2642572.1)

Last updated on NOVEMBER 09, 2023

Applies to:

Symptoms

 PDB stopped to be updated.
EPAP server responded with RC 1005

02/16/20-23:10:00 (TID 7f46c11b4700) CIP: 10.73.130.xx CID: 12264 Req: "begin_txn(type write)"
02/16/20-23:10:00 (TID 7f46c11b4700) CIP: 10.73.130.xx CID: 12264 Rsp: "rsp (rc 1005, data (id 12260, ip ::ffff:10.73.130.yy, port 8627))"

One of remote clients started write transaction, but didn't closed transaction. There was no Req: "end_txn()" from client. Hence all next requests Req: "begin_txn(type write)" were rejected.

02/16/20-23:07:05 (TID 7f46c1bb5700) CIP: 10.73.130.yy CID: 12260 Req: "begin_txn(type write)"
02/16/20-23:07:05 (TID 7f46c1bb5700) CIP: 10.73.130.yy CID: 12260 Rsp: "rsp (rc 0)"

Questions:

1. How long EPAP can wait incoming subsequent requests from client (for example, ent_sub) if write transaction was successfully created?
2. What EPAP will do if write transaction is created, but there is no incoming requests for long time? In our case customer found that PDB isn't updating in six hours since issue started.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.