T l Data Warehouse - publib.boulder.ibm.com

Tivoli® Data Warehouse

Tivoli Data Warehouse Messages

Version 1.2 (Revised December 2004)

SC09-7776-00

��

Tivoli® Data Warehouse

Tivoli Data Warehouse Messages

Version 1.2 (Revised December 2004)

SC09-7776-00

��

First Edition, online revision 1 (December 2004)

This edition applies to version 1.2 of Tivoli Data Warehouse and to all subsequent releases and modifications until

otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2003, 2004. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

About this guide . . . . . . . . . . . v

What is new in this version of the guide? . . . . v

Who should read this guide . . . . . . . . . v

Publications . . . . . . . . . . . . . . v

Tivoli Data Warehouse publications . . . . . vi

Related publications . . . . . . . . . . vi

Accessing publications online . . . . . . . ix

Ordering publications . . . . . . . . . . x

Contacting customer support . . . . . . . . . x

Conventions used in this guide . . . . . . . . xi

Typeface conventions . . . . . . . . . . xi

Operating system-dependent variables and paths xi

Chapter 1. Identifying a message . . . . 1

Setting the trace level . . . . . . . . . . . 5

Chapter 2. Problem determination tools 7

LogXML Viewer . . . . . . . . . . . . . 7

First Failure Data Capture (FFDC) . . . . . . . 8

Chapter 3. Messages . . . . . . . . . 9

Notices . . . . . . . . . . . . . . 165

Trademarks . . . . . . . . . . . . . . 167

© Copyright IBM Corp. 2003, 2004 iii

||

iv Tivoli Data Warehouse Messages

About this guide

Tivoli® Data Warehouse allows customers to produce cross application reports

from various Tivoli and customer applications. The infrastructure enables a set of

extract, transform, and load (ETL) utilities to extract and move data from Tivoli

application data stores to a central data warehouse database. The architecture of

Tivoli Data Warehouse is documented to allow data from non-Tivoli applications to

be integrated into its central data repository. Customers can then generate

task-oriented data marts from this repository and these data marts can be used to

produce cross application reports.

This guide contains the messages that are generated by each of the Tivoli Data

Warehouse components. For each message, a sample-generated message is

provided as well as a description of the message, and the Administrator Response

to take in response to the message.

What is new in this version of the guide?

This version of the Tivoli Data Warehouse Messages, SC09-7776 is an update of the

guide dated December 2003, which was published in conjunction with Tivoli Data

Warehouse, Version 1.2. This update supersedes previous versions of Tivoli Data

Warehouse Messages, SC09-7776.

This version of the Tivoli Data Warehouse Messages, SC09-7776 contains the

following additions and enhancements to these messages:

v CDWIC0007E

v CDWIC0015E

v CDWIC5207E

v CDWIC0017E

v CDWIC1075W

Changes to this document are indicated by vertical bars in the left margin of the

text.

Who should read this guide

This guide is for administrators and installers who plan for, install, configure, and

maintain Tivoli Data Warehouse.

Administrators and installers should have the following knowledge:

v Basic system administration and file management of the operating systems on

which the components of Tivoli Data Warehouse are installed.

v An understanding of the basic concepts of relational database management.

v Experience administering IBM® DB2® databases.

Publications

This section lists publications in the Tivoli Data Warehouse library and other

related documents.

© Copyright IBM Corp. 2003, 2004 v

|

||||

||

|

|

|

|

|

||

Tivoli Data Warehouse publications

The following documents are available in the Tivoli Data Warehouse library:

v Tivoli Data Warehouse Documentation CD, LK3T-8111

Provides all documents in the Tivoli Data Warehouse library, except for Enabling

an Application for Tivoli Data Warehouse, GC32-0745. All documents are available

in English; selected documents are available in other languages.

v Tivoli Data Warehouse Release Notes, GI11-0857

Provides last-minute information about Tivoli Data Warehouse and lists

hardware requirements and software prerequisites.

v Installing and Configuring Tivoli Data Warehouse, GC32-0744

Describes how Tivoli Data Warehouse fits into your enterprise, explains how to

plan for its deployment, and gives installation and configuration instructions. It

contains maintenance procedures and troubleshooting information. Additionally,

this guide describes how to install warehouse packs and reports.

This document also describes how to install DB2 Universal Database™ and

Crystal Enterprise for use with Tivoli Data Warehouse.

v Tivoli Data Warehouse Messages, SC09-7776

Lists the messages generated by Tivoli Data Warehouse and describes the actions

you should take.

v Enabling an Application for Tivoli Data Warehouse, GC32-0745

Provides information about connecting an application to Tivoli Data Warehouse.

This document is for application programmers who use Tivoli Data Warehouse

to store and report on the data of their application, data warehousing experts

who import Tivoli Data Warehouse data into business intelligence applications,

and customers who create reports.

The Tivoli Data Warehouse information center contains documents from the Tivoli

Data Warehouse library in both PDF and HTML formats. All documents are

available in English; selected documents are available in other languages. The

information center is available online, as described in “Accessing publications

online” on page ix, and on the Tivoli Data Warehouse Documentation CD, LK3T-8111.

The following documents are in the information center:

v Tivoli Data Warehouse Release Notes

v Installing and Configuring Tivoli Data Warehouse

v Tivoli Data Warehouse Messages

Enabling an Application for Tivoli Data Warehouse is available only on the Tivoli Data

Warehouse Support Web site. See “Contacting customer support” on page x for

more information.

Related publications

The following section describes additional publications that can help you

understand and use Tivoli Data Warehouse and its prerequisites.

The Tivoli Glossary

The Tivoli Software Glossary includes definitions for many of the technical terms

related to Tivoli software. The Tivoli Software Glossary is available, in English only,

at the following Web site:

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm

vi Tivoli Data Warehouse Messages

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm

IBM Redbooks

IBM Redbooks™ are developed and published by the IBM International Technical

Support Organization, the ITSO. They explore integration, implementation, and

operation of realistic customer scenarios. The following Redbooks contain

information about Tivoli Data Warehouse:

v Introduction to Tivoli Enterprise Data Warehouse, SG24-6607

Provides a broad understanding of Tivoli Data Warehouse. Some of the topics

that are covered are concepts, architecture, writing your own ETLs, and best

practices in creating data marts.

v Planning a Tivoli Enterprise Data Warehouse Project, SG24-6608

Explains the planning tasks that must be completed before deploying Tivoli Data

Warehouse. The guide shows how to apply these planning steps in a real-life,

warehouse pack implementation using IBM Tivoli Monitoring. It also contains

frequently used Tivoli and DB2 commands and lists troubleshooting tips for

Tivoli Data Warehouse.

Although this book is based on Tivoli Enterprise™ Data Warehouse, Version 1.1,

its concepts apply to Tivoli Data Warehouse, Version 1.2.

Crystal Enterprise publications

The following documents describe how to install, use, and administer Crystal

Enterprise. These documents are available on the Crystal Enterprise 9 CD, which is

shipped with Tivoli Data Warehouse:

v Crystal Enterprise 9 Installation Guide

Provides information and procedures for installing Crystal Enterprise. This guide

also includes detailed instructions for the different installation modes available.

v Crystal Enterprise 9 Getting Started Guide

Provides basic installation information and serves as a general introduction to

Crystal Enterprise, ePortfolio, the Crystal Management Console, the Crystal

Publishing Wizard, and the overall product architecture.

v Crystal Enterprise 9 ePortfolio User’s Guide

Provides information and procedures for accessing and using ePortfolio and its

report viewers.

v Crystal Enterprise 9 Administrator’s Guide

Provides information and procedures for the administrative tasks. Procedures are

provided for common tasks. Conceptual information and technical details are

provided for all advanced topics.

v Crystal Reports 9 User’s Guide

Provides procedures for typical reporting tasks such as placing fields, formatting

reports, and sorting records. It also contains information about advanced

formula creation and accessing different types of data. Acts as a reference for

basic reporting needs as well as an introduction to new concepts in report

creation.

DB2 Universal Database publications

The DB2 library contains important information about the database system and

data warehousing technology provided by IBM DB2 Universal Database Enterprise

Edition, DB2 Warehouse Manager, and the DB2 Data Warehouse Center.

If you are new to data warehousing and the DB2 product, the IBM DB2 Universal

Database Business Intelligence Tutorial leads you through the basics of data

warehousing and the use of the DB2 Data Warehouse Center. This online tutorial is

About this guide vii

available from both the DB2 HTML Documentation CD and the DB2 First Steps

component after installing DB2 Universal Database on your system.

Refer to the DB2 library for help in installing, configuring, administering, and

troubleshooting DB2 products. The DB2 library is available online at the following

Web address:

http://www.ibm.com/software/data/db2/library/

After installing DB2, the library is also available on your system.

The following documents are particularly relevant for people working with Tivoli

Data Warehouse:

v IBM DB2 Universal Database for Windows Quick Beginnings, GC09-2971

Guides you through the planning, installation, migration (if necessary), and

setup of a partitioned database system using the IBM DB2 product on

Microsoft® Windows® systems.

v IBM DB2 Universal Database for UNIX Quick Beginnings, GC09-2970

Guides you through the planning, installation, migration (if necessary), and

setup of a partitioned database system using the IBM DB2 product on UNIX®

systems.

v IBM DB2 Universal Database Administration Guide: Implementation, SC09-2944

Covers the details of implementing your database design. Topics include

creating and altering a database, database security, database recovery, and

administration using the DB2 Control Center, a DB2 graphical user interface

(GUI).

v IBM DB2 Universal Database Administration Guide: Performance, SC09-2945

Provides information about configuring and tuning your database environment

to improve performance.

v IBM DB2 Universal Database Data Warehouse Center Administration Guide,

SC26-9993

Provides information about how to build and maintain a data warehouse using

the DB2 Data Warehouse Center.

v IBM DB2 Warehouse Manager Installation Guide, GC26-9998

Provides the information for installing the following DB2 Warehouse Manager

components: Information Catalog Manager, warehouse agents, and warehouse

transformers.

v IBM DB2 Universal Database and DB2 Connect Installation and Configuration

Supplement, GC09-2957

Provides advanced installation considerations and guides you through the

planning, installation, migration (if necessary), and setup of a platform-specific

DB2 client. Once the DB2 client is installed, you then configure communications

for both the client and server, using the DB2 GUI tools or the Command Line

Processor. This supplement also contains information on binding, setting up

communications on the server, the DB2 GUI tools, Distributed Relational

Database Architecture™ application server (DRDA® AS), distributed installation,

the configuration of distributed requests, and accessing heterogeneous data

sources.

v IBM DB2 SQL Reference Volume 1, SC09-2974 and IBM DB2 SQL Reference Volume

2, SC09-2975

viii Tivoli Data Warehouse Messages


Describes SQL syntax, semantics, and the rules of the language. This book also

includes information about release-to-release incompatibilities, product

limitations, and catalog views.

You can order both volumes of the SQL Reference in the English language in

North America with the form number SBOF-8933.

v IBM DB2 Universal Database Message Reference Volume 1, GC09-2978 and IBM DB2

Universal Database Message Reference Volume 2, GC09-2979

Lists the messages and codes issued by DB2, the Information Catalog Manager,

and the DB2 Data Warehouse Center, and describes the actions you should take.

z/OS Publications

This section lists publications in the DB2 Universal Database for z/OS® and

OS/390® library and other documentation for those using Tivoli Data Warehouse

on the z/OS operating system.

DB2 Universal Database for z/OS and OS/390 publications: This section lists

publications in the DB2 Universal Database for z/OS and OS/390 library:

v IBM DB2 Universal Database for z/OS and OS/390 Administration Guide, SC26-9931

Provides information about how to administer and customize DB2 Universal

Database for z/OS and OS/390. Its audience is mainly composed of system

administrators, IT administrators, and users.

v IBM DB2 Universal Database for z/OS and OS/390 An Introduction to DB2 for

OS/390, SC26-9937

Provides information about how to get started with DB2 Universal Database for

z/OS and OS/390. It also gives an overall view of the product.

v IBM DB2 Universal Database for z/OS and OS/390 Messages and Codes, GC26-9940

Defines and explains the DB2 Universal Database for z/OS and OS/390

messages and codes.

v IBM DB2 Universal Database for z/OS and OS/390 Installation Guide, GC26-9936

Provides information about how to install DB2 Universal Database for z/OS and

OS/390.

v IBM DB2 Universal Database for z/OS and OS/390 Utility Guide and Reference,

SC26-9945

Contains usage information for the tasks of system administration, database

administration, and database operation. It presents detailed information on using

utilities, specifying syntax (including keyword and parameter descriptions), and

starting, stopping, and restarting utilities. This book also includes job control

language (JCL) and control statements for each utility.

v IBM DB2 Universal Database for z/OS and OS/390 Diagnosis Guide and Reference,

LY37-3740

Provides information about how to debug and fix common problems with DB2

Universal Database for z/OS and OS/390.

Accessing publications online

The documentation CD, Tivoli Data Warehouse Documentation CD, contains the

Tivoli Data Warehouse publications. The format of the publications is PDF, HTML,

or both. Refer to the readme file on the CD for instructions on how to access the

documentation.

About this guide ix

IBM posts publications for this and all other Tivoli products, as they become

available and whenever they are updated, to the Tivoli Software Information

Center Web site. The Tivoli Software Information Center is located at the following

Web address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Click the Tivoli Data Warehouse link to access the product library.

The DB2 product library is located at the following Web address:


Note: If you print PDF documents on other than letter-sized paper, select the Fit to

page check box in the Adobe Acrobat Print dialog. This option is available

when you click File → Print. Fit to page ensures that the full dimensions of a

letter-sized page print on the paper that you are using.

Ordering publications

You can order many IBM and Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755

v In Canada: 800-426-4968

v In other countries, for a list of telephone numbers, see the following Web site:

http://www.ibm.com/software/tivoli/order-lit/

Contacting customer support

If you have a problem with any Tivoli product, refer to the following IBM Software

Support Web site:

http://www.ibm.com/software/sysmgmt/products/support/

If you have a problem with Tivoli Data Warehouse, refer to the following IBM

Support Web site:

http://www.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.html

If you have a problem with a DB2 product, refer to the following IBM Software

Support Web site:

http://www.ibm.com/software/data/db2

If you want to contact customer support, see the IBM Software Support Guide at the

following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,

depending on the severity of your problem, and the following information:

x Tivoli Data Warehouse Messages

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html


http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

http://www.ibm.com/software/tivoli/order-lit/

http://www.ibm.com/software/sysmgmt/products/support/

http://www.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.html

http://www.ibm.com/software/data/db2

http://techsupport.services.ibm.com/guides/handbook.html

v Registration and eligibility

v Telephone numbers and e-mail addresses, depending on the country in which

you are located

v Information you must have before contacting IBM Software Support

Conventions used in this guide

This guide uses several conventions for special terms and actions and for operating

system-dependent commands and paths.

Typeface conventions

This guide uses the following typeface conventions:

Bold Lowercase and mixed-case commands, command options, and

flags that appear within text appear like this, in bold type.

Graphical user interface elements (except for titles of windows and

dialogs) and names of keys also appear like this, in bold type.

Italic Variables, values you must provide, new terms, and words and

phrases that are emphasized appear like this, in italic type.

Monospace Code examples, output, and message text appear like this, in

monospace type.

Text strings you must type, when they appear within text, names

of Java™ methods and classes, and HTML and XML tags also

appear like this, in monospace type.

Operating system-dependent variables and paths

When referring to environment variables in a context that can occur only on a

system running a Windows operating system, environment variables and path

names are displayed using the Windows notation. For example, %SystemRoot%

and C:\Program Files\TWH\, respectively. If the context applies to both Windows

and UNIX operating systems, this guide uses the UNIX convention for specifying

environment variables and for directory notation. For example, $TEMP and

/usr/local/bin/.

To convert from the UNIX format to the Windows format, replace $variable with

%variable% for environment variables and replace each forward slash (/) with a

backslash (\) in directory paths.

Note: If you are using the bash shell on a Windows system, you can use the UNIX

conventions.

This guide uses the following environment variables:

Variable name Meaning

ProgramFiles Identifies the directory where program files are

installed. Usually, this is C:\Program Files\, but it

can also be represented with the SystemDrive

environment variable as

%SystemDrive%:\Program Files\.

Although the ProgramFiles variable is not used in

Windows NT®, this document uses it to refer to the

corresponding location on Windows NT systems.

About this guide xi

TWH_TOPDIR The top-level directory in which the Tivoli Data

Warehouse files are installed. The default value on

Windows systems is %ProgramFiles%\TWH\. The

default value on UNIX systems is /opt/twh/.

TIVOLI_COMMON_DIR The directory where Tivoli Data Warehouse logs

the messages and trace files. By default, the Tivoli

common logging directory is located at

%ProgramFiles%\IBM\Tivoli\common\ on

Windows systems and at

/usr/ibm/tivoli/common/ on UNIX systems.

xii Tivoli Data Warehouse Messages

Chapter 1. Identifying a message

The messages are all identified in the same way. The following example explains

the components of the identifier:

CDWIC0003I

CDW Identifies the product code for Tivoli Data Warehouse.

IC Identifies the subsystem code.

0003 Identifies the serial number of the message.

I Identifies the type of the message, which can be:

I Informational messages provide users with information or

feedback about normal events that have occurred or are occurring,

or request information from users in cases where the outcome will

not be negative, regardless of the response.

Note: Informational messages are not included in this manual.

W Warning messages indicate that potentially undesirable conditions

have occurred or could occur, but the program can continue.

Warning messages often ask users to make decisions before

processing continues.

E Error messages indicate problems that require intervention or

correction before the program can continue.

Message and trace logs are generated. The message text is translated into different

languages and is displayed according to the locale selected by the user. Messages

are appended to the message logs, providing a complete record of the errors.

Trace logs on the other hand, provide enough information for support to diagnose

a problem remotely. When a problem occurs, you can change the trace level so that

it will gather the data needed by support to understand the problem. Refer to

“Setting the trace level” on page 5.

The messages contained in this manual are grouped according to their subsystem

code. Refer to the following table for more information.

Table 1. Subsystem codes

Code Description

CR Indicates messages that can be generated by the program that migrate

reports.

Messages are logged in:

TIVOLI_COMMON_DIR/cdw/logs/tools/reporting_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/reporting_trace_log.log.

© Copyright IBM Corp. 2003, 2004 1

Table 1. Subsystem codes (continued)

Code Description

CW Indicates messages that can be generated by the programs that configure

warehouse packs: twh_config_wep.pl and ConfigWep.pm, which are called

by the installation wizard or by twh_configwep.bat.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/configwep_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/configwep_trc.log

DI Indicates messages that can be generated by the program that accesses user

information (DBInfoMgr).

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/DBInfoMgr_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/DBInfoMgr_trace_log.log.

ET Indicates messages that can be generated by tools that configure ODBC data

sources and databases. These tools are called by the installation.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/dbsetup_message_log.log and

TIVOLI_COMMON_DIR/cdw/logs/tools/odbccfg_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/dbsetup_trace_log.log and

TIVOLI_COMMON_DIR/cdw/logs/tools/odbccfg_trace_log.log.

EX Indicates messages that can be generated by the SQL run-time program,

which converts generic SQL to vendor specific SQL that can operate on the

source database.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/etl/execsql2_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/etl/execsql2_trace_log.log.

FF Indicates messages that can be generated by First Failure Data Capture

(FFDC), which is the ability to capture useful data after the problem has

been logged and to collect enough data that the problem can be diagnosed

without having to reproduce the problem. This code also indicates messages

that can be generated by the mvlogdir utility, which gives you the

capability to update important Tivoli Data Warehouse files prior to

manually moving the common logging directory for Tivoli Data Warehouse

only.

2 Tivoli Data Warehouse Messages


Code Description

IC Indicates messages that can be generated during the installation and

uninstallation of Tivoli Data Warehouse and warehouse packs.

Messages are logged in:

TIVOLI_COMMON_DIR/cdw/logs/install/core_install_message_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/core_backend_message_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_message_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_backend_message_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/core_uninstall_message_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/wep_uninstall_message_log.log

and TIVOLI_COMMON_DIR/cdw/logs/install/wep_uninstall_backend_message_log.log.

Trace information is logged in:

TIVOLI_COMMON_DIR/cdw/logs/install/core_install_trace_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/core_backend_trace_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_trace_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_backend_trace_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/core_uninstall_trace_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/wep_uninstall_trace_log.log and

TIVOLI_COMMON_DIR/cdw/logs/install/wep_uninstall_backend_trace_log.log.

IS Indicates messages that can be generated by the installation wizard during

the core installation, as well as upgrades, adding data marts and central

data warehouses, and install recovery of Tivoli Data Warehouse.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/install/core_install_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/install/core_install_trace_log.log

IT Indicates messages that can be generated by the application that imports

resource bundles during the installation of Tivoli Data Warehouse.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/install/core_install_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/install/core_install_trace_log.log.

IW Indicates messages that can be generated by the installation wizard during

the installation of warehouse packs.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_trace_log.log.

Chapter 1. Identifying a message 3


Code Description

RT Indicates messages that can be generated by the run_react.pl and React.pm

programs, which are internal tools called by other Tivoli Data Warehouse

programs.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/react_message_log.log .

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/react_trace_log.log.

For React, there are also 2 other trace files that can be created on a remote

agent site (not the control server):TIVOLI_COMMON_DIR/cdw/logs/tools/react_agent_launcher_trc.log

TIVOLI_COMMON_DIR/cdw/logs/tools/react_agent_trc.log.

RU Indicates messages that can be generated by the roll-up script, which

warehouse packs use to process data marts.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/etl/rollup/rollupMulti_message.log.

Trace information is logged in:

TIVOLI_COMMON_DIR/cdw/logs/etl/rollup/rollupMulti_trace.log.

SQ Indicates messages that can be generated by RunMultiSQL, which works

with the SQL run-time program.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/etl/RunMultiSQL_message_log.log.

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/etl/RunMultiSQL_trace_log.log.

TD Indicates messages that can be generated by an internal program that

changes user IDs and passwords for ODBC data sources, warehouse

sources, and warehouse targets.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/TWHDBAdmin_message_log.log.

Trace information in

TIVOLI_COMMON_DIR/cdw/logs/tools/TWHDBAdmin_trace_log.log.

TG Indicates messages that can be generated by the twh_dwc_xxxx.pl scripts,

which are tag file creation scrips used during the installation of Tivoli Data

Warehouse.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/install/core_install_message_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/core_backend_message_log.log,

and TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_backend_message_log.log.

Trace information is logged inTIVOLI_COMMON_DIR/cdw/logs/install/core_install_trace_log.log,

TIVOLI_COMMON_DIR/cdw/logs/install/core_backend_trace_log.log,

and TIVOLI_COMMON_DIR/cdw/logs/install/wep_install_backend_trace_log.log.



Code Description

TR Indicates messages that can be generated when you are running the

program that changes report server values.

Messages are logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/TWHRptAdmin_message_log.log

Trace information is logged in:TIVOLI_COMMON_DIR/cdw/logs/tools/TWHRptAdmin_trace_log.log

UW Indicates messages that can be generated during the uninstallation of the

warehouse enablement packs. Messages are logged in

TIVOLI_COMMON_DIR/cdw/logs/install/wep_uninstall_message_log.log.

They log trace information in

TIVOLI_COMMON_DIR/cdw/logs/install/wep_uninstall_trace_log.log by

default.

Setting the trace level

Trace information is gathered based on the trace level you specify in the

programName.trc.level value in the programNamelogging.properties file, where

programName is the name of the program that you want to collect information

about. To change the amount of information gathered, complete the following

steps:

1. Open the programNamelogging.properties file. All properties files are located in

the $TIVOLI_COMMON_DIR/cdw/logs/properties/ directory.

2. Set the programName.trc.level value. Valid values are INFO, DEBUG_MIN,

DEBUG_MID, and DEBUG_MAX. By default, programs that run only once,

such as the installation programs, are set to the highest trace level

(DEBUG_MAX).

3. Save and close the file.

The next time you run the program, it will gather trace information based on the

trace level you specified.

When installing the control server, the Tivoli Data Warehouse installation wizard

runs with the highest level of tracing.

Chapter 1. Identifying a message 5


Chapter 2. Problem determination tools

The following tools are located in the Tivoli common logging directory under

cdw/tools:

v “LogXML Viewer”

v “First Failure Data Capture (FFDC)” on page 8

These tools assist you in viewing and gathering message and trace information

about the problem.

LogXML Viewer

Tivoli applications support a common XML format, in which they log messages.

This common format is called Log XML. The Log XML Viewer processes logs in

that format, enabling you to view the message logs in any Web browser in an

easy-to-read format. Viewing trace messages with the Log XML Viewer is not

supported.

The viewer is installed with Tivoli Data Warehouse and is located in the

$TIVOLI_COMMON_DIR/cdw/tools/ directory. The Log XML Viewer converts

the logged messages into ASCII or HTML for presentation. Visual cues are

associated with error and warning messages.

To run the Log XML Viewer, type the following at a command prompt:

viewer fullPathToLog.xmlFile > myLog.htm

The variable fullPathToLog.xmlFile is the full path to the log file you want to view

and myLog.htm is the file you want to redirect the contents to. If

fullPathToLog.xmlFile or myLog.htm contains the space character, enclose the value in

double quotation marks (″) or use the short name. For example:

cd C:\Program Files\IBM\tivoli\common\cdw\tools

viewer c:\Progra~1\IBM\tivoli\common\cdw\logs\install\core_install_message_log.log \

> C:\TEMP\core_install_message_log.html

cd C:\Program Files\IBM\tivoli\common\cdw\tools

viewer \

"c:\Program Files\IBM\tivoli\common\cdw\logs\install\core_install_message_log.log" \

> C:\TEMP\core_install_message_log.html

After redirecting the output to a new file, open the new file from a browser

window.

Notes:

1. The LogXML Viewer is deleted when you uninstall Tivoli Data Warehouse. If

the uninstallation fails after the viewer is deleted, you cannot format the log

files.

2. If the installation of Tivoli Data Warehouse fails before it installs the Java

virtual machine, the LogXML Viewer will not run. If you need the tool to

examine logs created during a failed installation, you can edit the viewer file

and modify it to use a Java virtual machine already installed on your computer.


First Failure Data Capture (FFDC)

First Failure Data Capture (FFDC) is the ability to capture useful data after a

problem has been logged. The purpose of FFDC features is to collect enough data

so that a problem can be diagnosed without having to reproduce it a second time.

Because it is likely that a failure will happen while the system is in an unattended

mode, it is important to capture this data in such a way that it is not overwritten,

before it can be gathered and sent to a support center or help desk. Data that is

captured as part of FFDC can include trace logs, message logs, dumps of

in-memory data structures, and so forth.

The minimal trace log, the message files, and the script message files are the

primary sources for the First Failure Data Capture for the Tivoli Data Warehouse

installation program. Each error condition is analyzed during development of trace

and message logs to determine the information that is needed to properly diagnose

the failure. FFDC is installed with Tivoli Data Warehouse and is located in the

$TIVOLI_COMMON_DIR/cdw/tools directory.

To manually run the program, type the following at a command prompt from the

$TIVOLI_COMMON_DIR/cdw/tools directory:

v On Windows systems:

ffdc.bat

v On UNIX systems:

./ffdcunix.sh

The error information is compressed and stored in the

$TIVOLI_COMMON_DIR/cdw/ffdc/dateTime directory for diagnosis of the

problem, where dateTime refers to the date and time that FFDC ran. FFDC displays

the system date and time information on the screen when the program runs.

FFDC will not work in the following situations:

v If the Tivoli Data Warehouse installation fails before the Java virtual machine is

installed.

v If the uninstallation of Tivoli Data Warehouse fails after the Java virtual machine

has been deleted.

When this happens, you can take one of the following actions:

v You can gather the logs manually.

v You can modify the FFDC script to specify the path of a different Java virtual

machine.


Chapter 3. Messages

CDWCR0001E The report migration utility could not start the message logger that is defined in the

reportinglogging.properties file.

Explanation: The $TIVOLI_COMMON_DIR/cdw/logs/properties/reportinglogging.properties file defines the

message log and trace files. The log file defined by Tivoli Data Warehouse installation is named

$TIVOLI_COMMON_DIR/cdw/logs/tools/reporting_message_log.log. The program could not write message

information to the file.

Administrator Response: Verify that the user has permissions to access this file. If the properties file has been

modified, restore the original file from a backup. Run the report migration utility again.

CDWCR0002E The report migration utility could not start the trace logger that is defined in the

reportinglogging.properties file.

Explanation: The $TIVOLI_COMMON_DIR/cdw/logs/properties/reportinglogging.properties file defines the

message log and trace files. The log file defined by Tivoli Data Warehouse installation is named

$TIVOLI_COMMON_DIR/cdw/logs/tools/reporting_trace_log.log. The program could not write trace information to

the file.

Administrator Response: Verify that the user has permission to access this file. If the properties file has been

modified restore the original file from a backup. Run the report migration utility again.

CDWCR0004E The TWH_TOPDIR variable was not defined.

Explanation: This is an internal error. The Tivoli Data Warehouse installation program should pass a valid

parameter list. The TWH_TOPDIR was not passed to the report migration utility on the command line. The

TWH_TOPDIR variable is needed to locate files required to run the report migration utility.

Administrator Response: Run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0005E An error occurred in the report migration utility.

Explanation: This is an internal error. The report migration utility migrates reports that were created for use with

Tivoli Enterprise Data Warehouse, Version 1.1 to the Crystal Reports format that can be used with Tivoli Data

Warehouse, Version 1.2. This migration utility ran when you upgraded your Tivoli Data Warehouse installation from

Version 1.1 to Version 1.2 or installed a warehouse pack for Version 1.1.

Administrator Response: Review the trace logs for additional information about the error and take corrective action

if possible. Otherwise, run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0007E The report migration utility ended because of an error.

Explanation: A fatal error occurred and no reports were migrated.

Administrator Response: Review the reporting_message_log.log file in the

$TIVOLI_COMMON_DIR/cdw/logs/tools directory for additional messages indicating the specific error that caused

the report migration utility to stop.

CDWCR0008E A Crystal Enterprise server was not passed to the Crystal connection utility. The parameter,

ceserver, was not specified.

Explanation: This is an internal error. The Tivoli Data Warehouse installation calls the Crystal connection utility and

passes the correct parameters. When calling the Crystal connection utility, the parameter, ceserver, must be specified.

Administrator Response: Verify that the Crystal Enterprise server was specified correctly on the Tivoli Data

Warehouse installation panels. Run FFDC and contact IBM Customer Support to help you diagnose the problem.


CDWCR0009E A Crystal Enterprise user was not passed to the Crystal connection utility. The parameter, ceuser,

was not specified.

Explanation: This is an internal error. The Tivoli Data Warehouse installation calls this utility and passes the correct

parameters. A Crystal Enterprise user must be specified by using the parameter, ceuser.

Administrator Response: Verify that the Crystal Enterprise user was specified correctly on the Tivoli Data

Warehouse installation panels. Run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0011E A connection could not be made to the Crystal Enterprise server.

Explanation: The Crystal Enterprise server connection failed.

Administrator Response: Verify that the user id, password and server name for the Crystal Enterprise server were

specified correctly in the Tivoli Data Warehouse installation wizard. Verify that the Crystal Enterprise server is up

and running. If the domain of the Crystal Enterprise server is not in the Domain name server (DNS) list of the

machine attempting to make the connection, an entry for the Crystal Enterprise server must be made in the host file.

See the Installing and Configuring Tivoli Data Warehouse guide for more information.

CDWCR0012E The data mart data source name was not passed to the Crystal connection utility. The parameter,

dsn, was not specified.

Explanation: This is an internal error. The Tivoli Data Warehouse installation calls the report migration utility and

passes the correct parameters. A data source name must be specified by using the parameter, dsn.


CDWCR0013E The data mart user id was not passed to the Crystal connection utility. The parameter, user, was

not specified.


passes the correct parameters. A data mart user (DB2 user) must be specified by using the parameter, user.


CDWCR0014E The password for the data mart user was not passed to the Crystal connection utility. The

parameter, passwd, was not specified.


should pass the correct parameters. A data mart logon password for a DB2 user must be specified by using the

parameter, passwd.


CDWCR0016E A number that is not valid was found for a component attribute group by clause.

Explanation: This is an internal error indicating corrupt metadata for a report. The report migration utility found a

number that is not valid for a component attribute group by clause. Either the data is corrupt in the comma

separated value (CSV) files for a warehouse pack for Version 1.1, or in the RPI.SELECTIONS table, if this is a 1.1 to

1.2 core upgrade.


CDWCR0017E A number that is not valid was found for a component attribute order by clause.


number that is not valid for a component attribute order by clause. Either the data is corrupt in the comma separated

value (CSV) files for a warehouse pack for Version 1.1, or in the RPI.SELECTIONS table, if this is a 1.1 to 1.2 core

upgrade.


CDWCR0009E • CDWCR0017E


CDWCR0018E A number that is not valid was found for the number of metrics.


number that is not valid for the number of metrics. Either the data is corrupt in the comma separated value (CSV)

files for a warehouse pack for Version 1.1, or in the RPI.SELECTIONS table, if this is a 1.1 to 1.2 core upgrade.


CDWCR0019E A number that is not valid was found for the number of component attributes.


number that is not valid for the number of component attributes. Either the data is corrupt in the comma separated

value (CSV) files for a warehouse pack for Version 1.1, or in the RPI.SELECTIONS table, if this is a 1.1 to 1.2 core

upgrade.


CDWCR0020E A number that is not valid was found for the metric ID.


number that is not valid for the metric ID. Either the data is corrupt in the comma separated value (CSV) files for a

warehouse pack for Version 1.1, or in the RPI.SELECTIONS table, if this is a 1.1 to 1.2 core upgrade.


CDWCR0021E A number that is not valid was found for the metric aggregation.

Explanation: This is an internal error indicating corrupt metadata for a report. The metric aggregation can be avg,

min, max, or tot. It’s represented with a number in Tivoli Data Warehouse’s metadata and should be valid. Either the

data is corrupt in the comma separated value (CSV) files for a warehouse pack for Version 1.1, or in the

RPI.SELECTIONS table, if this is a 1.1 to 1.2 core upgrade.


CDWCR0022E A number that is not valid was found for the number of iterations.

Explanation: This is an internal error indicating corrupt metadata for a report. Iteration is an internal object used to

keep track of report metadata. The report migration utility found a number that is not valid for the number of

iterations. Either the data is corrupt in the comma separated value (CSV) files for a warehouse pack for Version 1.1,

or in the RPI.SELECTIONS table, if this is a 1.1 to 1.2 core upgrade.


CDWCR0023E Cannot open the reportinglogging.properties file.

Explanation: The report migration utility can not open the reportinglogging.properties file. The file is located in the

$TIVOLI_COMMON_DIR/cdw/logs/properties directory. This error indicates a corrupt Tivoli Data Warehouse

installation or a corrupt reportinglogging.properties file.

Administrator Response: If you manually edited this file, restore it from a backup copy, or run the Tivoli Data

Warehouse installation again.

CDWCR0024E Cannot open the log.properties file.

Explanation: The report migration utility can not open the log.properties file. The file is located in the

$TWH_TOPDIR/logginglocation directory. This error indicates a corrupt Tivoli Data Warehouse installation or a

corrupt log.properties file.

Administrator Response: Verify that the $TWH_TOPDIR/logginglocation/log.properties file has not been manually

edited. Try to restore this file from a backup copy or run the Tivoli Data Warehouse installation again.


Chapter 3. Messages 11

CDWCR0025E An error occurred setting up message and trace logging.

Explanation: This is an internal error. An unexpected exception occurred setting up message and trace logging. The

trace logs may have additional information for the error condition to aid in debugging, and are located in the

TIVOLI_COMMON_DIR/cdw/logs/tools and TIVOLI_COMMON_DIR/cdw/logs/install directory.


CDWCR0026E Failed to connect to the control database.

Explanation: This is usually an internal error. The installation program should have already failed as it needs to

connect to the control database. A null connection handle was returned from the method that connects to the control

database. A connection is required to continue report migration.

Administrator Response: Verify that the DB2 server is functioning correctly and you can manually connect to the

control database. Review the reporting_message_log.log file in the $TIVOLI_COMMON_DIR/cdw/logs/tools

directory for additional messages that may indicate corrective action. If you cannot determine the cause of the

problem, run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0027E No reports were found to migrate.

Explanation: This is a warehouse pack for Version 1.1 installed on a 1.2 system. The warehouse pack stated there

were reports in the configuration file, but there were no reports found in the rpi.rpi2xml_tmp2 table. This is an

internal table that is created from reading the comma separated values (CSV) file. Data was found in the file but not

in the table that is created from the file.

Administrator Response: Check the logs and verify that there are no SQL errors. If there are, then take action as

indicated by the error. Otherwise, run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0029E An error was found while migrating a report.

Explanation: An error was found during the report migration. This is usually a problem with the metadata that

defines a report. The report was not migrated but the report migration utility will continue to run and migrate the

rest of the reports.


$TIVOLI_COMMON_DIR/cdw/logs/tools directory for additional messages that may indicate corrective action. If

you cannot determine the problem, run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0030E The report migration utility ended with errors. number_reports_migrated reports were migrated

successfully. number_failed_reports reports failed to migrate.

Explanation: There were some reports that had errors and failed to migrate.


$TIVOLI_COMMON_DIR/cdw/logs/tools directory for additional messages that may indicate corrective action. Take

corrective actions as indicated by messages and run the migration again. Determine which reports failed to migrate

and whether that is expected behavior. Some reports may fail to migrate if they were replaced by new versions of

reports but were not deleted. If you cannot determine the problem, run FFDC and contact IBM Customer Support to

help you diagnose the problem.

CDWCR0031E An input output error occurred while processing file xml_file_name. System error message:

error_message.

Explanation: An error occurred trying to write the named XML file. The XML file is an intermediate format used in

the migration process. Usually the error is disk space or permission problems.

Administrator Response: Take action based on the system error message.



CDWCR0032E An error occurred parsing the XML file. System error message: error_message.

Explanation: This is an internal error. An error occurred parsing the XML file that was generated from the report

interface metadata. The XML file is an intermediate format used in the migration process. It was written with data

that is not allowed by the document type definition (DTD), which defines the structure of the XML file. This report

was skipped and processing of other reports will continue.


CDWCR0033W No reports were found to migrate.

Explanation: No reports were found to migrate during a Tivoli Data Warehouse 1.1 to 1.2 migration. This is

expected behavior if your 1.1 Tivoli Data Warehouse installation had no reports created with the report interface.

Administrator Response: Verify that this is the expected behavior. If it is not expected behavior, the report

definitions in the RPI.REPORT or RPI.DATAMART table are incorrect. Restore these tables from a database backup

and run the report migration utility again.

CDWCR0035W The star schema, star_schema_name, was not found for report report_name.

Explanation: This error occurs on a 1.1 to 1.2 upgrade. Some warehouse packs for Version 1.1 deleted reports

created in the report interface in a patch by creating new reports and star schemas. The old star schemas were

deleted but the reports were not deleted. When a report is encountered that has no associated star schema, it is

assumed that this is a report that is not valid and it is skipped. The migration of other reports continues.

Administrator Response: This is usually a normal condition, but you should verify that reports have been migrated

as expected. Verify that the report named is one that should be skipped. If it is not a report you want skipped, the

DB2 Data Warehouse Center IWH and RPI tables are out of sync. Some database corruption has occurred or the star

schema may have been deleted using the DB2 Data Warehouse Center GUI. Since the core migration has completed,

you have 2 options: 1) Restore your 1.1 environment, fix the IWH or RPI tables and run the migration again. You can

verify the report and associated star schema using the report interface and the DB2 Data Warehouse Center GUI. 2)

Fix the existing IWH or RPI tables and run the report migration again. Backup your control database and send it to

support. Support will send an updated backup that will migrate correctly. Fixing the database might not be possible

depending on the corruption found in the tables. If that is the case, you have to choose option 1 if you want the

report in question migrated.

CDWCR0036E The star schema star_schema_name was not found in rpi.strings metadata for report report_name.

Explanation: This is an internal error and indicates a warehouse pack that is not valid or corrupted report interface

metadata. The report interface metadata tables or the comma separated value (CSV) files for a warehouse pack do

not contain the expected data.


CDWCR0037E There were no joins found for report report_name and star schema star_schema_name.

Explanation: This is an internal error and indicates a warehouse pack that is not valid or corrupted report interface

metadata. The report interface metadata tables or the comma separated value (CSV) files for a warehouse pack do

not contain the expected data.


CDWCR0038E An exception occurred encrypting the data mart password for the DB2 mart user.

Explanation: This is an internal error. The data mart password is encrypted and written to an XML file that is used

for the migration process. If there is an error during encryption the data mart password cannot be set for the report

and processing for the report stops.




CDWCR0039E The creation of table table_name failed with return code return_code .

Explanation: This is usually a database error. Working tables and views are used for the migration process. The

migration cannot continue if the program is unable to create these tables.

Administrator Response: Verify that the control database is running and that you can create tables with the named

schema. Run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0040E There were no join columns inserted into rpi.strings2.

Explanation: This is usually a warehouse pack error. The expected metadata was not found. RPI.strings2 is an

internal table that is used during a warehouse pack for Version 1.1 migration. The report was skipped and migration

of other reports will continue.


CDWCR0041E There were no display columns inserted into rpi.strings2.


internal table that is used during a warehouse pack for Version 1.1 migration. The report was skipped and migration

of other reports will continue.


CDWCR0042E There were no from lines inserted into rpi.strings2.


internal table that is used during a warehouse pack for Version 1.1 migration. The report is skipped and migration of

other reports will continue.


CDWCR0043E The database driver is null for the database_name database.

Explanation: The connection information for the database which was retrieved from an encrypted file is not correct.

This indicates that the file is corrupt, or the DB2 database user id or password has been changed after the Tivoli Data

Warehouse installation, and the correct utilities to change database information have not been run.

Administrator Response: If you changed the database userid or password, be sure to run the twh_update_userinfo

utility then run the migration again. Otherwise, restore the $TWH_TOPDIR/.mddb.properties file from a backup

copy or run the Tivoli Data Warehouse installation again. If the database driver is still null, run FFDC and contact

IBM Customer Support to help you diagnose the problem.

CDWCR0044E The URL is null for the database_name database.

Explanation: This is an internal error. The connection information for the database which was retrieved from an

encrypted file is not correct.


CDWCR0045E The user ID is null for the database_name database.




CDWCR0046E The connection is null for the database_name database.






CDWCR0047E The connection to the database_name database failed. Exception: exception .

Explanation: This could be a problem with user, password, or database configuration. The specified exception

information should give additional details about the error.

Administrator Response: Take corrective action based on the specified exception information.

CDWCR0048E Insert into rpi.rpi2xml_tmp2 failed with return code return_code.

Explanation: This is usually a database error. This is a working table used during the migration process to store

report metadata. The migration cannot continue if the migration report utility is unable to populate this table.

Administrator Response: Verify that the control database is running and you can create and insert data into a table

with the named schema. Contact your DBA for further assistance.

CDWCR0049E A null value was retrieved for column column_name.

Explanation: This is an internal error. The required metadata that describes a report was not found. Either the data

is corrupt in the comma separated value (CSV) files for a warehouse pack for Version 1.1, or in the RPI.SELECTIONS

table, if this is a 1.1 to 1.2 core upgrade.


CDWCR0050E A SQL error was generated while processing report report_name. SQLState: SQLState SQLMessage:

SQLMessage SQL Error Code: SQLError

Explanation: An error occurred while processing the named report. The report was skipped and migration of other

reports will continue. If this error is generated for only one report then it is usually a problem with the report

metadata. If this error is generated for multiple reports it is usually a database problem (log space, etc).

Administrator Response: Take action based on the SQL error generated, if this is a custom report, or contact IBM

Customer Support if this is a Tivoli warehouse pack report. Once the problem is corrected run the migration report

utility again.

CDWCR0051E An SQL error was generated. SQLState: sql_state SQLMessage: sql_message SQL Error Code:

sql_error

Explanation: A SQL error occurred outside the context of processing a report. This is a fatal error because there was

a problem accessing the database or creating necessary tables (log space, invalid password, etc.).

Administrator Response: Take action based on the SQL error generated and run the report migration utility again.

Contact your DBA for assistance.

CDWCR0052E No data was read from the comma separated value (CSV) file file_name.

Explanation: A warehouse pack for Version 1.1 is being installed but there was no data found in the CSV file. All

warehouse packs for Version 1.1 that have REPORTS=TRUE specified in the configuration file are expected to have

CSV files.

Administrator Response: Check the file name specified and verify that there is data, and that the file has

permission to allow reads. Verify that the version number is correct in the file name. A Tivoli released warehouse

pack should not encounter this problem. If this is a customer-developed warehouse pack and there are no CSV files,

verify that the product_code/twh_install_props.cfg file has REPORTS_INCLUDED=false.

CDWCR0053E The number of entries parsed from comma separated value (CSV) file file_name exceeds the

expected limit. There were entries entries found but nine were expected.

Explanation: This is usually an internal parsing error. A warehouse pack for Version 1.1 is being installed, but when

reading the CSV file the number of entries found exceeded the expected limit. This error could also occur if the CSV

file is corrupted.

Administrator Response: Check the named file and verify that it is a valid CSV file. Run FFDC and contact IBM

Customer Support to help you diagnose the problem.



CDWCR0054W The star schema star_schema_name was not found for health check report report_name.

Explanation: This error occurs during a 1.1 to 1.2 upgrade. Some warehouse packs for Version 1.1 deleted reports

created in the report interface in a patch by creating new reports and star schemas. The old star schemas were

deleted but the reports were not deleted. When a report is encountered that has no associated star schema, it is

considered a report that is not valid and it is skipped. The migration of other reports continues.

Administrator Response: This is usually a normal condition but you should verify that reports have been migrated

as expected. Verify that the report named is one that should be skipped. If it is not the report to be skipped, the DB2

Data Warehouse Center IWH and RPI tables are out of sync, some database corruption has occurred, or the star

schema may have been deleted using the DB2 Data Warehouse Center GUI. Since the core migration has completed

you have two options: 1) Restore your 1.1 environment, fix the IWH or RPI tables and run the report migration

utility again. You can verify the report and associated star schema using the report interface and the DB2 Data

Warehouse Center GUI. 2) Fix the existing IWH or RPI tables and run the report migration utility again. Backup your

control database and send it to IBM Customer Support. Support will send an updated backup that will migrate

correctly. Fixing the database might not be possible depending on the corruption found in the tables. If that is the

case, you have to choose option 1 if you want the report in question migrated.

CDWCR0055E There were no from lines queried from rpi.strings using the star schema star_schema_name for the

report report_name .

Explanation: This is an internal error indicating corrupt metadata. Expected report interface and DB2 Data

Warehouse Center metadata was not found. The report was skipped but migration of other reports will continue.

Administrator Response: Verify that this was a valid report created by the report interface that was expected to be

migrated. If it was, take a backup of the control database. Run FFDC and contact IBM Customer Support to help you

diagnose the problem.

CDWCR0056E There were no join lines queried from rpi.strings using the star schema star_schema_name for the

report report_name .

Explanation: This is an internal error indicating corrupt metadata. Expected report interface and IBM Data

Warehouse Center metadata was not found. The report was skipped but migration of other reports will continue.

Administrator Response: Verify that this was a valid report, created by the report interface, that was expected to be

migrated. If it was, take a backup of the control database. Run FFDC and contact IBM Customer Support to help you

diagnose the problem.

CDWCR0057E The insert into the rpi.counter failed. The return code is: return_code.

Explanation: This is probably a database error. This table contains an identity column which is a sequence number

that is used to create views for health check reports that have multiple queries. One row should have been inserted

but the executeUpdate JDBC code indicates that no rows were inserted. The report was skipped and migration will

continue with the next report.

Administrator Response: Take action based on the return code in the message or contact your DBA for assistance.

You can run the report migration tool again if this error is generated from a 1.1 to 1.2 upgrade. If this is a warehouse

pack for Version 1.1 installation, install the warehouse pack again after the problem is corrected.

CDWCR0058E The query of the counter column from RPI.counter failed.

Explanation: This is probably a database error. This table contains an identity column that is a sequence number

used to create views for health check reports that have multiple queries. One row should have been retrieved but the

executeUpdate JDBC code indicates that no rows were retrieved. The report was skipped and migration will continue

with the next report.

Administrator Response: Take action based on the return code in the message or contact your DBA for assistance.

You can run the migration again if this error is generated from a 1.1 to 1.2 upgrade. If this is a warehouse pack for

Version 1.1 installation, install the warehouse pack again after the problem is corrected.

CDWCR0054W • CDWCR0058E


CDWCR0059E An input output error occurred processing the file file_name. System error message: error_message.

Explanation: An error occurred trying to access files in the product_code/version directory. Usually the error is a

disk space or permission problem.


CDWCR0060E The file file_name was not deleted.

Explanation: The delete function did not delete the file that lists failed migrated reports. Java gives an error if there

is a problem deleting the file.


CDWCR0061E The file file_name was not deleted because the process does not have permission to read the file.

Explanation: The permissions for the named file are not correct. The report migration utility is called from the Tivoli

Data Warehouse installation that should have permission to access the named file.

Administrator Response: Verify that the error is generated from a Tivoli Data Warehouse installation program, that

it is run by a user with Administrator privileges, and that the permissions for the named file are correct.

CDWCR0062E An input output error occurred processing the file file_name. System error message: error_message.

Explanation: An error occurred trying to write the named reports.bad file. This file contains a list of files that failed

to migrate. Usually the error is a disk space or permission problem.


CDWCR0063E The file name, file_name derived from the product code and TWH_TOPDIR environment variable

is incorrect. System error message: error_message.

Explanation: This is an internal error. The named file does not exist. The Tivoli Data Warehouse installation should

have passed a valid product code.


CDWCR0064E An error occurred migrating reports. Error: error_text.

Explanation: There was an error that occurred while migrating reports.

Administrator Response: Take corrective action based on the information in the error message.

CDWCR0100E The name Name is not valid.

Explanation: This is an internal error. The names being processed are metadata that defines a report and should

have valid values. The name must contain at least one non-whitespace character.


CDWCR0101E The database name Name is not valid.

Explanation: This is an internal error. The database name should have a valid value in the migration XML file. It is

either empty or not a valid string.


CDWCR0102E Unable to decrypt the database password.

Explanation: This is an internal error. The password being processed should have a valid value. There was a

problem decrypting the database password specified in the migration XML file.




CDWCR0104E The data source user name Name is not valid.

Explanation: This is an internal error. The user name being processed should have a valid value. The data source

user name specified in the migration XML file is not valid.


CDWCR0105E There was a problem parsing the XML element Element.

Explanation: This is an internal error. The XML file built by the report migration utility contains errors. This file is

expected to be valid.


CDWCR0106E The report name Name is not valid.

Explanation: This is an internal error. The report name is expected to be valid. Report names must contain at least

one non-whitespace character.


CDWCR0107E The table name Name is invalid.

Explanation: This is an internal error. The report name is expected to be valid. Table names must contain at least

one non-whitespace character.


CDWCR0108E The join could not be added because the table Table does not exist.

Explanation: This is an internal error. The report metadata is expected to be valid. The XML representing the report

has a join defined to a table but there is no table element in the XML. XML is used internally to format and

transform report metadata.


CDWCR0109W The message key Key was not found.

Explanation: This is usually a warehouse pack error. Translated terms are provided by each warehouse pack

through a resource bundle (warehouse pack for Version 1.1) or an XML file (warehouse pack for Version 1.2). The

report has defined a term to be translated but that term was not found in the translated term table derived from the

resource bundle. There will be a term that was not translated on the report, but the report migrated and processing

will continue. This error might be expected when installing a patch as translations only occur for major releases.

Administrator Response: Contact IBM Customer Support to determine whether this is an expected error for the

warehouse pack.

CDWCR0110W The resource bundle Bundle is not available.

Explanation: This is an internal error. The resource bundle for standard report elements, group by clause, is

provided with the report migration utility. Some report elements will not be translated correctly during migration.

Processing will continue.


CDWCR0111E The connection to the database DB failed. The error is Error_text.

Explanation: This is usually a database configuration, database down, or other similar type error.

Administrator Response: Take action based on the error message or contact your database administrator.



CDWCR0150E The directory Dir does not exist.

Explanation: This is probably an internal error. The specified directory should have been created by the Tivoli Data

Warehouse installation process.

Administrator Response: Verify that the process you are running has permission to access the specified file. Run

FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0152E The file File_name is not a valid report interface XML document. The error is Error.

Explanation: This is an internal error. The migration XML file failed XML validation.


CDWCR0153E There was a problem processing the XML file File. The error is Error_text.

Explanation: This is an internal error. The report metadata is stored in an XML format during the report migration

process. The XML should have been generated correctly by the report migration utility but there was a problem

processing this intermediate file.


CDWCR0154E The XML file File is not a valid XML format.

Explanation: This is an internal error. The report metadata is stored in an XML format during the report migration

process. The XML file has a document type other than Report defined.


CDWCR0155E There was a problem converting the report created by the report interface Report to a Crystal

report. The error is: Error_text.

Explanation: This is usually an internal error. The error information gives details about the error.


CDWCR0156E The Crystal report named Name could not be saved to the file File. The error is: Error_text.

Explanation: This is usually an internal error. The report migration was successful, but there was a problem writing

the output Crystal report file. The error information gives details about the error.


CDWCR0157E The Crystal report application server (RAS) source developer kit (SDK) reported an error. The

error is: Error_text

Explanation: This is usually an internal error. The error information gives details about the error. An operation that

makes use of the Crystal report application server source developer kit failed. See the error text in the message for

details.


CDWCR0158E The report type Type is incorrect for the current converter Converter.

Explanation: This is an internal error. A conversion is being attempted but the conversion type and report type do

not match. The correct conversion routine should be used.




CDWCR0159E The formula FormulaName was not found in the template report.

Explanation: This is an internal error. Formulas are used in the report templates and should match what the

migration code is expecting.

Administrator Response: Verify that the report templates in the TWH_TOPDIR/report/migrate/template directory

have not been corrupted by restoring a backup. Run FFDC and contact IBM Customer Support to help you diagnose

the problem.

CDWCR0160E Conversion failed for the report Report Name. The error is Error_text.

Explanation: This is an internal error. Reports created with the report interface should migrate, but this report could

not be converted to a Crystal report. Processing of other reports will proceed.


CDWCR0161W Sort modification failed for the report Report Name. The error is Error.

Explanation: This is an internal error. The migration program should be able to set the sort order, but the

modification of the sorting options for this report failed. Processing will continue, but the report sort order may not

be the same as the original report.


CDWCR0162W The table Table Name could not be removed from the report Report Name.

Explanation: The report templates have tables defined but these are replaced by the tables specified in the report

created by the report interface. Deletion of the original table failed. This is usually harmless and processing will

continue.

Administrator Response: Check that the report displays the correct data. If not, run FFDC and contact IBM

Customer Support to help you diagnose the problem.

CDWCR0163W Generation of the translation XML for the report Report Name failed for language Language Code.


Explanation: This is an internal error. The report migration utility generates XML files that contain translated terms

for each migrated report. The translated terms in the XML file are used to display translated strings in reports when

viewed through ePortfolio. Translation will be unavailable for the named report and language.


CDWCR0191E The required system property Prop is missing.

Explanation: This is an internal error. The install should call the migration utility with correct parameters.


CDWCR0193E An error occurred migrating reports. The error is: error_text.

Explanation: There was an error while migrating reports to Crystal reports. The error information gives details

about the error.

Administrator Response: Take corrective action based on the information in the message.

CDWCR0200E The properties file passed to the Crystal connection utility is null.

Explanation: This is an internal error. The Tivoli Data Warehouse installation passed a null properties file name so

logging cannot be initialized.




CDWCR0201E The Crystal connection utility failed to initialize the message logger that is defined in the Name

properties file.

Explanation: This is an internal error if there have been no modifications to the properties file specified in the

message.

Administrator Response: Verify that the properties file is valid and is located in the

%tivoli_common_dir%\cdw\logs\properties directory. If this file has been edited or deleted try restoring a backup

version. Run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0202E The Crystal connection utility failed to initialize the trace logger that is defined in the Name

properties file.

Explanation: This is an internal error if there have been no modifications to the properties file specified in the

message.

Administrator Response: Verify that the properties file is valid and is located in the

%tivoli_common_dir%\cdw\logs\properties. If this file has been edited or deleted try restoring a backup version.

Run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0203E The directory parameter passed to the Crystal connection utility is null.

Explanation: This is an internal error. The Tivoli Data Warehouse installation program must pass the location of the

Crystal Enterprise SDK jar files.


CDWCR0204E The Crystal Enterprise server returned a failure message while trying to establish a session.

Explanation: The Crystal connection utility received a failure message from the Crystal Enterprise server when

trying to open a session. This error may be generated if the TWH_TOPDIR environment variable is incorrect or the

hostname, user name, or password specified for the Crystal Enterprise server is incorrect.

Administrator Response: Verify that the Crystal Enterprise server is up and running. If the domain of the Crystal

Enterprise server is not in the Domain name server (DNS) list of the machine attempting to make the connection, an

entry for the Crystal Enterprise server must be made in the host file. See the Installing and Configuring Tivoli Data

Warehouse guide for more information.

CDWCR0205E The version of the Crystal Enterprise server, version, is not the required version. The required

Tivoli version is required_version.

Explanation: The version of the specified Crystal Enterprise server is not the version required by Tivoli Data

Warehouse.

Administrator Response: Verify that the server host name specified is the Tivoli version of the Crystal Enterprise

server.

CDWCR0206E The call to retrieve the version of the Crystal Enterprise server failed.

Explanation: This is usually an internal error. The Crystal connection utility was able to logon and establish a

session using the Crystal interface, but the call to get the version failed. The Crystal connection utility uses the

Crystal source development kit interface to get the version of the installed server. This call failed.

Administrator Response: Verify that the Crystal Enterprise server is still active. Try restarting the server and

running the Tivoli Data Warehouse installation that failed again. Run FFDC and contact IBM Customer Support to

help you diagnose the problem.

CDWCR0207E The call to set the report application server keycode on the Crystal Enterprise server failed.

Explanation: This is usually an internal error as the Crystal connection utility was able to logon and establish a

session using the Crystal interface. The report migration utility uses the Crystal report application server source

development kit. The use of this source development kit requires a special keycode that is set by the Crystal

connection utility. This call failed.



Administrator Response: Verify that the Crystal server is still active. Verify that the OEM keycode is the only

keycode defined in the Crystal Enterprise server, restart the server, and run the Tivoli Data Warehouse installation

that failed again. Run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWCR0208E The Crystal Enterprise server call to delete the report application server keycode on the Crystal

Enterprise server failed.

Explanation: This is usually an internal error as the Crystal connection utility was able to logon and establish a

session using the Crystal interface. The report migration utility uses the Crystal report application server source

development kit. The use of this source development kit requires a special keycode that is set by the Crystal Connect

utility then deleted after the migration is complete. This call failed.

Administrator Response: Verify that the Crystal server is still active. Try restarting the server and running the Tivoli

Data Warehouse installation that failed again. Run FFDC and contact IBM Customer Support to help you diagnose

the problem.

CDWCR0209E An error occurred connecting to the Crystal Enterprise server. The error is: error_text.

Explanation: An error has occurred while trying to connect to the Crystal Enterprise server.

Administrator Response: Take corrective action based on the information in the message.

CDWCW0004E The twh_config_wep.pl program cannot write to the log message file file_name. The error is error.

Explanation: The program that configures warehouse packs could not open the log message file in append mode.

The file name is not valid or the file and directory permissions do not permit this operation to succeed.

Administrator Response: Make sure the file and directory permissions are correct.

CDWCW0005E The twh_config_wep.pl program cannot read the common logging properties file file_name. The

error is error.

Explanation: The program that configures warehouse packs could not open the common logging properties file in

read mode. The file name is not valid or the file and directory permissions do not permit this operation to succeed.


CDWCW0006E The tivoli_common_dir entry was not found in the common logging properties file file_name.

Explanation: The tivoli_common_dir entry in the common logging properties file defines the location of the Tivoli

common logging directory.

Administrator Response: Check the contents of the common logging properties file. If the file does not contain the

entry and you know what the correct value should be, manually edit the file and add the entry and value. If the

entry is not there and you do not know what the value should be, reinstall Tivoli Data Warehouse.

CDWCW0007W The entry entry that specifies the log message file name in the configWEP logging properties file

file_name is not valid. The program is setting the entry to the default value configwep_log.log.

Explanation: The entry supplies the name of the log message file for the program that configures warehouse packs.

The entry was left blank, so the program is setting the entry to the default value.

Administrator Response: No action is required.

CDWCW0009W The entry entry that specifies the debug level in the configWEP logging properties file file_name

is not valid. The program is setting the entry to the default value INFO.

Explanation: The entry specifies the level of trace information to gather for the program that configures warehouse

packs. Valid values are INFO, DEBUG_MIN, DEBUG_MID, and DEBUG_MAX.


CDWCR0208E • CDWCW0009W


CDWCW0010W The entry entry that specifies the trace message file name in the configWEP logging properties

file file_name is not valid. The program is setting the entry to the default value configwep_trc.log.

Explanation: No additional information is available for this message.

CDWCW0014E The twh_config_wep.pl program cannot append to the trace message file file_name. The error is

error.

Explanation: The program that configures warehouse packs could not open the trace message file in append mode.

The file name is not valid or the file and directory permissions do not permit this operation to succeed.

Administrator Response: Make sure the file name is valid and that the file and directory permissions are correct.

CDWCW0015E The twh_config_wep.pl program cannot read the configWEP logging properties file file_name. The

error is error.

Explanation: The program that configures warehouse packs could not open the configWEP logging properties file in

read mode. The file name is not valid or the file and directory permissions do not permit this operation to succeed.


CDWCW0021E An option that is not valid was specified in the twh_config_wep.pl program.

Explanation: The program that configures warehouse packs cannot continue. Refer to the usage statement for valid

command syntax.

Administrator Response: If the program ran from the command line, run it again, verifying that only valid options

are specified. If the program was called as part of an installation, run FFDC and contact IBM Customer Support. If

possible, specify the installation options that were selected.

CDWCW0031E The DBNAME value was not specified in the twh_config_wep.pl program.

Explanation: The program that configures warehouse packs requires that the database name of the control database

be specified using the -d parameter. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the DBNAME

information using the -d parameter. If the program was called as part of an installation, run FFDC and contact IBM

Customer Support. If possible, specify the installation options that were selected.

CDWCW0032E The DBUSER value was not specified in the twh_config_wep.pl program.

Explanation: The program that configures warehouse packs requires that the user for the control database be

specified using the -u parameter. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the DBUSER

information using the -u parameter. If the program was called as part of an installation, run FFDC and contact IBM


CDWCW0033E The DBPASS value was not specified in the twh_config_wep.pl program.

Explanation: The program that configures warehouse packs requires that the password for the control database be

specified using the -p parameter. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the DBPASS

information using the -p parameter. If the program was called as part of an installation, run FFDC and contact IBM


CDWCW0034E The FUNCTION value was not specified in the twh_config_wep.pl program.

Explanation: The program that configures warehouse packs requires that the agent site be specified using the -a

parameter. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the AGENTSITE

information using the -a parameter. If the program was called as part of an installation, run FFDC and contact IBM

CDWCW0010W • CDWCW0034E



CDWCW0035E The twh_config_wep.pl program ended with errors.

Explanation: The program that configures warehouse packs ended with errors. This message is always preceded by

other messages that describe the errors in more detail.

Administrator Response: Review the trace and message logs in the Tivoli common logging directory for previously

listed error information.

CDWCW0036E The CONFIGFILE value was not specified when the function was set to add, delete, update,

move, testconn or listconn in the twh_config_wep.pl program.

Explanation: The program that configures warehouse packs requires that the configuration file be specified with the

-c parameter when the function parameter is set to add, delete, update, testconn or listconn in the installation wizard

and when the function is set to add, delete or move from the command line when using twh_configwep.bat. The

program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the configuration file

name using the -c parameter. If the program was called as part of an installation, run FFDC and contact IBM


CDWCW0041E The twh_config_wep.pl program failed to set connection information.

The return code is return_code.

The function is: function.

The error is: error.

The database name is database_name.

The user is user_name.

Explanation: The information returned in the message provides specific information about the problem.

Administrator Response: Refer to the error message that was returned and take the actions specified. Review the

trace and message logs in the Tivoli common logging directory for previously listed error information.

CDWCW0042E The twh_config_wep.pl program failed to set configuration information.




The configWEP function is configwep_function.

The install flag is install_flag.

The top directory is directory.

The temporary directory is directory.

The trace file is file_name.




CDWCW0043E The twh_config_wep.pl program failed to configure the warehouse pack.






trace and message logs in the Tivoli common logging directory for previously listed error information and resolve

any problems you find.

CDWCW0035E • CDWCW0043E


CDWCW0044E The twh_config_wep.pl program failed to list information about the installed warehouse packs.




Explanation: The list function is only available from the command line.

Administrator Response: Review the trace and message logs in the Tivoli common logging directory for error

information.

CDWCW0045E The twh_config_wep.pl program failed to list the client/server connections and ODBC data

sources.







CDWCW0046E The twh_config_wep.pl program failed to process the configuration file configuration_file.







CDWCW0060E Usage: twh_configwep -u user -p password -f function -c configuration_file.

The twh_config_wep.pl program is used to:

Add one or many sources or central data warehouses to a warehouse pack.

Delete one or many sources or central data warehouses from a warehouse pack.

Move ETL processing to another agent site for a warehouse pack.

List installed warehouse packs.

The -u and -p parameters are the user name and password for the control database.

If the function is list, then the configuration file is not required.

If the function is add, delete or move, the configuration file should contain this entry

(as well as the entries described below):

AVA_CODE=<product code for application>

In the entries below <n> is a number. All the entries that relate to

the same source or central data warehouse should use the same number. Many

sources or many central data warehouses can be included in the same configuration file,

but a configuration file cannot contain both sources and central data warehouses.

1. If the function is add, then the configuration file should contain these entries:

a. For sources:

TDW_WSOURCE<n>_ODBC_DS_NAME=<ODBC data source name>

TDW_WSOURCE<n>_DB_TYPE=<database type> The value can be DB2UDB (DB2 UDB), DB2390

(DB2 for z/OS and OS/390), ORA (Oracle), INF (Informix®), SYB (Sybase), MSSQL (MS SQL Server)

or TEXT (text file).

TDW_WSOURCE<n>_CS_CONN_NAME=<client/server connection name>

TDW_WSOURCE<n>_DB_HOST=<fully-qualified host name where the database resides>

TDW_WSOURCE<n>_DB_PORT=<port used for the database at the database server host>

TDW_WSOURCE<n>_DB_NAME=<database name at the database server host>

TDW_WSOURCE<n>_DB_USER=<user for the database connection>

TDW_WSOURCE<n>_DB_PASS=<password for the database connection>

If the database type is DB2UDB, DB2390, or ORA, the

client/server connection will be created if it does not already exist.

If the client/server connection is created before running the twh_config_wep.pl program,

these parameters are not required:



TDW_WSOURCE<n>_DB_HOST, TDW_WSOURCE<n>_DB_PORT, and

TDW_WSOURCE<n>_DB_NAME.

If the database type is INF, SYB, or MSSQL, the

client/server connection must be created before running the twh_config_wep.pl program

and these parameters are not required:

TDW_WSOURCE<n>_DB_HOST, TDW_WSOURCE<n>_DB_PORT, and

TDW_WSOURCE<n>_DB_NAME.

If the database type is TEXT, set the following entry as indicated:

TDW_WSOURCE<n>_CS_CONN_NAME=<directory on the agent site where text files exist>.

The following parameters are not required: TDW_WSOURCE<n>_DB_HOST,

TDW_WSOURCE<n>_DB_PORT, and TDW_WSOURCE<n>_DB_NAME.

For all database types, the ODBC data source will be created if it does not exist.

If the ODBC data source does exist, it will be re-used.

b. For central data warehouses:

TDW_CDW<n>_ODBC_DS_NAME=<ODBC data source name>

2. If the function is delete, the configuration file should contain these entries:

a. For sources:

TDW_WSOURCE<n>_ODBC_DS_NAME=<ODBC data source name>

b. For central data warehouses:

TDW_CDW<n>_ODBC_DS_NAME=<ODBC data source name>

3. If the function is move, the configuration file should contain these entries:

a. For warehouse packs that include ETL1 processing:

TDW_CDW1_CLIENT_HOST=<Fully-qualified hostname of the new ETL1 agent site>

b. For warehouse packs that include ETL2 processing:

TDW_MART1_CLIENT_HOST=<Fully-qualified hostname of the new ETL2 agent site>


CDWCW0070E The environment variable TWH_TOPDIR is not set. Install Tivoli Data Warehouse, Version 1.2

before running this program.

Explanation: The TWH_TOPDIR environment variable sets the top-level directory in which the Tivoli Data

Warehouse files are installed. The default value on Windows systems is %ProgramFiles%\TWH\. The default value

on UNIX systems is /opt/twh/.

Administrator Response: Ensure the system was restarted after the installation of Tivoli Data Warehouse, Version

1.2. Review the trace and message logs in the Tivoli common logging directory for previously listed error

information. Reinstall Tivoli Data Warehouse, Version 1.2 if TWH_TOPDIR is still not set.

CDWCW0083E The ConfigWep.pm program cannot read the configuration file file_name. The error is error.

Explanation: An attempt to open the configuration file in read mode failed. This file is read by the ConfigWep.pm

program and contains information about the product (AVA) code, source databases, central data warehouses and data

mart databases that the warehouse pack uses. The file name is not valid or the file and directory permissions do not

permit this operation to succeed.

Administrator Response: Make sure the file and directory permissions are correct. Review the trace and message

logs for previously listed error messages.

CDWCW0085E The ConfigWep.pm program cannot read the inforesource.del file file_name. The error is error.

Explanation: An attempt to open the inforesource.del file in read mode failed. This file contains information about

warehouse sources and targets. The file name is not valid or the file and directory permissions do not permit this

operation to succeed.





CDWCW0089E The ConfigWep.pm program cannot append to the log message file file_name. The error is error.

Explanation: An attempt to open the log message file in append mode failed. The file name is not valid or the file

and directory permissions do not permit this operation to succeed.



CDWCW0090E The ConfigWep.pm program cannot write to the inforesource.del file file_name. The error is error.

Explanation: An attempt to open the inforesource.del file in write mode failed. This file contains information about

warehouse sources and targets. The file name is not valid or the file and directory permissions do not permit this




CDWCW0091E The ConfigWep.pm program cannot write to the new inforesource.del file file_name. The error is

error.

Explanation: An attempt to open the new inforesource.del file in write mode failed. This file contains changed

information about warehouse sources and targets. The file name is not valid or the file and directory permissions do

not permit this operation to succeed.



CDWCW0092E The ConfigWep.pm program cannot read the new relationship.del file file_name. The error is

error.

Explanation: An attempt to open the new relationship.del file in read mode failed. This file contains changed

information about relationships to warehouse sources and targets. The file name is not valid or the file and directory

permissions do not permit this operation to succeed.



CDWCW0093E The ConfigWep.pm program cannot write to the new relationship.del file file_name. The error is

error.

Explanation: An attempt to open the new relationship.del file in write mode failed. This file contains changed





CDWCW0094E The ConfigWep.pm program cannot append to the relationship.del file file_name. The error is

error.

Explanation: An attempt to open the relationship.del file in append mode failed. This file contains information

about relationships to warehouse sources and targets. The file name is not valid or the file and directory permissions

do not permit this operation to succeed.



CDWCW0095E The ConfigWep.pm program cannot read the relationship.del file file_name. The error is error.

Explanation: An attempt to open the relationship.del file in read mode failed. This file contains information about

relationships to warehouse sources and targets. The file name is not valid or the file and directory permissions do not






CDWCW0096E The ConfigWep.pm program cannot append to the trace message file file_name. The error is error.

Explanation: An attempt to open the trace message file in append mode failed. The file name is not valid or the file




CDWCW0097E The ConfigWep.pm program cannot append to the translate file file_name. The error is error.

Explanation: An attempt to open the translate file in append mode failed. This file contains translation information

for the database type. The file name is not valid or the file and directory permissions do not permit this operation to

succeed.



CDWCW0098E The ConfigWep.pm program cannot read the translate file file_name. The error is error.

Explanation: An attempt to open the translate file in read mode failed. This file contains translation information for

the database type. The file name is not valid or the file and directory permissions do not permit this operation to

succeed.



CDWCW0099E The ConfigWep.pm program cannot write to the translate file file_name. The error is error.

Explanation: An attempt to open the translate file in write mode failed. This file contains translation information for

the database type. The file name is not valid or the file and directory permissions do not permit this operation to

succeed.



CDWCW0100E The ConfigWep.pm program cannot find the AVA_CODE (product code) entry in the

configuration file file_name.

Explanation: The entry in the configuration file does not exist or the warehouse pack installation failed.

Administrator Response: Add the AVA_CODE entry to the configuration file if it is not there and try installing the

warehouse pack again. Review the trace and message logs in the Tivoli common logging directory for previously


CDWCW0101E A system error occurred. error_message.

Explanation: Refer to the error message.



CDWCW0103E An unsupported argument is used with the listconn option. Allowed arguments are (ALL).

Explanation: Use the ALL argument with the listconn option.


are specified. If the program was called as part of an installation, run FFDC and contact IBM Customer Support. If

possible, specify the installation options that were selected.



CDWCW0105E The control database password is not set for the ConfigWep.pm program.

Explanation: A program has invoked the setConnectionInfo method on a ConfigWep object with a zero-length string

as the third parameter, which is the value of the database password.

Administrator Response: If the program ran from the command line, run it again, providing the DBPASS

information using the -p parameter. If the program was called as part of an installation, run FFDC and contact IBM


CDWCW0106E The control database user is not set for the ConfigWep.pm program.

Explanation: A program has invoked the setConnectionInfo method on a ConfigWep object with a zero-length string

as the second parameter, which is the value of the database user.

Administrator Response: If the program ran from the command line, run it again, providing the DBUSER

information using the -u parameter. If the program was called as part of an installation, run FFDC and contact IBM


CDWCW0107E The temporary directory is not set for the ConfigWep.pm program.

Explanation: A program has invoked the prepare method on a ConfigWep object with a zero-length string as the

second parameter, which is the value of the temporary directory.


listed error messages.

CDWCW0108E The environment variable TWH_TOPDIR is not set for the ConfigWep.pm program.


second parameter, which is the value of the Tivoli Data Warehouse top directory. The top directory is set with the

TWH_TOPDIR environment variable and is the top-level directory in which the Tivoli Data Warehouse files are

installed.

Administrator Response: Ensure the system was restarted after the installation of Tivoli Data Warehouse, Version

1.2. Review the message logs in the Tivoli common logging directory. Reinstall Tivoli Data Warehouse, Version 1.2 if

TWH_TOPDIR is still not set.

CDWCW0111E The ConfigWep.pm program failed to store temporary directory settings.

Explanation: This is an internal error.



CDWCW0112E The warehouse pack with product (AVA) code product_code is not installed.

Explanation: The warehouse pack is not installed.

Administrator Response: Run twh_wepinstall located in TWH_TOPDIR/install/bin to install the warehouse pack.

Review the trace and message logs in the Tivoli common logging directory for previously listed error messages.

CDWCW0120E The ConfigWep.pm program failed to retrieve the database type for the ODBCcfg program.

Explanation: The ODBCcfg program configures ODBC data source information. This is an internal error.



CDWCW0121E The ConfigWep.pm program failed to retrieve the database type for the dbsetup program.






CDWCW0122E The ConfigWep.pm program failed to retrieve the database type for the translate file name.




CDWCW0123E The ConfigWep.pm program failed to retrieve the database type.




CDWCW0124E The warehouse pack role role is not valid. The add, delete, and update functions can only be

used on a warehouse pack whose role is ETL1, ETL2, E1E2, or MCDW.

Explanation: The warehouse pack role defines the type of ETL processing that occurs for the warehouse pack.

Administrator Response: Uninstall the warehouse pack and reinstall it. If the program ran from the command line,

run it again, verifying that only valid options are specified.

CDWCW0125E The database type for the function function with dependent entries is not valid. When the

TDW_WSOURCEn_DB_NAME, TDW_WSOURCEn_DB_PORT, and TDW_WSOURCEn_DB_HOST

entries are used in the configuration file, valid values for the TDW_WSOURCEn_DB_TYPE entry

are DB2UDB, DB2390, or ORA.

Explanation: The combination of entries in the configuration file is not valid. The warehouse pack installation will

create a valid connection type if the database type is DB2UDB, DB2390, or ORA.


are specified. If the program was called as part of an installation, review the trace and message logs in the Tivoli

common logging directory for previously listed error messages.

CDWCW0127E The function function is not valid. Valid values are add, delete, move, get or list.

Explanation: Valid values are add, delete, move, get or list.




CDWCW0128E The function function is not valid. Valid values are add, delete, update, list or listconn.

Explanation: Valid values are add, delete, update, list or listconn.




CDWCW0129E The ODBC data source data_source is already associated with the warehouse pack.

Explanation: The warehouse pack already uses the ODBC data source name that was specified.




CDWCW0141E A warehouse pack configuration file entry entry is not valid. For a wep_role warehouse pack called

from the program program with function function, these entries are allowed: entry_list, where n is a

number.

Explanation: The warehouse pack role defines the type of ETL processing that occurs for the warehouse pack. Refer

to Installing and Configuring Tivoli Data Warehouse or the usage statement for more information about the combination



of entries allowed in the configuration file for each function and warehouse pack role.




CDWCW0142E No changes can be made to a warehouse pack whose role is ETL2.

Explanation: It is not possible to add or delete source databases or central data warehouse databases for a

warehouse pack with a role of ETL2.




CDWCW0143E No value was found for the entry entry. For a wep_role warehouse pack called from the program

program with function function, a value must be provided for the entry entry, where n is a number.







CDWCW0144E A required entry entry was not found. For a wep_role warehouse pack called from the program

program with function function, these entries are required: entry_list, where n is a number.







CDWCW0145E No value was found for an entry entry that is required based on other entries. For a wep_role

warehouse pack called from the program program with function function, when a value is provided

for one of these entries (entry_list), a value must be provided for all of these entries (entry_list),

where n is a number.







CDWCW0146E The data_source_name source database cannot be deleted from this warehouse pack because it is

the default source database for the warehouse pack.

Explanation: An ODBC data source is set as the default source database for each warehouse pack. Other ODBC data

sources can be added and deleted, but the default data source cannot be deleted.






CDWCW0147E The cdw_name central data warehouse database cannot be deleted from this warehouse pack

because it is the default central data warehouse database for the warehouse pack.

Explanation: A central data warehouse is set as the default central data warehouse database for each warehouse

pack. Other central data warehouses can be added and deleted, but the default central data warehouse cannot be

deleted.




CDWCW0148E The number of source databases (number) is not valid. For a wep_role warehouse pack called from

the program program with function function, number source databases must be provided.







CDWCW0149E The number of central data warehouse databases (number) is not valid. For a wep_role warehouse

pack called from the program program with function function, number central data warehouse

databases must be provided.







CDWCW0150E The number of data mart databases (number) is not valid. For a wep_role warehouse pack called

from the program program with function function, number data mart databases must be provided.







CDWCW0152E More than one client host is being used for central data warehouse databases for this warehouse

pack.

Explanation: A client host is an agent site where central data warehouses are defined. Only one client host can be

used as a source database at one time in a configuration file.




CDWCW0153E More than one client host is being used for source databases for this warehouse pack.

Explanation: Only one client host, or agent site where central data warehouses are defined, can be used as the

source database at one time in a configuration file.






CDWCW0154E All ODBC data sources that refer to data mart databases must be defined at the same client host.

Explanation: ODBC data sources that create connections to or from data marts must be defined at the same client

host, or agent site.




CDWCW0155E All ODBC data sources that refer to source databases and central data warehouse databases must

be defined at the same client host.

Explanation: Only one client host, or agent site where central data warehouses are defined, can be used as the

source database at one time in a configuration file.




CDWCW0156E The database type for the add or delete function is not valid. Valid values for

TDW_WSOURCEn_DB_TYPE are DB2UDB, DB2390, ORA, SYB, MSSQL, INF, or TEXT.

Explanation: The value specified for the database type in the configuration file is not valid.




CDWCW0161E A failure was detected during rollback processing.

The rollback function is function.

The rollback error is error.

The original function is function.

The original error is error.

Explanation: A failure was detected and the ConfigWep.pm program attempted to undo (rollback) the changes

made before the failure occurred. However, this rollback operation was not successful.

Administrator Response: Review the trace and message logs in the Tivoli common logging directory.

CDWCW0162E The ODBC data source name in the configuration file is not set.

Explanation: The ODBC data source name is specified by the TDW_WSOURCE<n>_ODBC_DS_NAME entry in the

configuration file that is called by the program that configures warehouse packs.




CDWCW0163E The client host name in the configuration file is not set.

Explanation: The ODBC data source name is specified by the TDW_WSOURCE<n>_CLIENT_HOST entry in the

configuration file that is called by the program that configures warehouse packs.




CDWCW0166E The parameters of the ODBC data source for the source database found in the configuration file

do not match the parameters found in the Tivoli Data Warehouse Registry. The following

parameters do not match: parameter_list.

Explanation: The Tivoli Data Warehouse Registry contains internal metadata that is used by Tivoli Data Warehouse.






CDWCW0168E No row was found in the twg.odbc_comp_profile table for the primary reference to this ODBC

data source. The ODBC data source is parameter_list and the client host is client_host.

Explanation: This is an internal error. The table describes specific Tivoli Data Warehouse components and contains

the components’ metadata.



CDWCW0170E The following warehouse packs are in an inconsistent state: wep_list.

Explanation: A previous failure has left the warehouse packs in an inconsistent state. The warehouse packs must be

restored to a consistent state or uninstalled before using Tivoli Data Warehouse.


listed error messages. If the warehouse packs cannot be restored to a consistent state, uninstall them using

twh_wepuninstall located at TWH_TOPDIR/install/bin.

CDWCW0171E The ConfigWep.pm program cannot read the intransit file file_name. The error is error.

Explanation: An attempt to open the intransit file in read mode failed. This file is used to indicate that a warehouse

pack is being configured. This file is deleted when the configuration of the warehouse pack completes successfully. If

the configuration fails to complete successfully and the changes cannot be undone, the existence of this file indicates

that the warehouse pack is in an inconsistent state. The file name is not valid or the file and directory permissions do



logs in the Tivoli common logging directory.

CDWCW0172E The ConfigWep.pm program cannot write to the intransit file file_name. The error is error.

Explanation: An attempt to open the intransit file in write mode failed. This file is used to indicate that a warehouse

pack is being configured. This file is deleted when the configuration of the warehouse pack completes successfully. If

the configuration fails to complete successfully and the changes cannot be undone, the existence of this file indicates

that the warehouse pack is in an inconsistent state. The file name is not valid or the file and directory permissions do




CDWCW0173E The ConfigWep.pm program cannot append to the inforesource.del file file_name. The error is

error.

Explanation: An attempt to open the inforesource.del file in append mode failed. This file contains information

about warehouse sources and targets. The file name is not valid or the file and directory permissions do not permit

this operation to succeed.



CDWCW0174E The ConfigWep.pm program cannot read the backup inforesource.del file file_name. The error is

error.

Explanation: An attempt to open the backup inforesource.del file in read mode failed. This file contains a copy of







CDWCW0175E The ConfigWep.pm program cannot write to the backup inforesource.del file file_name. The error

is error.

Explanation: An attempt to open the backup inforesource.del file in write mode failed. This file contains a copy of





CDWCW0176E The ConfigWep.pm program cannot read the backup relationship.del file file_name. The error is

error.

Explanation: An attempt to open the backup relationship.del file in read mode failed. This file contains a copy of





CDWCW0177E The ConfigWep.pm program cannot write to the backup relationship.del file file_name. The error

is error.

Explanation: An attempt to open the backup relationship.del file in write mode failed. This file contains a copy of





CDWCW0178E The ConfigWep.pm program cannot write to the new relationship.del file file_name. The error is

error.

Explanation: An attempt to open the new relationship.del file in write mode failed. This file contains changed





CDWCW0179E The ConfigWep.pm program cannot write to the ConfigWep ODBC data sources file file_name.

The error is error.

Explanation: An attempt to open the configWEP ODBC data sources file in write mode failed. This file contains

ODBC data source information from remote agent systems. The file name is not valid or the file and directory




CDWCW0180E The ConfigWep.pm program cannot write to the ODBC data sources file file_name. The error is

error.

Explanation: An attempt to open the configWEP ODBC data sources file in write mode failed. This file contains

ODBC data source information from the control server. The file name is not valid or the file and directory






CDWCW0181E The ConfigWep.pm program cannot read the React.pm ODBC data sources file file_name. The

error is error.

Explanation: An attempt to open the React.pm ODBC data sources file in read mode failed. This file contains ODBC

data source information from remote agent systems. The file name is not valid or the file and directory permissions




CDWCW0182E The ConfigWep.pm program cannot read the new inforesource.del file file_name. The error is

error.

Explanation: An attempt to open the new inforesource.del file in read mode failed. This file contains changed





CDWCW0183E The ConfigWep.pm program failed to update extract control information because no central data

warehouse is associated with this warehouse pack.

Explanation: When the program is removing sources, it checks the extract control database. If no central data

warehouse is associated with the warehouse pack, the program will fail. An uninstallation might have failed after

breaking the central data warehouse connection.




CDWCW0184E More than one directory or file whose name starts with v exists in the apps/AVA directory under

the Tivoli Warehouse top directory.

Explanation: Only one directory whose name starts with v should exist in the apps/ AVA directory under the Tivoli

Warehouse top directory, where AVA is the product code.


CDWCW0186E The wep_name warehouse pack is in an inconsistent state. The intransit file must be deleted.

Explanation: The intransit file could not be deleted. This file is used to indicate that a warehouse pack is being

configured. This file is deleted when the configuration of the warehouse pack completes successfully. If the

configuration fails to complete successfully and the changes cannot be undone, the existence of this file indicates that

the warehouse pack is in an inconsistent state.

Administrator Response: Delete the intransit file to restore the warehouse pack to a consistent state.

CDWCW0187E The control database name is not set for the ConfigWep.pm program.


first parameter, which is the value of the control database name.


CDWCW0188E The ConfigWep.pm program failed to configure the warehouse pack. The following list contains

the ODBC data sources, client/server connections, TCP/IP nodes, DCS nodes and translate file lines

that were added or deleted as a result of a failed attempt to configure the wep_name warehouse pack.

Explanation: Manual intervention is required to restore the warehouse pack to a consistent state.

Administrator Response: To restore the warehouse pack to a consistent state:

1. For lines starting with ADDED, manually remove the entries described in the list.



2. For lines starting with DELETED, manually add the entries described in the list.

Once this is done, remove the AVA_configwep_in_trans file in the apps directory under the Tivoli Data Warehouse

top directory.

CDWCW0189E The ConfigWep.pm program was unable to establish a connection to the host host.

Explanation: The program is trying to establish a connection to a source database, remote agent site, or so forth.

Administrator Response: Ping the host to see if it is available on the network. Review the trace and message logs in

the Tivoli common logging directory.

CDWCW0190E The wep_name warehouse pack is in an inconsistent state.

The restore function is function.

The restore error is error.

The previous function is function.

The previous error is error.


Administrator Response: Uninstall the warehouse pack using twh_wepuninstall located at

TWH_TOPDIR/install/bin. Review the trace and message logs in the Tivoli common logging directory.

CDWCW0191E The database type database_type is unsupported.

Explanation: An attempt to create a client/server connection failed because the database type is not valid.


CDWCW0192E No previous version of the warehouse pack was found.

Explanation: An attempt to patch a warehouse pack failed because no previous version of the warehouse pack was

found.


CDWCW0193E More than one active version of the wep_name warehouse pack exists.

Explanation: Only one version of a warehouse pack can be active at a time.


CDWCW0194E One or many test connections to the ODBC data sources failed.

Explanation: One or many test connections to the ODBC data sources failed.


CDWCW0195E The ConfigWep.pm program cannot read the ConfigWep ODBC data sources file file_name. The

error is error.

Explanation: The program that configures warehouse packs could not open the configWEP ODBC data sources file

in read mode. The file name is not valid or the file and directory permissions do not permit this operation to

succeed.


CDWCW0295E The test connection to the ODBC data source failed.

Explanation: The test connection to the ODBC data source failed.




CDWCW0296E No changes were made. The new agent site(s) specified are the same as the existing agent site(s)

used by the warehouse pack.

Explanation: When using the move option for the ConfigWep.pm program, the agent site(s) specified in the

configuration file should be different from the agent site(s) currently used by the warehouse pack.

Administrator Response: Run the program again and make sure that only valid options are specified.

CDWCW0800W The ODBC data source odbc_name is not being used by the warehouse pack wep_name.



CDWCW0803W The database type for the function function with dependent entries is not valid. When the

TDW_WSOURCEn_DB_NAME, TDW_WSOURCEn_DB_PORT, and TDW_WSOURCEn_DB_HOST

entries are used, valid values for TDW_WSOURCEn_DB_TYPE are DB2UDB, DB2390, or ORA.


Explanation: The value specified for the database type in the configuration file is not valid. This value is specified

in the configuration file and will not prevent the uninstallation from occurring.


CDWCW0804W The database type for the Add or Delete function is not valid. Valid values for

TDW_WSOURCEn_DB_TYPE are DB2UDB, DB2390, ORA, SYB, MSSQL, INF, or TEXT. Processing

will continue.

Explanation: The value specified for the database type in the configuration file is not valid. This value is specified

in the configuration file and will not prevent the uninstallation from occurring.


CDWCW0806W No value was found for an entry entry that is required based on other entries. For a wep_role

warehouse pack called from the program program with function function, when a value is provided

for one of these entries (entry_list), a value should be provided for all of these entries (entry_list),

where n is a number. Processing will continue.

Explanation: These values are specified in the configuration file and will not prevent the uninstallation from

occurring.


CDWCW0807W The number of source databases number is not valid. For a wep_role warehouse pack called from

the program program with function function, number source databases should be provided. Processing

will continue.

Explanation: Source databases are specified in the configuration file and will not prevent the uninstallation from

occurring.


CDWCW0808W The number of central data warehouse databases (number) is not valid. For a wep_role warehouse

pack called from the program program with function function, number central data warehouse

databases should be provided. Processing will continue.

Explanation: Central data warehouse databases are specified in the configuration file and will not prevent the

uninstallation from occurring.


CDWCW0296E • CDWCW0808W


CDWCW0809W The number of data mart databases (number) is not valid. For a wep_role warehouse pack called

from the program program with function function, number data mart databases should be provided.


Explanation: Data mart databases are specified in the configuration file and will not prevent the uninstallation from

occurring.


CDWCW0810W No value was found for an entry entry. For a wep_role warehouse pack called from the program

program with function function, a value must be provided for the entry entry, where n is a number.


Explanation: The entry is specified in the configuration file and will not prevent the uninstallation from occurring.


CDWCW0811W No central data warehouse databases are associated with this warehouse pack. Processing will

continue.


CDWCW0812W A failure was detected while configuring warehouse pack. Any changes made before the failure

will now be rolled back. Processing will continue.


CDWCW0813W There are missing values for one or many entries. The following entries are not set: entry_list.



CDWCW0814W No row was found in the odbc_datasource table for the entry_list ODBC data source. The client

host is host_name. Processing will continue.


CDWCW0815W The wep_name warehouse pack is not installed. Processing will continue.


CDWCW0816W The following warehouse packs are in an inconsistent state: wep_names. Continuing to uninstall

the warehouse pack.


CDWCW0817W The ConfigWep.pm program failed to update extract control information because no central data

warehouse is associated with this warehouse pack. Since this happened during a rollback,

processing will continue.


CDWCW0818W A failure was detected while configuring warehouse pack. No changes were made. Processing

will continue.


CDWCW0809W • CDWCW0818W


CDWCW0819W No changes were made.


CDWDI0003E The program that accesses user information (DBInfoMgr) ended with an error.

Explanation: Other error messages are returned with this error message.

Administrator Response: Review the program message logs in the Tivoli common logging directory for previously


CDWDI0004E The program that accesses user information (DBInfoMgr) was unable to obtain a message or trace

logger.

Explanation: The program could not write the program messages and cannot continue. The Tivoli common logging

directory file system might be out of space or the file system might be unavailable.

Administrator Response: Verify that the file system containing the Tivoli common logging directory is available and

has sufficient space available.

CDWDI0005E The following arguments are not valid and were passed to the program that accesses user

information (DBInfoMgr): arguments.

Explanation: The program cannot continue because arguments that are not valid were specified.

Administrator Response: Run FFDC and contact IBM Customer Support for assistance reviewing the program log

and trace files in the Tivoli common logging directory.

CDWDI0007E The program that accesses user information (DBInfoMgr) was called with a -b argument,

indicating that a business view name would be supplied. However, no BusinessView name was

supplied.

Explanation: The program cannot continue because the business view name was not supplied.

Administrator Response: Fix the command line arguments supplied to the program and run it again. If it is a Data

Warehouse Center step, verify the arguments in the properties window for the step.

CDWDI0008E The program that accesses user information (DBInfoMgr) was called with a -i argument, indicating

that an InfoResource name would be supplied. However, no InfoResource name was supplied.

Explanation: The program cannot continue because the information resource name was not supplied.

Administrator Response: Fix the command line arguments supplied to the program and run it again.

CDWDI0009E The program that accesses user information (DBInfoMgr) was called with an unsupported

argument unsupported_argument.




CDWDI0010E The program that accesses user information (DBInfoMgr) was called without specifying one of the

following required arguments: -v, -i, -b, or -a.

Explanation: The program did not detect a required argument and cannot continue.



CDWCW0819W • CDWDI0010E


CDWDI0011E The program that accesses user information (DBInfoMgr) was called with an argument

unique_argument and also other arguments. However, no other arguments can be specified when

using unique_argument.

Explanation: The program detected a combination of arguments that is not valid and cannot continue.



CDWDI0012E The program that accesses user information (DBInfoMgr) did not find a warehouse source_or_target

associated with the business view supplied with the -b command.

Explanation: The IWH.INFORESOURCE table on the control server does not contain an InfoResource record for the

supplied input values. An InfoResource is either a warehouse source or a warehouse target in the Data Warehouse

Center. A warehouse source is required for any business view. However, a warehouse target is optional.

Administrator Response: If appropriate, associate the warehouse business view with an InfoResource source or

target.

CDWDI0013W The SQL statement issued to determine the following information did not return any data:

sql_output_information.

Explanation: The program that accesses user information (DBInfoMgr) issues SQL statements to retrieve information

stored in the database. No data being returned might result in a program error, depending on whether this

information is required. This message is logged to assist in debugging the program if it ends in error.

Administrator Response: Review the program message logs in the Tivoli common logging directory for previously


CDWDI0014E The SQL statement issued to determine the sql_output_information returned an error.

Explanation: The program that accesses user information (DBInfoMgr) issues SQL statements to retrieve information

stored in the database.

Administrator Response: Run FFDC and contact IBM Customer Support for assistance reviewing the program

message and trace logs in the Tivoli common logging directory to determine the details of the SQL failure. Verify that

the control server database is active and available.

CDWDI0015W The program that accesses user information (DBInfoMgr) did not find a database name associated

with the inforesource_name InfoResource.

Explanation: The InfoResource, that is either a warehouse source or a warehouse target, does not specify a database

name.

Administrator Response: Update the InfoResource to specify a database name.

CDWDI0016E The program that accesses user information (DBInfoMgr) was not able to obtain the vault

information and cannot continue.

Explanation: The program depends on the vault information to access the control server database.



CDWDI0017E The program that accesses user information (DBInfoMgr) was not able to determine the control

server database name and cannot continue.

Explanation: The program depends on the control server database in order to access the Tivoli Data Warehouse

metadata.



CDWDI0011E • CDWDI0017E


CDWDI0018E The program that accesses user information (DBInfoMgr) was not able to determine the control

server host name and cannot continue.

Explanation: The program depends on the control server host name in order to access the Tivoli Data Warehouse

metadata.



CDWDI0019E The program that accesses user information (DBInfoMgr) was not able to determine the

warehouse service name and cannot continue.

Explanation: The program depends on the warehouse service name in order to access the Tivoli Data Warehouse

metadata.



CDWDI0021E The program that accesses user information (DBInfoMgr) was called with a -a argument,

indicating that an agent site name would be supplied. However, no agent site name was supplied.

Explanation: The program cannot continue because an agent site name was not supplied.


CDWDI0022E The program that accesses user information (DBInfoMgr) was called with a -p argument,

indicating that a password would be supplied. However, no password was supplied.

Explanation: The program cannot continue because a password was not supplied.


CDWDI0023E The program that accesses user information (DBInfoMgr) was called with a -i argument, and also

arguments other than -p. However, when specifying -i, only the -p argument is allowed.




CDWDI0024E The program that accesses user information (DBInfoMgr) was called with a -a argument, and also

arguments other than -p. However, when specifying -a, only the -p argument is allowed.




CDWDI0025E The program that accesses user information (DBInfoMgr) was called with a -b argument, and also

-p. However, when specifying -b, the -p argument is not allowed.

Explanation: The program cannot continue because an argument that is not valid was specified.



CDWDI0026E TWH_TOPDIR is not set.

Explanation: The value of TWH_TOPDIR must be set using the -D argument when calling the program that

accesses user information (DBInfoMgr).

Administrator Response: Run the program again, specifying the TWH_TOPDIR value using the -D argument.



CDWDI0028E The program that accesses user information (DBInfoMgr) failed to connect to the control database.

Explanation: The error could be a failure in the connection attempt, not valid or missing connection information, or

an inability to locate or reach the database server where the control database resides.

Administrator Response: Review program message logs in the Tivoli common logging directory for more details

about the error.

CDWDI0029E A trace logger could not be set up and the program that accesses user information (DBInfoMgr)

cannot run because of an environment configuration error.

Explanation: The program traces a base set of messages as it runs to facilitate debugging. The software that is used

to trace messages could not start.

Administrator Response: Correct the environment, checking the class path and the command used to start the

program. Run the program again.

CDWDI0030E A message logger could not be set up and the program that accesses user information

(DBInfoMgr) cannot run because of an environment configuration error.

Explanation: The program logs a base set of messages as it runs to facilitate debugging. The software that is used to

log messages could not start.



CDWDI0035E The program that accesses user information (DBInfoMgr) could not open or load either the

log.properties file or the DBInfoMgrlogging.properties file.

Explanation: These files are necessary for configuring message and trace logging.


program. Check the informational paths displayed by the program and verify that they are correct. Run the program

again.

CDWDI0036E The program that accesses user information (DBInfoMgr) encountered an error when trying to

start message and trace logging. This is caused by an error in the environment.

Explanation: The program could not start message and trace logging because of an error in the environment.



again.

CDWDI0037E The program that accesses user information (DBInfoMgr) did not find any agent site information

for an agent site named agent_site_name.

Explanation: The Data Warehouse Center does not have any information regarding an agent site by this name. An

agent site by this name might not exist in the Data Warehouse Center.

Administrator Response: Verify that the agent site name is spelled correctly and that the agent site exists in the

Data Warehouse Center.

CDWDI0038E The BusinessView name must be 80 characters or less.

Explanation: The business view name supplied with the -b argument was too long.

Administrator Response: Run the program again, specifying a BusinessView name of 80 characters or less.



CDWDI0039E The IRName must be 80 characters or less.

Explanation: The InfoResource name supplied with the -i argument was too long.

Administrator Response: Run the program again, specifying an IRName value of 80 characters or less.

CDWDI0040E The AgentSite name must be 80 characters or less.

Explanation: The agent site name supplied with the -a argument was too long.

Administrator Response: Run the program again, specifying an AgentSite name of 80 characters or less.

CDWDI0041E The password must be 14 characters or less.

Explanation: The password supplied with the -p argument was too long.

Administrator Response: Run the program again, specifying a password of 14 characters or less.

CDWDI0042W The program that accesses user information (DBInfoMgr) encountered a warning condition but is

able to continue. possible_warning_text. Review the message logs for details of the warning condition.


CDWDI0043E The program that accesses user information (DBInfoMgr) encountered an error condition and is

unable to continue. possible_error_text

Explanation: The DBInfoMgr program has found an error when trying to access user information.

Administrator Response: Review the message logs for details of the error condition. If necessary, run FFDC and

contact IBM Customer Support to help diagnose the problem.

CDWET0001E No environment variable environment_variable was found. Source the environment script

script_name first.

Explanation: An environment variable that is necessary to run the configuration tool was not set.

Administrator Response: Source the client environment setup script that was provided by the vendor to set the

required environment variable. Then rerun the configuration tool.

CDWET0002E The configuration tool does not recognize the current operating system operating_system.

Explanation: Refer to the Tivoli Data Warehouse Release Notes for a list of supported operating systems.

Administrator Response: Make sure that Tivoli Data Warehouse is installed on a supported operating system.

CDWET0003E The ODBC Driver library file file_name could not be found.

Explanation: The configuration tool cannot find an ODBC Driver library file that is needed to connect to an ODBC

data source.

Administrator Response: Verify that the DB2 Data Warehouse Center Agent has been installed on this machine.

Also verify that the IWH.environment configuration script contains an entry for ODBCINI which points to a valid

.odbc.ini file and that this script has been sourced prior to running the configuration tool.

CDWET0004E The ODBC data source name data_source_name is already defined in the file file_name.

Explanation: The data source was already defined. ODBC data source names must be unique.

Administrator Response: Verify that the defined data source connects to the intended database. If not, create a new

ODBC data source with a different name.

CDWDI0039E • CDWET0004E


CDWET0005E The configuration tool cannot write to the file file_name. An error was returned: error.

Explanation: The configuration tool could not write to the file. Refer to the returned error message for more

information.

Administrator Response: Verify that you have permission to access the file.

CDWET0006E The configuration tool cannot find the ODBC data source data_source_name in the file file_name.

Explanation: The configuration tool cannot find the ODBC data source entry in the .odbc.ini file.

Administrator Response: Verify that the data source name has not been misspelled and that the ODBCINI

environment variable points to a valid .odbc.ini file.

CDWET0007E The program is unable to retrieve a list of installed ODBC drivers.

Explanation: The configuration tool scanned the installed ODBC drivers for this system, but no results were

returned. No ODBC drivers are available to set up System ODBC Data Sources.

Administrator Response: In the ODBC Data Source Administrator window, select the Drivers tab for a list of ODBC

drivers that are installed on the system. Verify that the ODBC drivers were properly installed. If necessary, install the

drivers again.

CDWET0008E An ODBC driver named driver_name was not found.

Explanation: The ODBC driver mentioned in the message is not installed on the system for the DBMS vendor that

was entered in the installation GUI.

Administrator Response: Verify that the name entered for the DBMS vendor is correct and supported. Refer to

Tivoli Data Warehouse Release Notes for a list of supported vendors. Verify that the ODBC drivers supported by the

configuration tool were properly installed with the DB2 Data Warehouse Center. If necessary, install the drivers again.

CDWET0009E The DBMS vendor vendor_name is not currently supported by the configuration tool.

Explanation: The configuration tool does not recognize the DBMS vendor name.

Administrator Response: Check for spelling errors in the DBMS vendor name. If spelling is correct, verify that the

vendor is supported. Refer to Tivoli Data Warehouse Release Notes for a list of supported vendors.

CDWET0010E The configuration tool was unable to create an ODBC data source using the parameters provided.

The error message is: error.

Explanation: An error occurred while attempting to create an ODBC data source entry. Check the system error

message for more details.

Administrator Response: Check the system error message for details about the ODBC data source creation failure.

Ensure that all parameters are spelled correctly and are valid for the vendor.

CDWET0011E The parameter list that was supplied to the configuration tool is not complete.

Explanation: Not enough parameters were supplied in the installation GUI.

Administrator Response: Check the usage statement that was returned and rerun the configuration tool with the

appropriate parameters.

CDWET0012W A failure was returned by DB2 while trying to create the catalog entry catalog_entry.

The following command was entered: command.

The following error was returned: error.

Explanation: The configuration tool received an error from DB2 when it attempted to catalog a database name, node

name, or database alias.

Administrator Response: Identify the type of error that occurred by checking the returned message. If an identically

CDWET0005E • CDWET0012W


named entry exists which is not used by some other process, remove the catalog entry and rerun the configuration

tool.

CDWET0013E A failure was returned by DB2 while trying to remove the catalog entry catalog_entry.

The following command was entered: command.


Explanation: The configuration tool received an error from DB2 when it attempted to uncatalog a database name,

node name, or database alias.

Administrator Response: Identify the type of error that occurred by checking the returned message. Also check the

spelling of the catalog entry that was provided to the configuration tool.

CDWET0014E The connection test failed. The user name and password must be provided.

Explanation: The user name or the password was not provided when testing the connection. Both are needed to

perform a valid test.

Administrator Response: Provide both the user name and the password when testing the connection.

CDWET0015E The connection test failed. The return code is: return_code.


Explanation: The configuration tool failed during a connection test.

Administrator Response: Check the message returned for more information. If available, run the setup script

provided by the DBMS vendor (such as db2profile.sh for DB2) prior to rerunning the configuration tool.

CDWET0016E The DBMS environment has not been properly configured for the vendor vendor.

The command entered to check the environment is: command.


Explanation: The configuration tool determined that the DBMS environment was not properly set up.

Administrator Response: Check the message returned for more information. If available, run the setup script

provided by the DBMS vendor (such as db2profile.sh for DB2) prior to rerunning the configuration tool.

CDWET0017E No database name or node name was provided.

Explanation: The configuration tool requires either the database name or the node name to complete the request.

Administrator Response: Provide the database name or the node name as indicated in the usage statement for the

configuration tool.

CDWET0018E An error occurred while opening the file file_name.


Explanation: The configuration tool cannot read the tnsnames.ora file.

Administrator Response: Check the message returned for more information. Verify that the file exists and that it is

readable and writable by the configuration tool.

CDWET0019E The Oracle client net service name service_name has already been configured and does not match

the configuration parameters.

The TNSNames file is file_name.

Explanation: The net service name located in the tnsnames.ora file does not contain the same configuration

parameters that were used by the configuration tool.

Administrator Response: Update the net service name entry in the tnsnames.ora file so that the address

specification (port and server name) and connect data match or simply delete the entry and recreate it.

CDWET0013E • CDWET0019E


CDWET0020E The program program_name does not exist or could not be located in the current path.

Explanation: The configuration tool could not access the program.

Administrator Response: Verify that the program exists and is in the current path.

CDWET0021E The option option is not supported for the vendor vendor.

Explanation: A request was made to the configuration tool which is not supported for the indicated vendor.

Administrator Response: Check that the option you provided is appropriate for the vendor you specified.

CDWET0022E The DB2 catalog entry data_source_name already exists.

You cannot create a DB2 ODBC data source named data_source_name that points to the DB2 catalog

entry catalog_entry

because the DB2 catalog entry catalog_entry

already exists.

Explanation: An attempt was made to create a DB2 ODBC data source with the same name as an existing DB2

catalog entry. Existing DB2 catalog entries cannot be used as names for DB2 ODBC data sources unless the ODBC

data source references a DB2 catalog entry with the same name.

Administrator Response: Verify that the ODBC data source name you chose does not already exist as a DB2 catalog

entry. If it does exist, choose an ODBC data source name that does not exist in the DB2 catalog.

CDWET0023E A general ODBC error occurred : error_text.

Explanation: The ODBC driver manager returned a general ODBC error.

Administrator Response: Consult the error message for more information.

CDWEX8011E An SQL error occurred that indicates the user is not authorized to perform the requested

operation.

The SQL statement is: sql_statement.


Explanation: This error will be generated when a user ID or password is not valid or when the user attempts to

access or update a table in another schema or table space to which the user does not have access. See the database

vendor message and documentation for further information.

Administrator Response: Verify that the user ID and password are valid and that you can perform the operation

manually on the database.

CDWEX8012E An SQL error occurred that indicates all the connections have been used, the connection failed,

the connection was lost, or the RDBMS is unavailable.



Explanation: This error indicates that the database is down or performance and tuning arguments are inadequate

for the workload. See the database vendor message and documentation for further information.

Administrator Response: Verify that you can connect to the database server from the client. Contact your database

administrator to resolve the problem.

CDWEX8013E An SQL statement generated a unique constraint violation.



Explanation: This error is generated when there is an attempt to insert or update data in a table that has the same

primary key as an existing row. See the database vendor message and documentation for further information.

Administrator Response: Run the statement that is failing manually on the database. Once you have fixed the data

or SQL logic problem, run the DB2 Data Warehouse Center step again.

CDWET0020E • CDWEX8013E


CDWEX8014E An SQL statement generated a referential integrity violation.



Explanation: There was an attempt to insert, update, or delete a row that violates a required relationship. You might

have tried to insert data into a child table when there is no associated parent or a you might be trying to delete a

parent when there is a dependent child. See the database vendor message and documentation for further

information.



CDWEX8015E An SQL statement generated an error that indicates an object already exists.



Explanation: This error usually occurs with the CREATE statement and indicates that an attempt to create an object

with the same name as an object that already exists has occurred. See the database vendor message and

documentation for further information.



CDWEX8016E An SQL statement generated an error that indicates the object was not found.



Explanation: An operation was attempted against an object that does not exist. See the database vendor message

and documentation for further information.



CDWEX8017E An SQL statement generated an error that indicates the INSERT statement’s column list and the

values to be inserted do not match.



Explanation: This error indicates that the number of values provided for insertion is different than the number of

columns in the table. See the database vendor message and documentation for further information.



CDWEX8084W A general SQL warning occurred.




Administrator Response: Check the SQL error and correct the statement as appropriate.

CDWEX8085E The number of arguments provided is not valid.

USAGE: execsql input_file output_file source_datasource source_username source_password

[target_datasource target_username target_password]

--or--

execsql source_datasource source_username source_password

Explanation: Too many or too few arguments were provided. See the usage statement for the correct syntax of the

command.

Administrator Response: Check the usage statement and issue the command again with the required arguments.

CDWEX8014E • CDWEX8085E


CDWEX8086W The SQL run-time program found more target columns (number_of_columns) than source columns

(number_of_columns). It will not populate the last number_of_columns columns in the target table. They

will default to NULL values.

Explanation: An SQL statement (INSERT INTO, SELECT FROM) is not valid. Fewer columns were selected than

were inserted. NULL values will be used for the extra target columns.

Administrator Response: Verify that NULL columns are appropriate for the columns in the target table. If not,

correct the SQL statement and run the program again.

CDWEX8087E A general SQL error occurred: database_messages.

Explanation: The message lists the messages and error codes returned from the database vendor through the ODBC

driver GetDiagRecs function. See the database vendor message and documentation for further information.

Administrator Response: Check the SQL error and correct the statement as appropriate.

CDWEX8088E The work file file_name, which was returned from the program that accesses user information

(DBInfoMgr), failed to open.

Explanation: There was an error while attempting to write to a temporary file that is used internally by the SQL

run-time program.

Administrator Response: Verify that permissions allow you to write to the file.

CDWEX8089E The file file_name failed to open with error error_number.

Explanation: There was an error while attempting to read a file.

Administrator Response: Verify that the file exists and that permissions allow you to read it.

CDWEX8090E The SQL statement exceeded the maximum length (length) allowed at line line_number.

Explanation: The SQL statement exceeded the hard coded memory limit for storing an SQL statement. It is unlikely

that a valid SQL statement would exceed the hard coded length listed in the error message. The lack of a terminator

causes the SQL run-time program to group multiple SQL statements together.

Administrator Response: Check the statement for errors and reduce its length to less than the size specified in

parentheses in the error message. Verify that all terminators are appropriately placed.

CDWEX8091E An "out of memory" error occurred while attempting to allocate amount_of_memory bytes.

Explanation: The program tried to allocate memory, but was unable to do so. The system might not have enough

RAM available

Administrator Response: Verify that the system has the required amount of physical RAM available. Once verified,

attempt to run the application again and observe the process size to determine if it grows dramatically prior to

receiving this error.

CDWEX8092E The number of columns (number_of_columns) read in the file (file_name) exceeded the number of

columns (number_of_columns) existing or specified for the target table. Line number line_number.

SQLState 21S01.

Explanation: The data file contains more comma separated values (CSV) per line than was indicated (or available)

in the target table’s columns. The SQL run-time program has no way to determine where the extra values go.

Administrator Response: Check the CSV file to determine that the number of values is correct. This error is caused

by too many commas on a single line. Errors could include a string which contains a comma that is not properly

wrapped by double quotes or the regional arguments replacing decimals (.) with commas (,). Resolve the file

corruption and run the program again.

CDWEX8086W • CDWEX8092E


CDWEX8093E A failure occurred while forming the INSERT statement used by the SQL run-time program to

transfer data across data sources. No columns were located in the target table.

Explanation: Zero columns should not be listed for the target table, other than because of an ODBC driver

corruption or an SQL run-time program corruption.

Administrator Response: Verify that only supported ODBC drivers are used because unsupported drivers would

cause unknown errors. If supported drivers are being used and this error still occurs, contact IBM Customer Support.

CDWEX8094E An internal corruption occurred: details.

Explanation: The details that are provided will assist IBM Customer Support to debug the problem.


CDWEX8095E The file ended while still within a quoted string. Check the SQL script to verify that all quotes

have been closed properly.

Explanation: This error typically occurs because a string was not quoted properly. The beginning or ending quote is

missing or an embedded quote exists in the string that has not been escaped with another quote placed adjacent to

the embedded quote.

Administrator Response: Check the SQL script for malformed quoted strings and correct them. Then attempt to run

the SQL script again.

CDWEX8096E The SQL run-time program found more source columns (number_of_columns) than target columns

(number_of_columns).

Explanation: The SELECT SQL statement is incorrect. There are more columns selected from a source table than are

inserted into the target table.

Administrator Response: Correct the SQL statement and run the program again.

CDWEX8097E The target table table_name was not found.

Explanation: The initial SQLFetch call for the specified table returned an ODBC error code of SQL_NO_DATA. This

indicates that the target table does not exist.

Administrator Response: Specify a valid target table in the SQL statement and run the program again.

CDWEX8098E The program that accesses user information (DBInfoMgr) failed to start.

Explanation: The system call starting the program returned an RC=1, which indicates it could not run the specified

program. This problem can occur when you run the SQL run-time program from the command line if the Tivoli Data

Warehouse environment has not been sourced correctly. This error might also occur if the program cannot open

temporary files in the TIVOLI_COMMON_DIR/cdw/logs/etl directory because the system call redirects stdour and

stderr to temporary working files.

Administrator Response: Use the twh_run.sh program to set up your environment correctly. Verify that the process

can create and write to files in the TIVOLI_COMMON_DIR/cdw/logs/etl directory.

CDWEX8099E An error occurred when calling the program that accesses user information (DBInfoMgr). The

program logged the following error information: error.

Return code: return_code.

Explanation: The system call starting the program returned a non zero value.

Administrator Response: Check the access user information (DBInfoMgr) program logs in the Tivoli common

logging directory and take action as indicated.



CDWEX8100E The comma separated values (CSV) file attempted to write an unsupported column type

(type_number: type_name).

Explanation: This version of the SQL run-time program does not support one of the column types in the SELECT

statement (BLOB, CLOB, or so forth).

Administrator Response: Correct the column type or exclude the column from the SELECT statement and run the

program again.

CDWEX8101E The column (column_number, column_name) of size column_size exceeded the maximum size

allowed. The maximum size allowed is size.

Explanation: An attempt was made to write a column to the comma separated values (CSV) file, but the column

size was larger than could be handled.

Administrator Response: Alter the table to reduce the size of the column to the listed maximum size in the error

message.

CDWEX8102W The data was truncated while reading from file file_name, column column_number, and line

number line_number. The length of column data read from the file was length, but the column

target_column_name size is size. SQLState 22001.

The following data was read: data.

This is the data after it was truncated: data.

Explanation: The data file has column data that is larger than what is defined in the database for the target table

and column.

Administrator Response: Verify that the data printed in the message is correct and populating the correct target

column.

CDWEX8103E A target data source was specified and a target directive was specified in the SQL script, but no

user or password was defined.

Explanation: A target user and password is required for running SQL scripts that have target directives, such as

EXECUTE_AT_TARGET.

Administrator Response: Check the usage statement and issue the command again with the required arguments or

verify that there is a target table specified for the step in the DB2 Data Warehouse Center GUI.

CDWEX8104E An INSERT_INTO_SOURCE or INSERT_INTO_TARGET directive was found, but no target data

source was given.

Explanation: No data source was specified as the target of the INSERT statement.

Administrator Response: Call the SQL run-time program with arguments that specify both a target and source data

source. If RunMultiSQL runs from the DB2 Data Warehouse Center, verify that the step has a source and target table

defined.

CDWEX8105E An error occurred while attempting to run the EDIT_USING directive program. The command

interpreter could not be found.

Explanation: The program could not run. This usually means there is a problem in the environment.

Administrator Response: Verify that the user program is in the path environment variable and that the program can

be run.

CDWEX8106E An error occurred while attempting to run the EDIT_USING directive program. The argument list

contains too many arguments.

Explanation: Too many arguments were listed in the argument list.

Administrator Response: Correct the arguments in the argument list and run the program again.



CDWEX8107E An error occurred while attempting to run the EDIT_USING directive program. The

command-interpreter file has a format that is not valid and cannot run.

Explanation: The user defined program failed to run. This might be an error from the command interpreter or the

program.

Administrator Response: Correct the file that is not valid and run the program again.

CDWEX8108E An error occurred while attempting to run the EDIT_USING directive program. There is not

enough memory available to run the command.

Explanation: There is not enough memory available to run the EDIT_USING directive program.

Administrator Response: Determine why no memory is available to start a new process.

CDWEX8109W An error was returned from the EDIT_USING directive program. Return Code: return_code. Error

number: error.

Explanation: The user defined program failed to run. This might be an error from the command interpreter or the

program.

Administrator Response: Verify that the command runs correctly from a command prompt.

CDWEX8110E While processing the arguments passed to the SQL run-time program, a source data source was

not defined correctly.

Explanation: Two source data sources were defined with the -s argument or the -s argument was specified with

another argument where it is not allowed.

Administrator Response: Verify that only one -s argument is used at the command line. Verify that the -b or -i

arguments are not specified in conjunction with the -s argument.

CDWEX8111E An unrecognized database vendor type (type) follows the IFTARGET directive or IFSOURCE

directive at line number line_number.

Explanation: The directive entries must be separated by a space and can only have an optional ’not’ (!) symbol in

front, indicating that the surrounded text NOT be run if that vendor is present. Characters that are not valid might

be present (such as commas for separating), but should be avoided.

Administrator Response: Verify that exact vendor names are used with space separators and ’not’ symbols (!)

following the directive. Recognized vendors are DB2, DB2os390, Oracle, Sybase, MSSQL, Informix, Text, and TSM.

CDWEX8112E The INSERT INTO column list does not contain a matching column for entry number number

(column_name). Column list: column_list.

Explanation: This error occurs on a cross-data source INSERT INTO statement. The attached SQL statement

returned more columns than the target table has (or more columns than you indicated in your target table column

list).

Administrator Response: Issue the SELECT statement by itself to see what columns it returns and verify that the

target table columns match exactly (or that your target column list matches).

CDWEX8113E The translate file contains an empty argument list. The macro macro at line number line_number is

not valid.

Explanation: The specified translate file has an error in it. A macro is defined as having an argument list, indicated

by having parentheses (), but no arguments are contained within the parentheses.

Administrator Response: Correct the problem in the translate file by removing the parentheses from the macro or

by placing the correct argument(s) inside of the parentheses.



CDWEX8114E The translate file contains too many close parentheses in the column list for macro macro at line

number line_number.

Explanation: There is at least one extra close paraentheses, ), at the specified line number.

Administrator Response: Correct the malformed macro in the translate file and run the program again.

CDWEX8115E The INSERT INTO column list contains a blank column name (column number column_number).

Explanation: Two commas are next to each other or have a white space between them in the INSERT INTO column

list.

Administrator Response: Remove the extra column or put the correct column name between the two columns and

run the program again.

CDWEX8116E While processing the arguments passed to the SQL run-time program, a source user was not

defined correctly.

Explanation: Two source users were defined with the -u argument, the -u argument was specified with another

argument where it is not allowed, or a source user was not specified.

Administrator Response: Verify that only one -u argument is used at the command line. Verify that the -b or -i

arguments are not specified in conjunction with the -u argument. Verify that the -u argument is specified or that a

user is associated with the source data source in the DB2 Data Warehouse Center.

CDWEX8117E While processing the arguments passed to the SQL run-time program, a source password was not

defined correctly.

Explanation: Two source passwords were defined with the -p argument, the -p argument was specified with another

argument where it is not allowed, or a source password was not specified.

Administrator Response: Verify that only one -p argument is used at the command line. Verify that the -b or -i

arguments are not specified in conjunction with the -p argument. Verify that the -p argument is specified or that a

password is associated with the source data source in the DB2 Data Warehouse Center.

CDWEX8118E While processing the arguments passed to the SQL run-time program, a target data source was


Explanation: Two target data sources were defined with the -t argument or the -t argument was specified with

another argument where it is not allowed.

Administrator Response: Verify that only one -t argument is used at the command line. Verify that the -b or -j

arguments are not specified in conjunction with the -t argument.

CDWEX8119E While processing the arguments passed to the SQL run-time program, a target user was not

defined correctly.

Explanation: Two target users were defined with the -v argument, the -v argument was specified with another

argument where it is not allowed, or a target user was not specified.

Administrator Response: Verify that only one -v argument is used at the command line. Verify that the -b or -j

arguments are not specified in conjunction with the -v argument. Verify that the -v argument is specified or that a

user is associated with the target data source in the DB2 Data Warehouse Center.

CDWEX8120E While processing the arguments passed to the SQL run-time program, a target password was not

defined correctly.

Explanation: Two target passwords were defined with the -w argument, the -w argument was specified with

another argument where it is not allowed, or a target password was not specified.

Administrator Response: Verify that only one -w argument is used at the command line. Verify that the -b or -j

arguments are not specified in conjunction with the -w argument. Verify that the -w argument is specified or that a

password is associated with the target data source in the DB2 Data Warehouse Center.



CDWEX8121E While processing the arguments passed to the SQL run-time program, a source IRName was not

defined correctly.

Explanation: Two source IRNames were defined with the -i argument or the -i argument was specified with another

argument where it is not allowed.

Administrator Response: Verify that only one -i argument is used at the command line. Verify that the -b or -s

arguments are not specified in conjunction with the -i argument.

CDWEX8122E While processing the arguments passed to the SQL run-time program, a target IRName was not

defined correctly.

Explanation: Two target IRNames were defined with the -j argument or the -j argument was specified with another


Administrator Response: Verify that only one -j argument is used at the command line. Verify that the -b or -t

arguments are not specified in conjunction with the -j argument.

CDWEX8123E While processing the arguments passed to the SQL run-time program, a step name was not

defined correctly.

Explanation: Two step names were defined with the -b argument or the -b argument was specified with another


Administrator Response: Verify that only one -b argument is used at the command line. Verify that the -i, -j -s, or -t

arguments are not specified in conjunction with the -b argument.

CDWEX8124E While processing the arguments passed to the SQL run-time program, an input file was not

defined correctly.

Explanation: Two input files were specified with the -n argument, but only one is allowed.

Administrator Response: Remove the -n argument that is not correct.

CDWEX8125E The vendor type vendor_type is not valid.

Explanation: The database vendor type is not valid.

Administrator Response: Correct the vendor type and run the program again. Recognized vendors are DB2,

DB2os390, Oracle, Sybase, MSSQL, Informix, Text, and TSM.

CDWEX8126E While processing the arguments passed to the SQL run-time program, an output file was not

defined correctly.

Explanation: Two output files were specified with the -o argument, but only one is allowed.

Administrator Response: Remove the -o argument that is not correct.

CDWEX8127E While processing the arguments passed to the SQL run-time program, a source SQL statement

was not defined correctly.

Explanation: Two source SQL statements were specified with the -q argument, but only one is allowed.

Administrator Response: Remove the -q argument that is not correct.

CDWEX8128E While processing the arguments passed to the SQL run-time program, a target SQL statement was


Explanation: Two target SQL statements were specified with the -r argument, but only one is allowed.

Administrator Response: Remove the -r argument that is not correct.



CDWEX8129E While processing the arguments passed to the SQL run-time program, an argument (-argument)

was found without a value.

Explanation: All arguments require an associated value. An argument was found that was followed by another

argument rather than a value.

Administrator Response: Fix the argument list so that a value is associated with every argument.

CDWEX8130E The translate file contains too few close parentheses in the column list for macro macro at line

number line_number.

Explanation: There are not enough close parentheses, ), at the specified line number. There must be one close

parentheses for every open parentheses.

Administrator Response: Correct the malformed macro in the translate file and run the file again.

CDWEX8131E While processing the arguments passed to the SQL run-time program, an argument was found

that is not valid: argument.

Explanation: An argument was specified that the SQL run-time program cannot process.

Administrator Response: Review the usage statement and specify the arguments correctly.

CDWEX8132E A target directive was specified in the SQL script, but no target data source was defined.

Explanation: A target data source is required to run SQL scripts that have the EXECUTE_AT_TARGET directive.

Administrator Response: Check the usage statement and issue the command again with the required arguments or

verify that there is a target table specified for the step in the DB2 Data Warehouse Center GUI.

CDWEX8133E The input file contains an INSERT INTO statement with an empty column list. The statement

that is not valid is at line number line_number.

Explanation: The input file has an INSERT INTO statement defined with a column list, indicated by parentheses (),

but no columns were contained within the parentheses.

Administrator Response: Correct the problem in the input file by removing the parentheses from the statement or

by placing the correct arguments inside of the parentheses.

CDWEX8134E The input file contains too many close parentheses in the column list at line number line_number.

Explanation: A statement that is not valid exists in the input file at the line number listed. The statement has more

close parentheses ’)’ than it has open parentheses ’(’.

Administrator Response: Correct the malformed statement in the input file and run it again.

CDWEX8135E The translation statement exceeded the maximum length (length) allowed.

Explanation: A valid translation statement would not exceed the hard coded length listed in the error message. The

lack of a terminator causes the SQL run-time program to group multiple translation statements together.

Administrator Response: Check the statement for errors and reduce its length to below the size specified in


CDWEX8136E The translation statement exceeded the maximum length because a closing quote was not found

on line number line_number.

Explanation: A valid translation statement would not exceed the hard coded length listed in the error message. The

lack of a terminator causes the SQL run-time program to group multiple translation statements together.

Administrator Response: Check the statement for errors and reduce its length to below the size specified in




CDWEX8137E The input file has an ENDIF directive with no matching IF directive at line number line_number.

Explanation: There must be an IF directive at the specified line number.

Administrator Response: Correct the input file and run the program again.

CDWEX8138E The input file has a DONE directive with no matching FOR directive at line number line_number.

Explanation: There must be a FOR directive at the specified line number.

Administrator Response: Correct the input file and run the program again.

CDWEX8139W The program is skipping an unrecognized directive directive at line number line_number.

Explanation: A directive was found that could not be processed because it is of an unrecognized type. This directive

was ignored and processing continued.

Administrator Response: Check for a spelling error. Correct the directive and run the program again.

CDWEX8140E The translate file contains two identically named macros: macro, line number line_number and

macro, line number line_number.

Explanation: The macros must have unique names. Either rename or remove one of the macros.

Administrator Response: Rename or remove one of the macros and run the file again.

CDWEX8141W An SQL statement was found at the end of the file without a termination character and cannot

run.

Explanation: This error occurs because a statement does not have a termination character. In most cases the

termination character is a semicolon(;).

Administrator Response: Check the SQL script for a missing semicolon (;) or an OVERRIDE_TERMINATOR

directive. If there is a directive to override the terminator, that character must be used to end the statement.

CDWEX8142E There are no valid SQL statements in the input file.

Explanation: The input file must contain at least one valid SQL statement.

Administrator Response: Verify that there are SQL statements in the file. If there are, a quote is probably missing.

CDWEX8143E The input file is using a macro, but fewer arguments are specified for the macro than are defined

for the macro. The following SQL statement is in error: sql_statement.

Explanation: The macro specified is missing required arguments.

Administrator Response: Check the macro in the translate file to determine which arguments are required. Correct

the SQL statement and run the program again.

CDWEX8144E The following SQL statement is missing a closing parenthesis for the macro: sql_statement.

Explanation: There must be one close parenthesis for every open parenthesis.

Administrator Response: Correct the SQL statement and run the program again.

CDWEX8145E The target SQL statement was found at line number line_number, but no target data source was

specified.

Explanation: The input file specified a cross data source transfer with the INSERT_INTO directive, but no target

data source was passed as an argument.

Administrator Response: Run the program again and specify the -t argument or define a target table from the DB2

Data Warehouse Center for the step you are running.



CDWEX8146E The OVERRIDE_TERMINATOR directive was found at line number line_number, but there is no

argument.

Explanation: This directive requires an argument, which is the alternate termination character.

Administrator Response: Correct the directive and run the program again.

CDWEX8147E The SQL run-time program ran out of internally defined buffer space while processing the value

list of a FOR directive at line number line_number.

Explanation: This is probably an internal error because 8KB of space is provided to process the list of values.

Administrator Response: Set tracing to DEBUG_MAX. Then run FFDC and contact IBM Customer Support to help

you diagnose the problem.

CDWEX8148E The SQL script exceeded the maximum number of values allowed maximum_number in the value

list of a FOR directive at line number line_number.

Explanation: This error probably results from a syntax error because the maximum number of values allowed

should be adequate for application programs.

Administrator Response: Verify that the syntax of the statement is correct. If the application exceeds the maximum

values allowed, split the application into multiple FOR loops.

CDWEX8149E No values were found in the value list while parsing a FOR directive at line number line_number.

Explanation: A list of values is required for the FOR Directive.

Administrator Response: Check the usage statement of the FOR directive and correct the syntax in the SQL script.

CDWEX8150E The TO keyword was not found while parsing a FOR FROM directive at line number

line_number.

Explanation: The TO keyword is required and must be entered as TO or to. Mixed case is not valid.

Administrator Response: Check the usage statement of the FOR FROM directive and correct the syntax in the SQL

script. Verify that the keyword is not mixed case.

CDWEX8151W The translate file file_name contains no macro definitions.

Explanation: The translate file usually contains at least one translation although it is not required.

Administrator Response: If this translate file was provided by Tivoli Data Warehouse, such as db2.translate, there

should be translations. The file is probably corrupted. Translate files provided by other Tivoli applications might

contain no entries. If the generated SQL script contains SQL statements that are not valid and that have double

underscore (__) characters, there is probably a problem with the translate file. If the file generates correctly, no

additional translations are needed and this warning can be ignored.

CDWEX8152E The FROM value in a FOR FROM loop exceeded the maximum number of digits allowed at line

number line_number. The size of the value is size and only 8 digits are allowed.

Explanation: The FROM value should not exceed 8 digits.

Administrator Response: Check for syntax errors in the FOR FROM directive.

CDWEX8153E The TO value in a FOR FROM loop exceeded the maximum number of digits allowed at line

number line_number. The value is value and only 8 digits are allowed.

Explanation: The TO value should not exceed 8 digits.




CDWEX8154E The BY value in a FOR FROM loop exceeded the maximum number of digits allowed at line

number line_number. The value is value and only 4 digits are allowed.

Explanation: The BY value should not exceed 4 digits.


CDWEX8155E The FROM value (value) at line number line_number in a FOR FROM loop was not correctly

converted to a numeric value.

Explanation: The FROM value supplied is an illegal integer.


script.

CDWEX8156E The TO value (value) at line number line_number in a FOR FROM loop was not correctly converted

to a numeric value.

Explanation: The TO value supplied is an illegal integer.


script.

CDWEX8157E The BY value (value) at line number line_number in a FOR FROM loop was not correctly converted

to a numeric value.

Explanation: The FROM value supplied is an illegal integer.


script.

CDWEX8159E The FROM (value), TO (value), and BY (value) values in the FOR FROM directive at line

numberline_number are not valid. These values will result in an infinite loop.

Explanation: The values supplied will result in an infinite loop. For example, if the FROM value is greater than the

TO value and the BY value is positive, an infinite loop will result.

Administrator Response: Supply correct FROM, TO, and BY values.

CDWEX8160E The SQL run-time program ran out of internally defined buffer space while processing the

variable list of a FOR directive at line number line_number.

Explanation: This is probably an internal error because 8KB of space is provided to process the list of variables.



CDWEX8161E No variables were found in the variable list while parsing a FOR directive at line number

line_number.

Explanation: A list of variables is required for the FOR directive.

Administrator Response: Check the usage statement of the FOR directive and correct the syntax in the SQL script.

CDWEX8162E The SELECT_FROM keyword was not found while parsing a FOR SELECT directive at line

number line_number.

Explanation: The SELECT_FROM_SOURCE or SELECT_FROM_TARGET keyword is required.

Administrator Response: Check the usage statement of the FOR SELECT directive and correct the invalid syntax in

the SQL script. Verify that the case of the keyword is correct. It must be upper or lower case.



CDWEX8163E An SQL SELECT statement was not found after a SELECT_FROM keyword in a FOR SELECT

directive at line number line_number.

Explanation: An SQL SELECT statement or the keyword LIMIT must follow a SELECT_FROM_SOURCE or

SELECT_FROM_TARGET keyword..

Administrator Response: Check the usage statement of the FOR SELECT directive and correct the syntax in the SQL

script. Verify that the case of the select statement is correct. It must be upper or lower case, mixed case is not

supported.

CDWEX8164E The LIMIT value exceeded the maximum number of digits allowed in a FOR SELECT directive at

line number line_number. The value is value and the maximum number allowed is maximum_number.

Explanation: The optional LIMIT value, which limits the number of rows processed in a result set, must be a

number less than the maximum number allowed.


script. Specify a LIMIT value that is less than the maximum iteration value allowed. If you require a larger number

of values, split the application into multiple FOR loops.

CDWEX8165E The LIMIT value (limit_value) at line number line_number in a FOR SELECT loop was not correctly

converted to a numeric value.

Explanation: The LIMIT value supplied is an illegal integer.


script.

CDWEX8167E No columns were retrieved with the SQL SELECT statement in a FOR SELECT directive at line

number line_number.

Explanation: The SQL SELECT statement is probably not valid. There should always be columns associated with an

SQL SELECT statement.

Administrator Response: Check the FOR directive and verify that a valid SQL SELECT statement has been

provided. Stored procedures and other SQL statements are not supported.

CDWEX8168E The number of columns retrieved (number_of_columns) with the SQL SELECT statement at line

number line_number does not match the number of variables (number_of_variables) defined in a FOR

SELECT directive.

Explanation: The number of variables and number of columns must match in a FOR SELECT directive. The data

associated with the column list is used to build the value list for the specified variables.

Administrator Response: Adjust the list of variables or the column list in the SELECT statement. If you are selecting

all columns (with a SELECT FROM), specify a column list to verify that extraneous columns are not being used.

CDWEX8169E The program exceeded the maximum number of values allowed (maximum_number) while fetching

data in a FOR SELECT directive at line number line_number.

Explanation: The result set for the SQL query must be less than or equal to the maximum number allowed.

Administrator Response: If your result set is over the maximum number of rows, specify the LIMIT keyword and

limit the amount of data that is used for processing in a FOR SELECT loop. An SQL SELECT statement probably

does not have an appropriate WHERE clause to filter the data.

CDWEX8170E No values were found in the value list while processing a FOR SELECT directive at line number

line_number. The result set for the query was empty.

Explanation: The SQL query statement retuned no data so there are no values to use for variable substitution.

Administrator Response: An SQL select statement probably has a WHERE clause that is not valid or the data that is

being queried is not valid. Correct the query or the data and run the DB2 Data Warehouse Center step again.



CDWEX8171E An unexpected null pointer was returned from function allocForNode.

Explanation: This is an internal error and should not occur.



CDWEX8172E More than one variable was found, but a SELECT_FROM_SOURCE or SELECT_FROM_TARGET

keyword was not found while parsing a FOR directive at line number line_number.

Explanation: Only the FOR SELECT directive allows multiple variables for substitution.

Administrator Response: Check the FOR directive usage statement and correct the FOR directive syntax.

CDWEX8173E The IN, FROM, or SELECT_FROM keyword not found while parsing a FOR directive at line

number line_number.

Explanation: The FOR directive is not valid.

Administrator Response: Check the syntax of the FOR directive and correct the FOR statement syntax.

CDWEX8174E The SQL run-time program ran out of internally defined buffer space while processing the

generated SQL statement in a FOR loop at line number line_number.

Explanation: There might be a missing quote or semicolon in an SQL statement. The line number refers to the line

of the closing DONE statement. New SQL statements are substituting the variables for values in the FOR loop.

Administrator Response: Check the syntax of the SQL statements that are within the FOR loop and correct any that

are missing quotes or semicolons.

CDWEX8175E A bad pointer was passed to process the comment for the FOR directive.

Explanation: This is an internal error and should not occur.



CDWEX8176E The FOR loop did not find a matching DONE statement.

Explanation: Every FOR directive must have a matching DONE directive.

Administrator Response: Check the SQL script and verify that there is the same number of DONE and FOR

directives.

CDWEX8178E The TWH_TOPDIR environment variable was not found during logging initialization.

Explanation: TWH_TOPDIR is a required environment variable for valid Tivoli Data Warehouse installations. It is

used to locate the common logging location and properties files required for logging operations.

Administrator Response: Verify that you are logged on with a user ID that has been set up to run with Tivoli Data

Warehouse.

CDWEX8179E The program failed to open the Tivoli Data Warehouse logging location file file_name. The error

from the open call is: error.

Explanation: The logging location file is in a well defined location and should be accessible, so that applications can

determine the location of the Tivoli common logging directory.

Administrator Response: Verify that the TWH_TOPDIR environment variable points to the correct directory. Check

the permissions on the file that failed to open. If the specified directory or file does not exist, the installation is

corrupted or you are using a version of Tivoli Data Warehouse that is older than Version 1.2.



CDWEX8180E The program could not find the Tivoli common logging directory entry tivoli_common_dir in the

TWH_TOPDIR/logginglocation/log.properties file.

Explanation: The tivoli_common_dir entry should always be in the log.properties file.

Administrator Response: Edit the file and verify that the property exists. The file might have been edited manually

and an editing error was made. If you do not see a problem or cannot find the entry, restore this file from a backup

location.

CDWEX8181E The program could not open the SQL run-time program’s properties file, file_name, for reading.

Explanation: The properties file defines logging characteristics and is required for logging operations.

Administrator Response: Verify that the file permissions allow access to the file. If the path is not correct, the

tivoli_common_dir entry in the TWH_TOPDIR/logginglocation/log.properties file is not valid. The file might have

been edited manually, the Tivoli common logging directory might have been moved and this entry was not updated,

or the TWH_TOPDIR environment variable is not correct.

CDWEX8182E The program failed to process the SQL run-time logging properties file.

Explanation: The execsql2Logging.properties file defines logging characteristics and is required for logging

operations.

Administrator Response: Verify that the file permissions allow access to the log file. If the path is not correct, the

tivoli_common_dir entry in the TWH_TOPDIR/logginglocation/execsql2Logging.properties file is not valid. The file

might have been edited manually, the Tivoli common logging directory might have been moved and this entry was

not updated, or the TWH_TOPDIR environment variable is not correct.

CDWEX8183E Setting the path to the codeset files failed with error error.

Explanation: Codesets are required to process translated messages correctly. The location used is

TWH_TOPDIR/codeset.

Administrator Response: Verify that the TWH_TOPDIR environment variable is correct and that the codeset

directory exists. Verify that the process has read access to this directory. If the files do not exist, the install might be

corrupted or your version of Tivoli Data Warehouse is older than Version 1.2.

CDWEX8184E The logging environment failed to initialize with error error.

Explanation: The program could not process the execsql2Logging.properties file.

Administrator Response: The properties file has probably been edited manually and edits have been made that are

not valid. Restore a backup of the file.

CDWEX8185W The program failed to initialize the message logger that is defined in the

execsql2Logging.properties file. It is using the default log file file_name.

Explanation: The program cannot log messages to the program’s message log file.

Administrator Response: The message logger that is defined by the Tivoli Data Warehouse installation is named

execsql2.msg. Verify that the execsql2Logging.properties file has been edited correctly.

CDWEX8186W The program failed to initialize the trace logger that is defined in the execsql2Logging.properties

file. It is using the default log file file_name.

Explanation: The program cannot log trace information to the program’s trace log file.

Administrator Response: The trace logger that is defined by the Tivoli Data Warehouse installation is named

execsql2.trc. Verify that the execsql2Logging.properties file has been edited correctly.

CDWEX8180E • CDWEX8186W


CDWEX8187E The message catalog cdw_ex_msgs.cat failed to open.

Explanation: There is a catalog file supplied for each supported language with the Tivoli Data Warehouse

installation. However, the catalog file requested in addition to the default language failed to open. The program will

use the host locale specified by the LANG environment variable to derive the lang directory. For example, if

LANG=fr_CA, the program will try to locate the fr_CA directory, then fr, and finally C, the default language. The

default language should always be available in a valid Tivoli Data Warehouse installation.

Administrator Response: Verify that the TWH_TOPDIR/msgcat/ lang/cdw_ex_msgs.cat file exists and that the

process has read access to the file.

CDWEX8188W A trace level severity code that is not valid at line line_number was passed to the function that

writes trace messages.

Explanation: The trace message will be treated as if the severity was DEBUG_MIN.

Administrator Response: This is a programming error that should be reported to IBM Customer Support. The only

impact is that a trace message might be written at an incorrect severity level.

CDWEX8189W The program could not retrieve the translated message for message message_number. The message

was generated in file file_name at line number line_number.

Explanation: The program will use the default English message if it is available. A programming error probably

occurred because a message key that is not valid was specified.


CDWEX8190W The program failed to open the log file file_name with error error.

Explanation: The program cannot write to the file defined by the environment variable VWP_LOG. The VWP_LOG

environment variable is set by the DB2 Data Warehouse Center GUI and should write to the directory specified by

the environment variable VWS_LOGGING. VWS_LOGGING is usually the DB2 sqllib/logging directory. Messages

will not be displayed within the DB2 Data Warehouse Center GUI, so log files will have to be checked to determine

what messages were generated.

Administrator Response: Verify that the process has write access to the directory and file.

CDWEX8191E The EDIT USING directive found at line number line_number has no arguments.

Explanation: Arguments are required with the EDIT USING directive.

Administrator Response: Review the syntax for the directive in Enabling an Application for Tivoli Data Warehouse and

correct the error.

CDWEX8192E A syntax error was encountered parsing an INSERT INTO statement at line number line_number.

Explanation: The syntax of the SQL command is not correct. Check the parentheses and required arguments for the

statement.

Administrator Response: Correct the syntax of the specified INSERT INTO statement and run the program again.

Review your SQL Reference manual for correct syntax.

CDWEX8194E Setting the path to the message catalog file failed with error error.

Explanation: Message catalogs are required to process translated messages correctly. The location used is

TWH_TOPDIR/msgcat/ language/cdw_ex_msgs.cat, where language is the language of the host or C if the language

is English or the language was not found.

Administrator Response: Verify that the TWH_TOPDIR environment variable is correct and that the msgcat

directory exists. Verify that the process has read access to this directory. If the files do not exist, the installation is

corrupted or your version of Tivoli Data Warehouse is older than Version 1.2.



CDWEX8196E An unknown SQL data type type was returned from the database vendor.

Explanation: The SQL run-time program uses the ODBC function SQLDescribeCol to derive information about the

column. This call returned an unknown data type.

Administrator Response: Verify that you are using a supported version of DB2 and the ODBC drivers that were

shipped with IBM. This error could occur if you use ODBC drivers from other sources.

CDWEX8197W There was an error locating the table_qualifier and table_owner and table_name in sp_tables assuming

the database username equals the server login name.

Explanation: The SQL run-time program could not find the table.

Administrator Response: Verify that you are using a supported version of DB2 and the ODBC drivers that were

shipped with IBM. This error could occur if you use ODBC drivers from other sources.

CDWEX8198W The target column column_number has a size (column_size) or buffer size (buffer_size) that is greater

than the maximum size allowed (maximum_size). The SQL run-time program is adjusting the size of

the column to the maximum size maximum_size.

Explanation: The program determined that the specified target column is larger than the maximum size allowed.

Therefore, the column size is adjusted to the default size.

Administrator Response: This error is usually due to large binary data types. Some database vendors report the

maximum size for the data type rather than the actual size of the column. For example, a 3 byte field would be

reported as a size of 3 GB. This is an informational message, but you should verify that your data does not exceed

the maximum allowed.

CDWEX8199W The source column column_number has a size (column_size) that is greater than the maximum size

allowed (maximum_size). The SQL run-time program is adjusting the size of the column to the

maximum size maximum_size.

Explanation: The program determined that the specified source column is larger than the maximum size allowed

and the column size is defaulted.

Administrator Response: This error is usually due to large binary data types. Some database vendors report the

maximum size for the data type rather than the actual size of the column. For example, a 3 byte field would be

reported as a size of 3 GB. This is an informational message, but you should verify that your data does not exceed

the maximum allowed.

CDWEX8200E The number of columns (number_of_columns) in the result set is greater than the number of

columns (number_of_columns) specified or available in the target table. The SQL statement is:

sql_statement.

Explanation: The result set from an SQL query exceeds the number of columns that was either specified or available

in the target table.

Administrator Response: Check the QUERY statement to verify that the number of values retrieved is less than or

equal to the number of columns specified or available in the target table.

CDWEX8201W The data source name data_source_name is not a SYSTEM data source name. It is a user data

source name.

Explanation: ODBC data source names can be defined for the system or for the user. A user data source takes

precedence.

Administrator Response: Verify that this is the intended behavior. If you intend to use the system data source

name, delete or rename the user data source.

CDWEX8196E • CDWEX8201W


CDWEX8202E The program exceeded the maximum number of variables allowed (maximum_number) while

passing a FOR SELECT directive at line number line_number.

Explanation: The list of variables in the FOR SELECT directive must be less than or equal to the maximum number

of variables allowed.


script. If you require more variables, split the application into multiple FOR loops.

CDWEX8203E An error occurred while attempting to open the HKEY_CURRENT_USER key :

’SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources’ in the Tivoli Data Warehouse Registry and

the error message could not be retrieved for return code return_code.

Explanation: A failure occurred accessing the Registry to retrieve ODBC data sources. When getting the message

with API FormatMessage a failure occurred so no message could be printed.

Administrator Response: Look up the message associated with the return code and take action as indicated. Also

check the ODBC data source entries that are being used by the SQL script. If you do not see an error, try deleting

and creating the data source again.

CDWEX8204E An error occurred while attempting to open the HKEY_CURRENT_USER key :

’SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources’ in the registry. The system returned

(return_code) return_message.

Explanation: A failure occurred accessing the Tivoli Data Warehouse Registry to retrieve ODBC data sources. The

system messages retrieved with API FormatMessage give details about the cause of the error.

Administrator Response: Take corrective action based on the system messages. Also check the ODBC data source

entries that are being used by the SQL script. If you do not see an error, try deleting and creating the data sources

again.

CDWEX8177E The EDIT_USING, INSERT_INTO_SOURCE, or INSERT_INTO_TARGET directive was specified

at line number line_number, but there was no SQL INSERT INTO, SELECT FROM statement.

Explanation: An SQL INSERT INTO, SELECT FROM statement must follow the cross data source directives.

Administrator Response: Check the SQL script and verify that there is an INSERT INTO, SELECT FROM source

SQL statement following all cross data source directives.

CDWFF0001W One or more command line parameters for the first failure data capture (FFDC) program are

missing.

Explanation: Refer to the following usage statement when running a command for the program: java FFDC [Tivoli

common logging directory] [zip output file] [directory to zip]

Administrator Response: Correct the command line parameters. Run the program again.

CDWFF0003W An exception was received when closing the compressed archive. There might not be files in the

directory to compress.

Explanation: While creating the compressed file containing log and environment information, the program received

an exception. This exception can be caused by no files being in the requested directories to archive.

Administrator Response: Verify that the parameters supplied to the first failure data capture program are correct.

Verify that there are files in the directories to place in an archive file. Run the program again.

CDWFF0004E An exception was received when updating the log.properties file under the

$TWH_TOPDIR/logginglocation directory.

Explanation: The configuration that specifies the location of the Tivoli common logging directory for the Tivoli Data

Warehouse software could not be updated. The program that updates the log.properties file updates other files at the

same time. Updating only the log.properties file might lead to incorrect logging locations or logging failures for

Tivoli Data Warehouse programs.

CDWEX8202E • CDWFF0004E


Administrator Response: Verify that the log.properties file is in the $TWH_TOPDIR/logginglocation directory.

Verify that the contents of the log.properties file includes an entry for the tivioli_common_dir. Verify that the

directory paths passed to the mvlogdir program as parameters are correct. Run the program again. Update the file

manually only if the problem persists.

CDWFF0006E An exception was received when updating the fileDir parameter in the logging properties files.

Explanation: When the directory path for the Tivoli common logging directory is changed, the fileDir parameter

that controls the logging location of software must be updated.

Administrator Response: If an error occurs, edit each properties file manually and alter the fileDir parameter in

each logging file to match the new value for the Tivoli common logging directory.

CDWFF0007E An exception was received when updating script files for the Tivoli Data Warehouse first failure

data capture, move common logging directory, and log viewer tools in the Tivoli common logging

directory.

Explanation: When the directory path for the Tivoli common logging directory is changed, the paths in the scripts

must be updated to reflect the new path. The scripts used to run the utilities might contain path information that is

not valid.

Administrator Response: If an error occurs, edit each script file manually and alter the path information to reflect

the new value for the Tivoli common logging directory.

CDWIC0001W Warnings were detected, but the installation was able to continue.

Explanation: A command returned a warning message. However, the warning that was logged did not negatively

impact the success of the installation.

Administrator Response: Review the installation logs in the Tivoli common logging directory to ensure that

messages indicate conditions that are acceptable.

CDWIC0002W General errors were detected, but the installation was able to continue.

Explanation: A command returned an error message. However, the error that was logged did not negatively impact

the success of the installation.



CDWIC0003E The installation program cannot locate or read the configuration file file_name.

Explanation: The installation program does not have permission to access the file or a file name was specified that

is not correct.

Administrator Response: Verify that the directory and file permissions are correct and that you have specified the

correct file. Try installing again.

CDWIC0004E A required command line option option is missing.

Explanation: The required command line argument for the core installation program was not specified or is not

correct.

Administrator Response: If you are running the command from the command line, review the syntax for the

command by running it with the -h option. Otherwise, run FFDC and contact IBM Customer Support.

CDWIC0005E The configuration file file_name is not valid. An argument argument was not found in the file.

Explanation: The installation program attempted to validate the configuration file and did not find the specified

argument that is required.

Administrator Response: Run FFDC and contact IBM Customer Support.

CDWFF0006E • CDWIC0005E


CDWIC0006E The environment variable variable was not set before calling the method method.

Explanation: An environment variable that is necessary for the proper operation of the installation program is not

defined to the current environment. This is an internal error.


CDWIC0007E An argument argument that is not valid was found in the configuration file file_name.

Explanation: The installation program attempted to validate the configuration file and found the specified argument

is not valid. A common problem is the machines are not configured to use fully qualified host names.

Administrator Response: Make sure your host systems are configured to use fully qualified host names and make

sure DNS is configured between distributed systems. Then retry the installation.

If necessary, run FFDC and contact IBM Customer Support.

CDWIC0008E The operating system used on this system is not supported.

Explanation: The operating systems supported are Windows 2000, Windows NT, AIX®, and Solaris. Also, refer to

Tivoli Data Warehouse Release Notes for the most recent list of supported operating systems.

Administrator Response: Install Tivoli Data Warehouse on another machine or install a supported version of the

operating system on this machine.

CDWIC0009E The installation program cannot calculate disk space requirements.

Explanation: The installation program is attempting to calculate the total amount of disk space available for use

during the installation. This check is performed to verify that disk space requirements are met prior to beginning the

installation.


CDWIC0010E The installation program cannot access the temporary directory specified in the configuration file

file_name.

Explanation: The TMPDIR and TEMPDIR environment variables might not be set correctly.

Administrator Response: If installing from the installation wizard, verify that the TMPDIR and TEMPDIR

environment variables are set correctly.

CDWIC0011E The installation program cannot add the directory directory_name to the PATH environment

variable.

Explanation: During the installation, the PATH environment variable is extended to include directories needed by

the installation.


CDWIC0012E You do not have the correct authority to install Tivoli Data Warehouse.

Explanation: The installation program detected that you do not have the authority needed to run the installation.

Administrator Response: Log in as root (on UNIX) or as an administrator (on Windows operating systems) and

start the installation again.

CDWIC0013E This version of Tivoli Data Warehouse is already installed.

Explanation: Reinstalling the application can result in the loss of historical data.

Administrator Response: If you want to reinstall the current version of Tivoli Data Warehouse, you must first

uninstall the installed version of Tivoli Data Warehouse and then reinstall it. Uninstalling the current version of Tivoli

Data Warehouse will cause a loss of all historical data and will drop all core databases associated with the current

version of the Tivoli Data Warehouse.

CDWIC0006E • CDWIC0013E


|

||

||

|

CDWIC0014E The installation program cannot create the directory directory_name in the Tivoli Data Warehouse

target directory directory_name.

Explanation: The directory permissions to the target directory might not be set correctly.

Administrator Response: Verify that the permissions on the target directory are set correctly.

CDWIC0015E The installation program cannot connect to the database database_name for Tivoli Data Warehouse.

Explanation: A connection attempt was made to the database, but the attempt failed.

Administrator Response: Verify that the user name and password used are correct. Also, verify that you can

connect to the specified database from a DB2 command line. See Installing and Configuring Tivoli Data Warehouse for

instructions.

CDWIC0016E The installation program cannot create the database database_name for Tivoli Data Warehouse.

Explanation: The installation could not create a new database.

Administrator Response: Review the message and trace logs for previously listed error messages that might prevent

the installation from creating a new database.

CDWIC0017E An SQL error occurred during the connection test. The SQL error code is error for database

database_name.

Explanation: A fatal error occurred while attempting to connect to the database.

Administrator Response: Verify that LDAP is disabled. If it is not disabled, turn off LDAP support with the

following commands in a DB2 CLP command window:

DB2SET -ALL

DB2SET DB2_ENABLE_LDAP=NO

RESTART DB2 VIA DB2STOP

DB2START

If necessary, refer to the database vendor documentation for specific information about the SQL error code.

CDWIC0018E The installation program cannot catalog database database_name for Tivoli Data Warehouse.

Explanation: The installation cannot catalog the database. The host might not be available or the user name and

password specified might not be correct.

Administrator Response: Verify that the user name and password used to catalog the database are correct. Also

verify that the database and host are available.

CDWIC0019E Function function_name was called with an incorrect number of arguments in the generic routines.



CDWIC0020E The installation program cannot locate the SQL script sql_script.

Explanation: The installation program attempted to run the SQL script specified, but could not find it in the location

specified.

Administrator Response: Verify that the location of the SQL script is valid.



|

|

|||

||

|

||

|

|

|

|

|

CDWIC0021E The installation program cannot read or access the SQL script sql_script.

Explanation: The installation program attempted to run the SQL script, but the current user does not have authority

to read the script.

Administrator Response: Check the permissions associated with the SQL script.

CDWIC0022E The installation program cannot run SQL script sql_script.

Explanation: The SQL script might not exist or it might contain SQL statements that are not valid.


CDWIC0023E The installation program cannot remove the database user information from SQL script sql_script.

Explanation: The installation program cannot find the file or might not have the correct permissions.

Administrator Response: Review the SQL script listed and verify that all user name and password information has

been completely removed.

CDWIC0024E The installation program cannot run a test DB2 command.

Explanation: A test database command was attempted to verify access to the DB2 command line interface.

Administrator Response: Verify which user you specified for database access. Verify that the DB2 command line

executable is located in the path for the specified user.

CDWIC0025E No interp argument was supplied to the function.



CDWIC0026E The argument argument is only allowed on Windows operating systems.

Explanation: The argument is not allowed on the current operating system.

Administrator Response: Attempt the installation on a Windows machine or run it with different arguments.

CDWIC0027E The argument argument is only allowed on Windows, AIX, or Solaris operating systems.


Administrator Response: Attempt the installation on the supported platforms or run it with different arguments.

CDWIC0028E The argument is only allowed on Windows, AIX, Solaris, and Linux operating systems.


Administrator Response: Attempt the installation on the supported platforms or run it with different arguments.

CDWIC0029E An unknown interp argument interp was specified.



CDWIC0030E The installation program cannot start an existing database instance for database database_name.

Explanation: An attempt was made to access the database. The installation program could not start the database

instance.

Administrator Response: Manually try to start the database instance. If necessary, contact the database

administrator.



CDWIC0031E The installation program cannot catalog the remote host host_name for the central data warehouse.

Explanation: The host name specified might not be correct or the host might not be available.

Administrator Response: Verify that the user name, password, host name, and port values are all correct for the

database. Verify that the remote database instance is started and that the host is available.

CDWIC0032E The installation program cannot connect to the database database_name.

Explanation: The host might not be available or the wrong host name might be specified.

Administrator Response: Verify that the user name and password specified for the database are correct. Verify that

the database instance is started.

CDWIC0033E The component type component_type specified in file file_name for the distributed option is an

unknown type.

Explanation: Valid types are COPT_CTRL_TYPE(0), COPT_CDW_TYPE(1), COPT_MART_TYPE(2), and

COPT_RPI_TYPE(3).


CDWIC0034E An unknown connection type connection_type was specified when attempting to access the

database. Valid connection types are conn_type_connect(0) and conn_type_attach(1).

Explanation: An internal error occurred.


CDWIC0035E Function function_name was called without a host name.



CDWIC0036E Function function_name can only be called in the context of a distributed (custom) installation.



CDWIC0037E The value for a property property in the configuration file file_name cannot be NULL during a

distributed (custom) installation.

Explanation: The property specified cannot be NULL during a distributed installation.


CDWIC0038E The installation program cannot catalog the TCP/IP node node_name for database database_name.

Explanation: The installation program could not catalog a remote database system and cannot access the remote

databases.

Administrator Response: Verify that the correct host name was entered in the GUI for the specified database.

CDWIC0039E The installation program cannot catalog the database database_name.

Explanation: The installation program cannot access the database.

Administrator Response: Verify that the user name, password, host name, and port information entered in the GUI

are correct.



CDWIC0040E Method method is not supported for the module module_name.



CDWIC0041W Warnings were detected while running the SQL script sql_script, but the installation program was

instructed to continue.

Explanation: A warning was found while running an SQL script. Although these errors are expected and not

considered fatal, they should be reviewed to verify that no corrective action should be taken.

Administrator Response: Review the installation log files found in the Tivoli common logging directory for specific

information about the warnings.

CDWIC0042W An empty SQL script sql_script was found, but the installation program was instructed to

continue.

Explanation: An empty file was found while running an SQL script. Although these errors are expected and not

considered fatal, they should be reviewed to verify that no corrective action should be taken.

Administrator Response: Review the installation log files found in the Tivoli common logging directory for specific

information on the warnings.

CDWIC0043W Processes scheduled by Tivoli Enterprise Data Warehouse, Version 1.1 were found and saved to

the file file_name before migrating the database to Tivoli Data Warehouse, Version 1.2.

Explanation: The installation detected an existing control database (TWH_MD) that contained scheduled Tivoli

Enterprise Data Warehouse, Version 1.1 processes. Since these schedules will be lost during the migration to Tivoli

Data Warehouse, Version 1.2, the schedules were saved to the file for reference when configuring the processes in

Tivoli Data Warehouse, Version 1.2.

Administrator Response: If necessary, review the file for assistance scheduling Tivoli Data Warehouse, Version 1.2

processes. No further action is required.

CDWIC0044E The installation program cannot add user user_name to group group_name.

Explanation: The installation could not add the specified user to the specified group.

Administrator Response: Check the user name and group name to verify that they are correct. Also verify that the

user running the installation has permission to change the group information for the specified user.

CDWIC0045W The installation program cannot remove the group group_name.

Explanation: The installation could not remove the group from the system.

Administrator Response: Check the group name to verify that it is correct. Verify that the user running the

installation has permission to remove group information.

CDWIC0046E The environment variable TWH_TOPDIR is not set. Install Tivoli Data Warehouse, Version 1.2

before running this installation program.

Explanation: The TWH_TOPDIR environment variable sets the top-level directory in which the Tivoli Data

Warehouse files are installed. The default value on Windows systems is %ProgramFiles%\TWH\. The default value

on UNIX systems is /opt/twh/.

Administrator Response: Ensure that the system was restarted after the installation of Tivoli Data Warehouse,

Version 1.2. Review the trace and message logs in the Tivoli common logging directory for previously listed error

information. Reinstall Tivoli Data Warehouse, Version 1.2 if TWH_TOPDIR is still not set.



CDWIC0047E The installation program cannot modify the udf_mem_sz parameter for the local DB2 server

instance.

Explanation: The installation program attempted to modify the configuration options on the local DB2 server

instance. The udf_mem_sz parameter update is necessary for the proper operation of Tivoli Data Warehouse.

Administrator Response: Verify that the DB2 user has proper authorization within DB2 to change the database

configuration arguments.

CDWIC0071E The installation program cannot locate or include the generic routines in the twh_gen_routines.pl

file.

Explanation: The generic routines file contains methods and subroutines that are necessary for the installation

program to function correctly. Since this file cannot be found, the installation program must exit.

Administrator Response: Verify that the file has been installed and check the permissions to access the file and

directory.

CDWIC0072E The installation program cannot create the directory directory_name.

Explanation: An attempt to create the directory failed. The directory is needed for the installation program to

function properly.

Administrator Response: Check the permissions of the parent directory for the directory. Verify that the parent

directory exists and that the user performing the installation can write to it.

CDWIC0073E The installation program cannot modify the applheapsz parameter for the database database_name.

Explanation: The installation program attempted to modify the configuration options on the database specified. The

applheapsz parameter is necessary for the proper operation of Tivoli Data Warehouse.



CDWIC0074E The installation program cannot register the database database_name as an ODBC data source.

Explanation: The database must be registered as an ODBC data source so that the database can be used by ODBC

client programs.


CDWIC0075E The installation program cannot register OLE/OCX.

Explanation: The attempt to register OLE/OCX was unsuccessful for the control database (TWH_MD). Registration

is done by using the iwh2regi command. Since this is only one part of the control database installation, this is a fatal

error and the installation program stops.


CDWIC0076E The installation program cannot configure the DB2 Data Warehouse Center control database

(TWH_MD) tables.

Explanation: The installation program failed to run the iwh2regi.exe DB2 command to update and configure the

control database tables that are needed to configure Tivoli Data Warehouse.

Administrator Response: Verify that the user name and password entered for the control database are correct.

CDWIC0077E The installation program cannot modify the udf_mem_sz parameter for database database_name.

Explanation: The installation program attempted to modify the configuration options on the database specified. The

udf_mem_sz configuration option is necessary for the proper operation of Tivoli Data Warehouse.

Administrator Response: Verify that the user name and password entered for the database are valid and that the

user has the correct permissions.



CDWIC0078E The installation program cannot run the script script.



CDWIC0079E The installation failed to import the tag file file_name into the database database_name. Look at the

log file in the directory directory_name for error information.

Explanation: Tag files are used to import information into the control database (TWH_MD) for use by the Data

Warehouse Manager.

Administrator Response: Review the log file for errors. Verify that the user name and password entered for the

database are correct.

CDWIC0080E The argument argument that is specified at the command line is not a valid argument.

Explanation: One of the command line arguments specified is not valid for the installation program.

Administrator Response: Review the command syntax.

CDWIC0081W The installation could not stop the database database_name instance.

Explanation: An attempt to stop the database instance did not succeed.

Administrator Response: Try installing again and verify that the correct database user is specified.

CDWIC0082E The installation program cannot write to the configuration file file_name for the core component

list.

Explanation: The installation program failed to create the core component list file that contains the database and

host information for each of the Tivoli Enterprise Data Warehouse, Version 1.1 components.

Administrator Response: Ensure that the file permissions are set correctly and that there is adequate space on the

system. Try the installation again.

CDWIC0085E Only one metadata database can be defined in the configuration file file_name.

Explanation: The configuration file specified contains tag information for more than one metadata database.

Metadata database configuration file tags must begin with TWH_CTRL_ or COPT_CTRL_.


CDWIC0086E The installation program cannot modify the app_ctl_heap_sz parameter for the database

database_name.

Explanation: The installation program attempted to modify the app_ctl_heap_sz parameter for the specified

database. This parameter is necessary for proper operation of Tivoli Data Warehouse.



CDWIC0088E There must be at least one central data warehouse defined in the configuration file file_name.

Explanation: Central data warehouses can be defined with tags beginning with TWH_CDW and COPT_CDW.


CDWIC0089E There must be at least one data mart defined in the configuration file file_name.

Explanation: Data marts can be defined with tags beginning with TWH_DM and COPT_DM.




CDWIC0091E The installation program is unable to retrieve control server information from the Tivoli Data

Warehouse Registry.

Explanation: The installation program attempted to determine the database information for the Tivoli Data

Warehouse control server. The Tivoli Data Warehouse Registry contains internal metadata that is used by Tivoli Data

Warehouse.

Administrator Response: Verify that the user name and password entered for the control database (TWH_MD) are

correct and try installing again.

CDWIC0092E The installation program program_name can only run on a platform platform.

Explanation: The installation action is not valid on the current operating system.

Administrator Response: Move to a different system with a supported operating system installed or install or

upgrade to a valid operating system on this system and try the installation again.

CDWIC0093E The installation program failed to import database database_name as a source into the DB2 Data

Warehouse Center. Look at the log file in directory directory_name for error information.

Explanation: The installation program attempted to create a source database entry in the DB2 Data Warehouse

Center for the database name, but the tag file that contains this information could not import into the DB2 Data

Warehouse Center.

Administrator Response: Verify that the user name and password information specified for the database is correct.

Examine the log file for error information and try the installation again.

CDWIC0094E The installation program failed to import database database_name as a target into the DB2 Data

Warehouse Center. Look at the log file in directory directory_name for error information.

Explanation: The installation program attempted to create a target database entry in the DB2 Data Warehouse

Center for the database name, but the tag file that contains this information failed to import into the DB2 Data

Warehouse Center.



CDWIC0095W The installation program could not remove the system ODBC data source entry for database

database_name.

Explanation: The ODBC data source entry that could not be removed will not cause any issues with the currently

running system. However, the ODBC data source entries will still be configured on the system.

Administrator Response: Manually remove the ODBC entry for the specified database.

CDWIC0096W The installation program could not drop the database database_name.

Explanation: The installation program attempted to remove the database, but could not, so the database is still

available.

Administrator Response: Verify that the user name and password are correct for the database. Also verify that the

database is available and that the host is running. Contact the database administrator for further assistance in

resolving this issue.

CDWIC0097E The installation program could not drop remote database database_name.

Explanation: The database might be in use or the host might be down.

Administrator Response: Verify that the user name and password are correct for the database. Also verify that the

database is available and that the host is running.



CDWIC0098E The installation program cannot find the file file_name.

Explanation: The installation program attempted to access the file, but could not find it.

Administrator Response: Verify that the file exists and try the installation again.

CDWIC0099E The installation program cannot read the file file_name.

Explanation: The installation program could not access the file for reading.

Administrator Response: Check the directory and file permissions of the file and try the installation again.

CDWIC0100W Warnings were detected while running the SQL script sql_script.

Explanation: The warnings returned do not make the system unstable. However, consult the message and trace logs

to verify the cause of the warning.

Administrator Response: Review the message and trace logs for additional information.

CDWIC0101E The installation program failed to create the source and target database (database_name) tag file to

import into the DB2 Data Warehouse Center.

Explanation: The installation program attempted to create a tag file to add a source or target database to the DB2

Data Warehouse Center.

Administrator Response: Verify that you have permissions to create the tag file. Check for available space.

CDWIC0102W The installation program failed to start the warehouse logger service.

Explanation: The service might already be started.


CDWIC0103W The installation program failed to start the warehouse kernel service.

Explanation: The service might already be started.


CDWIC0104W The installation program failed to stop the warehouse kernel service.

Explanation: The service might already be stopped.


CDWIC0105W The installation program failed to stop the warehouse logger service.

Explanation: The service might already be stopped.


CDWIC0106E The installation program failed a test connection to host host_name on port port for database

instance instance.

Explanation: The test connection to the database failed. Since the database is not accessible, the installation program

must exit.

Administrator Response: Verify that the user ID and password entered in the installation wizard are correct. Check

that the remote host is available and that the DB2 server is running on the port specified.



CDWIC0107E The installation program could not commit Tivoli Data Warehouse Registry entries. Refer to the

log files in directory_name directory for details on the exact cause of the failure.

Explanation: The installation program failed to write the Registry information to the Registry database. The Registry

contains internal metadata that is used by Tivoli Data Warehouse.

Administrator Response: Check the log file for further information about the error. Correct the problem if possible

and try the installation program again.

CDWIC0108E A user defined installation program program_name is associated with the agent site agent_site.

Remove the user defined installation program before removing the agent site.

Explanation: A warehouse pack is currently installed and is using the agent site. While warehouse packs are using

this agent site, the site cannot be removed.

Administrator Response: Uninstall the warehouse packs that use the installation program.

CDWIC0109E The installation program cannot remove the control database (TWH_MD) once it is created.

Explanation: The central data warehouse database is used for the installation of warehouse packs for Version 1.1

and must be retained for backward compatibility.

Administrator Response: This database cannot be removed. If the wrong database was chosen, select another

database for removal.

CDWIC0110E The installation program cannot remove the mart database (TWH_MART) database once it is

created.

Explanation: The mart database is used to install warehouse packs for Version 1.1 and must be retained for

backward compatibility.

Administrator Response: This database cannot be removed. If the wrong database was chosen, select another

database for removal.

CDWIC0111E Removing the selected central data warehouse databases will remove all currently defined central

data warehouse databases.

Explanation: Tivoli Data Warehouse cannot function properly without at least one defined central data warehouse

database.

Administrator Response: If only one central data warehouse database is defined to the system, there is nothing

more to do. If more than one central data warehouse is defined to the system, select fewer databases and try to

remove them again.

CDWIC0112E Removing the selected data mart databases will remove all currently defined data mart databases.

Explanation: The data mart databases selected for removal will cause all data mart databases currently defined to

the Tivoli Data Warehouse to be removed. The warehouse cannot function properly without at least one data mart

database defined.

Administrator Response: If only one data mart database is defined to the system, there is nothing more to do. If

more than one data mart database is defined to the system, select fewer databases and try to remove them again.

CDWIC0115E The installation program failed to import the agent site agent_site_name into the DB2 Data

Warehouse Center. Look at the log file in the directory directory_name for error information.

Explanation: The installation program could not import the agent site information into the DB2 Data Warehouse

Center.





CDWIC0116E The installation program could not obtain the current list of central data warehouse databases.

Explanation: The list is contained in the Tivoli Data Warehouse Registry. The Registry contains internal metadata

that is used by Tivoli Data Warehouse.

Administrator Response: Verify that the user name and password information specified for the metadata database

is correct. Verify that the DB2 server containing the metadata database is started.

CDWIC0117E The installation program could not obtain the current list of data mart databases.

Explanation: The list is contained in the Tivoli Data Warehouse Registry. The Registry contains internal metadata

that is used by Tivoli Data Warehouse.


is correct. Verify that the DB2 server containing the metadata database is started.

CDWIC0118W The installation program could not remove the script instance information from the

TWG.script_instance table for database database_name.

Explanation: The installation program attempted to delete information from the TWG.script_instance table. The

command failed to run properly and returned an error.


is correct. Examine the table in question and verify that there is no data for the database in the TWG.script_instance

table.

CDWIC0119W The installation program could not remove the ODBC data source information from the

TWG.odbc_datasource and TWG.odbc_comp_profile tables for database database_name.

Explanation: The installation program attempted to delete information from the TWG.odbc_datasource and

TWG.odbc_comp_profile tables. The command failed to run properly and returned an error.


is correct. Examine the tables in question and verify that the database is removed.

CDWIC0120W The installation program could not remove the client database information from the

TWG.client_database table for database database_name.

Explanation: The installation program attempted to delete information from the TWG.client_database table. The

command failed to run properly and returned an error.


is correct. Examine the table in question and verify that the database has been removed.

CDWIC0121E The installation program cannot find the component component in the current configuration.

Explanation: The installation program cannot access the component. You might not have authority to access the

metadata database.


is correct. Verify the name of the component is correct and try the command again.

CDWIC0122W The installation program is unable to copy the core installation file to the installation directory

directory_name.

Explanation: The installation user might not have the correct authority or there might not be enough space in the

directory.

Administrator Response: Verify that the installation user has permission to copy files into the TWH directory and

subdirectories and that there is adequate space to do so.

CDWIC0116E • CDWIC0122W


CDWIC0123E The installation program is unable to create the twh_shell file in the tools directory directory_name.

Explanation: The installation program cannot create the twh_shell file. The installation user might not have the

correct authority or there might not be enough space in the directory.



CDWIC0124E The installation was cancelled.

Explanation: Since the installation was cancelled, many cleanup operations did not run.

Administrator Response: Verify that the installation is completely cleaned up before installing again. See Installing

and Configuring Tivoli Data Warehouse for information about cleaning up a failed installation.

CDWIC0127W The uninstallation program could not find the agent site for the local system.

Explanation: The uninstallation program could not find the agent site in the Tivoli Data Warehouse Registry on the

control server. The uninstallation program continued, but the agent site might not have been removed from the

configuration.

Administrator Response: Verify that the agent site has been removed from the TWG.host_function_profile table that

is located in the control database (TWH_MD) or type the following command at a command prompt:

"<TWH_TOPDIR>\tools\perl\bin\perl.exe" "<TWH_TOPDIR>/tools/bin/twh_get_config.pl" -c RA where

<TWH_TOPDIR> refers to the top directory where Tivoli Data Warehouse is installed.

If the agent site still appears to be installed, the Registry will need to be updated manually. Contact IBM Customer

Support for assistance with manually removing the agent site information.

CDWIC0128W The uninstallation program could not remove the agent site agent_site from the Tivoli Data

Warehouse Registry.

Explanation: The uninstallation program continued to clean up the agent site, but the agent site might not be

removed from the Registry.

Administrator Response: Verify that the agent site has been removed from the TWG.host_function_profile table that

is located in the control database (TWH_MD) or type the following command at a command prompt:

"<TWH_TOPDIR>\tools\perl\bin\perl.exe" "<TWH_TOPDIR>/tools/bin/twh_get_config.pl" -c RA where

<TWH_TOPDIR> refers to the top directory where Tivoli Data Warehouse is installed.

If the agent site still appears to be installed, the Registry will need to be updated manually. Contact IBM Customer

Support for assistance with manually removing the agent site information.

CDWIC0129W The uninstallation program could not remove the client database connection database_name.

Explanation: The uninstallation program could not remove the client database connection to the database specified.

This failure will not cause problems on the system, but will show unused database connections that were not cleaned

up properly.

Administrator Response: Manually remove the database connection information for the database.

CDWIC0130W The uninstallation program could not remove the node connection node_name.

Explanation: The uninstallation program could not remove the node connection information for the node specified.

This failure will not cause problems on the system, but will show unused node connections that were not cleaned up

properly.

Administrator Response: Contact your database administrator to manually clean up the node connection

information for the node specified.



CDWIC0131W The uninstallation program could not remove the DCS connection dcs_name.

Explanation: The connection specified by the database connection services (DCS) could not be removed. This failure

will not cause problems on the system, but will show unused connections, created by the database connection

services, that were not cleaned up properly.

Administrator Response: Contact your database administrator to manually clean up the DCS connection.

CDWIC0132E An administration function must be specified with -f if a core component is specified with a -c.

Explanation: The core configuration installation program requires that an administration function (-f flag) be

specified when a core component (-c flag) is specified at the command line. The valid administration function is:

uninstall.

Administrator Response: Retry the command with valid command line options.

CDWIC0133W The uninstall administration function is not supported on objects of type component_type. The

uninstallation program will not uninstall the component.

Explanation: The uninstall function was attempted on a component that was not a central data warehouse or data

mart component. The uninstall function is only supported on components of these types.

Administrator Response: If a component was selected that is not correct, try running the uninstallation program

again with the correct component. Otherwise, no further action is required.

CDWIC0134W Warehouse packs are currently using component component. The uninstallation program will not

uninstall the component.

Explanation: The uninstall function was attempted on a component that warehouse packs are using. The uninstall

function can only be run on components that warehouse packs are not using.

Administrator Response: If a component was selected that is not correct, try running the uninstallation program

again with the correct component. Otherwise, no further action is required.

CDWIC0135E An administration function was specified that is not valid.

Explanation: The core configuration installation program requires that a valid administration function (-f flag) be

specified. The valid administration function is: uninstall.

Administrator Response: Retry the command with the valid command line options.

CDWIC0136E The current version registry_version of the Tivoli Data Warehouse Registry is at an unsupported

level.



CDWIC0141E The central data warehouse schema cannot be removed because it does not exist.



CDWIC0142E The data mart schema cannot be removed because it does not exist.



CDWIC0131W • CDWIC0142E



instance instance. A user ID or password was specified that is not valid.


must exit.

Administrator Response: Verify that the user name and password entered in the installation wizard are correct.

CDWIC0144E The installation program cannot create the database database_name for Tivoli Data Warehouse. A

user ID or password was specified that is not valid.

Explanation: The installation could not create a new database.


CDWIC0145E The installation program cannot create the remote agent site because the control server is not at

the correct level. You must first upgrade the control server to the version level before installing the

remote agent site.

Explanation: The installation program checked the level of the control server and determined that it was not at the

correct level. Based on it’s current level, the remote agent installation failed.

Administrator Response: Upgrade the control server to the level specified and retry the remote agent installation

again.


instance instance. A DB2 UDB on z/OS and OS/390 location was specified that is not valid.


must exit.



instance instance. A DB2 UDB database type was specified for a DB2 UDB on z/OS and OS/390

database.

Explanation: The test connection to the database failed, because an incorrect database type was specified. Since the

database is not accessible, the installation program must exit.

Administrator Response: Verify that the proper database type was specified for the database in the installation

wizard.

CDWIC1040E The current version version of the central data warehouse is at an unsupported level.

Explanation: The central data warehouse is at an unknown level and the installation is corrupted.


CDWIC1050E The central data warehouse tables do not match the expected tables for version version.

Explanation: The central data warehouse is at an unknown level and the installation is corrupted.


CDWIC1051E The central data warehouse database sequences do not match the expected sequences for version

version.





CDWIC1052E The central data warehouse indexes do not match the expected indexes for version version.



CDWIC1053E The central data warehouse constraints do not match the expected constraints for version version.



CDWIC1054E The central data warehouse triggers do not match the expected triggers for version version.



CDWIC1055E The installation program failed to update the current environment using the file file_name.

Explanation: The installation program tried to load the file into the current environment, but could not update the

environment variables.

Administrator Response: Check the syntax of the file and verify that the file exists and that permissions are correct.

CDWIC1056E The installation program failed to parse the configuration file file_name.

Explanation: The configuration file contains entries that are not valid.

Administrator Response: Review the message logs for previously listed error messages that give more information

about the problem.

CDWIC1057E Validation of the configuration file file_name failed.

Explanation: The configuration file contains entries that are not valid.

Administrator Response: Review the message logs for previously listed error messages that give more information

about the problem.

CDWIC1058E The directory directory_name that is defined by the variable variable is not a valid directory.

Explanation: The directory that is defined by the variable does not exist or is not available.

Administrator Response: Verify that the directory is created and available.

CDWIC1059E The directory directory_name is not accessible.

Explanation: The directory should be readable and writable by the user performing the installation.

Administrator Response: Check the permissions of directory specified.

CDWIC1060E The installation program failed to create a temporary table space for database database_name.

Explanation: A temporary table space is required. The database user might not have access to the database or there

might not be enough disk space available.

Administrator Response: Check the database permissions for the database user specified during the installation.

Verify that there is enough disk space available and retry the installation.



CDWIC1061E The installation program failed to promote steps (step_names) to production mode. The error was:

error.

Explanation: The installation program could not change the step names to production mode.

Administrator Response: Verify that the database permissions are correct. Verify that the DB2 Data Warehouse

Center services are running. Review the error message supplied and try the installation again.

CDWIC1062E The installation program failed to set the password of the DB2 Data Warehouse Center source or

target (source_or_target) named (inforesource_name).

Explanation: The installation program attempts to set the password of the DB2 Data Warehouse Center sources and

targets that it creates. These passwords must be set before any warehouse packs are installed or any Data Warehouse

Steps are run. Since the installation program was not able to set the password for this source or target, the

installation failed.

Administrator Response: Verify that DB2 on the control server is started. Verify that the vwkernel and vwlogger

services on the control server is started. If the problem persists, run FFDC and contact IBM Customer Support.

CDWIC1063E The installation program failed to set the password of the DB2 Data Warehouse Center agent site

agent_site_name.

Explanation: The installation program attempts to set the password of the DB2 Data Warehouse Center sources and

targets that it creates. These passwords must be set before any warehouse packs are installed or any Data Warehouse

Steps are run. Since the installation program was not able to set the password for this source or target, the

installation failed.

Administrator Response: Verify that DB2 on the control server is started. Verify that the vwkernel and vwlogger

services on the control server is started. If the problem persists, run FFDC and contact IBM Customer Support.

CDWIC1064E The Tivoli Data Warehouse Registry method method_name failed with return code return_code.

Explanation: One of the methods that updates the Tivoli Data Warehouse failed.

Administrator Response: Verify that the database instance is started and that the control database (TWH_MD) is

accessible. Verify that the user name and password are correct for the database. Check the log file for further

information about the error and correct the problem. Then try the installation again.

CDWIC1065E A failure was detected while running the tag file generator. The error was: error.

Explanation: The installation program failed to run the tag file generator tool properly.


CDWIC1066E The directory directory_name specified for the report source is not accessible.

Explanation: This directory should have been created and be readable and writable by the user performing the

installation.

Administrator Response: Check that the directory is available and that the permissions of the directory are correct.

CDWIC1067E The destination folder for the Tivoli Crystal Publisher was not specified.

Explanation: This is an internal error. The installation program should have built a valid parameter list. The

destination folder is needed in the parameter list to determine where the Crystal report files will be installed.


CDWIC1068E The source data source name for the Tivoli Crystal Publisher was not specified.

Explanation: This is an internal error. The installation program should have built a valid parameter list. The source

data source name is needed in the parameter list to determine what database the Crystal report files will be

accessing. This data source name was not specified by the calling program.




CDWIC1069E The source data source user ID for the Tivoli Crystal Publisher was not specified.


data source user ID is needed in the parameter list to allow Crystal reports to access the data source. This data

source user ID was not specified by the calling program.


CDWIC1070E The source data source password for the Tivoli Crystal Publisher was not specified.


data source password is needed in the parameter list to allow access to the source data source name by the Crystal

reports. This data source password was not specified by the calling program.


CDWIC1071W Installation of the report server component was successful. However, the Tivoli Crystal Publisher

failed to install reports from source source_name. In order to retry the installation of the migrated

reports, use the twh_core_admin command line utility.

Explanation: The Tivoli Crystal Publisher attempted to install the reports from the source specified. This installation

failed to complete successfully.

Administrator Response: Verify that the reports to be installed are available. Verify that the Crystal Enterprise

server is available and that the user specified has the proper permissions on the server to allow the report

installation. If necessary, run FFDC and contact IBM Customer Support.

CDWIC1072E The installation program failed to convert the comma separated value files to XML format for the

application with product code product_code.

Explanation: An attempt was made to convert the Version 1.1 comma separated value formatted reports to the XML

report format. This attempt failed.


CDWIC1073W Installation of the report server component was successful. However, the installation program

failed to convert reports from the control database (TWH_MD) to XML format. In order to retry the

report migration, use the twh_core_admin command line utility.

Explanation: An attempt was made to convert the Version 1.1 reports currently installed in the control database to

the XML report format. This attempt failed.


CDWIC1074E The installation program failed to convert the XML files to Crystal RPT format for the application

with product code ava_code.

Explanation: An attempt was made to convert the Version 1.1 XML report format to the Crystal RPT report format.

This attempt failed.



failed to convert the control database (TWH_MD) reports from the XML report format to the Crystal

report format. In order to retry the report migration, use the twh_core_admin command line utility.

Explanation: An attempt was made to convert the Version 1.1 reports currently installed in the control database

from the XML report format to the Crystal report format. This attempt failed.

Administrator Response: Ensure that %TWH_TOPDIR% does not contain a trailing slash, as it does in

TWH_TOPDIR=C:\apps\TWH\. Furthermore, launch the Crystal Configuration Manager and verify that all

configured Crystal servers are running and enabled. Note that a server could have a status that indicates it is



|||

||

|||

running, but still be disabled. If a server is disabled, enable it and run twh_core_admin -f report_migrate to retry the

report migration.

If errors persist, make sure that no DLL files are missing as a result of an unreported Crystal Enterprise installation.

CDWIC1076E The installation program is unable to retrieve report server information from the Tivoli Data

Warehouse Registry.

Explanation: The installation program attempted to determine the configuration information for the Tivoli Data

Warehouse report server. The Tivoli Data Warehouse Registry contains internal metadata that is used by Tivoli Data

Warehouse.

Administrator Response: Verify that the user name and password entered for the control database (TWH_MD) are

correct and try installing again.


failed to convert some reports from the control database (TWH_MD) to XML format. In order to

retry the report migration, use the twh_core_admin command line utility.

Explanation: An attempt was made to convert the Version 1.1 reports currently installed in the control database to

the XML report format. This attempt failed for some reports.

Administrator Response: Check the log file for a list of failed reports. Update the reports and run the migration

again by using the twh_core_admin command. If the report continues to fail migration, then run FFDC and contact

IBM Customer Support.


failed to convert some of the control database (TWH_MD) reports from the XML report format to

the Crystal report format. In order to retry the report migration, use the twh_core_admin command

line utility.

Explanation: An attempt was made to convert the Version 1.1 reports currently installed in the control database

from the XML report format to the Crystal report format. This attempt failed for some reports.

Administrator Response: Check the log file for a list of failed reports. Update the reports and run the migration

again by using the twh_core_admin command. If the report continues to fail migration, then run FFDC and contact


CDWIC1079E The installation program is unable to find the table_name table in the control database (TWH_MD).

It was unable to migrate 1.1 reports.

Explanation: The table specified is needed in order to perform the RPI report migration. Running report migration

from the command line interface is only valid on a 1.1 upgraded configuration.

Administrator Response: Verify that the installation program is running on a 1.1 upgraded configuration and try

the migration again.

CDWIC1080W Installation of the report server component was successful. However, the Tivoli Crystal Publisher

failed to install some reports from source source_name. In order to retry the report migration, use the

twh_core_admin command line utility.

Explanation: The Tivoli Crystal Publisher attempted to install the reports from the source specified. This installation

failed for some reports.

Administrator Response: Verify that the reports that failed to be installed are available.

CDWIC5005E The warehouse pack installation program could not read the warehouse pack configuration file

file_name.

Explanation: The warehouse pack installation program did not find or could not read the configuration file it needs

to proceed. The configuration file is generated by the installation wizard.

Administrator Response: Check the permissions to your %TEMP% directory, which is located in the Tivoli common

logging directory under /cdw, and try the installation again.



||

|

CDWIC5006E The required value that specifies the warehouse pack configuration file was not supplied.

Explanation: The warehouse pack installation program did not find a value needed by the installation program to

install the warehouse pack. An argument is automatically generated and supplied to the installation program by the

installation wizard. However, you must manually supply the argument if you are using the command line. The

configuration file is specified by -c.

Administrator Response: If the installation wizard was used, no additional action can be performed locally. If you

used the command line, verify that you specified the name of the configuration file with -c. If necessary, run FFDC

and contact IBM Customer Support.

CDWIC5007E The warehouse pack installation program did not find the required command line argument that

specifies the configuration file.

Explanation: The installation did not receive all the command line arguments it needs to properly start. These

values should be generated by the installation wizard during the installation process. The configuration file is

specified with -c.


CDWIC5018E A TDW_INSTALL_TYPE_DETECTED property in the twh_wep_install.cfg file is set to a value that

is not valid.

Explanation: This value determines the type of installation mode used by the warehouse pack installation program.


CDWIC5019E The WEP_ROLE value provided in the twh_install_props.cfg file is not valid etl_type.

Explanation: The warehouse pack role is a static value provided with each warehouse pack package in a file called

twh_install_props.cfg and this value determines the type of installation procedure to run.

Administrator Response: Verify that this value is ETL1, ETL2, E1E2, or MCDW.

CDWIC5020E The WEP_ROLE value CONS that is provided in the twh_app_install.cfg file is not currently

supported etl_type.

Explanation: The warehouse pack role is a static value provided with each warehouse pack package in a file called

twh_install_props.cfg. This value determines the type of installation procedure to run.

Administrator Response: CONS is not supported in this release and should not be used. Verify that this value is

either ETL1, ETL2, E1E2, or MCDW.

CDWIC5022E A TDW_WSOURCEx property is not valid in the twh_wep_install.cfg file or the warehouse pack

source section is not in the correct sequence.

Explanation: The properties supply the warehouse pack application sources and the configuration file determines

the warehouse pack installation. Some properties are interdependent.


CDWIC5023E The number of global objects created is not valid.

Explanation: There was a problem with the process that loads the global variables in the warehouse pack

installation program.


CDWIC5042E The installation program could not open the warehouse pack twh_install_props.cfg file located at

directory_name.

Explanation: The file that drives the warehouse pack installation parameters could not be accessed or located. The

file is required to install the warehouse pack.



Administrator Response: Verify that the file exists and that the file permissions allow the installation user to access

this file.

CDWIC5043E The property property_name was not defined in the application installation file.

Explanation: The is an internal error. The file that drives the warehouse pack installation process is missing a

parameter that is required to complete the warehouse pack installation.


CDWIC5044E The installation program cannot create an application backup directory at directory_name.

Explanation: The backup directory is used to back up the metadata database and the file systems of the installed

warehouse pack.

Administrator Response: Verify that the installation user has permission to create directories at the location

specified.

CDWIC5045E The installation program is unable to back up files from directory directory_name.

Explanation: The installation is trying to copy files supplied by the warehouse pack to the TWH product tree.

Administrator Response: Verify that the installation user has permission to copy files at the location specified.

CDWIC5046E The installation program is unable to create the warehouse pack translate directory.

Explanation: The translate directory is used to store custom translation files deployed by some warehouse packs.



CDWIC5047E The installation program is unable to create the warehouse pack export directory.

Explanation: The export directory is used to store DB2 Data Warehouse Center backup delta information.



CDWIC5048E The installation program is unable to copy application files to the installation directory

directory_name.

Explanation: The installation is trying to copy files supplied by the warehouse pack to a directory in the TWH

product tree.



CDWIC5049E The installation program is unable to copy warehouse pack translate files to the shared translate

directory directory_name.

Explanation: The installation is trying to copy files supplied by the warehouse pack to a directory in the TWH

product tree.



CDWIC5050E The installation program is unable to create the application directory directory_name.

Explanation: The warehouse pack installation program could not create the specified directory.





CDWIC5051E The installation program failed to stop the DB2 Data Warehouse Center NT services vwkernel and

vwlogger.

Explanation: The warehouse pack installation program could not stop the DB2 Data Warehouse Center services

needed to load warehouse pack metadata into the metadata database.

Administrator Response: Verify that the installation user has permission to start and stop these services.

CDWIC5053E The installation program could not make the database backup of the metadata database.

Explanation: The warehouse pack installation program may not have been able to stop the DB2 database instance.

The installation was backing up the control database (TWH_MD) and received an error.

Administrator Response: Test stopping DB2 by typing db2stop force at the DB2 command line. Review the error

message supplied by the database vendor and review the DB2 logs.

CDWIC5058E The installation program could not locate any tag files to load into the DB2 Data Warehouse

Center in the tag_file_dir directory.

Explanation: The installation program requires one or more tag files to be supplied with the warehouse pack. It also

requires tag files to be available from the Tivoli Data Warehouse installation.

Administrator Response: Verify that a tag file exists in the specified directory. If not, run FFDC and contact IBM

Customer Support.

CDWIC5059E The installation program failed while importing the tag file tag_file_name into the DB2 Data

Warehouse Center.

Explanation: The installation was importing objects into the DB2 Data Warehouse Center.

Administrator Response: Review the specified log for detailed information about the error and reinstall after

resolving the error.

CDWIC5060W Warnings were detected while loading the tag file named tag_file_name into the DB2 Data

Warehouse Center, but the installation program was instructed to continue.


CDWIC5061E The installation program failed to clean up the warehouse pack export directory.

Explanation: The warehouse pack installation program failed to delete the temporary files in the SQL/export

directory.

Administrator Response: Verify that the installation user has permission to remove files from the TWH directory

and subdirectories.

CDWIC5065E An error was encountered while trying to read or run the application script file_name.

Explanation: The warehouse pack installation program could not find the specified file or had permissions problems

with it.

Administrator Response: Verify that the specified file exists and that the installation user has permission to use and

run it.

CDWIC5066E An error was detected while running the script_type extension script supplied by the warehouse

pack.

Explanation: Warehouse packs can supply custom scripts that extend Tivoli Data Warehouse functionality.

Administrator Response: Verify that the script can be run by the installation user. Review the installation trace logs

for extension script failure information.



CDWIC5068E The installation program is unable to create the directory_name directory.

Explanation: The attempt to create the directory to be used by extension scripts in the warehouse pack based on

Version 1.1 failed.

Administrator Response: Verify that the installation user has permission to create directories at the location

specified.

CDWIC5070E A failure was detected while running the tag file generator.

Explanation: The warehouse pack installation program failed to run the tag file generator tool properly.


CDWIC5071E The warehouse pack type is not valid.

Explanation: There might be an internal processing error between the warehouse pack installation program and

installation wizard processes.


CDWIC5077E No value was returned for the password from the user information program.

Explanation: This is an internal error. The program that accesses user information did not return a password. The

installation cannot continue.


CDWIC5078E The Perl method method is not supported for the warehouse pack installation type obj_type.

Explanation: The warehouse pack installation program has an internal problem related to the type of warehouse

pack it is installing.


CDWIC5082E The installation program failed while loading the NLS bundle.

Explanation: The NLS bundle contains translated terms that allow translated reports to be generated. The

installation could not import the bundles.

Administrator Response: Verify that all databases are running and that all specified classes were supplied. Review

the error message supplied and try the installation again.

CDWIC5083E The installation program is unable to copy the twh_install_props.cfg file to the installation

directory directory_name.

Explanation: This file contains the properties for the warehouse pack.



CDWIC5084E The installation program is unable to copy the warehouse pack installation configuration file to

file_name.

Explanation: The installation could not copy the file to the specified location.





CDWIC5086W The installation program failed to promote step (step_name) to mode mode.

Explanation: The warehouse pack installation failed to promote the step in the DB2 Data Warehouse Center.

Administrator Response: Review the error message supplied and try the installation again.

CDWIC5088E The installation program failed while trying to set connection information for the DB2 Data

Warehouse Center object.

Explanation: An internal installation program error has occurred.

Administrator Response: Ensure that the user name and password for the control database (TWH_MD) are not

blank and have valid formats. Then retry the installation.

CDWIC5089E The GUI and the application installation program are not synchronized.

Explanation: This is an internal error and is unrecoverable.


CDWIC5091E The installation program found a format that is not valid for the application release version

(APP_REL_VERSION) in the twh_install_props.cfg file. The value must have the following format:

x.x.x.x.

Explanation: The value of the property must be in the form of x.x.x.x.

Administrator Response: Correct the format of the property and retry the installation.

CDWIC5092E An error occurred while running a SELECT statement against the Tivoli Data Warehouse Registry

to get the list of installed warehouse pack versions.

Explanation: There was a problem with the a query run against the database.

Administrator Response: Confirm that queries can be run against the Tivoli Data Warehouse Registry or the control

database (TWH_MD) by this user.

CDWIC5094E A valid Tivoli Data Warehouse installation was not detected on the system. The warehouse pack

cannot be installed until Tivoli Data Warehouse is properly installed on the system.

Explanation: The correct Tivoli Data Warehouse version was not detected when a query was run to find it in the

Tivoli Data Warehouse Registry. This may be the result of a failed installation.

Administrator Response: Check the Tivoli Data Warehouse Registry to ensure that Tivoli Data Warehouse is

installed at the proper level. Run FFDC and contact IBM Customer Support.

CDWIC5095E The prerequisite version of Tivoli Data Warehouse directory_name specified by the warehouse pack

is not installed. The highest version installed is version.

Explanation: The minimum version of Tivoli Data Warehouse required to install the warehouse pack was not

detected on this system.

Administrator Response: Verify that the property TWH_CORE_PREREQ_VERSION in the twh_install_props.cfg file

is at the same level as or below the current Tivoli Data Warehouse version.

CDWIC5097E You are attempting to install a patch to a warehouse pack without installing the base product.

Install the base product first and then reinstall this patch.

Explanation: A warehouse pack patch was detected during the installation, but cannot be installed until the base

product is installed.

Administrator Response: Install the base product first.



CDWIC5098E You are attempting to install a warehouse pack patch that is not on the current release path for the

product. You can only install patches on the same major, minor, and maintenance versions of the

highest warehouse pack level installed.

Explanation: A version 1.1 based patch was detected during the installation, but cannot be installed because it is the

wrong major, minor, or maintenance version of the currently installed warehouse pack.

Administrator Response: Find and install the correct patch or upgrade the base of this warehouse pack.

CDWIC5099E A successful installation of version version of the warehouse pack is already detected on the

system.

Explanation: Reinstalling the warehouse pack can result in the loss of historical data.

Administrator Response: If you want to reinstall the current version, you must first uninstall the installed

warehouse pack and then reinstall it. Uninstalling the current version of the warehouse pack might cause a loss of

historical data. If the correct version is installed, no further action is required.

CDWIC5100E The version of the warehouse pack you are installing directory_name is older than the warehouse

pack version that is already installed.

Explanation: You cannot install an older version of a warehouse pack that is already detected on the system.


CDWIC5102E The warehouse pack cannot specify a prerequisite product code

(WPACK_PREREQ_AVA_NAME_x) in the twh_install_props.cfg file and set the version

(WPACK_PREREQ_VERSION_x) to NULL.

Explanation: In the twh_install_props.cfg file, peer dependencies can be set on other warehouse pack product codes

and versions to ensure that those warehouse packs are installed first. The WPACK_PREREQ_AVA_NAME_x and

WPACK_PREREQ_VERSION_x properties cannot be set to NULL if dependencies are to be used.

Administrator Response: Correct the properties so that they require the minimum version of the peer warehouse

pack to install the warehouse pack.

CDWIC5103E The prerequisite warehouse pack wep_name, version version was not detected on this system.

Explanation: The peer warehouse pack product code and version was not detected on the installed system. To

complete installation of the warehouse pack, the peer warehouse pack must be installed first. Peer warehouse packs

and versions are set in the twh_install_props.cfg file with the WPACK_PREREQ_AVA_NAME_x and

WPACK_PREREQ_VERSION_x properties.

Administrator Response: Install the required peer warehouse pack and then reinstall the warehouse pack.

CDWIC5104E The installation program could not determine a valid ETL_TYPE or WEP_ROLE when running.

Explanation: This is an internal error that might result from a problem in a warehouse pack’s twh_install_props.cfg

file.

Administrator Response: Verify that the values in the warehouse pack twh_install_props.cfg file are valid.

CDWIC5105E The .marker file that specifies the version of the currently installed warehouse pack was not

found. The installation program is checking the directory directory_name.

Explanation: The version marker file is needed to determine the version at which this warehouse pack is currently

installed.

Administrator Response: Confirm that this product installation is an upgrade and check for *.marker files under the

$TWH_TOPDIR/apps/ ava_code directory.



CDWIC5106E The installation program could not find the warehouse pack’s home directory under

$TWH_TOPDIR at directory_name.

Explanation: The home directory for the installed warehouse pack should be located under $TWH_TOPDIR, which

is the top-level directory in which the Tivoli Data Warehouse files are installed. The default value for $TWH_TOPDIR

on Windows systems is %installation programFiles%\TWH\. The default value on UNIX systems is /opt/twh/.

Administrator Response: Confirm that the directory exists and that the appropriate permissions are set.

CDWIC5107E Delta processing of the warehouse pack patch files failed.

Explanation: This process removes prior SQL statements from the SQL files when wrapped by the appropriate

statements.

Administrator Response: Ensure that the proper permissions are set for the warehouse pack’s directory under the

TWH_TOPDIR tree.

CDWIC5109E The installation program could not rename the warehouse pack’s version directory, in the apps

subtree, to the new version number.

Explanation: The warehouse pack installation is attempting to upgrade or patch an existing warehouse pack

installation and is unable to create the new version directory.

Administrator Response: Verify that the permissions are correct under the TWH_TOPDIR tree to allow for directory

name changes.

CDWIC5111E The installation program was unable to open the directory directory_name for reading.

Explanation: The installation program cannot access the directory.

Administrator Response: Verify that the directory exists and that permissions are set correctly.

CDWIC5112E The installation program cannot find the backup of the warehouse pack that is currently being

installed. The installation program cannot continue without the backup.

Explanation: The backup should be located under the $TWH_TOPDIR/apps_backups/ ava_code directory for the

control database (TWH_MD).

Administrator Response: Verify that the backup exists and that permissions allow this user to create directories

under the $TWH_TOPDIR directory.

CDWIC5114E The installation program could not commit the Tivoli Data Warehouse Registry entries.

Explanation: The installation program failed to write the Registry information to the Registry database. The Registry


Administrator Response: Ensure that you have permission to insert and commit entries into the control database

(TWH_MD). Also review the installation message and trace logs.

CDWIC5116E The installation program could not copy the warehouse pack files to the remote agent host at

directory_name.

Explanation: The installation program detected a failure while running the React toolkit to copy warehouse pack

files to the remote agent site.


CDWIC5119E The installation program detected a failure while running the ConfigWEP tool to set up warehouse

sources.

Explanation: This is an internal application error.

Administrator Response: Review the ConfigWEP tool logs under the Tivoli common logging directory for specific

errors about the problem.



CDWIC5120E The installation failed while trying to set the enabled code or the state of the warehouse pack to

’E’ in the Tivoli Data Warehouse Registry.

Explanation: The installation program cannot set the flag needed to persist the installation state to success in the

Tivoli Data Warehouse Registry.

Administrator Response: Ensure that the proper permissions are set to write to the control database (TWH_MD).

CDWIC5123E The installation program could not access the backup directory for the metadata database at

directory_name.

Explanation: The warehouse pack installation attempted to make a backup of the control database (TWH_MD).

Administrator Response: Ensure that the directory exists and make sure the permissions are set correctly.

CDWIC5125E The installation program could not find all required DB2 Data Warehouse Center delta export

files.

Explanation: The delta export files are needed to uninstall the warehouse pack’s DB2 Data Warehouse Center

objects. This is an internal error.

Administrator Response: Verify that there are 36 files located under the directory $TWH_TOPDIR/apps/

ava_code/v version/etl/export. If not, run FFDC and contact IBM Customer Support.

CDWIC5126E The installation program detected a failure while running the agent site tag file generator.

Explanation: The internal tag file generation tool failed while trying to make an agent site tag file for the DB2 Data

Warehouse Center import process.

Administrator Response: Validate that the selections for the agent site location are active remote agent sites in the

DB2 Data Warehouse Center.

CDWIC5127E No central data warehouse databases are registered for a consuming warehouse pack. The

warehouse pack for Version 1.2 patch installation process cannot continue.

Explanation: A consuming type of warehouse pack is a package which pulls data from one or more central data

warehouses for its own use. Therefore, one or more central data warehouse databases should be registered.


CDWIC5128E No source databases that contain a central data warehouse ETL process are registered for the

warehouse pack. The warehouse pack for Version 1.2 patch installation process cannot continue.

Explanation: A central data warehouse ETL process pulls data from a source database into a central data warehouse

database. Therefore, one or more source databases should be registered.


CDWIC5129E No version of the warehouse pack is registered as active and enabled. The warehouse pack for

Version 1.2 patch installation process cannot continue.

Explanation: To install a patch for a warehouse pack, a version of the warehouse pack must be both active and

enabled.


CDWIC5130E No DB2 Data Warehouse Center process contains the step step_name.

Explanation: The warehouse pack supplied a DB2 Data Warehouse Center step name to be scheduled or promoted.

However, the installation program cannot find a DB2 Data Warehouse Center process that contains the step.




CDWIC5131E The installation program cannot return a valid list of etl_name steps.

Explanation: The warehouse pack supplied a DB2 Data Warehouse Center step name to be scheduled or promoted.

However, the installation program was unable to determine the list of steps within the process containing this step.


CDWIC5134E The installation program cannot start the DB2 Data Warehouse Center services.

Explanation: The warehouse pack installation must stop and restart the DB2 Data Warehouse Center services in

order to perform various DB2 Data Warehouse Center installation actions.

Administrator Response: Start the DB2 Data Warehouse Center services manually and try installing again.

CDWIC5135E The installation program cannot stop the DB2 Data Warehouse Center services.

Explanation: The warehouse pack installation must stop and restart the DB2 Data Warehouse Center services in

order to perform various DB2 Data Warehouse Center installation actions.

Administrator Response: Stop the DB2 Data Warehouse Center services manually and try installing again.

CDWIC5136E The installation program failed while trying to query the Tivoli Data Warehouse Registry for the

core component state values.

Explanation: The installation program encountered an error while accessing the control database (TWH_MD). The

installation was retrieving internal configuration information that is related to the Tivoli Data Warehouse core

components.

Administrator Response: Ensure that the control database is running and that you can connect to it. Ensure that the

installation user has privileges to connect to the database.

CDWIC5137E The remote agent site agent_site_name on which you are installing the warehouse pack was not

successfully installed.

Explanation: You are attempting to install a warehouse pack on a remote agent site that was not installed properly.

Administrator Response: Review the logs for the remote agent installation and if possible, correct the problem and

reinstall it.

CDWIC5138E One or more remote agent sites (agent_site_names) are installed at a different release or patch level

than the control server. To prevent problems with the warehouse pack installation, all core

component remote agent sites must be installed at the same version as the control server.

Explanation: After a consistency check, it was determined that one more of the remote agent sites are not at the

same product level as the control server. This can cause problems with installations and the runtime environment for

the warehouse packs.

Administrator Response: Verify that all upgrades and patches to the Tivoli Data Warehouse core are installed at all

agent locations. Install the appropriate product level at sites not at the same level as the control server.

CDWIC5140E The installation program failed to retrieve the list of remote agents from the Tivoli Data

Warehouse Registry. At least one remote agent site should exist in the Registry after a successful

Tivoli Data Warehouse installation.

Explanation: The installation program was unable to retrieve a list of remote agent sites. However, after a successful

Tivoli Data Warehouse installation, a default remote agent site should exist.

Administrator Response: Verify that the Tivoli Data Warehouse installation of the control server was successful. If

so, verify that the installation of any remote agent sites was also successful.



CDWIC5141E The installation program failed to resolve the host name specified for the remote agent

agent_site_name as a valid remote agent host name in the Tivoli Data Warehouse Registry. Specify a

registered remote agent site host name.

Explanation: The remote agent site specified by the installation configuration file was not found in the Tivoli Data

Warehouse. Verify that the agent site selected exists as an actual agent location.

Administrator Response: Review the valid remote agent sites in the DB2 Data Warehouse Center. Ensure that the

value that is supplied to the warehouse pack installation program is valid.

CDWIC5142E The installation program detected an error while trying to retrieve a list of core component host

names and related information from the Tivoli Data Warehouse Registry.

Explanation: An error occurred while trying to retrieve configuration information from the control database

(TWH_MD).

Administrator Response: Verify that you can connect to the database as the installation user. Review the installation

trace logs for database failure information.

CDWIC5143E The installation program detected an error while trying to copy the after script log file to the

warehouse pack’s log directory in the TWH product tree.

Explanation: The installation program was unable to copy the installation configuration file into the warehouse pack

logs directory in the TWH tree.

Administrator Response: Verify that there is adequate disk space available and that the installation user has

permission to write to the TWH product tree.

CDWIC5144E The password for a warehouse pack source was not supplied by the configuration file. This value

is required, but can be set to null.

Explanation: The password for a warehouse pack source database was not supplied in the installation configuration

file.

Administrator Response: Verify that all required values are supplied before retrying the installation.

CDWIC5147E The installation program detected a failure while trying to generate a tag file to associate DB2

Data Warehouse Center steps for the warehouse pack. possible_error_text

Explanation: An internal tool (twh_dwc_step_to_agtste.pl) used to create tag files to associate steps in the DB2 Data

Warehouse Center failed to generate the necessary tag file.

Administrator Response: Review the error information provided in the message. Correct any problems and reinstall

the warehouse pack.

CDWIC5161W No warehouse pack data mart database relationships were found in the Tivoli Data Warehouse

Registry.

Explanation: The Registry contains internal metadata that is used by Tivoli Data Warehouse. No data mart

relationship information was found.


messages indicate conditions that are acceptable. If so, no further action is required.

CDWIC5162W No data mart database tables for the warehouse pack were found or removed.

Explanation: This is an internal error. The installation program cannot find any data mart tables in the installation.

Administrator Response: Review the warehouse pack implementation guide to verify that there are no data mart

database tables to be removed. If necessary, run FFDC and contact IBM Customer Support.



CDWIC5163W A database error was detected while trying to remove data mart database objects for the

warehouse pack. The uninstallation program is continuing, but these objects might need to be

removed manually.

Explanation: This is an internal error. Some data mart objects might not have been removed by the uninstallation

program. You may need to remove these objects manually.

Administrator Response: Review the warehouse pack implementation guide to determine if the warehouse pack

contains data mart database objects that need to be removed. If necessary, run FFDC and contact IBM Customer

Support.

CDWIC5164W No warehouse pack central data warehouse database relationships were found in the Tivoli Data

Warehouse Registry.

Explanation: This is an internal error. The Registry contains internal metadata that is used by Tivoli Data

Warehouse. No central data warehouse relationship information was found. It may be that this relationship was

already removed during a previous attempt at uninstalling the warehouse pack.


contains central data warehouse database relationships that need to be removed. If necessary, run FFDC and contact


CDWIC5165W A database error was detected while trying to remove central data warehouse database objects

from database database_name for the warehouse pack. The uninstallation program is continuing, but

these objects might need to be removed manually.

Explanation: This is an internal error. Some central data warehouse objects might not have been removed by the

uninstallation program. You might need to remove these objects manually.


contains central data warehouse database objects that need to be removed. If necessary, run FFDC and contact IBM

Customer Support.

CDWIC5166W The uninstallation program failed to create a list of tables to delete from the database_name

database.

Explanation: This is an internal error. The uninstallation program could not generate a list of tables to be deleted.


contains a list of tables that need to be removed. If necessary, run FFDC and contact IBM Customer Support.

CDWIC5167W The uninstallation program failed to drop the table table_name in the database_name database.

Explanation: This is an internal error. The uninstallation program did not drop the specified table.

Administrator Response: Review the warehouse pack implementation guide to determine if this table should be

dropped. If necessary, run FFDC and contact IBM Customer Support.

CDWIC5168W The uninstallation program failed to create a list of views to delete from the database_name

database.

Explanation: This is an internal error. No list of views was generated by the installation program.


contains views that need to be removed. If necessary, run FFDC and contact IBM Customer Support.

CDWIC5169W The uninstallation program failed to drop the view view_name in the database_name database.

Explanation: This is an internal error. The uninstallation program did not drop the specified view.

Administrator Response: Review the warehouse pack implementation guide to determine if this view should be

dropped. If necessary, run FFDC and contact IBM Customer Support.

CDWIC5163W • CDWIC5169W


CDWIC5170W No files were found for the uninstallation program to delete.

Explanation: This is an internal error. The uninstallation program did not find any files to delete.

Administrator Response: It may be that the warehouse pack files were removed during a previous uninstall

attempt. If necessary, run FFDC and contact IBM Customer Support.

CDWIC5173E The uninstallation program was unable to copy the configuration input file to the temporary

directory.

Explanation: The uninstallation program user might not have the correct authorization or there might not be

enough space.

Administrator Response: Verify that you have permission to copy files to the temporary directory. Also ensure that

there is adequate disk space on the system.

CDWIC5174E The tool that configures warehouse packs was returned an error while trying to delete the

warehouse pack sources. possible_error_text

Explanation: Review the error for specific information about the problem that occurred when the ConfigWEP tool

tried to delete the warehouse pack sources.

Administrator Response: Review the error information and trace logs for the installation program that configures

warehouse packs.

CDWIC5175E The uninstallation program could not retrieve all the values required to connect to the control

database (TWH_MD). The name of the database, user name, and password are required.

Explanation: The uninstallation program cannot connect to the control database.


CDWIC5176E The uninstallation program failed to locate or open the warehouse pack properties file file_name

supplied with the warehouse pack.

Explanation: The properties file might not exist or you may not have the authority to open it.

Administrator Response: Verify that the file can be accessed by the uninstallation program user.

CDWIC5177E The uninstallation program detected a failure while trying to delete the warehouse pack objects

from the DB2 Data Warehouse Center.

Explanation: The uninstallation program could not delete the warehouse pack objects from the DB2 Data Warehouse

Center.


CDWIC5178E The uninstallation program detected a failure while running the warehouse pack script_type

extension script named script_name.

Explanation: The optional extension script that a warehouse pack can supply failed during the uninstallation

program.


CDWIC5179E The uninstallation program was unable to remove the Interim Fix Registry records.

Explanation: The uninstallation program could not remove the table that tracks patches and interim fixes.

Administrator Response: Verify that the control database (TWH_MD) is available and that you can access the

database.



CDWIC5180E The uninstallation program failed while trying to remove the relationships in the

wep_function_profile table in the Tivoli Data Warehouse Registry.

Explanation: The Registry contains internal metadata that is used by Tivoli Data Warehouse.


database.


wep_role_profiles table in the Tivoli Data Warehouse Registry.



database.

CDWIC5182E The uninstallation program failed while trying to remove the relationships in the wep_version

table in the Tivoli Data Warehouse Registry.



database.

CDWIC5183E The uninstallation program failed while trying to remove the relationships in the warehouse pack




database.

CDWIC5184E The uninstallation program failed while trying to remove the scripts names from the Tivoli Data

Warehouse Registry.



database.

CDWIC5185E The uninstallation program detected a failure while running the React toolkit to delete files from

the remote agent site host at agent_site.

Explanation: The React toolkit is used to remove warehouse pack files from the warehouse pack’s agent site. This

process failed.

Administrator Response: Review the log files associated with the React toolkit.

CDWIC5186E The uninstallation program detected a failure while running the React toolkit to delete backup

files from the remote agent site host at agent_site.

Explanation: The React toolkit is used to remove warehouse pack files from the warehouse pack’s agent site. This

process failed.

Administrator Response: Review the log files associated with the React toolkit.

CDWIC5187E The installation program cannot build a list of the central data warehouse and data mart databases

configured in the Tivoli Data Warehouse Registry. Return Code 1: return_code. Return Code 2:

return_code.

Explanation: DB2 UDB databases named central data warehouse (TWH_CDW) and mart (TWH_MART) must be

installed prior to installing warehouse packs for Version 1.1. In order to verify that these have been created, the

installation program queries the Registry. These queries did not complete successfully.



Administrator Response: Verify that the metadata database is available and try the installation again.

CDWIC5188E The following DB2 UDB databases, required for warehouse packs for Version 1.1, have not been

configured: database_names.

Explanation: DB2 UDB databases named central data warehouse (TWH_CDW) and mart (TWH_MART) must be

installed prior to installing warehouse packs for Version 1.1. The databases listed in the message have not yet been

configured.

Administrator Response: Install the missing central data warehouse and data mart DB2 UDB databases. Then

reinstall the warehouse pack.

CDWIC5189E The installation program failed to promote the warehouse pack steps.

Explanation: The warehouse pack installation failed to promote the steps in the DB2 Data Warehouse Center.

Administrator Response: Review the error message supplied and try the installation again.

CDWIC5190E A previously existing warehouse pack directory directory_name was found and the installation

program was unable to remove it.

Explanation: The warehouse pack directory already exists on the system. This may be from a previous installation

of the warehouse pack that was not completely removed. The installation program attempted to remove this

directory, but this attempt failed.

Administrator Response: Remove this directory manually and try the installation again.

CDWIC5191W The uninstallation program was unable to delete the warehouse pack directory directory_name.

Explanation: The uninstallation program could not delete the warehouse pack directory. The directory may be

currently open or in use. The uninstallation program will continue, but this directory will be left on the system and

should be removed manually.

Administrator Response: Remove this directory manually.

CDWIC5192E The installation program detected an application translate file (file_name) which does not follow

the defined naming standards.

Explanation: This is an internal error in the warehouse pack. The warehouse pack being installed did not follow the

Tivoli Data Warehouse naming standards.

Administrator Response: Contact the support group responsible for this warehouse pack.

CDWIC5193W The uninstallation program was unable to delete the warehouse pack translate files in the

directory_name directory.

Explanation: The uninstallation program could not delete the warehouse pack translate files. The files may be

currently open or in use. The uninstallation program will continue, but these files will be left on the system and

should be removed manually.

Administrator Response: Remove the warehouse pack translate files manually. Note that the translate directory may

include files from any of the installed warehouse packs. So, be sure to only remove those used by this warehouse

pack. The warehouse pack translate files will always be named using the product code as the first three characters.

CDWIC5195E The installation program detected an illegal or duplicate property in the twh_install_props.cfg file

supplied by the warehouse pack. The property is property_name.

Explanation: The twh_install_props.cfg file is an installation project file supplied with each warehouse pack. The

specified value is not valid.

Administrator Response: This is an internal error in the warehouse pack. Contact the support group responsible for

this warehouse pack.



CDWIC5196E The installation program detected that the warehouse pack installation properties file, called

twh_install_props.cfg, is missing the following properties property_names.


specified values are missing.



CDWIC5197E The installation program was unable to read or access the script_type file supplied by the

warehouse pack. The file name supplied was file_name.


property which specifies an extension script to run during the installation has a value that is not valid. The script

could not be found.



CDWIC5198E The installation program encountered an error while trying to retrieve the ETL step names from

the Tivoli Data Warehouse Registry.

Explanation: An internal error was encountered while trying to retrieve configuration information from the Registry.

Administrator Response: Review the database log for specific failure information.

CDWIC5199E The property_name property, specified in the twh_install_props.cfg file supplied by the warehouse

pack, has a value that is not valid. Review the trace log and enablement documentation for further

information on setting properties in the twh_install_props.cfg file.


property which specifies an extension script to run during the installation has a value that is not valid.



CDWIC5200E A value that is not valid was detected in the twh_install_props.cfg file supplied by the warehouse

pack. The property is property_name and the value is property_value. The value must be set to

property_type for the WEP_ROLE type of wep_role.


property is not set to the appropriate value for the specific installation scenario.



CDWIC5201E The uninstallation program could not commit the Tivoli Data Warehouse Registry entries.

Explanation: The uninstallation program failed to remove the Registry information from the Registry database. The

Registry contains internal metadata that is used by Tivoli Data Warehouse.

Administrator Response: Ensure that you have permission to delete and commit entries into the control database

(TWH_MD). Also review the uninstall message logs.

CDWIC5203E The installation program failed while trying to test a connection to the Crystal Enterprise server.

Explanation: The Crystal Enterprise server could not be contacted by the installation program.

Administrator Response: Ensure that the Crystal Enterprise server is up and ready to receive remote

communication.



CDWIC5204E The installation program failed while trying to load reports into the Crystal Enterprise server.

possible_error_text

Explanation: Reports supplied by this warehouse pack were not loaded into the Crystal Enterprise server.

Administrator Response: Review the error information supplied with the error and the reporting message logs. If

no error information is available, run FFDC and contact IBM Customer Support.

CDWIC5206E The installation program failed while trying to migrate reports supplied with the warehouse pack

to the Crystal Enterprise format (from .csv format to .xml format).

Explanation: The installation program was converting reports supplied with the warehouse pack to an intermediate

format before installing them into the Crystal Enterprise server. The conversion failed.

Administrator Response: Review the reporting message logs for more details, or run FFDC and contact IBM

Customer Support.

CDWIC5207E The installation program failed while trying to migrate reports supplied with the warehouse pack

to the Crystal Enterprise format (from .xml format to .rpt format).

Explanation: The installation program was converting reports supplied with the warehouse pack to a Crystal

Enterprise format. The conversion failed. An ODBC data source connection from the Crystal Enterprise Server to the

data mart might not exist.

Administrator Response: Review the reporting error logs for more details. If a logon error occurs, often an ODBC

data source connection from the Crystal Enterprise Server to the data mart was not established before installing a

warehouse pack that contained reports to be migrated. Refer to the steps in Installing and Configuring Tivoli Data

Warehouse for instructions about creating the ODBC connection.

In addition, ensure that the Crystal servers that can be accessed from the Crystal Configuration Manager use fully

qualified host names. If they do not, recreate them, ensuring that you specify the fully qualified host names.

If one of these issues is not the problem, run FFDC and contact IBM Customer Support.

CDWIC5208E The installation program was instructed to install reports, but no reports can be found in the

report directory supplied by the warehouse pack.

Explanation: The warehouse pack has a configuration setting of REPORTS_INCLUDED=TRUE in the

twh_install_props.cfg file. This setting requests that supplied reports be loaded into the Crystal Enterprise server. No

reports were detected in the reports directory of the warehouse pack.

Administrator Response: Ensure that reports are supplied under the reports directory in the warehouse pack.

CDWIC5209E The installation program detected that the warehouse pack schedulable_step property is not set.

Explanation: The warehouse pack is expected to supply this value in the twh_install_props.cfg file.

Administrator Response: Run FFDC and contact IBM Customer Support for the supplied warehouse package.

CDWIC5210E A value that is not valid was detected in the twh_install_props.cfg file supplied by the warehouse

pack. The property is property_name and the value is property_value. The value must not be set to

property_type for the WEP_ROLE type of wep_role.


property must be set to an appropriate value.





||

|||

||||

||

|

CDWIC5211E A value was detected that is not valid in the twh_install_props.cfg file supplied by the warehouse

pack. The property is property_name and the value is property_value. The value must be either true or

false.


property must be set to a value of True or False.



CDWIC5212E The installation program detected a failure while running the twh_get_config.pl utility.

Explanation: The twh_get_config.pl utility was being run to collect a list of installed central data warehouses and

data marts in the environment and determine if the selected targets are supported by this warehouse pack. It failed

to run properly.

Administrator Response: Review the trace log for more information or run FFDC and contact IBM Customer

Support.

CDWIC5213E The database name or database type is not valid and is either not installed or supported by this

warehouse pack. The database location selected for the location_type was database_name. The required

types are: database_types.

Explanation: The database name or the database type is not valid. Use one of the required types specified in the

message.

Administrator Response: Select another database location that is installed in the core infrastructure or ensure the

type of database selected is supported by the warehouse pack.


wep_install_stage table in the Tivoli Data Warehouse Registry.


Administrator Response: Verify that the control database is available and that you can access the database.

CDWIC5215E The installation program failed while trying to action a record in the TWG.WEP_INSTALL_STAGE




CDWIC5216E The rollback of the ConfigWEP tool processing for this warehouse pack failed. The warehouse

pack is in an inconsistent state.

Explanation: The installation of the warehouse pack failed. An attempt was made to rollback changes made while

running ConfigWEP tool, but this failed. Some changes took affect, but others did not, leaving the warehouse pack in

an inconsistent state.


CDWIC5217E The rollback of the warehouse pack data from the DB2 Data Warehouse Center failed. The

warehouse pack is in an inconsistent state.

Explanation: The installation of the warehouse pack failed. Specific changes that will prevent a reinstallation

attempt could not be rolled back.




CDWIC5218W The rollback of the warehouse pack data succeeded.

Explanation: The installation of the warehouse pack failed. Specific changes that would have prevented a

reinstallation attempt were rolled back successfully.

Administrator Response: Review the message log information to resolve the error in the warehouse pack

installation. Then reinstall the warehouse pack.

CDWIC5219E The installation program is unable to remove existing application files in the installation directory

directory_name.

Explanation: The installation is trying to remove existing application files in a directory in the TWH product tree.

Administrator Response: Verify that you have permission to remove files in the TWH directory and subdirectories.

CDWIC5220E The installation input configuration file called configuration_file contains a property that is not valid

or is a duplicate. The property is tag_value.

Explanation: This is an internal warehouse pack error. The specified file is used to drive a background installation

program. The following errors might have occurred:

v The specified property is a duplicate of one already in the file.

v The property is not recognized as a valid value.


CDWIC5221E The installation input configuration file called configuration_file contains a property called

property_name that is not valid or the value is missing.

Explanation: The specified file is used to drive a background installation program. The input parameters are listed

in this file and the format must conform to the standards specified in Installing and Configuring Tivoli Data Warehouse.

The following errors might have occurred:

v The specified property is missing.

v A multi-source value was detected to be out of sequence.


CDWIC5222E The installation program could not read or locate the input configuration file named

configuration_file.

Explanation: The file that supplies input parameters to the installation program could not be located.

Administrator Response: Verify the file exists and has permissions for the installation program to use.

CDWIC5223E The installation program could not obtain the warehouse pack source database information from

the DB2 Data Warehouse Center.

Explanation: The DB2 Data Warehouse Center source database information was unavailable.


CDWIC5224E The uninstallation program failed while trying to remove the warehouse pack source database

information from the wep_inforesource table in the Tivoli Data Warehouse Registry.



CDWIC5225E The installation program could not update the DB2 Data Warehouse Center source database

information from the warehouse pack source database information.

Explanation: The DB2 Data Warehouse Center source database information could not be set.




CDWIC5226E The uninstallation program was unable to remove the DB2 Data Warehouse Center schedule

records.

Explanation: The uninstallation program could not remove the warehouse pack step schedule information.

Administrator Response: Verify that the control database is available and that the uninstallation program user can

access the database.

CDWIC5227E The uninstallation program is unable to copy the warehouse pack uninstallation configuration file

to file_name.

Explanation: The uninstallation program could not copy the file to the specified location.

Administrator Response: Verify that you have permission to copy files into the TWH directory and subdirectories

and that there is adequate space to do so.

CDWIC5229W The uninstallation program failed to create a list of sequences to delete from the database_name

database.

Explanation: The uninstallation program could not create a list of sequences to delete.

Administrator Response: Review the uninstallation logs in the Tivoli common logging directory to ensure that


CDWIC5230W The uninstallation program failed to drop the sequence sequence_name in the database_name

database.

Explanation: The uninstallation program could not drop the sequence.

Administrator Response: Review the uninstallation logs in the Tivoli common logging directory to ensure that


CDWIC5231E The uninstallation program detected an unsupported database vendor type value of vendor_type.

Explanation: This is an internal error. The supported database vendor type values for a central data warehouse or a

mart database are DB2UDB and DB2390.


CDWIC5232E An error occurred during the warehouse pack installation. possible_error_text.

Explanation: This is an internal error. The warehouse pack installation cannot continue.


CDWIC5233W An warning condition occurred during the warehouse pack installation. possible_warning_text.

Explanation: This is an internal warning only. The warehouse pack installation will continue.

Administrator Response: If additional information is desired, run FFDC and contact IBM Customer Support.

CDWIC5234E An error occurred during the warehouse pack uninstallation. possible_error_text.

Explanation: This is an internal error. The warehouse pack uninstallation program cannot continue.


CDWIC5235W An warning condition occurred during the warehouse pack uninstallation. The message is:

possible_warning_text. The warehouse pack uninstallation program will continue. If additional

information is desired, run FFDC and contact IBM Customer Support.




CDWIC5236E The installation program could not update the DB2 Data Warehouse Center source or target

database information for the Tivoli Data Warehouse supplied sources or targets.

Explanation: This is an internal error. The DB2 Data Warehouse Center source or target database information could

not be set.


CDWIC5237E The warehouse pack installation failed to remove the warehouse pack from the DB2 Data

Warehouse Center. The warehouse pack is in an inconsistent state.

Explanation: The installation of the warehouse pack failed. An attempt was made to remove changes made in the

DB2 Data Warehouse Center by the warehouse pack tag files but this failed, leaving the warehouse pack in an

inconsistent state. An inconsistent state is caused by some configuration changes taking effect, while others do not.


CDWIC5238E The uninstallation program detected an unsupported extension script type value of script_type.

Explanation: This is an internal error. The supported extension script types for a warehouse pack uninstallation are

pre and after.


CDWIC5239E The uninstallation program extension script supplied by the warehouse pack indicated that it

identified dependent warehouse packs installed.

Explanation: The optional extension script that a warehouse pack can supply indicated that it identified dependent

warehouse packs installed. This warehouse pack cannot be uninstalled until all dependent warehouse packs have

been uninstalled.

Administrator Response: Refer to the implementation guide for the warehouse pack to determine the dependent

warehouse packs and uninstall these. If the error continues, run FFDC and contact IBM Customer Support.

CDWIC5241E The uninstallation program was unable to complete a backup of the control database (TWH_MD).

Explanation: The uninstallation program was backing up the control database and received an error.

Administrator Response: Review the uninstallation program logs in the Tivoli common logging directory.

CDWIC5242E The uninstallation program is unable to create the directory_name directory.

Explanation: The attempt to create the directory to be used by extension scripts in the warehouse pack for Version

1.1 failed.

Administrator Response: Verify that you have permission to create directories at the location specified.

CDWIC5243E The uninstallation program detected an error while trying to retrieve a list of core component host

names and related information from the Tivoli Data Warehouse Registry.

Explanation: An error occurred while trying to retrieve configuration information from the control database

(TWH_MD).

Administrator Response: Verify that you can connect to the database as the installation user. Review the installation

trace logs for database failure information.

CDWIC5244E The installation program did not find an existing application directory for this warehouse pack.

Explanation: When patching or upgrading a warehouse pack, it is expected that there will be an existing single

version of the application directory under TWH_TOPDIR/apps directory.




CDWIC5245E The installation program found more than one existing application directory for this warehouse

pack.

Explanation: When patching or upgrading a warehouse pack, an existing single version of the application directory

under TWH_TOPDIR/apps directory is expected.


CDWIC5246E The installation program identified an installation program name that is not valid referenced in a

warehouse pack tag file.

Explanation: A warehouse pack tag file refers to a installation program name that is not valid.


CDWIC5247E The installation program identified a server name that is not valid referenced in a warehouse pack

tag file.

Explanation: A warehouse pack tag file refers to a server name that is not valid.


CDWIC5248E The installation program identified an object that is not valid in a warehouse pack tag file.

Explanation: A warehouse pack tag file contains an object that is not valid.


CDWIC5249E The warehouse pack media contains more than one tag file.

Explanation: Warehouse packs built for Tivoli Data Warehouse 1.2 may provide only one tag file.


CDWIC5250W The uninstallation program failed to delete any warehouse pack records from the table

TWG.MSRC_HISTORY in the central data warehouse.

Explanation: The uninstallation program deletes references to the warehouse pack from the table

TWG.MSRC_HISTORY in the central data warehouse. However, the attempt to delete any references to this

warehouse pack failed. These references may have already been removed as part of a previous uninstallation attempt.

Administrator Response: Review the message files to determine why this deletion failed. Manually view the

contents of this table to determine whether all references to this warehouse pack have been removed from the table.

CDWICE The installation program detected a warehouse pack type (wep_role_type) that is not valid when

writing the input configuration file for the installation program that configures warehouse packs.

Explanation: Valid warehouse pack types are ETL1, ETL2, E1E2, and MCDW.


CDWIS0003E The specified component cannot be added to the list because an entry with the same host name

and port number already exists.

Explanation: The same combination of host name and port number cannot be used for more than one component.

Administrator Response: Choose another combination of host name and port number and add the component

again.

CDWIC5245E • CDWIS0003E


CDWIS0004E A connection cannot be established to the Crystal Enterprise Server on host host. The error is: error

Explanation: The test connection failed because of the error.

Administrator Response: Verify the information provided on the panel and make sure that the Crystal Enterprise

server is installed and running at the specified location.

CDWIS0005E Port number value port is not valid. The port number must be a positive integer between 1 and

65535.

Explanation: The port number must be a positive integer between 1 and 65535.

Administrator Response: Provide a valid value for the port number.

CDWIS0006E The Tablespace Size Primary value size is not valid. The value must be a positive integer between

1 and 1048576.

Explanation: The value must be a positive integer between 1 and 1048576.

Administrator Response: Provide a valid value for the table space size.

CDWIS0007E The Tablespace Size Secondary value size is not valid. The value must be a positive integer

between 1 and 1048576.

Explanation: The value must be a positive integer between 1 and 1048576.

Administrator Response: Provide a valid value for the table space size.

CDWIS0008W The installation is laying down files and configuring the environment. If you cancel the

installation now, no changes will be saved. Do you want to cancel the installation?

Explanation: You tried to cancel an installation during the initial phase when tools and utility files are being laid

down. If you cancel the installation now, no changes will take affect and your system will remain in its initial state.

The rollback operation will occur.

Administrator Response: Click Yes to cancel the installation.

Click No to continue the installation.

CDWIS0009W If you cancel the installation now, the databases will be left in an inconsistent state. You can

attempt to use the uninstallation wizard to remove the files that were laid down and to undo the

changes made in the databases. Do you want to cancel the installation?

Explanation: You tried to cancel an installation after the initial phase was completed. Utility files were copied to the

TWH_TOPDIR directory and the uninstallation program was created. The installation process is now configuring

databases.

If you cancel the installation now, the databases will be left in an inconsistent state. You can attempt to run the

uninstallation program to undo the changes made to the environment (such as remove files and variable values) and

to undo changes made in the databases.

Administrator Response: Click Yes to cancel installation. Use the uninstallation program to attempt to undo the

changes.


CDWIS0017E The installation cannot find DB2 UDB on this system. Cancel the installation and install DB2

UDB manually.

Explanation: You must install DB2 UDB on this machine before installing the Tivoli Data Warehouse.

Administrator Response: Click Cancel to exit the installation wizard and install DB2 UDB.

CDWIS0004E • CDWIS0017E


CDWIS0018E Version installed_version of DB2 UDB is installed. Tivoli Data Warehouse requires version

required_version or this version with a higher fix pack.

Explanation: Tivoli Data Warehouse requires a specific version of DB2 UDB to be installed on the system. You can

also install Tivoli Data Warehouse with this version of DB2 UDB if fix packs have been applied.

Administrator Response: Click Cancel to exit the installation wizard and install the required version of DB2 UDB.

CDWIS0019W No server component was detected in your DB2 UDB installation.

Explanation: Tivoli Data Warehouse requires specific components of DB2 UDB to be installed on the system.

Administrator Response: Click Cancel to exit the installation wizard and install the required DB2 UDB server

component.

CDWIS0020E A fatal error occurred while running the Perl script script_name. The installation cannot continue.

Explanation: This type of error means that the Tivoli Data Warehouse environment is damaged.

Administrator Response: Click OK to close the installation wizard.

Run FFDC and contact IBM Customer Support to help diagnose the problem.

CDWIS0021E A fatal error occurred while parsing a temporary output file file_name. The installation cannot

continue.

Explanation: This type of error means that the Tivoli Data Warehouse environment is damaged.

Administrator Response: Click OK to close the installation wizard.


CDWIS0022E The variable_name value variable_value is not valid. The name cannot be longer than 8 characters

and must be uppercase. It must start with a letter, but can contain a combination of letters and

numbers.

Explanation: The name must follow the guidelines specified in the message.

Administrator Response: Provide a valid value.

CDWIS0023E The variable_name value variable_value is not valid. The name cannot be longer than 16 characters

and must be uppercase. It must start with a letter, but can contain a combination of letters, numbers,

and underscores.

Explanation: The name must follow the guidelines specified in the message.

Administrator Response: Provide a valid value.

CDWIS0025E A central data warehouse is already configured or installed on DB2 UDB for z/OS and OS/390.

Only one central data warehouse is allowed on a DB2 UDB for z/OS and OS/390 database in each

Tivoli Data Warehouse deployment.

Explanation: Tivoli Data Warehouse allows only one central data warehouse on DB2 UDB for z/OS and OS/390. If

more central data warehouses are necessary, then create them on a DB2 UDB database.

Administrator Response: Choose the DB2 UDB database type to have more than one central data warehouse.

CDWIS0026E The program cannot open port port on remote host host.

Explanation: The program attempted to open the specified port on the specified host and failed.

Administrator Response: Verify that the host name and port number are correct.



CDWIS0027E The host name host_name is not fully qualified. Specify a fully qualified host name.

Explanation: A fully qualified host name is necessary to avoid ambiguities which could arise when machines with

similar names exist on different network domains.

Administrator Response: Provide the fully qualified name of the host.

CDWIS0028E A data mart database is already configured or installed on this location of DB2 UDB for z/OS and

OS/390. Only one data mart is allowed on the same location of a DB2 UDB for z/OS and OS/390

database.

Explanation: Tivoli Data Warehouse allows only one data mart database on a single location of a DB2 UDB for

z/OS and OS/390 database. If more data marts are necessary, then create them on a DB2 UDB database or on a

different location of the DB2 UDB for z/OS and OS/390 database.

Administrator Response: Choose the DB2 UDB database type or another location of the DB2 UDB for z/OS and

OS/390 database to have more than one central data warehouse.

CDWIS0029E The disk partition where the directory directory is located has insufficient disk space to complete

the installation. The partition requires an additional bytes_needed bytes.

Explanation: To install the warehouse pack, the installation wizard requires additional space. There was not enough

disk space to proceed.

Administrator Response: Free up the required amount of space on the specified partition and retry the installation.

CDWIS0031E The value specified for the field_name field is too long to fit into the Tivoli Data Warehouse

database. Provide a shorter value.

Explanation: Information gathered from the installation wizard panels is stored in a Tivoli Data Warehouse

database. The database columns are limited in length, so to avoid truncation the values must not exceed the limit.

Administrator Response: Specify a shorter value for the field.

CDWIS0032W Tivoli Data Warehouse supports up to four data marts in each deployment. By adding this data

mart, your deployment will exceed the number of supported data marts.

Explanation: Tivoli Data Warehouse verification teams have not tested more than four data marts in a deployment.

There are no known reasons why more data marts will not function properly, but these configurations are not

supported.

Administrator Response: Be aware that more than four data marts in a deployment are not supported. However,

there are no known reasons why more data marts will not function properly. Continue if you still want to add this

data mart.

CDWIS0033W Tivoli Data Warehouse supports up to four central data warehouses in each deployment. By

adding this central data warehouse, your deployment will exceed the number of supported central

data warehouses.

Explanation: Tivoli Data Warehouse verification teams have not tested more than four central data warehouses in a

deployment. There are no known reasons why more central data warehouses will not function properly, but these

configurations are not supported.

Administrator Response: Be aware that more than four central data warehouses in a deployment are not supported.

However, there are no known reasons why more central data warehouses will not function properly. Continue if you

still want to add this central data warehouse.

CDWIS0034E In order to perform this operation, you must have administration privileges.

Explanation: You must have administration privileges to install and uninstall Tivoli Data Warehouse.

Administrator Response: Log out and log back in as a user ID with administration privileges.



CDWIS0035E No Crystal Enterprise server information is available in the Tivoli Data Warehouse Registry. The

Tivoli Data Warehouse installation might be corrupted.

Explanation: In order to install or migrate reports, a Crystal Enterprise server must be recognized by the Tivoli Data

Warehouse installation process as being installed and registered in the environment. No registration information can

be found, so no report operations can be performed. The Crystal Enterprise server is required to install Tivoli Data

Warehouse and since no information is now available, the Tivoli Data Warehouse environment might be corrupted.


CDWIS0036E The warehouse pack configuration failed and left Tivoli Data Warehouse in an inconsistent state.

Run the command line utility that configures the warehouse pack (configWEP) again to restore

Tivoli Data Warehouse to a consistent state.

Explanation: An inconsistent state is caused by some configuration changes taking effect, while others do not. If the

inconsistent state is a result of running the configWEP from the command line, run the command again to restore

Tivoli Data Warehouse to a consistent state or to generate a message that details manual recovery steps.

Administrator Response: Run the configWEP command line utility again. See Installing and Configuring Tivoli Data

Warehouse for details about this command. Complete any manual recovery steps that are necessary. If the error

persists, run FFDC and contact IBM Customer Support for assistance.

CDWIS0041E An error occurred during installation or uninstallation of Tivoli Data Warehouse.

Explanation: This is a general message placeholder.








CDWIS0044E Tivoli Data Warehouse remote agent is already installed on this machine.

Explanation: If Tivoli Data Warehouse remote agent is installed on the machine it is not allowed to install another

remote agent or control server, as it will corrupt the environment.

Administrator Response: Cancel installation. Installation cannot continue if a remote agent is installed on the

machine.

CDWIS0045E The Tivoli Data Warehouse control database is unavailable. Make sure that the DB2 instance on

the control server host is running properly.

Explanation: The installation wizard cannot access the Tivoli Data Warehouse control database. The DB2 instance on

the control server machine is not running properly or the databases on the control server are corrupted.

Administrator Response: Make sure that the DB2 instance on the control server is running properly and that Tivoli

Data Warehouse environment is not corrupted.

CDWIS0046W If you cancel the installation now, the databases will be left in an inconsistent state. You can

attempt to reinstall the warehouse pack later. Do you want to cancel the installation?

Explanation: You tried to cancel an installation after the initial phase was completed. Utility files were copied to the

TWH_TOPDIR directory and the uninstallation program was created. The installation process is now configuring the

databases.

CDWIS0035E • CDWIS0046W


If you cancel the installation now, the databases will be left in an inconsistent state. You can attempt to reinstall this

warehouse pack later.

If this warehouse pack is a prerequisite for any packs or if it is a base version for any subsequent patches, then the

installation of the subsequent packs and patches will fail.

Administrator Response: Click Yes to cancel installation of this warehouse pack.


CDWIS0047W If you cancel the installation now, this and all following components will not be installed. You

can attempt to add these component later. Do you want to cancel the installation?

Explanation: You tried to cancel an installation of additional Tivoli Warehouse components. If you cancel the

installation now, the current and all subsequent components will not be installed. The database was modified, but it

will not affect the Tivoli Data Warehouse functionality. You can attempt to add these components later.

Administrator Response: Click Yes to cancel installation. Run the installation again to add components.


CDWIS0048W The listed warehouse packs were not tested to be used with Tivoli Data Warehouse 1.2. The

upgrade will continue.

Explanation: There is a possibility that the warehouse pack will corrupt the Tivoli Data Warehouse working

environment. The Tivoli Data Warehouse team has tested significant number of warehouse packs and marked them

as certified. However, there are many warehouse packs that were not tested and therefore Tivoli Data Warehouse

team cannot guarantee their functionality.

Administrator Response: Continue the upgrade if you acknowledge the fact that the listed warehouse packs were

not tested in Tivoli Data Warehouse Version 1.2. Contact IBM Customer Support and provide the warehouse pack

name and version for more assistance.

CDWIS0049E The listed warehouse packs do not work for Tivoli Data Warehouse Version 1.2. The upgrade

cannot continue.

Explanation: Tivoli Data Warehouse team has tested a significant number of warehouse packs and marked them as

certified. There are some warehouse packs that were recognized as not valid and they cannot be used in the Tivoli

Data Warehouse 1.2 environment. Such warehouse packs need to be removed or patched to a valid level before

upgrading.

Administrator Response: Stop the upgrade of Tivoli Data Warehouse. You must upgrade the warehouse packs to a

valid patch level, then attempt to upgrade Tivoli Data Warehouse again. Contact IBM Customer Support and provide

the warehouse pack name and version for more assistance.

CDWIS0050E Installation of Crystal Publisher has failed.

Explanation: Crystal Publisher installation has failed. The Tivoli Data Warehouse environment might be corrupted.


CDWIT0001E The required input properties file could not be found.

Explanation: The properties file expected by the Import Resource Bundle tool might not have been properly created

or was incorrectly specified when passed to this program.

Administrator Response: Review the Tivoli Data Warehouse installation logs for earlier errors concerning the

installation.

CDWIT0002E An error occurred while loading the input properties file.

Explanation: The specified properties file could not be loaded for use by the program. The file expected by the

Import Resource Bundle tool might not have been properly created.

CDWIS0047W • CDWIT0002E


Administrator Response: Review the Tivoli Data Warehouse installation logs for earlier errors concerning the

program installation. Try the installation again.

CDWIT0003E An error occurred while connecting to the database. A database connection could not be obtained.

Explanation: The program cannot connect to the database.

Administrator Response: Refer to the database name and the database error in the Tivoli Data Warehouse

installation logs.

CDWIT0008E The specified property is required and was not found in the properties file.

Explanation: The program cannot continue.

Administrator Response: Refer to the property name in the Tivoli Data Warehouse installation logs to determine

which property is missing. Verify that the property was properly specified during the program installation.

CDWIT0009E The installation of the resource bundle failed.

Explanation: A database error occurred while performing a database update. The resource bundle key was not

updated in the database. The database might not be up to date.

Administrator Response: Review the Tivoli Data Warehouse installation logs for additional error messages

indicating that other keys and resource bundles have failed.

CDWIT0010E The installation of the resource bundle failed.

Explanation: A database error occurred while inserting or updating the database with the specified resource bundle

key. The database might not be up to date.

Administrator Response: Review the Tivoli Data Warehouse installation logs for additional error messages

indicating other keys and resource bundles have failed.

CDWIT0011E The resource bundle to install could not be found.

Explanation: The program could not find the resource bundle it was trying to install.

Administrator Response: Refer to the resource bundle name indicated in the Tivoli Data Warehouse installation logs

to determine which resource bundle was not found.

CDWIT0012E The specified resource bundle failed to install because of previous errors.

Explanation: Previous errors caused the resource bundle installation to fail.

Administrator Response: Refer to the resource bundle name indicated in the Tivoli Data Warehouse installation logs

to determine which resource bundle failed. Refer to previous error messages for specific details about other keys that

failed or other problems that were encountered during the installation of this resource bundle.

CDWIT0016E The program failed to load the specified required property.


Administrator Response: Refer to the property name in the Tivoli Data Warehouse installation logs. Verify that the

property was properly specified during the installation.

CDWIT0017E An error was received while importing the resource bundles for the specified class.

Explanation: The installation failed.

Administrator Response: Refer to earlier messages for specific bundles that might have failed. Refer to the resource

bundle name and class name in the Tivoli Data Warehouse installation logs. Install the failed resource bundles again

or reinstall the entire program, if necessary.

CDWIT0003E • CDWIT0017E


CDWIT0018E An error occurred while loading the specified resource bundle.

Explanation: The resource bundle could not be loaded.

Administrator Response: Refer to the appended resource bundle name that could not be loaded. Verify that the

resource bundle exists and that it is in the correct format.

CDWIT0019E The program cannot import the resource bundles because of previous errors.

Explanation: One or more errors caused the Import Resource Bundles program to return a FAILURE return code.

Administrator Response: Refer to previous messages for errors. Continue to run the program until it completes

successfully.

CDWIT0021W An error was received while attempting to close the database INSERT statement.

Explanation: Errors are logged in the installation logs.

Administrator Response: Refer to the error message in the Tivoli Data Warehouse installation logs. The program

will attempt to continue. Review the logs to determine if other failures occurred. If no other failures occurred, the

program completes without failure.

CDWIT0022W An error was received while attempting to close the database UPDATE statement.





CDWIT0023W An error was received while attempting to close the database connection.





CDWIW0001E The configuration file file_name is not valid. Enter the name of the file again.

Explanation: The file name was left blank or the file does not exist. Enter the name and location of the

twh_install_props.cfg file.

Administrator Response: Enter the name of the correct file.

CDWIW0002E The content of the configuration file file_name is not valid. Verify the contents of the file and

enter the name of the file again.

Explanation: Warehouse pack development teams must provide valid configuration files to ensure installation. Refer

to Installing and Configuring Tivoli Data Warehouse for details about the format of a configuration file.

Administrator Response: Verify that the configuration file contains valid information if you created it. If the

configuration file does not contain valid information and was provided by a warehouse pack development team,

contact IBM Customer Support and provide the warehouse pack name, version, and configuration file.

CDWIW0003E Enter a value in the User ID field.

Explanation: User ID information is required to continue.

Administrator Response: Enter the user ID of the database administrator.

CDWIT0018E • CDWIW0003E


CDWIW0004E Enter a value in the Password field.

Explanation: Password information is required to continue.

Administrator Response: Enter the password of the database administrator.

CDWIW0005E Enter a value in the Data Source Name field.

Explanation: Data source name information is required to continue.

Administrator Response: Enter the name of the data source.

CDWIW0006E Enter a value in the Remote Host Name field.

Explanation: Remote host information is required to continue. The remote host is the name of the machine where

you want to create a client/server connection.

Administrator Response: Enter the name of the remote host.

CDWIW0007E Enter a value in the Remote Port Number field.

Explanation: Remote port information is required to continue. The remote port is the port number of the machine

where you want to create a client/server connection. The value must be a positive integer of 1 - 65535.

Administrator Response: Enter the remote port number.

CDWIW0008E Enter a value in the Remote Database Name field.

Explanation: Remote database name information is required to continue. The remote database name will be used to

create a client/server connection on the specified host.

Administrator Response: Enter the name of the remote database.

CDWIW0009E Enter a value in the Hour field.

Explanation: The hour must be an integer between 0 and 23.

Administrator Response: Enter the hour.

CDWIW0010E The Hour field contains an entry ’hour_value’ that is not valid. The hour must be an integer

between 0 and 23.

Explanation: The hour value sets the time to run the ETL. It must be an integer between 0 and 23.

Administrator Response: Enter a valid hour.

CDWIW0011E Enter a value in the Minute field.

Explanation: The minute must be an integer between 0 and 59.

Administrator Response: Enter the minute.

CDWIW0012E The Minute field contains an entry ’minute_value’ that is not valid. The minute must be an integer

between 0 and 59.

Explanation: The minute value sets the time to run the ETL. It must be an integer between 0 and 59.

Administrator Response: Enter a valid minute.

CDWIW0004E • CDWIW0012E


CDWIW0013E The following error occurred while copying files: error. Correct the error and then click Back to

return to the previous panel and click Next to retry the copy operation.

Explanation: The source or destination is not set up correctly or there is limited space in the temporary directory.

Administrator Response: Check the following items: source, destination media, and the space in the temporary

directory.

CDWIW0014E Tivoli Common Logging Directory is a required field.

Explanation: Tivoli Data Warehouse logs messages and trace files in subdirectories of this directory. By default, the

Tivoli common logging directory is located at /usr/ibm/tivoli/common on UNIX systems and

%ProgramFiles%\ibm\tivoli\common on Windows systems.

Administrator Response: Enter the directory where you want Tivoli products to store their logs.

CDWIW0015E The program cannot open port port on remote host host.

Explanation: The program attempted to open the specified port on the specified host and failed.

Administrator Response: Verify that the host name and port number are correct.

CDWIW0016E The ODBC data source source_name already exists at the host agent site, but has never been

registered with Tivoli Data Warehouse. This ODBC data source uses driver which is not supported

by IBM Data Warehouse Manager, so it cannot use it again. Change the ODBC data source name on

the panel or remove the existing ODBC data source name and start the warehouse pack installation

again.

Explanation: The ODBC data source name exists at the agent site, but it was never used in a warehouse pack

installation. The ODBC data source name uses driver which is not supported by IBM Data Warehouse Manager, so it

cannot use it again.

Administrator Response: Provide another name for the ODBC data source or remove the existing ODBC data

source name and restart warehouse pack installation.

CDWIW0017E Tivoli Data Warehouse, Version 1.2 is not installed on this computer and is a prerequisite.

Explanation: You cannot install a warehouse pack on this system until you upgrade to or install Tivoli Data

Warehouse, Version 1.2 on this system.

Administrator Response: Cancel the current warehouse pack installation and install Tivoli Data Warehouse, Version

1.2. Then try installing the warehouse pack again.

CDWIW0019E Directory Name is a required field. Enter the name of the directory where data files reside.

Explanation: The directory name is necessary to create the data source name. Use the existing absolute directory

name that points to the data file. The absolute path must exist on the selected host.

Administrator Response: Enter the name of directory where data files reside.

CDWIW0020E The Tivoli Data Warehouse Registry returned information about the central data warehouse, data

mart databases, or warehouse agents that is not correct.

Explanation: The Tivoli Data Warehouse Registry is not available or its content might be damaged. The Registry

contains information about the Tivoli Data Warehouse environment and is necessary for warehouse pack installations.

Administrator Response: Cancel the current installation and make sure that the database that contains the Tivoli

Data Warehouse Registry is available. This metadata database is named the control database (TWH_MD). If it is

available and the error still occurs, run FFDC and contact IBM Customer Support to help diagnose the problem.



CDWIW0022E The component component is not completely configured.

Explanation: In order to proceed with the installation, all components must be completely configured.

Administrator Response: Select the incomplete component and click Edit to configure it.

CDWIW0023E The ODBC data source source_name already exists for the current warehouse pack.

Explanation: The ODBC data source name cannot be used again.

Administrator Response: Provide another name for the ODBC data source.

CDWIW0024E The tag file supplied by the warehouse pack does not contain a data source name. The

warehouse pack installation cannot continue.

Explanation: This is an internal error. The tag file supplied by the warehouse pack does not contain a data source

name. The warehouse pack development team must supply the correct tag file before shipping the warehouse pack.

This problem occurs because the installation cannot retrieve the source name from the tag file. The tag file is a

machine file and should not be edited in any text editor.

Administrator Response: Contact support for the warehouse pack you are installing or contact IBM Customer

Support for additional assistance. Provide the content of the warehouse pack directory and all Tivoli Data Warehouse

log files.

CDWIW0025E The warehouse pack wep_name cannot be removed because it is required by the warehouse pack

wep_name.

Explanation: Some warehouse packs require other warehouse packs to be installed prior to their installation. These

requirements are specified in each warehouse pack’s configuration file.

Administrator Response: To remove a warehouse pack that is required by other warehouse packs, you must remove

those packs first.

CDWIW0026E The ODBC data source source_name already exists at the host agent site. Provide values that match

stored values for this ODBC data source to use this name again.

Explanation: The ODBC data source already exists at the agent site and has been registered with Tivoli Data

Warehouse or was used during this installation. However, not all the values provided match the stored values, so this

ODBC data source cannot be used again.

Administrator Response: Provide another name for the ODBC data source or verify that all the values you provide

match stored values if you want to use existing and registered ODBC data source names again.

CDWIW0027W The following ODBC data sources have already been used by Tivoli Data Warehouse:

source_names. The ODBC data sources will be used again, but because they might be used by other

warehouse packs you cannot edit the parameters.

Explanation: The listed ODBC data source names are default values for the currently configured warehouse pack,

but ODBC data sources with the same name have already been registered with Tivoli Data Warehouse. The registered

data source will be used again but you will not be able to edit any parameters.

Administrator Response: Continue with the installation and use the configured ODBC data sources or remove

entries from the table and create new data sources.

CDWIW0028W To complete the warehouse pack configuration, manually run the initialization step step_name as

well as any additional steps documented in the warehouse pack implementation guide. The ETL,

while scheduled based on the options selected, will not run until these steps have been performed.

Explanation: Some warehouse packs require an initialization process to be run manually before starting.

Administrator Response: Refer to the warehouse pack implementation guide for information about running

initialization processes.

CDWIW0022E • CDWIW0028W


CDWIW0029W The agent site host was changed from host to host. Click Reset and Continue to change the agent

site host and to remove all ODBC data sources that are configured for the current installation of the

warehouse pack. Click Do Not Reset to use the original agent site host.

Explanation: All ODBC data sources are currently configured for use on the original agent site host with this

warehouse pack configuration. When the warehouse agent site host is changed for currently installed warehouse

packs, the ODBC data source information will be reset. New ODBC data sources need to be configured for use on the

newly selected warehouse agent site host.

Administrator Response: Click Reset and Continue if you want to reset the ODBC data source list. You need to

create another ODBC data source list if you want to proceed with the warehouse pack configuration. Click Do Not

Reset if you want to change your warehouse agent host name back to the original name.

CDWIW0034E The client/server connection name is too long for DB2 UDB or DB2 UDB for z/OS and OS/390

databases.

Explanation: DB2 UDB and DB2 UDB for z/OS and OS/390 databases do not allow client/server connection names

to be longer than 8 characters.

Administrator Response: Specify a client/server connection name that is no longer than 8 characters.

CDWIW0035E No central data warehouses and data mart databases have been created on DB2 UDB. You cannot

install this warehouse pack.

Explanation: Warehouse packs that were created for Tivoli Enterprise Data Warehouse, Version 1.1, only work with

central data warehouses and data mart databases created on DB2 UDB. A central data warehouse (TWH_CDW) and a

mart (TWH_MART) database must be created on DB2 UDB.

Administrator Response: Cancel the installation or choose another warehouse pack to install. To install the current

warehouse pack, create the appropriate central data warehouses and data mart databases on DB2 UDB and try

installing the warehouse pack again.

CDWIW0036E The warehouse pack wep_name with product code product_code and version version is already

selected for installation or has already been installed on the system.

Explanation: The warehouse pack is already selected or is listed in the installed warehouse packs table. A

warehouse pack cannot be listed more than once in the table.

Administrator Response: Choose another warehouse pack to install.

CDWIW0041E The client/server connection connection_name already exists for the current type of database.

Specify another name.

Explanation: The client/server connection name must be unique for each type of database. The specified name was

already used and a new connection cannot be created.

Administrator Response: Choose another name for the client/server connection.

CDWIW0042E Connection Name is a required field. Select a client/server connection name or click New to

create a new connection name.

Explanation: The client/server connection name is necessary to create the data source name.

Administrator Response: Select a client/server connection name or click New to create a new connection name.

CDWIW0043E The base version of the warehouse pack must be installed before you can install a patch. The

warehouse pack wep_name, version wep_version is a patch.

Explanation: A patch cannot be installed unless the base version of the warehouse pack has already been installed.

When the base version of a warehouse pack is installed on a system (not patched), the last period-separated number

in the version equals zero.

Administrator Response: Install the base version of the warehouse pack and then install the patch.

CDWIW0029W • CDWIW0043E


CDWIW0044E The warehouse pack wep_name, version wep_version is an upgrade for a currently installed

warehouse pack. The upgrade cannot be installed because it is not a base version.

Explanation: When upgrading a warehouse pack that is already installed on the system, you must upgrade to a

base version of the warehouse pack. The last period-separated number of a base version equals zero.

Administrator Response: Use a base version of the upgrade package to upgrade the warehouse pack.

CDWIW0045E The warehouse pack wep_name, version wep_version is an upgrade for a currently installed

warehouse pack. The version number must be higher than the installed version number

installed_wep_version.

Explanation: When a warehouse pack is an upgrade to a warehouse pack that is already installed on the system, its

version number must be higher than the version number of the installed warehouse pack.

Administrator Response: Verify that you are using the correct upgrade package to upgrade the warehouse pack.

CDWIW0046E The warehouse pack wep_name, version wep_version, is a patch and requires Tivoli Data

Warehouse, Version new_core_version. However, it must require the same version of Tivoli Data

Warehouse, installed_core_version, as the installed warehouse pack it is patching.

Explanation: The warehouse pack patch requires Tivoli Enterprise Data Warehouse, Version 1.1, but you are

patching a warehouse pack that requires Tivoli Data Warehouse, Version 1.2. When a warehouse pack is a patch to a

warehouse pack that is already installed on the system, the required Tivoli Data Warehouse versions must be the

same.

Administrator Response: Verify that you are using the correct warehouse pack during the patch.

CDWIW0047E The version number of the patch you are installing, warehouse pack wep_name,

versionwep_version, must be higher than the installed warehouse pack version number

installed_wep_version.

Explanation: When a warehouse pack is a patch to a warehouse pack that is already installed on the system, the last

of its period-separated numbers must be higher than that of the installed version, but the rest of the numbers must

be the same.


CDWIW0048E The warehouse pack wep_name, version wep_version, requires Tivoli Data Warehouse, version

new_core_version. The required version number must be lower than 1.2.0.0.

Explanation: The current warehouse pack patch requires a lower version of Tivoli Data Warehouse than 1.2.0.0.


CDWIW0049E The warehouse pack wep_name, version wep_version, requires Tivoli Data Warehouse, version

new_core_version. The version must be higher than or equal to 1.2.0.0.

Explanation: The current warehouse pack patch requires a version of Tivoli Data Warehouse that is higher than or

equal to 1.2.0.0.


CDWIW0050E The warehouse pack role new_role specified in warehouse pack wep_name, version wep_version

must be the same as the role installed_role installed with the current warehouse pack.

Explanation: The warehouse pack role defines the type of ETL processing that occurs for the warehouse pack. The

current warehouse pack patch must have the same role as the installed warehouse pack. The role cannot change

during the patch. This error might be caused by an error in the configuration file.

Administrator Response: Verify that you are using the correct warehouse pack during the patch. Verify that the

configuration file contains valid information if you created it. If the configuration file was provided by a warehouse

pack development team, contact IBM Customer Support and provide the warehouse pack name and version and the

name of the configuration file.



CDWIW0051E A value must be specified for the ETL_TAG_INCLUDED key in the configuration file file_name.

Verify the contents of the file and enter the name of the file again.

Explanation: Warehouse pack development teams must provide valid configuration files to ensure proper

installation.


configuration file was provided by a warehouse pack development team, contact IBM Customer Support and provide

the warehouse pack name and version and the name of the configuration file.

CDWIW0052E A value must be specified for the CDW_DB_TYPE key in the configuration file file_name. Verify

the contents of the file and enter the name of the file again.


installation.




CDWIW0053E A value must be specified for the MART_DB_TYPE key in the configuration file file_name. Verify

the contents of the file and enter the name of the file again.


installation.




CDWIW0054E No central data warehouses were found in the Tivoli Data Warehouse deployment that are

compatible with the database type specified by the current warehouse pack. The installation of the

warehouse pack cannot continue.

Explanation: Warehouse pack development teams specify which database types are compatible with each warehouse

pack. A compatible database type must be present in the Tivoli Data Warehouse deployment to install the warehouse

pack. This error usually occurs if the warehouse pack only supports central data warehouses on DB2 UDB, but no

DB2 UDB databases are present.

Administrator Response: Create a central data warehouse on the required database type.

CDWIW0055E No data mart databases were found in the Tivoli Data Warehouse deployment that are

compatible with the database type specified by the current warehouse pack. The installation of the

warehouse pack cannot continue.

Explanation: Warehouse pack development teams specify which database types are compatible with each warehouse

pack. A compatible database type must be present in the Tivoli Data Warehouse deployment to install the warehouse

pack. This error usually occurs if the warehouse pack only supports data mart databases on DB2 UDB, but no DB2

UDB databases are present.

Administrator Response: Create a data mart on the required database type.

CDWIW0056E The configuration file for the warehouse pack contains a value that is not valid for the version_key

key. The value version_value cannot be interpreted as a version number.

Explanation: The warehouse pack provides a number of keys whose values indicate version. The version must be in

the form of N.N.N or N.N.N.N, where N is an integer.






CDWIW0057E The configuration file of the current warehouse pack contains a combination of values that is not

valid for DWC_INIT_STEP_NAME, SCHEDULABLE_ETL1_STEP_NAME, and

SCHEDULABLE_ETL2_STEP_NAME for a wep_role warehouse pack role.

Explanation: The warehouse pack requires a specific combination for scheduling key values depending on the

warehouse pack role. Here are possible combinations:

If you have a warehouse pack with a role of ETL1, the value for DWC_INIT_STEP_NAME is optional, the value for

SCHEDULABLE_ETL1_STEP_NAME is required, and the value for SCHEDULABLE_ETL2_STEP_NAME must be

NULL.

If you have a warehouse pack with a role of ETL2, the value for DWC_INIT_STEP_NAME is optional, the value for

SCHEDULABLE_ETL1_STEP_NAME must be NULL, and the value for SCHEDULABLE_ETL2_STEP_NAME is

required.

If you have a warehouse pack with a role of E1E2, the value for DWC_INIT_STEP_NAME is optional, the value for

SCHEDULABLE_ETL1_STEP_NAME is required, and the value for SCHEDULABLE_ETL2_STEP_NAME is required.

If you have a warehouse pack with a role of MCDW, the value for DWC_INIT_STEP_NAME must be NULL, the

value for SCHEDULABLE_ETL1_STEP_NAME must be NULL, and the value for

SCHEDULABLE_ETL2_STEP_NAME must be NULL.




CDWIW0058E The ODBC data source source_name already exists at the host agent site. Provide values that match

stored values for this ODBC data source to use this name again.

Explanation: The ODBC data source already exists at the agent site and has been registered with Tivoli Data

Warehouse or was used during this installation or installations of warehouse packs for previous versions of Tivoli

Data Warehouse. However, not all the values provided match the stored values, so this ODBC data source cannot be

used again.

Administrator Response: Provide another name for the ODBC data source or verify that all the values you provide

match stored values if you want to use existing and registered ODBC data source names again.

CDWIW0059E The tag file file_name was not supplied by the warehouse pack. The warehouse pack installation

cannot continue.

Explanation: The warehouse pack that is being installed does not have a tag file. The warehouse pack development

team must supply the correct tag file before shipping the warehouse pack. This problem occurs because the

installation cannot retrieve the source name from the tag file. The tag file is a machine file and should not be edited

in any text editor.

Administrator Response: Contact support for the warehouse pack you are installing or contact IBM Customer

Support for additional assistance. Provide the content of the warehouse pack directory and all Tivoli Data Warehouse

log files.

CDWIW0060E The configuration file file_name for the current warehouse pack contains a value that is not valid

for key_name key. The installation cannot continue.

Explanation: Warehouse pack development teams must provide a valid twh_install_props.cfg file to ensure

installation. Refer to Enabling an Application for Tivoli Data Warehouse for details about the format of the configuration

file.


configuration file does not contain valid information and was provided by a warehouse pack development team,




CDWIW0061W The following ODBC data sources have already been created on the specified Tivoli Data

Warehouse remote agent host: source_names. The ODBC data sources could be used again, but

specified user ID and password must match those from ODBC DS.

Explanation: The listed ODBC data source names are default values for the currently configured warehouse pack,

but ODBC data sources with the same name have already been created on specified remote agent host. They have

never been registered with Tivoli Data Warehouse. These ODBC data sources could be used again if the correct user

ID and password are provided.

Administrator Response: Continue with the installation and use the configured ODBC data sources and specify

valid user ID and password or remove entries from the table and create new data sources.

CDWIW0062E An error occurred during installation of the Tivoli Data Warehouse warehouse pack.

Explanation: This is a general message placeholder. This message will be used only when there will be a need for a

message, but no new messages could be created in the source repository.


CDWIW0063E An error occurred during installation of Tivoli Data Warehouse warehouse pack.




CDWIW0064E An error occurred during installation of Tivoli Data Warehouse warehouse pack.




CDWIW0065E The currently selected warehouse pack requires Tivoli Data Warehouse wep_core_version for its

functionality. The only Tivoli Data Warehouse versions supported in this release must be more than

or equal to minimum_core_version and less than maximum_core_version.

Explanation: The warehouse pack was created with a version of Tivoli Data Warehouse that is not compatible with

the one you have in your environment or the warehouse pack configuration file contains information that is not

valid. Refer to Enabling an Application for Tivoli Data Warehouse for details about the format of the configuration file.

Administrator Response: Verify the information you created in the configuration file contains valid information. If

the configuration file does not contain valid information and was provided by a warehouse pack development team,


CDWIW0066W The warehouse pack wep_name, version wep_version with PRODUCT code wep_ava was not tested

with Tivoli Data Warehouse version 1.2 and therefore is not supported.

Explanation: There is a possibility that this warehouse pack will corrupt the Tivoli Data Warehouse working

environment because it has not been tested.

Administrator Response: Be aware that this warehouse pack is not supported for Tivoli Data Warehouse version

1.2. Contact IBM Customer Support and provide the warehouse pack name and version for more assistance.

CDWIW0067E The warehouse pack wep_name, version wep_version with PRODUCT code wep_ava is not

supported by Tivoli Data Warehouse Version 1.2.

Explanation: This warehouse pack has failed the certification process, and therefore it cannot be used in Tivoli Data

Warehouse 1.2 environment. It should be removed or patched to a valid level before running the upgrade installation.

Administrator Response: Cancel the installation of this warehouse pack or go back and install only verified

warehouse packs. Obtain the valid level of this warehouse pack and install it later. Contact IBM Customer Support

and provide the warehouse pack name and version for more assistance.

CDWIW0061W • CDWIW0067E


CDWIW0068E Server Name is a required field. A valid server name from a previously chosen agent site must be

specified .

Explanation: The server name is missing. The server name is necessary to create the data source name.

Administrator Response: Specify a valid server name from a previously chosen agent site.

CDWRT0004E The twh_react.pl program cannot append to the log message file file_name. The error is error.

Explanation: An attempt to open the log message file in append mode failed. Either the file name is not valid or the

file and directory permissions do not permit this operation to succeed.


CDWRT0005E The twh_react.pl program cannot read the common logging properties file file_name. The error is

error.

Explanation: An attempt to open the common logging properties file in read mode failed. Either the file name is not

valid or the file and directory permissions do not permit this operation to succeed.


CDWRT0006E The tivoli_common_dir entry was not found in the common logging properties file file_name.

Explanation: The tivoli_common_dir entry in the common logging properties file defines the location of the Tivoli

common logging directory.

Administrator Response: Check the contents of the common logging properties file. If the entry is not there, install

Tivoli Data Warehouse again.

CDWRT0007W An entry entry that is not valid for the log message file name was found in the react logging

properties file file_name. The program is setting the entry to the default value react_message_log.log.


CDWRT0009W An entry entry that is not valid for the level was found in the react logging properties file

file_name. The program is setting the entry to the default value INFO.


CDWRT0010W An entry entry that is not valid for the trace message file name was found in the react logging

properties file file_name. The program is setting the entry to the default value react_trace_log.log.


CDWRT0014E The twh_react.pl program cannot append to the trace message file file_name. The error is error.

Explanation: An attempt to open the trace message file in append mode failed. Either the file name is not valid or

the file and directory permissions do not permit this operation to succeed.


CDWRT0015E The twh_react.pl program cannot read the react logging properties file file_name. The error is error.

Explanation: An attempt to open the react logging properties file in read mode failed. The file name is not valid or



CDWIW0068E • CDWRT0015E


CDWRT0021E An option was specified that is not valid in the twh_react.pl program.



are specified. If the program was called as part of an installation, contact IBM Customer Support and specify the

installation options that were selected.

CDWRT0031E The DBNAME value was not specified in the twh_react.pl program.

Explanation: The program requires that the database name of the control database be specified using the -d

parameter. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the DBNAME value

using the -d parameter. If the program was called as part of an installation, contact IBM Customer Support and

specify the installation options that were selected.

CDWRT0032E The DBUSER value was not specified in the twh_react.pl program.

Explanation: The program requires that the user for the control database be specified using the -u parameter. The


Administrator Response: If the program ran from the command line, run it again, providing the DBUSER value

using the -u parameter. If the program was called as part of an installation, contact IBM Customer Support and


CDWRT0033E The DBPASS value was not specified in the twh_react.pl program.

Explanation: The program requires that the password for the control database be specified using the -p parameter.

The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the DBPASS value

using the -p parameter. If the program was called as part of an installation, contact IBM Customer Support and


CDWRT0034E The AGENTSITE value was not specified in the twh_react.pl program.

Explanation: The program requires that the agent site be specified using the -a parameter. The program cannot

continue.

Administrator Response: If the program ran from the command line, run it again, providing the AGENTSITE value

using the -a parameter. If the program was called as part of an installation, contact IBM Customer Support and


CDWRT0035E The MODULE value was not specified in the twh_react.pl program.

Explanation: The program requires that the Perl module be specified using the -m parameter. The program cannot

continue.

Administrator Response: If the program ran from the command line, run it again, providing the MODULE value

using the -m parameter. If the program was called as part of an installation, contact IBM Customer Support and


CDWRT0040E The twh_react.pl program failed to run the setmodule method on the react object.


The function is function.

The error is error.

The module is module.

The module values are module_values.



CDWRT0021E • CDWRT0040E


CDWRT0041E The twh_react.pl program failed to run the setConnectionInfo method on the react object. The

return code is return_code.


The error is error.

The database name is database_name.

The user is user.



CDWRT0042E The twh_react.pl program failed to run the prepare method on the react object.



The error is error.

The top directory is directory_name.

The temporary directory is directory_name.

The trace file is file_name.



CDWRT0043E The twh_react.pl program failed during remote agent processing for agent site agent_site.



The error is error.

The module is module.

The arguments are arguments.



CDWRT0062E The react_agent_launcher.pl program ended abnormally and returned return_code.

Explanation: The react_agent_launcher.pl program ended with an error. The information returned in the message

provides specific information about the problem.

Administrator Response: Review the message logs in the Tivoli common logging directory.

CDWRT0091E The twh_react.pl program ended with an error at date_time.

Explanation: An error occurred at the specified time. The error information is contained in the message logs.


CDWRT0098E Usage: perl twh_react.pl -d twh_md -u user -p password -a agentsite -m module -v module_values.

Explanation: All parameters are required except module values. Module values may or may not be set depending

on the requirements of the specified module.


CDWRT0099E The environment variable TWH_TOPDIR is not set. Install Tivoli Data Warehouse, Version 1.2

before running this program.

Explanation: The environment variable TWH_TOPDIR is set when you install Tivoli Data Warehouse. It is possible

that you did not restart your system after installing Tivoli Data Warehouse.

Administrator Response: Ensure that the system was restarted after the installation of Tivoli Data Warehouse,

Version 1.2. Review the message logs in the Tivoli common logging directory.



CDWRT0101E A system error occurred. error_message.

Explanation: Refer to the text of the error message.



CDWRT0104E The database name is not set for the CmdLineUtil.pm program.

Explanation: A program has invoked the setConnectionInfo method on a CmdLineUtil object with a zero-length

string as the first parameter, which is the value of the database name.




CDWRT0105E The database password is not set for the CmdLineUtil.pm program for database database_name and

user database_user.


string as the second parameter, which is the value of the database user.




CDWRT0106E The database user is not set for the CmdLineUtil.pm program for database database_name.


string as the third parameter, which is the value of the database password.




CDWRT0107E The temporary directory is not set for the CmdLineUtil.pm program.

Explanation: A program has invoked the prepare method on a CmdLineUtil object with a zero-length string as the

second parameter, which is the value of the temporary directory.


CDWRT0108E The Tivoli Data Warehouse top directory is not set for the CmdLineUtil.pm program.

Explanation: A program has invoked the prepare method on a CmdLineUtil object with a zero-length string as the

first parameter, which is the value of the Tivoli Data Warehouse top directory.


CDWRT0110E The react_agent_launcher.pl program failed to create a react object.

Explanation: A program has invoked the new method on a React object but the object was not created.


CDWRT0111E The react_agent_launcher.pl program failed to store database connection information. The return

code is return_code. The output is output. The error is error.

Explanation: The program failed to store database connection information (database name, user or password) using

the setConnectionInfo method on a React object.




CDWRT0112E The react_agent_launcher.pl program failed to store temporary directory settings. The return code

is return_code. The output is output. The error is error.

Explanation: The program failed to store the name of the temporary directory using the prepare method on a React

object.


CDWRT0113E The react_agent_launcher.pl program failed to complete the run_agent method. The return code is

return_code. The output is output. The error is error.

Explanation: The program failed to complete the run_agent method on a React object.


CDWRT0114E The database name is not set for the React.pm program.

Explanation: A program has invoked the setConnectionInfo method on a React object with a zero-length string as

the first parameter, which is the value of the database name.




CDWRT0115E The database password is not set for the React.pm program for database database_name and user

database_user.


the second parameter, which is the value of the database user.




CDWRT0116E The database user is not set for the React.pm program for database database_name.


the third parameter, which is the value of the database password.




CDWRT0120E The CmdLineUtil.pm program cannot open the command file file_name for writing. The error is

error.

Explanation: An attempt to open the command file in write mode failed. This file is used to store DB2 commands

for execution by the DB2 Command Line Processor. The file name is not valid or the file and directory permissions


Administrator Response: Make sure the file name is valid and the file and directory permissions are correct. Review

the trace and message logs in the Tivoli common logging directory.

CDWRT0121E The CmdLineUtil.pm program cannot open the log file file_name for reading. The error is error.

Explanation: An attempt to open the log file in read mode failed. This file is used to store the output from the

execsql2 program. The file name is not valid or the file and directory permissions do not permit this operation to

succeed.





CDWRT0123E The CmdLineUtil.pm program cannot open the temporary file file_name for writing. The error is

error.

Explanation: An attempt to open the temporary file in write mode failed. This file is used to store the output from

the execsql2 program. The file name is not valid or the file and directory permissions do not permit this operation to

succeed.



CDWRT0124E The DB2 password is not set.

Explanation: The DB2 password is not set on the current CmdLineUtil object. The program cannot continue. The

DB2 password should be set using the setConnectionInfo method.


CDWRT0125E The DB2 user is not set.

Explanation: The DB2 user is not set on the current CmdLineUtil object. The program cannot continue. The DB2

user should be set using the setConnectionInfo method.


CDWRT0130E The Copy.pm program cannot change directory to the Tivoli Data Warehouse top directory

directory_name. The error is error.

Explanation: An attempt to change directory to the Tivoli Data Warehouse top directory failed. The directory name

is not valid or the directory permissions do not permit this operation to succeed.

Administrator Response: Make sure the directory name is valid and the directory permissions are correct. Review


CDWRT0131E The Copy.pm program cannot make a directory under the Tivoli Data Warehouse top directory


Explanation: An attempt to create a directory under the Tivoli Data Warehouse top directory failed. The directory

name is not valid or the directory permissions do not permit this operation to succeed.



CDWRT0132E The Copy.pm program cannot recursively remove a directory under the Tivoli Data Warehouse

top directory directory_name. The error is error.

Explanation: An attempt to recursively remove a directory under the Tivoli Data Warehouse top directory failed.

The directory name is not valid or the directory permissions do not permit this operation to succeed.



CDWRT0140E The function function is not valid. Allowed values are add, delete, get or listconn.

Explanation: The DBConnection.pm program was invoked with a setting for function that is not supported. The

allowed values are: add, delete, get or listconn.

Administrator Response: If the program was called as part of an installation, contact IBM Customer Support and




CDWRT0141E The arguments arguments are not valid. Allowed values are ETL1, ETL2, BEFORE, AFTER or

blank.

Explanation: The DBConnection.pm program was invoked with a setting for arguments that is not supported. The

allowed values are ETL1, ETL2, BEFORE, AFTER or blank.



CDWRT0142E The install flag is install_flag is not valid. Allowed values are Y or N.

Explanation: The DBConnection.pm program was invoked with a setting for the install flag that is not supported.

The allowed values are Y or N.



CDWRT0150E The Delete.pm program cannot change directory to the Tivoli Data Warehouse top directory


Explanation: An attempt to change directory to a directory under the Tivoli Data Warehouse top directory failed.




CDWRT0152E The Delete.pm program cannot recursively remove the directory directory_name under the Tivoli

Data Warehouse top directory. The error is error.

Explanation: An attempt to recursively remove a directory under the Tivoli Data Warehouse top directory failed.




CDWRT0201E The React.pm program cannot append to the control trace file file_name. The error is error.

Explanation: An attempt to open the control trace file for appending failed. This file is used for the react trace

messages log file at the control server. The file name is not valid or the file and directory permissions do not permit

this operation to succeed.



CDWRT0202E The React.pm program cannot write to the agent return message file file_name. The error is error.

Explanation: An attempt to open the agent return message file for writing failed. This file exists at the control server

and is used to hold the return message from the remote agent site. The file name is not valid or the file and directory




CDWRT0203E The React.pm program cannot append to the agent trace message file file_name. The error is error.

Explanation: An attempt to open the agent trace message file for appending failed. This file exists at the control

server and is used to hold the trace message from the remote agent site. The file name is not valid or the file and

directory permissions do not permit this operation to succeed.





CDWRT0206E The React.pm program failed to retrieve the module and arguments from twg.copy_data. The error

is error.

Explanation: The twg.copy_data table holds the module and arguments of the react module that is to be executed at

the remote agent site. An attempt to retrieve the module and arguments failed.


CDWRT0207E The React.pm program failed to load the module module. The error is error.

Explanation: The program was unable to create the module.


CDWRT0208E The module module was not found in tools/lib/React or apps/lib/React under the Tivoli Data

Warehouse top directory.

Explanation: The React.pm program could not find the module in the specified directories.


CDWRT0209E The step Data Warehouse Center step is not in Development, Test, or Production status. The status

is status.

Explanation: The only permitted values for the status of a Data Warehouse Center step are Development, Test, or

Production.

Administrator Response: Reset the status of the step using the Data Warehouse Center. Review the trace and

message logs in the Tivoli common logging directory.

CDWRT0210E The remote warehouse agent failed to record the status of the copy. The agent site is agent_site.

The module is module. The arguments are arguments. The agent error is error. The server error is

server_error.

Explanation: The remote warehouse agent failed to record the status of the copy. The TWG.COPY_DATA does not

contain a success/failure row. This row should have been inserted by the react program running at the remote agent

system.

Administrator Response: Check the trace information in the react_agent_launcher.trc and react_agent.trc files in the

cdw/temp/tools directory in the directory given by the value of TIVOLI_COMMON_DIR at the remote agent

system.

Try these suggested actions:

1. Verify that the control server and the remote agent system are able to ping each other.

2. Verify that the password for the agent site in the Data Warehouse Center is correct.

3. At the control server, run Warehouse Control Database Management to reset the Warehouse Services.

4. Verify that the control server has been rebooted since Tivoli Data Warehouse, Version 1.2 was installed.

5. Verify that the remote agent system has been rebooted since Tivoli Data Warehouse, Version 1.2 was installed.

6. At the control server, verify that the Warehouse Server and Warehouse Logger services are set up to logon as a

local user in the local Administrator’s group.

7. Review the trace and message logs in the Tivoli common logging directory at both the control server and the

remote agent system.

8. Contact IBM Customer Support and send the logs to them.

CDWRT0211E The remote DB2 warehouse agent failed to return a compressed tar file to the control server. The

agent error is error.

Explanation: The DB2 warehouse agent failed to return files from the remote agent site. The BIN_DATA column in

TWG.COPY_DATA does not contain a compressed tar file containing the returned files.


cdw/temp/tools directory in the directory given by the value of TIVOLI_COMMON_DIR at the remote agent site.






3. At the control server, run DB2 Warehouse Control Database Management to reset the Warehouse Services.


5. Verify that the remote agent site has been rebooted since Tivoli Data Warehouse, Version 1.2 was installed.




remote agent site.


CDWRT0212E The warehouse agent returned an error.

The local error is local_error.

The agent error is agent_error.

Explanation: The remote warehouse agent returned an error.


cdw/temp/tools directory in the directory given by the value of TIVOLI_COMMON_DIR at the remote agent

system.




3. At the control server, run Warehouse Control Database Management to reset the Warehouse Services.


5. Verify that the remote agent system has been rebooted since Tivoli Data Warehouse, Version 1.2 was installed.




remote agent system.


CDWRT0225E The run_agent method of the module module failed. The function is function. The error is error.

Explanation: The run_agent method of the specified module failed. The run_agent method of the module is the

method that is executed at the remote agent system.


CDWRT0226E The temporary directory is not set for the React.pm program.

Explanation: A program has invoked the prepare method on a React object with a zero-length string as the second

parameter, which is the value of the temporary directory.


CDWRT0227E The Tivoli Data Warehouse top directory is not set for the React.pm program.

Explanation: A program has invoked the prepare method on a React object with a zero-length string as the first

parameter, which is the value of the Tivoli Data Warehouse top directory.




CDWRT0228E The React.pm program cannot read the agent launcher trace file file_name. The error is error.

Explanation: An attempt to open the agent launcher trace file for reading failed. This file holds trace messages for

the program that launches the React.pm program at the remote agent system. The file name is not valid or the file




CDWRT0229E The React.pm program cannot read the agent trace file file_name. The error is error.

Explanation: An attempt to open the agent trace file for reading failed. This file holds trace messages for the

React.pm program at the remote agent system. The file name is not valid or the file and directory permissions do not




CDWRT0230E The agent site name is not set.

Explanation: The React.pm program cannot run the module because the agent site name is not set. The agent site

name is the first parameter to the run_control method in the React.pm program.


CDWRT0232E The agent site agent_site has not been created.

Explanation: The React.pm program cannot run the module because the agent site has not been created in the

control database.

Administrator Response: Verify that Tivoli Data Warehouse, Version 1.2 has been installed at the remote agent

system. Review the trace and message logs in the Tivoli common logging directory.

CDWRT0233E The host name for agent site agent_site has not been set.

Explanation: The React.pm program cannot run the module because the host name for the agent site is not set.


system. Reset the host name for the agent site using the Data Warehouse Center. Review the trace and message logs

in the Tivoli common logging directory.

CDWRT0234E The operating system for agent site agent_site is operating_system. Allowable values are Windows,

AIX or Solaris.

Explanation: The React.pm program cannot run the module because the operating system for the agent site is set to

a value that is not supported.


system. Reset the operating system for the agent site using the Data Warehouse Center. Review the trace and

message logs in the Tivoli common logging directory.

CDWRT0235E The user name for agent site agent_site has not been set.

Explanation: The React.pm program cannot run the module because the user for the agent site is not set.


system. Reset the user for the agent site using the Data Warehouse Center. Review the trace and message logs in the

Tivoli common logging directory.



CDWRT0236E The agent site password for agent site agent_site has not been set.

Explanation: The React.pm program cannot run the module because the password for the agent site is not set.


system. Reset the password for the agent site using the Data Warehouse Center. Review the trace and message logs in

the Tivoli common logging directory.

CDWRT0237E The React.pm program cannot read the agent return message file file_name. The error is error.

Explanation: An attempt to open the agent return message file for reading failed. This file exists at the control

server and is used to hold the return message from the remote agent site. The file name is not valid or the file and

directory permissions do not permit this operation to succeed.



CDWRT0240E The React.pm program cannot change directory to the temporary directory directory_name. The error

is error.

Explanation: An attempt to change directory to the temporary directory failed. The directory name is not valid or

the directory permissions do not permit this operation to succeed.



CDWRT0241E The React.pm program cannot read the export CSV file file. The error is error.

Explanation: An attempt to open the export CSV file for reading failed. This file holds the exported contents of the

columns of the twg.copy_data table that are not large objects. The file name is not valid or the file and directory




CDWRT0242E The React.pm program cannot write to the export CSV file file_name. The error is error.

Explanation: An attempt to open the export comma separated values (CSV) file for writing failed. This file holds the

exported contents of the columns of the twg.copy_data table that are not large objects. The file name is not valid or




CDWRT0243E The Copy.pm program cannot read the export CSV file file. The error is error.

Explanation: An attempt to open the export CSV file for reading failed. This file holds the exported contents of the

columns of the twg.copy_data table that are not large objects. The file name is not valid or the file and directory




CDWRT0244E The Copy.pm program cannot write to the export CSV file file_name. The error is error.

Explanation: An attempt to open the export comma separated values (CSV) file for writing failed. This file holds the

exported contents of the columns of the twg.copy_data table that are not large objects. The file name is not valid or






CDWRT0245E More than one directory or file whose name starts with v exists in the apps/AVA directory under

the Tivoli Warehouse top directory.

Explanation: Only one directory or file whose name starts with v is permitted in the apps/AVA directory under the

Tivoli Warehouse top directory. More than one directory or file was found.


CDWRT0246E The Delete.pm program cannot remove translate file file_name in the directory_name directory. The

error is error.

Explanation: An attempt to delete a translate file failed. Translate files hold application-specific translation

definitions. The file or directory permissions do not permit this operation to succeed.



CDWRT0247E The Execute.pm program cannot change directory to directory_name. The error is error.

Explanation: An attempt to change to a directory failed. The file or directory permissions do not permit this




CDWRU0004E The environment variable variable is not set.

Explanation: The specified environment variable is required and should be set for all valid Tivoli Data Warehouse

and DB2 installations. The user ID that is running the program might not have been set up to run with Tivoli Data

Warehouse or you have a corrupted Tivoli Data Warehouse installation.

Administrator Response: Verify that the environment is correct. Run the program again while logged on as the

same user ID that installed Tivoli Data Warehouse or reinstall Tivoli Data Warehouse.

CDWRU0005E The file file_name failed to open with the following error: error.

Explanation: The process might not have permission to write to the directory or there might not be space on the file

system.

Administrator Response: Verify that the process has permission to write to the directory and that there is space

available on the file system. If other operating system errors are indicated in the error text, consult your operating

system documentation for further diagnostic information.

CDWRU0006E The tivoli_common_dir entry was not found in the

$TWH_TOPDIR/logginglocation/log.properties file.

Explanation: The entry that defines the common logging location was not found in the logging properties file.

Administrator Response: Verify that there is an entry named tivoli_common_dir in the log.properties file. If this

entry is not found, review the installation logs to determine if the installation failed. Restore the file from a backup

copy or reinstall Tivoli Data Warehouse.

CDWRU0007W The entry entry is not valid that was found in the logging properties file file_name. The program

is setting the entry to the default value default_value.

Explanation: Depending on the entry in the error message, a null value was found for a file name or the tracing

level was not set to a valid value. Valid tracing level values are: INFO, DEBUG_MIN, DEBUG_MID, and

DEBUG_MAX.

Administrator Response: Update the properties file with valid entries or restore a valid copy of the file from a

backup. If a backup copy of the file is not available, reinstall Tivoli Data Warehouse to generate a valid file.

CDWRT0245E • CDWRU0007W


CDWRU0009E An argument argument that is not valid was passed to the program.

Explanation: The specified argument is not valid.

Administrator Response: Refer to the usage information and run the program again with correct parameters if you

developed the warehouse pack. If Tivoli provided the warehouse pack, an unexpected error occurred and you should

run FFDC and call IBM Customer Support.

CDWRU0011E The SELECT statement for the table table_name failed with the following database error: error.

Return code = return_code.

Explanation: A general database error was encountered while running an SQL statement.

Administrator Response: Take action based on the specific error message provided by the database vendor.

CDWRU0012E An incorrect number number of arguments was passed to the rollupMulti program. Two

arguments are required.

Explanation: Two arguments are required for the rollupMulti program.

Administrator Response: Refer to the usage information and run the program again with correct parameters if you

developed the warehouse pack. If the warehouse pack was provided by Tivoli, you should run FFDC and call IBM

Customer Support.

CDWRU0013E SELECT, an SQL query, returned no data from TWG.rollup_tables. No tables were selected for

aggregation.

Explanation: No row was found in TWG.rollup_tables for the product code and STEPNAME.

Administrator Response: Verify that the table exists in the TWH_MART database and that it is populated with rows

that correspond to the product code and STEPNAME. Refer to Enabling an Application for Tivoli Data Warehouse for

more information regarding the TWG.rollup_tables. If the warehouse pack was provided by Tivoli, you should run

FFDC and call IBM Customer Support.

CDWRU0020E The program failed to copy the generic template for rollup processing. The copy command is

command and the return message is the following: message. The return code is return_code.

Explanation: An attempt was made to copy rollupMulti.generic from the $TWH_TOPDIR/tools/bin directory to the

Tivoli common logging directory, but the copy failed. The process might not have permission to write to the directory

or there might not be space on the file system. The user ID that is running the program might not have been set up

to run with Tivoli Data Warehouse or the Tivoli Data Warehouse installation is corrupted.

Administrator Response: Verify that the environment is correct. Run the program again while logged on as the user

ID that installed Tivoli Data Warehouse or reinstall Tivoli Data Warehouse.

CDWRU0021E An error occurred when the SQL run-time program attempted to run the generated rollup script.

The return code is return_code and the the return message is message.

Explanation: After generating a generic SQL script for rollup processing, the rollupMulti program calls the SQL

run-time program to run the generated script. This process failed because of the reasons specified in the appended

message. Refer to Enabling an Application for Tivoli Data Warehouse for more information about rollup processing.

Administrator Response: If the appended message indicates that a general database error occurred, take the

corrective action indicated in the message. If the error occurred while manipulating data, refer to the log in the Tivoli

common logging directory that was generated by the SQL run-time program. Log information might indicate

database access problems, bad data values, or incorrectly coded data mart tables. Fix the problem and run the

program again.

CDWRU0009E • CDWRU0021E


CDWSQ0003E The RunMultiSQL.jar program ended with an error.


Administrator Response: Review the message logs in the Tivoli common logging directory for additional messages

indicating the specific error that caused the program to stop.

CDWSQ0004E The RunMultiSQL.jar program cannot connect to the control database.

Explanation: The control database (TWH_MD) contains information required to run the DB2 Data Warehouse Center

step. The error could be a failure in the connection attempt, not valid or missing connection information, or an

inability to locate or reach the database server where the control database resides.

Administrator Response: Review the message logs in the Tivoli common logging directory for more details about

the error.

CDWSQ0006E The following arguments are not valid and were passed to the RunMultiSQL.jar program:

arguments.


Administrator Response: Review the program usage statement and run the program again with valid options.

CDWSQ0007E The directory structure is not valid. There is no directory beginning with v in directory_name.

Explanation: The RunMultiSQL.jar program expects a directory that begins with v for each warehouse pack. This

directory is created automatically when the warehouse pack is installed. The directory might have been deleted or

the warehouse pack might not have been installed successfully.

Administrator Response: Uninstall the warehouse pack and then reinstall it.

CDWSQ0008E The directory structure is not valid. Only one directory beginning with v should exist in

directory_name.

Explanation: The RunMultiSQL.jar program cannot continue. The program expects exactly one directory beginning

with v for each warehouse pack. This directory is created automatically when the warehouse pack is installed. The

directory might have been deleted or the warehouse pack might not have been installed successfully.

Administrator Response: Uninstall the warehouse pack and then reinstall it.

CDWSQ0009E A trace logger could not be set up and the RunMultiSQL.jar program cannot run.

Explanation: The program traces a base set of messages as it runs to facilitate debugging. The software that is used

to trace messages could not start because of an environment configuration error.



CDWSQ0010E The RunMultiSQL.jar program was unable to start a process to run the SQL run-time program.

Explanation: The program calls the SQL run-time program to run the application SQL scripts defined in the DB2

Data Warehouse Center step. This might indicate a problem with the operating system or runtime environment.

Administrator Response: Review the message and trace files in the Tivoli common logging directory for details

about the exception.

CDWSQ0017E The program could not open or load the log.properties file or the RunMultiSQLlogging.properties

file.

Explanation: These files are necessary for configuring message and trace logging.



again.

CDWSQ0003E • CDWSQ0017E


CDWSQ0018E The RunMultiSQL.jar program encountered an error when trying to start message and trace

logging because of an error in the environment.

Explanation: The program encountered an error when it tried to initialize message and trace logging. This is caused

by an error in the environment.



again.

CDWSQ0019E The RunMultiSQL.jar program was called with an unsupported option unsupported_option.


Administrator Response: Review the program usage statement. Correct the options supplied to the program and

run it again.

CDWSQ0020E The RunMultiSQL.jar program was called with a -s option, indicating that a step name would be

supplied. However, no step name was supplied.

Explanation: The program detected a -s option, but no value was supplied with it. The program cannot continue.

Administrator Response: Fix the command line options supplied to the program and run it again. From the DB2

Data Warehouse Center GUI, update the parameters in the properties window for the step.

CDWSQ0022W The SQL statement issued to determine the following information did not return any data:

sql_output_information.

Explanation: The RunMultiSQL.jar program issues SQL statements to retrieve information stored in the database.

No data being returned might or might not result in a program error depending on whether this information is

required. This message is logged to assist in debugging the program should the program end in error.


CDWSQ0023E The SQL statement issued to determine the sql_output_information returned an error.

Explanation: The RunMultiSQL.jar program issues SQL statements to retrieve information stored in the database.

Administrator Response: Contact IBM Customer Support to review the message logs in the Tivoli common logging

directory to determine the details of the SQL failure.

CDWSQ0024E The SQL run-time program ended in error with return code return_code.

Explanation: The RunMultiSQL.jar program calls the SQL run-time program to process the application SQL script.

Administrator Response: Review the message logs in the Tivoli common logging directory as well as the log file

produced from the SQL run-time program to determine the cause of the error. Contact IBM Customer Support for

further assistance.

CDWSQ0026E The RunMultiSQL.jar program has determined that this DB2 Data Warehouse Center step will

process an extract script named script_name. However, there were no source databases defined for

this script.

Explanation: The program accesses tables in the control server database (TWH_MD) to determine the source

databases against which an extract script should be run. In this case, there were no database sources defined for this

step to be run against.

Administrator Response: An extract script is expected to have at least one source database. Run FFDC and contact

IBM Customer Support to help you resolve the problem.

CDWSQ0018E • CDWSQ0026E


CDWSQ0028E TWH_TOPDIR is not set. The value of TWH_TOPDIR must be set using the -D option when

calling the RunMultiSQL.jar program.

Explanation: TWH_TOPDIR is the top-level directory in which the Tivoli Data Warehouse files are installed.

Administrator Response: Run the program again specifying the TWH_TOPDIR value using the -D option. Make

sure that you rebooted the system after installing Tivoli Data Warehouse.

CDWSQ0029E A message logger could not be set up and the RunMultiSQL.jar program cannot run.

Explanation: The program logs a base set of messages as it runs to facilitate debugging. The software that is used to

log messages could not start. This is because of an environment configuration error.



CDWSQ0030E The RunMultiSQL.jar program could not write messages or trace information to the message and

trace logger and cannot continue.

Explanation: The program cannot write trace information and messages to logs. There might not be enough space

on the file system.

Administrator Response: Verify that the file system containing the Tivoli common logging directory is available and

has sufficient space.

CDWSQ0031E The directory structure is not valid. There is no application directory named directory_name.

Explanation: The RunMultiSQL.jar program expects an application directory by this name to exist on the agent site

specified in the DB2 Data Warehouse Center step properties. This directory is created automatically on the agent site

and is specified when the warehouse pack is installed or when the command that configures warehouse packs

(twh_configwep) was run to update the agent site. The directory might have been deleted or the warehouse pack

installation or configuration command (twh_configwep) might not have completed successfully.

Administrator Response: Uninstall the warehouse pack and then reinstall it or run the twh_configwep command

again.

CDWSQ0032E The step name must be 80 characters or less.

Explanation: The step name supplied with the -s argument was too long.

Administrator Response: Run the program again, specifying a step name value of 80 characters or less.

CDWSQ0033E A step name must begin with a product code followed by an underscore.

Explanation: The step name supplied with the -s argument did not match the required naming standards.

Administrator Response: Run the program again, specifying a step name value beginning with a product code

followed by an underscore.

CDWSQ0034E The RunMultiSQL.jar program was called without specifying the required -s option.

Explanation: The program did not detect a required option and cannot continue.

Administrator Response: Contact IBM Customer Support for assistance reviewing the program log and trace files in

the Tivoli common logging directory. From the DB2 Data Warehouse Center GUI, update the parameters in the

properties window for the step.

CDWSQ0035W The RunMultiSQL.jar program encountered a warning condition but is able to continue.

possible_warning_text

Explanation: A warning condition was detected, but the RunMultiSQL.jar program continued without an error.

Administrator Response: Review the message logs details to determine the warning.

CDWSQ0028E • CDWSQ0035W


CDWSQ0036E The RunMultiSQL.jar program encountered an error condition and is unable to continue. It is:

possible_error_text

Explanation: An error was detected, and the RunMultiSQL.jar program could not continue.

Administrator Response: Review the message logs for details. If necessary, run FFDC and contact IBM Customer

Support to help diagnose the problem.

CDWTD0003E The command that changes user IDs and passwords (twh_update_userinfo) stopped because of an

error.


Administrator Response: Review the command message logs in the Tivoli common logging directory for additional

messages indicating the specific error that caused the command to stop.

CDWTD0004E The command that changes user IDs and passwords (twh_update_userinfo) was unable to obtain

a message or trace logger and cannot write the command messages.

Explanation: The command cannot continue because it cannot write command messages.

Administrator Response: Verify that the file system that contains the Tivoli common logging directory is available

and has sufficient space.

CDWTD0006E The following arguments are not valid and were passed to the command that changes user IDs

and passwords (twh_update_userinfo): arguments.

Explanation: The command changes user IDs and passwords (twh_update_userinfo) cannot continue because

arguments that are not valid were passed to the command.

Administrator Response: Review the command usage statement and run the twh_update_userinfo command again

with valid arguments.

CDWTD0008E The command that changes user IDs and passwords (twh_update_userinfo) was called with an

unsupported option unsupported_argument.

Explanation: The command cannot continue because an unsupported argument was specified.

Administrator Response: Review the twh_update_userinfo command usage statement. Correct the options supplied

to the twh_update_userinfo command and run it again.

CDWTD0009E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -s

option indicating that a database server host name would be supplied. However, no database server

host name was supplied.

Explanation: The command cannot continue because a server host name was not supplied.

Administrator Response: Fix the command line options supplied to the twh_update_userinfo command and run it

again.

CDWTD0010E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -i

option indicating that a database instance name would be supplied. However, no database instance

name was supplied.

Explanation: The command cannot continue because a database instance name was not supplied.


again.

CDWSQ0036E • CDWTD0010E


CDWTD0011E The SQL statement issued to determine the sql_output_information returned an error.

Explanation: The command that changes user IDs and passwords (twh_update_userinfo) issues SQL statements to

retrieve information stored in the database.

Administrator Response: Contact IBM Customer Support to review the command message and trace logs in the

Tivoli common logging directory to determine the details of the SQL failure.

CDWTD0012E The twh_react.pl command ended in error with return code: return_code.

Explanation: The command that changes user IDs and passwords (twh_update_userinfo) calls the command to

update the connection control file on the remote agent site.


produced by the command to determine the cause of the error.

CDWTD0013E TWH_TOPDIR not set.

Explanation: The value of TWH_TOPDIR must be set using the -D option when calling the command that changes

user IDs and passwords (twh_update_userinfo).

Administrator Response: Run the twh_update_userinfo command again, specifying the TWH_TOPDIR command

using the -D option.

CDWTD0015E The twh_react.pl script cannot update the connection control file on the remote agent site

agent_site_name.

Explanation: The command that changes user IDs and passwords (twh_update_userinfo) calls the twh_react.pl

script to update the connection control file on the remote agent site. The twh_react.pl script returned an error. The

user information program will continue. However, processes that run on this remote agent site may experience

problems connecting to the control server.


produced by the twh_react.pl script to determine the cause of the error. Verify that the remote agent site is available

and that the DB2 remote agent service is running.

CDWTD0017E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -d

option indicating that a database name would be supplied. However, no database name was

supplied.

Explanation: The command cannot continue because a database name was not supplied.


again.

CDWTD0018E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -u

option indicating that a database user ID would be supplied. However, no database user ID was

supplied.

Explanation: The command cannot continue because a user ID was not supplied.

Administrator Response: Fix the command line options supplied to the command and run it again.

CDWTD0019E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -n

option indicating that a new database user ID would be supplied. However, no new database user

ID was supplied.

Explanation: The command cannot continue because a user ID was not supplied.


again.

CDWTD0011E • CDWTD0019E


CDWTD0020E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -p

option indicating that a new database password would be supplied. However, no new database

password was supplied.

Explanation: The command cannot continue because a password was not supplied.


again.

CDWTD0021E The command that changes user IDs and passwords (twh_update_userinfo) was called without

specifying -l, -s, or -c. One of these options is required.

Explanation: The command cannot continue because a required argument was not specified.


to the command and run it again.

CDWTD0022E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -l

option and also other options. However, no other options can be specified when using -l.

Explanation: The command cannot continue because no other options can be specified when you specify -l.




option. However, when using -s, both -i and -d must be specified.

Explanation: The command cannot continue because required arguments were not specified.



CDWTD0024E The command that changes user IDs and passwords (twh_update_userinfo) was called with both

-s and -c options. However, these options are mutually exclusive.

Explanation: The command cannot continue because -s and -c cannot be specified together.

Administrator Response: Review the command usage statement. Correct the options supplied to the command and

run it again.

CDWTD0025E The command that changes user IDs and passwords (twh_update_userinfo) was called with both

-u and -a options. However, these options are mutually exclusive.

Explanation: The command cannot continue because -u and -a cannot be specified together.




option. However, when using -s, either -u or -a must also be specified.




CDWTD0027E The command that changes user IDs and passwords (twh_update_userinfo) requires that -n or -p

be specified when not using -l. However, neither -n or -p were indicated.






CDWTD0028E The command that changes user IDs and passwords (twh_update_userinfo) was called with a -c

option. However, when using -c, only -n and -p are allowed.

Explanation: The command cannot continue because an argument that is not valid was specified.



CDWTD0029E The command that changes user IDs and passwords (twh_update_userinfo) cannot connect to the

control database (TWH_MD).

Explanation: The error might be a failure in the connection attempt, not valid or missing connection information, or


Administrator Response: Review the twh_update_userinfo message logs in the Tivoli common logging directory for

more details about the error.

CDWTD0031E The command that changes user IDs and passwords (twh_update_userinfo) cannot start a process

to run the twh_react.pl script.

Explanation: The command calls the twh_react.pl script to update the connection control file on the remote agent

site. This might indicate a problem with the operating system or runtime environment.

Administrator Response: Review the message and trace files to locate details of the exception.

CDWTD0033E A trace logger could not be set up and the command that changes user IDs and passwords

(twh_update_userinfo) cannot run because of an environment configuration error.

Explanation: The command traces a base set of messages as it runs to facilitate debugging. The software that is used



twh_update_userinfo command. Run the twh_update_userinfo command again.

CDWTD0034E A message logger could not be set up and the command that changes user IDs and passwords

(twh_update_userinfo) cannot run because of an environment configuration error.

Explanation: The twh_update_userinfo command logs a base set of messages as it runs to facilitate debugging. The

software that is used to trace messages could not start.


command. Run the command again.

CDWTD0039E The command that changes user IDs and passwords (twh_update_userinfo) cannot open or load

the log.properties file or the TWHDBAdminlogging.properties file.

Explanation: These files are necessary to configure message and trace logging.


command. Check the informational paths displayed by the command and verify that they are correct. Run the

command again.

CDWTD0040E The command that changes user IDs and passwords (twh_update_userinfo) encountered an error

when trying to start message and trace logging because of an environment configuration error.

Explanation: The command encountered an error when it tried to start message and trace logging. This is caused by

an error in the environment configuration.

Administrator Response: Correct the environment configuration, checking the class path and the command used to

start the command. Check the informational paths displayed by the command and verify that they are correct. Run

the command again.



CDWTD0041E The SQL statement issued to update the following information returned an error:

sql_output_information. Verify that the control server database is active and available.

Explanation: The command that changes user IDs and passwords (twh_update_userinfo) issues SQL statements to

update information stored in the database.

Administrator Response: Run FFDC and contact IBM Customer Support to help you resolve the problem and

determine the details of the SQL failure.

CDWTD0042E No available Data Warehouse Center sources or targets matching the specified values were found.

Source databases of warehouse packs created for Tivoli Enterprise Data Warehouse, Version 1.1

cannot be updated using this command.

Explanation: The command that changes user IDs and passwords (twh_update_userinfo) did not find any Data

Warehouse Center sources or targets that matched the specified input values. Data Warehouse Center sources for the

source databases of warehouse packs created for Tivoli Enterprise Data Warehouse, Version 1.1 cannot be updated

using this command.

Administrator Response: Use the -l flag to obtain a complete list of the database values of all available DB2 Data

Warehouse Center sources and targets. If the database user information that needs to be updated is the source

database of a warehouse pack created for Tivoli Enterprise Data Warehouse, Version 1.1, refer to the warehouse pack

documentation for instructions on setting the user ID and password values using the DB2 Data Warehouse Center.

Additionally, review the twh_update_userinfo message logs in the Tivoli common logging directory for additional

information.

CDWTD0043E The update of the control server user information was aborted.

Explanation: The command that changes user IDs and passwords (twh_update_userinfo) was unable to connect to

the control server database using the user ID or password values provided. Because the input values could not be

validated, the update request was aborted.

Administrator Response: Run the command after verifying that the control database is available and that the

specified user ID and password can be used to successfully connect to it.

CDWTD0045E The database server host name must be 80 characters or less.

Explanation: The database server host name supplied with the -s argument was too long.

Administrator Response: Run the command again, specifying a database server host name of 80 characters or less.

CDWTD0046E The database server instance name must be 8 characters or less.

Explanation: The database server instance name supplied with the -i argument was too long.

Administrator Response: Run the command again, specifying a database server instance name of 8 characters or

less.

CDWTD0047E The database name must be 254 characters or less.

Explanation: The database name supplied with the -d argument was too long.

Administrator Response: Run the command again, specifying a database name of 254 characters or less.

CDWTD0048E The database user ID must be 128 characters or less.

Explanation: The database user ID supplied with the -u argument was too long.

Administrator Response: Run the command again, specifying a database user ID of 128 characters or less.



CDWTD0049E The new database user ID must be 128 characters or less.

Explanation: The new database user ID supplied with the -n argument was too long.

Administrator Response: Run the command again, specifying a new database user ID of 128 characters or less.

CDWTD0050E The database password must be 14 characters or less.

Explanation: The database password supplied with the -p argument was too long.

Administrator Response: Run the command again, specifying a database password of 14 characters or less.

CDWTD0051W The command that changes user IDs and passwords (twh_update_userinfo) encountered a

warning condition but is able to continue. possible_warning_text


CDWTD0052E The command that changes user IDs and passwords (twh_update_userinfo) encountered an error

condition and is unable to continue. possible_error_text

Explanation: Review the message logs for details of the error condition.

Administrator Response: If necessary, run FFDC and contact IBM Customer Support to help diagnose the problem.

CDWTG0021E An argument that is not valid was supplied to the twh_dwc_agtste.pl program.

Explanation: The twh_dwc_agtste.pl program cannot continue. The program usage statement is logged in the

program’s message logs. There was an argument supplied to the twh_dwc_agtste.pl that was not valid.

Administrator Response: If the program ran from the command line, run it again, verifying that only valid

arguments are specified. If the program was called as part of an installation, run FFDC and contact IBM Customer

Support. If possible, specify the installation arguments that were selected.

CDWTG0022E An argument that is not valid was supplied to the twh_dwc_step_to_agtste.pl program.

Explanation: The program cannot continue. The program usage statement is logged in the program’s message logs.




CDWTG0023E An argument that is not valid was supplied to the twh_dwc_sched.pl program.





CDWTG0024E An argument that is not valid was supplied to the twh_dwc_srctgt.pl program.





CDWTG0025E An argument that is not valid was supplied to the twh_dwc_srctgt_to_agtste.pl program.





CDWTD0049E • CDWTG0025E


CDWTG0031E The AGENTSITE value was not supplied to the twh_dwc_agtste.pl program.

Explanation: The program requires that an agent site name be specified using the -a argument. The program cannot

continue.


using the -a argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0032E The OSTYPE value was not supplied to the twh_dwc_agtste.pl program.

Explanation: The program requires that the operating system type be specified using the -o argument. The program

cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the OSTYPE value

using the -o argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0033E The HOSTNAME value was not supplied to the twh_dwc_agtste.pl program.

Explanation: The program requires that the TCP/IP host name be specified using the -h argument. The program

cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the HOSTNAME value

using the -h argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0034E The USERID value was not supplied to the twh_dwc_agtste.pl program.

Explanation: The program requires that the user ID be specified using the -u argument. The program cannot

continue.

Administrator Response: If the program ran from the command line, run it again, providing the USERID value

using the -u argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0035E The STEPNAME value was not supplied to the twh_dwc_step_to_agtste.pl program.

Explanation: The program requires that the process step be specified using the -s argument. The program cannot

continue.

Administrator Response: If the program ran from the command line, run it again, providing the STEPNAME value

using the -s argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0036E The AGENTSITE value was not supplied to the twh_dwc_step_to_agtste.pl program.

Explanation: The program requires that an agent site value be specified using the -a argument. The program cannot

continue.




CDWTG0037E The STEPNAME value was not supplied to the twh_dwc_sched.pl program.

Explanation: The program requires that the process step be specified using the -s argument. The program cannot

continue.

Administrator Response: If the program ran from the command line, run it again, providing the STEPNAME value

using the -s argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0031E • CDWTG0037E


CDWTG0038E The DATETIME value was not supplied to the twh_dwc_sched.pl program.

Explanation: The program requires that a date and time be specified in the form ″yyyy-mm-dd-hh:mi:ss″ using the

-t argument. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the DATETIME value

using the -t argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0039E The PREFIX value was not supplied to the twh_dwc_srctgt.pl program.

Explanation: The program requires that a prefix be specified using the -p argument. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the PREFIX

information using the -p argument. If the program was called as part of an installation, run FFDC and contact IBM

Customer Support. If possible, specify the installation arguments that were selected.

CDWTG0040E The ODBC_SRC value was not supplied to the twh_dwc_srctgt.pl program.

Explanation: The program requires that the name of the ODBC data source be specified using the -o argument. The


Administrator Response: If the program ran from the command line, run it again, providing the ODBC_SRC value



CDWTG0041E The PREFIX value was not supplied to the twh_dwc_srctgt_to_agtste.pl program.

Explanation: The program requires that a prefix be specified using the -p argument. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the PREFIX value

using the -p argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0042E The ODBC_SRC value was not supplied to the twh_dwc_srctgt_to_agtste.pl program.

Explanation: The program requires that the name of the ODBC data source be specified using the -o argument. The


Administrator Response: If the program ran from the command line, run it again, providing the ODBC_SRC value



CDWTG0043E The AGENTSITE value was not supplied to the twh_dwc_srctgt_to_agtste.pl program.

Explanation: The program requires that an agent site value be specified using the -a argument. The program cannot

continue.




CDWTG0044E The HOSTNAME value was not supplied to the twh_dwc_srctgt.pl program.

Explanation: The program requires that a TCP/IP host name be specified using the -h argument. The program

cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the HOSTNAME value

using the -h argument. If the program was called as part of an installation, run FFDC and contact IBM Customer




CDWTG0045E The USERID value was not supplied to the twh_dwc_srctgt.pl program.

Explanation: The program requires that a user ID be specified using the -u argument. The program cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the USERID value

using the -u argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0051E The OSTYPE value must be supplied to the twh_dwc_agtste.pl program using the -t argument

and be an integer between 1 and 7..

Explanation: The program cannot continue because a value that is not valid was specified. The seven operating

system types are identified in a list. Specify the number of the operating system type.

Administrator Response: If the program ran from the command line, run it again, providing a valid OSTYPE value

between 1 and 7. If the program was called as part of an installation, run FFDC and contact IBM Customer Support.

If possible, specify the installation arguments that were selected.

CDWTG0052E The YEAR value of the DATETIME argument in the twh_dwc_sched.pl program must be a value

between 2000 and 2099.

Explanation: The program cannot continue because a value that is not valid was specified.

Administrator Response: If the program ran from the command line, run it again, providing a valid YEAR between

2000 and 2099. If the program was called as part of an installation, run FFDC and contact IBM Customer Support. If

possible, specify the installation arguments that were selected.

CDWTG0053E The MONTH value of the DATETIME argument in the twh_dwc_sched.pl program must be a

value between 01 and 12.


Administrator Response: If the program ran from the command line, run it again, providing a valid MONTH value

between 01 and 12. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0054E The DAY value of the DATETIME argument in the twh_dwc_sched.pl program must be a value

between 01 and 31.


Administrator Response: If the program ran from the command line, run it again, providing a valid DAY value



CDWTG0055E The DATETIME value is not valid in the twh_dwc_sched.pl program.


Administrator Response: If the program ran from the command line, run it again, providing a valid DATETIME

value. If the program was called as part of an installation, run FFDC and contact IBM Customer Support. If possible,

specify the installation arguments that were selected.

CDWTG0056E The HOUR portion of the DATETIME value in the twh_dwc_sched.pl program must be a value

between 00 and 23.


Administrator Response: If the program ran from the command line, run it again, providing a valid HOUR value

between 00 and 23 inclusively. If the program was called as part of an installation, run FFDC and contact IBM

Customer Support. If possible, specify the installation arguments that were selected.



CDWTG0057E The MIN portion of the DATETIME value in the twh_dwc_sched.pl program must be a value

between 00 and 59.


Administrator Response: If the program ran from the command line, run it again, providing a valid MIN value



CDWTG0058E The SEC portion of the DATETIME value in the twh_dwc_sched.pl program must be a value

between 00 and 59.


Administrator Response: If the program ran from the command line, run it again, providing a valid SEC value



CDWTG0060E The arguments -o and -d cannot both be supplied to the twh_dwc_sched.pl program.

Explanation: The program cannot continue because a combination of arguments was specified that is not valid.

Administrator Response: If the program ran from the command line, run it again, specifying either -o or -d, but not

both. If the program was called as part of an installation, run FFDC and contact IBM Customer Support. If possible,


CDWTG0061E Either -o or -d must be supplied to the twh_dwc_sched.pl program.

Explanation: The program cannot continue because a required value was not specified.

Administrator Response: If the program ran from the command line, run it again, specifying either -o or -d. If the

program was called as part of an installation, run FFDC and contact IBM Customer Support. If possible, specify the

installation arguments that were selected.

CDWTG0063E The arguments -s and -t cannot both be supplied to the twh_dwc_srctgt.pl program.


Administrator Response: If the program ran from the command line, run it again, specifying either -s or -t, but not



CDWTG0064E Either -s or -t must be supplied to the twh_dwc_srctgt.pl program.


Administrator Response: If the program ran from the command line, run it again, specifying either -s or -t. If the



CDWTG0065E The arguments -s and -t cannot both be supplied to the twh_dwc_srctgt_to_agtste.pl program.


Administrator Response: If the program ran from the command line, run it again, specifying either -s or -t, but not



CDWTG0066E Either -s or -t must be supplied to the twh_dwc_srctgt_to_agtste.pl program.


Administrator Response: If the program ran from the command line, run it again, specifying either -s or -t. If the





CDWTG0071E The TAGFILE value was not supplied to the twh_dwc_agtste.pl program.

Explanation: The program requires that the name of the tag file be specified using the -f argument. The program

cannot continue.

Administrator Response: If the program ran from the command line, run it again, providing the TAGFILE name

using the -f argument. If the program was called as part of an installation, run FFDC and contact IBM Customer


CDWTG0072E The TAGFILE value was not supplied to the twh_dwc_step_to_agtste.pl program.

Explanation: The program requires that the tag file be specified using the -f argument. The program cannot

continue.




CDWTG0073E The TAGFILE value was not supplied to the twh_dwc_sched.pl program.


continue.




CDWTG0074E The TAGFILE value was not supplied to the twh_dwc_srctgt.pl program.


continue.




CDWTG0075E The TAGFILE value was not supplied to the twh_dwc_srctgt_to_agtste.pl program.


continue.




CDWTG0081E The program is unable to open the specified tag file in the twh_dwc_agtste.pl program.

Explanation: The program cannot write to the specified tag file and cannot continue.

Administrator Response: If the program ran from the command line, run the program again, verifying that the

TAGFILE value specified with the -f argument is a file to which the process can write. If the program was called as

part of an installation, run FFDC and contact IBM Customer Support. If possible, specify the installation arguments

that were selected.

CDWTG0082E The program is unable to open the specified tag file in the twh_dwc_step_to_agtste.pl program.







that were selected.

CDWTG0083E The program is unable to open the specified tag file in the twh_dwc_sched.pl program.





that were selected.

CDWTG0084E The program is unable to open the specified tag file in the twh_dwc_srctgt.pl program.





that were selected.

CDWTG0085E The program is unable to open the specified tag file in the twh_dwc_srctgt_to_agtste.pl program.





that were selected.

CDWTG0091E The twh_dwc_agtste.pl program ended with an error.

Explanation: Other messages have already been logged that indicate the specific problem.


that indicate the specific error that caused the program to stop.

CDWTG0092E The twh_dwc_step_to_agtste.pl program ended with an error.




CDWTG0093E The twh_dwc_sched.pl program ended with an error.




CDWTG0094E The twh_dwc_srctgt.pl program ended with an error.




CDWTG0095E The twh_dwc_srctgt_to_agtste.pl program ended with an error.






CDWTG0200W The twh_dwc_agtste.pl program encountered a warning condition but is able to continue.

Explanation: There was a warning message found, but the twh_dwc_agtste.pl program continued without an error.

Administrator Response: Review the message logs for details of the warning condition.

CDWTG0201E The twh_dwc_agtste.pl program encountered an error condition and is unable to continue.

Explanation: An error occurred while running the twh_dwc_agtste.pl program. It was unable to continue

processing.

Administrator Response: Review the message logs for details of the error. If necessary, run FFDC and contact IBM

Customer Support to help diagnose the problem.

CDWTG0203W The twh_dwc_step_to_agtste.pl program encountered a warning condition but is able to continue.

Explanation: There was a warning message found, but the twh_dwc_step_to_agtste.pl program continued without

an error.


CDWTG0204E The twh_dwc_step_to_agtste.pl program encountered an error condition and is unable to continue.

Explanation: An error occurred while running the twh_dwc_step_to_agtste.pl program. It was unable to continue

processing.



CDWTG0205W The twh_dwc_sched.pl program encountered a warning condition but is able to continue.

Explanation: There was a warning message found, but the twh_dwc_sched.pl program continued without an error.


CDWTG0206E The twh_dwc_sched.pl program encountered an error condition and is unable to continue.

Explanation: An error occurred while running the twh_dwc_sched.pl program. It was unable to continue

processing.



CDWTG0207W The twh_dwc_srctgt.pl program encountered a warning condition but is able to continue.

Explanation: There was a warning message found, but the twh_dwc_srctgt.pl program continued without an error.


CDWTG0208E The twh_dwc_srctgt.pl program encountered an error condition and is unable to continue.

Explanation: An error occurred while running the twh_dwc_srctgt.pl program. It was unable to continue processing.

Administrator Response: Review the message logs for details of the error condition. If necessary, run FFDC and

contact IBM Customer Support to help diagnose the problem.

CDWTG0209W The twh_dwc_srctgt_to_agtste.pl program encountered a warning condition but is able to

continue.

Explanation: There was a warning message found, but the twh_dwc_srctgt_to_agtste.pl program continued without

an error.


CDWTG0200W • CDWTG0209W


CDWTG0210E The twh_dwc_srctgt_to_agtste.pl program encountered an error condition and is unable to

continue.

Explanation: An error occurred while running the twh_dwc_srctgt_to_agtste.pl program. It was unable to continue

processing.

Administrator Response: Review the message logs for details. If necessary, run FFDC and contact IBM Customer

Support to help diagnose the problem.

CDWTR0003E The command that changes the report server values (twh_update_rptsrv) stopped because of an

error.

Explanation: The report server values were not changed because of an error. Messages have already been logged

that indicate the specific problem.

Administrator Response: Review the command message logs in the Tivoli common logging directory for additional

messages indicating the specific error that caused the command to stop.

CDWTR0004E The command that changes the report server values (twh_update_rptsrv) was unable to obtain a

message or trace logger and cannot write the command messages.

Explanation: The command cannot continue because it cannot log trace or message information.

Administrator Response: Verify that the file system that contains the Tivoli common logging directory is available

and has sufficient space.

CDWTR0006E The following arguments are not valid and were passed to the command that changes the report

server values (twh_update_rptsrv): arguments.

Explanation: The command cannot continue because arguments that are not valid were specified.

Administrator Response: See Installing and Configuring Tivoli Data Warehouse to review the command usage

statement. Run the command again with valid arguments.

CDWTR0008E The command that changes the report server values (twh_update_rptsrv) was called with an

unsupported argument unsupported_argument.

Explanation: The command cannot continue because an argument that is not valid was specified.

Administrator Response: See Installing and Configuring Tivoli Data Warehouse to review the twh_update_rptsrv

command usage statement. Correct the arguments supplied to the command and run it again.

CDWTR0009E The command that changes the report server values (twh_update_rptsrv) was called with a -h

argument indicating that a report server host name would be supplied. However, no report server

host name was supplied.

Explanation: The command cannot continue because the host name was not supplied.

Administrator Response: See Installing and Configuring Tivoli Data Warehouse to fix the command line arguments

supplied to the command and run it again.

CDWTR0010E The command that changes the report server values (twh_update_rptsrv) was called with a -p

argument indicating that a report server password would be supplied. However, no report server

password was supplied.

Explanation: The command cannot continue because the password was not supplied.

Administrator Response: See Installing and Configuring Tivoli Data Warehouseto fix the command line arguments


CDWTG0210E • CDWTR0010E


CDWTR0011E The SQL statement issued to determine the output sql_output_information returned an error.

Explanation: The command that changes the report server values (twh_update_rptsrv) issues SQL statements to

retrieve information stored in the database.

Administrator Response: Review the twh_update_rptsrv message logs in the Tivoli common logging directory to

determine the details of the SQL failure. If necessary, run FFDC and contact IBM Customer Support to help diagnose

the problem.

CDWTR0012E TWH_TOPDIR was not set.

Explanation: The value of TWH_TOPDIR must be set using the -D argument when calling the command that

changes the report server values (twh_update_rptsrv).

Administrator Response: Run the command again, specifying the TWH_TOPDIR command using the -D argument.

CDWTR0013E The command that changes the report server values (twh_update_rptsrv) was called with a -n

argument indicating that a report server port number would be supplied. However, no report server

port number was supplied.

Explanation: The command cannot continue because the port number was not supplied.



CDWTR0014E The command that changes the report server values (twh_update_rptsrv) was called with a -u

argument indicating that a report server user ID would be supplied. However, no report server user

ID was supplied.

Explanation: The command cannot continue because the user ID was not supplied.



CDWTR0015E The command that changes the report server values (twh_update_rptsrv) was called without

specifying -l, -h, -u, or -p. One of these arguments is required.



statement. Correct the arguments supplied to the command and run it again.

CDWTR0016E The command that changes the report server values (twh_update_rptsrv) was called with a -l

argument as well as additional arguments. However, no other arguments can be specified when

using -l.




CDWTR0017E The command that changes the report server values (twh_update_rptsrv) cannot connect to the

control database.

Explanation: The error might be a failure in the connection attempt, not valid or missing connection information, or


Administrator Response: Review twh_update_rptsrv message logs in the Tivoli common logging directory for more

details about the error.

CDWTR0011E • CDWTR0017E


CDWTR0019E A trace logger could not be set up and the command that changes the report server values

(twh_update_rptsrv) cannot run because of an environment configuration error.

Explanation: The command traces a base set of messages as it runs to facilitate debugging. The software that is used




CDWTR0020E A message logger could not be set up and the command that changes the report server values

(twh_update_rptsrv) cannot run because of an environment configuration error.

Explanation: The command logs a base set of messages as it runs to facilitate debugging. The software that is used




CDWTR0025E The command that changes the report server values (twh_update_rptsrv) cannot open or load the

log.properties file or the TWHRptAdminlogging.properties file.

Explanation: These files are necessary to configure message and trace logging.



command again.

CDWTR0026E The command that changes the report server values (twh_update_rptsrv) encountered an error

when trying to start message and trace logging because of an environment configuration error.

Explanation: The command logs a base set of messages as it runs to facilitate debugging. The software that is used




command again.

CDWTR0027E The SQL statement issued to update the data updated_data returned an error.


update information stored in the database.



the problem.

CDWTR0028W The SQL statement issued to determine the select_data did not return any data.


retrieve information stored in the database. No data being returned might or might not result in a command error

depending on whether this information is required. This message is logged to assist in debugging the command if it

ends with an error.


CDWTR0029E The SQL statement issued to insert the inserted_data returned an error.


insert information stored in the database.


determine the details of the SQL failure.




CDWTR0030E The SQL statement issued to delete the deleted_data returned an error.


delete information stored in the database.



the problem.

CDWTR0031E The host name must be 80 characters or less.

Explanation: The report server host name supplied with the -h argument (twh_update_rptsrv) was too long.

Administrator Response: Run the command again, specifying a host name value of 80 characters or less.

CDWTR0032E The password must be 14 characters or less.

Explanation: The report server password supplied with the -p argument was too long.

Administrator Response: Run the command again, specifying a password value of 14 characters or less.

CDWTR0033E The user ID must be 128 characters or less.

Explanation: The report server user ID supplied with the -u argument was too long.

Administrator Response: Run the command again, specifying a user ID value of 128 characters or less.

CDWTR0035E The command that changes the report server values (twh_update_rptsrv) was called with a -F

argument but not a -h. However, the -F argument is only allowed when using -h.




CDWTR0036W The Tivoli Crystal Publisher command ended in error with return code return_code.

Explanation: The command, twh_update_rptsrv, calls the Tivoli Crystal Publisher command to update the report

server hostname.


produced from the Tivoli Crystal Publisher command to determine the cause of the error. Contact IBM Customer

Support for further assistance.

CDWTR0039W The command that changes the report server values (twh_update_rptsrv) encountered a warning

condition but is able to continue. possible_warning_text. Review the message logs for details of the

warning condition.


CDWTR0040E The command that changes the report server values (twh_update_rptsrv) encountered an error

condition and is unable to continue. possible_error_text

Explanation: The twh_update_rptsr command had trouble with the report server values. Review the message logs

for details of the error condition.

Administrator Response: If necessary, run FFDC and contact IBM Customer Support to help diagnose the problem.

CDWTR0041E The command that changes the report server values (twh_update_rptsrv) cannot be run as there is

no Crystal Enterprise server configured in this environment.




CDWTR0042E The host name must be a fully qualified host name.

Explanation: The report server host name supplied with the -h argument is not a fully qualified host name.

Administrator Response: Run the command again, specifying a fully qualified host name value.

CDWUW0001E The data returned from the Tivoli Data Warehouse Registry is not valid.

Explanation: The Tivoli Data Warehouse Registry is not accessible or its content might be damaged. The Registry


Administrator Response: Make sure that the control database (TWH_MD) is available. If this error occurs while the

database is available, run FFDC and contact IBM Customer Support to help you diagnose the problem.

CDWUW0005E An error occurred during uninstallation of Tivoli Data Warehouse warehouse pack.









CDWVW0001E The attribute parameter is not a recognized attribute for tag object objectType.

Explanation: An attribute was not recognized as valid for the tag file specified. This error occurs when parsing the

DB2 Data Warehouse Center tag file during warehouse pack validation. This parse error could denote either a change

to the internal structure of the tag file or a potential tag file corruption.

Programmer Response: This error needs developer attention. Please provide this error and associated tag file to

Tivoli Data Warehouse Support.

CDWVW0002E The tag file entry line appears to not be correct. There is no attribute associated with this tag.

Explanation: No attribute was found for the tag specified. This error occurs when parsing the DB2 Data Warehouse

Center tag file during warehouse pack validation. This parse error could denote either a change to the internal

structure of the tag file or a potential tag file corruption.

Programmer Response: This error needs developer attention. Please provide this error and the associated tag file to

IBM Customer Support to help diagnose the problem.

CDWVW0003E The DB2 Data Warehouse Center warehouse sourceOrTargetobject name objectName does not follow

the standard naming convention. The warehouse object should be named goodName<uppercased

PRODUCT code>_<data source>_type).

Explanation: The DB2 Data Warehouse Center warehouse target name does not comply with the business rules

standard of <uppercased PRODUCT code>_<data source name>_target.

Programmer Response: Rename this DB2 Data Warehouse Center warehouse target to comply with the Tivoli Data

Warehouse 1.2 business rules standard of <uppercased PRODUCT code>_<data source name>_<target or source>.

CDWTR0042E • CDWVW0003E


CDWVW0004E The DB2 Data Warehouse Center warehouse sourceOrTarget object name objectName does not

properly incorporate the ODBC data source name dataSourceName) which is embedded in this tag

file. To properly match the ODBC data source name, the DB2 Data Warehouse Center warehouse

sourceOrTarget object must be goodName.

Explanation: The DB2 Data Warehouse Center Warehouse source or target object name does not comply with the

Tivoli Data Warehouse 1.2 business rules standard. In particular, the data source name embedded in the tag file does

not match the middle section <data source> of your object name. This check is case sensitive.

Programmer Response: Correct the problem by either renaming the DB2 Data Warehouse Center Warehouse object

to use the entry in the Data source name in the Data Source tab in the Properties option for this object, or you can

change the Data source name to match the middle section of DB2 Data Warehouse Center Warehouse object name. In

either situation the data source name must match the middle section of this DB2 Data Warehouse Center Warehouse

source or target object.

CDWVW0005E The User Defined Program (UDP) objectName is using program for the shell command. This shell

command is not allowed in warehouse packs for Version 1.2. You must use twh_shell only.

Explanation: Tivoli Data Warehouse 1.2 has provided a standard shell tool which is required when building a UDP.

Shells which were valid in Tivoli Data Warehouse 1.1 such as bash, sh, ksh, etc. are no longer allowed.

Programmer Response: Alter your User Defined Program in the DB2 Data Warehouse Center to use twh_shell as

the Program Name under the Program tab of the Properties option on this object.

CDWVW0006E The database object objectName pointing to the database databaseName has a DBTYPE of

dbFamilyNumber (dbFamily) and a DBETYPE of dbTypeNumber(dbType). This DBTYPE is not allowed in

warehouse packs for Version 1.2. Please make certain all central data warehouse and mart database

objects have a DBTYPE of (validDBTYPE).

Explanation: An invalid database type was discovered for a Warehouse source or target database object in the DB2

Data Warehouse Center tag file.

Programmer Response: Delete this DB2 Data Warehouse Center Warehouse source or target object and recreate it

with the proper DB2 Data Warehouse Center Warehouse source or target type before exporting the tag file again. A

DB2 type is required for central data warehouse and mart data sources.

CDWVW0007E The database object objectName pointing to the database databaseName has a DBTYPE of

dbFamilyNumber (dbFamily) and a DBETYPE of dbTypeNumber (databaseType). This DBTYPE is not

allowed in warehouse packs for Version 1.2. Please make certain all source database objects have a

DBTYPE of (validDBTYPE).

Explanation: An invalid database type was discovered for a Tivoli Data Warehouse source or target database object

in the IBM DB2 Data Warehouse Center tag file.

Programmer Response: Delete this DB2 Data Warehouse Center Warehouse source or target object and recreate it

with the proper Warehouse source or target type before exporting the tag file again. A generic ODBC type is required

for data sources other than the central data warehouse and mart data sources.

CDWVW0008E A directory directoryName was detected which is not part of a standard Tivoli Data Warehouse

warehouse pack and is not allowed.

Explanation: The business rules standard for Tivoli Data Warehouse Version 1.2 gives a strict directory structure that

warehouse packs must follow based on the type of warehouse pack, a base installation, an upgrade, or a patch. The

ValidateWEP tool has determined that a directory exists that is not in the business rules standard.

Programmer Response: Remove this directory from your warehouse pack. If this directory is required for

warehouse pack functionality, place it in the misc/ directory.

CDWVW0004E • CDWVW0008E


CDWVW0009E The property name (propertyName) requested to be deleted is not recognized. This name is not

specified as a valid property.

Explanation: This is an internal error in the ValidateWEP tool. An attempt was made to remove a property which

did not exist in memory.

Programmer Response: Contact IBM Customer Support to help diagnose the problem.

CDWVW0010E No WEP_ROLE was provided. A WEP_ROLE entry in the configuration file,

twh_install_props.cfg, is needed in order to determine the rule set used for validation.

Explanation: The twh_install_props.cfg file located in the top directory of the warehouse pack does not contain the

entry, WEP_ROLE. This entry is a requirement for the warehouse pack because it provides information necessary to

determine the warehouse pack type.

Programmer Response: Add a line entry for the WEP_ROLE in the twh_install_props.cfg file which matches your

warehouse pack type.

CDWVW0011E The file matchedFile in directory directoryName’ is not part of a standard Tivoli Data Warehouse

warehouse pack and is not allowed.

Explanation: The business rules standard for Tivoli Data Warehouse Version 1.2 gives a strict file naming

requirement that warehouse packs must follow based on the type of warehouse pack, a base installation, an upgrade,

or a patch. The ValidateWEP tool has determined that a file name exists that is not in the business rules standard.

Programmer Response: Check the name of the file for accuracy. If the filename is accurate, remove this file from

your warehouse pack. If this file is required for warehouse pack functionality, place it in the misc/ directory.

CDWVW0012E The files in the directory dirName matching the filter filterName are not allowed.

Explanation: The business rules standard for Tivoli Data Warehouse Version 1.2 gives a strict file naming

requirement that warehouse packs must follow based on the type of warehouse pack, a base installation, an upgrade,

or a patch. The ValidateWEP tool has determined that a filename exists that does not follow the business rules

standard.

Programmer Response: Check the name of the file for accuracy. If the filename is accurate, remove this file from

your warehouse pack. If this file is required for warehouse pack functionality, place it in the misc/ directory.

CDWVW0013E An invalid tag line tagLine was found. Skipping to next line.

Explanation: This is an internal error in the ValidateWEP tool. An illegal entry was found in the tag file. This could

be caused by either a corrupted tag file or by scanning a tag file created by a more recent version of the DB2 Data

Warehouse Center than this version of the ValidateWEP tool.

Programmer Response: Try reexporting the tag file to replace the indicated tag file and run the ValidateWEP tool

again to rule out tag file corruption. If the error still occurs, contact IBM Customer Support for assistance.

CDWVW0014E There is an unrecognized properties entry (propertiesEntry) found in rulesFile. The right value was

not recognized.

Explanation: This is an internal error in the ValidateWEP tool. An entry was found in the rules file that attempted

to assign an value that is not valid to a property. This could be caused by a corrupted ValidateWEP jar file or is a

defect in the Rules file.

Programmer Response: Insure that the ValidateWEP jar file is at the beginning of the CLASS_PATH and attempt to

rerun. If the problem still occurs with the ValidateWEP tool at the begining of the CLASS_PATH, contact IBM

Customer Support for further assistance.



CDWVW0015E There is an unrecognized properties entry (propertiesEntry) found in rulesFile. The Left value not

recognized.

Explanation: This is an internal error in the ValidateWEP tool. An entry was found in the rules file that was not

recognized as a valid property. This could be caused by a corrupted ValidateWEP jar file or is a defect in the Rules

file.

Programmer Response: Insure that the ValidateWEP jar file is at the beginning of the CLASS_PATH and attempt to

run the ValidateWEP tool again. If the problem still occurs at the begining of the CLASS_PATH, with the

ValidateWEP tool, contact IBM Customer Support for further assistance.

CDWVW0016E There is an unrecognized propEntrypproperties line. The property value is missing. The line

follows: (line)

Explanation: The property entry in the warehouse pack properties file contains no values. Empty properties are not

allowed.

Programmer Response: Add one or more valid values to the property as needed and appropriate for this

warehouse pack type.

CDWVW0017E The minimum required length (numberValue) for currentProperty found in rulesFile exceeds the

maximum allowed length of (maximumRequiredLength)


to set the minimum required length of a property higher than the maximum allowed length for that same property.

No values given in the configuration file can meet these two criteria.

Programmer Response: Make certain that the ValidateWEP jar is at the beginning of the CLASS_PATH and attempt

to run the ValidateWEP tool again. If the problem still occurs with the ValidateWEP tool at the beginning of the

CLASS_PATH, contact IBM Customer Support for further assistance.

CDWVW0018E No entry was provided. An entry entry in the configuration file is needed in order to determine

the ruleset used for validation.

Explanation: The ValidateWEP tool was unable to determine the type of warehouse pack, a base installation, an

upgrade, or a patch, without the indicated property entry.

Programmer Response: Be certain to add the property entry to the configuration file as indicated in the error

message.

CDWVW0019E The property propertyName was not found in the configuration file, but is a required entry.

Explanation: This property is required for this warehouse pack type, but it was not found in the warehouse pack’s

configuration file.

Programmer Response: Add the property to the warehouse pack’s configuration properties file with one or more

valid values as needed.

CDWVW0020E The property value propertyValue for property named propertyName must be all uppercase

characters.

Explanation: This property is case sensitive and the entry provided did not match the case required.

Programmer Response: Change the property value to all uppercase characters.

CDWVW0021E The property propertyName has a value badValue that appears to match an acceptable

valuegoodValue but it is in the wrong case. This property is case sensitive.


Programmer Response: Change the property value to match the acceptable value provided.



CDWVW0022E The property propertyName has a value badValue’ which does not match any of the required values

(goodValueList).

Explanation: The property value provided in the warehouse pack configuration file does not match any of the

allowed values for that property type.

Programmer Response: Change your property value to match one of the valid values provided.

CDWVW0023E The property value propertyName length is (propertyLength). The minimum length allowed for this

property is (minimumRequiredLength).

Explanation: The property value given in the warehouse pack configuration file is shorter than that allowed by the

business rules.

Programmer Response: Correct the property value to be the proper length in the configuration file.

CDWVW0024E The property value propertyName length is (propertyLength). The maximum length allowed for this

property is (maximumRequiredLength).

Explanation: The property value given in the warehouse pack configuration file is longer than that allowed by the

business rules.

Programmer Response: Correct the property value to be the proper length in the configuration file.

CDWVW0025E The property value propertyValue for the property named propertyName must be all lower case

characters.


Programmer Response: Change the property value to all lowercase characters.

CDWVW0026E There is a missing symbol and value for one of the property entries. The equal sign can not be

found. The line is as follows: (line)

Explanation: The property entry does not contain an equal (=) sign. The Business Rules standard indicates that a

property value must be followed by an equal sign which is then followed by a value.

Programmer Response: Fix the property entry by adding an equal sign and a value to assign to the property.

CDWVW0027E The step named ’scriptName’ does not begin with this warehouse pack’s PRODUCT code

’avaCode’. Please modify the step name to match the AVA_CODE entry in your configuration file.

Explanation: The 1.2 warehouse pack’s business rules require that steps begin with the PRODUCT code

(AVA_CODE) in all uppercase. Either this step does not begin with the PRODUCT code at all, or it does not match

the uppercase requirement.

Programmer Response: Modify the name of the step in the DB2 Data Warehouse Center to begin with the

uppercased PRODUCT code and reexport the tag file.

CDWVW0028E The step named ’scriptName’ does not have an associated script in the warehouse pack directory

named ’dirName’. Be sure the script is included in this directory and is named the same as the step.

Explanation: No script can be found in the etl/generic directory which matches the step name found in the tag file.

The script must be named the same as the DB2 Data Warehouse Center step. This comparison is case sensitive.

Programmer Response: Determine whether the DB2 Data Warehouse Center step is misnamed or if the script in the

etl/generic directory is misnamed. Each step in the tag must have a matching generic script name.

CDWVW0029E There are too many files (numMatches) matching the filter ’filterName’ in the directory ’dirName’.

Please limit the number of files to (’numFiles’) or less.

Explanation: You have exceeded the maximum number of files which match the file filter given. This rule is used to

impose a limit on the number of files allowable in a warehouse pack, such as the number of tag files.



Programmer Response: Reduce the number of files which match the file filter provided.

CDWVW0030E Not enough files (numberMatches) were found in the directory directoryName that matched the

filter filterName. The warehouse pack must have at least (numberFiles) files that match this filter.

Explanation: You have not matched the minimum number of files required that match the file filter provided.

Programmer Response: Either create or increase the number of files that match the file filter provided.

CDWVW0031E Unable to acquire the AVA_CODE from the properties file.

Explanation: The AVA_CODE property in the warehouse pack configuration file does not exist or cannot be found.

Programmer Response: Verify that the AVA_CODE entry exists and is correct in the warehouse pack configuration

file.

CDWVW0032E Unable to acquire the base directory from the WepDir object.

Explanation: This is an internal error in the ValidateWEP tool. An attempt was made to acquire the warehouse

pack’s base directory from the WepDir object. This directory entry is not populated. This could be caused by a

corrupted jar file or a defect in the ValidateWEP tool code.

Programmer Response: Please make certain that the ValidateWEP jar is at the beginning of the CLASS_PATH and

run the ValidateWEP tool again. If the problem still occurs, contact IBM Customer Support for further assistance.

CDWVW0033E Unable to build the ruleset. No configuration object was provided.

Explanation: This is an internal error in the ValidateWEP tool. An attempt was made to acquire the ConfigWep

object by the WepDir object. That object was not populated at the time. This could be caused by a corrupted jar file

or a defect in the code.



CDWVW0034E Unable to load the fileName tag file.

Explanation: The ValidateWEP tool attempted to load the tag file shown but was prohibited from doing so. Either a

permissions problem exists or the tag file is missing.

Programmer Response: Verify that the tag file exists and is named exactly as specified in the error message. If so,

verify that the tool has read access to the file.

CDWVW0035E Unable to load the rulesFile rules file.

Explanation: This is an internal error in the ValidateWEP tool. The tool was not able to locate the rules file. This

could be caused by a corrupted ValidateWEP jar file.



CDWVW0036E Unable to load the tag file. The filename is not available.


pack’s tag file name from the WepDir object. That directory entry was not populated. This could be caused by a






CDWVW0037E The entry (version) is not correct. The segment number segmentNumber segment) is not a valid

integer. The format for the entry must follow the <version>.<release>.<modification>.<fix pack>

format. (i.e. 1.2.0.0).

Explanation: The version number is not correct. It must follow the <version>.<release>.<modification>.<fix pack>

version numbering style.

Programmer Response: Correct the version number in the warehouse pack configuration script so that it follows the

numbering style indicated. Be sure that only numbers are used and that there are four segments in the version

number.

CDWVW0038E A null filename was provided for the readSqlFile().


pack’s SQL file name from the tagFile object. That filename entry was not populated. This could be caused by a




CDWVW0039E Unable to load the fileName configuration file.

Explanation: The program attempted to load the configuration file shown but was prohibited from doing so. Either

a permissions problem exists or the configuration file is missing.

Programmer Response: Verify that the configuration file exists and is named exactly as specified in the error

message. If so, verify that the tool has read access to the file.

CDWVW0040E The location (target or source) to run the SQL statement has already been provided at line

number lineNumber directive.

Explanation: More than one directive was given to indicate where the SQL statement is to be run. You are only

allowed to indicate one location (--#INSERT_INTO_SOURCE, --#INSERT_INTO_TARGET or

--#EXECUTE_AT_TARGET) per SQL statement.

Programmer Response: Remove all location directives except for the correct target or source location.

CDWVW0041E There was no terminating character given at line number lineNumber directive.

Explanation: No terminating character was found in this SQL statement. The terminating character is usually the

semicolon (;) but can be overridden with the --#OVERRIDE_TERMINATOR directive.

Programmer Response: Add the terminating character in the proper location at the end of the statement.

CDWVW0042E No information follows the Edit Using directive at line number lineNumber directive.

Explanation: The --#EDIT_USING directive in the generic SQL script was not complete. There was no information

provided following the directive itself.

Programmer Response: Correct the --#EDIT_USING directive in your script following the documented rules for

generic SQL. See the Enabling an Application for the Tivoli Data Warehouse, Version 1.2 documentation for details.

CDWVW0043E An Edit Using directive was already provided in this SQL statement at line number lineNumber

directive.

Explanation: There was more than one --#EDIT_USING directive given for a single SQL statement. You are only

allowed to indicate once that an insert into scenario needs to be processed by an external program.

Programmer Response: Remove all --#EDIT_USING directives except for the one to be followed.



CDWVW0044E The script provided is not an allowed --#EDIT_USING program at line number lineNumber

directive. Allowed programs are: (allowedPrograms).

Explanation: The program used to modify data is not supported. Only use one of the supported --#EDIT_USING

programs to modify data.

Programmer Response: Replace the indicated program with one of the programs supported by --#EDIT_USING.

CDWVW0045E There was no information following the If Target directive at line number lineNumber directive.

Explanation: The --#IF directive is not complete. There is nothing following the directive.

Programmer Response: Correct the directive by following the rules for the --#IF directive in the Enabling an

Application for the Tivoli Data Warehouse, Version 1.2 documentation.

CDWVW0046E The vendor provided at line number lineNumber directive is not recognized. Recognized vendors

are: (dbVendors).

Explanation: The --#IFSOURCE or --#IFTARGET directive indicates a database vendor type that is unknown or not

valid. Only use supported vendors as indicated in the error message.

Programmer Response: Verify that the vendor provided is not mispelled and is a supported database vendor type.

CDWVW0047E There was no matching --#IFSOURCE or --#IFTARGET found at line number lineNumber directive

for this Endif directive.

Explanation: An --#ENDIF was encountered which had no matching --#IFSOURCE or --#IFTARGET directive.

Programmer Response: Check to be certain that an --#IFTARGET or --#IFSOURCE directive exists for this --#ENDIF

directive. If there is no --#IFTARGET or --#IFSOURCE directive, remove this --#ENDIF directive.

CDWVW0048E There was no information following the --#USE_TRANSLATE directive at line number

lineNumber directive.

Explanation: The --#USE_TRANSLATE directive has missing information. There is nothing following the directive.

Programmer Response: Correct the directive by following the rules for the --#USE_TRANSLATE directive in the

Enabling an Application for the Tivoli Data Warehouse, Version 1.2 documentation.

CDWVW0049E The associated translate file translateFile was not found in the directoryName directory at line

numberlineNumber directive.

Explanation: The warehouse pack’s specific translate file was not found in the translate directory, even though the

--#USE_TRANSLATE directive indicated that one existed.

Programmer Response: Be certain the translate file is included in the directory shown and named exactly as

specified in your --#USE_TRANSLATE directive.

CDWVW0050E You are already in a --#FOR loop at line number lineNumber directive. Embedded --#FOR directives

are not allowed.

Explanation: A second --#FOR loop was encountered inside of the first --#FOR loop. This is not allowed. The

ExecSQL2 tool does not allow embedded --#FOR loops in generic SQL scripts.

Programmer Response: Remove the embedded --#FOR loop from the generic SQL script.

CDWVW0051E There was no matching --#FOR for this --#DONE directive at line number lineNumber directive.

Explanation: A --#DONE directive was encountered that did not have a matching --#FOR directive.

Programmer Response: Check to make sure that the matching --#FOR exists and is not misspelled. If it does not

exist, remove the --#DONE directive.



CDWVW0052E The directive at line number lineNumber directive was not recognized.

Explanation: An --# directive was encountered that was not recognized by the ValidateWEP tool.

Programmer Response: Either correct or remove the directive if it is not valid. If the directive is valid it is possible

that the generic script is newer than the ValdateWEP tool to verify the script. If this is the case contact IBM Customer

Support for a more recent version of the ValidateWEP tool.

CDWVW0053E The maximum allowed length (numberValue) for currentProperty found in rulesFile was less than the

minimum allowed length of (minimumRequiredLength ).


to set the maximum required length of a property lower than the minimum allowed length for that same property.

No values given in the configuration file can meet these two criteria.

Programmer Response: Make certain that the ValidateWEP jar is at the beginning of the CLASS_PATH and attempt

to run the ValidateWEP tool again. If the problem still occurs with the ValidateWEP tool at the beginning of the

CLASS_PATH, contact IBM Customer Support for further assistance.

CDWVW0054E The entry (version) is not in the correct format. There are numberSegments segments (instead of 4)

for this entry. The format for the entry must follow the ’<version>.<release>.<modification>.<fix

pack>’ format. (i.e. ’1.2.0.0’).

Explanation: The version number is not in the correct format. It must follow the

<version>.<release>.<modification>.<fix pack> version numbering style.

Programmer Response: Correct the version number in the warehouse pack configuration script so that it follows the

numbering style indicated. Only numbers can be used and be aware there are four segments in the version number.

CDWVW0060E An internal error occurred, make sure that the ValidateWEP jar file is at the beginning of the

CLASS_PATH.

Explanation: An unexpected error condition was encountered and logged to the ValidateWEP tool trace file.

Programmer Response: Make sure that the ValidateWEP jar file is at the beginning of the CLASS_PATH and run the

ValidateWEP tool again. If the problem still occurs, contact IBM Customer Support for further assistance.


CLASS_PATH.





CLASS_PATH.





CLASS_PATH and run the ValidateWEP tool again.






CDWVW0100W The property propName has already been added. An attempt was made to add a duplicate

property to the list. Discarding the second attempt.

Explanation: A duplicate entry was found in the warehouse pack configuration file. Duplicate property entries are

not allowed.

Programmer Response: Remove the duplicate entry from the warehouse pack configuration file and run the

ValidateWEP tool again.

CDWVW0101W A --#VERSION directive was already provided at line number lineNumber directive for this SQL

file. Only one is needed.

Explanation: The --#VERSION directive is specific to the entire generic SQL script, not just a single SQL statement.

It only needs to be provided once per script.

Programmer Response: Remove all but one of the --#VERSION directives from the script.

CDWVW0102W A potential inefficiency exists in file generateFileat line #lineNum. The use of the Edit Using

directive is not efficient.

Explanation: Use of the --#EDIT_USING directive causes data to be transferred from the database to the ExecSQL

process, written to a file, modified by an external program, read from the external programs file and inserted into the

target database. This process is not efficient and is discouraged if there are other ways to manipulate the data from

within the database.

Programmer Response: Consider alternatives to --#EDIT_USING such as stored procedures or SQL manipulation

before resorting to an external program to alter the data.

CDWVW0103W A potential inefficiency exists in file generateFile at line number lineNumber. A SQL keyword

LIKE was found. Use of this keyword is not efficient. Be sure there is no other way to perform this

task before using this keyword.

Explanation: Use of the SQL keyword LIKE is not efficient since it requires the database’s SQL engine to perform

pattern matching against text columns. An absolute comparison (=) or set comparison in (...) would provide better

performance.

Programmer Response: Consider alternatives to using the LIKE keyword before resorting to its use in your SQL

script.

CDWVW0104W A potential inefficiency exists in file generateFile at line number lineNumber. A SQL Select * was

found. Using a Select * in queries can be inefficient. Please consider providing specific column

names in your query to improve efficiency.

Explanation: Using a Select * in queries can be inefficient as the databases SQL engine has to query system tables to

determine the columns you wish to select before running the actual select statement itself. Over multiple runs this

extra table scan can increase the overall time to run an ETL.

Programmer Response: Provide column names in your select statement instead of relying on the * to populate the

column names for you.

CDWVW0105W A potential inefficiency exists in file genFile at line number lineNumber. Using NOT IN in a

select WHERE clause can be inefficient. Be sure that there is no other way to perform this task

before doing this.

Explanation: Use of the SQL keywords NOT IN is not efficient because it requires the database’s SQL engine to scan

the entire table for columns that do not match the set provided. An absolute comparison (=) or set comparison in (...)

would provide better performance.

Programmer Response: Consider alternatives to using the NOT IN keywords before resorting to their use in your

SQL script.

CDWVW0100W • CDWVW0105W


CDWVW0106W A potential inefficiency exists in file genFile at line number lineNumber. Using a <> in a select

WHERE clause is not efficient. Be sure that there is no other way to perform this task before using

it.

Explanation: Use of the <>, i.e., NOT IN, is not efficient because it requires the database’s SQL engine to scan the

entire table for columns that do not match the set provided. An absolute comparison (=) or set comparison in (...)

provides better performance.

Programmer Response: Consider alternatives to using the <> comparison before resorting to its use in your SQL

script.

HOST Report Server Host Name


USER Report Server User ID


CDWVW0106W • USER



Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not give you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758

U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement or any equivalent agreement

between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may

vary significantly. Some measurements may have been made on development-level

systems and there is no guarantee that these measurements will be the same on

generally available systems. Furthermore, some measurement may have been

estimated through extrapolation. Actual results may vary. Users of this document

should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of

performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the

suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or

withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business

operations. To illustrate them as completely as possible, the examples include the

names of individuals, companies, brands, and products. All of these names are

fictitious and any similarity to the names and addresses used by an actual business

enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrates programming techniques on various operating platforms. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating

platform for which the sample programs are written. These examples have not

been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or

imply reliability, serviceability, or function of these programs. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM for the purposes of developing, using, marketing, or distributing application

programs conforming to IBM’s application programming interfaces.


If you are viewing this information softcopy, the photographs and color

illustrations may not appear.

Trademarks

The following terms are trademarks or registered trademarks of International

Business Machines Corporation in the United States, other countries, or both:

AIX NetView

DB2 OS/2

DB2 OLAP Server OS/390

DB2 Universal Database Rational Rose

Distributed Relational Database Architecture Redbooks

Domino RS/6000

DRDA Tivoli

IBM Tivoli Enterprise

IMS Tivoli Enterprise Console

Informix TME

Lotus WebSphere

MVS z/OS

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.

in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

Microsoft Corporation in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation

in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other

countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

Other company, product or service names may be trademarks or service marks of

others.

Notices 167


��

Printed in USA

SC09-7776-00

Documents

T l Data Warehouse - publib.boulder.ibm.com