DBCollect/Usage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 45: | Line 45: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
= Explanation of all options = | |||
<code></code> | |||
== help == | |||
<code>--help</code> or <code>-h</code> | |||
Shows usage (list of all arguments) | |||
== version == | |||
<code>--version</code> or <code>-V</code> | |||
Shows detailed version, build and copyright details | |||
== debug == | |||
<code>--debug</code> or <code>-D</code> enables debugging. This will result in more logging (sometimes dumping unhandled Python exceptions and traces. | |||
Even without this option, debug info is written to the {{dbcollect}} logfile for troubleshooting purposes. | |||
== quiet == | |||
<code>--quiet</code> or <code>-q</code> hides most normal terminal output (except errors). Useful for scripted runs (such as with [[DBCollect/Ansible]]) | |||
== overwrite == | |||
<code>--overwrite | -o</code> | |||
Overwrites the previous dbcollect ZIP file if it exsts. |
Revision as of 13:47, 28 May 2024
Usage
Verify correct install
# Show version
dbcollect -V
# Show usage
dbcollect -h
# Update to last version (if the system has https access to github)
dbcollect --update
Run with default settings
# Default run
dbcollect
# If you get Error DBC-020 (zipfile already exists), you can overwrite the old zipfile:
dbcollect -o
# or
dbcollect --overwrite
Resolve AWR reporting issues
dbcollect checks for prior AWR usage to make sure it will not trigger Oracle license violations ( More info)
If you get Error [DBC-E021] No AWR or Statspack detected:
# If you are sure you have Diagnostics Pack license:
dbcollect --force-awr
# If you want to ignore databases without AWR usage:
dbcollect --ignore-awr
# If the problem databases are not important, try excluding them:
dbcollect --exclude inst1,inst2
Explanation of all options
help
--help
or -h
Shows usage (list of all arguments)
version
--version
or -V
Shows detailed version, build and copyright details
debug
--debug
or -D
enables debugging. This will result in more logging (sometimes dumping unhandled Python exceptions and traces.
Even without this option, debug info is written to the dbcollect logfile for troubleshooting purposes.
quiet
--quiet
or -q
hides most normal terminal output (except errors). Useful for scripted runs (such as with DBCollect/Ansible)
overwrite
--overwrite | -o
Overwrites the previous dbcollect ZIP file if it exsts.