[sknmail@rediffmail.com]

Hi,

We are in a process of migration of OTM from v5.0 to v5.5. After the Oracle software upgrade from Oracle 9i to 10G, the dbms_scheduler package has become invalid in sys schema. This is after we applied the Daylight patch on Oracle DB Software version 10.2.0.3

On creating package function dbms_scheduler.create_job gives error as "ORA-00600: internal error code, arguments: [12811], [0], [], [], [], [],".

What do you think could have wrong gone?

And finally do you think the OTM OLTP migration from 5.0 to 5.5 i.e dbupdate_55.sql and dbmigrate_55.sql or dbpatch_55.sql script can fail because of this invalid object.

I see this function being referenced in CREATE_ROD_PACKAGE once to create job and next time to ENABLE for ROD database.

Please let us know your opinion.

Thanks very much in advance

Regards,
Skn

[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

[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)

[chrisplough]

Suresh,

I'm glad to hear that you were able to move forward. Thanks for the information about the 32-bit to 64-bit Oracle upgrade -- I'm sure that it will help someone else in the community with a future migration.

Good luck and please let us know if you encounter any further issues.

--Chris