Infrastructure Software

To satisfy my curiosity, I've just tried, for the first time, oracle-validated configuration on a clean 32-bit OEL-5.2 installation without oracle database software already installed. I've used the actual

oracle-validated-1.0.0-8.el5.i386

rpm package.

According to the official oracle documentation's recommendations and naming convention, taken as a standard, I can say that oracle-validated configuration more failed than succeeded.

CORRECT SETTINGS:

* /etc/sysctl.conf has been correctly set

* /boot/grub/grub.conf has been correctly set


FAILED SETTINGS AND INCORRECT CREATIONS:

* /etc/security/limits.conf has been correctly set for oracle, but all other entries in the file related to other users has been erased by validation script

* no modification of /etc/pam.d/login file (pam_limits.so)

* the script created 'dba' and 'oinstall' groups and 'oracle' user with 'dba' group as primary group (not 'oinstall'), that is not in compliance with official oracle documentation. To verify:

[root@localhost ~]# id oracle
uid=502(oracle) gid=502(dba) groups=502(dba),503(oinstall)

If oinstall is not the primary group, what is it supposed to do?

I'd appreciate if someone could clarify this dichotomy between Oracle official documentation's recommendations and "oracle-validated configuration".

Thanks in advance.

NJ