Robin Moffatt • 1/26/2010

Identify your OBIEE users by setting Client ID in Oracle connection

Read Original

This technical article addresses a common OBIEE administration problem: identifying which user's report generated specific SQL that is causing database performance issues. It provides a solution by showing how to use the `dbms_session.set_identifier` command within an OBIEE connection pool to tag database sessions with the OBIEE username, enabling DBAs and admins to trace SQL from the database back to the originating user and report.

0 comments
#oracle #Connection Pooling #Database Monitoring
Identify your OBIEE users by setting Client ID in Oracle connection

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Top picks — 2026 January
Paweł Grzybek • 1 votes
3
In Praise of –dry-run
Henrik Warne • 1 votes
4
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
5
Vibe coding your first iOS app
William Denniss • 1 votes
6
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
7
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes