not opening pdf file..[DM_OBJ_MGR_E_FETCH_FAIL]error: "attempt to fetch object with handle 06014cde

Hi,

when i am opening the file it is showing [DM_OBJ_MGR_E_FETCH_FAIL]error: "attempt to fetch object with handle 06014cde8055a479 failed" error.

I tried to find out the issue i dump the obect '09014cde80768cd1' attribute it was showing i_contents_id = '06014cde8055a479' but when i tried to look for this id in dmr_content this id is not present in dmr_content but when i run the following query

select r_object_id, rendition, content_size, full_format, format from dmr_content where any parent_id in (select r_object_id from dm_document where r_object_id='09014cde80768cd1')

it returns the r_object_id = '06014cde8055a478'. my question is how it is this possible ? .. i_contents_id should be 06014cde8055a478 for the object '09014cde80768cd1'

can someone explain this to me....(why not in sync).

Thank you,

Ujjwal Tiwari

Find more posts tagged with

Documentum

Comments

bacham2

There can be multiple dmr_content objects per sysobject: primary content + renditions. I suppose that 06014cde8055a478 is a rendition (check rendition attribute: if > 0 then it is a rendition). The content ID stored under i_contents_id is the primary content. Apparently, it's not there which means that your object is corrupted. Shouldn't really happen. Maybe someone issued the DESTROY_CONTENT admin method on it (I've seen that before) which would have destroyed this object.

acarver

As bacham2 mentioned, a document can have two (or more) renditions/records in dmr_content.

Each rendition should have an associated file in the server's storage directory.

A couple of ideas to help you dig deeper:

1. Is 06010...a478 the primary rendition, i.e. its file format matches the dm_document's format?

2. Does 06010...a479 exist in dmr_content (perhaps with a different parent_id than 09...cd1 ) ?

3. Use the GET_PATH api command to determine the path and file associated with 06010...a478 ;

the next file in the directory should be associated with 06010...a479 - presumably it does not exist since you are getting the FETCH_FAIL error.

It will be interesting to figure out if the file ever existed, or perhaps it exists with some problem preventing retrieval ( 0 bytes, open file, ...) .

4. Is 09...cd1 the latest version of the document? Could the system have run one of the jobs that prunes old versions or renditions?