here is no thumb rule for maximum memory a good program can consume in the system but based on your experience can you please let me know at least the range ?
I came across with a situation that there is program which is fetching about 2 million records of total size around 190MB. But system could not allocate this much memory so the program aborted. I suggested them to process only 50,000 records at a time which worked fine. But I want to know if my suggestion was good enough. Can't the system with below configuration allocate 190MB for a program. There was no much load on the system at that time.
Our configuration:
SAP 46c on Win 2K
RAM: 4GB
Virtual memory: 8GB.
Do you guys know what are all the things to be done to enable ZERO MEMORY MANAGEMENT in 46C ?
You can get an overall estimate by looking in SM04 and switching on the MB size beside the users so so you will see how much memory the current transactions are using. Take into consideration that there is a big difference between dialog transactions (with several steps) and mass processing or lists. The latter two consume usually a lot more memory.
190 MB is not much, our usercontextes can become as big as 2 GB per user (which is the limit on 32bit platforms) several times a day. This is not uncommon on systems that have a lot of data in them, however, it's impossible to give a general advise here since this is VERY different on what applications you are running, how many systems are connected (BW,
CRM, APO etc.) and so on.
Start with note 88416, there is explained in depth what it is and how it works.
For Windows you also should look in note 129813 which will describe the rebasing process since M$ has the start addresses of their DLLs loaded into the PXA. This is one reason why we switched to a non M$ operating system because after each IE patch (in fact after each patch) you need to check if the new DLLs will fragment your PXA/shared memory.
Note 546361 can also be helpfull. If you have "hangs" in the system read note 530871 which will describe the problem (and finally recommend upgrading to Windows 2003).
What is Zero Administration Memory Management?
The zero administration memory management on Windows requires no manual settings and adapts itself dynamically to the memory requirements of the users. Even hardware changes (for example memory enhancement) are detected and the parameters set correspondingly.
The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. An "infinitely" large memory resource is made available with this method. The extended memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended memory extends itself in steps of "[PM] / 2" up to the set limit of the profile parameter em/max_size_MB or until the address space in the Windows pagefile is used up.
By setting the standard value for em/max_size_MB to 20000 MB (100000 MB for 64 bit), it is the size of the Windows pagefile that finally represents the actual limit for the extension of the extended memory. The profile parameter PHYS_MEMSIZE determines how much of the entire main memory is to be used by SAP. The parameter is entered during installation in accordance with the entry. The standard valuefor PHYS_MEMSIZE is the size of the main memory [HS]. Even with zero administration management, the Windows system should be configured in such a way that it keeps the file cache to a minimum size. Therefore, make sure that indicator "Maximize Throughput for Network Application" is activated under 'Control Panel' -> 'Network' -> 'Services' -> 'Server' -> 'Properties'.
What is the Maximum Memory a good Program Should Request
How to Find How Much Allocated Memory
What tcode can I used to find out how much memory is allocated to R/3 in total? I know for Oracle I can get the SGA memory. I am using SAP 4.7 / Oracle 9i on Unix AIX.
Go to ST02 --> Detailed analysis --> Sap memory. This will let you know memory allocated for that app server. You can also find out memory allocated for user (mode list) and Quotas.
You can also use report RSMEMORY to find out how sap alloctes memory to Dia and Non Dia work processes.
I'm afraid that is incorrect. The question is also not a simple answer.
Go to ST02 --> Detailed analysis --> Storage is the correct path. The Virtual memory allocated line shows SAP's allocated memory.
This memory does not include what the DB uses or the OS or other things running on the server. More importantly it does not include heap (private memory) allocated by WP's. It also does not include the executable size of the GW, the ICM and the dispatcher but it does include most of their memory in the shared memory areas.
It also does not allow for additional memory that a Windows system may dynamically allocate to extended memory if the users use it all up.
Question on Shared Memory and IMODE
Can someone tell me about Shared memory (Code Definition) and IMODE?
I have never heard these terms in SAP R/3, Shared momey sounds like its related to Operating System.
All memory is OS memory I'm afraid there is little distinction in that regard.
Shared memory is memory that can be addressed by different processes as opposed to private memory that can only be addressed by the process that creates it. A good examlpe would be the Program Buffer (PXA) this buffer hold the recently used programs in memory for fast access and needs to be read by all work processes. A more impotrant shared memory area is extended memory. In 32 bit processing you need to keep shared memory areas at a minimum because otherwise you limit the amount of space in the address space that your program can use for its own data. I won't get into a sad chat about all this bat thats hared memory.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
An IMODE is an internal mode. An example may be best, log onto a SAP system, create a new session and leave one at the main menu and with the other go to ST02. In ST02 near the bottom of the screen double click on the extended memory line. In the next screen click on the Mode List button. You will see you have the ST02 session marked with an X for being attached and another session in IMODE 0.
With the other session got to SM36 then swap back to ST02, press enter and you will see the session has an IMODE 0 and an IMODE 1 use. Now from the SM36 screen click on the button Job Selection and jump back to St02 and press enter, you will see the session has an imode 0 1 and 2 active.
Imode 0 is not really an IMOde but the main mode that all your information relevant in any transaction is available. As you call transactions inside transactions you need new memory and the old stuff needs to be save for when you green arrow back. This is why you have imodes so that when you green arrow back from the job selection screen above (I mode2) it is no longer the active mode and imode 1 is reactivated.
Incorrect SAP login logs
With report RSUSR006, you can check those users that have been locked.
For those that are not locked, the report will list down the number of wrong login that the users have done.
List of Inactive Users Logs
To list out all the users who are inactive for the last 6 months, which means they have not logged into the SAP server.
If you have lots of affiliates to your main company, this will result in lots of users. Out of them, there might be lots of inactive users who have left the company.
You may wish to delete those inactive users.
Use SA38 to run RSUSR200.
This report is part of the AIS (Audit Information System) and will report users who have not logged on for a specified period of time.
Finding the SAP Statistics for transactions and programs
When was a program, transaction last used?
How to know which users are using which transaction or executing which program?
Which are the most frequently used programs or transaction?
To know how many users are viewing and maintaining a particular transaction use transaction 'ST03', in3.0x :-
* Performance database
* Select instance
* Select desired period
* Choose Transaction profile
To find the Frequently Used Programs or Transactions in 4.6x :-
ST03 ---> Detail analysis Button --> Under Global - One recent period then select day or week or month ---> Transaction profile Button
In 4.6x, you can also try the new Workload Analysis tcode 'ST03N'.
The SAP standard retention period is 3 months. You can change the Standard Statistics via clicking :-
Goto -> Parameters -> Perfomance Database
To analyze the Statistics by users for transactions and programs use transaction STAT
STAT looks at the STAT file created by each SAP Instance.
It is by default 100 MB. Every hour there is a COLLECTOR_FOR_PERFORMANCE job RSCOLL00 aggregating this data into MONI table. It will truncate STAT file once the specified limit is reached.
So, you can see details for however many days in this 100 MB using STAT, or ST03 to see the MONI aggregated data.
To change the 100 MB limit, ST03 -> Goto -> Parameters -> Performance Database.
Statistical Logs for all the R/3 System
o check the workload statistics for all the R/3 System, go to transaction STAD.
Why data was not showing in ST03?
Problem:
Last one month I face this problem when I am taking full system o/s backup of production server stopping all the oracle automatic serveice with SAPOSCOL & SAPPRD_00 , STOP SAPMMC. When backup was completed, I started all the service. However, after some time data was not showing in ST03. When I stop & start this sap services SAPOSCOL & SAPPRD_00, then data will start showing for some time but after 2 day same problme comes again.
All sap pjobs are running well. What could be the problem in SAP.
Details of server:
O/S : Windows 2003
SAP : 4.7 EE
Oracle : 9i
Solution:
1. Ensure that the job COLLECTOR_FOR_PERFORMANCEMONITOR executes the report RSCOLL00 hourly. Furthermore, the report RSSTAT80 should be executed every hour. You achieve this by maintaining the table TCOLL with transaction SM31. Enter "X" in every hour for the report RSSTAT80 (column "Time of day").
2. The report RSSTAT80 should be executed every hour. You achieve this by maintaining the table TCOLL with transaction SM31. Enter "X" in every hour for the report RSSTAT80 (column "Time of day"). You should then increase the maximum number of statistics records read in each run of RSSTAT80. You can set this value with transaction ST03, Goto -> Parameters -> Performance database. Press "Modify parameters" and enter at least 10,000 for the value "Max. number of records cumulated per call". You must then save the settings.
3. Using transaction ST03, Goto -> Parameters -> Performance database, pushbutton "Modify parameters", increase the value of "Max. number of records cumulated per call" to at least 10,000 and save the change. If this or a larger value is already set, please proceed as in point 2.
Statistics of SAP Application Modules
he transaction ST07 provide information such as the numbers of users logged on into each of the SAP Application modules.
Double click on the application modules for more information breakdown.
If there are no analysis data is available for the history in ST07, it is because the program RSAMON40, which generates snapshots of the application monitor data and saves them to the database, has not started yet. If RSAMON40 runs regularly, the data may sometimes be deleted again by a reorganization program.
For releases lower than 31I, schedule the program RSAMON40 periodically (hourly) as a background job.
As of Release 31I, this report is automatically carried out by the performance collector (RSCOLL00). Check the scheduling of RSAMON40 in table TCOLL as described in note 12103.
To prevent the data from being deleted again by a reorganization program, you must still make the following entry in the SAPWLREORG table:
CI ID =
MONIKEY = --
RESIDENCY = 0
