Incorrect Permission On User Trace File After Setting ''_trace_files_public''=True
(Doc ID 303604.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 8.1.7 to 11.2]
Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 20-Sep-2016***
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.
alter session set sql_trace=true;
select sysdate from dual;
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 user/passwd@R101:
-rw-r----- 1 oracle dba 2381 Sep 16 16:58 r101_ora_23640.trc
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!