To enable, from the Desktop Client Console window or when logged into DMCLI, run the following command: set sdp_ trace on /user_directory=<drive:\path to a directory> Once this is set, reproduce the issue which you wish to trace.
The most obvious way to perform custom actions at login/logout is to implement HttpSessionListener interface - which is standard Java interface - (with methods sessionCreated/sessionDestroyed) and declare custom listener in web.xml.
A problem arose where tracing of the Dimensions listener was required so -trace and -tracedir were added to the listener.dat in order to generate the logs. However following an attempted restart of the listener no logs were produced in the target directory specified by -tracedir.
The listener then needs to be restarted in order for this to take effect. However all commands run to the server will be logged. This option must be used for server based or standalone Dimensions commands that are run outside of DMCLI, such as: replicator, pdiff, upload, download etc.
tnslsnr LISTENER (also the oracle listener is running) 3 Turn on tracing at the ADMIN level and re-execute the operation. Find below the link to the document about setting up the Oracle tracing
1. Stop the Dimensions CM Listener Service 2. Edit the file $DM_ROOT\dfs\deploy_config.dat and make the following changes 3. Modify the line: #log_dir=c:/temp/ by removing the # and ensuring the on the CM Server that the directory specified exists and is writeable for all users
