Recovers a corrupted database and resolves an unresolved
distributed transaction by completing the transaction.
See the Oracle Rdb7 Guide to Distributed Transactions for
complete information on unresolved transactions and for
information on the transactions managers (DECdtm and Encina)
supported by Oracle Rdb.
1 – Description
Use the RMU Recover Resolve command to commit or abort any
unresolved distributed transactions in the after-image journal
(.aij) file. You must complete the unresolved transactions to the
same state (COMMIT or ABORT) in every .aij file affected by the
unresolved transactions.
The RMU Recover Resolve command performs the following tasks:
o Displays identification information for an unresolved
transaction.
o Prompts you for the state to which you want the unresolved
transaction resolved (if you did not specify the State
qualifier on the command line). If you are using DECdtm to
manage the transaction, you can specify COMMIT, ABORT, or
IGNORE. If you are using an XA transaction, you can specify
COMMIT or ABORT.
o Prompts for confirmation of the state you specified
o Commits, aborts, or ignores the unresolved transaction
o Continues until it displays information for all unresolved
transactions
2 – Format
(B)0[mRMU/Recover/Resolve aij-file-name
[4mCommand[m [4mQualifiers[m x [4mDefaults[m
x
/Active_IO=max-reads x See the RMU/Recover command
/Aij_Buffers=integer x See the RMU/Recover command
/Areas[=storage-area[,...]] x See the RMU/Recover command
/[No]Confirm x See description
/Format={Old_File|New_Tape} x See the RMU/Recover command
/Label=(label-name-list) x See the RMU/Recover command
/[No]Log x See the RMU/Recover command
/[No]Media_Loader x See the RMU/Recover command
/[No]Online x See the RMU/Recover command
/[No]Rewind x See the RMU/Recover command
/Root=root-file-name x See the RMU/Recover command
/State=option x See description
/[No]Trace x See the RMU/Recover command
/Until=date-time x See the RMU/Recover command
3 – Parameters
3.1 – aij-file-name
The name of the file containing the after-image journal. This
cannot be an optimized after-image journal (.oaij) file. The
default file extension is .aij.
4 – Command Qualifiers
4.1 – Confirm
Confirm
Noconfirm
Prompts you for confirmation of each transaction state you alter.
The default for interactive processing is Confirm.
Specify the Noconfirm qualifier to suppress this prompt. The
default for batch processing is Noconfirm.
4.2 – State
State=option
Specifies the state to which all unresolved transactions will be
resolved.
If you are using DECdtm to manage your distributed transaction,
options for the State qualifier are:
o Commit-Commits all unresolved transactions.
o Abort- Aborts all unresolved transactions.
o Ignore-Does not resolve any transactions.
If you are using Encina to manage your distributed transaction,
options for the State qualifier are:
o Commit-Commits all unresolved transactions.
o Abort- Aborts all unresolved transactions.
If you do not specify the State qualifier, Oracle RMU prompts
you to enter an action, for each unresolved transaction in
that .aij file. If DECdtm is managing your transaction and you
enter Ignore, Oracle RMU-instead of resolving the transaction-
attempts to contact the coordinator to resolve the transaction.
The transaction remains unresolved until the coordinator becomes
available again and instructs the transaction to complete or
until you manually complete the transaction by using the RMU
Recover Resolve command again. For more information about the
activities of the coordinator, see the Oracle Rdb7 Guide to
Distributed Transactions.
Because a coordinator is not involved with transactions managed
by Encina, the Ignore option is not valid for XA transactions.
5 – Usage Notes
o To use the RMU Recover Resolve command for a database, you
must have the RMU$RESTORE privilege in the root file for the
database or the OpenVMS SYSPRV or BYPASS privilege.
o If you have restored the database by using the New qualifier
and have not deleted the corrupted database, use the Root
qualifier to override the original file specification for the
database root file.
o After it rolls forward from the .aij file specified on the
command line, Oracle RMU prompts you for the name of the next
.aij file. If there are more .aij files to roll forward, enter
the file name, including the version number for that .aij
file. If there are no other .aij files, press the Return key.
For more information about rolling forward and determining
transaction sequence numbers for .aij files, see the Oracle
Rdb Guide to Database Maintenance.
o Note the following points regarding using Oracle Rdb with the
Encina transaction manager:
- Only databases that were created under Oracle Rdb V7.0 or
higher, or converted to V70 or higher, can participate in
XA transactions.
- To start a distributed transaction, you must have the
DISTRIBTRAN database privilege for all databases involved
in the transaction.
- Oracle Rdb supports only explicit distributed transactions
with Encina. This means that your application must
explicitly call the Encina routines to start and end the
transactions.
6 – Examples
Example 1
The following command recovers the mf_personnel database and
rolls the database forward from the old .aij file to resolve the
unresolved distributed transactions. Because the State qualifier
is not specified, Oracle RMU will prompt the user for a state for
each unresolved transaction.
$ RMU RECOVER/RESOLVE MF_PERSONNEL.AIJ;1
Example 2
This example specifies that all unresolved transactions in the
mf_personnel.aij file be committed.
$ RMU/RECOVER/RESOLVE/STATE=COMMIT MF_PERSONNEL.AIJ
For more examples of the RMU Recover Resolve command, see the
Oracle Rdb7 Guide to Distributed Transactions.