Hi All ,
At my site there is load utility running loading each partition . Yesterday it was brought to attention that these jobs are running long into the system. On investigation found this situation for one of the partition
Where the loaded records(load replace) were 0 but build phase elapse time was 42:24 minutes
18:57:27.72 DSNURWT - (RE)LOAD PHASE STATISTICS - NUMBER OF RECORDS=0 FOR TABLE
18:57:27.72 DSNURWT - (RE)LOAD PHASE STATISTICS - TOTAL NUMBER OF RECORDS LOADED
:27.72 DSNURILD - (RE)LOAD PHASE STATISTICS - NUMBER OF INPUT RECORDS PROCESSED=
:27.72 DSNURILD - (RE)LOAD PHASE COMPLETE, ELAPSED TIME=00:00:00
18:57:27.73 DSNURBXE - BUILD PHASE STATISTICS - NUMBER OF KEYS=0 FOR INDEX XXXXX
19:39:52.03 DSNURBXE - BUILD PHASE STATISTICS - NUMBER OF KEYS=0 FOR INDEX
:52.03 DSNURBXD - BUILD PHASE STATISTICS - NUMBER OF INDEXES=0
:52.03 DSNURBXD - BUILD PHASE COMPLETE, ELAPSED TIME=00:42:24
Job performing load already has sorted records(input for load) for specific partition .
When I checked further , runstats data was very old December
2018 . Did the runstats to observe further and today also job ran
long with similar situation (load records =0 elapse time high
on build phase)
Tablespace type is partition by range.
table type is table controlled partition
Table has 2 indexes - which allows duplicates .
One of the index type is P and other type 2
Table has 90 million records. Last REORGed in 2017. Last
runstats 6th Feb 2020.
Any suggestions what else I can check .
Manoj K Jadwani