|
The tw_model_init utility enables you to initialize the model, this consists of deleting any data that you have in the datastore and reapplying the taxonomy. The utility can also install and activate a TKU after deleting the datastore. The TKU package must be stored on the appliance filesystem. The tw_model_init utility does not delete configuration data held outside the datastore. However, some configuration like information is held in the datastore and is lost when running tw_model_init. This is:
If you suspect datastore corruption, consult the knowledgebase article KA325751 to determine whether the datastore is corrupted. If you discover that there is corruption then you should contact BMC Customer Support.
To use the utility, type the following command at the $TIDEWAY/bin/ directory: tw_model_init [options] where options are any of the commands described in the following table.
User exampleBy default, the tw_model_init utility activates the TKU package that came with the version of BMC Atrium Discovery appliance that you have installed. If you are not planning to use that TKU, you can set the --no-tku option to save you time when running the utility. However, if you use this option and then forget to subsequently load a TKU, your BMC Atrium Discovery instance will collect significantly less data. Initializing the model without activating a TKUThe following example illustrates how you can initialize the model without installing and activating a TKU: $TIDEWAY/bin/tw_model_init --no-tku Effect on CMDB synchronizationWhen a host has significantly changed so that its key has also changed, problems can be caused if tw_model_init is used before the changed host is rediscovered. In this case, on the next CMDB synchronization, duplicate hosts will be created in the CMDB representing the changed host, and the CIs representing the original hosts will never be deleted. To ensure that no duplicate hosts are created, you can delete and then recreate the BMC.ADDM dataset. |
