Re: Table with ~255+ columns
Date: Tue, 17 Nov 2020 10:48:27 +0000
Message-ID: <CAGtsp8kQ291GXPnsB=6-cwL_CaJy-K79z5KGXSdy50rEqQ6-gA_at_mail.gmail.com>
I got curious because the parameter name sounded interesting, so I did a
google search.
The first hit was an article I'd written 11 years ago where I'd mentioned
it in a comment: https://jonathanlewis.wordpress.com/2011/12/16/i-wish-3/
Regards
Jonathan Lewis
On Mon, 16 Nov 2020 at 21:34, Kenny Payton <k3nnyp_at_gmail.com> wrote:
> Do some research on _rowlen_for_chaining_threshold hidden parameter and
> associated bug/notes. Depending on your use case it might help with the
> physical reads associated with “table fetch continued row” events. I’ve
> had some success with it in my distant past. I have also used a process
> that used "analyze table list chained rows into …” to identify problematic
> rows, back them up into a separate table, delete the rows and reinsert them
> with the hidden parameter to get the multiple row pieces into single
> blocks. This is useful when the chaining is being caused by row updates.
>
> Kenny
>
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Nov 17 2020 - 11:48:27 CET