Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2010
    Posts
    7

    Unanswered: Error Message for "Invalid input parameter"

    Hi All,

    Our current DB2 UDB is ver 8.2. There are the following messages showing in the db2diag.log.

    ================================================

    2010-08-18-17.23.06.816951-240 I11213G320 LEVEL: Severe
    PID : 22139 TID : 3066418880 PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:4
    RETCODE : ZRC=0x800F00FC=-2146500356=SQLO_INV_PARM "Invalid input parameter"

    2010-08-18-17.23.06.817489-240 I11534G321 LEVEL: Severe
    PID : 3832 TID : 3065611968 PROC : db2fmp (
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:4
    RETCODE : ZRC=0x800F00FC=-2146500356=SQLO_INV_PARM "Invalid input parameter"

    2010-08-18-17.23.06.819276-240 I11856G321 LEVEL: Severe
    PID : 3832 TID : 3035786128 PROC : db2fmp (
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:4
    RETCODE : ZRC=0x800F00FC=-2146500356=SQLO_INV_PARM "Invalid input parameter"

    2010-08-18-17.23.06.817691-240 I12178G321 LEVEL: Severe
    PID : 3832 TID : 3005660048 PROC : db2fmp (
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:4
    RETCODE : ZRC=0x800F00FC=-2146500356=SQLO_INV_PARM "Invalid input parameter"

    ================================================

    Also, in the db2inst1.nfy, it shows the following messages

    ================================================

    2010-08-18-17.23.06.227410 Instance:db2inst1 Node:000
    PID:22134(db2tcpcm) TID:3086567104 Appid:none
    common communication sqlcctcpconnmgr_child Probe:125

    ADM7009E An error was encountered in the "TCPIP" protocol support. A possible
    cause is that the maximum number of agents has been exceeded.

    2010-08-18-17.23.06.259403 Instance:db2inst1 Node:000
    PID:22135(db2tcpcm) TID:3086567104 Appid:none
    common communication sqlcctcpconnmgr_child Probe:125

    ADM7009E An error was encountered in the "TCPIP" protocol support. A possible
    cause is that the maximum number of agents has been exceeded.

    2010-08-18-17.23.06.267244 Instance:db2inst1 Node:000
    PID:22134(db2tcpcm) TID:3086567104 Appid:none
    common communication sqlcctcpconnmgr_child Probe:125

    ADM7009E An error was encountered in the "TCPIP" protocol support. A possible
    cause is that the maximum number of agents has been exceeded.

    2010-08-18-17.23.06.269385 Instance:db2inst1 Node:000
    PID:22134(db2tcpcm) TID:3086567104 Appid:none
    common communication sqlcctcpconnmgr_child Probe:125

    ADM7009E An error was encountered in the "TCPIP" protocol support. A possible
    cause is that the maximum number of agents has been exceeded.

    ================================================

    How should I deal with this error messages? Is just increase DBM parameter MAXAGENTS (current is 200) good enough? What else I should take care?

    Is any possible will generate this kind of message??

    Thanks you so much.

    --zhif

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Errors in the db2diag.log can be part of db2stop process. Check if db2stop was issued just prior to 0x800F00FC

  3. #3
    Join Date
    Aug 2010
    Posts
    7
    Hi Bella,

    Indeed. Yes. There is a db2stop prior to this series of error messages.
    So, this error messages is part of the db2stop process.

    Thank you very much.

    --zhif

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •