IT18390: UPDATE DBM CFG IN A CLIENT INSTANCE FAILS WITH SQL5126N AFTER UPGRADING FROM LOWER VERSION.

DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• Update dbm cfg fails with SQL5126N on a client instance which
  was created on 10.5 or older version and upgraded to V11.
  
  $ db2 update dbm cfg using diaglevel 4
  SQL5126N  The UPDATE DATABASE MANAGER CONFIGURATION command
  failed because the
  specified database manager configuration parameter is not
  supported by the
  current instance node type. Database manager configuration
  parameter:
  "fcm_buffer_size". Instance node type: "2".
  
  The dbm cfg fcm_buffer_size is introduced in V11. During
  upgrading a client instance, a certain value is set as the
  default but it is not correct for client instances. After the
  upgrade the problem occurs when running update dbm cfg. If the
  client instance is newly created in V11, the problem does not
  occur.
  

Local fix

• Re-create the client instance on V11.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 11.1 Mod 2 Fix Pack 2
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP