467,212 Members | 1,186 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,212 developers. It's quick & easy.

What is the overhead for the backup compress option ?

Hi,

I get a SQL2009C when using the 'compress' option for backup, but the
util_heap_sz does not blow if I do not use the 'compress' option. What is
the overhead induced by the compress option in the BACKUP command ?

Platform: DB2 UDB V8.1 Fixpack 5 / Aix 5.1.

Thanks for your help.

Jean-Marc
Nov 12 '05 #1
  • viewed: 2146
Share:
2 Replies
Jean-Marc Blaise wrote:
Hi,

I get a SQL2009C when using the 'compress' option for backup, but the
util_heap_sz does not blow if I do not use the 'compress' option. What is
the overhead induced by the compress option in the BACKUP command ?

Platform: DB2 UDB V8.1 Fixpack 5 / Aix 5.1.

Thanks for your help.

Jean-Marc


My experience was that we had to increase the util_heap_sz by as much as 4
times when using the compress option.

This is because the backup now holds both uncompressed and compressed images
in memory (how that equates to 4x I don't understand !!!)

However, the labs told me that this problem would be fixed in Stinger, so
I'd look into getting Fixpack 7 onto your system ASAP (you should be doing
this anyway because of a couple of remote exploits in all prior versions)

HTH

Phil Nelson
ScotDB Limited
Nov 12 '05 #2
Hi Philip,

Thanks for your quick answer. I have already pushed to use FP7 :-) ... for a
migration to V8 that I have been waited for 1 1/2 year ...

Best regards,

Jean-Marc

"Philip Nelson" <te*****@scotdb.com> a crit dans le message de
news:Gm*********************@news.easynews.com...
Jean-Marc Blaise wrote:
Hi,

I get a SQL2009C when using the 'compress' option for backup, but the
util_heap_sz does not blow if I do not use the 'compress' option. What is the overhead induced by the compress option in the BACKUP command ?

Platform: DB2 UDB V8.1 Fixpack 5 / Aix 5.1.

Thanks for your help.

Jean-Marc
My experience was that we had to increase the util_heap_sz by as much as 4
times when using the compress option.

This is because the backup now holds both uncompressed and compressed

images in memory (how that equates to 4x I don't understand !!!)

However, the labs told me that this problem would be fixed in Stinger, so
I'd look into getting Fixpack 7 onto your system ASAP (you should be doing
this anyway because of a couple of remote exploits in all prior versions)

HTH

Phil Nelson
ScotDB Limited

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Tim Gahnstrom | last post: by
6 posts views Thread by Joachim Klassen | last post: by
3 posts views Thread by Stanley Sinclair | last post: by
4 posts views Thread by uthuras@hotmail.com | last post: by
1 post views Thread by kaming | last post: by
9 posts views Thread by george.zhang@lombard.ca | last post: by
5 posts views Thread by zgh1970 | last post: by
4 posts views Thread by Lennart | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.