Troubleshooting Guide

Prerequisite or related product issues

This section details errors that occur with products that are installed and configured with the Data Warehouse Center.

A DataJoiner Version 2 CREATE SERVER MAPPING statement for an Oracle data source fails

DataJoiner Version 2 CREATE SERVER MAPPING SQL statements fail on a workstation that has the Data Warehouse Center installed.

You might receive the message DB2SYSC.EXE -- Ordinal not found or one that implies that the SERVER MAPPING failed because it could not load the SQL*NET data access module.

Cause

The CREATE SERVER MAPPING statement fails because DataJoiner accesses the ORA73.DLL file that is provided with the Data Warehouse Center instead of the ORA73.DLL file in the ORANT\BIN directory. This condition occurs because DataJoiner looks for the Oracle DLL through the Path system variable. The system path is updated during a Data Warehouse Center installation so that it includes a directory containing a ORA73.DLL file that is provided by the Data Warehouse Center.

Action

Update the Path system variable. Ensure that the directory that contains the Oracle ORA73.DLL file (in ORANT\BIN) is specified first in the path (before the VWSWIN\IWH\ODBC32 directory).

Unable to connect to a DB2 database from a Windows NT or Windows 2000 agent site

You are unable to access a DB2 source database, target database, or warehouse control database from a Windows NT or Windows 2000 agent site.

Cause

There are several reasons why you might have this problem:

Your DB2 client is configured incorrectly.
Your warehouse control database is not registered as an ODBC system DSN on your warehouse server and on your Data Warehouse Center administrative interface workstation.
Your source database and target database are not registered as ODBC system DSNs on your agent site workstation.
Your TCP/IP service is not started, or TCP/IP connectivity problems exist.

Action

Try the following solutions:

Verify that the workstation name is entered as NNAME in your DB2 client database manager configuration.

Ensure that the node and database are cataloged correctly, as follows:

Verify that the DB2 client catalog:	Matches the host DB2 catalog:
node	`NNAME`
host name	TCP/IP host name
service name	SVCENAME of the database manager host configuration
database name	database name

Ensure that the DB2 security service is started correctly and that the DB2 service is started correctly. Check the DB2DIAG.LOG file in your DB2 installed directory for any startup errors.
Verify that your warehouse control database is registered as an ODBC system DSN on your warehouse server workstation and all your Data Warehouse Center administrative interface workstations.
Verify that your source database and target database are registered as ODBC system DSNs on your agent sites.
Ensure that the TCP/IP service is started at both the client and host. To do this, check the Services application of the Control Panel program group on both workstations.
Verify TCP/IP connectivity. Ensure that all cables are connected, that the TCP/IP service is started on both workstations, and that the LAN is functioning.
If these configurations are correct, ping the server workstation from the client workstation command prompt.
If the ping command succeeds, ensure that the server's DB2COMM environment variable is set to TCPIP.
If the ping command fails:
- Verify that the server and the client have the same entry for the server TCP/IP port number in the TCP/IP SERVICES file.
- Ensure that the entries for the DB2 server in the client SERVICES file and the server SERVICES file do not contain tab characters.
- Ensure that the DB2 server recognizes the port number. If not, update the DB2 server configuration:
  1. Enter the following command from the DB2 Command Line Processor:
```
update dbm cfg using svcename your-svc
```
    where your-svc is the server's SERVICE name from the SERVICES file.
  2. Stop and restart DB2.
- If you do not have a domain name server, verify that the TCP/IP host name is entered in the client TCP/IP HOSTS file for the server workstation.
- If you have a domain name server, or an entry for the server in the TCP/IP HOSTS file, select the network icon in the Client NT workstation Control Panel. Verify that the TCP/IP configuration is correct. If it is correct, click the DNS push button and verify that the host and domain names are correct.

Cannot connect to an ODBC data source on UNIX

Cause

If an ODBC connection type is selected, ODBC uses the data source name and the required attributes in the .odbc.ini file. This control file must reside in the home directory of the user ID that is used to start the warehouse agent process.

Action

Verify that the .odbc.ini file is in the correct directory. You can find the user ID that is used to start the warehouse agent process on the Parameters page of the Agent Site notebook.

Also verify that the data source is defined correctly in the .odbc.ini file.

Unable to use TCP/IP to connect to AS/400 from Windows NT or Windows 2000

You are trying to use TCP/IP to connect to the AS/400 from a DB2 Connect for Windows NT or Windows 2000 workstation.

Cause

This configuration is not supported.

Action

Try connecting with TCP/IP from a client workstation to the DB2 Connect for Windows NT or Windows 2000 workstation, and then to the host using APPC. For more information, run the following trace on the DB2 Connect for Windows NT or Windows 2000 workstation:

At a command prompt, enter:
```
db2trc on -1 8000000
```
Reproduce the problem.
At a command prompt, enter:
```
db2trc dmp db2.trc
```
To turn off the trace, at a command prompt, enter:
```
db2trc off
```

Connecting to a Sybase source fails

You are trying to connect to a Sybase warehouse source (to import table definitions or run a step), and receive an error indicating that the Sybase Open Client Context failed.

Cause

This error can occur because of problems with the environment in which the warehouse agent runs.

Action

Verify that the warehouse agent and the Sybase client do not have conflicting language environment settings. Also, if you are using a Windows NT or Windows 2000 agent, run the warehouse agent daemon or warehouse server (if you are using the default agent) as a user process instead of a system process.

To verify and change the language environment settings:

Click Start --> Settings --> Control Panel.
Double-click the System icon.
Click the Environment tab.
Update the system environment settings by removing (or renaming) the LANG system environment variable.
For the AIX and Solaris Operating Environment agents, verify that the values specified in the LANG and LC_ALL environment variables are defined in all applicable sections of the locale.dat file (for example, [SUN] and [SUN_SRV4]). Make sure that the locale=xx_xxx entry is before the locale=C,.... entry in this file.
You can find the environment variables in /usr/lpp/db2_07_01/bin/IWH.environment or /opt/IBMdb2/V7.1/bin/IWH.environment.
Verify that the SYBASE system environment variable points to the correct directory.
Click OK.

To run a Windows NT warehouse agent daemon or the warehouse server as a user process:

Click Start --> Settings --> Control Panel.
Double-click the Services icon.
The Services window opens.
Select the warehouse agent daemon or warehouse server.
Click Startup.
The Service window opens.
Click This Account in the Log On As area.
Type a valid user ID in the This Account field.
Type the password in the Password and Confirm Password fields.
Click OK.
The Service window closes.
In the Services window, click Close.
Restart the workstation that runs the warehouse agent daemon or warehouse server.

To run a Windows 2000 warehouse agent daemon or the warehouse server as a user process:

Click Start --> Settings --> Control Panel --> Administrative Tools --> Services .
The Services window opens.
Right-click the warehouse agent daemon or warehouse server and click Properties.
Click the Log on tab.
Select a Windows 2000 user on behalf of which the service should run.
Click OK.
In the Services window, click Close.
Restart the workstation that runs the warehouse agent daemon or warehouse server.

FTP log displays "NAMEFMT not a valid command"

Cause

This message is displayed if the FTP server system does not support the NAMEFMT command. The NAMEFMT command is an AS/400-specific FTP subcommand.

Action

It is normal for this message to be displayed. You can ignore it.

The warehouse server or warehouse agent is unresponsive when using ODBC drivers that were purchased separately

You are using ODBC drivers that you purchased separately from the Data Warehouse Center, and the warehouse server or warehouse agent is unresponsive.

Cause

Many times, ODBC drivers other than those provided with the Data Warehouse Center produce an informational, warning, or error message when a user or application connects to one of its sources. Because the Data Warehouse Center runs as a background system process, no message is displayed. However, the ODBC driver is waiting for a user response to the message.

Action

If you are experiencing these symptoms when using the Data Warehouse Center, use the ODBCTEST tool to test the connection. Connect to the ODBC source by entering the following command on a command line:

ODBCTEST <system dsn name> <odbc user ID> <password>

where <odbc user ID> is the ODBC user ID to use to connect to the database and <password> is the password for the ODBC user ID.

The ODBCTEST tool writes messages to the command window. If any ODBC-related messages appear, address the situation as described in the ODBC message, or use the ODBC drivers that come with the Data Warehouse Center.

[ Top of Page | Previous Page | Next Page ]