IDM/OID upgrade assistant (UA) failed in the examination - on 11.1.1.2

Question

Does anyone have problem upgrading Oracle Identity Management/OID from 10.1.2.3 to 11.1.1.2 on Linux SUSE-10 64-bit?.
1. Upgrade Oracle seed DB 10.1.0.5 32-bit to 10.2.0.4 64-bit. Using DBUA - OK, no problem.
2. Started As 10.1.2.3 Infrastucture - IDM/OID/Metadata Repository and Middle Tier - Portal/Forms/Reports/Discoverers - OK, No problem.
3. Installed Weblogic 10.3.2 - OK, No problem.
4. Installed NEW 11.1.1.2 IDM/OID components OID and DIP only - OK, No problem.
5. Run ua (upgrade assistant) to upgrade OID to 11.1.1.2 and got error - Examination OID failed. UA stopped.
Installed 64-bit Fusion Middleware IDM/OID - Probably this is the problem?.
Have not tried the 32-bit Fusion Middleware IDM/OID yet.
Had a SR opened with Oracle Support and have no solution yet.
Follow the instructions from:
Oracle® Fusion Middleware Upgrade Guide for Oracle Identity Management
11g Release 1 (11.1.1)
Part Number E10129-02
***** Error in OID oidctl.log *****
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: Session ID = 540
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: OracleProcess ID = 16253
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: WARNING: Connected to incorrect OID base schema version, (version=10.1.2.3.0).
WARNING: OID server (version 11.1.1.2.0) is now operating in read_only mode
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: WARNING: Connected to incorrect OID base schema version, (version=OID 10.1.2.3.0).
WARNING: OID (version 11.1.1.2.0) is now operating in read_only mode
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:15:34+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:15:44+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:15:54+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:04+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:14+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:34+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:44+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:54+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
***********************************************************************************

Answer 1

Hi Milan,
take a look to "Oracle Database Data Cartridge Developer's Guide" [http://docs.oracle.com/cd/E11882_01/appdev.112/e10765/dom_idx.htm#autoId50] (here is the 11g rel2 version but is the same with 9i)
Domain Indexes and SQLLoader*
SQLLoader conventional path loads and direct path loads are supported for tables on which domain indexes are defined, with two limitations:
-The table must be heap-organized.
+-The domain index cannot be defined on a LOB column.+
To do a direct path load on a domain index defined on an IOT or on a LOB column, perform these tasks:
-Drop the domain index
-Do the direct path load in SQL*Loader.
-Re-create the domain indexes.
doesn't seem to be possible to use "direct path method" with spatial (domain) indexes
i hope for you that there is a workaround ...
good luck,
CarlT