Creating a Database Object Manually in the Physical Layer

When you create a database object manually, you must also manually set up an associated connection pool.

For multidimensional data sources, if you create the physical schema in the Physical layer of the repository, you need to create one database in the physical layer for each cube, or set of cubes, that are in the same catalog (database) in the data source. A physical database can have more than one cube. The cubes must belong to the same catalog in the data source.


Oracle strongly recommends importing your physical schema.

  1. In the Administration Tool, in the Physical layer, right-click and select New Database.

    Make sure that no object is selected when you right-click.

  2. In the Database dialog, in the General tab, complete the fields using the table as a guide.
Option Description

Data source definition: Database

The database type for your database.

Data source definition: CRM metadata tables

This property is only available for relational data sources and is for legacy Siebel Systems sources only.

When selected, indicates that the definition of physical tables and columns for Siebel CRM tables was derived from the Siebel metadata dictionary.

Data source definition: Virtual Private Database

Identifies the physical database source as a virtual private database (VPD). When a VPD is used, returned data results are contingent on the user's authorization credentials. Therefore, it is important to identify these sources. These data results affect the validity of the query result set that is used with caching.

Always select this option for Essbase, Hyperion Financial Management, and Hyperion Planning data sources that are configured for SSO in the corresponding connection pool.


If you select this option, you also should select the Security Sensitive option in the Session Variable dialog.

Persist connection pool

To use a persistent connection pool, you must set up a temporary table first.

Allow populate queries by default

When selected, allows everyone to execute POPULATE SQL. If you want most, but not all, users to be able to execute POPULATE SQL, select this option and then limit queries for specific users or groups.

Allow direct database requests by default

When selected, allows all users to execute physical queries. The Oracle BI Server sends unprocessed, user-entered, physical SQL directly to an underlying database. The returned results set can be rendered in Oracle BI Server, and then charted, rendered in a dashboard, and treated as an Oracle Business Intelligence request.

If you want most, but not all, users to be able to execute physical queries, select this option and then limit queries for specific users or groups.