Release notes for IBM Information Server Version 8.0.1 Fix Pack 1a

IBM Information Server 8.0.1 Fix Pack 1a replaces Fix Pack 1 and allows additional components to be installed after Fix Pack 1a is installed.

If you have previously installed Fix Pack 1, install Fix Pack 1a only if you need to install additional IBM Information Server components, such as WebSphere^® Information Analyzer. If you have previously installed Fix Pack 1, you do not need to install Fix Pack 1a on systems that do not have a domain layer. If you have previously installed Fix Pack 1 and you applied additional patches before installing Fix Pack 1a, then you must reinstall those patches. When reinstalling these patches you must use a different procedure than you used to initially install them. You must use the specific procedure described in the Reinstalling patches after Fix Pack 1a is installed section.

The fix pack updates for the client layer are provided for the Microsoft^® Windows^® XP, Microsoft Windows Vista, and Microsoft Windows Server 2003 operating systems. The fix pack updates for the server and domain layers are provided for Windows Server 2003, Red Hat Linux^® Advanced Server Enterprise 4.0, IBM AIX^® 5.2 and 5.3, Solaris 9 and 10, and SUSE Linux Enterprise Server 10 on Intel^® x86.

Fix Pack 1a must be installed on all computers that run the client, domain, and server layers.

A separate fix pack package is provided for each operating system. IBM Information Server 8.0.1 Fix Pack 1a installation packages have self-describing names with the .ispkg file name extension, such as is_801.fp1a.redhat.ispkg and is_801.fp1a.win.ispkg.

The client, domain, and server layers can coexist on one physical computer that is running the Windows Server 2003 operating system. The client, domain, and server layers also can be distributed across multiple computers. For example, the client layer can exist on a computer running the Windows XP operating system, while the domain and server layers exist on separate computers running the AIX operating system.

This distributed architecture requires installation of Fix Pack 1a on each computer where IBM Information Server is installed. For distributed installations, you must install Fix Pack 1a on each computer to ensure a proper upgrade. Install Fix Pack 1a on the domain layer first, then the server layer, and then the client layer.

To use different versions of WebSphere DataStage^® clients with Fix Pack 1a, you must install the Multi-Client Manager program. See the Multi-Client Manager release notes that are contained in the mcm_801.fp1a.win.zip file for details on installing and using the Multi-Client Manager program with Fix Pack 1a.

For information about hardware and software compatibility, see the detailed system requirements document at www.ibm.com/support/docview.wss?uid=swg27008923.

IBM Information Server 8.0.1 Fix Pack 1a adds SUSE Linux Enterprise Server 10 on Intel x86 support for the server and domain layers.

Software requirements

Before you install IBM Information Server 8.0.1 Fix Pack 1a, ensure that your computer meets the following software requirements.

JRE bundled with IBM Information Server Version 8.0.1

The JRE that is bundled with IBM Information Server is required for fix pack installation. Fix Pack 1a installation will fail if the JRE that is bundled with IBM Information Server is not used. The JRE must be run from one of the directories shown below. These paths assume that the product is installed in the default location.

Note: Your path will vary if you installed IBM Information Server in a different location.

Windows

C:\IBM\InformationServer\ASBNode\apps\jre\bin

C:\IBM\InformationServer\_jvm\jre\bin

C:\IBM\WebSphere\AppServer\java\bin

Note: c:\IBM\InformationServer\WebSphere\AppServer\java\bin for installation on the domain layer.

AIX, Solaris, Red Hat Linux, SUSE Linux

/opt/IBM/InformationServer/ASBNode/apps/jre/bin

/opt/IBM/InformationServer/_jvm/jre/bin

/opt/IBM/WebSphere/AppServer/java/bin

Note: For AIX operating systems use /opt/IBM/WebSphere/AppServer/java/bin for installation on the domain layer.

To add the JRE to the executable path, issue the following command:

export PATH=/opt/IBM/InformationServer/ASBNode/apps/jre/bin:$PATH

To verify that the JRE is in the correct path, issue the following command:

which java

If you installed IBM Information Server in a different location make sure that the JRE is in the installed directory structure.

Teradata client version 8.2.0.2

The Red Hat Linux Teradata connector requires Teradata client version 8.2.0.2 with the papi8200.08.02.00.02 efix. Before Fix Pack 1a is installed, download the papi8200.08.02.00.02 efix from www.ncr.com.

During efix installation, select option 2 to install the library built with the gcc 3.3 compiler of the 32-bit Teradata PT API library. The Teradata connector requires the library that is installed by option 2.

UNIX^® systems umask setting

On UNIX systems, set the umask value to 022.

Hardware requirements

Disk usage

350 MB of disk space is required to install Fix Pack 1a.

This section describes how to install IBM Information Server 8.0.1 Fix Pack 1a.

To install the WebSphere MetaBrokers and bridges fix pack update, see Installing WebSphere MetaBrokers and bridges.

To install the Multi-Client Manager program, see Installing the Multi-Client Manager program.

Restrictions

• The Fix Pack 1a installer is a Java™ application that requires the JRE 1.4.2 that is installed with IBM Information Server.
• You must reinstall Fix Pack 1a if you install additional IBM Information Server product components after you install Fix Pack 1a. You can install product components, such as WebSphere Information Analyzer, on IBM Information Server 8.0.1 after the fix pack is installed, but you must reinstall Fix Pack 1a to update the newly installed components.
• For distributed installations you must install Fix Pack 1a on all layers. Follow this installation sequence:
  1. Domain
  2. Server
  3. Client
• On UNIX, the fix pack must be installed by the root user.
• For server and domain layers on Windows, the fix pack must be installed by a user with administrator privileges. Use the same user name and password you used to install IBM Information Server to ensure you have the correct privileges.
• The fix pack installation takes about 25 minutes to perform and must occur with no interruptions.

Preparing your system for installation

IBM Information Server 8.0.1 installed on client, domain, and server layers

IBM Information Server 8.0.1 must be installed on the client, domain, and server layers before you install Fix Pack 1a. For new installations on the client layer, you can install Fix Pack 1a on the domain and server layers first, and then install IBM Information Server 8.0.1 on the client layer, and then install Fix Pack 1a on the client layer.

Note: You can also install Fix Pack 1a on IBM Information Server Fix Pack 1 installations. You must install Fix Pack 1a on IBM Information Server Fix Pack 1 installations if you want to add product components, such as WebSphere Information Analyzer, to existing installations.

Shut down IBM Information Server

Shut down IBM Information Server before you perform a full backup.

Back up content

Before you install IBM Information Server 8.0.1 Fix Pack 1a, perform a full backup of all IBM Information Server content, including:

• Repository (xMeta and WebSphere Information Analyzer databases)
• WebSphere Application Server installation. For example, C:\IBM\WebSphere\AppServer on Windows or /opt/IBM/WebSphere/AppServer on UNIX.
• IBM Information Server installation (the IBM Information Server folder). For example, C:\IBM\InformationServer on Windows or /opt/IBM/InformationServer on UNIX.

Start IBM Information Server

Start IBM Information Server.

Increase Inactive Session Timeout value for Global Session Properties

Increasing the value of the Inactive Sessions Timeout is recommended before you install Fix Pack 1a on slower systems. Increase the value of the Inactive Sessions Timeout to 7200 seconds (60 minutes) to ensure a successful installation. Follow these steps to change the value of the timeout to avoid being disconnected automatically during Fix Pack 1a installations:

1. Log in to the IBM Information Server Web console.
2. Click the Administration tab.
3. In the Navigation pane, select Session Management > Active Sessions.
4. In the Active Sessions pane, click Global Session Properties.
5. Specify 7200 for the Inactive Session Timeout field.
6. Click Save and Close.
   Note: You can reset the Inactive Sessions Timeout value to your original value after you install Fix Pack 1a.

Ensure that the server and domain are running

To ensure that the server and domain are running:

1. In a browser window, enter http://host_server:9080 where host_server is the name or IP address of the domain server.
2. Log in by using the IBM Information Server Administrator user name and password (this is not the WebSphere Application Server password).

Ensure that the database for IBM Information Server is running and that the following products and services are running properly

The database for IBM Information Server and other products and services must be running for the Fix Pack 1a installation to succeed.

• IBM DB2, Oracle, or SQL Server database for IBM Information Server
• WebSphere Application Server
• Logging Agent
• Application Services Backbone (ASB) Agent
• WebSphere DataStage engine

Ensure that IBM Information Server 8.0.1 is not in use

Do not perform any actions on IBM Information Server components during Fix Pack 1a installation. The server and domain layers of IBM Information Server 8.0.1 must be fully dedicated to the installation process. Do not run any other applications or attempt to access any IBM Information Server services during the installation.

During Fix Pack 1a installation, the WebSphere Application Server and IBM Information Server are automatically shut down and restarted multiple times. Do not interfere with the automatic shutting down and restarting of WebSphere Application Server and IBM Information Server .

Note: After Fix Pack 1a installation is complete, you must restart the Windows computers for the server and domain layers. Windows computers that have only the client layer installed do not have to be restarted.

Shut down clients

Ensure that no clients are running IBM Information Server 8.0.1, including WebSphere DataStage and QualityStage Administrator, WebSphere DataStage Designer, and WebSphere Information Services Director.

Login requirements

To install Fix Pack 1a on server and domain layers, you must log in to the computer with administrator rights.

• On UNIX, log in as the root user to install the fix pack.
• On Windows, log in as a system administrator to install the fix pack. Use the same user name and password you used to install IBM Information Server to ensure you have the correct privileges.

Important: Do not log in as dsadm to install the fix pack.

Installing Fix Pack 1a

The Fix Pack 1a installation supports two installation modes on all operating systems: installation wizard and command line. You install the MetaBrokers and bridges fix pack update and the Multi-Client Manager fix pack update after you install and verify the main fix pack installation.

The path in the following commands assumes that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location. The user name and password might also be different. Use the correct path, user name, and password for your system. You must use the same user name and password that you used to install IBM Information Server.

Command line parameters

The IBM Information Server client installation does not require the IBM Information Server administrator user name or password.

-i

IBM Information Server installation root directory

-p

The file name of the Fix Pack 1a installation package

-user

IBM Information Server administrator user name

-password

IBM Information Server administrator password

-verbose

Includes more information in the console output

-console

Install without opening the installation wizard.

-force

Force reinstallation of a patch after you install Fix Pack 1a. See Reinstalling patches after Fix Pack 1a is installed.

or

Force reinstallation of Fix Pack 1a to update new components. See Adding components after Fix Pack 1a is installed.

Important: You must enter all command line options and required parameters (except for the -verbose option) to use the -console parameter for installation on server and domain layers.

Command line installation on AIX, Solaris, Red Hat Linux, and SUSE Linux operating systems

The fix pack package is_801.solaris.ispkg shown in the following command is appropriate for the Solaris operating system. Use the fix pack package appropriate for your operating system.

Command line installation on Windows operating systems

Wizard installation on AIX, Solaris, Red Hat Linux, and SUSE Linux operating systems

The paths in the following command assume the product is installed in the default location. Your paths will vary if you installed IBM Information Server in a different location. Use the correct paths to install Fix Pack 1a.

To install Fix Pack 1a in wizard mode on AIX, Solaris, Red Hat Linux, and SUSE Linux operating systems, you must make sure your X11 client is running. To ensure that your X11 client is running, set your DISPLAY variable properly, and verify that the X Window System application can be started.

Wizard installation on Windows operating systems

Verifying installation

After you install Fix Pack 1a, verify the installation. The paths in the following commands assume the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

• On Windows operating systems, restart the computer where you installed Fix Pack 1a on server and domain layers.
• Start IBM Information Server client applications such as WebSphere DataStage and QualityStage Administrator, WebSphere DataStage and QualityStage Designer, WebSphere DataStage and QualityStage Director, IBM Information Server Web console, and so on.
• Verify that the Version.xml file includes SUCCESS in the version history.
  • Windows operating systems: C:\IBM\InformationServer\Version.xml
  • AIX, Solaris, Red Hat Linux, SUSE Linux operating systems: /opt/IBM/InformationServer/Version.xml
• Review the ISinstalltimestamp.txt log file (where timestamp is the timestamp in YYYY.MM.dd.hh.mm.ss format) to ensure that FATAL and SEVERE errors are not present.
  • Windows operating systems: C:\IBM\InformationServer\logs\ISinstalltimestamp.txt
  • AIX, Solaris, Red Hat Linux, SUSE Linux operating systems: /opt/IBM/InformationServer/logs/ISinstalltimestamp.txt
• Ensure that you can log in and perform the existing functions in your IBM Information Server environment.

Post-installation backup

Perform a full backup of the IBM Information Server installation. See Back up content for details.

Installing WebSphere MetaBrokers and bridges

If you install the WebSphere MetaBrokers and bridges update, you must install it after the IBM Information Server 8.0.1 Fix Pack 1a installation is complete and that you have verified the installation.

1. Log in as an administrator to the system where you installed Fix Pack 1a.
2. Extract the contents of the mbb_801.fp1.win.zip file.
3. Open the directory where you extracted the .zip file and double-click the setup.exe file.
4. Follow the instructions in the wizard to install WebSphere MetaBrokers and bridges.
5. Read the MetaBrokers and bridges release notes that are contained in this .zip file for details on using MetaBrokers and bridges with the Metadata Workbench.

Installing the Multi-Client Manager program

Install the Multi-Client Manager program after you install Fix Pack 1a only if you install IBM Information Server 8.0.1 and IBM Information Server 8.0.1 Fix Pack 1a on the same computer and you want to use the Multi-Client Manager program to switch between these specific versions of the WebSphere DataStage client programs.

Do not install the Multi-Client Manager program for any other reason. For example, if you want to switch between IBM Information Server 8.0.1 Fix Pack 1a and IBM Information Server 7.5.3, do not install this Multi-Client Manager program. Use your existing Multi-Client Manager program.

If you install the Multi-Client Manager program, you must install it after the IBM Information Server 8.0.1 Fix Pack 1a installation is complete and you have verified the installation.

1. Log in with administrator access to the system where you installed Fix Pack 1a.
2. Extract the contents of the mcm_801.fp1a.win.zip file.
3. Read the Multi-Client Manager release notes that are contained in the mcm_801.fp1a.win.zip file for details on installing and using the Multi-Client Manager program with Fix Pack 1a.

Reinstalling patches after Fix Pack 1a is installed

This section applies only if you have previously installed Fix Pack 1 and applied patches after Fix Pack 1 was installed. After you install Fix Pack 1a, you must reinstall the patches that were applied after Fix Pack 1 was installed.

Review the Version.xml file to determine previously installed patches

Confirm what patches were installed after Fix Pack 1 was installed by viewing the Version.xml file.

• Windows operating systems: C:\IBM\InformationServer\Version.xml
• AIX, Solaris, Red Hat Linux, SUSE Linux operating systems: /opt/IBM/InformationServer/Version.xml

Patch history appears in the History section of the Version.xml file and is similar to the following example:

<Sequence description="Rollup Patch 7. Summary ecase 126607" id="2" 
installLocation="" lastUpdateDate="Thu Jan 10 13:43:55 EST 2008" patch="126607a" 
rollback="C:\IBM\InformationServer\Updates\126607a" status="Success" version="" />  

Reinstall patches

The patch installer that was included with all previously released patches does not allow these patches to be reinstalled when other patches, or Fix Pack 1a, have been installed later. The installer used in Fix Pack 1a allows you to override this behavior. When reinstalling patches, follow original patch installation instructions with these required modifications:

1. Use the updater.jar delivered with Fix Pack 1a.
   Important: Do not use the updater.jar that was released with the patch.
2. Invoke the patch installer directly from the command line.
   Important: Do not use the Install_Patch.sh or Install_Patch.bat scripts that were released with the patch.
3. Add the -force option to the command line that you use to invoke the patch installer.

For example, use the following command to reinstall patch_128727_aix.ispkg on AIX:

/opt/IBM/InformationServer/ASBNode/apps/jre/bin/java -jar updater.jar -i /opt/IBM/InformationServer -p patch_128727_aix.ispkg -user admin -password manager -console -force

Adding components after Fix Pack 1a is installed

Known IBM Information Server 8.0.1 Fix Pack 1a installation problems

At time of publication, the following problems are known for the Fix Pack 1a installation.

Fix Pack 1a installations fails on OutOfMemory exception in WebSphere Application Server

Fix Pack 1a installation might fail if the maximum heap size is not sufficient for that system and an OutOfMemory exception occurs in WebSphere Application Server. Some systems running WebSphere Application Server might require increasing the heap size to successfully install Fix Pack 1a. The default maximum heap size allocation of WebSphere Application Server process is automatically set to 768 MB during IBM Information Server installation.

Workaround

Set the maximum heap size property to 1280 MB before installing Fix Pack 1a.

Follow these steps to change the maximum heap size allocated to the application server process:

1. Log in to the WebSphere administrative console as the WebSphere administrator.
2. In the topology tree, expand Servers and click Application Servers.
3. Click the server1 link (where server1 is the name of the application server you want to configure).
4. Under Server Infrastructure, expand Java and Process Management.
5. Click Process Definition.
6. Under the Additional Properties section, click Java Virtual Machine.
7. In the Maximum Heap Size field, type 1280.
8. Click Apply or OK.
9. Install Fix Pack 1a.
10. Reset the value of Maximum Heap Size to your original value after you install Fix Pack 1a.

(eCase 126922)

Fix Pack 1a installation fails on Solaris when NLS is enabled and locale is Spanish

Fix Pack 1a cannot be installed on Solaris systems when NLS is enabled and the locale is es_ES (or any other Spanish locales designated with es_). Installation fails with the error message:

A license file was not created.

Workaround

Install Fix Pack 1a with an English language locale, such as en_GB or en_US.

Successful Fix Pack 1a installation on SUSE Linux Enterprise Server 10 on Intel x86 includes warning message in log

On SUSE Linux Enterprise Server 10 on Intel x86, successful Fix Pack 1a installations might include the following warning message in the Fix Pack 1a installation log:

Error: cat: /scratch/Ascential/DataStage/DSEngine/.asbnode: No such file or directory

This warning message appears in the following scenario:

• DataStage engine with NLS disabled is upgraded from WebSphere DataStage 7.5.3 to WebSphere DataStage 8.0.1
• Configuration includes a remote DB2^® repository
• ITAG with NLS enabled is installed on SUSE Linux Enterprise Server 10 on Intel x86 with the following DataStage Server values:
  • ITAG value not equal to the default ADE
  • Port number not equal to the default 31538
• The selected product components to install are:
  • DataStage and QualityStage
  • Information Analyzer
  • Business Glossary

Fix Pack 1a is installed successfully with the error message.

Workaround

Ignore the error message in the Fix Pack 1a installation log.

(eCase 128216)

SEVERE error appears in the installation log

IBM Information Server installations that include WebSphere DataStage might generate SEVERE error message in the installation log file. The following error message can be ignored:

SEVERE: Exit Code: 0, Info: Stopping JobMonApp JobMonApp has been shut down.
DataStage Engine 8.0.1.0 instance "801" has been brought down., Error: DeadLock Daemon shutdown

Workaround

This message does not require action. Ignore this message. Any other SEVERE error messages indicate that the Fix Pack 1a installation did not succeed. Contact IBM customer support.

(eCase 128341)

Installing additional components fails when Java executable path is set for Fix Pack 1a

After Fix Pack 1a is installed, the installation of additional components will fail if the same command or console window is used. The IBM Information Server installation that is used to add additional components incorrectly resolves the JRE by appending /jre to the Java present in the path.

Workaround

Close the command or console window after you install Fix Pack 1a. Open a new command or console window before you install additional IBM Information Server product components.

(eCase 128006)

Invalid Version.xml file causes Fix Pack 1a installation to fail

After successful installations, the Version.xml file includes SUCCESS in the version history. The only valid entries in the Version.xml file are SUCCESS and PARTIALSUCCESS. Do not edit this file.

Workaround

If the Version.xml file is edited or becomes corrupt, delete this file before you install Fix Pack 1a. Move or copy this file to retain a record of what patches were previously installed. Move or copy the Version.xml and then delete the original Version.xml file.

(eCase 128499)

Fix pack installation fails when installation is unable to stop the ASBAgent service

During Fix Pack 1a installation, the WebSphere Application Server and the IBM Information Server are automatically shut down and restarted multiple times. The fix pack installation fails when the ASBAgent service is not stopped in one of the following scenarios:

• The installer fails to stop the ASBAgent service using a net stop command. The installation log confirms this failure with the following warning:

  WARNING: java.lang.Exception: Information Server can not be shut down in a timely manner, 
  please reboot windows and complete the rest of the installation.

• The installer fails to stop the ASBAgent process after a shutdown request times out. Contact Microsoft for further information when the installation log confirms this failure with the following warning about a corrupted Windows component in the system:

  taskkill.exe -Unable to Locate Component Window appears with the message. This application 
  failed to start because framedyn.dll was not found. Re-installing the application may 
  fix the problem

Workaround

Use the Windows Task Manager to manually stop the ASBAgent process. If manually stopping the ASBAgent process does not work, restart your computer and then restart the fix pack installation.

(eCase 122332)

Fix pack installation fails if the port for the IBM Information Server domain has been changed in WebSphere Application Server

If the port for the IBM Information Server domain computer was modified in WebSphere Application Server after the original installation, the Fix Pack 1a installation fails with an authentication error. The following error message appears in the log:

SEVERE:
com.ibm.is.install.update.installer.ConsoleUpdateDriver Failed to authenticate 
username/password, please ensure your application server is running, and ensure 
you have entered valid Information server administrator user name/password. Return 
message is: null

Workaround

Confirm that the value in the vpd.script file reflects the actual port being used for IBM Information Server before installing the fix pack.

1. Locate the vpd.script file for your system.
   The following table lists the directory by operating system to locate the vpd.script file on your system.

   Table 2. Directory of vpd.script file by operating system.

   Operating system	Directory
   Windows	C:\Program Files\Common Files\InstallShield\Universal\IBM\InformationServer\Gen2\_vpddb
   AIX	/usr/lib/objrepos/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
   Solaris	/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
   Red Hat Linux and SUSE Linux	/root/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb

2. Edit the /root/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb/vpd.script file to ensure the port is correct.
   Search for LPV_ASB_PORT to locate the port configuration entry that is similar to:

   INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES(211,'LPV_ASB_PORT','9080',NULL,'false')

3. If the port is incorrect, change the value to the port being used.
4. Save the vpd.script file.
5. Restart the installation.

(eCase 126428)

Network failure occurs when attempting to locate the domain controller

Installation succeeds when run by the local administrator, but fails when run by another user who is a member of the local administrator group.

Workaround

Log on as local administrator and reinstall in a stable network environment.

(eCase 103336)

Known IBM Information Server problems

At time of publication, the following information describes the currently known limitations, problems and workarounds for IBM Information Server 8.0.1 Fix Pack 1a. Any limitations and restrictions might or might not apply to other releases of the product.

WebSphere Application Server

(eCase 125865)

XMeta user ID cannot exceed 64 characters

(eCase 116044)

Administration Scheduling reports that are run on a locale other than English (for example, Japanese) generate report results that might not display the pie charts used in the detail sections of the report output correctly

There is no known workaround for this problem.

(eCase 114153)

Processing large volume of data causes a shadow window to display

A shadow window is displayed when the IBM Information Server Web console creates an application with a large volume of data or more than 100 operations.

(eCase 114963)

Crashes occur on Windows operating systems when a data entry is displayed in a log view after date format is changed

Windows allows you to configure how dates are displayed in Regional and Language Options in the control panel. A short date format that uses a pattern with the forward slash (/) separator and only M or MM for months, d or dd for days, yy or yyyy for years is supported. If your default options are different or if you have modified the default options, the application might not function properly when a date entry field is displayed.

(eCase 115787)

Out of memory exceptions in log views containing large number of log events

While using the IBM Information Server Web console to view logs, out of memory exceptions might occur when retrieving logs with large numbers of events, the number of events that can be returned for a log view are limited in the console. This limit is specified in the file InformationServer\Clients\ISC\isc.exe.config using the key logging.max.view.events in the appSettings section. The property is initially absent from the properties file, causing the default limit to be 10000.

Workaround

Add the appSettings section to the isc.exe.config properties file right before the </configuration> tag. Specify the desired limit as the value for this key. Set the value to -1 to ignore the limit (not recommended). For example:

<appSettings>
	<add key="logging.max.view.events" value="-1" />
</appSettings>

(eCase 120056)

IBM Information Server Web console alert occurs when Advanced Searches filter with Start Date and End Date

(eCase 123944)

Task execution summary report output incorrectly uses 12-hour format

The output of the Task execution summary reports in the Administration > Scheduling folder incorrectly shows the start and end time in a 12-hour date format instead of 24-hour date format. This discrepancy might lead to some confusion when comparing the values to the start and end date/time report parameters criteria that are expressed in 24-hour date/time format.

(eCase 116301)

Delay when viewing a very large number of log events on the IBM Information Server Web console

Workaround

Filter the log events to limit the number of log events displayed. You can filter by time interval, date range, category, severity level, message or context item values.

(eCase 120444)

Read and write permissions required for the registered_servers.xml file

The registered_servers.xml file in the InformationServer\ASBNode\conf directory requires read and write permissions on all IBM Information Server client and server systems.

(eCase 119620)

User interface differences between IBM Information Server Web console and Web client

(eCases 123813 and 122581)

Information Server Reporting Guide gives incorrect information

Only the IBM Information Server Web console supports all report types from all suite activities and modules. The console supports a smaller set of reports. Either tool can be used to view a report, but you cannot run or edit a report which was created by the IBM Information Server Web console. You cannot run or edit reports from the IBM Information Server console that were created by the IBM Information Server Web console.

(eCase 123706)

Report headers are not displayed

Report headers are not displayed when the report captures no records for Logging reports under the Administration folder.

(eCase 116296)

Report is terminated when the report start date is greater than the stop date

When creating a Logs messages by date range report, if the start date report parameter is set to a value greater than the end date report parameter, the report will terminate when run. No records are retrieved and no feedback is provided.

(eCase 116297)

Error from Business Objects might pop up during import on Windows Server 2003 Business Object client environments

Workaround

Click to proceed through the errors and the import succeeds without error.

(eCase 121979)

Report metadata is not connected to OLAP metadata when importing from Business Objects

Report metadata imported using the Business Objects file-based bridges are not properly connected to OLAP metadata that is also imported with Business Objects file-based bridges when the Repository authentication mode option setting is Standalone.

Workaround

Use Enterprise authentication mode.

Open the report file using Business Objects to ensure that the report you want to import has access to the Business Objects Universe it is based on. Importing of linkages might fail when access errors are reported by Business Objects.

(eCase 124554)

OLAP models and report definitions are not imported by business intelligence bridges with default Export logical objects option

When importing metadata from business intelligence tools, the setting for the Export logical objects option in the Additional Category section of the Import Export Manager Parameter Selection dialog box is not enabled by default. This option is required when importing from business intelligence tools because physical data resource metadata, such as database tables, is imported. The Export logical objects option under the Additional Category section of the Import Export Manager Parameter Selection dialog box is required to additionally import OLAP models and report definitions.

Workaround

Enable the Export logical objects option in the Additional Category section of the Import Export Manager Parameter Selection dialog box.

(eCase 124550)

Operational Locator Matching is case sensitive

The matching criteria for DataResourceLocators is case sensitive and causes the Host/Computer name portion of the locator that is passed in as lowercase not to match one that is in all uppercase.

(eCase 119367)

Importing an IBM Rational^® Data Architect glossary model (.ndm file) into WebSphere DataStage using bridges fails

WebSphere DataStage does not support importing glossary metadata.

Workaround

• Use the IBM Rational Data Architect MetaBroker^® from the Import Export Manager to import glossary metadata, or
• Export glossary metadata directly from IBM Rational Data Architect to the IBM Information Server.

To use either workaround, IBM Rational Data Architect must be installed on the same machine as the Import Export Manager. The installation must include the Metadata Server Integration feature.

(eCase 120725)

System Architect bridges are non-functioning

Import of logical and conceptual data modeling artifacts is not supported. IBM Information Server supports import of physical objects such as Database, Table, and Column.

(eCase 123453)

Installation summary incorrect

Installation summary incorrectly shows that IBM WebSphere Federation Server will be installed even if Federation Server is not included in the license and it was not selected for installation.

Workaround

Request a license that includes Federation Server.

(eCase 118526)

Fixed IBM Information Server problems

This table lists the IBM Information Server problems that are fixed with IBM Information Server 8.0.1 Fix Pack 1a.

Known WebSphere DataStage problems

At time of publication, the following information describes the currently known limitations, problems, and workarounds for WebSphere DataStage. Any limitations and restrictions might or might not apply to other releases of the product.

Teradata connector fails to insert data into table with binary columns

The insert data operation fails when Teradata connector stage attempts to insert data in a table that contains columns of binary types (BYTE, VARBYTE, or BLOB) and there is no data available on an input link for these columns (zero-length data). An error message similar to the following message appears in the log:

Teradata_Connector_3,0: Internal Error: (len > 0): api/rawfield.C: 272

Workaround

Provide data in the input link for each record in the columns when the target table contains binary columns or exclude columns with zero-length data from the insert statement.

(eCase 128050)

Unable to run XML Input Stage on AIX

Jobs terminate because they fail to load the xmli.so library file. Both server and parallel jobs are terminated.

Workaround

Contact IBM Support for help with this issue.

(eCase 122076)

WebSphere MQ connector cannot connect to WebSphere MQ 6.0 in client or server mode

If any of the following errors occur, follow the instructions in the workaround.

• Error IIS-CONN-WSMQ-000005 is listed in the log file.
• Connection within the connector stage results in one of the following errors:
  • In Windows: An exception occurred while trying to receive the response from the handler: An exception was received from the handler: System call LoadLibraryEx() failed with OS error 126 (The specified module could not be found.)
  • In UNIX: An exception occurred while trying to receive the response from the handler: An exception was received from the handler: System call dlopen() failed with OS error 2 (No such file or directory)

Workaround

Make the WebSphere MQ libraries accessible to the connector. By default, the libraries are in the following directory. Contact your WebSphere MQ Administrator if you cannot find the libraries in these paths.

• Windows: C:\Program Files\IBM\WebSphereMQ\bin
• UNIX: /opt/mqm/lib

After you identify the directory location of the WebSphere MQ libraries, modify the path environment variable to include the appropriate directory for the user that runs the connector process.

The path is in one of these environment variables:

• Windows: Path
• AIX: LIBPATH
• HP-UX: SHLIB_PATH
• Solaris/Linux: LD_LIBRARY_PATH

(eCase 120292)

When using the Teradata connector, the Metadata Importer (Connector Wizard) method of importing metadata might not work for Asian language character sets

Workaround

1. Click DataStage Designer > Import > Table Definitions.
2. Click Plug-in Metadata Definitions or click Orchestrate Schema Definitions to import table definitions from a variety of data sources.

(eCase 123832)

When using the Teradata connector, the WebSphere DataStage 4-byte float is not the same as Teradata 8-byte float and cause write jobs to insert incorrect float values

If you write a float value and then read that value, the result might not be identical to the original value that was written. This is because WebSphere DataStage uses a 4-byte float, whereas Teradata uses an 8-byte float.

Workaround

Modify the job to use a double float. WebSphere DataStage uses an 8-byte double float, so this matches the Teradata float.

(eCase 123831)

When using the Teradata connector on SUSE Linux Enterprise Server 10 on Intel x86, Unicode is not supported

The Unicode character set is not supported when using the Teradata connector on SUSE Linux Enterprise Server 10 on Intel x86.

(eCase 127970)

View Data exception when Generate SQL = YES

View data functionality is not working from within the connector stage editor when the property Generate SQL is set to Yes. Clicking the View data hyperlink results in an error.

Workaround

Set Generate SQL to No and enter the statement manually or use the SQL Builder. Alternatively, View data functionality is accessible from the Connector Import Wizard.

(eCase 123370)

ODBC Connector problem on AIX when writing to CLOB data

The job can hang indefinitely during the write operation.

Workaround

Use an alternate stage.

(eCase 117097)

DB2 API extract and date handling of type 0001-01-01 problem

When DB2 date values are represented by the default value of 0001-01-01, these values are incorrectly read as an Integer equivalent of -718432 (instead of 0). PX Jobs reading these values result in joblog warnings similar to

APT_CombinedOperatorController,0:Resource bundle corresponding to message key DSTAGE-TODC-00103 not found! Check that DSHOME or APT_RESPATH is set. and DB2_UDB_API_0,0: ?? (1; 0; 1721424) 

This causes zero records to be processed.

Workaround

Set the Date column to CHAR.

(eCase 118621)

Error loading orchoracle when using Oracle Enterprise stage

Workaround

Type the following command to load the Oracle library correctly:

PX_DBCONNECTHOME=/scratch/IBM/InformationServer/Server/DSComponents;export PX_DBCONNECTHOME  - $ ./install.liborchoracle

(eCase 115580)

Parallel job with Java Client stage does not work

Workaround

Set the DSHOME, DATASTAGE_JRE and DATASTAGE_JVM environment variables as follows (adjust appropriately per install):

For Windows operating systems:

1. Set DATASTAGE_JRE

   DATASTAGE_JRE=$ASBNode/apps/jre

2. Set DSHOME

   DSHOME=C:\IBM\InformationServer\Server\DSEngine

3. Modify LIBPATH inside dsenv

   LIBPATH=$ASBHOME/jre/bin/sovvm before $ASBNode/apps/jre/bin

4. Do not set DATASTAGE_JVM.

For Linux, Solaris, and UNIX operating systems:

1. Set DATASTAGE_JRE

   DATASTAGE_JRE=$ASBNode/apps 

2. Set DSHOME

   DSHOME=/opt/IBM/InformationServer/Server/DSEngine

3. Set DATASTAGE_JVM

   DATASTAGE_JVM=jre/bin/j9vm  

(eCase 118191)

Chinese locale zh_CN.EUC on Solaris is not supported

Workaround

On Solaris, the locale should be set to the zh_CN.GBK locale, which is a superset of the older zh_CN.EUC locale.

(eCase 117549)

Chinese installation not supported for Linux environment

UTF-8 locale on Chinese Linux systems is not supported. Only zh_CN.GB2312 is supported.

(eCase 114895)

Shared Metadata Management allows multiple databases to be created under the same host using the same database name and instance

(eCase 115223)

In SQL Builder, selected columns are not dragged to the update column selection grid for Upsert Mode/Order as Update then Insert

(eCase 115234)

In SQL Builder, the update values are lost when Validation is ON

In update column grid, the update values are lost when values are added to the respective select columns. This problem is seen when the Validation button on the Toolbar is turned ON before making the query.

Workaround

Turn the Validation button OFF before building the query.

Note: The default state of the Validation is OFF.

(eCase 116587)

In SQL Builder, certain Oracle 9i functions are displaying an error

These functions are not supported.

(eCase 115989)

Oracle Enterprise: Making a delete statement after making an upsert statement results in SQL Builder opening in upsert mode

Building a DELETE query after making an upsert causes the wrong SQL Builder window to open with the Insert, Update and SQL tabs.

Workaround

To build a DELETE query after making an upsert, cancel and come back to the Stage Editor, and then invoke SQL Builder for DELETE.

(eCase 116968)

Creating a project using the Administrator is very slow when using the default kernel parameters

Workaround

Use the recommended settings to configure the kernel parameters on Solaris.

1. Make a backup copy of /etc/system before you modify it.
2. Update /etc/system with the suggested kernel parameters and values.
3. Restart the computer.

Suggested kernel values for installing WebSphere Application Server on Solaris [1]:

set shmsys:shminfo_shmmax = 4294967295
set shmsys:shminfo_shmseg = 1024
set shmsys:shminfo_shmmni = 1024
set semsys:seminfo_semaem = 16384
set semsys:seminfo_semmni = 1024
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmns = 16384
set semsys:seminfo_semmsl = 100
set semsys:seminfo_semopm = 100
set semsys:seminfo_semmnu = 2048
set semsys:seminfo_semume = 256
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 65535

Suggested kernel values for db2osconf:

set msgsys:msginfo_msgmni = 2560
set semsys:seminfo_semmni = 3072
set shmsys:shminfo_shmmax = 5747768524
set shmsys:shminfo_shmmni = 3072

(eCase 116480)

Classic Federation stage does not support parameter array

The default insertarraysize should be 1 instead of 2000. (eCase 116896)

Parallel job not supported when running jobs from WebSphere Information Services Directory

It is not possible to run a Parallel job that contains either a Server Shared Container or a Basic Transformer stage when those stages are connected to a WebSphere Information Services Director Input stage. The Parallel engine produces a warning similar to the following: Operator nnn is not wave aware; the operator is reset and rerun on each wave if multiple waves present.

(eCase 117012)

Unable to import metadata from IBM WebSphere Metadata Server database

(eCase 117747)

Datasets created in prior versions cannot be modified.

Modification (append, truncate, overwrite) is NOT supported, and production of backward compatible datasets is not supported when upgrading from one major version to another (7.0 and later to 8.0 and later). READING of datasets produced by the prior version is supported.

(eCase 118650)

IBM XL C/C++ Enterprise Edition for AIX, V9.0 compiler is not supported

(eCase 122662)

Invalid Search Expression alert is displayed sequentially when you click the Refresh button

Error message is displayed when an invalid search expression is entered when using the SQL builder utility.

Workaround

Click the Refresh icon on toolbar.

(eCase 115991)

Errors result when switching between client and server

When using the MQ Connector, switching between client and server modes and then selecting a queue or test connect might result in an error.

Workaround

Restart the agent.

(eCase 124080)

Connection problem occurs between ITAG installation on WebSphere DataStage when using Admin Client after installing the second ITAG version

(eCase 116898)

Fixed WebSphere DataStage problems

This table lists the WebSphere DataStage problems that are fixed with Information Server 8.0.1 Fix Pack 1a.

Known WebSphere QualityStage problems

At time of publication, there are no known WebSphere QualityStage problems.

Fixed WebSphere QualityStage problems

This table lists the WebSphere QualityStage problems that are fixed with IBM Information Server 8.0.1 Fix Pack 1a.

Known WebSphere Information Analyzer problems

At time of publication, the following information describes the currently known limitations, problems and workarounds for WebSphere Information Analyzer. Any limitations and restrictions might or might not apply to other releases of the product.

Reports that are created using the IBM Information Server Web console fail when copied and edited

When you select a report that was created in the root category, and click Create Copy and edit the report, the report creation fails. This general reporting issue also occurs in IBM WebSphere Information Services Director.

Workaround

Move the reports that need to be copied to a category other than the root category.

(eCase 124908)

Reports do not work if the HOST name contains a period

HOST is used by WebSphere Application Server and the underlying system and cannot be changed or deleted.

Workaround

Do not use the HOST name created during IBM Information Server installation. Create a new HOST without periods, under which you can add data stores to import the metadata to be analyzed.

(eCase 123766)

Help information does not display

The Help information does not display when you click Learn more or when you press the F1 key.

Workaround

Copy the files in the C:\IBM\InformationServer\ASBServer\apps\eclipse\plugins\plugins folder one level up to the C:\IBM\InformationServer\ASBServer\apps\eclipse\plugins folder.

(eCase 114617)

Validity Summary grid

The Validity Summary grid is not loaded when domain type is selected as Range, the minimum and maximum values are set, and you click the Save button.

Workaround

Close the panel after save.

(eCase 116006)

Fixed WebSphere Information Analyzer problems

This table lists the WebSphere Information Analyzer problems that are fixed with IBM Information Server 8.0.1 Fix Pack 1a.

Known IBM WebSphere Information Services Director problems

At time of publication, the following information describes the currently known limitations, problems and workarounds for IBM WebSphere Information Services Director. Any limitations and restrictions might or might not apply to other releases of the product.

IBM WebSphere Information Services Director jobs hang when using multinode PX configuration files with combinable operators including the SKIP option (such as the Sample operator)

Workaround

Insert a copy operator in the job before the sample operator.

Deployment fails if application is created with Japanese characters

Because of a bug within the WebSphere Java2WSDL application, when a package name contains multi-byte characters (for example, Japanese characters), the WSDL that is generated by Java2WSDL is not in a valid XML format. Specifically, the WSDL contains an attribute that looks similar to

<Schema targetnamespace="http://&#20035;&#20036.ibm.com"/>

The

乃&#20036

should be UTF-8 characters, not UNICODE characters. When the WSDL is used later in the deployment it is rejected because of those invalid characters.

Workaround

• Do not use multi-byte characters in an Application Name or Service Name, or
• Change the base package name from its default, which includes the application name and service name, so that it does not include multi-byte characters.

(eCase 114159)

Incorrect URL for SA05: WebSphere Service Registry and Repository Client Jars SupportPac™ in the IBM Information Server Planning, Installation, and Configuration Guide

The correct URL to obtain the SA05: WebSphere Service Registry and Repository Client Jars SupportPac is http://www-1.ibm.com/support/docview.wss?rs=171&uid=sw. This SupportPac contains the jar files necessary for a Java client application to communicate with WebSphere Service Registry and Repository Version 6 and is provided as a convenient way of obtaining the correct client files without running the WebSphere Service Registry and Repository installer.

(eCase 115563)

Deployment wizard does not lock the application

Redeploying an application does not lock the runtime version of the application. This allows changes during deployment that are not saved after the redeployment (for example, adding a provider for an operation in the application being re-deployed). Making changes during deployment might cause the redeployment to fail (for example, if a service in the application is published to the WSRR the re-deployment will fail and you will have to start over again)

Workaround

Do not make changes to the application during deployment.

(eCase 116343)

Setting up an input column for an operation provider with a constant value is not supported for DB2 Federation provider when the column type is XML

(eCase 116658)

IBM WebSphere Information Services Director does not support XML type in stored procedure result sets

(eCase 117095)

Fixed IBM WebSphere Information Services Director problems

This table lists the IBM WebSphere Information Services Director problems that are fixed with IBM Information Server 8.0.1 Fix Pack 1a.

IBM has several methods for you to learn about products and services.

You can find the latest information about IBM Information Server on the Web at http://www.ibm.com/software/data/integration/info_server/. To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide.

Contacting IBM

You can contact IBM by telephone for customer support, software services, and general information.

Customer support

To contact IBM customer service for IBM Information Server in the United States or Canada, call 1-866-INFO-NOW (1-866-463-6669).

To find worldwide support contact information for IBM Information Server, see the eService Support Center Directory at https://www.ibm.com/software/data/support/iis/eservice/.

Software services

General information

To find general information in the United States, call 1-800-IBM-CALL (1-800-426-2255).

Go to http://www.ibm.com for a list of numbers outside of the United States.

Providing comments on the documentation

Please send any comments that you have about this information or other documentation.