TIP: Tracing a session via a logon trigger

Awhile back I found a tip which has come in handy quite a few times. Just recently I was troubleshooting an ORA-03124 error which occurred during a run of a BI tool. The BI tool spawns many sessions while gathering and processing data so its not practical to sit there, grab the sessions information and turn on tracing manually.

From Oracle Magazine Tip for Week of June 26, 2006:

CREATE OR REPLACE TRIGGER ON_LOGON_SCOTT
AFTER LOGON ON DATABASE
WHEN ( USER = 'SCOTT' )
BEGIN
execute immediate 'alter session set events ''10046 trace name context forever, level 12''';
EXCEPTION
WHEN OTHERS THEN
NULL;
END;

Of course, don't forget to disable it after!

Jinitiator Vulnerability

Great analysis over at Integrigy about on the recent Jinitiator vulnerabilities. If you are running Jinitiator versions 1.1.8.3 to 1.1.8.25 then you should definitely take a look.

Integrigy Jinitiator Vulnerability Analysis

Port Pools

Every now and then I get a request asking which port a specific service is using. The server team may ask for a list of ports so they can be reserved, etc. The Metalink document below lists all the ports required and which services run on them. It also has a nice utility which will calculate the ports required depending on the port pool you choose when installing or cloning.

Subject: FAQ: Cloning Oracle Applications Release 11i Doc ID: Note:216664.1

See question number 21: What is the port pool? What if I want to give a specific value to a Server Port?

Note: the port calculations given by the utility are defaults. They may have been changed in your environment for various reasons. For example, we may have to change the port listed below because it interfered with another application.

<jcache_port oa_var="s_java_object_cache_port" oa_type="PORT">12346 </jcache_port>