Recover Deleted Documents in Documentum

Hi All,

I would like someone to put some light on how to recover the deleted documents in Documentum.It is said to be dmr_content object type that plays a role in indentifying the documents that were deleted but once you recognize the content objects how does one get the object back into documentum.

Any effort to explore this would be highly appreciated.

Thanks and Regards,

Bidanta

Find more posts tagged with

Comments

dnvhariprasad

You can recover documents if dm_clean job was not run.

dm_clean job will delete all the orphaned documents. There are lot of posts in the community if you search for "recovering deleted documents".

The following is the extract from one of the solutions given in the powerlink..

Whenever a document is deleted, only the document's metadata is deleted.  The content itself (i.e. the object pointed to by the dmr_content  object) remains in the content storage area until the IAPI script  generated by the dmclean utility is run (see the System Administrator's  Guide for more information on the dmclean utility). Assuming that the  dmclean utility has not been run, it is still possible to recover the  object's content file. Note: The document's attributes cannot be  recovered without going back to a database backup. Below is an outline  of a strategy which can be used to do this recovery. Initially,  you need to gather some data on the document that you want to recover  such as: a) What was the name of the client machine where the  file was last checked in? This is the set_client attribute. b)  What was the date/time of the last checkin? This is the set_time  attribute. c) What format was the document? This is the  full_format attribute. d) What was the name of the object? This  is the object_name attribute. With this information, the  following query can be issued from IDQL: select r_object_id from  dmr_content where any parent_id is null and set_client = <set_client  attribute> and full_format = <full_format attribute> and  set_time > DATE('<date>') This will retrieve a set of  r_object_id's that correspond to content objects that have been deleted  and meet your criteria. Once you have found the appropriate r_object_id  of the deleted document, you are ready to find the file. Using IAPI,  execute the following commands: API> apply,c,<r_object_id  of deleted dmr_content object>,GET_PATH 
API> next,c,q0 
API>  get,c,q0,result This returns the file system path to the  object. For example: /disk2/dm20/data/solar20o/content_storage_01/00000065/80/00/14/07  Now that you have the path of the content file, you can create a  new object with this content by doing the following: API>  create,c,dm_document 
0900006580005a65. 
API>  set,c,<object_id>,object_name 
SET> Restored Document 
OK  
API>  setfile,c,<object_id>,/disk2/dm20/data/solar20o/content_storage_01/00000065/80/00/14/07,<full_format  attribute> 
OK 
API> link,c,<object_id>,/Temp 
OK 
API>  save,c,<object_id> Now look for a document named  "Restored Document" in the /Temp cabinet. If it is there, then you have  successfully recovered the deleted document!

You may want to check out CYA SmartRecovery, it performs hot backups of Documentum objects and allows you to easily identify objects that have been lost or corrupted. It enables you to recover one, several, or thousands of objects back to their original states within the repository, without taking Documentum offline. You can find more information and reviews here: https://gallery.emc.com/docs/DOC-1554?viewTab=overview&version=14

chuckie4

Hello,

I've been attempting to use the instructions below to restore an object. Everything has worked great up until I began creating the new object it. I have already recovered the object id of the deleted record and was in the process of attaching the content to the new object:

API> create,c,dm_document
0900006580005a65.
API> set,c,<object_id>,object_name
SET> Restored Document
OK
API> setfile,c,<object_id>,/disk2/dm20/data/solar20o/content_storage_01/00000065/80/00/14/07,<full_format attribute>
OK
API> link,c,<object_id>,/Temp
OK
API> save,c,<object_id>

I keep receiving an error running the set api command (see below):

API> set,c,<newly generated objectid>,<name of object>

[DM_API_E_BADATTRNAME]error: "Bad attribute name '' for document/object."

Can someone shed some light on what values I need with this command?

Thanks much,

Charles

broberts

Hi All,

Before I begin I just want to identify myself as an employee of CYA, the solution mentioned in one of the postings by LL.

Chuckie4,

Based on your post you are asking why you get the [DM_ATI_BADATTRNAME] error, is this correct? Your api script is pretty straight forward. The cause of this error should be a simple syntax issue such as a copy/paste problem. The error reports "Bad attribute name '' for document/object." . The '' is the bad attribute. The oddity is it is not showing you any data between the single quotes as in the example :

API> create,c,dm_document
...
09000bd08001d298
API> set,c,l,obj_name
SET> my_doc_name
...
[DM_API_E_BADATTRNAME]error: "Bad attribute name 'obj_name' for document/object."

Unless the error you have posted is just missing the data between the single quotes due to the way the data was saved when it was posting.

The ap syntax you have is correct :

API> flushcache,c
...
OK
API> create,c,dm_document
...
09000bd08001d299
API> set,c,l,object_name
SET> My_document_name
...
OK
API> setfile,c,l,C:\Documentum\data\db3024\content_storage_01\00000bd0\80\00\12\a3.pdf,pdf
...
OK
API> link,c,l,/Temp
...
OK
API> save,c,l
...
OK
API> flushcache,c
...
OK
API> fetch,c,09000bd08001d299
...
OK
API> get,c,l,object_name
...
My_document_name

As everyone has mention, rebuilding the object is not a simple task. When the object is deleted in the repository the sysobject metadata is instantly lost and the related dmr_content objects are orphaned.

If you are lucky and you can figure out the dmr_content object related to the deleted sysobject you may be able to drill down to the filestore and find the content. From there reimport it back into the repository, as a new object losing all metadata, as you have attempted.

If the metadata is important you can restore a backup of the database to an alternate location, or restore the entire repository if you want. From there you can retrieve some of the metadata for a user to manually enter.

As LL mention CYA SmartRecovery is a product for this particular problem. SR will capture the sysobject along with all related objects (all metadata) as well as content. In the event you need to recover an object(s) you will be able to navigate the repository, or query on attributes, select the object and recover. The object is then restored back to the repository in the same state it was at the time it was captured maintaining all metadata (dates, id’s, folders, workflow, lifecycle, ect.. ect.. ) and content.

AkhilAgarwal

Hi,

The above issue looks similar to what I have been observing in my environment. Everything is fine until the creation of object but when I am trying to set the object name, it is giving an error. I tried different ways, cleared the cache, restart the App and content server, tried on 2 different environment but still same error.

API>set,c,0901bbc98018a663,Test

...

Error processing command:DfTypedObjectException:: THREAD: TP_http1 : 5588; MSG: [DM_API_E_BADATTRNAME]error: "Bad attribute name 'Test' for document/object."; ERRORCODE: 100; NEXT: null

API>set,c,0901bbc98018a663,TCS

object Id is the id which was created to assign an object name. Please help.

VHK

simple thing you missed out is you didn't specify for which atttribute the value has to be set like object_name or description. etc

AkhilAgarwal

Thank you for the email. Yes, I figured it out last night and it worked.

Now I am stuck at setfile command, I am getting the below error.

API>setfile,c,l,/usr/local/documentum/data/edmsna2/content_storage_02/0001bbc9/80/11/05/84.pdf

...

Error processing command:DfSysObjectException:: THREAD: TP_http1 : 5588;

MSG: error: "Cannot access file

'/usr/local/documentum/data/edmsna2/content_storage_02/0001bbc9/80/11/05/84.pdf'

due to Operating System error."; ERRORCODE: 100; NEXT: null

Am I doing something wrong here also? I am new to this stuff so everything

I am trying is a new learning .

Thanks again.

Thanks and Regards,

Akhil Agarwal

Documentum and Google Apps - Support

Jaguar Land Rover (JLR)

Victoria Court, 8 Dormer Place

Leamington Spa, CV32 5AE, United Kingdom

Mobile: +44-744 830 4172

e-mail: aagarwa4@jaguarlandrover.com

VHK

create,c,sop_doc /* returns r_object_id of new document */

set,c,l,object_name/* l references the last created or fetched ID */

Dept Proposal

set,c,l,affected_departments[0]

BusApps /* assigns an attribute value */

set,c,l,affected_departments[1]

Sales

setfile,c,l,c $:\$ tmp\my_doc.doc,msw6 /* assigns content file */

save,c,l

AkhilAgarwal

Hi,

I tried everything and in the format you listed above but "setfile" is not

working. I am getting the same error, I have tried to access the file on my

local machine but still the same error. Although, I able to access

/urs/local location but when I am trying the actual path like

/usr/local/documentum/...... , I am getting the error. I tried moving one

dummy file at /usr/local/ and made "dmadmin" as owner but still the same

error/

Thanks and Regards,

Akhil Agarwal

Documentum and Google Apps - Support

Jaguar Land Rover (JLR)

Victoria Court, 8 Dormer Place

Leamington Spa, CV32 5AE, United Kingdom

Mobile: +44-744 830 4172

e-mail: aagarwa4@jaguarlandrover.com

chiranjeevi

Hi Akhil Agarwal,

I had the same error faced while using setfile api command. However when I run the api script in IAPI tool in content server it did work with out any issue. May be you could try the same.

Regards,

Chiranjeevi