High query IO wait

I have a query that take huge amount of IO waits:
table address (ENT_ID, ADDR1, ADDR2,CITY, STATE, zip, COUNTRY, ADDR_ID, ACCT_ID, VALID_FROM_DT, VALID_THRU_DT, STAT, addr_hash, sys_delete_dt, mhh,ADDR_TYPE)
single reversed indexes on ADDR_HASH, acct_id, addr_id
Composite PK on ENT_ID, ADDR_TYPE, ACCT_ID, STAT
here is the query:
SELECT ENTITY_ID, ADDR1, CITY, STATE, zip, COUNTRY, ADDR_ID, ACCT_ID, VALID_FROM_DT, VALID_THRU_DT FROM ADDRESS WHERE ADDR_HASH = :1 AND SYS_DELETE_DT IS NULL;
The query uses the right index on addr_hash to obtain TABLE ACCESS BY INDEX ROWID over the index range scan.
Please advise what can I do to optimize this query?
Thanks a lot,mj

Yes, it was analyzed earlier yesterday immediatelly before the processes start hitting the DB. - 10.1.0.4/aix 5.3
I do not see anything wrong with the execution to require so long IO waits.... Please, let me know what I did oversee...
The IO wait time is measured by the query:
select distinct sql_text, sql_id, elapsed_time, cpu_time, user_io_wait_time
from sys.v_$sqlarea
order by 5 desc;
Execution Plan
0 SELECT STATEMENT Optimizer=FIRST_ROWS (Cost=1 Card=1 Bytes=3
23)
1 0 TABLE ACCESS (BY INDEX ROWID) OF 'ADDRESS' (TABLE) (Cost=1
Card=1 Bytes=323)
2 1 INDEX (RANGE SCAN) OF 'IX_ADDR_HASH' (INDEX) (Cost=1 Car
d=1)
Statistics
1 recursive calls
0 db block gets
4 consistent gets
1 physical reads
0 redo size
449 bytes sent via SQL*Net to client
235 bytes received via SQL*Net from client
1 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
0 rows processed
Thanks a lot,mj

Similar Messages

  • High I/O wait observed in Linux based Oracle Database Server

    Hi,
    We have just migrated Oracle Database from Solaris Server to Linux VM [ESX] server.
    We have observed that there is high I/O wait issues while database query is running on Linux VM, which was ideally zero in case of Solaris. The same Database was running with no i/o wait on solaris physical server.
    In the same ref.I would like to below points.
    - Recommendations for running Oracle on VM based Linux.
    - Recommendations from ESX Host side
    Please suggest.

    user558914 wrote:
    We have just migrated Oracle Database from Solaris Server to Linux VM [ESX] server.
    We have observed that there is high I/O wait issues while database query is running on Linux VM, which was ideally zero in case of Solaris. The same Database was running with no i/o wait on solaris physical server.What did you expect? A virtualised I/O subsystem to respond and perform like a real one?
    That would a very unrealistic expectation. And as comparisons go, as sensible as comparing the taste of an apple with the odour of the colour blue.
    Forget about comparisons. Only marketing, sales and the idiot believe the cr@p that introducing several s/w layers between the the target (e.g. sector on spinning rust) and the destination (e.g. Oracle) makea the path between target and destination, faster.
    To optimise the virtualised target, you need to make the path as short as possible. If your virtual disk is for example a file on a cooked file system on the host, then you are introducing the host's complete I/O layer for accessing that virtual drive. If your virtual disk is an actual (raw) partition or drive on the host, then path is faster - passing through the host kernel as direct I/O and bypassing the host's cache and file system drivers.
    I suggest that when you setup your virtualised environment, you do proper stress testing of the various configurations of a virtualised I/O subsystem, using something like fio.

  • Update query is waiting for async descriptor resize

    Hi All,
    One of the update query which was completing in 1-2 mins. Suddenly today it started taking more than 3-4 hours and still it is running.
    Below is the query, I can see the explain plain. I can see the query is waiting for async descriptor resize wait event
    UPDATE AP_INVOICE_DISTRIBUTIONS SET POSTED_FLAG = 'N' WHERE POST
    ED_FLAG = 'S' AND (ACCOUNTING_DATE >= :B2 OR :B2 IS NULL) AND (A
    CCOUNTING_DATE <= :B1 OR :B1 IS NULL)
    when i checked the P1text, P2text columns of v$session, it is showing outstanding #aio,current ai0 limit respectively.
    Explan plan
    CODEPLAN_TABLE_OUTPUT
    | Id  | Operation                      | Name                         | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | UPDATE STATEMENT               |                              |       |       |   250 (100)|          |
    |   1 |  UPDATE                        | AP_INVOICE_DISTRIBUTIONS_ALL |       |       |            |          |
    |   2 |   NESTED LOOPS                 |                              |       |       |            |          |
    |   3 |    NESTED LOOPS                |                              |    39 | 12480 |   250   (0)| 05:14:02 |
    |*  4 |     TABLE ACCESS BY INDEX ROWID| AP_ACCOUNTING_EVENTS_ALL     |    39 |   624 |   145   (0)| 03:02:09 |
    |*  5 |      INDEX RANGE SCAN          | AP_ACCOUNTING_EVENTS_N2      |  3954 |       |    14   (0)| 00:17:36 |
    |*  6 |     INDEX RANGE SCAN           | AP_INVOICE_DISTRIBUTIONS_N18 |     4 |       |     2   (0)| 00:02:31 |
    PLAN_TABLE_OUTPUT
    |*  7 |    TABLE ACCESS BY INDEX ROWID | AP_INVOICE_DISTRIBUTIONS_ALL |     1 |   304 |     4   (0)| 00:05:02 |
    CODE
    Please help me on this.
    Env Details --
    DB version -- 11.2.0.1
    OS - IBM AIX.
    Thanks in advance...

    This could be this bug
    Bug 9829397 - Excessive CPU and many "asynch descriptor resize" waits for SQL using Async IO (Doc ID 9829397.8)

  • High buffer busy wait

    hi all ,
    How to resolve high buffer busy wait in my DB.

    Simple: reduce your I/O requirements.
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1860222500346889715
    So you need to find out what's causing your high I/O requirements, and then see if you can fix that.

  • 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 ) ?

  • Why does Lightroom 4.3 use very high cpu when waiting for user to click OK?

    I saved metadata for 52 photos. 
    Lightroom 4.3 couldn't save metadata for 2 of the photos and opened a window to tell me so. (It had no problem saving metadata on second attempt.)
    While it waited for my response and wasn't doing any work, it was using over 50% of my CPU.
    Why?
    Windows 7 is 32-bit Professional.
    Processor: Intel Core i5 750 Processor 2.66 GHz
    Here's my system info as reported by Lightroom. 
    Lightroom version: 4.3 [865747]
    Operating system: Windows 7 Business Edition
    Version: 6.1 [7601]
    Application architecture: x86
    System architecture: x86
    Logical processor count: 4
    Processor speed: 2.7 GHz
    Built-in memory: 3579.4 MB
    Real memory available to Lightroom: 716.8 MB
    Real memory used by Lightroom: 710.9 MB (99.1%)
    Virtual memory used by Lightroom: 847.9 MB
    Memory cache size: 2.0 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
    Library Path: D:\Users\Calvin\Pictures\My Lightroom\lightroom\lightroom4\lightroom4.lrcat
    Settings Folder: C:\Users\Calvin\AppData\Roaming\Adobe\Lightroom
    Adapter #1: Vendor : 10de
        Device : 640
        Subsystem : c9593842
        Revision : a1
        Video Memory : 1007
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (Realtek High Definition Audio)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    Direct2DEnabled: false
    GL_ALPHA_BITS: 0
    GL_BLUE_BITS: 8
    GL_GREEN_BITS: 8
    GL_MAX_3D_TEXTURE_SIZE: 2048
    GL_MAX_TEXTURE_SIZE: 8192
    GL_MAX_TEXTURE_UNITS: 4
    GL_MAX_VIEWPORT_DIMS: 8192,8192
    GL_RED_BITS: 8
    GL_RENDERER: GeForce 9500 GT/PCIe/SSE2
    GL_SHADING_LANGUAGE_VERSION: 3.30 NVIDIA via Cg compiler
    GL_VENDOR: NVIDIA Corporation
    GL_VERSION: 3.3.0
    OGLEnabled: true
    OGLPresent: true
    GL_EXTENSIONS: GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

    I don't think so. 
    I have enough experience with LR to know what to expect for various activities. 
    Previews for all photos had been rendered long before I initiated the Save Metadata.
    Metadata for 50 of the 52 files had already been written. 
    The high cpu had gone on for at least 5 minutes.   I switched to another app imediately after initiating the Save Metadata for the 52 files and only went back to LR when I heard my CPU fan running for a long time.
    When I got back to LR, I saw the "Could not save metadata" window.  I clicked "Show in Library" and OK.  As soon as I did that, CPU usage went back to normal. 
    I've experienced the exact same scenario, where LR can't save metadata for all photos and I've never had LR get stuck consuming a very large amount of CPU.
    As a test, I selected 118 other photos, changed metadata for all of them and then selected all and saved metadata.  LR took about 20 seconds to save metadata for all 118 and LR CPU usage never went above 17%.  The difference is that LR did not show the "Could not save metadata" window.

  • Very high data block waits

    I have one table xxxx in a tablespace tbx and the tablespace tbx has only 1 datafile. The table xxxx size is 890MB w/ 14 millions records. The datafile size is 2048MB. This table is a frequently access with insert/delete/select. The system spends alot of time waiting on this datafile. If I create a new tablespace abc with 20 datafiles worth about 100MB each, would it help reducing the data block wait count? The pctfree/pctused is 10/40 respectively.
    Can anyone please give me an how to resolve this?

    I am looking at an Oracle Statistics. We use SAN technology with RAID 0+1 Striped across all disks.
    First I use this query to get the wait statistics:
    select time, count, class
    from v$waitstat
    order by time, count;
    From this query above, I got this result and database just been up 02/17/2004, just about 4 days ago:
    TIME COUNT CLASS
    0 0 sort block
    0 0 save undo block
    0 0 save undo header
    0 0 free list
    0 0 bitmap block
    0 0 unused
    0 0 system undo block
    0 0 system undo header
    0 0 bitmap index block
    10 10 extent map
    48 656 undo header
    271 853 undo block
    301 730 segment header
    780382 1214405 data block
    Then I use this query to find which datafile is being hit the most:
    select count, file#, name
    from x$kcbfwait, v$datafile
    where indx + 1 = file#
    order by count desc;
    The query above returned:
    COUNT     FILE#     NAME
    473324     121     /xx/xx_ycm_tbs_03_01.dbf
    104179     120     /xx/xx_ycm_tbs_02_01.dbf
    93336     118     /xx/xx_idx_tbs_03_01.dbf
    93138     119     /xx/xx_idx_tbs_03_02.dbf
    80289     90     /xx/xx_datafile67.dbf
    64044     108     /xx/xx_ycm_tbs_01_01.dbf
    61485     41     /xx/xx_datafile25.dbf
    61103     21     /xx/xx_datafile8.dbf
    57329     114     /xx/xx_ycm_tbs_01_02.dbf
    29338     5     /xx/xx_datafile02.dbf
    29101     123     /xx/xx_idx_tbs_04_01.dbf
    file# 121 is in a tablespace with this only datafile and this tablespace hold only one table. file#120 is the same thing, it's in another tablespace and only one table in that tablespace.
    At the same time, i use TOP in Solaris I see iowait range between 5-25% during busy hour.

  • Tkprof High query value

    Hi friend;
    I have one tkrpof and end of the file the query value is too high like 43830952, what doest it mean? How i can solve this problem

    Yes you can :) You need to use \ tags.
    \Your text here\yieldsYour text hereThe query column reflects the number of logical I/Os performed. So it looks like you performed 43,830,952 logical I/Os in roughly 33 minutes. What I would do personally is if you are having performance problems try and identify the query or queries in the TKPROF report that are performing the most I/O or have the highest elapsed time.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • High I/O  waits

    Any thoughts about why, when Streams capture processes are started up, the disk activity pegs i/o waits constantly high. It is pretty much slow down the whole database server.
    This is the state of CPU when we have streams instance up and without any dml activity.
    CPU states: 0.4% idle, 17.9% user, 4.5% kernel, 77.2% iowait, 0.0% swap
    Any suggestion to any parameters tweaking or recommendation is truly appreciated.

    Hi
    I have found this also, and have just raised an ITAR on it. On our new 10G servers the Capture process constantly re-reads the whole of the current log file. On one of our servers it is reading 110MB of data / second. As soon as we stop the 2 capture processes it IO drops to nothing.
    Is this exactly what you are seeing. Does anyone out there have any ideas on a fix.
    Thanks

  • Exremely high (98%) roll wait time

    I am running a ECC 6.0 EHP4 server in solaris 5.10 OS, Oracle 10.2.0.4.
    My users experience extremely high roll wait time when they execute transactions like PA20/PA30. It took about 20 minutes for it to load.
    I ran stad and found out the majority of the portion is wasted at roll wait time. How do we know what caused the wait time?
    e.g. user execute TCODE PA20 and wait for the hourglass for about 20 minutes before the record is shown
    Other transactions ran smoothly.
    Your help is appreciated.

    After a RFC trace, it showed this RFC statement having very high duration:
    RFC Statement
    Function module name      HTTP_GET
    Source IP Address         a.b.c.d
    Source Server             ourSECCServer
    Destination IP Address    a.b.c.d (same ip as source)
    Destination Server        ourSECCServer
    Client/Server             Client
    Conversation ID
    RFC Trace Rec. Status     4
    Sent Bytes                9.476
    Received Bytes            3.353
    Total Sent Bytes
    Total Received Bytes
    ABAP program name         SAPLSFTP
    RFC Time                  224881.681
    Any ideas?

  • Abnormal high "query" count in customer tkprof output

    We have a performance problem with one of our customer.
    A query is made on a 12K rows table, and there is no full scan, the index is used.
    If we run the query on our test database, which is identical, and examine the tkprof output, things appears normal:
    Fetch=80, cpu=0.0, disk=0, query=15738,rows=782
    But the same query, on and identical table, same index at our customer:
    Fetch=831, cpu=4.75, disk=141, query=550564, rows=830
    I dont unerstand what is the "query" parameter, the number of cache buffers read in memory ?
    It is unbeleivebly high, further more, hard to understand high number of rows in the execution plan:
    Ours
    1570 TABLE ACCESS BY INDEX ROWID MY_SECRET_TABLE_NAME
    1570 INDEX RANGE SCAN MY_PRIMARY_KEY_INDEX
    Customers:
    88413 TABLE ACCESS BY INDEX ROWID MY_SECRET_TABLE_NAME
    92917 INDEX RANGE SCAN MY_PRIMARY_KEY_INDEX
    We dont understand such high numbers. On theory, from our former DBA, was that our indexes where not create properly. A unique key index was create, then a primary constraint with the same name, was added to the table. Apparently we should have created only the constraint, and not the second index.
    Any help appreciated.

    Hi Guy,
    Query = db block gets + consistent gets.
    Consistent gets are the block reads you need to reconstruct a read-consistent image of the data.
    If you can't fetch all records at a time, you will get multiple fetches. At each fetch Oracle will issue consistent gets, as it needs to provide to you the data in the state when you started the query.
    Looking at your statistics, it is quite clear what happened.
    Fetch=80, cpu=0.0, disk=0, query=15738,rows=782
    782 rows in 80 fetches. Roughly 10 rows per fetch.
    But the same query, on an identical table, same index at our customer:
    Fetch=831, cpu=4.75, disk=141, query=550564, rows=830
    830 rows in 830 fetches (the last fetch is to check there is no more data), which means 1 row per fetch.
    In both cases: consistent gets at every fetch.
    Somehow your client has made sure, by means of a setting, he will fetch only 1 row at a time. And that is killing him.
    Nothing wrong with any index.
    Hth
    Sybrand Bakker
    Senior Oracle DBA

  • For Update Query with Wait Clause from ORACLE Forms

    Hi
    We are using Oracle Forms 10g running with 10g database 10.2.0.1.0. We happend to see a query which is getting generated in AWR report like Select rowid, all_columns from TableName for Update of C1 Nowait. But no such query is really written in forms and we are aware that, Any query prefixed with rowid is definitely executing from Forms. But how the ForUpdate and Nowait clause is appended to the query.
    We have checked the following properties in the database Block
    *1) Locking Mode is set to Automatic*
    *2) Update Changed Columns only is set to YES*
    *3) Query all records is set to No (Though this particular property may not be relevant to the issue)*
    What is the property or setting which might trigger such a query from ORACLE Forms with ForUpdate and Nowait clause.
    Any ideas/suggestions on why such behaviour. Please have a healthy discussion on this. Thanks in advance.

    Why have you started another thread on the same thing?
    FOR UPDATE cursor is causing Blocking/ Dead Locking issues
    Just use one thread to avoid confusion.
    The fact that nobody has answered on the other thread for a couple of days could be to do with it being the weekend and most people are not at work.
    Either be patient or, if it's more "urgent" than that, raise a SR/Tar with Oracle metalink.

  • Query on Waiting state under V$SESSION

    Hi ALL,
    I want to know what is blocking my query which is just a simple select SQL statement
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE     10.2.0.4.0     Production
    TNS for Linux: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Since it is a prod environment , underlying tables are analyzed...

    Nikhil Juneja wrote:
    Hi ALL,
    I want to know what is blocking my query which is just a simple select SQL statementpost SQL & result that show above is true.
    SELECT are not "blocked" in Oracle.

  • High virtual circuit wait event

    Hi,
    in my 11g Enterprise Edition Database I have a problem with some sessions that are almost always in virtual circuit wait event. What is this wait event and how can I troubleshoot it?
    IMPORTANT: I'm not using XDB or APEX
    Edited by: Insaponata on Jan 9, 2011 8:00 AM

    From awr report based on the last our of work I see:
    Top 5 Timed Foreground Events
    Event     Waits     Time(s)     Avg wait (ms)     % DB time     Wait Class
    virtual circuit wait     95,038     16,056     169     263.91     Network
    DB CPU          305          5.02     
    SQL*Net message from dblink     42,432     48     1     0.79     Network
    db file sequential read     21,990     48     2     0.78     User I/O
    db file scattered read     26,021     36     1     0.59     User I/O
    Do you think that this situation is normal? If no, how can I troubleshoot?

  • RSRT statistics data - high query runtime

    Hi
    I have a query on a multiprovider that has a few fields with exception aggregation upto 2 levels - doc number and item. I executed the query in RSRT with "Display Statistics data" and "Do not use cache" settings from the debug options. When i go to the Aggregation Layer tab of the stats screen i see that the basic infoprovider and the aggregates are listed twice or thrice. The infoproviders have a huge volume of data and the number of records read and transported for the duplicate entries shown are the same.
    Initially i thought it is because of the 2 levels of exception aggregation but then i ran another query on the same multiprovider with similar exception aggregation and found that there are no duplicate entries and the basic inproviders are read only once.
    the query is running very slow and i need to tune up the performance.
    I would like to know why is the infoprovider being read twice for this query alone??
    Regards,
    Sujai

    ok! Then it could be because of some other reasons why it is reading twice. This won't be happening because of nested Exception aggregarion.
    Try to make the query same one by one and check what is making the query to read the infoprovider twice.

Maybe you are looking for

  • [Athlon64] CPU cant see my other HD I want to use for storage

    Ok so I have the msi k8n-neo v with 3000+ athlon 64, Im running win xp 32, I had too much problems with win xp 64 ( wasnt running my games well ) ANYHOO... I have a 120 gig sata WD HD, now I have this other HD WD 40gig but its not SATA.  It has windo

  • Installing Oracle 9i Server

    Hi everyone I had Windows 2000, now I have windows XP. I have a PIII 870MHz with 256Mb RAM. I am trying to reinstall Oracle. It worked fine the first time I installed it then I tried to deinstall it and reinstall it. It now hangs when it get to "Proc

  • How to set bind parameter in vo in execute method

    Hi, I m using this Query in VO.There are 7 bind variables i want to set the bind parameter before calling the execute Query of VO but i m unable to set values in bind parameter. I am getting the values in sysout but when trying to print the query by

  • How to save the image on the web through java code?

    Suppose a picture can be loaded on the browser, and nothing else. If I want to use a jave code to intercept the picture and save it into a file, what does the code look like? I know the URL of the picture. Thanks.

  • Green shadows when scrolling text after calibration

    Hello, I'm having strange screen behavior after calibrating it (I'm using Spyder 3 hardware with both its own software and ColorEyes DisplayPro). What happens is that when the screen is correctly calibrated I get annoying green shadows when I'm scrol