| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
This chapter outlines the installation process, discusses the hardware and software requirements, and introduces the Oracle Warehouse Builder architecture and its components. This chapter includes the following topics:
Oracle Warehouse Builder is an information integration tool that leverages the Oracle Database to transform data into high-quality information. As shown in Figure 1-1, the Oracle Database is a prominent component in the Warehouse Builder architecture as the database hosts the Warehouse Builder repository, the code generated by Warehouse Builder, and also hosts the target schema.
Figure 1-1 illustrates the interaction of the major components of the Warehouse Builder software. The Design Center is the user interface for designing, managing, scheduling, and deploying ETL processes for moving and transforming data. All metadata associated with the work done in the Design Center is stored in the Oracle Warehouse Builder Repository. The repository is hosted on an Oracle Database and you can use the Repository Browser to report on the metadata in the repository. Also hosted on an Oracle Database is the Target Schema to which Warehouse Builder loads data resulting from the ETL processes you execute through the Control Center Service.
Figure 1-1 Warehouse Builder with Traditional Client/Server Implementation
The Design Center provides the graphical interface for defining sources and designing targets and ETL processes.
Control Center Manager
Also in the Design Center client is the Control Center Manager from which you can deploy and execute ETL processes. The Control Center Manager is a comprehensive deployment console that enables you to view and manage all aspects of deployment.
The target schema is the target to which you load your data and the data objects you designed in the Design Center such as cubes, dimensions, views, and mappings. The target schema contains Warehouse Builder components such as synonyms that enable the ETL mappings to access the audit/service packages in the repository. The repository stores all information pertaining to the target schema such as execution and deployment information.
Notice in Figure 1-1 that the target schema is not a Warehouse Builder software component but rather an existing component of the Oracle Database. As such, you can associate multiple target schemas with a single Warehouse Builder repository. You can have a 1 to 1 relationship or many target schemas to a single repository. For example, Figure 1-2 depicts two target schema hosted on the same database as the repository. One target schema associated with multiple repositories, however, is not permitted.
A Warehouse Builder repository is comprised of a repository owner, one or more repository users, and a schema. The repository schema stores metadata definitions for all the sources, targets, and ETL processes that constitute your design metadata. In addition to containing design metadata, a repository can also optionally contain the runtime data generated by the Control Center Manager and Control Center Service. Or you can create two repositories, one for design metadata and another for runtime metadata.
As part of the initial installation of Warehouse Builder, you use the Repository Assistant to define one or more repositories. Later in the implementation cycle, you also use the Repository Assistant to manage existing repositories or create new ones.
For examples on the options for implementing repositories, see Implementation Strategies.
The Repository Browser is a web browser interface for reporting on the repository. You can view the metadata, create reports, audit runtime operations and perform lineage and impact analysis. The Repository Browser is organized such that you can browse design repository specific and control center specific information.
The Control Center Service is the component that enables you to register locations and deploy from the Control Center Manager, and the ability to execute ETL mappings and process flows.
This section provides an overview of the various options for implementing Warehouse Builder. Detailed instructions on how to implement each option are provided in subsequent sections in Chapter 2, "Installing an Oracle Warehouse Builder Repository".
Basic Implementation
The simplest option is to install all client and server components on a single local computer, which is suitable if you are performing a proof of concept or launching a pilot program.
Traditional Client/ Server Implementation
As depicted in Figure 1-1, client components reside on multiple client machines and server components reside on a single server.
Separate Design and Runtime Environments Implementation
In an implementation such as shown in Figure 1-2, one repository stores metadata definitions for objects such as sources, targets, and ETL processes that users access through the Design Center.
A separate repository stores runtime data. Notice that a single Control Center Service manages the control center and its deployment and execution activities.
The runtime data is stored in audit tables that users access through the control center specific reports in the Repository Browser.
The only communication between the design repository and the control center repository occurs when you deploy objects to the target schema.
Figure 1-2 Split Repositories Implementation
Remote Runtime Environment Implementation
The Control Center Service is the Warehouse Builder server component that governs the deployment of objects to target schemas. Most commonly, as shown in Figure 1-2, the Control Center Service can be installed on the machines hosting the target schemas.
For those exceptions in which the Control Center Service cannot be installed on the same computer as the target schema, the alternative is to implement a remote runtime environment.
Implement a remote runtime environment if the Warehouse Builder software is not supported for the operating system hosting the target schema. Also consider remote runtime if your company security policies restrict you from installing additional software on the computer hosting the target schema.
For additional information, see Implementing a Remote Runtime (Optional).
The steps you take to install Warehouse Builder depend on if you are installing the software on to a new server or if you are upgrading an existing installation. If you want to upgrade an existing installation, refer to Chapter 3, "Upgrading to Oracle Warehouse Builder 10g Release 2 (10.2)".
If you want to begin a new installation, use the following instructions to determine which chapters and sections in this book to reference.
To begin a new installation:
Determine your implementation strategy.
To accommodate a variety of environments and customer needs, Warehouse Builder offers you flexibility in where you install server and client components.
Review Warehouse Builder Architecture and Components and Understanding the Installation Requirements to develop an implementation strategy.
Review the Oracle Warehouse Builder Release Notes.
The release notes may contain installation notes or known issues that affect your installation strategy. Access the release notes either on the Oracle Warehouse Builder CD-ROM or, for the latest version, go to the Oracle Technology Network at http://otn.oracle.com.
For RAC environments only, proceed to Steps for Installing Warehouse Builder in RAC Environments. Otherwise, continue with the next step in these instructions.
Installing the Warehouse Builder Software on the server
Review the Checklist: Before You Launch the Universal Installer and then launch the Oracle Universal Installer and follow the prompts to install the Warehouse Builder software onto the computer you designated as the server. In the case of a split implementation, install Warehouse Builder software on each of the two machines hosting repositories.
Installing an Oracle Warehouse Builder Repository
The Repository Assistant prompts you to define users and an owner for the repository.
To launch the Repository Assistant on Windows, from the Windows Start menu, select Programs and navigate to the Oracle product group you installed in the previous step. Select Warehouse Builder, Administration, and then Repository Assistant.
To launch the Repository Assistant on UNIX, locate OWB_ORACLE_HOME/owb/bin/unix and execute reposinst.sh.
Setting the Security Policy for the Repository (Optional)
When you install a repository, Warehouse Builder enforces a default metadata security policy. The default policy is a minimal security policy appropriate for proof-of-concept or pilot projects.
You can override the default by selecting a maximum security policy. Alternatively, you can use the security interface in Warehouse Builder to design your own security policy. In either of these two cases, ensure that repository database has the Advanced Security Option (ASO) enabled.
Installing Optional Components (Optional)
See Chapter 5 for instructions on enabling optional components such as browsers, third party tools, and related Oracle products.
Install the Warehouse Builder software on the client machines.
Repeat Installing the Warehouse Builder Software for each computer to be used as a client.
When you complete the installation process, you can launch all the Warehouse Builder components as described in Launching Warehouse Builder Components.
Refer to this section as you develop your implementation strategy.
Table 1-1 lists the components required and Table 1-2 lists some of the optional components in an Oracle Warehouse Builder environment.
Required Components
Table 1-1 lists the components required in an Oracle Warehouse Builder environment. The table summarizes important considerations for installing each component and identifies where to look for further details.
Table 1-1 Required Components
| Components | Requirements |
|---|---|
|
Server computer The operating system can be any Windows or UNIX platform supported by Oracle 10g database. For the most up-to-date list of certified hardware platforms and operating system versions, review the certification matrix on the OracleMetaLink Web site at |
For Windows, both 32-bit and 64-bit architectures are supported. Ensure that the computer has a minimum of 850 MB disk space, 768 MB available memory, and 768 MB of page file size, TMP, or swap space. For UNIX, ensure that the computer has a minimum of 1100 MB disk space, 768 MB available memory, and 1100 MB of page file size, TMP, or swap space. See Preparing the Server. |
|
Oracle Database The database can be any of the following versions:
If you intend to deploy dimensional structures to an Analytic Workspace, you must use either:
|
You must have SYSDBA privileges to install the Warehouse Builder repository on the database. Ensure that DB_BLOCK_SIZE is set to the most optimal value of 16384 or the largest block size the server allows. See Preparing the Oracle Database. Review the following topics as necessary: |
|
Client computer Client machines must have either a Windows or a Linux operating system. |
For Windows, ensure that the computer has a minimum of 850 MB disk space, 768 MB available memory, and 1GB of page file size, TMP, or swap space. For Linux 32-bit, ensure that the computer has a minimum of 1100 MB disk space, 768 MB available memory, and 1GB of page file size, TMP, or swap space. |
|
Oracle Universal Installer Review the "Checklist: Before You Launch the Universal Installer" and launch the Oracle Universal Installer in install Warehouse Builder components to servers or clients. |
Be sure to specify a separate Oracle home for Warehouse Builder. For example, specify OWB_ORACLE_HOME. |
|
Oracle Warehouse Builder Components
|
You can have a single, unified repository. Or you can define separate repositories with one to contain design metadata and another to contain runtime metadata generated by the Control Center Service. Install a repository on every server that hosts a target schema. If necessary, you can have a target schema without installing additional Warehouse Builder components on its server. For an overview, see Warehouse Builder Architecture and Components. For examples, see Installing a Repository using the Advanced Setup Options. |
Optional Components
Table 1-2 lists some of the optional components that are compatible with an Oracle Warehouse Builder environment. The table summarizes important considerations for each optional component and identifies where to look for further details.
Table 1-2 Optional Components
| Components | Requirements |
|---|---|
|
Oracle E-Business Suite (Optional) You have the option of making data and metadata from E-Business Suite available to Warehouse Builder users. |
|
|
Oracle Workflow (Optional) This is an option for you to use Oracle Workflow to manage job dependencies. If you plan to use Warehouse Builder process flows, you need to install Oracle Workflow to enable deployment. |
Warehouse Builder is compatible with the following versions:
|
|
Oracle Enterprise Manager (Optional) This is an option for you to use Oracle Enterprise Manager to schedule jobs. |
Warehouse Builder is compatible with Oracle9i Enterprise Manager Release 2. |
|
Third Party Name and Address Data (Optional) This is an option if you plan to use the Name and Address operator to cleanse name and address data. |
You will need the following from one of the certified vendors listed on Oracle Technology Network:
|
If you have yet to install an Oracle Database on the server, then consult the Oracle Database Installation Guide for your operating system. Be sure to install the required operating system patches before installing the Oracle Database.
Warehouse Builder 10g Release 2 (10.2.0.2) is available on the same platforms supported by Oracle Database 10g.
Review the certification matrix on the OracleMetaLink Web site for the most up-to-date list of certified hardware platforms and operating system versions. This Web site also provides compatible client and database versions, patches, and workaround information for bugs. The OracleMetaLink Web site is available at the following URL:
On all UNIX platforms other than Linux, only the Warehouse Builder server components are supported. For Linux 32-bit platforms, however, you can install both server and client components. That is, you can install the Repository and Control Center Service on a UNIX server but the Design Center and Repository Browser require either a Windows or Linux 32-bit platform.
If you are installing only the server components, ensure that the UNIX operating system meets the requirements listed in Table 1-3. If you are also installing the client components to be accessed by Linux, see the additional hardware requirements listed in Preparing Client Machines.
Table 1-3 UNIX Operating Environment Software Requirements
| Requirement | Value |
|---|---|
|
Disk Space |
1100 MB |
|
Available Memory |
768 MB. Memory requirements increase depending on the functions performed and the number of users connected. |
|
Page File Size, TMP, or Swap Space |
1 GB |
Setting Environmental Variables in UNIX
When installing UNIX, you must specify the environmental variable for the Oracle home.
Use the UNIX commands listed in Table 1-4 where full_path is the path into which you will install Warehouse Builder 10g Release 2 (10.2.0.2).
On Windows platforms, you can install either the Warehouse Builder server or client components or both components on the same computer. Table 1-5 contains the Windows operating system requirements. These requirements are in addition to the requirements of any other Oracle products you are installing on the same computer. Refer to the documentation for each Oracle product you are installing to determine complete system requirements.
Table 1-5 Windows Operating Environment Software Requirements
| Requirement | Value |
|---|---|
|
Disk Space |
850 MB |
|
Available Memory |
768 MB Memory requirements increase depending on the functions being performed and the number of users connected. |
|
Page File Size, TMP, or Swap Space |
1 GB |
|
System Architecture |
32-bit and 64-bit Note that while the OWB Design Center client is installed with the DB, only the 32-bit Windows and 32-bit Linux Design Center clients are certified and supported by Oracle. For Windows, Design Center is only supported on 32-bit client operating systems, not on Windows Server 2003. Note also that Oracle provides both 32-bit and 64-bit versions of Warehouse Builder server components. The 32-bit version of Warehouse Builder must run on the 32-bit version of the operating system. The 64-bit version of Warehouse Builder must run on the 64-bit version of the operating system. |
|
Operating System |
Warehouse Builder server components are supported on the following operating systems:
Warehouse Builder Design Center client is only supported on Linux x86 32-bit and the following Windows 32-bit platforms:
|
Warehouse Builder 10g Release 2 (10.2.0.2) is supported and certified for use with the following releases of the Oracle Database:
Oracle9i Release 2 (9.2.x) Enterprise Edition
Oracle Database 10g Enterprise Edition R1 (10.1.x)
Oracle Database 10g Standard Edition R2 (10.2.x)
Oracle Database 10g Enterprise Edition R2 (10.2.x)
Note:
Warehouse Builder has not been tested or certified and therefore is not supported for use with the Personal or Express Editions of the Oracle Database. Also, if you intend to utilize an Oracle Database Standard Edition, see the limitations described in Hosting the Repository on Oracle Database Standard Edition.For each database you intend to install the Warehouse Builder repository, you need a user with SYSDBA privileges.
You must install the Oracle Database on any computer that you intend to create a Warehouse Builder design repository or a target schema as described in subsequent chapters.
The size requirements for the repository varies according to the character set. The tablespace usage of an empty repository with an AL32UTF8 character set, for example, is approximately 90 MB. To accommodate an average usage of the Warehouse Builder repository with a single-byte character set, Oracle recommends an additional 1330 MB for a total of 1420 MB recommended. For multi-byte character sets, you should extrapolate a larger tablespace requirement.
If you intend to implement one of the metadata security options available in Warehouse Builder, enable the Oracle Advanced Security option in the database. See Setting the Security Policy for the Repository (Optional) for an overview of the metadata security options.
Before installing Warehouse Builder, prepare the Oracle Database by setting the necessary configuration parameters. If the database will host both the design and runtime components, the Oracle 10g database self tunes its configuration settings to optimize server resources. The only additional parameters you may need to set are for Configuring the Target Data File Path for Flat File Targets.
If the design and runtime components are to be in separate design repositories, refer to Parameters for the Design Repository Database Instance and Parameters for the Runtime Repository Database Instance.
The Oracle 10g database self tunes its configuration settings to optimize server resources. To ensure that Warehouse Builder performs effectively, verify that DB_BLOCK_SIZE is set to its optimal value.
Table 1-6 lists the configuration parameters to use as an initial guide for ensuring performance.
Table 1-6 Initialization Parameters for the Design Repository Instance
| Initialization Parameter | Set to Value | Comments |
|---|---|---|
|
|
|
If this parameter is not in the initialization file, add it to the end of the file. |
|
|
|
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. |
|
|
|
Oracle recommends locking the design SGA in physical memory. |
|
|
|
Set this to
|
|
|
|
You may specify a higher value. |
|
|
|
This setting is required for the following connect statement to work:
If, however, this parameter is set to |
To support the Warehouse Builder runtime component, you may need to modify the Oracle Database instance. Table 1-7 lists the database configuration parameters.
Table 1-7 Initialization Parameters for the Runtime Instance
| Initialization Parameter | Set to Value | Comments |
|---|---|---|
|
|
|
This parameter is required for the Warehouse Builder and Oracle Workflow advanced queuing system. |
|
|
|
If this parameter is not in the initialization file, add it to the end of the file. |
|
|
|
This parameter is set when the database is created. Do not change it. The recommended value is |
|
|
|
Set this value to 300 MB or as high as the system permits. You may need to adjust operating system parameters to allow larger shared memory segments. Do not set any value for the |
|
|
|
A value of 16 is recommended, but 32 is preferred. |
|
|
see comments |
If you have fewer than 8 CPUs, set |
|
|
|
Disable this parameter by setting it to
|
|
|
|
If the platform does not support asynchronous I/O, set |
|
|
|
A minimum setting of '1' is required for the install to complete without error. |
|
|
|
The minimum recommended value is 20 MB. Do not set any value for the |
|
|
|
Optimal setting is |
|
|
|
Do not set any value for this parameter if you set a value for the Prerequisite: |
|
|
See comments |
Set the value to larger than 512K and must be 128K times the number of CPUs. |
|
|
|
This setting increases the timeout for performing checkpoints from the default 3 minutes to 5 minutes. |
|
|
0 |
This is only required when installing on RAC systems. If it is not set to |
|
|
|
You may specify a higher value if you launch multiple sessions or if you run multiple or complicated mappings in one session. |
|
|
|
For other possible optimizer modes, see Oracle Designing and Tuning for Performance, Oracle Database Performance Tuning Guide and Reference, and Oracle Data Warehousing Guide. |
|
|
|
Set |
|
|
|
This setting delegates the task of tuning parallel processing to the server. Set this parameter for Oracle9i or Oracle8i databases only. For Oracle 10g and later, this parameter is not available and setting SGA_TARGET to a nonzero value is recommended. |
|
|
|
This is 300 MB. If you perform frequent sorting and aggregation, you can increase this value. However, |
|
|
|
The PL/SQL compiler in Oracle Database 10g Release 2 (10.2.0.2) can perform more elaborate optimization on PL/SQL code. |
|
|
|
Set this parameter to |
|
|
|
You must use the |
|
|
|
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. |
|
|
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 Note: For Oracle 10g and later, setting |
|
|
|
The recommended minimum value is 400 MB. Do not set any value for the |
|
|
|
|
|
|
|
With this setting, you do not have to create rollback segments. |
|
|
|
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 Configuring the Target Data File Path for Flat File Targets. |
|
|
|
. |
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 = *
Certain functionalities in Oracle Warehouse Builder require the Enterprise Edition of the Oracle Database. Therefore, if you host the a Warehouse Builder repository on a Standard Edition of the database, some functionalities are not supported.These limitations include, but are not limited to, the following:
Limited Password Security in Oracle Database Standard Edition
Table compression is not supported.
Partitioning of tables is not supported.
You cannot use partition exchange loading in mappings.
Bitmap indexes are not supported.
You cannot set the value of the configuration parameter Data Segment Compression to COMPRESS.
You cannot import dimensions and cubes using the Import Metadata Wizard.
Dimensional objects that use a ROLAP or MOLAP implementation cannot be deployed successfully.
For Windows, ensure that the computer has a minimum of 850 MB disk space, 768 MB available memory, and 1GB of page file size, TMP, or swap space.
For Linux, ensure that the computer has a minimum of 1100 MB disk space, 768 MB available memory, and 1GB of page file size, TMP, or swap space.
If you previously deinstalled Warehouse Builder and the path <OWB_ORACLE_HOME>\owb\j2ee\owbb remains, delete the owbb directory before installing Warehouse Builder again.
About ORACLE_HOME and Warehouse Builder
Oracle home is the top-level directory in which you install Oracle software. Some Oracle products enable you to share the same Oracle home. Or you can create separate homes and assign names to each home as you install each product.
Although you can install some Oracle products to share the same Oracle home, Warehouse Builder cannot share its home directory. Install Warehouse Builder into a separate Oracle home directory from the Oracle Database or any other Oracle product.
Setting Environmental Variables in UNIX
When installing client components on Linux, you must specify the environmental variable for the Oracle home.
Use the UNIX commands listed in Table 1-8 where full_path is the path into which you will install Warehouse Builder 10g Release 2 (10.2.0.2).
Oracle Warehouse Builder uses Oracle Universal Installer to install components and to configure environment variables. The installer guides you through each step of the installation process.
Whether you are installing Warehouse Builder components onto a server or a client computer, you use the Oracle Universal Installer to install Warehouse Builder components. Before launching the Universal Installer, review and complete the Checklist: Before You Launch the Universal Installer.
This section contains additional points to address before launching the Universal Installer:
If you have not already done so, review the Oracle Warehouse Builder Release Notes either on the Oracle Warehouse Builder CD-ROM or, for the latest version, go to the Oracle Technology Network at http://otn.oracle.com.
For Windows NT/2000/XP Professional, ensure that you are logged on to your system as a member of the Administrators group.
For UNIX, be sure you are not logged in as the root user when you start the Oracle Universal Installer. If you are, then only the root user will have the permissions required to manage Oracle Warehouse Builder.
For both server and client installation, you must specify an Oracle home directory such as OWB_ORACLE_HOME to be used only for the Warehouse Builder installation. For UNIX, you must set the ORACLE_HOME environmental variable.
Close all other open applications.
To run the Oracle Universal Installer:
Insert the Oracle Warehouse Builder CD-ROM.
If your computer supports the autorun feature, the autorun window will automatically launch the Oracle Warehouse Builder installation.
If your computer does not support the autorun feature, locate the executable setup.exe in the root directory of the CD-ROM or downloaded software. Start the installer by launching the setup.exe program.
When prompted, specify a home directory such as OWB_ORACLE_HOME to be used only for the Warehouse Builder installation.
Follow the on screen instructions.
When the software installation completes successfully, you can continue with the next step in General Steps for Installing Warehouse Builder.
To run the Oracle Universal Installer:
You can run Oracle Universal Installer from the CD-ROM. Do not run the Installer while the CD-ROM directory is the current directory or you will be unable to unmount the next CD-ROM when prompted to do so.
Log in as the oracle user.
Note:
Be sure you are not logged in as the root user when you start the Oracle Universal Installer. If you are, then only the root user will have permissions to manage Oracle Warehouse Builder.Start the installer by entering the following at the prompt:
cd mount_point
./runInstaller
Install the OWB_ORACLE_HOME into the same operating system user as Oracle Database ORACLE_HOME.
Note:
As the installation proceeds, the Oracle Universal Installer prompts you to run several scripts. You need to switch user and run the script as root.When the software installation completes successfully, you can continue with the next step in General Steps for Installing Warehouse Builder.
The Oracle Warehouse Builder CD installs the client and server-side software at the same time. After you complete the installation, you can launch the Warehouse Builder components listed in Table 1-9.
The components in Table 1-9 are listed in the order that you are likely to use the components directly after installation:
Table 1-9 Launching Warehouse Builder Components from Windows or Linux Clients
| Warehouse Builder Component | Windows:Select Start, Programs, OWB_ORACLE_HOME, and then ... | Linux:Locate OWB_ORACLE_HOME/owb/bin/unix and then... |
|---|---|---|
|
Repository Assistant Enables you to manage repositories and their schemas and users. |
Select Administration, and then Repository Assistant. |
Execute reposinst.sh |
|
Design Center Is the primary design interface. |
Select Design Center. |
Execute owbclient.sh |
|
Start Control Center Service This command is only necessary when working in a remote runtime environment. |
Select Administration then Start Control Center Service. |
Execute local_service_login.sh If the service fails to start, you can run OWB_ORACLE_HOME/owb/rtp/sql/service_doctor.sql. |
|
Control Center Manager Is the command to deploy and execute to a remote runtime environment. |
Launch the Design Center. From the Tools menu, select Control Center Manager. |
Execute local_service_login.sh as follows: local_service_login.sh -startup <OWB-Home> |
|
Stop Control Center Service This command is only necessary when working in a remote runtime environment. |
Select Administration then Stop Control Center Service. |
Execute local_service_login.sh as follows: local_service_login.sh -closedown <OWB-Home> |
|
Start OWB Browser Listener |
Select Administration, and then Start OWB Browser Listener. |
Execute startOwbbInst.sh |
|
Repository Browser |
Select Repository Browser. |
Start the OWB Browser Listener and then execute openRAB.sh. |
|
Stop OWB Browser Listener |
Select Administration then Stop OWB Browser Listener. |
Execute stopOWBBInst.sh |
|
OMB Plus Is the scripting utility that enables to perform all operations available in the graphical user interfaces. |
Select OMB Plus. |
Execute OMBPlus.sh. |
The overall process for installing on a RAC environment is similar to the General Steps for Installing Warehouse Builder. However, there are a few specific details to observe as noted in the following instructions:
To install in a RAC environment:
Create the RAC environment as described in the Oracle Clusterware and Oracle Real Application Clusters Installation Guide specific to your platform.
If you have not already done so, review the most recent Oracle Warehouse Builder Release Notes available at http://otn.oracle.com.
Preparing Host Machines
For each computer to host Warehouse Builder components, configure the tnsnames.ora file located in the OWB_ORACLE_HOME\network\admin directory.
Be sure to set the initialization parameter MAX_COMMIT_PROPAGATION_DELAY to a value of zero.
Also configure tnsnames.ora for each Oracle Database server that will be a Warehouse Builder data source or target. If you fail to configure tnsnames.ora for any host or database server, you may encounter a repository connection error such as "The connection to the repository was lost, because of the following database error: ORA-12154:TNS:could not resolve the connect identifier specified".
Installing the Warehouse Builder Software
Review the Checklist: Before You Launch the Universal Installer and then launch the Oracle Universal Installer.
Installing an Oracle Warehouse Builder Repository
The Repository Assistant prompts you to define users and an owner for the repository.
To launch the Repository Assistant on Windows, from the Windows Start menu, select Programs and navigate to the Oracle product group you installed in the previous step. Select Warehouse Builder, Administration, and then Repository Assistant.
To launch the Repository Assistant on UNIX, locate OWB_ORACLE_HOME/owb/bin/unix and execute reposinst.sh.
Register each RAC node.
For each node, launch the Repository Assistant and select the Advanced Set up option. Connect to the node using the net service name. Select the option for registering the RAC instance.
If the software is installed on separate disks, copy rtrepos.properties to each node in the cluster.
If you did not install to a shared disk, then you must manually copy the file <OWB_ORACLE_HOME>/owb/bin/admin/rtrepos.properties from the primary node to each node in the cluster.
Installing Optional Components (Optional).
Consider performing the optional step Configuring Repository Browser Environments. The Repository Browser lets you nominate a RAC node and register other nodes.
Install the Warehouse Builder software on the client machines.
Repeat Installing the Warehouse Builder Software for each computer to be used as a client.
When complete the installation process, you can launch all the Warehouse Builder components.
When Launching Warehouse Builder Components such as the Design Center, Control Center Manager, and Repository Assistant, select the log on option SQL*Net connection and specify the net service name you assigned in the tnsnames.ora file.
Since you can connect to Warehouse Builder repositories using a net service name, you can embed RAC properties into the connect string to utilize RAC functionalities such as connect time failover, load balancing on server and load balancing of connections.
Ensuring the Availability of Service Names for RAC Nodes
The Control Center Service requires that service names for the individual nodes in the cluster be available. If these are not present after the RAC installation, you must manually ensure the availability.
Whether you are installing Warehouse Builder components onto a server or a client computer, you use the Oracle Universal Installer to install Warehouse Builder components.
For RAC, it is recommended that you install the Warehouse Builder components on each node of the cluster. The Control Center Service is required on to each node of the RAC cluster.You can achieve this in a single installation of the Warehouse Builder software if you install on a shared disk such as an OCFS or NTS shared disk.
Before launching the Universal Installer, review and complete the Checklist: Before You Launch the Universal Installer.
This section contains additional points to address before launching the Universal Installer:
If you have not already done so, review the latest version Oracle Warehouse Builder Release Notes at http://otn.oracle.com.
To enable clusterware installation, ensure that you are running an interactive secure shell such as /bin/ssh and have host user equivalency to all nodes.
For Windows NT/2000/XP Professional, ensure that you are logged on to your system as a member of the Administrators group.
For UNIX, be sure you are not logged in as the root user when you start the Oracle Universal Installer. If you are, then only the root user will have the permissions required to manage Oracle Warehouse Builder.
Specify an Oracle home directory such as OWB_ORACLE_HOME to be used only for the Warehouse Builder installation. For UNIX, you must set the ORACLE_HOME environmental variable.
The installed location must be the same directory path if using separate OWB_ORACLE_HOME installed disks, that is, local physical disks on each server.
Close all other open applications.
To run the Oracle Universal Installer:
Insert the Oracle Warehouse Builder CD-ROM.
If your computer supports the autorun feature, the autorun window will automatically launch the Oracle Warehouse Builder installation.
If your computer does not support the autorun feature, locate the executable setup.exe in the root directory of the CD-ROM or downloaded software. Start the installer by launching the setup.exe program.
When prompted to specify the cluster node, you can select all hosts or the local node.
If you select local node, then you must install Warehouse Builder separately for each system unless installing to a shared disk.
When prompted, specify a home directory such as OWB_ORACLE_HOME to be used only for the Warehouse Builder installation.
Follow the on screen instructions.
When the software installation completes successfully, you can continue with the next step in General Steps for Installing Warehouse Builder.
To run the Oracle Universal Installer:
You can run Oracle Universal Installer from the CD-ROM. Do not run the Installer while the CD-ROM directory is the current directory or you will be unable to unmount the next CD-ROM when prompted to do so.
Log in as the oracle user.
Note:
Be sure you are not logged in as the root user when you start the Oracle Universal Installer. If you are, then only the root user will have permissions to manage Oracle Warehouse Builder.Start the installer by entering the following at the prompt:
cd mount_point
./runInstaller
When prompted to specify the cluster node, you can select all hosts or the local node.
If you select local node, then you must install Warehouse Builder separately for each system unless installing to a shared disk.
Install the OWB_ORACLE_HOME into the same operating system user as Oracle Database ORACLE_HOME.
Note:
As the installation proceeds, the Oracle Universal Installer prompts you to run several scripts. You need to switch user and run the script as root.When the software installation completes successfully, you can continue with the next step in General Steps for Installing Warehouse Builder.
List all of the instance or node names in the cluster. Issue the following command:
srvctl config database -d <dbname>
where dbname is the unique database name as specified by the init parameter db_name.
For a given instance, instn, add a service with the following command:
srvctl add service -d <dbname> -s <instn> -r <instn>
The resulting service name is <instn>.<clusterdomainname>. For example, if the instance name is owbrac1,then the service name could be owbrac1.us.oracle.com.
For a given instance, instn,start the service with the following command:
srvctl start service -d <dbname> -s <instn>
For a given instance, instn,verify the service is running with the following command:
srvctl status service -d <dbname> -s<instn>
Complete steps 2 through 4 for each RAC node.
|
 Copyright © 2000, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
