on 08-07-2014 4:07 PM
HI ,
The user is getting the TSV_TNEW_PAGE_ALLOC_FAILED error while running a some job
The amount of storage space (in bytes) filled at termination
Roll area...................... 6221072
Extended memory (EM)........... 2002738624
Assigned memory (HEAP)......... 3000059984
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 4294967295
he is getting this error while executing when ever he runs that job
HI Guys,
It is a standard archiving job ,I am pasting the job log for this.
Please check ..it is saying Log is full.
Job started
Step 001 started (program FI_DOCUMNT_WRI, variant WRI_RES_8490_1,
1 of the 1 company codes selected still have open periods
Archiving session 006372 is being created
Total of documents read/archived: 0/0
Total of documents read/archived: 108000/0
Total of documents read/archived: 210000/0
Total of documents read/archived: 340000/0
Total of documents read/archived: 457000/0
Path: /usr/sap/archive/APPL/
Name for new archive file: TPW910_FI_20140805_074110_FI_DOCUMNT
Total of documents read/archived: 587000/1
Total of documents read/archived: 742000/7
Total of documents read/archived: 894000/24
Message number 999999 reached. Log is full
Job cancelled after system exception ERROR_MESSAGE
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Did you look for related sap notes ?
Have a look at below:
1661074 - FI Archiving throws error BL252 "Message number 999999 reached. Log is full"
Divyanshu
Hi,
Sometimes, jobs get failed because of bigger selection range. You can ask the user if he can breakdown the range in smaller chunks under 2-3 variants(as required) . He can keep these variants in same job.
Regards,
Anjali.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
system, job name, full dump, logs ?
Please provide complete details on this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is a z job of some archiving for PP_Order
For this user only we are getting this error for that perticular job.
The systme is ECC 6.0 Ehp6 oracle database .
SAP kernel....... 720
Memory consumption is
Roll.... 6221072
EM...... 2002738624
Heap.... 3000059984
Page.... 32768
MM Used. 4737199616
MM Free. 254668992
These are the current peremeters which were configured
abap/buffersize 2000000
em/initial_size_MB 40960http://
ztta/roll_extension 2000000000
ztta/roll_area 7000000
abap/heap_area_nondia 3000000000
in our system.
================
Category Resource Shortage
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 05.08.2014 16:44:40
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|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) |
| 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. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| The internal table "\FUNCTION-POOL=SCD5\DATA=DATA_TAB_POS" 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: 1568 |
| Number of rows: 424196 |
| Allocated rows: 424196 |
| Newly requested rows: 8 (in 1 blocks) |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 6221072 |
| Extended memory (EM)........... 2002738624 |
| Assigned memory (HEAP)......... 3000059984 |
| Short area..................... " " |
| Paging area.................... 32768 |
| 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
Hi SAP basis,
While executing any archiving jobs ensure that it is done during night time or low load period for following reasons
- Avoid system performance
- System get sufficient resources to process the jobs
Few suggestion based on dump
- Reduce the selection data
- Execute the jobs when there are very minimal system load
- Execute if on the app server having enough system resource. Change the executing server of background jobs accordingly.
Regards,
Deepak Kori
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.