Move EBS 12.1.3 Vision from Win Server 2003 (DB 11.1.0.3 32-bit) to Win Server 2008 R2 (DB 11.2.0.4 64-bit)

Oracle EBS 12.1.3 Vision environment was migrated from Windows Server 2003 32-bit (DB 11.1.0.3 32-bit) to Windows Server 2008 R2 64-bit (DB 11.2.0.4 64-bit). 

These metalink docs provide very much information of what this migration needs:

1188535.1 - Oracle E-Business Suite R12 to Microsoft Windows Server 2008 R2

1058763.1 - Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2

387859.1 - Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12

414992.1 - Using Cygwin to Maintain Oracle E-Business Suite Release 12 on Windows

In essence, the migration process can be broken down into these steps:

1. Apply all necessary patches in Win2k3 environment.  Run adpreclone on both tiers
2. Prepare the Windows 2k8 R2 environment for EBS use (cygwin, Visual Studio)
3. Move both Apps and DB Tiers from Win2k3 to Win2k8.  Use the same directory structures
4. Run adcfgclone on DB Tier, and then on Apps Tier
5. Install database 11.2.0.4 64bit.  Apply the latest DB RUP patch
6. Run DBUA to upgrade the database from 11.1.0.3 32-bit to 11.2.0.4 64-bit
7. Prepare the new Oracle Home for EBS use (init params, perl library, appsutil folder, 64 bit jre, etc). 
8. Run adconfig on the new DB Tier

To save time, I did not run the "recompile objects" during the upgrade.  When the system was running fine after all steps had done, I run the "invalid everything, then recompile everything" script – ultirp.sql and ultrp.sql script.  However, I got this error (similar to this):

Encounter ORA-07445: exception encountered : core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x5A1113A] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ]

This error made the session became disconnect, core dump and generated all kinds of debug and trace files.

The same error occurred if I ran adadmin -> validate APPS schema. Even worst is that it happened when applying any patch which required compile invalid objects.

Reviewing the invalid objects (about 1k left), and manually recompiled them batch by batch.  Finally I was able to pinpoint what objects gave this error -- database Views which have name started with ZPB.

And yes…it's typical RTFM problem.  I should pay more attention to the doc 1058763.1which explicit said:

The following EBS products are currently not supported with E-Business Suite 
Release 12 on Oracle Database 11g Release 2 (11.2.0):

•       Oracle Enterprise Data Warehouse (EDW)

•       Oracle Enterprise Planning and Budgeting (EPB)

So I dropped all those invalid ZPB views and utlrp.sql can be completed without issue now.

The REAL root cause is – OLAP in 32-bit database does not migrate to 64-bit database directly, as stated in doc 352784.1 – "Cannot Open Business Area After Upgrade of Database From 32-bit to 64-bit, Error "ORA-33272: Analytic workspace ZPB.ZPBCODE cannot be opened".