Refer to this chapter in the event that you encounter errors or problems with an installation. This chapter includes the following topics:
Take the following steps to troubleshoot errors in Warehouse Builder:
Review this chapter 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 Installation Problems That Do Not Display Error Messages".
Check for additional information about the problem by "Inspecting Logs Files in Warehouse Builder".
If the problem remains unresolved, search for a possible solution at
Review the Oracle Warehouse Builder Release Notes for installation notes or known issues.
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".
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:
When you run the Oracle Universal Installer to install Warehouse Builder, the installation error logs are automatically stored in:
When you run the Warehouse Builder Repository Assistant, the workspace installation error logs are stored in:
See "Error Messages Related to Installation" for suggested actions for commonly encountered errors during installation.
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.
If you are importing design metadata using the Warehouse Builder Transfer Wizard, then you can view the log file after the import is complete. Warehouse Builder displays the My Metadata Transfer dialog box.
Click View Log File to view the log file, as shown in Figure 6–1. Click Save As to save the log file to your local system.
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, as shown in Figure 6–2.
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 Explorer, select View from the menu bar, and then click Validation Messages. The messages are displayed in the Validation Results window.
After you generate scripts for Warehouse Builder objects, the Generation Results window displays the generation results and errors, as shown in Figure 6–3. 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.
You can store execution or deployment error and warning message logs on your local system by specifying a location for them. In the Project Explorer, 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_ORACLE_HOME\log\Repository_Name\log.xx on the Oracle Database server.
Errors related to transforming or loading data are stored the runtime 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.
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:
If your Name and Address server is enabled in:
then it produces the log file
This section includes the following topics:
OWBSYS is not granted access to OWB_ORACLE_HOME/owb/bin/admin/rtrepos.properties: Please run UnifiedRepos/reset_owbcc_home.sql specifiying the path of the Oracle home from which the Control Center Service is being run.
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_ORACLE_HOME directory. On Windows, to determine the correct path for the
OWB_ORACLE_HOME directory, examine the path displayed as part of the default Windows command prompt, and replace the backslashes with Unix-style forward-slashes. Do not supply a trailing slash. For example, if the Windows command prompt is:
then the text you would enter is:
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE. You can verify the credentials by issuing the following connect statement:
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.
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
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.bat as appropriate. Use this script as follows:
local_service_login.sh [-startup | -closedown] OWB_ORACLE_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.
NAMESPACESERVICEIMPLmay be invalid. This occurs after a database export or import from the Warehouse Builder repository schema if the repository owner has no
SYS.V_$SESSION. You can diagnose the cause as follows:
In SQL*Plus, connect to the Warehouse Builder repository schema.
Enter the following command at the SQL prompt:
ALTER PACKAGE NAMESPACESERVICEIMPL compile body;
If Warning: Package body altered with compilation errors appears, enter the following command at the SQL prompt:
The following errors mean that the Warehouse Builder repository owner has no
SELECT privilege on
PL/SQL: SQL statement ignored PLS-00201: Identifier 'SYS.V_$SESSION' must be declared
In SQL*Plus, connect as the
At the SQL prompt, enter the following command:
grant SELECT on V_$SESSION to Warehouse Builder_Repository_Owner;
Connect to the
Enter the following command at the SQL prompt:
alter package NAMESPACESERVICEIMPL compile;
SYSDBAcredentials. You can verify this from SQL*Plus by issuing the following connect statement:
In a standard database installation, the preceding connect statement works because
EXCLUSIVE and the default password file is created by the installation process.
If your database is configured with
NONE, then the following statement fails:
In this case, you have two options.
EXCLUSIVE and create a password file if none exists.
TRUE. With this setting, the statement
TNS_NAME_OF_DB enables the Warehouse Builder Assistants to connect to
OWB_ORACLE_HOME, start the Name and Address Server:
For Windows: Run
For UNIX: Run
Open the log file:
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
For UNIX: Start the server by running
owb/bin/unix/NAStart.sh. Stop the server by running
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.
Note:To grant permission to an OWB repository user to use Enterprise Manager for performing tasks, enter the following command in SQL*Plus:
-mxparameter in the
-Dlimitparameter in the
owbclient.batfile specifies the memory threshold (80% of Dlimit) at which the Warehouse Builder memory manager begins to assist Java garbage collection. If you change the
-mxparameter value, set the
-Dlimitparameter to the same value, or at least to 90% of the value. Note that setting the
-Dlimitto a low value can have a negative impact on the performance of Warehouse Builder.
-Dlimitparameter in Warehouse Builder as follows:
Exit Warehouse Builder.
Open this file in a text editor:
For Windows: Open the
For UNIX: Open the
-Dlimit parameter to 334.
Save and close the file.
Restart Warehouse Builder.
MAX_ENABLED_ROLESparameter, this error occurs.
MAX_ENABLED_ROLESparameter in the
init.orafile. When you deinstall a repository or a target schema, delete the associated roles as well.
From SQL*Plus, connect to a
Create user test_lj identified by test_lj; Grant connect, resource to test_lj;
/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
Change directory to
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.
SERVICE_NAMEis added to the
TNSNAMES.ORAas a subclause to the
CONNECT_DATAsection 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).
TNSNAMES.ORAfile as follows:
GLOBAL_DBNAME parameter in the
LISTENER.ORA for each SID 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.
Use the values of the parameters that exist in the
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
BIKES and your
COM, then your
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
For example, if
SERVICE_NAMES = "TEST817" and
db_domain is not set, then the
TNSNAMES.ORA entry is:
CONNECT_DATA =(SERVICE_NAME = "TEST817")).
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
DB_DOMAIN is not set in the
INIT.ORA and there is no
GLOBAL_DBNAME in the
LISTENER.ORA, then your
TNSNAMES.ORA file is
SYSuser 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.
ALTER DATABASE RENAME GLOBAL_NAME TO
;or redeploy your connectors.
Refer to Oracle Warehouse Builder User's Guide for information on deploying connectors.
select_catalog_roleprivilege. 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.
SYSuser to the existing version of the Oracle Database from which you exported the target schemas. Enter the following statement in
revoke select_catalog_role from
Export the target schema into an Oracle
.DMP file again, and then import the file into the Oracle Database.
PATH are set correctly. Your Oracle home directory must to point to the
OWB_ORACLE_HOME. Set your
PATH variable to include the
OWB_ORACLE_HOME\bin directory before any other Oracle products.
Ensure that the
TNSNames.ora file is configured correctly:
For Windows: From the Oracle Database program group, start Net Configuration Assistant and select Local Net Service Name Configuration to configure
For UNIX: Set
PATH to the
OWB_ORACLE_HOME for Warehouse Builder 11g Release 1 (11.1), then run
/bin/netca to start Net Configuration Assistant. Select Local Net Service Name Configuration to configure
SYSuser 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;
x.kglnaobj as objectname
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 receive:
SID SERIAL# USERNAME OBJECTNAME
--- ------- -------- ----------
9 29623 RTU_4942 DBMS_AQ
Noting the SID and Serial Number, issue the following command to stop the user sessions:
ALTER SYSTEM KILL SESSION '
For example, enter the following command to stop the session listed in the sample output for this error:
ALTER SYSTEM KILL SESSION '9,29623';
This section includes causes and actions for the following installation problems:
If the client is installed on Windows and you launched the client from the Start menu, you may not see any error messages.
run OWB_ORACLE_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'.
\binis listed correctly in the Environmental Variables.
At the DOS command prompt, enter:
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.
To check, verify, or reinstall the Java Virtual Machine (JVM) server in the database, refer to My Oracle Support (formerly Oracle MetaLink):
In your Web browser, go to:
Log in to My Oracle Support (formerly OracleMetaLink), or register as a new user.
Enter the following terms into the Search field, separating each term by semicolons):
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.
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:
At the command prompt, navigate to:
Run one of the execution files as listed in Table 1-9 and pipe the output to a log file.
For example, enter:
owbclient.bat 1>out.log 2>error.log
Examine the resulting log file.
Use this log when contacting Oracle Support.