Changes Related to Data Source Connectivity

1-16 Upgrade Guide for Oracle Business Intelligence This new gesture direction from many to one matches the direction of the new join arrow, described in the previous bullet. ■ Presentation catalogs in the Presentation layer are now called subject areas.

1.2.2.8 Repository Modeling Changes

Note the following changes in Oracle BI 11g related to repository modeling: ■ Bridge tables are now identified using repository modeling techniques. They are no longer identified using the Bridge table option in the Logical Table dialog that existed in previous releases. Check the repository to ensure that the bridge tables are modeled appropriately. See Modeling Bridge Tables in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information. ■ You might notice that some queries that used to return one result now return a different result. This behavior occurs because the determination of which logical table source to use for a query is now very ordered, whereas in previous releases, the determination was random. Examine and adjust the modeling to correct the behavior. ■ In 10g, if two logical table sources for the same logical table map to the same physical table, and both logical table sources are used in a query, and both logical table sources have a WHERE clause filter, then the filter from only one of the logical table sources was applied. The other WHERE clause filter was ignored. In 11g, in this situation, the WHERE clause filters from both logical table sources are applied to the query. Typically, this behavior produces the desired results. If you encounter errors related to this issue, then you can correct them by using physical table aliases to ensure that the same physical table is not mapped to the same logical table at different levels.

1.2.2.9 Changes to Write Back

If you configured write-back capability in a previous release of Oracle Business Intelligence, you must now explicitly select the Writeable option for each logical column for which you want to enable write back. See Enabling Write Back on Columns in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information.

1.2.2.10 Changes to Static Variables

Static repository variables must have default initializers that are constant values. See About Repository Variables in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information.

1.2.2.11 MUD History Must Be Manually Upgraded in Oracle Business Intelligence 11g

The Oracle BI Administration Tool multiuser development MUD environment enables users to obtain historical information about repository changes, as follows: ■ Subset changes prior to merge are stored as modified subset repositories. ■ Each version in the MUD location is stored as repository_name.version_number. In Oracle BI 11g, repository files are encrypted with a user-specified repository password. As a result, the Administration Tool can open only repository files that have been fully upgraded and encrypted.