Patch 4.5.1.58 Script Is Creating Index With Maxextent 99 (Doc ID 736844.1)

Last updated on SEPTEMBER 11, 2008

Applies to:

Oracle Clinical - Version: 4.5.3
Information in this document applies to any platform.

Goal

The patch 4.5.1.58 script creates an index (actually 2 of them) and overrides the tablespace
defaults by hard coding a storage clause with maxextents=99. One of the index creations failed.

Following is the code in the script

/* Bug 6624713 */
prompt Dropping index received_dcm_site_nfk_idx....
DROP INDEX
RECEIVED_DCM_SITE_NFK_IDX;

prompt creating index received_dcm_site_nfk_idx....
CREATE INDEX
RECEIVED_DCM_SITE_NFK_IDX ON RECEIVED_DCMS (
SITE_ID
, CLINICAL_STUDY_ID
, END_TS
, RECEIVED_DCI_ID
, RECEIVED_DCM_ENTRY_TS
, LAST_DATA_CHANGE_TS
) TABLESPACE RXC_LI_IDX_TSPA
STORAGE (
INITIAL 500K
NEXT 1M
MINEXTENTS 1
MAXEXTENTS 99
PCTINCREASE 0) COMPRESS 3
;

prompt Dropping index received_dcm_site_nfk_idxt....
DROP INDEX
RECEIVED_DCM_SITE_NFK_IDXT;


prompt creating index received_dcm_site_nfk_idxt....
CREATE INDEX
RECEIVED_DCM_SITE_NFK_IDXT ON RECEIVED_DCMST (
SITE_ID
, CLINICAL_STUDY_ID
, END_TS
, RECEIVED_DCI_ID
, RECEIVED_DCM_ENTRY_TS
, LAST_DATA_CHANGE_TS
) TABLESPACE TEST_INDEX
STORAGE (
INITIAL 50K
NEXT 100K
MINEXTENTS 1
MAXEXTENTS 99
PCTINCREASE 0) COMPRESS 3
;
/* End of Bug 6624713 */


Shall we proceed to re-create both of them without any storage clause parameter (or a maxextents =
unlimited) ?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms