ODP and ADO and a trigger - problem

Question

I have written a simple trigger to turn on tracing for a session based on the username:
It works fine through sqlplus. The application works when run using JDBC and native(?) java. But when we use hibernate and ODP.net and ADO.net The session goes into a loop of recursive sql and gets an ORA-36 too many recursive levels. I am not a java developer and I am at a loss on how to proceed. It appears to be firing the trigger or have fired the trigger, and then look for global_db_name until it dies.
CREATE OR REPLACE TRIGGER gopal_user_login_trigger
AFTER LOGON ON DATABASE
DECLARE
     user_name VARCHAR2(30);
BEGIN
SELECT username INTO user_name FROM sys.V$SESSION
WHERE audsid = USERENV('SESSIONID') AND audsid != 0 ;
IF UPPER(user_name) = 'GOPALASSETUSER'      
THEN
     DBMS_MONITOR.SESSION_TRACE_ENABLE(NULL, NULL, true, true);
END IF;
EXCEPTION
WHEN NO_DATA_FOUND then null;
END;

Answer 1

Hi,
Thanks for the bug number - that helped alot.
Why the global_db_name lookup, I do not know. It appears to be part of the logon processing that follows the trigger.It is, indeed, part of the logon process and is called by internal code so that makes sense now.
If you have MetaLink support, I would recommend opening an SR. One simple thing that I might suggest is to set "enlist=false" in your connect string if you can and test with that.
Thanks,
Mark