Post Article

Welcome! Guest
New User? Register | Login
Home Tutorials FAQ Transaction Codes Useful Tips SAP Institutes Books Resume Jobs Submit Resume Post Job
Interview Questions
Post your Article
ShareThis
Search SAP Tutorials Search
Home BASIS
Windows: Problems due to address space fragmentation
By: Shailesh
Singh | 27
Sep 2007 1:55 am
Note 129813
Problems occur when you start an SAP
4.x instance with more than 2 GB of
physical memory and Zero
Administration Memory Management.
This effect can also appear in 3.1I
systems if the buffers are large (no
Zero Administration Memory
Management).
This effect can also occur after you
import Windows service packs or DB
upgrade packages in which DLLs have
been exchanged.
Caution:
Anew version of the Address Space
Viewer for I386 that permits you to rebase Jcontrol and Jlaunch processes without a passcode is
attached to this note as of 11 March, 2005.
SYMPTOM:
The instance does not start at all. The dev_w0 contains the entry:
*** ERROR => Reserve 512 MB error= 8
*** ERROR => Not enough contiguous space in process
or
*** ERROR => NTGetBaseAddress failed, no free region
The SAP R/3 instance under Windows NT starts with the message PXA_NO_SHARED_MEMORY.
The dev_w0 contains the message:
AError Code PXA_NO_SHARED_MEMORY.
AAllocating PXAin local storage, size=4MB
A*** WARNING: MINIMUMINSTALLATION ***
or
A---PXA------------------------------- APXAINITIALIZATION
*** ERROR => [MapOsShm] Can't find free space for Shared Memory...
*** ERROR => [CreateOsShm] MapViewOfFile(6,00000394) failed with..
Other terms
Address space, fragmentation under Windows NT
Reason and Prerequisites
Unfavorable Basis addresses of Windows system DLLs or DB Client DLLs fragment the address
space of the work processes. The large shared memory segments (PXA, extended memory...) may
under certain circumstances no longer be connected in the work process's virtual address space
since these DLLs fragment the available free address space.
The affected ABAP program buffer is generally the last one which was created. In turn, this makes the
system start the emergency PXAbuffer of only 4MB.
Solution
The following solutions are available:
Upgrade the application server to a 64-Bit version. If a 64-Bit version of SAP ABAP Server is available
and your hardware will support the required 64-Bit Windows Version, we recommend this upgrade.
You use an SAP ABAP Server 4.6D on an x86_64 hardware architecture, but you use a 32-bit
operating system.
For x86_64, no 64-Bit 4.6D ABAP Server kernel exists, however, if you use the Windows Server 2003
operating system for x64, the address space of the 32-bit kernel is increased from 2 GB (or 3 if the
/3GB option has been set in boot.ini) to 4 Gigabyte. By increasing the address space by one
Gigabyte, problems regarding the address space fragmentation may be reduced considerably.
If the problem occurs just after importing the 4.6D kernel, proceed according to Note 373326.
Decrease the large shared memory segments in size.
Reduce the reserved local address space for extended memory by setting the profile parameter
em/address_space_MB = 250 in the instance profile (also for activated zero administration memory
management). This makes more contiguous memory space available to the ABAP program buffer.
The individual user can, as a result, only allocate 250 MB extended memory and then changes into
the HEAP memory. Simultaneously, decreasing the value of the PXAbuffer (abap/buffersize) can also
eliminate the effect for now.
Expand the virtual address space.
If you use Windows 2000 or Windows Server 2003 Server, activate the '3GB' option, as described in
Note 110172. This may solve your problem completely.
SAP R/3
ABAP
BASIS
SAP Security
SAPGUI
Sales and Distribution
(SD)
Financial Accounting
(FI-CO)
Material Management
(MM)
Production Planning
(PP)
Quality Management
(QM)
Plant Maintenance (PM)
Human Resources (HR)
Project System (PS)
SAP CO Tips
Business One
Business Warehouse
(BW)
Business Workflow
(BW)
Advanced Planner and
Optimizer (APO)
Asset Management (AM)
Industry Solutions (IS)
Project Scheduling
Customer Relationship
Management (CRM)
Netweaver
SAP Exchange
Infrastructure (XI)
SAP Solution Manager
NetWeaver
SAP Quick Help
Useful Tips
FAQ
SAP Glossary
Transaction Codes
SAP Consultants
SAP Resume
Sample Resume
Education Services /
Training / Certification
SAP Partners
Java/SAP development
UNIX
Oracle Database
MaxDB
SAP Third Party
Products
SAP Alliances
PHP
SAP NEWS/Announcements
SAP NEWS
Announcements
Classifieds
SAP NON Technical
About SAP
User Account
Management
Get Secure Account
Provisioning on
Servers & Platforms.
Learn More Now
www.Centrify.com/On-Demand-Webinar
SAP Jobs at
Accenture
Submit a Resume for
SAP Careers with a
Global Leader. Apply
Now.
www.accenture.com
SAP Basis
Consulting
Symmetry's Basis
Experts have the
solutions you need
www.Sym-Corp.com
Free S.A.P Training
100s of S.A.P training
Providders Free S.A.P
training all Modules
www.benchfolks.com
Siemens Runs
Greener
Learn How SAP Helps
Siemens Improve
Resource Management
www.SAPRunBetter.com/greener
www.QlikView.com
Ads by Google
Like Be the first of your friends to like this.
ManageEngine.com/EventLogAnalyzer Ads by Google
converted by Web2PDFConvert.com
Change the Basis addresses of the DLLs (rebase).
This method can be used for very large abap/buffersize parameters in particular.
You can use the "SAP Address Space Viewer" to change the DLLs' basis addresses and clear the
address space. The tool is attached to this note.
CAUTION: The I386 had to be split. Unpack the files sapadrspcI386_1.sar andsapadrspcI386_2.sar
into the same directory.
Below you can find brief instructions to quickly rebase the affected DLLs on an application server.
The steps need be performed only once for each application server and only for a single
DISP+WORK process, because all work processes load the same DLLs.
Note that it may be necessary to rebase and restart several times, since the affected DLLs are not
always reached by the first rebasing (for example, if they were located in an address space not
relevant for the SAP System).
NOTE :
If you use Windows 2000 or Windows Server 2003, Windows File Protection (WFP) may prevent the
rebasing of system DLLs since those are automatically replaced by the original DLLs. For more
information about Windows File Protection see: http://support.microsoft.com/default.aspx?
scid=kb;EN-US;222193
All DLLs in directory %windir%\system32\dllcache are subject to WindowsFile Protection.
For information about rebasing DLLs under Windows File Protection referto Note 664269.
How to proceed:
a) Reduce the large shared memory segments in size as described above to allow the SAP System
to start successfully.
b) Log on to the application server with a local administrator account (for example, adm).
c) Install the "SAP Address Space Viewer": Unpack the archive into any directory, and start the
program "setup.exe". Select all components displayed, and confirm the following dialogs.
d) Start the 'SAP Address Space Viewer' by choosing Start -> Programs -> SAP Tools -> SAP Address
Space Viewer.
e) In the window displayed, press the button 'System DLLs' and then 'Collect'. Confirm the default
value displayed. This determines the Windows system DLLs' basis addresses, in order to avoid
conflicts with new Basis addresses. Exit the window with 'OK'. This action only has to be carried out
once after you install the tool.
f) In the process window displayed, select one DISP+WORK.EXE (but not the dispatcher -> note the
value in the column 'Type'), and press the 'Clean Address Space' button.
g) The next window displays the list of DLLs that fragment the address area of the work process.
Make sure that the checkbox 'Rebasing without Passcode' (new as of Version 6.2) is activated, and
press the 'Rebase' button. This option defragments the adress area provided and tested by SAP
without requiring you to enter a passcode.
Note:
By manually deactivating the checkbox mentioned you can change the adress area to be
defragmented and the target area. However, we do not recommend that you do this, since the
consequences can be critical. For this reason, the system asks you to enter a passcode provided by
SAP when you try to rebase with this checkbox disabled. SAP will only release the passcode after
having previously checked the selected address area. You can only perform the rebasing after you
have entered the passcode.
To obtain the passcode for rebasing the affected DLLs, create a customer message that contains
the rebasing key and a list of the DLLs with their corresponding base addresses located in the
predefined address space. You can generate a list of the DLLs with the button 'Print' or with one of
the following commands:
- sapadrlist.exe /p
- sapadrlist.exe /d
- tlist
Passcodes are presently only assigned by the SAP Development after the information transferred
has been checked. This can take one or two days. As an interim solution until you receive the
passcode, reduce the large shared memory segments in size as shown above and implement the
described solutions.
After receiving and entering the passcode, confirm this dialog box with 'OK'. The DLLs are now
rebased. Check the displayed log for possible errors.
h) After successfully rebasing, exit the 'SAP Address Space Viewer', stop the SAP System, remove the
parameter em/address_space_MB from the instance profile or change the value from
abap/buffersize back to its original value. Boot the application server.
The problem should be solved the next time you start the R/3 instance.
For more information about the problem and a more detailed description of the tool used and the
rebase method see the Online help "SAPADRSPC.CHM".
In case that the SAP processes are not displayed by the Address Space Viewer, make sure that both
SAPService and the user starting the SAP Address Space Viewer have been added to the local group
of "Administrators".
The following list shall serve for identifying the SHM(shared memory) segments
(according to the ID in square brackets in layout SHM[]):
: ID - Description
------------------------------------------------------------------
1 : SHM_SYS_ADM_KEY - application server admin.
2 : SHM_DP_ADM_KEY - disp. administration tables
3 : SHM_DP_CA_KEY - disp. communication areas
4 : SHM_PF_KEY - statistic area
5 : SHM_SAPSCSA_AREA_KEY - scsa area
6 : SHM_PXA_KEY - abap
7 : SHM_VB_ADM_KEY - update
8 : SHM_PAGING_AREA_KEY - shared paging
9 : SHM_ROLL_AREA_KEY - shared roll
10 : SHM_POOL_0 - shared memory pool
11 : SHM_CALI_BUFFER - factory calendar buffer
12 : SHM_CCC_KEY - TemSe char code convert buf.
Articles
Ads by Google
Sap Consultants
Sap Fico
Sap Integration
Consultor Sap
Tablas Sap PP
converted by Web2PDFConvert.com
Submit Comment
13 : SHM_ALERT_AREA_KEY - alert area
14 : SHM_PRES_BUF - presentation buffer
15 : DVS_SHM_KEY - document administration
16 : SHM_SEM_MONI_BUFFER - Sema activity monitoring
17 : SHM_ROLL_ADM_KEY - roll administration
18 : SHM_PAGING_ADM_KEY - paging adminitration
19 : SHM_DB_TBUFF - table-buffer
20 : SHM_GW_POOL - Gateway pool:
21 : SHM_GW_TAB - Gateway tables
22 : SHM_GW_REQ1 - Gateway req table
23 : SHM_GW_REQ2 - Gateway req table seg. 2
24 : SHM_GW_REQ3 - Gateway req table seg. 3
25 : SHM_GW_REQ4 - Gateway req table seg. 4
26 : SHM_GW_REQ5 - Gateway req table seg. 5
27 : SHM_GW_REQ6 - Gateway req table seg. 6
28 : SHM_GW_REQ7 - Gateway req table seg. 7
29 : SHM_GW_REQ8 - Gateway req table seg. 8
30 : SHM_THRUN_ADM_KEY - Taskhandler runtime admin.
31 : SHM_REQ_QUEUE_KEY - Dispatcher request queue
33 : SHM_DB_TBUFF_P - table buffer, part.buffering
34 : SHM_ENQ_TABLE_KEY - enqueue table
35 : SHM_SAPCOM- SAP communication BK/EDI
36 : SHM_PERF_MON_AREA_KEY - performance monitoring
37 : SHM_SEM_ADM_AREA- fast SEMADMon MPE
38 : SHM_AS4_ES_ADM- ext.memory admin on AS400
39 : SHM_QUE_ADM_AREA- queue ADMon AS400
40 : SHM_DB_POOL - database buffer pool
41 : SHM_DB_STBUFF - DB statistics buffer
42 : SHM_DB_TTBUFF - DB TTAB buffer
43 : SHM_DB_FTBUFF - DB FTAB buffer
44 : SHM_DB_IRBUFF - DB IREC buffer
45 : SHM_DB_SNTBUFF - DB short nametab buffer
46 : SHM_DB_SYNC - DB sync table
47 : SHM_DB_CUA_BUFFER - DB CUAbuffer
48 : SHM_NO_BUFFER - number range buffer
49 : SHM_RSPO_ADMIN - spool admin (SpoolWP+DiaWP)
50 : SHM_POOL_50 - shared memory pool
51 : SHM_EM_ADM- Ext. Memory Administration
52 : SHM_MSBUF - buffer for MsgServer list
53 : SHM_EM_ADM_T - Ext. Memory Administration
54 : SHM_DB_OBJ_BUFFER - export/import buffer
55 : SHM_RSPO_LOCAL_KEY - spool local printer+joblist
56 : SHM_PF_AS_KEY - application statistics
57 : SHM_PROFILE - profile in shared memory
58 : SHM_ENQID_KEY - EnqId
59 : SHM_ENQ_2_TABLE_KEY - AS400 enqueue table ext.
60 : SHM_ENQ_3_TABLE_KEY - AS400 enqueue table ext.
61 : SHM_AS4_ES_ADM2 - ext.memory admin on AS400
62 : SHM_MPI_ADM- memory pipes (see krn/mpi)
63 : SHM_ICM_MAN - memory for ICM
64 : SHM_DB_OTR_BUFFER - online text repository buf.
65 : SHM_DB_ESM_BUFFER - export/import shared memory
Comments
No Comments Posted for this Article.
Leave a comment
Type the characters you see in the picture below.
SAP Online Help | SAP Jobs | SAP Training | SAP Books | SAP Software | SAP News | RSS/Syndication | Contact Us
Free Classifieds & Business Listing | SAP ERP Support/Consulting | Online Travel Portal & Community | Terms Of Use | Terms & Conditions
2005-2010 SAP Techies. All rights reserved.
Ads by Google Fi Co Sap Sap Resume
Ads by Google Sap HR Resume Sap Consultant
converted by Web2PDFConvert.com

Search... Like 0
converted by Web2PDFConvert.com