RE: Index on Partition Table
- From: Jacques Kilchoer <Jacques.Kilchoer@xxxxxxxxx>
- To: "Jaromir D.B. Nemec" <jaromir@xxxxxxxxxxxx>, "mdinh@xxxxxxxxx" <mdinh@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 14 Jun 2010 18:26:56 -0700
You are right, my answer completely missed the question. GLOBAL is the default.
If you don't have either GLOBAL or LOCAL then it's the same as saying GLOBAL.
If you just have the GLOBAL clause and nothing else, or you omit the
GLOBAL/LOCAL clause, then you will end up with a GLOBAL non-partitioned index.
De : Jaromir D.B. Nemec [mailto:jaromir@xxxxxxxxxxxx]
Envoyé : dimanche 13 juin 2010 03:12
À : Jacques Kilchoer; mdinh@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Objet : Re: Index on Partition Table
Hello,
> If you don't specify GLOBAL, then a local partitioned index will be created.
I'd formulate it as follows
If you specify LOCAL instead of GLOBAL, then a local partitioned index will be
created.
I was not able to verify it in the documentation, but test (10.2.0.3) shows no
difference between the options:
ALTER TABLE fct ADD CONSTRAINT fct_pk PRIMARY KEY (key) USING INDEX;
and
ALTER TABLE fct ADD CONSTRAINT fct_pk PRIMARY KEY (key) USING INDEX GLOBAL;
In both cases a nonpartitioned index is created.
The difference start by adding the global index properties such as
ALTER TABLE fct ADD CONSTRAINT fct_pk PRIMARY KEY (key) USING INDEX GLOBAL
partition by hash (key) partitions 2
In this case a global partitioned index is created.
Regards,
Jaromir
Other related posts:
