ITL waits
Hi ,
Was going through the MS Doc TX Transaction locks - Example wait scenarios (Doc ID 62354.1)
In that under Waits due to Insufficient 'ITL' slots in the block i executed the query it shows a index with high value for ITL waits
SQL>
SELECT t.OWNER, t.OBJECT_NAME, t.OBJECT_TYPE, t.STATISTIC_NAME, t.VALUE
FROM v$segment_statistics t
WHERE t.STATISTIC_NAME = 'ITL waits'
AND t.VALUE > 0;
OWNER OBJECT_NAME OBJECT_TYPE STATISTIC_NAME VALUE
APPLSYS FND_LOGINS_U1 INDEX ITL waits 38Is that initrans of this index has to be increased?? And also i increased the value of initrans of index from 10 to 30 and then executed the query again. It shows the same value? How do i verify if the ITL waits on this segment is resolved or not?
baskar.l
Hi,
Got it from MS Doc How To Modify The Physical Attribute INITRANS For An Existing Table Or Index? (Doc ID 549074.1) as we need to rebuild the index if we want the existing blocks to change. As far table concern we need re-organize it.
baskar.l
Similar Messages
-
What is bad # for 'Space Allocated/Used" and 'ITL Waits' in V$SEGMENT_STATS
I ran a query against the V$SEGMENT_STATISTICS view today and got some possibly disturbing numbers. Can some one let me know if they are bad or if I just reading to much into them.
DB has been up since 1/10/2011 so they represent the stats since then. DB size is 3TB
OBJECT_NAME OBJECT_TYPE STATISTIC_NAME VALUE
XXPK0EMIANCE INDEX space allocated 27,246,198,784
ITEMINTANCE TABLE space allocated 22,228,762,624
LITEMINSTANCE TABLE space used 19,497,901,889
XXPK0TEMINSTANCE INDEX space used 17,431,957,592
TTINGCORE TABLE space allocated 8,724,152,320
XXPK0IANCE INDEX space allocated 6,912,212,992
SKISTANCE TABLE space allocated 4,697,620,480
IIXCNSTANCE TABLE space allocated 4,697,620,480
on the XXPK0EMIANCE index the inital extent is 64k
XXPK0MINSTANCE INDEX ITL waits 1,123
XXIEKILSTANCE INDEX ITL waits 467
XXPKLINSTANCE INDEX ITL waits 463
XXPKCE INDEX ITL waits 338
XXIE3ENT INDEX ITL waits 237
If these are bad do they impact performance? My understanding is that being wait states, things stop until they are resolved. Is that true.
Also these looked high, are they?
LATION_PK INDEX logical reads 242,212,503,104
XXAK1STSCORE INDEX logical reads 117,542,351,984
XXPK0TSTANCE INDEX logical reads 113,532,240,160
TCORE TABLE db block changes 1,913,902,176
SDENT TABLE physical reads 72,161,312
XXPK0PDUCT INDEX segment scans 35,268,027
ESTSORE TABLE buffer busy waits 2,604,947
XXPK0SUCORE INDEX buffer busy waits 119,007
XXPK0INSTANCE INDEX row lock waits 63,810
XXPK0EMINSTANCE INDEX row lock waits 58,129
XXPK0NSTANCE INDEX row lock waits 57,776
XXIE2DDSTANCE INDEX row lock waits 54,788
XXPK0DDDSTSCORE INDEX row lock waits 49,167
Am i just reading too much into this? I am not a DBA, our DBA is too busy doing data changes and such to spent time looking at these stuff. I was tasked to try to find out why our DB is so slow.Statistics on waits and reads are cumulative since the last database instance startup --- which was more than 4 months ago.
So :
XXPK0MINSTANCE INDEX ITL waits 1,1231,123 waits in 4+ months isn't bad.
Reading such statistics without reference to the duration is utterly meaningless.
Those 1,123 waits could have been 10 waits a day @1 every 2 hours.
OR those 1,123 waits could have occurred between 01:00 and 01:30 on 03-May-2011.
We have no way of knowing which is the case.
Hemant K Chitale -
Oracle Version 11.2.0.3 PSU3
OS: SLES11 GA 64 bit
We had an issue with ITL waits on a specific table. In test this resulted in a deadlock so as a fix we rebuilt the table with initrans 8 and pctfree 75, this has improved the situation as we no longer have deadlocks but we have had an instance of high waits for ITL slots. Our development team assure us that a maximum of 6 transactions should be active on the table in question at any given time so we should not see any waits at all. As a bonus feature the table in question is initially loaded with just the primary key columns and the rest of the data (60 columns in all) is filled in over time which can cause considerable row migration to occur has anyone else encountered an issue of this type? Does row migration use additional ITL slots? I am attempting to replicate this in a development environment but so far can not get a replication of the problem.rp0428 wrote:
Row migration can consume excess ITL entries - every row migrated in a single transaction will allocate an ITL slot in the target block, so if you manage to get (say) 5 rows in a block migrating in a single transaction and they all migrate to the same block you will find that you have used 5 ITL slots in that block - so you can't rule out the possibility that the migration is the cause of the ITL waits.
Can you expand on that a bit and reconcile it with what you say in the ITL entry in your Oracle Scratchpad Glossary article?
http://jonathanlewis.wordpress.com/2009/06/23/glossary/
The transaction needs to acquire only one ITL entry in the block no matter how many rows in the block it changes.
If an ITL (Interested Transaction List) entry represents 'interest' by a singlel transaction why would that single transaction need more than one entry in the block when migrating rows but not when updating existing rows?
What am I overlooking?
rp0428,
There are two possible replies to that question - the absolutely straightforward one is that I forgot to mention any special cases (the "Index Explosion" bug is another, very similar, case) when I wrote that note; the "wiggle" one is that each migration event behaves like a recursive transaction, which leaves you with one ITL entry per arriving row.
Regards
Jonathan Lewis -
High Buffer Busy Wait due to Concurrent INSERTS
Hi All,
One of my OLTP database is running on 11.1.0.7 (11.1.0.7.0 - 64bit Production) with RHEL 5.4.
On frequent basis, i am observing 'BUFFER BUSY WAITS' and last time i tried to capture some dictionary information to dig the waits.
1. Session Watis :
Oracle Sec Hash
Sid,Serial User OS User Svr-Pgm Wait Event State-Seq Wt Module Cmnd Value P1 P2 P3
633,40830 OLTP_USE fateadm 21646-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863905 1
647, 1761 OLTP_USE fateadm 22715-orac buffer busy wai Wtng-3837 0 ORDERS ISRT 3932487748 384 1863905 1
872, 5001 OLTP_USE fateadm 21836-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863905 1
702, 1353 OLTP_USE fateadm 21984-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863905 1
337,10307 OLTP_USE fateadm 21173-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863905 1
751,43016 OLTP_USE fateadm 21619-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863905 1
820,17959 OLTP_USE fateadm 21648-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863905 1
287,63359 OLTP_USE fateadm 27053-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863905 1
629, 1653 OLTP_USE fateadm 22468-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863905 1
788,14160 OLTP_USE fateadm 22421-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863905 1
615, 4580 OLTP_USE fateadm 21185-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863905 1
525,46068 OLTP_USE fateadm 27043-orac buffer busy wai Wtng-9034 1 ORDERS ISRT 3932487748 384 1863905 1
919,23243 OLTP_USE fateadm 21428-orac buffer busy wai Wtng-6340 1 ORDERS ISRT 3932487748 384 1863906 1
610,34557 OLTP_USE fateadm 21679-orac buffer busy wai Wtng-6422 1 ORDERS ISRT 3932487748 384 1863906 1
803, 1583 OLTP_USE fateadm 21580-orac buffer busy wai Wtng-6656 1 ORDERS ISRT 3932487748 384 1863906 1
781, 1523 OLTP_USE fateadm 21781-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863906 1
369,11005 OLTP_USE fateadm 21718-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863906 1
823,35800 OLTP_USE fateadm 21148-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863906 1
817, 1537 OLTP_USE fateadm 22505-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863906 1
579,54959 OLTP_USE fateadm 22517-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863906 1
591,33597 OLTP_USE fateadm 27027-orac buffer busy wai Wtng-9999 1 ORDERS ISRT 3932487748 384 1863906 1
481, 3031 OLTP_USE fateadm 21191-orac buffer busy wai Wtng-3502 1 ORDERS ISRT 3932487748 384 1863906 1
473,24985 OLTP_USE fateadm 22629-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863906 1
868, 3984 OLTP_USE fateadm 27191-orac buffer busy wai Wtng-9999 0 ORDERS ISRT 3932487748 384 1863906 1
select owner,segment_name,segment_type from dba_extents where file_id = 384 and 1863905 between block_id and block_id + blocks -1;
OWNER SEGMENT_NAME SEGMENT_TYPE
ORDER ORDER_DETAILS TABLE
select TABLE_NAME,PARTITIONED,ini_trans ,degree,compression,FREELISTS from dba_TABLES WHERE TABLE_NAME='ORDER_DETAILS';
TABLE_NAME PAR INI_TRANS DEGREE COMPRESS FREELISTS
ORDER_DETAILS NO 1 1 ENABLED 1
Tablespace is not ASSM managed !
select
object_name,
statistic_name,
value
from
V$SEGMENT_STATISTICS
where
object_name = 'ORDER_DETAILS';
OBJECT_NAME STATISTIC_NAME VALUE
ORDER_DETAILS logical reads 487741104
ORDER_DETAILS buffer busy waits 4715174
ORDER_DETAILS db block changes 200858896
ORDER_DETAILS physical reads 143642724
ORDER_DETAILS physical writes 20581330
ORDER_DETAILS physical reads direct 55239903
ORDER_DETAILS physical writes direct 19500551
ORDER_DETAILS space allocated 1.6603E+11
ORDER_DETAILS segment scans 9727
ORDER_DETAILS table is ~ 153 GB non-partitioned table.
It seems its not a READ BY OTHER SESSIONS wait but BUFFER BUSY due to write-wirte contention inside same block. I have never observed Cache Buffer Chain/ ITL-Wait/ High wait time on dbfile sequential/scattered reads.Table contains one PK (composite index on 3 columns) which seems to be highly fragmented.This non partitioned global Index has 3182037735 rows and blevel is 4.
BHAVIK_DBA.FATE1NA>select index_name,status,num_rows,blevel,pct_free,ini_trans,clustering_factor from dba_indexes where index_name='IDX_ORDERS';
INDEX_NAME STATUS NUM_ROWS BLEVEL PCT_FREE INI_TRANS CLUSTERING_FACTOR
IDX_ORDERS VALID 3182037735 4 2 2 2529462377
1 row selected.
One of the index column value is being populated by sequence. (Monotonically increasing value)
SEGMENT_NAME MB
IDX_ORDERS 170590.438
Index size is greater than table size !Tuning goal here is to reduce buffer busy waits and thus commit latencies.
I think, i need to increase FREELISTS and PCT_FREE to address this issue, but not much confident whether it is going to solve the issue or not?
Can i ask for any help here ?Hi Johnathan;
Many thanks for your detailed write-up. I was expecting you !
Your post here gave lot of information and wisdom that made me think last couple of hrs that is the reason for the delay in reply.
I did visited your index explosion posts couple of times and that scenario only gave me insight that concurrent DML (INSERT) is cause of index fragmentation in my case.
Let me also pick the opportunity to ask you to shed more light on some of the information you have highlighted.
if you can work out the number of concurrent inserts that are really likely to happen at any one instant then a value of freelists that in the range of
concurrency/4 to concurrency/2 is probably appropriate.May i ask you how did you derive this formula ? I dont want to miss learning opportunity here !
Note - with multiple freelists, you may find that you now get buffer busy waits on the segment header block.I did not quite get this point ? Can you shed more light please? What piece in segment header block is going to result contention(BBW on SEGMENT HEADER) on all concurrent inserts ?
The solution to this is to increase the number of freelist groups (making sure that
freelists and freelist groups have no common factors).My prod db NON-RAC environment. Can i use FREELIST GROUPS here ? My little knowledge did not get, What "common factors" you are referring here ?
The reads could be related to leaf block splits, but there are several possible scenarios that could lead to that pattern of activity - so the next step is to find out which blocks are being
read. Capture a sample of the waits, then query dba_extents for the extent_id, file_id, and block_id (don't run that awful query with the "block_id + blocks" predicate) and cross-check the
list of blocks to see if they are typically the first couple of blocks of an extent or randomly scattered throughout extents. If the former the problem is probably related to ASSM, if the
latter it may be related to failed probes on index leaf block reuse (i.e. after large scale deletes).I have 10046 trace file with me (giving you some sample below) that can give some information. However, since the issue was critical, i killed the insert process and rebuilt both the indexes. Since, index is rebuilt, i am not able to find any information in dba_extents.
select SEGMENT_NAME,SEGMENT_TYPE,EXTENT_ID from dba_extents where file_id=42 and block_id=1109331;
no rows selected
select SEGMENT_NAME,SEGMENT_TYPE,EXTENT_ID from dba_extents where file_id=42 and block_id=1109395 ;
no rows selected
select SEGMENT_NAME,SEGMENT_TYPE,EXTENT_ID from dba_extents where file_id=42 and block_id=1109459;
no rows selected
select SEGMENT_NAME,SEGMENT_TYPE,EXTENT_ID from dba_extents where file_id=10 and block_id=1107475;
no rows selected
select SEGMENT_NAME,SEGMENT_TYPE,EXTENT_ID from dba_extents where file_id=10 and block_id=1107539;
no rows selected
select object_name,object_Type from dba_objects where object_id=17599;
no rows selected
WAIT #4: nam='db file sequential read' ela= 49 file#=42 block#=1109331 blocks=1 obj#=17599 tim=1245687162307379
WAIT #4: nam='db file sequential read' ela= 59 file#=42 block#=1109395 blocks=1 obj#=17599 tim=1245687162307462
WAIT #4: nam='db file sequential read' ela= 51 file#=42 block#=1109459 blocks=1 obj#=17599 tim=1245687162307538
WAIT #4: nam='db file sequential read' ela= 49 file#=10 block#=1107475 blocks=1 obj#=17599 tim=1245687162307612
WAIT #4: nam='db file sequential read' ela= 49 file#=10 block#=1107539 blocks=1 obj#=17599 tim=1245687162307684
WAIT #4: nam='db file sequential read' ela= 198 file#=10 block#=1107603 blocks=1 obj#=17599 tim=1245687162307905
WAIT #4: nam='db file sequential read' ela= 88 file#=10 block#=1107667 blocks=1 obj#=17599 tim=1245687162308016
WAIT #4: nam='db file sequential read' ela= 51 file#=10 block#=1107731 blocks=1 obj#=17599 tim=1245687162308092
WAIT #4: nam='db file sequential read' ela= 49 file#=10 block#=1107795 blocks=1 obj#=17599 tim=1245687162308166
WAIT #4: nam='db file sequential read' ela= 49 file#=10 block#=1107859 blocks=1 obj#=17599 tim=1245687162308240
WAIT #4: nam='db file sequential read' ela= 52 file#=10 block#=1107923 blocks=1 obj#=17599 tim=1245687162308314
WAIT #4: nam='db file sequential read' ela= 57 file#=42 block#=1109012 blocks=1 obj#=17599 tim=1245687162308395
WAIT #4: nam='db file sequential read' ela= 52 file#=42 block#=1109076 blocks=1 obj#=17599 tim=1245687162308470
WAIT #4: nam='db file sequential read' ela= 98 file#=42 block#=1109140 blocks=1 obj#=17599 tim=1245687162308594
WAIT #4: nam='db file sequential read' ela= 67 file#=42 block#=1109204 blocks=1 obj#=17599 tim=1245687162308686
WAIT #4: nam='db file sequential read' ela= 53 file#=42 block#=1109268 blocks=1 obj#=17599 tim=1245687162308762
WAIT #4: nam='db file sequential read' ela= 54 file#=42 block#=1109332 blocks=1 obj#=17599 tim=1245687162308841
WAIT #4: nam='db file sequential read' ela= 55 file#=42 block#=1109396 blocks=1 obj#=17599 tim=1245687162308920
WAIT #4: nam='db file sequential read' ela= 54 file#=42 block#=1109460 blocks=1 obj#=17599 tim=1245687162308999
WAIT #4: nam='db file sequential read' ela= 52 file#=10 block#=1107476 blocks=1 obj#=17599 tim=1245687162309074
WAIT #4: nam='db file sequential read' ela= 89 file#=10 block#=1107540 blocks=1 obj#=17599 tim=1245687162309187
WAIT #4: nam='db file sequential read' ela= 407 file#=10 block#=1107604 blocks=1 obj#=17599 tim=1245687162309618TKPROF for above trace
INSERT into
order_rev
(aggregated_revenue_id,
legal_entity_id,
gl_product_group,
revenue_category,
warehouse_id,
tax_region,
gl_product_subgroup,
total_shipments,
total_units_shipped,
aggregated_revenue_amount,
aggregated_tax_amount,
base_currency_code,
exchange_rate,
accounting_date,
inventory_owner_type_id,
fin_commission_structure_id,
seller_of_record_vendor_id,
organizational_unit_id,
merchant_id,
last_updated_date,
revenue_owner_type_id,
sales_channel,
location)
VALUES
(order_rev.nextval,:p1,:p2,:p3,:p4,:p5,:p6,:p7,:p8,:p9,:p10,:p11,:p12,to_date(:p13, 'dd-MON-yyyy'),:p14,:p15,:p16,:p17,:p18,sysdate,:p19,:p20,:p21)
call count cpu elapsed disk query current rows
Parse 0 0.00 0.00 0 0 0 0
Execute 613 5.50 40.32 96672 247585 306916 613
Fetch 0 0.00 0.00 0 0 0 0
total 613 5.50 40.32 96672 247585 306916 613
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 446
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 164224 0.04 62.33
SQL*Net message to client 613 0.00 0.00
SQL*Net message from client 613 0.03 0.90
latch: cache buffers chains 8 0.00 0.00
latch: object queue header operation 2 0.00 0.00Is there any other way to find out culprit amongst the two you have listed (ASSM / failed probes on index leaf block reuse ) ? -
Amount of max possible simultaneous INSERTs depend on what ??
Hi all,
can somebody comment on following statement , whether its is absolutely true, only a part of the truth or completely wrong :
"The maximum possible amount of transactions that are simultaneously performing inserts into an Oracle- table is MAINLY constrained by the available ITL-slots of that table." (Assumption : Hardware performance identical)
Background : We have a mission critical table where every user performs inserts (some kind of an audit table). These inserts are part of the original business transaction and are -normally- very fast.
Problem is that the commit of the original business txn is only issued after populating this audit table.
We were asked how many hanging user transactions would be required in order to completely lock the table for further inserts and as a consequence completely hangup the application.
Cheers,
Migmbobak wrote:
2.) You didn't mention version, or whether you're using ASSM, but, if you're still using MSSM (free list managment), then you'll need to consider freelists as well. The freelists parameter should be set to the max concurrent number of inserts on a segment.
Mark,
I wasn't planning to go into details about how to configure the number of blocks available for insertion, but you're right: freelists is a significant setting, as is freelist groups. ASSM is roughly equivalent to just freelists 16 freelist groups 1 - which is why systems with very high rates of concurrent DML should seriously consider avoiding it.
P.S. Come to think of it, you're more likely to have trouble from buffer busy waits before you run into problems with ITL waits if you try increasing insertion concurrency by setting a high INITRANS.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
"Science is more than a body of knowledge; it is a way of thinking" Carl Sagan -
Oracle Version: 11.1.0.7 64x
OS Version: Windows 2008 Server 64x
Hi There,
We're just trying to generate a awr report for one of our databases and the report is coming out with no data.
statistics_level parameter is set to "TYPICAL"; any idea to what's going on please?
Thanks
SQL>
SQL> @?/rdbms/admin/awrrpt.sql
Current Instance
~~~~~~~~~~~~~~~~
DB Id DB Name Inst Num Instance
1391811405 WEBTST 1 webtst
Specify the Report Type
~~~~~~~~~~~~~~~~~~~~~~~
Would you like an HTML report, or a plain text report?
Enter 'html' for an HTML report, or 'text' for plain text
Defaults to 'html'
Enter value for report_type: text
Type Specified: text
Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Id Inst Num DB Name Instance Host
* 1391811405 1 WEBTST webtst WEBDBTST
Using 1391811405 for database Id
Using 1 for instance number
Specify the number of days of snapshots to choose from
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Entering the number of days (n) will result in the most recent
(n) days of snapshots being listed. Pressing <return> without
specifying a number lists all completed snapshots.
Enter value for num_days: 1
Listing the last day's Completed Snapshots
Snap
Instance DB Name Snap Id Snap Started Level
webtst WEBTST 43973 12 May 2011 00:00 1
43974 12 May 2011 01:00 1
43975 12 May 2011 02:00 1
43976 12 May 2011 03:00 1
43977 12 May 2011 04:00 1
43978 12 May 2011 05:00 1
43979 12 May 2011 06:00 1
43980 12 May 2011 07:00 1
43981 12 May 2011 08:00 1
43982 12 May 2011 09:00 1
43983 12 May 2011 10:00 1
43984 12 May 2011 11:00 1
43985 12 May 2011 11:02 1
Specify the Begin and End Snapshot Ids
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enter value for begin_snap: 43984
Begin Snapshot Id specified: 43984
Enter value for end_snap: 43985
End Snapshot Id specified: 43985
Specify the Report Name
~~~~~~~~~~~~~~~~~~~~~~~
The default report file name is awrrpt_1_43984_43985.txt. To use this name,
press <return> to continue, otherwise enter an alternative.
Enter value for report_name:
Using the report name awrrpt_1_43984_43985.txt
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: parse time elapsed
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: DB CPU
WARNING (-20016)
ORA-20016: Missing value for SGASTAT: free memory
WARNING (-20016)
ORA-20016: Missing value for SGASTAT: free memory
WARNING (-20009)
ORA-20009: Missing System Statistic logons current
WARNING (-20009)
ORA-20009: Missing System Statistic logons current
WARNING (-20009)
ORA-20009: Missing System Statistic opened cursors current
WARNING (-20009)
ORA-20009: Missing System Statistic opened cursors current
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: sql execute elapsed
WARNING (-20008)
ORA-20008: Missing Init.ora parameter undo_management
WARNING (-20008)
ORA-20008: Missing Init.ora parameter db_block_size
WARNING (-20016)
ORA-20016: Missing value for SGASTAT: log_buffer
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: DB time
WARNING (-20008)
ORA-20008: Missing Init.ora parameter timed_statistics
WARNING (-20008)
ORA-20008: Missing Init.ora parameter timed_statistics
WARNING (-20008)
ORA-20008: Missing Init.ora parameter statistics_level
WARNING (-20008)
ORA-20008: Missing Init.ora parameter statistics_level
WARNING (-20008)
ORA-20008: Missing Init.ora parameter sga_target
WARNING (-20008)
ORA-20008: Missing Init.ora parameter pga_aggregate_target
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: background cpu time
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: background elapsed
WARNING (-20023)
ORA-20023: Missing start and end values for time model stat: connection manageme
WARNING (-20016)
ORA-20016: Missing value for SGASTAT: buffer_cache
WARNING (-20016)
ORA-20016: Missing value for SGASTAT: buffer_cache
WARNING: Since the DB Time is less than one second, there was
minimal foreground activity in the snapshot period.
Some of the percentage values will be invalid.
WORKLOAD REPOSITORY report for
DB Name DB Id Instance Inst Num Startup Time Release RAC
WEBTST 1391811405 webtst 1 29-Apr-11 04:50 11.1.0.7.0 NO
Host Name Platform CPUs Cores Sockets Memory(GB)
WEBDBTST Microsoft Windows x86 64-bit .00
Snap Id Snap Time Sessions Curs/Sess
Begin Snap: 43984 12-May-11 11:00:01
End Snap: 43985 12-May-11 11:02:00
Elapsed: 1.98 (mins)
DB Time: 0.00 (mins)
Cache Sizes Begin End
~~~~~~~~~~~ ---------- ----------
Buffer Cache:MM Std Block Size:K
Shared Pool Size: 0M 0M Log Buffer:K
ORA-01403: no data found
Error encountered in Report Summary
Continuing to Report Sections
Time Model Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Operating System Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Operating System Statistics - DetailDB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Foreground Wait Class DB/Inst: WEBTST/webtst Snaps: 43984-43985
-> s - second, ms - millisecond - 1000th of a second
-> ordered by wait time desc, waits desc
-> %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
-> Captured Time accounts for % of Total DB time .00 (s)
-> Total FG Wait Time: (s) DB CPU time: .00 (s)
Avg
%Time Total Wait wait
Wait Class Waits -outs Time (s) (ms) %DB time
DB CPU 0 100.0
Foreground Wait Events DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Background Wait Events DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Wait Event Histogram DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Service Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Service Wait Class Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Elapsed Time DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by CPU Time DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Gets DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Reads DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Executions DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Parse Calls DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Sharable Memory DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
SQL ordered by Version Count DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Instance Activity Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Instance Activity Stats - Absolute ValuesDB/Inst: WEBTST/webtst Snaps: 43984
No data exists for this section of the report.
Instance Activity Stats - Thread ActivityDB/Inst: WEBTST/webtst Snaps: 43984-
No data exists for this section of the report.
Tablespace IO Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
File IO Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Buffer Pool Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Instance Recovery Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Buffer Pool Advisory DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
PGA Aggr Summary DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
PGA Aggr Target Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
PGA Aggr Target Histogram DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
PGA Memory Advisory DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
Shared Pool Advisory DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
SGA Target Advisory DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
Streams Pool Advisory DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
Java Pool Advisory DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
Buffer Wait Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Enqueue Activity DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Undo Segment Summary DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Undo Segment Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Latch Activity DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Latch Sleep Breakdown DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Latch Miss Sources DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Mutex Sleep Summary DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Parent Latch Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Child Latch Statistics DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Segments by Row Lock Waits DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Segments by ITL Waits DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Segments by Buffer Busy Waits DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Dictionary Cache Stats DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Library Cache Activity DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Memory Dynamic Components DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Memory Resize Operations Summary DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Memory Resize Ops DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Process Memory Summary DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
sum
SGA breakdown difference DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Streams CPU/IO Usage DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Streams Capture DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Streams Apply DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Buffered Queues DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Buffered Subscribers DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Rule Set DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Persistent Queues DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Persistent Subscribers DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
Resource Limit Stats DB/Inst: WEBTST/webtst Snap: 43985
No data exists for this section of the report.
init.ora Parameters DB/Inst: WEBTST/webtst Snaps: 43984-43985
No data exists for this section of the report.
End of ReportSQL> show parameter statistics
NAME TYPE VALUE
optimizer_use_pending_statistics boolean FALSE
statistics_level string TYPICAL
timed_os_statistics integer 0
timed_statistics boolean TRUE
SQL>
SQL> SELECT statistics_name,
2 session_status,
3 system_status,
4 activation_level,
5 session_settable
6 FROM v$statistics_level
7 ORDER BY statistics_name;
STATISTICS_NAME SESSION_ SYSTEM_S ACTIVAT SES
Active Session History ENABLED ENABLED TYPICAL NO
Adaptive Thresholds Enabled ENABLED ENABLED TYPICAL NO
Automated Maintenance Tasks ENABLED ENABLED TYPICAL NO
Bind Data Capture ENABLED ENABLED TYPICAL NO
Buffer Cache Advice ENABLED ENABLED TYPICAL NO
Global Cache Statistics ENABLED ENABLED TYPICAL NO
Longops Statistics ENABLED ENABLED TYPICAL NO
MTTR Advice DISABLED DISABLED TYPICAL NO
Modification Monitoring ENABLED ENABLED TYPICAL NO
PGA Advice ENABLED ENABLED TYPICAL NO
Plan Execution Sampling ENABLED ENABLED TYPICAL YES
Plan Execution Statistics DISABLED DISABLED ALL YES
SQL Monitoring ENABLED ENABLED TYPICAL YES
Segment Level Statistics ENABLED ENABLED TYPICAL NO
Shared Pool Advice ENABLED ENABLED TYPICAL NO
Streams Pool Advice ENABLED ENABLED TYPICAL NO
Threshold-based Alerts ENABLED ENABLED TYPICAL NO
Time Model Events ENABLED ENABLED TYPICAL YES
Timed OS Statistics DISABLED DISABLED ALL YES
Timed Statistics ENABLED ENABLED TYPICAL YES
Ultrafast Latch Statistics ENABLED ENABLED TYPICAL NO
Undo Advisor, Alerts and Fast Ramp up ENABLED ENABLED TYPICAL NO
V$IOSTAT_* statistics ENABLED ENABLED TYPICAL NO
23 rows selected.
SQL>Thanks
Edited by: rsar001 on May 12, 2011 11:33 AM -
How to get list of block identifiers in a empty table and an empty index
We have an application that has issue with ITL waits: this application is running many INSERT statements on a table that has 2 NUMBER columns and one primary key index. The application is designed to run INSERT statements but they are never committed (this is a software package).
To check what are the really allocated ITL slots, I know that I can dump data block but I don't know how to get the block identifiers/numbers for an "empty" table and an "empty" index. Does someone knows how to do that ?
PS: I already had a look to the Metalink notes and I have a Metalink SR for that but maybe OTN forum is faster ?You should be able to find the first data/index block with the following, even on an empty table/index.
select header_file, header_block +1
from dba_segments
where segment_name = '<index or table name>'; -
Blank awr report shown in oracle standars edition 11g (11.2.0.1.0)
Hi, friends ..
I am using Oracle 11g standars edition(11.2.0.1.0) on solaris 10 platform.I do have a very strange probleem..when iam trying to capture awr report i am getting a blank
awr report contain ing nothing...like below section
---------------------------------------------------------------------------->
WARNING: Since the DB Time is less than one second, there was minimal foreground activity in the snapshot period. Some of the percentage values will be invalid.
WORKLOAD REPOSITORY report for
DB Name DB Id Instance Inst num Startup Time Release RAC
DISDB 771054785 disdb 1 30-Dec-10 10:12 11.2.0.1.0 NO
Host Name Platform CPUs Cores Sockets Memory (GB)
dissemination-new Solaris Operating System (x86-64) .00
Snap Id Snap Time Sessions Cursors/Session
Begin Snap: 1 30-Dec-10 11:30:21
End Snap: 2 30-Dec-10 12:30:52
Elapsed: 60.51 (mins)
DB Time: 0.00 (mins)
Report Summary
Cache Sizes
Begin End
Buffer Cache: M M Std Block Size: K
Shared Pool Size: 0M 0M Log Buffer: K
Load Profile
Per Second Per Transaction Per Exec Per Call
DB Time(s): 0.0 0.0 0.00 0.00
DB CPU(s): 0.0 0.0 0.00 0.00
Redo size:
Logical reads: 0.0 1.0
Block changes: 0.0 1.0
Physical reads: 0.0 1.0
Physical writes: 0.0 1.0
User calls: 0.0 1.0
Parses: 0.0 1.0
Hard parses:
W/A MB processed: 0.0 0.0
Logons:
Executes: 0.0 1.0
Rollbacks:
Transactions: 0.0
Instance Efficiency Percentages (Target 100%)
Buffer Nowait %: Redo NoWait %:
Buffer Hit %: In-memory Sort %:
Library Hit %: Soft Parse %:
Execute to Parse %: 0.00 Latch Hit %:
Parse CPU to Parse Elapsd %: % Non-Parse CPU:
Shared Pool Statisitics Not Available
Top 5 Timed Foreground Events
Event Waits Time(s) Avg wait (ms) % DB time Wait Class
DB CPU 0 100.00
Host CPU (CPUs: Cores: Sockets: )
Load Average Begin Load Average End %User %System %WIO %Idle
Instance CPU
%Total CPU %Busy CPU %DB time waiting for CPU (Resource Manager)
Memory Statistics
Begin End
Host Mem (MB):
SGA use (MB):
PGA use (MB):
% Host Mem used for SGA+PGA:
Main Report
Report Summary
Wait Events Statistics
SQL Statistics
Instance Activity Statistics
IO Stats
Buffer Pool Statistics
Advisory Statistics
Wait Statistics
Undo Statistics
Latch Statistics
Segment Statistics
Dictionary Cache Statistics
Library Cache Statistics
Memory Statistics
Streams Statistics
Resource Limit Statistics
Shared Server Statistics
init.ora Parameters
Back to Top
Wait Events Statistics
Time Model Statistics
Operating System Statistics
Operating System Statistics - Detail
Foreground Wait Class
Foreground Wait Events
Background Wait Events
Wait Event Histogram
Wait Event Histogram Detail (64 msec to 2 sec)
Wait Event Histogram Detail (4 sec to 2 min)
Wait Event Histogram Detail (4 min to 1 hr)
Service Statistics
Service Wait Class Stats
Back to Top
Time Model Statistics
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Operating System Statistics
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Operating System Statistics - Detail
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Foreground Wait Class
s - second, ms - millisecond - 1000th of a second
ordered by wait time desc, waits desc
%Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Captured Time accounts for % of Total DB time .00 (s)
Total FG Wait Time: (s) DB CPU time: .00 (s)
Wait Class Waits %Time -outs Total Wait Time (s) Avg wait (ms) %DB time
DB CPU 0 100.00
Back to Wait Events Statistics
Back to Top
Foreground Wait Events
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Background Wait Events
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Wait Event Histogram
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Wait Event Histogram Detail (64 msec to 2 sec)
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Wait Event Histogram Detail (4 sec to 2 min)
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Wait Event Histogram Detail (4 min to 1 hr)
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Service Statistics
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Service Wait Class Stats
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
SQL Statistics
SQL ordered by Elapsed Time
SQL ordered by CPU Time
SQL ordered by User I/O Wait Time
SQL ordered by Gets
SQL ordered by Reads
SQL ordered by Physical Reads (UnOptimized)
SQL ordered by Executions
SQL ordered by Parse Calls
SQL ordered by Sharable Memory
SQL ordered by Version Count
Complete List of SQL Text
Back to Top
SQL ordered by Elapsed Time
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by CPU Time
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by User I/O Wait Time
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Gets
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Reads
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Physical Reads (UnOptimized)
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Executions
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Parse Calls
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Sharable Memory
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
SQL ordered by Version Count
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
Complete List of SQL Text
No data exists for this section of the report.
Back to SQL Statistics
Back to Top
Instance Activity Statistics
Instance Activity Stats
Instance Activity Stats - Absolute Values
Instance Activity Stats - Thread Activity
Back to Top
Instance Activity Stats
No data exists for this section of the report.
Back to Instance Activity Statistics
Back to Top
Instance Activity Stats - Absolute Values
No data exists for this section of the report.
Back to Instance Activity Statistics
Back to Top
Instance Activity Stats - Thread Activity
No data exists for this section of the report.
Back to Instance Activity Statistics
Back to Top
IO Stats
IOStat by Function summary
IOStat by Filetype summary
IOStat by Function/Filetype summary
Tablespace IO Stats
File IO Stats
Back to Top
IOStat by Function summary
No data exists for this section of the report.
Back to IO Stats
Back to Top
IOStat by Filetype summary
No data exists for this section of the report.
Back to IO Stats
Back to Top
IOStat by Function/Filetype summary
No data exists for this section of the report.
Back to IO Stats
Back to Top
Tablespace IO Stats
No data exists for this section of the report.
Back to IO Stats
Back to Top
File IO Stats
No data exists for this section of the report.
Back to IO Stats
Back to Top
Buffer Pool Statistics
Buffer Pool Statistics
Checkpoint Activity
Back to Top
Buffer Pool Statistics
No data exists for this section of the report.
Back to Buffer Pool Statistics
Back to Top
Checkpoint Activity
No data exists for this section of the report.
Back to Buffer Pool Statistics
Back to Top
Advisory Statistics
Instance Recovery Stats
MTTR Advisory
Buffer Pool Advisory
PGA Aggr Summary
PGA Aggr Target Stats
PGA Aggr Target Histogram
PGA Memory Advisory
Shared Pool Advisory
SGA Target Advisory
Streams Pool Advisory
Java Pool Advisory
Back to Top
Instance Recovery Stats
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
MTTR Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
Buffer Pool Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
PGA Aggr Summary
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
PGA Aggr Target Stats
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
PGA Aggr Target Histogram
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
PGA Memory Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
Shared Pool Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
SGA Target Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
Streams Pool Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
Java Pool Advisory
No data exists for this section of the report.
Back to Advisory Statistics
Back to Top
Wait Statistics
Buffer Wait Statistics
Enqueue Activity
Back to Top
Buffer Wait Statistics
No data exists for this section of the report.
Back to Wait Statistics
Back to Top
Enqueue Activity
No data exists for this section of the report.
Back to Wait Statistics
Back to Top
Undo Statistics
Undo Segment Summary
Undo Segment Stats
Back to Top
Undo Segment Summary
No data exists for this section of the report.
Back to Undo Statistics
Back to Top
Undo Segment Stats
No data exists for this section of the report.
Back to Undo Statistics
Back to Top
Latch Statistics
Latch Activity
Latch Sleep Breakdown
Latch Miss Sources
Mutex Sleep Summary
Parent Latch Statistics
Child Latch Statistics
Back to Top
Latch Activity
No data exists for this section of the report.
Back to Latch Statistics
Back to Top
Latch Sleep Breakdown
No data exists for this section of the report.
Back to Latch Statistics
Back to Top
Latch Miss Sources
No data exists for this section of the report.
Back to Latch Statistics
Back to Top
Mutex Sleep Summary
No data exists for this section of the report.
Back to Latch Statistics
Back to Top
Parent Latch Statistics
No data exists for this section of the report.
Back to Latch Statistics
Back to Top
Child Latch Statistics
No data exists for this section of the report.
Back to Latch Statistics
Back to Top
Segment Statistics
Segments by Logical Reads
Segments by Physical Reads
Segments by Physical Read Requests
Segments by UnOptimized Reads
Segments by Optimized Reads
Segments by Direct Physical Reads
Segments by Physical Writes
Segments by Physical Write Requests
Segments by Direct Physical Writes
Segments by Table Scans
Segments by DB Blocks Changes
Segments by Row Lock Waits
Segments by ITL Waits
Segments by Buffer Busy Waits
Back to Top
Segments by Logical Reads
Total Logical Reads: 1
Captured Segments account for 4.6E+06% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type Logical Reads %Total
SYS SYSTEM I_SYSAUTH1 INDEX 15,008 1500800.00
SYS SYSTEM I_OBJ2 INDEX 4,752 475200.00
SYS SYSTEM TAB$ TABLE 2,176 217600.00
SYS SYSTEM I_JOB_NEXT INDEX 1,856 185600.00
SYS SYSTEM SYS_C00646 INDEX 1,664 166400.00
Back to Segment Statistics
Back to Top
Segments by Physical Reads
Total Physical Reads: 1
Captured Segments account for 400.0% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type Physical Reads %Total
SYS SYSAUX WRH$_SYSMETRIC_SUMMARY_INDEX INDEX 3 300.00
SYS SYSTEM KOTAD$ TABLE 1 100.00
Back to Segment Statistics
Back to Top
Segments by Physical Read Requests
Total Physical Read Requests: 1
Captured Segments account for 400.0% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type Phys Read Requests %Total
SYS SYSAUX WRH$_SYSMETRIC_SUMMARY_INDEX INDEX 3 300.00
SYS SYSTEM KOTAD$ TABLE 1 100.00
Back to Segment Statistics
Back to Top
Segments by UnOptimized Reads
Total UnOptimized Read Requests: 1
Captured Segments account for 400.0% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type UnOptimized Reads %Total
SYS SYSAUX WRH$_SYSMETRIC_SUMMARY_INDEX INDEX 3 300.00
SYS SYSTEM KOTAD$ TABLE 1 100.00
Back to Segment Statistics
Back to Top
Segments by Optimized Reads
No data exists for this section of the report.
Back to Segment Statistics
Back to Top
Segments by Direct Physical Reads
No data exists for this section of the report.
Back to Segment Statistics
Back to Top
Segments by Physical Writes
Total Physical Writes: 1
Captured Segments account for 1.1E+04% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type Physical Writes %Total
SYSMAN SYSAUX MGMT_METRICS_RAW_PK INDEX 27 2700.00
SYS SYSAUX WRH$_SYSMETRIC_HISTORY TABLE 16 1600.00
SYS SYSAUX WRH$_SYSMETRIC_HISTORY_INDEX INDEX 16 1600.00
SYSMAN SYSAUX MGMT_SYSTEM_PERF_LOG_IDX_01 INDEX 9 900.00
SYS SYSAUX SMON_SCN_TIME TABLE 9 900.00
Back to Segment Statistics
Back to Top
Segments by Physical Write Requests
Total Physical Write Requestss: 1
Captured Segments account for 5.1E+03% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type Phys Write Requests %Total
SYSMAN SYSAUX MGMT_METRICS_RAW_PK INDEX 11 1100.00
SYS SYSAUX SMON_SCN_TIME TABLE 9 900.00
SYSMAN SYSAUX MGMT_SYSTEM_PERF_LOG_IDX_01 INDEX 6 600.00
SYSMAN SYSAUX MGMT_CURRENT_METRICS_PK INDEX 4 400.00
SYS SYSTEM I_JOB_NEXT INDEX 2 200.00
Back to Segment Statistics
Back to Top
Segments by Direct Physical Writes
No data exists for this section of the report.
Back to Segment Statistics
Back to Top
Segments by Table Scans
Total Table Scans: 1
Captured Segments account for 900.0% of Total
Owner Tablespace Name Object Name Subobject Name Obj. Type Table Scans %Total
SYS SYSTEM I_OBJ2 INDEX 9 900.00
Back to Segment Statistics
Back to Top
Segments by DB Blocks Changes
% of Capture shows % of DB Block Changes for each top segment compared
with total DB Block Changes for all segments captured by the Snapshot
Owner Tablespace Name Object Name Subobject Name Obj. Type DB Block Changes % of Capture
SYS SYSTEM I_JOB_NEXT INDEX 896 58.95
SYSMAN SYSAUX MGMT_METRICS_RAW_PK INDEX 160 10.53
SYSMAN SYSAUX MGMT_CURRENT_METRICS_PK INDEX 112 7.37
SYS SYSAUX SMON_SCN_TIME TABLE 80 5.26
SYSMAN SYSAUX MGMT_SYSTEM_PERF_LOG_IDX_01 INDEX 64 4.21
Back to Segment Statistics
Back to Top
Segments by Row Lock Waits
No data exists for this section of the report.
Back to Segment Statistics
Back to Top
Segments by ITL Waits
No data exists for this section of the report.
Back to Segment Statistics
Back to Top
Segments by Buffer Busy Waits
No data exists for this section of the report.
Back to Segment Statistics
Back to Top
Dictionary Cache Stats
No data exists for this section of the report.
Back to Top
Library Cache Activity
No data exists for this section of the report.
Back to Top
Memory Statistics
Memory Dynamic Components
Memory Resize Operations Summary
Memory Resize Ops
Process Memory Summary
SGA Memory Summary
SGA breakdown difference
Back to Top
Memory Dynamic Components
No data exists for this section of the report.
Back to Memory Statistics
Back to Top
Memory Resize Operations Summary
No data exists for this section of the report.
Back to Memory Statistics
Back to Top
Memory Resize Ops
No data exists for this section of the report.
Back to Memory Statistics
Back to Top
Process Memory Summary
No data exists for this section of the report.
Back to Memory Statistics
Back to Top
Back to Memory Statistics
Back to Top
SGA breakdown difference
No data exists for this section of the report.
Back to Memory Statistics
Back to Top
Streams Statistics
Streams CPU/IO Usage
Streams Capture
Streams Capture Rate
Streams Apply
Streams Apply Rate
Buffered Queues
Buffered Queue Subscribers
Rule Set
Persistent Queues
Persistent Queues Rate
Persistent Queue Subscribers
Back to Top
Streams CPU/IO Usage
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Streams Capture
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Streams Capture Rate
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Streams Apply
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Streams Apply Rate
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Buffered Queues
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Buffered Queue Subscribers
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Rule Set
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Persistent Queues
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Persistent Queues Rate
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Persistent Queue Subscribers
No data exists for this section of the report.
Back to Streams Statistics
Back to Top
Resource Limit Stats
No data exists for this section of the report.
Back to Top
Shared Server Statistics
Shared Servers Activity
Shared Servers Rates
Shared Servers Utilization
Shared Servers Common Queue
Shared Servers Dispatchers
Back to Top
Shared Servers Activity
No data exists for this section of the report.
Back to Shared Server Statistics
Back to Top
Shared Servers Rates
No data exists for this section of the report.
Back to Shared Server Statistics
Back to Top
Shared Servers Utilization
No data exists for this section of the report.
Back to Shared Server Statistics
Back to Top
Shared Servers Common Queue
No data exists for this section of the report.
Back to Shared Server Statistics
Back to Top
Shared Servers Dispatchers
No data exists for this section of the report.
Back to Shared Server Statistics
Back to Top
init.ora Parameters
No data exists for this section of the report.
Back to Top
Dynamic Remastering Stats
No data exists for this section of the report.
Back to Top
End of Report
---------------------------------------------->>
here intresting is that i also can't have the memory section view also.i trien to clear awr repositary and recreate it..bounce database,also tried taking different snap value.But does notmake any change.can u tell me why tha happening..and how can i get a good awr report.Hi there,
I have covered this in my blog entry on the subject. Check that link out for more licensing information and other resources.
The problem you are experiencing is caused by the fact that AWR is part of the DIAGNOSTIC and TUNING packs of Oracle 11g, which as of 11g is no longer a standard feature of the database but rather an optional extra which must be licensed in addition to your default Oracle Standard Edition package. In terms of the licensing, you just need to license it as an optional extra so that you will actually be using it legally, and then you can go ahead and enable it.
While it may be an additional licensed item, it is actually installed on your DB by default, but is just not enabled. So, once you have cleared the licensing issue, you will be free to enable diagnostics by setting the new database parameter, CONTROL_MANAGEMENT_PACK_ACCESS. You can do this by running the following as a dba:
<pre>alter system set control_management_pack_access="DIAGNOSTIC+TUNING" scope=both;</pre>
After running this command, your database will start accumulating diagnostic information. Note that you will need to wait until new snapshots are created in which the new diagnostic information will be available. I found that although most of the information became available after setting CONTROL_MANAGEMENT_PACK_ACCESS, it was only once the database was restarted that all of the information became available. I have seen many people reporting similar behavior.
Old snapshots will obviously continue to give the errors because they did not have the diagnostic information available at the time. -
Column p3 (id#/block#) in v$session_wait/v$active_session_history
The environment is 10.2.0.3 in AIX 5.3.0.0 in a two node cluster.
In v$session_wait/v$active_session_history, the column p3 is reffered as
For gc buffer busy waits - id#
and
For buffer busy waits - Class#
(1)Could somebody please explain what exactly these values mean id#/class# and how can we associate them with other statitistics availble to troublshoot the issue?
In my system when I made a query in v$active_session_history it is found that file#(p1) with block# (p2) 287724 is having high count of "gc buffer waits" with tow different values in id# (p3) (pls find below result) The file 16 with block 287724 is having most number of counts for gc buffer busy (with two different id#(??))
EVENT P1 P2 P3 COUNT(*)
gc buffer busy 18 1091724 65537 2
gc buffer busy 16 287724 131073 58
gc buffer busy 7 575153 65537 2
gc buffer busy 13 1528666 65537 1
gc buffer busy 14 843396 65537 2
gc buffer busy 12 1157771 65537 1
gc buffer busy 16 287724 65537 86
gc buffer busy 12 12231 65537 1
gc buffer busy 18 1091732 65537 1
gc buffer busy 11 1642482 65537 2
gc buffer busy 10 1527484 65537 2
EVENT P1 P2 P3 COUNT(*)
gc buffer busy 11 1642497 65537 1
gc buffer busy 14 843396 131073 1
And I found that this is a primary key index with the segment_statistics as follows (from V$SEGMENT_STATISTICS)
OBJECT_NAME STATISTIC_NAME VALUE
PROCESS_LOCK_PK logical reads 18176
PROCESS_LOCK_PK buffer busy waits 33
PROCESS_LOCK_PK gc buffer busy 776
PROCESS_LOCK_PK db block changes 6624
PROCESS_LOCK_PK physical reads 2
PROCESS_LOCK_PK physical writes 64
PROCESS_LOCK_PK physical reads direct 0
PROCESS_LOCK_PK physical writes direct 0
PROCESS_LOCK_PK gc cr blocks received 1991
PROCESS_LOCK_PK gc current blocks receive 2771
PROCESS_LOCK_PK ITL waits 0
OBJECT_NAME STATISTIC_NAME VALUE
PROCESS_LOCK_PK row lock waits 0
PROCESS_LOCK_PK space used 0
PROCESS_LOCK_PK space allocated 0
PROCESS_LOCK_PK segment scans 0
with these available informations how can I solve this problem of "gc buffer busy" waits.
I am not able to find from anywhere what exactly this "id#" is and how can we use it to solve this problem.
Any help will be highly appreciated.
Thanks
N. Sethi
Message was edited by:
user623256Hi,
gc buffer busy
This wait event, also known as global cache buffer busy prior to Oracle 10g, specifies the time the remote instance locally spends accessing the requested data block. This wait event is very similar to the buffer busy waits wait event in a single-instance database and are often the result of:
Hot Blocks - multiple sessions may be requesting a block that is either not in buffer cache or is in an incompatible mode. Deleting some of the hot rows and re-inserting them back into the table may alleviate the problem. Most of the time the rows will be placed into a different block and reduce contention on the block. The DBA may also need to adjust the pctfree and/or pctused parameters for the table to ensure the rows are placed into a different block.
Inefficient Queries ? as with the gc cr request wait event, the more blocks requested from the buffer cache the more likelihood of a session having to wait for other sessions. Tuning queries to access fewer blocks will often result in less contention for the same block.
Please find the below link.. I hope it will help out for you..Since I did not have much idea on RAC ..
http://www.ardentperf.com/2007/09/12/gc-buffer-busy-waits-in-rac-finding-hot-blocks/
Thanks
Pavan Kumar N -
Hi,
we have migrated database from single instance to 2 node RAC recently and since then we have been observing degardation of perfromance.The mostly observed wait events on the database are buffer busy waits and db file sequential read.another observation is that library cache miss rate always hangs above 60%.
It'a documentum application.
The application is using only two tablespaces one for data and another for indexes.Kindly suggest the way in whch i can boost up the perfromance.
vamsiHello,
Well moving from single install to RAC is more then just high availability. You need to do some tuning, and I mean serious tuning.
The are huge amounts of resources out on the web about this. In short here is what you are facing:
"The main way to reduce buffer busy waits is to reduce the total I/O on the system. This can be done by tuning the SQL to access rows with fewer block reads (i.e., by adding indexes). Even if we have a huge db_cache_size, we may still see buffer busy waits, and increasing the buffer size won't help.
The resolution of a "buffer busy wait" events is one of the most confounding problems with Oracle. In an I/O-bound Oracle system, buffer busy waits are common, as evidenced by any system with read (sequential/scattered) waits in the top-five waits."
Hope this helps you get on your way. Check in the database forums for more help, or just have your local DBA tune the database. If he you are running enterprise edition then you should have access to the performance tools, including SQL Tuning advisor, Segment advisor.
When you generate an snapshot report, check if you don't have any ITL waits, see what segments and block the database is hot for. see what SQL statement are hot(meaning how many times its been executed, and how many buffer is reads every time).
Hope this helps.
Jan -
Understanding statspack report(CPU time in top time events)
Hi,
I am using oracle 9.2.0.8 RAC on SUN solaris platform.I am trying to understand my DB statistics using the below statspack report.Can you please coment on the below report
My quetions/thoughts are:
1) CPU time is in the top timed events,Is that eman some need to do with CPU increase.Was CPU bottleneck?
2) Parse CPU to Parse Elapsd %: 80.28 .Is this means I am hard parsing most of the time.How can identify which queries doing more hard parses.what is mean by% Non-Parse CPU: 98.76
3) Memory Usage %: 96.25 96.64.It seems to be there is too much memory usage.Can you elaborate this usage about what could be the reasons for this to happen
4) global cache cr request is coming in the top wait evetns and top timed events.Is there some issue with RAC?
5) can you please explain about 5 CR Blocks Served (RAC) and 5 CU Blocks Served (RAC) and Top 5 ITL Waits per
Your help is appreciated!!
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 2,101,521.49 18,932.15
Logical reads: 91,525.82 824.54
Block changes: 6,720.68 60.55
Physical reads: 5,644.92 50.85
Physical writes: 464.97 4.19
User calls: 922.79 8.31
Parses: 342.37 3.08
Hard parses: 1.52 0.01
Sorts: 324.18 2.92
Logons: 2.66 0.02
Executes: 2,131.75 19.20
Transactions: 111.00
% Blocks changed per Read: 7.34 Recursive Call %: 78.48
Rollback per transaction %: 22.43 Rows per Sort: 15.89
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.66 Redo NoWait %: 100.00
Buffer Hit %: 93.86 In-memory Sort %: 100.00
Library Hit %: 99.95 Soft Parse %: 99.56
Execute to Parse %: 83.94 Latch Hit %: 99.79
Parse CPU to Parse Elapsd %: 80.28 % Non-Parse CPU: 98.76
Shared Pool Statistics Begin End
Memory Usage %: 96.25 96.64
% SQL with executions>1: 34.19 32.67
% Memory for SQL w/exec>1: 39.87 40.47
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
CPU time 10,406 42.54
db file sequential read 1,707,372 4,282 17.51
global cache cr request 2,566,822 2,369 9.68
db file scattered read 1,109,892 1,719 7.03
SQL*Net break/reset to client 17,287 1,348 5.51
Wait Events for DB: Instance:
-> 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
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
db file sequential read 1,707,372 0 4,282 3 8.5
global cache cr request 2,566,822 3,356 2,369 1 12.8
db file scattered read 1,109,892 0 1,719 2 5.5
SQL*Net break/reset to clien 17,287 0 1,348 78 0.1
buffer busy waits 312,198 11 1,082 3 1.6
Message was edited by:
user509266This statspack taken for 30 minutes interval.We have 16 CPU's.We never got ORA-4031 errors.It means you have 16 * 30 * 60 = 28,800 seconds CPU available during the interval but you only used 10,406. So you don't have a CPU problem.
For Statspack documentation, you can have a look to <ORACLE_HOME>/rdbms/admin/spdoc.txt, Metalink note 228913.1, Jonathan Lewis Scratchpad, books commended by Rajesh Kumar Yogi and also to http://www.oracle.com/technology/deploy/performance/index.html -
Oracle 11g Performance (DW or OLTP)
Hi
I have a what I consider a large oracle database, that I'm having performance problems with. It is designed as a star schema with a very large fact table (15 billion records) and one of the dimensions has 1 Billion records. The data is being inserted is split 10/90 between batch and single inserts and that table space is defined as 8k. Currently there are 100Million inserts a day into the fact table and we would like to tripple that load. Select response takes hours, the raw space being used is 6TB including all the index overhead.
Does anyone have any advise? It this database considered OLTP or DW? The fact table (PARAMETER_VALUE) average row size is 46 bytes.
This is my fact table
CREATE TABLE PARAMETER_VALUE
PARAMETER_VALUE_KEY NUMBER NOT NULL,
PARAMETER_TYPE_KEY NUMBER NOT NULL,
PARAMETER_VALUE_TIMESTAMP TIMESTAMP(6) NOT NULL,
TEST_EVENT_KEY NUMBER,
DEVICE_KEY NUMBER,
RESOURCE_KEY NUMBER,
RAW_RESOURCE_KEY NUMBER,
PARAMETER_VALUE_CHAR VARCHAR2(2000 BYTE),
PARAMETER_VALUE_NUMBER NUMBER,
PARAMETER_VALUE_HEX RAW(2000),
PARAMETER_DATA_QUALITY CHAR(1 BYTE) DEFAULT 'G' NOT NULL,
CONSTRAINT CKC_PARAMETER_DATA_QU_PARAMETE
CHECK (PARAMETER_DATA_QUALITY in ('G','B','Q')),
CONSTRAINT CKT_PARAMETER_VALUE
CHECK ((DECODE(RESOURCE_KEY,NULL,0,1) + DECODE(DEVICE_KEY,NULL,0,1) + DECODE(RAW_RESOURCE_KEY,NULL,0,1) ) = 1),
CONSTRAINT CKT_PARAMETER_VALUE_VALUE
CHECK ((DECODE(parameter_value_char,NULL,0,1) + DECODE(parameter_value_number,NULL,0,1) + DECODE(parameter_value_hex,NULL,0,1) ) = 1),
CONSTRAINT PARAMETER_VALUE_PK
PRIMARY KEY
(PARAMETER_VALUE_KEY)
USING INDEX
TABLESPACE HPS_STG_INDEX,
CONSTRAINT PARAMETER_VALUE_AK
UNIQUE (PARAMETER_VALUE_TIMESTAMP, PARAMETER_TYPE_KEY, RESOURCE_KEY, DEVICE_KEY, RAW_RESOURCE_KEY)
USING INDEX LOCAL,
CONSTRAINT PARM_VALUE_DEVICE_FK
FOREIGN KEY (DEVICE_KEY)
REFERENCES HPS_STG.DEVICE (DEVICE_KEY),
CONSTRAINT PARM_VALUE_NETWORK_RESOURCE_FK
FOREIGN KEY (RESOURCE_KEY)
REFERENCES HPS_STG.NETWORK_RESOURCE (RESOURCE_KEY),
CONSTRAINT PARM_VALUE_NR_RAW_FK
FOREIGN KEY (RAW_RESOURCE_KEY)
REFERENCES HPS_STG.NETWORK_RESOURCE_RAW (RAW_RESOURCE_KEY),
CONSTRAINT PARM_VALUE_PARM_TYPE_FK
FOREIGN KEY (PARAMETER_TYPE_KEY)
REFERENCES HPS_STG.PARAMETER_TYPE (PARAMETER_TYPE_KEY),
CONSTRAINT PARM_VALUE_TEST_EVENT_FK
FOREIGN KEY (TEST_EVENT_KEY)
REFERENCES HPS_STG.TEST_EVENT (TEST_EVENT_KEY)
DEFERRABLE INITIALLY IMMEDIATE
TABLESPACE HPS_STG_DATA
PARTITION BY RANGE (PARAMETER_VALUE_TIMESTAMP)
SUBPARTITION BY HASH (PARAMETER_TYPE_KEY)
SUBPARTITION TEMPLATE
(SUBPARTITION SP01 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP02 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP03 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP04 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP05 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP06 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP07 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP08 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP09 TABLESPACE HPS_STG_DATA,
SUBPARTITION SP10 TABLESPACE HPS_STG_DATA
INTERVAL( NUMTOYMINTERVAL(1,'MONTH'))
PARTITION PARAMETER_TIME_PART_01 VALUES LESS THAN (TIMESTAMP' 2008-11-01 00:00:00')
COMPRESS FOR DIRECT_LOAD OPERATIONS
TABLESPACE HPS_STG_DATA
( SUBPARTITION PARAMETER_TYPE_PART_01_SP01 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP02 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP03 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP04 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP05 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP06 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP07 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP08 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP09 TABLESPACE HPS_STG_DATA,
SUBPARTITION PARAMETER_TYPE_PART_01_SP10 TABLESPACE HPS_STG_DATA ),
This is my very large dimension table
CREATE TABLE TEST_EVENT
TEST_EVENT_KEY NUMBER NOT NULL,
EVENT_NAME VARCHAR2(32 BYTE) NOT NULL,
EVENT_TYPE VARCHAR2(32 BYTE),
EVENT_START_TIMESTAMP TIMESTAMP(6) NOT NULL,
EVENT_END_TIMESTAMP TIMESTAMP(6),
EVENT_DATA_QUALITY CHAR(1 BYTE) DEFAULT 'G' NOT NULL,
CONSTRAINT CKC_EVENT_DATA_QUALITY
CHECK (EVENT_DATA_QUALITY in ('G','B','Q')),
CONSTRAINT TEST_EVENT_PK
PRIMARY KEY
(TEST_EVENT_KEY)
USING INDEX
TABLESPACE HPS_STG_TEST_EVENT_INDEX
TABLESPACE HPS_STG_TEST_EVENT_DATA
PARTITION BY RANGE (EVENT_START_TIMESTAMP)
INTERVAL( NUMTOYMINTERVAL(1,'MONTH'))
PARTITION TEST_EVENT_PART_01 VALUES LESS THAN (TIMESTAMP' 2009-01-01 00:00:00')
COMPRESS FOR ALL OPERATIONS
TABLESPACE HPS_STG_DATA,
Would reference partition help? Would 32K tablespace help? I'm experiencing a lot or ITL waits on the Fact table.A good starting point would be to read Tim Gorman's paper about scaling to infinity. It seems likely that you will want to figure out a way that new data finds its way into your DW through some variety of partition exchange. Even if that is not the case, Tim's excellent paper should help you to frame your thinking on the subject in a useful way.
Good luck,
mwf -
Hi,
This an outpout of two hours awr report of EBS oracle version 10203.
Its shows few ITL locks that should be fixed by increasing the size of the INITRANS to 20.
Currently the INITRANS is set to 11.
The FREELIST is set to 4 and also the FREELIST GROUP is set to 4
There are 8 indexes on this table (they are all have the same INITRANS+FREELIST+FREELIST GROUP)
The table contain 250 million records.
The table is not partitioned.
How can i find which of the 8 indexes i should deal with ?
They are all start with the name: "RA_CUST_TRX_LINE_GL_" ?
Would you consider doing more things beside increasing the INITRANS ?
My second question is regarding the last section which shows the
same indexes waiting on Buffer Busy Waits .
Is there an event that i can use in order to find what cause the
index to wait so many times ?
Please note that the issue is not if to partition the table or not , i already working in test env. to partition the table.
I would like to get your advices regarding the current situation.
Thanks
tagSegments by ITL Waits DB/Inst: xxx/xxx Snaps: 8311-8313
-> % of Capture shows % of ITL waits for each top segment compared
-> with total ITL waits for all segments captured by the Snapshot
Tablespace Subobject Obj. ITL % of
Owner Name Object Name Name Type Waits Capture
AR AR_INDEX1 RA_CUST_TRX_LINE_GL_ INDEX 10 18.18
AR AR_INDEX1 RA_CUSTOMER_TRX_LINE INDEX 9 16.36
AR AR_INDEX1 RA_CUST_TRX_LINE_GL_ INDEX 9 16.36
AR AR_INDEX1 AR_PAYMENT_SCHEDULES INDEX 5 9.09
AR AR_INDEX1 AR_PAYMENT_SCHEDULES INDEX 5 9.09
Segments by Buffer Busy Waits DB/Inst: xxx/xxx Snaps: 8311-8313
-> % of Capture shows % of Buffer Busy Waits for each top segment compared
-> with total Buffer Busy Waits for all segments captured by the Snapshot
Buffer
Tablespace Subobject Obj. Busy % of
Owner Name Object Name Name Type Waits Capture
AR AR_INDEX1 RA_CUST_TRX_LINE_GL_ INDEX 41,671 20.30
AR AR_INDEX1 RA_CUST_TRX_LINE_GL_ INDEX 22,248 10.84
AR AR_INDEX1 IL_RA_CUST_TRX_LINE_ INDEX 18,067 8.80
AR AR_INDEX1 RA_CUST_TRX_LINE_GL_ INDEX 15,571 7.58
AR AR_DATA RA_CUST_TRX_LINE_GL_ TABLE 15,075 7.34
tagHi Mr Lewis,
You wrote :
tagChecking buffer busy waits - you need to know whether these are "read by other session"
or "real" buffer busy waits as this part of the report doesn't distinguish the classes.
So check the wait times again for "read by other session" and "buffer busy waits" to see what the spread is.I recheck the AWR report and found at the top 5 events: read by other session
tagTop 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
CPU time 10,998 39.9
db file sequential read 2,545,797 8,793 3 31.9 User I/O
read by other session 1,081,643 2,852 3 10.4 User I/O
library cache pin 18,450 1,253 68 4.5 Concurrenc
db file scattered read 115,039 1,226 11 4.5 User I/O
-------------------------------------------------------------And also:
tag Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
db file sequential read 2,545,797 .0 8,793 3 142.3
read by other session 1,081,643 .0 2,852 3 60.4
library cache pin 18,450 .1 1,253 68 1.0
db file scattered read 115,039 .0 1,226 11 6.4
log file parallel write 111,366 .0 803 7 6.2
SQL*Net more data from clien 28,701 .0 661 23 1.6
enq: TX - index contention 25,492 .0 303 12 1.4
log file sync 14,065 .0 205 15 0.8
latch: cache buffers chains 670,408 .0 135 0 37.5
Log archive I/O 6,751 .0 120 18 0.4
library cache load lock 1,539 .0 97 63 0.1
buffer busy waits 234,058 .0 61 0 13.1So, there is 5 times more : "read by other session" than "buffer busy waits".
What that mean ? what should i check ?
Thanks Again -
Hi All,
Can somebody please please tell some ways in which i can improve the data buffer quality? Presently it is 51.2%. The DB is 10.2.0.2.0
I want to know, wat all factors do i need to keep in mind if i want to increase DB_CACHE_SIZE?
Also, i want to know how can i find out Cache Hit ratio?
Further, i want to know which are the most frequently accessed objects in my DB?
Thanks and Regards,
Nick.Nick-- wud b DBA wrote:
Hi Aman,
Thanks. Can u please give the appropriate query for that?
And moreover when i'm giving:
SQL>desc V$SEGMENT-STATISTICS; It is giving the following error:
SP2-0565: Illegal identifier.
Regards,
Nick.LOL dude I put it by mistake. Its dash(-) sign but we need underscore(_) sign.
About the query, it may vary what you really mean by "most used obect". If you mean to find the object that is undergoing lots of reads,writes than this may help,
SELECT Rownum AS Rank,
Seg_Lio.*
FROM (SELECT St.Owner,
St.Obj#,
St.Object_Type,
St.Object_Name,
St.VALUE,
'LIO' AS Unit
FROM V$segment_Statistics St
WHERE St.Statistic_Name = 'logical reads'
ORDER BY St.VALUE DESC) Seg_Lio
WHERE Rownum <= 10
UNION ALL
SELECT Rownum AS Rank,
Seq_Pio_r.*
FROM (SELECT St.Owner,
St.Obj#,
St.Object_Type,
St.Object_Name,
St.VALUE,
'PIO Reads' AS Unit
FROM V$segment_Statistics St
WHERE St.Statistic_Name = 'physical reads'
ORDER BY St.VALUE DESC) Seq_Pio_r
WHERE Rownum <= 10
UNION ALL
SELECT Rownum AS Rank,
Seq_Pio_w.*
FROM (SELECT St.Owner,
St.Obj#,
St.Object_Type,
St.Object_Name,
St.VALUE,
'PIO Writes' AS Unit
FROM V$segment_Statistics St
WHERE St.Statistic_Name = 'physical writes'
ORDER BY St.VALUE DESC) Seq_Pio_w
WHERE Rownum <= 10; But if you are looking for the objects which are most highly in the waits than this query may help
select * from
select
DECODE
(GROUPING(a.object_name), 1, 'All Objects', a.object_name)
AS "Object",
sum(case when
a.statistic_name = 'ITL waits'
then
a.value else null end) "ITL Waits",
sum(case when
a.statistic_name = 'buffer busy waits'
then
a.value else null end) "Buffer Busy Waits",
sum(case when
a.statistic_name = 'row lock waits'
then
a.value else null end) "Row Lock Waits",
sum(case when
a.statistic_name = 'physical reads'
then
a.value else null end) "Physical Reads",
sum(case when
a.statistic_name = 'logical reads'
then
a.value else null end) "Logical Reads"
from
v$segment_statistics a
where
a.owner like upper('&owner')
group by
rollup(a.object_name)) b
where (b."ITL Waits">0 or b."Buffer Busy Waits">0)This query's reference:http://www.dba-oracle.com/t_object_wait_v_segment_statistics.htm
So it would depend upon that on what ground you want to get the objects.
About the cache increase, are you seeing any wait events related to buffer cache or DBWR in the statspack report?
HTH
Aman.... -
Hi
My 11.1.0.6 database on Windows is 16K Block Size and the tables has huge inserts and updates.
To set the correct values for PCTUSED and PCTFREE as Tablespace is in no ASSM , i checked the avg_row_len of a table , it shows 45.
My questions are
1) This value for avg_row_len is in Bytes ?
2) I set the PCT USED value to 70 and PCT Free to 30, is this good ?
3) Setting PCT USED to lower value will have less I/O ?
I would appreciate if some one could through light on these points
Thanks YOu1) This value for avg_row_len is in Bytes ?
yes
2) I set the PCT USED value to 70 and PCT Free to 30, is this good ?
it depends on the table access like how many DML operations done concurently, etc.
3) Setting PCT USED to lower value will have less I/O ?
if concurency level is high, there is chance that more sessions may try to access the same block simultaneously. so in this case if PCT USED is less, less data exists per block, so contention for the block can be reduced. but more number of blocks will read/written, increases the logical/physical IO.
anlyze AWR reports to get the better understanding of your database with respect to IO, CPU, concurency like ITL waits, buffer waits, etc.
Thanks,
Siva
Maybe you are looking for
-
Hello, i´ve written a FM which also calls SAP FM´s. Somewhere there is this statement: else. message w207(m7) with ymcha-charg ymcha-matnr. endif. This line throws an error... Because the FM is used in a job, this job
-
A/P Invoice entered incorrectly
I have copied a GRPO, but made some change in the price by mistake, and added the document. How do I reverse it. If I do credit memo, then the transaction is reversed, but I don't have any link to create a new AP Invoice based on the base document. D
-
My desktop image will not resize no matter what I do.
For some reason, I cannot get the images that I use as my desktop wallpaper to do anything but "full screen". I've done restarts and tried every type of image display and nothing works. I have some great wallpaper images, but unless I can do "fit to
-
Hello guys, i want to know this for a long time. How can I make a 3D Cube Transition (like that in Linux or MAC desktop) to use with MovieClips. Go see this component here. I hope that you can help me making this. Compliments.
-
Monitor IBM x server hardware component runing Linux
We'd like to monitor IBM x server hardware component, we knew there is a IBM MP. However, the official document said: "Extensive monitoring of the health of hardware components for IBM System x servers and BladeCenter x86/x64 bladesrunning Windows" M