DBCollect/Detection: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
* If no logons file is specified, {{dbcollect}} runs the command <code>ps -eo pid,user,group,args</code> to find all running processes on the OS. | * If no logons file is specified, {{dbcollect}} runs the command <code>ps -eo pid,user,group,args</code> to find all running processes on the OS. | ||
* Running instances are matched if the args match <code>ora_pmon_<oracle_sid></code> | * Running instances are matched if the args match <code>ora_pmon_<oracle_sid></code> | ||
* If the <code>--included</code> option is given, only instances that are explicitly included will be processed (a warning message is given for non-included instances) | |||
* If the <code>--excluded</code> option is given, only instances that are not explicitly excluded will be processed (a warning message is given for excluded instances) | |||
Revision as of 14:54, 31 August 2025
Instance detection
This page describes how dbcollect detects (running) Oracle instances and their correct ORACLE_HOMEs.
Running instances
- If a logons file is provided (using
--logons), dbcollect will NOT automatically detect instances, but only connect to the services listed in the logons file. - If no logons file is specified, dbcollect runs the command
ps -eo pid,user,group,argsto find all running processes on the OS. - Running instances are matched if the args match
ora_pmon_<oracle_sid> - If the
--includedoption is given, only instances that are explicitly included will be processed (a warning message is given for non-included instances) - If the
--excludedoption is given, only instances that are not explicitly excluded will be processed (a warning message is given for excluded instances)