View and verify data from table and index partitions

Asked by: lium1

mrjoltcola,

A couple of weeks ago, you have suggested the following;
1) Generate test data: For your case it is as simple as running some insert statements with keys that will go into different partitions.

2) Viewing the plan: Use autotrace. http://download.oracle.com/docs/cd/B10501_01/server.920/a96533/autotrac.htm

You said to find out whethert are working, it only takes 2 records inserted into different partitions, and tracing the query as above to know it is working.

Can you provide the exact syntax to insert 2 records into different partitions? Also, do I need to point to any particular partition when I insert the records?

Instant Access to this Solution

Plus...

30 Day FREE access, no risk, no obligation

Collaborate with the world's top tech experts

Unlimited access to our exclusive solution database

Never be left without tech help again

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

"The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.

"Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin

"Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

>> when I inserted date fields in the format of DD-MON-YYYY into my table and did the query, found that date field in the table at the right partition.
>>Does it mean Oracle doesn't care what format you use to insert because it automatically convert it into the right format?

Oracle does care. If you don't give an explicit format when inserting dates, it will use NLS_DATE_FORMAT in your session. Otherwise, it is safer to always use TO_DATE(..., ...) to format your date explicitily. As long as Oracle converts it to a date, then the partitioning will take over and distribute it according to the range.

>>My question is how I suppose to know the partition index I have created work properly according to it's partition?

This goes back to your original question. View the execution plan. See this sample.

-- same table but with a locally partitioned primary key
drop table t_part;
create table t_part
(
id integer,
col varchar2(20),
ts timestamp,
constraint pk_t_part primary key(id)
using index local
)
partition by range(id)
(
partition r1000000 values less than (1000000),
partition r2000000 values less than (2000000),
partition r3000000 values less than (3000000)
)
;

insert into t_part values(1, 'in part r1000000', sysdate);
insert into t_part values(1000000, 'in part r2000000', sysdate);
insert into t_part values(2000000, 'in part r3000000', sysdate);

exec dbms_stats.gather_schema_stats('SCOTT');

set autotrace on

select * from t_part partition(r2000000) where id = 1000000;

-- The query returns one row.

ID COL TS
---------- -------------------- ---------------------------------------------------------------------------
1000000 in part r2000000 03-NOV-09 11.21.12.000000 AM

-- And I see a plan generated that shows that it accessed the local index.


Execution Plan
----------------------------------------------------------
Plan hash value: 3386062270
 
----------------------------------------------------------------------------------------------------------------
| Id  | Operation                          | Name      | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
----------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                   |           |     1 |    31 |     1   (0)| 00:00:01 |       |       |
|   1 |  PARTITION RANGE SINGLE            |           |     1 |    31 |     1   (0)| 00:00:01 |     2 |     2 |
|   2 |   TABLE ACCESS BY LOCAL INDEX ROWID| T_PART    |     1 |    31 |     1   (0)| 00:00:01 |     2 |     2 |
|*  3 |    INDEX UNIQUE SCAN               | PK_T_PART |     1 |       |     0   (0)| 00:00:01 |     2 |     2 |
----------------------------------------------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
 
   3 - access("ID"=1000000)
 
 
Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
          2  consistent gets
          0  physical reads
          0  redo size
        662  bytes sent via SQL*Net to client
        524  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:

Select all Open in new window

Question

View and verify data from table and index partitions

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

Oracle Database

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Need individual assistance?

Our experts are ready to help.

Want to learn from the best?

Read articles from industry experts.

Working on a long term project?

Store your work and research.

What Makes Experts Exchange Unique?

Trusted by the world's most respected brands.

Faithfully serving IT professionals since 1996.

Related Solutions

Free Tech Articles

Cloud Class Webinars

Join the Community

Give a Little. Get a Lot.

Answers

3 Ways to Join

The Experts

The Experts

Testimonials

Testimonials

Testimonials

Business Clients

Business Clients

In the Press

In the Press

In the Press