[sknmail@rediffmail.com]

Hi Chris,

Thanks very much for those different suggestions you have provided. However we took an easy step of restarting the entire process again since this was a devel environment.

However Chris, on Metalink there is mention of this error as a part of upgrade from Oracle 9i to 10g, however it says there is a chance that Oracle 9i was installed using a 32bit architecture, while upgrade to Oracle 10g was done using 64bit archi. or viceversa.

Moreover when we encountered this error, we found that none of the OTM packages were invalid in Glogowner and Reportowner. Only sys.dbms_scheduler package was in invalid state. As you said we could have gone further and performed the 5.5 migration, however we wanted to be sure that it not causing a major issue and also we were clear we will require this package later.

Anyhow when I write this reply, we are done with the Oracle 10g (10.2.0.3) database upgrade. Now going to run the 5.5 migration scripts.

Thanks very much Chris.

Warm Regards,
Suresh (Skn)