I had planned to start running all of my “Tips” posts in the EMC Developer Network, but I wanted to editorialize a little in this Tip, so I’ve decided to throw it up here. This issue arose when I installed a new repository into an existing environment. It is a documented issue, though the Support guys need to read that documentation a little more closely.
dm_audittrail
Tips: Don’t Depend on That Sequential Object ID
I recently ran into a situation that challenged one of my basic beliefs in the setup of the Documentum repository, object ids may not be sequential!!!
What you say? Impossible you say? Yet it happened.
What I encountered isn’t a widespread phenomenon, but it could happen to you.
What Happened
Tips: Taming the Documentum Audit Trail
The Documentum Audit Trail. It is one of the un-tamed beasts in many Documentum deployments. The requirements for auditing often come into conflict with the reality of the out-of-the-box functionality. To makes things useful for the average user, organizations tend to set earlier than desired audit purges and/or severely restrict what they audit which can lead to important actions being overlooked.
On the other hand, keeping everything makes finding what you want an expensive proposition.
Word of Pie 