Originally posted by: CTetreault

I have an ongoing issue where files created by an Oracle process are created with 640 permissions (instead of 644, as one would expect with an 022 umask), and the group is oracle's secondary group, not its primary group. The developers think it's an AIX issue, but I've been insisting that there must be something within the oracle process that applies its own values since touching a new file creates it with the correct ownership and permissions.

My question is this: is there anything in AIX that might override the default values? The umask is set to 022 in /etc/security/user, /etc/profile, and the user's .profile.
#AIX-Forum

Originally posted by: romeo_ninov

Do you have information what was the value of umask on the time oracle DB start?
And what are oracle user primary and secondary groups (my crystal ball is broken)
#AIX-Forum

Originally posted by: CTetreault

The umask was 022 when the server and DB were started. Oracle's primary group is oinstall, it's secondary group is dba. The oracle process should create files using oracle's umask and primary group, but for some reason, it doesn't. The files are created with an 027 umask and dba as the owning group.

We've opened a ticket with Oracle, too. I don't think this is an AIX issue, but just wanted to verify that I'm not missing some obscure AIX setting that could change those values.

Thanks for your help.
#AIX-Forum

Originally posted by: romeo_ninov

> CTetreault wrote:
> The umask was 022 when the server and DB were started. Oracle's primary group is oinstall, it's secondary group is dba. The oracle process should create files using oracle's umask and primary group, but for some reason, it doesn't. The files are created with an 027 umask and dba as the owning group.
>
Especially for Oracle DB the files should belong to group dba. oinstall group have special purpose. You can check in installation manual of oracle DB
#AIX-Forum

Originally posted by: j.gann

> My question is this: is there anything in AIX that might override the default values?

any process, once it is running, can alter his own setting of umask as well as change the group it runs with and of course dictate the permissions of files it creates.

you're on the wrong path if you think setting the umask in a user's shell was more than providing a nonbinding default for processes started by this user.

should you(or the developers) actually know which process creates the files you can trace it's system calls with truss(1) or check the process's properties with the tools from the bos.perfagent.proctools fileset.

and keep in mind that directory permission SGID (set group id) also affects group ownership of newly created files in this dir.

good luck
#AIX-Forum