Before you install and run this plug-in, you must make changes to your Oracle Application Server and N1 Grid SPS Master Server.
Modify the /etc/system file.
Add the following lines to your /etc/system file and reboot:
* included for Oracle set semsys:seminfo_semmap=80 set semsys:seminfo_semmni=2200 set semsys:seminfo_semmns=2200 set semsys:seminfo_semmnu=2000 set semsys:seminfo_semmsl=256 set semsys:seminfo_semopm=210 set semsys:seminfo_semume=600 set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=100 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=100
Add an Oracle database group to the /etc/group file.
Edit the /etc/group file on the system on which you intend to install the Oracle Application Server product and add the following line:
dba::120:
Add an Oracle user to the /etc/passwd file.
Edit the /etc/passwd file on the system on which you intend to install the Oracle Application Server product and add the following line:
oracle:x:500:120::/export/home/oracle:/bin/csh
Synchronize the /etc/shadow file.
Use the following command: pwconv
Activate the Oracle user account.
Use the passwd oraclecommand and provide a password for the Oracle user.
If your system is in NIS and an Oracle account or dba group is already in the NIS maps, verify the configuration of the /etc/nsswitch.conf file.
Make sure that files appears before nis in the passwd entry in the /etc/nsswitch.conf file.
Use the same definition of Oracle and dba in all systems.
Some of the plans that are provided with this plug-in require significant time to execute. As a result, you should verify that the timeout values for the Master Server are long enough to allow the plans to run.
Edit the provisioning system config.properties file on the Master Server. By default, the file is in the /opt/SUNWn1sps/N1_Grid_Service_Provisioning_System_5.0/server/config/config.properties directory. Set the following timeout values:
pe.nonPlanExecNativeTimeout=1800 pe.defaultPlanTimeout=18000 userdb.sessionTimeout=10800000
You must restart the Master Server for the timeout changes to occur.
When you install the Remote Agent, set root as the user and group that own the installation. Also select yes when asked if you want to allow the setuid functionality.
To enable the use of clustering functionality in the Oracle environment, systems that are part of a cluster must be able to communicate remotely with each other through a remote shell (rsh command). To enable remote functionality, create the rhosts file in the home directory of the oracle account and add the line + oracle to it.