Deleting CIs in BMC Atrium Explorer
Reconciliation jobs should automatically purge instances from BMC Atrium Configuration Management Database (BMC Atrium CMDB) when the CIs that those instances represent are deleted from their dataset. If reconciliation jobs miss an instance that should be deleted, you can delete that instance manually through the BMC Atrium Explorer. For more information about reconciliation jobs, see Reconciliation jobs.
If you use BMC Atrium Explorer to delete an underlying CI related to BMC Remedy IT Service Management records — for example, a CI related to a change request in BMC Change Management — the CI status is automatically propagated to the consuming applications. You do not need to clean up broken CI relationships and associations in consuming BMC applications.
CI deletion and relationships
When you manually delete a configuration item (CI) from the database in BMC Atrium Explorer, all relationships associated with that CI are also deleted. When you run a promotion, deleting the computer CI deletes the two relationships to the operating system and the monitor. But by default, deleting the source CI does not delete the destination CIs.
Deleting CI and relationships
However, if Cascade Delete is enabled for the relationships, deleting a source CI cascades down to destination CIs. When you delete a source CI of a Cascade Delete relationship, the destination CI of the relationship and all destinations of relationships below it are deleted when the source CI is deleted. Administrators can only enable Cascade Delete in relationship classes that follow weak relationships, or that follow 1-to-1 or 1-to-many cardinality. For more information about cascading delete, see Relationships in the data model.
Instance deletions in the BMC Asset dataset
You cannot directly delete instances in the BMC Asset dataset, which is reserved for production use. To delete an instance in the BMC Asset dataset, you must first convert the Asset view to a Sandbox view. You then can delete it in the Sandbox dataset. The instance is marked as deleted, or soft deleted, and appears in the view with the Deleted icon. Then, click Promote Sandbox Changes to merge the changes into the BMC Asset dataset.
After the changes are merged, run a reconciliation job with the Purge activity to physically delete only instances that have been marked as deleted, or soft deleted. For more information about the Purge activity, see Purging soft-deleted data by using the Reconciliation Engine.
To delete instances
- In BMC Atrium Explorer, open a view for an editable dataset (for example, the Sandbox).
- Add the instances that you want to delete to the view.
You can query for instances as described in BMC Atrium Explorer and building queries, or you can open an existing view containing the instances you want to edit as described in BMC Atrium Explorer views.
- In the display pane, select one or more instances you want to delete.
- Click the selected instances and select Delete from Database.
The instance is marked as deleted, or soft deleted, and appears in the view with the Deleted icon.
Delete from Databasecommand determines whether the selected instance should be marked as deleted (soft deleted ) or deleted from the dataset (hard deleted ).
For example, if you create a CI in the Sandbox view, click the CI, and then select
Delete from Database, the CI is deleted from the Sandbox dataset (hard deleted ) and removed from the view. However, if you are working in a BMC Asset view that has been converted to a new Sandbox view, and you click the CI and then you select
Delete from Database, the CI is marked as deleted ( soft deleted ) and appears in the view with the Deleted icon.
- In the confirmation dialog box, click OK.
- If you are finished working in the Sandbox dataset and are ready to promote changes to the BMC Asset dataset, click Promote Sandbox Changes in the toolbar.
For more information, see Promoting instances.