[chrisplough]

Hello Skn,

We're running through several v5.5 migrations for clients right now and have seen similar issues.

What we've found is that several OTM packages can become invalid after the upgrade from 9iR2 (9.2.0.x) to 10gR2 (10.2.0.3) -- though we've been able to reduce the number of invalid objects by ensuring that the OTM database has been upgraded to 9.2.0.8 prior to the upgrade to 10.2.0.3.

If this doesn't resolve it, the best advice I can give you is to run through the remaining OTM migration scripts (dbupdate_55.sql, ./update_content.sh, dbmigrate_55.sql, and dbpatch_55.sql); as the remaining packages we had issues with here recompiled and valid by the end of the process.

On another note, prior to your PROD migration, I highly recommend completing 3 test migrations, to ensure the process will run smoothly, you have all workarounds / fixes documented and your team is prepped and ready to go.

Hope this helps,
--Chris