- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Job SAP_COLLECTOR_PERFMON_RSORACOL failure
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Job SAP_COLLECTOR_PERFMON_RSORACOL failure
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 08-21-2012 3:42 PM
Hi Experts,
Could anyone please share some details about background job 'SAP_COLLECTOR_PERFMON_RSORACOL' using program 'SWNC_TCOLL_STARTER' to collect oracle statistics.
First thing is that I cannot see this job released in system or any frequency of the cancellec background jobs. Not sure how it is running daily with DDIC.
Second doubt; is what exactly it calculates. I can see latest data present in DB02old despite this job failure. But DB02 is blank. Please advise whether these two are related. SMON IDs in table DB02_COLL_PLAN are active except only one. which we may try activate to bring data to DB02. But our first concern is to stop this job failure.
The issue started two weeks ago; when we upgraded our BW system to NW 7.3. Since then the above mentioned job is regularly failing. Before that; it was running fine. Job is failing with below error related to memory. But values of memeory parameters are enough and this issue does not arise in other jobs.
Job fails with below run time error
ategory ABAP Server Resource Shortage
untime Errors TSV_TNEW_PAGE_ALLOC_FAILED
ate and Time 08/20/2012 20:05:37
hort dump has not been completely stored (too big)
Short text
No more memory available to extend an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Please make a note of the actions and input which caused the error.
-
To resolve the problem, contact your
SAP system administrator.
Using transaction ST22 for ABAP dump analysis you can see and
administrate termination messages and retain them for longer periods.
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
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension
Amount of memory per user in extended memory (EM)
o abap/heap_area_total
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).
Error analysis
The internal table "???" could not be enlarged further. In order to
make error handling possible this table had to be deleted. This means
that the table will either be displayed further down or, if you go from
here to the ABAP Debugger, with 0 rows.
At the time of the interruption the following characteristics of the
internal table were ascertained:
Memory location: "Session memory"
Row width: 956
No. of rows: 0
Allocated rows: 4409004
Newly requested rows: 16 (in 275563 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 19730464
Extended memory (EM)........... 4001284624
Assigned memory (HEAP)......... 3891166864
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 18446744027572828144
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,
please use the following search criteria:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLSDBORA3" bzw. "LSDBORA3F05"
"DELETE_DUPLICATED_PARAMS"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem (short dump).
To obtain this, select "System->List->Save->Local File (unconverted)"
on the current screen.
2. A suitable hardcopy printout of the system log.
To obtain this, call the system log with Transaction SM21
and set the time interval to 10 minutes before and 5 minutes after
the short dump. In the display choose "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, choose "More Utilities->Upload/Download->Download" in the
Editor.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Please advise whether anyways th ememory used by this job can be reduced or deletion of any old stat files etc may help.
Thanks
Varun
- SAP Managed Tags:
- NW AS Java Administrator (NWA)
Accepted Solutions (0)
Answers (1)
Answers (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Varun,
Can you post little more information from the dump ? The next portions till what you have opied earlier.
What is the current system patch level ?
Regards,
Samik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Samik,
Which patch exactly is needed. The BW, BAsis and ABAP patches have verion 730 and patch level 7. Could you please advise on this job. What exactly the job does and how is it running multiple times daily buty I can't find it in released state in SM37.
The dump details are below
"
Category ABAP Server Resource Shortage
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 08/21/2012 04:12:36
Short dump has not been completely stored (too big)
Short text
No more memory available to extend an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Please make a note of the actions and input which caused the error.
-
To resolve the problem, contact your
SAP system administrator.
Using transaction ST22 for ABAP dump analysis you can see and
administrate termination messages and retain them for longer periods.
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
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension
Amount of memory per user in extended memory (EM)
o abap/heap_area_total
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.
o abap/heap_area_dia:
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
o abap/heap_area_nondia:
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
o em/initial_size_MB:
Extended memory area from which all users of an
application server can satisfy their memory requirement.
o abap/shared_objects_size_MB:
Size of the shared memory area that can be used to save shared
objects area instances. This memory area is global for all users
of the application server.
Error analysis
The internal table "???" could not be enlarged further. In order to
make error handling possible this table had to be deleted. This means
that the table will either be displayed further down or, if you go from
here to the ABAP Debugger, with 0 rows.
At the time of the interruption the following characteristics of the
internal table were ascertained:
Memory location: "Session memory"
Row width: 956
No. of rows: 0
Allocated rows: 4420620
Newly requested rows: 16 (in 276289 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 19730464
Extended memory (EM)........... 4001284624
Assigned memory (HEAP)......... 3963801712
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 18446744027572828144
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,
please use the following search criteria:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLSDBORA3" bzw. "LSDBORA3F05"
"DELETE_DUPLICATED_PARAMS"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem (short dump).
To obtain this, select "System->List->Save->Local File (unconverted)"
on the current screen.
2. A suitable hardcopy printout of the system log.
To obtain this, call the system log with Transaction SM21
and set the time interval to 10 minutes before and 5 minutes after
the short dump. In the display choose "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, choose "More Utilities->Upload/Download->Download" in the
Editor.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release..... 730
SAP Basis Level. 0007
Application server... "ushapsp701lg"
Network address...... "3.156.17.107"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 54
Shortdump setting.... "full"
"
regards
Varun
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Varun,
You are not seeing this job in released status because this is not explicitly scheduled. RSCOLL00 triggers this job after its run. Please refer to note 1300273 for more details.
This job is a DB02 collector, hence data is not correctly populated in your DB02.
Can you try to paste the complete dump details ?
Regards,
Samik
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Samik,
Complete dump details are below:
Category ABAP Server Resource Shortage
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 08/21/2012 10:05:46
Short text
No more memory available to extend an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Please make a note of the actions and input which caused the error.
-
To resolve the problem, contact your
SAP system administrator.
Using transaction ST22 for ABAP dump analysis you can see and
administrate termination messages and retain them for longer periods.
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
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension
Amount of memory per user in extended memory (EM)
o abap/heap_area_total
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.
o abap/heap_area_dia:
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
o abap/heap_area_nondia:
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
o em/initial_size_MB:
Extended memory area from which all users of an
application server can satisfy their memory requirement.
o abap/shared_objects_size_MB:
Size of the shared memory area that can be used to save shared
objects area instances. This memory area is global for all users
of the application server.
Error analysis
The internal table "???" could not be enlarged further. In order to
make error handling possible this table had to be deleted. This means
that the table will either be displayed further down or, if you go from
here to the ABAP Debugger, with 0 rows.
At the time of the interruption the following characteristics of the
internal table were ascertained:
Memory location: "Session memory"
Row width: 956
No. of rows: 0
Allocated rows: 4429340
Newly requested rows: 16 (in 276834 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 19730464
Extended memory (EM)........... 4001284624
Assigned memory (HEAP)......... 3998118176
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 18446744027572828144
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,
please use the following search criteria:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLSDBORA3" bzw. "LSDBORA3F05"
"DELETE_DUPLICATED_PARAMS"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem (short dump).
To obtain this, select "System->List->Save->Local File (unconverted)"
on the current screen.
2. A suitable hardcopy printout of the system log.
To obtain this, call the system log with Transaction SM21
and set the time interval to 10 minutes before and 5 minutes after
the short dump. In the display choose "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, choose "More Utilities->Upload/Download->Download" in the
Editor.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release..... 730
SAP Basis Level. 0007
Application server... "ushapsp701lg"
Network address...... "3.156.17.107"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 51
Shortdump setting.... "full"
Database server... "usushdbsp196"
Database type..... "ORACLE"
Database name..... "UBP"
Database user ID.. "SAPBIW"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 720
created (date)... "Mar 21 2012 09:27:32"
create on........ "SunOS 5.9 Generic_122300-28 sun4u"
Database version. "OCI_102, 11.2.0.2.0, V1, default"
Patch level. 201
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "SunOS 5.9, SunOS 5.10, SunOS 5.11"
Memory consumption
Roll.... 19730464
EM...... 4001284624
Heap.... 3998118176
Page.... 24576
MM Used. 7685428136
MM Free. 323535640
User and Transaction
Client.............. 100
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transaction ID...... "50335773BECA68E8E1000000039C116B"
EPP Whole Context ID.... "80212854B4421EE1BAF635E25E4B95DB"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "SAPLSDBORA3"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
Information on where terminated
Termination occurred in the ABAP program "SAPLSDBORA3" - in
"DELETE_DUPLICATED_PARAMS".
The main program was "RSORACOL ".
In the source code you have the termination point in line 196
of the (Include) program "LSDBORA3F05".
The program "SAPLSDBORA3" was started as a background job.
Job Name....... "SAP_COLLECTOR_PERFMON_RSORACOL"
Job Initiator.. "DDIC"
Job Number..... 10001800
Source Code Extract
Line SourceCde
166 data : wa_ora_param_temp like line of tab_ora_param_prev.
167 data : param_name(150), param_value(255) type c.
168 data : snap_id_prev type i.
169
170 data : prev_param(150) type c.
171 data : tab_as_string type string.
172 FIELD-SYMBOLS: <tab> TYPE ty_ora_param.
173
174
175 assign (tab_name) to <tab>.
176
177 clear wa_ora_param.
178 * sort tab_ora_param ASCENDING by paramname snap_id.
179 * move tab_ora_param to tab_ora_param_temp.
180 sort <tab> ASCENDING by paramname snap_id.
181 move <tab> to tab_ora_param_temp.
182
183 loop at tab_ora_param_temp into wa_ora_param_temp.
184
185 param_name = wa_ora_param_temp-paramname.
186 param_value = wa_ora_param_temp-new_value.
187 snap_id_prev = wa_ora_param_temp-snap_id + 1.
188
189 check param_name ne prev_param.
190
191 loop at <tab> into wa_ora_param
192 where snap_id >= snap_id_prev
193 and paramname = param_name .
194
195 if wa_ora_param-new_value eq param_value.
>>>>> delete <tab>.
197 endif.
198 param_value = wa_ora_param-new_value.
199 prev_param = param_name.
200 endloop.
201
202 endloop.
203
204 ENDFORM. " DELETE_DUPLICATED_PARAMS
205 *&---------------------------------------------------------------------*
206 *& Form AVOID_LOAD_ALL_PARAMS
207 *&---------------------------------------------------------------------*
208 * text
209 *----------------------------------------------------------------------*
210
211 FORM avoid_load_all_params .
212
213 data : param_name(150), param_value(255) type c.
214 data : tab_ora_param_temp type ty_ora_param.
215 data : tab_ora_param_visit type ty_ora_param.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 2
SY-DBCNT 65
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Oracle monitoring: DB02 collector
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20120821
SY-UZEIT 100258
SY-XPROG RSDBRUNT
SY-XFORM %_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
6 FORM SAPLSDBORA3 LSDBORA3F05 196
DELETE_DUPLICATED_PARAMS
5 FORM SAPLSDBORA3 LSDBORA3F05 94
COMPARE_PARAM_BETW_SNAPIDS
4 FORM SAPLSDBORA3 LSDBORA3F05 38
GET_ORA_PARAM_HIST
3 FUNCTION SAPLSDBORA3 LSDBORA3U40 50
ORA_COLL_DBA_HIST_PARAM2
2 FORM RSORACOL RSORACOL 193
DATA_COLLECTION
1 EVENT RSORACOL RSORACOL 75
START-OF-SELECTION
Chosen variables
Name
Val.
No. 6 Ty. FORM
Name DELETE_DUPLICATED_PARAMS
PARAM_NAME
O7_DICTIONARY_ACCESSIBILITY
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
4354445444455544445544444552222222222222222222222222222222222222222222222222222222222222222222
F7F49349FE129F133533929C9490000000000000000000000000000000000000000000000000000000000000000000
004F0037005F00440049004300540049004F004E004100520059005F00410043004300450053005300490042004900
PREV_PARAM
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000
WA_SE_GE_HI-TO
00000000
00000000
00000000
33333333
00000000
00300030003000300030003000300030
SNAP_ID_PREV
10001
0021
0071
00002711
<%_L035>
10001
0021
0071
00002711
<%_L036>
O7_DICTIONARY_ACCESSIBILITY
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
4354445444455544445544444552222222222222222222222222222222222222222222222222222222222222222222
F7F49349FE129F133533929C9490000000000000000000000000000000000000000000000000000000000000000000
004F0037005F00440049004300540049004F004E004100520059005F00410043004300450053005300490042004900
<TAB>
Table IT_20[4429326x956]
\FUNCTION-POOL=SDBORA3\DATA=TAB_ORA_PARAM
Table reference: 13
TABH+ 0(20) = 0000000108154400000000000000000000000000
TABH+ 20(20) = 0000000D000000140043960E000003BC000002B0
TABH+ 40(16) = 040000260004A92000042CC403000000
store = 0x0000000108154400
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 13 (0x0000000D)
label = 20 (0x00000014)
fill = 4429326 (0x0043960E)
leng = 956 (0x000003BC)
loop = 688 (0x000002B0)
xtyp = TYPE#000123
occu = 4 (0x00000004)
accKind = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniNo)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0x0000000108075C98
pgHook = 0xFFFFFFF754CA0EC0
idxPtr = 0xFFFFFFF755400178
id = 17 (0x00000011)
shmTabhSet = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4440060 (0x0043BFFC)
lineAlloc = 4429340 (0x0043961C)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x00000002)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
Internal notes
The termination was triggered in function "tsvItabCloneTableBody"
of the SAP kernel, in line 895 of the module
"//bas/720_REL/src/krn/runt/abtsv.c#8".
The internal operation just processed is "TDEL".
Internal mode was started at 20120821100258.
ABAP Control Blocks (CONT)
Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 Source Code Line
20120 4061
14869 LOOP 05 0000 8001 0072 C00A 0000 0000 0000 LSDBORA3F05 191
14873 BRAN 05 0019 LSDBORA3F05 191
14874 COMP 00 000A C00D C00B LSDBORA3F05 191
14876 BRAF 06 0003 LSDBORA3F05 191
14877 comp 00 02DB C00E C00C LSDBORA3F05 191
14879 BRAF 02 FFF6 LSDBORA3F05 191
14880 BREL 80 0000 LSDBORA3F05 191
14881 LOOP 10 0000 0000 0000 0000 0000 0000 0000 LSDBORA3F05 191
14885 comp 00 02DB 0345 C003 LSDBORA3F05 195
14887 BRAF 02 0006 LSDBORA3F05 195
14888 BREL 80 0000 LSDBORA3F05 195
>>>>> TDEL 00 0000 8001 0000 0000 0000 0000 0000 LSDBORA3F05 196
14893 move FF 01FE C003 0345 LSDBORA3F05 198
14895 move FF 012C C005 C002 LSDBORA3F05 199
14897 BRAX 01 FFE4 LSDBORA3F05 200
14898 BRAX 01 FFBD LSDBORA3F05 202
14899 ENDF 00 0000 LSDBORA3F05 204
14900 ---- 00 0000 LSDBORA3F05 204
14901 CPOP 00 0000 LSDBORA3F05 162
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi All,
SAP note 1274775 helped in the problem.
Note 1274775 - DBACockpit/DB02N: Big segment history/ many index partitions
Regards
Varun
- SAP Cloud ALM and Identity Authentication Service (IAS) in Technology Blogs by SAP
- Kyma Integration with SAP Cloud Logging. Part 2: Let's ship some traces in Technology Blogs by SAP
- [BIG PROBLEM] SAP Host Agent cannot connect to SYSTEMDB in Technology Q&A
- Consuming SAP with SAP Build Apps - Connectivity options for low-code development - part 2 in Technology Blogs by SAP
- Unable to log in to SAP BusinessObjects CMC in Technology Blogs by Members
| 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.