How to get rid of deleted entries from database?

I have some documents that are deleted using DQL. I cannot query them using DQL nor view them using DA. the job dm_DMClean runs once a day.

But I can still see them using SQL server. Just inside the dm_sysobject_s, the i_is_deleted is marked as 1. I guess something must be wrong when delete these files. It is annoying to see them.

Please let me know how to delete them completely.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

rishi08

This is normal behavior. The below text is from server fundamentals, chapter "Object Type and Instance Manipulations and Customizations"

When the object you destroy is the original version (the version identified by the chronicle ID), Content Server does not actually remove the object from the repository.

Instead, it sets the object’s i_is_deleted property to TRUE and removes all associated objects, such as relation objects, from the repository. The server also removes the object from all cabinets or folders and places it in the Temp cabinet. If the object is carrying the symbolic label CURRENT, it moves that label to the version in the tree that has the highest r_modify_date property value. This is the version that has been modified most recently.

Regarding the “select * from dm_document (all)”, if you check the actual sql statement that is being executed, you wil notice that the statement has a where clause as “i_is_deleted = 0”. Below is the sql that is being executed when you run the “select * from dm_document (all)” statement.

select all dm_document.r_object_id, dm_document.object_name, dm_document.title, dm_document.subject, dm_document.resolution_label, dm_document.owner_name, dm_document.owner_permit, dm_document.group_name, dm_document.group_permit, dm_document.world_permit, dm_document.log_entry, dm_document.acl_domain, dm_document.acl_name, dm_document.language_code, dm_document.r_object_type, dm_document.r_creation_date, dm_document.r_modify_date, dm_document.a_content_type from dm_document_sp dm_document where

dm_document.i_is_deleted = 0

All comments

RalfKahrl

Are those objects you see the initial version of a version tree (r_object_id = i_chronicle_id) and you have still versions with that specific i_chronicle_id? In this case it is a normal behavoir that the entry for the initial version is keept inside the database (marked as deleted) just to keep the version tree of existing documents together.

Hongmei

If the entry is the initial version inside a version tree, then I should be able to see it by using DQL

select * from dm_document(all). But I can't.

Also the i_contents_id is 0000000000000000, the r_content_size is 0, the a_full_text is 0, r_immutable_flag is 1, r_full_content_size is quite big 469582.

The problem might come from two places. Something wrong when upload the file, or something wrong when delete the file.

Please help me to clean the database, I hate to see them that I can't get access.

rishi08

This is normal behavior. The below text is from server fundamentals, chapter "Object Type and Instance Manipulations and Customizations"

When the object you destroy is the original version (the version identified by the chronicle ID), Content Server does not actually remove the object from the repository.

dm_document.i_is_deleted = 0

kain

The right answer is :

“select * from dm_document (deleted)”

Hongmei

The dql

“select * from dm_document (deleted)”

can actually get undeleted document as well as deleted.