Re: rage partitioning; engine not picking up partition

James is correct .

Please post the results from dbms_xplan. e.g like this.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.2.0 - Production

SQL> @ ?/rdbms/admin/utlxplan

Table created.

SQL> explain plan for select * from data_holder.indiv where customer_urn = 255;

Explained.

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

PLAN_TABLE_OUTPUT

---


----------------------------------------------------------------------------
| Id  | Operation                   |  Name        | Rows  | Bytes | Cost  |
----------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |              |     1 |    71 |     4 |
|   1 |  TABLE ACCESS BY INDEX ROWID| INDIV        |     1 |    71 |     4 |
|   2 |   INDEX UNIQUE SCAN         | PRIKEYINDIV  |  1000K|       |     3 |
----------------------------------------------------------------------------

Note: cpu costing is off, 'PLAN_TABLE' is old version

10 rows selected.

SQL>

and also your understanding can be led to truth by reading the
datawarehousing guide and the concepts guide on  tahiti.oracle.com.
"James Williams" <willjamu_at_mindspring.com> wrote in message
news:3e345f21.41365767_at_nntp.mindspring.com...


> >It is my understanding that Oracle should pick up the correct

> >partition even without any kind of index (local or global) and that

> >partitioning is mostly helpful when doing full table scans such as in

> >this operation.  The plan shows a full scan but no partition selection

> >and basically the operation takes the same amount of time as an

> >identical non partitioned table.  I've even enabled parallelism on the

> >table and in the session, still no luck.  Am I missing something here?

> >

>

>

> IIRC, I don't believe this to be correct. Oracle has something in 8+

> called partitoned. For it to  scan the proper partition you must have

> a partioning index  on the appropriate key.

>

> If you create an index and then analyze the table and check the

> explain plan then you should be able to get the proper partition.

> Otherwise, you can tell the query which partition to look in manually.

>