Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I have tons of books, have book marked tons of tutorials, which have helped, but this forum has answered those "impossible to find" solutions. I am thrilled with this site..."

Geography

Where in the world do Tek-Tips members come from?
malves (IS/IT--Management)
20 Aug 01 17:06
Hi,

We have a DW that uses BO as its reporting tool, at the database level (ORACLE) all queries are ran by the same user and from the same machine (the one where the BO server is installed) making impossible to check who is running what. when something is wrong with the queries the the users launch I would like to call them and asking what they are doing, however becouse all connections appear in Oracle with the same user/machine I don't know who is running what.

Is there any way to change the way BO connects to the database ?
Another solution would be call a procedure to set some oracle application info (dbms_application_info.set_module) however I don't know if I can change BO connection to call a procedure each time a user connects. Is it possible ?

Thanks in advance,
Miguel

TheVMan (IS/IT--Management)
24 Aug 01 8:49
Miguel,
The problem you are experiencing is the very reason that we tend to shy away from group ids connecting to the DB.  The obvious answer is to have your connection changed to use @variable('BOUSER') and @variable('BOPASS'), so that the currently logged in user will have his credentials passed to the DB.  Clearly this means you have to set each user up with select access to your DB.

Hope that helps.
V

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close