6 Troubleshooting a Warehouse Builder Installation

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, 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:

C:\Oracle\My_OWB_Home\>

then the text you type is:

C:/Oracle/My_OWB_Home

• 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.

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.

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;
   
   

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

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.

1. From your owb home, start the Name and Address Server:

   For Windows: Run owb\bin\win32\NAStart.bat.

   For UNIX: 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, verify that you have extracted the regional library data to the correct location. If you have extracted the data to the wrong location, 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, 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 wish, because it is automatically started at the execution of any mapping that employs the Name and Address operator.

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.

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.

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 you make to LISTENER.ORA for this purpose by stopping and restarting the listener process.

2. Use the values of the parameters existing 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, 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 be DB_NAME.

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 the 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 the 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 1 (11.1), then run owb home/bin/netca to start Net Configuration Assistant. Select Local Net Service Name Configuration to configure TNSNames.ora.

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 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, type the following to kill the session listed in the sample output for this error:

ALTER SYSTEM KILL SESSION '9,29623';

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.