OIM 11gR2: Schema Backup and Restoration using Data Pump Client Utility
(Doc ID 1492129.1)
Last updated on OCTOBER 23, 2019
Applies to:Identity Manager - Version 188.8.131.52.0 to 184.108.40.206.9 [Release 11g]
Information in this document applies to any platform.
The Database Layer (OIM and its dependent Schemas) are an integral part of the OIM Application Infrastructure.
This document intends to provide for a Step-By-Step process in detail for the Logical Backup and Restoration of the OIM Application Schema(s) particularly focusing on the OIM 11g R2 Database Schema Topology using Oracle’s Data Pump utility.
What this Technical Note covers
A) Backup of OIM 11g R2 and its dependant Schemas of a running deployment.
B) Restoration from scratch on a different1/same database instance.
C) The methodology depicted is not intended for a Production level Backup Restoration and Recovery solution for an enterprise customer deployment.
1 - a different instance on the same or on a different physical machine.
What this Technical Note does not cover
A) Backup/Restoration methodology for the OIM 11g Upgrade environments
B) Backup/Restoration methodology for T2P scenarios.
Similar Oracle Support Tech-note published for OIM 11gR1/PS1 Schemas (Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g R1/PS1]) is available at support.oracle.com as “OIM 11gR1: Schema Backup and Restoration using Data Pump Client Utility ( <Document 1359656.1> )”
Oracle Identity Manager 11g R2 Database Schemas
From the operational perspective, OIM 11g R2 Database Schema topology consists of the following FIVE mandatory schemas:
a) Oracle Identity Manager (OIM) Schema [OIM 11gR2]
b) Meta Data Service (MDS) Schema
c) Service Oriented Architecture (SOAINFRA) Infra and ORASDPM Schema
d) Oracle Platform Security Services (OPSS) Schema
OIM 11gR2 Database Backup and Restoration
Logical Backup of OIM Schema
For the Logical Backup of OIM 11g Schema(s) (and its subsequent Restoration) the recommended tool is Oracle11g R1/R2 Data Pump Export Utility.
Restoration of OIM Schema
For the restoration of the Logical Backup (taken using the Oracle 11g/10g Data Pump Export utility), the corresponding utility i.e. the Data Pump Import utility is to be essentially used.
Following are the possible scenarios of restoration based on the location of restore:
a) Local restoration [Restoration in the same Database Instance post Schema drop]
b) Remote restoration [Restoration in a different Database Instance]
Data Pump is a tool of choice over conventional export/import utility as it not only provides a platform independent data dump but also by way of its architectural enhancements it is faster.
Data Pump command line clients are available out-of-the-box with Oracle Database Client/Server (Oracle DB 10g and onwards) with no additional licensing cost.
NOTE –Check for the compatibility of the Data Pump Client wrt to the Target Database in use.
Compatibility between the DB version and the Data Pump Client:
A newer version of Data Pump Client cannot be used in order to export data from a lower database version.
For example to export data from database version 10.2.0.3 or 9.2 the 22.214.171.124 Data Pump Client would not suffice.
Remote Restoration Vs Local Restoration
Steps for restoration on Local or Remote DB Instances are same almost the same except for:
a) In Remote Restoration; schemas are imported in a different database instance (which can be on a different machine as well).This Database may or may not have any prior OIM 11g Schemas or even any FMW Schema created on it, depending on this some additional steps may be required.
b) In the case of Remote DB restoration, the JDBC connection information is to be modified as per the steps in the section ‘OIM 11gR2 mid-tier side JDBC Connection configuration’.
What has changed for the Logical Export/Import in OIM 11g R2 Schema(s)
a) In the case of export/import of dependent schemas
- There is a new dependent schema OPSS introduced in OIM 11gR2.
- MDS has introduced VPD based access policies for few tables.
- SOAINFRA has a new DBMS_AQ job.
b) On the OIM side in 11gR2, Catalog and ADF features have introduced three DBMS SCHEDULER JOBS in the Database
Generic High Level steps in Logical Export of OIM 11g R2 Schema(s)
Order of Export of OIM, MDS, SOAINFRA, ORASDPM, and OPSS Schemas does not matter from the OIM 11g R2 Application functionality perspective.
What to retain along with the exported data dump:
For ease of subsequent restoration, following details are to be retained for later reference along with the OIM export dump:
- Name of the OIM/dependent Schemas
- Default and Temporary Tablespace names of OIM/its dependant schemas, along with names of any other tablespaces involved in OIM/other Schema objects.
- Data Pump/Conventional Export log file
Generic High Level steps in Logical Import of OIM 11g R2 Schema(s)
Steps 2) and 4) can be skipped if restoring on the same DB Instance (using the same schema names).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Oracle Identity Manager 11g R2 Database Schemas|
|OIM 11gR2 Database Backup and Restoration|
|Logical Backup of OIM Schema|
|Restoration of OIM Schema|
|Remote Restoration Vs Local Restoration|
|What has changed for the Logical Export/Import in OIM 11g R2 Schema(s)|
|Generic High Level steps in Logical Export of OIM 11g R2 Schema(s)|
|Generic High Level steps in Logical Import of OIM 11g R2 Schema(s)|
|Detailed Steps for Export of OIM 11g R2 Schema(s)|
|Data Pump Export|
|Detailed Steps for Restoration of OIM Schema(s)|
|Data Pump Import|
|OIM 11gR2 mid-tier side JDBC Connection configuration|
|Data Source Configuration editing|
|MBean Configuration changes|