Troubleshooting
Problem
This document outlines the steps to generate a UDA trace on Windows without having to reboot the server. Sometimes it is impractical to reboot production or critical development servers. You will have to restart the Cognos Services and the setting of the Environment Variables to enable the trace, which is only good for the current session. If you do not need to keep UDA tracing active, for instance while troubleshooting a specific issue, this may be a good solution. [NOTE:] This may not work when running VMware. If a trace file is not generated when following the steps below, you may need to create the environment variables as outlined in the Related Documents listed below. A server reboot would be required.
Resolving The Problem
Steps:
- Stop the Cognos Service.
- Launch a Windows command prompt.
- Set the required environment variables by running the following commands
- set TRACE_FILE=C:\uda.log (Note: This can be set to any valid directory/file_name where the user has write permission)
- set TRACE_LAYER_DMD_SQLAPIRW=0x2
- Change directory to \Cognos install location\bin\
- Type startup.bat
- Launch a Browser and run the report you are trying to capture the UDA trace for.
- Check C:\uda.log to ensure you have captured the UDA trace information.
- To stop the tracing, close the DOS session, parameters are only good for the session.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21373137