Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Oracle Database Appliance (ODA) (MOSC)

rac gv$session tracking down osuser's SQL_ID's

Jun 17, 2020 10:42AM edited Jul 1, 2020 5:05AM in Oracle Database Appliance (ODA) (MOSC) 2 commentsAnswered

Hi MOSC,

Given this query and result:

select distinct osuser, username, schemaname from gv$session order by 1;

Result:

elwright TEMPOREAD HELXXXXX

( The result was only temporary, if we run that query today it returns no rows for "elwright" as they have disconnected.)

We are trying to find the SQL_ID's that osuser "elwright" ran via username "TEMPOREAD".
A problem is that many connections use the login/username "TEMPOREAD" to query schemaname, HELXXXXX, in the ODA db.

And as such we get 1000+ SQL_ID's for TEMPOREAD and can't pin-point the one that osuser "elwright" ran.

We found "elwright" in DBA_AUDIT_SESSION with SESSIONID = 93318728

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month