Currenty I am implementing table-partitioning for my client (v9.5.2a on win2003-64) for some tables.
One big table contains mutation(history) and I give it 1 dedicated partition/tablespace a year.
Nice to mention:
- each tablespace get ist own dedicated compress-dictionary
Code:
2009-02-09-08.51.39.802000+000 E296878442F561 LEVEL: Warning
PID : 3108 TID : 1508 PROC : db2syscs.exe
INSTANCE: NODE : 000 DB :
APPHDL : 0-10734 APPID: *LOCAL.xxx.090205112818
AUTHID : ADMIND.....
EDUID : 1508 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities, sqluDoPhysicalConsistencyPt, probe:1943
MESSAGE : ADM5592I A compression dictionary was built and inserted into object
"4" in tablespace "65" via "LOAD" processing.
2009-02-09-08.51.39.817000+000 E296879005F561 LEVEL: Warning
PID : 3108 TID : 1508 PROC : db2syscs.exe
INSTANCE: NODE : 000 DB :
APPHDL : 0-10734 APPID: *LOCAL.xxx.090205112818
AUTHID : ADMIND....
EDUID : 1508 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities, sqluDoPhysicalConsistencyPt, probe:1943
MESSAGE : ADM5592I A compression dictionary was built and inserted into object
"4" in tablespace "66" via "LOAD" processing.
- using "db2top" you monitor very nice which "partition" is access right now.
Question:
It would be nice to reorg only the 2009 part of my table. I could "rollout" to a separate table, reorg that and roll back in again, but during that time I do not have a consistent table available. Is there a better way (coming)?
dBforums
>
to reorg 1 partition
02-09-09, 05:10
Linear Mode
