Solution Manager 4.0 on AMD64 Installation Problem

[Former Member]

Hi guys,

I'm trying to install SOLMAN 4.0 with MAXDB on a linux box with the following configuration:

OS: SLES 9

CPU: 2 x AMD 64 @ 2 GHz

RAM: 4 GB

JAVA: IBM Java 2 64bit R7

Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)

IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20061124 (JIT enabled)

J9VM - 20061121_1035_LHdSMr

JIT - r7_level20061020_1803)

The problem occurs at the beginning of the installation when the swap size is being checked. An error message is shown saying only that some error has occurred. I can abort the installation or retry but this doesn't help. I'm a newbie in SAP field so I made 25 GB swap partition but the problem still exists. I can't understand the log file too:

ERROR 2007-02-23 19:26:52

FCO-00011 The step runChecks with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|PrerequisiteCheckerDialogs|ind|ind|ind|ind|

2|0|runChecks was executed with status ERROR .

Any comment would be of great help.

Thanks

Nedyalko

[Former Member · Accepted solution]

Hello,

Did you check the ulimits for the SAP users?

Kind regards,

Martin

[Former Member · Accepted solution]

Hi Martin,

how can I check the ulimits? I suppose ulimits = user limits.

Regards,

Nedyalko

[Former Member · Accepted solution]

Hi Nedyalko,

You are right, ulimits = user limits.

You can check the settings with ulimit -a in a shell.

I have found the following on ulimit in the SuSe administration guide (hope it helps):

With the ulimit (user limits) command, it is possible to set limits for the use of

system resources and to have these displayed. ulimit is especially useful for

limiting the memory available for applications. With this, an application can be

prevented from using too much memory on its own, which could bring the system

to a standstill.

ulimit can be used with various options. To limit memory usage, use the options

listed in Table 9.1.

Table 9.1: ulimit: Setting Resources for the User

-m maximum size of physical memory

-v maximum size of virtual memory

-s maximum size of the stack

-c maximum size of the core files

-a display of limits set

System-wide settings can be made in /etc/profile. There, enable creation of

core files, needed by programmers for debugging. A normal user cannot increase

the values specified in /etc/profile by the system administrator, but he can

make special entries in his own ~/.bashrc.

Example 9.3: ulimit: Settings in /.bashrc

1. Limits of physical memory:

ulimit -m 98304

1. Limits of virtual memory:

ulimit -v 98304

Memory amounts must be specified in KB. For more detailed information, see

man bash.

Note

Not all shells support ulimit directives. PAM (for instance,

pam_limits) offers comprehensive adjustment possibilities if you

depend on encompassing settings for these restrictions.

Since it might be that you have a problem with the file limits I also found this in SAP note 797084:

Additional notes on installing an SAP system on SLES 9

Number of "file descriptors"

Some SAP applications (for example, J2EE Engine, MaxDB, XI, portal) need a larger number of "file descriptors" than is set by default (1024).

To increase the default number of files that a process can open simultaneously to e.g. 32800, edit the following file:

/etc/security/limits.conf

and add the following lines to it:

• hard nofile 32800

• soft nofile 32800

These changes take effect after you log off and log back on again (in "bash" test with: ulimit -n).

If you need more than 32800 "file descriptors", you can increase the value even further -- e.g. when using the SAP J2EE Engine.

With kind regards,

Martin

[Former Member · Accepted solution]

Hi Martin,

Thanks for the information that you have found. I have already tried the last one with the file descriptiors in /etc/security/limits.conf but this doesn't solve the problem. The problem is not in the user limits because almost all of the values are set to unlimited.

core file size (blocks, -c) 0

data seg size (kbytes, -d) unlimited

file size (blocks, -f) unlimited

max locked memory (kbytes, -l) 32

max memory size (kbytes, -m) unlimited

open files (-n) 1024

pipe size (512 bytes, -p) 8

stack size (kbytes, -s) unlimited

cpu time (seconds, -t) unlimited

max user processes (-u) 36864

virtual memory (kbytes, -v) unlimited

Anyway ... Thanks again for your advices. If I find any solution I'll post it here.

Best Regards,

Nedyalko

[Former Member · Accepted solution]

Ok, no problem.

One other thing I found on these forums that might help (although you might have found it yourself already):

[Former Member · Accepted solution]

Hi Martin,

thanks for your help, the link above is very helpful too and I solved my problem as described in that thread.

Thanks once again,

Cheers,

Nedyalko

[Former Member · Accepted solution]

Hi Nedyalko,

No problem, I'm glad it helped and that your problem is solved now.

Kind regards,

Martin

[Former Member]

-