Creating and Administering General Properties for Physical Tables
Use the General tab of the Physical Table dialog box to create or edit a physical table in the Physical layer of the Administration Tool.
Creating or Editing Physical Tables
This section describes how to create or edit the general properties for a table. This includes physical cube tables and alias tables.
- In the Physical layer of the Administration Tool, perform one of the following steps:
- To create a physical table, right-click the physical database and choose New Object > Physical Table.
- To create a physical cube table for a multidimensional data source, right-click the physical database and choose New Object > Physical Cube Table.
- To create an alias table, right click a physical table, and choose New Object > Alias.
- To edit an existing physical table, double-click the physical table icon.
- In the selected Physical Table dialog box, complete the fields using Table 13 as a guide.
To include the table in the Oracle BI Server query cache, select this check box. When you select this check box, the Cache persistence time settings become active. This is useful for OLTP data sources and other data sources that are updated frequently. Typically, you should check this option for most tables. | |
When you select this option, cache entries do not expire. This could be useful when a table will be important to a large number of queries users might run. For example, if most of your queries have a reference to an account object, keeping it cached indefinitely could actually improve performance rather than compromise it. | |
How long table entries should persist in the query cache. The default value is Infinite, meaning that cache entries do not automatically expire. However, this does not mean that an entry will always remain in the cache. Other invalidation techniques, such as manual purging, LRU (Least Recently Used) replacement, metadata changes, and use of the cache polling table, result in entries being removed from the cache. If a query references multiple physical tables with different persistence times, the cache entry for the query will exist for the shortest persistence time set for any of the tables referenced in the query. This makes sure that no subsequent query gets a cache hit from an expired cache entry. For more information, refer to Troubleshooting Problems with an Event Polling Table. | |