Search This Blog

Tuesday, June 14, 2011

Upgrading from DRM 11.1.2.0.1 to 11.1.2.1

Steps for the upgrade:

  1. Assumption : That there exists a successful 11.1.2.0.1 installation.
  2. Software downloaded for the 11.1.2.1 upgrade (on edelivery.oracle.com)
  3. Backup the DRM Repository database for the 11.1.2.0.1 version
  4. Un-install DRM 11.1.2.0.1 (This does not drop the DRM Metadata repository, or the DRM Console database settings)
  5. Un-zip and Run the setup to install 11.1.2.1
  6. Ensure that the application configuration and database connection information are still correct as the in 11.1.2.0.1.
  7. IMPORTANT NOTE: Since this is an upgrade to a newer version, the following action is mandatory to update the metadata tables to reflect the new features and functionality of the Oracle tool
    • Open the DRM Console 11.1.2.1
    • Under Applications, click on Apply updates (This process will apply updates to the current application)
   Note: Oracle DRM 11.1.2 was not supported on Windows Server 2008. However 11.1.2.1 is, it is the recommended OS base for a DRM install. Ensure that a 64bit OS is used on either 11.1.2 or 11.1.2.1. Even if the memory is bumped up to 64GB its a gotcha if the product is used on a 32bit OS, not all the memory is utilized ~50% or less of the memory will be utilized.

Other requirements for a clean installation of Oracle DRM Fusion edition: 

  1. Application Server: Windows Server 2003 R2. (For non-production environments the Oracle DRM server can also be successfully installed on Vista, XP, Windows 7)
  2. IIS 6 or IIS 7 is installed and running. 
  3. ASP.Net 2 and Microsoft .Net Framework 3.5  (Note: Ensure that SP1 has been installed and IIS is configured to use ASP.Net 2.)
  4. A relational database for the DRM Metadata tables. (Oracle documentation indicates DRM is supporte d on Oracle and SQL Server RDBMS). These tutorials are demonstrated on a Oracle 11g repository.
  5. Ensure that Oracle 11g(run as admin)Client has been installed on the App-Server and configured with appropriate TNSNAMES.ORA entries. Note: Typically in a live environment, the Database resides on a seperate server and not on the App-server. (For a local personal installation, the database and DRM can be installed on the same machine and a TNSNAMES.ORA entry is not necessary in this case)
  6. Ensure that the connection between the DRM application server and database has been validated using the same credentials
  7. A Windows User has been created having credentials to:
    • Edit registry settings
    • Read and write to the local file system
    • Launch processes
    • Run as a service
For the purpose of these tutorials, the Oracle DRM Fusion edition is installed based on Internal authentication. External authentication requires Shared Services and will be out of scope

For additional information please refer to the Oracle® Hyperion Data Relationship Management, Fusion Edition Installation guide.
http://download.oracle.com/docs/cd/E17236_01/nav/portal_1.htm
Posted by at

6 comments:

  1. AnonymousJune 21, 2011 at 6:04 PM

    Is the Oracle Client needed for the migration utility? or just to have DRM connect to its backend? I have a client installed on my 11.1.2.1.101 installation but don't have a TNSNAMES.ORA and DRM works fine. Any ideas? I thought it might using thin OCI drivers that it ships with or something. Thanks

    ReplyDelete
  2. GeetaJune 21, 2011 at 10:27 PM

    TNSNAMES.ORA is needed on a Windows App Server that hosts DRM and the Oracle DB that holds the DRM metadata repository is on a seperate server. If you have the Oracle DB and DRM installed on the same machine a TNSNAMES.ORA file is not required locally. Connectivity occurs via OCI in this case.

    ReplyDelete
  3. VineetOctober 24, 2011 at 8:34 PM

    Hi Geeta,

    Thanks a lot for your posts, its really helpfull.As of now I am working on DRM 9.3.2 ( I know its pretty old) but now my client wants to upgrade it to latest version of DRM i guess that is 11.1.2.1. Do you have any document which can help me in migrating from 9.3.2 to the latest one. Thanks a lot for your help in advance.

    Regards
    Vineet

    ReplyDelete
  4. VineetOctober 24, 2011 at 10:21 PM

    Also if you can share any document around understanding the Oracle DRM repository metadata tables that would be great. Really appreciate your help.

    Regards
    Vineet

    ReplyDelete
  5. GeetaOctober 24, 2011 at 10:30 PM

    Hi Vineet,

    The process is pretty easy, follow the steps:

    1) Install 11.1.2.1.103 (latest)
    2) Configure 11.1.2.1.103
    3) Either use the config tool to create a 11.1.2.1.103 drm repository and metadata tables or run the scripts created in the wizard.
    4) Use the repository wizard and select copy/upgrade
    5) Choose your 9.3.2 db repository as source and 11.1.2.1.103 created in 2) as target.
    6) Right click on the application and make sure you click on "apply updates"
    7) Reboot DRM services

    Also, ensure that you have a backup of the 9.3.2 drm respository to revert to just in case the upgrade fail.

    ReplyDelete
  6. AnonymousOctober 25, 2011 at 7:19 PM

    Hi Geeta,

    I did installed DRM 11.1.2.1.103 the challenge is while creating a repository(upgrade) from an Existing,

    My existing DRM 11.1.1.1.00 has lot of export to tables to different Databases and it looks like as part of the repository upgrade in DRM 11.1.2.1.103 we need to specifically provide the Path (if it's a Hierarchy Export to a file path),DB connection (in case if it's a Export to Table)..it's painful to update all the exports and there are more then 120 such,

    Is there any option we can exclude(like the way we do with versions) these getting migrated or any quick fixes?


    Your help and thoughts are greatly appreciated,

    Thanks,
    Murali

    ReplyDelete

Subscribe to: Post Comments (Atom)