DB2 Warehouse V10.5 Known Issues

Content

IBM® DB2® Warehouse is a component of IBM DB2 Advanced Enterprise Server Edition V10.5, IBM DB2 Enterprise Server Edition V10.5, and IBM DB2 Advanced Workgroup Server Edition V10.5.

Oracle Compatibility Support

Issue: In Design Studio, a control or data flow that employs a table that is created in Oracle compatibility mode as a target or a data source, fails to execute.
User Response: Setup the SQL execution database with a database that is created in Oracle Compatibility mode. The reason for this is that during the flow execution process, a temporary table is created in the SQL execution database. Because the target or a data source table was created in Oracle Compatibility mode, so must the the SQL execution database.
For more information on the SQL execution database, see the DB2 Knowledge Center.

Issue: In the Administration Console, if a flow contains table source or table target operators that have the Location property set to Remote database and the selected table is created in Oracle compatibility mode, the flow fails.
User Response: No work around is available at this time.

Install

Issue: DB2 Enterprise Server Edition V10.5.5 fails to un-install. If you installed DB2 Enterprise Server Edition and InfoSphere Federation Server Relational Wrappers by installing DB2 Warehouse 10.5 and then you upgraded to DB2 Warehouse V10.5.5, un-installing removes DB2 Warehouse V10.5.5, but does not remove DB2 Enterprise Server Edition V10.5.5.
User Response:
Solution 1: Before you uninstall DB2 Enterprise Server Edition by un-installing DB2 Warehouse V10.5.5, uninstall InfoSphere Federation Server Relational Wrappers.

Solution 2: To uninstall DB2 Enterprise Server Edition V10.5.5, after you uninstall DB2 Warehouse V10.5.5, complete the following steps:

1. Generate a response file (db2ese.rsp) in the /root/dsw directory with the following content: REMOVE_PROD = DB2_SERVER_EDITION
2. Run the following command:

<user_install_folder>/db2/V10.5/install/db2_deinstall -r /root/dsw/db2ese.rsp.

Issue: The installation fails, despite no warnings or errors being displayed.
User Response: There may not be enough disk space to complete the installation. Re-install DB2 Warehouse, and during the installation, check the Pre-installation Summary pane for the amount of free disk space. Approximately 1.2 GB of disk space is recommended for the installation images of the data server components. If you plan to install the client components on the same computer, you will need a total of 2.5 GB of disk space.
For more information on installation requirements, see the DB2 Knowledge Center.

Issue: On Linux and AIX platforms, the installation fails, despite no warnings or errors being displayed.
User Response: There may not be enough disk space in the tmp folder to complete the installation. Re-install DB2 Warehouse, and during the installation, check the Pre-installation Summary pane for the amount of free disk space. Approximately 1.5 GB of disk space is recommended.
For more information on installation requirements, see the DB2 Knowledge Center.

Issue: On Windows 7 32-bit, Windows 8 32-bit, and Linux on X86 32-bit platforms the server images are for non-production use only.
User Response: 32-bit platforms are intended for development and test only. Please move to a 64-bit platform to take advantage of the full functionality of DB2 Warehouse.
For more information on system requirements, see the DB2 Knowledge Center.

Issue: DB2 Warehouse does not support installation on Windows 8.1 or on Windows 2012 R2 platform.
User Response: To install DB2 Warehouse on Windows, enable compatibility mode by completing the following steps:

1. Right-click the installer (install.exe) and select Properties.
2. On the Properties page, click the Compatibility tab.
3. Select the Run this program in compatibility mode for check box.
4. From the adjacent drop-down menu, select Windows 7. Click Apply.
5. Continue with the installation as outlined in the DB2 Knowledge Center.

Issue: DB2 Warehouse does not support un-installation on Windows 8.1 or on Windows 2012 R2 platform.
User Response: To un-install DB2 Warehouse on Windows, enable compatibility mode by completing the following steps:

1. Right-click the un-installer (uninstall.exe) and select Properties.
2. On the Properties page, click the Compatibility tab.
3. Select the Run this program in compatibility mode for check box.
4. From the adjacent drop-down menu, select Windows 7. Click Apply.
5. Continue with the un-installation as outlined in the DB2 Knowledge Center.

Admin Console

Issue: Some error messages from the Admin Console do not display the details tab.
User Response: No work around is available at this time.
Design Studio

Issue: If the reference flow is updated and saved, none of the updates are saved.
User Response: Save the parent operators in addition to the reference operators.

Intelligent Miner

Issue: Intelligent Miner is not supported on Inspur Itanium K1 platform running Inspur K-UX and POWER Linux for Little Endian on Ubuntu 14.04.
User Response: There is no response at this time.

Cubing Services

Issue: Cubing Services are not supported on Inspur Itanium K1 platform running Inspur K-UX and POWER Linux for Little Endian on Ubuntu 14.04.
User Response: There is no response at this time.

APAR Fix List

The following APARs are fixed in DB2 Warehouse Fix Pack 4:

· PJ41691: If the project path includes spaces, the operators that run sql statement from the DB2 command line fail.
· PJ41760: If you run a subprocess with multiple variable comparison operators for several iterations, an out of memory issue occurs.
· PJ41777: When control flow logs are viewed in a web browser, there are special characters ( &quot;, &lt;, etc..) that make it hard to read and understand the flow logs.
· PJ41940: Control flows cannot be triggered at the scheduled time because of the max thread number limitation.
· PJ42092: In non-english Design Studio versions, Japanese characters cannot be used as a customized JDBC driver name.
· PJ42131: After creating an schedule, sometimes the start date changes to an unintended date.
· PJ42116:The deploy change function does not function as intended if a new variable with a design time (DESIGN_TIME) is defined in the changed flow.
· PJ42124: If you have defined a number of connections with external JDBC drivers, the Administration Console hangs during start up process.
· PJ42125: Subprocess activities are not marked as complete in a parallel container if the subprocess contains an iterator operator
· PJ42155 :There are special characters ( &apos;) in control flow logs when view them in browser.

The following APARs are fixed in DB2 Warehouse Fix Pack 3:

• PJ40792: Change the current date time format used in Admin Console from "mm/dd/yyyy hh:mm:ss" to a more friendly format to customers like "Dec 4, 2012 3:43:00 PM".
• PJ41047: When using CreateSchedule command, there is a problem with date format convertion under DE locale. It will cause the schedule creation to fail. After applying the fix, users can use German date format in command line like dd.MM.yyyy.