Here is the sql used to create the table! After table creation before any data is imported I show 70+ extents. We are having performance issues around this table! This is an upgrade from 8.1.7 where no issues were reported! However after the upgrade on 10.2 we are having performance issues.
CREATE TABLE TRAK
(
tkdept1 CHAR(2),
tkacct CHAR(8),
tkdate1 CHAR(10),
tktime1 CHAR(8),
tkseq1 char(1),
tkdept2 CHAR(2),
tknhcd CHAR(3),
tkdate2 CHAR(10),
tktime2 CHAR(8),
tkseq2 CHAR(1),
tkdept3 CHAR(2),
tkrxnm CHAR(6),
tkdate3 CHAR(10),
tktime3 CHAR(8),
tkseq3 CHAR(1),
tkdept4 CHAR(2),
tkdate4 CHAR(10),
tktime4 CHAR(8),
tkseq4 CHAR(1),
tkrph CHAR(3),
tkemp CHAR(3),
tkrfl CHAR(2),
tkrqty CHAR(4),
tktyp CHAR(2),
tkcopay CHAR(10),
tkoptyp CHAR(4),
tkcptyp CHAR(4),
tkrej CHAR(12),
tkcg CHAR(1),
filler CHAR(50),
tkevt1 CHAR(60),
tkevt2 CHAR(60),
tkevt3 CHAR(60),
tkevt4 CHAR(60),
tkevt5 CHAR(60),
tkevt6 CHAR(60),
tkevt7 CHAR(60),
tkevt8 CHAR(60),
tkevt9 CHAR(60),
tkevt10 CHAR(60),
tkevt11 CHAR(60),
tkevt12 CHAR(60),
tkevt13 CHAR(60),
tkevt14 CHAR(60),
tkevt15 CHAR(60),
tkevt16 CHAR(60),
tkevt17 CHAR(60),
tkevt18 CHAR(60),
tkevt19 CHAR(60),
tkevt20 CHAR(60),
CONSTRAINT TRAKK0 PRIMARY KEY
(tkdept1,tkacct,tkdate1,tk
time1,tkse
q1)
using index tablespace user_index
storage (INITIAL 5M NEXT 1M PCTINCREASE 1)
)
STORAGE (INITIAL 50M NEXT 5M PCTINCREASE 1)
TABLESPACE USER_DATA;
CREATE INDEX TRAKK1 ON TRAK (tkdept2,tknhcd,tkdate2,tk
time2,tkse
q2)
STORAGE (INITIAL 5M NEXT 1M PCTINCREASE 1)
TABLESPACE USER_INDEX;
CREATE INDEX TRAKK2 ON TRAK (tkdept3,tkrxnm,tkdate3,tk
time3,tkse
q3)
STORAGE (INITIAL 5M NEXT 1M PCTINCREASE 1)
TABLESPACE USER_INDEX;
CREATE INDEX TRAKK3 ON TRAK (tkdept4,tkdate4,tktime4,t
kseq4)
STORAGE (INITIAL 5M NEXT 1M PCTINCREASE 1)
TABLESPACE USER_INDEX;
COMMIT;
Start Free Trial