ora-27125: unable to create shared memory segment linux-x86_64

[former_member199632]

Hi,

When performing the installation of NW 7.0 EHP2,

in the Database creation stage it throws this error.

ora-27125: unable to create shared memory segment linux-x86_64

Oracle 10.2

SuSE Linux 11

These are the files used for the installation

kernel version -> SAP KERNEL 7.21 64-BIT UNICODE

SOFTWARE PROVISIONING MGR 1.0 -> Linux on x86_64 64bit

oracle ->  ORACLE RDBMS 10.2 LINUX_X86_64

(NOT installed the oracle patch 10.2.0.5)    

ORACLE Client 10.2.0.5 V3

NW 7.0 EHP2 Installation Export 1

NW 7.0 EHP2 Installation Export 2

Is it something to do with the oracle patch??

OR before preceding are there any parameters to change from linux level?

regards,

zerandib

[error file attached]

[Former Member · Accepted solution]

Hi Zerandib,

Apart from what james and gaurav mentioned, I would recommend to install Opatch 10.2.0.5 and oracle parameters 830576 - Parameter recommendations for Oracle 10g .

Also do refer the oss note 797084 - SUSE LINUX Enterprise Server 9: Installation notes

Point General notes for both ORACLE 9.x and ORACLE 10.x.

Also provide us the log file ora_sql_results.log latest ones.

Regards,

Ram

[former_member199632 · Accepted solution]

Hi Ram,

After patching it to 10.2.0.5, it works OK.

thanks

regards,

zerandib

[Former Member · Accepted solution]

Hi Zerandib,

Good to hear the issue is resolved. Also do update the parameters as per the oss note to avoid furture issues.

Regards,

Ram

[Former Member]

Hi,

check this out note : 797084 - SUSE LINUX Enterprise Server 9: Installation notes

Regard's

[former_member182657]

Hi,

in the Database creation stage it throws this error.
ora-27125: unable to create shared memory segment linux-x86_64

Have a look with SAP Note  797084 - SUSE LINUX Enterprise Server 9: Installation notes

& can follow

When creating the database, the process may terminate with the error message:

                        ORA-27125: "unable to create shared memory segment"
           To avoid this problem during the installation as well as when the ORACLE database is being started after a reboot of the system, you need to add the following line:
                    vm. disable_cap_mlock=1
           to the file "/etc/sysctl. conf" This requires that the "sapinit.rpm" (SLES 9 SP3 and future releases) RPM package has been installed on the system - see above under the section Linux kernel parameters for further details on this RPM package).

In order for the change to take effect in the running system, you must run the following command as the user "root":
                    /etc/init.d/boot.sapconf restart

Hope this will help you.

Regards,

[JamesZ]

Hi zerandib,

Please check SAP note

853972.

Best regards,

James

[Mofizur]

This message was moderated.