In the Table list on the left side of the dialog, select the table that the foreign key Select the columns in the left table that the foreign key references. Select the columns in the right table that make up the foreign key columns. Optional To specify a
4. In the Table lists on the left and right side of the dialog, select the tables that the
logical join references.5. Optional To specify a driving table for the key, select a table from the Driving
list, and an applicable cardinality. This option is useful for optimizing the manner in which the Oracle BI Server processes multi-database inner joins when one table is very small and the other table is very large. Do not select a driving table unless multi-database joins are going to occur. See Specifying a Driving Table for more information about driving tables.6. Select the join type from the Type list, or keep the default value.
7. Set the Cardinality for each side of the join, or keep the default values.
8. Click OK.
Creating Logical Foreign Key Joins with the Joins Manager Logical foreign key joins might be needed if the Oracle BI Server is to be used as an ODBC data source for certain third-party query and reporting tools. Typically, you should not create logical foreign keys. This capability is in the Administration Tool to provide compatibility with previous releases. To create a logical foreign key join with the Joins Manager: 1. In the Administration Tool, select Tools, then select Options. 2. In the General tab of the Options dialog, select Allow logical foreign key join creation .3. Click OK.
4. Select Manage, then select Joins to display the Joins Manager.
5. Select Action New Logical Foreign Key.
6. In the Browse dialog, double-click a table to display the Logical Foreign Key
dialog.7. Type a name for the foreign key.
8. In the Table list on the left side of the dialog, select the table that the foreign key
references.9. Select the columns in the left table that the foreign key references.
10. Select the columns in the right table that make up the foreign key columns.
11. Optional To specify a driving table for the key, select a table from the Driving
list, and an applicable cardinality. Caution: Use extreme caution in deciding whether to specify a driving table. Driving tables are used for query optimization only under rare circumstances and when the driving table is extremely small, that is, less than 1000 rows. Choosing a driving table incorrectly can lead to severe performance degradation. 8-10 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition This option is useful for optimizing the manner in which the Oracle BI Server processes multi-database inner joins when one table is very small and the other table is very large. Do not select a driving table unless multi-database joins are going to occur. See Specifying a Driving Table for more information about driving tables.12. Select the join type from the Type list, or keep the default value.
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