DB monitoring scripts run as sysdba - what is best practice
Hi
Oracle 19c RAC with DG
Currently, the database monitoring scripts are run from oracle user crontab. There I have configured numerous scripts to be executed as sysdba privielge (sqlplus -s / as sysdba).
Since the scripts are run very often (some even every minute, like monitoring database status, etc), then the issue I am facing with that, lots and lots of audit records are generated due to that.
I have tried creating separate user (for multitenant environments, the common user and for noncdb the regular user), but I can't monitor everything with it, since, for example, when database is not in opened state, I cannot connect to it without sysdba. And also, when standby database is in recovery in mounted state, I cannot query lag also without sysdba.