Simulate a deadlock - Lock the dm_document subtype table

Hello ,

I have dfc java process which inserts new documents into a custom document type. I have a test case where i need to see the outcome of the process if there is a deadlock . Is it possible to lock the entire custom type table and then run the the process to see the outcome . Example in Oracle you can lock the entire table for update. Can this similarly be done in documentum . I have access to the da / dqleditor

How can i enforce a deadlock considering new documents are to be inserted.

Find more posts tagged with

Comments

dnvhariprasad

if you want to lock the object type you can set proper acls. However I dont think that suits your requirement.

DCTM_Guru

There are multiple concepts that are getting thrown around with thought to the real definitions. The dm_document subtype table is still dependent on the dm_document/dm_sysobject table when you are creating a new document.

Since the Content Server manages deadlock issues behind the scenes, you will have to simulate this on the backend via the database. So if you want to lock the entire dm_sysobject_s table, use your Oracle procedure.

dnvhariprasad - ACL is only available once an document instance is created (in other words, row in the dm_sysobject table is created). There is NO ACL on the actual table itself.

Hartmut_Clausen

I have never used it myself, but the adminstrative method "set_apideadlock" looks like the tool you are searching. Have a look at the DQL Reference for details.