Oracle Table scan for numbers

When I use a numeric value against a column defined as varchar in which would adopt it, Oracle performs a full table scan, although there is an index of this column. Is there a reason why Oracle has in this way? I use 10.2.0.3.0

create table employees (empid varchar2 (3));

insert into employees values ('123');

create index emp_index on employees (empid).

Select * from employees where empid = '123'; -Index scan interval

Select * from employees where empid = 123; -Full Table Scan

Select * from employees where empid = to_char (123); -Index scan interval

However, this is not the case when I use a string where clause against a column defined as number.

create table managers (mgr_id number (3));

insert into values of managers (123);

create index mgr_index on managers (mgr_id);

Select * managers where mgr_id = 123; -Index scan interval

Select * managers where mgr_id = '123'; -Index scan interval

user6794035 wrote:
When I use a numeric value against a column defined as varchar in which would adopt it, Oracle performs a full table scan, although there is an index of this column. Is there a reason why Oracle has in this way? I use 10.2.0.3.0

This is due to the average implicit data type conversion Oracle does. Here is the excerpt from the documentation

Character and multivalued example when a condition compares a character value and a NUMERIC value, Oracle implicitly converts the value of character to a NUMERIC value, instead of converting the NUMBER of value to a character value.

This can be illustrated using DBMS_XPLAN:

SQL> EXPLAIN PLAN FOR SELECT * FROM EMPLOYEES WHERE EMPID = 123;

Explained.

SQL> SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);

PLAN_TABLE_OUTPUT
-----------------------------------------------------------------------------------------------------

Plan hash value: 1445457117

-------------------------------------------------------------------------------
| Id  | Operation         | Name      | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |           |     1 |     3 |     2   (0)| 00:00:01 |
|*  1 |  TABLE ACCESS FULL| EMPLOYEES |     1 |     3 |     2   (0)| 00:00:01 |
-------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(TO_NUMBER("EMPID")=123)

See the TO_NUMBER() function applied to the EMPID column in the section 'information of predicate? It's the implicit conversion is made. As a function is applied to a column and a function-based Index is not Oracle executes a FTS.

HTH!

Tags: Database

Similar Questions

3 clues on 3 different columns, but explain plan shows full table scan for select queries

I have a table - used and have index - functional ind1 (upper (f_name)), index - (emp_id) ind2 ind3 (upper (l_name) functional on 3 columns diffferent - what, emp_id, l_name respectively.) Now when I check explain plans for sub queries, they all have two shows complete table for the employee of the table scan. FYI - employee table is non-parittioned.

Can someone tell me why 3 indices are not used here?

(1) select emp_id, upper (f_name), upper (l_name) of the employee

(2) select upper (f_name), mp_id, upper (l_name) of the employee

where upper (f_name) = upper (f_name)

and emp_id = emp_id

and upper (l_name) = upper (l_name)

If I can push oracle (version 11) to use these indexes somewho - maybe using tips? Any help is appreciated.


Observations:

SQL> desc emp1;
 Name                                      Null?    Type
 ----------------------------------------- -------- -----------------
 EMPID                                      NOT NULL NUMBER
 F_NAME                                    NOT NULL VARCHAR2(3)
 L_NAME                                    NOT NULL VARCHAR2(3)
 SALARY                                    NUMBER
 JOB_ROLE                                 VARCHAR2(5)
 DEPTID                                     NUMBER

create index idx2 on emp1(empid);
create index idx1 on emp1(upper(f_name) );
create index idx3 on emp1(f_name,empid, l_name);
exec dbms_stats.gather_table_stats(user,'EMP1', cascade=>true);

8 rows selected.

SQL> explain plan for
  2  select /*+ index_join(e idx1 idx2 idx3)*/   upper(l_name),empid, upper(f_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 3449967945

-------------------------------------------------------------------------
| Id  | Operation        | Name | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      | 20000 |   175K|    14   (0)| 00:00:01 |
|   1 |  INDEX FULL SCAN | IDX3 | 20000 |   175K|    14   (0)| 00:00:01 |
-------------------------------------------------------------------------

8 rows selected.

SQL> explain plan for
  2  select    upper(f_name),empid,upper(l_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 3449967945

-------------------------------------------------------------------------
| Id  | Operation        | Name | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      | 20000 |   175K|    14   (0)| 00:00:01 |
|   1 |  INDEX FULL SCAN | IDX3 | 20000 |   175K|    14   (0)| 00:00:01 |
-------------------------------------------------------------------------

8 rows selected.

SQL> explain plan for
  2  select /*+ index_ffs(e idx3)*/   upper(l_name),empid, upper(f_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 2496145112

-----------------------------------------------------------------------------
| Id  | Operation            | Name | Rows  | Bytes | Cost (%CPU)| Time     |
-----------------------------------------------------------------------------
|   0 | SELECT STATEMENT     |      | 20000 |   175K|    14   (0)| 00:00:01 |
|   1 |  INDEX FAST FULL SCAN| IDX3 | 20000 |   175K|    14   (0)| 00:00:01 |
-----------------------------------------------------------------------------

8 rows selected.

SQL> explain plan for
  2  select /*+ index(e idx3)*/   upper(l_name),empid, upper(f_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 3449967945

-------------------------------------------------------------------------
| Id  | Operation        | Name | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      | 20000 |   175K|    14   (0)| 00:00:01 |
|   1 |  INDEX FULL SCAN | IDX3 | 20000 |   175K|    14   (0)| 00:00:01 |
-------------------------------------------------------------------------

8 rows selected.

SQL> explain plan for
  2  select    upper(f_name),empid,upper(l_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 3449967945

-------------------------------------------------------------------------
| Id  | Operation        | Name | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      | 20000 |   175K|    14   (0)| 00:00:01 |
|   1 |  INDEX FULL SCAN | IDX3 | 20000 |   175K|    14   (0)| 00:00:01 |
-------------------------------------------------------------------------

8 rows selected.

SQL> drop index idx3;

Index dropped.

SQL> explain plan for
  2     select   upper(l_name),empid, upper(f_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 3330885630

--------------------------------------------------------------------------
| Id  | Operation         | Name | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |      | 20000 |   175K|    18   (0)| 00:00:01 |
|   1 |  TABLE ACCESS FULL| EMP1 | 20000 |   175K|    18   (0)| 00:00:01 |
--------------------------------------------------------------------------

8 rows selected.

SQL> create index idx3 on emp1(f_name,empid, l_name );

Index created.

SQL>  explain plan for
  2     select   upper(l_name),empid, upper(f_name) from emp1 e;

Explained.

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
Plan hash value: 3449967945

-------------------------------------------------------------------------
| Id  | Operation        | Name | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      | 20000 |   175K|    14   (0)| 00:00:01 |
|   1 |  INDEX FULL SCAN | IDX3 | 20000 |   175K|    14   (0)| 00:00:01 |

best way to avoid the full table scan for clause "column is zero.
I have a query with is control null, and because of that it performs a total scan of table (in millions of rows in the table)

SELECT id, x,
LAG (id) OVER (PARTITION BY userid ORDER BY has had place, id) as p_id,.
FROM MyTable
WHERE X is ZERO

What is the best way for me to avoid the full table scan. I have indexes for the X column and other columns.

Thank you
Hi Vasif

NULL values are indexed if the indexed entry also includes a value non-zero.

If you create an index such as:

CREATE INDEX mytable_x_idx ON mytable (x, ' ');

ensure all null values for the column X are indexed and will therefore potentially use the index to search for null values, assuming of course the result set is small enough to justify the use of the index in your query.

I have spoken previously on my blog:

http://richardfoote.WordPress.com/2008/01/23/indexing-nulls-empty-spaces/

See you soon

Richard Foote
http://richardfoote.WordPress.com/

Extract/Scan for numbers of several lines of strings

Hi all

I want to extract (data) numbers obtained from an acquisition of series that will be shown in several online channels:

$# pressure 20

! @temperature 100

#voltage 1.2

I want to extract 20 100 and 1.2 so that I can do more than manipulation of data. Should I use the regular expression to match? I couldn't get a good regular expression to extract the numbers.

Thank you!

Insert data as XML into the Oracle Table
Hi all

I have a requirement where the data in XML format, and I need to insert into the Oracle Table. For example, I get XML data in the following format,
< results >
< row >
< BANK_ACCOUNT_ID > 10010 < / BANK_ACCOUNT_ID >
< BANK_ID > 300968 < / BANK_ID >
Vision operations < LEGAL_ENTITY > < / LEGAL_ENTITY >
< BANK_NAME > BofA < / BANK_NAME >
< BANK_ACCOUNT_NUM > 10271-17621-619 < / BANK_ACCOUNT_NUM >
< BANK_ACCOUNT_NAME > BofA-204 < / BANK_ACCOUNT_NAME >
< BRANCH_NAME > New York < / BRANCH_NAME >
USD < CURRENCY_CODE > < / CURRENCY_CODE >
< BALANCE_DATE > 2007 - 11 - 09 < / BALANCE_DATE >
< LEDGER_BALANCE > 432705900.56 < / LEDGER_BALANCE >
< / row >
< row >
< BANK_ACCOUNT_ID > 10091 < / BANK_ACCOUNT_ID >
< BANK_ID > 300984 < / BANK_ID >
Vision industries < LEGAL_ENTITY > < / LEGAL_ENTITY >
Barclay Bank < BANK_NAME > < / BANK_NAME >
< BANK_ACCOUNT_NUM > 70986798 < / BANK_ACCOUNT_NUM >
Bank Multi currency-626 < BANK_ACCOUNT_NAME > Barclays < / BANK_ACCOUNT_NAME >
Reading < BRANCH_NAME > < / BRANCH_NAME >
GBP < CURRENCY_CODE > < / CURRENCY_CODE >
< BALANCE_DATE > 2007 - 11 - 14 < / BALANCE_DATE >
< LEDGER_BALANCE > 24244085.24 < / LEDGER_BALANCE >
< / row >
< row >
< BANK_ACCOUNT_ID > 10127 < / BANK_ACCOUNT_ID >
< BANK_ID > 300968 < / BANK_ID >
< LEGAL_ENTITY > SSC U.S. 01 < / LEGAL_ENTITY >
< BANK_NAME > BofA < / BANK_NAME >
< BANK_ACCOUNT_NUM > 4898744 < / BANK_ACCOUNT_NUM >
< BANK_ACCOUNT_NAME > BofA SSC U.S. 02-7188 < / BANK_ACCOUNT_NAME >
< BRANCH_NAME > New York < / BRANCH_NAME >
USD < CURRENCY_CODE > < / CURRENCY_CODE >
< BALANCE_DATE > 2007 - 11 - 28 < / BALANCE_DATE >
< LEDGER_BALANCE > 10783815.28 < / LEDGER_BALANCE >
< / row >
< / results >

I like to write PLSQL code that will receive these data with XML tags and insert it into the Oracle Table. Is this possible with built-in XML features provided in the Oracle database?

Please Guide...

Kind regards
Priyanka
But the problem is the file XML is to have the details of the records if you carefully observed the XML file. But by using more high statement select I get output in the following format.
ORG_ID REQ_LINE PO_NUMBER EXPECTED_REC_QTY USER_NAME REQ_NUMBER
204204 1444714450 11 64446445 11 OPERATIONSOPERATIONS

The table has only one row, so you get a single row as output.
I'm surprised that you find useful examples showing how to divide the data into several lines.

(1) create the table with the following option, it will optimize the performance of storage and query for large XML documents:
```
CREATE TABLE xxios_xml_data_test(xml_data XMLTYPE)
XMLTYPE COLUMN xml_data STORE AS SECUREFILE BINARY XML
;
```
(2) interview table with:
```
SQL> select x.*
  2  from xxios_xml_data_test t
  3     , xmltable(
  4         '/Results/Row'
  5         passing t.xml_data
  6         columns ORG_ID           number       path 'ORG_ID'
  7               , REQ_NUMBER       number       path 'REQ_NUMBER'
  8               , REQ_LINE         number       path 'REQ_LINE'
  9               , PO_NUMBER        number       path 'PO_NUMBER'
 10               , EXPECTED_REC_QTY number       path 'EXPECTED_REC_QTY'
 11               , USER_NAME        varchar2(30) path 'USER_NAME'
 12       ) x
 13  ;

    ORG_ID REQ_NUMBER   REQ_LINE  PO_NUMBER EXPECTED_REC_QTY USER_NAME
---------- ---------- ---------- ---------- ---------------- ------------------------------
       204      14447          1       6444                1 OPERATIONS
       204      14450          1       6445                1 OPERATIONS
 
```

Need help for query flat_file type clobdata oracle table data.

Hi Sir,

I need help to query oracle table flat file data having given clob type.

Oracle Version:

Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
"CORE     10.2.0.1.0     Production"
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production



Source table

  CREATE TABLE order_details 
   (     QUEUE_SEQNUM NUMBER(10,0) NOT NULL ENABLE, 
     LINE_SEQNUM NUMBER(10,0) NOT NULL ENABLE, 
     CHAR_DATA CLOB, 
     OPTIMISTIC_LOCK_KEY NUMBER(20,0)
   )

COLUMN FOR CHAR_DATA FLAT_FILE

EU,6067AT,AT10,000000402004,NexiumGERDManagementProject,Z435,,ZZ29,NIS-GOLD,AT
EU,6067AT,AT10,000000402038,NIS-OEU-ARI-2007/1,Z450,,ZZ29,NIS-OEU-ARI-2007/1,AT
EU,6067AT,AT10,000000402039,SymbicortNISinCOPD,Z450,,ZZ29,NIS-REU-DUM-2007/1,AT
EU,6067AT,AT10,000000402040,D1443L00044SeroquelXRRuby,Z450,,ZZ29,D1443L00044,AT
EU,6067AT,AT10,000000402041,NIS-GEU-DUM-2008/1,Z450,,ZZ29,NIS-GEU-DUM-2008/1,AT
EU,6067AT,AT10,000000402042,SonstigeAktivitÃ¤tenLCM,Z450,,ZZ29,.,AT
EU,6067AT,AT10,000000402134,D1680L00002Saxagliptin,Z450,,ZZ29,D1680L00002,AT
EU,6067AT,AT10,000000402199,SeroquelWaveNIS,Z450,,ZZ29,NIS-NEU-DUM-2009/1,AT
EU,6067AT,AT10,000000402313,SeroquelExtra(D1443L00082),Z450,,ZZ29,D1443L00082,AT
EU,6067AT,AT10,000000402517,AtlanticD5130L00006(AZD6140),Z450,,ZZ29,D5130L00006,AT
EU,6067AT,AT10,000000554494,ArimidexSt.Gallen(13+2),Z142,,ZZ09,,AT
EU,6067AT,AT10,000000554495,ArimidexASCO(5delegates),Z142,,ZZ09,,AT
EU,6067AT,AT10,000000554496,ArimidexSanAntonio6delegates,Z142,,ZZ09,,AT
EU,6067AT,AT10,000000554497,ArimidexBreastCancerSummit(13+2),Z130,,ZZ09,,AT
EU,6067AT,AT10,000000554498,ArimidexEIH(15delegates),Z130,,ZZ09,,AT
EU,6067AT,AT10,000000554499,ArimidexNIFA(200delegates),Z135,,ZZ09,,AT
EU,6067AT,AT10,000000554500,ArimidexNIFAworkshops(8x25),Z135,,ZZ09,,AT
EU,6067AT,AT10,000000554501,ArimidexPraktischeGyn.Fortbildung,Z147,,ZZ09,,AT
EU,6067AT,AT10,000000554502,ArimidexAGO,Z147,,ZZ09,,AT
EU,6067AT,AT10,000000554503,ArimidexHÃ¤mato/OnkologieKongress,Z147,,ZZ09,,AT
EU,6067AT,AT10,000000554504,ARIMIDEXGYNÃ¤KOLOGENKONGRESS,Z147,,ZZ09,,AT
EU,6067AT,AT10,000000554505,ArimidexChirurgenkongress,Z147,,ZZ09,,AT

EXPECTED RESULTS:

AFFIRM_CODE COMPANY_CODE INTERNAL_ORDER_CODE INTERNAL_ORDER_DESC ENIGMA_ACTIVITY             SUB_ACTIVITY_CODE IN_AFF_IND ORDER_TYPE EXTERNAL_ORDER COUNTRY        
EU          6067AT       AT10                 000000402004       NEXIUMGERDMANAGEMENTPROJECT     Z435           NULL        ZZ29       NIS-GOLD        AT             
EU          6068AT       AT11                 000000402005       NEXIUMGERDMANAGEMENTPROJECT     Z435           NULL        ZZ29       NIS-GOLD        AT

Sorry, my bad. Without database at hand, I'll try 'baby steps' (borrowed from Frank) so you don't confuse it with errors that I might add (happens far too often already, but at least you won't "swallow" as forum members think is one of the main goals of this fighter - help her learn - providing not only the proverbial fish.)
Search the Forum - your problem is one of its best sellers. Watching {message identifier: = 10694602} ("split string into" was the key word used in research) you can try something as

select table_row,
       level clob_row,
       regexp_substr(char_data,'[^' || chr(13) || chr(10) || ']+',1,level) the_line
  from (select to_char(queue_seqnum)||':'||to_char(line_seqnum) table_row,
               char_data
          from order_details
       )
 connect by regexp_substr(char_data,'[^' || chr(13) || chr(10) || ']+',1,level) is not null
        and prior char_data = char_data
        and prior table_row = table_row
        and prior sys_guid() is not null

to get all the s the_lineall CLOB and after that the use of the example even to get your columns of each the_line.

Concerning

Etbin

Edited by: Etbin on 3.2.2013 09:01

.. .but I m connected to do things according to the instructions, I can't do something.

Used to happen to me too and I did as told to the but only after explaining any disadvantages, I was aware of in time. The last sentence is usually: "O.K. now be just and Don't come back with that kind of thing when it turns out that this isn't the right thing."
rp0428 post - something to remember.

Events in db of SIDS waiting for full table scan
Guys,

10.2.0.5 / node 2 RAC / RHEL-3

CanAnyone give me a sql to find all done SID full table scans in a database?

Thank you!
Hari
You hear all the sessions a FTS right now, or all sessions that have never done a FTS? For the latter, you can run something like this,
```
select sid,name,value from v$statname natural join v$sesstat
where name like 'table scans%tables%' order by sid;
```

How to set different fonts for numbers in the titles and tables of contents

Hello
I noticed some people to use a different font for the numbers in the titles and tables of contents to get an extra magic. Is it possible to automate the use of fonts in paragraph styles?
Oh and suggestions on which fonts would be a good thing for numbers?
Thank you!

Furthermore, you must doany of this fancy stuff if you use an OpenType font that made OSF glyphs (and if you are not you will need to set the font as part of your style). Just head on to the style definition and enable OSF there OpenType features section.

Simple query in Oracle Table in MS Access causes a full table scan.
I run a very simple query in MS ACCESS to an Oracle table attached as follows:

Select *.
EXPRESS_SERVICE_EVENTS-(EXPRESS is the name of the related table. SERVICE_EVENTS)
When executed > MyDate()

or

Select *.
EXPRESS_SERVICE_EVENTS-(EXPRESS is the name of the related table. SERVICE_EVENTS)
When executed > [Forms]! [MyForm]! [Date1]

We have more than 50 machines and this query works well on more than half of them, using an Oracle Index on the field "run." Exactly the same thing running on other machines results in a full table scan, so regardless of the index (the DB access even access all machines).

Strangely, if we write the query as follows:

Select *.
Of EXPRESS_SERVICE_EVENTS
When executed > # 2009-09-04 08:00 #.

It works fast everywhere!

Any help with this "phenominon" would be appreciated.

We did the things:
Check the locale settings of the ODBC driver, MS Access settings (as in tools-> Options), we have the latest XP and Office service packs and re-related all the Access Tables on the slow and fast machines independently).
All machines use the same version of the ODBC driver?

If you have access to Metalink, check the following note:
Note.257828.1 Scan of Table full Ext/Pub while seeking the DATE columns using the ODBC Oracle driver:

In a Word, try "bind timestamp date" option in the dsn configuration and do not forget to update the links in the table.

It will be useful,
Greg

Get the error loading file csv to oracle table

Hello
I'm tryitng to load the csv file into oracle db table.
Source:
CSV file have account_numbers, customer_names. all the fields, it took as channel.
Target: Oracle db
If I took all the fields as varchar, it loads very well. but I want to
Oracle table fields: digital account numbers or decimal (20.2)
customer_names as varchar2 format.
When I'm trying to load csv to oracle table, I am getting following error.
ODI-1228: fgh1 (integration) task fails on the target odi_user1 ORACLE connection.
Caused by: java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
I tried so many times. I am still getting error.
TO_NUMBER function I also used, getting same error
Please help me,
Thank you and best regards,
A.Kavya.

Hi, String, CSV file data type have values of amount a 54,356,4657.89 format. Like this. In odi, I took number (30.2) of data types for the target table. When I traced in odi, I get error like invalid number. to do this, I changed the values in csv file format. I removed commas. for example, 543564657.89. Yet once, I traced csv to oracle in odi. executd successfully. Thanks & regards, A.kavya.

Path to XML index table is full table scan

Hi all
I have a version of oracle 11.2.0.4.6 database
Try to implement partitioning on XML indexes.
Creates a table and index partitioned by time stamp as below.
Whenever I'm trying to find the path table makes a full table scan.
I have applied the fix as indicated ( Doc ID 13522189.8 ).
So the recovery is quite slow and partition pruning does not not on XML indexes.
Wondering if anyone has experienced the same problem?
CREATE TABLE INCIDENT
(
INCIDENT_PK NUMBER (14.5).
INCIDENTGROUPING_PK NUMBER (14.5).
INCIDENTTYPE_PK NUMBER (14.5).
SECURITYCLASS_PK NUMBER (14.5).
STAMP OF INCIDENT_DATE,
SYS INCIDENT_DETAIL. XMLTYPE
)
TABLESPACE DATA_TBS_INCIDENT
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE)
64K INITIALS
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
DEFAULT USER_TABLES
)
LOGGING
NOCOMPRESS
PARTITION BY RANGE (INCIDENT_DATE)
(PARTITION SEP2013_WEEK1 VALUES LESS THAN (to_timestamp (' 00:00:00.00 2013-09-08 ',' YYYY-MM-DD HH24:MI:SS.))) FF2')),
PARTITION SEP2013_WEEK2 VALUES LESS THAN (to_timestamp ('2013-09-15 00:00:00.00 ',' YYYY-MM-DD HH24:MI:SS.)) FF2')),
PARTITION SEP2013_WEEK3 VALUES LESS THAN (to_timestamp ('2013-09-22 00:00:00.00 ',' YYYY-MM-DD HH24:MI:SS.)) FF2')),
..........);
CREATE the INDEX INCIDENTxdb_idx
ON corpaudlive. INCIDENT (INCIDENT_detail) INDEXTYPE IS XDB. LOCAL XMLINDEX 10 PARALLEL
PARAMETERS (' PATH TABLE INCIDENT_PATHTABLE (TABLESPACE DATA_TBS_INCIDENT))
PIKEY INDEX INCIDENT_PATHTABLE_PIKEY_IX (TABLESPACE IDX_TBS_INCIDENT)
PATH ID INDEX INCIDENT_PATHTABLE_ID_IX (TABLESPACE IDX_TBS_INCIDENT)
INCIDENT_PATHTABLE_VALUE_IX VALUE INDEX (TABLESPACE IDX_TBS_INCIDENT)
ORDER KEY INDEX INCIDENT_PATHTABLE_KEY_IX (TABLESPACE IDX_TBS_INCIDENT)
Paths (INCLUDE (//forename //surname //postcode //dateofbirth //street //town))');
SQL > explain the plan for
2 Select INCIDENT_pk in INCIDENT where XMLEXISTS ('/ / name [text () = 'john']' by the way of INCIDENT_detail)
3 and XMLEXISTS ("/ / name [text () 'clark' =]' by the way of INCIDENT_detail")
4 and a.INCIDENT_date between TO_TIMESTAMP (January 10, 2014 ',' DD/MM/YYYY "")
5 and TO_TIMESTAMP (September 10, 2014 ',' DD/MM/YYYY ');
He explained.
Elapsed time: 00:00:02.77
SQL > select * from table (dbms_xplan.display);
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hash value of plan: 123057549
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| ID | Operation                                       | Name                           | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |    TQ | IN-OUT | PQ Distrib.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT |                                |     1.    70. 1803 (5) | 00:00:22 |       |       |        |      |            |
|   1. COORDINATOR OF PX |                                |       |       |            |          |       |       |        |      |            |
|   2.   PX SEND QC (RANDOM). : TQ10003 |     1.    70. 1803 (5) | 00:00:22 |       |       | Q1, 03 | P > S | QC (RAND) |
|   3.    SEMI NESTED LOOPS.                                |     1.    70. 1803 (5) | 00:00:22 |       |       | Q1, 03 | SVCP |            |
|   4.     NESTED LOOPS |                                |     1.    57. 1800 (5) | 00:00:22 |       |       | Q1, 03 | SVCP |            |
|   5.      VIEW                                       | VW_SQ_1                        |   239. 5975 | 1773 (5) | 00:00:22 |       |       | Q1, 03 | SVCP |            |
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   6.       UNIQUE HASH |                                |   239. 25334 |            |          |       |       | Q1, 03 | SVCP |            |
|   7.        RECEIVE PX |                                |   239. 25334 |            |          |       |       | Q1, 03 | SVCP |            |
|   8.         PX SEND HASH | : TQ10002 |   239. 25334 |            |          |       |       | Q1, 02 | P > P | HASH |
|   9.          UNIQUE HASH |                                |   239. 25334 |            |          |       |       | Q1, 02 | SVCP |            |
| * 10 |           HASH JOIN |                                |   239. 25334 | 1773 (5) | 00:00:22 |       |       | Q1, 02 | SVCP |            |
| 11.            KIND OF BUFFER.                                |       |       |            |          |       |       | Q1, 02 | ISSUE |            |
| 12.             RECEIVE PX |                                |     1.    22.     3 (0) | 00:00:01 |       |       | Q1, 02 | SVCP |            |
| 13.              PX SEND BROADCAST | : TQ10000 |     1.    22.     3 (0) | 00:00:01 |       |       |        | S > P | BROADCAST |
| 14.               TABLE ACCESS BY INDEX ROWID | X$ PT74MSS0WBH028JE0GUCLBK0LHM4 |     1.    22.     3 (0) | 00:00:01 |       |       |        |      |            |
| * 15 |                INDEX RANGE SCAN | X$ PR74MSS0WBH028JE0GUCLBK0LHM4 |     1.       |     2 (0) | 00:00:01 |       |       |        |      |            |
| * 16.            HASH JOIN |                                | 12077 |   990K | 1770 (5) | 00:00:22 |       |       | Q1, 02 | SVCP |            |
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 17.             RECEIVE PX |                                |   250K |    10 M |    39 (0) | 00:00:01 |       |       | Q1, 02 | SVCP |            |
| 18.              PX SEND BROADCAST | : TQ10001 |   250K |    10 M |    39 (0) | 00:00:01 |       |       | Q1, 01 | P > P | BROADCAST |
| 19.               SYSTEM PARTITION ALL |                                |   250K |    10 M |    39 (0) | 00:00:01 |     1.   112. Q1, 01 | ISSUE |            |
| * 20.                TABLE ACCESS BY LOCAL INDEX ROWID | INCIDENT_PATHTABLE |   250K |    10 M |    39 (0) | 00:00:01 |     1.   112. Q1, 01 | SVCP |            |
| * 21.                 INDEX RANGE SCAN | INCIDENT_PATHTABLE_VALUE_IX |   161.       |    25 (0) | 00:00:01 |     1.   112. Q1, 01 | SVCP |            |
| 22.             ITERATOR BLOCK PX |                                |   221 M | 8865M | 1671 (1) | 00:00:21 |    53.    54. Q1, 02 | ISSUE |            |
| * 23.              TABLE ACCESS FULL | INCIDENT_PATHTABLE |   221 M | 8865M | 1671 (1) | 00:00:21 |    53.    54. Q1, 02 | SVCP |            |
| * 24.      TABLE ACCESS BY ROWID USER | INCIDENT |     1.    32.     1 (0) | 00:00:01 | ROWID | ROWID | Q1, 03 | SVCP |            |
| * 25.     SEE PUSHED PREDICATE. VW_SQ_2                        |     1.    13.    20 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| 26.      NESTED LOOPS |                                |     1.   106.    20 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| 27.       NESTED LOOPS |                                |     4.   106.    20 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 28.        NESTED LOOPS |                                |     4.   256.     8 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| 29.         TABLE ACCESS BY INDEX ROWID | X$ PT74MSS0WBH028JE0GUCLBK0LHM4 |     1.    22.     3 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| * 30 |          INDEX RANGE SCAN | X$ PR74MSS0WBH028JE0GUCLBK0LHM4 |     1.       |     2 (0) | 00:00:01 |       |       | Q1, 03 | SVCP |            |
| 31.         ITERATOR SYSTEM PARTITION.                                |     4.   168.     5 (0) | 00:00:01 |    53.    54. Q1, 03 | SVCP |            |
| * 32 |          TABLE ACCESS BY LOCAL INDEX ROWID | INCIDENT_PATHTABLE |     4.   168.     5 (0) | 00:00:01 |    53.    54. Q1, 03 | SVCP |            |
| * 33 |           INDEX RANGE SCAN | INCIDENT_PATHTABLE_PIKEY_IX |     4.       |     4 (0) | 00:00:01 |    53.    54. Q1, 03 | SVCP |            |
| 34.        ITERATOR SYSTEM PARTITION.                                |     1.       |     2 (0) | 00:00:01 |   KEY |   KEY | Q1, 03 | SVCP |            |
| * 35 |         INDEX RANGE SCAN | INCIDENT_PATHTABLE_KEY_IX |     1.       |     2 (0) | 00:00:01 |   KEY |   KEY | Q1, 03 | SVCP |            |
| * 36 |       TABLE ACCESS BY LOCAL INDEX ROWID | INCIDENT_PATHTABLE |     1.    42.     3 (0) | 00:00:01 |     1.     1. Q1, 03 | SVCP |            |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Information of predicates (identified by the operation identity card):
---------------------------------------------------
10 - access("SYS_P9".") PATHID '=' ID')
Access (SYS_PATH_REVERSE ("PATH") 15 - > = HEXTORAW ('02582E') AND SYS_PATH_REVERSE ("PATH") < HEXTORAW ('02582EFF'))
16 - access("SYS_P11".") RID "IS 'SYS_P9'." GET RID OF"AND TBL$ OR$ IDX$ PART$ NUM ("CORPAUDLIVE". "THE INCIDENT", 0,7,65535, "SYS_P9" "." " "RID") = TBL$ OR$ IDX$ PART$ NUM ("CORPAUDLIVE". "INCIDENT_PATHTAB
THE', 0,7,65535, ROWID))
filter ("SYS_P9". "ORDER_KEY" < = 'SYS_P11' "." " ORDER_KEY' AND 'SYS_P11 '. "" ORDER_KEY "< SYS_ORDERKEY_MAXCHILD ("SYS_P9". "ORDER_KEY")) "
20 filter (SYS_XMLI_LOC_ISTEXT ("SYS_P11". "LOCATOR", "SYS_P11" "." " PATHID') = 1)
21 - access("SYS_P11".") The VALUE "= 'John')
23 filter (SYS_XMLI_LOC_ISNODE ("SYS_P9". "LOCATOR") = 1 AND SYS_OP_BLOOM_FILTER (: BF0000, "SYS_P9".) " PATHID'))
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
24 - filter("A".") INCIDENT_DATE' > = TIMESTAMP' 2014 - 10 - 01 00:00:00.000000000 "AND"A"". "" INCIDENT_DATE"< = TIMESTAMP' 2014 - 10 - 09 00:00:00.000000000' AND
"ITEM_2" = TBL$ OR$ IDX$ PART$ NUM ("INCIDENT", 0,7,65535, "A". ROWID))
25 filter ("ITEM_4" = TBL$ OR$ IDX$ PART$ NUM ("INCIDENT", 0,7,65535, "A".) ROWID))
30 - access (SYS_PATH_REVERSE ("PATH") > = HEXTORAW('027FF9') AND SYS_PATH_REVERSE ("PATH") < HEXTORAW ('027FF9FF'))
32 filter (SYS_XMLI_LOC_ISNODE ("SYS_P2". "LOCATOR") = 1) "
33 - access("SYS_P2".") GET RID OF"="A ". ROWID AND 'SYS_P2 '. ("' PATHID '=' ID ')
35 - access("SYS_P4".") GET RID OF"="A ". ROWID AND 'SYS_P2 '. "" ORDER_KEY "< ="SYS_P4. " "" ORDER_KEY "AND"SYS_P4 ". "" ORDER_KEY "< SYS_ORDERKEY_MAXCHILD ("SYS_P2". "ORDER_KEY")) "
filter ("SYS_P4". "RID"IS "SYS_P2"." GET RID OF"AND TBL$ OR$ IDX$ PART$ NUM("INCIDENT",0,7,65535,"SYS_P2".") "RID") = TBL$ OR$ IDX$ PART$ NUM ("INCIDENT_PATHTABL
E «(, 0,7,65535, ROWID)).
36 - filter("SYS_P4".") The VALUE '= 'clark' AND SYS_XMLI_LOC_ISTEXT ("SYS_P4".' LOCATOR', 'SYS_P4 '. (("" PATHID ') = 1).
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note
-----
-dynamic sample used for this survey (level = 6)
69 selected lines.
Elapsed time: 00:00:00.47
SQL > spool off
Thank you
CenterB

You must create a XMLIndex with two groups:

create table actionnew)

number of action_pk

action_date timestamp

action_detail xmltype

)

partition by (range (action_date)

partition values before_2015 less (timestamp ' 2015-01-01 00:00:00 ')

, partition values jan_2015 less (timestamp ' 2015-02-01 00:00:00 ')

, partition values feb_2015 less (timestamp ' 2015-03-01 00:00:00 ')

);

create index actionnew_sxi on actionnew (action_detail)

indexType is xdb.xmlindex

local

parameters (q'~)

Group my_group_1

XMLTable actionnew_xt1

"/ audit/action_details/screen_data/tables/table/row.

path of varchar2 (100) the columns "name".

, path of surname varchar2 (100) "first name".

Group my_group_2

XMLTable actionnew_xt2

"/ audit/action_details/fields.

path of varchar2 (100) the columns "name".

, path of surname varchar2 (100) "first name".

~'

);

Select x.*

to actionnew t

xmltable)

"/ audit/action_details/screen_data/tables/table/row.

in passing t.action_detail

path of varchar2 (100) the columns "name".

, path of surname varchar2 (100) "first name".

) x

where t.action_date between timestamp ' 2015-02-01 00:00:00 '

and timestamp ' 2015-03-01 00:00:00 '

and x.forename = 'anwardo. '

and x.surname = 'gram '.

;

Tuning sql insert that inserts 1 million lines makes a full table scan

Hi Experts,
I'm on Oracle 11.2.0.3 on Linux. I have a sql that inserts data into a table of History/Archives of a table main application based on the date. The application table has 3 million lines. and all the lines that are more then 6 months old must go in a table of History/Archives. This was decided recently, and we have 1 million rows that meet this criterion. This insertion in table archive takes about 3 minutes. Plan of the explain command shows a full table scan on the main Board - which is the right thing, because we are pulling 1 million rows in the main table in the history table.
My question is that, is it possible that I can do this sql go faster?
Here's the query plan (I changed the names of table etc.)
```
   INSERT INTO EMP_ARCH
   SELECT *
FROM EMP M
where HIRE_date < (sysdate - :v_num_days);
call     count       cpu    elapsed       disk      query    current        rows
------- ------  -------- ---------- ---------- ---------- ----------  ----------
Parse        2      0.00       0.00          0          0          0           0
Execute      2     96.22     165.59      92266     147180    8529323     1441230
Fetch        0      0.00       0.00          0          0          0           0
------- ------  -------- ---------- ---------- ---------- ----------  ----------
total        4     96.22     165.59      92266     147180    8529323     1441230
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: FIRST_ROWS
Parsing user id: 166
Rows     Row Source Operation
-------  ---------------------------------------------------
1441401   TABLE ACCESS FULL EMP (cr=52900 pr=52885 pw=0 time=21189581 us)
```
I heard that there is a way to use opt_param tip to increase the multiblock read County but did not work for me... I will be grateful for suggestions on this. can collections and this changing in pl/sql also make it faster?
Thank you
OrauserN

(1) create an index on hire_date

(2) tip 'additional' use in the 'select' query '

(3) run ' alter session parallel DML'; before you run the entire statement

Confusion of full Table Scan
Hello experts,

I am on 11g R2 RHEL5, I have a general question here, oracle said complete random for table scan reads are slower sequential reading, as far as my knowledge a sequential read is a monobloc read into the buffer cache, and read a straggling is a multiblock read that can occur for a full restricted index scan or a full table scan. My question is what is a shuffle? and how it is different from the sequential reading? on the technical side... Please put some light on these technical terms, so that I can work on the setting. There is also a warrant RANDOM i/o.
In a very brief way, the scan would be something like, you ask for the first time for employees starting with the name 'Aman' (wasn't there a lot with this name) to access using an index be a better choice (perhaps not a good example of a column containing names in real time. Example is just for the sake of discussion) then asking with the name of 'John '.

Aman...

Queries - full table scan
Hello

If I use the name like '% abc %' I still have full table scan. Is it possible to avoid it?

I read on the full-text index:

CTXCAT for the name fields
context of the clob fields

(1) is that correct or is at - it an easier option?

2) is this correct that these indices should be rebuild when the data changes?

Our database is 10.2.0.4, the above information is 11g docs

Kind regards

Nico

Published by: S11 on May 5, 2011 14:55
Histograms would be useless with a like '% something' value.

Function of material you can complete analysis that a Gigabyte table in 30 seconds then how a problem is a complete analysis for a partial value. How many times is this going to be done.

If the answer is high then you should probably use the Oracle text features.

HTH - Mark D Powell.

CBO: full instead of bitmap index use, why table scan?

I have a query in which it is clearly benefitial to use the bitmap index, rather oracle goes for the full table scan. Could you please shed some light on this? Because even a hint does not help, I guess that something prevents oracle (11.1.0.7.0) to use it in a sort of range index scan pass.

installation program:

create table test_distance (
x_display number,
y_display number,
x_rough number(5,2) as (trunc(x_display,2)),
y_rough number(5,2) as (trunc(y_display,2)));

insert into test_distance (x_display,y_display) 
(select dbms_random.value(-180,180), dbms_random.value(-90,90) from dual connect by level < 200000);

create bitmap index test_bm_xrough on test_distance(x_rough);
create bitmap index test_bm_yrough on test_distance(y_rough);

create or replace function  western_bbox_longitude(x binary_double, y binary_double, radius binary_double) return number
is
begin
  --simplified
 return x - 0.0001*radius;
end;
/

exec dbms_stats.gather_table_stats(user,'TEST_DISTANCE',cascade=>true,estimate_percent=>100);

several select statements:

--remember x and y values and use them in the subsequent queries.
select * from test_distance where rownum = 1;

alter session set statistics_level = all;

--no bind variable, no function call -> proper plan
select * from test_distance where x_rough = 16.14 and y_rough = -35.53;
select * from table(dbms_xplan.display_cursor(null,null,'ALLSTATS LAST'));

--with bind variable, no function call -> still proper plan
select * from test_distance where x_rough = :xin and y_rough = :yin;
select * from table(dbms_xplan.display_cursor(null,null,'ALLSTATS LAST'));

--using between, bind variable, no function call -> proper plan
select * from test_distance where x_rough between :xin-0.01 and :xin and y_rough between :yin-0.01 and :yin;
select * from table(dbms_xplan.display_cursor(null,null,'ALLSTATS LAST'));


--full table scan, why?
select td.*,
trunc(western_bbox_longitude(:xin,:yin,:radius),2)
from test_distance td 
where x_rough = trunc(
western_bbox_longitude(:xin,:yin,:radius),2);
select * from table(dbms_xplan.display_cursor(null,null,'ALLSTATS LAST'));

--forcing oracle to use the index results in bitmap index full instead of range scan, why?
select /*+ index( td test_bm_xrough) */ td.*,
trunc(western_bbox_longitude(:xin,:yin,:radius),2)
from test_distance td 
where x_rough = trunc(
western_bbox_longitude(:xin,:yin,:radius),2);
select * from table(dbms_xplan.display_cursor(null,null,'ALLSTATS LAST'));

--guessing it might be related to the selectivity of the function doesn't change the plan either
associate statistics with functions western_bbox_longitude default selectivity 0.001;

Ah sorry, I somehow read the wrong line in your initial statement where it between the function has been used.

Yes it is possible that the selectivity of the function plays a role here. More likely may be the order of execution for the undeterministic functions is then different for literals. However, you can try to work around this problem by using a few different approaches.

encapsulate the function inside a double subseelct

select /*+ index( td test_bm_xrough) */ td.*,
   (select trunc(western_bbox_longitude(:xin,:yin,:radius),2))
from test_distance td
where x_rough = (select trunc(western_bbox_longitude(:xin,:yin,:radius),2) from dual);

This should allow to cache the result of the function to a certain extent. Otherwise, the result of the function may be recalculated for each row in the test_distance table.

The same can be achieved with a WITH clause
not tested

with wboxlong as (select trunc(western_bbox_longitude(:xin,:yin,:radius),2) xrough from dual)
select /*+ index( td test_bm_xrough) */ td.*,
   x.xrough
from test_distance td
join wboxlong x on td.x_rough = x.xrough

Also note that your tip worked. Oracle uses the bitmap indexes to access the data. Index indicator indicates to the CBO to use this index if possible, but is not on the path. If you want a different plan, you can try to apply also the path combined with a suspicion as NO_INDEX_FFS (http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements006.htm#SQLRF50413).

Published by: Sven w. on January 3, 2011 18:57

Oracle Table scan for numbers

Similar Questions

Maybe you are looking for