Re: Table with 300 columns (ie > 255) : Row Chaining ?

> I didn't know that. Also, the splilt at the 96th column was the
> surprise. Why 96 ?

Your test table has 350 columns. A row piece can store at most 255 columns. As a result, you have two row pieces: one with 255 columns and another with 95 (350-255) columns. As I wrote in my previous reply, the pieces are split and stored in "reverse order". That means two things: 1) the first row piece is the one having 95 columns 2) the first row piece is stored after the second one.

> What if the table has 250 columns ? Then it is a single row piece
> without a split ?

If it fits in a single block and it is not subject to row migration, it is stored in a single piece.

HTH
Chris Antognini

Troubleshooting Oracle Performance, Apress 2008 http://top.antognini.ch

--
http://www.freelists.org/webpage/oracle-l