When checking for new known issues with 10.2.0.3 patchset on Metalink I discovered that an upgrade problem was added - Metalink Note 401435.1.

The issue affects all 64 platforms especially when database is upgraded from any previous 32 bit release. So far there are no one-off patch and no workaround except… well, use Data Pump or exp/imp. Typical, “workaround” approach from Oracle. In my last post about 10.2.0.3 issues I mentioned Veritas bug (now fixed with one-off), for which Oracle proposed moving files to non-Veritas storage. Do they think that companies using Veritas do it just for fun of spending an awful lot amount of money? Well, some might do but I digress.

Here is the number of useful Metalink notes if you are interested:

• Bug 5520937 - Upgrade to 10.2.0.3 can fail with ORA-600 [22635]
• Alert - ORA-600 [22635] and ORA-600 [KOKEIIX1] Reported While Upgrading Or Patching Databases To 10.2.0.3
• Ora-600[22635] While Upgrading Database From 10.2.0.2 To 10.2.0.3
• Bug 5748280 - ORA-600 [KOKEIIX1], ORA-600 [22635] WHEN APPLYING 10.2.0.3 PATCHSET
• Bug 5755471 - ORA-00600 [22635], AT SYS.UPGRADE_SYSTEM_TYPES_FROM_920 DURING UPGRADE

You did not forget to test you backups, eh?

Update: Metalink Note 412271.1 was updated with much more details since I posted this entry and patches 5871314 and 5892355 are available. Note that the problem is there any change of bits 32->64 or 64->32 and even if change occurred before 10.2.0.3 patched. See note 412271.1 for more details.