RE: Lost one in Migration

I was told by Oracel Support to just change the compatible setting and then
the ananlyst said "Oops' when it didn't work. I couldn't continue it took
about a week to get it back. No one knew what to do. They all said "That
isn't good!" We had already dismantled the old servers (32 bit) and
reconfigured the new 64 bit servers we had to get a workaround to make the
old version (8.0.6.3) work so we could do another recovery and try again.
That trace that they say works to overcome the problem doesn't work. If
you can do a restore back to the 8.1.7 version you can just take out the
compatible parameter and try again. If not, you may be in for a long haul.

HPUX
Going from 8.1.7.4 to 9.2.0.4.
I and another DBA have just about exhausted our things to try.

I had a compatible='9.2.0' in the init.ora for the 9i migration. You
can't do this, but must set it AFTER the migration. I had obtained a
copy of the init.ora from a working Version 9 and went over the lines
one by one comparing them to "PFTST" to make the version 9 init.ora.

Now I get the stuff below. I've tried using:
_allow_resetlogs_corruption=TRUE
EVENT = "10619 trace name context forever, level 1"
Both of which were mentioned as ways to get around the problem.

The information transmitted is intended solely
for the individual or entity to which it is
addressed and may contain confidential and/or
privileged material. Any review, retransmission,
dissemination or other use of or taking action
in reliance upon this information by persons or
entities other than the intended recipient is
prohibited. If you have received this email in
error please contact the sender and delete the
material from any computer. [ST:A234]