MDS Customizations are Removed After You Restart the OIM Managed Server of an Upgraded Setup
If any MDS customizations are done after a successful upgrade to 12c (12.2.1.3.0) and if those customizations are lost after you restart the OIM Managed Server, you cannot recover the MDS changes. You have to do the MDS customizations again.
To avoid the repeated occurrence of this issue each time you restart the
Managed Server, replace the existing 12c (12.2.1.3.0)_ORACLE_HOME>/idm/server/apps/oim.ear/metadata.tar
file
with the file that is present at the same location after you install the 12c (12.2.1.3.0) binaries, prior to the upgrade.
Note:
This issue is applicable only for MDS customizations that were made after the successful upgrade to 12c but lost after restarting the OIM Managed Server.As part of the pre-upgrade tasks, after installing the 12c (12.2.1.3.0) binaries, you would have already taken a backup of the
original 12c (12.2.1.3.0)_ORACLE_HOME>/idm/server/apps/oim.ear/metadata.tar
file. See Backing Up the metadata.mar File Manually.
If the backup of the original file is not present after you install the binaries, you should install the 12c (12.2.1.3.0) binaries at any temporary location and extract the file.
For a HA setup, the original 12c (12.2.1.3.0)_ORACLE_HOME>/idm/server/apps/oim.ear/metadata.tar
file
is present on the secondary nodes where upgrade bootstrap was not executed.
Parent topic: Troubleshooting the Oracle Identity Manager Upgrade