This content has been marked as final. Show 5 replies
I am also in the same process and following the guide' http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm'.
One would be required to upgrade the connector after upgrading from 10g to 11g. Following above ugprade guide will not ugprade the connector version.
If you perform upgrade OIM to 11g, you have to redefine the connectors which will still be in 10g versions and these connectors will not be upgraded to 11g. But if you go for migration you can install the latest version of available connectors and run the target recon to link user accounts.
OIM 11g migration question
It's always better to have another environment with 11g database and import 9i schema into current database. OIM 11g will work on 9i repository upgrade as well but it may cause issue later.
All your data, configurations and files under xellerate directory are migrated. Once connector is installed it's nothing but combination of components like resource objects, process definitions, forms etc. They all are upgraded to 11g. Whatever jar file are there, they moved to OIMHOME_JARS table and they remain same i.e. 9i APIs only. This may cause issues later. Form versions remain same.
If you go with the path for target reconciliation of user resource profile and new environment path. The historical data like profile history will not be then ported from older to new OIM, In that case how do we go about achieving it.
Followed the repository upgrade path and re implemented the connectors as the connectors were not upgradable to 11g targets.