Abap/heap_area_total
Hi,
While running a job it fails with the below error
======================================================================
A Tue Mar 11 10:01:15 2008
A WP has reached abap/heaplimit = 40000000 bytes
A
A Tue Mar 11 10:05:40 2008
A *** ERROR => User 104418 reached avail. heapsize = 1905 MB: see ST22 [abstor.c 1681]
A *** ERROR => Increase abap/heap_area_total [abstor.c 1682]
A *** ERROR => heap memory WP0: 1905 MB [abstor.c 1686]
========================================================================
What is the best option to avoid this error?, changing the parameter values(should not cause page in/out which results in perfomance)?
Currently i have the following values set
============================
abap/heap_area_dia 2000000000
abap/heap_area_nondia 2000000000
abap/heap_area_total 2000000000
abap/heaplimit 40000000
============================
Regards,
Sam
Hello Cheriyan,
I would recommend tuning the affected program instead alongwith memory tuning. Normally on AIX, we keep more extended memory and lesser heap memory.
Also considering you have 64-Bit AIX.
If you keep extended memory sufficiently large, dialog process do not go into PRIV mode easily and avoid using the heap.
Also accessing extended memory is faster for programs cause it uses memory pointer switching.
Please check the following SAP Note:
Note 191801 - AIX 64-bit with very large amount of Extended Memory
Regards,]
Siddhesh
Similar Messages
-
TIME_OUT ABAP DUMP executing KE30 in Business time
HI All,
when or users areexecuting KE30 in peak load time , say from 8:00 AM to 6:00 PM it times out , but on weekends and evenings where there is less load on system it executes properly, below are memory paramaters on app server
ztta/roll_area 6500000 Byte Roll area per workprocess (total)
ztta/roll_first 1 Byte First amount of roll area used in a dialog WP
ztta/short_area 4000000 Byte Short area per workprocess
rdisp/ROLL_SHM 24576 8 kB Part of roll file in shared memory
rdisp/PG_SHM 16384 8 kB Part of paging file in shared memory
rdisp/PG_LOCAL 150 8 kB Paging buffer per workprocess
em/initial_size_MB 8192 MB Initial size of extended memory
em/blocksize_KB 4096 kB Size of one extended memory block
em/address_space_MB 4092 MB Address space reserved for ext. mem. (NT only)
ztta/roll_extension 4000000000 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia 4000000000 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia 4000000000 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total 4000000000 Byte Max. usable heap memory
abap/heaplimit 40000000 Byte Workprocess restart limit of heap memory
ar running on db2 9.7 fp4 Instance memory is 40GB, STMM is ON, not sure what further i can tune on DB,
Regards
thummaHello Thumma,
1). When running the transaction, did you checked what are the tables its reading ? Try to run ST05 trace and create an Index for the table which spends most time on it.
2). On the tables that you see in SM50 for the t-code KE30, run Individual statistics in DB20.
3). How is your St02 buffers look like. Did you run SAPPFPAR Check ?
You can run like /usr/sap/<SYSTEMNAME>/SYS/exe/run/sappfpar check pf=/usr/sap/<SYSTMENAME>/SYS/profile/<Profile name> nr=<System number> name=<System name>
Tune the SWAPs as recommended by SAPPFPAR . Refer to below link
http://basishowto.blogspot.com/2011/07/sappfpar-tools-to-check-sap-server.html
Regards,
Arjun -
ABAP process job ( BI_PROCESS_ABAP ) in process chain running for long time
Dear Experts,
We have an ABAP process job BI_PROCESS_ABAP in a process chain. This job is running for a very long time than previous run time.
Recently we had an ORACLE database upgrade from 9.2 to 10g.
From the very next day , we are having this problem.
And also previously this process-chain was under control of BASIS guys . they were using a tool called CRONACLE to schedule it. At the time of upgrade this tool was crashed and they asked us to schedule it in BW system instead.
Underlying program is using two custom tables.
one is having both primary & secondary indexes but the other table is having only primary index.
I am not sure whether we have secondary indexes on other table prior to upgrade or not.
Where must be the problem?...
At the time of upgrade BASIS has re-organized the table space along with database upgrade.
please help me...
Regards,
SRIKANTHPlease ask yr basis consultant to check the system parms.
Below i have listed down SAP recommneded system parms .
abap/heap_area_total 4000000000
abap/heap_area_dia 2000000000
abap/heap_area_nondia 2000000000
Also check in SM37 if any other jobs are running for long time, peventing the your job running.
Check the SM12 for locks or SM58 -
Error 'Processeur ABAP : TSV_TNEW_PAGE_ALLOC_FAILED'
Hi all,
I have developed a custom program (Z-program) for a interface and its working fine in the development server.But in the testing server its running for more than '34 HRS' then interrupted giving a dump stating that
' Processeur ABAP : TSV_TNEW_PAGE_ALLOC_FAILED '.
NOTE: The testing server has Millions of records in DB tables whereas Development server has few records.
The reason for the error is ' You attempted to extend an internal table, but the required space was
not available ' .
The exact error is happening in the Program 'SAPLBUPA_SELECT' which is being used inside the Custom function module in the main program.
These are the Memory space being used by the program.
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6219104
Extended memory (EM)........... 2002803088
Assigned memory (HEAP)......... 1999943184
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 4294967295
Is it a good practice to increase the memory parameters like ' ABAP/HEAP_AREA_TOTAL, ABAP/HEAP_AREA_NONDIA, ABAP/HEAP_AREA_DIA ' since it will affect the memory space being allocated for the entire testing server.
Orelse to Include the OSS note specific for this particular problem [ You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"TSV_TNEW_PAGE_ALLOC_FAILED" C
"SAPLBUPA_SELECT" or "LBUPA_SELECTF03"
"FILL_BUFF_BUT000_SINGLE"
Please suggest me a solution so that we can transport the program in Production <removed by moderator>.
Many thanks in advance.
Edited by: Thomas Zloch on Jun 28, 2011 10:05 AMHi,
The problem arising in the standard FM 'BUP_BUT000_SELECT_SINGLE' which has been used in one of the Custom FM which inturn based on the Partner No, fetches the "solvency score' value which is the basic need of the program.
So, we need to find the solvency score value for all the Business Partners , in such a case all the entries will be filled in the internal table.
The problem creating line is ' insert is_but000_buf into table gt_but000_buf ' inside the sub-routine
' fill_buff_but000_single ' which is inside the FM 'BUP_BUT000_SELECT_SINGLE' .
The worst thing is even before the table " gt_but000_buf" is being filled the program is giving Dump.
The internal table (with the internal identifier "IT_20047967") could not be
enlarged any further. To enable error handling, the internal table had
to be deleted before this error log was formatted. Consequently, if you
navigate back from this error log to the ABAP Debugger, the table will
be displayed there with 0 lines.
When the program was terminated, the internal table concerned returned
the following information:
Line width: 1142
Number of lines: 7272
Allocated lines: 7272
New no. of requested lines: 8 (in 1 blocks)
those 7272 lines are present in the table gt_but000_guidind,
but the actual table (" gt_but000_buf") which is giving the dump has 0 lines :
SAPLZEXTRACT0003
LZEXTRACT0003U01 686
I_CANAL 04
33
04
T_ZR006 Table IT_44732325[0x69]
T_DETAIL Table IT_44732386[904x567]
T_RET[] Table IT_20047937[0x548]
SYST-REPID SAPLZEXTRACT0003
5454545554453333222222222222222222222222
310CA58421340003000000000000000000000000
%_DUMMY$$
2222
0000
SY-REPID SAPLZEXTRACT0003
5454545554453333222222222222222222222222
310CA58421340003000000000000000000000000
E_ZR006-VKONT 4N-BK7193-01
342443333233
4ED2B7193D01
E_FKK-GPART 4-BB8101
3244333322
4D22810100
E_DETAIL-JJTITULAIRE 14
33
14
T_TEL Table IT_44732350[0x114]
T_MAIL Table IT_44732348[0x272] -
Help needed on abap heap area parameters
Hi Gurus ,
I need your help in regards with abap heap area parameters , we are facing a lot of system no roll memory issues on one of our instance.
As for my understanding :
1)abap/heap_area_dialog : heap memory limit for dialog process.
2).abap/heap_area_nondialog: heap memory limit for non-dialog process.
3).abap/heap_area_total : what this implies ?
In my production instance the parameters are as follows :
Actuals
abap/heap_area_dialog -
2GB (Recommended : 2GB for an application server with max 50 users )
abap/heap_area_nondialog:-- 2GB (Recommended : 2GB or an application server with max 50 users )
abap/heap_area_total --- 1GB (Recommended and default value: 2GB)
My doubt is "abap/heap_area_total of 1GB " might creating problems .
What is the recommended value for abap/heap_area_total on Solaris 10 ?
your valuable inputs required :!Hello Sandy
Have a look at this link for UNIX
http://help.sap.com/saphelp_nw04/helpdata/en/02/96257b538111d1891b0000e8322f96/content.htm
For more in memory management in below link
http://help.sap.com/saphelp_nw04/helpdata/en/02/96253c538111d1891b0000e8322f96/frameset.htm
Regards
Vivek -
How to adject ABAP HEAP SIZE???
Hi,
How do I adjust ABAP Heap size..??
any step by step or note?
Thanks,Hi Afi,
you can get some information here:
http://help.sap.com/saphelp_nw04s/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/frameset.htm
There you will also find the parameters:
abap/heap_area_dia: Heap Memory Limit for Dialog Work Processes
abap/heap_area_nondia: Heap Memory Limit for Non-Dialog Work
abap/heap_area_total: Total Quota for Heap Memory
and recommendations how to configure them.
Have a look and award points if useful.
Rgds,
Loukas -
TSV_TNEW_PAGE_ALLOC_FAILED,Parameter wrong set these are abap dump
We are using windows 2003 server with 32 bit database oracle (500 GB)
all most of the jobs terminated with TSV_TNEW_page_ALLOC_faild ,paramerter rorg sert etc
please advise my sap parameter is ok or some change for the best utlization of the tehe memeory.
what is ths valuse of the phys_memsize
my parameter detils are the following..
rsdb/reco_add_error_codes |-12152 , -12560 , -3114 , -3113 |
abap/heap_area_dia
2000000000
nobuf/max_attempts
1200
rdisp/appc_ca_blk_no
1000
rdisp/wp_ca_blk_no
2050
ztta/roll_area
15000000
rdisp/PG_MAXFS
200000
gw/netstat_once
0
abap/heap_area_nondia
2000000000
rdisp/rfc_min_wait_dia_wp
5
enque/table_size
10000
gw/max_sys
1500
gw/max_overflow_size
25000000
rdisp/max_comm_entries
2000
rdisp/tm_max_no
2000
gw/max_conn
2000
rsdb/obj/max_objects
20000
rsdb/obj/buffersize
40000
sap/bufdir_entries
10000
zcsa/presentation_buffer_area
20000000
zcsa/db_max_buftab
10000
zcsa/table_buffer_area
100000000
rsdb/cua/buffersize
10000
rtbb/buffer_length
60000
rsdb/ntab/irbdsize
8000
rsdb/ntab/ftabsize
60000
rsdb/ntab/entrycount
30000
login/system_client
508
abap/buffersize
800500
rdisp/max_wprun_time
3000
SAPSYSTEMNAME
PRD
INSTANCE_NAME
DVEBMGS51
SAPSYSTEM
51
rdisp/wp_no_dia
10
rdisp/wp_no_btc
4
rdisp/wp_no_vb
4
rdisp/wp_no_vb2
1
rdisp/wp_no_enq
1
rdisp/wp_no_spo
1
SAPGLOBALHOST
PRDSVR
PHYS_MEMSIZE
2458
advans thanks
with best regards
venkat
|read SAP note 88416.
set PHYS_MEMSIZE to 2700
delete all these parameters from instance and default profiles
restart SAP and try again:
em/initial_size_MB
[PM]
[PM]
Mbyte
--- em/max_size_MB
--- 20000
--- 100000
Mbyte
em/address_space_MB
512
4096
Mbyte
ztta/roll_first
1
1
Byte
--- ztta/roll_area
--- 2000000
--- 3000000
Byte
ztta/roll_extension
2000000000
2000000000
Byte
abap/heap_area_dia
2000000000
2000000000
Byte
abap/heap_area_nondia
2000000000
0
Byte
abap/heap_area_total
2000000000
[PM]*1048576
Byte
- rdisp/ROLL_MAXFS
[BE] * 100
[BE] * 100
8KB Block
--- rdisp/ROLL_SHM
[BE] * 100
[BE] * 100
8KB Block
--- rdisp/PG_MAXFS
--- 32768
--- 32768
8KB Block
rdisp/PG_SHM
[BE] * 50
[BE] * 50
8KB Block
thwen also check if it`s always the same program that fails. if it is aZ PROGRAM, ask your programmer to use less Internal memory.
obviously, the long term solution is 64-bit. -
Memory Dump :FBL5N No roll storage space of length 1753104 available for internal storage.
Dear Friends,
I am getting below error during T-Code FBL3N Report. No roll storage space of length 1753104 available for internal storage.
Our Server' RAM size is 24 GB,and existing parameters are as below
ztta/roll_area: 6500000
ztta/roll_extension:2000683008
abap/heap_area_total:2000683008
abap/heap_area_dia: 5000000000
abap/heap_area_nondia: 2000683008
em/initial_size_MB: 4092
Please suggest Parameter to be change.
Details Dump log ST22
Runtime Errors TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Date and Time 04.03.2014 10:18:48
|Short Text |
| No roll storage space of length 1753104 available for internal storage. |
|What happened? |
| Each transaction requires some main memory space to process |
| application data. If the operating system cannot provide any more |
| space, the transaction is terminated. |
|What can you do? |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
|Error analysis |
| The internal table "\CLASS=ZCL_IM__GTA_TAX_CODE\METHOD=IF_EX_FI_ITEMS_CH_DATA~C |
| HANGE_ITEMS\DATA=GT_BSIK" could not be enlarged further. |
| |
| Memory location: "Session memory" |
| |
| You attempted to extend the data structure for the management of the |
| memory blocks for table "\CLASS=ZCL_IM__GTA_TAX_CODE\METHOD=IF_EX_FI_ITEMS_CH_D |
| ATA~CHANGE_ITEMS\DATA=GT_BSIK". However, the 1753104 bytes required for |
| this were no longer available in the specified memory area. |
| |
| The amount of memory requested is no longer available. |
|How to correct the error |
| |
| Try to decide by analysis whether this request is |
| reasonable or whether there is a program error. You should pay |
| particular attention to the internal table entries listed below. |
| |
| |
| |
| |
| |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TSV_TNEW_BLOCKS_NO_ROLL_MEMORY" " " |
| "ZCL_IM__GTA_TAX_CODE==========CP" or "ZCL_IM__GTA_TAX_CODE==========CM001" |
| "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|System environment |
| SAP-Release 700 |
| |
| Application server... "NEWPRD1" |
| Network address...... "10.0.0.1" |
| Operating system..... "Windows NT" |
| Release.............. "6.0" |
| Hardware type........ "16x AMD64 Level" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 19 |
| Shortdump setting.... "full" |
| |
| Database server... "NEWPRD1" |
| Database type..... "ORACLE" |
| Database name..... "PRD" |
| Database user ID.. "SAPSR3" |
| |
| Terminal................. " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 700 |
| created (date)... "Sep 17 2012 22:56:00" |
| create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00" |
| Database version. "OCI_10201_SHARE (10.2.0.4.0) " |
| |
| Patch level. 353 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 700 |
| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
| NT 6.0, Windows NT 6.1, Windows NT 6.2" |
| |
| Memory consumption |
| Roll.... 16192 |
| EM...... 1826770240 |
| Heap.... 0 |
| Page.... 40960 |
| MM Used. 1815573536 |
| MM Free. 2717408 |
|User and Transaction |
| |
| Client.............. 500 |
| User................ 1651 |
| Language key........ "E" |
| Transaction......... " " |
| Transactions ID..... "ED4EA3E3AB0AF11DA318E61F131BC713" |
| |
| Program............. "ZCL_IM__GTA_TAX_CODE==========CP" |
| Screen.............. "SAPMSSY0 1000" |
| Screen line......... 6 |
|Information on where terminated |
| Termination occurred in the ABAP program "ZCL_IM__GTA_TAX_CODE==========CP" - |
| in "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS". |
| The main program was "RFITEMGL ". |
| |
| In the source code you have the termination point in line 64 |
| of the (Include) program "ZCL_IM__GTA_TAX_CODE==========CM001". |
| The program "ZCL_IM__GTA_TAX_CODE==========CP" was started as a background job. |
| Job Name....... "RFITEMGL" |
| Job Initiator.. "BASIS" |
| Job Number..... 09115400 |
|Source Code Extract |
|Line |SourceCde |
| 34| MANDT TYPE BSEG-MANDT, |
| 35| BUKRS TYPE BSEG-BUKRS, |
| 36| BELNR TYPE BSEG-BELNR, |
| 37| GJAHR TYPE BSEG-GJAHR, |
| 38| BUZEI TYPE BSEG-BUZEI, |
| 39| QSSKZ TYPE BSEG-QSSKZ, |
| 40| KTOSL TYPE BSEG-KTOSL, |
| 41| HKONT TYPE BSEG-HKONT, |
| 42| END OF TY_BSEG, |
| 43| |
| 44| BEGIN OF TY_FINAL, |
| 45| BUKRS TYPE BSEG-BUKRS, |
| 46| BELNR TYPE BSEG-BELNR, |
| 47| GJAHR TYPE BSEG-GJAHR, |
| 48| END OF TY_FINAL. |
| 49| |
| 50| DATA: CW_ITEMS TYPE RFPOSXEXT, |
| 51| GT_BSIK TYPE STANDARD TABLE OF TY_BSIK, |
| 52| GW_BSIK TYPE TY_BSIK, |
| 53| GT_BSAK TYPE STANDARD TABLE OF TY_BSAK, |
| 54| GW_BSAK TYPE TY_BSAK, |
| 55| GT_BSEG TYPE STANDARD TABLE OF TY_BSEG, |
| 56| GW_BSEG TYPE TY_BSEG, &nbsap basis wrote:
|Information on where terminated |
| Termination occurred in the ABAP program "ZCL_IM__GTA_TAX_CODE==========CP" - |
| in "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS". |
| The main program was "RFITEMGL ". |
| |
| In the source code you have the termination point in line 64 |
| of the (Include) program "ZCL_IM__GTA_TAX_CODE==========CM001". |
| The program "ZCL_IM__GTA_TAX_CODE==========CP" was started as a background job. |
| Job Name....... "RFITEMGL" |
| Job Initiator.. "BASIS" |
| Job Number..... 09115400 |
First of all try to optimize code. -
When running a report in RRMX in BI 7.
Hello All,
When I try to run a report in RRMX I get a Runtime error. Please find the ABAP Dump Analysis from ST22.
Runtime Errors SYSTEM_NO_TASK_STORAGE
Date and Time 13.05.2008 16:17:08
Short dump has not been completely stored (too big)
Short text
Unable to fulfil request for 5855472 bytes of storage space.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
A new storage area of 5855472 bytes was requested
(storage calss TASK).
All the available space has been used up.
Possible reason: Either the volume of data to be processed is too large
or the available swap space is too small.
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server olbiwprd_BWP_00 on host olbiwprd (wp 1)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1880
The error reported by the operating system is:
Error number..... " "
Error text....... " "
How to correct the error
Restrict volume of data or increase swap space.
Try to decide by analysis whether this request is
reasonable or whether there is a program error. You should pay
particular attention to the internal table entries listed below.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SYSTEM_NO_TASK_STORAGE" " "
"CL_RSR_NET_GRID===============CP" or "CL_RSR_NET_GRID===============CM00A"
"MERGE_RANGES"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "olbiwprd"
Network address...... "10.10.10.7"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "OLBIWPRD"
Database type..... "MSSQL"
Database name..... "BWP"
Database user ID.. "bwp"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 30 2006 00:29:20"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 83
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 1709536
EM...... 419168344
Heap.... 500866656
Page.... 16384
MM Used. 910107048
MM Free. 10780592
User and Transaction
Client.............. 400
User................ "SETTM"
Language Key........ "E"
Transaction......... " "
Program............. "CL_RSR_NET_GRID===============CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "BWP"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "asynchron without reply and non-transactional (emode 0,
imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 400
User................ "SETTM"
Transaction......... "RRMX"
Call Program........."SAPLRSAH"
Function Module..... "RSAH_BIW_CALL_SERVER"
Call Destination.... "NONE"
Source Server....... "olbiwprd_BWP_00"
Source IP Address... "10.10.10.7"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases P_T_RANGE_INT
Table IT_2188559[365967x160]
DATA=P_T_RANGE_INT
Table reference: 2392
TABH+ 0(20) = 08F3DE520000000000000000580900000F652100
TABH+ 20(20) = 8F950500A0000000FFFFFFFF04140500500C0000
TABH+ 40( 8) = 10000000C1248001
store = 0x08F3DE52
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 2392 (0x58090000)
label = 2188559 (0x0F652100)
fill = 365967 (0x8F950500)
leng = 160 (0xA0000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000051
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xA88AF34D
pgHook = 0xA0040539
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 92815 (0x8F6A0100)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 376816 (0xF0BF0500)
lineAlloc = 366000 (0xB0950500)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_TAB_LINES
365967
8900
F550
RRK_C_CHAVL-REST_HRY
REST_H
545554222222222222222222222222222222222222222222222222222222
2534F8000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
<L_S_WA1>
SY-REPID
CL_RSR_NET_GRID===============CP
4455555445545443333333333333334522222222
3CF232FE54F7294DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SYST-REPID
CL_RSR_NET_GRID===============CP
4455555445545443333333333333334522222222
3CF232FE54F7294DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SPACE
2
0
0
0
<L_S_WA1>-LEVEL
L_S_WA2-LEVEL
0
0000
0000
<L_S_WA1>-FORMAT
L_S_WA2-FORMAT
22222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000
<L_S_WA1>-X1
L_S_WA2-X1
0
0000
0000
<L_S_WA1>-X2
L_S_WA2-X2
0
0000
0000
<L_S_WA1>-Y2
L_S_WA2-Y1
0
0000
0000
No. 13 Ty. METHOD
Name CL_RSR_NET_GRID=>FILL_RANGES
I_AREA_OPTIMIZATION
X
5
8
0
0
ME->P_NOSTYLES
2
0
0
0
RS_C_FALSE
2
0
0
0
ME
0000F000
60009100
RS_C_TRUE
X
5
8
0
0
ME->N_T_RANGES
Table[initial]
ME->P_T_RANGE_INT
Table IT_2188559[365967x160]
L_S_RANGES_FROM
0.0.0.0.0.0.0.1. ####
00000000222222222222222222222222222222222222222222222222222222222222222222220000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
RRX1_C_AXIS-COLUMNS
X
5
8
0
0
L_S_RANGES_TO
0000000022222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
ME->N_EXTRA_COLUMNS
10
0000
A000
ME->N_EXTRA_ROWS
1
0000
1000
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 12 Ty. METHOD
Name CL_RSR_NET_GRID=>FILL_GRID
I_FROM_ROW
0
0000
0000
I_TO_ROW
0
0000
0000
I_FROM_COLUMN
0
0000
0000
I_TO_COLUMN
0
0000
0000
I_WITH_CAPTION_ROWS
X
5
8
0
0
I_WITH_CAPTION_COLUMNS
X
5
8
0
0
I_WITH_DATA
X
5
8
0
0
I_FORMATTED_VALUES
X
5
8
0
0
I_MAX_COLS
65535
FF00
FF00
RRFMT_C_VALEXCP-NORMAL
X
5
8
0
0
SY-SUBRC
0
0000
0000
ME->P_NOSTYLES
2
0
0
0
ME
0000F000
60009100
L_AREA_OPTIMIZATION
X
5
8
0
0
No. 11 Ty. METHOD
Name CL_RSR_XLS_VIEW=>SERIALIZE_RESULT
I_R_PARAMETER
A0005000
A0005200
E_SX_RESULT
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1. #######
000000FF00FF00FF00FF200000FF
000000FF00FF00FF00FF000000FF
000000FF00FF00FF00FF000000FF
000000FF00FF00FF00FF000000FF
%_DUMMY$$
2222
0000
0000
0000
L_R_GRID
0000F000
60009100
SPACE
2
0
0
0
ME
60009000
1000E000
L_S_SESSION_SETTINGS-MASK_DATE
DD/MM/YYYY
44244255552222222222
44FDDF99990000000000
00000000000000000000
00000000000000000000
L_DATE_MASK
DD/MM/YYYY
4424425555
44FDDF9999
0000000000
0000000000
L_S_SESSION_SETTINGS
DD/MM/YYYY ### #########
2442442555522222222222222222222222222222222000222000000000222222222222222222222222222222222222
044FDDF999900000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST
####閏#################################¤#########<###########################'#µ#########XC####
00008000000000000000000000000000000000A000000000300000000000000000000000000020B000100000540000
1000F5D00000000000000010100010000000004000000000C000000000000000000000000000705000E00000830200
0000900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
RS_C_TRUE
X
5
8
0
0
RRX1_C_MAX_ROW
65535
FF00
FF00
%_SPACE
2
0
0
0
ME->N_SX_RESULT+4(4)
0
0000
0000
L_R_GRID->N_MAX_X
23
1000
7000
ME->N_SX_RESULT-MAX_Y
0
0000
0000
L_R_GRID->N_MAX_Y
36516
A800
4E00
ME->N_SX_RESULT+16(8)
Table IT_2188115[0x152]
DATA=N_SX_RESULT-RANGES
Table reference: 75887
TABH+ 0(20) = 0000000000000000000000006F28010053632100
TABH+ 20(20) = 0000000098000000FFFFFFFF04A10100D0070000
TABH+ 40( 8) = 10000000C1248401
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 75887 (0x6F280100)
label = 2188115 (0x53632100)
fill = 0 (0x00000000)
leng = 152 (0x98000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000027
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_R_GRID->N_T_RANGES
Table[initial]
ME->N_SX_RESULT+8(8)
Table IT_2188116[0x692]
DATA=N_SX_RESULT-GRID
Table reference: 75888
TABH+ 0(20) = 0000000000000000000000007028010054632100
TABH+ 20(20) = 00000000B4020000FFFFFFFF04A1010010070000
TABH+ 40( 8) = 10000000C1308401
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 75888 (0x70280100)
label = 2188116 (0x54632100)
fill = 0 (0x00000000)
leng = 692 (0xB4020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000023
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_R_GRID->N_T_GRID
Table IT_2188558[839877x692]
DATA=N_T_GRID
Table reference: 2409
TABH+ 0(20) = 08F35E520000000000000000690900000E652100
TABH+ 20(20) = C5D00C00B4020000FFFFFFFF04140500E0060000
TABH+ 40( 8) = 10000000C1308001
store = 0x08F35E52
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 2409 (0x69090000)
label = 2188558 (0x0E652100)
fill = 839877 (0xC5D00C00)
leng = 692 (0xB4020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000022
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xF8C5BB3C
pgHook = 0x70C46839
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 92814 (0x8E6A0100)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 851968 (0x00000D00)
lineAlloc = 839888 (0xD0D00C00)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ME->N_SX_RESULT+32(8)
Table[initial]
L_R_GRID->N_T_SYMBOLS
Table[initial]
ME->N_SX_RESULT+24(8)
Table[initial]
L_R_GRID->N_T_TEXT
Table[initial]
SY-REPID
CL_RSR_XLS_VIEW===============CP
4455555545554453333333333333334522222222
3CF232F8C3F6957DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->N_SX_RESULT+40(2)
2
0
0
0
L_R_GRID->N_EDITABLE
2
0
0
0
SYST-REPID
CL_RSR_XLS_VIEW===============CP
4455555545554453333333333333334522222222
3CF232F8C3F6957DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->N_R_REQUEST
5000A000
E0001000
RSBBS_C_RETURN_TYPE-INTERNAL
I
4
9
0
0
ME->N_SX_RESULT+48(8)
Table IT_2188117[0x490]
DATA=N_SX_RESULT-TXT_ELEMENTS
Table reference: 75889
TABH+ 0(20) = 0000000000000000000000007128010055632100
TABH+ 20(20) = 00000000EA010000FFFFFFFF04A4010060230000
TABH+ 40( 8) = 10000000C1248401
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 75889 (0x71280100)
label = 2188117 (0x55632100)
fill = 0 (0x00000000)
leng = 490 (0xEA010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000174
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
No. 10 Ty. METHOD
Name CL_RSR_XLS_VIEW=>SERIALIZE
I_R_PARAMETER
A0005000
A0005200
E_SX_DATAPROVIDER
DATA_PROVIDER_1 ##########################################0000##0 00000000 ###
4454555454445532222222222222220000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF3333003223333333322000
4141F02F69452F10000000000000000000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF0000000000000000000000
0000000000000000000000000000000000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF0000000000000000000000
0000000000000000000000000000000000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF0000000000000000000000
L_DO_NOT_READ_DATA
2
0
0
0
ME->N_R_REQUEST
5000A000
E0001000
ME->N_R_REQUEST->N_SX_REQUEST
Ð#######Ë###Ï###Ä###Ì#######Î###Í###Ê###########Ô#फ#####
D00000F0C010C010C030C01000F0C010C010C01000FF00FFD02000FF
00F0B040B040F00040B0C030D020E010D020A05000FF00FF40B000FF
000000000000000000000000000000000000000000FF00FF000000FF
008000700080008000900080008000800080008000FF00FF009000FF
RS_C_FALSE
2
0
0
0
ME
60009000
1000E000
E_SX_DATAPROVIDER-RESULT
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1. #######
000000FF00FF00FF00FF200000FF
000000FF00FF00FF00FF000000FF
000000FF00FF00FF00FF000000FF
000000FF00FF00FF00FF000000FF
L_CNT
109
6000
D000
No. 9 Ty. METHOD
Name CL_RSR_XLS_WORKBOOK=>SERIALIZE
I_R_PARAMETER
A0005000
A0005200
E_SX_WORKBOOK
0.0.0.1. X####।#########X###############
00002500906010C000FF500000FF00FF00FF
10000800B04000F000FF800000FF00FF00FF
000000000000000000FF000000FF00FF00FF
000000000090009000FF000000FF00FF00FF
%_SPACE
2
0
0
0
SY
####閏#################################¤#########<###########################'#µ#########XC####
00008000000000000000000000000000000000A000000000300000000000000000000000000020B000100000540000
1000F5D00000000000000010100010000000004000000000C000000000000000000000000000705000E00000830200
0000900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
RSSTA_C_HANDLETP-BEX_DP
DP
4522
4000
0000
0000
L_EVENT_CNT
108
6000
C000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
CL_RSR_XLS_WORKBOOK===========CP
4455555545554544444333333333334522222222
3CF232F8C3F7F2B2FFBDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_VIASELSCR
0
4
L_SX_DP-NAME
DATA_PROVIDER_1
445455545444553222222222222222
4141F02F69452F1000000000000000
000000000000000000000000000000
000000000000000000000000000000
L_DO_NOT_READ_DATA
2
0
0
0
RS_C_FALSE
2
0
0
0
L_FETCH_DATA
X
5
8
0
0
RS_C_TRUE
X
5
8
0
0
SY-XFORM
RSR_NET_INTERFACE
555544554454544442222222222222
232FE54F9E45261350000000000000
000000000000000000000000000000
000000000000000000000000000000
L_SX_DP-REF
60009000
1000E000
SY-REPID
CL_RSR_XLS_WORKBOOK===========CP
4455555545554544444333333333334522222222
3CF232F8C3F7F2B2FFBDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
L_SX_DATAPROVIDER
DATA_PROVIDER_1 ##########################################0000##0 00000000 ###
4454555454445532222222222222220000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF3333003223333333322000
4141F02F69452F10000000000000000000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF0000000000000000000000
0000000000000000000000000000000000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF0000000000000000000000
0000000000000000000000000000000000FF00FF00FF00FF00FF00FF00FF00FF00FF00FF0000000000000000000000
E_SX_WORKBOOK-T_DATAPROVIDER
Table[initial]
ME->N_R_MESSAGES
60009000
5000A000
E_SX_WORKBOOK-T_MESSAGES
Table[initial]
SYST
####閏#################################¤#########<###########################'#µ#########XC####
00008000000000000000000000000000000000A000000000300000000000000000000000000020B000100000540000
1000F5D00000000000000010100010000000004000000000C000000000000000000000000000705000E00000830200
0000900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
No. 8 Ty. FUNCTION
Name RSR_NET_INTERFACE_II
I_R_PARAMETER
A0005000
A0005200
E_OUTPUT
E_T_MIME[]
Table IT_2188371[1x2944]
FUNCTION-POOL=RSR_XLS_RFCFORM=RSR_NET_INTERFACEDATA=%_%_E_T_MIME
Table reference: 776
TABH+ 0(20) = 0820EA41D06A4A26000000000803000053642100
TABH+ 20(20) = 01000000800B0000FFFFFFFF04120000F0050000
TABH+ 40( 8) = 04000000C1308001
store = 0x0820EA41
ext1 = 0xD06A4A26
shmId = 0 (0x00000000)
id = 776 (0x08030000)
label = 2188371 (0x53642100)
fill = 1 (0x01000000)
leng = 2944 (0x800B0000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000017
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x5046733D
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 92777 (0x696A0100)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x08F39E54
>>>>> 2nd level extension part <<<<<
tabhBack = 0xE85E713D
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
L_CMD_VAL
SY-REPID
SAPLRSR_XLS_RFC
5454555554555442222222222222222222222222
310C232F8C3F2630000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
C_PARAMETER_THEMEDEF
THEMES
544445
485D53
000000
000000
SY
####閏#################################¤#########<###########################'#µ#########XC####
00008000000000000000000000000000000000A000000000300000000000000000000000000020B000100000540000
1000F5D00000000000000010100010000000004000000000C000000000000000000000000000705000E00000830200
0000900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RS_C_TRUE
X
5
8
0
0
L_PAGENO
0001
3333
0001
0000
0000
L_RETURN_CODE
0
0000
0000
L_R_WORKBOOK
60009000
80007000
%_DUMMY$$
2222
0000
0000
0000
%_VIASELSCR
0
4
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_SX_WORKBOOK
0.0.0.1. X####।#########X###############
00002500906010C000FF500000FF00FF00FF
10000800B04000F000FF800000FF00FF00FF
000000000000000000FF000000FF00FF00FF
000000000090009000FF000000FF00FF00FF
C_CMD_DEFAULT_WORKBOOK
DEFAULT_WORKBOOK
4444545554544444
45615C4F7F2B2FFB
0000000000000000
0000000000000000
C_CMD_GET_THEME_CATALOG
GET_THEME_CATALOG
44555444454454444
754F485D5F3141CF7
00000000000000000
00000000000000000
No. 7 Ty. FUNCTION
Name RSR_NET_INTERFACE
I_INPUT
<?xml version="1.0" encoding="utf-16"?>##<ArrayOfBExSer_ParameterValue xmlns:xsi="http://www.w
3376627677666323232266666666327762332330034776746447567556766676756676276667377632677732277727
CF8DC065239FED21E0205E3F49E7D2546D162FEDAC12219F6258352F0121D545261C5508DCE3A839D28440AFF777E7
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_STATISTIC_STEP_CLOSE
2
0
0
0
E_OUTPUT
E_SUBRC
0
0000
0000
E_T_MESSAGE[]
Table IT_2188370[0x892]
FUNCTION-POOL=RSR_XLS_RFCFORM=RSR_NET_INTERFACEDATA=%_%_E_T_MESSAGE
Table reference: 2339
TABH+ 0(20) = 0000000078B72540000000002309000052642100
TABH+ 20(20) = 000000007C030000FFFFFFFF04120000E0060000
TABH+ 40( 8) = 10000000C1248001
store = 0x00000000
ext1 = 0x78B72540
shmId = 0 (0x00000000)
id = 2339 (0x23090000)
label = 2188370 (0x52642100)
fill = 0 (0x00000000)
leng = 892 (0x7C030000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000022
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x08F31E54
>>>>> 2nd level extension part <<<<<
tabhBack = 0xD053713D
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_funcHi,
It is a memory or buffer related problem. Contact your BASIS.
Looks like there is a shortage of space. Analyse the dump in ST22 and look for its proposals.
OSS note 965351 might be applicable (if you are on 640/ unix).
regards,
NR -
Friends,
Please kindly help me to analyse this dump.
In BI end routine select * query has been written to fetch values from active dso . They are using non primary key in the where condition.
More than 2 crore 20 million records were avaialble in that DSo for that condtion. While executing this query its going to dump.
If i move ahead with Open cursor set Hold will this query work fine and using open cursor set hold can i fetch 2 crore 20 million records.
In dump its shwoing to check the parameters : ztta/roll_area ,ztta/roll_extension and abap/heap_area_total . Even i checked those parametrs in RZ11. The curent val is sufficient.
Please kindly advice me for this dump and will open cursor set hold avoid the dump for 2 crore 20 million records.
Thanks
Edited by: Suhas Saha on Sep 29, 2011 1:06 PMI am not completely convinced: the difference depends on the task which has to be done with the records of a package.
If the records are processed and the result must be written to the database into another table, then it will be necessary to COMMIT the changes, otherwise the 20.000.000 records will cause an overflow in the redo-logs of the database.
=> Only the OPEN CURSOR WITH HOLD will survive the DB-Commit.
The SELECT ... PACKAGE SIZE is simpler and can be used, if the result is further processed and reduced in size, which makes it possible to keep all data in memory (no intermediate DB-COMMITs are necessary) .
I would assume that case is the less frequent use case.
Siegfried -
Short dump due to performance issue
Hi all,
I am facing performance issue in my sandbox. Below is the content of short dump.
Short text
Unable to fulfil request for 805418 bytes of memory space.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Pls help me to resolve this issue
Regards,
Kalyani
Edited by: kalyani usa on Jan 9, 2008 9:04 PMHi Rob Burbank,
I am pasting the transaction I found in the dump
Transaction......... "SESSION_MANAGER "
Transactions ID..... "4783E5B027A73C1EE10000000A200A17"
Program............. "SAPMSYST"
Screen.............. "SAPMSYST 0500"
Screen line......... 16
Also i am pasting the screenshot of ST02
Nametab (NTAB) 0
Table definition 99,22 6.799 3.591 62,97 20.000 12.591 62,96 0 8.761
Field definition 99,06 31.563 345 1,15 20.000 13.305 66,53 244 7.420
Short NTAB 99,22 3.625 2.590 86,33 5.000 3.586 71,72 0 1.414
Initial records 52,50 6.625 3.408 56,80 5.000 249 4,98 817 5.568
0
program 99,58 300.000 1.212 0,42 75.000 67.561 90,08 7.939 46.575
CUA 99,08 3.000 211 8,84 1.500 1.375 91,67 23.050 846
Screen 99,46 4.297 1.842 45,00 2.000 1.816 90,80 81 963
Calendar 100,00 488 401 85,14 200 111 55,50 0 89
OTR 100,00 4.096 3.281 100,00 2.000 2.000 100,00 0
0
Tables 0
Generic Key 99,69 29.297 2.739 9,87 5.000 177 3,54 57 56.694
Single record 89,24 10.000 63 0,64 500 468 93,60 241 227.134
0
Export/import 76,46 50.000 40.980 83,32 2.000 2.676
Exp./ Imp. SHM 97,82 4.096 3.094 94,27 2.000 1.999 99,95 0
SAP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area 0,16 432 18.672 131.072 131.072 IDs 98,11
Page area 0,19 496 187.616 65.536 196.608 Statement 95,00
Extended memory 9,89 151.552 1.531.904 1.531.904 0 0,00
Heap memory 0 0 1.953.045 0
0,00
Regards,
Kalyani -
SYSTEM_NO_ROLL dump when trying to precalculate data with RSRD_BROADCAST_PR
Dear all,
At my present customer we are facing a problem when doing a precalculate of data with RSRD_BROADCAST_PROCESSOR.
The dump message is:
Runtime Errors SYSTEM_NO_ROLL
Date and Time 20.08.2008 3:20:54
Short text
Unable to fulfil request for 1082885568 bytes of memory space.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
More main memory area was requested.
However, all the available space has been used up.
Possible reasons:
#NAAM?
#NAAM?
#NAAM?
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server sapbwp00_PB1_00 on host sapbwp00 (wp 40)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1881
The error reported by the operating system is:
Error number..... " "
Error text....... " "
How to correct the error
Try to decide by analysis whether this request is
reasonable or whether there is a program error. You should pay
particular attention to the internal table entries listed below.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
SYSTEM_NO_ROLL " "
CL_ABAP_CONV_OUT_CE===========CP or "CL_ABAP_CONV_OUT_CE===========CM003"
WRITE
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "sapbwp00"
Network address...... "10.91.1.85"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 40
Shortdump setting.... "full"
Database server... "csu123"
Database type..... "ORACLE"
Database name..... "PB1"
Database user ID.. "SAPPB1"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jan 23 2008 23:12:46"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 144
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 8782704
EM...... 5091782384
Heap.... 2968385120
Page.... 49152
MM Used. 6350628336
MM Free. 1717574096
User and Transaction
Client.............. 400
User................ "*********"
Language key........ "N"
Transaction......... " "
Transactions ID..... "48AB1576041B51CCE10000000A5B0155"
Program............. "CL_ABAP_CONV_OUT_CE===========CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "CL_ABAP_CONV_OUT_CE===========CP" -
in "WRITE".
The main program was "RSRD_BROADCAST_PROCESSOR ".
In the source code you have the termination point in line 5
of the (Include) program "CL_ABAP_CONV_OUT_CE===========CM003".
The program "CL_ABAP_CONV_OUT_CE===========CP" was started as a background job.
Job Name....... "BIBCAST4AVN2YK4QXLZWI2MO0ZD5OD3P"
Job Initiator.. "********"
Job Number..... 02000600
Source Code Extract
Line SourceCde
1 METHOD write.
2
3 IF view IS INITIAL.
4 * Single field
>>>>> SYSTEM-CALL CONVERT ID 24
6 " EXPORTING
7 DATA data
8 ENDIAN me->endian
9 IGNORE_CERR me->ignore_cerr
10 N n
11 " IMPORTING
12 LEN len
13 " CHANGING
14 CINFO me->cinfo
15 BUFFER me->buffer.
16 ELSE.
17 * Structure
18 DATA:
19 viewstr TYPE xstring.
20 viewstr = view->get_view( ).
21
22 SYSTEM-CALL CONVERT ID 25
23 " EXPORTING
24 DATA data
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 4
SY-DBCNT 2
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Broadcasting Framework: doorgegeven instellingen uitvoeren
SY-MSGTY S
SY-MSGID RSRB1
SY-MSGNO 803
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080820
SY-UZEIT 24659
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
9 METHOD CL_ABAP_CONV_OUT_CE===========CP CL_ABAP_CONV_OUT_CE===========CM003 5
CL_ABAP_CONV_OUT_CE=>WRITE
8 METHOD CL_RSRD_UTILITIES=============CP CL_RSRD_UTILITIES=============CM006 8
CL_RSRD_UTILITIES=>CONVERT_STRING_TO_XSTRING
7 METHOD CL_RSRD_DISTRIBUTOR_MAIL======CP CL_RSRD_DISTRIBUTOR_MAIL======CM002 30
CL_RSRD_DISTRIBUTOR_MAIL=>SET_BODY
6 METHOD CL_RSRD_DISTRIBUTOR_MAIL======CP CL_RSRD_DISTRIBUTOR_MAIL======CM004 43
CL_RSRD_DISTRIBUTOR_MAIL=>IF_RSRD_F_DISTRIBUTOR_RT~DISTRIBUTE
5 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 123
CL_RSRD_SETTING=>EXECUTE_NODES
4 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 144
CL_RSRD_SETTING=>EXECUTE_NODES
3 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 144
CL_RSRD_SETTING=>EXECUTE_NODES
2 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM002 108
CL_RSRD_SETTING=>EXECUTE
1 EVENT RSRD_BROADCAST_PROCESSOR RSRD_BROADCAST_PROCESSOR 180
START-OF-SELECTION
Chosen variables
Name
Val.
No. 9 Ty. METHOD
Name CL_ABAP_CONV_OUT_CE=>WRITE
N
-1
FFFF
FFFF
DATA
MIME-Version: 1.0##Content-Type: multipart/related;## boundary="=_48AB15C6041B51CCE10000000A5B
0
0
4,44426E+93
D9D5D65239FEA01E0DA3FE45E4D4905A0D5C490124F25C1454BDA02F5E4129D2DF4812153604125133510000000152
VIEW
F0000000
F0000000
LEN
0
0
0
%_SPACE
0
0
2
0
SYST-REPID
CL_ABAP_CONV_OUT_CE===========CP
0
0
4,45445E+39
3CF1210F3FE6FF54F35DDDDDDDDDDD3000000000
%_DUMMY$$
0
0
2222
0
RSJOBINFO
00000000000000 ##
0
0
2,22222E+81
0
ME->BUFFER
ME->ENDIAN
0
0
2
0
ME->IGNORE_CERR
0
0
2
0
ME->CINFO
##41024110#Ā####################ā##¨M퇀##罿N##0000############## ### ###0000#0000#########怀### #
0000000000000000000000000000000000000D00700000000000000000000000002000000000000000000000600020
0000000000010000000000000000000010000100F00000000000000000000000000000000000000000000000000000
00333333332000000000000000000001000A4C00740033330000000000000020000000333303333002000002000000
014102411030000001000001010100081008D000FE0000000D000C000D000D00020001000000000003000003010001
SY-XFORM
CONVERSION_EXIT
0
0
4,44546E+29
3FE65239FEF5894000000000000000
VIEWSTR
ME->POSITION
0
0
0
No. 8 Ty. METHOD
Name CL_RSRD_UTILITIES=>CONVERT_STRING_TO_XSTRING
I_STRING
MIME-Version: 1.0##Content-Type: multipart/related;## boundary="=_48AB15C6041B51CCE10000000A5B
0
0
4,44426E+93
D9D5D65239FEA01E0DA3FE45E4D4905A0D5C490124F25C1454BDA02F5E4129D2DF4812153604125133510000000152
R_XSTRING
SY-REPID
CL_RSRD_UTILITIES=============CP
0
0
4,45555E+39
3CF2324F549C94953DDDDDDDDDDDDD3000000000
%_DUMMY$$
0
0
2222
0
SYST-REPID
CL_RSRD_UTILITIES=============CP
0
0
4,45555E+39
3CF2324F549C94953DDDDDDDDDDDDD3000000000
LO_CONVERT_OUT
90000006
0000002F
%_SPACE
0
0
2
0
SYST
#######################################H#########ÿ#############################T###ÿ###ฐXu#̀##
0
0,00E+00
0000000000000000000000000000000000000004000000000F000000000000000000000000000105000F0001570000
0000040800000000000002010100010000000008000000000F000000000000000000000000000604000F000085000C
No. 7 Ty. METHOD
Name CL_RSRD_DISTRIBUTOR_MAIL=>SET_BODY
SYST-REPID
CL_RSRD_DISTRIBUTOR_MAIL======CP
0
0
4,45555E+39
3CF2324F493429254F2FD19CDDDDDD3000000000
ME->O_R_PARAMETER
80000007
F0000020
ME->IF_RSRD_F_DESIGN_TIME~C_PARAMETER_TYPE_TEXT
DI_BODY
0
0
4,45445E+29
49F2F4900000000000000000000000
L_BODY
%_DUMMY$$
0
0
2222
0
ME->IF_RSRD_F_DESIGN_TIME~C_PARAMETER_TYPE_PCD_FOLDER
DI_IMPORTANCE
0
0
4,45445E+29
49F9D0F241E3500000000000000000
L_IMPORTANCE
MEDIUM
0
0
444454
D5495D
SY-REPID
CL_RSRD_DISTRIBUTOR_MAIL======CP
0
0
4,45555E+39
3CF2324F493429254F2FD19CDDDDDD3000000000
ME->O_SX_DOCUMENT+148(256)
multipart/related
0
0
6,76768E+93
D5C490124F25C145400000000000000000000000000000000000000000000000000000000000000000000000000000
ME->O_SX_DOCUMENT+440(8)
Table IT_77861199[0x296]
DATA=O_SX_DOCUMENT-T_MIMES
Table reference: 2400542&nHi,
Take help of your basis team to extend the Memory allocation for this Job
or you need to Restrict the Information that you are Broadcasting
I mean some more restrictions in the report to reduce the Data Size for brodcasting
Assigning the Points is the way to say thanks in SDN if helpful
Regards
Hari -
Job terminated in source system - Request set to red during delta load
Hi All,
There is issue with the delta load where as full load works fine and it results in below job termination with below log.
Job started
Step 001 started (program SBIE0001, variant &0000000128086, user ID ALEREMOTE1)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDITM
RLOGSYS = BWP_010
REQUNR = REQU_DA9R6Y5VOREXMP21CICMLZUZU
UPDMODE = R
LANGUAGES = *
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 0 *
abap/heap_area_total.......... 17173577728 *
abap/heaplimit................ 40000000 *
zcsa/installed_languages...... DE *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 3000000 *
ztta/roll_extension........... 2000000000 *
Object requested is currently locked by user ALEREMOTE1
Job cancelled after system exception ERROR_MESSAGE
Please help me to resolve this issue.
Thanks,
Madhu,Hello,
As per the screen shot provided below, data soruce belongs to LO, so first check in RSA7, whether it has got mark in RSA7, for which you have entries in RSA7 against the data source. If you are not able to find the data source in RSA7, then you need to set-up the update methods, based on the requirement.
1) Direct Delta
2) Queued Delta
3) Unserialised V3 Update
Once it is done, Delete the Previous Initilisation, again perform the Re-Init With Out data and now schedule the Delta Data Loads
Hope this may Help you.
Thanks
PT -
Job terminated in source system -- Request set to red
Hi Developers and supporters can you any one help me.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the
Date Time Message
13.10.2010 16:48:01 Job started
13.10.2010 16:48:01 Step 001 started (program SBIE0001, variant &0000000024579, user ID RFCUSR)
13.10.2010 16:48:01 DATASOURCE = 0ACTIVITY_ATTR
13.10.2010 16:48:01 *************************************************************************
13.10.2010 16:48:01 * Current Values for Selected Profile Parameters *
13.10.2010 16:48:01 *************************************************************************
13.10.2010 16:48:01 * abap/heap_area_nondia......... 2000683008 *
13.10.2010 16:48:01 * abap/heap_area_total.......... 2000683008 *
13.10.2010 16:48:01 * abap/heaplimit................ 40894464 *
13.10.2010 16:48:01 * zcsa/installed_languages...... 6EDGIJL *
13.10.2010 16:48:01 * zcsa/system_language.......... E *
13.10.2010 16:48:01 * ztta/max_memreq_MB............ 256 *
13.10.2010 16:48:01 * ztta/roll_area................ 6500352 *
13.10.2010 16:48:01 * ztta/roll_extension........... 2000683008 *
13.10.2010 16:48:01 *************************************************************************
13.10.2010 17:57:09 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
13.10.2010 17:57:09 Job cancelledHi SUSUSU,
The dump is related to temp table space issue.check the space for PSATEMP table.
Use tcode DB02 to check the table spaces, in the tree diaplayed on you left. try to see the % used for your ODS & FACT tablespaces. Incase the % are too high like 99% etc, get in touch with you BASIS team.
Request your basis team to increase the PSATEMP table space.
Or
Decrease the data packet size and run the info package.
to decreae the packet size -- in the IP screen menu --> schedular -->Datasource setting for sending data --> there change the parameter Maximum size of a data packet in kByte.
down you can find the area to enter the data packet size .
for ex if it is 20000 decrease it to 10000 and run the info package -
Job terminated in source system -- Request set to red,SAPSQL_SQLS_INVALID_
Hi All,
can any one help on this issue.
I run the BI statistics in production and found out the error while triggering the delta's
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Error msg : Job terminated in source system --> Request set to red
Message no. RSM078
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS = BCLNT300
REQUNR = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE = D
LANGUAGES = *
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 0 *
abap/heap_area_total.......... 2147483648 *
abap/heaplimit................ 40894464 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 3000320 *
ztta/roll_extension........... 2000683008 *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
But delta laoding for same is working in DEV...but not in prod...
Please suggest
Regards
ShwetaSwetha
finally found out the notes.
Please look into them and ask you basis to implemnt,
1161940
1106569
1145041
1146851
Please have a look and ask for implemtation in your system which are suitable for you
We also faced the same issue job termination in source system for BI Statistics
Regards#
Srini
Maybe you are looking for
-
Maverick wont download. error message. Please advise
Each time I go to download the free update, it asks for my apple ID which I input and then after a few seconds an error message pops up saying there was a problem with the download try again later. Please advise a way around this. Thanks
-
Problem in displaying decimals in ALV
Hello Everyone, I am facing problem in displaying decimals in ALV Here i want to display 1.00000- but is displaying as 1,000.00- Is there any solution by not using REPLACE and changing the user settings. Please let me know. <removed by moderator> Tha
-
Could anyone answer the following questions ? 1. Will Enterprise Manager Version 2.2 and 9.2 tune Java Stored Procedures? 2. If not, are there plans in EM 4.0 for Enterprise Manager to tuneJava Stored Procedures? cheers! Karthik
-
But other then what is stored in the cloud, I haven't any videos, movies or books stored. Any help is appreciated Thank you
-
Hi All, Please help me how to do dynamic import file path since we have multiple environment where our reports will be migrated. Thanks