Hello Stefan,
This is a expected behavior. Oracle JVM associates it's System.out and
System.err output streams with trace files. The same way behaves
different Java Application Servers, because if they would not do this,
than the output generated via System.out would be simple lost, because
there is not terminal to output to, when java procedure/function is
called.
There can be also many different information in trace file besides
10046 trace information, if you will enable other trace events, when
trace 10046 enabled.
On 5/11/06, Stefan Knecht <knecht.stefan@xxxxxxxxx> wrote:
> Hello list
>
> I've been using java to perform various tasks in the database for some
time
> now. However, I just noticed today that 10046 behaves quite odd in
> conjunction with java calls.
>
> I tested this on 10.1.0.3, and am wondering if this behaviour is
expected:
>
> create or replace and compile java source named java_test
> as
> import java.lang.*;
> public class java_test
> {
> public static int print_test(String foo)
> {
> try {
> System.out.println("hi there!\n");
> }
> finally
> {
> return 0;
> }
> }
> }
> /
>
> create or replace function run_java_test (x in varchar2) return number
> as
> language java name 'java_test.print_test( java.lang.String) return
integer';
> /
>
>
> alter session set events '10046 trace name context forever, level 12';
>
> select run_java_test('foo') from dual;
>
> alter session set events '10046 trace name context off';
>
> Then look at the resulting trace file :)
>
>
> /eva1_data2/SCANS/admin/udump/scans_ora_809282.trc
> Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
> With the Partitioning, OLAP and Data Mining options
> ORACLE_HOME = /eva1_data2/SCANS/oracle
> System name: OSF1
> Node name: sr-ac99-0181
> Release: V5.1
> Version: 2650
> Machine: alpha
> Instance name: SCANS
> Redo thread mounted by this instance: 1
> Oracle process number: 17
> Unix process pid: 809282, image: oracle@sr-ac99-0181 (TNS V1-V3)
>
> *** 2006-05-11 11:05:30.399
> *** SERVICE NAME:(SYS$USERS) 2006-05-11 11:05:30.394
> *** SESSION ID:(529.6213) 2006-05-11 11:05: 30.394
> hi there!
> *** 2006-05-11 11:05:47.648
> =====================
> PARSING IN CURSOR #14 len=69 dep=0 uid=0 oct=42 lid=0 tim=983910284288
> hv=3164292706 ad='10920648'
> alter session set events '10046 trace name context forever, level 12'
> END OF STMT
> EXEC
> #14:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=983910284288
> WAIT #14: nam='SQL*Net message to client' ela= 1024 p1=1650815232 p2=1
p3=0
> WAIT #14: nam='SQL*Net message from client' ela= 7168 p1=1650815232 p2=1
> p3=0
> =====================
>
> anyone experience this before ??
>
>
> Stefan
>
--
Best regards,
Edgar Chupit
callto://edgar.chupit
