IBM Red Brick Warehouse RELEASE NOTES for Windows Platforms Version 6.30.xC15

Preventive Service Planning

Abstract

Content

IBM Red Brick Warehouse

RELEASE NOTES for Windows Platforms
Version 6.30.xC15

Contents

Chapter 1. RELEASE NOTES
1.1 Important release information
1.2 Software support
1.3 New features in Version 6.30.xC15
1.4 New features in Version 6.30.xC14
1.5 New features in Version 6.30.xC13
1.6 New features in Version 6.30.xC12
1.7 New features in Version 6.30.xC9
1.8 New features in Version 6.30.xC1
1.9 Supported Windows platforms
1.10 Data access for .NET Framework applications
1.11 ODBC Driver compatibility
1.12 JDBC Driver requirements
1.13 Interoperability with other IBM products
1.14 Significant operational changes

1.15 Installation and upgrade notes

1.16 Known issues

1.17 Fixed issues

1.18 Documentation notes

Chapter 2. Notices
2.1 Trademarks

Chapter 3. Contacting IBM
3.1 Product Information
3.2 Accessible documentation
3.3 Comments on the documentation

Chapter 1. RELEASE NOTES

1.1 Important release information

IBM® Red Brick® Warehouse Version 6.30.xC15 is a new release that contains new features and enhancements.

The version string TC15 refers to the 32-bit Windows platform. The string UC15 refers to 32-bit Linux platform. The string FC15 refers to 64-bit UNIX,64-bit Linux and 64-bit Windows platforms. Throughout these release notes, V6.30.xC15 refers to all platforms generically.

These release notes contain information about all of the Red Brickproducts, including the Client Connector Pack and the Administrator tool.

Before you use V6.30.xC15, read the following sections:

1.3, "New features in Version 6.30.xC15"
1.4, "New features in Version 6.30.xC14"
1.5, "New features in Version 6.30.xC13"
1.6, "New features in Version 6.30.xC12"
1.7, "New features in Version 6.30.xC9"
1.8, "New features in Version 6.30.xC1"
1.14, "Significant operational changes"
1.15, "Installation and upgrade notes"
1.16, "Known issues"
1.18, "Documentation notes"

1.2 Software support

If you have technical questions about IBM Red Brick Warehouse but cannot find the answer in the appropriate document, contact IBM Software Support as follows:

Telephone:
1-800-274-8184 or 1-913-492-2086 (7 a.m. to 7 p.m. central time, Monday through Friday)

Internet access:
www.ibm.com/software/data/informix/support/

1.3 New features in Version 6.30.xC15

IBM Red Brick Warehouse V6.30.xC15 contains the following new features and enhancements. The following list briefly describes each feature.

New server platforms

RHEL 6
AIX 7.1
Windows 7
Windows 8
Windows 2012

1.4 New features in Version 6.30.xC14

IBM Red Brick Warehouse V6.30.xC14 contains the following new features and enhancements. The following list briefly describes each feature.

Support for JDK 1.6

IBM Red Brick Warehouse V6.30.xC14 supports Red Brick JDBC driver on JDK 1.6.

New server platforms

Windows Server 2008 R2

1.5 New features in Version 6.30.xC13

IBM Red Brick Warehouse V6.30.xC13 contains new features and enhancements. The following list briefly describes each feature.

Stacktrace feature

The stacktrace feature is a part of the IBM Red Brick Warehouse diagnostics.

When the IBM Red Brick Warehouse server stops or encounters a pre-defined list of FATAL errors, a stacktrace log file is generated. The log file name format is proc_name-pid-time_stamp.log, and the log file is stored in the RB_CONFIG/logs folder, where proc_name is the name of the process that crashed, pid is the process ID, and time_stamp is the date and time when the process crashed. The stacktrace feature is supported on the following operating systems:

Microsoft Windows (32-bit)

You can start or stop the stacktrace feature in client applications such as RISQL® by using session-wide settables. To enable the stacktrace feature in IBM Red Brick Warehouse, set the OPTION STACK_TRACE ON | OFF to ON in the rbw.config file.

New server platforms

Microsoft Windows Server 2003 (64-bit)
Microsoft Windows Server 2008 (64-bit)

1.6 New features in Version 6.30.xC12

IBM Red Brick Warehouse V6.30.xC12 contains new features and enhancements. The following list briefly describes each feature.

Remote TMU logging is enabled

IBM Red Brick Warehouse V6.30.xC12 implements logging for remote TMU.

An OPTION parameter called REMOTE_TMU_MIN_LOG is used to enable or disable logging. Set the option to ON in both the server and client rbw.config files. When logging is enabled, two log files are generated for every remote load operation that is performed. The log files are saved in the RB_CONFIG\logs directory. The client log file is named rb_ctmu_pid.log and the server log file is named rb_drvtmu_pid.log, where pid is the process ID of the remote TMU process and the driver TMU process.

Support for JDK 1.5

IBM Red Brick Warehouse V6.30.xC12 supports Red Brick JDBC driver on JDK 1.5.

Note: Red Brick Warehouse V6.30.xC12 release supports only the following JDBC 3.0 APIs:

getJDBCMajorVersion()
getJDBCMinorVersion()
getDatabaseMinorVersion()
getDatabaseMajorVersion()

Enhanced logging using CALLOUT scripts

IBM Red Brick Warehouse V6.30.xC12 contains a CALLOUT script that you can call to run an external command from the product if fatal errors are generated. For more information about CALLOUT scripts, see "Enhanced logging using CALLOUT scripts".

Reporting tool for accounting

IBM Red Brick Warehouse V6.30.xC12 contains the acctview tool to read and interpret the accounting logs. The acctview tool is available in the redbrick_dir\utils\service directory, where redbrick_dir is the Red Brick installation directory.

For more information about acctview tool, see "Acctview reporting tool for accounting".

New server platform

Microsoft Windows Server 2008 (32-bit)

1.7 New features in Version 6.30.xC9

IBM Red Brick Warehouse V6.30.xC9 contains new features and enhancements. The following list briefly describes each feature and indicates which documents to consult for more information.

64-bit ODBC drivers for the 64-bit Windows platform

IBM Red Brick Warehouse V6.30.xC9 contains a new 64-bit ODBC driver for the 64-bit Windows platform. The 64-bit ODBC driver is named rb64odbc.dll.

The 64-bit ODBC driver comes with the rb64odin.dll file, which is the set up dll file for configuring the 64-bit ODBC DSN. The rb64odbc.dll and rb64odin.dll files are available in the Windows\system32 directory.

Enhancements in the TMU GENERATE statement

The TMU GENERATE statement now supports:

Generation of DDL statements (including DDL for segments and indexes) for the entire database.
Generation of DDL statements (including DDL for segments and indexes) for a table.

1.8 New features in Version 6.30.xC1

IBM Red Brick Warehouse V6.30.xC1 contains a large number of new features and enhancements. The following list briefly describes each feature and indicates which documents to consult for more information.

Query execution and optimization

Optimizer directives--The server supports SET commands for controlling the availability of specific STAR indexes for single- and multi-fact joins and for adjusting thresholds that influence the overall choice of STARjoin and TARGETjoin plans (Query Performance Guide, Chapter 2; SQL Reference Guide, Chapter 9).
SQL OLAP functions--The server supports additional functions for analytic queries: PERCENT_RANK, CUME_DIST, PERCENTILE_CONT, and PERCENTILE_DISC. The PERCENTILE functions are useful for calculating median values (SQL Reference Guide, Chapter 6).

The server also supports the ROUND scalar function (SQL Reference Guide, Chapter 5).

Dynamic segment elimination--Complementing compile-time "SmartScan" optimizations, the server also supports run-time or "dynamic" segment elimination, which further optimizes data access for table scans and TARGETjoins that use local indexes. Segment elimination is also factored into selectivity estimates that determine which query plan is chosen (Query Performance Guide, Chapter 2).
TARGETjoin performance enhancement--The performance of TARGETjoin queries is optimized, and single-column B-TREE indexes can participate in TARGETjoin plans (SQL Reference Guide, Chapter 9; Query Performance Guide, Chapter 3).
Memory mapping for queries--To optimize access to dimension tables and their primary-key indexes, these objects are partially or wholly memory-mapped during query execution (SQL Reference Guide, Chapter 9; Query Performance Guide, Chapter 4).

TMU and PTMU enhancements (Table Management Utility Reference Guide)

Expression support--You can define arithmetic expressions and conditional CASE expressions for input columns inside the TMU control file. Also, the ACCEPT/REJECT clause accepts multiple conditions (Chapter 3).
Memory tuning--Loads and REORG operations benefit from smarter memory use and distribution. To fine-tune loads, you can set the maximum size of the buffer cache and specify the distribution of buffers among conversion, output, and index tasks (Chapter 2).
XML namespaces and nested XML data--Loads in XML format now support XML namespaces and namespace prefixes, as well as XML data that has a "nested" structure (Chapter 3).
Multi-character delimiters--Separated-format loads support delimiters that consist of more than one character (Chapter 3). The EXPORT command provides complementary string-delimiter support (SQL Reference Guide, Chapter 8).

General administration features

Alter tables using a working segment--You can add or drop table columns into a predefined working segment. This option provides greater reliability and recoverability than other ALTER TABLE modes (Administrator's Guide, Chapter 9; SQL Reference Guide, Chapter 8).
System catalog compaction--To improve performance, you can use the rb_syscompact utility to reduce the size of the database system catalog (Administrator's Guide, Chapter 9).
Incremental maintenance for precomputed views with nullable grouping columns--Views that required rebuild maintenance plans because they contain nullable grouping columns are now updated with incremental plans, improving maintenance performance (IBM Red Brick Vista User's Guide, Chapter 4).

Client features

The Red Brick ODBC Driver supports array fetches and parameter arrays:

Array fetches allow an ODBC application to fetch more than one result set row at a time from the database, reducing the number of calls to the SQLFetch or SQLFetchScroll API.
Parameter arrays can be used to emulate block inserts by executing the same INSERT statement iteratively with successive sets of parameter values. The ODBC Driver executes an INSERT statement for each element it gets from the array; this process continues until either an error occurs or all of the elements have been processed.

(Microsoft ODBC Programmer's Reference, Client Installation and Connectivity Guide, Chapter 2)

Administrator tool enhancements--The flow of the wizards for managing database objects is more logical and consistent. The Manage Tables wizard supports the new ALTER TABLE option that uses a working segment to add and drop columns. The online help describes these enhancements in detail.

New server platforms

HP-UX 11i for Intel Itanium 2
Microsoft Windows Server 2003 (32-bit)

Online Information Center

The Red Brick Warehouse Version 6.3 documentation is available on the Web in the form of a standard IBM Information Center:
http://publib.boulder.ibm.com/infocenter/rb63help/

1.9 Supported Windows platforms

IBM Red Brick Warehouse V6.30.TC15 (32 bit) is supported on the following Windows platforms:

Windows 7 (32-bit) Base, later updates
Windows 7 (64-bit) Base, later updates
Windows 8 (32-bit) Base, later updates
Windows 8 (64-bit) Base, later updates
Windows 2012 (64-bit) Base, later updates
Windows Server 2003 (32-bit) SP1 or later
Windows Server 2008 (32-bit) SP1 or later
Windows Server 2003 (64-bit) SP1 or later
Windows Server 2008 (64-bit) Base, SP1 or later, R2

IBM Red Brick Warehouse V6.30.FC15 (64 bit) is supported on the following Windows platforms:

Windows 7 (64-bit) Base, later updates
Windows 8 (64-bit) Base, later updates
Windows 2012 (64-bit) Base, later updates
Windows Server 2003 (64-bit) SP1 or later
Windows Server 2008 (64-bit) Base, SP1 or later, R2

The Windows components of Client Connector Pack V2.30 32-bit and IBM Red Brick Warehouse Administrator V2.30 are supported on the following platforms:

Windows 7 (32-bit) Base, later updates
Windows 7 (64-bit) Base, later updates
Windows 8 (32-bit) Base, later updates
Windows 8 (64-bit) Base, later updates
Windows 2012 (64-bit) Base, later updates
Windows 2000 Professional (32-bit) SP4 or later
Windows XP Professional (32-bit) SP1 and SP2
Windows XP Professional (64-bit) SP1 and SP2
Windows Server 2008 (32-bit) SP2 or later
Windows Server 2008 (64-bit) SP1 or later, R2
Windows Server 2003 (32-bit) SP1 or later
Windows Server 2003 (64-bit) SP1 or later

Windows Vista Business Edition (32-bit) - Not applicable

The Windows components of Client Connector Pack V2.30 64-bit and IBM Red Brick Warehouse Administrator V2.30 are supported on the following platforms:

Windows 7 (64-bit) Base, later updates
Windows 8 (64-bit) Base, later updates
Windows 2012 (64-bit) Base, later updates
Windows XP Professional (64-bit) SP1 and SP2
Windows Server 2008 (64-bit) SP1 or later, R2
Windows Server 2003 (64-bit) SP1 or later

Do not use earlier service packs than those that are listed.
Microsoft Visual C++ 2005 SP1 Redistributable Package Package is required to be installed on the system.
To run the installer on Windows 7, Windows 8 and Windows 2012, right-click setup.exe and click Run as administrator.

1.10 Data access for .NET Framework applications

IBM Red Brick Warehouse does not have a native .NET data provider. To access a Red Brick data source from a .NET Framework application, use the System.Data.Odbc namespace, which is the .NET Framework Data Provider for ODBC. For information about using the System.Data.Odbc namespace, refer to the Microsoft documentation: http://msdn.microsoft.com/en-us/library/system.data.odbc.aspx

Note: Before you can connect to a Red Brick data source by using the System.Data.Odbc interface, you must configure an ODBC Data Source Name (DSN) on the system.

1.11 ODBC Driver compatibility

The following section describes the backward compatibility of UNIX and Windows Red Brick ODBC Drivers with IBM Red Brick Warehouse databases:

IBM Red Brick Warehouse V6.0.x, V6.10.x, V6.11.x, V6.20.x and V6.30.x databases are compatible with:

Windows ODBC Driver V5.01 (Client Connector Pack V2.0.x), UNIX ODBC Driver V6.01
Windows ODBC Driver V5.02.x (Client Connector Pack V2.10.x and 2.11.x), UNIX ODBC Driver V6.02.x
Windows ODBC Driver V5.62.x (Client Connector Pack V2.20.x), UNIX ODBC Driver V6.62.x
Windows ODBC Driver V5.63.x (Client Connector Pack V2.30.x), UNIX ODBC Driver V6.63.x

If you use a V5.01/6.01 or earlier ODBC Driver with a V6.10.x or later database, you will not be able to define a column with the SERIAL data type.

The ODBC Drivers and ODBClib SDKs for UNIX and Linux platforms are installed from the server directory (RBW) on the installation media, not the Client Connector Pack directory (CCP). The Client Connector Pack also includes Windows versions of the RISQL Entry Tool, RISQL Reporter, and Client TMU applications. For installation instructions and more information about these components, see the Client Installation and Connectivity Guide.

For more information about the Red Brick ODBC Drivers on all platforms, see the Client Installation and Connectivity Guide.

1.12 JDBC Driver requirements

IBM Red Brick Warehouse V6.30.xC15 supports JDK 1.4,1.5 and 1.6. Alternatively, you can install the Java(TM) Runtime Environment (JRE) Versions 1.4,1.5 or 1.6. The JRE package is smaller and is sufficient for running Red Brick JDBC applications.

Note: Security vulnerability CVE-2010-4476: Java Runtime Environment hangs when converting "2.2250738585072012e-308" to a binary floating-point number.

For information about avoiding this vulnerability refer to the developerWorks website:
www.ibm.com/developerworks/java/jdk/alerts/cve-2010-4476.html

The recommended levels of JDK/JRE are also mentioned in the link.

The following jar files are required for running the Red Brick JDBC Driver:

redbrick.jar

Red Brick JDBC Driver.
jndi.jar

The JNDI API; required only if you are working with Datasources.
jdbc2_0-stdext.jar

The JDBC 2.0 Standard Extension; required only if you are working with Datasources.
fscontext.jar or ldap.jar

File System Context Service Provider jar file or LDAP Service Provider jar file; required only if you are working with Datasources.
providerutil.jar

This file is required by fscontext.jar and ldap.jar (and is downloaded with these jar files).
Make sure the required jar files are set in your CLASSPATH environment variable. Note how these files are bundled for different Java versions:

jndi.jar and ldap.jar are included in J2SE 1.3, not J2SE 1.2.
jdbc2_0-stdext.jar and fscontext.jar are not included in J2SE 1.2 or J2SE 1.3.

Note: The JDBC drivers for IBM Red Brick Warehouse V6.3.xC15 are compatible with the earlier versions of IBM Red Brick Warehouse databases.

1.13 Interoperability with other IBM products

IBM Red Brick Warehouse operates with the following IBM products:

IBM DB2® Information Integrator. For details about using a Red Brick database as an Information Integrator data source, see Appendix D of the Administrator's Guide.
IBM DB2 Warehouse Manager. For details about using Warehouse Manager to export data from Red Brick databases to DB2 databases, or vice versa, go to the Informix zone on the developerWorks web site:

www.ibm.com/developerworks/db2/zones/informix/

IBM Tivoli® Storage Manager. For information about using Tivoli Storage Manager as a storage management system for TMU backups, see the Table Management Utility Reference Guide.
IBM HTTP Server. For information about using IBM HTTP Server as part of a three-tier Red Brick JDBC application, see the Client Installation and Connectivity Guide.

1.14 Significant operational changes

Before you use IBM Red Brick Warehouse V6.30.xC15, note the following operational changes.

1.14.1 Stopping the Red Brick services

Do not use the Services control panel to stop the Red Brick services if active connections exist; the services will not be stopped, and subsequent attempts to stop the service will result in errors. Use the rbwservice utility to control the Red Brick services, as described in "Syntax for the rbwservice.exe utility".

Do not try to control the Red Brick services concurrently from multiple executables (two instances of the Services control panel, two instances of rbwservice.exe, or a combination of the two). When different computers, users, or scripts issue concurrent start and stop requests, the behavior of the Red Brick services is unpredictable.

1.14.2 New level 0 backups required

If you use TMU backups, perform a new level 0 backup on each database after upgrading to IBM Red Brick Warehouse V6.30.xC4 and later versions. Because of problems that were fixed in V6.30.xC4 and V6.30.xC5, your existing TMU backups might not be reliable.

1.14.3 Red Brick Data Mine not supported

Data mining with the Red Brick Data Mine feature is not supported in Version 6.20 and later versions. In Version 6.30.xC3 and later versions, the upgrade process skips models and related data-mining objects. You do not need to use the DROP MODEL statement to remove model objects before running the upgrade.

1.15 Installation and upgrade notes

The following sections contain notes on installing IBM Red Brick Warehouse and upgrading existing databases. After you have read these notes, see the Installation and Configuration Guide for standard installation and upgrade procedures.

1.15.1 For the first time

If you are a new user, follow the procedure for a first-time installation described in the Installation and Configuration Guide. This procedure is designed for sites not currently using IBM Red Brick Warehouse.

1.15.2 With an existing warehouse

If you are currently using an earlier version of the Red Brick server, read the information in the Installation and Configuration Guide under "Running two releases of IBM Red Brick Warehouse." This section describes how to allow users to continue working with the current database and software while you install the new version in a separate directory. You can then test the new version to see how the changes will affect your warehouse implementation before you upgrade your production databases.

Follow this procedure whenever the changes between releases are substantial or if an upgrade is required. A database cannot be used with an earlier release after it has been upgraded to a newer one.

Upgrade paths

The V6.30.xC15 release requires an upgrade of existing V6.20.x and earlier databases to accommodate changes to the system catalog. You can upgrade any V6.0.x, V6.1x, or V6.20.x database directly to V6.30.xC15. To upgrade from V5.1.x, you must first upgrade to V6.0.x or V6.1x.

Before upgrading, you must follow these steps

Back up the database in case the upgrade is not successful.
If your database contains a backup segment, drop the backup data:
alter database drop backup data;
If your database is versioned, clean and drop the version log:
alter database clean version log;
alter database drop version log;
If you are not sure whether your database contains a backup segment or a version log segment, run the following query:
select name from rbw_segments
where usage = 'BACKUP_DATA' or usage = 'VERSION_LOG';
Finally, make sure there are no pending ALTER TABLE operations or offline loads:
select name from rbw_segments where insynch = 'N';

Caution: It might not be possible to restore a database from a TMU backup that you created with a previous release of the Red Brick server. After the upgrade to V6.30.xC15, immediately perform a full backup (level 0), by using either the TMU backup program or an external tool.

If you created your database with a linguistic sort order (that is, any sort order other than Binary), re-create any indexes built on character columns after upgrading the database to Version 6.3. In previous releases, the index entries might not have been sorted according to the defined linguistic sort order.

Migrating databases to new platforms

A database created on one type of platform cannot be accessed by a Red Brick server running on another type of platform. For example, Red Brick databases created on HP-UX systems are not accessible on AIX® systems and databases created on RHEL or Windows systems are not accessible on HP-UX systems.

To migrate a database to a different type of platform, unload the data in external format from the old system and load it into a new database on the new system. To re-create the database objects, run the CREATE TABLE and LOAD DATA statements that the TMU UNLOAD EXTERNAL operation generates.

Selecting a code set during a Windows installation

When you install IBM Red Brick Warehouse on Windows platforms and specify a locale, the default code set for the language and territory you choose appears in the list box. Other valid code sets can be selected from above and below the default selection. For example, if you select SimplifiedChinese and China as your language and territory, the default code set in the list box is MS936. The other valid choices are UTF-8 and MS54936, but only UTF-8 is displayed in the list. To select MS54936, click the up arrow next to the default selection.

Administrator tool installation and compatibility

Before installing IBM Red Brick Warehouse Administrator V2.30, be sure to uninstall the previous version of the tool. To do this, select the Uninstaller utility for IBM Red Brick Warehouse Administrator from the Programs menu.

You can use the current Administrator tool (V2.30) with IBM Red Brick Warehouse V6.20.x and V6.30.x databases.

1.16 Known issues

This section describes known issues in IBM Red Brick Warehouse V6.30.xC15. This section is organized as follows:

Installation and upgrade issues
Database administration issues
Query-related issues
Connectivity issues
Administrator tool issues

1.16.1 Installation and upgrade issues

This section lists the known issues related to IBM Red Brick Warehouse installation, upgrade, and uninstallation.

IBM Red Brick service visible after uninstallation

After you uninstall IBM Red Brick Warehouse, you can see the IBM Red Brick service in the Services window.

The rb32odbc.dll file is not deleted after running the Uninstaller program for Client Connector Pack

After you run the Uninstaller program for the Client Connector Pack of IBM Red Brick Warehouse version 6.30.xC12 or later, the rb32odbc.dll file is not deleted from the system32 directory.

Note: This issue exists with the Client Connector Pack that is installed on the Windows 7 operating system.

1.16.2 Database administration issues

This section lists the known issues related to database administration.

The ALTER SYSTEM CLOSE USER SESSION command fails to stop a TMU process on a Windows system

On a Windows-based system, the ALTER SYSTEM CLOSE USER SESSION command stops all RISQL sessions but fails to stop a TMU process.

Indexes with large keys

You can create an index with a key that is up to 4,000 bytes in size. However, an index with a key larger than 2,600 bytes is likely to cause problems with inserts, updates, and some loads. To avoid these problems, make sure that the maximum size of an index key is less than 2,600 bytes.

/PAE switch causes fatal errors

When there is a large number of processes running and the /PAE switch is set in the boot.ini file, Red Brick operations sometimes return fatal errors. Do not set the /PAE switch on computers that are running Red Brick applications.

For XML loads, invalid namespace prefixes sometimes cause inappropriate errors

You must use valid namespace prefixes, as defined by the W3C standard for using namespaces in XML. In most cases, an illegal namespace causes a syntax error that identifies the offending line number in the control file. However, some invalid prefixes, such as those that are invalid because they start with numeric values, return inappropriate error messages. For example, consider the following illegal prefixes:

2003.01.02:
In this case, the TMU returns message 1402 because the parser tries to parse 2003.01.02 as a numeric constant and fails. (This prefix is also illegal because it contains periods.)
1eAbc:
In this case, the TMU returns error 8205 because the parser tries to interpret 1eAbc as a floating-point literal and fails (because of the letter A after 1e.)

Resumed ALTER TABLE IN_PLACE operation corrupts data

An ALTER TABLE IN_PLACE operation results in corrupted data when a segment runs out of space and you add a PSU to the segment in order to resume the operation. After the RESUME operation has completed, a CHECK TABLE operation on the segment reports that the segment is corrupt.

Recommendation: Use the IN_PLACE USING working_segment option introduced in Version 6.3. The problem described here does not occur when you use a working segment to alter a table.

TMU UNLOAD not supported for tables with more than 2^31 -1 rows

A TMU UNLOAD operation can unload a maximum of 2,147,483,647 rows (2^31 -1) but cannot unload any rows from a table that contains more than this number of rows. If the table you want to unload contains more than 2^31 -1 rows, the UNLOAD operation against the table will fail, regardless of the number of rows you try to unload. To unload rows from very large tables, use the SQL EXPORT command, as documented in the SQL Reference Guide.

RISQL session fails to connect to the server and results in a fatal error

RISQL session fails to connect to the server when multiple queries that fetch a huge amount of data are cancelled using the ALTER SYSTEM CANCEL USER command. This also results in a fatal error.

An error occurs even if the number of segments in the database is less than the maximum limit

The following error occurs before the number of segments that are created in the database reaches the maximum limit:

** ERROR ** (7514) Maximum number of usable segments exceeded.

To avoid this problem, ensure that you create a maximum of 61437 segments. When you want to create more than 61437 segments, delete some of the existing segments. The problem occurs when a segment is assigned an ID 61438.

In the Japanese build of Red Brick Warehouse, the error messages are saved in English

In the Japanese build of Red Brick Warehouse V6.30.xC12, the following error messages are saved in English:

RBE413U: Message: Callout script does not support inline or C-type comments: String. Ignoring line.
RBE414U: Message: Callout script does not support more than five error sections
RBE416U: Message: Detected setting for Error: ERROR_NUM in Callout script.
RBE417U: Message: No setting for Error: ERROR_NUM detected in Callout script.
RBE418U: Message: Fork failed for Callout script.
RBE419U: Message: Error detected in Callout configuration file, String: callout script string.
RBA6524F: Message: Reached the maximum number of database sessions or load processes.

Note: The first 6 messages are saved in the error log file.

Please note that IBM Red Brick Copy Management service doesn't work on machines with winsock version 6.0.

PTMU fatal error 6524 may cause Red Brick not to return control back to the user or terminal.

Whenever the admin daemon gets busy working with DST tables, it can become slow in reading the messages from the message queue.

In such a scenario the message queue doesn't get empty and thus we cannot send any more request as the admin daemon is too slow to empty the queue. We may see the ** ERROR ** (1503) Message queue operation on qid -1 failed with err no 3 in such a situation.

1.16.3 Query-related issues

This section lists the known issues related to database queries.

Hash-join queries run out of block cache

Queries that perform a HASH 1-1 Match operation might run out of block cache during execution, resulting in a fatal 132 error. To solve this problem, increase the query memory limit.

Space character not supported as delimiter in EXPORT statements

You cannot use a space character as a delimiter in an SQL EXPORT statement. However, you can set the Tab key as a delimiter. See "Correct the description of valid EXPORT delimiter characters on pages 406 and 462".

RANGE LIKE SEGMENT clause cannot be used to attach a STAR index to a segment that is not a boundary segment

You cannot use the RANGE LIKE SEGMENT clause to attach a STAR index to a segment that is not a boundary segment. This clause works only when you attach a STAR index to either the last segment or the first segment of the segment range.

To overcome this limitation, specify a range based on the segment name and row numbers (RBW_ROWNUM pseudocolumn) of the segmenting column for the referenced (dimension) table. The segmenting column of the referenced table is defined in the CREATE TABLE statement. See "Methods for attaching a STAR index to a segment".

1.16.4 Connectivity issues

This section lists the known issues related to database connectivity.

Incomplete display of long ConnectionPoolDataSource names

In the Add and Edit dialog boxes for PooledDataSources in the JDBC Data Source Administrator tool (rbdsadmin.*), long ConnectionPoolDataSource names are not fully displayed. The pop-up menu does not resize itself to accommodate long names.

JDBC CONVERT function

The JDBC CONVERT function currently supports the following nonstandard type names: SQL_CHAR, SQL_VARCHAR, SQL_REAL, SQL_INTEGER, SQL_FLOAT, SQL_TIMESTAMP, SQL_DECIMAL, SQL_DATE, and SQL_TIME.

Microsoft SQL Server Data Transformation Services (DTS)--loading data with the TMU

DTS loads data into ODBC data sources using INSERT statements. These statements load one row at a time, and the performance is very poor. You should run TMU LOAD DATA operations to load the data, then process the cube using Analysis Services.

Microsoft SQL Server Analysis Services--incorrect DDL generated for Day option

Incorrect DDL is generated when the Day option is selected in the Create the Time Dimension Levels wizard (for example: Year, Month, Day) and the cube is processed with ROLAP data storage. As a workaround, you can manually correct the DDL before it is executed.

Processing cubes with Microsoft SQL Server Analysis Services

When you use Analysis Services to build a cube from tables in an IBM Red Brick Warehouse database, you can choose MOLAP (the default), HOLAP, or ROLAP for data storage. To use the ROLAP option, you must add the following parameter to your rbodbc32.ini file:
TXN_CAPABLE_ALL=MMC.EXE
where mmc.exe is the application program name for Microsoft SQL Server 2000 Analysis Services. When this parameter is set, SQLGetInfo(SQL_TXN_CAPABLE) returns SQL_TC_ALL for Analysis Services.

TimeZone returns unexpected results with JDK 1.2

The JDBC 2.0 TimeZone function might return unexpected results when it is used in Java applications compiled with JDK 1.2.

ODBC/JDBC Drivers incorrectly report query cancellation

The ODBC and JDBC drivers might return a "Statement Cancelled" message despite the fact that the server has successfully executed the query. This timing problem only occurs when the cancel request is sent to the server immediately after the server has sent its OK status to the client and the client has yet to acknowledge that status.

JDBC date string results

Because of a problem in the JavaSoft JDK, the JDBC driver does not return an error for invalid date strings in getDate, getTimestamp, or getTime commands. For example, getDate (col ('9999-12-33')) returns the date 10000-01-02 and getDate(col('1999-02-29')), a date that does not exist, returns the date 1999-03-01.

Microsoft Access dynaset mode

When the Microsoft Access query tool is used with the dynaset capability enabled, performance might be slow on certain tables with multi-column primary keys. If you encounter slow performance, disable the dynaset capability by changing the SnapshotOnly ODBC option setting to 1, which sets the query mode to SnapshotOnly. Note that results from SnapshotOnly mode queries, unlike results from dynaset mode queries, cannot be updated.

To change the setting in Microsoft Access 2.0, add the following line to the [ODBC] section of the \WINDOWS\MSACC20.INI file:
SnapshotOnly = 1

To change the setting in Microsoft Access 7.0 or later, use the Registry Editor to disable the dynaset capability by following these steps:

Start the Registry Editor by entering the following command at the MS-DOS prompt:
c:\>regedit
Navigate to the \Engines\ODBC folder. The location of this folder depends on your Windows operating system and Microsoft Access version. For example:
\HKEY_LOCAL_MACHINE\Software\Microsoft\Access\7.0\Jet\3.0\Engines\ODBC
or
\HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\ODBC
Double-click SnapshotOnly and change its value to 1.

If the SnapshotOnly parameter does not exist in the ODBC folder, create it and modify it as follows:

From the Edit menu, select Edit, then New, then DWORD Value.
Enter SnapshotOnly for the DWORD name.
From the Edit menu, select Edit, then Modify.
Change Value data to 1 and click the OK button.

When linking tables from a Red Brick database with Microsoft Access 7.0, do not select any key columns. Doing so will cause poor performance on that table. For more information about configuring the ODBC settings for Microsoft Access, see the Microsoft Access Help topic "ODBC Settings."

The java.sql.date class returns an IllegalArgumentException error

On JDK 1.6 update 18 and later, the java.sql.date class returns a java.lang.IllegalArgumentException error. This problem occurs when the date is not passed in the 'YYYY-MM-DD' format. For example, if the date is passed as '2010-1-1', the JDBC system displays an error. The correct date format is '2010-01-01'.

Note: This issue is fixed in the IBM Red Brick Warehouse V6.30.xC14.

Red Brick Show utility may report incorrect number of closed sessions.

In some cases, connections that have been closed or terminated, remain in the Red Brick Show utility (rbshow) output. A workaround for this issue, is to use an alternate Red Brick server executable located in the utils/service directory. Please contact customer support if you are experiencing this issue .

Whenever the server and client have different locale, there maybe a chance that the number of bytes used to represent a character on client locale is more than the bytes used to represent the same character on the server locale.

In such a scenario times we do see codeset conversion problems. The recommended solution is to increase the size of the column in question on the server side

1.16.5 Administrator tool issues

This section lists the known issues related to the Administrator tool.

Alter System wizard does not display list of users

If you attempt to change the user priority via the Manage System wizard, the User Priority screen does not list any users. This problem arises when you use the following procedure:

From the Manage menu, select System.
Select User Priority and click Next.
Click the User drop down list.

At this time, there is no list of Users.

You can use the following procedure to change the user priority:

From the Manage menu, select Users.
Select Alter User and click Next.
Select a user to alter and click Next.

The Edit the Comment and Priority screen appears.

Refresh All to see changes to the database

After performing operations within the Administrator tool, you have to select Refresh All from the View menu in order to see the results of those operations. The tool does not update its view of the database automatically.

The GUI Admin tool is not supported with 64-bit versions of the Client Connectivity Pack (CCP).
The GUI Admin tool does not support 64-bit ODBC data sources. It is only compatible with 32-bit ODBC data sources that are created with the Red Brick 32-bit Client Connector Pack (CCP).

1.17 Fixed issues

This section describes issues reported by customers and fixed in IBM Red Brick Warehouse V6.30.xC2 through V6.30.xC15. The CSL number is the Customer Support Log number assigned to each case.

This section is organized as follows:

Installation and upgrade issues
Database administration issues
Query-related issues
Connectivity issues
Administrator tool issues
Documentation issues

1.17.1 Installation and upgrade issues

CSL #00356
Red Brick menu tree left in the All Programs listing but does not function after uninstalling 6.30.FC13.
CSL #44936,999,760
The 64 Bit xC14 CCP installer no longer creates a folder in the "START => All Programs" like the 32 Bit CCP installer did.
CSL #35946,999,760
The version of CCP on Windows platform can be determined from the ODBC driver version specified at Administrative Tools -> Data Source (ODBC).
CSL #71391,999,760
Installer drops two rbodbc64.ini files after installing 6.30.FC14 64-bit CCP on Windows 2008 R2.
CSL #71297,999,760
The 64 bit Win2008R2 6.30.FC14 Japanese CCP had hardcoded US locale for the config and ini files.
CSL #50884,999,760
RBWEXCEPT.log output on startup in 6.30.xC14 Redbrick server.

1.17.2 Database administration issues

CSL #381821
On Windows platforms, the ALTER SYSTEM CLOSE USER SESSION command failed to terminate idle clients immediately.
CSL #388948
On multi-CPU Windows servers, certain INSERT INTO...SELECT queries failed to complete because of a resource allocation problem.
CSL #390977
When an SQL EXPORT operation was cancelled with either Ctrl-C or an ALTER SYSTEM command, the EXPORT output file remained locked.
CSL #391741
The password settings CHANGE_INITIAL and CHANGE_MINIMUM_DAYS were not compatible; new users were prompted to change their passwords on first login but the changes failed because the password age had not elapsed.
CSL #392561
To create hierarchies, users had to either be a member of the DBA system role or have CREATE_ANY authorization. Being a member of the RESOURCE system role was insufficient and resulted in error 53 when users submitted the CREATE HIERARCHY statement.
CSL #392884
An attempt to create a precomputed view with a non-primary-key/foreign-key join specification resulted in a fatal 132 error instead of the expected error 1903.
CSL #393039
Precomputed view maintenance failed for views that reference synonyms.
CSL #394788
TMU online backups sometimes failed with unpredictable errors.
CSL #397479
When a remote TMU operation exceeded the maximum number of discards specified in the TMU control file, the rb_ctmu program aborted and had to be stopped by using the Task Manager.
CSL #398852
When precomputed view maintenance was successful, the TMU issued warning messages 1932 and 1967 and returned a status code of 1. In Version 6.30.xC2 and later versions, the TMU issues information messages 2600 and 2601, which are equivalent to messages 1932 and 1967 but do not cause the warning status.
CSL #406175
In rare cases, an attempt to create a table with a large number of foreign-key constraints resulted in a fatal 132 error.
CSL #405681
The PASSWORD LOCK_PERIOD_HOURS parameter was not working as documented.
CSL #405558
An OPTIMIZE OFF load into a table with an index that had an extremely large key failed with error 236 when a full file system or segment was not the cause of the problem. In Version 6.30.xC3 and later versions, this kind of load operation returns appropriate error and warning messages.
CSL #408923
An attempt to drop the last PSU from an unattached segment (ALTER SEGMENT...DROP LAST STORAGE) resulted in a fatal error. In Version 6.30.xC3 and later versions, this command returns the appropriate syntax error.
CSL #410294
A table with a large number of segments and a history of attach and detach operations on those segments could not be unloaded with the TMU.
CSL #410388
An attempt to drop the last, empty PSU from a table (ALTER SEGMENT...DROP LAST STORAGE) failed with error 6405.
CSL #414468
When the creator of an object was dropped from the database, the next user that was created became the creator of that object and could view, alter, or drop the object according to the new user's privileges. In Version 6.30.xC3 and later versions, when the creator of an object is dropped, the first DBA user found in the system catalog becomes the owner of that object.
CSL #420643
A standard TMU discard file for duplicates was not created when a referential integrity (RI) discard file was specified for a load and OPTIMIZE ON or OFF mode was not explicitly defined in either the TMU control file or the rbw.config file.
CSL #421480
REORG operations on TARGET indexes resulted in performance degradation. See "SET TARGET_INDEX_MEMORY_GROWTH command" in this document.
CSL #423979, 424303
TMU loads failed when the TMU_BUFFERS parameter was set in the rbw.config file.
CSL #426391
Internal memory management problems during the maintenance of the backup segment caused certain TMU loads to hang. See "New level 0 backups required" in this document.
CSL #426730
The LA_SEL_ROWCNT attribute in the accounting file returned zero for SELECT statements instead of the correct row count.
CSL #426963
Tables that were created without a MAXROWS PER SEGMENT clause returned unexpected results for CHECK TABLE statements and queries because an unlimited number of rows could be loaded into the table. In V6.30.xC4 and later versions, if you attempt to insert more than 232 -1 rows into a segment, the server returns an error.
CSL #428374
If you issued multiple rbwservice.exe stop commands on Windows Server 2003 computers, client connections were terminated before their operations could complete. In Version 6.30.xC4 and later versions, the rbwservice.exe stop command behaves the same on Windows 2000 and Windows Server 2003 computers. Only the first stop command is recognized, allowing client connections to complete their operations before the service is stopped; subsequent stop commands are ignored.
CSL #434862
The TMU backup and restore features sent incorrect information to the administration daemon (rbwadmd), resulting in inaccurate Red Brick Warehouse backup and restore processes. See "New level 0 backups required" in this document.
CSL #396559, 423905, 423979, 433079, 434048, 426270

CSL #396559: The ALTER SYSTEM CLOSE USER SESSION ALL (DATABASE ALL) command could stop any of the system daemons.
CSL #423905, 423979: The ALTER SYSTEM CLOSE USER SESSION ALL statements caused either the Red Brick service to stop or other unexpected behavior.
CSL #433079, 434048: The ALTER SYSTEM CLOSE USER SESSION command did not stop the user session or caused other unexpected behavior.
CSL #426270: The ALTER SYSTEM CLOSE USER SESSION user_name PROCESS pid or ALL command sometimes stopped another user's session or a session with another process ID.

Note:

CSL #440109
An appropriate error message was not displayed when a separated-format load encountered rows that were wider than 8K. In Version 6.30.xC6, message 492 has been added; see page "RBL492" in this document.
CSL #70890,999,760
A primary key index that was built on multiple columns, including some VARCHAR columns, became corrupted during a load.
CSL #73008,999,760
An attempt to create a table with a long RANGE clause that did not contain newline characters caused the server to terminate.
CSL #89853,999,760
A single-segment B-TREE index with variable length keys might be corrupted, if the TMU ran with OPTIMIZE ON.
CSL #01213,999,760
A CASE expression with a character condition used the evaluation result of the first row and erroneously applied that result to all the remaining rows.
CSL #10660,999,760
When a foreign key constraint was added to a table with many constraints, system catalog might fail with the E_NOT_FOUND status.
CSL #12461,999,760
When the TMU was run with fixed-format records, and the RTRIM function was used against multi-byte VARCHAR columns, a buffer overrun might occur. This might cause the table to be incorrectly loaded with data.
CSL #27625,999,760
SELECT statements that use large IN lists caused the Red Brick service to stop.
CSL #325585, #28137,122,000
Customers requested the following enhancements in the TMU GENERATE statement:

Generation of DDL statements (including DDL for segments and indexes) for a table.
Generation of DDL statements (including DDL for segments and indexes) for the entire database.

CSL #88951,000,884
The rbw.show script returned incorrect result value for the number of active connections. The result value included the number of parallel server processes that the queries processed.
CSL #684787,999,760
The showlocks utility when run with an incorrect table ID caused a segmentation fault. For example, when showlocks utility was run as showlocks <db_path> 99999, the utility resulted in a segmentation fault because 99999 was an incorrect table ID.
CSL #91596,999,760
The EXPORT command returned a fatal error when the ENCLOSED BY clause was used in the export command.
CSL #01127,999,760
DECIMAL PACKED load returned a warning message. See "Option to revert to the V6.2 load behavior" in this document.
CSL #71781,442,000
The number of processors that were involved in the load operation could not be controlled on logical partition (LPAR.) This resulted in a degradation of the load performance even when the number of processors on the LPAR was tuned down. See "TUNE TMU_CPUS parameter" in this document.
CSL #86152,999,760
The IBM Red Brickcopy Management service works on all 32/64 bit Windows machines with winsock version 5.1,5.2 and 6.1.
CSL #00326,999,760
Red Brick Warehouse server gets terminated upon issuing multiple rbwservice stop command even when there are active connections. To avoid this problem please upgrade to Red Brick V6.30.xC14
CSL #07861,999,760
The acctview -t option prompting to enter time interval in milliseconds, does not display the progress in correct time interval.
CSL #82077,047,649
An user with USER_MANAGEMENT role should be able to create new users and maintain their passwords
CSL #50532,999,760
Red Brick RB_TMU not returning focus upon inputting an incorrect password in the command line on Windows 2008 R2
CSL #27334,999,760
Unexpected "** ERROR ** (7514) Maximum number of usable segments exceeded." message.

1.17.3 Query-related issues

CSL #394135
Domain MEDIUM and hybrid TARGET indexes on large tables were sometimes corrupted after a parallel REORG operation.
CSL #394838
Depending on the degree of parallelism at runtime, certain fact-to-fact STARjoin queries returned inconsistent results.
CSL #395953
When the FORCE_AGGREGATION_TASKS parameter was set to a value equal to or greater than the TOTALQUERYPROCS value, parallel aggregation queries returned fatal 132 errors.
CSL #402721
The query optimizer chose a STARjoin plan when a TARGETjoin plan would have been more efficient, except when the TARGETjoin was forced with a threshold setting of 100.
CSL #403687
A complex view with a large number of expressions in the select list returned a fatal 132 error because the internal representation of these expressions exceeded a VARCHAR offset limit. In Version 6.30.xC2 and later versions, the server returns an error message when this limit is reached.
CSL #404205
When dynamic or static segment elimination was used with local TARGETjoin, parallel query performance degraded because the system allocated an insufficient number of tasks to the TARGETjoin operator.
CSL #404302
The output of the SET STATS INFO command did not include statistics message 500.
CSL #407402
A parallel STARjoin query that used a STAR index with a very large number of dimensions returned a fatal 132 error.
CSL #408743
A query with a very large number of UNION operations took a long time to compile. In Version 6.30.xC3 and later versions, you can use a new SET command or TUNE parameter to stop the execution of long-running queries that contain an excessive number of UNION operations.
See "SET MAX_UNION_LIMIT command" in this document.
CSL #410595
A query with redundant OLAP functions inside a subquery failed during compilation.
CSL #410874
When the memory-mapping feature was enabled, queries returned intermittent 10410 errors.
CSL #419401
A database with a Thai locale returned inconsistent results for multiple runs of the same SELECT COUNT(DISTINCT) query within the same session.
CSL #419648
Certain queries that contain outer joins and multiple subquery predicates failed with fatal 132 errors.
CSL #423215
The week datepart for the EXTRACT scalar function is not compliant with ISO standard 8601. In V6.30.xC4 and later versions, you can enable ISO-compliant behavior by using a new SET command or configuration parameter. See "SET WEEKNUMBER_ISO8601 command" in this document.
CSL #423770
Certain queries with multiple fact tables failed with a fatal 132 error during query compilation.
CSL #424021
Depending on the size of the intermediate result sets for each fact table, certain fact-to-fact join queries did not complete their execution.
CSL #431584
Table scan queries that used query memory mapping failed because of faulty comparisons between the PSU filenames for memory-mapped dimension tables and indexes.
CSL #433374
If a query generated a TARGETScan plan, the compiler could incorrectly eliminate some required predicates.
CSL #431638
TARGETjoin performance was degraded when the plan switched to full index scans of local TARGET indexes.
CSL #431885
If the length of any string used in an SQL query exceeded 4000 characters, the RISQL Entry Tool connection failed.
CSL #432766
In databases with non-binary locales, such as Swedish, a query returned a fatal 132 error when the plan included a B-TREE 1-1 Match join and certain other conditions were true.
CSL #435069
The SET STAR INDEX AVAILABILITY command incorrectly influenced the processing of self-join queries on fact tables.
CSL #440220
A query with an aggregate expression in the ON condition for a join returned a fatal error. In Version 6.30.xC6, this kind of query returns error 100. See "RBS100" in this document.
CSL #440293; 77181,999,000
On Windows platforms, queries returned multiple 10132 and 1625 errors when the QUERY_MMAP parameter was set to ON. See "SET QUERY MMAP command" in this document.
CSL #66461,999,760
A query that contained a TO_CHAR function returned a fatal error when the format string was "DDD" and the source date referred to a leap year.
CSL #74631,999,760
When a query contained a large number of predicates or joins, a transitive closure of predicates could terminate prematurely. In these cases, the query returned incorrect results.
CSL #75275,999,760
A query failed with a fatal error when the Hash 1-1 Match operator was involved in the join; the intermediate row format in the query plan was variable (because of a VARCHAR data type); and the query memory limit was set low enough to require the intermediate join results to spill to disk.
CSL #10660,999,760
A query to fetch column descriptors of the foreign keys defined for a particular table failed because insufficient space was allocated to store these keys.
CSL #24445,033,000
A query failed with a fatal 1506 error when the query memory limit was set low enough to cause the results of the query to spill to disk.
CSL #23887,756,000
When a "?" character was used in a query to define a column name of a table, the query failed.
CSL #75138,999,760
A query returned a fatal 132 error and caused the Red Brick service to stop unexpectedly because of a problem with the Microsoft Visual C++ compiler.
CSL #75249,999,760
When the memory mapping feature was enabled, queries returned errors. In Version 6.30xC9, the memory mapping is disabled (OFF) by default. On Windows platforms, turn on memory mapping by either setting the OPTION QUERY_MMAP parameter in the rbw.config file to ON or by using the equivalent SET command.
CSL #15118,999,760
A subquery nested inside DELETE statements returned a fatal 10410 error that caused the delete operation to fail.
CSL #67993,999,760
A complex expression that contained aggregate functions in the select list and a FROM clause in the subquery returned a compilation error.
CSL #33297,999,000
The CREATE INDEX statement returned a fatal 132 error that caused the create index operation to fail.
CSL #33044,999,760
On Windows platforms, a parallel STARjoin query returned a fatal 132 error.
CSL #20821,999,760, 76524,000,834
The RESTORE SHOW command terminated the vacuum cleaner daemon.
CSL #67760,999,760
Multibyte characters were logged incorrectly and caused the rbwlog output to be corrupted.
CSL #0798,999,760
Data returned by the CASE statement was corrupted.
CSL #18430,999,760
Query that contained OLAP functions returned a fatal error.
CSL #37166,999,760
The SET COLUMN X FORMAT DECIMAL Y query returned inconsistent results in some cases. The query ran successfully in the RISQL tool.
CSL #35653,487,000
The ODBC-compliant database applications that called the SQLBindParameter function too many times caused a segmentation fault. Therefore, the IBM Red Brick Warehouse server crashed.
CSL #24730,999,760
Attempt to load a Red Brick created unload data file fails with error
"** FATAL ** (132) Internal error in function: 'badstatus E_ROW_NOT_FOUND ./src/rldtab.c:3841'".
CSL #87373,999,760
Unable to EXPORT display number in the format '-0.010'.
CSL #00729,999,760
The "set export_max_file_size 3G;" command fails with "** ERROR ** (8732) SET EXPORT_MAX_FILE_SIZE value must be less than 2G".
CSL #28900,999,760
Log message USA325R not output for some queries.
CSL #50629,999,760
Negative values beginning with 0 were not displayed as -0.nnn.
CSL #50629,999,760
Loads are not showing in DST_COMMANDS or DST_LOCKS on Windows 2008 R2 with Redbrick 6.30.FC14.
CSL #03225,999,760
Left Outer Join query is returning incorrect results.

1.17.4 Connectivity issues

CSL #397520
A table with single-character values in its VARCHAR primary-key column returned an invalid column-length error when viewed with Microsoft Access.
CSL #399556
When a CHAR column contained only space characters, ODBC applications returned no value at all for the column. In Version 6.30.xC2 and later versions, applications return fully padded fixed-length strings for all CHAR columns, including those that only contain spaces.
CSL #411779
The CHAR columns in the first row of a query result were not fully padded for an ODBC application that was running in asynchronous mode. All subsequent rows were padded as expected.
CSL #420340
The SQLColAttribute() ODBC function used the StringLengthPtr argument to return the number of bytes of the result for non-character data as well as character data.
CSL #20175
The JDBC Driver did not support escape clauses for table and column names that contain characters such as underscores and percent symbols. See Ã¢â‚¬Å“Escape characters in table and column names on page 35.
CSL #82914,999,000
The value of the ODBC statement attribute SQL_ATTR_MAX_ROWS that was set in one statement was incorrectly applied to other statements in the same connection.
CSL #02154,999,760
The Red Brick ODBC Driver returned a fatal 132 error when a multi-threaded ODBC application created and dropped statement handles frequently in a multi-CPU machine.
CSL #23763,999,760
When an application with a Red Brick client on a Windows Server 2003 computer tried to load data through a corrupted input pipe on a remote Linux server, the application failed to respond to user commands.
CSL #49142,005,000, #07776,999,760, #66358,999,760
Customers requested a 64-bit ODBC driver for Windows platforms. See "New features in Version 6.30.xC9", "Updates for 64-bit clients" in this document.
CSL #00185,999,760
The version number of the Client Connector Pack ODBC driver was not updated in the 6.30.xC7 and 6.30.xC8 releases. In Red Brick Warehouse Version 6.30.xC9, the version number of the Client Connector Pack ODBC driver is updated to 5.63.00.90.
CSL #81872,999,760
Customers requested support for the Intel-based Xeon and Pentium 64-bit processors for Windows and Vista platforms. IBM Red Brick Warehouse Version 6.30 already supports these platforms.
CSL #22170,057,649
The 6.30.FC13 CCP(64-bit) ODBC driver fails to connect to a 64 bit AIX 6.30.FC1 Red Brick warehouse due to incomplete entries in c:\Windows\rbodbc64.ini file.

1.17.5 Administrator tool issues

CSL #360120
The Japanese version of the Administrator tool displayed corrupted characters for labels within Vista Advisor analyses. In Version 2.30.2 and later versions, these labels are displayed in English.
CSL #391232
Using the Save As button on Show DDL-generated CREATE TABLE statements caused segment names and ranges to be fragmented and continued on the next line.
CSL #392426
The Show DDL output for ALTER MACRO statements on temporary and public macros did not include the TEMPORARY and PUBLIC keywords.
CSL #397544
The Show DDL output displayed incorrect information if the tables were created with leading spaces in the name after the opening single quote (for example, ' ABC ').
CSL #397923
The password settings CHANGE_INITIAL and CHANGE_MINIMUM_DAYS were not compatible; new users were prompted to change their passwords on first login but the changes failed because the password age had not elapsed. When these new users logged into the Administrator tool, the tool returned a fatal message 145. In Version 2.30.2 and later versions, the tool returns a new error message that instructs administrators to use the RISQL Entry Tool to drop and re-create new user accounts and reset their passwords.
CSL #404770
The Show DDL function returned incorrect syntax for locally segmented indexes.
CSL #408925
Response times for selecting and inspecting tables in the Database tab regressed from Version 2.20 to 2.30.
CSL #421687, 433369
After upgrading from Version 2.20 to Version 2.30 of the Administrator tool, customers encountered performance problems with Show DDL commands against large databases.
CSL #43545,110,846
A macro with the name "s" (or "S") returned an ODBC error. See "Macro cannot be named "s" (or "S")" in this document.
CSL #66975,999,760
Customers faced problems when they used the graphical user interface (GUI) administrator tool to drop an index segment on the database.
CSL #81832,999,616
The Red Brick Warehouse Administrator tool crashed when customers ran the queries in an asynchronous mode.
CSL #39366,442,000
The Show DDL function fails with overflow error 10273 using GUI admin tool.

1.17.6 Documentation issues

CSL #342878, 420886
Queries that return relatively small result sets sometimes spill the results to temporary space; this behavior was not documented. See "Spill files for Execute operator" in this document.
CSL #392733
The SQL Reference Guide does not document the fact that outer joins must contain equality predicates. See "SQL Reference Guide" in this document.
CSL #400533
The Administrator's Guide incorrectly states that the length of the Status column in the RBW_LOADINFO table is 128 bytes. The actual length is 256 bytes.
CSL #404345
The IBM Red Brick Vista® User's Guide does not explain the case where precomputed views cannot be used to rewrite the select expressions on either side of a UNION operator. See page "Precomputed view rewrites of UNION queries" in this document.
CSL #419011
Red Brick support for the Microsoft .NET Framework was not documented. See "Data access for .NET Framework applications" in this document.
CSL #423655
The output of the EXPORT command changed between Version 6.20 and Version 6.30, but this change was not documented. In V6.30.xC1 and later versions, EXPORT operations that use DELIMITED format or XML format do not return leading zeroes and leading spaces for numeric and decimal columns. To retain leading zeroes and spaces in your output, use EXTERNAL format. See also "Correct the EXPORT output for the DELIMITED and XML format examples" in this document.
CSL #424485, 430395
The Administrator's Guide does not include LA_TIME_OF_DAY in the list of accounting parameters, and the LA_SERVER_NAME description has the wrong datatype. See "LA_TIME_OF_DAY accounting parameter" in this document.
CSL #433180
The Administrator's Guide incorrectly states that database passwords must not exceed 8 characters. See "Maximum length of database passwords" in this document.
CSL #434991
The Administrator's Guide states incorrect dbsize estimates for certain CREATE TABLE statements. See page "Correct size estimates for tables" in this document.
CSL #435611
Some changes to the values stored in the RBW_SEGMENTS table were not documented. See "Changes to the RBW_SEGMENTS table" in this document.
CSL #421480
The TARGET_INDEX_MEMORY_GROWTH parameter applies only to OPTIMIZE ON index builds. This restriction was not documented. See "SET TARGET_INDEX_MEMORY_GROWTH command" in this document.
CSL #438500
Messages 320 and 367 sometimes return conflicting statistics information for load operations. See "Number of "processed rows" when the DISCARDS limit is reached" in this document.
CSL #86172,999,760
The inability of the Client TMU to connect through a firewall was not documented. See "Client TMU restriction" in this document.
CSL #89559,999,760
The formula for calculating free space in versioned database tables was not documented. See "Formula for calculating free space in versioned database tables" in this document.
CSL #61773,999,760
The use of the current Administrator tool (V2.30) with IBM Red Brick Warehouse V6.0.x and later databases was incorrectly documented. See "Administrator tool installation and compatibility" in this document.
CSL #75057,999,760
References to the Itanium operating system were incorrect. Itanium is replaced by Itanium 2 in these release notes.
CSL #40259,000,834
The solution for error RBA6532E was not documented. See "Messages and Codes Reference Guide" in this document.
CSL #04288,999,760
The list of supported Windows service packs was not up-to-date. See "Supported Windows platforms" in this document for an updated list.
CSL #18330,005,000
The information that the 64-bit ODBC driver is available only for IBM Red Brick Warehouse version 6.30.TC9 was incorrect. This driver is available on all platforms. This information is corrected in this release notes.
CSL #77628,000,834
The user privilege requirement when using Tivoli Storage Manager (TSM) for XBSA backups was not documented in the Table Management Utility Reference Guide. See "User privilege requirement when using Tivoli Storage Manager for XBSA backups" in this document.
CSL #02840,000,781
IBM Red Brick Warehouse version 6.30.xC12 and later versions are supported on the AIX 6.1 operating system. This was not documented in the release notes of the V6.30.xC12 release under the New features in Version 6.30.xC12 section.

1.18 Documentation notes

The Version 6.3 documentation is available online in the form of a standard IBM Information Center:

http://publib.boulder.ibm.com/infocenter/rb63help/

The following sections contain corrections to the documents that were published for IBM Red Brick Warehouse V6.30.xC1.

1.18.1 Administrator's Guide

This section lists the documentation notes for the Administrator's Guide.

Maximum length of database passwords

On pages 15 and 221 (under Note), the document states that database passwords must not exceed 8 characters. This limit applies only when all of the following conditions are true:

The executable is the RISQL Entry Tool, RISQL Reporter, TMU, or Client TMU.
The password is entered at the command-line password prompt, not as part of the command itself.
The platform is UNIX or Linux.

In all other login scenarios, you can use database passwords that exceed 8 characters up to a maximum of 128 characters.

Correct size estimates for tables

Page 97 incorrectly states: "For the preceding CREATE TABLE statement, dbsize estimates the size of the table to be 4,156,872 kilobytes."

The correct result is 4,282,840 kilobytes.

Page 102 incorrectly states: "For the CREATE TABLE statement for Fact1, dbsize estimates the size of the table to be 4,038,104 kilobytes."

The correct result is 4,156,872 kilobytes.

Configuring address space on Windows

Page 115 incorrectly states that "the maximum physical memory on Windows is 2 gigabytes."

The maximum physical memory on Windows computers varies. The default addressability limit on Windows is 2 gigabytes, but you can enable up to 3 gigabytes of address space for Red Brick Warehouse applications running on Windows Server 2003 machines by setting the /3GB switch in the boot.ini file. For details, see the Installation and Configuration Guide.

The /3GB switch is not supported on Windows 2000 machines.

Effect of a inaccurate fill factor for the VARCHAR column

Add the following information after the second bulleted list item in the "Effect of fill factor on performance" section on page 143.

Run out of space in a segment.

When the fill factor is inaccurate, you might run out of space in a segment and the system might return error 235. This error can occur even when the data that previously resided in this segment is deleted and then reloaded in the segment.

For more information on specifying an accurate fill factor, see the "Setting the VARCHAR column fill factor" section in the Administrator's Guide.

Formula for calculating free space in versioned database tables

Add the following information to the "Versioned DELETE Operations" section on page 183.

In a versioned database, REPLACE mode loads must keep deleted rows allocated in the event of a rollback operation. When all the rows in a block are deleted, the block is freed, except when the rows are deleted by a versioning transaction. The block cannot be freed because the versioning transaction might be rolled back. The block is retained as part of the table; however, all the rows in the block are deleted. The deleted rows are reused when the table is loaded again.

Because of this behavior, you cannot rely on the RBW_SEGMENTS.TOTALFREE and RBW_STORAGE.USED values to determine the amount of available space in table segments after versioned transactions have deleted or replaced rows. Instead, run the CHECK TABLE command, then calculate the amount of available space (in kilobytes) by using this formula:
RBW_SEGMENTS.TOTALFREE + (free blocks from CHECK TABLE * 8K) + (freespace from CHECK TABLE)

Status column length

Page 411 incorrectly states that the length of the Status column in the RBW_LOADINFO table is 128 bytes. The actual length is 256 bytes.

LA_TIME_OF_DAY accounting parameter

On page 250, add the LA_TIME_OF_DAY parameter to the table and update the descriptions of the LA_SEL_ROWCNT and LA_SERVER_NAME parameters:

Parameter: LA_TIME_OF_DAY
Data type: SDDT_INT4
Description: Timestamp of the component that ran the statement.

Parameter: LA_SEL_ROWCNT
Data type: SDDT_INT4
Description: Row count for a SELECT, INSERT, UPDATE, or DELETE statement.

Parameter: LA_SERVER_NAME
Data type: SDDT_CHAR
Description: Warehouse server name (the value set for the RB_HOST environment variable).

Note: Other LA parameters that are not documented in the table either do not apply to the accounting log or are for internal use only.

Syntax for the rbwservice.exe utility

Add the following information to page 332:

Use the rbwservice utility to start, stop, create, delete, or check the status of (query) Red Brick services.

The following diagram shows the syntax for the rbwservice utility:

>>-rbwservice--+-----------------+-- -t--type--+-----------+---->
'-\\computer_name-' '- -h--host-'

>--+---------------+--+- -create-+-----------------------------><
'- -p--password-' +- -delete-+
+- -start--+
+- -stop---+
'- -query--'

Follow the order of the arguments shown in the diagram. The server returns an error if you specify arguments in the incorrect order.

\\computer_name

The computer where the service is running or will run. If no computer name is given, the local computer is used.
type (-t)

RBW for the Red Brick Warehouse Service
CM for the Copy Management Service

host (-h)

The Red Brick host name.
password (-p)

The password for the redbrick user account, which you should use to create the service. The password is not required for the delete, start, stop, and query options. If you do not provide a password, the system local account is used.
To display the rbwservice syntax, enter rbwservice with no options at the system prompt.

The following examples demonstrate some correct uses of the rbwservice utility:

C:\Documents and Settings\redbrick>rbwservice \\brick.abc.def.com -t RBW -query
Interrogating service RedBrickServiceRB630TC1 ...
Red Brick Service RedBrickServiceRB630TC1 is running.

C:\Documents and Settings\redbrick>rbwservice -t RBW -stop
Stopping service RedBrickServiceRB630TC1 ...
Stopped service RedBrickServiceRB630TC1

C:\Documents and Settings\redbrick>rbwservice -t CM -query
Interrogating service RedBrickService-CopyManagement ...
Red Brick Service RedBrickService-CopyManagement is not running.

Default value for TMU_SERIAL_MODE parameter

On page 372, update the configuration file entry for the TMU_SERIAL_MODE parameter. The default value is OFF.

# Default PTMU behavior
#TUNE TMU_SERIAL_MODE { OFF | ON }

Changes to the RBW_SEGMENTS table

On page 415, add the following information to the description of the RBW_SEGMENTS table:

All indexes, including TARGET indexes that are created in default segments, are implicitly segmented by range. Queries of the RBW_SEGMENTS table return the following values for all single-segment indexes, whether the segment is a named segment or a default segment:

NCOLS = 1
MINKEY = MIN
MAXKEY = MAX

For example:

RISQL> create TARGET index CLASS_TG_IDX on CLASS (CLASS_TYPE) with fillfactor 100 domain size large;
RISQL> select ncols, minkey, maxkey from rbw_segments where iname = 'CLASS_TG_IDX';
NCOLS MINKEY MAXKEY
1 MIN MAX

Correct row limit for tables

On page 14, the "Database limits" section incorrectly states that a table can contain a maximum of 248 rows.

A table can have a maximum of "2 to the power of 48" rows (that is, 281474976710656 rows).

Methods for attaching a STAR index to a segment

On page 285, in the "Attaching and detaching segments" section, replace the existing information about attaching segments to a STAR index with the following text:

Use one of the following methods to attach a segment to a STAR index:

Specify the data segment name in the RANGE LIKE SEGMENT clause, if you want to attach the STAR index to either the last segment or the first segment of the segment range.
Specify a range based on the segment name and row numbers (RBW_ROWNUM pseudocolumn) of the segmenting column for the referenced (dimension) table, if the existing segment to which you are attaching a STAR index is not a boundary segment. Define the segmenting column of the referenced table in the CREATE TABLE statement.

Macro cannot be named "s" (or "S")

Add the following information as the last bulleted list item in the "Guidelines for macro definitions" section on page 170:

Do not create a macro with the name "s" (or "S"). The Administrator tool uses this name internally to store information.

Enhanced logging using CALLOUT scripts

Add the "Enhanced logging using CALLOUT scripts" section to page 245 after Query logging.

CALLOUT scripts are used to run an external command from the product if fatal errors are generated.

Use the following methods to activate CALLOUT scripts:

Set the OPTION CALLOUT_SCRIPT ON | OFF option to ON in the rbw.config file on the server.
Set the SET CALLOUT SCRIPT ON | OFF to ON at the RISQL prompt.

The CALLOUT script is named rbw.cos and is available in the Red Brick Warehouse installation directory. Sections in the CALLOUT script contain the necessary details for running specific tools when an error occurs.
The following are some guidelines on sections:

Every section begins with an error number and ends with a colon. For example,"132:" is a valid section name.
Sections with a misplaced colon are not supported. For example, ":132", "13:2", and "ERR132:" are invalid section names.
Only five error sections and five commands in each section are supported.

An error number is based on the section name and all the guidelines that apply to a section name also apply to the error number.

A CALLOUT script also contains comments. The following are some guidelines on comments:

Every line that starts with a hash symbol (#) is a comment. For example, "# This is the start of the section" is a valid comment.
Multiple line and inline comments are not supported. For example, "This is the start of the section #" is an invalid comment.

The output for the CALLOUT scripts is available in the redbrick_dir\logs directory, where redbrick_dir is the Red Brick installation directory.
The format for the standard output file is as follows:
section_name.command_name.timestampcommand_number ThreadID or PID.stdout, where PID is the process ID.
For example, 132.concdump.03252009130126532.stdout
The format for the error file is as follows:
section_name.command_name.timestampcommand_number ThreadID or PID.stderr, where PID is the process ID.
132.concdump.03252009130126532.stderr

A CALLOUT script uses the Red Brick tools, such as concdump, syschk, vlgdump, and so on, to get the necessary information when a fatal occurs. The CALLOUT script does not support redirection operators such as ">", "|", and so on. You must specify the absolute path of the tool in the CALLOUT script.

Changes to the Configuration information table in Appendix B

On page 384, add the following information to the Configuration information table after BARTAPE.

File element: OPTION CALLOUT_SCRIPT
Description: Default: OFF This parameter is required when the query causes a fatal error and calls the CALLOUT script feature.

Changes to the Summary of configuration parameters table in Appendix B

On page 401, add the following information to the Summary of configuration parameters table after PERFORMANCE_ MONITOR_ MAXSESSIONS.

	Set with			Affects
Parameters	rbw.config	SQLSET	TMU command	Server	TMU	Daemon
CALLOUT_SCRIPT	x	x		x

Acctview reporting tool for accounting

On page 254, after Controlling accounting, add the following information about acctview reporting tool for accounting.

IBM Red Brick Warehouse V6.30.xC12 contains the acctview tool to read and interpret the accounting logs. The acctview tool is available in the redbrick_dir\utils\service directory, where redbrick_dir is the Red Brick installation directory.

The acctview tool uses the options that you specify to read the accounting logs. The tool also generates the TMU control file and a text file. You can use the TMU control file and the loader to load the data in the text file into a database table.

Loading the data into a table using the loader fails in the following conditions:

The text file that the acctview tool generates uses "***" as a separator. The loading fails if the text file contains a LOAD statement with "***" as a separator. Because the "***" in the LOAD statement is considered a separator, the text after the separator is ignored, and incomplete data is loaded in the table.
The acctview tool reads the log files and displays data at the command prompt or saves the data in a TMU control file and in a text file depending on the option that you select. If you want to see the data on the command prompt, the acctview tool converts the data to HH:MM:SS centiseconds format and displays it. For example: 10:30:32 34, where 10 is HH (hours), 30 is MM (minutes), 32 is SS (seconds), and 34 is centiseconds. However, if you want to save the data in a text file, the tool saves the data in the centiseconds format. Therefore, the Elapsed time, UserCPU time, and SystemCPU time columns in the table display information in the centiseconds format in the text file. Loading fails if the integer column contains a colon.

You must create the following table to use acctview to load data:

CREATE TABLE ACCOUNTING (
DATETIME CHARACTER(20),
USERNAME CHARACTER(257),
SERVER INTEGER,
DBNAME CHARACTER(257),
VERB CHARACTER(17),
ELAPSED INTEGER,
UCPU INTEGER,
SCPU INTEGER,
LREAD INTEGER,
LWRITE INTEGER,
COST FLOAT,
MEMUSED INTEGER,
SPILLCOUNT INTEGER,
CHILDCOUNT INTEGER,
SELECTROWCOUNT INTEGER,
LOADROWCOUNT INTEGER,
SOURCEID CHARACTER(257),
PROCESSID CHARACTER(257),
SQLTEXT CHARACTER(257)
);

1.18.2 Client Installation and Connectivity Guide

This section lists the documentation notes for the Client Installation and Connectivity Guide.

SQL_ATTR_LOGIN_TIMEOUT connection attribute

On page 13, remove the SQL_ATTR_LOGIN_TIMEOUT connection attribute from the list of supported attributes for the SQLGetConnectAttr and SQLSetConnectAttr functions. This connection attribute is not supported.

Escape characters in table and column names

On page 75, add the following information:

The following JDBC Driver functions support escape characters in table names and column names:

DataBaseMetadata.getColumns()
DataBaseMetadata.getTables()
DataBaseMetadata.getColumnPrivileges()
DataBaseMetadata.getTablePrivileges()

For example:

DataBaseMetadata.getColumns(null, null, "RBW\\_TABLES", "%")

Updates for 64-bit clients

On page 1, remove the sentence "These components reside in the \CCP\Client32 directory on the software CD-ROM." from the "Components of the Client Connector Pack" section, and add the following note after the Product Description table:

Note:

In 64-bit clients, the components reside in the \CCP\Client64 directory.
In 32-bit clients, the components reside in the \CCP\Client32 directory.

On page 2, in the "ODBC driver requirements" section, replace the sentence "The Red Brick ODBC Driver released with Client Connector Pack Version 2.3 and IBM Red Brick Warehouse 6.3 is available in a 32-bit version only." with the following sentence:

On page 2, replace the existing information of the first bulleted list item in the "Installing Client Connector Pack components" section with the following information:

On page 3, in the "Installing Client Connector Pack components" section, add the following note to fifth numbered list item in the "To start the installation":

Note:

On page 5, in the "Uninstalling the Client Connector Pack" section, replace the existing information in the "To uninstall the Client Connector Pack" with the following information:

Choose Start > Settings > Control Panel > Add/Remove Programs to check if your registry file already has Client Connector Pack installed. If Client Connector Pack is installed, Client32 or Client64 appears on the list.
Choose Start > Programs > Red Brick Client (32) > Uninstaller to uninstall the 32-bit Client Connector Pack from Windows.

Note:

To uninstall the 64-bit Client Connector Pack from Windows Vista, choose Start > Control Panel > Programs > Programs and Features > Red Brick Client (64).
To uninstall the 64-bit Client Connector Pack from Windows Server 2003, follow the below procedure.

Right click on x64/setup.exe and run as administrator. The same setup from which the server was installed.
Select Maintain or upgrade an existing instance.(select the server to be removed).
Select Remove option from(Modify,Repair,Remove) Program Maintenance Wizard.

On page 6, in the "Configuring data sources on Windows" section:

Replace the existing information of the first numbered list item in the "To reconfigure a DSN" and "To delete a DSN" with the following information:
For 32-bit clients, choose Start > Settings > Control Panel > ODBC Data Sources to display the ODBC Data Source Administrator dialog box. However, for 64-bit clients run the following command from the command prompt: c:\windows\system32\odbcad32.exe.
Replace the existing information of the first numbered list item in the "To test a DSN" with the following information:
For 32-bit clients, choose Start > Programs (or Program Manager) > Red Brick Client 32. For 64-bit clients, choose Start > Programs (or Program Manager) > IBM > Red Brick Client (64)

On page 19, in the "SQLGetInfo information types" section:

Add the information "or RB64ODBC.DLL" in the return values column corresponding to the SQL_DRIVER_NAME information type.
Replace the information in the return values column corresponding to the SQL_TXN_CAPABLE information type with the following:
SQL_TC_NONE or TXN_CAPABLE_ALL if SQL_TXN_CAPABLE is set to the ODBC application name (in the rbodbc32.ini file for 32-bit clients and 64-bit clients on Windows, or as an environment variable on UNIX).

1.18.3 Query Performance Guide

This section lists the documentation notes for the Query Performance Guide.

Spill files for Execute operators

On page 30, add the following paragraph to the "Spill process" section:
In order to reserve sufficient query memory for the operators that are most likely to need it, the Execute operator at the top of a query plan is always allocated a small amount of memory. If the ODBC or JDBC client program that receives rows from the Execute operator cannot consume the rows quickly enough, the operator spills the rows to temporary space. This behavior is a direct result of the client's inability to process the rows and can occur even for queries with relatively small result sets.

1.18.4 SQL Reference Guide

This section lists the documentation notes for the SQL Reference Guide.

Add the following statement to pages 188 and 207

Outer joins must contain equality predicates. Non-equality predicates are only supported for inner joins.

Add the following text to the definition of the ON search_condition on page 188

Although the predicate in an ON condition can be a complex expression, the expression must not contain aggregate functions, RISQL functions, or SQL OLAP functions.

Add the following statement to the description of the DROP LAST STORAGE clause on page 276

The OF TABLE or OF INDEX clause is required in an ALTER SEGMENT...DROP LAST STORAGE statement. You cannot drop the last PSU from a segment that is not attached to a table or index.

ALTER SYSTEM CHANGE STACK_SIZE command

Add the following ALTER SYSTEM command to Chapter 8 on page 289.

The ALTER SYSTEM CHANGE STACK_SIZE command increases the stack size for the Red Brick server. The syntax for this command is as follows:
ALTER SYSTEM CHANGE STACK_SIZE TO size [K|M]
where size is a positive integer. You must specify either K (kilobytes) or M (megabytes).

This command overrides the STACK_SIZE parameter of the rbw.config file and sets the stack size for all subsequent connections to the database, and for subsequent threads created in the current session. Threads that are already created retain their original stack size.

This command prevents the failure of the Red Brick service because of stack overflow. For example, processing of a query with a large IN list internally builds up huge expressions that require more stack space than the default stack size (1 MB for the Windows platform). These huge expressions cause the server to run out of stack space and return a stack overflow error.

To reset the stack size to the value currently specified in the rbw.config file (or the default, if the STACK_SIZE parameter is not specified), use the following command:
ALTER SYSTEM CHANGE STACK_SIZE TO DEFAULT
The ALTER SYSTEM command is useful for running occasional queries that require additional stack space. The DBA can reset the stack size to the default value as soon as these memory-intensive queries are run.

Add the following statement to the Authorization description for the CREATE HIERARCHY command on page 321

A hierarchy created by a user who belongs to the RESOURCE role is not visible to that user in the system tables unless the same user created the base table on which the hierarchy is defined.

Correct the description of valid EXPORT delimiter characters on pages 406 and 462

The Tab key is a valid delimiter. You can set Tab as the delimiter either within the EXPORT statement itself (by using the DELIMITED BY syntax) or by using the SET EXPORT_DELIMITER command:
set export_delimiter '<Tab key>';

You cannot set the EXPORT delimiter to the Tab key by using the OPTION EXPORT_DELIMITER parameter in the rbw.config file.

Correct the EXPORT output for the DELIMITED and XML format examples on pages 410 through 412

The examples of EXPORT output files for DELIMITED and XML formats show leading zeroes and leading spaces for numeric and decimal columns, respectively. In V6.30.xC1 and later versions, these zeroes and spaces are returned only for EXPORT operations that use the EXTERNAL format.

LOCK DATABASE description

On page 431, the LOCK DATABASE WRITE mode description should read as follows:

Once a database is locked in WRITE mode:

The database cannot be locked in any other mode.
The database server does not allow queries or updates to the database, except from the session that locks the database.

SET MAX_UNION_LIMIT command

Add the following SET command description to Chapter 9.

The SET MAX_UNION_LIMIT command defines the maximum number of UNION operations that a single query can process. This command does not apply to INTERSECT and EXCEPT operations. The purpose of this command is to prevent very complex UNION queries from compiling and executing, which takes a long time and requires a large amount of memory. For example, the following SET command imposes the limit at 100 UNION operations:
set max_union_limit 100;

A query that exceeds this limit does not compile or execute and immediately returns an error. To apply the limit to all sessions, set the equivalent TUNE parameter in the rbw.config file:
tune max_union_limit 100

SET QUERY MMAP command

Add the following recommendation to the SET command description on page 492.

On Windows platforms under heavy workload conditions, turn off memory mapping by either setting the OPTION QUERY_MMAP parameter in the rbw.config file to OFF or using the equivalent SET command.

SET WEEKNUMBER_ISO8601 command

Add the following SET command description to Chapter 9.

The SET WEEKNUMBER_ISO8601 command defines the numbering scheme for week values in datetime expressions. If you set WEEKNUMBER_ISO8601 to ON, queries that extract week dateparts return values that are ISO8601-compliant. According to the ISO standard, the first week of a given year (week 1) is the first week that has the majority of its 7 weekdays inside that year. If the week containing January 1st has four or more days inside the new year, it is week 1; otherwise, it is week 52 or 53 of the previous year, and the following week is week 1. To fully comply with the ISO8601 standard, the SET WEEKNUMBER_ISO8601 command sets the first day of the week to Monday, regardless of the setting of the FIRST_DAYOFWEEK parameter, which by default treats Sunday as day 1.

The default value for the SET WEEKNUMBER_ISO8601 command (and its equivalent configuration parameter) is OFF. The default behavior is to treat January 1st of a given year and the rest of that week as week 1, regardless of the number of days in that week.

The following examples demonstrate the default behavior and the ISO-compliant behavior. The first run of the query returns the default week-numbering scheme for the first few days of January, 1999. The second run returns ISO-compliant week values for the same period because the WEEKNUMBER_ISO8601 parameter is set to ON.

RISQL> select date, day, extract(week from date) as weekno
from period where date between '01-01-1999' and '01-09-1999';
DATE DAY WEEKNO
1999-01-01 FR 1
1999-01-02 SA 1
1999-01-03 SU 2
1999-01-04 MO 2
1999-01-05 TU 2
1999-01-06 WE 2
1999-01-07 TH 2
1999-01-08 FR 2
1999-01-09 SA 2

RISQL> set weeknumber_iso8601 on;

RISQL> select date, day, extract(week from date) as weekno
from period where date between '01-01-1999' and '01-09-1999';
DATE DAY WEEKNO
1999-01-01 FR 53
1999-01-02 SA 53
1999-01-03 SU 53
1999-01-04 MO 1
1999-01-05 TU 1
1999-01-06 WE 1
1999-01-07 TH 1
1999-01-08 FR 1
1999-01-09 SA 1

The SET command applies to individual sessions. To set ISO-compliant behavior for all sessions, enter the following line in the rbw.config file:
NLS_LOCALE WEEKNUMBER_ISO8601 ON

SET TARGET_INDEX_MEMORY_GROWTH command

Add the following SET command description to Chapter 9.

The TARGET_INDEX_MEMORY_GROWTH command defines the type of memory growth for TARGET index builds. Use this command for both initial index builds and subsequent REORG operations; however, this command only takes effect when OPTIMIZE ON is set.

You can set the growth type to EXPONENTIAL or LINEAR. If a TARGET index has very low cardinality or the data distribution is skewed, set the TARGET_INDEX_MEMORY_GROWTH parameter to EXPONENTIAL. If the TARGET index has a random set of values or the data distribution is uniform, set the parameter to LINEAR. Skew is the most important factor to consider. The LINEAR option will not work well if some of the index keys reference only a few rows but other keys reference a large number of rows.

The default value for this command (and the corresponding OPTION parameter in the rbw.config file) is LINEAR. The SET command applies to the current session only; the OPTION parameter applies to all sessions. The SET command can be used in both server sessions and TMU control files.

Replace the text in the Usage Notes section on page 295 with the following text

It is not possible to calculate in advance the exact space requirements of an ALTER TABLE statement when:

The statement contains VARCHAR columns.

The statement does not contain any VARCHAR columns, but the specified table in the statement already contains VARCHAR columns.

Add the following statement to the macros for statistical functions on page 84

Before using the following scalar functions, you must run the CREATE MACRO statement:

EXP
LN
SQRT

Add a cross reference to Administrator's Guide in the CREATE TABLE > Segment_specification section

In the SQL Statements and RISQL extensions chapter, under the CREATE TABLE > Segment_specification section, add the following line.

For detailed information about using named segments, go to the IBM Red Brick Warehouse 6.3 Information Center at http://publib.boulder.ibm.com/infocenter/rbhelp/v6r3/index.jsp?, and search for planning for segmented storage and rules of segmenting.

1.18.5 Table Management Utility Reference Guide

This section lists the documentation notes for the Table Management Utility Reference Guide.

Client TMU restriction

Add the following restriction to page 17.

The Client TMU (rb_ctmu) cannot be used to connect to the server-side TMU through a firewall. The TCP/IP filtering feature, available with Windows 2000, is also not supported.

Prerequisite for performing TMU load operation

Add the following information to the "Procedure for loading data" section on page 65.

Before you attempt the load operation, allow the Red Brick service to start completely. If you run a TMU load operation before the Red Brick service starts, the system returns a fatal exception.

Number of "processed rows" when the DISCARDS limit is reached

Add the following information to the DISCARDS keyword description on page 97.

When the DISCARDS limit is reached for a non-versioned load, messages 320 and 367 might return inconsistent statistical information. The number of "processed rows," as reported by message 320, might be less than the total number of rows loaded and discarded, as reported by message 367. This behavior is expected.

For non-versioned loads, all input rows are processed in batches to optimize load performance. The rollback operation that occurs when the DISCARDS limit is reached rolls back the successfully loaded rows from the last batch but not the discarded rows. The discards have been written to the discard file and this operation cannot be rolled back. Therefore, the discards from the last batch are not counted as part of the "rows processed" total in message 320.

For example, a table is loaded with DISCARDS set to 15,040. The load is processed in 100-row batches, and the DISCARDS limit is reached during the 300th batch, causing a rollback of that batch. 29,900 rows (299 batches * 100 rows) have been processed, as reflected by message 320. However, message 367 reports that 14,899 rows have been loaded and 15,040 have been discarded, a total of 29,939 rows. The difference of 39 rows in the two totals is accounted for by the discards in the 300th batch.

Rules for specifying namespace prefixes

The following information is missing from pages 119 and 120.

You must terminate a path_prefix at the beginning of an xml_path specification with a colon, and no white spaces are allowed between the prefix and the colon. For example, "namespace1:" is legal but "namespace1 :" returns an error. This rule does not apply to the element_prefix and attribute_prefix specifications within XML paths. (See "For XML loads, invalid namespace prefixes sometimes cause inappropriate errors" for information about a related known issue with invalid namespace prefixes.)

Correction to UNLOAD syntax description

Remove the phrase "during an unload-to-external operation" from the DDLFILE and TMUFILE keyword descriptions on page 197. DDL and TMU output files are supported for both internal and external unload operations.

Generating DDL statements for the entire database

On page 211, in the "Generating CREATE TABLE statements" section, add the following note:

Note:

To generate DDL for all the tables in a database including the segments and indexes on the tables, replace table_name with all, that is:

The TMU GENERATE statement does not drop the default primary key index from the table in the database.

Generating DDL statements for a table

On page 211, in the "Generating CREATE TABLE statements" section:

Replace the sentence "The file does not include any segment information." from the DDLFILE 'filename' description on page 211 with the following sentence:
The file can include segment and index information for the table.

Replace the information in the "Example: GENERATE statements and external-format data" section with the following information:

User privilege requirement when using Tivoli Storage Manager for XBSA backups

Add the following user privilege requirement to the description of configuration requirements for Tivoli Storage Manager (TSM) on page 302.

Make sure that the rb_tmu user (the user running backups) has administrator privileges.

TUNE TMU_CPUS parameter

Add the TUNE TMU_CPUS num_cpus parameter description to "Parallel loading tasks (PTMU only)" on page 55.

The TUNE parameter controls the number of processors that are used in the load operation. The TUNE parameter is a nonzero integer. The default value for the parameter is the number of processors that are present on the computer.

Option to revert to the V6.2 load behavior

Add the "Option to revert to the V6.2 load behavior" section before "REORG tasks (PTMU only)" on page 54.

You can add the TMU_DECIMAL_PACKED_WEAK_CHECKING option to the IBM Red Brick Warehouse XC12 release configuration file to revert to V6.2 load behavior. Set the TMU_DECIMAL_PACKED_WEAK_CHECKING option to ON to load decimal packed data in the database even when loading causes the data to be truncated.

1.18.6 Vista User's Guide

This section lists the documentation notes for the Vista User's Guide.

Defining explicit hierarchies on tables referenced by derived dimensions

Add the following information to page 26.

To make sure that the query rewrite system can make efficient use of the derived dimensions you create, define explicit hierarchies on the detail dimension table columns referenced by the derived dimension table. Specifically, create hierarchies from the column that is declared as the primary key in the derived dimension to every other column that is referenced in the derived dimension. Be sure to create these hierarchies on the detail dimension instances of these columns, not the derived dimension columns. If you do not create these hierarchies, the optimal precomputed view might not be chosen or inefficient SQL might be generated for your rewritten queries.

For example, consider the following detail dimension table:
create table sales_area
(areakey int not null, hq_city char(20) not null, region char(20) not null,
country char(20) not null, geo char(20) not null,
primary key (areakey)) maxrows per segment 2500;

Assume that the following derived dimension is created with sales_area as its detail dimension:
create table sales_area_dd
(region char(20) not null, country char(20) not null, geo char(20) not null,
rowct int, primary key (region)) maxrows per segment 1000;

The region column is defined as the primary key of this derived dimension. Therefore, declare the following hierarchies against the detail table sales_area:

create hierarchy sales_area_hier
(from sales_area(region) to sales_area(country),
from sales_area(region) to sales_area(geo));

Precomputed view rewrites of UNION queries

Add the following discussion to the "Queries that cannot be rewritten" section on page 19.

Queries that contain set operators (UNION, INTERSECT, and EXCEPT) are evaluated block by block. Each select expression on either side of the set operator is a potential rewrite candidate, based on the availability of valid precomputed views that contain precomputed results at the right level of aggregation. However, in order to qualify for precomputed view rewrites, the query must compute the aggregate totals before the select expressions are unioned.

For example, assume that the following valid precomputed view exists in the Aroma database:

create view store_sales_view (perkey, storekey, dollars, rowct) as
(select perkey, storekey, sum(dollars), count(*) from sales
group by perkey, storekey)
using store_sales (perkey, storekey, dollars, rowct);

The UNION select expressions in the following subquery are rewritten against this precomputed view because they compute their own aggregate totals before the two result sets are unioned:

select store.storekey, period.perkey, total_sales
from
(select storekey, perkey, sum(dollars) as total_sales
from sales group by storekey, perkey
union
select storekey, perkey, sum(dollars) as total_sales
from sales2 group by storekey, perkey) as salesunion,
period, store
where salesunion.perkey = period.perkey
and salesunion.storekey = store.storekey
order by store.storekey, period.perkey;

The following query, in which the aggregations are computed in the outer query after the subquery results have been unioned, cannot be rewritten:

select store.storekey, period.perkey, sum(dollars) as total_sales
from
(select storekey, perkey, dollars
from sales
union
select storekey, perkey, dollars
from sales2) as salesunion,
period, store
where salesunion.perkey = period.perkey
and salesunion.storekey = store.storekey
group by store.storekey, period.perkey
order by store.storekey, period.perkey;

The major difference between the two queries is that aggregation occurs in the inner query in the first case but in the outer query in the second case.

1.18.7 Installation and Configuration Guide for Windows Platforms

This section lists the documentation notes for the Installation and Configuration Guide for Windows Platforms.

Updates for the Red Brick Warehouse Server installation and uninstallation paths

On page 12, in the "Running the setup program" section, replace the information in the fifth list item with the following information:

Enter the following path in the text field, with drive as the letter that maps to your CD-ROM drive:

For 32-bit Red Brick Server: drive:\rbw\i386\disk1\setup.
For 64-bit Red Brick Server: drive:\rbw\x64\disk1\setup.

Note: Before you install the Red Brick Warehouse Server on Windows Server 2008, you must set the RB_ CONFIG system variable to point to the Red Brick Warehouse installation path. Ensure that the value of the RB_CONFIG variable ends with a back slash (\). For example, if you installed Red Brick Warehouse Server in the C:\RedBrick\RBW folder, set the RB_ CONFIG variable to C:\RedBrick\RBW\. If you restart a Red Brick Warehouse service on Windows Server 2008, ensure that the RB_CONFIG variable points to the correct Red Brick Warehouse Server.

On page 24, in the "Removing IBM Red Brick Warehouse" section, replace the information in the fourth list item with the following information:

To uninstall 32-bit Red Brick Warehouse, click Start > Programs > Red Brick Warehouse > Uninstaller.
To uninstall 64-bit Red Brick Warehouse, follow the below procedure.

Right click on x64/setup.exe and run as administrator. The same setup from which the server was installed.
Select Maintain or upgrade an existing instance.(select the server to be removed).
Select Remove option from(Modify,Repair,Remove) Program Maintenance Wizard.

1.18.8 RISQL Entry Tool and RISQL Reporter User's Guide

This section lists the documentation notes for the RISQL Entry Tool and RISQL Reporter User's Guide.

Using the RISQL tool in a Windows 64-bit system

This section is applicable only to Windows Server 2008 (64-bit).

On page 4, add the following information after "Windows Only" in the "Starting the tool" section:

When one of the following conditions is true, you must either enable the administrator option for the command prompt or disable the User Account Control (UAC) security feature:

Before you install IBM Red Brick Warehouse.
When you want to start the RISQL Entry Tool by using a non-administrator user ID on a computer where 64-bit Red Brick Warehouse is installed.

1.18.9 Messages and Codes Reference Guide

The following messages were either added or changed in V6.30.xC2 through V6.30.xC15:

------------------------------------------------------------------------
RBS100E Aggregation functions, RISQL display functions, and OLAP functions are not allowed in the WHERE clause or in the ON clause.

System action: The WHERE clause or the ON clause included an aggregation function, an OLAP function, or a RISQL display function, or a column alias for such a function. Predicates containing display or OLAP functions must be specified in the WHEN clause. Predicates containing aggregation functions must be specified in the HAVING clause.

User response: Correct the error and resubmit the statement.

------------------------------------------------------------------------
RBL485W The model table: table_name cannot be upgraded.

System action: The database contains a Data Mine MODEL table. Red Brick Warehouse no longer supports MODEL tables and the model table specified in the message will not exist in the upgraded database.

User response: None.

------------------------------------------------------------------------
RBL492W The length of input row num in file file_name is longer than maximum allowed length of len bytes.

System action: This happens in the row conversion stage, when reading data in separated format, and input row is longer than expected maximum length. Internal default maximum row length is used when no RECORDLEN was specified. Data load will terminate. Please provide RECORDLEN parameter and re-start.

User response: Check the RECORDLEN parameter and adjust it to match the input data row length.

------------------------------------------------------------------------
RBA801W Valid values for WEEKNUMBER_ISO8601 are ON and OFF.

System action: An invalid value was specified for the settable WEEKNUMBER_ISO8601.

User response: Correct and resubmit the statement.

------------------------------------------------------------------------
RBS1702E Number of UNION operators in the query exceeds the MAX_UNION_LIMIT setting.

System action: The number of UNION operators in the query exceeds the limit set by the MAX_UNION_LIMIT parameter.

User response: Increase the MAX_UNION_LIMIT parameter and submit the query again. You can change this parameter by running a SET command or updating the rbw.config file.

------------------------------------------------------------------------
RBL2600I The precomputed view viewname has been marked invalid.

System action: A table has been updated via a load operation, thus invalidating all the precomputed views defined on the table.

User response: Update the precomputed tables to match the new data in the detail table. After the precomputed tables have been updated to match the data in the detail table, you can then mark the precomputed views valid with either the ALTER VIEW view_name SET VALID command or the ALTER TABLE table_name SET PRECOMPUTED VIEWS VALID command.

------------------------------------------------------------------------
RBL2601I Precomputed view maintenance for viewname succeeded and it has been marked valid.

System action: The view maintenance operation for the named view succeeded and the view has been marked valid.

User response: None necessary.

------------------------------------------------------------------------
RBS3400E VARCHAR column length exceeded internal limit.

System action: The server could not represent the VARCHAR column internally because its length exceeded the VARCHAR offset limit. A very long select list, a large number of literals in the select list, or a combination of these characteristics could cause this problem.

User response: If you cannot determine the cause of the problem, record what you were doing and contact Customer Support.

------------------------------------------------------------------------
RBS3509E Valid values for TARGET_INDEX_ MEMORY_GROWTH are either LINEAR or EXPONENTIAL.

System action: An invalid value was specified for the settable TARGET_INDEX_MEMORY_GROWTH.

User response: Correct the value and resubmit the statement.

------------------------------------------------------------------------
RBA6532E Out of vacuum cleaner shared resources.

System action: The vacuum cleaner infrastructure has run out of shared resources. Either the vacuum cleaner is not running or it is not able to keep up with the changes.

User response: Wait for a few minutes and re-attempt the operation. If the problem persists, increase the maximum number of versions for the version log. For more information, see the syntax of the ALTER DATABASE command in the SQL Reference Guide. If the problem still persists, contact Customer Support.

------------------------------------------------------------------------
RBL7131E Unrecoverable backup error occurred on file: name. OS error number is: err. Database files are not affected by this failure, but subsequent incremental backups might be inconsistent.

System action: A fatal error occurred while operating on the file shown in the error message.

User response: Do not do any further incremental or online backups at any level until this problem is resolved. In order to resolve the problem please contact IBM support. A level 0 checkpoint backup can be initiated safely.

------------------------------------------------------------------------
RBS8665W Index index_name has reached its maximum depth in segment_name.

System action: The tree for the specified index has reached its maximum depth. No more rows can be added to the index.

User response: For a TMU load, try sorting the input rows based on the index before loading the table. Also try running the load operation in OPTIMIZE ON mode. If possible, re-create the table with a primary key that consists of fewer columns or smaller columns.

------------------------------------------------------------------------
RBS8666F Index has reached its maximum depth. Error inserting row row_num into table table_name.

System action: The specified row cannot be inserted into the table. For more details, refer to previously displayed messages, including message 8665.

User response: Refer to the response text for message 8665.

------------------------------------------------------------------------
RBC12050E TMU received invalid handle. OS error: osmessage

System action: The rb_ctmu program encountered an incorrect pipe handle when reading data from the standard input (stdin).

User response: Run the process again. If you still receive the same error, modify the load script to eliminate the corrupted pipe.

------------------------------------------------------------------------
RBE411U Completed Callout script run for error error_num

System action: The Callout script completed.

User response: None necessary.

------------------------------------------------------------------------
RBE412U Unable to open file filename.

System action: The Callout script could not open the specified file for further processing. The possible reasons for this can be that the file does not have sufficient permissions, or the file is not available.

User response: Ensure that the required file is available. If available, ensure that the file has read and write permissions.

------------------------------------------------------------------------
RBE413U Callout scripts does not support Inline/C-typed Comments: string. Ignoring line.

System action: The Callout script contains an inline or C-type comment that is not supported. The Callout script ignores the line and the script continues to run.

User response: Remove the inline or C-type comment and run the Callout script again.

------------------------------------------------------------------------
RBE414U Callout Script does not support more than 5 Error sections

System action: The Callout script file has more than five error sections. Only the first five sections are parsed and the remaining sections are discarded.

User response: Provide or use only five error sections in the Callout script.

------------------------------------------------------------------------
RBE416U Detected setting for Error: error_num in Callout Script

System action: An error section for the error_num is found in the Callout script.

User response: None necessary.

------------------------------------------------------------------------
RBE417U No setting for Error: error_num detected in Callout Script

System action: The Callout script feature is detected but no error section for the error_num is found in the Callout script.

User response: If you want to run the Callout Script for error number error_num, then create a section for the error number error_num in the Callout script.

------------------------------------------------------------------------
RBE418U Fork failed for Callout Script

System action: The fork operation performed by the Callout script failed.

User response: Examine the operating-system logs for messages that are logged when this error is reported. Based on this analysis, adjust the kernel parameters as required. If needed, contact the Red Brick customer support.

------------------------------------------------------------------------
RBE419U Error detected in Callout Configuration file, Callout script string. Ending Callout Run.

System action: A syntax error is detected in the Callout script.

User response: See the Usage notes for Callout scripts and modify the appropriate error line.

------------------------------------------------------------------------
RBA6524F Reached the maximum number of database sessions or load processes.

System action: The limit on the total number of database sessions was reached.

User response: Review the DST_SESSIONS table, and stop any idle database sessions. For parallel loads with a high number of non-unique indexes, use the TMU_INDEX_TASKS and TMU_CONVERSION_TASKS configuration parameters to control the number of processes.

------------------------------------------------------------------------
RBC12003I Connection information for Remote TMU execution:

System action: The Client TMU displays this information message when you retrieve the information like port number, machine name, and so on, to run the remote TMU file. This is not an error message.

User response: None necessary.

Chapter 2. 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 all 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-0032, 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 may 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.

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
J35/G4
555 Bailey Avenue
San Jose, CA 95141-1003
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 information 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 measurements 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.

All IBM prices shown are IBM's suggested retail prices, are current and
are subject to change without notice. Dealer prices may vary.

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

Each copy or any portion of these sample programs or any derivative
work, must include a copyright notice as follows:
© IBM 2014. Portions of this code are derived from IBM Corp. Sample
Programs. © Copyright IBM Corp. 1996-2014. All rights reserved.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

2.1 Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other
companies and have been used in at least one of the documents in the DB2
UDB documentation library:

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.

Intel, Xeon, Itanium, and Pentium are trademarks of Intel Corporation in
the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Other company, product, or service names may be trademarks or service
marks of others.

Linux is a registered trademark of Linus Torvalds. Red Hat and all Red
Hat-based trademarks and logos are trademarks or registered trademarks
of Red Hat, Inc. in the United States and other countries.

Other company, product, or service names may be trademarks or service
marks of others.

Chapter 3. Contacting IBM

If you have a technical problem, please review and carry out the actions
suggested by the product documentation before contacting DB2 Data
Warehouse Edition Customer Support. This guide suggests information that
you can gather to help DB2 Data Warehouse Edition Customer Support to
serve you better.

For information or to order any of the DB2 Data Warehouse Edition
products, contact an IBM representative at a local branch office or
contact any authorized IBM software remarketer.

If you live in the U.S.A., you can call one of the following numbers:
* 1-800-IBM-SERV (1-800-426-7378) for customer service
* 1-888-426-4343 to learn about available service options
* 1-800-IBM-4YOU (426-4968) for DB2 marketing and sales

Note: In some countries, IBM-authorized dealers should contact their
dealer support structure instead of the IBM Support Center.

3.1 Product Information

Information regarding DB2 Data Warehouse Edition is available by
telephone or by the World Wide Web at
http://www.ibm.com/software/data/db2/dwe.

This site contains the latest information on the technical library,
ordering books, product downloads, newsgroups, FixPaks, news, and links
to Web resources.

If you live in the U.S.A., then you can call one of the following
numbers:
* 1-800-IBM-CALL (1-800-426-2255) to order products or to obtain
general information.
* 1-800-879-2755 to order publications.

http://www.ibm.com/software/data/db2/udb/dwe/
Provides links to information about DB2 Data Warehouse Edition.

http://www.ibm.com/software/data/db2/9
The DB2 Web pages provide current information about news,
product descriptions, education schedules, and more.

http://www.elink.ibmlink.ibm.com/
Click Publications to open the International Publications
ordering Web site that provides information about how to order
books.

http://www.ibm.com/education/certify/
The Professional Certification Program from the IBM Web site
provides certification test information for a variety of IBM
products.

3.2 Accessible documentation

Documentation is provided in XHTML format, which is viewable in most Web
browsers.

XHTML allows you to view documentation according to the display
preferences that you set in your browser. It also allows you to use
screen readers and other assistive technologies.

Syntax diagrams are provided in dotted decimal format. This format is
available only if you are accessing the online documentation using a
screen reader.

3.3 Comments on the documentation

Your feedback helps IBM to provide quality information. Please send any
comments that you have about this book or other DB2 Data Warehouse
Edition documentation. You can use any of the following methods to
provide comments:
* Send your comments using the online readers' comment form at
www.ibm.com/software/data/rcf.
* Send your comments by electronic mail (e-mail) to
comments@us.ibm.com. Be sure to include the name of the product, the
version number of the product, and the name and part number of the
book (if applicable). If you are commenting on specific text, please
include the location of the text (for example, a title, a table
number, or a page number).
* Send your comments by mail to:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.

For information on how to contact IBM outside of the United States, go
to the IBM Worldwide page at www.ibm.com/planetwide.

[{"Product":{"code":"SSCRW7","label":"Red Brick Warehouse"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF033","label":"Windows"}],"Version":"6.3","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Tips

IBM Red Brick Warehouse RELEASE NOTES for Windows Platforms Version 6.30.xC15

Preventive Service Planning

Abstract

Content

Was this topic helpful?

Document Information

UID

Share your feedback

Need support?