Planning for Db2 for Linux, UNIX and Windows database upgrades

Review upgrade requirements for Db2 for Linux, Unix, and Windows databases.

Before you begin

For minimum version and fix pack requirements, see IBM® FileNet® P8 system requirements.

In some cases, it is possible to exceed the maximum rowsize of 32 KB for the Content Platform Engine database during the upgrade. See the technote Adding properties to a class with the IBM FileNet Content Engine on DB2 receives error stating that the length exceeds the capacity of the database (Technote 21384306) for information about diagnosing and resolving the problem for a Content Engine database. Use the diagnosis steps from the technote before you upgrade to determine how close the database is to exceeding the row size, and the resolution steps to reduce the amount of row size space being used before you upgrade.

Databases that are used for Content Platform Engine must be configured with a minimum of 32 KB page sizes and a UTF-8 code page.

Procedure

To install Db2 for Linux, UNIX and Windows and create DB2® instances:

  1. Set or verify the following instance and database settings.
    Db2 for Linux, UNIX and Windows version 10.5 or later:
    db2set DB2_WORKLOAD=FILENET_CM
    Set CUR_COMMIT=ON
  2. Connect to your object store databases by entering the following command:
    db2 connect to db_name user user_name using password
    where
    • db_name is the name of your object store database
    • user_name is the user ID used to access the object store database
    • password is the password for the user ID used to access the object store database
    Issue the following command:
    db2 update db cfg using cur_commit ON
  3. After making these changes, stop and restart the database using db2stop and db2start.

What to do next

Db2 for Linux, UNIX and Windows 10.5 (or later) supports an extended row size by default. This means that you can create properties without exceeding the record length limit for the page size, because column allocation sizes are no longer counted against the limit during column creation. If an updated or inserted value causes the sum of the bytes across all columns to exceed the physical record length limit of the page size, Db2 for Linux, UNIX and Windows stores a descriptor (24 bytes) in the column. The descriptor points to an off-row location. For databases that you upgraded to Db2 for Linux, UNIX and Windows 10.5 (or later) from a release prior to Db2 for Linux, UNIX and Windows 10.5, issue this command to enable extended row size support:
UPDATE DATABASE CONFIGURATION FOR dbName USING EXTENDED_ROW_SZ ENABLE
When you add a new property to a class, Content Platform Engine determines whether extended row size is enabled for the Db2 for Linux, UNIX and Windows 10.5 (or later) database. Making this determination requires having the SELECT privilege (granted by default) on a view:
SELECT ON SYSIBMADM.DBCFG

If extended row size is enabled for a Db2 for Linux, UNIX and Windows database, even if table overflow is enabled on an object store, Content Platform Engine does not overflow tables when you add a property to a class. That is, all columns are added to the original table.

If extended row size is not enabled for a Db2 for Linux, UNIX and Windows database, or if you revoked the view permission, rows are limited to 32 KB (at column allocation time), and Content Platform Engine overflows tables if overflow is enabled on an object store.

If your system has existing overflow tables and you upgraded to Db2 for Linux, UNIX and Windows 10.5 (or later), and you enabled extended-row-size support, Db2 for Linux, UNIX and Windows adds new columns to the original table, not the overflow table. Content Platform Engine associates new properties with the overflow table only if it determines that a property can reuse an existing column that is no longer used.