error msg="Error pinging oracle: Invalid as: sysdg"

[kebagb]

I'm submitting a ...

• [ ] bug report
• [] feature request

What is the current behavior?

Unable to connect to Oracle DB when using "as sysdg" option

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

I don't know if this is a bug or some restriction within the way we can use the DATA_SOURCE_NAME string. I'd just like to clarify whether what we are trying to do is valid/supported.

What is the expected behavior?

I had hoped that we could use the "as sysdg" option in the same way that we can use "as sysdba"

What is the motivation / use case for changing the behavior?

We have a requirement to use this option when connecting to one of our databases.

Please tell us about your environment:

Oracle 19c.

[wes-pro]

I needed this also - to be able to monitor Standby databases using SYSDG role. This is limitation of https://github.com/sijms/go-ora on which oracledb_exporter currently depends on. These are my changes (I'm not Golang programmer but it seems trivial and works for me): https://github.com/sijms/go-ora/pull/563/files With these changes I can use sysdg role similarily to how SYSDBA is handled, i.e.: DATA_SOURCE_NAME=oracle://user:password@node-vip:1521/unq_name?dba+privilege=sysdgd "sysdgd" is not typo - I used internal name taken from python oracledb client.