MVSFORUMS.com

grimpeur · Beginner Joined: 10 Jul 2006 Posts: 16 Topics: 5

Hi,
I have a number of partitioned tablespaces which are updated via S/I/U/D
rather than utility loads.
Because of this, when data trips into the next partition, compression is not activated automatically (a re-org is required to do this) increasing the staorage required and increasing the chance of update job fails.
Is there any way of ensuring that compression is activated automatically? Or if not, an easy way of identifying when data has reached a new partition (I have numerous tablespaces with this scenario).
Thanks.

dbzTHEdinosauer · Posted: Mon Jan 15, 2007 10:15 am Post subject:

couple of links:
the-incredible-shrinking-data-db2s-compression-part-i-10568

db2-data-compression-part-ii-the-saga-continues-10921

b2-data-compression-part-iii-the-conclusion-11100

techtarget.com/eac/knowledgebaseAnswer

here is a link to DB2 document concerning compression:

http://www.redbooks.ibm.com/abstracts/sg245261.html?Open

your problem is DB2 v7, need to either upgrade to 8 or think about reducing which tables are COMPRESS=YES.
_________________
Dick Brenholtz
American living in Varel, Germany

grimpeur · Beginner Joined: 10 Jul 2006 Posts: 16 Topics: 5

OK, thanks for that.

dbzTHEdinosauer · Posted: Tue Jan 16, 2007 10:05 am Post subject:

You know when you are 'tripping' into a new partition, because the original INSERT
received an SQLCODE -904, and SQLERRD(1,2,3,4,5,or 6) = 00C9009C or 00C9009D or 00D70014. Which means programatically (or thru triggers) the user (not DB2) must provide a new partition number.

and

COMPRESS is not something you turn on or off during the application program. This is something the DBA's need to do with either original Table definition or thru alters.

I gave you the links so that you would see that your original question made no sense and I thought you might learn something.
_________________
Dick Brenholtz
American living in Varel, Germany