Upgrading an Existing Data Relationship Management Application

You must update the repository information for all existing applications. You can upgrade applications from release 9.2.x, 9.3.x, and 11.1.x and copy applications from the current release.

Note:

For release-specific upgrading and copying information, see Repository Upgrade Paths for 9.2.x, 9.3.x, and 11.1.1.x, Repository Upgrade Paths for 11.1.2.0.x, and Repository Copy Paths for 11.1.2.1.

  To upgrade an existing Data Relationship Management application:

  1. Select Start, then Programs, then Oracle EPM System, then Data Relationship Management, and then Configuration Console.

  2. Select an application to upgrade or add a new application to upgrade.

    Note:

    You must update repository information for all existing applications before starting the Data Relationship Management service.

  3. On the Repository Configuration tab, click the Repository Wizard button.

  4. On the Select the Desired Repository Operation page, select these options and click Next:

    • Create a New Repository

    • Copy or Upgrade an Existing Repository

  5. On the Source Connection page, do the following:

    1. Select a database provider: Oracle or SqlServer.

    2. Enter the connection to the source repository. This is the database from which data is copied. Nothing is changed in this database.

    3. Enter a user ID and password for a user who can read from this database.

    4. Optional: Change the Connection Timeout or Command Timeout.

    5. Click Test Connection.

  6. Click Next.

  7. On the Target Connection page, do the following:

    • Select the database provider: Oracle or SqlServer.

    • Enter the connection to the target database where the upgraded repository will reside.

    • Enter the user ID and password for an administrator who has rights to create a database schema and data files.

    • Optional: Change the Connection Timeout or Command Timeout.

      Note:

      These settings are saved in the drm-config.xml and are used by the engines when they start. To perform large operations (such as a large version delete), set the Command Timeout to a larger value than the default.

    • Click Test Connection.

  8. Click Next.

  9. On the Repository Analysis screen, review and make changes to:

    • Versions –– Select the versions to upgrade; de-select versions that should not be included in the upgrade.

    • Exports –– Set up file connections, database connections, and include connections for the exports to be upgraded. You can make changes at the top of the screen for all exports or make changes to individual exports.

    • Books –– Set up pre file connections, post file connections, and combined file connections for the books to be upgraded. You can make changes at the top of the screen for all books or make changes to individual books.

    • Imports –– Set up import file connections for the import to be upgraded. You can make changes at the top of the screen for all imports or make change to individual imports.

    • Invalid Property References –– These property references are invalid and may result in unexpected behavior after upgrade.

    Note:

    For additional information on these objects and how data conversion works during upgrade, see Data Analysis and Data Conversion.

  10. Click Next.

  11. Do one of the following:

  12. On the Repository User and Data File Settings page, enter the user id and password which will be created as the schema owner for the Data Relationship Management repository.

  13. Accept the default tablespace settings or make changes and click Next.

    Note:

    It is highly recommended that dedicated tablespaces be used for Data, Indexes, Transactions, and Properties. The default tablespace names may already be in use, and will be re-used if a new tablespace name is not specified.

  14. On the Application Administrator Creation page, enter a password for the Administrator user and click Next.

    Note:

    The default Administrator user is ADMIN.

    Caution!

    If you are upgrading 11.1.2.x applications, the password for an existing ADMIN user is not overwritten with the password entered here.

  15. On the Create Repository Confirmation page, review the settings and click Next to start the creation process.

    When the database has been created a success message is displayed.

  16. Click Next.

  17. On the Copy Repository Confirmation page, review the settings and click Next to start the copy process.

    When the database has been copied a success message is displayed.

  18. Click Next.

    On the completion page, click Save Log to save the log file.

  19. On the Repository Operation Complete screen, click Finish.

    You are returned to the main screen of the console where you can review the settings.

  20. Click Save Configuration, otherwise connection information is lost when the console is closed.

For additional application configuration tasks, see: