Configuration Item objects appear as soft deleted but are actually hard deleted

Version 7

    Verified Product Versions

    LANDESK Service Desk 7.6

    Environment:

    Landesk/Ivanti Service Desk - All Versions

     

     

    Problem:

    Prior to Service Desk 7.3.1, all Configuration Items had the property in Object Designer for Deletion Type as Soft Deletion, but in practice performed a hard deletion.  This was logged as Problem #3968, and was fixed in 7.3.1.  This allowed Configuration Item objects to properly inherit the soft deletion property.  Unfortunately, Configuration Item objects created prior to an upgrade to 7.3.1 (including the ones in the out-of-the-box database) still exhibit hard deletion properties.

    Current versions that include a CI that was in place before 7.3.1 will still have this issue.

     

     

    Cause:

    The changes made in 7.3.1 did not retro-actively fix existing Configuration Item objects.

     

     

    Solution:

    The existing CIs need a small change to their metadata in the database to start soft deleting properly.  This can be done with the script below.  Please test this script on a backup copy of the database before applying to a live environment.  Lastly, take a full backup of the the database before applying to live.

     

    SQL Server:

    update md_class_type set md_deletion_type = 1
         where md_defined_by = 2
         and md_supertype_guid = '159677C0-A2D5-45AB-B69A-1DCE7F3B93CB'
    Oracle:
    update md_class_type set md_deletion_type = 1
         where md_defined_by = 2
         and md_supertype_guid = 'C0779615D5A2AB45B69A1DCE7F3B93CB';
    This is currently logged as Problem #5624. If you are experiencing this issue, please log this with your support provider. Reference the problem number in your case description.