The LIXA project supplies a recovery utility you must use to
perform some special tasks related to distributed transaction
recovery. The command is named lixar and is
located in the bin directory; use
--help option to retrieve the list of
the available options:
tiian@ubuntu:~$ /opt/lixa/bin/lixar --help
Usage:
lixar [OPTION...] - LIXA recovery utility
Help Options:
-?, --help Show help options
Application Options:
-p, --print Print a report of all the prepared and in-doubt transactions compatible with current configuration and profile
-x, --xid Select specified transaction for rollback/commit
-X, --xid-file Select specified file as a list of transaction to rollback/commit
-c, --commit Commit prepared & in-doubt transactions
-r, --rollback Rollback prepared & in-doubt transactions
-v, --version Print package info and exit
-b, --bypass-bqual-check Bypass xid branch qualifier check
-B, --bypass-formatid-check Bypass xid format id check
-e, --use-tmendrscan-flag Use TMENDRSCAN flag for last xa_recover call
The LIXA test utility is a LIXA client program and it does
not need
any special authorization to run because it does not need to write
the content of /opt/lixa/var/ directory.
The usage of the lixar command is strictly related to recovery tasks and is explained in Chapter 9, Recovery.
--commit and
--rollback are safe; only
specifying “commit” and “rollback” can
damage the state of the data managed by your resource managers.
You must start the state server before you can start lixar; if you don't start the state server, you will get something like shown below:
tiian@ubuntu:~$ /opt/lixa/bin/lixar
Execution options:
- print report = no
- transaction(s) will be committed = no
- transaction(s) will be rolled back = no
- bypass xid branch qualifier check = no
- bypass xid format id check = no
- use TMENDRSCAN flag for last xa_recover call = no
tx_open() returned TX_FAIL: unable to proceed