If the issue occurred in a background process, it is best to create a debug background process that
can be reused when needed. Follow these steps:
- Go to Database Manager.
- Select the Format info.startup.
- Search for the background process you want to debug, such as alert.startup.
- Add the word DEBUG to the end of the name; for example, alert.startup.DEBUG.
- Click the Add button.
- In the array to the right, enter the debug parameters, such as -RTM:3, -debugdbquery:999
- Click Save.
- Go to System Status.
- Stop the existing background process by using k in the command column in front of the process,
- Click Start Scheduler and select the debug version of the background schedule from the list to start the debug process.
- Execute the steps leading up to the issue. Stop the debug background process again and start the regular background process as discussed in the previous steps. These steps limit the number of processes that are traced.
Important: Use all the debug parameters necessary, while trying to avoid “over-debugging” the issue (where you trace additional steps or users that do not help troubleshoot the issue).
Another option is starting a servlet with trace parameters and connecting to it for reproduction, for example,
sm -bg scheduler event1 60 1 -rtm:3 -debugdbquery:999 -utallocmode:2 -log:../logs/event_pmo1.log
SM Admin should be engaged to make decision which option is best.