VLDB Partitioning and Indexing

Hi All,
Here are some details about our DB.
It is a TELCO OLAP DB.
We are trying to run 20 batches in a month (we call it period).
In our biggest table, we will be loading more than 300 mills rows in each individual batch.
Thus in one month this table must have (300 Mills X 20) rows.
We are using Datastage as ETL tool. ETL is running on 12 duo core CPU's.
That's why we have 12 sub-partitions to the main partition to make the load purely parallel i.e. each node will be loading to individual sub-partition.
We are planning to partition all the Fact and Summary tables by
Period Key And sub-partition by Account_Key (Hash partition) (12 sub partitions).
1.     Partitioning and sub-partitioning impact on database maintenance.
2.     Impact on reporting i.e. how efficient will be the query if it is spread over multiple partitions and sub partitions.
3.     Re-Indexing.
As we know that SqlLoader will load the data and then it tries to reindex it. First few load will be quicker as partition is empty but how will it react at the end of the month.
There will be around 20 loads in one period (one period = one month).
Our biggest fact table is expected to have at least 300 mills rows in each load
And 16 Indexes.
Can we have some idea about how much time it may take to reindex this table?
Are there any other better ways to do it so that it is efficient for both load and query.
Thanks and regards,
Munish

Yes, sort of... hooked to a Linksys that's hooked to an AEBS, which serves both Airport and Airport Extreme as well as 3rd party B & G Wireless.
Unfortunately I consider it a real drawback that only one Computer can have Write Priviledges at a time, all the others can only Read. It can be switched, but I ended up using the USB Connection and just Sharing it as an external drive. Ethernet 10/100 only had 10MB/Sec writes, while USB2 had 20MB/Sec writes. Shared FW Drives get as little as 26MB/Sec... Might be that I have 802.11b devices sharing the AEBS, dunno.
Also, it requires Drivers, and though they've been good from 10.2.x through 10.4.8, you just never know when like 10.5.x or later might not work!
Personally, I'd only buy a Gigabit Ethernet NAS/NDAS Drive... if I bought one at all, but truthfully, Firewire Drives and/or eSATA Drives Shared over the Network, and using Tri-Backup is what works best for me.

Similar Messages

Difference between a partition and index

In BW how does an index differ from a partition? Thanks

Hi,
Partitioning works on the Binary Search functionality.The data is divided into parts and stored logically.Depending on the variable input the data is fetched intelligently through Data Mining concept.
For eg: if you have 120 records of Customer say 10 records per month and you have done a partition on 0CALMONTH.
So now the data will be stored in 12 sets of 10 each for a year data.Now depending upon your input say you put June month along with other selection then it will hit only the set for June month.So instead of searching for all over 120 records it will search only in that 1 set of 10 records.This improves query performance.
However, the restriction is that partitioning can be done only on time variable.
Whereas, Indexing works like the Primary Index or Key field of an R/3 table.
More the Index better the search and query performance.But again the flip side is it will complicate the design to provide Index on many fields and data loading time would be increased.Any changes and you would require to drop the index then reload and then again rebuild the Index.The number of Indexes to be used to improve query performance is a compromise between designs.
Hope this helps.

Optimizer=ALL_ROWS, PARTITION HASH, INDEX (RANGE SCAN) POOR PERFORMANCE?

Our os is;
SunOS 5.9
and database is;
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit
Our autotrace outputs are below also we have 10046 trace outputs;
08:41:04 tcell_dev@SCME > set timing on
08:41:19 tcell_dev@SCME > set autot on
08:41:21 tcell_dev@SCME > SELECT lnpessv.PROFILE_ID FROM SCME.LNK_PROFILEENTITY_SUBSSERVVAR lnpessv
08:41:25 2 WHERE lnpessv.SUBSCRIPTION_SERVICEVARIANT_ID = 1695083 ;
PROFILE_ID
1.400E+14
1.600E+14
Elapsed: 00:00:03.07
Execution Plan
0 SELECT STATEMENT Optimizer=ALL_ROWS (Cost=3 Card=3 Bytes=51)
1 0 PARTITION HASH (ALL) (Cost=3 Card=3 Bytes=51)
2 1 INDEX (RANGE SCAN) OF 'PK_PROFILEENTITY_SUBSSERVVAR' (INDEX (UNIQUE)) (Cost=
3 Card=3 Bytes=51)
Statistics
1 recursive calls
0 db block gets
1539 consistent gets
514 physical reads
0 redo size
258 bytes sent via SQL*Net to client
273 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
2 rows processed
08:41:32 tcell_dev@SCME > SELECT lnpessv.PROFILE_ID FROM SCME.LNK_PROFILEENTITY_SUBSSERVVAR lnpessv
08:41:43 2 WHERE lnpessv.SUBSCRIPTION_SERVICEVARIANT_ID = 169508 ;
PROFILE_ID
1.400E+14
1.600E+14
Elapsed: 00:00:04.01
Execution Plan
0 SELECT STATEMENT Optimizer=ALL_ROWS (Cost=3 Card=3 Bytes=51)
1 0 PARTITION HASH (ALL) (Cost=3 Card=3 Bytes=51)
2 1 INDEX (RANGE SCAN) OF 'PK_PROFILEENTITY_SUBSSERVVAR' (INDEX (UNIQUE)) (Cost=
3 Card=3 Bytes=51)
Statistics
1 recursive calls
0 db block gets
1537 consistent gets
512 physical reads
0 redo size
258 bytes sent via SQL*Net to client
273 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
2 rows processed
Here we see 97% wait time, and responce time is unexceptable; These are the waits from 10046 trace file;
WAIT #1: nam='gc cr grant 2-way' ela= 783 p1=341 p2=67065 p3=1 obj#=169530 tim=571610438395
WAIT #1: nam='db file sequential read' ela= 6924 file#=341 block#=67065 blocks=1 obj#=169530 tim=571610445466
WAIT #1: nam='gc cr grant 2-way' ela= 564 p1=294 p2=86263 p3=1 obj#=169531 tim=571610446493
WAIT #1: nam='db file sequential read' ela= 6629 file#=294 block#=86263 blocks=1 obj#=169531 tim=571610453158
INDEX RANGE SCAN PK_PROFILEENTITY_SUBSSERVVAR PARTITION: 1 512 (cr=1537 pr=512 pw=0 time=4272017 us)
This is the related tables properties;
OWNER     SCME
TABLE_NAME     LNK_PROFILEENTITY_SUBSSERVVAR
TABLESPACE_NAME     DATA01
STATUS     VALID
PCT_FREE     10
INI_TRANS     10
MAX_TRANS     255
INITIAL_EXTENT     65536
MIN_EXTENTS     1
MAX_EXTENTS     2147483645
LOGGING     NO
BACKED_UP     N
NUM_ROWS     239587420
BLOCKS     1587288
EMPTY_BLOCKS     0
AVG_SPACE     0
CHAIN_CNT     0
AVG_ROW_LEN     41
AVG_SPACE_FREELIST_BLOCKS     0
NUM_FREELIST_BLOCKS     0
DEGREE     1
INSTANCES     1
CACHE     N
TABLE_LOCK     ENABLED
SAMPLE_SIZE     71876226
LAST_ANALYZED     29.05.2006 23:21:24
PARTITIONED     NO
TEMPORARY     N
SECONDARY     N
NESTED     NO
BUFFER_POOL     DEFAULT
ROW_MOVEMENT     DISABLED
GLOBAL_STATS     YES
USER_STATS     NO
SKIP_CORRUPT     DISABLED
MONITORING     YES
DEPENDENCIES     DISABLED
COMPRESSION     DISABLED
DROPPED     NO
We are suspecting rac configuration and hash partition and index usage with rac.
Any comments will be welcomed,
Thank you.
Tonguç

this is the output of dbms_metadata.get_ddl for the table;
CREATE TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR"
(     "SUBSCRIPTION_SERVICEVARIANT_ID" NUMBER NOT NULL ENABLE NOVALIDATE,
     "PROFILE_ID" NUMBER NOT NULL ENABLE NOVALIDATE,
     "CREATED_BY_ID" NUMBER,
     "CREATED_DATE" DATE DEFAULT SYSDATE,
     "UPDATED_BY_ID" NUMBER,
     "UPDATED_DATE" DATE,
     CONSTRAINT "PK_PROFILEENTITY_SUBSSERVVAR" PRIMARY KEY ("SUBSCRIPTION_SERVICEVARIANT_ID", "PROFILE_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 4194304
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID","PROFILE_ID")
(PARTITION "SYS_P52989"
TABLESPACE "INDX02",
PARTITION "SYS_P52990"
TABLESPACE "INDX02",
PARTITION "SYS_P54010"
TABLESPACE "INDX02",
PARTITION "SYS_P54011"
TABLESPACE "INDX02",
PARTITION "SYS_P54012"
TABLESPACE "INDX02") ;
CREATE UNIQUE INDEX "SCME"."PK_PROFILEENTITY_SUBSSERVVAR" ON "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ("SUBSCRIPTION_SERVICEVARIANT_ID", "PROFILE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 4194304
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID","PROFILE_ID")
(PARTITION "SYS_P52989"
TABLESPACE "INDX02",
PARTITION "SYS_P52990"
TABLESPACE "INDX02",
PARTITION "SYS_P53499"
TABLESPACE "INDX02",
PARTITION "SYS_P53500"
TABLESPACE "INDX02") ENABLE NOVALIDATE,
     CONSTRAINT "FK_LNK_PROF_REFERENCE_SDP_SUBS" FOREIGN KEY ("SUBSCRIPTION_SERVICEVARIANT_ID")
     REFERENCES "SCME"."SDP_SUBSCRIPTIONSERVICEVARIANT" ("SUBSCRIPTION_SERVICEVARIANT_ID") DEFERRABLE INITIALLY DEFERRED ENABLE NOVALIDATE
) PCTFREE 10 PCTUSED 40 INITRANS 10 MAXTRANS 255 NOCOMPRESS NOLOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "DATA01" ;
CREATE INDEX "SCME"."LNK_PROFILEENTITY_SUB_HNDX3" ON "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ("SUBSCRIPTION_SERVICEVARIANT_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 2097152
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID")
(PARTITION "SYS_P53501"
TABLESPACE "INDX02",
PARTITION "SYS_P53502"
TABLESPACE "INDX02",
PARTITION "SYS_P53499"
TABLESPACE "INDX02",
PARTITION "SYS_P53500"
TABLESPACE "INDX02") ;
CREATE INDEX "SCME"."PROFILE_ID_NDX43" ON "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ("PROFILE_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "INDX03" ;
ALTER TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" ADD CONSTRAINT "PK_PROFILEENTITY_SUBSSERVVAR" PRIMARY KEY ("SUBSCRIPTION_SERVICEVARIANT_ID", "PROFILE_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE(INITIAL 4194304
BUFFER_POOL DEFAULT)
TABLESPACE "INDX02" GLOBAL PARTITION BY HASH ("SUBSCRIPTION_SERVICEVARIANT_ID","PROFILE_ID")
(PARTITION "SYS_P52989"
TABLESPACE "INDX02",
PARTITION "SYS_P52990"
PARTITION "SYS_P53498"
TABLESPACE "INDX02",
PARTITION "SYS_P53499"
TABLESPACE "INDX02",
PARTITION "SYS_P53500"
TABLESPACE "INDX02") ENABLE NOVALIDATE;
ALTER TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" MODIFY ("SUBSCRIPTION_SERVICEVARIANT_ID" NOT NULL ENABLE NOVALIDATE);
ALTER TABLE "SCME"."LNK_PROFILEENTITY_SUBSSERVVAR" MODIFY ("PROFILE_ID" NOT NULL ENABLE NOVALIDATE);

Re-org oracle 11.1.0.7 partitioned and sub partitioned index not validiting

Hi,
As part of maintenance i did the following thing on the oracle 11.1.0.7 on windows (no archive log mode);
     Re-orgnaized the tables in application- data tablespace - done
     Re-orgnaized large table in SYSAUX tablespace - only one table (alter table sys.WRI$_OPTSTAT_HISTGRM_HISTORY move tablespace sysaux
alter index sys.I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST rebuild nologging;
alter index sys.I_WRI$_OPTSTAT_H_ST rebuild nologging;)
     Re-built the indexes on applicaton index tbs- done
     Re-built the partition indexes on application index tbs - done
     rebuilding of indexes in SYSAUX - done since it was invalid
     Run the analyze job –
     Re-claim the space at database level and OS level
but i have the issues of partitioned and subpartition indexes are not validating..how to validate the indexes i am using the below querires but:
ORA-14287: cannot REBUILD a partition of a Composite Range partitioned i

i am using the below sqls:
set head off
set linesize 200
select 'alter index '||index_owner||'.'||index_name||' rebuild partition '||partition_name||' ; ' from dba_ind_partitions where status <> 'VALID' and index_owner not in ('SYS','SYSTEM')
set head off
set linesize 200
select 'alter index '||index_owner||'.'||index_name||' rebuild subpartition '||subpartition_name||' ;'
from dba_ind_subpartitions
where status <> 'VALID'

Cannot INSERT records into Partitioned Spatial Table and Index

I am trying to tune our Spatial Storage by creating partitioning our spatial_entity table and index. I used the World Geographic Reference System (GEOREF) creating a partition for each 15 x 15 degree grid square assigning a partition key of decimal longitude, decimal_latitude. The build went OK, however when trying to insert a data record I receive an ORA-14400: Inserted partition key does not map to any partition.
I validated the CREATE(s), and all appears correct, but obviously something is not correct, which is prompting for expert help in this forum.
I would be very grateful for your help.
Below are the code snippets for the table and index, and an insert statement.
CREATE TABLE spatial_entity
     geoloc_type VARCHAR2 (60 BYTE) NOT NULL
,entity_id NUMBER NOT NULL
,metadata_xml_uuid VARCHAR2 (40 BYTE) NOT NULL
,geoloc MDSYS.sdo_geometry NOT NULL
,nee_method CHAR (1 BYTE) NOT NULL
,nee_status CHAR (1 BYTE) NOT NULL
,decimal_latitude NUMBER (15, 6) NOT NULL
,decimal_longitude NUMBER (15, 6) NOT NULL
PARTITION BY RANGE (decimal_longitude, decimal_latitude)
     PARTITION p_lt_0_90s
          VALUES LESS THAN (1, -90)
     ,PARTITION p_lt_0_75s
          VALUES LESS THAN (1, -75)
     ,PARTITION p_lt_0_60s
          VALUES LESS THAN (1, -60)
     ,PARTITION p_lt_0_45s
          VALUES LESS THAN (1, -45)
     ,PARTITION p_lt_0_30s
          VALUES LESS THAN (1, -30)
     ,PARTITION p_lt_0_15s
          VALUES LESS THAN (1, -15)
     ,PARTITION p_lt_0_0
          VALUES LESS THAN (1, 0)
     ,PARTITION p_lt_0_15n
          VALUES LESS THAN (1, 15)
     ,PARTITION p_lt_0_30n
          VALUES LESS THAN (1, 30)
     ,PARTITION p_lt_0_45n
          VALUES LESS THAN (1, 45)
     ,PARTITION p_lt_0_60n
          VALUES LESS THAN (1, 60)
     ,PARTITION p_lt_0_75n
          VALUES LESS THAN (1, 75)
     ,PARTITION p_lt_0_90n
          VALUES LESS THAN (1, maxvalue)
CREATE INDEX geo_spatial_ind ON spatial_entity (geoloc)
INDEXTYPE IS mdsys.spatial_index
PARAMETERS ('layer_gtype=MULTIPOINT TABLESPACE=GEO_SPATIAL_IND') LOCAL
(PARTITION p_lt_0_90s,
PARTITION p_lt_0_75s,
PARTITION p_lt_0_60s,
PARTITION p_lt_0_45s,
PARTITION p_lt_0_30s,
PARTITION p_lt_0_15s,
PARTITION p_lt_0_0,
PARTITION p_lt_0_15n,
PARTITION p_lt_0_30n,
PARTITION p_lt_0_45n,
PARTITION p_lt_0_60n,
PARTITION p_lt_0_75n,
PARTITION p_lt_0_90n,
INSERT INTO spatial_entity
     geoloc_type
     ,entity_id
     ,metadata_xml_uuid
     ,geoloc
     ,nee_method
     ,nee_status
     ,decimal_latitude
     ,decimal_longitude
VALUES
               'BATCH'
               ,0
               ,'6EC25B76-8482-4F95-E0440003BAD57EDF'
               ,"MDSYS"."SDO_GEOMETRY"
                    2001
                    ,8307
                    ,"MDSYS"."SDO_POINT_TYPE" (32.915286, 44.337902, NULL)
                    ,NULL
                    ,NULL
               ,'M'
               ,'U'
               ,32.915286
               ,44.337902
Thank you for you help.
Dave

Thank you for your quick reply. I did not post the entire CREATE script as it is quite long. The portion of the script that is applicable to the INSERT is:
,PARTITION p_lt_45e_90s
          VALUES LESS THAN (23, -90)
     ,PARTITION p_lt_45e_75s
          VALUES LESS THAN (23, -75)
     ,PARTITION p_lt_45e_60s
          VALUES LESS THAN (23, -60)
     ,PARTITION p_lt_45e_45s
          VALUES LESS THAN (23, -45)
     ,PARTITION p_lt_45e_30s
          VALUES LESS THAN (23, -30)
     ,PARTITION p_lt_45e_15s
          VALUES LESS THAN (23, -15)
     ,PARTITION p_lt_45e_0
          VALUES LESS THAN (23, 0)
     ,PARTITION p_lt_45e_15n
          VALUES LESS THAN (23, 15)
     ,PARTITION p_lt_45e_30n
          VALUES LESS THAN (23, 30)
     ,PARTITION p_lt_45e_45n
          VALUES LESS THAN (23, 45)
     ,PARTITION p_lt_45e_60n
          VALUES LESS THAN (23, 60)
     ,PARTITION p_lt_45e_75n
          VALUES LESS THAN (23, 75)
     ,PARTITION p_lt_45e_90n
          VALUES LESS THAN (23, maxvalue)
Or, I do not fully understand. Are you indicating that I must explcitly state the longitude in each clause,
e.g ,PARTITION p_lt_45e_45n
          VALUES LESS THAN (45, 45)
,PARTITION p_lt_45w_45n
          VALUES LESS THAN (-45, 45)
If so, that answers the question of why it cannot find a partition, however an Oracle White Paper "Oracle Spatial Partitioning Best Practices" Sept 2004, discusses multi column partitioning such as represented by this problem, and gives an INSERT statement example of :
CREATE TABLE multi_partn_table (in_date DATE,
geom SDO_GEOMETRY, x_value NUMBER, y_value NUMBER)
PARTITION BY RANGE (X_VALUE,Y_VALUE)
PARTITION P_LT_90W_45S VALUES LESS THAN (1,-45),
PARTITION P_LT_90W_0 VALUES LESS THAN (1,0),
PARTITION P_LT_90W_45N VALUES LESS THAN (1,45),
PARTITION P_LT_90W_90N VALUES LESS THAN (1,MAXVALUE
and as I am writing this I am seeing that I failed to include the longitude and latitude in the SDO_GEOMETRY clause, so it does appear tht I need to explicitly state the longitude valuues.
What is your judgement sir?
Dave

How to partition tables and indexes in this scenario?

So our situation is pretty simple. We have 3 tables.
A, B and C
the model is A->>B->>C
Currently A, B and C are range partitioned on a key created_date however it's typical that only C is every qualfied with created date. There is a foreign key from B -> A and C -> B
we have many queries where the data is identified by state that is indexed currently non partitioned on columns in A ... there are also indexes on the foreign keys that get from C -> B -> A. Again these are non partitioned indexes at this time.
It is typical that we qualify A on either account or user or both. There are indexes (non partitioned) on these
We have a problem now because many of the queries use leading wildcards ie. account like '%ACCOUNT' etc. This often results in large full table scans. Our solution has been to remove the leading wildcard but this isn't always possible.
We are wondering how we can benefit from partitioning and or sub partitioning table A. since it's partitioned on created_date but rarely qualify by that.
We are also wondering where and how we can benefit from either global partitioned index or local partitioned indexes on tables A. We suspect that the index on the foreign key from C to B could be a local partitioned index.
I am also wondering what impact pushing the state from A that's used to qualify A down to C would have any advantage.
C is the table that currently we qualify with the partition key so I figure if you also pushed down the state from A that's used to qualify the set of C's we want based on the set of B's we want based on the set of A thru qualfying on columns within A.
If we push down some of those values to C and simply use C when filtering I'm wondering what the plans will look like compared to having to work all the way up from the bottom to the top before it begins qualifying A.
Edited by: steffi on Jan 14, 2011 11:36 PM

We are wondering how we can benefit from partitioning and or sub partitioning table A. since it's partitioned on >created_date but rarely qualify by that. Very good question. Why did you partition on it? You will never have INSERTS on these partitions, but maybe deletes and updates? The only advantage (I can think of) would be to set these partitions in a read only tablespace to ease backup... but that's a weired reason.
we have many queries where the data is identified by state that is indexed currently non partitioned on columns in >A ... there are also indexes on the foreign keys that get from C -> B -> A. Again these are non partitioned indexes at >this time.Of course. Why should they be partitioned by Create_date?
It is typical that we qualify A on either account or user or both. There are indexes (non partitioned) on these
We have a problem now because many of the queries use leading wildcards ie. account like '%ACCOUNT' etc. This >often results in large full table scans. Our solution has been to remove the leading wildcard but this isn't always possible.I would suspect full index scan. Isn't it?
We are also wondering where and how we can benefit from either global partitioned index or local partitioned >indexes on tables A. We suspect that the index on the foreign key from C to B could be a local partitioned index.As A is not accessed by any partition, why should C and B profit? You should look to partition by the key you are using to access. But, you are looking to tune your SQLs where the access is like '%ACCOUNT' on A. Then when there is a match. ORACLE joins via your index and nested loop (right?) to B and C.
I am also wondering what impact pushing the state from A that's used to qualify A down to C would have any >advantage.Why should it. It just makes the table and indexes larger => more IO.
C is the table that currently we qualify with the partition key so I figure if you also pushed down the state from A >that's used to qualify the set of C's we want based on the set of B's we want based on the set of A thru qualfying >on columns within A.If the access from A to C would be .. AND A.CREATE_DATE =C.CREATE_DATE and c.key like '%what I want%' which does not qualifify for a FK ;-) then, as that could be resulting in a partition scan, you could "profit". But, I'm sure that's not your model.
If we push down some of those values to C and simply use C when filtering I'm wondering what the plans will look >like compared to having to work all the way up from the bottom to the top before it begins qualifying A.So you want to denormalize A,B,C and into one table? With the same access is like '%ACCOUNT' you would get a full scan on an index as before, just the objects would be larger due to redundance and harder to maintain. In the end you would have a bad and slower design.
Maybe you explain what the problem is.
Full index scan can not be avoided, but that can be made faster by e.g. parallel query, and then the join to B and C should be a "snip" if you just identify a small subset of rows in these tables.

A question regarding database table partitioning and table indexes in 10g

We are considering partitioning a large table in our 10g database, in order to improve response time. I believe I understand the various partitioning options, but am wondering about the indexes built over the table. When the table is partitioned, will the indexes also be partitioned "automatically"? Or do I need to also partition the indexes as well?
Thank you in advance to any and all who respond to this question.

Hello,
When you build your partiton table you just need to create indexes locally and they will be partitioned automatically, see following example
CREATE TABLE YY_EVENT
PART_KEY       DATE                              NOT NULL,
SUBPART_VALUE NUMBER                             NULL,
EVENT_NAME     VARCHAR2(30 BYTE)                  NULL,
EVENT_VALUE    NUMBER                             NULL
TABLESPACE TEST_DATA
PARTITION BY RANGE (PART_KEY)
PARTITION Y_EVENT_200901 VALUES LESS THAN (TO_DATE(' 2009-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    TABLESPACE TEST_DATA,
PARTITION Y_EVENT_200902 VALUES LESS THAN (TO_DATE(' 2009-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    TABLESPACE TEST_DATA
-- This will create paritioned indexes automatically
CREATE INDEX MY_IDX ON YY_EVENT
(EVENT_NAME)
TABLESPACE TEST_DATA
LOGGING
LOCAL;Regards
Edited by: OrionNet on Feb 25, 2009 12:05 PM

Cube process stuck - finished building aggregations and indexes for the partition

Hi friends
My cube processing stuck up at "Finished building aggregations and indexes for the partition". How can I troubleshoot this.
Appreciate your help.
Royal Thomas

Royal,
Your question is discussed
here and
here also. May be it will help you out.
Best regards.

I've messed up my boot camp partition and would love some help :)

OK So here's what I've done..
I removed my optical drive, inserted a hard drive caddy, moved my main 750GB hard drive to this location, installed a brand new 250GB SSD, installed Mavericks on said SSD, and booted up. Everything was happy. But now I have 550 GB of my 750GB taken up by my old install of OSX. I took all of my files off, put them on an external drive, and formatted the OSX Journaled portion of the hard drive to ExFat. This, of course, broke the ability to boot from Windows.
My goal:
250GB SSD: OSX
750 Hard Drive: 200GB to Windows, the remaining in a format writable to both Windows and Mac. (which is why I chose ExFat).
And, obviously, the ability to boot from either.
What do I do? I don't have any of my original install media from Windows (I think it was a W7 install that I upgraded with a download to W8 from M$'s website). I'd like to retain everything that's installed there already on BC and just repair it somehow. I've read around that ReFit might help. I'm willing to try it if the general consensus says that's the way to go.
Also, I've noticed that when I changed my user account to be able to store on my ExFat drive, that it can never finish indexing and I can't install dropbox. Is there a better solution to what I'm trying to do?

So, since I got no bites here... How about this...
I formatted that ExFat partition to a Mac OS Journaled partition, and my computer seems to be working great. I will keep it like this. Anyone know how to repair that Windows install from BootCamp?

Where did the Partitions and SubPartitions go?

I created a table with partition Range (Transaction_Date, Retention_Period) and hash (Record_Id) subpartition template (for 32 subpartitions)
Then I add more partitions and while the loop is going on I can get counts of partitions and subpartitions. The job finished and my log table shows about 1800 partitions added and there should be 32 subpartitions for each of the partitions. However, user_tab_partitions shows zero records for the table, and user_tab_subpartitions also show zero record. After a few minutes the partitions show up but no subpartitions. The indexes on the table have also disappeared (one local and one global)
Any explanation for this behaviour?
Working on Exadata 11.2.0.3
Querying
USER_TABLES
USER_TAB_PARTITIONS
USER_TAB_SUBPARTITIONS
USER_INDEXES

>
Step 1. Create Table xyz (c1 date, c2 integer c3 integer, etc)
partition by range (c1,c2)
subpartition template (s01, s02... s32)
create index i1 on xyz (c1,c2,c3) local;
Then, since I want to create about 1800 partitions I have a procedure that has a "loop around" ALTER TABLE add Partition .. until all the partitions are created. This is the "Job" which while running I query USER_TAB_PARTITIONS and USER_TAB_SUBPARTITIONS to see how things are progressing. And Yes ALTER Table has no progressing to verify.
So al the partitions get created. No errors from the procedure to go through creating all the partitions. So I would expect that at the end I should get to see all the new partitions for the Table. Instead I get "no records" from USER_TAB_PARTITIONS and USER_TAB_SUBPARTITIONS.
I am also aware that "ALTER TABLE ADD PARTITION .." cannot make indexes go away. However, if the query on USER_INDEXES returns nothing, what happend to the Index created before the partitions were added?
I am not using DBMS_REDEFINITION. The only procedure is to add partitions one at a time for each date for 3 years. If you have a better way than a procedure please advise accordingly.
>
In order to help you the first step is to understand what problem you are dealing with. Then comes trying to determine what options are available for addressing the problem. There are too many times , and yours may, or may not, be another one, where people seem to have settled on a solution before they have really identified the problem.
Anytime someone mentions the use of dynamic SQL it raises a red flag. And when that use is for DDL, rather than DMl, it raises a REALLY BIG red flag.
Schema objects need to be managed properly and the DDL that creates them needs to be properly written and kept in some sort of version control.
Scripts and procedures that use dynamic SQL are more properly used to create DDL, not to execute it. That is, rather than use a procedure to dynamically create or alter a table you would use the procedure to dynamically create a DDL script that would create or alter the table.
Let's assume that you know for certain that your table really needs to have 1800 partitions, be subpartitioned the way you say and have partition and subpartitions names that you assign. Well, that would be a pain to hand-write 1800 partition definitions.
So you would create a procedure that would produce a CREATE TABLE script that had the proper clauses and syntax to specify those 1800 partitions. Your 'loop' would not EXECUTE an ALTER TABLE for each partition but would create the partition specification and modify the partition boundaries for each iteration through the loop. Sort of like
for i from 1 to 365 loop
add partition spec for startDate + i
end loop;The number of iterations would be a parameter and you would start with 2 or 3. Always test with the smallest code that will produce the correct results. If the code works for 3 days it will work for any larger reasonable number.
Then you would save that script in your version control system and run it to create the table. There would be nothing to monitor since there is just one script and when it is done it is done.
That would be a proper use of dynamic sql: to produce DDL, not to execute it.
Back to your issue. If I were your manager then based on what you posted I would expect you to already have
1. a requirements document that stated the problem (e.g. performance, data management) that was being addressed
2. test results that showed that your proposed solution (a table partitioned the way you posted) solves the problem
The requirements doc would have detail about what the performance/management issues are and what impact they are having
You also need to document what the possible solutions are, the relative merits of each solution and the factors you considered when ranking the solutions. That is, why is your particular partitioning scheme the best solution for the problem.
You should have test results that show the execution plans and performance you achieved by using a test version of your proposed table and indexes.
Until you have 'proven' that your solution will work as you expect I wouldn't recommend implementing the full-blown version of it.
1. Create a table MANUALLY that has 2 or three days worth of partitions.
2. Load those partitions with a representative amount of data
3. Execute test queries to query data from one of those partitions
4. Execute the same test queries against your current table
5. Capture the execution plans (the actual ones) for those queries. Verify that you are getting the performance improvements that you expected.
Once ALL of that prep work is done and you have concluded that your table/index design is correct then go back to work on writing a script/procedure that will produce (not execute) DDL to produce the main table and partitioning you designed.
Just an aside on what you posted. The indexes should be created AFTER the table and its partitions are created. If you are creating your local index first, as you post suggests, you are forcing Oracle to revamp it 1800 times when each partition is added. Just create the index after the table.
p.s. the number of posts anyone has is irrevelant. The only thing that matters is whether the advice or suggestions they provide is helpful. And the helpfullness of those is limited to, and based on, ONLY the information a poster provides. For exampe, your proposed partitioning scheme might be perfectly appropriate for your use case or it could be totally inappropriate. We have no way of knowing without knowing WHY you chose that scheme.
But I haven't seen one like that so it makes me suspicious that you really need to get that complicated.

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

Creation of Hash Partitioned Global Index

Hash Partion Index creation
Hi friends,
Could you suggest me whether we can create a hash partitioned index by using syntax as below in 9i.
CREATE INDEX hgidx ON tab (c1,c2,c3) GLOBAL
PARTITION BY HASH (c1,c2)
(PARTITION p1 TABLESPACE tbs_1,
PARTITION p2 TABLESPACE tbs_2,
PARTITION p3 TABLESPACE tbs_3,
PARTITION p4 TABLESPACE tbs_4);
I am getting error ORA-14005 Missing Key word Range.
Thanks in advance for your help.

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

Problems with partitioning and install Grub. Fresh install

All,
First post here. I appreciate any help you can offer.
I am having some problems when installing Arch Linux.
I am installing Arch on a brand new (3 days old) Toshiba SatelliteC655D-S5300 Laptop.
Hot sheet can be found at http://cdgenp01.csd.toshiba.com/content … -S5300.pdf.
I was initially installing from 2011.08.19 x86_64 Core CD but someone suggested using the latest version.
Now I am installing from 2011.11.13 x86_64 CD burned at 4x (the slowest my burner can go).
I am able to complete all steps up to installing GRUB, but it fails to install.
During partitioning I receive a few errors and I believe this is contributing to the issue.
At first I tried automatic partitioning with 100mb boot, 1024mb swap, 10,000mb / and the rest of 320g for /home. Each partition is ext3 except /boot which is ext2.
During the automatic partitioning an error briefly occured: /usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found.
After speaking with a friend they suggested manually partitioning and using UUIDs instead.
1) So far I have removed all partitions, rebooted.
2) Partitioned using cFdisk. Bootable 100mb parition, 1024mb swap, 15,000mb primary (/), 3000mb logical (/var), and the rest 300949mb logical (/home).
3) Once I write the changes and quit I reboot.
4)I go back into the installer and complete steps 1-3.
5) Go to step 4 and and then manually configure block devices, file systems, or mount points.
6) I choose the option for uuid and hit ok.
At this point 3 error messages appear at the bottom:
/usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'part,' : not a valid identifier
/usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'type,' : not a valid identifier
/usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'label,' : not a valid identifier
(Screenshot: http://i.imgur.com/OHRKo.jpg)
7) Next it prompts me to add the mount points for each partition set.
8) Select the partition, the mount point, it asks me for label and any additional opts for mkfs.ext3.
9) I leave the label and opts field blank. After selecting ok to the opts field I get the same 3 errors as above:
/usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'part,' : not a valid identifier
/usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'type,' : not a valid identifier
/usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'label,' : not a valid identifier
(Screenshot: http://i.imgur.com/QqkSP.jpg)
I am able to successfully set a mount point and format each partition. But I receive the same set of 3 errors occur for each partition.
10) Once I complete the formatting I proceed to step 8, install bootloader.
It says Generating Grub device map.. This could take a while. Please be patient.
I receivieve the following error on this screen: /usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found.
(Screenshot: http://i.imgur.com/B5j4K.jpg)
11) After the error displays it goes to the next screen, before installing grub you must review config file. etc.
12) I hit ok and then :q the config file. Is there a critical change in the config file that I'm missing?
13) After closing the file I select which the boot device where the GRUB bootloader will be installed. My only option is /dev/sda. I hit ok
Then I get the following 2 errors:
/usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found
/usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found
(Screenshot: http://i.imgur.com/ol840.jpg)
13) Error installing GRUB. See /dev/tty7 for output. Ok
14) GRUB was NOT successfully installed. Ok
I checked out TTY7.
It shows the installer issuing the following commands in GRUB.
1) device (hd0,) /dev/sda
Error 12: Invalid device requested
2) root (hd0,0)
Filesystem type is extf2, partition type 0x83
3) setup (hd0,)
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
Running "embed /grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
Running "install /grub/stage1 (hd0,0) /grub/stage2 p /grub/menu.lst "... succeeded
Done.
4) quit
I have tried rebooting from here and using the Arch CD to boot into the existing OS but it does not work.
I tried grub-install /dev/sda
I get Probing devices to check BIOS drives. This may take a long time.
/dev/mapper../dm-0 does not have any corresponding BIOS drive.
I have tried going into grub and issuing the same commands the install script did.
Same errors.
I'm afraid I don't have network access at the moment so I can't get a successful /arc/report-issues to run.
I hope I've included enough information to start the troubleshooting.
Let me know if I've missed anything!
Thanks in advance,
-Jason
Last edited by username17 (2011-11-17 22:37:56)

username17 wrote:I get Probing devices to check BIOS drives. This may take a long time.
/dev/mapper../dm-0 does not have any corresponding BIOS drive.
Your drive does not have an MBR to install grub to as it is a GPT disk - which is also not supported under the old GRUB.
You need to create a small partition at the very beginning of the drive (8MB is plenty) and set the "bios_grub" flag. ie the "BIOS drive" your error refers to.
You will then need to install the grub2-bios package following the chroot instructions on the grub2 wiki page here: https://wiki.archlinux.org/index.php/GRUB2#Installation
** Please note that I found the chroot mounts to be outdated - replace "/tmp/install" with "/mnt" **
Your alternative solution is to boot a gparted liveCD and prepare your disk as MBR - this will (most likely) destroy all existing data on the disk.

Table and Index compression in data warehouse - thoughts?

Hi,
We have a data warehouse with large fact tables and materialized views of this data.
Approx 3 million inserts per day week-ends about 12 million.
The fact tables we have expected to have 200 million, and couple with 1-3 billion.
Tables partitioned and have bitmap indexes.
Just wondered what thoughts were about compressing large fact tables and mviews both from point of view of ETL into them and reporting from them afterwards.
I take it, can compress/uncompress accordingly without any problem?
Many Thanks

After compression, most SELECT statements would not get slower. Actually, many can get faster due to reduced IO and buffer needs.
The situation with DMLs is more complex. It depends on the exact compression options (basic or advanced) and the DML (INSERT,UPDATE, direct load,..),but generally DML are negatively affected by compression.
In a Data Warehouses (DWs), it is usually quite beneficial to compress partitions or tables that contain data that is not supposed to be modified (read only or read mostly). Please note that in many cases you do not have to compress while you are loading the data – you can do that later.
You can also consider compressing some of your B-tree indexes (if you use them in your DW system).
Iordan Iotzov
http://iiotzov.wordpress.com/

Create a fast refresh materialized view with partitioned primary index

Hi,
I have a materialized view that is based on a table with primary key.
I want to create a materialized view with a partitioned primary index . do you have any way of doing it?
I tried to create a materialized view with rowid and then I created a partitioned primary index on it.
It did not work as what I expected. I could not perform a fast refresh on it. the materialized view can only complete refresh
thank you

Hi,
Here is some info from the Oracle Documentation.
http://download.oracle.com/docs/cd/E11882_01/server.112/e10706/repmview.htm
http://download.oracle.com/docs/cd/E11882_01/server.112/e10810/basicmv.htm
Determining the Fast Refresh Capabilities of a Materialized View
http://download.oracle.com/docs/cd/E11882_01/server.112/e10706/repmview.htm#BABEDIAH
Regards,

VLDB Partitioning and Indexing

Similar Messages

Maybe you are looking for