Tivoli

Data

Warehouse

Messages

Version

1.2

SC09-7776-00

Tivoli

Data

Warehouse

Messages

Version

1.2

SC09-7776-00

First

Edition

(December

2003)

This

edition

applies

to

version

1,

release

2,

modification

0

of

Tivoli

Data

Warehouse

and

to

all

subsequent

releases

and

modifications

until

otherwise

indicated

in

new

editions.

Copyright

International

Business

Machines

Corporation

2003.

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

Who

should

read

this

guide

.

.

.

.

.

.

.

.

. v

Publications

.

.

.

.

.

.

.

.

.

.

.

.

.

. v

Tivoli

Data

Warehouse

publications

.

.

.

.

.

. v

Related

publications

.

.

.

.

.

.

.

.

.

. vi

Accessing

publications

online

.

.

.

.

.

.

. ix

Ordering

publications

.

.

.

.

.

.

.

.

.

. x

Contacting

customer

support

.

.

.

.

.

.

.

.

. x

Conventions

used

in

this

guide

.

.

.

.

.

.

.

. x

Typeface

conventions

.

.

.

.

.

.

.

.

.

. x

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

.

.

.

.

.

.

.

.

.

.

.

.

.

. 163

Trademarks

.

.

.

.

.

.

.

.

.

.

.

.

.

. 165

Copyright

IBM

Corp.

2003

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.

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.

Tivoli

Data

Warehouse

publications

The

following

documents

are

available

in

the

Tivoli

Data

Warehouse

library:

v

Tivoli

Data

Warehouse

Documentation

CD,

LK3T-8111

v

Tivoli

Data

Warehouse

Release

Notes,

GI11-0857

Provides

late-breaking

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.

Copyright

IBM

Corp.

2003

v

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

their

applications

data,

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.

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

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

to

perform

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.

vi

Tivoli

Data

Warehouse:

Messages

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

Crystal

Enterprise

publications

The

following

documents

describe

how

to

install,

use,

and

administer

Crystal

Enterprise.

These

documents

are

available

on

theCrystal

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

Users

Guide

Provides

information

and

procedures

for

accessing

and

using

ePortfolio

and

its

report

viewers.

v

Crystal

Enterprise

9

Administrators

Guide

Provides

information

and

procedures

covering

a

wide

range

of

administrative

tasks.

Procedures

are

provided

for

common

tasks.

Conceptual

information

and

technical

details

are

provided

for

all

advanced

topics.

v

Crystal

Reports

9

Users

Guide

Provides

procedures

for

typical

reporting

tasks

such

as

placing

fields,

formatting

reports,

and

sorting

records.

It

also

contains

information

on

more

specific

areas

of

interest

such

as

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.

For

those

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

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.

About

this

guide

vii

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

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

on

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

to

install

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

Describes

SQL

syntax,

semantics,

and

the

rules

of

the

language.

This

book

also

includes

information

about

release-to-release

incompatibilities,

product

limits,

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

the

Tivoli

Decision

Support

for

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

and

the

Tivoli

Decision

Support

for

OS/390

library:

viii

Tivoli

Data

Warehouse:

Messages

v

IBM

DB2

Universal

Database

for

z/OS

and

OS/390

Administration

Guide,

SC26-9931

Provides

information

on

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

end

users.

v

IBM

DB2

Universal

Database

for

z/OS

and

OS/390

An

Introduction

to

DB2

for

OS/390,

SC26-9937

Provides

information

on

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

on

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

on

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.

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:

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

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.

About

this

guide

ix

http://publib.boulder.ibm.com/tividd/td/tdprodlist.htmlhttp://www.ibm.com/software/data/db2/library/

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-3.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:

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

operating

system-dependent

commands

and

paths.

Typeface

conventions

This

guide

uses

the

following

IBM-style

typeface

conventions:

Bold

Lowercase

and

mixed-case

commands,

command

options,

and

flags

that

appear

within

text

appear

like

this,

in

bold

type.

x

Tivoli

Data

Warehouse:

Messages

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/sysmgmt/products/support/http://www-3.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.htmlhttp://www-3.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.htmlhttp://www.ibm.com/software/data/db2http://techsupport.services.ibm.com/guides/handbook.html

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.

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.

About

this

guide

xi

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

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

Table

1.

Subsystem

codes

(continued)

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

Table

1.

Subsystem

codes

(continued)

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.

4

Tivoli

Data

Warehouse:

Messages

Table

1.

Subsystem

codes

(continued)

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

6

Tivoli

Data

Warehouse:

Messages

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.

Copyright

IBM

Corp.

2003

7

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.

8

Tivoli

Data

Warehouse:

Messages

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.

Copyright

IBM

Corp.

2003

9

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

CDWCR0013E

The

data

mart

user

id

was

not

passed

to

the

Crystal

connection

utility.

The

parameter,

user,

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

mart

user

(DB2

user)

must

be

specified

by

using

the

parameter,

user.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

CDWCR0014E

The

password

for

the

data

mart

user

was

not

passed

to

the

Crystal

connection

utility.

The

parameter,

passwd,

was

not

specified.

Explanation:

This

is

an

internal

error.

The

Tivoli

Data

Warehouse

installation

calls

the

report

migration

utility

and

should

pass

the

correct

parameters.

A

data

mart

logon

password

for

a

DB2

user

must

be

specified

by

using

the

parameter,

passwd.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

CDWCR0017E

A

number

that

is

not

valid

was

found

for

a

component

attribute

order

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

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

CDWCR0009E

CDWCR0017E

10

Tivoli

Data

Warehouse:

Messages

CDWCR0018E

A

number

that

is

not

valid

was

found

for

the

number

of

metrics.

Explanation:

This

is

an

internal

error

indicating

corrupt

metadata

for

a

report.

The

report

migration

utility

found

a

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

CDWCR0019E

A

number

that

is

not

valid

was

found

for

the

number

of

component

attributes.

Explanation:

This

is

an

internal

error

indicating

corrupt

metadata

for

a

report.

The

report

migration

utility

found

a

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

CDWCR0020E

A

number

that

is

not

valid

was

found

for

the

metric

ID.

Explanation:

This

is

an

internal

error

indicating

corrupt

metadata

for

a

report.

The

report

migration

utility

found

a

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

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.

Its

represented

with

a

number

in

Tivoli

Data

Warehouses

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

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.

CDWCR0018E

CDWCR0024E

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.

Administrator

Response:

Run

FFDC

and

contact

IBM

Customer

Support

to

help

you

diagnose

the

problem.

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.

Administrator

Response:

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

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.

Administrator

Response:

Review

the

reporting_message_log.log

file

in

the

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

CDWCR0025E

CDWCR0031E

12

Tivoli

Data

Warehouse:

Messages

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