Translate

Thursday, 1 March 2012

OBIA Upgrade RPD

Oracle OBIA Repository Upgrade from 10g to 11g


Follow this procedure to prepare for the repository upgrade.
To prepare for the Analytics repository upgrade
  1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:
    • Original
    • AfterEqualize
    • AfterMerge
    • AfterManualWork
    • AfterRegressions
  2. Copy the following repositories to the folder \OracleBIUpgrade\Original:
    • The production repository that you also upgraded to the 11g format  (for example, Customer_OracleBIAnalyticsApps.rpd.
    • The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)
    If, in your current environment, you are running Oracle BI Applications for one or more modules using a Oracle BI repository in which you extracted the corresponding projects for the modules from the standard Oracle BI repository file you received from the previous release, you need to extract the same projects from the OracleBIAnalyticsApps_79x.rpd file and use this as your original repository. (If you have the original repository that you extracted during the last upgrade, you can use it as the original repository file.) This will prevent you from losing any new metadata you would like to add in this upgrade.
    Also, if you customized the Oracle BI repository by trimming a large number of objects and you would like to get those objects back during the current upgrade, you need to trim the OracleBIAnalyticsApps_79x.rpd file in the same way and use the modified version as the original repository file. This will prevent you from losing any new metadata you would like to add in this upgrade.

Equalizing the Oracle BI Repositories

The Merge feature in the Administration Tool relies on a change detection algorithm to determine the changes that need to be made to upgrade repositories correctly. For the algorithm to work correctly, it has to determine which objects in the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) are equivalent.
The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_OracleBIAnalyticsApps.rpd whether it is coming from the OracleBIAnalyticsApps_79x.rpd.
Equivalence between objects is established using the Administration Tool's Equalize feature. The file that you specify in the Output option (-O) is the only file that is modified during the equalization process.
The Equalize feature has several mechanisms for determining whether an object in two different repositories is semantically the same:
  • Fully Qualified Name. If an object in one repository has the same fully qualified name as another object of the same class in another repository, then the two objects are declared equal.
  • Simple String Substitution. Equivalence can be declared between two objects of the same class in two repositories whose only difference is that some key characters in their names differ. The equalizerpds executable file ignores those characters while checking fully qualified names. For example, "Core"."W_DAY_D" might be considered equivalent to "Core"."W DAY D" if the characters "_" and " " have been declared as equivalent.
  • Rename File. When none of the preceding rules are applicable, equivalence can be manually declared using a script as input to the equalizerpds executable file. Oracle ships the rename files (MAP) for the major releases. The files are located in the $ORACLE_BI_HOME\biapps\upgrade folder. You can also create your own rename files for customizations not covered in the files that Oracle ships. You can open and edit the rename files in Microsoft Excel.
    Table 6-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.
    Table 6-2 Rename MAP Files to Be Used for Various Releases
    Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)Rename MAP File to Be Used
    Siebel Business Analytics Applications 7.0.xNot available
    Siebel Business Analytics Applications 7.5.xNot available
    Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)Rename77-7963.map
    Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)Rename771-7963.map
    Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this releaseRename782-7963.map
    Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this releaseRename783-7963.map
    Oracle BI Applications 7.9.0Rename79x-7963.map
    Oracle BI Applications 7.9.1Rename79x-7963.map
    Oracle BI Applications 7.9.2Rename79x-7963.map
    Oracle BI Applications 7.9.3Rename793to7963.map
    Oracle BI Applications 7.9.4Rename794to7963.map
    Oracle BI Applications 7.9.5Rename79x-7963.map
    Oracle BI Applications 7.9.5.1Rename7951to7963.map
    Oracle BI Applications 7.9.5.2Rename7951to7963.map
    Oracle BI Applications 7.9.6Rename79x-7963.map
    Oracle BI Applications 7.9.6.2Not required
The syntax of the equalizerpds command is as follows:
equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name 
[-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.
To equalize a repository
  1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.
  2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsAppss_793.rpd). An example of the equalizerpds command is as follows:
    equalizerpds -B SADMIN
    -C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
    -D Administrator -E SADMIN
    -F \\OracleBIUpgrade\Original\OracleBIAnalyticsApps.rpd
    -O \\OracleBIAnalyticsUpgrade\AfterEqualize\OracleBIAnalyticsApps.rpd
    -X -J rename7x-79.map
    
    The MAP files are located in the $ORACLE_BI_HOME\biapps\upgrade folder.
    If the equalizerpds.exe executable file runs correctly, no errors are returned.
  3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_79x.rpd). An example of the equalizerpds command is as follows:
    equalizerpds -B SADMIN
    -C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
    -E SADMIN
    -F \\OracleBIUpgrade\Original\Customer_OracleBIAnalyticsApps.rpd
    -O \\OracleBIUpgrade\AfterEqualize\Customer_OracleBIAnalyticsApps.rpd
    
    The execution of equalizerpds that equalizes the customer repository with the original repository does not use the rename file.
    Make sure that the original repository is copied unchanged into its new location so that after running the script, all three repositories are contained within the \OracleBIUpgrade\AfterEqualize directory.
  4. To verify the process completed successfully, compare the size of the repositories. The output repository (-O) should be close to the same size as the repository you equalized (-F).

Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.
To compare the Oracle BI repositories
  • Use the Administration Tool's Compare Repositories feature to analyze the differences between your existing repository and the new version of the repository to which you are upgrading. Note where elements have been created, removed, or changed in the new version. Consider whether you can use the new metadata and retire customizations you made in the existing repository.
    For instructions on how to use the Administration Tool's Compare Repositories feature, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
To merge versions of the Oracle BI repositories
  1. Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.
  2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.
  3. From the Administration Tool menu bar, select File, then select Merge.
  4. Select the Merge Type option Full Repository Merge.
  5. In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).
  6. Enter the password for the original repository.
  7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.
  8. Enter the password for the modified repository.
  9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
    The new repository will contain the final results of the merge.
  10. Select the Equalize during merge check box.
  11. Click Next.
  12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.
  13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
    When all rows have a value in the Decision field, the Finish button is enabled.
  14. Select the Check consistency of the merged RPD check box.
  15. Click Finish.
    This process can take up to 40 minutes, depending on the size of the repositories you are working with. A message will alert you when the merge is complete.
  16. The number of errors returned by the consistency check is an indication of how successful the merge process was. If you receive many errors, for example, over 300, you should analyze the reason for the errors. If the merge process failed to recognize that two objects are the same, you may need to edit the rename file if the object is in the Current repository, or add your own rename file if you have renamed many of the objects and the upgrade engine failed to relate them to the original objects.
    You also may need to change the actions you selected in the Decision drop-down list before rerunning the merge. This could save you time by reducing the number of errors that you will need to fix manually.
    Once you are satisfied with the results of the merge, you should fix the remaining errors manually. It is important that you fix all errors before moving on to the next step. This repository serves as the input for the next stage.
    You should also check that all of your customized objects are present and that no duplicate physical tables were introduced. To check for duplicate tables, search for physical tables using a query such as:
    where name like '*#1'
    
  17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

No comments:

Post a Comment

Google Big Query Clone / Copy DataSets / Tables - PROD --> TEST --> DEV Projects

Google Big Query Cloning of Datasets & Tables across GCS Projects. We searched the internet and could not find a simple cloning / ...