Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
Tivoli® Data Warehouse
Tivoli Data Warehouse Release Notes
Version 1.3
SC32-1399-01
���
Tivoli® Data Warehouse
Tivoli Data Warehouse Release Notes
Version 1.3
SC32-1399-01
���
Note
Before using this information and the product it supports, read the information in Appendix B, “Notices,” on page 21.
Third Edition (April 2005)
This edition applies to Tivoli Data Warehouse, Version 1.3 and to all subsequent releases and modifications until
otherwise indicated in new editions.
This edition replaces SC32-1399-00.
© Copyright International Business Machines Corporation 2002, 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1. About this release . . . . . 1
New in this release . . . . . . . . . . . . 1
Product fix history . . . . . . . . . . . . 1
Compatibility with previous releases . . . . . . 2
Product compatibility . . . . . . . . . . . 2
Chapter 2. Installation information . . . 3
Hardware requirements . . . . . . . . . . . 3
Software requirements . . . . . . . . . . . 4
Database requirements . . . . . . . . . . 5
Report interface requirements . . . . . . . . 6
Installation and upgrade notes . . . . . . . . 6
Performance . . . . . . . . . . . . . 7
Chapter 3. Known limitations, problems,
and workarounds . . . . . . . . . . . 9
Limitations . . . . . . . . . . . . . . . 9
Known problems and workarounds . . . . . . 11
Installation, upgrade, or uninstallation problems 11
Report interface problems . . . . . . . . 12
Miscellaneous problems . . . . . . . . . 12
Internationalization problems . . . . . . . . 14
Appendix A. Support information . . . 17
Learning about education . . . . . . . . . . 17
Searching knowledge bases . . . . . . . . . 17
Search the documentation . . . . . . . . 17
Search the Internet . . . . . . . . . . . 17
Obtaining fixes . . . . . . . . . . . . . 18
Contacting IBM Software Support . . . . . . . 18
Determine the business impact of your problem 19
Describe your problem and gather background
information . . . . . . . . . . . . . 19
Submit your problem to IBM Software Support 19
Appendix B. Notices . . . . . . . . . 21
Trademarks . . . . . . . . . . . . . . 23
© Copyright IBM Corp. 2002, 2005 iii
iv Tivoli Data Warehouse Release Notes
Chapter 1. About this release
This document provides important information about Tivoli® Data Warehouse,
Version 1.3. This information is the most current information for the product and
supersedes all other documentation. Read the information in this document before
installing or using Tivoli Data Warehouse.
New in this release
Tivoli Data Warehouse, Version 1.3, has the following new and changed features:
Note: Functionality depends upon features that individual warehouse packs
provide.
v Support for IBM® DB2 Universal Database™ Enterprise Server Edition, Version
8.2, including the IBM DB2® Data Warehouse Center that is included with IBM
DB2 Universal Database Enterprise Server Edition, Version 8.2.
v Support for Crystal Enterprise Professional v.10.
v Support for 1.1 and 1.2 warehouse packs and their patches. Support for the
upgrade of a 1.1 warehouse pack to a 1.2 warehouse pack, where the warehouse
pack is designed with this support. Reports for 1.1 warehouse packs converted
to the Crystal Enterprise format during warehouse pack installation.
v Scripts and instructions about pre-creating central data warehouse databases and
data mart databases for tuning these databases manually for high performance
before installing Tivoli Data Warehouse.
v Pre-creation of table spaces larger than 4K pages during installation of Tivoli
Data Warehouse.
v New and modified event tables for the central data warehouse schema.
v Updates to accessibility and globalization items that are related to previous
versions of the Java™ Virtual Machine and InstallShield MultiPlatform
Product fix history
The following defects were fixed for Tivoli Data Warehouse, Version 1.3:
v Removed all accessibility issues.
v On some windows of the installation wizards, the button text is no longer
truncated. This had been a limitation of the InstallShield Multiplatform product
used for the installation process.
v PMR 17980 br499: Steps of an ETL process had failed randomly in the DB2 Data
Warehouse Center.
v Defect 157941: In the DB2 Data Warehouse Center, the Processing Options tab of
the Step Properties window had displayed a message that the selected agent site
was not valid.
v InstallShield Multiplatform and its Java Virtual Machine (JVM) formerly had
documented issues regarding DBCS locales. For example, extra spaces had
occurred between characters, or characters were truncated, or default fonts were
not readable.
v Defect 174154: Warehouse packs for IBM Tivoli Enterprise Console® could not
run on Tivoli Data Warehouse, Version 1.3. A DB2 server, Version 7, could not
run with a DB2 client, Version 8.
© Copyright IBM Corp. 2002, 2005 1
Compatibility with previous releases
You can install warehouse packs for version 1.1 and version 1.2 on Tivoli Data
Warehouse, Version 1.3. See Installing and Configuring Tivoli Data Warehouse,
GC32-0744 for additional details.
Product compatibility
For compatibility of warehouse packs with Tivoli Data Warehouse, Version 1.3, see
the documentation for each applicable warehouse pack.
The installation programs for Tivoli Data Warehouse and warehouse packs cannot
be run using Tivoli Remote Control.
2 Tivoli Data Warehouse Release Notes
Chapter 2. Installation information
This chapter provides hardware and software requirements.
Note: If your systems do not meet the hardware and software requirements that
are listed in this section, you might receive confusing error messages and
have problems installing and using Tivoli Data Warehouse.
Hardware requirements
This section provides information about the hardware requirements for installing
Tivoli Data Warehouse.
See the planning chapter in Installing and Configuring Tivoli Data Warehouse for
database sizing formulas and considerations.
As the warehouse pack for each Tivoli product is added to the Tivoli Data
Warehouse installation, additional hard disk space is required. See the
documentation for each warehouse pack for planning information and hard disk
space requirements.
Table 1 lists the minimum and recommended hardware requirements for Tivoli
Data Warehouse.
Table 1. Hardware requirements
Deployment
type Component
Minimum
requirements
Recommended
size
Temporary hard
disk space
Quick start All v 1 GB RAM
v 1 GB hard disk
space
v 933 MHz
processor
v 4 GB RAM
v 3 GB hard disk
space
1 GB
Distributed Control server v 1 GB RAM
v 1 GB hard disk
space
v 933 MHz
processor
v 3+ GB RAM
v 1 GB hard disk
space
1 GB
Central data
warehouse
v 1 GB RAM
v 2 GB hard disk
space
v 933 MHz
processor or
Power 4, 5
processor
v 3+ GB RAM
v 20+ GB hard
disk space
1 GB
Data mart v 1 GB RAM
v 2 GB hard disk
space
v 933 MHz
processor or
Power 4, 5
processor
v 3+ GB RAM
v 4+ GB hard
disk space
1 GB
© Copyright IBM Corp. 2002, 2005 3
Note: The quick start deployment is convenient for small installations and requires
less space.
Software requirements
This section provides information about the software requirements for Tivoli Data
Warehouse.
Table 2 lists the operating systems that Tivoli Data Warehouse supports.
Table 2. Supported operating systems
Operating system Data
source1
Warehouse
agents
Control
server
Central
data
warehouse
Data mart
Microsoft® Windows®
2000 Server, service pack
2 or higher
Microsoft Windows 2000
Advanced Server, service
pack 2 or higher
Microsoft Windows
Server 2003 Enterprise
and Datacenter
Editions+
Yes Yes Yes Yes Yes
IBM AIX®, Versions 5L,
including 5.1 and 5.2
AIX, Version 5.2 support
is for 32-bit and 64-bit
systems when running
with DB2 Universal
Database Enterprise
Edition, Version 8x
Yes Yes No Yes Yes
IBM AIX, Versions 5L,
including 5.3
Yes No No Yes Yes
Sun Solaris, Versions 2.8,
2.9, and 2.10
Yes Yes for 2.8
and 2.9
No Yes Yes
Red Hat Linux®,
Versions 7.2 and 7.3
Yes No No No No
Red Hat Enterprise
Linux 2.1 for xSeries® —
32b, RHEL 3.0 AS+ for
xSeries (ES and WS
versions)
Yes No No No No
SuSE Linux Enterprise
Server 7.0, 7.2, and 7.3
xSeries
SuSE Linux Enterprise
Server 8.0/UL 1.0 SP3
for xSeries
SuSE Linux Enterprise
Server 9.0
Yes No No No No
4 Tivoli Data Warehouse Release Notes
Table 2. Supported operating systems (continued)
Operating system Data
source1
Warehouse
agents
Control
server
Central
data
warehouse
Data mart
IBM z/OS®, V1R2,
V1R3, V1R4, and V1R5
Yes No No Yes Yes
1 Data source support is determined by the ODBC support in DB2 releases.
Database requirements
Table 3 lists the databases that are supported by the Tivoli Data Warehouse
components. In addition, Tivoli Data Warehouse supports file imports from the
Merant driver as a data source.
Table 3. Supported relational database management systems
Database systems Data sources1 Control
database
Central data
warehouse
Data mart
IBM DB2 Universal
Database Enterprise
Server Edition,
Version 8.23
Yes Yes (Windows) Yes (AIX,
Windows, and
Solaris)
Yes (AIX,
Windows, and
Solaris)
DB2 Universal
Database Enterprise
Edition, Version 7.1
and 7.22
Yes No No No
DB2 Universal
Database for z/OS
and OS/390®,
Version 7.1 with IBM
Data Management
Tools, Management
Tools Package for
DB2 V7 on z/OS;
FMID JDB771D
Yes No Yes Yes
IBM DB2 Universal
Database for z/OS,
Version 8.1 with IBM
Data Management
Tools, Management
Tools Package for
DB2 V7 on z/OS;
FMID JDB771D
No No Yes Yes
Oracle client, Version
8.1.7 and either:
v Oracle, Version 8i
v Oracle, Version 9i
or 9i v2
Yes No No No
Microsoft SQL Server,
Version 7.0 on
Windows NT®
Microsoft SQL Server
2000 on Windows
2000
Yes No No No
Chapter 2. Installation information 5
Table 3. Supported relational database management systems (continued)
Database systems Data sources1 Control
database
Central data
warehouse
Data mart
Sybase, Version 12
and 12.5
Yes No No No
Informix® 9.2 and 9.3 Yes No No No
1 Data source support is determined by the ODBC support in DB2 releases.
2 Fix pack 8 with its fix, fix pack 10a, or fix pack 11 for DB2 Universal Database, Version
7.2 is required.
3 When upgrading to DB2 Universal Database, Version 8.2, you must apply fix 13411 before
upgrading to Tivoli Data Warehouse, Version 1.3.
Table 4 lists the DB2 requirements for each Tivoli Data Warehouse component.
Table 4. DB2 requirements
Deployment type Component DB2 requirement
Quick start All DB2 server
Distributed Control server DB2 server
Central data warehouse DB2 server
Data mart DB2 server
Crystal Enterprise server DB2 client
Report interface requirements
To view and publish reports, Tivoli Data Warehouse requires Crystal Enterprise
Professional v.10. Crystal Enterprise Professional v.10 is shipped with Tivoli Data
Warehouse. For information about Crystal Enterprise requirements, see the Crystal
Enterprise documentation.
Installation and upgrade notes
This section provides information about the Tivoli Data Warehouse installation.
Review the information in this section before you begin your installation.
To continue using the instances and databases you installed with Tivoli Data
Warehouse, Version 1.2, you must upgrade IBM DB2 Universal Database Enterprise
Server Edition, Version 7.2 to IBM DB2 Universal Database Enterprise Server
Edition, Version 8.2 on each system in your Tivoli Data Warehouse deployment
where DB2 Universal Database is installed.
Note: This upgrade requirement applies only to control, central data warehouse,
and data mart databases. You do not need to migrate DB2 7.2 source
databases.
After upgrading to DB2 Universal Database, Version 8.2, you must apply DB2 fix
13411 before upgrading to Tivoli Data Warehouse, Version 1.3 (see Defect 177549).
The DB2 fix is available in the \hotfix\DB2\13411 directory of the Tivoli Data
Warehouse installation CD. Place the iwh2regi.exe and ddd.dll files in the
SQLLIB\BIN directory of the DB2 Universal Database installation.
6 Tivoli Data Warehouse Release Notes
An DB2 upgrade tool can be used to automate the upgrade process if your system
settings are not complex and your environment meets certain requirements. If your
system does not meet these requirements, you must manually upgrade DB2
Universal Database. For details, see the chapter on upgrading Tivoli Data
Warehouse in Installing and Configuring Tivoli Data Warehouse.
Performance
A DB2 fix improves the performance of an installation on a single Windows
system. Without this fix, the performance is much slower than Tivoli Data
Warehouse, Version 1.2. A significant performance degradation can occur with
Tivoli Data Warehouse, Version 1.3, and DB2 Universal Database, Version 8.2, when
all warehouse components are installed on a single Windows system. Entitled
customers can reference the online APAR documentation for JR21289 for more
details. For customers who deploy Tivoli Data Warehouse before the fix pack is
available, an interim fix is available by searching the Tivoli Data Warehouse
support site
http://www.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.html
for ’DB2 performance efix for TDW 1.3’.
Chapter 2. Installation information 7
8 Tivoli Data Warehouse Release Notes
Chapter 3. Known limitations, problems, and workarounds
This section provides information about known software limitations and defects for
Tivoli Data Warehouse, Version 1.3.
Refer to the Tivoli Data Warehouse Troubleshooting Guide for problem determination
information for installation, configuration, and error messages. It also describes
how to obtain information to debug problems.
Limitations
This section describes the limitations of Tivoli Data Warehouse.
v Do not alter IWH tables without first consulting DB2 Data Warehouse Center
Support.
Various objects have disappeared from the DB2 Data Warehouse Center (DWC)
GUI at some customer sites. Extensive consultation with DB2 Data Warehouse
Center support has shown that users must not alter the IWH tables without
consulting with DB2 Data Warehouse Center support.
Altering columns such as iwhid in the IWH.RELATIONSHIP table causes
adverse effects in the DB2 Data Warehouse Center. The iwhid column is not
unique. The following problems can occur when data is altered in this column:
– Parameters are removed from steps, rendering them useless.
– Data is removed from star schemas, corrupting reports.
– Entire ETL steps are removed, making a warehouse pack useless.
– Objects are corrupted in the DB2 Data Warehouse Center, making both the
DB2 Data Warehouse Center and Tivoli Data Warehouse useless.v Defect 175030: Crystal Enterprise, V.10 is not supported in Windows 2003
environments where the IBM HTTP server is installed. For information about
Crystal Enterprise requirements, see the Crystal Enterprise documentation.
v Defect 175318: The Crystal Advanced HTML Viewer does not work in Crystal
Enterprise, V.10. This limitation applies only to the View action from ePortfolio
and the Preview action from the Crystal Management Console. For information
about Crystal Enterprise issues, see the Crystal Enterprise documentation.
Workaround: Use the default HTML viewer. Alternatively, view scheduled
reports with the Crystal Advanced HTML Viewer.
v After the initial installation of Tivoli Data Warehouse, adding central data
warehouses and data marts to the control server can fail if the port for the DB2
server is not set to the default, 50000. In the Tivoli Data Warehouse installation
wizard, you must set the Host Location in the Central Data Warehouse
Properties window to be remote and specify the port number to use.
v When you change to a new Crystal Enterprise server, the Everyone group
privileges are affected by importing using the Crystal Enterprise Import Wizard.
(For details, see the section on Client tools installation in the Crystal Enterprise 10
Installation Guide.) After running the twh_update_rptsrv command, reset the
permissions as required.
v Some migrated reports with specific sets of data might cause X-axis labels to be
truncated or overwritten. Crystal Enterprise has a limitation that a graph must
fit on a physical page.
© Copyright IBM Corp. 2002, 2005 9
v When viewing reports with the ePortfolio, if you select the drop-down box to
choose a specific time frame, the date and time values are reset to their default
value.
v If Information Catalog Manager (ICM) Version 7 is installed on the same
Windows NT or Windows 2000 system as Sybase Open Client, an error occurs
and the Sybase Utilities stops. An error message similar to the following is
displayed:
Fail to initialize LIBTCL.DLL.
Please make sure the SYBASE environment variable is set correctly.
Remove the LC_ALL environment parameter from the Windows environment
parameters to correct this problem.
Note: If you remove the LC_ALL environment, the following ICM functions are
disabled:
– Information Catalog User
– Information Catalog Administrator
– Information Catalog ManagerLC_ALL is a locale category parameter. Locale categories are manifest constants
that the localization routines use to specify which portion of the locale
information a program should use. The locale refers to the locality (country or
region) for which certain aspects of a program can be customized.
Locale-dependent areas include, for example, the formatting of dates, or the
display format for monetary values. LC_ALL affects all categories of
locale-specific behavior.
Use the following procedure to remove the LC_ ALL environment parameter:
1. On the task bar, select the Start button → Settings → Control Panel → System.
The System Properties window is displayed.
2. Select the Environment tab.
3. Select LC_ALL.
4. Click Delete.v For Sybase, the following error message might be displayed:
The ’CREATE TABLE’ command is not allowed within a
multi-statement transaction in the ’database_name’
database.
Workaround:
1. From the ISQL command line, enter use master.
2. Enter go.
3. Enter sp_dboption dbname’ddl in tran’,true, where dbname is the name of
the database.
4. Enter go. The following message is displayed:
Database option ’ddl in tran’ turned ON for database ’dbname’
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
5. Enter use dbname.
6. Enter go.
7. Enter checkpoint.
8. Enter go.
9. Enter quit.
10 Tivoli Data Warehouse Release Notes
Known problems and workarounds
This section provides information about known problems with Tivoli Data
Warehouse. Workarounds are provided for some problems. Defects listed here
apply to all languages. For information about defects associated with specific
languages, see “Internationalization problems” on page 14.
Installation, upgrade, or uninstallation problems
v Defect 177148: The installation of a warehouse pack might fail to copy the files
to the remote agent site. The logs could indicate that the tar command returned
an unexpected ″in the future″ message type.
v Defect 177483: Among other warehouse packs that cannot be installed, the
warehouse pack for IBM Tivoli Netview (ANM Version 1.1.0) cannot be installed.
v Defect 176312: The warehouse pack installation wizard hangs when going back
to previous windows and changing options for the central data warehouse and
data mart agents.
Workaround: Minimize and then restore the installation wizard. The screen is
refreshed and the installation wizard is able to continue.
v On AIX and Solaris, the vwdaemon process does not always restart after
installing the DB2 Warehouse Manager.
Workaround: Reboot the AIX or Solaris system after the installation of the DB2
Warehouse Manager.
v Defect 164948: On z/OS, the installation of Tivoli Data Warehouse might fail if
the values provided in the installation wizard are not valid. Also, the resources
specified in the installation wizard must be available at the time of installation.
The following error message might be displayed:
CDWIC0022E The installation program cannot run SQL script sql_script.
Workaround: Ensure that the values provided in the installation wizard are valid
and that the resources specified in the installation wizard are available at the
time of installation. Review the execsql2_message_log.log to determine where
the failure occurred in the database script.
v Defect 167717: When you install a warehouse pack and use the default schedule
to run the extract, transform, and load (ETL) processes, the default start date is
December 15, 2002 (12/15/2002). Nevertheless, your scheduled ETLs will run
successfully after installation.
v When you upgrade IBM DB2 Data Warehouse Manager, Version 7.2 to IBM DB2
Data Warehouse Manager, Version 8.2, the link to the version 7 daemon is not
updated when version 8 is installed.
Workaround: The following four files in the /usr/bin directory are symbolically
linked to the old version 7 binary files after the version 8 upgrade is done:
– IWH2AGNT
– iwhetrig
– IWH.startup
– vwdaemon
Rename these files with alternate extensions so that they are no longer found in
the path.
v Defect 177632: The Tivoli Web Site Analyzer warehouse pack (AWT)
uninstallation fails with the following message:
CDWIC5177E A failure occurred while deleting the warehouse pack objects
from the DB2 Data Warehouse Center.
Chapter 3. Known limitations, problems, and workarounds 11
The uninstallation apparently deletes virtually everything except the warehouse
pack’s data mart target resource called AWT_TWSA_MART_Target. The
uninstallation logs show that this resource is deleted with a return code of 0, but
the uninstallation program still finds the resource, making the uninstallation fail.
Workaround: To uninstall the Tivoli Web Site Analyzer warehouse pack (ava
code AWT) with Tivoli Data Warehouse, Version 1.3, manually uninstall the
remaining Tivoli Web Site Analyzer warehouse pack objects from the DB2 Data
Warehouse Center and rerun the Tivoli Data Warehouse warehouse pack
uninstallation program for the Tivoli Web Site Analyzer warehouse pack.
Use the following steps to uninstall manually:
1. Open the DB2 Data Warehouse Center.
2. Expand Warehouse Schemas.
3. Select AWT_SITE_STAR.
4. In the right panel, select all the AWT tables, right-click, and select Remove.
5. Click OK for confirmation.
6. In the left panel, select AWT_SITE_STAR, right-click, and select Remove.
7. Click OK for confirmation.
8. Expand Warehouse Targets.
9. Expand AWT_TWSA_MART_Target and select Tables.
10. In the right panel, select all the AWT tables, right-click, and select Remove.
11. Click OK for confirmation.
12. In the left panel, select AWT_TWSA_MART_Target, right-click, and select
Remove.
13. Click OK for confirmation.
14. Close the DB2 Data Warehouse Center.
15. Rerun the Tivoli Data Warehouse warehouse pack uninstallation program
for the AWT warehouse pack.
Report interface problems
v Defect 177308: An error similar to the following occurs when opening specific
IBM Tivoli Enterprise Console reports that are scheduled:
Unable to connect: incorrect log on parameters.
File ~ceb3f43c0514a32554.rpt
The affected reports are Events for Hostname IP Address by Status and Events
for Source by Status.
v Defect 163415: Extreme case reports that had an ascending output in Tivoli
Enterprise™ Data Warehouse, Version 1.1 can only run with a descending output
after migration to Tivoli Data Warehouse, Version 1.2.
Miscellaneous problems
v Defect 167862: When incorrect command line parameters are entered for the
administrative utilities, a response similar to the following is generated:
twh_core_admin.pl : unrecognized option ’-r’
Try ’twh_core_admin.pl --help’ for more information.
Workaround: You must omit the text .pl from the statement. For example, use
the following statement:
twh_core_admin --help
v Defect 153132: In some cases when you use the DB2 Data Warehouse Center to
run steps, the characters < and > are displayed in pop-up messages. The
12 Tivoli Data Warehouse Release Notes
DB2 Data Warehouse Center has a limitation of not displaying the symbol for
greater than (>) and the symbol for less than (<).
v APAR: JR20112 (the specific Tivoli Data Warehouse APAR is IY57659) : In some
cases, the first time you run a step that uses the Tivoli Data Warehouse rollup
mechanism, a DB2 defect occurs with an error message similar to the following
example:
DWC07356E An agent’s processing of a command of type
’runUDP’ failed for edition ’44’ of step
’amy_m05_s040_Mart_Rollup’.
CDW8101E Select from rpi.ss_joincols failed
with the following message:
Database Connection Information
Database server= DB2/NT 8.2.1
SQL authorization ID = DB2ADMIN
Local database alias = TWH_MD
SQL0575N View or metrialized query table
’RPI.SS_JOINCOLS’ cannot be used because it
has been marked inoperative.
SQLSTATE=51024 RC=7356
RC2=8410
Workaround: Use either of the following methods to drop and recreate the view:
– For the first method, type the following information at the DB2 command
line:
connect to twh_md user userid using password
drop view rpi.ss_joincols
create view RPI.ss_joincols as
SELECT
ss.name as ssname,
a1.largedrschemaname as schema,
a1.largedrtablename as tabname,
a1.largename as colname
FROM
IWH.AttributeLink at,
IWH.Relationship r1,
IWH.StarSchema ss,
IWH.Relationship r2,
IWH.attribute a1
where
at.type=’JOIN’ and
at.iwhid = r1.source_iwhid and
r1.relation_name = ’StarSchema_TO_AttLnk’ and
r1.target_iwhid = ss.iwhid and
r2.relation_name = ’AttLink1_TO_Attr_Rel’ and
r2.source_iwhid = at.iwhid and
a1.iwhid = r2.target_iwhid
union
SELECT
ss.name as ssname,
a1.largedrschemaname as schema,
a1.largedrtablename as tabname,
a1.largename as colname
FROM
IWH.AttributeLink at,
IWH.Relationship r1,
IWH.StarSchema ss,
IWH.Relationship r2,
IWH.attribute a1
where
at.type=’JOIN’ and
at.iwhid = r1.source_iwhid and
r1.relation_name = ’StarSchema_TO_AttLnk’ and
Chapter 3. Known limitations, problems, and workarounds 13
r1.target_iwhid = ss.iwhid and
r2.relation_name = ’AttLink2_TO_Attr_Rel’ and
r2.source_iwhid = at.iwhid and
a1.iwhid = r2.target_iwhid;
– For the second method do the following steps:
1. Double-click on the rpi.ss_joincols view in Control Center (under the
control database, under the Views item) to get the create SQL for this view
(copy and paste to a text file).
2. Drop the view.
3. Run the SQL to recreate the view. For example, if you copied the SQL for
the view create to a file called create_rpi_ss_joincols.sql, you could run
this SQL with the following commands (ensuring that the last line of this
file ends with a semicolon):
db2 connect to twh_md user <user>
db2 -stvf create_rpi_ss_joincols.sql;
Internationalization problems
This section provides information about known problems with Tivoli Data
Warehouse versions that are in languages other than English.
Note: Some defects described in “Known problems and workarounds” on page 11
might affect translated versions of Tivoli Data Warehouse.
v Defect 175850: On AIX, the installation of IBM WebSphere® does not work on
UTF-8 Japanese systems. For information about IBM WebSphere issues, see the
IBM WebSphere documentation.
v Defect 177075: Upgrading from Tivoli Data Warehouse, Version 1.2, to Tivoli
Data Warehouse, Version 1.3, can fail in the Simplified Chinese locale (zh_CN)
with the following message:
CDWIC0158E Migration of the TWH_MD to the DB2 version 8 format failed.
In Tivoli Data Warehouse, Version 1.2, the DB2CODEPAGE environment variable
was required. This configuration causes some of the data in the control database
to become corrupted.
Workaround: Run the following updates to the control database to correct the
problem and allow the upgrade to continue.
1. Restore the control database from the backup that you created before
beginning the upgrade.
2. Run these commands from a DB2 command prompt:
update iwh.udpgroup set name=x’444232206953657269657320E78988’
where grouptype=1
update iwh.udpgroup set name=x’444232207A2F4F5320E78988’
where grouptype=2
update iwh.udpgroup set name=x’44423220554442’
where grouptype=3
update iwh.udpgroup set name=x’
E7BB9FE8AEA1E4BFA1E681AFE58F98E68DA2E599A8’
where grouptype=4
update iwh.udpgroup set name=x’
E4BB93E5BA93E5BBBAE8AEAEE4B88DE8A681E4BDBFE794A8E79A84E7A88BE5BA8F’
where grouptype=5
update iwh.udpgroup set name=x’4F4C41502053657276657220E7A88BE5BA8F’
14 Tivoli Data Warehouse Release Notes
where grouptype=6
update iwh.udpgroup set name=x’E69687E4BBB6E7A88BE5BA8F’
where grouptype=7
update iwh.udpgroup set name=x’53514C’
where grouptype=8
update iwh.udpgroup set name=x’E4BB93E5BA93E58F98E68DA2E599A8’
where grouptype=9
update iwh.udpgroup set name=x’E5A48DE588B6’
where grouptype=10
update iwh.udpgroup set name=x’E58583E695B0E68DAEE7A88BE5BA8F’
where grouptype=13
update iwh.udpgroup set name=x’
E59CA8E5A496E983A8E7949FE68890E79A84E7A88BE5BA8F’
where grouptype=16
3. Restart the upgrade by using the Tivoli Data Warehouse installation wizard.v Defect 176311: On AIX remote agents, some log files contain corrupted DBCS
characters. The log files are written in the UTF-8 code page, but are read in the
Shift-JIS code page. After the log files are read in the UTF-8 format, the
characters are displayed correctly.
Workaround: Use the iconv command to convert files with corrupted DBCS
characters to the IBM-943 (Shift-JIS) encoding:
iconv -f UTF-8 -t IBM-943 log_file [ > output_file]
v Defect 176742: When parameters for certain reports are set beforehand and then
you view the reports, the following error occurs:
Illegal pattern character ’y’
v Defect 177109: Some inconsistencies with terminology might be observed with
window titles in InstallShield.
v Defect 177169: Incorrect national characters might be displayed in messages.
v Tivoli Data Warehouse cannot be installed in directories that are named using
the double-byte character set (DBCS).
Workaround: Install Tivoli Data Warehouse in a directory that is named using
the single-byte character set (SBCS).
Chapter 3. Known limitations, problems, and workarounds 15
16 Tivoli Data Warehouse Release Notes
Appendix A. Support information
This section describes the following options for obtaining support for IBM
products:
v “Searching knowledge bases”
v “Obtaining fixes” on page 18
v “Contacting IBM Software Support” on page 18
Learning about education
IBM and its worldwide network of education partners offer a variety of course
types, online, on-site and instructor-led education, covering every aspect of the
Tivoli software portfolio.
View available Tivoli Data Warehouse 1.3 Training at:
Tivoli Software Education:
http://www.ibm.com/software/tivoli/education/
Virtual Skills Center for Tivoli Software:
http://www.cgselearning.com/tivoliskills/
Searching knowledge bases
If you have a problem with your IBM software, you want it resolved quickly. Begin
by searching the available knowledge bases to determine whether the resolution to
your problem is already documented.
Search the documentation
IBM provides extensive documentation that can be installed on your local
computer or on an intranet server. You can use the search function of the PDF to
query conceptual information, instructions for completing tasks, reference
information, and support documents.
Search the Internet
If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem. You can search a variety of resources including:
v IBM technotes
v IBM downloads
v IBM Redbooks™
v IBM developerWorks®
v Forums and news groups
v Google
© Copyright IBM Corp. 2002, 2005 17
Obtaining fixes
A product fix might be available to resolve your problem. You can determine what
fixes are available for your IBM software product by checking the product support
Web site:
1. Go to the IBM Software Support Web site
(http://www.ibm.com/software/support).
2. Under Products A - Z, select your product name. This opens a product-specific
support site.
3. You can learn about fixes and optionally download the fixes.
For more information about types of fixes, see the Software Support Handbook
(http://techsupport.services.ibm.com/guides/handbook.html).
Contacting IBM Software Support
IBM Software Support provides assistance with product defects.
Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2 and WebSphere products that
run on Windows or UNIX® operating systems), enroll in Passport Advantage® in
one of the following ways:
– Online: Go to the following Passport Advantage Web page:
(http://www.lotus.com/services/passport.nsf/
WebDocs/Passport_Advantage_Home)
Click How to Enroll.
– By phone: For the phone number to call in your country, go to the IBM
Software Support Web site
(http://techsupport.services.ibm.com/guides/contacts.html) and click the
name of your geographic region.v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries®, pSeries®, and iSeries™ environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web page (http://www.ibm.com/servers/eserver/techsupport.html).
If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to
the contacts page of the IBM Software Support Handbook on the Web
(http://techsupport.services.ibm.com/guides/contacts.html) and click the name of
your geographic region for phone numbers of people who provide support for
your location.
Follow the steps in this topic to contact IBM Software Support:
1. Determine the business impact of your problem.
2. Describe your problem and gather background information.
3. Submit your problem to IBM Software Support.
18 Tivoli Data Warehouse Release Notes
Determine the business impact of your problem
When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
you are reporting. Use the following criteria:
Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact
on operations. This condition requires an immediate solution.
Severity 2 Significant business impact: The program is usable but is severely limited.
Severity 3 Some business impact: The program is usable with less significant features (not critical to
operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on operations, or a reasonable
circumvention to the problem has been implemented.
Describe your problem and gather background information
When explaining a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can the problem be re-created? If so, what steps led to the failure?
v Have any changes been made to the system? (For example, hardware, operating
system, networking software, and so on.)
v Are you currently using a workaround for this problem? If so, please be
prepared to explain it when you report the problem.
Submit your problem to IBM Software Support
You can submit your problem in one of two ways:
v Online: Go to the ″Submit and track problems″ page on the IBM Software
Support site (http://www.ibm.com/software/support/probsub.html). Enter
your information into the appropriate problem submission tool.
v By phone: For the phone number to call in your country, go to the contacts page
of the IBM Software Support Handbook on the Web
(http://techsupport.services.ibm.com/guides/contacts.html) and click the name
of your geographic region.
If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround for you to implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
IBM product support Web pages daily, so that other users who experience the
same problem can benefit from the same resolutions.
For more information about problem resolution, see Searching knowledge bases
and Obtaining fixes.
Appendix A. Support information 19
20 Tivoli Data Warehouse Release Notes
Appendix B. 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 might 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.
© Copyright IBM Corp. 2002, 2005 21
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 is for planning purposes only. The information herein is subject to
change before the products described become available.
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
illustrate 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
22 Tivoli Data Warehouse Release Notes
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 in softcopy form, the photographs and color
illustrations might not display.
Trademarks
The following terms are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both:
IBM The IBM logo
AIX NetView
DB2 OS/2
DB2 Connect OS/390
DB2 DataJoiner Passport Advantage
DB2 DataPropagator pSeries
DB2 OLAP Server Rational
DB2 Universal Database Rational Rose
developerWorks Redbooks
Distributed Relational Database Architecture RS/6000
Domino Tivoli
DRDA Tivoli Enterprise
eServer Tivoli Enterprise Console
IMS TME
Informix WebSphere
Lotus xSeries
iSeries z/OS
MVS zSeries
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Intel, the Intel Inside logos, MMX, and Pentium are trademarks of Intel
Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft and Windows NT are registered trademarks of Microsoft 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.
Other company, product, and service names may be trademarks or service marks
of others.
Appendix B. Notices 23
24 Tivoli Data Warehouse Release Notes
����
Printed in USA
SC32-1399-01