User Guide

Back Up Native Directory and Hyperion Product Repositories
After migrating users and groups to use the new identity attribute, you cannot revert to the
previously used identity attribute. Before starting the migration, create backups of Native
Directory database and the Hyperion product databases that store user and group information.
● Native Directory repository
● Shared Services repository
● Essbase (security file)
● Oracle's Hyperion® Planning – System 9 repository
● Oracle's Hyperion® Financial Management – System 9 repository
● Oracle's Hyperion® Reporting and Analysis – System 9 repository
Migration Sequence
Before migrating to the unique identity attribute, run the Update Native Directory Utility if
Native Directorycontain stale data. See Chapter 9, “Using the Update Native Directory Utility
to Clean Stale Native Directory Data.”
Begin by migrating Shared Services users and groups to the unique identity attribute. If you use
Essbase and Planning, migrate Essbase users and groups, and then migrate Planning users and
groups.
You can migrate Financial Management and Reporting and Analysis users and groups anytime
after migrating Shared Services users and groups.
See “Product-Specific Updates” on page 128 for more information.
Behavior During Migration
After you migrate Shared Services users and groups to the unique identity attribute,Hyperion
products stop working until the user and group information contained in product-specific
repositories is updated to reflect the unique identity attribute.
Shared Services and Hyperion product migration to the unique identity attribute can take
considerable time, depending on the number of users and groups involved. Because Hyperion
products will not be available during this time, Hyperion recommends that you schedule in a
way that minimizes downtime.
Important Considerations When Using the Unique Identity Attribute
● The unique identity attribute can be set only for MSAD and other LDAP-enabled user
directories.
● For migration to work, all similar user directories configured on Shared Services must be
migrated to the new unique identity attribute. All MSAD user directory configurations must
be updated with the unique identity attribute before Shared Services can migrate MSAD
users and groups to the new attribute. Similarly, the configuration of all LDAP-enabled user
Using the Unique Identity Attribute to Handle Inter-OU Moves in LDAP-Enabled User Directories
39