SEM_BW_BCS 603 RUNTIME ERROR: TSV_TNEW(BTR)_PAGE_ALLOC_FAILED

Question

hi everyone,
When i run the transcation:ucwb, execute the SEM_BCS workbench/monitor ,an runtime error occured.
My BW dev system and qas system have came across the same situation
My environment is:
AIX5300 64b
memory8G swap space20G
Oracle10g
Netweaver2004s
SAP_BW level 18
SEM_BW 603 with SP2
following is the error info:
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 administrator
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) // initial value :1000000; current value:6000000
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) //initial value:2000000000;current value:2000000000**
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000) //initial value:2000000000;current value:2000000000
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. //em/address_space_MB :initial value:4096;current value:8192**
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) //initial value:2000000000;current value:2000000000**
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)//initial value:2000000000;current value:2000000000**
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200) )//initial value:4096;current value:4096**
Extended memory area from which all users of an
application server can satisfy their memory requirement.
rror analysis
The internal table "\AREA=CL_UGMD_META2\INSTANCE=UGMD_FIELDINFO_LOCAL\VERSID=37
2\OBJ=\DATA=DT_X030L" 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: "\AREA=CL_UGMD_META2\INST=UGMD_FIELDINFO_LOCAL\CLNT="
Row width: 254
Number of rows: 982
Allocated rows: 982
Newly requested rows: 64 (in 1 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 16192
Extended memory (EM)........... 29328936
Assigned memory (HEAP)......... 0
Short area..................... " "
Paging area.................... 73728
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" " "
"CL_UG_FIELDINFO_LOCAL_SHM=====CP" or "CL_UG_FIELDINFO_LOCAL_SHM=====CM003"
"SET_DATA"
****************************************************************8
Any ideas any suggestions will be much appreciated !
Thanks very much
Regards!
Peter

Answer 1

i increase the value of the profile parameter：abap/shared_objects_size_MB
the problem soluted