Skip Headers
Oracle® Warehouse Builder Installation and Administration Guide
11g Release 2 (11.2) for Windows and Linux
Part Number E10579-01
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

A Troubleshooting the Installation and Setup

This section describes some troubleshooting tasks you may need to perform during installation and setup of Oracle Warehouse Builder.

This section includes the following topics:

General Steps for Troubleshooting Warehouse Builder

Take the following steps to troubleshoot errors in Warehouse Builder:

  1. Review this section for a possible solution to the problem.

    If Warehouse Builder displays an error message during the installation process, then refer to "Error Messages Related to Installation". If you did not note the error number, you can review the "Log Files for Installation Errors".

    In the absence of an error message, refer to "Troubleshooting Other Installation Problems".

  2. Check for additional information about the problem by "Inspecting Log Files in Warehouse Builder".

  3. If the problem remains unresolved, search for a possible solution at My Oracle Support at https://metalink.oracle.com/.

  4. Review the Oracle Warehouse Builder Release Notes for installation notes or known issues.

  5. If you are unable to resolve the problem in the previous steps, contact Oracle Support.

    Oracle Support may ask you to complete the steps in "Generating Log Files for a Specific Warehouse Builder Component".

Inspecting Log Files in Warehouse Builder

This section outlines all the different types of error messages that are logged by Warehouse Builder and how to access them.

Warehouse Builder logs the following types of errors:

Log Files for Installation Errors

When you run Oracle Universal Installer to install Warehouse Builder, the installation error logs are automatically stored in:

C:\ProgramFiles\Oracle\Inventory\logs\installActions<timestamp>.log

When you run the Warehouse Builder Repository Assistant, the workspace installation error logs are stored in:

OWB_HOME\UnifiedRepos\log_timestamp.log

See "Error Messages Related to Installation" for suggested actions for commonly encountered errors during installation.

Log Files for Metadata Import and Export Errors

Metadata Import: When you import a project or specific objects into your workspace using the Metadata Import Utility, Warehouse Builder records details of the import process in a log file. You can specify the name and location of this log file from the Metadata Import dialog box.

Metadata Export: When you export a Warehouse Builder project or specific objects using the Metadata Export Utility, Warehouse Builder records the details of the export in a log file. You can specify the name and location of this log file from the Metadata Export dialog box.

Log File for Validation Errors

In Warehouse Builder, you can validate all objects by selecting the objects from the console tree and then selecting Validate from the Object menu. After the validation is complete, the validation messages are displayed in the Validation Results window.

You can also validate mappings from the Mapping Editor by selecting Mapping, then Validate. The validation messages and errors are displayed in the Validation Results window.

On the Validation tab of the Validation Results window, double-click an object name in the Object column to display the editor for that object. You can fix errors in the editor. Double-click a message in the Message column to display the detailed error message in a message editor window. To save the message to your local system, select Code in the menu bar, then select Save as File.

Warehouse Builder saves the last validation messages for each previously validated objects. You can access these messages at any time by selecting the object from the console tree in the Project Navigator, select View from the menu bar, and then click Validation Messages. The messages are displayed in the Validation Results window.

Log File for Generation Errors

After you generate scripts for Warehouse Builder objects, the Generation Results window displays the generation results and errors. Double-click an error under the Messages column on the Validation tab to display a message editor that enables you to save the errors to your local system.

After you generate scripts for Warehouse Builder objects, the Generation Results window displays the generation results and errors. Double-click an error under the Messages column on the Validation tab to display a message editor that enables you to save the errors to your local system.

Log Files for Deployment and Execution Errors

You can store execution or deployment error and warning message logs on your local system by specifying a location for them. In the Project Navigator, select the project. Then from the Tools menu, select Preferences. In the Preferences dialog box, click the Logging option in the object tree to the left. In the list box on the right, you can set the log file path, file name and maximum file size. You can also select the types of logs you want to store.

You can view this log of deployment and error messages from the Warehouse Builder console by selecting View from the menu bar, and then Messages Log. This Message Log dialog box is read-only.

Errors related to the Control Center Service are stored at the following path:

OWB_HOME\log\Repository_Name\log.xx on Oracle Database server.

Errors related to transforming or loading data are stored in the Control Center audit tables. You can access these error reports using the Repository Browser. The Browser provides detailed information about past deployments and executions. Click the Execution tab in the Execution reports to view error messages and audit details.

Log File for Name and Address Server Errors

If you are using the Name and Address cleansing service provided by Warehouse Builder, you can encounter related errors.

Name and address server start up and execution errors can be located at:

OWB_HOME\owb\bin\admin\NASver.log

If your Name and Address server is enabled in:

OWB_HOME\owb\bin\admin\NameAddr.properties:TraceLevel=1,

then it produces the log file NASvrTrace.log.

Error Messages Related to Installation

This section includes the following topics:

Causes and Actions

No fonts were found in '<drive>:\Program Files\ Qarbon\viewlet Builder3jre\lib\fonts'
Cause: After installing Warehouse Builder client components, you installed another software program that relies on Jinitiator and overwrote Java objects necessary of Oracle products. This may prevent you from launching Warehouse Builder or any other Oracle product that depends on Java objects.
Action: Re-install Jinitiator.
OWBSYS is not granted access to OWB_HOME/owb/bin/admin/rtrepos.properties: Please run UnifiedRepos/reset_owbcc_home.sql specifiying the path of Oracle Home from which the Control Center Service is being run.
Cause: When running the script reset_owbcc_home.sql and prompted for the OWB_HOME, you typed an invalid path for OWB_HOME.
Action: Run the script again and enter the correct path.

On all platforms, including both Windows and Unix, the path you enter must use forward slashes, and is case-sensitive. The case of the path entered here must match exactly the case of the path for the Warehouse Builder home as known by the operating system.

On Unix, the correct path to enter is the path for the OWB_HOME directory. On Windows, to determine the correct path for the OWB_HOME directory, and examine the path displayed as part of the default Windows command prompt.

SYS user does not have SYSDBA privileges.
Cause: In a standard database installation, the SYS user has SYSDBA credentials and REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE. You can verify the credentials by issuing the following connect statement:

SQL> CONNECT sys@tns_name_of_db AS SYSDBA;

Enter password: sys_password

If your database is configured with REMOTE_LOGIN_PASSWORDFILE=NONE, then the statement fails.

Action: If the statement fails, then you have the following options:

  • Reconfigure your database with

    REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and create a password file if none exists.

  • If the preceding is not an option, reconfigure your database with

    O7_DICTIONARY_ACCESSIBILITY=TRUE.

RTC-5301: The Control Center Service is not currently available.
Cause: A Control Center Service must be running to enable the Control Center to manage deployments and executions. The service connects to the Control Center using JDBC and can be run from any Warehouse Builder home. Normally the service is runs on the server host.
Action: You can start a service on the server host by using the script start_service.sql.

If it is not possible to run the service on the server host, then start the Control Center Service on the local computer using the script local_service_login.sh or local_service_login.bat as appropriate. Use this script as follows:

local_service_login.sh [-startup | -closedown] OWB_HOME

In this mode, the Control Center Service runs on the local computer and is available only when that computer is available and can connect to the Control Center.

Use the script show_service.sql to determine the status of the service.

Control center service log file reports "DBMS_OBFUSCATION" or "No key is found."
Cause: The encryption of the passwords is out of sync with the client.
Action: Reset the repository and restart the control center service. To reset the repository, run owb/rtp/sql/reset_repository.sql.
API5022: Cannot Connect to the Specified Repository
This error occurs when you try to connect to the a repository after having performed a database export or import from the Warehouse Builder repository schema.
Cause: The package NAMESPACESERVICEIMPL may be invalid. This occurs after a database export or import from the Warehouse Builder repository schema if the repository owner has no SELECT privilege on SYS.V_$SESSION. You can diagnose the cause as follows:

  1. In SQL*Plus, connect to the Warehouse Builder repository schema.

  2. Enter the following command at the SQL prompt:

    ALTER PACKAGE NAMESPACESERVICEIMPL compile body;

  3. If Warning: Package body altered with compilation errors appears, enter the following command at the SQL prompt:

    show errors;

  4. The following errors mean that the Warehouse Builder repository owner has no SELECT privilege on SYS.V_$SESSION.

    PL/SQL: SQL statement ignored
PLS-00201: Identifier 'SYS.V_$SESSION' must be declared
Action: Complete the following steps:

  1. In SQL*Plus, connect as the SYS user.

  2. At the SQL prompt, enter the following command:

    grant SELECT on V_$SESSION to Warehouse Builder_Repository_Owner;

  3. Connect to the Repository_Owner.

  4. Enter the following command at the SQL prompt:

    alter package NAMESPACESERVICEIMPL compile;
Run-time Assistant fails with LoadJava Error.
Cause: This can occur if the Oracle Database does not have the JServer option installed.
Action: Make sure that the Oracle Database has JServer option installed.
Error when specifying a SYSDBA user.
Oracle Warehouse Builder Assistants require you to provide SYSDBA credentials when installing the Oracle Warehouse Builder Design Repository or run-time components.
Cause: In a standard database installation, the SYS user has SYSDBA credentials. You can verify this from SQL*Plus by issuing the following connect statement:

connect sys/sys_password@TNS_NAME_OF_DB as sysdba;

In a standard database installation, the preceding connect statement works because REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and the default password file is created by the installation process.

If your database is configured with

REMOTE_LOGIN_PASSWORDFILE=NONE, then the following statement fails:

connect sys/sys_password@TNS_NAME_OF_DB as sysdba;

In this case, you have two options.

Action: Reconfigure your database with

REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and create a password file if none exists.

Action: If the preceding is not an option, then reconfigure your database with

O7_DICTIONARY_ACCESSIBILITY=TRUE. With this setting, the statement

connect sys/sys_password@TNS_NAME_OF_DB enables the Warehouse Builder Assistants to connect to SYS user.

Regional Name and Address Data Libraries Are Not Available.
Cause: The Name and Address regional data libraries may not have been installed in the correct location.
Action: Ensure that you have successfully extracted regional data to the NAS_DATA directory.

  1. From the OWB_HOME, start the Name and Address Server:

    For Windows, run owb\bin\win32\NAStart.bat.

    For Linux, Run owb/bin/unix/NASTART.sh.

  2. Open the log file: owb\bin\admin\NASvr.log.

    The log contains a list of installed countries.

    If there is no such list, then verify that you have extracted the regional library data to the correct location. If you have extracted the data to the wrong location, then you can either reinstall the data, or modify the owb\bin\admin\NameAddr.properties file to indicate the correct file path. If you modify the NameAddr.properties file, then stop and restart the Name and Address Server as follows:

    For Windows, start the server by running owb\bin\win32\NAStart.bat. Stop the server by running owb\bin\win32\NAStop.bat.

    For UNIX, start the server by running owb/bin/unix/NAStart.sh. Stop the server by running owb/bin/unix/NAStop.sh.

  3. Once you have verified the installation, you can stop the Name and Address Server if you want, because it is automatically started at the execution of any mapping that employs the Name and Address operator.

Lineage and impact analysis reports: Extensive tablespace requirements for materialized views.
The first time you refresh a materialized view, it is populated from the Oracle Warehouse Builder repository. The materialized view can occupy up to twice the amount of space allocated to the entire Warehouse Builder repository.
Cause: Insufficient space has been allocated to the Warehouse Builder repository schema.
Action: If the Warehouse Builder repository schema is created in a tablespace that is dedicated to its use, these issues are easier to monitor. Ensure that sufficient free space exists on the physical drive for tablespace expansion. Within Oracle Enterprise Manager, ensure that the tablespace is set to Autoextend On.

Note:

To grant permission to an OWB repository user to use Enterprise Manager for performing tasks, enter the following command in SQL*Plus: GRANT SELECT any dictionary to "&OWB repository user";
Java out of memory error occurs during a batch operation.
Operations requiring large amounts of memory can result in a Java out of memory error, if the system resources (such as virtual memory) are constrained.
Cause: There is not enough virtual memory. The Warehouse Builder client runs with a maximum heap size, as defined by the -mx parameter in the owbclient.bat file. The -Dlimit parameter in the owbclient.bat file specifies the memory threshold (80% of Dlimit) at which the Warehouse Builder memory manager begins to assist Java garbage collection. If you change the -mx parameter value, set the -Dlimit parameter to the same value, or at least to 90% of the value. Note that setting the -Dlimit to a low value can have a negative impact on the performance of Warehouse Builder.
Action: Increase the -Dlimit parameter in Warehouse Builder as follows:

  1. Exit Warehouse Builder.

  2. Open this file in a text editor:

    For Windows, open the $OWBHOME\bin\win32\ombplus.bat.

    For UNIX, open the $OWBHOME\bin\win32\owbclient.sh.

  3. Change the -Dlimit parameter to 334.

  4. Save and close the file.

  5. Restart Warehouse Builder.

ORA-01925: Maximum of 30 enabled roles exceeded
This error occurs when installing a repository or a target schema.
Cause: The maximum number of enabled roles in the database has been exceeded. When you create a repository or a target schema, new roles are created in the database assigned to the schema in question. When the number of roles exceeds the value of the MAX_ENABLED_ROLES parameter, this error occurs.
Action: Increase the value of the MAX_ENABLED_ROLES parameter in the init.ora file. When you deinstall a repository or a target schema, delete the associated roles as well.
INS0009: Unable to connect to the database. Verify the connect information.
This error occurs when you try to connect to a database.
Cause: See the cause for ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.
Action: Follow the instructions for ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.
INS0022: A spawned program error.
Cause: This error message can result from a server issue when installing Warehouse Builder run-time components on an HP-UX operating system.
Action: To identify the server issue, complete the following steps:

  1. From SQL*Plus, connect to a SYS user.

    Create user test_lj identified by test_lj;
Grant connect, resource to test_lj;

  2. Create OWB_HOME/owb/bin/unix/test.sh with the following contents:

    ../unix/loadjava -thin -verbose -order -resolve -user 
'test_lj/test_lj@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hpdgpa3)(PORT=1522))(CONNECT_DATA=(SERVICE_NAME=dgpadw)))' 
../../lib/int/rtpserver.jar

  3. Change directory to OWB_HOME/owb/bin/unix/.

  4. Run test.sh.

ORA-12154: TNS: Could not resolve service name.
This error occurs when you try to connect to a database.
Cause: You defined a Warehouse Builder location and specified connection information using SQL*Net. However, the required TNS name is not accessible.
Action: To set up a TNS name for use during deployment in general and for execution of mappings and process flows, the TNS name needs to be accessible from the OWB_HOME being used to run the control center service. To ensure access, run the Net Configuration Assistant from the OWB_HOME and then restart the control center service.

To set up a TNS name for use by database links, the TNS name needs to be accessible from the database server home. To ensure access, run the Net Configuration Assistant from the database server home.

Cause: See the cause for ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.
Action: Follow the instructions for ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.
ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.
This error occurs when you try to connect to a database.
Cause: If you used Oracle Net Easy Configuration or Oracle Net Assistant to create the Net Service Name entry, and you used the default option (Service Name) on the newly created Net Service Name, then the parameter SERVICE_NAME is added to the TNSNAMES.ORA as a subclause to the CONNECT_DATA section in the Net Service Name entry. This replaces the (SID=SIDname) subclause in previous releases of the database, for example, Oracle Database8i (8.1.x).
Action: Implement the TNSNAMES.ORA file as follows:

  1. Use the GLOBAL_DBNAME parameter in the LISTENER.ORA for each SID that you want to identify as a separate service. Use the value of this parameter as the value of the SERVICE_NAME parameter. You need to activate any changes that you make to LISTENER.ORA for this purpose by stopping and restarting the listener process.

  2. Use the values of the parameters that exist in the INIT.ORA, namely SERVICE_NAMES and DB_DOMAIN, to determine the value of the SERVICE_NAME that you must use in TNSNAMES.ORA. The valid construction of this value is SERVICE_NAMES.DB_DOMAIN with the period separating the two INIT.ORA values. If your SERVICE_NAMES is BIKES and your DB_DOMAIN is COM, then your SERVICE_NAME is BIKES.COM.

  3. If there is no DB_DOMAIN parameter set in your INIT.ORA, or if there is no GLOBAL_DBNAME in the LISTENER.ORA, then you can use the SERVICE_NAMES from the INIT.ORA in your TNSNAMES.ORA for the SERVICE_NAME parameter.

    For example, if INIT.ORA contains SERVICE_NAMES = "TEST817" and db_domain is not set, then the TNSNAMES.ORA entry is: CONNECT_DATA =(SERVICE_NAME = "TEST817")).

  4. If you have multiple values specified in the SERVICE_NAMES parameter in the init.ora, then you can use one of them. If SERVICE_NAMES is not set, then you can use DB_NAME.DB_DOMAIN parameters from the INIT.ORA file.

  5. If SERVICE_NAMES and DB_DOMAIN is not set in the INIT.ORA and there is no GLOBAL_DBNAME in the LISTENER.ORA, then your SERVICE_NAME in TNSNAMES.ORA file is DB_NAME.

PL/SQL: ORA-04052: Error occurred when looking up remote object
This error occurs when you have upgraded to <Oracle Database version> and are trying to redeploy mappings without first redeploying connectors.
Cause: While upgrading Oracle Database, you moved your database to a new computer. Your old and new database instances do not have the same domain name. You can verify the cause by logging in to SQL*Plus as a SYS user and entering the following command: SELECT * FROM GLOBAL_NAME; If the Global Name of the old database does not match that of the new database, then a domain mismatch is causing this error.
Action: Either add the domain name to the Global Name in your new database by issuing a command similar to the following statement: ALTER DATABASE RENAME GLOBAL_NAME TO xxx10G.US.ORACLE.COM; or redeploy your connectors.

Refer to Oracle Warehouse Builder User's Guide for information on deploying connectors.

IMP-00003: ORACLE error 30371 encounteredORA-30371: column cannot define a level in more than one dimension
This error occurred when you were importing your target schema during migration.
Cause: The Warehouse Builder target schema is created with the select_catalog_role privilege. If you have the same dimension object defined in multiple Warehouse Builder target schemas, then Oracle Export creates duplicates in the export file, and this error occurs when you import.
Action: Connect as a SYS user to the existing version of the Oracle Database from which you exported the target schemas. Enter the following statement in

SQL*Plus: revoke select_catalog_role from OLD_Target_Schema;

Export the target schema into an Oracle .DMP file again, and then import the file into Oracle Database.

Unable to connect to SQL*Plus in <Oracle Database version>
Cause: Your Oracle home or Path is not set correctly, or your Net Service Names are not configured.
Action: Ensure your Oracle home and Path are set correctly, and your Net Service Names are configured in Oracle Database.

  • Ensure that ORACLE_HOME and PATH are set correctly. Your Oracle home directory must to point to the OWB_HOME. Set your PATH variable to include the OWB_HOME\bin directory before any other Oracle products.

  • Ensure that the TNSNames.ora file is configured correctly:

    For Windows, from Oracle Database program group, start Net Configuration Assistant and select Local Net Service Name Configuration to configure TNSNames.ora.

    For UNIX, set ORACLE_HOME and PATH to the OWB_HOME for Warehouse Builder 11g Release 2 (11.2), then run OWB_HOME/bin/netca to start Net Configuration Assistant. Select Local Net Service Name Configuration to configure TNSNames.ora.

ORA-04020 deadlock detected while trying to lock object or ORA-04021 timeout occurred while waiting to lock object
When creating run-time objects, the Run-Time Assistant halts and produces these errors in the error log when trying to lock sys.dbms_aq.
Cause: User sessions may be pinning Advanced Queue objects.
Action: First, log into SQL*Plus as a SYS user and run a query to identify which user sessions are pinning the Advanced Queue packages, using the following query as an example: 
column s.sid format a5;
column s.serial# format a8;
column s.username format a10;
column objectname format a10;
select distinct
 s.sid,
 s.serial#,
 s.username,
 x.kglnaobj as objectname
from
 dba_kgllock l,
 v$session s,
 x$kgllk x
where
 l.kgllktype = 'Pin' and
 s.saddr = l.kgllkuse and
 s.saddr = x.kgllkuse and
x.kglnaobj in ('DBMS_AQ', 'DBMS_AQADM');

The following is an example of the output you may receive:

SID    SERIAL# USERNAME  OBJECTNAME
---    ------- --------  ----------
9      29623  RTU_4942   DBMS_AQ

Noting the SID and Serial Number, issue the following command to kill the user sessions:

ALTER SYSTEM KILL SESSION 'SIDNoted, SerialNumberNoted';

For example, enter the following command to kill the session listed in the sample output for this error:

ALTER SYSTEM KILL SESSION '9,29623';

ORA-04088: error during execution of trigger 'DVSYS.DV_BEFORE_DDL_TRG'
Cause: When you attempt to create a Warehouse Builder repository on an Oracle Database that includes the Database Vault option, you may encounter an error such as ORA-04088.
Action: Disable the triggers DV_BEFORE_DDL_TRG and DV_AFTER_DDL_TRG.
Import wizard throws error ORA-00997 when importing a table.
Cause: When you import table definitions from an Oracle Database, you may encounter an error such as "Repository Error Message: ORA-00997: illegal use of LONG datatype...". This occurs when the CURSOR_SHARING parameter is set to FORCE or SIMILAR.
Action: Set the database parameter CURSOR_SHARING to EXACT.
DPF-0029: Source <Table_Name> must have less than 165 attributes
Cause: Creating data profiling on a table having more than 165 columns.
Action: Select a subset of columns from the table for profiling, by defining an attribute set. This is a data profiling restriction.

Troubleshooting Other Installation Problems

This section includes causes and actions for the following installation problems:

Causes and Actions

Warehouse Builder Clients that Previously Launched Now Momentarily Display the Splash Screen and Fail to Start
Cause: If you attempt to start a Warehouse Builder client such as the Design Center and the splash screen displays momentarily but the client fails to start, you may have overwritten required java objects during the subsequent installation of another software product.

If the client is installed on Windows and you launched the client from the Start menu, you may not see any error messages.

Action: Manually start the client by typing at the DOS prompt run OWB_HOME\owb\owbclient.bat. You are likely to encounter an error message such as No fonts were found in '<drive>:\Program Files\ Qarbon\viewlet Builder3jre\lib\fonts'.
Newly Installed Warehouse Builder Clients Fail to Start and Previously Launched Oracle Products Fail to Start
Cause: After installing Warehouse Builder software, an error in the path variable can prevent you from launching Warehouse Builder clients and other Oracle products that previously launched without problems.
Action: Verify the that the path for OWB_HOME\bin is listed correctly in the Environmental Variables.
A Warehouse Builder Client Freezes or Hangs
Cause: Client software may freeze or hang due to various causes.
Action: If a Warehouse Builder client appears to freeze or hang, perform a stack trace as follows:

  1. At the DOS command prompt, enter:

    cd OWB_HOME\owb\bin\win32\

  2. Run owbclient.bat.

  3. When the program hangs, press Ctrl+Break.

    This produces the thread-dump. Contact Oracle Support and provide them with this information to help identify the problem.

Checking Java Virtual Machine (JVM)

To check, verify, or reinstall the Java Virtual Machine (JVM) server in the database, refer to My Oracle Support:

  1. In your Web browser, go to the following URL: http://metalink.oracle.com.

  2. Log into My Oracle Support, or register as a new user.

  3. Enter the following terms into the Search field, separating each term by semicolons):

    INITJVM.SQL; INSTALL; JAVAVM; JVM; VERIFY; SERVER; INSTALL; CLEANUP

  4. Press Enter.

This search returns the cleanup notes for the JVM. The number of available documents frequently changes because Oracle Support creates, merges, and deletes various cleanup notes. This string of search words returns the most current and pertinent documents.

Generating Log Files for a Specific Warehouse Builder Component

If Warehouse Builder is producing errors or exhibiting other unexpected results, additional error logging can help you and Oracle Support identify the cause.

For additional error logging:

  1. At the command prompt, navigate to:

    For Windows, OWB_HOME\owb\bin\win32

    For UNIX, OWB_HOME/owb/bin/unix

  2. Run one of the execution files and pipe the output to a log file.

    For example, enter: owbclient.bat 1>out.log 2>error.log

  3. Examine the resulting log file.

    Use this log when contacting Oracle Support.

Checking the System Path of Oracle Warehouse Builder

You must ensure that Oracle Universal Installer added the bin directory of the new Oracle Warehouse Builder 11.2 installation to the system path ahead of other Oracle product bin directories. This is easily checked using the command prompt.

To verify the system path for Oracle Warehouse Builder on Windows:

  1. In the Command Prompt window, enter path.

    C:\>path

  2. The system returns the value of the path variable; verify that C:\OWB112 precedes other Oracle products.

    PATH=C:\OWB112\bin;C:\oracle\product\11.2.0\db_1\bin; ... \

To verify the system path for Oracle Warehouse Builder on Linux:

  1. Echo the PATH variable in your shell.

Configuring OWB for RAC

When installing Oracle Warehouse Builder on a RAC cluster, the RAC service names must be unique and match the node that they're running on. This ensures that the Control Center Service uses a database service on the correct node, which in turn ensures access to the correct file system.

For example, the wb_rt_service_nodes should be similar to those in Table A-1.

Table A-1 Naming RAC Service Nodes

Node Instance Host Port Service Name

1

1

host_1

port_number_1

RACSRVC_1

2

2

host_2

port_number_2

RACSRVC_2

3

3

host_3

port_number_3

RACSRVC_3

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us