IBM Support

JR28297: DB2CONNECT GATEWAY FAILS TO LOCATE NEXT SERVER TO CONNECT TO AFTER A COMMUNICATION ERROR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2Connect gateway configure in sysplex may fail to locate next
server to connect to after it got communication error
with former server, no matter there is still valid
server in server list.
.
 At the time problem reproduced, following db2diag.log can be
observed.
2008-02-29-19.55.42.812000+540 I101222H581        LEVEL: Warning
PID     : 1544                 TID  : 216         PROC :
INSTANCE: DB2                  NODE : 000         DB   : SAMPLE
APPHDL  : 0-8                  APPID: *LOCAL.DB2.080229105439
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrRetrySetup,
probe:15
MESSAGE : The correlation token of the failed connection is
DATA #1 : Hexdump, 26 bytes
0x01E1EB38 : 4739 4243 4336 3231 2E4E 3130 372E 3038
G9BCC621.N107.08
0x01E1EB48 : 3032 3239 3130 3535 3432
.
Then following db2diag.log entry are repeated showing  same
server
 that got communication error is being tested for connection in
db2diag.log
.
2008-02-29-19.55.42.812000+540 I102209H1619       LEVEL: Warning
PID     : 1544                 TID  : 216         PROC :
INSTANCE: DB2                  NODE : 000         DB   : SAMPLE
APPHDL  : 0-8                  APPID: *LOCAL.DB2.080229105439
FUNCTION: DB2 UDB, DRDA Application Requester,
sqljrInternalConnect, probe:37
MESSAGE : Reconnecting to Hostname/IP Address -->
DATA #1 : Hexdump, 256 bytes
0x01EDF026 : 3139 322E 3136 382E 3132 382E 3131 0000
192.168.128.11..
0x01EDF036 : 0000 0000 0000 0000 0000 0000 0000 0000
                < snippet >
0x01EDF116 : 0000 0000 0000 0000 0000 0000 0000 0000
................
.
2008-02-29-19.55.42.812000+540 I103830H512        LEVEL: Warning
PID     : 1544                 TID  : 216         PROC :
INSTANCE: DB2                  NODE : 000         DB   : SAMPLE
APPHDL  : 0-8                  APPID: *LOCAL.DB2.080229105439
FUNCTION: DB2 UDB, DRDA Application Requester,
sqljrInternalConnect, probe:37
MESSAGE : Reconnecting to Service name/Port number -->
DATA #1 : Hexdump, 15 bytes
0x01EDF126 : 3830 3030 0000 0000 0000 0000 0000 00
8000...........

Local fix

  • non

Problem summary

  • DB2Connect gateway configure in sysplex may fail to locate next
server to connect to after it got communication error
with former server, no matter there is still valid
server in server list.

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 8.1 FixPak 17

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    JR28297
    • 

  • Reported component name
    DB2 CUE WINDOWS
    • 

  • Reported component ID
    5724B6201
    • 

  • Reported release
    820
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2008-03-05
    • 

  • Closed date
    2009-08-31
    • 

  • Last modified date
    2009-08-31
    • 





    

  • 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 CUE WINDOWS
    • 

  • Fixed component ID
    5724B6201
    • 



Applicable component levels


    

  • R810  PSN
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            31 August 2009
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback