New in this release

Additional Query Patroller support for Linux operating systems

Query Patroller is now supported on the following additional platforms:

|
• Linux^(R) Operating Systems on AMD64 and Intel^(R) EM64T systems |(x86-64), requiring the 2.6 kernel or later. Query Patroller supports both |32-bit and 64-bit DB2^(R) UDB instances on this platform.
|
• Linux Operating Systems on POWER^(TM) (iSeries and pSeries^(R) systems), |requiring the 2.6 kernel or later. Query Patroller supports only 64-bit DB2 |UDB instances on this platform.

Development Center enhancement for Java stored procedures

The Development Center now supports using the DB2 Universal JDBC Driver |for building Java^(TM) stored procedures which have source larger than 32K |and target a DB2 UDB for z/OS^(R) V7 server. Before this support was added, |the Universal Driver was supported only for DB2 UDB z/OS V8 Java stored procedures. |In order for this support to work, you must install DB2 for z/OS V7 APAR |PK01445.

Support for native DB2 driver for PHP

IBM^(R) officially supports the use of the ibm_db2 extension for PHP |to connect to IBM DB2 Universal Database^(TM) servers from applications written |in PHP. The ibm_db2 extension is available from http://pecl.php.net/ibm_db2/ and is documented as part of the PHP manual |at http://www.php.net/.

Support for 31-bit applications on 64-bit Linux for zSeries

To support 31-bit applications running on 64-bit Linux for zSeries^(R) |that need to connect to a DB2 Universal Database server, use the DB2 Runtime |Client for 31-bit Linux for zSeries, available for download from http://www.ibm.com/software/data/db2/udb/support.html. This configuration |will not coexist with DB2 products for 64-bit Linux for zSeries in the same |Linux Virtual Machine.

DB2 Cube Views enhancements

DB2 Cube Views^(TM) Version 8.2 FixPak 3 (equivalent to Version 8.1 FixPak |10) incorporates several enhancements to the DB2 Cube Views metadata and Optimization |Advisor that have been made since Version 8.2 FixPak 2 (equivalent to Version |8.1 FixPak 9).

Support for additional platforms

DB2 Cube Views adds support for the following platforms:

|
• Red Hat Enterprise Linux 3 (32-bit and 64-bit) for PowerPC^(R)
|
• Red Hat Enterprise Linux 4 (32-bit and 64-bit) for AMD
|
• SUSE Linux Enterprise Server 8 (32-bit only) for PowerPC
|
• SUSE Linux Enterprise Server 9 (32-bit and 64-bit) for AMD

Improved support for degenerate dimensions

Degenerate dimensions are dimensions that refer to only the fact table. |Degenerate dimensions are most useful when you have dimension information |(such as a time stamp) embedded in your fact table that you want to use to |specify a dimension. With Version 8.2 FixPak 3 (equivalent Version 8.1 FixPak |10), you no longer need to specify a self-join between the degenerate dimension |and the facts object.

Additional functional dependency information to improve summary tables

You can now specify functional dependencies between levels within a hierarchy. | The level-key attributes from one level can be mapped to the level-key attributes |of the level above or below in the hierarchy through a functional dependency.

Support for optimizing inner joins that have unique keys

The optimization rules are relaxed in Version 8.2 FixPak 3 (equivalent |Version 8.1 FixPak 10) so that you can optimize models that include the following |types of joins:

|
• Inner-join with a unique key and a not-null foreign key
|
• Inner-join with a unique key and a nullable foreign key

Type property added to levels

Levels have a new required property that specifies the level type as unknown, |regular, or time.

Default measure for facts objects and cube facts objects

You can specify a measure as the default measure for a facts object and |a cube facts object. Vendor applications can use the default measure as the |starting measure for drill-down reports.

Support for optional ordering of member attributes in a level

The ordering of attributes in a level is an optional metadata property |that enables some vendor applications to sort the result sets. For example, |in a City level you might specify City Name in ascending order as the ordering |attribute for the City level in the Market dimension. This specification causes |the cities to be displayed alphabetically in a vendor report.

Optional units property added to measures

Measures have a new optional property so that you can provide a descriptive |text string of the units that the measure is in. For example, you might specify dollars for a sales measure or boxes sold for a quantity |sold measure. Vendor applications might display the units property with the |measure value or measure name.

Optional All level property added to hierarchies

Hierarchies have a new optional property to specify an all level. An all level is a level at the |top of a hierarchy with exactly one member that represents the aggregation |of all of the members in the lower levels in the hierarchy. For example, if |you include an all level in a product dimension, |the measures in the fact table, such as sales, are aggregated for all products. |An all level is useful for most hierarchies.

Attribute relationship is deprecated

The attribute relationship is deprecated. Use levels instead of attribute |relationships to model the relationships between one or more attributes within |a hierarchy.

Updated metadata for the CVSAMPLE sample database

The metadata that is provided with the CVSAMPLE sample database is extended |to include examples of all of the new metadata enhancements in Version 8.2 |FixPak 3 (equivalent to Version 8.1 FixPak 10)