Incorrect Permission On User Trace File After Setting ''_trace_files_public''=True
Last updated on DECEMBER 06, 2016
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.4 to 11.2.0.3 [Release 8.1.7 to 11.2]Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 20-Sep-2016***
Symptoms
User can not read user trace files in udump even with "_trace_files_public"=TRUE set in init file.
When connection is made via sqlnet TCP protocol.
When connection is made via BEQ protocol, the trace file permission is correct.
eg:
perform:
alter session set sql_trace=true;
select sysdate from dual;
exit
trace file generated by sqlplus scott/tiger:
-rw-r--r-- 1 oracle dba 1538 Sep 16 16:57 r101_ora_23637.trc
trace file generated by sqlplus scott/tiger@R101:
-rw-r----- 1 oracle dba 2381 Sep 16 16:58 r101_ora_23640.trc
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms