SYSTEM_NO_TASK_STORAGE DDIC_ACTIVATION upgrade to EHP4 SPS5

Question

Hello,
When want to upgrade our system from SAP ERP 6.0 EHP3 SPS5 ( Windows 32 Bit with RAM 3Gb )  to EHP4 SPS5 with SAINT  we encountered the following Error in  DDIC Activation phase :
The following details help you to analyze the problem:
     -   Error in phase: DDIC_ACTIVATION
     -   Reason for error: TP_STEP_FAILURE
     -   Return code: 0012
     -   Error message: OCS Package SAPK-60401INEAAPPL, tp step A, return
         code 0012
In ST22 we have the following message :
Runtime Errors         SYSTEM_NO_TASK_STORAGE
Date and Time          20.05.2011 19:51:09
Short text
     Unable to fulfil request for 3897444 bytes of storage space.
We have adjut the following parameters but we still have the error :
tta/roll_extension = 2000000000
ztta/roll_area = 1000000
ztta/roll_first = 1
em/max_size_MB = 20000
em/initial_size_MB = 2048
abap/heap_area_dia = 2000000000
abap/heap_area_total = 5000000000
abap/heap_area_nondia = 2000000000
We have also applied  /3GB in boot.ini for windows (recommendation Note 1275873 - Memory bottleneck during DDIC activation during EHP import ).
Thank you for you help.

Answer 1

The short-dump issue you are experiencing is a well known problem which uses to occur on 32-bit architecture system platforms;
those short-dumps are a clear indication of a 'lack of memory (address space) issue'.
When a program (or a transaction or a job) is running, the work process
follows this memory allocation sequence (valid for Windows platforms):
   a) Roll memory up to the quota "ztta/roll_first"
   b) Extended memory up to the quota "em/address_space_MB"
   c) Roll memory up to the quota "ztta/roll_area"
   d) Heap memory up to the quota "abap/heap_area_dia"
Short dumps like these ones arise when additional memory
is required to extend the internal table, but none is available.
Check these points :
- make sure parameters values are set as indicated in Note 88416
read the document "Optimizing the Memory Settings for
    SAP Systems on 32-Bit Windows" that you will find at:
    http://service.sap.com/~sapidb/011000358700006425762006E
Also,
- Enable the Windows startup option /3GB, as per Note 110172
- Reduce the memory parameters rdisp/ROLL_SHM and rdisp/PG_SHM to
    6000 and check that other memory buffers like abap/buffersize have
    not been increased from default values.
Note 110172 : Windows: Transactions with large memory requirements
- Niraj