As suggested in the responses, the problem was not setting "project.max-shm-memory" parameter properly, and it is done by using projadd command to solve the issue. Many thanks for the solution. - Ansu Original posting: > > Dear Sun Managers, > > > > We have Oracle 10g running on Sun Cluster 3.1 / Solaris 10. > Just before putting it on production last night, we made some > final fine tuning on Oracle, and part of that, we changed the > Oracle SGA Memory parameter values, to make SGA_TARGET value to > 4 GB. We have 16 GB physical memory on the system. When we > restarted Oracle on cluster, it did not come up, but outside > cluster it was working perfectly OK. We had no clues on what was > the issue, but to rule out all possibilities, we have reduced > SGA_TARGET parameter value to 3.5 GB, and to our surprise, it > started working. > > > > Now, is it a limitation on Solaris 10 or Sun Cluster 3.1 that > this value can not go more than or equal to 4 GB? Or should we > check any other possibilities? We plan to put it in production > as soon as possible. > > > > Thanks in advance - > > > > - Ansu ------ _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Mon Sep 22 06:05:09 2008
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:12 EST