Follow these procedures to capture debug information.
- Before enabling debug, reproduce the problem with the least run
Debug captures a lot, the resulting
zipfile 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
If the problem area is known, then debug can be constrained to a particular module by including the
$ 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_dirdirectory 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 –debugoption.Running this command generates both debug for daemon and include debug in all client runs:
$ orachk –d start –debug
$ exachk –d start –debugWhen debug is run with the daemon, Oracle ORAchk and Oracle EXAchk create a daemon debug log file in the directory the daemon was started:
- Collect the resulting output
zipfile, and the daemon debug log file if applicable.