We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] SAPOSCOL is getting stop with Shared Memory Full Error

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from D. Caddick on Feb 26 at 3:29 AM
Hi,

Your Shared memory is looking ok, but You should adjust Pool 40:

Key: 40 Pool for database buffers
Size configured.....: 110000000 ( 104.9 MB)
Size min. estimated.: 109175040 ( 104.1 MB)
Advised Size........: 112000000 ( 106.8 MB)

Amend the Parameter ipc/shm_psize_40 to 112000000 from 110000000

You need to restart the SAP system to activate the parameter.

Did you run

cleanipc ## remove (## = system number)

if you have other systems installed on the server do NOT run "cleanipc all remove" with root user.

Regards

---------------Original Message---------------
From: islamsk
Sent: Wednesday, February 19, 2014 10:45 AM
Subject: SAPOSCOL is getting stop with Shared Memory Full Error

Dear Friends,

I am facing issues with my production server , every month end when users start taking out reports from PRODUCTION server then automatically SAPOSCOL stop working and gives error shared memory full. due to this our server performance also goes down, server start working very slow.

Then after server reboot all start working smoothly.

I have SAP ECC 6.0 with EHP 6 on SUSE linux 11.2 OS with Sybase 15.7 DB.

Please let me know how to increase the shared memory to resolve the issues.

Thanks in advance

Regards,

Islam

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, Inc. and message author.
Ziff Davis, Inc. 28 E 28th Street New York, NY 10016
D. Caddick  

Consultant
12 achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Have a technical question? Need to find IT solutions? Ask your peers in the Toolbox for IT community.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language