Oracle® Warehouse Builder Installation and Configuration Guide 10g Release 1 (10.1) Part Number B12150-02 |
|
|
View PDF |
Before installing Warehouse Builder, you need to prepare your Oracle Database by setting the following configuration parameters:
The Warehouse Builder Repository database runs on standard Oracle Database configuration parameters.
Table A-1 lists the configuration parameters to use as an initial guide for ensuring performance.
Table A-1 Initialization Parameters for the Design Repository Instance
Initialization Parameter | Set to Value | Comments |
---|---|---|
|
This setting is required for the following connect statement to work:
If, however, this parameter is set to |
|
|
This setting is an alternative to use if you cannot set the
|
|
|
You may specify a higher value. |
|
|
This parameter is set when the database is created and cannot be changed. Warehouse Builder does not recommend a value higher than |
|
|
This is 100 MB. |
|
|
If this parameter is not in the initialization file, add it to the end of the file. |
|
|
This setting is required to ensure that the |
|
|
Oracle recommends locking the design SGA in physical memory. |
To support the Warehouse Builder runtime component, you need to modify the Oracle Database Enterprise Edition instance on the system where your data warehouse will reside.
Note:
If you install Warehouse Builder on Oracle8i, you must configure the Warehouse Builder Runtime instance to have at least one non-system rollback segment for the seeded runtime packages to compile. Warehouse Builder suggests the use of server-managed rollback segments.Table A-2 lists the database configuration parameters.
Table A-2 Initialization Parameters for the Runtime Instance
Initialization Parameter | Set to Value | Comments |
---|---|---|
|
This parameter is set when the database is created. Do not change it. The recommended value is |
|
|
For other possible optimizer modes, see Oracle Designing and Tuning for Performance, Oracle Database Performance Tuning Guide and Reference, and Oracle Data Warehousing Guide. |
|
See comments |
Set the value to larger than 512K and must be 128K times the number of CPUs. |
|
500 MB to 1 GB |
The larger value, or as close to it as possible, is recommended if computer memory allows it. If you set the
Alternatively, you can set the |
|
|
This setting amounts to 300 MB. Set this value as high as the system permits. Do not set any value for the |
|
|
The recommended minimum value is 50 MB. Oracle recommends raising this parameter to 100MB if memory is available. In the unlikely case that you require more than 100MB, ensure that this parameter is tuned by a knowledgeable DBA. Do not set any value for the |
|
|
This setting enables the server to set the Prerequisite: Do not set any value for the |
|
|
A value of 16 is recommended, but 32 is preferred. |
|
|
If the platform does not support asynchronous I/O, set |
|
|
|
|
|
Disable this parameter by setting it to
|
|
|
This is 300 MB. If you perform frequent sorting and aggregation, you can increase this value. However, |
|
|
Set |
|
|
The PL/SQL compiler in Oracle Database 10g Release 1 (10.1) can perform more elaborate optimization on PL/SQL code. |
|
|
This setting increases the timeout for performing checkpoints from the default 3 minutes to 5 minutes. |
|
|
||
|
With this setting, you do not have to create rollback segments. |
|
|
A minimum setting of '1' is required for the install to complete without error. |
|
|
You may specify a higher value if you launch multiple sessions or if you run multiple or complicated mappings in one session. |
|
|
Set this parameter to |
|
See note. |
Do not set this parameter to TRUE as that would conflict with other recommendations. |
|
|
The minimum recommended value is 20 MB. Do not set any value for the |
|
|
You must use the |
|
|
If this parameter is not in the initialization file, add it to the end of the file. |
|
|
This parameter is required for the Warehouse Builder and Oracle Workflow Advanced Queueing System. |
|
|
Specifies the directories that PL/SQL can use for file input and output. If you use flat file targets in Warehouse Builder, set this parameter to the directory where you want to create the flat file target so that your database engine has access to it. (Refer to AppendixA, "Configuring the Target Data File Path for Flat File Targets" for details). |
|
|
||
|
Oracle strongly recommends creating a resource plan for managing resource usages for Warehouse Builder runtime. Refer to the Oracle Database Administration Guide for information on resource plans. |
|
|
Optimal setting is |
To configure the Target Data File Path for Flat file Targets, you set this path in the init.ora
file of the warehouse instance. Set the UTL_FILE_DIR
parameter to the directory for the flat file targets so that the database has access to it.
For example, for the output file location D:\Data\FlatFiles\File1.dat
, set the UTL_FILE_DIR
parameter in your init.ora
file to:
UTL_FILE_DIR = D:\Data\FlatFiles
For multiple valid file locations, such as both D:\Data\FlatFiles
and E:\OtherData
, set the parameter in init.ora
to:
UTL_FILE_DIR = D:\Data\FlatFiles UTL_FILE_DIR = E:\OtherData
These lines must be consecutive in the init.ora
file.
You can bypass this checking of directories by using the following command:
UTL_FILE_DIR = *
If you plan to integrate your Warehouse Builder Design Browser and Runtime Audit Browser with Oracle Application Server, set the parameters listed in Table A-3.