Could someone make me to understand how the trace files available in trace location of 11g database(dump location in 10g or below)are having permission 640 in some databases and 660(UNIX flavored systems) . As these are the files getting created by default with database operation, what is the parameter responsible for it?
It depends on umask set in user's profile. Looks like it determines the permissions of trace files.
[oracle@test env_file]$ umask
0022 tracefiles_public=true, this parameter allows other than DBA also to read the trace files
My assumption was also the same that umask value controls it until i came across few Oracle database servers where umask value is set to 027 and still in some cases trace files are getting generated with permission value 660 and in some servers with 640. so just wondering any other parameter responsible for it as well? I know setting umask value to 0027 is not recommended by Oracle but still that does not explain why file permission value are changing from server to server.
TRACEFILES_PUBLIC is false.
However I gave gone through numerous documents on it during this time.. and those are pointing to..
umask value may be changed.
OEM logs may come with different file permission.
and Oracle internally choose what should be the permission of datafiles and redologs. (not sure if that is true with trace files)