Click Select next to Patch File. Browse to select the patch file you want to apply, Click Finish.
2. Select File, then select Merge. The Merge Repository Wizard appears.
Figure 16–11 shows the Merge Repository Wizard. Figure 16–11 Merge Repository Wizard: Select Input Files Screen Patch Merge3. For Merge Type, select Patch Repository Merge.
4. Click Select next to Original Master Repository. Browse to select the original
repository, then click Open. Note that the original repository cannot be the same as the modified currently open repository. 5. Enter the repository password for the original repository.6. Click Select next to Patch File. Browse to select the patch file you want to apply,
then click Open. 7. Optionally, click Select next to Save Merged Repository as, then enter a file name under which the patched repository will be saved and click Save.8. Click Finish.
16-20 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Using patchrpd to Apply a Patch You can also apply a patch using the patchrpd utility. This feature is especially useful when you want to patch repositories on Linux and UNIX systems where the Administration Tool is not available. Note that unlike the Administration Tool patch feature, patchrpd does not display or resolve conflicts. If a conflict is detected, patchrpd displays a warning and exits. Before running patchrpd, you must first run bi-init.cmd or bi-init.sh on UNIX to launch a command prompt or shell window that is initialized to your Oracle instance. You can find this utility in: ORACLE_INSTANCEbifoundationOracleBIApplicationcoreapplicationsetup Then, run patchrpd from the resulting shell window with the desired options, as follows: patchrpd [-P modified_rpd_password] -C modified_rpd_pathname [-W original_rpd_password] -G original_rpd_pathname -I xml_patch_file_pathname -O output_rpd_pathname [-S schema_location] [-8] Where: modified_rpd_password is the repository password for the modified repository, also called the customer or customized repository. The password argument for the modified repository is optional. If you do not provide a password argument for the modified repository, you are prompted to enter a password when you run the command. To minimize the risk of security breaches, Oracle recommends that you do not provide a password argument either on the command line or in scripts. Note that the password argument is supported for backward compatibility only, and will be removed in a future release. modified_rpd_pathname is the name and location of the modified repository. original rpd_password is the repository password for the original repository. The password argument for the original repository is optional. If you do not provide a password argument for the original repository, you are prompted to enter a password when you run the command. To minimize the risk of security breaches, Oracle recommends that you do not provide a password argument either on the command line or in scripts. Note that the password argument is supported for backward compatibility only, and will be removed in a future release. original_rpd_pathname is the name and location of the original repository. xml_patch_file_pathname is the name and location of the XML patch file you want to apply. output_rpd_pathname is the name and location of the RPD output file you want to generate. schema_location is the name and location of the Oracle BI Server XML schema. If you do not specify a location, patchrpd assumes the schema file is in the default location of ORACLE_HOMEbifoundationserverbinxudml1.xsd. -8 specifies UTF-8 encoding. For example: patchrpd -C customer.rpd -G original.rpd -I patch.xml -O patched.rpd Give password for customer repository: my_modified_rpd_password Give password for original repository: my_original_rpd_password Managing Oracle BI Repository Files 16-21 This example applies a patch called patch.xml to the customer.rpd repository, and then generates an output repository called patched.rpd. Querying and Managing Repository Metadata You can use repository queries to help manage repository metadata in the following ways: ■ Examine and update the internal structure of the repository. For example, you can query for objects in the repository based on name, type such as Logical Column or Presentation Hierarchy, or on a combination of name and type. You can then edit or delete objects that appear in the Results list. You can also create new objects and view parent hierarchies. ■ Query a repository and view reports that show such items as all tables mapped to a logical source, all references to a particular physical column, content filters for logical sources, initialization blocks, and security and user permissions. For example, you might want to run a report before making any physical changes in a database that might affect the repository. You can save the report to a file in comma-separated value CSV or tab-delimited format. ■ You can save a query to run again later, or save the query results to an external file. When you save to an external file, the encoding options are ANSI, Unicode, and UTF-8. This section contains the following topics: ■ Querying the Repository ■ Querying Related Objects Querying the Repository You can query for objects in the repository using the Query Repository tool. You can also construct a filter to filter the results, save a query, run a previously saved query, or create new repository objects. To query a repository: 1. In the Administration Tool, open your repository.2. Select Tools, then select Query Repository.
Parts
» Oracle Fusion Middleware Online Documentation Library
» Click OK when you are finished setting preferences.
» Select Set Icon. Oracle Fusion Middleware Online Documentation Library
» Select the appropriate DSN and click OK.
» Click OK. Oracle Fusion Middleware Online Documentation Library
» Without opening a repository, select File Multiuser History.
» In the ODBC Data Source Administrator dialog, click the System DSN tab, and
» In the Select Data Source screen, in the Connection Type field, select the type of
» Click Finish. Oracle Fusion Middleware Online Documentation Library
» In the Administration Tool, select File, then select Import Metadata.
» Provide the Data source name for the primary database. Click OK.
» In the Select Data Source screen, select OracleADF_HTTP for Connection Type.
» Select the objects you want to import in the Available list and move them to the Click Finish.
» In the Database dialog, click the Features tab. In the Features tab, use the information in
» Specify or adjust the properties as needed, then click OK.
» In the Persist connection pool area, click Clear. Click OK.
» To add tables to the display folder, click Add. Then, in the Browse dialog, select Click OK.
» Click OK in the Hierarchy dialog.
» Select View Members. Click Query to display results. When finished, click Close.
» Click OK. Select Create Columns for Alias Table. Then, from the sub-list, select the alias
» Type the text of the hint in the Hint field and click OK.
» In the shortcut menu, select Update Row Count. Click Yes to check out the objects.
» If you want to provide a dynamic list of currency options, create a table in your
» Click OK. Click OK or Cancel to close the Dimensions dialog.
» From the right-click menu, select Create Logical Dimension, then select either
» In the Check Out Objects dialog, click Yes to check out the objects that appear in
» If the values for the source are unique, select the option Select distinct values.
» Click OK. To move a table, in the Name list, select the table you want to reorder. Then, use
» In the Finish Script screen, the complete path and file name appears. Click Finish.
» Click OK, then click OK again to return to the Identity Manager.
» On the General tab, in the Data source definition: Database field, ensure that the
» Click OK. Open the user.sh file. You can find this file at:
» Click Select next to Patch File. Browse to select the patch file you want to apply, Click Finish.
» Select Tools, then select Query Repository. Click Query.
» When you have finished mapping columns between the selected physical tables, Click Finish.
» In the Choose Directory dialog, click Browse to locate and select the location Click OK.
» To remove the selected objects, click Yes.
» Repository initialization blocks only In the Schedule area, select a start date and
» In the [Repository|Session] Variable Initialization Block dialog, click Edit Data
» Click Edit Data Target. Click OK.
» Check out the branch project using File Multiuser Checkout. You can check
Show more