RE: Chained vs. migrated rows - Any easy way to tell the difference?

Joel,

Regarding "ORA-01495: specified chain row table not found", a systematic way to troubleshoot this type of problem is to enable SQL trace:

alter session set events '10046 trace name context forever, level 4'

followed by your analyze list chained rows. The trace file will show you exactly where it goes wrong. If the trace file doesn't show or doesn't show enough recursive SQLs, flush shared pool and try again. If you absolutely cannot flush shared pool, try some "harmless" DDL on the table and recreate the chained_rows table that you think is used to get the recursive SQLs out of dictionary cache.

Yong Huang       

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