Re: Select into or create <table> as & LONG datatypes - what to do?

Is it chaining or is it migration?

Storage clauses won't fix up row chaining (and I'd be concerned that with a long raw in the picture, we are talking about real row chaining, not mere migration). Chaining's simply an inidication that the block size is too small -and block size can't be fixed unless you re-create the entire database.

I suppose the acid test is this: export, truncate the table, and import with ignore=y. Analyze for statistics, and if the problem has gone away, it was migration. If it hasn't, it was chaining. (Incidentally, truncate rather than drop, otherwise, the table created after the import is a new table, with a new object ID, to which prior redo cannot be applied).

Regards
HJR "The Ghost" <The_at_Ghost.com> wrote in message news:L4br6.21398$p66.7388505_at_news3.rdc1.on.home.com...
>
> Export and import the entire table.
> Use proper storage clauses.
>
>
> "Glen A. Sromquist" <stromqgl_at_alpac.ca> wrote in message
> news:FHar6.10379$Lm2.1287744_at_news0.telusplanet.net...
> > I am trying to correct a table with a high number of chained rows, so
 I've
> > ran the UTLCHAIN script, analyze <table> list chained rows into
> > chained_rows, now I want to insert the chained rows from table_a into a
 temp
> > table by using:
> >
> > create table table_a_chained
> > as select * from table_ a
> > where rownum in (select head_rownum from chained_rows
> > where table_name = 'table_a')
> >
> > Then delete the rows from table_a and re-insert them from the temp
 table.
> >
> > unfortunatly one of the columns in table_a is a LONG RAW datatype and it
> > wont allow this.
> >
> >
> > Can I work around this?
> >
> >
> > thanks in advance...
> >
> >
>
>
Received on Tue Mar 13 2001 - 05:36:59 CST