Description of problem:

Oracle resource agent has parameter monuser used for connectiong to database to perform monitoring operation check. If this user fails to login into database the sysdba user is used instead however this is not logged anywhere. 

Example: monuser is created with pcs command with password which doesn't match its password on database level. In such a case monitoring operation is in debug logs reported as successful but there is no mention that monitoring operation was finished by sysdba user and not monuser. This brings confusion and also involves generating of audit logs each time sysdba user access database. According to monuser description audit logs are not supposed to be generated when monuser is used:


--------------
monuser - Monitoring user name. Every connection as
sysdba is logged in an audit log. This can
result in a large number of new files created.
A new user is created (if it doesn't exist) in
the start action and subsequently used in monitor.
It should have very limited rights. Make sure
that the password for this user does not expire.
--------------




Version-Release number of selected component (if applicable):
resource-agents-3.9.5-105.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. create oracle resource with monuser with invalid password 
2. monitor logs (monitoring op is successful - now failure/warning)
3.

Actual results:
sysdba user is used instead of monuser but there is no way how to find out (audit logs are generated)

Expected results:
warning gets printed in case monitoring operation is handled by sysdba user instead monuser

Additional info: