This section discusses:
Trace flags in PeopleSoft tools.
Sybase API-specific tracing.
Trace Flags in PeopleSoft Tools
When reporting problems to customer support, it is advisable to generate files with traces of the problem that you want to report. Use the trace flags incorporated in PeopleSoft tools to generate these files. The trace flags are accessible through the configuration files for the Process Scheduler and the application server and through the selection of several flags when using the PeopleSoft Configuration Manager on your developer workstation.
Use “TRACESQL=63” to display the SQL statements executed when using PeopleSoft applications. This trace flag is very useful to identify problems in the SQL being executed against a database that hosts a PeopleSoft application.
The trace flag will show the details about the execution of a SQL statement, including:
if the statement was recompiled.
if the statement was using an old query plan.
the time it took to execute.
the time between executions.
if the SQL was parametrized.
Sybase API-Specific Tracing
When using Sybase, you can select from three SQL Trace options that you can use to enable very detailed Sybase tracing:
Database API-specific Calls
Sybase Bind Information
Sybase Fetch Information
To set these options, use the Trace tab in the PeopleSoft Configuration Manager. Keep in mind that online performance will be affected.
The output of the Sybase tracing can be found in %TEMP%/SYBxxx.TMP, where xxx is a random integer that is different for each file based on each connection.
If you select any options other than Database API, Sybase Bind Information, and Sybase Fetch Information, the tracing output will be found in %TEMP%/DBG1.TMP.
Note: Only use tracing for debugging purposes, since performance will be affected. Depending on what level of tracing you select, a very large file can be created. To turn tracing off for Windows, clear the boxes in Configuration Manager.