CRMXIF_PRODUCT_INDOBJ_SAVE causing TSV_TNEW_PAGE_ALLOC_FAILED

I'm calling CRMXIF_PRODUCT_INDOBJ_SAVE in a batch conversion program. However, after 3 hours of processing my program abends with a TSV_TNEW_PAGE_ALLOC_FAILED on line 62 of CRMXIF_PRODUCT_INDOBJ_SAVE (APPEND ls_settype TO et_settype.). This is an SAP FM. Have you used this FM in batch? Is there some kind of cleanup FM that must be called after CRMXIF_PRODUCT_INDOBJ_SAVE is invoked?
Thanks
Leo

Hello Leo,
Please check if SAP note 1325215 can help
Best Regards
Barry

Similar Messages

Error TSV_TNEW_PAGE_ALLOC_FAILED caused by Function CHANGEDOCUMENT_READ

Hi,
I met the error TSV_TNEW_PAGE_ALLOC_FAILED when I call the function CHANGEDOCUMENT_READ.
However, I only import a day , a table and a objectclass.
CALL FUNCTION 'CHANGEDOCUMENT_READ'
      EXPORTING
        date_of_change             = c_day
        objectclass                = c_class
        tablename                  = c_table
        date_until                 = c_day
      TABLES
        editpos                    = i_editpos
      EXCEPTIONS
        no_position_found          = 1
        wrong_access_to_archive    = 2
        time_zone_conversion_error = 3
        OTHERS                     = 4.
And when I debug it, I found it get very huge data(Both CDHDR and CDPOS have more than 500,000 records).
Any suggestion will be helpful.
Thanks,
Franklin

It looks like you will read to call it multiple times including the parameters TIME_OF_CHANGE and TIME_UNTIL, But this will be very time consuming.
Check the documentation on these two parameters.
Rob

Production error - Urgent - TSV_TNEW_PAGE_ALLOC_FAILED

Hi All,
Im getting dumps in production system with
Runtime Error: TSV_TNEW_PAGE_ALLOC_FAILED. and when checked the trace, it says as Data type "MCVBAPB" was found in a newer version than required.
Any pointers to this wil be helpful
thanks
Booma

the TSV_TNEW_PAGE_ALLOC_FAILED dump has naught to do with the version of MCVBAPB. the dump clearly states that there was no more paging area available to run the report/transaction that caused the dump. this might either be due to an too big selection or a lack of memory. Consult your basis-people with that one.
the version of MCVBAPB: MCVBAPB is a structure belonging to LIS (Logistics Information System) so obviously someone changed that structure. check in t-code SE11, MCVBAPB the runtime and the database object of the structure (in case it is active).

Runtime errors: TSV_TNEW_PAGE_ALLOC_FAILED

Hi,
When I am trying to check the consistency of background jobs in SM65, It is throwig a runtime error TSV_TNEW_PAGE_ALLOC_FAILED. Kindly look into the below text message from ST22.
ShrtText
    No 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?
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    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)
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.
Error analysis
The internal table "IT_18" could not be enlarged further. To allow
error handling, the table had to be deleted before this log was
created. So, if you branch to the ABAP debugger from the display
of this log, the table will there be displayed with 0 rows.
At the moment of the termination, the following data was
determined for the respective internal table:
Storage location: "Session memory"
Row width: 1296
Number of rows: 1166120
Allocated rows: 1166120
Newly requested rows: 8 (in 1 blocks)
           Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server ord-sapprd_PRD_00 on host ord-sapprd (wp 0)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1878
How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 1709536
    Extended memory (EM)........... 408685712
    Assigned memory (HEAP)......... 1190561024
    Short area..................... " "
    Paging area.................... 57344
    Maximum address space.......... " "
    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
    "SAPLSBPT" or "LSBPTFXX"
    "DO_TBTCO_CONSISTENCY_CHECK"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
   To obtain this, select in the current display "System->List->
   Save->Local File (unconverted)".
2. A suitable printout of the system log
   To obtain this, call the system log through transaction SM21.
   Limit the time interval to 10 minutes before and 5 minutes
   after the short dump. In the display, then select the function
   "System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, select the Editor function "Further Utilities->
   Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "ord-sapprd"
Network address.......... "10.31.18.27"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "16x Intel 80158"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Kindly suggest me the options ASAP as this is happened in the production system.
Thanks in advance,
Suneetha Reddy

Hi Sunnetha,
SM65 is a resource hungry tcode, and always suggested to run during a off-business hours. Try to run when there is not much acvitity going on in the system.
I'm not very much sure, but please check how many entries there in TBTCO table. as the dump gives indication of
DO_TBTCO_CONSISTENCY_CHECK.
Check RSBTCDEL(2) program is running daily or not. This runs as a background job to delete the old job information from the tables TBTC*. If this has not run, then you can run and delete older job logs and then retry.
Which system you're using? ECC or BW??
Note - parameter settings of BW largely varies from that of a ECC system.
Thanks,
Debasis.

TSV_TNEW_PAGE_ALLOC_FAILED with internal table declared with occurs 0

HI guys,
when the internal table is declared as occurs 0, the dump TSV_TNEW_PAGE_ALLOC_FAILED is encountered, when changing the declaration into standard table, th dump disappears. Why is this so?
Thanks!

There are three type of tables: Standard, sorted and hashed tables (see [here|http://help.sap.com/abapdocu_70/en/ABAPDATA_ITAB.htm]). When you define a table using the keyword OCCURS you're still defining a standard table.
Your exception indicates that you're running out of memory. The difference in the declarations that you mention shouldn't cause that. Main difference between the two declaration versions is probably that your table defined via OCCURS has a header line, whereas your other table doesn't (unless you declared it explicitly as WITH HEADER LINE).
I don't think though that with that little information anybody could explain the short dump. Actually it sounds rather odd that the change you mention should cause the dump (or make it go away). So I suspect you probably have to post further details. You might want to check the shortdump yourself and place a breakpoint at this place and run it for each version. Maybe you can see some difference...

TSV_TNEW_PAGE_ALLOC_FAILED at SEM BCS

Hey SAP-Admins !
I have a Problem with this shortdump TSV_TNEW_PAGE_ALLOC_FAILED at TA: UCWB_INT
We're running Windows 64 Bit / SAP + DB with 24 GB RAM and 30 GB swap space.
I don't understand why we got this dump cause cause we have ZAMM aktiv and only the
memory parameter 
Phys_memsize = 8192
abap/use_paging = 0 
abap/heaplimit = 408944640 
abap/swap_reserve = 20971520 
em/blocksize_KB = 1024 
abap/shared_objects_size_MB = 600 
rdisp/max_wprun_time = 3600 
aktiv.
memorystate on the OS-System at the Dump
http://i53.tinypic.com/zlexjc.jpg
output memlimits
D:\usr\sap\B07\SYS\exe\nuc\NTAMD64>memlimits -v off
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Verbose mode off
Check the maximum data size per process (malloc)
Maximum process heap size = 4096MB
----
| Result |
----
Maximum heap size per process........: 4096 MB
measurement limited to 4096 MB
this value is probably limited by swap space
Total available swap space...........: 4096 MB
measurement limited to 4096 MB
main memory size x 3 recommended , minimum 1 GB
swap space probably even bigger, but cannot be
totally allocated by only one process
output sappfpar
D:\usr\sap\B07\SYS\exe\nuc\NTAMD64>sappfpar check pf=D:\usr\sap\B07
\SYS\profile\
B07_DVEBMGS00_SAPBON1S22
================================================================================
== Checking profile: D:\usr\sap\B07
\SYS\profile\B07_DVEBMGS00_SAPBON1S22
================================================================================
***WARNING: Unexpected parameter: login/password_max_new_valid =0
***WARNING: Unexpected parameter: login/password_max_reset_valid =0
Shared memory disposition overview
================================================================
Key: 1 Size: 2500 ( 0.0 MB) System administration
Key: 2 Size: 5503580 ( 5.2 MB) Disp. administration
tables
Key: 3 Size: 13714400 ( 13.1 MB) Disp. communication areas
Key: 4 Size: 519448 ( 0.5 MB) statistic area
Key: 5 Size: 4096 ( 0.0 MB) SCSA area
Key: 6 Size: 362086400 ( 345.3 MB) ABAP program buffer
Key: 7 Size: 14838 ( 0.0 MB) Update task administration Key: 8 Size: 134217828 ( 128.0 MB) Paging buffer
Key: 9 Size: 268435556 ( 256.0 MB) Roll buffer
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert
Buf.
Key: 13 Size: 40500000 ( 38.6 MB) Alert Area
Key: 14 Size: 4400128 ( 4.2 MB) Presentation buffer
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity
monitoring
Key: 17 Size: 2747780 ( 2.6 MB) Roll administration
Key: 18 Size: 917604 ( 0.9 MB) Paging adminitration
Key: 19 Size: 100000000 ( 95.4 MB) Table-buffer
Key: 30 Size: 30720 ( 0.0 MB) Taskhandler runtime admin. Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue
Key: 33 Size: 51200000 ( 48.8 MB) Table buffer,
part.buffering
Key: 34 Size: 16777216 ( 16.0 MB) Enqueue table
Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 42 Size: 7056992 ( 6.7 MB) DB TTAB buffer
Key: 43 Size: 32504728 ( 31.0 MB) DB FTAB buffer
Key: 44 Size: 7914392 ( 7.5 MB) DB IREC buffer
Key: 45 Size: 4842392 ( 4.6 MB) DB short nametab buffer
Key: 46 Size: 20480 ( 0.0 MB) DB sync table
Key: 47 Size: 4097024 ( 3.9 MB) DB CUA buffer
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer
Key: 49 Size: 2769392 ( 2.6 MB) Spool admin
(SpoolWP+DiaWP)
Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.
Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer
Key: 54 Size: 4202496 ( 4.0 MB) Export/Import buffer
Key: 55 Size: 8192 ( 0.0 MB) Spool local
printer+joblist
Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared
mem
Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset
Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes
Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository
Buf.
Key: 65 Size: 41951232 ( 40.0 MB) Export/Import Shared
Memory
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring
V01.0
Nr of operating system shared memory segments: 41
Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....: 41
Shared memory segment size required min..: 362086400 ( 345.3 MB)
Swap space requirements estimated
================================================
Shared memory....................: 1181.0 MB
Processes........................: 247.4 MB
Extended Memory .................: 4096.0 MB

Total, minimum requirement.......: 5524.4 MB
Process local heaps, worst case..: 8192.0 MB
Total, worst case requirement....: 13716.4 MB
Errors detected..................: 0
Warnings detected................: 2
D:\usr\sap\B07\SYS\exe\nuc\NTAMD64>
thank you a lot !
Darius

Hey Mercedes, 
thank you for your answer! 
but this system are running with ZAMM configuration
1. The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. An "infinitely" large memory resource is made available with this method. The extended memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended memory extends itself in steps of "[PM] / 2" up to the set limit of the profile parameter em/max_size_MB (64 Bit 100000) or until the address space in the Windows page file is used up.
In this case this DUMP is very strange cause there are no limits beside the PHYS_MEMSIZE parameter 
Roll area...................... 2417280 
Extended memory (EM)........... 2000358240 
Assigned memory (HEAP)......... 2000047808 
Short area..................... " " 
Paging area.................... 942080 
Maximum address space.......... " " 
best regards
Darius

TSV_TNEW_PAGE_ALLOC_FAILED during extraction

Hi Experts,
during extraction I receive TSV_TNEW_PAGE_ALLOC_FAILED short dump.
More information from ST22:
The internal table "\PROGRAM=AQZZSYSTBWGENER0SY000000000022\DATA=%DTAB[]" 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: 2020
Number of rows: 921272
Allocated rows: 921272
Newly requested rows: 8 (in 1 blocks)
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6216720
Extended memory (EM)........... 1001373672
Assigned memory (HEAP)......... 2000087232
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 18446744054030015328
So it seems that there is a memory problem cause of the big amount of data (around 1.200.000 records at all should be transferred).
I already split up the number of parallel processes and maximum lines in ta-code SBIW. This made the process faster but still the short dump appears.
This is the initial data extraction and all records have to be transferred. Is there any possibility in splitting up an initial data extraction in several packages? It's based on a generic extractor which get's data through InfoSet/ABAP FM.
Many thanks in advance.
Best regards
Tobias

Well, we are talking about the initialization only, hence I dont think the necessity of creating several process chains .. Say you can create multiple infopackages .. with non overlapping selection criteria ..
Example ..
Calendar year :- 2008
Calendar Year :- 2009
so on ..
And they can be loaded manually !!
once all the init selections are done .. you just need a single infopackage for delta loading which will actually load the delta records for all the successful init conditions ..
Hope that helps ..
Thanks.

What is the maximum number of recursive call as i think it is causing short dump

Hi All,
This may not have a specific answer i suppose but approx is also fine. There was a short dump in production ( the background job failed , an is failing each day since a week now ). I was analysing it what i found was the cause for there was numerous call to the same routine within it self ( recursion ). The exact number i dont have but they were atleast more the 200.
The error message which i get is :
Are there any solution regarding
Category
Resource Shortage
Runtime Errors
TSV_TNEW_PAGE_ALLOC_FAILED
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.
it would be great if we know the max numbers of an recursive call so that i can do the necessary changes or if some 1 has any other alternative solution pls. help.
Regards,
Dhruvin
P.s : it's a productive environment issue.

The dump is not caused by depth of recursion but rather memory limits being exceeded by your process, these are controlled by profile parameters (System administrator stuff) and "normally" (unless changed to other values) allow up to 4 GB of memory usage (mostly by internal tables). You can quickly check the current memory consumption of your active process via SM50.
Make sure that the routine that is called recursively (or other relevant parts of your process) free up memory by using CLEAR and FREE statements for internal tables that are no longer needed.
If data is being selected from the database also look into block processing via the PACKAGE SIZE option.
Thomas

TSV_TNEW_PAGE_ALLOC_FAILED Dump in Production BW 3.5 system

Hi Basis Gurus,
In our production BW 3.5 system we are getting dump in ST22.
The dump is TSV_TNEW_PAGE_ALLOC_FAILED
Please let me know what could be the reason for this dump and why we are getting it.
I tried searching in service market place and there we can find lot of things related to this dump.But not sure which one is specificaly related to this dump.
Our system details are as follows
BW 3.5
Solaris OS
Oracle Database.
Please help me in resolving this dump.
Regards,
Anil.

Hello Anil,
what is the frequency of these dumps.
If the dump once in a while,you can simply ignore it
If frequency is more....you will need to reasrch a bit before increasing the paging memory as suggested previously
Just check what program is causing the dump,is it SAP standard program or a z program created by your developers.
If it is a SAP standard program just search on market place and look if any new version of the program exists which is tuned better and which consumes less memory
If it is a z program ask your developer to tune the program(this can be a highly cause of this dump as programs created usually consume a lot of memory due to which this dump occurs)
If none of these help,go for increase in the paging memory as previusly suggested
Rohit

CTM Run failing with TSV_TNEW_PAGE_ALLOC_FAILED runtime error

Hi,
While doing the CTM run,system is giving the memory dump with run time error TSV_TNEW_PAGE_ALLOC_FAILED.
I understand this is because memory constraint and possible recommendation to either increase the Memory or reduce the master data selections for planning but would like to know if some master data discrepancy can cause the infinite run of CTM and hence memory dump like product at location being set as Inhouse production but no PPM maintained for it.
Any suggestions on this willl reward points.
Thanks,
Manish
Edited by: Manish Thukral on Jun 24, 2008 9:34 PM

Marcelo,
Thanks for you reponse.Can you please share some more information on what explanation profile is and where it is set so that can I check.
Manish

"TSV_TNEW_PAGE_ALLOC_FAILED" errors

Our SAP system always gets the "TSV_TNEW_PAGE_ALLOC_FAILED" errors,
It has 16 GB physical memory and its em/initial_size_MB is 13.87 GB and its ztta/roll_extension isztta/roll_extension 2.79 GB.
I want to know where these errors come from :
(1)Our overall Extended Memory (em/initial_size_MB) is not large enough ?
(2)Or our overall Extended Memory is OK but ztta/roll_extension is too small ?
Please help me how to find out the root cause of this error.
Thank you very much.

is this dump for standard SAP or locally developed program? also check whether user ran report without any selection parameters? is this dump occurring frequently?
cheers,
-Sunil

Error TSV_TNEW_PAGE_ALLOC_FAILED during Enchancement Pack 4 upgrade

Hi Everyone,
I'm at upgrade stage MAIN_SHDRUN/ACT_UPG which has been stuck here for the past couple of days. Finally errored out with:
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-40401INEAIPPE.TRN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDMASGL", no.: "19283900")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDMASGL""19283900""TRN"
1 ETP111 exit code : "12"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60011INLSOFE.TRN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDMASGL", no.: "19283900")
Long text: see above
1AEPU320 See job log"RDDMASGL""19283900""TRN"
1 ETP111 exit code : "12"
I checked ST22 and it is giving me dump TSV_TNEW_PAGE_ALLOC_FAILED. I read in many places to increase the virtual memory which I have to 85829MB, I've increased abap/heap_area_dia to 9221225472 & abap/heap_area_nondia 9221225472 but I continue to get the same errors. I'm not sure how to proceed past this and I'm running very behind schedule to get this installation completed. Any suggestions? Any help would be greatly appreciated. Thank you!

Hi
Pl tune the parameters of SAP , Oracle and OS in phased manner. It will definetly solve your problem.
Pl note that change the memory related parameters in stage-1
Regards
Vimal

Run-time error "TSV_TNEW_PAGE_ALLOC_FAILED" occurred

Hi all,
I am running BDLS report in background after system copy. Its getting failed. On checking the failed job log in SM37 am getting the TSV_TNEW_PAGE_ALLOC_FAILED runtime error and message as below.
I have checked and all memory parameters looks fine and similar to other systems, No other program/report is running on the server. Please help.
Memory low. Leave the transaction before taking a break!
Message no. 00072
Diagnosis
The memory on your application server is running low.
System Response
You are exclusively using one of the few work processes running on the application server. So that this does not hinder the other users too much, the work process is released if you do not work with it for a few minutes. The system terminates the transaction, causing you to lose data that you previously entered.
Procedure
Continue to work as normal and exit the transaction before you take a long break
memory parameter settings as below
ztta/roll_area 3000320 Byte
ztta/roll_first 1024 Byte
ztta/short_area 1600000 Byte
rdisp/ROLL_SHM 16384 8 kB
rdisp/PG_SHM 8192 8 kB
rdisp/PG_LOCAL 150 8 kB
em/initial_size_MB 6144 MB
em/blocksize_KB 4096 kB
em/address_space_MB 4092 MB
ztta/roll_extension 2000683008 Byte
abap/heap_area_dia 2147483648 Byte
abap/heap_area_nondia 2147483648 Byte
abap/heap_area_total 2147483648 Byte
abap/heaplimit 83886080 Byte
abap/use_paging 0
WP trace info
A *** ERROR => User SSeeeN reached avail. heapsize = 2047 MB: see ST22 [abstor.c 1766]
A *** ERROR => Increase abap/heap_area_total [abstor.c 1768]
A *** ERROR => heap memory WP0: 2047 MB [abstor.c 1771]
A *** ERROR => heap memory WP1: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP2: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP3: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP4: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP5: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP6: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP7: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP8: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP9: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP10: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP11: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP12: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP13: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP14: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP15: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP16: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP17: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP18: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP19: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP20: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP21: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP22: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP23: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP24: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP25: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP26: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP27: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP28: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP29: 0 MB [abstor.c 1771]
A *** ERROR => heap memory WP30: 0 MB [abstor.c 1771]
Please help.
Regards,
Sandeep

Hi Mho,
Yes i started BDLS in background and its getting cancelled after running for 2.5 hours.
The below WP trace is when i am seeing BDLS job log via SM37 which is a dialog and is getting terminated with TSV_NEW_PAGE-allocation failed.
the job log file is quite huge. Is that a problem ??
-rwxrwxrwx 1 sidadm sapsys 1071026978 Jan 20 23:52 0001X21231200X62021
-rw-rw---- 1 sidadm sapsys 1071029688 Jan 21 05:28 0001X02591200X84343
I got this in SM21.
During background processing, the system was unable to read the
specified job log. This may be due to the following:
- The instance from which you wanted to read the job log does not
 have access to the central SAP directory containing the job logs:
 /usr/sap/<Systemname>/SYS/global/<client>JOBLG, for example
 /usr/sap/C11/SYS/global/000JOBLG for the job logs for client 000 in
 system C11. Make sure your instance has access to this
 directory. Examine the syslog for relevant entries.
- As job logs are written and read using the SAP TemSe subsystem,
 there may be problems within TemSe.
 Examine the syslog for relevant entries.
- The disk, on which the directory specified above is stored, is
 full. Consequently, no new job logs can be read or written.
However, i executed another small job which has finished fine and we can see the SM37 jobs

Getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" during the load

Hi Experts,
I am getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" when loading data one ODS to Two cubes in 3.1 system . we have only 12000 records to load. this load is delta update. daily we loaded 14000 record from this load but today we are getting short dump.
Short Dump : TSV_TNEW_PAGE_ALLOC_FAILED
Description : No storage space available for extending the internal table.we attempted to extend an internal table, but the required space wasnot available.
Thanks

This is a memory issue whereby an internal table requires more memory than what is currently available. If you're executing this during processing of other ETL, then your memory is being consumed by all of the processes and you would need to change your schedule as to balance the load better.
Another possibility is that you have an extremely inefficient SQL statement in a routine that is causing the memory to be overly consumed. Even though the output may be less than average, there is a possiblity that it's reading more data in a SELECT statement and therefore requires more memory than normal.
Finally, have you Basis team look at this issue to determine if there's anything that they can do to resolve it.

USB CAUSING LOCK-UPS

Hi,
30-40% of the time when I use my front usb it will cause Win XP to lock up and I have to hit the reset button. Has anyone else experienced this and also any remedies? It happens with my scanner, gamepad and ipaq. Setup=Win XP prof w/ service pack 1, KT3ultra2, AMD 1600xp, power supply is 400 watts.
Thanx

Hi Maesus,
I have AMI bios version 3.31a. I can't find the usb version on XP (I only know how to get to it on Win 98SE). It's the one that came with Win XP. If it matters, the VIA driver I'm using is v4.42. Lastly the USB connectors are the ones built into the front panel of my case. I wired it up according to the manual.
Again, the unusual thing is when it doesn't lock-up everything works fine.
Thanx again for your help

CRMXIF_PRODUCT_INDOBJ_SAVE causing TSV_TNEW_PAGE_ALLOC_FAILED

Similar Messages

Maybe you are looking for