Ad Widget

Collapse

oracle odbc monitoring using role based connects (sysdba/sysdg/...)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • robert.ortel
    Junior Member
    • Jun 2023
    • 5

    #1

    oracle odbc monitoring using role based connects (sysdba/sysdg/...)

    Hi,

    I want to do some oracle checks using odbc on ASM instances (login as sysdba) and mounted physical standby databases (login as sysdg). But using zabbix odbc based checks I do always fail to login with this error:


    Cannot connect to ODBC DSN: [SQL_ERROR]:[28000][1017][[Oracle][ODBC][Ora]ORA-01017: invalid username/password; logon denied]​


    The identical logins work well using sqlplus. I am very sure on the oracle side everything is correct. But I noticed that zabbix documentation only tells with agent based monitoring that "as sysdba" can be used.


    - Are such role based logins even possible using zabbix "database monitor" items (so ODBC)?
    - If yes, how? Is there a trick how to configure those regarding the username or password definition (how and where to include that "as sysdba")?


    Thanks,
    Robert
  • robert.ortel
    Junior Member
    • Jun 2023
    • 5

    #2
    Hi,

    as nobody posted here and I had no idea as well I wrote me a shell script to use as an external script which logs into the database using sqlplus and executes a provided sql file. With that I can use any role (SYSDBA, SYSASM, SYSDG, ...) and so can connect to an ASM instance or physical standby's in mounted mode.

    This script returns the result as a CSV, which zabbix prepocessing can convert to JSON which then can be used with JSONPath to extract the data.

    I do use this script on a zabbix proxy server which has the oracle client installed to make use of the oracle tools.

    Regards,
    Robert

    Comment

    • robert.ortel
      Junior Member
      • Jun 2023
      • 5

      #3
      PS: This is no more using ODBC of course. But what matters for me is that it is still a remote connect executed not on the database server itself (by an agent running there).

      Comment

      Working...