Recovering an ObjectServer
An ObjectServer can be recovered in a number of ways utilizing the different tools outlined in this section. In the event of an ObjectServer outage, it is recommended to attempt the following steps to recover it.
- Try to restart the ObjectServer
If the ObjectServer has stopped, it may be because the process has been inadvertently killed. First, check the ObjectServer log file for any errors that may have caused the outage. Next, after any remedial actions have been taken, restart the ObjectServer. Note that the ObjectServer may have already been restarted by the Netcool Process Agent if it is running under PA control.
- Delete the .chk and .log files
If the ObjectServer will not start normally, try deleting any .chk and .log files present in the ObjectServer’s db directory as one of these may be corrupted and hence may prevent the ObjectServer from starting.
- Restore
master_store.tabandtable_store.tabfiles from backupIf the previous steps have failed, it may be that the ObjectServer’s database files are corrupted. In this case, then next step would be to restore the
master_store.tabandtable_store.tabfiles from a backup. Simply replace the existing ones with the backups and then attempt to start the ObjectServer. - Rebuild the ObjectServer from
nco_osreportSQL filesIf the previous steps have failed, the
nco_dbinitutility can be used to rebuild an ObjectServer’s configuration using the SQL files generated via thenco_osreportutility. If thenco_osreportutility is run after each time a configuration change is made, then the configuration contained within these files should be up-to-date. See the previous subsection for information on how to do this. - Rebuild the ObjectServer from the original solution delivery SQL files
If the previous steps have failed, the ObjectServer can be rebuilt using the original solution delivery SQL files and
nco_confpackpackages, where present. The section entitled: Solution delivery, outlines how ObjectServer configuration for an IBM Netcool solution can be delivered via SQL files andnco_confpackpackages, if needed. These files can be used to rebuild an ObjectServer to its initial configuration. Note that this option assumes that the solution delivery files have been kept up-to-date, per the guidelines.