...
The can be done with the list transactions command:
| Panelnoformat | ||
|---|---|---|
| ||
dbvrep> LIST TRANSACTIONS |
...
The Transaction ID is the hex value of the combined columns XIDUSN, XIDSLOT, XIDSQN from v$transaction on the source database. The Transaction ID is also set in columns MODULE and ACTION from V$SESSION on the target database.
To find the actual SQL statement run the following query and match the Transaction ID (run on source database):
| Panelnoformat | ||
|---|---|---|
| ||
SQL> select inst_id, to_char(XIDUSN, 'xxxxxxxx'), to_char(XIDSLOT,'xxxxxxxx'), to_char(XIDSQN,'xxxxxxxx') from gv$transaction; |
...
| Info |
|---|
If this above transaction does not return any rows, then look into v$session on target database to find the Transaction ID in columns MODULE and ACTION |
We are only interested in the INSERT statements.
When the Transaction ID of the INSERT statement is found, then the record can be committed with:
| Panelnoformat | ||
|---|---|---|
| ||
dbvrep> apply commit transaction xxx |
This will then cause the update statement to proceed as the insert statement is now committed on the target database.
If uncommitted transactions happen on a frequent basis, please Contacting Support
Please also see http://support.dbvisit.com/entries/24825508-Committing-uncommitted-transactions