How To Copy An OLAP Analytic Workspace (AW) From One Instance To Another Instance Using EIF Files
(Doc ID 437595.1)
Last updated on FEBRUARY 06, 2018
Applies to:Oracle OLAP - Version 10.1.0.5 and later
Information in this document applies to any platform.
This note describes how to best copy Analytic Workspaces (AW) from one system (for instance a Development system) to another system (for instance, a Production system) without modifying the original system. In general, when you migrate an entire system / instance to another server or platform, you cannot use full database export for Analytic Workspaces. This may render these objects unreadable on the new platform due to differences in internal storage structures between platforms.
The steps described in this note are aimed at creating an identical version of the Analytic Workspaces while keeping the original system operational. You can, of course, drop all OLAP-related objects (and OLAP itself) from the original system once the steps in this article are complete and verified the new system works as expected.
- Source and Target system have the OLAP option installed and operational, ie. dba_registry shows the OLAP components as VALID.
- Source and Target system need not be of the same platform
- Sufficient disk space is available to export the RDBMS schemas as well as generating EIF files.
- The target system has enough disk space to hold the dump files and EIF files as well as the schemas and AWs to be created.
Note that when migrating from a 32 bit platform to a 64 bit platforms, the size of AWs may actually grow, but in general, you should expect the AW storage requirements to be slightly smaller due to elimination
of storage marked as 'free' in the RDBMS.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!