IBM Support

Values of database_memory and appl_memory database configuration parameters are not retained when upgrading a database through a backup restore on DB2 PureScale and partitioned database environments.

Troubleshooting


Problem

If the database_memory, appl_memory, or both database configuration parameters are updated individually on a member or database partition, these values might change during a database upgrade that uses the RESTORE DATABASE command.

Symptom

After a database upgrade that uses the RESTORE DATABASE command, the values of the database_memory and appl_memory database configuration parameters might be set to AUTOMATIC, a newly calculated value, or both. These values might be different than the pre-upgrade values.

Cause

Since the value of the database_memory and appl_memory database configuration parameters is specified for individual members or database partitions, instead of being set globally for all members or database partitions prior to the upgrade, these database configuration parameters might be treated as AUTOMATIC and their values might be changed during a database upgrade that uses the RESTORE DATABASE command.

Environment

The change in database configuration parameter values might occur on DB2® pureScale® and partitioned database environments.

Diagnosing The Problem

Issue the GET DATABASE CFG FOR <dbname> command on all members or database partitions, and verify that the value of the database_memory and the appl_memory database configuration parameters are the same on all members and database partitions.

Resolving The Problem

To ensure that the database_memory and the appl_memory database configuration parameter values remain unchanged after the upgrade, perform the following actions:

  1. Save the values for all database configuration parameters on all members or database partitions by saving the output of the GET DATABASE CFG FOR <dbname> command to a file on all members or database partitions. For more details on how to save this information, see Backing up DB2 server configuration and diagnostic information.
  2. After the database upgrade, determine whether the values of the database_memory and the appl_memory database configuration parameters are the same as the values in the saved output file.
  3. If the values are different, manually update the database_memory and the appl_memory database configuration parameters to the pre-upgrade value by issuing the UPDATE DATABASE CFG command on each member or database partition.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Database Objects\/Config - Database","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.5","Edition":"Advanced Enterprise Server;Enterprise Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21637448

Page Feedback