Partitioned table tuning help

Hi,
Below query is taking huge time for returning result(28579 rows 9 mins).IN this query table audit table is partitioned .Here i'm suspecting count (*)is main problem.I'm taking count for pagination, i'm displaying each page 100 rows based on count only i have to do pg nation ..Here year is range partitioned and month is LIST partitioned .Here year,month,school_code and auidt_date only mandatory params rest of them optional.Please advice to improve the performance
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64biQuery
SELECT ia.*--,rank() over(order by year)
,COUNT(year) OVER() AS record_count
-- ROWNUM          AS row_num
FROM IBAUDIT.ibis_audit ia
WHERE YEAR = 2012
AND MONTH = 'MAY'
AND audit_date BETWEEN to_date('04/04/2012','dd-mm-yyyy') AND to_date('04/04/2013','dd-mm-yyyy')
AND school                                                     = '000008'
AND (:i_candidate                                             IS NULL
OR candidate                                                   = :i_candidate)
AND (:i_user                                                  IS NULL
OR person_code                                                 = :i_user)
AND (:i_person                                                IS NULL
OR active_person_code                                          = :i_person)
AND (:i_element                                               IS NULL
OR element                                                     = :i_element)
AND (:i_action                                                IS NULL
OR DECODE(action, 'INSERT', 'ADD', 'UPDATE', 'CHANGE', action) = UPPER(:i_action))
AND EXISTS
(SELECT 1
FROM IBIS.subject_component sc
WHERE sc.year           = 2012
AND sc.month            = 'MAY'
AND sc.paper_code       = ia.paper_code
AND (:i_subject        IS NULL
OR sc.subject           = :i_subject)
AND (:i_subject_option IS NULL
OR sc.subject_option    = :i_subject_option)
AND (:i_lvl            IS NULL
OR sc.lvl               = :i_lvl)
AND (:i_component      IS NULL
OR sc.component         = :i_component)
explan
line 1: SQLPLUS Command Skipped: set linesize 130
line 2: SQLPLUS Command Skipped: set pagesize 0
PLAN_TABLE_OUTPUT
Plan hash value: 2770926248
| Id | Operation                            | Name                          | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT                     |                               |     1 |   369 | 2601 (28)| 00:00:23 |       |       |
|   1 | WINDOW BUFFER                       |                               |     1 |   369 | 2601 (28)| 00:00:23 |       |       |
|* 2 |   TABLE ACCESS BY LOCAL INDEX ROWID | IBIS_AUDIT                    |     1 |   294 | 2601 (28)| 00:00:23 |   181 |   181 |
|   3 |    NESTED LOOPS                      |                               |     1 |   369 | 2601 (28)| 00:00:23 |       |       |
|   4 |     SORT UNIQUE                      |                               |     1 |    75 |    44   (0)| 00:00:01 |       |       |
|* 5 |      TABLE ACCESS BY INDEX ROWID     | SUBJECT_COMPONENT             |     1 |    75 |    44   (0)| 00:00:01 |       |       |
|* 6 |       INDEX RANGE SCAN               | SUBJECT_COMPONENT_ASSESS_TYPE | 1131 |       |     8   (0)| 00:00:01 |       |       |
|   7 |     PARTITION RANGE SINGLE           |                               |       |       |            |          |    37 |    37 |
|   8 |      PARTITION LIST SINGLE           |                               |       |       |            |          |   KEY |   KEY |
|   9 |       BITMAP CONVERSION TO ROWIDS    |                               |       |       |            |          |       |       |
| 10 |        BITMAP AND                    |                               |       |       |            |          |       |       |
| 11 |         BITMAP CONVERSION FROM ROWIDS|                               |       |       |            |          |       |       |
|* 12 |          INDEX RANGE SCAN            | IBIS_AUDIT_SCHOOL             | 21826 |       |    33   (4)| 00:00:01 |   181 |   181 |
| 13 |         BITMAP CONVERSION FROM ROWIDS|                               |       |       |            |          |       |       |
|* 14 |          INDEX RANGE SCAN            | IBIS_AUDIT_PAPER              | 21826 |       |    84   (4)| 00:00:01 |   181 |   181 |
Predicate Information (identified by operation id):
   2 - filter("YEAR"=2012 AND (:I_CANDIDATE IS NULL OR "CANDIDATE"=:I_CANDIDATE) AND (:I_USER IS NULL OR
              "PERSON_CODE"=:I_USER) AND (:I_PERSON IS NULL OR "ACTIVE_PERSON_CODE"=:I_PERSON) AND (:I_ELEMENT IS NULL OR
              "ELEMENT"=:I_ELEMENT) AND "AUDIT_DATE">=TO_DATE('2012-04-04 00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND (:I_ACTION IS NULL OR
              DECODE("ACTION",'INSERT','ADD','UPDATE','CHANGE',"ACTION")=UPPER(:I_ACTION)) AND "AUDIT_DATE"<=TO_DATE('2013-04-04 00:00:00',
              'yyyy-mm-dd hh24:mi:ss') AND "SC"."YEAR"="IA"."YEAR" AND "SC"."MONTH"="IA"."MONTH")
   5 - filter((:I_SUBJECT_OPTION IS NULL OR "SC"."SUBJECT_OPTION"=:I_SUBJECT_OPTION) AND (:I_SUBJECT IS NULL OR
              "SC"."SUBJECT"=:I_SUBJECT) AND (:I_COMPONENT IS NULL OR "SC"."COMPONENT"=:I_COMPONENT) AND ("SC"."LVL"=:I_LVL OR :I_LVL IS
              NULL))
   6 - access("SC"."YEAR"=2012 AND "SC"."MONTH"='MAY')
12 - access("SCHOOL"='000008')
14 - access("SC"."PAPER_CODE"="IA"."PAPER_CODE")
36 rows selected

user575115 wrote:
Hi,
Below query is taking huge time for returning result(28579 rows 9 mins).IN this query table audit table is partitioned .Here i'm suspecting count (*)is main problem.I'm taking count for pagination, i'm displaying each page 100 rows based on count only i have to do pg nation ..Here year is range partitioned and month is LIST partitioned .Here year,month,school_code and auidt_date only mandatory params rest of them optional.Please advice to improve the performance
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64biQuery
SELECT ia.*--,rank() over(order by year)
,COUNT(year) OVER() AS record_count
-- ROWNUM          AS row_num
FROM IBAUDIT.ibis_audit ia
WHERE YEAR = 2012
AND MONTH = 'MAY'
AND audit_date BETWEEN to_date('04/04/2012','dd-mm-yyyy') AND to_date('04/04/2013','dd-mm-yyyy')
AND school                                                     = '000008'
AND (:i_candidate                                             IS NULL
OR candidate                                                   = :i_candidate)
AND (:i_user                                                  IS NULL
OR person_code                                                 = :i_user)
AND (:i_person                                                IS NULL
OR active_person_code                                          = :i_person)
AND (:i_element                                               IS NULL
OR element                                                     = :i_element)
AND (:i_action                                                IS NULL
OR DECODE(action, 'INSERT', 'ADD', 'UPDATE', 'CHANGE', action) = UPPER(:i_action))
AND EXISTS
(SELECT 1
FROM IBIS.subject_component sc
WHERE sc.year           = 2012
AND sc.month            = 'MAY'
AND sc.paper_code       = ia.paper_code
AND (:i_subject        IS NULL
OR sc.subject           = :i_subject)
AND (:i_subject_option IS NULL
OR sc.subject_option    = :i_subject_option)
AND (:i_lvl            IS NULL
OR sc.lvl               = :i_lvl)
AND (:i_component      IS NULL
OR sc.component         = :i_component)
);explan
PLAN_TABLE_OUTPUT
Plan hash value: 2770926248
| Id | Operation                            | Name                          | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT                     |                               |     1 |   369 | 2601 (28)| 00:00:23 |       |       |
|   1 | WINDOW BUFFER                       |                               |     1 |   369 | 2601 (28)| 00:00:23 |       |       |
|* 2 |   TABLE ACCESS BY LOCAL INDEX ROWID | IBIS_AUDIT                    |     1 |   294 | 2601 (28)| 00:00:23 |   181 |   181 |
|   3 |    NESTED LOOPS                      |                               |     1 |   369 | 2601 (28)| 00:00:23 |       |       |
|   4 |     SORT UNIQUE                      |                               |     1 |    75 |    44   (0)| 00:00:01 |       |       |
|* 5 |      TABLE ACCESS BY INDEX ROWID     | SUBJECT_COMPONENT             |     1 |    75 |    44   (0)| 00:00:01 |       |       |
|* 6 |       INDEX RANGE SCAN               | SUBJECT_COMPONENT_ASSESS_TYPE | 1131 |       |     8   (0)| 00:00:01 |       |       |
|   7 |     PARTITION RANGE SINGLE           |                               |       |       |            |          |    37 |    37 |
|   8 |      PARTITION LIST SINGLE           |                               |       |       |            |          |   KEY |   KEY |
|   9 |       BITMAP CONVERSION TO ROWIDS    |                               |       |       |            |          |       |       |
| 10 |        BITMAP AND                    |                               |       |       |            |          |       |       |
| 11 |         BITMAP CONVERSION FROM ROWIDS|                               |       |       |            |          |       |       |
|* 12 |          INDEX RANGE SCAN            | IBIS_AUDIT_SCHOOL             | 21826 |       |    33   (4)| 00:00:01 |   181 |   181 |
| 13 |         BITMAP CONVERSION FROM ROWIDS|                               |       |       |            |          |       |       |
|* 14 |          INDEX RANGE SCAN            | IBIS_AUDIT_PAPER              | 21826 |       |    84   (4)| 00:00:01 |   181 |   181 |
Predicate Information (identified by operation id):
2 - filter("YEAR"=2012 AND (:I_CANDIDATE IS NULL OR "CANDIDATE"=:I_CANDIDATE) AND (:I_USER IS NULL OR
"PERSON_CODE"=:I_USER) AND (:I_PERSON IS NULL OR "ACTIVE_PERSON_CODE"=:I_PERSON) AND (:I_ELEMENT IS NULL OR
"ELEMENT"=:I_ELEMENT) AND "AUDIT_DATE">=TO_DATE('2012-04-04 00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND (:I_ACTION IS NULL OR
DECODE("ACTION",'INSERT','ADD','UPDATE','CHANGE',"ACTION")=UPPER(:I_ACTION)) AND "AUDIT_DATE"<=TO_DATE('2013-04-04 00:00:00',
'yyyy-mm-dd hh24:mi:ss') AND "SC"."YEAR"="IA"."YEAR" AND "SC"."MONTH"="IA"."MONTH")
5 - filter((:I_SUBJECT_OPTION IS NULL OR "SC"."SUBJECT_OPTION"=:I_SUBJECT_OPTION) AND (:I_SUBJECT IS NULL OR
"SC"."SUBJECT"=:I_SUBJECT) AND (:I_COMPONENT IS NULL OR "SC"."COMPONENT"=:I_COMPONENT) AND ("SC"."LVL"=:I_LVL OR :I_LVL IS
NULL))
6 - access("SC"."YEAR"=2012 AND "SC"."MONTH"='MAY')
12 - access("SCHOOL"='000008')
14 - access("SC"."PAPER_CODE"="IA"."PAPER_CODE")
36 rows selected
Plan operations look okay although the Nested Loops operation in step 3 looks out of place - would a hash join work better with the bitmaps? Partition elimination looks great! The series of 1 values at the top of the plan in steps 0-4 suggests something is wrong with either the statistics or the optimizer's processing of the query; you are really getting a lot more rows than the optimizer is estimating.
You reported the query runs faster without the COUNT() which you need. How much faster?
AND and OR conditions mixed together in WHERE clause can add overhead. Would using NVL() instead of the AND/OR combinations affect performance (beware index supression)?
The estimated statistics disappear reading the plan from bottom to the top in step 11. Are all of the objects in the plan - tables and indexes both - analyzed with current values? In particular the # of rows in step 2 for IBIS_AUDIT looks odd - 1 row (possibly correct)? Similarly the estimated values ifor the index lookup in step 5 look low.
If necessary a materialized view with automatic query rewrite (provided that this works) is an option but tuning the SQL is a better idea.

Similar Messages

Ubuntu wrecked partition table. Help to fix?

(Macbook Pro 2013 15" Crystalwell 4 Core, 500GB SSD 16GB RAM)
I should have known that installing Ubuntu next to Bootcamp was a bad idea.
So here's what's up... Before this whole debacle began I had two separate partitions on my SSD. The primary partition was for Mavericks with 300GB. The second partition was to a Bootcamped Windows 7 with 150 GB of space. I left 50GB free between the two, which still left me at
disk0s1 for EFI, ~200 MB
disk0s2 for Macintosh HD, 300 GB
disk0s3 for Recovery HD 650 MB
disk0s4 for Bootcamp 148 GB
Here's where my problem began. Genius me decided to attempt to install Ubuntu via live USB onto the 50GB space in between. I have reFIT installed so this wasn't a problem. After loading into Ubuntu and realizing that it wouldn't load into the 50GB space, I rebooted and installed alongside Windows (through the Ubuntu live usb) following the install GUI Prompt.
The installation failed after it got hung on a CRON command and drained the battery from my unplugged computer sitting next to me in my bed (I fell asleep waiting for it to finish, even though it was at 100% battery when it started the installation). When I woke up my computer was dead, so I plugged it in. I started reFIT and booted into Windows after seeing that Ubuntu wasn't there. I was given the "Choose OS" prompt from Windows and Ubuntu wouldn't load, so I said screw it and went back to Mavericks. When I opened my Disk utility partitions table to see where it might have gone wrong....
Great Odin's Raven.
I now had ext4 partitions sitting above my bootcamp partition and linux-swap partitions below it. Absolutely no free space. I switched back to Windows, avoiding the failed Ubuntu OS, and uninstalled wubi from Windows (the universal uninstall for ubuntu, I used the Windows "uninstall application" application from Control Center), hopefully deleting the mess it had made of my drive table.
It didn't.
Since I couldn't delete the partitions back to free space around my bootcamp volume using Disk utility (insufficient hfs+ permissions or something like that), I decided to take a more agressive option. I installed partedMagic onto a live USB and once again rebooted my computer into the live USB. I went in and using gParted removed the partitions in front of the bootcamp volume and behind it reducing them to empty space. Good! Hoping for the best I went back to reFIT and booted into Windows...
"No bootable device -- insert boot disk and press any key"
Well crap.
After some more research into why this wasn't working, I was sure that somehow my EFI wasn't loading the right area of my hard drive. Then I think I found out what happened. I ran diskutil list from terminal and saw this..
IceMan-HomeBase:~ Tim$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            300.2 GB   disk0s2
   3:                  Apple_HFS Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                148.0 GB   disk0s6
disk0s6. There's the problem. Mac doesn't like anything beyond disk0s4, which is where Bootcamp was originally and where it should be now, at disk0s4.
If it were merely an issue of copying the bootcamp volume and repartitioning the hard drive, that wouldn't be a problem, but even WinClone doesn't like this volume. When I tried to do a copy, it threw an error saying "Invalid partition ID of 6"
Here is my question.
Is there a way to change the IDENTIFIER back to disk0s4 from disk0s6 and save my Windows 7 partition, is there some other way to save my files to a backup and clean install, or is he dead, Jim?
Sorry if this was a little long-winded, but I figured too much information would be better than not enough.
Thank you in advance for anyone brave enough to read this.
TL;DR
Partition table went bogus because of a bad Ubuntu OS install. Windows can't find a bootable device. Disk0s4 is now disk0s6. Possible way to change this?

Problem solved, I used iPartition to resize the partition back to its original size after which I could copy all data off.

Regarding partition table..pls help

I am creating a table
as
CREATE TABLE T3
PARTITION BY RANGE(CREATED)
(PARTITION T1 VALUES LESS THAN (TO_DATE('01-APR-2006','DD-MON-YYYY')),
PARTITION T2 VALUES LESS THAN (TO_DATE('01-JUN-2006','DD-MON-YYYY')))
AS SELECT * FROM T1
am getting error :
ORA-14400: inserted partition key does not map to any partition
since am new to the partitioning concepts, pls help.
Thanks.

Oups :-)
I referenced the source table name (T1) instead on the newly partitionned table (T3) fromyour original post, sory :)
The select should read:
SELECT *
FROM T3 PARTITION (T3);
Thinking of that, you should give another name to the partition in order to avoid confusion!
Yoann.

Need help with importing data in partition table

Hi,
DB:8.1.7
OS: win 2003 server
I have a table which is 4.5GB in size. I created a new partition table,with local indexes. I exported the original table with all indexes,triggers and procedures.
After creating the empty partitioned table,i imported the dump file. The data isn't loaded. My questions are:
1) Will the indexes be overwritten?
2) Will the data go automatically in allocated partitions?
3) Do i need to export only table data ignoring indexes,triggers etc?
Best Regards,

ateeqrahman wrote:
1) Will the indexes be overwritten?Not if they already exist with the same name, or with the same logical definition (ie. same columns are already indexed)
2) Will the data go automatically in allocated partitions?Yes
3) Do i need to export only table data ignoring indexes,triggers etc?Do you need the triggers? do you need indexes that you haven't created manually? What about grants?

Tuning SQL | Partition Table | MJC

All good hearted people -
Problem :- This SQL runs forever and returns nothing when STATS are stale. If I collect the table level stats (dbms_stats) on these partitioned table it runs again as normal (< 2 minutes).
I see Merge Join cartesian in the explain plan when it runs bad. After the stats done, this MJC disappeared from the plan and things back to normal.
Also, If convert one of those partition into a regular table(amms partition 2010-03-16 ) and join to the other partition table's (cust ) partition this works fine.
Note : After every load we run partition level stats on these tables (not table level stats).
My question is why am I getting MJC? How to solve this issue?
<code>
select aln.acct_no as acct_no, aln.as_of_dt, max(acm.appno) as appno, count( * )
from amr.amms aln, acr.cust acm <================= both tables are range partitioned by date
where acm.acctno = aln.acct_no
and acm.acctno > 0
and acm.as_of_dt = date '2010-03-16' <============ partition key on cust table < 2M rows
and aln.as_of_dt = date '2010-03-12' < ============= partition key on amms table < 2M rows
group by aln.acct_no, aln.as_of_dt
having count( * ) = 1
</code>
Env: Oracle 10g | 10.2.0.4 | ASM | 2 node RAC | Linux x86 | Archivelog | Partition | Optimizer Choose |

and acm.as_of_dt = date '2010-03-16'
and aln.as_of_dt = date '2010-03-12' not valid syntax!

Query regarding Partition table Explain plan

Hello,
We are amidst a tuning activity, wherein a large table has been partitioned for better administration. During testing, I was analyzing the explain plans for long running sql's and found a piece that I was unable to understand. The PSTART and PSTOP columns show ROWID as its value, which in normal partition pruning scenario be the Partition number or the KEY. I tried to look around for this issue but did not get enough information. Can anybody help me of what it means? Also, if there is a good explanation of the same, it will be extremely helpful.
The snippet from explain plan looks like:
| Id | Operation                                | Name                          | Rows | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Pstop |
7 |        TABLE ACCESS BY GLOBAL INDEX ROWID| XXXXXXXXXXXXXXXXXXXX             | 43874 | 9083K|       | 1386   (1)| 00:00:17 | ROWID | ROWID |
On another similar query it looks like:
| Id | Operation                             | Name                         | Rows | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Pstop |
|   6 |     TABLE ACCESS BY GLOBAL INDEX ROWID| XXXXXXXXXXXXXX               | 22455 | 4648K|       |   456   (1)| 00:00:06 |     9 |     9 |
I have another query with regards to the Partition tables. Does it, require/benefit if, the Indexes to be in partitioned mode? I tried to read about it but did not get a conclusive evidence. I am trying to test it and post here the outcome, but if anybody has experience of working with it, it would be great to have some advice.
Oracle Version:- 10.2.0.4
Regards,
Purvesh.

Hi Purvesh.
Great explanation and example on this this topic...
Ask Tom &quot;explain plan on range-partitioned table&quot;
Hope this help.

Slow inserts into partitioned table

I am having trouble inserting into a simple partitioned table after an upgrade to 11.2.0.3. I'm seeing insert speeds of subsecond up to 10 and 12 seconds. We have pre created the partitions for this table (and all children via reference partitioning). We have gathered dictionary and static object stats as well as statistics on all partitions.
Queries against the dictionary are incredibly slow as well and showing very high io.
Any help would be greatly appreciated. Thank you for your time.
Windows 2008 advanced server
Oracle Enterprise edition 11.2.0.3
Edited by: user593549 on Mar 26, 2012 11:16 AM

user593549 wrote:
I am having trouble inserting into a simple partitioned table after an upgrade to 11.2.0.3. I'm seeing insert speeds of subsecond up to 10 and 12 seconds. We have pre created the partitions for this table (and all children via reference partitioning). We have gathered dictionary and static object stats as well as statistics on all partitions.
Queries against the dictionary are incredibly slow as well and showing very high io.
Any help would be greatly appreciated. Thank you for your time.
Windows 2008 advanced server
Oracle Enterprise edition 11.2.0.3
Edited by: user593549 on Mar 26, 2012 11:16 AMThread: HOW TO: Post a SQL statement tuning request - template posting
HOW TO: Post a SQL statement tuning request - template posting

Local index vs global index in partitioned tables

Hi,
I want to know the differences between a global and a local index.
I'm working with partitioned tables about 10 millons rows and 40 partitions.
I know that when your table is partitioned and your index non-partitioned is possible that
some database operations make your index unusable and you have tu rebuid it, for example
when yo truncate a partition your global index results unusable, is there any other operation
that make the global index unusable??
I think that the advantage of a global index is that takes less space than a local and is easier to rebuild,
and the advantage of a local index is that is more effective resolving a query isn't it???
Any advice and help about local vs global index in partitioned tables will be greatly apreciatted.
Thanks in advance

here is the documentation -> http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/partconc.htm#sthref2570
In general, you should use global indexes for OLTP applications and local indexes for data warehousing or DSS applications. Also, whenever possible, you should try to use local indexes because they are easier to manage. When deciding what kind of partitioned index to use, you should consider the following guidelines in order:
1. If the table partitioning column is a subset of the index keys, use a local index. If this is the case, you are finished. If this is not the case, continue to guideline 2.
2. If the index is unique, use a global index. If this is the case, you are finished. If this is not the case, continue to guideline 3.
3. If your priority is manageability, use a local index. If this is the case, you are finished. If this is not the case, continue to guideline 4.
4. If the application is an OLTP one and users need quick response times, use a global index. If the application is a DSS one and users are more interested in throughput, use a local index.
Kind regards,
Tonguç

Insert statement does not insert all records from a partitioned table

Hi
I need to insert records in to a table from a partitioned table.I set up a job and to my surprise i found that the insert statement is not inserting all the records on the partitioned table.
for example when i am using select statement on to a partitioned table
it gives me 400 records but when i insert it gives me only 100 records.
can anyone help in this matter.

INSERT INTO TABLENAME(COLUMNS)
(SELECT *
FROM SCHEMA1.TABLENAME1
JOIN SCHEMA2.TABLENAME2a
ON CONDITION
JOIN SCHEMA2.TABLENAME2 b
ON CONDITION AND CONDITION
WHERE CONDITION
AND CONDITION
AND CONDITION
AND CONDITION
AND (CONDITION
HAVING SUM(COLUMN) > 0
GROUP BY COLUMNS

How to delete the data from partition table

Hi all,
Am very new to partition concepts in oracle..
here my question is how to delete the data from partition table.
is the below query will work ?
delete from table1 partition (P_2008_1212)
we have define range partition ...
or help me how to delete the data from partition table.
Thanks
Sree

874823 wrote:
delete from table1 partition (P_2008_1212)This approach is wrong - as Andre pointed, this is not how partition tables should be used.
Oracle supports different structures for data and indexes. A table can be a hash table or index organised table. It can have B+tree index. It can have bitmap indexes. It can be partitioned. Etc.
How the table implements its structure is a physical design consideration.
Application code should only deal with the logical data structure. How that data structure is physically implemented has no bearing on application. Does your application need to know what the indexes are and the names of the indexes,in order to use a table? Obviously not. So why then does your application need to know that the table is partitioned?
When your application code starts referring directly to physical partitions, it needs to know HOW the table is partitioned. It needs to know WHAT partitions to use. It needs to know the names of the partitions. Etc.
And why? All this means is increased complexity in application code as this code now needs to know and understand the physical data structure. This app code is now more complex, has more moving parts, will have more bugs, and will be more complex to maintain.
Oracle can take an app SQL and it can determine (based on the predicates of the SQL), which partitions to use and not use for executing that SQL. All done totally transparently. The app does not need to know that the table is even partitioned.
This is a crucial concept to understand and get right.

How can I create my own tag name while creating a partition table.

I have X4500 running Solaris 10. I have formatted a disk and created partition table as given below.
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]
/dev/dsk/c0t0d0s0 is part of active ZFS pool zpool1. Please see zpool(1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> partition
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> print
Current partition table (original):
Total disk sectors available: 1953508749 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 usr wm 34 4.00GB 8388641
1 usr wm 8388642 2.00GB 12582945
2 usr wm 12582946 200.00GB 432013345
3 usr wm 432013346 175.00GB 799014945
4 usr wm 1166180386 375.43GB 1953508748
5 usr wm 799014946 175.00GB 1166016545
6 usr wm 1166016546 80.00MB 1166180385
8 reserved wm 1953508749 8.00MB 1953525132
partition>
I am unable to specify my own tag name. How can I change the tag name to one of my interest.
I need to create 3 partitions as told below
partitions:
/earth
/mars
/work
/earth and /work should be roughly equal in size, /mars should be twice the size of the others, if that is possible. If not 3 partitions of equal size will do.
Please, help me .
Thank you.

Exactly 1TB? Slightly under/slightly over?
Traditional Solaris disk labels are in VTOC format, but this format cannot describe disks larger than 1TB. So EFI labels must be used on disks larger than 1TB. Setup is slightly different.
Are these physical disks or LUNs from a SAN array? If they are array LUNS, it is often the case that they don't have a Sun label of any type. So...
#1 Apply a Solaris label
If the LUNS don't have a label (when selected in 'format', it gives a warning that no label is present and offers to apply a label immediately). When run non-interactively, format assumes "yes" for any questions. So all you'd have to do is select every disk to have it apply labels to any unlabled disk. Run 'format' once and find the highest number (maybe it's 50 for you). Create a text file that looks like this:
disk 1
disk 2
disk 3
disk 50Then feed that to format like this:
# format -f /tmp/disklist or whatever you've named the file.
#2 Apply the partition layout to all disks you want.
You asked if you should do the same procedure, but I don't see that you've actually done anything above other than print out the existing layout. Take one of your 48 drives and partition it the way you want manually (set the slices to the sizes that you want). Then you can copy the layout of that disk to others. You only want to do this between disks/LUNs of the same size. As an example, if you've explicitly partitioned c1t0d0 and you want to apply this to c1t1d0, do this:
# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2Repeat for all of your other disks.
Darren

Importing partitioned table data into non-partitioned table

Hi Friends,
SOURCE SERVER
OS:Linux
Database Version:10.2.0.2.0
i have exported one partition of my partitioned table like below..
expdp system/manager DIRECTORY=DIR4 DUMPFILE=mapping.dmp LOGFILE=mapping_exp.log TABLES=MAPPING.MAPPING:DATASET_NAPTARGET SERVER
OS:Linux
Database Version:10.2.0.4.0
Now when i am importing into another server i am getting below error
Import: Release 10.2.0.4.0 - 64bit Production on Tuesday, 17 January, 2012 11:22:32
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "MAPPING"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "MAPPING"."SYS_IMPORT_FULL_01": MAPPING/******** DIRECTORY=DIR3 DUMPFILE=mapping.dmp LOGFILE=mapping_imp.log TABLE_EXISTS_ACTION=APPEND
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'MAPPING_ABC' does not exist
Failing sql is:
CREATE TABLE "MAPPING"."MAPPING" ("SAP_ID" NUMBER(38,0) NOT NULL ENABLE, "TG_ID" NUMBER(38,0) NOT NULL ENABLE, "TT_ID" NUMBER(38,0) NOT NULL ENABLE, "PARENT_CT_ID" NUMBER(38,0), "MAPPINGTIME" TIMESTAMP (6) WITH TIME ZONE NOT NULL ENABLE, "CLASS" NUMBER(38,0) NOT NULL ENABLE, "TYPE" NUMBER(38,0) NOT NULL ENABLE, "ID" NUMBER(38,0) NOT NULL ENABLE, "UREID"
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"MAPPING"."IDX_TG_ID" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."PK_MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."IDX_UREID" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."IDX_V2" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."IDX_PARENT_CT" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"MAPPING"."CKC_SMAPPING_MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type CONSTRAINT:"MAPPING"."PK_MAPPING_ITM" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_TG_ID" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."PK_MAPPING" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_UREID" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_V2" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_PARENT_CT" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"MAPPING"."FK_MAPPING_MAPPING" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"MAPPING"."FK_MAPPING_CT" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"MAPPING"."FK_TG" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"MAPPING"."FK_TT" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"MAPPING"."X_PART" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."X_TIME_T" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."X_DAY" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
ORA-39112: Dependent object type INDEX:"MAPPING"."X_BTMP" skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_TG_ID" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_V2_T" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."PK_MAPPING" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_PARENT_CT" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"MAPPING"."IDX_UREID" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"MAPPING"."MAPPING" creation failed
Job "MAPPING"."SYS_IMPORT_FULL_01" completed with 52 error(s) at 11:22:39Please help..!!
Regards
Umesh Gupta

yes, i have tried that option as well.
but when i write one tablespace name in REMAP_TABLESPACE clause, it gives error for second one.. n if i include 1st and 2nd tablespace it will give error for 3rd one..
one option, what i know write all tablespace name in REMAP_TABLESPACE, but that too lengthy process..is there any other way possible????
Regards
UmeshAFAIK the option you have is what i recommend you ... through it is lengthy :-(
Wait for some EXPERT and GURU's review on this issue .........
Good luck ....
--neeraj

Can I use gpt to recreate/unerase a partition table? (Rebuild the GPT/GUID partition table?) I don't want to do FILE recovery.

(Yes, I've googled a bunch and read threads like this one already.)
Can I use gpt or some other app to recreate/unerase a partition table? That is, how can I rebuild a disk's GPT/GUID partition table?) I don't want to do FILE recovery.
What happened: Instead of erasing a single partition off a disk with many partitions, the entire partition table was erased (using Disk Utility, w/o deleting the underlying files). Somehow the "Erasing a disk deletes all data on all its partitions." warning message was missed.
I have a copy of the output of df, with the number of blocks in each partition, from just prior to the erasure, so I should be able to recreate the GPT/GUID partition table. Editing the GPT with a hex editor is not feasible. Simply recreating the partitions with Disk Utility will overwrite the key filesystem tables on each partition, and I don't want to do that, plus Disk Utility doesn't allow me to specify exact partition sizes anyway.
Surely there's an app for rebuilding the partition table (other than emacs' hexl-mode!) for recreating/unerasing a partition table when the partition sizes and orders are known? I've looked at the advertising for a bunch of recovery software and none of them clearly indicate that they will do what I want.
I guess I can try using gpt on a copy of the reformatted drive I've made with dd, and see what happens. But perhaps someone knows of a tool that should do what I need, or knows if gpt is that tool or not.
There are answers and tools that will do FILE recovery - search for files and recover the ones that aren't fragmented or deleted. As far as I can find, they just look for files on the disk, and don't pay much, if any attention to the filesystem info or directory heirarchy, which in this case is valuable. Of course I could send it in to DriveSavers, or the like. But none of that seems necessary, and the scavenging file recovery apps won't do the job well,
E.g. some are mentioned here:
I don't want to do FILE recovery.
Thanks for any help.
The links in this post are to pages describing the underlined term, e.g. the man pages for df and gpt.
dd output includes:
Filesystem
512-blocks
Used Available Capacity Mounted on

Aperture has the ability to work with files in their existing location. They are called "referenced masters." When you import images, you should select the "In their current location" in the "Store Files:" drop down box. Have a read of the documentation for full specifics. Unsure how you can resolve your duplication; might be some work but next time have a read of the manual first
Information for versions is stored in the Aperture database (library file). The masters can be inside the library file itself, or they can be somewhere else.

Error in creating partition table in oracle spatial by ankur

Hi,
Am working on Oracle 10.2.0.3
Am not able to create partition table in Oracle
i have all the required columns in node and edge table ......the moment i try to create partition table using exec sdo_router_partition.partion_router i get the following error:
ERROR at line 1:
ORA-00947: not enough values
ORA-06512: at "MDSYS.SDO_ROUTER_PARTITION", line 1510
ORA-06512: at "MDSYS.SDO_ROUTER_PARTITION", line 661
ORA-06512: at line 1
Can someone help ??

hey i have found the solution myself :)

Non-Partitioned Global Index on Range-Partitioned Table.

Hi All,
Is it possible to create Non-Partitioned Global Index on Range-Partitioned Table?
We have 4 indexes on CS_BILLING range-partitioned table, in which one is CBS_CLIENT_CODE(*local partitioned index*) and others are unknown types of index to me??
Means other 3 indexes are what type indexes ...either non-partitioned global index OR non-partitioned normal index??
Also if we create index as :(create index i_name on t_name(c_name)) By default it will create Global index. Please correct me......
Please help me in identifying other 3 indexes types by referring below ouputs!!!
select INDEX_NAME,TABLE_NAME,PARTITIONING_TYPE,LOCALITY from dba_part_indexes where TABLE_NAME='CS_BILLING';
INDEX_NAME TABLE_NAME PARTITI LOCALI
CSB_CLIENT_CODE CS_BILLING RANGE LOCAL
select index_name,index_type,table_name,table_type,PARTITIONED from dba_indexes where table_name='CS_BILLING';
INDEX_NAME INDEX_TYPE TABLE_NAME TABLE_TYPE PAR
CSB_CREATE_DATE NORMAL CS_BILLING TABLE NO
CSB_SUBMIT_ORDER NORMAL CS_BILLING TABLE NO
CSB_CLIENT_CODE NORMAL CS_BILLING TABLE YES
CSB_ORDER_NBR NORMAL CS_BILLING TABLE NO
select INDEX_OWNER,INDEX_NAME,TABLE_NAME,COLUMN_NAME from dba_ind_columns where TABLE_NAME='CS_BILLING';
INDEX_OWNER INDEX_NAME TABLE_NAME COLUMN_NAME
RPADMIN CSB_CREATE_DATE CS_BILLING CREATE_DATE
RPADMIN CSB_SUBMIT_ORDER CS_BILLING SUBMIT_TO_INVOICE
RPADMIN CSB_SUBMIT_ORDER CS_BILLING ORDER_NBR
RPADMIN CSB_CLIENT_CODE CS_BILLING CLIENT_CODE
RPADMIN CSB_ORDER_NBR CS_BILLING ORDER_NBR
select dip.index_name, dpi.locality, dip.partition_name, dip.status
from dba_part_indexes dpi, dba_ind_partitions dip
where dpi.table_name ='CS_BILLING'
and dpi.index_name = dip.index_name;
INDEX_NAME LOCALI PARTITION_NAME STATUS
CSB_CLIENT_CODE LOCAL CSB_2006_4Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2006_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_1Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_2Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_4Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_1Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_2Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_4Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_1Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_2Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_4Q USABLE
select * from dba_part_indexes
where table_name ='CS_BILLING'
and locality = 'GLOBAL';
no rows selected
-Yasser
Edited by: YasserRACDBA on Mar 5, 2009 11:45 PM

Yaseer,
Is it possible to create Non-Partitioned and Global Index on Range-Partitioned Table?
Yes
We have 4 indexes on CS_BILLING range-partitioned table, in which one is CBS_CLIENT_CODE(*local partitioned index*) and others are unknown types of index to me??
Means other 3 indexes are what type indexes ...either non-partitioned global index OR non-partitioned normal index??
You got local index and 3 non-partitioned "NORMAL" b-tree tyep indexes
Also if we create index as :(create index i_name on t_name(c_name)) By default it will create Global index. Please correct me......
Above staement will create non-partitioned index
Here is an example of creating global partitioned indexes
CREATE INDEX month_ix ON sales(sales_month)
   GLOBAL PARTITION BY RANGE(sales_month)
      (PARTITION pm1_ix VALUES LESS THAN (2)
       PARTITION pm2_ix VALUES LESS THAN (3)
       PARTITION pm3_ix VALUES LESS THAN (4)
        PARTITION pm12_ix VALUES LESS THAN (MAXVALUE));Regards

Partitioned table tuning help

Similar Messages

Maybe you are looking for