Dear List,
I have a table which partitioned on date range This table has 10 indexes
on it I just wondered do I have to Partitioned all the 10 indexes or NOT?
Example:
Create table test(col1 number,col2 number,col3 number,col4 date)
tablespace data
partition by range(col4)
( partition part1
Hamid
On a partitioned table you can create either global (normal) indexes or
local (partitioned) indexes. There are advantages and disadvantages to each,
but you could start with normal indexes and then switch to partitioned
indexes as you find the need.
Dennis Williams
DBA, 80%OCP, 100% DBA
The global indexes can also be partitioned - using a different partition
column or different ranges than the table partitions. The drawback with
global indexes (partitioned or not) is that they become invalid when you do
an exchange partition or drop partition. Personally I think local indexes
are
Hamid,
You ae referring to decision between two types of indexes in case of a
partitioned table. You couls have a LOCAL index, in which case the index
will partitioned exactly in the same way as the table. The other one is
GLOBAL index, in which case you simple create an index (unpartitioned, if
What if I just not using any LOCAL or GLOBAL for creating index on a
partitioned table like as I said:
create index on test1(col2) tablespace users; as you see no
LOCAL no GLOBAL is this wrong or NOT?
-Original Message-
Sent: Thursday, June 12, 2003 12:50 PM
To: Multiple
GLOBAL is the default. If you ommiit the keyowrd, you have essentially
created a non-partitioned global index. This is not wrong; but do you want
to create a global index?
Arup Nanda
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Thursday, June 12,
Hi, Alex,
1. Can I ask you, what's UT.222? If UT supposed to be oracle schema, 222 is
not valid index name.
2. You can specify tablespace for EVERY next index partition, if you specify
CREATE INDEX ... TABLESPACE xxx and then move all partitions wherever you
want. After all new
Alex,
You have the syntax correct, but your index name seems invalid. Also, there
is no need to put double quotes around the tablespace name.
alter index index name rebuild partition partition name tablespace
tablespace name
is correct, though.
HTH,
Diana
-Original Message-
Sent:
Hi, Alex,
1. Can I ask you, what's UT.222? If UT supposed to be oracle schema, 222 is
not valid index name.
2. You can specify tablespace for EVERY next index partition, if you specify
CREATE INDEX ... TABLESPACE xxx and then move all partitions wherever you
want. After all new
/
SEGMENT_NAME SEGMENT_TYPE PARTITION_NAME
-- --
RAW_LOG_DATA_IX01INDEX PARTITIONP66
We have seen the wait on the read take well over an hour. After it
completes, the next wait will be for the same file and block
10 matches
Mail list logo
