_CRSD_UMASK not Working in 11gR2
(Doc ID 1353333.1)
Last updated on JANUARY 24, 2020
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]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
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
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document