I've noticed that the backup files produced by RMAN (Database is 126.96.36.199.0 Enterprise Edition) )on a RHEL5.5. server which is running ASM have group permissions assigned to ASMADMIN (so the file permissions are assigned to ORACLE:ASMADMIN) as opposed to OINSTALL or any other group.
While this is not an issue (it's not currently impacting us in any way) I'm curious as to how and why this happens. I suspect it is related to the fact that the oracle executable has these permissions also but I can't find any material to confirm my suspicion. If anyone could shed some light on this for me that would be great.
It appears that you are correct about the file permissions inheriting from the Oracle executable - I tried running a data pump export and the file did indeed pick up the same ORACLE:ASMADMIN permissions as I'd noticed with the RMAN output.
Thanks for the tip.