IBM Optim – Technical Release Notes
Welcome to IBM Optim.
This document contains the
following information:
-
Product Support Policies
-
Special Setup Considerations for UNIX
-
Special Setup Parameters for UNIX
-
Requirements for Viewing Generated Output Files
in Windows and
UNIX
-
Known Problems
-
Documentation Errata
Upon initial installation of IBM Optim, the
following license information can be used
for a 30-day full function trial of IBM
Optim:
Company Name: OPTIMDEMO
Company ID: 388713
Company Password: 9863ZU
License Key: LRIOLG-FVKFPN-STMBJ7-QY7EZS-4ZWSG1
For further License Key information please
go to www.ibm.com/software/wdi
IBM supports operating systems and
third-party products in accordance
with the vendor
support policy. For example, when the Oracle Corporation
discontinues
support for a version of its database, IBM may move
Optim support for Oracle
to Tier 2 for a period of time.
While new features
and software fixes
for discontinued versions of databases will not be
available, Optim
will continue to function with the database.
Please
refer to the Product Support Policies document for more information.
In UNIX, setup does not check to determine
if an instance of the Optim Server
is running as a
daemon and setup will not upgrade components that are
locked by a running
daemon. Therefore, if you are upgrading the Optim Server
on a UNIX platform,
you must first follow the steps to Shut Down the Server
in the Installation
and Configuration Guide.
IBM uses InstallShield
to install Optim on a UNIX OS. By default, the
InstallShield
setup program requires a connection graphical interface.
You may also install from the command line.
Both methods are described
in detail in the
Installation and Configuration Guide as are troubleshooting
tips for a
graphical interface.
If IBM Support asks for trace information during
the Setup process,
you must create an
ASCII file with the following name:
setup.sp
The file should contain the line of text:
is.debug=1
When you install Optim in a Solaris
environment that uses the
Triteal Window Manager
and an error message indicates that
the JVM cannot be
found, it is possible that the Motif widget library is
out of date. Verify
that the Motif widget library is at least libXm.so.4.
Alternately, either use
the OpenWindows Desktop or the Common Desktop
Environment to install the
product.
Trace and diagnostic files generated by
Optim are encoded as UTF8 files.
To correctly view these files in Windows or UNIX,
a UTF8-enabled
editor must be
used. For example, in Windows, Notepad
is a UTF8-enabled
editor. If an editor that is not enables for UTF-8 is
used, any characters
greater than 255
(i.e., 0xFF) or any double-byte characters will not
display properly.
In addition, trace and diagnostic files
generated by Optim are encoded
with the endianess of the operating system where they were created.
- Archive and
Extract processes for IBM DB2 LUW tables associated with an MQT will fail with
an internal error.
This problem can be circumvented by
de-selecting Views from the objects to be extracted.
In situations where this workaround
is not acceptable, contact IBM Optim support to obtain the fix,
OPTM-06.05.01-001.
- When you execute a Load or Insert request
that contains one or more LOB
columns into a Sybase database under Windows
2000, various error
messages and poor performance can result.
In addition, the request can
cause the computer to stop responding
(hang).
Microsoft has determined that this problem
is in Windows and can be
resolved by applying fixes supplied by
Microsoft. For Windows 2000, the
problem is corrected in Service Pack 3.
For more information, please refer to the
appropriate Microsoft Knowledge
Base Articles:
Q296265 - Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;q296265
- When you use Oracle to store the Optim
Directory tables, errors may
occur if the schema name used matches the
names of the tables
(e.g., PSTOBJ2, PSTDBA2, PSTPK2, PSTREL2,
PSTPT2, or PSTAUDIT2).
- If you use a MS SQL Server 2000 database
with a MS SQL Server client
that is earlier than 2000 (e.g., 7.0 or
before) and create indexes with
a DESC clause on any column, the DESC
clause is ignored and no errors
are reported.
To resolve this problem, ensure that you
have installed the MS SQL
Server 2000 client on any machine that is
used to perform a CREATE task.
The Archive User Manual and the Optim online help
incorrectly state,
"The Archive File Maintenance command
can only be run in a Windows
environment."
Note that the Archive File Maintenance command can be run
in all
Optim-supported platforms.