_CRSD_UMASK not Working in 11gR2
Last updated on FEBRUARY 23, 2017
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 12.1]
Information in this document applies to any platform.
After upgraded Oracle clusterware to 11gR2, _CRSD_UMASK parameter is not working anymore.
Before the clusterware upgrade, files created by listener spawned sessions have umask of _CRSD_UMASK(set in init.crsd in /etc), but after the upgrade, they inherit the umask of root user.
Upgraded Oracle Clusterware to 11gR2
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