(Alternative working title: How your expensive, top of the line Enterprise
Database can drive you bonkers)
I ran into this over the weekend during non-business hours - on a 42GB
table with 7,744 partitions.
Oracle delivers an autotask job in 12.1.0.2(+) called:
SYS.CLEANUP_ONLINE_IND_BUILD.
Guess what happens if you create an index online while that job is
running? Your index gets borked.
Unless there was something wrong with my index build, which I don't think
there is:
create index redacted.claim_elig_evt_q_idx01 on redacted.claim_elig_evt_q
(contract_id) invisible online parallel 16 local
/
Index created.
Elapsed: 00:43:04.52
alter index redacted.claim_elig_evt_q_idx01 noparallel
/
alter index redacted.claim_elig_evt_q_idx01 noparallel
*
ERROR at line 1:
ORA-14415: index in partially dropped state, submit DROP INDEX
Why Oracle would design an AUTOTASK job that can break online index builds
is beyond comprehension.
Chris
