Well, this is PL/SQL batch and not OCI/JDBC. Anyway, Oracle 9.2.0.4 as
methioned in the first post. Did you consider using Profiler to
analyze how much call to DBMS_APPLICATION_INFO contributes?
You can try simple PL/SQL loop with 100000 dummy iterations with and
without call to DBMS_APPLICATION_INFO and get the impact comparing
elapsed time.
Alternatively you can create private synonym for DBMS_APPLICATION_INFO
to your own package to measure impact on every call but it might
actually give significant measurement intrusion.

2006/6/8, Edgar Chupit <chupit@(protected)>:
> Nelson,
>
> Please note, that in 10g you don't have to call
> dbms_session.set_module to "register" you module in the database
> (tracefile). 10g allows you to piggyback module information using "End
> to End Metrics", for example, in java (this applies to all Oracle Call
> Interfaces) you can use OracleConnection.setEndToEndMetrics() and
> Oracle will not send message instantly, but will piggyback this
> information to next server call (parse/execute/fetch/etc).


--
Best regards,
Alex Gorbachev

http://oracloid.blogspot.com
--
http://www.freelists.org/webpage/oracle-l