Results 1 to 2 of 2
  1. #1
    Join Date
    May 2010
    Location
    Mexico
    Posts
    3

    Red face Unanswered: MESSAGE : O33 Read Queue Timeout Loop Max Exceeded

    HI,

    We just migrated our Production DB2 V8.1 to DB2 V9.7 This is the third time we did such a migration, but, this time something seems to have changed and we started running into problem that we never ran into. The following message keeps occurring in db2diag.log and the database simply hangs forever. It doesn't respond to any SQL or db2start/db2stop commands either.

    2010-05-27-16.37.07.607085-300 I40945655A333 LEVEL: Info
    PID : 21760 TID : 1 PROC : db2
    INSTANCE: insindo NODE : 000
    EDUID : 1
    FUNCTION: DB2 UDB, command line process, clp_read_outputq, probe:88
    MESSAGE : O33 Read Queue Timeout Loop Max Exceeded
    DATA #1 : signed integer, 4 bytes
    31


    Can you help me?

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Reduce your diaglevel to 3 in order to stop this message. For the hang, force the instance to come down (db2_kill) and then perform manual cleanup. After executing db2_kill, execute ps -ef | grep insindo and ipcs | grep insindo. Remove processes (kill -9) / ipc resources (ipcrm) owned by insindo. When everything has been cleaned up, restart the instance and try executing some db2 commands/statements.

Posting Permissions

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