Abort Transaction
This example shows awrite transaction that receives an error on one of its update requests and then
aborts the transaction.
Table 33: Abort Transaction Example
DescriptionMessage
A PDBI connection has been
established to the Active PDBA.
connect(iid 1, version 1.0)→
rsp (iid 1, rc 0, data (connectId 6, side active))←
A write transaction has been
opened.
begin_txn(iid 2, type write)→
rsp (iid 2, rc 0)←
The DN has been created.
ent_sub(iid 3, dn 9195557000, sp 9195556666)→
rsp (iid 3, rc 0)←
Another DN has been created.
ent_sub(iid 4, dn 9195558000, sp 9195550000)→
rsp (iid 4, rc 0)←
The request to create a
stand-alone DN 9195551213 failed
because the DN already exists.
ent_sub(iid 5, dn 9195551213, sp 919555555)→
rsp (iid 5, rc 1014, data (dn 9195551213))←
The client decided to abort the
transaction because the previous
abort_txn(iid 6)→
rsp (iid 6, rc 0)←
update failed. This will cause the
two DNs created in iid 3 and iid
4 to be rolled back. No data is
updated. Note that the client did
not have to abort the transaction
here. The transaction could have
just been ended normally, and the
first two DNs would have been
created successfully.
The client is done and has
disconnected.
disconnect(iid 7)→
rsp (iid 7, rc 0)←
151
910-6022-001 Revision A, March 2011
PDBI Sample SessionsProvisioning Database Interface Manual
To Next Page
Loading...
