Collect Diagnostic Logs

This page is accessed via Configuration and Administration > Technical Support > Collect Diagnostic Logs.

Note: This feature is currently not available for on-premises installations. On-premises customers should continue to use QDLogs on the command line.

Use this page when Oracle Support directs you to collect log and configuration files.

This page creates a zipped TAR file containing all the requested output, which resides on the OTM application server. When running a request and choose Execute, the TAR file name is shown on the results page (the file name will not be displayed if you choose Publish or Schedule). The file name can also be obtained in the logs by turning on the QDLogs logging ID. Oracle Public Cloud customers should specify this file name in the Service Request so that Support can retrieve the file.

Note: This cannot be run more frequently than every 5 minutes.

Additionally, see How to Use the qdlogs.pl Script to Collect Data for Service Requests for Oracle Transportation Management (Doc ID 1519887.1) on My Oracle Support.

Collecting Diagnostic Logs

Note: If the QDLogs ID is on (in any log), the system will spawn out to the qdlogs script on each server and wait for the exit code and output. This means that if thread dumps are being collected on one server, thread dumps will not start being collected on the second server until finished on the first server. In practice, the system  should run with QDLogs ID off, turning it on only if there is a problem with the Collect Diagnostic Logs collection itself.

1. Select the Logs you want to collect.Installation: script8 logs related to installation.
   1. BI Publisher: Gathers Oracle Analytics Publisher-related logs.
   2. OBIEE: Collects comprehensive set of log and configuration files related to OAS.
   3. Mail: Selects mail logs from mail validations.
   4. Data Integration: Collects data integration logs related to Oracle Cloud Infrastructure.
      Note: This option will be enabled in a future release.
2. Select the Analyzer check box to collects health-check information about the system such as configurations and settings. For more information see Note 1579683.1 on My Oracle Support.
3. Select if you want to collect Thread Dumps, and specify the count, interval, and delay for the thread dumps. The interval and delay you specify are in seconds. Thread dumps are snapshots useful in diagnosing performance issues. Set the count and interval to be enough to cover the time period being investigated. The delay is used to wait a certain amount of time before collecting the data.
4. Select if you want to collect JRA Recording information to help diagnose performance issues, along with the length and delay. The length and delay you specify are in seconds. Set the length to be long enough to cover the time period being investigated. The delay is used to wait a certain amount of time before collecting the data. The Settings field lets you choose:
   • Default: default recording settings determined by the collection script.

   • Heap: detailed heap information.

5. Select if you want to collect Heap Dumps to help diagnose memory issues.
6. If you change the Configuration Collection or Performance Collection to a "Non-Standard" value, then select the specific types you want to collect. The Standard Configuration Collection includes all Configuration Collectors except for OTM PROPERTIES. The Standard performance collection includes all Performance Collectors except for JVM DUMP.
7. If you selected "Non-Standard" for Configuration Collection, select the Configuration Collection Types to be collected.
8. If you selected "Non-Standard" for Performance Collection, select the Performance Collection Types to be collected.
9. If you are running cluster scalability, specify a cluster to which this request should be assigned.
10. Enter a User Role. When you run, publish, or schedule a recurring process, you can specify the user role used to perform the process, just like when you run agents. The user role can be used to specify a separate VPD role or another domain to run the agent. When a recurring process is modified, the user role of the recurring process can be modified as well.
11. Select a Log Profile to generate focused logging when reproducing an error for the specific action. You cannot select a log profile when you choose to schedule a process, as automatic generation of action logs is not supported.
12. Select Execute, Publish, or Schedule to determine when the process will be executed.
13. Click Submit.