This documentation supports the 19.02 version of BMC Atrium Core.

To view the latest version, select the version from the Product version menu.

Deleting CIs in CMDB Explorer

Occasionally, your discovery application will not discover a configuration item (CI) or that it regularly discovered before. Though you might be tempted to delete the CI from BMC CMDB, do not do so right away. Usually such a missing CI is only temporarily removed or unavailable, such as when a computer system is shut down while its owner is on vacation.

You can mark a CI for deletion by setting the MarkAsDeleted attribute to Yes. When instances have been marked as deleted, you can exclude them from searches, reconciliation, and other activities by using the MarkAsDeleted attribute in your qualifications. You can preserve relationships and reconciliation identity in case a CI is later discovered again.

Establish a policy that specifies how long a CI can remain marked as deleted before it is actually deleted from the dataset. If the CI is rediscovered before reaching the end of that interval, you can reset the MarkAsDeleted attribute to NULL. 


Deleting CIs in the production dataset

You cannot directly delete instances in the production (BMC.Asset) dataset, which is reserved for production use. To delete an instance in the BMC Asset dataset, you must first open the instance in the Sandbox dataset. 


To mark a CI for deletion

Perform the following steps to delete a CI in CMDB Explorer: 

  1. Search for a CI on the CMDB Dashboard.
  2. On the search results page, click the CI that you want to view in the CMDB Explorer.
    The CI opens in the Explorer. 
  3. Right-click the CI and select Mark As Delete.

The instance is marked as deleted and appears in the view with the X sign.

Where to go from here

Promoting changes from a Sandbox dataset to production


Was this page helpful? Yes No Submitting... Thank you

Comments