I'm experimenting with Zabbix 1.5.3 and the new database monitoring module. After going through the pains of getting unixODBC functional (mainly becuase my distro's binary package was broken so I had to go get the sources and compile it myself), I'm unable to fully use it due to some flaws that may arguably be with unixODBC or perhaps the Oracle ODBC driver.
In order to run isql and establish an ODBC connection to Oracle I need to have three environment variables set. ORACLE_SID, TWO_TASK, and TNS_ADMIN.
TNS_ADMIN does not change and simply points to my tnsnames.ora file for database host and port mapping. I can easily set this before starting zabbix. ORACLE_SID and TWO_TASK need to have the database name I'm connecting to in addition to the isql command, therefore, I'm assuming they would be needed for any library based ODBC call as well.
The problem is that requiring these variables stops me from checking multiple databases. If I set them before launching zabbix I can check that database. I can't check any other Oracle databases though. The connections fail even though I have them defined in the ODBC configs.
If you could set these variables before making the ODBC call then I assume that would fix the problem.
In order to run isql and establish an ODBC connection to Oracle I need to have three environment variables set. ORACLE_SID, TWO_TASK, and TNS_ADMIN.
TNS_ADMIN does not change and simply points to my tnsnames.ora file for database host and port mapping. I can easily set this before starting zabbix. ORACLE_SID and TWO_TASK need to have the database name I'm connecting to in addition to the isql command, therefore, I'm assuming they would be needed for any library based ODBC call as well.
The problem is that requiring these variables stops me from checking multiple databases. If I set them before launching zabbix I can check that database. I can't check any other Oracle databases though. The connections fail even though I have them defined in the ODBC configs.
If you could set these variables before making the ODBC call then I assume that would fix the problem.
)
Comment