Re: Tested 11g OLTP compression and found rather serious issue
From: Mark D Powell <Mark.Powell_at_eds.com>
Date: Fri, 31 Jul 2009 06:46:37 -0700 (PDT)
Message-ID: <77469bb1-50d0-4854-9771-bb24aa6e6baf_at_n11g2000yqb.googlegroups.com>
On Jul 31, 5:02 am, "Tamkat..._at_gmail.com" <tamkat..._at_gmail.com> wrote:
> Oh, I forgot this important info, regret :
>
> SQL> select * from v$version;
>
> BANNER
> --------------------------------------------------------------------------------
> Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
> PL/SQL Release 11.1.0.7.0 - Production
> CORE 11.1.0.7.0 Production
> TNS for 32-bit Windows: Version 11.1.0.7.0 - Production
> NLSRTL Version 11.1.0.7.0 - Production
>
> - Kenneth Koenraadt
Date: Fri, 31 Jul 2009 06:46:37 -0700 (PDT)
Message-ID: <77469bb1-50d0-4854-9771-bb24aa6e6baf_at_n11g2000yqb.googlegroups.com>
On Jul 31, 5:02 am, "Tamkat..._at_gmail.com" <tamkat..._at_gmail.com> wrote:
> Oh, I forgot this important info, regret :
>
> SQL> select * from v$version;
>
> BANNER
> --------------------------------------------------------------------------------
> Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
> PL/SQL Release 11.1.0.7.0 - Production
> CORE 11.1.0.7.0 Production
> TNS for 32-bit Windows: Version 11.1.0.7.0 - Production
> NLSRTL Version 11.1.0.7.0 - Production
>
> - Kenneth Koenraadt
Ken, I do not know how table compression works on 11g but when first introduced if you updated a row in a compressed table Oracle stored the updated row back in uncompressed format. Compression was suggested for tables what had little to no update activity. Your results could be partially due to migrated rows if no enhancement to recompress the row was not added in 11g.
Interested in any updates you come up with.
HTH -- Mark D Powell -- Received on Fri Jul 31 2009 - 08:46:37 CDT