RPC 116 and ORA-03113

March 22, 2007 at 4:33 pm | Posted in Documentum and Oracle, Troubleshooting | Leave a comment

You may have encountered this error
It is returned by the DMCL to a Documentum client (like DFC, WDK, Webtop and so on) when the DMCL RPC client stub has encountered an error whilst waiting for a response from the server. Now this could be due to all sorts of things such as:

  • Network problems
  • Content Server session server crash
  • resource problem on the content server

Despite the text that usually returns with the error, network problems are the least likely source of this problems for most environments. More often than not the Content Server process/thread handling the RPC has hit some sort of problem (possibly a bug) and had to ‘bail out’ with an RPC error message ending up with the client.

The first place to look for information is the docbase log file ($DOCUMENTUM/dba/log) and the session logs ($DOCUMENTUM/dba/log/[docbaseid]/[username]). Often these will contain further error messages that reveal the real source of the problem. A support call to Documentum is often in order at this point particularly if it is a recurring issue.

ORA-03113 is really the Oracle counterpart of the Documentum RPC 116 error which is why I have put them together in this post. When an Oracle client (which for Documentum users means the Content Server) creates a session with Oracle it is connected to a process/thread in the Oracle server. Should this process encounter a problems that causes it to abort the client process receives a ORA-03113 error. Again this could be network problems but, particularly for Documentum Content Server setups where the Content Server is on the same machine as Oracle, this is less likely than other explanations.

I have encountered these problems in WebPublisher when running an ‘apply presentation’ command on a large number of files. In this particular case this turned out to be an Oracle bug which was resolved by upgrading from to The general approach is to look for process errors in the Oracle cdump log directory and if necessary raise a case with Oracle via metalink.

a last point: even though I have said network problems are the least likely source of problems, keep an open mind!

Leave a Comment »

RSS feed for comments on this post. TrackBack URI

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 )

Google photo

You are commenting using your Google 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 )

Connecting to %s

Blog at WordPress.com.
Entries and comments feeds.

%d bloggers like this: