Documentum Performance Tracing

This page provides links to my pages on how to trace various Documentum applications. If you see an application but no link then I haven’t got round to providing the tracing details yet; drop me a note in the comments and I’ll make it a higher priority. If you don’t see the application you want to trace, drop me a note in the comments and I’ll look into it.

There are many different types of tracing available in Documentum. This page deals with just the performance traces DMCL level 10 and DFC tracing. Which one you use depends on whether you are working with Documentum 5 (DMCL) or Documentum 6 (DFC). If you still work with EDMS98 or 4i you won’t find any information here – I haven’t worked with those products for years!

Documentum 5 – DMCL Tracing

  • WDK applications
  • Jobs
  • Methods
  • Lifecycles
  • DFS
  • Custom code
  • Workflow methods
  • Java method server
Advertisements

9 Comments »

RSS feed for comments on this post. TrackBack URI

  1. Hello, i need get the session logs of all user was logged between an date range, with dql or sql in the database. Please, Do you know how to do this?
    Very Very Thanks

    Peter Cayo from Perú

    • Session logs are not recorded in the database so not possible with SQL or DQL. If you look in the %DOCUMENTUM%\dba\logs subdirectories you will find individual session logs, it is possible you could find the information you need from analysis of the content of these files. Note that they do get cleaned up on a regular basis by the dm_LogPurge job

  2. Hello, i have solved performance problem and encountered with interesting problem. I have trouble with big DQL query(many symbols) which i want to transform to SQL with GET_LAST_SQL admin. method. Resulting SQL is cut off. I suppose it’s because of some limitation in the chain of processes which happen when I execute this method. May be SQL go to me by some protocol which have maximum length of the data packet. But i can’t find any useful information about how it works and what constraint it has. May be you can answer on my question. i want to know how it’s made and there is workaround for this problem.
    Thanks in advance.

    • Unfortunately this seems to be one of the problems with GET_LAST_SQL. I’m not sure it’s documented but probably the buffer in the Content Server used to store the sql is only of a limited size.

      There are a number of alternatives you could try, some of them are documented in the Tools and Tracing section of the Content Server Administrator’s guide.

      Alternatively you could trace at the database level. If you are using Oracle there is a technique described in my article http://www.xense.co.uk/pdf/SessionManager/SQL_Extended_Tracing.pdf.

  3. Thanks a lot.

  4. hello.

    i need some advice…we ran a queries to search for a single document number across all sectionson both test and prod machines.
    my account : 1 sec
    admin account : 50 secs

    i there anyway I can trace why the difference happened and how to tune it?

    Thanks.

    • So you have a single DQL that performs differently depending on whether you are a admin (superuser?) or not? So first step is find the SQL that is generated. Run in DA with ‘Show SQL’ option selected and you should see whether the SQL is different between admin account (it will be if admin is superuser). then you need to look at the database to see what the difference is – depends which database you use.

  5. Hi,
    we are using a webtop v5.3 sp5 based application. customers are facing major performance issue on the application. Like it will taking hail lot of time after clicking the action and page comes up. Please advise the detail level for the analysis. If you just point out the sections where we can look out to get better performance. If you have any related document to that please provide us. We are using oracle as Data base.
    Looking for your response.

    • You need to use the techniques described in https://robineast.wordpress.com/documentum-performance-tracing/dmcl-tracing-wdk-applications/ to generate a dmcl trace. Then look in the trace for long running queries or commands. The resolution then depends on what you find.

      Be aware that in versions of Documentum prior to D6 turning on a trace causes all sessions connected to the application server instance to be traced. To make your life easy you would trace when the user has exclusive access to the server.


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.
Entries and comments feeds.

%d bloggers like this: