This documentation supports the 21.05 (12.2) version of BMC Discovery.To view an earlier version of the product, select the version from the Product version menu.

tw_model_wipe

The tw_model_wipe utility enables you to delete all data in the datastore. The utility does not delete configuration data held outside the datastore. However, some configuration information is held in the datastore and can be deleted, if you choose to do so when running tw_model_wipe. This is:

  • Scan ranges
  • Scheduled scan ranges
  • Exclude ranges
  • CAM (saved queries, groups and subgroups, named values, functional component definitions, and generated patterns)
  • DDD Removal blackout windows
  • Configuration as a scanner or consolidator
  • Registered Windows proxies
  • Saved Queries (on the Reports page)
  • CMDB Sync configuration (both connections and filters)
  • Custom Categories (such as Location and Organizational Units)


Warning

The tw_model_wipe utility can delete all data in your datastore. Before you use tw_model_wipe to resolve an issue, it is recommended that you contact BMC Customer Support.

To use the utility, type the following command at the $TIDEWAY/bin/ directory:

tw_model_wipe [options] 

where options are any of the options described in the following table and the common command line options described in Using-command-line-utilities.

Effect on CMDB synchronization

The tw_model_wipe utility deletes the contents of the datastore. When you rescan your estate, the algorithm that identifies hosts (actually root nodes, which are Hosts, Network Devices, MFParts, Printers, and SNMP Managed Devices) may come up with a different identifier or key each time a root node is newly created in the datastore. However, the CMDB relies on the keys of the root nodes remaining the same; if they are not the same, then the CMDB creates duplicate CIs.

To avoid duplicate CI creation in the CMDB, BMC Discovery version 10 introduces a root node key information export utility which enables you to extract information and the key of root nodes from a machine before reinitialization. You can then upload this to the reinitialized machine where it is stored in the datastore as RootNodeKeyInfo nodes.

When you rescan the estate with the reinitialized machine, any potentially new root node is compared against the RootNodeKeyInfo nodes, and if a match is found for the discovery target, a new node is created using the key from the RootNodeKeyInfo node and the RootNodeKeyInfo node is deleted. If no match is found in the RootNodeKeyInfo nodes, then a new node is created with a new unique key.

To learn how to use the root node key information export utility, see preserving IDs when using tw_model_wipe.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*