IT23206: SQL5133N AFTER MOVING A DB2 CLIENT INSTALLATION TYPE TO SERVER TYPE

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

APAR status

• Closed as program error.

Error description

• Moving a Db2 CLIENT installation type on WINDOWS platform to
  SERVER type using the 'Work with Existing' option in db2setup,
  the installation succeeds.
  However, the value of FCM_BUFFER_SIZE parameter is not copied
  over correctly causing the db2start command fails with:
  DB2-0 : The service has returned a service-specific error code.
  SQL1022C  There is not enough memory available to process the
  command.
  SQL1032N  No start database manager command was issued.
  SQLSTATE=57019
  
  The db2diag.log shows the problem with Fast Communication
  Manager (FCM):
  EDUID   : 2264                 EDUNAME: db2sysc 0
  FUNCTION: DB2 UDB, fast comm manager, sqlkfAllocateFcmResources,
  probe:10
  RETCODE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt
  invalid size"
            DIA8563C An invalid memory size was requested.
  
  The DBM CFG shows:
  FCM buffer size                       (FCM_BUFFER_SIZE) = 0
  
  Trying to update the parameter fails, e.g.:
  db2 update dbm cfg using FCM_BUFFER_SIZE 32768
  SQL5133N  The configuration parameter was not updated because
  the specified
  value is not valid.  Specified value: "0".  Configuration
  parameter name:
  "fcm_buffer_size_int".
  
  In the db2diag.log it shows:
  
  FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
  logging function), probe:30
      DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
       sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -5133
  sqlerrml: 57
       sqlerrmc: 0 fcm_buffer_size 4k 8k 16k 32k 64k 128k 256k
  512k 1024k
       sqlerrp : SQL11012
       sqlerrd : (1) 0x00000000      (2) 0x00000000      (3)
  0x00000000
                 (4) 0x00000000      (5) 0x00000000      (6)
  0x00000000
       sqlwarn : (1)      (2)      (3)      (4)        (5)
  (6)
                 (7)      (8)      (9)      (10)        (11)
       sqlstate: 00000
  
  The same error happens when trying to run an instance update.
  
  There is a bug in configuration checking.
  

Local fix

• - Remove the client installation before server installation
  or
  - Install Server to a new location
  or
  - Create a new Db2 instance
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 Version 11.1 Mod 3 FixPack 3                  *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 Version 11.1 Mod 3 FixPack 3
  

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