Documentum Cleanup Objects Sequence for object types

kaushaldhabadge

Hi,

I have a scenario where I need to delete dm_document, dm_folder, dm_acl, dm_user, and dm_group.

The structure consists of a cabinet containing a folder that acts as a Classroom, with multiple Divisions, and each division further containing Batches—resulting in a deep folder hierarchy. Each folder has specific ACLs, but they are not necessarily the same across all folders.

Every folder contains dm_document objects, and to control access, I have created ACLs, Users, and Groups specifically for this Classroom. Now, I need to delete the entire Classroom, including its associated objects.

Could someone guide me on the correct sequence for deleting these objects?

For example, consider an ACL named dm_classroom_10th_Acl, which has the following accessors:

• Users: User1, User2
• Groups:
  • Group1 (User3, User5)
  • Group2 (User1, User2, User3, User4, User5, User6)
• Default Accessors: dm_owner, dm_world

All these users and groups are specific to this Classroom. Please advise on the correct sequence in which I should delete these objects.

rouset

IIRC the consistency checker in the server will only allow deletion of a user if there is no folder or document left in the repository that the user owns. And IIRC I don't believe a user can be deleted if a group exists where the user is a member. A small test with two users and a couple of folders and ACLs should enable you to prove this out.

Hicham Bahi

Not really. The server will allow deletion of a user even if he is owner of sysobjects or referenced in an ACL or group. Generally it's recommended to "reassign" users instead of deleting them.

If you want to delete them anyway, I suggest the following sequence: documents, folders, ACLs, groups and users. You may want to run the consistency checker afterwards to see if you missed anything.