Query is not using indexes
HelloI wonder if there is a way to make my query to use an index without specifying the INDEX indicator.
Thank you
Laurent
PS: I'm using 9.2.0.8
SQL> create table lsc_t1(a number primary key, b number);
Table created.
SQL> create table lsc_t2(a number primary key, b number);
Table created.
SQL> create table lsc_t3(a number primary key, b number);
Table created.
SQL> insert into lsc_t1(a,b) select rownum, dbms_random.value from dual connect by level<10000;
9999 rows created.
SQL> insert into lsc_t2(a,b) select rownum, dbms_random.value from dual connect by level<1000;
999 rows created.
SQL> insert into lsc_t3(a,b) select rownum, dbms_random.value from dual connect by level<1000;
999 rows created.
SQL> commit;
Commit complete.
SQL> begin
2 dbms_stats.gather_table_stats(user,'LSC_T1');
3 dbms_stats.gather_table_stats(user,'LSC_T2');
4 dbms_stats.gather_table_stats(user,'LSC_T3');
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> set timi on
SQL> select --+ INDEX(lsc_t1)
2 * from lsc_t1
3 where a in (select a from lsc_t2 where b<.01 union all select a from lsc_t3 where b<.01);
A B
---------- ----------
140 .138460932
161 .928661302
281 .830010122
440 .071851157
443 .355640404
516 .791276412
598 .508219846
600 .158621147
643 .748363911
747 .777346635
836 .390349029
869 .292453677
874 .914353702
881 .930301092
14 rows selected.
Elapsed: 00:00:00.03
SQL> select
2 * from lsc_t1
3 where a in (select a from lsc_t2 where b<.01 union all select a from lsc_t3 where b<.01);
A B
---------- ----------
140 .138460932
161 .928661302
281 .830010122
440 .071851157
443 .355640404
516 .791276412
598 .508219846
600 .158621147
643 .748363911
747 .777346635
836 .390349029
869 .292453677
874 .914353702
881 .930301092
14 rows selected.
Elapsed: 00:00:00.26
SQL> set timi off autot trace exp
SQL> select --+ INDEX(lsc_t1)
2 * from lsc_t1
3 where a in (select a from lsc_t2 where b<.01 union all select a from lsc_t3 where b<.01);
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=19 Card=17 Bytes=476)
1 0 NESTED LOOPS (Cost=19 Card=17 Bytes=476)
2 1 VIEW OF 'VW_NSO_1' (Cost=2 Card=17 Bytes=68)
3 2 SORT (UNIQUE)
4 3 UNION-ALL
5 4 TABLE ACCESS (FULL) OF 'LSC_T2' (Cost=2 Card=9 Bytes=216)
6 4 TABLE ACCESS (FULL) OF 'LSC_T3' (Cost=2 Card=8 Bytes=192)
7 1 TABLE ACCESS (BY INDEX ROWID) OF 'LSC_T1' (Cost=1 Card=1 Bytes=24)
8 7 INDEX (UNIQUE SCAN) OF 'SYS_C001186489' (UNIQUE)
SQL> select
2 * from lsc_t1
3 where a in (select a from lsc_t2 where b<.01 union all select a from lsc_t3 where b<.01);
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=6 Card=17 Bytes=476)
1 0 NESTED LOOPS (Cost=6 Card=17 Bytes=476)
2 1 TABLE ACCESS (FULL) OF 'LSC_T1' (Cost=6 Card=9999 Bytes=239976)
3 1 VIEW OF 'VW_NSO_1'
4 3 SORT (UNIQUE)
5 4 UNION-ALL (PARTITION)
6 5 TABLE ACCESS (BY INDEX ROWID) OF 'LSC_T2' (Cost=2 Card=1 Bytes=24)
7 6 INDEX (UNIQUE SCAN) OF 'SYS_C001186490' (UNIQUE) (Cost=1 Card=1)
8 5 TABLE ACCESS (BY INDEX ROWID) OF 'LSC_T3' (Cost=2 Card=1 Bytes=24)
9 8 INDEX (UNIQUE SCAN) OF 'SYS_C001186491' (UNIQUE) (Cost=1 Card=1)Laurent,
If check you my post carefully, you'll notice that the rewrite "is" using the filter outside the "union all" condition generates a plan that is - though not identical due to the operation "UNIQUE SORT" being outside instead of inside the definition of the view - point of view 'execution', 'equality' from my point of view. Please let me know if you think that this is not the case.
Kind regards
Randolf
Oracle related blog stuff:
http://Oracle-Randolf.blogspot.com/
SQLTools ++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676 /.
http://sourceforge.NET/projects/SQLT-pp/
Published by: Randolf Geist Sep 22, 2008 10:09
Solution of Tubby is not due to the execution of the sort after the LOOP IMBRIQUEE
Tags: Database
Similar Questions
-
Query is not using the index. (Included execution plan. TKPROF output not available)
Hi all
Version of DB: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
Here is the description of the problem:
(The statistics are up to date for all tables).
The query below does not use the index on ACCOUNTS_LIVE (ID). (Unique index)
Line 23 of the query uses accounts_live.id.SQL> explain plan for 2 select txn.account_number,to_number(txn.amount_lcy) txn_amt,to_date(booking_date,'YYYYMMDD') TXN_DATE, 3 sal.latest_sal,sal.sal_date,customer_name,employer_name, 4 decode(COMMUNICATION_TYPE_1,'MOBILE',COMMUNICATION_NO_1, 5 decode(COMMUNICATION_TYPE_2,'MOBILE',COMMUNICATION_NO_2)) mob, 6 txn.CURRENCY, CHEQUE_NUMBER,trans_dets,trans_reference,target,teller_id,acc.category,acc.inactive_marker, 7 acc.posting_restrict,cus.sector,cus.industry 8 from coreadmin.Gtxn_dtl_v1 txn, 9 (select account_number,round(to_number(nvl(amount_lcy,0)),2) latest_sal,TXN_DATE sal_date,rr 10 from 11 (select to_date(booking_date,'YYYYMMDD') TXN_DATE,batch_id,account_number,amount_lcy 12 ,row_number() over (partition by account_number 13 order by to_date(booking_date,'YYYYMMDD') desc NULLS LAST, 14 batch_id desc nulls last) rr, 15 CURRENCY, CHEQUE_NUMBER,trans_dets,trans_reference 16 from coreadmin.Gtxn_dtl_v1 17 where transaction_code in ('204','938') 18 and to_number(amount_lcy) > 0) 19 where rr = 1 20 ) sal,accounts_live acc,customers_live cus 21 where to_date(booking_date,'YYYYMMDD') between to_date('030109','DDMMRR') and to_date('020209','DDMMRR') 22 and txn.account_number = sal.account_number 23 and txn.account_number = acc.id 24 and txn.CUSTOMER_ID = cus.CUSTOMER_number 25 and target in ('30','31','32') 26 / Explained. SQL> select * from table(dbms_xplan.display); PLAN_TABLE_OUTPUT ------------------------------------------------------------------------------------------------------------------------------------------------------ Plan hash value: 920245766 ----------------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time | ----------------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 363M| 121G| | 223K (4)| 00:44:47 | |* 1 | HASH JOIN | | 363M| 121G| 6232K| 223K (4)| 00:44:47 | |* 2 | VIEW | | 34453 | 5820K| | 147K (1)| 00:29:36 | |* 3 | WINDOW SORT PUSHED RANK | | 34453 | 1480K| 4072K| 147K (1)| 00:29:36 | |* 4 | FILTER | | | | | | | | 5 | INLIST ITERATOR | | | | | | | |* 6 | TABLE ACCESS BY INDEX ROWID| GTXN_DTL_V1 | 34453 | 1480K| | 147K (1)| 00:29:31 | |* 7 | INDEX RANGE SCAN | IDX_TXN5 | 707K| | | 1815 (2)| 00:00:22 | |* 8 | HASH JOIN | | 598K| 106M| 20M| 63724 (1)| 00:12:45 | |* 9 | MAT_VIEW ACCESS FULL | CUSTOMERS_LIVE | 227K| 17M| | 2239 (4)| 00:00:27 | |* 10 | HASH JOIN | | 598K| 59M| 9504K| 57157 (1)| 00:11:26 | | 11 | MAT_VIEW ACCESS FULL | ACCOUNTS_LIVE | 249K| 6577K| | 1832 (2)| 00:00:22 | |* 12 | TABLE ACCESS BY INDEX ROWID | GTXN_DTL_V1 | 597K| 43M| | 52319 (1)| 00:10:28 | |* 13 | INDEX RANGE SCAN | IDX_TXN11_V1 | 1204K| | | 3931 (2)| 00:00:48 | ----------------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - access("TXN"."ACCOUNT_NUMBER"="ACCOUNT_NUMBER") 2 - filter("RR"=1) 3 - filter(ROW_NUMBER() OVER ( PARTITION BY "ACCOUNT_NUMBER" ORDER BY TO_DATE("BOOKING_DATE",'YYYYMMDD') DESC NULLS LAST,INTERNAL_FUNCTION("BATCH_ID") DESC NULLS LAST)<=1) 4 - filter(TO_DATE('030109','DDMMRR')<=TO_DATE('020209','DDMMRR')) 6 - filter(TO_NUMBER("AMOUNT_LCY")>0) 7 - access("TRANSACTION_CODE"='204' OR "TRANSACTION_CODE"='938') 8 - access("TXN"."CUSTOMER_ID"="CUS"."CUSTOMER_NUMBER") 9 - filter("TARGET"='30' OR "TARGET"='31' OR "TARGET"='32') 10 - access("TXN"."ACCOUNT_NUMBER"="ACC"."ID") 12 - filter("TXN"."CUSTOMER_ID" IS NOT NULL) 13 - access(TO_DATE("BOOKING_DATE",'YYYYMMDD')>=TO_DATE('030109','DDMMRR') AND TO_DATE("BOOKING_DATE",'YYYYMMDD')<=TO_DATE('020209','DDMMRR')) 38 rows selected. SQL> select index_name 2 from dba_ind_columns 3 where table_name = 'ACCOUNTS_LIVE' 4 and column_name = 'ID'; INDEX_NAME ------------------------------ IDX_ACCLIVE
11 the order ID explain plan shows that the index does not use.
Please suggest.
Thanks in advance,
JacWhat happens when you force the index by using hint and use the hash between txn and acc join?
See you soon
Sarma. -
View does not use index Mview underlying but mview uses indexes
Hello
I faced a situation where, while querying data to display based on mview does not use the index, but when we wonder of mview it uses index and produce quick results.
Here are the details:
querying from view: (completes in more than a minute even after passing hint) ================================ explain plan for select /*+ index( ITGI_CREDITOR_LEDGER_CMV ITGI_CREDITOR_LEDGER_INDX) */ * from CR_LEDGER_REP_V where vendor_id='1474911'; Plan hash value: 463951623 --------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | --------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 9056K| 5648M| 97644 (1)| 00:00:04 | |* 1 | VIEW | CR_LEDGER_REP_V | 9056K| 5648M| 97644 (1)| 00:00:04 | | 2 | COUNT | | | | | | | 3 | MAT_VIEW ACCESS FULL| ITGI_CREDITOR_LEDGER_CMV | 9056K| 2159M| 97644 (1)| 00:00:04 | --------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - filter("VENDOR_ID"=1474911) Querying from mview: (completes within a second) ============================== explain plan for select /*+ index( ITGI_CREDITOR_LEDGER_CMV ITGI_CREDITOR_LEDGER_INDX) */ * from ITGI_CREDITOR_LEDGER_CMV where vendor_id='1474911'; Plan hash value: 1726512073 -------------------------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | -------------------------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 21 | 5880 | 21 (0)| 00:00:01 | | 1 | MAT_VIEW ACCESS BY INDEX ROWID BATCHED| ITGI_CREDITOR_LEDGER_CMV | 21 | 5880 | 21 (0)| 00:00:01 | |* 2 | INDEX RANGE SCAN | ITGI_CREDITOR_LEDGER_INDX | 22 | | 3 (0)| 00:00:01 | -------------------------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("VENDOR_ID"=1474911) View DDL ======================== CREATE OR REPLACE FORCE VIEW SANJAY.CR_LEDGER_REP_V ( QRY, SR_NO, VENDOR_ID, VENDOR_TYPE, VENDOR_NUMBER, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE, GL_DATE, ACCOUNTING_DATE, PO, INVOICE_TYPE, AP_INVOICE_NO, INVOICE_DOC_CAT, AP_INVOICE_DATE, INVOICE_VOUCHER_NO, PAYMENT_VOUCHER_NO, CHQ_NO, DESCRIPTION, PAYMENT_DATE, ACC_CODE, PAYMENT_METHOD, CURR_CODE, DEBIT, CREDIT ) AS SELECT qry, ROWNUM srn, vendor_id, vendor_type_lookup_code, vendor_no, vendor_name, vendor_site_id, vendor_site_code, gl_date, accounting_date, po_distribution_id, invoice_type_lookup_code, invoice_num, doc_category_code, invoice_date, inv_voucher_num, payment_num, check_number, description, pay_accounting_date, account_code, payment_method_code, invoice_currency_code, debit, credit FROM sanjay.itgi_creditor_ledger_cmv;The plan does not change even if I do not use advice.
Although I said developer to use mview directly, but I did not understand this behavior.
DB version: 12.1
OPERATING SYSTEM: AIX 6.1
Kind regards
Gerard
Note that the query on the view plan is only to apply your filter predicates on line 1, rather than against the mview in line 3. Line 2 said you that enforcement must correspond to a kind of County before it can filter which is due to the virtual rownum in your point of view.
You need this column? In my opinion, it's meaningless. Remove the column from the view would mean that the view doesn't have to be assessed in its entirety (if not, how it will calculate rownums?) before allowing you to filter. You asked the developer to implement the work is likely to come with a different value of sr_no (if the developer is even using it?) than what he would have obtained by using the view.
The column tries to catch a unique key for the view? Are you aware that rownum values can and will change between requests to the same table as the order lines are selected is not guaranteed. If the column is actually useful (and it is correct to calculate at this level) you then could it sense it is calculated inside the mview? This means that you can only refresh the mview completely and rownum values can (and will) only change on refresh.
-
SQL not using indexes at runtime, but by using the index in "explain plan".
Hi all
I am facing a problem here that I don't get to think.
I have a SQL that makes a FULL ACCESS of TABLE into two tables and its costs are very high, but it occurs only when I run it in my program (I saw it in the session trace). If I do a "explain plan" sqlplus (SQL Navigator or PLSQL Developer) it shows that he use indexes and have a low cost. I already checked the statistics from both tables, and they are up to date.
Did someone never facing a similar problem or knows something I can do to find my problem?
Thank you all very much.
Hello
As far as I KNOW, optimizer Oracle never guarantees that an Index scan in query explain plan will be necessarily used during query execution.
ORACLE-BASE - DBMS_XPLAN: Oracle display execution Plans
Could you please read the above, run the query, as described and check the execution using DBMS_XPLAN plan. The cursor cache DISPLAY_CURSOR and not PLAN_TABLEs.
-
11g R2 optimizer is not using indexes
I have the table named OPT_TEST in my database 11g R2.
There is an index on the ename column of the table above.
11g does not use this index when I ask above table on the basis of the ename column.
SQL > select count (*) in the opt_test;
COUNT (*)
----------
851969
SQL > select count (*) in the opt_test where ename = 'KING '.
COUNT (*)
----------
1
SQL > exec dbms_stats.gather_table_stats ('SCOTT', 'OPT_TEST', method_opt = > 'for all columns size skewonly');
SQL > explain plan for select * from opt_test where ename = 'KING '.
He explained.
SQL > select parent_id, operation, options, object_name, id, io_cost from plan_table;
ID PARENT_ID OPERATION OPTIONS OBJECT_NAME IO_COST
---------- ---------- ------------------------------ ------------------------------ ------------------------------ ----------
0 SELECT STATEMENT 1365
1 0 TABLE ACCESS FULL OPT_TEST 1365
There is on one employee with the name 'KING' in the OPT_TEST table.
I have also generated stats on the table and the index but still optimizer makes complete analysis.user8916506 wrote:
SQL> select count(distinct ename) from opt_test ; COUNT(DISTINCTENAME) -------------------- 14 SQL> select ename,count(*) from opt_test group by ename; ENAME COUNT(*) ---------- ---------- ALLEN 65536 JONES 65536 FORD 65536 CLARK 65536 MILLER 65536 SMITH 65536 WARD 65536 MARTIN 65536 SCOTT 65536 TURNER 65536 ADAMS 65536 BLAKE 65536 KING 1 JAMES 65536 14 rows selected.The answer is b - I thought of:
You enabled Oracle to make a sample auto size, and he stopped on a very small sample because he thought that he had obtained a stable result. But he has never seen the line after line with KING. Therefore, when you query for KING oracle saw "not in the histogram. For versions of Oracle 10.2.0.3 beyond estimation is then "half the number of lines for the least popular value', which comes to 32 768.Concerning
Jonathan Lewis -
Optimizer not use indexes even after giving the indication
Hi all
I wonder why the Optimixzer does not use the index in the query below
Please suggest.Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod SQL> select column_expression 2 from ALL_IND_EXPRESSIONS 3 where table_name like 'GTXN_DTL_V1' 4 and index_name = 'IDX_TXN11_V1'; COLUMN_EXPRESSION ----------------------------------------- TO_DATE("BOOKING_DATE",'YYYYMMDD') SQL> select num_rows from all_tables 2 where table_name like 'GTXN_DTL_V1'; NUM_ROWS ---------- 29020867 SQL> explain plan for select * from gtxn_dtl_v1 where to_date(booking_date,'yyyymmdd') = to_date('030109','DDMMRR'); Explained. SQL> select * from table(dbms_xplan.display); PLAN_TABLE_OUTPUT ------------------------------------------------------------------------------------------- Plan hash value: 3140624094 --------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | --------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 55489 | 15M| 215K (4)| 00:43:08 | |* 1 | TABLE ACCESS FULL| GTXN_DTL_V1 | 55489 | 15M| 215K (4)| 00:43:08 | --------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - filter(TO_DATE("BOOKING_DATE",'yyyymmdd')=TO_DATE('030109','DDMMRR ')) 14 rows selected. --Giving Hint.. SQL> explain plan for select /*+ index(gtxn_dtl_v1 IDX_TXN11_V1) */ * 2 from gtxn_dtl_v1 3 where to_date(booking_date,'yyyymmdd') = to_date('030109','DDMMRR') 4 / Explained. SQL> select * from table(dbms_xplan.display); PLAN_TABLE_OUTPUT ------------------------------------------------------------------------------------------ Plan hash value: 3140624094 --------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | --------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 55489 | 15M| 215K (4)| 00:43:08 | |* 1 | TABLE ACCESS FULL| GTXN_DTL_V1 | 55489 | 15M| 215K (4)| 00:43:08 | --------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - filter(TO_DATE("BOOKING_DATE",'yyyymmdd')=TO_DATE('030109','DDMMRR ')) 14 rows selected.
Thanks in advance,
JacHello
you have created the index with uppercase letters (YYYYMMDD), but you try to run the query with small letters (YYYYMMDD), while acceptable with the name of the column it is not acceptable with a part of the function of the order of the function.Yuri
-
SQL, not not using index on a partitioned table
I partitioned table that has rows over 15 million
I have a query that selects records based on the flag = 1
There are only 2 possible values for the flag, it is 0 or 1
I tried two index and local bitmap index on this field.
The query always uses full table scan
any suggestions?Assuming that you have an index
CREATE INDEX idx_maint_chg_flag ON a_maintenance( CASE WHEN record_changed = 1 THEN 1 ELSE NULL END);your request would be
SELECT * FROM a_maintenance WHERE (CASE WHEN record_changed = 1 THEN 1 ELSE NULL END) = 1Of course, it may be easier to follow if you create a function is_record_changed
CREATE FUNCTION is_record_changed( p_flag NUMBER ) RETURN NUMBER IS BEGIN IF( p_flag = 1 ) THEN RETURN p_flag; ELSE RETURN NULL; END IF; END;create an index on this function
CREATE INDEX idx_maint_chg_flag ON a_maintenance( is_record_changed( record_changed ) );and use this function in your query
SELECT * FROM a_maintenance WHERE is_record_changed( record_changed ) = 1Justin
-
Index is not used, although suspicion.
DBVersion: 10.2.0.3
When I use a select statement like that no index on tabel 'walze w2' is used:CREATE TABLE "ESW"."DURCHLAUFZEIT_SONDER_AG" ( "AG" NUMBER(3,0) DEFAULT 0 NOT NULL ENABLE, "TAGE" NUMBER(5,0) DEFAULT 0 NOT NULL ENABLE, "ABTEILUNG" VARCHAR2(20 BYTE), Content of this table AG TAGE ABTEILUNG 910 1 EAV 133 1 TG 743 2 TM 719 2 TM 706 2 TM 979 10 TM
When I run the same sql to the delivery of the selection from tabel 'durchlaufzeit_sonder_ag' by my own index is used:select /*+ index(apl(arbeitsgang_nr))*/ /*+ index(w2 WALZE_IND1)*/ SUM (dsa.tage) tage, w2.walzen_nr walzen_nr, w2.walzen_ng walzen_ng from durchlaufzeit_sonder_ag dsa, auftrag_arbeitsplan apl, walze w2 where apl.arbeitsgang_nr in ( select dsa1.ag ag from durchlaufzeit_sonder_ag dsa1 where dsa1.abteilung = 'TM' )*and apl.auftr_nr = w2.auftr_nr and apl.auftr_jj = w2.auftr_jj and apl.auftr_pos = w2.auftr_pos and apl.auftr_los = w2.auftr_los and dsa.abteilung = 'TM' and dsa.ag = apl.arbeitsgang_nr GROUP BY w2.walzen_nr, w2.walzen_ng; -------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost | -------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 21 | 1155 | 4927 | | 1 | SORT GROUP BY | | 21 | 1155 | 4927 | |* 2 | HASH JOIN | | 21 | 1155 | 4922 | | 3 | NESTED LOOPS | | 333 | 11655 | 4682 | | 4 | NESTED LOOPS | | 16215 | 427K| 4682 | | 5 | TABLE ACCESS BY INDEX ROWID| DURCHLAUFZEIT_SONDER_AG | 4 | 40 | 2 | |* 6 | INDEX RANGE SCAN | DURCHLAUFZEIT_SONDER_AG_INDEX1 | 4 | | 1 | | 7 | TABLE ACCESS BY INDEX ROWID| AUFTRAG_ARBEITSPLAN | 4054 | 68918 | 1170 | |* 8 | INDEX RANGE SCAN | AUFTRAG_ARBEITSPLAN_IND3 | 4054 | | 7 | |* 9 | INDEX RANGE SCAN | DURCHLAUFZEIT_SONDER_AG_INDEX2 | 1 | 8 | | | 10 | *TABLE ACCESS FULL* | WALZE | 75432 | 1473K| 239 | --------------------------------------------------------------------------------------------------
I don't understand this. Why oracle do not use index (provided in the indicator) when I select the values in the durchlaufzeit_sonder_ag table, but when they provide my own values, it uses the index?select /*+ index(apl(arbeitsgang_nr))*/ /*+ index(w2 WALZE_IND1)*/ SUM (dsa.tage) tage, w2.walzen_nr walzen_nr, w2.walzen_ng walzen_ng from durchlaufzeit_sonder_ag dsa, auftrag_arbeitsplan apl, walze w2 where apl.arbeitsgang_nr in ( 743, 719, 706, 979 ) and apl.auftr_nr = w2.auftr_nr and apl.auftr_jj = w2.auftr_jj and apl.auftr_pos = w2.auftr_pos and apl.auftr_los = w2.auftr_los and dsa.abteilung = 'TM' and dsa.ag = apl.arbeitsgang_nr GROUP BY w2.walzen_nr, w2.walzen_ng; --------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost | --------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 2 | 94 | 1161 | | 1 | SORT GROUP BY | | 2 | 94 | 1161 | | 2 | TABLE ACCESS BY INDEX ROWID | WALZE | 1 | 20 | 2 | | 3 | NESTED LOOPS | | 2 | 94 | 1156 | |* 4 | HASH JOIN | | 31 | 837 | 1094 | | 5 | INLIST ITERATOR | | | | | | 6 | TABLE ACCESS BY INDEX ROWID| DURCHLAUFZEIT_SONDER_AG | 3 | 30 | 2 | |* 7 | INDEX RANGE SCAN | DURCHLAUFZEIT_SONDER_AG_INDEX2 | 3 | | 1 | | 8 | INLIST ITERATOR | | | | | | 9 | TABLE ACCESS BY INDEX ROWID| AUFTRAG_ARBEITSPLAN | 2276 | 38692 | 1091 | |* 10 | INDEX RANGE SCAN | AUFTRAG_ARBEITSPLAN_IND3 | 2276 | | 8 | |* 11 | INDEX RANGE SCAN | WALZE_IND1 | 1 | | 1 | ---------------------------------------------------------------------------------------------------As far as I know only the first comment of suspicion in a given query block is considered.
So it would be valid (unless hint_one is specified correctly)...
SELECT /*+ hint_one hint_two */ column_name FROM table_name; SELECT /*+ hint_one hint_two */ column_name FROM table_name; SELECT /*+ hint_one hint_two */ column_name FROM table_name; SELECT --+ hint_one hint_two column_name FROM table_name;But this should not (regardless of if hint_one is specified correctly)...
SELECT /*+ hint_one */ /*+ hint_two */ column_name FROM table_name;Also I do not believe your INDEX index specification is correct, a single set of brackets should be used and the alias name and index table must be separated by a space or a comma.
So it would be nice...
SELECT /*+ INDEX (table_alias index_name) */ column_name FROM table_name; SELECT /*+ INDEX (table_alias, index_name) */ column_name FROM table_name;But it would not...
SELECT /*+ INDEX (table_alias (index_name)) */ column_name FROM table_name;Also, you should be aware that an INDEX indicator is only considered provided that supports a given join order.
-
Setting the query: optimizer does not use the index function
Hello
I have a request written by a developer that I can't change.
It is here that the condition:
OÙ ( UPPER(TRIM (CODFSC)) = UPPER (TRIM ( '01923980500'))
OR UPPER(TRIM (CODUIC)) = UPPER (TRIM ( '01923980500')))
There is an index on CODFSC and on CODUIC1.
the plan is:
Plan
INSTRUCTION SELECT ALL_ROWS cost: 9 194 bytes: 3 206 502 cardinality: 15 054
ACCESS FULL ANAGRAFICA cost TABLE TABLE 1: 9 194 bytes: 3 206 502 cardinality: 15 054
So I created two new index on SUPERIOR (TRIM ()CODFSC)) and SUPERIOR (TRIM ()CODUIC)) but the plan
complete analysis of STIL.
Modifing where condition in:
OÙ ( CODFSC = UPPER (TRIM ( '01923980500'))
OR CODUIC = UPPER (TRIM ( '01923980500')))
the plan is:
SELECT STATEMENT ALL_ROWSCost: 157 bytes: 426 cardinality: 2
CONCATENATION OF 5
TABLE ACCESS BY INDEX ROWID ANAGRAFICA cost TABLE 2: cardinality of 5 bytes: 213: 1
1 INDEX RANGE SCAN INDEX ANAGRAFICA_IDX01 cost: cardinality 3: 1
TABLE ACCESS BY INDEX ROWID ANAGRAFICA cost TABLE 4: cardinality 152 bytes: 213: 1
3 INDEX SKIP SCAN INDEX ANAGRAFICA_IDX02 cost: cardinality 1: 151
Why optimizer not use my funct index?
Thank you.
Franck,
I always forget that the default value for the GOLD expansion depends on a path indexed for each branch.
2 in your use of or_predicates (2) depends on the position of complex predicate which must be expanded. If you change the order of predicate 'State = 0' to display AFTER the complex predicate, you must change the indicator of "or_predicates (1).
Outside of the current state of undocumented indicator, it also introduces the disturbing thought that, for a more complex query, a change in the transformation may result in another set of query blocks generated with a different ranking of the predicates. Yet another case to ensure that if you suggest anything suggest you (or create a SQL database).
Concerning
Jonathan Lewis
-
Query not using Full Scan Index
Hello world
I'm on 11.2.0.3.0 AIX 6.1.
There is a query such as:
Select: sys_b_0 | Count (distinct (column_name)) table;
that goes for the analysis full table. The column was values separate only 104 with not NULL values. To save memory buffer gets, I created an index on the table with the column used in the query (i.e. whose distinct values are recovered).
The problem is that even after the creation of indexes and force the flag index that it does not use the full scan of the index. The provided indication is correct in syntax and was the only clue in the query, so there is no question of conflicts with others.
Can anyone suggest me what I might be missing?
Thank you
It seems to me that if print_branch_code is defined as nullable in the table. If this is the case, the optimizer goes for a sweep of index, even if there is no real NULL values
-
query not using the index for some user
Hello
I have a query that is running in less than a second for sys, system, or schema owner. However, another user (test_user) take 30 seconds to run the same query.
I certainly dba and privileges identical to test_user as schmea_user, but the result is the same.
I checked
Select * from V$ SYS_OPTIMIZER_ENV;
Both are the same for both users.
I have check the plan to explain to both users. I noticed that for sys/system/schema_owner, the query uses an index, but not the test_user.
All have experience the issue where a user uses an index, but not the other?
Thank you for any assistance.Thank you for the display of formatting output, this output is much easier to read.
One of the first things you notice about the execution plans that is for the owner non-schema "SQL_ID, 0wcs85uywn72m, number of children 1" appears in the output of DBMS_XPLAN, while "SQL_ID 0wcs85uywn72m, child number 0" (the same SQL_ID but a different number of child) appears for the schema owner. "" Whereas the SQL_ID is the same, which indicates that the client requires exactly the same SQL statement, so it's a good start.
Then, note that in the predicate for the nonschema owner information section the following appears (sometimes with the order of the two conditions switched in position) as a condition placed on each table that is available in the schema:
filter(("SEAL_FLAG" IS NULL OR "SEAL_FLAG"'Y'))The above suggests the presence of the virtual private database (or a superset of private database virtual) generated the predicates. You should be able to confirm that this is the case by querying V$ VPD_POLICY using the SQL_ID which was displayed in the DBMS_XPLAN output:
SELECT * FROM V$VPD_POLICY WHERE SQL_ID='0wcs85uywn72m';As a test, I made a few minor adjustments to the example on this page:
http://Antognini.ch/2011/09/optimizer_secure_view_merging-and-VPD/
I changed the name of T to T12 and TESTUSER table specified for the schema names. I then created the function S of this page as follows:CREATE OR REPLACE FUNCTION s (schema IN VARCHAR2, tab IN VARCHAR2) RETURN VARCHAR2 AS BEGIN RETURN 'ID < 10'; END; /I then added a couple of lines in the T12 test table:
INSERT INTO T12 VALUES (1,1,NULL); INSERT INTO T12 VALUES (4,1,NULL); INSERT INTO T12 VALUES (10,1,NULL); INSERT INTO T12 VALUES (12,1,NULL); COMMIT;With an active 10053 trace, I executed the following SQL statement:
SELECT id, pad FROM t12 WHERE spy(id, pad) = 1The SQL_ID (in my case, found in the 10053 trace file) was 6hqw5p9d8g8wf, so I checked V$ VPD_POLICY to this SQL_ID:
SELECT * FROM V$VPD_POLICY WHERE SQL_ID='6hqw5p9d8g8wf'; ADDRESS PARADDR SQL_HASH SQL_ID CHILD_NUMBER OBJECT_OWNER OBJECT_NAME POLICY_GROUP POLICY POLICY_FUNCTION_OWNER PREDICATE ---------------- ---------------- ---------- ------------- ------------ ------------ ------------------------------ ------------------------------ ---------------------- ------------------------------ ------------------------------------------------------------------------------------ 000007FFB7701608 000007FFB7743350 1518838670 6hqw5p9d8g8wf 0 TESTUSER T12 SYS_DEFAULT T_SEC TESTUSER ID < 10As noted above, the VPD test function named S added the predicate "ID".< 10"="" to="" the="" sql="">
There are not many clues in the 10053 trace file in my test VPD generated additional predicates. Trace the following was found shortly after the beginning of the file (this is the SQL statement initially presented):
----- Current SQL Statement for this session (sql_id=6hqw5p9d8g8wf) ----- SELECT id, pad FROM t12 WHERE spy(id, pad) = 1I searched then down in the trace for final after changes query file (to be noted that this sentence could be slightly different in different versions of database Oracle). That's what I found:
Final query after transformations: ******* UNPARSED QUERY IS ******* SELECT "T12"."ID" "ID","T12"."PAD" "PAD" FROM "TESTUSER"."T12" "T12" WHERE "TESTUSER"."SPY"("T12"."ID","T12"."PAD")=1 AND "T12"."ID"<10 kkoqbc: optimizing query block SEL$F5BB74E1 (#0)Note that the final query after transformation shows how the final version of the query that has been rewritten by the query optimizer before the SQL statement has been executed and this version of the query includes AND "T12". "" IDENTITY CARD ".<10. if="" i="" was="" attempting="" to="" determine="" how="" that=""><10 predicate="" was="" added="" to="" the="" sql="" statement,="" i="" would="" start="" at="" the="" "current="" sql="" statement="" for"="" line="" in="" the="" trace="" file="" and="" search="" down="" the="" trace="" file="" for=""><10* -="" in="" this="" case,="" the="" following="" is="" what="" i="" found="" as="" the="" first="" search="" result,="" very="" close="" to="" the="" "current="" sql="" statement="" for"="" line="" in="" the="" trace="">
************************** Predicate Move-Around (PM) ************************** PM: PM bypassed: Outer query contains no views. PM: PM bypassed: Outer query contains no views. query block SEL$F5BB74E1 (#0) unchanged FPD: Considering simple filter push in query block SEL$F5BB74E1 (#0) "TESTUSER"."SPY"("T12"."ID","T12"."PAD")=1 AND "T12"."ID"<10 try to generate transitive predicate from check constraints for query block SEL$F5BB74E1 (#0) finally: "TESTUSER"."SPY"("T12"."ID","T12"."PAD")=1 AND "T12"."ID"<10As can be seen from the above (because the predicate again appeared before and after the line containing the word "Finally: '), the AND"T12 ". "" IDENTITY CARD ".<10 predicate="" was="" already="" added="" to="" the="" original="" sql="" statement="" by="" the="" time="" the="" predicate="" move-around="" section="" of="" the="" trace="" file="" was="" written,="" and="" that="" is="" the="" first="" mention="" of=""><10 in="" the="" trace="" file.="" in="" your="" case,="" you="" would="" search="" the="" 10053="" trace="" file="">
"SEAL_FLAG" IS NULLIf V$ VPD_POLICY revealed that there are virtual private database (VPD) generated predicates applied to the SQL statement, take a look at the following article in the Oracle documentation library:
http://docs.Oracle.com/CD/B28359_01/network.111/B28531/VPD.htmThis article lists the different points of view, who can be interviewed to learn more about the VPD rules which are in force in the schema. For example, with my SPV test:
SELECT * FROM ALL_POLICIES; OBJECT_OWNER OBJECT_NAME POLICY_GROUP POLICY_NAME PF_OWNER PACKAGE FUNCTION SEL INS UPD DEL IDX CHK ENA STA POLICY_TYPE LON ------------------------------ ------------------------------ ----------------------------- ------------------------------ ------------------------------ ----------------------------- ------------------------------ --- --- --- --- --- --- --- --- ------------------------ --- TESTUSER T12 SYS_DEFAULT T_SEC TESTUSER S YES YES YES YES NO NO YES NO DYNAMIC NOHe knows performance issues related to the use of VPD, some of which are Oracle Database version-dependent, and some have been fixed in recent versions. Take a look at the following articles if you have access to My Oracle Support:
MetaLink (MOS) Doc ID 728292.1 ' known performance problems when you use transparent encryption data and indexes on the encrypted columns.
MetaLink (MOS) Doc ID 967042.1 "How to investigate Query Performance regressions Caused by VPD (FGAC) predicates?"You might find working through the second of the above that the problem is caused by a bug in database Oracle.
On a side note. Execution plans you have published include the 0 value in the column starts many of the operations in the execution plan. 0 indicates that the operation never actually executed. A 0 is included in the column starts on the line that includes the FULL ACCESS of TABLE of PEOPLE_TRANSACTIONS at least to the OPC. Value 123, a full table of PEOPLE_TRANSACTIONS table scan PROPERTY_CONTAINER_ID was not actually performed.
Charles Hooper
http://hoopercharles.WordPress.com/
IT Manager/Oracle DBA
K & M-making Machine, Inc. -
Performance problem - Index is not used when a string of zero padded is queried
Hi all
I have a table T1 that has many columns. One such column C1 is a varchar2 (20). T1 has 10 million rows and there is an index I1 called C1. His stats are updated for tables and indexes. Here are the scenarios:
Is there a reason for this problem of performance? Why the optimizer goes for FTS in scenario 3?Scenario 1 select * from T1 where C1 = '0013206263' --Uses index I1 187 ms Scenario 2 select * from T1 where C1 = '8177341863' --Uses index I1 203 ms *Scenario 3* *select * from T1 where C1 = '0000000945' --Uses Fulll Table Scan --Very Slow* *45 seconds* When I force the sql to use the index through a hint, it is working fine: Scenario 4 select /*+ INDEX (t1 i1) */ * from T1 where C1 = '0013206263' --Uses index I1 123 ms Scenario 5 select /*+ INDEX (t1 i1) */ * from T1 where C1 = '8177341863' --Uses index I1 201 ms *Scenario 6* *select /*+ INDEX (t1 i1) */ * from T1 where C1 = '0000000945' --Uses index I1* *172ms*
Published by: user539954 on May 14, 2009 12:22
Published by: user539954 on May 14, 2009 12:32user539954 wrote:
one) says user_tab_histograms on the histogram on the column
-Online there are about 250 lines for this query (varies from between 0 and 254 endpoint_number)
Select * from user_tab_histograms where column_name like 'C1' and table_name like 'T1 '.It's balanced height histogram - by default in 10g if you do not deliberately block histograms you get histograms.
>
(b) If you "set autotrace traceonly explain' and run the queries a bit do you can predictions of a few lines for most of the values, but the predictions of a large number of lines when the value begins with zero, one or more zeros.
=> working on this now because there is a power outage nowNo need, your response to Justin provided examples which proved the point.
If you expect always a few lines for all values of this column then you must ensure that this histogram does not builds. To avoid histograms in general, you must specify method_opt like 'for all columns size 1' in the call to dbms_stats.gather_table_stats; and don't forget that in 10g, you get an automatic job working at 22:00 that could remember his stats because he thinks that current statistics have gone stale.Concerning
Jonathan Lewis
http://jonathanlewis.WordPress.com
http://www.jlcomp.demon.co.UK"Science is more than a body of knowledge; It's a way of thinking. "
Carl Sagan -
Partitioned index not used in the query
Hello
Oracle 10.2.0.1
Windows xp
I'm confused why oracle did not use a partitioned below index:
But when I said something different; then it accesses the indexes:SQL> set line 200; SQL> SET AUTOTRACE TRACEONLY EXPLAIN; SQL> select * from MYTABLE where PROD like 'SOAP%'; Execution Plan ---------------------------------------------------------- Plan hash value: 2899783245 ------------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop | ------------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1852 | 115K| 992 (3)| 00:00:12 | | | | 1 | PARTITION RANGE SINGLE| | 1852 | 115K| 992 (3)| 00:00:12 | 8 | 8 | |* 2 | TABLE ACCESS FULL | MYTABLE | 1852 | 115K| 992 (3)| 00:00:12 | 8 | 8 | ------------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - filter("PROD" LIKE 'SOAP%') SQL> desc MYTABLE; Name Null? Type ------------------------------------------------------------------------------------- -------- ----------- PROD_ID NOT NULL VARCHAR2(7) PROD NOT NULL VARCHAR2(30) AREA NOT NULL VARCHAR2(30) SUB_AREA NOT NULL VARCHAR2(30) SQL>
How to create prod_idx:SQL> select count(*) from MYTABLE where PROD like 'SOAP%'; Execution Plan ---------------------------------------------------------- Plan hash value: 1393798969 ---------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop | ---------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 16 | 18 (0)| 00:00:01 | | | | 1 | SORT AGGREGATE | | 1 | 16 | | | | | | 2 | PARTITION RANGE SINGLE| | 1852 | 29632 | 18 (0)| 00:00:01 | 8 | 8 | |* 3 | INDEX RANGE SCAN | PROD_IDX | 1852 | 29632 | 18 (0)| 00:00:01 | 8 | 8 | --------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 3 - access("PROD" LIKE 'SOAP%') filter("PROD" LIKE 'SOAP%') SQL>SQL> ED Wrote file afiedt.buf 1 create index prod_idx ON mytable(prod) 2 global partition by range(prod) 3 (partition prod1 values less than ('A'), 4 partition prod2 values less than ('B'), 5 partition prod3 values less than ('C'), 6 partition prod4 values less than ('D'), 7 partition prod5 values less than ('E'), 8 partition prod6 values less than ('F'), 9 partition prod7 values less than ('G'), 10 partition prod8 values less than ('H'), 11 partition prod9 values less than ('I'), 12 partition prod10 values less than ('J'), 13 partition prod11 values less than ('K'), 14 partition prod12 values less than ('L'), 15 partition prod13 values less than ('M'), 16 partition prod14 values less than ('N'), 17 partition prod15 values less than ('O'), 18 partition prod16 values less than ('P'), 19 partition prod17 values less than ('Q'), 20 partition prod18 values less than ('R'), 21 partition prod19 values less than ('S'), 22 partition prod20 values less than ('T'), 23 partition prod21 values less than ('U'), 24 partition prod22 values less than ('V'), 25 partition prod23 values less than ('W'), 26 partition prod24 values less than ('X'), 27 partition prod25 values less than ('Y'), 28 partition prod26 values less than ('Z'), 29* partition prod27 values less than (MAXVALUE)) SQL> / Index created.
Table is to have 14693792 lines.SQL> select count(*) from MYTABLE; Execution Plan ---------------------------------------------------------- Plan hash value: 3323402158 -------------------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Cost (%CPU)| Time | Pstart| Pstop | -------------------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 311 (0)| 00:00:04 | | | | 1 | SORT AGGREGATE | | 1 | | | | | | 2 | PARTITION RANGE ALL | | 14M| 311 (0)| 00:00:04 | 1 | 27 | | 3 | BITMAP CONVERSION COUNT | | 14M| 311 (0)| 00:00:04 | | | | 4 | BITMAP INDEX FAST FULL SCAN| MS_IDX_MYTABLE | | | | 1 | 27 | --------------------------------------------------------------------------------------------------------------
Why this is the case, please guide me to understand. Thank you.
Published by: user12050217 on July 29, 2010 23:37
Published by: user12050217 on July 29, 2010 23:38
-
Hi forum
Dynamically generated in this query:
SELECT TITULO_MEDIODEPAGO AS TITLE, IDA_MEDIODEPAGO AS IDA, COUNT (DISTINCT VISTA. ID1 | VISTA. ID2. VISTA. ID3) AS AMOUNT
OF MVISTA VISTA
WHERE ((COALESCE (VISTA. FECHAEXPIRACION, TO_DATE (' 01/01/9999 ',' dd/mm/yyyy ""))) > = SYSDATE) AND
((1=1) OR: p_rubro IS NULL) AND ((1=1) OR: p_subrubro IS NULL) AND
(VISTA. TITULO_PROVINCIA =: p_provincia) AND ((1=1) OR: p_ciudad IS NULL) AND
((1=1) OR: p_barrio IS NULL) AND ((1=1) OR: p_mediopago IS NULL) AND
((1=1) OR: p_nrocuotas IS NULL) AND ((1=1) OR: p_porcentaje IS NULL) AND
((1=1) OR: p_dias IS NULL) AND ((1=1) OR: p_textoBusqueda IS NULL)
TITULO_MEDIODEPAGO GROUP, IDA_MEDIODEPAGO
: p_rubro is null
: p_subrubro is null
: p_provincia = "PROV1.
: p_barrio is null
: p_mediopago is null
: p_nrocuotas is null
: p_porcentaje is null
: p_dias is null
: p_textoBusqueda is null
When I inspect the plan to explain it, I could see a full analysis on the materialized view MVISTA operation. I want to avoid this analysis complements the view with 500 k lines:
MAT_VIEW_ACCESS MVISTA Filter predicates
AND NLSSORT (VISTA. TITULO_PROVINCIA, "nls_sort = 'BINART_AI'") = NLSSORT (: P_PROVINCIA "nls_sort =" BINARY_AI"') COALESCE (VISTA. FECHAEXPIRACION, TIMESTAMP'9999-01-01 00:00:00 ') > = SYSDATE @! I add an index to the materialized view 'MVISTA' TITULO_PROVINCIA (CSA) and FECHAEXPIRACION (CSA) fields, but it is not used by the query. Why the index is not used? How to define the index serve him?
Thank you very much
One of the reasons for the index is not used because you apply the function nlssort on a single column.
You must use an index of feature based using this function instead.
In addition, I would rewrtite him coalesce to
(VISTA. FECHAEXPIRACION > = SYSDATE or VISTA. FECHAEXPIRACION is null)
-
Structured XMLIndex not used by the query
Hello
We try to use XMLIndexes structured for a query. But they are not used. A sample of similar work is as follows:
-Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit ProductionExample of XML data on the XMLTYPE column is:
<?xml version="1.0" encoding="UTF-8" standalone='yes'?> <abc:tagOne preparationTime="2012-10-17T13:01:23.000Z" schemaVersion="1.3.9.0" xsi:schemaLocation="" xmlns:def="DEF" xmlns:abc="ABC" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <def:tagTwo> <def:tagThree id="Identity1"> <def:Section domain="Domain123">10000</def:Section> </def:tagThree> <def:tagThree id="Identity2"> <def:Section domain="Domain123">20000</def:Section> </def:tagThree> <def:tagThree id="Identity3"> <def:Section domain="Domain123">30000</def:Section> </def:tagThree> <def:tagThree id="Identity4"> <def:Section domain="Domain123">40000</def:Section> </def:tagThree> </def:tagTwo> </abc:tagOne>
Query is like:select XMLAGG(XML_MESSAGE) from INT_PART_TABLE where XMLExists(' declare namespace abc="ABC"; declare namespace def="DEF"; $Message/abc:tagOne/def:tagTwo/def:tagThree[@id="Identity4"][def:Section[@domain="Domain123"] = ("50000", "40000") ]' passing xML_mESSAGE as "Message" )
We try to create indexes structured on the column of xmltype, as defined in the XML example file:CREATE INDEX INT_PART_TABLE_SXI ON INT_PART_TABLE (XML_MESSAGE) INDEXTYPE IS XDB.XMLINDEX PARAMETERS ('XMLTABLE INT_PART_content_table_01 XMLNAMESPACES (''ABC'' AS "abc", ''DEF'' AS "def"), ''/abc:tagOne/def:tagTwo'' COLUMNS xmltagTwo XMLTYPE PATH ''/abc:tagOne/def:tagTwo'' VIRTUAL XMLTABLE INT_PART_content_table_02 XMLNAMESPACES (''DEF'' AS "def"), ''/def:tagTwo'' PASSING xmltagTwo COLUMNS xmltagThree XMLTYPE PATH ''/def:tagThree'' VIRTUAL XMLTABLE INT_PART_content_table_03 XMLNAMESPACES (''DEF'' AS "def"), ''/def:tagThree'' PASSING xmltagThree COLUMNS section number PATH ''def:Section'', domain varchar2(20) PATH ''@domain'', id varchar2(20) PATH ''@id'' ')local;Table structure:
CREATE TABLE INT_PART_TABLE ( DB_ID VARCHAR2 (10 BYTE), xML_mESSAGE SYS.XMLTYPE, LOAD_TIMESTAMP TIMESTAMP (6) ) XMLTYPE xML_mESSAGE STORE AS BINARY XML (ENABLE STORAGE IN ROW CHUNK 16384 RETENTION CACHE READS NOLOGGING) ALLOW NONSCHEMA DISALLOW ANYSCHEMA PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE (BUFFER_POOL DEFAULT) PARTITION BY RANGE (LOAD_TIMESTAMP) (PARTITION P_12092012 VALUES LESS THAN (TIMESTAMP ' 2012-09-12 00:00:00') LOGGING NOCOMPRESS PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE (INITIAL 512 K NEXT 512 K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0 BUFFER_POOL DEFAULT), PARTITION MAX VALUES LESS THAN (MAXVALUE) LOGGING NOCOMPRESS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 128 K NEXT 128 K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0 BUFFER_POOL DEFAULT)) PARALLEL (DEGREE 8 INSTANCES 1);
- But the query above does not use the XMLINDEX STRUCTURE and instead turns to FTS INT_PART_TABLE. Please help here.
Is it the wrong way I created structured Index.
(I tried a few other ways where I got-> ORA-19279: XPTY0004 - dynamic XQuery type mismatch: expected - singleton sequence got several sequence element).
S ' Please NOTE that I used two "VIRTUAL" during the creation of the Index as otherwise I was getting the error:
ORA-29958: fatal error occurred in the execution of routine ODCIINDEXCREATE
ORA-30984: the XMLType column must be declared as virtualPlease suggest. Thank you.
Finally some time to watch this...
The following works for me:
Connected to:
Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production
With partitioning, OLAP, Data Mining and Real Application Testing options
SQL > create table (int_part_table)
2 db_id varchar2 (10 byte)
3, xml_message xmltype
4, load_timestamp timestamp (6)
5)
store xml_message 6 xmltype to the binary xml format
7 partition by range (load_timestamp)
() 8
9 lower values p_12092012 partition to (to_timestamp ('2012-09-12 00:00:00 ',' YYYY-MM-DD HH24:MI:SS'))))
10, partition p_max values less than (maxvalue)
11)
12 parallel (degree 8 instances 1);
Table created.
SQL > create index int_part_table_sxi on int_part_table (xml_message)
2 indextype is xdb.xmlindex
3 rooms
4 parameters (q'~)
5 XMLTABLE int_part_content_table_01
6 XMLNAMESPACES ('ABC' AS 'abc', 'DEF' AS 'def'),
7 ' / abc: Tallet / def:tagTwo / def:tagThree'
8 COLUMNS
9 article binary_double PATH 'def:Section '.
10, area varchar2 (20) PATH 'def:Section/@domain '.
11, id varchar2 (20) PATH '@id '.
12 ~');
The index is created.
SQL >
SQL >
SQL > insert into int_part_table values)
2 '1'
3, xmltype (')
4
' NS:ABC = 'ABC' xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" > ".
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19 ')
20, systimestamp
(21);
1 line of creation.
SQL > commit;
Validation complete.
SQL > exec dbms_stats.gather_table_stats (user, 'INT_PART_TABLE');
PL/SQL procedure successfully completed.
SQL >
SQL >
SQL > set autotrace traceonly explain
SQL > set lines 200
SQL > define pages 100
SQL >
SQL > select / * + no_parallel * / xml_message
2 of int_part_table
3 where (XMLExists)
4 ' declare namespace abc = "ABC"; (::)
5 declare def namespace = "DEF"; (::)
/ABC:tagOne/def:tagTwo/def:tagThree[@ID="Identity4 6 '.
7 and def:Section/@domain="Domain123.
8 and (def:Section = 40000
9 or def:Section = 50000)]"
10 passage xml_message
11 ) ;
Execution plan
----------------------------------------------------------
Hash value of plan: 3112612945
---------------------------------------------------------------------------------------------------------------------------------
| ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |
---------------------------------------------------------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1. 417. 15 (0) | 00:00:01 | | |
| 1. SEMI NESTED LOOPS. | 1. 417. 15 (0) | 00:00:01 | | |
| 2. RANGE OF PARTITION ALL THE | | 1. 367. 14 (0) | 00:00:01 | 1. 2.
| 3. TABLE ACCESS FULL | INT_PART_TABLE | 1. 367. 14 (0) | 00:00:01 | 1. 2.
| 4. ITERATOR SYSTEM PARTITION. | 1. 50. 1 (0) | 00:00:01 | KEY | KEY |
|* 5 | TABLE ACCESS BY LOCAL INDEX ROWID | INT_PART_CONTENT_TABLE_01 | 1. 50. 1 (0) | 00:00:01 | KEY | KEY |
|* 6 | INDEX RANGE SCAN | SYS78560_78563_RID_IDX | 1. | 0 (0) | 00:00:01 | KEY | KEY |
---------------------------------------------------------------------------------------------------------------------------------
Information of predicates (identified by the operation identity card):
---------------------------------------------------
5 - filter("SYS_SXI_0".") ID "="Identity4"AND ("SYS_SXI_0"". ")" SECTION "IS 4.0E + 004 D OR 'SYS_SXI_0'." SECTION "(= 5.0E + 004 D) AND"
'SYS_SXI_0 '. ("DOMAIN"="Domain123")
6 - access ("INT_PART_TABLE". ROWID = "SYS_SXI_0." ("' RID ')
filter (TBL$ OR$ IDX$ PART$ NUM ("DEV".) "INT_PART_TABLE", 0,0,0, "INT_PART_TABLE". ROWID) TBL = $ OR$ IDX$ PART$ NUM ("DEV". "INT_PAR
T_CONTENT_TABLE_01", 0,0,0,"SYS_SXI_0. " ROWID))
A few things to know:
-use BINARY_DOUBLE datatype to untyped (i.e. not based on a diagram) the numerical values of the XML index.
-J' developed the sequence iterator predicate you were using for a Boolean expression GOLD. Otherwise, the index is not used as intended.
You can also create a secondary index that satisfies the predicate #5 (see red part above):
SQL > create index int_part_content_table_01_ix1
2 on local int_part_content_table_01 (id, field, section);
The index is created.
SQL >
SQL > select / * + no_parallel * / xml_message
2 of int_part_table
3 where (XMLExists)
4 ' declare namespace abc = "ABC"; (::)
5 declare def namespace = "DEF"; (::)
/ABC:tagOne/def:tagTwo/def:tagThree[@ID="Identity4 6 '.
7 and def:Section/@domain="Domain123.
8 and (def:Section = 40000
9 or def:Section = 50000)]"
10 passage xml_message
11 ) ;
Execution plan
----------------------------------------------------------
Hash value of plan: 3704965392
--------------------------------------------------------------------------------------------------------------------------------------
| ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |
--------------------------------------------------------------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1. 417. 4 (25) | 00:00:01 | | |
| 1. NESTED LOOPS | | 1. 417. 4 (25) | 00:00:01 | | |
| 2. UNIQUE FATE | | 2. 100. 2 (0) | 00:00:01 | | |
| 3. SYSTEM PARTITION ALL | | 2. 100. 2 (0) | 00:00:01 | 1. 2.
| 4. TABLE ACCESS BY LOCAL INDEX ROWID | INT_PART_CONTENT_TABLE_01 | 2. 100. 2 (0) | 00:00:01 | 1. 2.
|* 5 | INDEX RANGE SCAN | INT_PART_CONTENT_TABLE_01_IX1 | 1. | 1 (0) | 00:00:01 | 1. 2.
|* 6 | TABLE ACCESS BY ROWID USER | INT_PART_TABLE | 1. 367. 1 (0) | 00:00:01 | ROWID | ROWID |
--------------------------------------------------------------------------------------------------------------------------------------
Information of predicates (identified by the operation identity card):
---------------------------------------------------
5 - access("SYS_SXI_0".") ID '= 'Identity4' AND 'SYS_SXI_0'." DOMAIN "=" Domain123 ")
filter ("SYS_SXI_0". "SECTION"IS 4.0E + 004 D OR 'SYS_SXI_0'." SECTION "(= 5.0E + 004 D)"
6 filter (TBL$ OR$ IDX$ PART$ NUM ("DEV".) "INT_PART_TABLE", 0,0,0, "INT_PART_TABLE". ROWID) TBL = $ OR$ IDX$ PART$ NUM ("DEV". "INT_PART_CON
TENT_TABLE_01", 0,0,0,"SYS_SXI_0. " ROWID))
Maybe you are looking for
-
I have a 2 transistor die in a single package as shown below I have 2 questions: 1. How do you Load Pull in MWO under a constant output power? I am using the CONSTPOUT in MWO but do not know if it works. I plan just to do this on a transistor die sin
-
I want to install Warcraft 3 on windows 7 ultimate 32 bit
last time I have installed before but nothing did not work properly now, after a while I tried to install again, but now, they said that "Windows NT is NOT SUPPORTED for Warcraft III" so, what should I do?
-
control multiple instrument via one rs232 port
How can I connect rs232 port unique to several temperature controller that has a different address for each. is this possible?
-
I want my pc be stopped automatically after a time to fix
On the night before going to bed, I want to run some programm like classical music / spiritual or any speech so that while listening to it I can go to sleep. In this case, after an hour or two, I can be in sleep and my pc running, so I want it turns
-
ENVY of HP DV7 - computer 7250US laptop gpu between
My DV7-7250US HP ENVY has only 4000 integrated graphics card intel I can't add another gpu. This would add a decent amount of power because intel has this 'thing' where you can map us graphic as proceesor integrated power. Cooling used to be a proble