cancel
Showing results for 
Search instead for 
Did you mean: 

Solaris 10, limit & SAP J2EE 7.11

ganimede_dignan
Contributor
0 Kudos

Hi,

in a Solaris 10 X64 box I've got and issue. It is a SAP J2EE 7.11 CE SAP MII 12.1 usage. Into /usr/sap/MIP/JXX/work/dev_icm log file there is a message:

[Thr 01] Fri Jul  5 09:49:44 2013

[Thr 01] Parameter system/type has value: "J2EE"

[Thr 01] *** WARNING => The maximum number of sockets supported on this host is 250.

This is less than the number of sockets configured in parameter icm/max_sockets (2048) [icxxman_mt.c 3335]

[Thr 01] started security log to file ./dev_icm_sec

I've already read SAP note number 737625... I try to apply it but the message is still exists. Have you got any advice?

The limit output from <sid>adm is:

cputime     unlimited
filesize    unlimited
datasize    unlimited
stacksize   10240 kbytes
coredumpsizeunlimited
descriptors 4096
memorysize  unlimited

The limit output from ora<sid> is:

cputime     unlimited
filesize    unlimited
datasize    unlimited
stacksize   10240 kbytes
coredumpsizeunlimited
descriptors 4096
memorysize  unlimited

The limit output from root is:

cputime     unlimited
filesize    unlimited
datasize    unlimited
stacksize   10240 kbytes
coredumpsizeunlimited
descriptors 256
memorysize  unlimited

Thank you.

Accepted Solutions (1)

Accepted Solutions (1)

ganimede_dignan
Contributor
0 Kudos

Hi,

it should be OK, see below.

/etc/user_attr

#

# Copyright (c) 2003 by Sun Microsystems, Inc. All rights reserved.

#

# /etc/user_attr

#

# user attributes. see user_attr(4)

#

#pragma ident   "@(#)user_attr 1.1      03/07/09 SMI"

#

adm::::profiles=Log Management

lp::::profiles=Printer Management

root::::auths=solaris.*,solaris.grant;profiles=Web Console Management,All;lock_after_retries=no;min_label=admin_low;clearance=admin_high

midadm::::project=MID

oramid::::project=MID

mipadm::::project=MIP

oramip::::project=MIP

sapadm::::project=MID

#daaadm::::project=MID

/etc/project

system:0::::

user.root:1::::process.max-sem-nsems=(priv,2048,deny);project.max-sem-ids=(priv,1024,deny);project.max-shm-ids=(priv,256,deny);project.max-shm-memory=(priv,18446744073709551615,deny)

noproject:2::::

default:3::::

group.staff:10::::

MID:100:SAP System MID:daaadm,midadm,oramid,sapadm::process.max-sem-nsems=(priv,2048,deny);project.max-sem-ids=(priv,1024,deny);project.max-shm-ids=(priv,256,deny);project.max-shm-memory=(priv,184467440737095

51615,deny);process.max-file-descriptor=(basic,65536,deny)

MIP:200:SAP System MIP:mipadm,oramip::process.max-sem-nsems=(priv,2048,deny);project.max-sem-ids=(priv,1024,deny);project.max-shm-ids=(priv,256,deny);project.max-shm-memory=(priv,18446744073709551615,deny)

Thank you.

former_member188883
Active Contributor
0 Kudos

Hi Ganimede,

Could you try setting following parameters in the file /etc/system:

     For mpi/max_pipes of 4,000: 

        set semsys:seminfo_semmni=500

         set semsys:seminfo_semmns=50000

    For mpi/max_pipes of 20,500:

        set semsys:seminfo_semmni=1000

        set semsys:seminfo_semmns=50000

Values for mpi/max_pipes should be calculated based on SAP note 737625.

Additionally try to change the descriptors settings for root user ( currently its 256) to 2048 and check the results.

Hope this helps.

Regards,

Deepak Kori

ganimede_dignan
Contributor
0 Kudos

I've just find that into .sapenv.csh there is:

switch (`uname`)

    case Sun*:

        limit descriptors 4096

        unsetenv LD_LIBRARY_PATH_64

        breaksw

    case OS\/390:

        alias hostname 'hostname -s'

        breaksw

    default:

endsw

so, each time descriptors is modified by a login script

csaba_goetz
Contributor
0 Kudos

Hello Ganimede,

sapenv.csh is taken only if no .sapenv_<hostname>.csh exists.

It looks like instead of the limit of <sid>adm the limit of root would be used.

This is a known issue, see SAP note 1437105 and 1827960.

Steps in brief:

- check the limit known by sapstartsrv

      sapcontrol -nr <instance nr.> -function OSExecute "/bin/ksh ulimit -a" 0 0

- download the newest sapinit

- add

      limit.descriptors=4096

  in /usr/sap/sapservices

- restart sapstartsrv

- check the limit known by sapstartsrv

      sapcontrol -nr <instance nr.> -function OSExecute "/bin/ksh ulimit -a" 0 0

Best regards

Adam

Answers (1)

Answers (1)

former_member188883
Active Contributor
0 Kudos

Hi Ganimede,

Solaris 10 doesn't use /etc/system but uses projects.

Check 

Note 724713 - parameter settings for Solaris 10

and make sure the parameter process.max-file-descriptor is set in the project and that the user <sid>adm is assigned to that project in /etc/user_attr

Hope this helps.

Regards,

Deepak Kori