RAC agents do not collect data after changed credential from using sysdba to nosysdba (4229543)

After applying a new Oracle patch to an Oracle instance, an exception for the DBO_Instance_General and DBO_Usability collections appear.

There are three conditions

• RAC agents running with non-sysdba
• "DBO - collection status" fired for collection DBO_Usbility and DBO_Instance_general
• The exception ORA-09042 in agent logs.

ERROR   [RAC-NAME-lowPriorityPool-2630-[DBO_Instance_General][]] com.quest.qsi.fason.oracle.collection.processor.DBOInstanceProcessor - Failed to run DBOInstanceGeneralProcessor processor of DBO_Instance_General collection of HOSTNAME-INSTANCE instance.
java.lang.RuntimeException: Failed to execute collection [DBO_Instance_General], reason=ORA-00942: table or view does not exist

This causes RAC agents not to collect data and the collection status alarm to fire.

WORKAROUND

Restart the RAC agent and the RAC instance agent in Administration | Agents | Agent Status

or 

Select the RAC agents from the Global View Databases Dashboard and click Settings | Stop Monitoring followed by Settings | Start Monitoring

STATUS

This has been identified in the Oracle cartridge Release Notes as a known issue FOM-76