Troubleshooting
Problem
My Guardium reports have blank database user for certain sessions. The sessions are local Oracle sessions where OS User authentication was used to login.
Cause
Oracle OS User authentication is a method to login to the Oracle database where no database user is specified. More details can be found in the Oracle documentation: Using the Operating System to Authenticate Users (External non IBM link)
This mechanism never supplies a database user during the session login and therefore Guardium can not record the database user.
Diagnosing The Problem
In Guardium reports, sessions using OS User authentication will have:
- Local connection (same client and server ip)
- Blank DB User, not ? DB User
- OS User and Source Program populated
- Most commonly SQLPLUS is the source program, but this is not a requirement
If the DB User is blank and OS User or Source Program is missing, most likely there is a performance problem resulting in dropped packets and missing data. This should be investigated as a separate issue see - Identifying and resolving common sniffer problems.
Resolving The Problem
Blank DB User is expected for sessions using Oracle OS User authentication. This is the expected behavior in all versions of Guardium as of the 'modified date' of this technote.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22008755