OIM 11gR1: Schema Backup and Restoration using Data Pump Client Utility (Doc ID 1359656.1)

Last updated on SEPTEMBER 01, 2023

Applies to:

Identity Manager - Version 11.1.1.3.0 to 11.1.1.5.0 [Release 11g]
Information in this document applies to any platform.

Purpose

Overview

The Database Layer (OIM and its dependent Schemas) are an integral part of the OIM Application Infrastructure.
Backup and Restoration of the OIM Schema(s) is a vital activity during the lifecycle of the application even in non-production environments (like Development, QA etc).
This document intends to provide for steps in detail for the Logical Backup and Restoration of the OIM Application Schema(s) in a non-production and non-enterprise environment using the Oracle Databaseâs Data Pump utility.
The content covered in the subsequent section does not apply to a Production level Backup Restoration and Recovery solution.

Oracle Identity Manager 11g (11.1.1.3.x i.e. DW/11.1.1.5.x i.e. PS1) Database Schemas

From the operational perspective, OIM 11g Database layer consists of the following three mandatory schemas:
a) Oracle Identity Manager (OIM) Schema
b) Meta Data Service (MDS) Schema
c) Service Oriented Architecture (SOAINFRA) Infra Schema and ORASDPM Schema

OIM 11g Database Backup and Restoration

Logical Backup of OIM Schema

OIM 11g Schema(s) Logical Backup can as such be taken through any of the standard backup methods available in Oracle RDBMS. However the recommended tool for Logical Backup (and its subsequent Restoration) 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 the Data Pump Import utility is to be used.
Following are the possible scenarios of restoration based on the location of restore:

a) Local restoration [Restoration in the same Database Instance]
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 11.1.0.7 Data Pump Client would not suffice.

2) Dont't use the exp utility to export as it doesn't work properly and its seen that export will fail to export the SOAINFRA schema correctly, it will fail with "EXP-00107: Feature (BINARY XML) of column USER_PROP in table DEV_SOAINFRA.EDN_EVENT_QUEUE_TABLE is not supported. The table will not be exported.

Steps for both Local and Remote Restoration are almost the same, except for that in Remote Restoration; schemas are imported in a different database instance (which can be on a different machine).
In that case JDBC connection information is to be modified as per the steps in the section OIM Application side JDBC Connection configuration.

Generic High Level steps in Logical Export of OIM Schema(s)

NOTE: Order of Export of OIM, MDS, and SOAINFRA, ORASDPM Schemas does not matter from the OIM Application functionality perspective.

What to retain along with the dump for ease of restoration

Following details should be kept for reference along with the OIM export dump:
â¢ Name of the OIM/dependent Schemas
â¢ Default, temporary tablespace name of OIM/dependant Schemas, along with names of any other tablespaces involved in OIM/other Schema objects
â¢ Data Pump/Conventional Export log file.