Solaris Environment Manager maxs out memory.

Question

We have a forte system in production, running on two Solaris 2.6 boxes. Each
has its own environment and they are connected. Our environments are called
"Data Center" and "Call Center". Our Forte memory settings are fairly
standard. We start at 20Mb and max out at 64Mb. We also have Forte keepalive
enabled, with the Forte recommended values. We are running Forte 3.0.L.3 and
using Oracle 8.0.5 for our database (as if it mattered). Each environment
has 1 or 2 NT Server boxes in it, and the clients are all NT4 using a model
node. Our Solaris machines have the patch installed that fixes the problem
that Peggy Adrian posted about earlier in the year.
Three times now in the past week, we have suddenly had the environment
manager for the data center suddenly start chewing up memory. When the data
center manager gets to about 64Mb, the data center environment manager
starts to do the same thing. Soon after, both environments die a hideous
death, and we have go in and start the node managers again.
Please note that we always export our environments to a ".edf" file and
bootstrap the environment manager (removing the environment repository)
whenever we install a new copy of the Forte applications, or whenever our
node manager dies (which seems far more frequent that I would like).
Interestingly, the environment repository hadn't grown any after the
environment manager "runs up the curtain and joins the choir invisibule".
If anyone can throw some light on this, and point us in the direction to
look to solve this problem it would be much appreciated.
Nick.

Answer 1

Hi,
@ Sunny: Thanks for response, the referred note was already checked and parameters are in sync as per note.
@Mohit: SAP wouldn't proceed till create database if Oracle software was not installed. thanks for the response.
@Markus: Thanks I agree with you, but I have doubt in this area. Isn't it like project.max-shm-memory was new parameter we need to set in local zone rather using shmsys:shminfo_shmmax in /etc/system. Do we need to still maintain this parameter in /etc/system in global zone.
As per SUN doc below parameter was obsolete from Solaris 10.
The following parameters are obsolete.
■ shmsys:shminfo_shmmni
■ shmsys:shminfo_shmmax
As per your suggestion, do we need to set below parameters in that case, please clarify.
Parameter                           Replaced by Resource Control      Recommended Value
semsys:seminfo_semmni   project.max-sem-ids                      100
semsys:seminfo_semmsl   process.max-sem-nsems               256
shmsys:shminfo_shmmax  project.max-shm-memory             4294967295
shmsys:shminfo_shmmni   project.max-shm-ids                       100
Also   findings of /etc/release
more /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Regards,
Sitarama.