RE: OLTP compression slow update
Date: Wed, 26 Dec 2012 14:55:34 -0500
Message-ID: <C95D75DD2E01DD4D81124D104D317ACA23212A1165_at_JAXMSG01.crowley.com>
Its been awhile, so just to make sure -- I believe runstats is best served on a database which has no-one else doing business -- like if you could fit it on your laptop, or after hours. Not even sure if multiple databases on the same server can serve to skew the results depending on what you are going for.
The reason being is that every session is contributing to the numbers -- like enqueues, latches, mutexes, or runtime.
Joel Patterson
Database Administrator
904 727-2546
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Michael Dinh
Sent: Tuesday, December 25, 2012 12:02 PM
To: Jared Still
Cc: oracle-l
Subject: Re: OLTP compression slow update
Thanks Jared.
Think we got bit by marketing bug. Back to basic and it does not get any easier than that.
CREATE TABLE md_fct_oltp PCTFREE 20 COMPRESS FOR OLTP AS SELECT Elapsed: 00:19:38.28
CREATE TABLE md_fct_nocp PCTFREE 20 AS SELECT Elapsed: 00:04:40.25
runstat here I come.
On Tue, Dec 25, 2012 at 8:34 AM, Jared Still <jkstill_at_gmail.com> wrote:
>
> On Mon, Dec 24, 2012 at 8:52 PM, Michael Dinh <mdinh235_at_gmail.com> wrote:
>
>> Hello,
>> Does anyone have any experience with updating compressed table?
>>
>> The only difference between 2 tables is no compression vs OLTP
>> compression.
>>
>> PL/SQL using FOR loop updating 1 row and a time and commit every
>> 10,000 rows.
>>
>
> Michael,
>
> This would be an excellent opportunity to use Tom Kyte's
> runstats<http://appsdba.com/techinfo/runstats.htm>
> ( modified version and original both available there)
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog:
> http://jkstill.blogspot.com Home Page: http://jaredstill.com
>
>
>
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Wed Dec 26 2012 - 20:55:34 CET