Resolves all unresolved distributed transactions for the
specified database. For more information on unresolved
transactions, see the Oracle Rdb7 Guide to Distributed
Transactions and the Oracle Rdb Release Notes.
1 – Description
Use the RMU Resolve command to commit or abort any unresolved
distributed transactions in the database. You must resolve the
unresolved transactions to the same state (Commit or Abort) in
every database affected by the unresolved transactions.
RMU Resolve performs the following tasks:
o Displays identification information for an unresolved
transaction.
o Prompts you for the state (Commit or Abort) to which you want
the unresolved transaction resolved (if you did not specify
the State qualifier on the command line).
o Prompts you for confirmation of the state you chose.
o Commits or aborts the unresolved transaction. If you commit or
abort the unresolved transaction, it is resolved and cannot be
resolved again.
o Continues to display and prompt for states for subsequent
unresolved transactions until it has displayed information for
all unresolved transactions.
Use the Parent_Node, Process, or Tsn qualifiers to limit the
number of unresolved transactions that Oracle RMU displays.
Use the Users and State=Blocked qualifiers with the RMU Dump
command to determine values for the Parent_Node, Process, and Tsn
qualifiers.
2 – Format
(B)0[mRMU/Resolve root-file-spec
[4mCommand[m [4mQualifiers[m x [4mDefaults[m
x
/[No]Confirm x See description
/[No]Log x Setting of DCL VERIFY flag
/Parent_Node=node-nam e x See description
/Process=process-id x See description
/State=options x None
/Tsn=tsn x See description
3 – Parameters
3.1 – root-file-spec
The database root file for which you want to resolve unresolved
transactions.
4 – Command Qualifiers
4.1 – Confirm
Confirm
Noconfirm
Prompts you for confirmation of each unresolved transaction. This
is the default for interactive processing.
Specify the Noconfirm qualifier to suppress this prompt. This is
the default for batch processing.
4.2 – Log
Log
Nolog
Specifies whether the processing of the command is reported to
SYS$OUTPUT. Specify the Log qualifier to request that summary
information about the resolve operation be reported to SYS$OUTPUT
and the Nolog qualifier to prevent this reporting. If you specify
neither, the default is the current setting of the DCL VERIFY
flag. (The DCL SET VERIFY command controls the setting of the DCL
VERIFY flag.)
4.3 – Parent Node
Parent_Node=node-name
Specifies the node name to limit the selection of transactions
to those originating from the specified node. If you omit
the Parent_Node qualifier, RMU Resolve includes transactions
originating from all nodes.
You cannot specify the Tsn or Process qualifier with the Parent_
Node qualifier.
The Parent_Node qualifier is not valid for XA transactions.
4.4 – Process
Process=process-id
Specifies the process identification to limit the selection of
transactions to those associated with the specified process. If
you omit this qualifier, RMU Resolve includes all processes with
transactions attached to the specified database.
You cannot specify the Parent_Node or Tsn qualifier with the
Process qualifier.
4.5 – State
State=options
Specifies the state to which all unresolved transactions be
resolved.
Options for the State qualifier are:
o Commit-Commits unresolved transactions.
o Abort-Aborts unresolved transactions.
If you do not specify the State qualifier, RMU Resolve prompts
you to enter an action, Commit or Abort, for each unresolved
transaction on that database.
4.6 – Tsn
Tsn=tsn
Specifies the transaction sequence number (TSN) of the unresolved
transactions whose state you want to modify.
The TSN value is contained in a quadword with the following
decimal format:
high longword : low longword
The high longword can hold a maximum user value of 32768
(215) and the low longword can hold a maximum user value of
4,294,967,295 (232). A portion of the high longword is used by
Oracle Rdb for overhead.
When you specify a TSN, you can omit the high longword and the
colon if the TSN fits in the low longword. For example 0:444 and
444 are both valid TSN input values.
If you omit the Tsn qualifier, RMU Resolve includes all the
unresolved transactions. You cannot specify the Parent_Node or
the Process qualifier with the Tsn qualifier.
5 – Usage Notes
o To use the RMU Resolve command for a database, you must
have the RMU$RESTORE privilege in the root file ACL for the
database or the OpenVMS SYSPRV or BYPASS privilege.
6 – Examples
Example 1
The following command specifies that the first displayed
unresolved transaction in the MF_PERSONNEL database be changed
to the Abort state and rolled back:
$ RMU/RESOLVE/LOG/STATE=ABORT MF_PERSONNEL
Example 2
The following command will display a list of all transactions
coordinated by node GREEN and might be useful if node GREEN
failed while running an application that used the DECdtm two-
phase commit protocol:
$ RMU/RESOLVE/PARENT_NODE=GREEN MF_PERSONNEL
Example 3
The following command displays a list of all transactions
initiated by process 41E0364A. The list might be useful for
resolving transactions initiated by this process if the process
were deleted.
$ RMU/RESOLVE/PROCESS=41E0364A MF_PERSONNEL
Example 4
The following command completes unresolved transactions for the
MF_PERSONNEL database, and confirms and logs the operation:
$ RMU/RESOLVE/LOG/CONFIRM MF_PERSONNEL
For more examples of the RMU Resolve command, see the Oracle Rdb7
Guide to Distributed Transactions.