-
Titre
Oracle Dataguard Standby database monitoring failed with table or view does not exist -
Description
Oracle Dataguard Standby database monitoring failed with "table or view does not exist" when customer using a non-sysdba account. The error was "table or view does not exists".
Below is the query which failed,SELECT timestamp,error_number, MESSAGE,facility FROM (SELECT timestamp, 'ORA-' || ERROR_CODE AS error_number,MESSAGE, facility FROM sys.v$dataguard_status WHERE severity IN ('Error', 'Fatal') AND timestamp > SYSDATE - 30 / 1000 / 60 / 60 / 24 ORDER BY message_num DESC) ERROR_TEXT WHERE rownum -
Cause
The table or view exists in the monitored standby database, however the account used by foglight to monitor the database is a non-sysdba account and it does not have the permission to query this table or view.
-
Résolution
A standby database will be in "Mount" state to restrict the normal user access. Only sysdba user can connect to the database. Hence it is recommended to use a "sysdba" account to monitor a standby database.
We recommend to monitor the standby database with sysdba system privilege to enable retrieving data when the standby is in mount mode. Monitoring with a normal user (unchecked sysdba), the agent will not be able to retrieve any data when the standby is in mount mode.
Enhancement ID ORAFOG-855 has been created to add notes regarding this issue to the Oracle cartridge installation guide.
-
Informations supplémentaires
We recommend to monitor the primary database with sysdba system privilege for better supporting during switchover. When data guard switches over between primary and standby, standby database agent will be able to connect to the database with sysdba system privilege and retrieve data.