D
Diagnostics and Debugging

This appendix contains reference information to use in the event that you encounter errors or problems with your installation. This appendix includes the following topics:

D.1 Debugging

This section includes the following topics:

D.1.1 Log File Locations

Warehouse Builder Repository Assistant:
ORACLE_HOME\owb\reposasst\log.txt.0
Warehouse Builder Runtime Assistant:
ORACLE_HOME\owb\rtasst\log.txt.0
Warehouse Builder Browser Assistant:
ORACLE_HOME\owb\browserasst\owbb_browser_install_log.txt.0
Warehouse Builder Runtime Platform Service:
Server side ORACLE_HOME\owb\log\Runtime_Repository_Name\log.0
Warehouse Builder Client: You specify the location in the Preferences screen.

D.1.2 Oracle9i Warehouse Builder is Frozen, or Hanging

If Warehouse Builder appears to be frozen or hanging, perform a stack trace as follows:

At the DOS command prompt, enter:
cd ORACLE_HOME\owb\bin\win32\
Run owbclient.bat.
When the program hangs, press Ctrl+Break.

This produces the thread-dump. This information will help Oracle Support to identify the problem.

D.1.3 Additional Error Logging for Errors and Other Unexpected Behavior

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

For additional error logging:

At the command prompt, navigate to:
Run one of the following execution files and pipe the output to a log file (for example, owbclient.bat > owbclient.log):

Oracle9i Warehouse Builder Browser Assistant

For Windows: browserinst.bat

For UNIX: browserinst.sh

Oracle9i Warehouse Builder Client

For Windows: owbclient.bat

For UNIX: owbclient.sh

Oracle9i Warehouse Builder Design Browser

For Windows: openDB.bat

For UNIX: openDB.sh

Oracle9i Warehouse Builder MDL File Upgrade Utility

For Windows: mdlconvertui.bat

For UNIX: mdlconvertui.sh

Oracle9i Warehouse Builder OMB Plus

For Windows: OMBPlus.bat

For UNIX: OMBPlus.sh

Oracle9i Warehouse Builder Repository Assistant

For Windows: reposinst.bat

For UNIX: reposinst.sh

Oracle9i Warehouse Builder Runtime Assistant

For Windows: runtimeinst.bat

For UNIX: runtimeinst.sh

Oracle9i Warehouse Builder Runtime Audit Browser

For Windows: openRAB.bat

For UNIX: openRAB.sh

Start Local RTP Service

For Windows: Run the script ORACLE_HOME\owb\bin\win32\local_service_login.bat with -startup ORACLE_HOME as the parameter

For UNIX: local_service_login.sh -startup ORACLE_HOME

Start Oracle9i Warehouse Builder OC4J Instance

For Windows: startOwbbInst.bat

For UNIX: startOwbbInst.sh

Stop Local RTP Service

For Windows: Run the script ORACLE_HOME\owb\bin\win32\local_service_login.bat with -closedown ORACLE_HOME as the parameter

For UNIX: local_service_login.sh -closedown ORACLE_HOME

Stop Oracle9i Warehouse Builder OC4J Instance

For Windows: stopOwbbInst.bat

For UNIX: stopOWBBInst.sh
Examine the resulting log file.

Use this log when contacting Oracle Support.

D.1.4 Checking Java Virtual Machine (JVM)

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

In your Web browser, go to: http://metalink.oracle.com.
Login to Oracle Metalink, or register as a new user.
Type the following terms into the Search field (note that they are separated by semicolons):
INITJVM.SQL; INSTALL; JAVAVM; JVM; VERIFY; SERVER; INSTALL; CLEANUP
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 will return the most current and pertinent documents.

D.1.5 Managing the Runtime Platform Service

The Runtime Platform Service is managed automatically by the Oracle Database Server. However, if you need to manually start and stop the service, use the scripts provided with your Warehouse Builder installation for that purpose.

The scripts are in the ORACLE_HOME\owb\rtp\sql directory. To run any of these scripts manually, log on to the Runtime Platform as the Runtime Repository owner. The scripts include:

start_service.sql: Use this to start the Runtime Platform Service
stop_service.sql: Use this to stop the Runtime Platform Service
show_service.sql: Use this to check whether the Runtime Platform Service is available.
service_doctor.sql: Use this to check the install status of the Runtime Platform Service components.

To manually start, stop, and check the Runtime Platform Service:

Log on to the Runtime Platform as the Runtime Repository owner.
Run the required script:

To start the Runtime Platform Service: Run the
ORACLE_HOME\owb\rtp\sql\start_service.sql script.

To stop the Runtime Platform Service: Run the
ORACLE_HOME\owb\rtp\sql\stop_service.sql script.

To check whether the Runtime Platform Service is available: Run the
ORACLE_HOME\owb\rtp\sql\show_service.sql script.

To check the install status of the Runtime Platform Service components: Run the
ORACLE_HOME\owb\rtp\sql\service_doctor.sql script.

D.1.6 Detecting Database Server Issues When Installing on HP-UX

It is possible that when you install Warehouse Builder Runtime components on an HP-UX operating system, the following error occurs: INS0022: A spawned program error. This may be a database server issue.

To identify the database server issue:

From SQL*Plus, connect to a SYS user.

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

Create ORACLE_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

Change directory to ORACLE_HOME/owb/bin/unix/.
Run test.sh.

D.2 Diagnostics

This section includes the following topics:

SYS user does not have SYSDBA privileges.

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 above 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 statement connect sys/<<sys_password>>@TNS_NAME_OF_DB as sysdba; will fail. In this case, you have the following options:

Re-configure your database with
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and create a password file if none exists.
If the above is not an option, re-configure your database with
O7_DICTIONARY_ACCESSIBILITY=TRUE.
With this setting, connect sys/<<sys_password>>@TNS_NAME_OF_DB will work, which allows Warehouse Builder Assistants to connect to SYS user.

INS0034: The Database Server needs to be configured by running Runtime Repository option locally.

You can encounter this message when running Oracle9i Warehouse Builder Runtime Assistant.

Cause: You do not have a database server local to the machine on which you are running Oracle9i Warehouse Builder Runtime Assistant.

Action: Run the Oracle9i Warehouse Builder Server Side installation on the machine where your Oracle database server is located and then launch the Runtime Assistant.

ORA-04021: Timeout occurred while waiting to lock object SYS.DBMS_AQADM.

You encounter this error when running the Runtime Repository Assistant. There are two possible resolutions to this issue.

Cause: The Runtime Assistant grants 'Execute' privileges on the SYS user dbms_aq packages to the Runtime Repository users being created. The database server waits for a lock on the dbms_aq package before it can apply this grant. If the package is in use by another user, the Runtime Repository will encounter error ORA-04021 from the database server.

Action: Using Oracle Enterprise Manager, connect to the database server and identify the session that is using the dbms_aq. Exit the application that is holding the lock and then recreate a new set of Warehouse Builder Runtime Repository users.

Action: Wait until the application holding the lock finishes running.

From SQL*Plus, connect as SYS user and execute the following SQL statements:

grant execute on sys.dbms_aq to scott;

grant execute on sys.dbms_aqadm to scott;
When the above statements are successful, execute the following SQL statements:

revoke execute on sys.dbms_aq from scott;

revoke execute on sys.dbms_aqadm from scott;
Recreate a new set of Warehouse Builder Runtime Repository users.
Restart the Runtime Platform Service by running the ORACLE_HOME\owb\rtp\sql\start_service.sql script.

API5022: Cannot Connect to the Specified Repository

This error occurs when you try to connect to the Design 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 Design Repository schema if the repository owner has no SELECT privilege on SYS.V_$SESSION. You can diagnose the cause as follows:

In SQL*Plus, connect to the Warehouse Builder Design 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:
```
show errors;
```
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:

In SQL*Plus, connect as the SYS user.

At the SQL prompt, enter the following command:

grant select on V_$SESSION to Warehouse Builder_Repository_Owner;

Connect to the Design_Repository_Owner.

Enter the following command at the SQL prompt:

alter package NAMESPACESERVICEIMPL compile;

Oracle9i Warehouse Builder Runtime 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.

You encounter an error when specifying a SYSDBA user.

Oracle9i Warehouse Builder Assistants require you to provide SYSDBA credentials when installing the Oracle9i Warehouse Builder Design Repository or Runtime 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 above 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 statement
connect sys/sys_password@TNS_NAME_OF_DB as sysdba; will fail. In this case, you have two options.

Action: Re-configure your database with
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and create a password file if none exists.

Action: If the above is not an option, re-configure your database with
O7_DICTIONARY_ACCESSIBILITY=TRUE. With this setting, the statement
connect sys/sys_password@TNS_NAME_OF_DB will work, which allows the Warehouse Builder Assistants to connect to SYS user.

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

From your ORACLE_HOME, start the Name and Address Server:

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

For UNIX: Run owb/bin/unix/NASTART.sh.
Open the log file: owb\bin\admin\NASvr.log.

The log should contain 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.
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.

Lineage and impact analysis reports: Extensive tablespace requirements for materialized views.

The first time you refresh a materialized view, it is populated from the Oracle9i Warehouse Builder repository. The materialized view can occupy up to twice the amount of space allocated to the entire Warehouse Builder Runtime Repository.

Action: If the Warehouse Builder Runtime 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.

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 of 384MB, 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 OWB 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:

Exit Warehouse Builder.
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.
Change the -Dlimit parameter to 334.
Save and close the file.
Restart Warehouse Builder.

ORA-01925: maximum of 30 enabled roles exceeded

This error occurs when you are installing a Design Repository, a Runtime Repository, a Target Schema, or a Runtime User.

Cause: The maximum number of enabled roles in the database has been exceeded. When you create a Design Repository, Runtime Repository, Target Schema, or a Runtime User, 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 Design Repository, Runtime Repository, Target Schema, or Runtime User, delete the associated roles as well.

java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path

Internal Server Error
java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path

at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1349)

at java.lang.Runtime.loadLibrary0(Runtime.java:749)

This error occurs in the Repository Selection page of the Runtime Audit Browser (Oracle9iAS-integrated version) when you try to view reports for a Runtime Repository using a Net Service-based database link.

Cause: The OWB Browser OC4J instance is not configured with the correct additional environment variable.

Action: Ensure that you have followed all the steps in Chapter 2, "Installing Oracle9i Warehouse Builder Components".

Internal Server Error

This is a Runtime Audit Browser Portlet Error returned by the listener.

Cause: This can occur if your Warehouse Builder Runtime Audit Browser portlet provider is not working because of your Data Source definition or your portlet provider definition.

Action: Check whether the Warehouse Builder Runtime Audit Browser portlet provider is working at the following URL:

http://hostname:port_number/owbb/providers/

For example:

http://dwlin12.us.oracle.com:7778/owbb/providers/

The following text should display:

"Congratulations! You have successfully reached your Provider's Test Page." 
Checking for components: 
Portlets are: 
Warehouse Builder Runtime Audit Browser

Verify your Data Source definition for the following regardless of whether you see the above text:

For Oracle9iAS Release 2 (9.0.2) only: Remove uix2.jar and shar.jar from the Default application library path as described in Chapter 2, "Installing Oracle9i Warehouse Builder Components".
The Warehouse Builder Data Source must be defined with the OWBB application, and not the Default application.
For Data Source Class, use com.evermind.sql.OrionCMTDataSource for the Oracle Data Source.
Check your JDBC URL. Typically if you use something like "jdbc:oracle:thin:@dwlin12:1521:iasdb", you will be using JDBC thin driver, and "iasdb" can only be an existing SID, not Service Name. Also note there is a colon preceding "@" sign. If you must use Service Name in the JDBC URL, try a full TNS string such as "(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = dwlin16)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = ora920.us.oracle.com) ) )"
If you make any changes to your Data Source definition, or if you re-deploy the application, you must restart the application.
Check your portlet provider definition. Make sure it is defined exactly as instructed in Chapter 2, "Installing Oracle9i Warehouse Builder Components".
Check your OC4J log under the Oracle Portal ORACLE_HOME. For example, a typical path on UNIX for a deployed OWBB application named OWBB is /usr/iasv2_portal/j2ee/owbb/log/owbb_default_island_1:

default-web-access.log

global-application.log

jms.log

rmi.log

server.log

INS0009: Unable to connect to the database. Verify the connect information.

See ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.

ORA-12154: TNS: Could not resolve service name.

See 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 the Net8 Easy Configuration or Net8 Assistant tools to create the Net Service Name entry, and you used the default option (Service Name) on the newly created Net Service Name, 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 the previous versions of Oracle8.

Action: Implement the TNSNAMES.ORA file as follows:

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 will need to activate any changes you make to LISTENER.ORA for this purpose by stopping and restarting the listener process.
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_DOMAI is COM, then your SERVICE_NAME is BIKES.COM.
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")).
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.
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.

D Diagnostics and Debugging