Some background: I am setting up several RAC clusters using 11gR2 of Grid Infrastructure and taking advantage of the new "role separation" feature that allows you to install and run your databases under one or more separate OS accounts from the Grid Infrastructure OS user. I did this to provide a little more security between the different databases in the cluster as well as the grid infrastructure software. In addition, some of the databases will be 10gR2 rather than 11g databases.
The permissions problems have been manifested in a couple of ways.
- 10gR2 database installer does not recognize cluster AFTER application of 11gR2 Grid Infrastructure patch 11.2.0.1 due to library permissions.
- 11gR2 (11.2.0.2) database installer has problem due to permissions on gpnp file permissions
- 11.2.0.2 Grid Infrastructure will not start in root.sh due to incorrect permissions caused by umask not being set properly before running root.sh.
I have submitted one SR already for item #1 above and will be submitting another for the second item soon. This seems to be a pattern for Oracle with this new feature; I hope that they will implement more rigorous testing processes in the future to address these issues. The third issue just cropped up recently and I will be submitting a bug report on that one as well.
Has anyone else out there had similar issues related to running in a role separation environment under 11gR2 of Grid Infrastructure? Also, is anyone having problems in general with permissions during Oracle installs / upgrades. While my general experience with Oracle is that after you get it installed and running it is rock solid, my experience with installing / patching Oracle, especially recently, is that there are TONS of problems related to insufficient permissions on files. Oracle's testing of their installation and patching processes leaves alot to be desired....