How to Capture Debug Output

Follow these procedures to capture debug information.

Before enabling debug, reproduce the problem with the least run necessary.
- Debug captures a lot, the resulting zip file can be large so try to narrow down the amount of run necessary to reproduce the problem.
  Use relevant command line options to limit the scope of checks.
Enable debug.

If you are running the tool in on-demand mode, then use -debug argument.

If the problem area is known, then debug can be constrained to a particular module by including the -module argument too.
```
$ orachk -debug [-module [ setup | discovery | execution | output ] ]
```
```
$ exachk -debug [-module [ setup | discovery | execution | output ] ]
```
When debug is enabled, Oracle Orachk and Oracle Exachk create a new debug log file in:
- output_dir /log/orachk _debug_ date_stamp _ time_stamp .log
- output_dir /log/exachk _debug_ date_stamp _ time_stamp .log
The output_dir directory retains a number of other temporary files used during health checks.

If you run health checks using the daemon, then restart the daemon with the -d start -debug option.

Running this command generates both debug for daemon and include debug in all client runs:
```
$ orachk -d start -debug
```
```
$ exachk -d start -debug
```
When debug is run with the daemon, Oracle Orachk and Oracle Exachk create a daemon debug log file in the directory the daemon was started:
```
orachk_daemon_debug.log
```
```
exachk_daemon_debug.log
```
Collect the resulting output zip file, and the daemon debug log file if applicable.