GWME-7.2.1-00 version 4127 Rollup Patch Details

h5. GW-internal notes on creating the new release

* The following files need to be updated for this new patch: \\
http://geneva/groundwork-professional/trunk/monitor-professional/profiles/plugins/check_oracle_by_jdbc \\
http://geneva/groundwork-professional/trunk/monitor-professional/profiles/plugins/check_oracle_by_jdbc.gdma \\
http://geneva/groundwork-professional/trunk/monitor-professional/profiles/plugins/check_oracle_db \\
all of them being placed into the {{/usr/local/groundwork/nagios/libexec/}} directory as usual.

* The following file needs to be updated for this new patch: \\
http://geneva/groundwork-professional/trunk/monitor-professional/monarch/bin/monarch_assign_service_to_host \\

blah blah blah

h4. Changes made in this patch installer

(beyond those included from patch 4125)

h5. Miscellaneous fixes

* The {{/usr/local/groundwork/nagios/libexec/check_oracle_db}} plugin has been overhauled.
** It will no longer generate a misleading OK result when in fact the underlying SQL query produced no result rows.
** Additional types of query-execution exceptions are now correctly sensed as failures.
** Command-line option flags are now parsed correctly. This will prevent argument-position errors, such as swapping the order of the warning and critical thresholds, which would have gone unnoticed by the previous version of the plugin. (Correct ordering of the plugin options is no longer presumed. With this new version and the correct option flags, options may now be specified in any order.)
** Much better debug output is now provided, under control of the new {{\-d}} option. This can assist in manual-run situations where there is some mystery as to what the script is seeing internally as results from the underlying SQL query.
** Most importantly, the {{\-n}} option value can now be the heading of the column whose values you wish to compare against the warning and critical thresholds. This is far more reliable that using a column number, partly because the column numbering starts with 0 (which is probably unexpected, and was formerly undocumented), and because there was no obvious way to check that you had actually selected the particular column you were interested in. As of the availability of this version of the plugin, using a column number is therefore deprecated, in favor of the heading.
** A proper usage message is now available. It can be spilled out by running the plugin without any arguments. It is quite extensive, and documents in detail the requirements for the SQL query to be run.
** A bunch of other internal improvements have been made as well, such as emitting more descriptive error messages.