0FI_AR_4 - Slow Sequential Read in ECC on Initial Load

Hi everyone,
We are using DataSource 0FI_AR_4. Our plug-in is PI2004.1.500. Support
pack level is 18. When we execute the initialisation from BW then we
experience poor run times against table BSAD. Through SM50 in ECC we
can see that this is doing a sequential read on view BKPF_BSAD as per
below. We have reviewed notes 641977, 760973 and 798536 and created
index 6 as instructed. This has made no difference.
The DataSource only allows us to select on Company Code and Fiscal
Year/Period so we can understand why the extract would be slow as the ECC read uses BUDAT and CPUDT. Unless the Fiscal Year/Period is somehow translated to BUDAT.
An extract of 80000 records takes 1hr 10 mins. We may have 4 to 5 million records to load.
Has anyone come across this problem before?
SELECT
"AUGBL" , "AUGDT" , "BELNR" , "BLART" , "BLDAT" , "BSCHL" , "BSTAT" ,
"BUDAT" , "BUKRS" , "BUZEI" ,
"CPUDT" , "DMBTR" , "FILKD" , "GJAHR" , "HKONT" , "KKBER" , "KUNNR" ,
"MABER" , "MADAT" , "MANSP" ,
"MANST" , "MONAT" , "MSCHL" , "REBZG" , "REBZJ" , "REBZZ" , "RSTGR" ,
"SAKNR" , "SGTXT" , "SHKZG" ,
"SKFBT" , "SKNTO" , "UMSKS" , "UMSKZ" , "VBELN" , "WAERS" , "WRBTR" ,
"WSKTO" , "XARCH" , "XBLNR" ,
"XNEGP" , "XREF1" , "XREF2" , "XREF3" , "ZBD1P" , "ZBD1T" , "ZBD2P" ,
"ZBD2T" , "ZBD3T" , "ZFBDT" ,
"ZLSCH" , "ZLSPR" , "ZTERM" , "ZUONR"
FROM
"BKPF_BSAD"
WHERE
"MANDT" = :A0 AND "BUKRS" IN ( :A1 , :A2 ) AND "BUDAT" BETWEEN :A3
AND :A4 AND "CPUDT" BETWEEN :A5 AND
:A6#

Hi,
you could try to trace the database access and check if the index is used for reading. Depending on that you can create an more appropriate index.
Did you also activate index 5?
Also an option would be to do paralell initializations based on company code.

Similar Messages

Sequential read in sm66 - Database size 550GB - system slow for users

Hello,
Currently when we use any standard transactions or custom program, it is going to sequential read in sm66.
We are getting slowness in system due to this issue for users.
Sm66 log:
sapXX01_XXX_00 0 DIA     12873 Running            Yes                  6 XIRFC    ZCL_WM_S Sequential Read MARD
sapXX01_XXX_00 20 BTC     16155 Running            Yes                 15 Zuser1 ZCL_SD_D Sequential Read LTAP
sapXX01_XXX_00 29 SPO     12018 Running            Yes                 12 Zuser1   print 35
sapXX01_XXX_00 30 SPO     12037 Running            Yes                 12 Zuser1   print 35
sapXX01_XXX_00 31 SPO     12041 Running            Yes                 12 SAPSYS   querying
sapXX02_XXX_02 3 DIA     15098 Running            Yes                714 Zuser2 ZCL_IM_B
sapXX02_XXX_02 4 DIA      8158 Running            Yes                 38 Zuser2 RWRPLPRO Sequential Read WRPL
sapXX02_XXX_02 6 DIA      8160 Running            Yes                555 Zuser3 ZCL_IM_B
sapXX03_XXX_03 0 DIA      1969 Running            Yes               2390 Zuser5 SAPLFAGL Sequential Read BSIS
sapXX03_XXX_04 0 BTC     10811 Running            Yes                209 Zuser6   ZCL_SD_D Sequential Read LTA
Database: Maxdb
OS: Linux
I understand that if you create Index on these table ( whichever it shows as sequential read ), it will improve the report performance.
Most of the time, system process shows that sequential read on VBAP, VKPA (sales tables), purchase tables, Finance tables and etc.
If sm66 shows as sequential read for few table, that means that corresponding user will get slowness on getting report/transaction output. I agree on that.
Is there any reason other user will get slowness ie if i run Va03 transaction, WE02 transaction which is not relevant to sm66 process over view.
I appreciate, if you give some recommendations reg. this performance improvement and to avoid this kind of sequential read.
I posted the Same question in DB forum also.
I want to get some more idea from this forum also. That is reason, i posted here again.
Thanks
Praba

Hi Volker,
Thanks for your reply.
We have three application server instance ie 00, 02, 03,   -
04 (enque server)
1) This parameter value on 00 instance ie : rdisp/wp_no_spo - Number of spool work processes
Dflt value - 0
ProfileVa - 1
Current value - 1
Minimum - Nothing
Maximum - 100
2) his parameter value on 02 instance ie : rdisp/wp_no_spo - Number of spool work processes
Dflt value - 0
ProfileVa - 1
Current value - 1
Minimum - Nothing
Maximum - 100
3) his parameter value on 03 instance ie : rdisp/wp_no_spo - Number of spool work processes
Dflt value - 0
ProfileVa - 1
Current value - 1
Minimum - Nothing
Maximum - 100

Query running very slow with db file sequential read waits which all indexes would be recommended

My query is doing lot of db file sequential reads I want to create few indexes and extended stats please help me with your suggestions.
Can anybody suggest I am unable to paste my query here -don't know why it's not getting pasted--is it not permitted ?
thank you.

The simplest way to find it out is using Oracle Enterprise Manager. Just locate the SQL ID for the SQL and run "SQL tuning advisor". This will exactly pinpoint where do you need to create indexes etc. Another option is manually running explain plan for the SQL and finding out which predicate is causing full scans with high i/o
Regards
Tushar

MacBook Pro (mid 2010) - Slow Startup and Initial Load of Apps after Mavericks Install

Hello everyone,
Long time Snow Leopard user here. I've been absolutely, 100% thrilled with my MBP's performance / speed since mid 2010. Since installing Mavericks I've noticed two things:
1. Initial on boot load times seem much slower
2. The first time you open an app (Safari, even TextEdit) is far slower than in Snow Leopard.
Now granted, once the computer has been on for about 5 minutes, and once you've had an application open for 1-2 minutes, than performance is okay once again. But it seems that quite literally everytime you do "anything" for the first time since the computer has been turned on you run the risk of a spinning beachball and an extended wait. This simply never happened in Snow Leopard.
I'm not a computer science major but I do understand that when you do something for the first time since a reboot it will need to load new files into the RAM which takes time. However, I've been using this computer since 2010 and have never experienced this behavior / speed / delay, etc... something seems fundamentally different.
For example, even just opening finder, and navigating to the Applications folder results in sluggish behavior the first time. Also, anytime you first click the top menu bar in an application you run the risk of a beachball.
It doesn't seem like a failing hard drive because I can read/write large chunks of data one an app is finally loaded. It's just initially loading the app takes quite literally 10-20 times longer than Snow Leopard. It seems like perhaps Mavericks itself, the core of the new OS was perhaps installed in a bad sector of the HD, but none of my other files are on bad sectors... if that makes sense. Again - I'm not a computer science major so I'm largely just making things up
It also seems as if multitasking and switching between several open apps has seen a decrease in performance. Could it be that perhaps Mavericks RAM management is superior to Snow Leopard, but only if there is a TON of RAM to go around? Could it be as simple as Macs with only 4GB installed should not be allowed to even install Mavericks?
Does this sound normal for Mavericks considering I have a C2D processor, a non SSD, and only 4GB ram? I know those specs are "outdated" for 2014, but keep in mind these were the specs that I've always had and with Snow Leoapard I was consistently thrilled with the speed of the computer.
I suppose my question is: should my strategy be to simply turn the computer on, get a cup of coffee and let everything load and maybe even have my frequently used apps load on startup, etc... and carry on as normal? Does something seem off? Should I invest in a new SSD / RAM upgrade? I know the upgrades couldn't hurt, but the issue is that I was perfectly content until upgrading to Mavericks
I've tried booting into OS X Recovery mode and using the Disk Utility. I've tried Safe Mode. I've included a "EtreCheck" report below. I'm open to any ideas / suggestions.
Thanks!!
Hardware Information:
 MacBook Pro (13-inch, Mid 2010)
 MacBook Pro - model: MacBookPro7,1
 1 2.4 GHz Intel Core 2 Duo CPU: 2 cores
 4 GB RAM
Video Information:
 NVIDIA GeForce 320M - VRAM: 256 MB
System Software:
 OS X 10.9.1 (13B42) - Uptime: 0 days 0:10:48
Disk Information:
 Hitachi HTS545025B9SA02 disk0 : (250.06 GB)
 EFI (disk0s1) <not mounted>: 209.7 MB
 Macintosh HD (disk0s2) / [Startup]: 249.2 GB (228.46 GB free)
 Recovery HD (disk0s3) <not mounted>: 650 MB
 MATSHITADVD-R UJ-898
USB Information:
 Apple Inc. Built-in iSight
 Apple, Inc. Keyboard Hub
 Logitech USB Receiver
 Apple Inc. Apple Keyboard
 Apple Internal Memory Card Reader
 Apple Inc. BRCM2046 Hub
 Apple Inc. Bluetooth USB Host Controller
 Apple Computer, Inc. IR Receiver
 Apple Inc. Apple Internal Keyboard / Trackpad
FireWire Information:
Thunderbolt Information:
Launch Daemons:
 [System] com.adobe.fpsaud.plist 3rd-Party support link
Launch Agents:
 [System] com.adobe.AAM.Updater-1.0.plist 3rd-Party support link
 [System] com.adobe.AdobeCreativeCloud.plist 3rd-Party support link
User Launch Agents:
 [not loaded] com.adobe.AAM.Updater-1.0.plist 3rd-Party support link
 [not loaded] com.google.keystone.agent.plist 3rd-Party support link
User Login Items:
 None
Internet Plug-ins:
 FlashPlayer-10.6: Version: 11.9.900.152 - SDK 10.6 3rd-Party support link
 Flash Player: Version: 11.9.900.152 - SDK 10.6 Outdated! Update
 QuickTime Plugin: Version: 7.7.3
 JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Outdated! Update
 AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 3rd-Party support link
 Default Browser: Version: 537 - SDK 10.9
Audio Plug-ins:
 BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
 AirPlay: Version: 1.9 - SDK 10.9
 AppleAVBAudio: Version: 2.0.0 - SDK 10.9
 iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
 Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes:
 Flash Player 3rd-Party support link
Old Applications:
 None
Time Machine:
 Time Machine not configured!
Top Processes by CPU:
 4% WindowServer
 1% EtreCheck
 0% mds
 0% mds_stores
 0% airportd
Top Processes by Memory:
 111 MB com.apple.IconServicesAgent
 94 MB Finder
 57 MB Dock
 53 MB SystemUIServer
 53 MB EtreCheck
Virtual Memory Information:
 1.64 GB Free RAM
 1.42 GB Active RAM
 314 MB Inactive RAM
 390 MB Wired RAM
 316 MB Page-ins
 0 B Page-outs

Wish I could be of some help, but I'm having similar issues on my mid 2011 macbook pro with 8 GB ram. It's very frustrating. I haven't worked on a computer this slow since the early 90's. Even simple things like signing in to this site bring up the beach ball for maybe ten seconds. When opening up apps I often have to wait minutes, and often end up force quitting when they hang. I'm using force quit a dozen or more times a day, when it used to be very rare.
I don't know if it's Mavericks. I installed a new hard drive in November, but the problems really started getting bad since the latest upgrade.
It's not just opening apps. If I have an app open in the background and switch to it I have similar issues. Watching a simple video is often accompanied by stalls and delays - which is really bad as I'm often using the laptop to edit video. It's become unuseable for work.
Perhaps the most frustrating is clicking on a link, only to find Safari decides to complete a previous scroll that it had paused. The page jumps down, and sometimes I end up clicking on a link I didn't want. Then I have to wait for THAT spinning beach ball before I can go back to the previous spinning beach ball.
It can take up to ten minutes to restart. I've tried everything I could find on these pages so far, and nothing has worked.
I thought maybe it was something I've done (and perhaps it is), but I keep seeing others with similar issues.

Long time to load data from PSA to DSO / CUBE. Sequential read RSBKDATA_V

Hi Gurus
The process stays for several hours on sequential read from RSBKDATA_V - temporary storage for DTPs.
After several hours, the processing finally starts, but even when I assign several BGDs to the DTP it takes hours to load the data.
We have BI7.0 with SP22, so all relevant notes are already implemented.
Does any one had similar problem, please?
Thanks in advance
Martin

Hi Martin,
this issue has cropped up a few times. Please check and implement the following notes:
1338465    P22:DTP:LOG: Performance problem when messages are added +
1331544    P22:HINT:Slow performance when accessing RSMONFACT +
1312701    70SP21: Performance on view RSBKDATA_V selects
1304234    70SP21: Performance on the hashed table p_th_rsbkdata_v **
1168098    70SP19: Performance during DataStore object extraction
1080027    70SP16: Performance during parallel processing
These notes should improve the performance of the DTPs in your system.
After you've added the notes, please check in tables RSBKDATA and RSBKDATAINFO whether they contain any data. If the tables are empty, please reorganise the tables, and restart the dtp.
Hope this helps you.
Rgds,
Colum

Possible Sequential Read Access for a Sorted Table

Hi All,
I have the following warnings in Code inspector check.
'Possible Sequential Read Access for a Sorted Table'
Kindly provide me the solution to overcome this warning message.
This is my code in BAdi : CRM_ORDER_FIELDCHECK , Method : FIELDCHECK
I am getting the above warning at
READ TABLE lt_status INTO ls_status WITH KEY status = 'E0001'
 user_stat_proc = 'ZITRHDQT'
 object_type = 'BUS2000114'.
and at
 MODIFY ct_input_field_names FROM ls_input_field_names
 TRANSPORTING changeable
 WHERE fieldname NE lv_field.
Please see the below code .
DATA : lt_header_guid TYPE crmt_object_guid_tab,
 lt_item_guid TYPE crmt_object_guid_tab,
 lt_order_i TYPE crmt_orderadm_i_wrkt,
 ls_order_i LIKE LINE OF lt_order_i,
 lt_status TYPE crmt_status_wrkt,
 ls_status LIKE LINE OF lt_status,
 ls_input_field_names TYPE crmt_input_field_names.
DATA : lv_header_guid TYPE crmt_fieldcheck_com-guid,
 lv_chng_no TYPE c VALUE 'A',
 lv_field(10) TYPE c VALUE 'ACT_STATUS'.
DATA: lv_status_completed TYPE crmt_boolean.
To Get GUID
IF is_fieldcheck_com-guid IS NOT INITIAL.
 lv_header_guid = is_fieldcheck_com-guid.
ELSE.
 lv_header_guid = is_fieldcheck_com-ref_guid.
ENDIF.
IF is_fieldcheck_com-ref_kind EQ 'A'.
 INSERT lv_header_guid INTO TABLE lt_header_guid.
 ELSE.
 SELECT SINGLE header FROM crmd_orderadm_i INTO lv_header_guid
 WHERE guid = is_fieldcheck_com-ref_guid.
 INSERT lv_header_guid INTO TABLE lt_header_guid.
ENDIF.
*To Get the required details
CALL FUNCTION 'CRM_ORDER_READ'
 EXPORTING
 it_header_guid = lt_header_guid
 IMPORTING
 et_status = lt_status
 EXCEPTIONS
 document_not_found = 1
 error_occurred = 2
 document_locked = 3
 no_change_authority = 4
 no_display_authority = 5
 no_change_allowed = 6
 OTHERS = 7.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE lt_status INTO ls_status WITH KEY status = 'E0001'
 user_stat_proc = 'ZITRHDQT'
 object_type = 'BUS2000114'.
IF sy-subrc = 0.
 ls_input_field_names-changeable = lv_chng_no.
 MODIFY ct_input_field_names FROM ls_input_field_names
 TRANSPORTING changeable
 WHERE fieldname NE lv_field.
ENDIF.
ENDMETHOD.
Regards
Venkat

Hello Blake,
Try this:
READ TABLE lt_action_fld WITH KEY STATUS = '0' BINARY SEARCH.
wf_index = sy-tabix.
loop at lt_action_fld from wf_index.
if lt_action_fld-status ne '0'.
exit.
endif.
delete lt_action_fld index wf_index.
endloop.
Let us know, if this helps.
Rgds,
Raghu.

Query navigation - no sequential read but too long time in SAPLRRK0

Hello guys, I need your help, please!
I've created a Query an appropriate aggregates. A test in RSRT with navigation shows a runtime of 300 ses. which I find OK, if I take into consideration the number ao records.
When I start the query in Analyser and have a look in SM50, I see the sequential read processes for some short time and then htere is a process SAPLRRK0 which takes about 18 minutes (!!!). Only after tis process terminates I receive the results in Analyser.
I cannot understand why the query runs so quick in RSRT and so slow in Analyser (OK, Excel takes time to formate the cells) - but why does the process SAPLRRK0 take so much runtime?
Thanks!

Dear friend
How to solve this problem with the report SAPLRRK0.
Thanks
Cristopher

Query on dba_free_space ends in wait by event db file sequential read

Hello All,
Env: 10gR2 on WinNT
I gave the query
select tablespace_name,sum(bytes)/1024/1024 from dba_free_space group by tablespace_name and its waiting for ever.
I checked the wait event from v$session and its "db file sequential read".
I put a trace on the session before the running the above query:
OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.06       0.06          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        0      0.00       0.00          0          0          0           0
total        2      0.06       0.06          0          0          0           0
Misses in library cache during parse: 1
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
db file sequential read                     13677        0.16        151.34
SQL*Net message to client                       1        0.00          0.00
db file scattered read                        281        0.01          0.53
latch: cache buffers lru chain                  2        0.00          0.00
OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
call     count       cpu    elapsed       disk      query    current        rows
Parse    13703      0.31       0.32          0          0          0           0
Execute 14009      0.75       0.83          0          0          0           0
Fetch    14139      0.48       0.74         26      56091          0       15496
total    41851      1.54       1.89         26      56091          0       15496
Misses in library cache during parse: 16
Misses in library cache during execute: 16
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
db file sequential read                        26        0.00          0.12
    1 user SQL statements in session.
14010 internal SQL statements in session.
14011 SQL statements in session.I took the AWR Report (for 1 hr time period) and the top 5 events came out as,
Event                                 Waits    Time (s)   (ms)   Time Wait Class
db file sequential read           1,134,643       7,580      7   56.8   User I/O
db file scattered read              940,880       5,025      5   37.7   User I/O
CPU time                                            967           7.2
control file sequential read          4,987           3      1    0.0 System I/O
control file parallel write           2,408           1      1    0.0 System I/O The PHYRDS(from dba_hist_filestatxs) on my system01.dbf is 161,028,980 for the latest snap.
Could someone throw some light into what is happening here ?
TIA,
JJ

Under some circumstances querying the dictionary can be slow, usually because of problems with bad execution plans related to bad statistics, try to gather statistics using dbms_stats.gather_fixed_objects_stats(); it has worked for me before.
You can also read Note 414256.1 Poor Performance For Tablespace Page Display In Grid Control Console which in addition points to a possible problem with the recycle bin.
HTH
Enrique

Initial load gets slower and slower

For a PoC I tried to use the internal goldengate mechanism for initial load. The size of the table is about 500 mb in total but over time the load is decreasing. Starting with nearly 1000 rows per second after one hour I was down to 50 Rows per hour and again decreasing down to not more than 10 rows per hour. So the entire load took 15 hours!
There is only a primary key on the target table and no other constraints.
Any idea?

Same thing happens performance-wise on imports: starts off pretty fast, then starts to slow down. Can you rebuild/enable the PK index after the load is done? That should be a safe operation, give that your source has a PK. Are you sure there aren't any other constraints (or triggers) on the target table?
Plus (assuming you are a DBA), what does AWR (or statspack, or tracing) show for wait events?

Sequential read of DD03L table is taking forever during SP install

Hello SDN
I'm applying some SP to my vanilla ECC install with Max DB.
Whenever I apply another set of SP or even SPAM update it inevitable hits a sequential read of table DD03L. And it takes forever to go throught it. It is a 1.5 Gb table.
I updated statistics for the DB in DB50 and applied notes 791984, 1015068 and 1022755 as described in note 822379.
I am running the latest kernel, dw set, tp and r3trans files
I still need to apply the whole Stack 7 and 8 for the whole ECC 6.0 and I'm afraid the table will keep growing.
Has anyone ran into the same issue?
Any suggestions how to make this process faster?
Thanks
MR

Hey,
The table DD03L is quite large,
however the upgrade should not take forever.
I think you should create a DB trace,
and find the problematic SQL statements,
When you have those long running statements,
you might be able to improve their performance (for example, create an index).

Log file sequential read and RFS ping/write - among Top 5 event

I have situation here to discuss. In a 3-node RAC setup which is Logical standby DB; one node is showing high CPU utilization around 40~50%. The CPU utilization was less than 20% 10 days back but from 9th oldest day it jumped and consistently shows the double figure. I ran AWR reports on all three nodes and found one node with high CPU utilization and shows below tops events-
EVENT WAITS TIME(S) AVG WAIT(MS) %TOTAL CALL TIME WAIT CLASS
CPU time 5,802 34.9
RFS ping 15 5,118 33,671 30.8 Other
Log file sequential read 234,831 5,036 21 30.3 System I/O
Sql*Net more data from
client 24,171 1,087 45 6.5 Network
Db file sequential read 130,939 453 3 2.7 User I/O
Findings:-
On AWR report(file attached) for node= sipd207; we can see that "RFS PING" wait event takes 30% of the waits and "log file sequential read" wait event takes 30% of the waits that occurs in database.
Environment :- (Oracle- 10.2.0.4.0, O/S - AIX .3)
1)other node awr shows "log file sync" - is it due to oversized log buffer?
2)Network wait events can be reduced by tweaking SDU & TDU values based on MDU.
3) Why ARCH processes taking much to archives filled redo logs; is it issue with slow disk I/O?
Regards
WORKLOAD REPOSITORY report for<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<DB Name DB Id Instance Inst Num Release RAC Host
XXXPDB 4123595889 XXX2p2 2 10.2.0.4.0 YES sipd207
Snap Id Snap Time Sessions Curs/Sess
Begin Snap: 1053 04-Apr-11 18:00:02 59 7.4
End Snap: 1055 04-Apr-11 20:00:35 56 7.5
Elapsed: 120.55 (mins)
DB Time: 233.08 (mins)
Cache Sizes
~~~~~~~~~~~ Begin End
Buffer Cache: 3,728M 3,728M Std Block Size: 8K
Shared Pool Size: 4,080M 4,080M Log Buffer: 14,332K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 245,392.33 10,042.66
Logical reads: 9,080.80 371.63
Block changes: 1,518.12 62.13
Physical reads: 7.50 0.31
Physical writes: 44.00 1.80
User calls: 36.44 1.49
Parses: 25.84 1.06
Hard parses: 0.59 0.02
Sorts: 12.06 0.49
Logons: 0.05 0.00
Executes: 295.91 12.11
Transactions: 24.43
% Blocks changed per Read: 16.72 Recursive Call %: 94.18
Rollback per transaction %: 4.15 Rows per Sort: 53.31
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.99 Redo NoWait %: 100.00
Buffer Hit %: 99.92 In-memory Sort %: 100.00
Library Hit %: 99.83 Soft Parse %: 97.71
Execute to Parse %: 91.27 Latch Hit %: 99.79
Parse CPU to Parse Elapsd %: 15.69 % Non-Parse CPU: 99.95
Shared Pool Statistics Begin End
Memory Usage %: 83.60 84.67
% SQL with executions>1: 97.49 97.19
% Memory for SQL w/exec>1: 97.10 96.67
Top 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
CPU time 4,503 32.2
RFS ping 168 4,275 25449 30.6 Other
log file sequential read 183,537 4,173 23 29.8 System I/O
SQL*Net more data from client 21,371 1,009 47 7.2 Network
RFS write 25,438 343 13 2.5 System I/O
RAC Statistics DB/Inst: UDAS2PDB/udas2p2 Snaps: 1053-1055
Begin End
Number of Instances: 3 3
Global Cache Load Profile
~~~~~~~~~~~~~~~~~~~~~~~~~ Per Second Per Transaction
Global Cache blocks received: 0.78 0.03
Global Cache blocks served: 1.18 0.05
GCS/GES messages received: 131.69 5.39
GCS/GES messages sent: 139.26 5.70
DBWR Fusion writes: 0.06 0.00
Estd Interconnect traffic (KB) 68.60
Global Cache Efficiency Percentages (Target local+remote 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer access - local cache %: 99.91
Buffer access - remote cache %: 0.01
Buffer access - disk %: 0.08
Global Cache and Enqueue Services - Workload Characteristics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg global enqueue get time (ms): 0.5
Avg global cache cr block receive time (ms): 0.9
Avg global cache current block receive time (ms): 1.0
Avg global cache cr block build time (ms): 0.0
Avg global cache cr block send time (ms): 0.1
Global cache log flushes for cr blocks served %: 2.9
Avg global cache cr block flush time (ms): 4.6
Avg global cache current block pin time (ms): 0.0
Avg global cache current block send time (ms): 0.1
Global cache log flushes for current blocks served %: 0.1
Avg global cache current block flush time (ms): 5.0
Global Cache and Enqueue Services - Messaging Statistics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg message sent queue time (ms): 0.1
Avg message sent queue time on ksxp (ms): 0.6
Avg message received queue time (ms): 0.0
Avg GCS message process time (ms): 0.0
Avg GES message process time (ms): 0.1
% of direct sent messages: 31.57
% of indirect sent messages: 5.17
% of flow controlled messages: 63.26
Time Model Statistics DB/Inst: UDAS2PDB/udas2p2 Snaps: 1053-1055
-> Total time in database user-calls (DB Time): 13984.6s
-> Statistics including the word "background" measure background process
time, and so do not contribute to the DB time statistic
-> Ordered by % or DB time desc, Statistic name
Statistic Name Time (s) % of DB Time
sql execute elapsed time 7,270.6 52.0
DB CPU 4,503.1 32.2
parse time elapsed 506.7 3.6
hard parse elapsed time 497.8 3.6
sequence load elapsed time 152.4 1.1
failed parse elapsed time 19.5 .1
repeated bind elapsed time 3.4 .0
PL/SQL execution elapsed time 0.7 .0
hard parse (sharing criteria) elapsed time 0.3 .0
connection management call elapsed time 0.3 .0
hard parse (bind mismatch) elapsed time 0.0 .0
DB time 13,984.6 N/A
background elapsed time 869.1 N/A
background cpu time 276.6 N/A
Wait Class DB/Inst: UDAS2PDB/udas2p2 Snaps: 1053-1055
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc
Avg
%Time Total Wait wait Waits
Wait Class Waits -outs Time (s) (ms) /txn
System I/O 529,934 .0 4,980 9 3.0
Other 582,349 37.4 4,611 8 3.3
Network 279,858 .0 1,009 4 1.6
User I/O 54,899 .0 317 6 0.3
Concurrency 136,907 .1 58 0 0.8
Cluster 60,300 .0 41 1 0.3
Commit 80 .0 10 130 0.0
Application 6,707 .0 3 0 0.0
Configuration 17,528 98.5 1 0 0.1
Wait Events DB/Inst: UDAS2PDB/udas2p2 Snaps: 1053-1055
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc (idle events last)
Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
RFS ping 168 .0 4,275 25449 0.0
log file sequential read 183,537 .0 4,173 23 1.0
SQL*Net more data from clien 21,371 .0 1,009 47 0.1
RFS write 25,438 .0 343 13 0.1
db file sequential read 54,680 .0 316 6 0.3
DFS lock handle 97,149 .0 214 2 0.5
log file parallel write 104,808 .0 157 2 0.6
db file parallel write 143,905 .0 149 1 0.8
RFS random i/o 25,438 .0 86 3 0.1
RFS dispatch 25,610 .0 56 2 0.1
control file sequential read 39,309 .0 55 1 0.2
row cache lock 130,665 .0 47 0 0.7
gc current grant 2-way 35,498 .0 23 1 0.2
wait for scn ack 50,872 .0 20 0 0.3
enq: WL - contention 6,156 .0 14 2 0.0
gc cr grant 2-way 16,917 .0 11 1 0.1
log file sync 80 .0 10 130 0.0
Log archive I/O 3,986 .0 9 2 0.0
control file parallel write 3,493 .0 8 2 0.0
latch free 2,356 .0 6 2 0.0
ksxr poll remote instances 278,473 49.4 6 0 1.6
enq: XR - database force log 2,890 .0 4 1 0.0
enq: TX - index contention 325 .0 3 11 0.0
buffer busy waits 4,371 .0 3 1 0.0
gc current block 2-way 3,002 .0 3 1 0.0
LGWR wait for redo copy 9,601 .2 2 0 0.1
SQL*Net break/reset to clien 6,438 .0 2 0 0.0
latch: ges resource hash lis 23,223 .0 2 0 0.1
enq: WF - contention 32 6.3 2 62 0.0
enq: FB - contention 660 .0 2 2 0.0
enq: PS - contention 1,088 .0 2 1 0.0
library cache lock 869 .0 1 2 0.0
enq: CF - contention 671 .1 1 2 0.0
gc current grant busy 1,488 .0 1 1 0.0
gc current multi block reque 1,072 .0 1 1 0.0
reliable message 618 .0 1 2 0.0
CGS wait for IPC msg 62,402 100.0 1 0 0.4
gc current block 3-way 998 .0 1 1 0.0
name-service call wait 18 .0 1 57 0.0
cursor: pin S wait on X 78 100.0 1 11 0.0
os thread startup 16 .0 1 53 0.0
enq: RO - fast object reuse 193 .0 1 3 0.0
IPC send completion sync 652 99.2 1 1 0.0
local write wait 194 .0 1 3 0.0
gc cr block 2-way 534 .0 0 1 0.0
log file switch completion 17 .0 0 20 0.0
SQL*Net message to client 258,483 .0 0 0 1.5
undo segment extension 17,282 99.9 0 0 0.1
gc cr block 3-way 286 .7 0 1 0.0
enq: TM - contention 76 .0 0 4 0.0
PX Deq: reap credit 15,246 95.6 0 0 0.1
kksfbc child completion 5 100.0 0 49 0.0
enq: TT - contention 141 .0 0 2 0.0
enq: HW - contention 203 .0 0 1 0.0
RFS create 2 .0 0 115 0.0
rdbms ipc reply 339 .0 0 1 0.0
PX Deq Credit: send blkd 452 20.1 0 0 0.0
gcs log flush sync 128 32.8 0 2 0.0
latch: cache buffers chains 128 .0 0 1 0.0
library cache pin 441 .0 0 0 0.0
Wait Events DB/Inst: UDAS2PDB/udas2p2 Snaps: 1053-1055
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc (idle events last)

We only apply on one node in a cluster so I would expect that the node running SQL Apply would have much higher usage and waits. Is this what you are asking?
Larry

Need fix for db file sequential read

Hi all,
My db is 10.2.0.3.0 on windows. One of our query is very slow. When I checked for the reason from v$session the wait event is db file sequential read. Generated ash report and checked. Report listed one file id(p1), block id(p2), and number of blocks -1(p3). And other objects in the top objects. So how u can fix this now. Does I need to pin the block in the buffer cache..? Or does I need to to pin that complete object. Please suggest. I need to fix this.
Thanks a lot..

962013 wrote:
Yes it is not issue, but yesterday query was running fine and today it is getting late. then what could be the reason to getting slow.
We was having standby database and we performed switch over. and now on the primary database (previously standby) query is running and getting slow. I guess this is reason.
So is there any action that we can take to minimize this issue. Please suggest...
Thanks
HOW To Make TUNING request
https://forums.oracle.com/forums/thread.jspa?threadID=2174552#9360003

Error in Initial Load of Products from ECC to CRM

Hi ,
Im getting below errors In initial load of MATERIAL from ECC to CRM.
Data cannot be maintained for set type COMM_PR_MAT
Data cannot be maintained for set type COMM_PR_UNIT
Data cannot be maintained for set type COMM_PR_SHTEXT
My Analysis is
I found these set types are already assigned in other base category and around 100+ materials are created using this base category.
After initial load of DNL_CUST_PROD1, i found these set types are not assigned to any of the categories of hierarchy R3PRODSTYP. Since R3PRODSTYP is not having above set types, my initial load is failing.
Required Solution
Is there any other way, I can download materials from ECC to CRM, with out deleting the existing materials and Z hierarchy created earlier from CRM.
Regards,
Prasad
Message was edited by:
SAP CRM

Hi there,
Try to attach the Set Types:
"COMM_PR_MAT", "COMM_PR_UNIT", "COMM_PR_SHTEXT", COMM_PR_BATCH, COMM_PR_LGTEXT, COMM_PR_LGTEXT1,COMM_PR_LGTEXT2,
to the Category "MAT_" and then run the Initial load again.
It should work now unless you have some other issues.
Best regards,
Pankaj S.

How can I make SP install faster? 1.5 GB table sequential read DD03L

Hello SDN
I'm applying some SP to my vanilla ECC install with Max DB.
Whenever I apply another set of SP it inevitable hits a sequential read of table DD03L. And it takes forever to go throught it.
I update statistics for the DB in DB50 and applied notes 791984, 1015068 and 1022755 as described in note 822379.
I am running the latest kernel, dw set, tp and r3trans files
Any suggestions?
Thanks
MR

Hi MR,
there might be too much going on to post here. As you are an SAP customer, please open a message in the MAXDB component, and open the R/3 service connection.
Thanks,
Ashwath

Query occasionally causes table scans (db file sequential read)

Dear all,
we periodically issue a query on a huge table via an oracle job.
Whenever I invoke the query manually, the response time is good. When I start the periodic job, initially the response times are good as well. After some days, however, the query suddenly takes almost forever.
My vague guess is that for some reason the query suddenly changes the execution plan from using the primary key index to a full table scan (or huge index range scan). Maybe because of some problems with the primary key index (fragmentation? Other?).
- Could it be the case that the execution plan for a query changes (automatically) like this? For what reasons?
- Do you have any hints where to look for further information for analysis? (logs, special event types, ...)?
- Of course, the query was designed having involved indexes in mind. Also, I studied the execution plan and did not find hints for problematic table/range scans.
- It is not a lock contention problem
- When the query "takes forever", there is a "db file sequential read" event in v$session_event for the query with an ever increasing wait time. That's why I guess a (unreasonable) table scan is happening.
Some charachteristics of the table in question:
- ~ 30 Mio rows
- There are only insertions to the table, as well as updates on a single, indexed field. No deletes.
- There is an integer primary key field with an B-tree index.
Charachteristics of the query:
The main structure of the query is very simple and as follows: I select a range of about 100 rows via primary key "id", like:
Select * from TheTable where id>11222300 and id <= 11222400
There are several joins with rather small tables, which make the overall query more complicated.
However, the few (100) rows of the huge table in question should always be fetched using the primary key index, shouldn't it?
Please let me know if some relevant information about the problem is missing.
Thanks!
Best regards,
Nang.

user2560749 wrote:
Dear all,
we periodically issue a query on a huge table via an oracle job.
Whenever I invoke the query manually, the response time is good. When I start the periodic job, initially the response times are good as well. After some days, however, the query suddenly takes almost forever.
My vague guess is that for some reason the query suddenly changes the execution plan from using the primary key index to a full table scan (or huge index range scan). Maybe because of some problems with the primary key index (fragmentation? Other?).
- Could it be the case that the execution plan for a query changes (automatically) like this? For what reasons?Yes possible, One reason is stats of the table has been changed i.e somebody issued dbms_stats. If you are worried about execution plan getting changed then two option 1) Lock the stats 2) Use hint in the query.
- Do you have any hints where to look for further information for analysis? (logs, special event types, ...)?Have a Ora-10053 trace enabled whenever query plan changes and analysis it.
- Of course, the query was designed having involved indexes in mind. Also, I studied the execution plan and did not find hints for problematic table/range scans.
- It is not a lock contention problem
- When the query "takes forever", there is a "db file sequential read" event in v$session_event for the query with an ever increasing wait time. That's why I guess a (unreasonable) table scan is happening.
If it db file sequential read then i see two things 1) It is doing index range scan(Not table full scan) or 2) It is scanning undo tablespaces.
Some charachteristics of the table in question:
- ~ 30 Mio rows
- There are only insertions to the table, as well as updates on a single, indexed field. No deletes.
- There is an integer primary key field with an B-tree index.
Charachteristics of the query:
The main structure of the query is very simple and as follows: I select a range of about 100 rows via primary key "id", like:
Select * from TheTable where id>11222300 and id <= 11222400
There are several joins with rather small tables, which make the overall query more complicated.
However, the few (100) rows of the huge table in question should always be fetched using the primary key index, shouldn't it?
Yes theoreitically it should practically we can only say by looking at run time explain plan(through 10053,10046 trace).
Please let me know if some relevant information about the problem is missing.
Thanks!
Best regards,
Nang.I am still not sure in which direction you are looking for solution.
Is your query performing bad once in a fortnight and next day it is all same again.
I suggest to
1) Check if the data is scanning undo tablespace. I see you mentioned there is lot of inserts, could be that Oracle would be scanning undo tablespace because of delayed clean out.
2) Check if that particular day the number of records are high compared to other day.
Or once it starts performing bad then for next couple of days there is no change in response time.
1) Check if explain plan has been changed?
And what action you take to bring back the response time to normal?
Regards
Anurag

0FI_AR_4 - Slow Sequential Read in ECC on Initial Load

Similar Messages

Maybe you are looking for