In the Persist connection pool area, click Set. Click OK, then click OK again to save the persist connection pool.

Setting Up Database Objects and Connection Pools 6-21 Setting Up Persist Connection Pools A persist connection pool is a database property that is used for specific types of queries typically used to support Marketing queries. In some queries, all of the logical query cannot be sent to the transactional database because that database might not support all of the functions in the query. This issue might be solved by temporarily constructing a physical table in the database and rewriting the Oracle BI Server query to reference the new temporary physical table. You can use the persist connection pool in the following situations: ■ Populate stored procedures. Use to rewrite the Logical SQL result set to a managed table. Typically used by Oracles Siebel Marketing Server to write segmentation cache result sets. ■ Perform a generalized subquery. Stores a nonfunction subquery in a temporary table, and then rewrites the original subquery result against this table. Reduces data movement between the Oracle BI Server and the database, supports unlimited IN list values, and might result in improved performance. In these situations, the user issuing the Logical SQL query must have been granted the Populate privilege on the target database. The persist connection pool functionality designates a connection pool with write-back capabilities for processing this type of query. You can assign one connection pool in a single database as a persist connection pool. If this functionality is enabled, the user name specified in the connection pool must have the privileges to create DDL Data Definition Language and DML Data Manipulation Language in the database. To assign a persist connection pool: 1. In the Physical layer of the Administration Tool, double-click the database object for which you want to assign a persist connection pool. 2. In the Database dialog, click the General tab.

3. In the Persist connection pool area, click Set.

If there is only one connection pool, it appears in the Persist connection pool field. 4. If there are multiple connection pools, in the Browse dialog, select the appropriate connection pool, and then click OK. The selected connection pool name appears in the Persist connection pool field. SQL Bypass Database Optional The name of the SQL Bypass database. The SQL Bypass database must be a physical database in the Physical layer of the repository. The database object for the SQL Bypass database must have a valid connection pool, with connection information that points to the same database that is being used by the JDBC Data source defined in the WebLogic Server. The SQL Bypass database does not need to have any tables under it. After a valid database name is supplied, the SQL Bypass feature is enabled for all queries. The SQL Bypass feature directly queries the database so that aggregations and other transformations are pushed down where possible, reducing the amount of data streamed and worked on in Oracle Business Intelligence. See About Specifying a SQL Bypass Database for more information. Table 6–8 Cont. Connection Pool Properties in the Miscellaneous Tab Property Description 6-22 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition 5. Optional To set write-back properties, click the Connection Pools tab. 6. In the connection pool list, double-click the connection pool. 7. In the Connection Pool dialog, click the Write Back tab. 8. Complete the fields using Table 6–7 as a guide. See also About Setting the Buffer Size and Transaction Boundary for additional information.

9. Click OK, then click OK again to save the persist connection pool.

To remove a persist connection pool: 1. In the Physical layer of the Administration Tool, double-click the database object that contains the persist connection pool you want to remove. 2. In the Database dialog, click the General tab.

3. In the Persist connection pool area, click Clear.