Scribd Logo
Importer

Bienvenue sur Scribd !

  • Obiee11g Mig

    Transféré par

    Mohamed Abrar
    79 vues34 pages
    This document summarizes the steps to migrate an existing OBIEE 11g RPD file to a new instance: 1. In Enterprise Manager, browse to the new RPD file location, provide the password and catalog name, and click Apply. This uploads the new RPD as a new instance. 2. An error occurs when logging into the RPD through Administration due to mismatched GUIDs between the RPD and repository. 3. The GUIDs must be refreshed by changing config file settings to YES, adding a line to the instance config file, restarting the servers, then changing the settings back to original values. 4. After restarting the servers, login through Administration now works

    Description originale:

    migration

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Formats disponibles

    PPTX, PDF, TXT ou lisez en ligne sur Scribd

    Avez-vous trouvé ce document utile ?

    Ce contenu est-il inapproprié ?

    Signaler ce document
    This document summarizes the steps to migrate an existing OBIEE 11g RPD file to a new instance: 1. In Enterprise Manager, browse to the new RPD file location, provide the password and catalog name, and click Apply. This uploads the new RPD as a new instance. 2. An error occurs when logging into the RPD through Administration due to mismatched GUIDs between the RPD and repository. 3. The GUIDs must be refreshed by changing config file settings to YES, adding a line to the instance config file, restarting the servers, then changing the settings back to original values. 4. After restarting the servers, login through Administration now works

    Droits d'auteur :

    Attribution Non-Commercial (BY-NC)
    Téléchargez comme PPTX, PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    79 vues34 pages

    Obiee11g Mig

    Transféré par

    Mohamed Abrar
    This document summarizes the steps to migrate an existing OBIEE 11g RPD file to a new instance: 1. In Enterprise Manager, browse to the new RPD file location, provide the password and catalog name, and click Apply. This uploads the new RPD as a new instance. 2. An error occurs when logging into the RPD through Administration due to mismatched GUIDs between the RPD and repository. 3. The GUIDs must be refreshed by changing config file settings to YES, adding a line to the instance config file, restarting the servers, then changing the settings back to original values. 4. After restarting the servers, login through Administration now works

    Droits d'auteur :

    Attribution Non-Commercial (BY-NC)
    Téléchargez comme PPTX, PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    sur 34

    MIGRATION IN OBIEE 11G

    Enterprise Manager
    Open the Enterprise Manager Select Coreapplication and click Deployment and Repository

    Enterprise Manager

    Enterprise Manager

    You can see the already existing RPD with the name as HRANALYTICS_ BI10003 Also the location of Catalog with the name HRANALYTICS is also seen in the Presentation Service Repository

    Enterprise Manager

    Enterprise Manager

    Browse to your location the new RPD named Banorte.rpd Give the Password for the RPD Also Provide the name of the catalog as Banorte in the Presentation Service Repository Note:The Banorte catalog should be already pasted before the migration process in the location mentioned under catalog folder

    Enterprise Manager

    Now click Apply The Banorte.rpd is uploaded as a new instance with serial number as Banorte_BI004 Now click Activate Changes Restart all the servers as shown below

    Enterprise Manager

    Enterprise Manager

    Enterprise Manager

    Administration Login

    Now login into the RPD using Administration The error appears as shown above The GUID of user weblogic does not match user reference GUID at the repository GUID stands for Global Unique Identifier and it must be refreshed in the config files as old user reference exist

    Weblogic Server Login

    Config Files

    Go to the Nqsconfig.ini in the location F:\OBIEE\instances\instance4\config\Oracle BI server component\coreapplication_obis1 In the config file find the line FMW_UPDATE_ROLE_AND_USER_REF_GUIDS =NO; Change it to YES and save the config file

    Config Files

    Config Files

    Config Files

    Now go to the location F:\OBIEE\instances\instance4\config\Oracle BI Presentation Server and find the instance config.xml file Find the catalog section as shown above Add a line as <ps:UpdateAccountGUIDs>UpdateAndExit</ps :UpdateAccountGUIDs> as shown below

    Config Files

    Command Prompt

    Go to the location F:\OBIEE\instances\instance4\Bin Copy the above location and open the command prompt Use commands opmnctl stopall and opmnctl startall as shown in the screens below The status of all the servers are also seen which is in running mode

    Command Prompt

    Command Prompt

    Command Prompt

    Command Prompt

    Config Files

    Now go to the Nqsconfig.ini and change the User reference Guids to NO as shown above Also Go to the instanceconfig.xml file and delete the UpdateAndExit line which was added in the Catalog section as shown below Both the files should be saved(we are making both the config files to restore them to the states they were before change was made

    Config Files

    Command Prompt

    Now again open the command prompt and copy the location F:\OBIEE\instances\instance4\Bin and run the opmnctl stopall and opmnctl startall commands as before Also the status can be seen using the command opmnctl status which shows the servers in running mode Now again go to Administration in online mode and login(It works fine as GUIDS are refreshed)

    Vous aimerez peut-être aussi