SAP AS JAVA installation in Solaris Zone envirn throws OUT of Memory error.

[Former Member]

Hi,

We are installing SAP NW2004s 7.0 SR3 AS JAVA on Solaris 10 in zone environment. Thsi was prod server getting build where on top of this we will install GRC 5.3.

We have faced no issues in development build.

But during the Prod build at databse create step, we are getting the below error

ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

Disconnected

SAPinst log entries where error messages started:

04:43:58.128

Execute step createDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0

INFO 2011-04-01 04:45:14.590

Working directory changed to /tmp/sapinst_exe.16718.1301647358.

INFO 2011-04-01 04:45:14.595

Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.

INFO 2011-04-01 04:45:14.609

Working directory changed to /tmp/sapinst_exe.16718.1301647358.

INFO 2011-04-01 04:45:14.621

Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.

INFO 2011-04-01 04:45:14.850

Account oraac5 already exists.

INFO 2011-04-01 04:45:14.852

Account dba already exists.

INFO 2011-04-01 04:45:14.852

Account oraac5 already exists.

INFO 2011-04-01 04:45:14.853

Account dba already exists.

INFO 2011-04-01 04:45:14.867

Working directory changed to /tmp/sapinst_exe.16718.1301647358.

INFO 2011-04-01 04:45:14.899

Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.

ERROR 2011-04-01 04:45:32.280

CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

Disconnected

. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.

ERROR 2011-04-01 04:45:32.286

MUT-03025 Caught ESAPinstException in Modulecall: ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

Disconnected

.

ERROR 2011-04-01 04:45:32.453

FCO-00011 The step createDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|createDatabase was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

Disconnected

.).

********************************************************************************************

ora_sql_results.log

04:45:15 SAPINST ORACLE start logging for

SHUTDOWN IMMEDIATE;

exit;

Output of SQL executing program:

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 1 04:45:15 2011

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to an idle instance.

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

SVR4 Error: 2: No such file or directory

Disconnected

SAPINST: End of output of SQL executing program /oracle/AC5/102_64/bin/sqlplus.

SAPINST found errors.

SAPINST The current process environment may be found in sapinst_ora_environment.log.

2011-04-01, 04:45:15 SAPINST ORACLE stop logging

================================================================================

2011-04-01, 04:45:15 SAPINST ORACLE start logging for

STARTUP NOMOUNT;

exit;

Output of SQL executing program:

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 1 04:45:15 2011

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to an idle instance.

ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

Disconnected

SAPINST: End of output of SQL executing program /oracle/AC5/102_64/bin/sqlplus.

SAPINST found errors.

SAPINST The current process environment may be found in sapinst_ora_environment.log.

2011-04-01, 04:45:32 SAPINST ORACLE stop logging

**************************************************************************************************************************

Already viewed S-note

724713 - parameter settings for Solaris 10 - (Parameters are set as per this note)

743328 - Composite SAP note: ORA-27102 - (no much information in memory problem on zones)

Please provide your suggestions/resolution.

Thankyou.

[sunny_pahuja2 · Accepted solution]

Hi,

You need to change solaris parameter and this error is very common. Please review solaris parameter as per SAP Note 724713 - parameter settings for Solaris 10.

Thanks

Sunny

[markus_doehr2]

What Solaris update is that? I have exactly the same issue with the newest Oracle Solaris (Solaris 10 U9) (check /etc/release).

After digging back and forward for a few hours my workaround was to set

set shmsys:shminfo_shmmax=18446744073709551615

in the global zone and reboot the server. After that was done I could create the shared memory realm and hence continue.

Markus

[Former Member]

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.

[markus_doehr2]

> @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.

I'm aware of the fact, that his changed and that this parameters shouldn't be necessary any more. I just said that it help me last week to get Oracle up'n running in a zone

I would just add this:

> shmsys:shminfo_shmmax project.max-shm-memory 4294967295

reboot the system and see if you can bring up the database. If not the we can try to dig further.

Markus

[Former Member]

Hi Markus,

Thanks, I will ask UNIX team to add that entry and I will update the status in the forum after reboot.

Since there is one more production instance hosted on this server in different zone, the reboot may take a time till weekend.

Regards...

Edited by: Sita Rr Uppalapati on Apr 5, 2011 5:26 PM

[Former Member]

Hi,

Yes Markus is right. Even it worked out for me when I carried out the installation.

Thanks & Regards

Raghunahth L

[Former Member]

Hi,

The memory value was added into /etc/project file in local zone rather in /etc/system file in global zone. No reboot was made and resolved the issue.

Below was entry format with necessary parameter value of resource controls.

group.<groupname>:<group-no.>::::process.max-sem-nsems=(priv,256,deny);project.max-sem-ids=(priv,100,deny);project.max-shm-ids=(priv,100,deny);project.max-shm-memory=(priv,18446744073709551615,deny)

thanks for all the responses.

Regards......

[Former Member]

Hi ,

Just wanted to confirm that in which phase you are getting this error? IS it create database phase. Have you installed oracle software in step where SAPINST will ask you to do so?

Thanks..

Mohit