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 fragmentationBy: ShaileshSingh | 27Sep 2007 1:55 am Note 129813

Problems occur when you start an SAP4.x instance with more than 2 GB ofphysical memory and ZeroAdministration Memory Management.

This effect can also appear in 3.1Isystems if the buffers are large (noZero Administration MemoryManagement).

This effect can also occur after youimport Windows service packs or DBupgrade packages in which DLLs havebeen exchanged.

Caution:A new version of the Address Space

Viewer for I386 that permits you to rebase Jcontrol and Jlaunch processes without a passcode isattached 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 processor*** ERROR => NTGetBaseAddress failed, no free regionThe SAP R/3 instance under Windows NT starts with the message PXA_NO_SHARED_MEMORY.The dev_w0 contains the message:A Error Code PXA_NO_SHARED_MEMORY.A Allocating PXA in local storage, size=4MBA *** WARNING: MINIMUM INSTALLATION ***orA---PXA------------------------------- A PXA INITIALIZATION*** 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 addressspace of the work processes. The large shared memory segments (PXA, extended memory...) mayunder certain circumstances no longer be connected in the work process's virtual address spacesince 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 thesystem start the emergency PXA buffer 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 availableand 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-bitoperating system.For x86_64, no 64-Bit 4.6D ABAP Server kernel exists, however, if you use the Windows Server 2003operating 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 oneGigabyte, 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 parameterem/address_space_MB = 250 in the instance profile (also for activated zero administration memorymanagement). 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 intothe HEAP memory. Simultaneously, decreasing the value of the PXA buffer (abap/buffersize) can alsoeliminate 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 inNote 110172. This may solve your problem completely.

SAP R/3

ABAPBASISSAP SecuritySAPGUISales 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 TipsBusiness OneBusiness Warehouse(BW)Business Workflow(BW)Advanced Planner andOptimizer (APO)Asset Management (AM)Industry Solutions (IS)Project SchedulingCustomer RelationshipManagement (CRM)Netweaver

SAP ExchangeInfrastructure (XI)SAP Solution ManagerNetWeaverSAP Quick Help

Useful TipsFAQSAP GlossaryTransaction CodesSAP Consultants

SAP ResumeSample ResumeEducation Services /Training / CertificationSAP Partners

Java/SAP developmentUNIXOracle DatabaseMaxDBSAP Third PartyProductsSAP AlliancesPHPSAP NEWS/Announcements

SAP NEWSAnnouncementsClassifiedsSAP NON Technical

About SAP

User AccountManagementGet Secure AccountProvisioning onServers & Platforms.Learn More Nowwww.Centrify.com/On-Demand-Webinar

SAP Jobs atAccentureSubmit a Resume forSAP Careers with aGlobal Leader. ApplyNow.www.accenture.com

SAP BasisConsultingSymmetry's BasisExperts have thesolutions you needwww.Sym-Corp.com

Free S.A.P Training100s of S.A.P trainingProvidders Free S.A.Ptraining all Moduleswww.benchfolks.com

Siemens RunsGreenerLearn How SAP HelpsSiemens ImproveResource Managementwww.SAPRunBetter.com/greener

www.QlikView.comAds 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 theaddress space. The tool is attached to this note.CAUTION: The I386 had to be split. Unpack the files sapadrspcI386_1.sar andsapadrspcI386_2.sarinto 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 singleDISP+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 notalways reached by the first rebasing (for example, if they were located in an address space notrelevant for the SAP System).

NOTE :If you use Windows 2000 or Windows Server 2003, Windows File Protection (WFP) may prevent therebasing of system DLLs since those are automatically replaced by the original DLLs. For moreinformation about Windows File Protection see: http://support.microsoft.com/default.aspx?scid=kb;EN-US;222193All 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 Systemto 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 theprogram "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 AddressSpace Viewer.e) In the window displayed, press the button 'System DLLs' and then 'Collect'. Confirm the defaultvalue displayed. This determines the Windows system DLLs' basis addresses, in order to avoidconflicts with new Basis addresses. Exit the window with 'OK'. This action only has to be carried outonce after you install the tool.f) In the process window displayed, select one DISP+WORK.EXE (but not the dispatcher -> note thevalue 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, andpress the 'Rebase' button. This option defragments the adress area provided and tested by SAPwithout requiring you to enter a passcode.

Note:By manually deactivating the checkbox mentioned you can change the adress area to bedefragmented and the target area. However, we do not recommend that you do this, since theconsequences can be critical. For this reason, the system asks you to enter a passcode provided bySAP when you try to rebase with this checkbox disabled. SAP will only release the passcode afterhaving previously checked the selected address area. You can only perform the rebasing after youhave entered the passcode.To obtain the passcode for rebasing the affected DLLs, create a customer message that containsthe rebasing key and a list of the DLLs with their corresponding base addresses located in thepredefined address space. You can generate a list of the DLLs with the button 'Print' or with one ofthe following commands:- sapadrlist.exe /p - sapadrlist.exe /d - tlist Passcodes are presently only assigned by the SAP Development after the information transferredhas been checked. This can take one or two days. As an interim solution until you receive thepasscode, reduce the large shared memory segments in size as shown above and implement thedescribed solutions.After receiving and entering the passcode, confirm this dialog box with 'OK'. The DLLs are nowrebased. Check the displayed log for possible errors.

h) After successfully rebasing, exit the 'SAP Address Space Viewer', stop the SAP System, remove theparameter em/address_space_MB from the instance profile or change the value fromabap/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 therebase method see the Online help "SAPADRSPC.CHM".

In case that the SAP processes are not displayed by the Address Space Viewer, make sure that bothSAPService and the user starting the SAP Address Space Viewer have been added to the local groupof "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 tables3 : SHM_DP_CA_KEY - disp. communication areas4 : SHM_PF_KEY - statistic area5 : SHM_SAPSCSA_AREA_KEY - scsa area6 : SHM_PXA_KEY - abap7 : SHM_VB_ADM_KEY - update8 : SHM_PAGING_AREA_KEY - shared paging9 : SHM_ROLL_AREA_KEY - shared roll10 : SHM_POOL_0 - shared memory pool11 : SHM_CALI_BUFFER - factory calendar buffer12 : SHM_CCC_KEY - TemSe char code convert buf.

ArticlesAds 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 area14 : SHM_PRES_BUF - presentation buffer15 : DVS_SHM_KEY - document administration16 : SHM_SEM_MONI_BUFFER - Sema activity monitoring17 : SHM_ROLL_ADM_KEY - roll administration18 : SHM_PAGING_ADM_KEY - paging adminitration19 : SHM_DB_TBUFF - table-buffer20 : SHM_GW_POOL - Gateway pool:21 : SHM_GW_TAB - Gateway tables22 : SHM_GW_REQ1 - Gateway req table23 : SHM_GW_REQ2 - Gateway req table seg. 224 : SHM_GW_REQ3 - Gateway req table seg. 325 : SHM_GW_REQ4 - Gateway req table seg. 426 : SHM_GW_REQ5 - Gateway req table seg. 527 : SHM_GW_REQ6 - Gateway req table seg. 628 : SHM_GW_REQ7 - Gateway req table seg. 729 : SHM_GW_REQ8 - Gateway req table seg. 830 : SHM_THRUN_ADM_KEY - Taskhandler runtime admin.31 : SHM_REQ_QUEUE_KEY - Dispatcher request queue33 : SHM_DB_TBUFF_P - table buffer, part.buffering34 : SHM_ENQ_TABLE_KEY - enqueue table35 : SHM_SAPCOM - SAP communication BK/EDI36 : SHM_PERF_MON_AREA_KEY - performance monitoring37 : SHM_SEM_ADM_AREA - fast SEM ADM on MPE38 : SHM_AS4_ES_ADM - ext.memory admin on AS40039 : SHM_QUE_ADM_AREA - queue ADM on AS40040 : SHM_DB_POOL - database buffer pool41 : SHM_DB_STBUFF - DB statistics buffer42 : SHM_DB_TTBUFF - DB TTAB buffer43 : SHM_DB_FTBUFF - DB FTAB buffer44 : SHM_DB_IRBUFF - DB IREC buffer45 : SHM_DB_SNTBUFF - DB short nametab buffer46 : SHM_DB_SYNC - DB sync table47 : SHM_DB_CUA_BUFFER - DB CUA buffer48 : SHM_NO_BUFFER - number range buffer49 : SHM_RSPO_ADMIN - spool admin (SpoolWP+DiaWP)50 : SHM_POOL_50 - shared memory pool51 : SHM_EM_ADM - Ext. Memory Administration52 : SHM_MSBUF - buffer for MsgServer list53 : SHM_EM_ADM_T - Ext. Memory Administration54 : SHM_DB_OBJ_BUFFER - export/import buffer55 : SHM_RSPO_LOCAL_KEY - spool local printer+joblist56 : SHM_PF_AS_KEY - application statistics57 : SHM_PROFILE - profile in shared memory58 : SHM_ENQID_KEY - EnqId59 : 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 AS40062 : SHM_MPI_ADM - memory pipes (see krn/mpi)63 : SHM_ICM_MAN - memory for ICM64 : SHM_DB_OTR_BUFFER - online text repository buf.65 : SHM_DB_ESM_BUFFER - export/import shared memory

CommentsNo 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 C lassifieds & 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

Windows: Problems due to address space fragmentationCommentsLeave a comment