6.5.2 SCI Software Troubleshooting

If a problem occurs with the SCI software, verify that the following are true:

• The sm_config(1M) template file matches the hardware configuration (SCI link and switch) and cluster topology.

• The sm_config(1M) command can be run successfully from one of the cluster nodes.

• Any reconfigured nodes were rebooted after the sm_config(1M) command was executed.

Also note the following problems and solutions:

• Some applications, such as Oracle Parallel Server (OPS), require an unusually high shared memory minimum to be specified in the /etc/system file. If the field shmsys:shminfo_shmmin in the /etc/system file is set to a value greater than 200 bytes, the sm_config(1M) command will not be able to acquire shared memory because it requests fewer bytes than the minimum the system can allocate. As a result, the system call made by the sm_config(1M) command fails, and the command is aborted.

  To work around this problem, edit the /etc/system file and set the value of shmsys:shminfo_shmmin to less than 200. Then reboot the machine for the new values to take effect.

• If you encounter semsys warnings and core dumps, check to see whether the semaphore values contained in the semsys:seminfo_* fields in the /etc/system file match the actual physical limits of the machine.