2567963 - CM parameter bad error causes instance crash

Your database instance has crashed

The db2diag.log shows the following error:

2017-01-01-01.00.00.000000-000 I279092E1245          LEVEL: Severe
PID     : 00000                TID : 000000000000000 PROC : db2sysc 0
INSTANCE: db2sid               NODE : 000
APPHDL  : 0-0000
HOSTNAME: db2hostname
EDUID   : 654                  EDUNAME: db2agent () 0
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x81360010=-2127167472=SQLZ_RC_CMPARM, SQLT_SQLJC
          "CM parameter bad"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 8 bytes
68
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
  [0] 0x00007F10A457DCDD _Z16sqljcLogCCIErrorP10sqljCmnMgrPKcP12SQLCC_COND_Thllll + 0x10D
  [1] 0x00007F10A2300CFE _Z12sqljcReceiveP10sqljCmnMgr + 0x32E
  [2] 0x00007F10A2344ADA /db2/db2nlx/sqllib/lib64/libdb2e.so.1 + 0x3478ADA
  [3] 0x00007F10A2341CA4 /db2/db2nlx/sqllib/lib64/libdb2e.so.1 + 0x3475CA4
  [4] 0x00007F10A23418AB _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xEB
  [5] 0x00007F10A203FE87 _ZN8sqeAgent6RunEDUEv + 0xAD7
  [6] 0x00007F10A38571F7 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
  [7] 0x00007F10A300F7C3 sqloEDUEntry + 0x303
  [8] 0x00007F10AA3F9E25 /lib64/libpthread.so.0 + 0x7E25
  [9] 0x00007F109DC6634D clone + 0x6D

DB2 10.5

"CM parameter bad", LogCCIError , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem