Parameter ztta/roll_area

Hi,
Few months ago, we changed this parameter from 6.500.000 to 65.000.000 because we had to throw some large and heavy jobs. Then we haven't changed this parameter, do anybody know what impact can have this hight value in our SAP?.
Beste Regards

If a user logs on to the SAP System, a user context is generated with
one external and one internal session, that is, the roll memory
management allocates a management-shared memory as well as a roll area.
When you create an internal session, the roll area is preallocated up to
the size of ztta/roll_first. If you require a larger roll area, the roll
area is retrieved from the extended memory, up to a maximum of the size
of ztta/roll_extension. For any further requirements, space is requested
from the roll memory up to the upper limit (ztta/roll_area -
ztta/roll_first). This process should prevent temporary memory being
wasted at the beginning, even if it is never actually required. The
ztta/roll_area and ztta/roll_first profile parameters can be set to any
value as long as the following condition is met:
1 <= ztta/roll_first <= ztta/roll_area
Regards,
Vincent

Similar Messages

Dump while loading data from POS DM to data source

Hello experts
I'm loading data from POS DM to data source 0RT_PA_TRAN_CONTROL, when amount of data is more then 1800000 records i get dump with the message "Unable to fulfil request for 8004 bytes of memory space."
How can i divide data on small packets? or can you suggest other solution?
I already check ztta/max_memreq_MB parameter and it's set to maximum.

Check the parameter ztta/roll_area in RZ11 , changes to this parameter would affect all the datasources.
The Maximum recommended size of a datapackage is 100.000 records and If a delta load is big, then divide the package into smaller using the parameter MAXDPAKS.
check this note for more info 1292059.
Also check below notes
1102641 Consult: Dump during insert in PSA table due to incorrect values
1163359 Load methods using SMQS or SAPI-controlled to transfer to BW
1160555 Determination of maximum data packages in a delta request
Points are appreciated.

Physical Memory Upgrade [SAP, Oracle parameter changes]

Hello Guru,
Good day!
I'm not sure if I'm in the correct forum, please bare with me if I'm not.
We are actually planning to increase our Production [Physical Memory] server from its current size 15360GB including [oracle, SAP & OS] to 44GB memory. Do you have any idea how can we calculate to the most needed SAP / DB parameter should be increase after we allocate the 44GB in preparation for Go-Live. Below are details of my systems [oracle version, kernel, R/3 System, OS version, SAP parameter and DB parameter.
Reason for memory upgrade: will create two client in one system with a different number of users and different plant e.g. America / Canada
======================================================================
SAP R/3 Version: SAP 4.6C
Oracle Version: 10.2.0.4.0
OS Level: AIX 5.3
orapaa> oslevel -g
Fileset                                 Actual Level        Maintenance Level
bos.rte                                 5.3.8.0             5.3.0.0
Physical Memory
Real,MB   15360
======================================================================
kernel release               46D
kernel make variant       46D_EXT
compiled on                  AIX 1 5 0056AA8A4C00
compiled for                  64 BIT
compile time                  Aug 17 2007 10:57:49
update level                  0
patch number                  2337
source id                     0.2337
======================================================================
orapaa> prtconf
System Model: IBM,9117-MMA
Machine Serial Number: 06DDD01
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6
Processor Version: PV_6_Compat
Number Of Processors: 4
Processor Clock Speed: 4208 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 9 SWT_AMR_SADCB335_SAP_HA_PRI
Memory Size: 15360 MB
Good Memory Size: 15360 MB
Platform Firmware level: Not Available
Firmware Version: IBM,EM340_095
Console Login: enable
Auto Restart: true
Full Core: false
======================================================================
Our current used SAP parameter
Profile parameters for SAP buffers     Parameters Name               Value     Unit
Program buffer
                    abap/buffersize               850000     Kb
CUA buffer
                    rsdb/cua/buffersize               10000
Screen buffer
                    zcsa/presentation_buffer_area     20000000 Byte
Generic key table buffer
                    zcsa/table_buffer_area          100000000 Byte
Single record table buffer
                    rtbb/buffer_length               60000
Export/import buffer
                    rsdb/obj/buffersize               40000      kB
Table definition buffer
                    rsdb/ntab/entrycount          30000
Field description buffer
                    rsdb/ntab/ftabsize               60000     kB
Initial record buffer
                    rsdb/ntab/irbdsize               8000     kB
Short nametab (NTAB)
                    rsdb/ntab/sntabsize          3000     kB
Calendar buffer
                    zcsa/calendar_area          500000     Byte
Roll, extended and heap memory     EM/TOTAL_SIZE_MB          6144     MB
                    ztta/roll_area               6500000     Byte
                    ztta/roll_first               1     Byte
                    ztta/short_area               1400000     Byte
                    rdisp/ROLL_SHM               16384     8 kB
                    rdisp/PG_SHM               16384     8 kB
                    rdisp/PG_LOCAL               150     8 kB
                    em/initial_size_MB               4092     MB
                    em/blocksize_KB               4096     kB
                    em/address_space_MB          4092     MB
                    ztta/roll_extension               2000000000     Byte
                    abap/heap_area_dia          2000000000     Byte
                    abap/heap_area_nondia          2000000000     Byte
                    abap/heap_area_total          2000000000     Byte
                    abap/heaplimit               40000000     Byte
                    abap/use_paging               0
======================================================================
Oracle Parameter
Oracle Parameter Name     Value     Unit
SGA_MAX_SIZE          6192     MB
PGA_AGGREGATE_TARGET     400     MB
DB_CACHE_SIZE           0
SHARED_POOL_SIZE     960     MB
LARGE_POOL_SIZE          16     MB
JAVA_POOL_SIZE           32     MB
LOG_BUFFER          14246912
db_block_buffers          655360
Thanks and regards,
Mike

I feel the best way to get the parameters which needs to be adjusted is to go for EarlyWatch Check after increasing the Physical Memory of your SAP system, as we cannot say how and which parameters needs to be checked and changed.. as there is some dependiblity also between the parameters...
All the best !

Parameter configuration of memory management

Hi all,
I receive from SAP a Analysis Check that suggest me to modify some value parameter of Memory management.
SAP suggest me:
ztta/roll_area: 3000329(current value) ->    6500000(Recommended value)
rdisp/PG_SHM: 8192(current value) ->    16384(Recommended value)
ztta/short_area: 3200000(current value) ->   4000000(Recommended value)
My request is: Can I modify these parameters with value suggest by SAP in my environment?
Is there any documentation which explain some info?
This is the information of the productive system:
machinfo
CPU info:
12 Intel(R) Itanium 2 9000 series processors (1.6 GHz, 24 MB)
          533 MT/s bus, CPU version C2
          18 logical processors
Memory: 65339 MB (63.81 GB)
Firmware info:
   Firmware revision: 7.44
   FP SWA driver revision: 1.18
   IPMI is supported on this system.
   Invalid combination of manageability firmware has been installed on this system.
   Unable to provide accurate version information about manageability firmware
Platform info:
   Model:                  "ia64 hp superdome server SD64B"
   Machine ID number:      xxxxxx
   Machine serial number: xxxxxx
OS info:
   Nodename: hostaddress
   Release:   HP-UX B.11.31
   Version:   U (unlimited-user license)
   Machine:   ia64
   ID Number: xxxx
   vmunix releaseversion:
@(#) $Revision: vmunix:    B.11.31_LR FLAVOR=perf

Hi,
I am sure that SAP must have recommanded these values after analysing your system. So you can anytime go for these values and what is good is....if you face any problem in future with these sets of values suggested by SAP, you can anytime escalaye back to SAP.
Please do not forget to take the backup of your Instance profile before making any change. Always adjust the values for pool 10 and pool 40 othwerwise your instance may not come up.
For more details about these parameters, please refer to below link.
http://help.sap.com/saphelp_nw04/helpdata/en/02/962acd538111d1891b0000e8322f96/frameset.htm
With Regards,
Saurabh

Can rdisp/max_alt_mode profile parameter cause memory problem?

After we increased the parameter to 8 from the default 6 because of the customer asking, we need to reset it to the default and restart the SAP.
We go a lot of error :
(u201EInsufficient Main Memoryu201D; "SPOOL_NO_CONVERSION"; Not enough ROLLR memory for STSOO block ) and a lot of update error.
These problems were comming up at the high level usage time. Now we use the default 6 max sessions but they still would like to increase it. Can anyone give an advice or have an experiance about this problem?
How should i refuse their claim? Or is there anyhitng else what should be set too with max_alt_mode parameter.
It is sapbasis 620 sp level 54.
Thank you very much.

Hi,
What is the value of ztta/roll_area parameter ? Is your existing roll_area is enough to handle multiple logon sessions of the user ?
I have opened the parameter description and found the following.
Parameter : rdisp/max_alt_modes
Short description: Maximum number of external sessions
Parameter description :
You can use this parameter to restrict the maximum number of external sessions a user is allowed to open in one logon.
You should only change this if the circumstances require it (for example, if there are too many roll areas, or the dialog load is too high).
Note that in certain situations the system may create new, hidden sessions automatically (for example, for frontend spooling).
You can change the parameter dynamically. The changes take effect logons that occur after the parameter change.
Caution:
Up to and including Web AS 6.10, SAP GUI can display a maximum of
6 external sessions. If you want to set the parameter to a higher
value, you require a SAP GUI of release Web AS 6.20 or higher.
You should only change this parameter if the circumstances require it (for example, if there are too many roll areas, or the dialog load is too high)
Regards,
Bhavik G. Shroff

Parameter changes make system stall/unresposive

Could a slight increase in either parameter create a huge backlash in the system:
1. ztta/roll_area or
2. abap/heap_area_total ??
I've researched each and understand what they do, but still want to ask if this could create issues. I reviewed response times for the day and compared it to passed days to find them quite similiar, but we still ran into an issue with 'slowness' all day. The dialog processes filled up and it hour glassed for a good minute. Then it would react like the bottleneck cleared and everything would go back to 'normal' for a bit. This happened pretty much all day today. The 2 parameters were changed to fix an ABAP dump we received daily.
Thanks for the help,
Ryan

We are running on OS400 V6R1 OS, the LPAR has roughly 200GBs of memory.
I changed
ztta/roll_area went from 5000000 to 7500000 and
abap/heap_area_total went from 2000000000 to 3500000000.
ST02 is showing:
Date + Time of Snapshot: 09/01/2010 09:25:26 Startup: 08/28/2010 18:45:10
Roll memory Dialog session kB 7,324
 Nondialog sess. kB 7,324
 Available kB 524,288
 in shared memory kB 524,288
 on disk kB 0
 Used kB 280,690
 Maximum used kB 338,416
Paging memory Session buffer kB 1,200
 Available kB 2,000,000
 in shared memory kB 1,048,576
 on disk kB 951,424
 Used kB 387,407
 Maximum used kB 569,304
Extended memory Dialog session kB 1,953,125
 Nondialog sess. kB 1,953,125
 Available kB 46,133,248
 Used kB 31,203,328
 Maximum used kB 39,948,288
Heap memory Dialog session kB 1,953,125
 Nondialog sess. kB 1,953,125
 Used kB 0
 Maximum used kB 3,417,949
The ABAP dump i was referring it is a TSV_TNEW_PAGE_ALLOC_FAILED, more info is:
Short text
 No more storage space available for extending an internal table.
What happened?
 You attempted to extend an internal table, but the required space was
 not available.
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrato
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
 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.
or analysis
The internal table "\FUNCTION-POOL=SCMS_R3DB\FORM=DB_PACK\DATA=PHIO_DATA-CONT_B
IN" could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 1022
Number of rows: 378832
Allocated rows: 378832
Newly requested rows: 16 (in 1 blocks)
to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 7219584
Extended memory (EM)........... 2002781760
Assigned memory (HEAP)......... 2000061360
Short area..................... " "
Paging area.................... 122880
Maximum address space.......... 4294967295
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_PAGE_ALLOC_FAILED" " "
"SAPLSCMS_R3DB" or "LSCMS_R3DBF01"
"DB_PACK"
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.
Memory consumption
Roll.... 7219584
EM...... 2002781760
Heap.... 2000061360
Page.... 122880
MM Used. 3960623456
MM Free. 40162736
I've got a customer message message open on this but I've got more back from you guys then that message. Thanks for the info.
Edited by: Ryan Cossette on Sep 1, 2010 4:45 PM

Hi how can i increase my parameter values in my system

Dear Experts ,
here my functional consultants gets below shotdump and how can i solve that an error
Runtime Errors         TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Short text
    No roll storage space of length 1802248 available for internal storage.
hat 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.
how much can i increase please suggest me
Regards

hih mark,
for what base i can increase my parameter values
presently in my parameter values are recomended valus
Parameter          present value          Recommended values
ztta/roll_area-           6500000                      (1.000.000-15.000.000)
ztta/roll_extension-      2000683008          (10.000.000-500.000.000)
abap/heap_area_total u2013 2000683008           (100.000.000-1.500.000.000)
abap/heap_area_dia u2013 2000683008          (10.000.000-1.000.000.000)
abap/heap_area_nondia u2013 2000683008           (10.000.000-1.000.000.000)
em/initial_size_MB u2013           4092                (35-1200)
how much can i increase
Regards

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.

Ztta / roll _ first why used?

Hi,
I've see many recommendations for this parameter like ztta / roll _ first = 1024 or ztta / roll _ first = 1.
Can someone explain why to set this parameter to a low value?
Why this parameter is important if we have extended memory?
Is this parameter deprecated in 64 bits, because extended memory is no more limited?
Regards

Hi,
USE OF ztta/roll_first
ztta/roll_first profile parameter is used for First amount of roll area used in a dialog Work Process
This parameter determines the amount of roll memory in bytes that is allocated to a dialog work process, before SAP Extended Memory is allocated.
On 64 bit platforms where there is sufficient amount of extended memory the default value for ztta/roll_first is set to 1 and this value should not normally be changed.
why to set this parameter to a low value?
To make more use of extended memory only a small portion of the roll area is used initially for this we use the profile parameter ztta/roll_first
Why this parameter is important if we have extended memory?
The standard format of memory allocation to the sap work process is
If a User starts a Transaction, the Usercontext allocate Memory from the local workprocess until ztta\roll_first is reached. So that there should be no Roll Memory used after reaching ztta\roll_first, the usercontext allocates memory until the SAP Extended Memory is reached.(em/initial_size_MB) If the maximum of extended Memory, or if ztta/roll_extension is reached, the rest of the roll Area will be used, until ztta/roll_are is reached and then assigns the heap memory
Hope this helps you
Thanks
Rama

Memory Parameter doubt!!

Hello,
Am trying to implement zero adminstaration memory management on windows 2003 server.
The SAP R/3 version 4.7 running on orcale 10.2 with windows server 2003 (32 bit) enterprise edition .
The server has a RAM of 16 gigs, since the OS is 32 bit and i have enabled the /3gb and /PAE latch. I have a doubt.
What should be the value of PHYS_MEMSIZE.
Now i have 8192 as the value.
Is that OK?
is Ztta/roll_area = 1 byte
is that sufficient?
appreciate insight on above questions.
I followed as per the note 88416.
Regards,
siddhartha.

Hi Siddartha,
PAE is an Intel-provided memory address extension that enables support of greater than 4 GB of physical memory for most 32-bit (IA-32) Intel Pentium Pro and later platforms.
Microsoft supports Physical Address Extension (PAE) memory in Microsoft Windows 2000, Windows XP, and Windows Server 2003 products:
Operating system Maximum memory support with PAE
Windows Server 2003 (and SP1), Standard Edition
4 GB of physical RAM*
Windows Server 2003, Enterprise Edition
32 GB of physical RAM
Windows Server 2003, Datacenter Edition
64 GB of physical RAM
Windows Server 2003 SP1, Enterprise Edition
64 GB of physical RAM
So , pls enable a /PAE switch in boot.ini file
Hope this is useful
Best Regards
Umesh

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,                              &nb

sap 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.

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 cancelled

Hi 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

Dispatcher getting stopped due to possible user/schema mismatch.Plz help

Hello All,
I have SAP Netweaver 7.01 ABAP AS installed on windows 2003. Was working fine but I had to have a bug fixed in win 2003 and restarted my SAP machine. Now, dispatcher is not running. Stops after a while. I have tried restarting SAP and the machine but dispatcher is not running. I looked at the dispatcher trace and dev_w0 but could not figure out the reason as I am new to SAP, please provide any pointers to solve this issue. Any general tips is also welcome. Timely help is greatly appreciated!
I have pasted parts of dev_disp and dev_w0 below. If you require more details, please let me know. Thank you very much!
-Arvind
dev_disp:
=========
trc file: "dev_disp", trc level: 1, release: "701"
sysno 00
sid NSP
systemid 560 (PC with Windows NT)
relno 7010
patchlevel 0
patchno 29
intno 20020600
make: multithreaded, Unicode, optimized
pid 3784
Fri Jun 10 19:25:12 2011
kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
length of sys_adm_ext is 576 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 3784) [dpxxdisp.c 1261]
 shared lib "dw_xml.dll" version 29 successfully loaded
 shared lib "dw_xtc.dll" version 29 successfully loaded
 shared lib "dw_stl.dll" version 29 successfully loaded
 shared lib "dw_gui.dll" version 29 successfully loaded
 shared lib "dw_mdm.dll" version 29 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Fri Jun 10 19:25:18 2011
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5529]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >egsap701_NSP_00 <
DpShMCreate: sizeof(wp_adm) 13632 (1704)
DpShMCreate: sizeof(tm_adm) 4415616 (21968)
DpShMCreate: sizeof(wp_ca_adm) 1664 (80)
DpShMCreate: sizeof(appc_ca_adm) 1600 (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm) 528064 (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1544)
DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 07050040, size: 5042120)
DpShMCreate: allocated sys_adm at 07050040
DpShMCreate: allocated wp_adm at 07052170
DpShMCreate: allocated tm_adm_list at 070556B0
DpShMCreate: allocated tm_adm at 070556E0
DpShMCreate: allocated wp_ca_adm at 0748B760
DpShMCreate: allocated appc_ca_adm at 0748BDE0
DpShMCreate: allocated comm_adm at 0748C420
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0750D2E0
DpShMCreate: allocated gw_adm at 0750D320
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 0750D350
DpShMCreate: allocated wall_adm at 0750D358
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
*** ERROR => ztta/cua_area is 180000. [sapinit.c 975]
*** ERROR => ztta/cua_area adjusted to 500000. [sapinit.c 979]
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 1023 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1656]
***LOG Q0K=> DpMsAttach, mscon ( egsap701) [dpxxdisp.c 12362]
DpStartStopMsg: send start message (myname is >egsap701_NSP_00 <)
DpStartStopMsg: start msg sent
CCMS: alert/MONI_SEGM_SIZE = 0 monitoring and alerting switched off.
DpMsgAdmin: Set release to 7010, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1048]
DpMsgAdmin: Set patchno for this platform to 29
Release check o.K.
Fri Jun 10 19:25:58 2011
my types changed after wp death/restart 0xbf --> 0xbe
my types changed after wp death/restart 0xbe --> 0xbc
my types changed after wp death/restart 0xbc --> 0xb8
my types changed after wp death/restart 0xb8 --> 0xb0
my types changed after wp death/restart 0xb0 --> 0xa0
my types changed after wp death/restart 0xa0 --> 0x80
*** DP_FATAL_ERROR => DpWPCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1565
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 10 19:26:08 2011
NiISelect: TIMEOUT occured (10000ms)
dump system status
max_rq_id 11
wake_evt_udp_now 0
wake events total 7, udp 7 (100%), shm 0 ( 0%)
since last update total 7, udp 7 (100%), shm 0 ( 0%)
Workprocess Comm. Area Blocks Fri Jun 10 13:56:08 2011
=============================
Slots: 20, Used: 1, Max: 0
+------+--------------+----------+-------------+
| id | owner | pid | eyecatcher |
+------+--------------+----------+-------------+
| 0 | DISPATCHER | -1 | *WPCAAD000* |
<SNIP>
[DpProcDied] Process died (PID:3492 HANDLE:1540)
DpStartStopMsg: send stop message (myname is >egsap701_NSP_00 <)
DpStartStopMsg: Write AD_STARTSTOP message with type= 0, name=egsap701_NSP_00 , sapsysnr= 0, hostname=egsap701
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 189 bytes
<SNIP>
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/20/8
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 14)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 2 / sock 1496
NiBufIClose: clear extension for hdl 2
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 3784) [dpxxdisp.c 10924]
Good Bye .....
dev_w0
========
trc file: "dev_w0", trc level: 1, release: "701"
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS all, MJ
B
B Fri Jun 10 19:25:18 2011
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...
B Library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded
B Version of 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "700.08", patchlevel (0.24)
B New connection 0 created
M sysno 00
M sid NSP
M systemid 560 (PC with Windows NT)
M relno 7010
M patchlevel 0
M patchno 29
M intno 20020600
M make: multithreaded, Unicode, optimized
M pid 2768
M
M kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2768) [dpxxdisp.c 1323]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm) 13632 (1704)
M DpShMCreate: sizeof(tm_adm) 4415616 (21968)
M DpShMCreate: sizeof(wp_ca_adm) 1664 (80)
M DpShMCreate: sizeof(appc_ca_adm) 1600 (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
M DpShMCreate: sizeof(comm_adm) 528064 (1048)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (96)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1544)
M DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 07050040, size: 5042120)
M DpShMCreate: allocated sys_adm at 07050040
M DpShMCreate: allocated wp_adm at 07052170
M DpShMCreate: allocated tm_adm_list at 070556B0
M DpShMCreate: allocated tm_adm at 070556E0
M DpShMCreate: allocated wp_ca_adm at 0748B760
M DpShMCreate: allocated appc_ca_adm at 0748BDE0
M DpShMCreate: allocated comm_adm at 0748C420
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 0750D2E0
M DpShMCreate: allocated gw_adm at 0750D320
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 0750D350
M DpShMCreate: allocated wall_adm at 0750D358
M rdisp/queue_size_check_value : -> off
M ThTaskStatus: rdisp/reset_online_during_debug 0
Y *** ERROR => ztta/cua_area is 180000. [sapinit.c 975]
Y *** ERROR => ztta/cua_area adjusted to 500000. [sapinit.c 979]
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host egsap701
M
M Fri Jun 10 19:25:19 2011
M calling db_connect ...
C
C DBSDBSLIB : version 700.08, patch 0.024 (Make PL 0.29)
C MAXDB shared library (dbsdbslib) patchlevels (last 10)
C (0.024) Default value for max. input variables is 2000 (note 655018)
C (0.024) Profile parameter to define max. input variables (note 655018)
C (0.024) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
C (0.024) Input parameters for SQL statements increased (note 655018)
C (0.018) Create index serial for MaxDB 7.6 (note 1267841)
C (0.018) More trace in case of packed to string conversion error (note 1262799)
C (0.016) R3trans export aborts with signal 6 (note 1262245)
C (0.009) IA64 alignment errors (note 1245982)
C (0.007) Support DB-Type 'SAP DB' by UPDSTAT (note 1225668)
C
C
C Loading SQLDBC client runtime ...
C SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 002-121-083-965
C SQLDBC Library Version : libSQLDBC 7.6.5 BUILD 011-123-196-300
C SQLDBC client runtime is MaxDB 7.6.5.011 CL 196300
C SQLDBC supports new DECIMAL interface : 0
C SQLDBC supports VARIABLE INPUT data : 1
C SQLDBC supports keepAlive indicator : 0
C INFO : SQLOPT= -I 0 -t 0 -S SAPR3
C Try to connect (DEFAULT) on connection 0 ...
C Attach to SAP DB : Kernel 7.7.06 Build 007-123-197-046
C Database release is SAP DB 7.7.06.007
C INFO : Database 'NSP' instance is running on 'egsap701'
C DB max. input host variables : 2000
C INFO : SAP DB Packet_Size = 131072
C INFO : SAP DB Min_Reply_Size = 4096
C INFO : SAP DB Comm_Size = 126976
C INFO : DBSL buffer size = 126976
C INFO : SAP DB MaxLocks = 300000
C INFO : Connect to DB as 'SAPNSP'
C *** ERROR => the connected user (SAPNSP) does not work with the right user/schema
[dbslsdb.cpp 4818]
C *** ERROR => application has to work with schema SAPR3 (dbs/ada/schema)
[dbslsdb.cpp 4820]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1449]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10563]
M
M Info for wp 0
M
M pid = 2768
M severity = 0
M status = 0
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M mode_cleaned_counter = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M attachedVm = no VM
M
M *****************************************************************************
M *
M * LOCATION SAP-Server egsap701_NSP_00 on host egsap701 (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Fri Jun 10 19:25:19 2011
M * RELEASE 701
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10783
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >BtcCallLgCl< for event BEFORE_DUMP
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 723]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 261]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 2768) [dpnttool.c 334]

Hello Rattandeep and Markus,
Thanks for explaining the error to me. I'm still facing the issue though!
My start profile is START_DVEBMGS00_egsap701 and instance profile is NSP_DVEBMGS00_egsap701 (they are included below).
In both profiles, the dbs/ada/schema has been currently deactivated. I get the same errors even after deactivating the parameter in both profiles. I also tried your suggestions by setting parameter values to SAPNSP and then to SAPR3 in both profiles but I'm still getting the same errors.
> the above log shows that you have to change the parameter with schema user SAPR3 instead of SAPNSP
You mean that the SAP system is started by SAPNSP user and since the profile is executed by SAPNSP user, we are getting the error? I don't know about the SAPR3 user or the user's credential. I only use bcuser/ddic RFC user to logon to SAP.
I don't know how to check the table space for SAPR3 database. As far as I know, BRTools is only for Oracle backends. So, I used Max DB database manager tool instead and found that the default NSP database has utilized about 50% data area (disk space). Overwrite mode is on and I have about 100% free log area (also determined through database manager tool). Still have not clue as to how to solve this. Please help. Thanks for your tips so far!
The start profile is as follows :
#.* Start profile START_DVEBMGS00_EGSAP701 *
#.* Version = 000004 *
#.* Generated by user = DDIC *
#.* Generated on = 27.04.2011 , 11:02:57 *
SAPSYSTEMNAME = NSP
SAPGLOBALHOST = egsap701
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
DIR_PROFILE = $(DIR_INSTALL)\profile
_PF = $(DIR_PROFILE)\NSP_DVEBMGS00_egsap701
# Copy SAP Executables
Start_Program_00 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
# Start ABAP database
_DB = $(DIR_CT_RUN)\strdbs.cmd
Start_Program_01 = immediate $(_DB) NSP
# Start SAP message server
_MS = $(DIR_EXECUTABLE)\msg_server$(FT_EXE)
Start_Program_02 = local $(_MS) pf=$(_PF)
# Start application server
_DW = $(DIR_EXECUTABLE)\disp+work$(FT_EXE)
Start_Program_03 = local $(_DW) pf=$(_PF)
rsdb/dbid = NSP
#dbs/ada/schema = SAPNSP
Instance profile is as follows:
#.* Instance profile NSP_DVEBMGS00_EGSAP701 *
#.* Version = 000006 *
#.* Generated by user = DDIC *
#.* Generated on = 27.05.2011 , 11:30:39 *
SAPSYSTEMNAME = NSP
SAPGLOBALHOST = egsap701
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
rdisp/wp_no_dia = 3
rdisp/wp_no_btc = 1
icm/server_port_0 = PROT=HTTP,PORT=80$$
# SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
rdisp/wp_no_enq = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 1
rdisp/wp_no_spo = 1
PHYS_MEMSIZE = 128
em/initial_size_MB = 10240
em/max_size_MB = 1024
abap/buffersize = 100000
#old_value: 0 changed: DDIC 27.04.2011 11:04:52
#old_value: 60000000 changed: DDIC 27.05.2011 11:29:55
alert/MONI_SEGM_SIZE = 0
enque/table_size = 2000
#parameter deactivated by: DDIC 27.05.2011 11:11:00
#rspo/local_print/method = 2
rsdb/ntab/entrycount = 5000
rsdb/ntab/ftabsize = 3000
rsdb/ntab/sntabsize = 100
rsdb/ntab/irbdsize = 1000
rsdb/cua/buffersize = 500
rsdb/obj/buffersize = 2048
rsdb/obj/max_objects = 500
rsdb/otr/buffersize_kb = 1000
rsts/ccc/cachesize = 6000000
rtbb/buffer_length = 500
rtbb/max_tables = 50
sap/bufdir_entries = 200
zcsa/presentation_buffer_area = 350000
zcsa/calendar_area = 300000
zcsa/table_buffer_area = 3000000
zcsa/db_max_buftab = 500
ztta/roll_area = 1000000
ztta/diag_area = 128000
ztta/dynpro_area = 150000
ztta/cua_area = 180000
rdisp/PG_SHM = 100
rdisp/PG_MAXFS = 256
rdisp/ROLL_SHM = 100
rdisp/ROLL_MAXFS = 2048
#old_value: 0 changed: DDIC 27.04.2011 11:04:52
#old_value: 300 changed: DDIC 27.05.2011 11:29:38
rdisp/autoabaptime = 0
rdisp/wp_ca_blk_no = 20
rdisp/appc_ca_blk_no = 20
rdisp/max_wprun_time = 30000
icm/min_threads = 5
icm/max_threads = 10
icm/max_conn = 20
mpi/total_size_MB = 10
rsdb/dbid = NSP
#parameter deactivated by: DDIC 27.05.2011 11:11:22
#dbs/ada/schema = SAPNSP

2LIS__04_P_COMP load failure

Hi,
I am facing a problem while loading data from R/3 to BW using the datasource 2LIS__04_P_COMP.
The data is extracted successfully but takes a lot of time in the update rules around 10 hrs.Ulitmately the load fails and i have to manually update it after which the load becomes successful.
When i check the job status in the R/3 side it shows me ARFSTATE =SYSFAIL error.
There are two source systems from which i load data .. one is A6P and other is ANP..the load from ANP is always successful and the one from A6P always fails with SYSFAIL error.The update rules for both the system is the same.
Please can someone assist me with this problem.

I will try debugging again.. but i have a query .When i check the particular request in the R/3 side when the load happens for the first time and it fails that is before it is manually updated, the job log in the R/3 side mentions ARFCSTATE = SYSFAIL in what cases does this kind of error occur .Job log details in R/3
17:17:13 Job started
17:17:13 Step 001 started (program SBIE0001, variant &0000000036256, user name ADMDTLOAD)
17:17:13 DATASOURCE = 2LIS_04_P_COMP
17:17:13 *************************************************************************
17:17:13 *           Current values of selected profile parameter                *
17:17:13 *************************************************************************
17:17:13 * abap/heap_area_nondia......... 4000000000                              *
17:17:13 * abap/heap_area_total.......... 4000000000                              *
17:17:13 * abap/heaplimit................ 62914560                                *
17:17:13 * zcsa/installed_languages...... 1MEFDST                                 *
17:17:13 * zcsa/system_language.......... E                                       *
17:17:13 * ztta/max_memreq_MB............ 64                                      *
17:17:13 * ztta/roll_area................ 6500352                                 *
17:17:13 * ztta/roll_extension........... 150994944                               *
17:17:13 *************************************************************************
17:18:03 37 LUWs confirmed and 37 LUWs to delete with FM RSC2_QOUT_CONFIRM_DATA
17:18:21 Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 52.524 records
17:18:21 Result of customer enhancement: 52.524 records
17:18:21 Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 52.524 records
17:18:21 Result of customer enhancement: 52.524 records
17:18:21 Asynchronous send of data package 000001 in task 0002 (1 parallel tasks)
17:18:26 Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 51.032 records
17:18:26 Result of customer enhancement: 51.032 records
17:18:26 Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 51.032 records
17:18:26 Result of customer enhancement: 51.032 records
17:18:27 Asynchronous send of data package 000002 in task 0003 (1 parallel tasks)
17:18:30 Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 14.966 records
17:18:30 Result of customer enhancement: 14.966 records
17:18:30 Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 14.966 records
17:18:30 Result of customer enhancement: 14.966 records
17:18:30 Asynchronous send of data package 000003 in task 0004 (2 parallel tasks)
17:18:32 Selection conditions filtered out a total of 0 records
20:18:44 tRFC: Data package = 000003, TID = 9B7CE88956FD47E8C3670107, duration = 03:00:06, ARFCSTATE = SYSFAIL
20:18:44 tRFC: start = 25.03.2008 17:18:38, end = 25.03.2008 20:18:44
20:18:52 tRFC: Data package = 000001, TID = 9B7CE889236647E8C35F0176, duration = 03:00:08, ARFCSTATE = SYSFAIL
20:18:52 tRFC: start = 25.03.2008 17:18:44, end = 25.03.2008 20:18:52
20:18:57 tRFC: Data package = 000002, TID = 9B7CE88917F647E8C3640256, duration = 03:00:10, ARFCSTATE = SYSFAIL
20:18:57 tRFC: start = 25.03.2008 17:18:47, end = 25.03.2008 20:18:57
20:18:57 Job Finished

MEMORY_NO_MORE_PAGING error

Hi,
We are using ECC 5.0 here. Our DB is Oracle 9.2.0.6 and OS is AIX.
We have a problem here.
Our Finance people run a report "S_ALR_87013542". It was working fine.
But now it is giving an error with ABAP Dump. The error is MEMORY_NO_MORE_PAGING.
I have increased the parameter "rdisp/PG_SHM" to the double value. Now the value is 16384. But it is still giving the same error.
I increased it on a Dialog Instance (application server through which Finance people access SAP)
I searched the notes, but could not find anything relevant about my error.
I have tried to run the report in the night when there is no load on the server. But even then it gives the same error.
My different Memory Paramters for the App server for finance people are listed below:-
ztta/roll_area                              3000320
rdisp/ROLL_SHM                              16384
rdisp/ROLL_MAXFS                            32768
rdisp/PG_SHM                                16384
rdisp/PG_MAXFS                              32768
abap/heap_area_dia                          2000683008
abap/heap_area_nondia                       2000683008
abap/heap_area_total                        2000683008
abap/heaplimit                              40894464
abap/swap_reserve                           20971520
ztta/roll_extension                         2000683008
My ABAP dump gives this error:-
Error analysis
    The ABAP/4 runtime system and the ABAP/4 compiler use a common
    interface to store different types of data in different parts of
    the SAP paging area. This data includes the
    ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
    CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
    macros (specified with DEFINE).
                                                                                To store further data in the SAP paging area, you attempted to
    allocate a new SAP paging block, but no more blocks were
    available.
                                                                                When the SAP paging overflow occurred, the ABAP/4 memory contained
    entries for 55 of different IDs.
                                                                                Please note:
    To facilitate error handling, the ABAP/4 memory was
    deleted.
How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
                                                                                Roll area...................... 16128
    Extended memory (EM)........... 418992800
    Assigned memory (HEAP)......... 0
    Short area..................... " "
    Paging area.................... 40960
    Maximum address space.......... 4294967295
                                                                                By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
    you can display an overview of the current roll and paging memory
    levels resulting from active users and their transactions. Try to
    decide from this whether another program requires a lot of memory
    space (perhaps too much).
                                                                                The system log contains more detailed information about the
    termination. Check for any unwanted recursion.
    Determine whether the error also occurs with small volumes of
    data. Check the profile (parameter "rdisp/PG_MAXFS", see
    Installation Guidelines).
    Is the disk or the file system that contains the paging file
    full to the extent that it cannot be increased, although it has
    not yet reached the size defined in the profile? Is the
    operating system configured to accommodate files of such a
    size?
                                                                                The ABAP processor stores different types of data in the SAP paging area
    . These include:
                                                                                (1) Data clusters (EXPORT ... TO MEMORY ...)
       (2) Parameters when calling programs (SUBMIT REPORT ...),
        dialog modues (CALL DIALOG ...) and transactions
        (CALL TRANSACTION USING ...)
    (3) Internally defined macros (DEFINE ...)
                                                                                Accordingly, you should check the relevant statements in a program
that results in an overflow of the SAP paging area.
                                                                                The EXPORT statement is particularly critical - specifically when many
internal tables, possibly with different IDs, are written to the
memory.
Kindly help
Regards,
Tajinder

Hello,
Here the parameters for concern are
1.rdisp/PG_SHM
2.rdisp/PG_MAXFS
1.rdisp/PG_SHM :
The value specifies the size of the paging buffer in 8KB blocks.
A paging buffer is no longer required for SAP Memory Managment,
because internal tables and lists are not stored in SAP paging.
Default : 0
2.rdisp/PG_MAXFS :
This value specifies the size of the SAP paging file in 8KB
blocks. The paging file is used to store extracts and for
Export to Memory.
Aim:
The paging file must be sufficiently large. It is not a problem
if it is set to too large a size.
Dependencies:
Sufficient disk space
You can try
1.Optimize the code, to use less memory.
OR
2.Increasing the parameter rdisp/PG_MAXFS as per the availability of disk space.
Hope this solves your problem.
Regards,
Edited by: Satish P on Oct 21, 2008 2:01 PM

Parameter ztta/roll_area

Similar Messages

Maybe you are looking for