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
- In the server's dm.cfg file (Dimensions Listener restart required) DM_SDP_TRACE <path to existing directory> - In the Desktop Client to trace a specific operation (From 14.x, no Dimensions Listener restart required)
Tracing using this method does not require SQL_ TRACE to be set or the Dimensions Listener to be restarted. Also, running trace in this way will also report any latches and/or waits.
Sporadic issue, appsrv processes are not running when the listener is being started. Customer switched on the listener trace and sees the following dmappsrv 2013/03/11 13:02:02 I P3432 T3444 Connecting to database@DIM9
When attempting to login into the Desktop Client, an error occurs similar to the following in the listener trace files: DMAPPSRV 2014/09/16 09:30:18 I P11228 T12160 Connecting to cm_typical@DIM10 DMAPPSRV 2014/09/16 09:30:19 E P11228 T12160 Pcms error: 0, Error: Unable to connect to database "cm_typical"
