Runtime errors: TSV_TNEW_PAGE_ALLOC_FAILED

Question

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

Answer 1

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.