on 06-02-2014 10:42 AM
Hi,
I am running SCM upgrade from 5.1 to 7.03 (NW740). In execution phase XPRAS_AIMMRG failed with error.
Environment details:
OS : Windows server 2008 R2 x64
DB:MS SQL SERVER 2008 r2
RAM :8 gb
XPRASUPG.ELG log details below.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR740XPRA90000031.SCN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A4 ERSAU 570 Update rules "F4TGWVOWGL5NVTEJ6VZ9WVLNG" read in version "D"
A4 ERSAU 570 Update rules "F4TM9JFI13PM2A445BP5WJ5H5" read in version "D"
A4 ERSAU 570 Update rules "F4Y5X7RTPAFBA41SICS7TNO7V" read in version "D"
A4 ERSAU 570 Update rules "F5JPKIBC381H1WEHRMYPNJICG" read in version "D"
A4 ERSAU 570 Update rules "F5L2BHAN9AUCY8BJ9NIXUZQ23" read in version "D"
1AETR012XProgram canceled (job "RDDEXECL", number "03284300")
1AEPU320 See job log"RDDEXECL""03284300""SCN"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
RDDEXECL job is failed with dump SYSTEM_NO_ROLL and LOAD_NO_ROLL.
I have updated parameter mentioned in Note 353579 as ztta/max_memreq_MB =3397
Below are the memory related parameters in my system:
ztta/roll_area 3000000 Byte
ztta/roll_first 1 Byte
ztta/short_area 1600000 Byte
rdisp/ROLL_SHM 32768 8 kB
rdisp/PG_SHM 16384 8 kB
rdisp/PG_LOCAL 150 8 kB
em/initial_size_MB 3397 MB
em/blocksize_KB 4096 kB
em/address_space_MB 3397 MB
ztta/roll_extension 2000000000 Byte
abap/heap_area_dia 2000000000 Byte
abap/heap_area_nondia 0 Byte
abap/heap_area_total 536870912 Byte
abap/heaplimit 40000000 Byte
abap/use_paging 0
ztta/max_memreq_MB 3397
I have observed that PHYS_MEMSIZE value is 512 in my system when i check in RZ11. I want calculate parameter values according to my physical memory.And refered note 88416 zero administration memroy manager for ABAP.
But confused with the formulas mentioned for 740 release kernel system.
Please provide the solution to the above issue and the correct values for the parameters.
[RAM] = size of the physical main memory = 8GB
In 7.40, parameter values can contain formulas. The expression $(Parameter) in the value of a parameter references the value of the parameter with the name Parameter.
Profile parameter | Standard 64-bit | Unit: |
PHYS_MEMSIZE | 1.0 * [RAM] | MB |
em/initial_size_MB | 0.7 * $(PHYS_MEMSIZE) | MB |
em/max_size_MB | 1.5 * $(PHYS_MEMSIZE) | MB |
abap/buffersize | $(em/initial_size_MB) * 1024 * 0.15 | KB |
abap/programs | $(abap/buffersize) / 4 | Entries |
abap/heap_area_dia | 2000000000 | byte |
abap/heap_area_nondia | 0 | byte |
abap/heap_area_total | 1048576 * $(PHYS_MEMSIZE) | byte |
abap/shared_objects_size_MB | $(em/initial_size_MB) * 0.02 | MB |
em/address_space_MB | $(em/initial_size_MB) | MB |
em/max_size_MB | $(PHYS_MEMSIZE) * 1.5 | MB |
rdisp/wp_ca_blk_no | $(rdisp/elem_per_queue) * 3 | Entries |
rdisp/PG_SHM | max(min(1000+40*max(5,floor(($(PHYS_MEMSIZE)-128) *25/128)),16384),1024) | 8KB block |
rdisp/PG_MAXFS | 32768 | 8KB block |
rsdb/ntab/entrycount | $(zcsa/db_max_buftab) | Entries |
rsdb/ntab/ftabsize | min(500000, ($(rsdb/ntab/entrycount))) | KB |
rsts/ccc/cache07 | $(rsts/ccc/cachesize) * 0.1 | byte |
rtbb/buffer_length | $(zcsa/table_buffer_area) * 0.1 / 1024 | KB |
rtbb/max_tables | $(zcsa/db_max_buftab) * 0.1 | Entries |
zcsa/table_buffer_area | max(30000000,$(em/initial_size_MB) * 1024 * 1024 * 0.05) | byte |
ztta/roll_extension | 2000000000 | byte |
Please provide the parameter values according to RAM size 8b
PHYS_MEMSIZE
em/initial_size_MB
em/max_size_MB
abap/buffersize
abap/programs
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
abap/shared_objects_size_MB
em/address_space_MB
em/max_size_MB
rdisp/wp_ca_blk_no
rdisp/PG_SHM
rdisp/PG_MAXFS
rsdb/ntab/entrycount
rsdb/ntab/ftabsize
rsts/ccc/cache07
rtbb/buffer_length
rtbb/max_tables
zcsa/table_buffer_area
ztta/roll_extension
Thanks,
krishna
Added parameter values according to Note
Zero administration memory management on windows(Note-88416)
Restarted application server and restarted the upgrade process. Issue resolved.
Thanks,
Krihsna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Addition to that below are the Abap dump details:
Error analysis
More main memory area was requested.
The total available space has already been assigned however. Possible
causes:
- A large number of (large) internal tables
- A large number of (large) programs active
- Deep nesting of subroutines with large amounts of local data
Last error logged in SAP kernel
Component............ EM
Location.......... SAP-Server SCM51NUN_SCN_51 on host SCM51NUN (wp 13)
Version.............. 37
Error code............ 7
Error text............ Warning: EM-Memory exhausted: Workprocess gets PRIV
Description............
System call..........
Module.............. D:/depot/bas/741_REL/src/krn/em/emxx.c
Line................ 2369
The error reported by the operating system is: Error number.....
Error text....... " "
How to correct the error
Perform an analysis to find out whether this request makes sense or
whether a program error has occurred. Pay particular attention to the
internal table entries listed below.
The amount of memory (in bytes) used at termination time was:
Roll area...................... 0
Extended memory (EM) 94977424
Assigned memory (HEAP) 536318720
Short area.....................
Paging area.................... 40960
Maximum address space.......... " "
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:
"SYSTEM_NO_ROLL"
"CL_RSBK_DTP_DATABASE==========CP" bzw. CL_RSBK_DTP_DATABASE==========CM003
"COPY_FROM_DB"
Thanks,
Krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
1. Set the 30 % of memory to DB, you can define the memory setting in MS SQL MMC sudio
2. Since current version is lower, so you have define the memory parameters as mention in the SAP Note 88416
3. In SCM instance you can suspend the all back groups.& lock the user id which not required one
4. Kindly refer the SAP Note search with "System_no_roll"
1010762 - Add. info. on upgrading to SAP SCM 5.1 ABAP
BR
SS
Hi Krishna
Just do the full restart and then try again in the same phase
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.