Upgrading when there are corrupt registry files
If you have tried to upgrade a stand-alone, fault-tolerant agent (an agent that is not shared with other components or does not have the connector feature) and received an error message that states that an instance of HCL Workload Automation cannot be found, this can be caused by a corrupt registry file. It is possible to upgrade a stand-alone, fault-tolerant agent that has corrupt registry files without having to reinstall the product. HCL Workload Automation has a recovery option you can run to re-create the necessary files. You can also use this option when upgrading nodes in clusters, where the node on which you want to perform the upgrade is not available or is in an inconsistent state. The recovery option re-creates the registry files and the Software Distribution information without having to reinstall the complete product.
You can run the recovery option using the twsinst script.
Re-creating registry files using twsinst
To re-create the registry files while upgrading an agent by using the twsinst script, from the directory that contains the HCL Workload Automation agent eImage, run twsinst using the synopsis described below.
- On Windows™ operating systems:
-
- Show command usage and version
-
twsinst -u | -v
- Upgrade an instance
-
twsinst -update -uname user_name -password password ..-acceptlicense yes|no [-domain user_domain] [-recovInstReg true] [-inst_dir install_dir]
- Example
-
cscript twsinst -update -uname twsuser -password twspassword -acceptlicense yes -inst_dir "C:\Program Files\IBM\TWA" -recovInstReg true
- On UNIX™ and Linux™ operating systems
-
- Show command usage and version
-
./twsinst -u | -v
- Upgrade an instance
-
./twsinst -update -uname user_name ..-acceptlicense yes|no ..[-inst_dir install_dir ..[-recovInstReg true]]
- Example
-
./twsinst -update -uname twsuser -inst_dir /opt/IBM/TWA -acceptlicense yes -recovInstReg true