XP Pro shared memory size of Intel GM45 on L305-S5905

The laptop's Vista Home Premium was recently replaced with XP SP3.
All is well, with one smaller (1GB) issue.
I am fairly certain (not 100%) i had changed the shared memory in Vista to 128MB (i only do basic 2D desktop stuff, nothing that would need more memory), however in XP all i can see is in Video settings is on Adapter tab it shows 1024MB for the graphics card, which would explain why the XP booting with Physical Address Extension only shows 2.87GB free out of the 4GB total.
Does anyone know where intel is hiding the ability to change the shared memory size, i don't seem to get nowhere with googling around for it. I would certainly rather have the memory available for applications than waste it on doing nothing.
I am looking at the intel driver since there is no option to set memory size in BIOS either.
Thanks in advance for your help,
Daniel

windows xp are seeing only 3 G of Ram memory...vista can see a lot more of ram ....i intal window Xp on my laptop and have the same probleme...a instal vista ultimatum end now i can use all the memery...i search a lot of forum and the sead theat xp cand see up to 4 G of ram...but it's nat true......and the video driver is configuretet to use 1760MB the maximum video card memory...i'm looking for a program to change the memoory of the video card..but tiil now i didn'f find anyfing...

Similar Messages

Can't find free space for Shared Memory (Size=83739 KB)

Hello All,
          I have an issue. i am unable to bring up the server. It is ABAP system.
dev_w0 log file show me memory error.
I Fri May 01 10:11:55 2009
I *** ERROR => [MapOsShm] Can't find free space for Shared Memory (Size=83739 KB)
               [shmnt.c      2174]
I *** ERROR => [AttachOsShm] MapViewOfFile(Key=62,Handle=0x000003FC) failed with Err=0
               [shmnt.c      2174]
I *** ERROR => ShmCreate: Attach (62,85748608,2) failed [shmnt.c      422]
Can some body help me with it.
Thanks and regards
Kiran

I am running into the same issue. What exactly solved your problem?
I will really appreciate any info., around this.
i am trying to install CE 7.2 Developer Workplace on Windows 32 bit.
Saurabh

Increase shared memory by IGD (intel HD)

when will the shared memory for intel HD graphics processor can be increase more than 256MB? some motherboard with some brand can assign until 1GB of RAM to the integrated graphic. future BIOS development should focus on this matter.
thank you
azuan

Quote from: azuan on 07-October-13, 10:32:54
the reason i asked is because the 'manual allocation' in the bios menu only limited to 256MB only.
The BIOS has no control over the video memory.
That 64/128/256 MB value is a legacy and it means the reserved system RAM for GPU.
Most of the GPUs don't need more than 64MB to operate properly.
But it's better to give them 128 or 256MB.
Why?
The "plug & play" (automatic allocation) mechanism was never a perfect one.
Two devices sharing the same I/O addressing space might lead to conflicts and system crashes.
You don't want another device to share system RAM with your GPU.
For this reason it's much better to "lock" that RAM area and to reserve it for the GPU.
Coming back to video memory, that will be allocated much later (after the OS is loaded) by the GPU.
Intel Dynamic Video Memory Technology is used for that.
Depending on the GPU, installed system RAM and application demand, up to 1.7 GB system RAM can be reserved as video memory.
Edited:
http://www.intel.com/support/graphics/sb/CS-029090.htm
Up to 1.7GB usable video memory for HD 2000, 3000, 4000 and 4600 (all the Gen 2/Gen 3/Gen 4 Intel processors).

Determine the current max shared memory size

Hello,
How do I determine the max shared memory value in effect on the box I have. I dont wish to trust /etc/system as that value may not be the effective value unless the system has been rebooted after that setting.
Any pointers would be appreciated.
Thanks
Mahesh

You can get the current values using adb:
# adb -k
physmem 3e113
shminfo$<shminfo
shminfo:
shminfo: shmmax shmmin shmmni
10000000 c8 c8
shminfo+0x14: shmseg
c8
The shminfo structure holds the values being used and the shminfo
macro will print out the values in hex.
Alan
Sun Developer Technical Support
http://www.sun.com/developers/support

Hi,URGENT--Memory size of binary Increasing due to multithreading in Pro*C

I got stuck in Multhithreading in PRO*C.
Memory size of my binary keeps on increasing.
Flow is like this.
My main thread spawns multiple threads of two types of threads. Both types of threads connect to different dbs.
In other words, i need to have multiple connections with to different db's i.e. configure multiple threads for same.
For this i take sql context variable in each thread and pass it to connect_to_db func. for connection. Then that thread use corresponding sql context variable for pl/sql function( CHANGE_INPUT) call.
This keeps of memory size of my binary inceasing.
In above code T_ABILLITY_INPUT is of object type whose ott converted header and out type file is already included.
CHANGE_INPUT is pls/sql function
Can any help me out in using multithreading in pro*c.
It's very-very URGENT, This is creating problem in live site.
Thaks in Advance
Code for process and connect_to_db function is same for both types of threads different is in object types to get process
sample code of connect_to_db
int connect_to_db(char username, char password, char dbname,sql_context ctx,char *ErrorMessage)
int ret;
char ConnString[50] = {0,};
sprintf(ConnString, "%s@%s", username, dbname);
EXEC SQL WHENEVER SQLERROR DO sql_error("ORACLE error--", ErrorMessage);
EXEC SQL ENABLE THREADS;
EXEC SQL CONTEXT ALLOCATE :*ctx;
EXEC SQL CONTEXT USE :*ctx;
EXEC SQL CONNECT :ConnString IDENTIFIED BY :password;
if(sqlca.sqlcode < 0)
return -1;
return 0;
sample code for pl/sql function call
int process(double num,char Flag,char dbName,char dbExtApp,char dbExtUname,char *
dbExtRef,sql_context ctx, char *err)
T_ABILLITY_INPUT *typAbilityInputObj;
T_ABILLITY_INPUT_ind *typAbilityInputObj_ind;
T_ABILLITY_INPUT *typAbilityInputObj2;
T_ABILLITY_INPUT_ind *typAbilityInputObj2_ind;
//declaration of some host variables
int iretVal=0;
char extUser[255];
char extApp[255];
char extRef[30];
char us[ABREF_LENGTH];
char app[ABREF_LENGTH];
char ref[ABREF_LENGTH];
memset(extUser,'\0',sizeof(extUser));
memset(extApp,'\0',sizeof(extApp));
memset(extRef,'\0',sizeof(extRef));
memset(us,'\0',ABREF_LENGTH);
memset(app,'\0',ABREF_LENGTH);
memset(ref,'\0',ABREF_LENGTH);
EXEC SQL CONTEXT USE :ctx;
EXEC SQL OBJECT CREATE :typAbilityInputObj:typAbilityInputObj_ind;
EXEC SQL OBJECT CREATE :typAbilityInputObj2:typAbilityInputObj2_ind;
EXEC SQL OBJECT SET EXTERNAL_USER,EXTERNAL_APPLICATION,EXTERNAL_REFERENCE OF : typAbili
tyInputObj TO :extUser, :extApp, :extRef;
EXEC SQL CALL CHANGE_INPUT(:typAbilityInputObj,:typAbilityInputObj2) into iretVal;
EXEC SQL OBJECT GET EXTERNAL_USER,EXTERNAL_APPLICATION,EXTERNAL_REFERENCE FROM :typAbil
ityInputObj2 INTO :us, :app, :ref;
EXEC SQL OBJECT UPDATE :typAbilityInputObj;
EXEC SQL OBJECT UPDATE :typAbilityInputObj2;
EXEC SQL OBJECT RELEASE :typAbilityInputObj;
EXEC SQL OBJECT RELEASE :typAbilityInputObj2;
EXEC SQL OBJECT DELETE :typAbilityInputObj;
EXEC SQL OBJECT DELETE :typAbilityInputObj2;
EXEC SQL COMMIT;
EXEC SQL OBJECT CACHE FREE ALL;
}

This must be my last last thing. AHT was on an iMac I bought in 2009. It was included on my "disk 2" along with several other applications. When I wiped and installed the full Lion, AHT was gone. Same is true for the full Mountain Lion installation media. It does not have AHT. I'm not at all sure how to get it back from Apple.
I was able to find it on my SL disc 2 and extract it again from that. Disc 2 won't install on Mountain Lion (the packages are too out of date) but the AHT pkg does.
Since you have it, consider packing it up and keeping it safe. Maybe someone who knows AHT better than I can elaborate on AHT. From what I've seen, you get it when your mac ships but if you ever wipe and reinstall the OS, you lose it.

Please help reducing shared memory for intel gpu

Hello.i am desperately trying to lower the ammount of shared memory on the intel hd 4600 because the amd r7 won't start at newer games.i don't have this option in bios so please help me to do any other way.thank you!

Bring this kernel panic report with you to the genius bar. Your MBP has a GPU issue.
Ciao.

Solaris 10 shared memory config/ora 11g

The ora 11 install guide for spark solaris 10 is very confusing wrt shared memory and my system does not seem to using memory correctly, lots of swapping on an 8GB real memory system.
The doc says to set /etc/system to:
shmsys:shminfo_shmmax project.max-shm-memory 4294967296
but infers that this is not used.
Then, the doc states to set a project shared mem value of 2GB:
# projmod -sK "project.max-shm-memory=(privileged,2G,deny)" group.dba
Why is this number different?
By setting to to 2G as documented oracle did not work at all and so I found Note:429191.1
on the solaris 10 memory which hints that these numbers should be big:
% prctl -n project.max-shm-memory -r -v 24GB -i project oracle_dss
% prctl -n project.max-shm-memory -i project oracle_dss
project: 101: oracle_dss
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 24.0GB - deny -
system 16.0EB max deny
Is there some logic in how to get solaris 10/ora 11 to hold hands. The install doc does not seem to contain it.

system does not seem to using memory correctly, lots of swapping on an 8GB real memory system.We could start (for example) with this question - How big is your SGA or how much of 8GB RAM takes your SGA?
The doc says to set /etc/system to:
shmsys:shminfo_shmmax project.max-shm-memory 4294967296
but infers that this is not used.From documentation:
In Solaris 10, you are not required to make changes to the /etc/system file to implement the System V IPC. Solaris 10 uses the resource control facility for its implementation. However, Oracle recommends that you set both resource control and /etc/system/ parameters. Operating system parameters not replaced by resource controls continue to affect performance and security on Solaris 10 systems.
Then, the doc states to set a project shared mem value of 2GB:
# projmod -sK "project.max-shm-memory=(privileged,2G,deny)" group.dba
Why is this number different?It's an example how "To set the maximum shared memory size to 2 GB"
By setting to to 2G as documented oracle did not work at all Docs says:
On Solaris 10, verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown.
If your SGA was greater than 2G I'm nor wondering why "oracle did not work at all".
So for 4GB SGA (for example) you need allow allocation of 4G of shared memory.
Note: shmsys:shminfo_shmmax != project.max-shm-memory. "project.max-shm-memory" is replacement of "shmsys:shminfo_shmmax" but function of these parameters differs.
"project.max-shm-memory resource control limits the total amount of shared memory of one project, whereas previously, the shmsys:shminfo_shmmax parameter limited the size of a single shared memory segment."
Relevant link to Sun docs: http://docs.sun.com/app/docs/doc/819-2724/chapter1-33

Shared memory in solaris 10 with oracle

Hi, I am a newbie to solaris and i have some questions on shared memory, Oracle in Solaris
My Questions might seem different, however please do read and try to answer. Thanks in advance.
1) if a solaris server has say 40gb of Ram, what would be the maximum size of a shared memory segment in this machine?
I know that if the server has 40GB. then max shared memory size is 10GB i.e. one fourth of ram, however not sure
2) What is the maximum size of a shared memory segment in solaris that a root user can define.
+ i know that its some where near 14 GB not very sure +
3) Assume i have created a user X and i allocated say 10GB limit for this user for shared memory.
I login to solaris using X and now, can i increase the size of the shared memory that this user can use?
I have a situation, where the root user, created a user named DBA and the root user allocated some 15gb for this DBA user as the max SHM limit.
Now the DBA user has set the max limit for shared memory as 1TB, which is causing hell of problems in the system.
* I am Not very sure on the concept. I am new to this product and facing this problem. please advice.*
+ Thanks +
Krishnakanth (Simply KK)

Not sure why your "oracle" user (owner who will be creating the instance) has been assigned the project user.root. I would say create a seperate project may be "dba" and give access to this project to the owner of the user who will be creating the oracle instance.
and then try to issue the command:
prctl -n project.max-shm-memory -v 8gb -r -i project dba
and check to see if you are still facing a problem?
Edited by: somjitdba on Apr 2, 2009 9:54 PM

Shared Memory Short Dump: SHMM ab_ShmResetLocks - anyone?

hello:)
I have a problem with shared memory area (SHMM) that dumps.
I have a tool that uses a shared memory area instance to store data.
When I run the tool and update the data stored in the instance, a short dump is thrown:
SYSTEM_SHM_AREA_OBSOLETE with the explanation:
An attempt was made to access a shared memory area that has already been
released. Possible reasons for release:
- explicit release from an ABAP program or from the shared objects
management transaction
- implicit release during resource shortages
The first one does not match, as I DO NOT explicitly release the instance of my area.
Moreover, ST22 shows me different parts of code every time, so my code is not the cause, or a specific part of code, or data that I shift.
The second one would probably be the cause.
But how can I avoid it?
Moreover, there in SM21(System Log) there is at this time, there is a runtime error, that says
ab_ShmResetLocks and nothing more:(
Shared Memory size is sufficient.
The Shared Memory Area Settings (SHMA) do not time out the read/write access(Lifetime: no entry and Automatic area structuring is set)
Any help is more than welcome, why i get the short dump!!
best regards
simon:)

Please check the following SAP notes:
[SAP Note 1105266 WDA: Runtime error SYSTEM_SHM_AREA_OBSOLETE|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_wd/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313035323636%7d]
Also check the below notes for related details.
Note 1322182 - Memory consumption of ABAP Shared Objects
[SAP Note 764187 SYSTEM_SHM_AREA_DETACHED runtime error|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_aba/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373634313837%7d]
Please check the size of the shared memory object in the profile parameter abap/shared_objects_size_MB.
Regards,
Dipanjan

SAPOsCol running but not working (shared memory not available)

Dear Forum,
We have just set new passwords for SAP AD users (incl SAPService<SID> and <SID>adm), after this restarted SAP instances and servers / clusters). Everything came up well and all services, incl SAPOsCol started up automatically with the new passwords.
Everything works fine - only this morning i wanted to have a look in ST06 and the program tells me "SAPOSCOL not running? (shared memory not available).
The service is running tho, would a restart of the service do any difference, and is there any possibility that a restart of the service on a live and running system would force a system restart? (i couldnt think of any, but I hate restarting services on a live running production system).
Would it be an option to stop/start the collector from ST06?
Thanks in advance,
Kind regards,
Soren

Hello Kaushal,
Thank you for your answer!
I tried to start and stop/start the service from ST06, but it doesnt work. Here is a content og the log - any ideas how i could start the collector without booting the server?
HWO description
      SAPOSCOL version COLL 20.95 701 - 20.64 NT 07/10/17, 64 bit, multithreaded, Non-Unicode
      compiled at   Feb 24 2009
      systemid      562 (PC with Windows NT)
      relno         7010
      patch text    COLL 20.95 701 - 20.64 NT 07/10/17
      patchno       32
      intno         20020600
      running on    L5183N01 Windows NT 6.0 6002 Service Pack 2 16x AMD64 Level 6 (Mod 26 Step 5)
      PATCHES
      DATE     CHANGELIST           PLATFORM             PATCHTEXT
      20081211 1032251              ALL                  Option -w support. Removed SizeOfRecord warning rt 130.
      20090114 1036522              UNIX                 Log file permissions: 664.
      20090203 1041526              UNIX                 Add. single instance check.
      20090210 1042962              ALL                  Continue after EWA HW XML generation failure.
09:46:39 12.04.2010   LOG: Profile          : no profile used
09:46:39 12.04.2010   LOG: Saposcol Version : [COLL 20.95 701 - 20.64 NT 07/10/17]
09:46:39 12.04.2010   LOG: Working directory : C:\usr\sap\PRFCLOG
09:46:39 12.04.2010   LOG: Allocate Counter Buffer [10000 Bytes]
09:46:39 12.04.2010   LOG: Allocate Instance Buffer [10000 Bytes]
09:46:40 12.04.2010   LOG: Shared Memory Size: 118220.
09:46:40 12.04.2010   LOG: Connected to existing shared memory.
09:46:40 12.04.2010   LOG: MaxRecords = 1037 <> RecordCnt + Dta_offset = 1051 + 61
09:46:55 12.04.2010 WARNING: WaitFree: could not set new shared memory status after 15 sec
09:46:55 12.04.2010 WARNING: Cannot create Shared Memory
thanks!
Soren
Edited by: Soeren Friis Pedersen on Apr 12, 2010 9:49 AM

SHARED MEMORY 문제(ORA-7329, ORA-7331, ORA-7279)

제품 : ORACLE SERVER
작성날짜 : 2004-07-22
SHARED MEMORY 문제(ORA-7329, ORA-7331, ORA-7279)
================================================
PURPOSE
다음은 shared memory 문제가 발생하는 경우(ora-7329,ora-7331,
ora-7279) 에 대해서 알아본다.
Explanation
1. 왜 Problem 이 생기나?
* Oracle 은 Process와 SGA(System Global Area) 간의
Communication를 위해 Shared Memory와 Semaphore 를 사용한다.
Oracle Instance 가 뜰 때 SGA를 Create하기 위해 Main Memory의
임의의 부분을 할당하는데 이 때 Shared Memory 나 Semaphore 가
적절하지 않으면 이에 관련한 Error가 발생한다.
2. 해결 방안
SGA는 Shared Memory 안에 생기므로 Shared Memory 는 각 Process에게
사용 가능해야 한다.
Shared memory 와 Semaphore parameter 는
- SHMMAX = 1개의 shared memory segment 의 maximum size,
SGA 크기 이상
- SHMMIN = 1개의 shared memory segment 의 minimum size, 1 byte
- SHMMNI = shared memory identifier의 숫자, 100 이상
- SHMSEG = 1개의 process에 attach되는 shared memory segment의
maximum 갯수, 10 이상
- SEMMNS = system의 semaphore 갯수, 200 이상
- SEMMNI = 시스템에서 identifier를 setting하는 semaphore 수,
70 이상
- SEMMSL = semaphore set 당 최대 semaphore 갯수,
initSID.ora 의 processes 값 이상
* 추천하는 Semaphore와 Shared Memory Parameter
Operating System Shared Memory Parameters Semaphore
================================================================
Sun OS
SHMSIZE = 32768 SEMMNS = 200
SHMMNI = 50 SEMMNI = 50
Solaris
SHMMAX = 8388608 SEMMNS = 200
SHMSEG = 20 SEMMSL = 50
SHMMNI = 100 SEMMNI = 70
HP/UX
SHMMAX = 0x4000000(64Mb) SEMMNS = 128
SHMSEG = 12 SEMMNI = 10
Digital Unix (DEC Alpha OSF/1)
SHMMAX = 4194304 SEMMNS = 60
SHMSEG = 32 SEMMSL = 25
Ultrix Use System Default     SEMNS SEMMSL = 5
AT&T Unix
          SHMMAX = RAM-Dependant     SEMMNS = 200
8 or 16Mb RAM
          SHMMAX = 5 Mb     For All RAM
32 Mb RAM
          SHMMAX = 8 Mb Values
64 Mb RAM
          SHMMAX = 16 Mb
128 Mb RAM
          SHMMAX = 32 Mb
256 Mb RAM
          SHMMAX = 64 Mb
512 Mb RAM
          SHMMAX = 128 Mb
1024 Mb RAM
          SHMMAX = 256 Mb
2048 Mb RAM
          SHMMAX = 512 Mb
          SHMSEG = 6 for all RAM Values
          SHMMIN = 1 for all RAM Values
Dynix/PTX
          SHMMAX = 11010048 SEMMNS = 200
          SHMSEG = 20 SEMMSL = 85
Other Parameter     NOFILES = 128
DG/UX
          SHMMAX = 4194304 SEMMNS = 200
          SHMSEG = 15
Shared Memory 와 Semaphore Parameter는 OS 의 Kernel Configuration
화일에 반드시 지정되어야 하며, File의 위치는 OS마다 차이가 있다.
현재의 Shared Memory 와 Semaphore Configuration 을 알기 위해서는
다음의 Command를 이용한다.
$ sysdef |more
* HP-UX (relevant sections only) 에서의 예:
Semaphore 관련 Parameters
- maximum value for semaphores(semaem)= 16384
- Semaphore map(semmap)= 4098
- number of semaphore identifiers(semmni) = 4096
- total number of semaphores in the system(semmns) = 8192
- number of semaphore undo structures(semmnu) = 1536
- semaphore undo entries per process(semume) = 512
- semaphore maximum value(semvmx) = 32767
Shared Memory 관련 Parameters
- maximum shared memory segment size in bytes(shmmax) = 536870912
- minimum shared memory segment size in bytes(shmmin) = 1
- maximum shared memory segments in system (shmmni) = 512
- maximum shared memory segments per process(shmseg) = 512
NOTE: SHMMAX는 현 system에 8개의 instance가 수행될 수 있는
충분한 값이다.
* Shared memory 또는 semaphore parameters 를 변경하기 위해서는 ...
1. Oracle Instance를 Shutdown 한다.
2. OS의 Kernel Configuration File이 있는 곳으로 간다.
3. System Utility 또는 Editor를 이용해서 필요한 값을 바꾼다.
System Utility는 다음과 같다
| OS |     Utility     |
| HP/UX | SAM     |
| SCO     |     SYSADMSH |
| AIX     |     SMIT     |
| Solaris |     ADMINTOOL |
4. Kernel 을 Reconfigure 한다.
5. System을 Reboot 한다.
6. Oracle Instance를 startup시킨다.
[ 예제 ] Solaris 2.3/2.4 parameters and commands:
1. SQLDBA 에서 :
SQLDBA> shutdown
SQLDBA> exit
2. Superuser(root)로 login 하고 :
# cd /etc
3. /etc/system file 에 다음을 추가 한다:
set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=20
set semsys:seminfo_semmns=200
set semsys:seminfo_semmni=70
4. Kernel을 reconfigure 한다:
# touch /reconfigure
5. Machine 을 reboot 한다:
#init 6
6. SQLDBA 에서 :
SQLDBA> startup
SQLDBA> exit
Oracle의 init<SID>.ora 파라미터 화일에는 SGA에 영향을 주는
Parameter들이 있다. OS의 Shared Momory와 Semaphore Parameter에
연결된 이 Parameter의 setting은 System과 Oracle의 Performance에
중요한 영향을 미친다.
Reference Documents
<Note:1011658.6>

system does not seem to using memory correctly, lots of swapping on an 8GB real memory system.We could start (for example) with this question - How big is your SGA or how much of 8GB RAM takes your SGA?
The doc says to set /etc/system to:
shmsys:shminfo_shmmax project.max-shm-memory 4294967296
but infers that this is not used.From documentation:
In Solaris 10, you are not required to make changes to the /etc/system file to implement the System V IPC. Solaris 10 uses the resource control facility for its implementation. However, Oracle recommends that you set both resource control and /etc/system/ parameters. Operating system parameters not replaced by resource controls continue to affect performance and security on Solaris 10 systems.
Then, the doc states to set a project shared mem value of 2GB:
# projmod -sK "project.max-shm-memory=(privileged,2G,deny)" group.dba
Why is this number different?It's an example how "To set the maximum shared memory size to 2 GB"
By setting to to 2G as documented oracle did not work at all Docs says:
On Solaris 10, verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown.
If your SGA was greater than 2G I'm nor wondering why "oracle did not work at all".
So for 4GB SGA (for example) you need allow allocation of 4G of shared memory.
Note: shmsys:shminfo_shmmax != project.max-shm-memory. "project.max-shm-memory" is replacement of "shmsys:shminfo_shmmax" but function of these parameters differs.
"project.max-shm-memory resource control limits the total amount of shared memory of one project, whereas previously, the shmsys:shminfo_shmmax parameter limited the size of a single shared memory segment."
Relevant link to Sun docs: http://docs.sun.com/app/docs/doc/819-2724/chapter1-33

Short Dump TSV_TNEW_PAGE_ALLOC_FAILED while using shared memory objects

Hi Gurus,
We are using shared memory objects to stor some data which we will be reading later. I have implemented the interfce IF_SHM_BUILD_INSTANCE in root class and using its method BUILD for automatic area structuring.
Today our developments moved from dev system to quality system, and while writing the data into the shared memory using the methods ATTACH_FOR_WRITE and DETACH_COMMIT in one report. We started getting the run time error TSV_TNEW_PAGE_ALLOC_FAILED.This is raised when the method DETACH_COMMIT is called to commit the changes in the shared memory.
Everyhting works fine before DETACH_COMMIT. I know that it is happening since the program ran out of extended memory, but I am not sure why it is happening at DETACH_COMMIT call. If excessive memory is being used in the program, this run time error should have been raised while calling the ATTACH_FOR_WRITE method or while filling the root class attributes. I am not sure why it is happening at DETACH_COMMIT method.
Many Thanks in advance.
Thanks,
Raveesh

Hi raveesh,
as Naimesh suggested: Probably system parameter for shared memory area is too small. Compare the system parameters in devel and QA, check what other shared memory areas are used.
Regarding your question, why it does not fail at ATTACH_FOR_WRITE but then on DETACH_COMMIT:
Probably ATTACH_FOR_WRITE will set an exclusive write lock on the shared memory data, then write to some kind of 'rollback' memory and DETACH_COMMIT will really put the data into shared memory area and release the lock. The 'rollback' memory is in the LUW's work memory which is much bigger as the usual shared memory size.
This is my assumption - don't know who can verify or reject it.
Regards,
Clemens

SAPOSCOL Problems with Shared Memory

Has anyone had any problems in either starting the saposcol or with keeping it running? We have noticed multiple problems for several years now, and are at a point where the saposcol is not running at all on any of our servers, nor can we start it running.
We're seeing "SAPOSCOL not running ? (Shared memory not available)". I am working with SAP with two different customer messages trying to determine why we cannot start the saposcol.
Does anyone have any ideas?
Thanks,
Traci Wakefield
CV Industries

I do have entries in the os-collector log:
      SAPOSCOL version COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005, 64 bit, single threaded, Non-Unicode
      compiled at   Nov 26 2005
      systemid      324 (IBM iSeries with OS400)
      relno         6400
      patch text    COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005
      patchno       102
      intno         20020600
      running on    CENTDB1 OS400 3 5 0010000A1E1B
13:25:06 28.02.2007   LOG: Profile          : no profile used
13:25:06 28.02.2007   LOG: Saposcol Version : [COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005]
13:25:06 28.02.2007   LOG: Working directory : /usr/sap/tmp
13:26:01 28.02.2007   LOG: Shared Memory Size: 339972.
13:26:01 28.02.2007   LOG: INFO: size = (1 + 60 + 3143) * 106 + 348.
13:26:01 28.02.2007   LOG: Connected to existing shared memory.
13:26:01 28.02.2007   LOG: Reused shared memory. Clearing contents.
13:26:04 28.02.2007   LOG: Collector daemon started
13:26:04 28.02.2007   LOG: read coll.put Wed Feb 28 13:22:01 2007
13:26:04 28.02.2007   LOG: Collector PID: 2469
13:27:05 28.02.2007   LOG: Set validation records.
14:00:32 28.02.2007 WARNING: Out of int limits in pfas41c1.c line 1528
12:58:37 10.03.2007   LOG: Stop Signal received.
12:58:38 10.03.2007   LOG: ==== Starting to deactivate collector ==========
12:59:01 10.03.2007   LOG: ==== Collector deactivated ================
Also, I have tried saposcol -d (and other parameters below):
saposcol -d
kill
clean
leave
quit.
delete the files coll.put, dev_coll"
4" From my open SAP message:
I have also done the following:
1 Check the authorizations of SAPOSCOL as mentioned in SAP Notes:
637174 SAPOSCOL cannot access Libraries of different SAP systems
175852 AS/400: Authorization problems in SAPOSCOL
2 Remove the shared memory (coll.put)
(according to SAP Note: #189072). You could find 'coll.put' in path:
'/usr/sap/tmp'.
3 End the following jobs in QSYSWRK:
QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA
4 Delete the temporary user space:
WRKOBJ OBJ(R3400/PERFMISC) OBJTYPE(USRSPC)
Afterwards you could start SAPOSCOL on operating system level.
Just logon to iSeries as <SID>OFR and run the following command:
SBMJOB CMD(CALL PGM(<kernel_lib>/SAPOSCOL) PARM('-l'))
JOB(SAPOSCOL) JOBQ(R3<SID>400/R3_<nn>)
LOG(4 0 SECLVL) CPYENVVAR(YES)
Thanks,
Traci"

SAPOSCOL is not running,shared memory not available

Hi,
While I tried to start the SAPOSCOL ,it is not starting and throughing the below error.
Profile          : no profile used
06:59:26 05.03.2010   LOG: Saposcol Version : [COLL 20.95 701 - V3.72 64Bit]
06:59:26 05.03.2010   LOG: Working directory : /usr/sap/tmp
06:59:26 05.03.2010   LOG: Process Monitoring active.
06:59:26 05.03.2010   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
06:59:26 05.03.2010   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
06:59:26 05.03.2010   LOG: The following processes will be monitored:
06:59:26 05.03.2010   LOG: Process:    jlaunch-DSAPINFO=IDH_00_dispatcher* for user:               idhadm
06:59:26 05.03.2010   LOG: Process:        jlaunch-DSAPINFO=IDH_00_server* for user:               idhadm
06:59:26 05.03.2010   LOG: Process:           jlaunch-DSAPINFO=IDH_00_sdm* for user:               idhadm
06:59:26 05.03.2010   LOG: RefreshDeviceFiltering failed - no filtering done!
06:59:26 05.03.2010   LOG: Shared Memory Size: 328100.
06:59:26 05.03.2010   LOG: Connected to existing shared memory.
06:59:26 05.03.2010   LOG: MaxRecords = 3492 <> RecordCnt + Dta_offset = 3031 + 61
06:59:42 05.03.2010 WARNING: WaitFree: could not set new shared memory status after 15 sec
06:59:42 05.03.2010   LOG: PfDeleteMonArea Failed
06:59:42 05.03.2010 _WARNING: Cannot create Shared Memory_
06:59:53 05.03.2010   LOG: check_remap: Switched to new shared memory.
Please help me regarding this .
Regards,
Minakshi

This is a bug in NT
Note 1322232 - saposcol: attaching to existing shared memory
I donot see a straight forward correction declared for the same issue in unix flavored systems. From the log file,working directory format(/usr/sap/tmp) looks like a unix box. Could you let us know the OS ? If its AIX there are many notes u may check , to begin with
Note 561356 - saposcol on AIX terminates due to memory leak
Note 710975 - FAQ: which saposcol should be used on AIX
cheers !
PRADi

Cannot create Shared Memory

Hi,
For maintenance activity we have restarted the system. When I checked in
ST06 for os collecotor is not running and "warning: cannot create shared memory". Then I have performed the following commands at OS level
saposcol u2013d
Collector > clean
Collector > quit
saposcol -k to stop the collector.
Before restarting
saposcol -d
Collector > leave (You should get a message Shared memory deleted)
Collector > quit
move the coll.put file
saposcol u2013f(Start the saposcol)
When I executed the last command. I got message saying that "Cannot create Shared Memory"
Environment:
Windows 2003 cluser environment.
4.6c
oracle 10g
Thanks and Regards
Satya

Hi Sergo,
No, but I restarted the SAP, DB and SAPOSCOL. SAPOSCOL is up and running but there is waring mmessage in log file as
02:27:11 19.04.2010   LOG: ====================================================================================
02:27:11 19.04.2010   LOG: =                           OS Collector Start
02:27:11 19.04.2010   LOG: ====================================================================================
02:27:11 19.04.2010   LOG: Starting C:\WINDOWS\SapCluster\SAPOSCOL.EXE
02:27:11 19.04.2010   LOG: Saposcol Version is [COLL 20.79 03/08/22 46D - 20.46 NT 04/08/01]
02:27:11 19.04.2010   LOG: Allocate Counter Buffer [10000 Bytes]
02:27:11 19.04.2010   LOG: Allocate Instance Buffer [10000 Bytes]
02:27:11 19.04.2010   LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0
02:27:11 19.04.2010   LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0
02:27:11 19.04.2010   LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0
02:27:11 19.04.2010   LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0
02:27:11 19.04.2010   LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0
02:27:11 19.04.2010   LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0
02:27:11 19.04.2010   LOG: INFO: saposcol's shared memory size is 86420.
02:27:11 19.04.2010   LOG: Connected to existing shared memory !
02:27:11 19.04.2010   LOG: MaxRecords = 637 <> RecordCnt + Dta_offset = 751 + 61
02:27:16 19.04.2010 WARNING: WaitFree: could not set new shared memory status after 5 sec
02:27:16 19.04.2010 WARNING: Cannot create Shared Memory
When I trying to stop the SAPOSCOL service. I got the message saying that
" Could not stop the SAPOSCOL service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion."
and it stopped the SAPOSCOL.
Then I am able to start SAPOSCOL.
The strange thing is in my environment, there are OS 10 drives but now I can see only 3 drives c, p and q.
Regards
Satya

XP Pro shared memory size of Intel GM45 on L305-S5905

Similar Messages

Maybe you are looking for