Loss Of Database Connection Information During DRM Metadata Extract And Load
Last updated on JULY 28, 2017
Applies to:Hyperion Data Relationship Management - Version 126.96.36.199.344 and later
Information in this document applies to any platform.
Migration extract/load is working as designed. Connection String and Username are not meant to be migrated.
Connection string is an encrypted value and may include host, username, and password information embedded. While this field could be extracted and loaded as encrypted, there's another issue with allowing these fields to be migrated.
Typically, migration pushes from one system to another would "require" that external connections use different configuration settings. If we load in a group of external connections (say from QE to PROD), the customer may accidentally export information to the wrong system. By not loading in connection-string, username, and password, we force the customer to supply valid information for the external connections in the post-migration system.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms