[checkmk-commits] Check_MK Git: check_mk: Renamed ORACLE_HOME_REMOTE back to REMOTE_ORACLE_HOME

Module: check_mk Branch: master Commit: 2de6e343db6819848304ebff1966f4861da2ddc3 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=2de6e343db6819… Author: Mathias Kettner &lt;mk(a)mathias-kettner.de&gt; Date: Tue Apr 14 16:09:27 2015 +0200 Renamed ORACLE_HOME_REMOTE back to REMOTE_ORACLE_HOME --- .werks/1903 | 2 +- agents/plugins/mk_oracle | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.werks/1903 b/.werks/1903 index 1ac0a5f..64c61c2 100644 --- a/.werks/1903 +++ b/.werks/1903 @@ -22,7 +22,7 @@ in downtime you'll put all other database checks from mk_oracle in a downtime as H2: Configuration You need an Oracle Client. You could use the remote option from an existing Database Server -to monitor another Server. It is recommended to set <tt>ORACLE_HOME_REMOTE</tt> in <tt>mk_oracle.cfg</tt> +to monitor another Server. It is recommended to set <tt>REMOTE_ORACLE_HOME</tt> in <tt>mk_oracle.cfg</tt> for the <tt>ORACLE_HOME</tt> which should be used for all remote connections. An existing <tt>ORACLE_HOME</tt> could be used as well, but do not do that in mixed configurations diff --git a/agents/plugins/mk_oracle b/agents/plugins/mk_oracle index f07030c..3adfdcb 100755 --- a/agents/plugins/mk_oracle +++ b/agents/plugins/mk_oracle @@ -694,7 +694,7 @@ function set_oraenv () { if [[ "$SID" =~ ^REMOTE_INSTANCE_.* ]] ; then # we get the ORACLE_HOME from mk_oracle.cfg for REMOTE execution - ORACLE_HOME=${ORACLE_HOME:-${ORACLE_HOME_REMOTE}} + ORACLE_HOME=${ORACLE_HOME:-${REMOTE_ORACLE_HOME}} else # we need to keep an existing ORACLE_SID in remote mode