This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

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

Deleting a dataset

Before deleting a dataset, you must run a reconciliation job to purge or delete configuration items (CIs) from the dataset. Otherwise, the server returns an error when you try to delete the dataset.

For more information about all these normalization and reconciliation activities, see Normalizing data and Reconciling data.

To delete a dataset

  1. To produce good identification results in reconciliation, use the Normalization Engine to normalize the CI attributes between the two datasets.
    You perform this step to make it easier to determine which CIs represent the same object. If you do not intend to preserve the CIs, you can ignore this step.
  2. For CIs that you want to preserve from the dataset that you intend to delete, create a standard Identification and Merge job to merge the CIs into the BMC.ASSET dataset.
    If you do not intend to preserve the CIs, you can ignore this step.
  3. To remove all instances from the dataset, create and run a manual reconciliation job with a Delete or Purge activity to remove all the CIs from the dataset.
  4. Open the BMC.CORE.CONFIG:BMC_Dataset form and search for the dataset record that you want to delete.
  5. Delete the dataset record.
    The dataset is now removed from the server.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.


  1. Jan Sierens

    I followed this procedure and now I get an error when running an reconciliation that this dataset doesn't exist anymore: Event - ARERRR[101049] Dataset <{1}> does not exists. The dataset is not used by this reconciliation though it still exists in the precedence rules. 

    Oct 14, 2014 07:00
    1. Jan Sierens

      I didn't run a recon job to delete CI's in the dataset because the dataset was not in use yet and empty. (When first creating the dataset I made a typo in the name and thought it was safest to delete and recreate the dataset with the correct name.)

      To delete of the dataset itself, I first did set the MarkedAsDelete flag to Yes, save and then deleted the record using the delete button.



      Oct 15, 2014 04:44
      1. Amol Redij

        Hi Jan,

        Thank you for your comment.

        The error occurs because all the references of the dataset may not be deleted. With deleting dataset from BMC.CORE.CONFIG:BMC_Dataset, it is also important to review component level configurations and remove dataset references, if any.



        Oct 16, 2014 05:14
        1. Lukasz Pilch

          Hello Amol Redij

          Could you list all dataset references then?

          Following this instruction will led to breaking some of reconciliation jobs, i.e. with merge action in it.

          May 03, 2016 05:26
          1. Amol Redij

            Hello Lukasz,

            Let me look at this and talk to the concerned SME.

            I shall reply to you as soon as I can.

            Thank you for your patience


            May 10, 2016 12:55
            1. Lukasz Pilch

              Hello Amol Redij

              Any updates?


              Best regards,


              Sep 19, 2016 04:42
  2. Henrik Nã¸rholm

    Totally screws up the Merge Job, as it still looks for deleted datasets. Also you cannot remove the deleted datasets from the precedence set. I see a bug.

    Jun 02, 2016 03:03