PI94282: STATEMENTS FAIL RETURNING SQL5197N - COMMUNICATION ERROR WITH THE SCHEDULER

APAR status

• Closed as fixed if next.

Error description

• You submit an SQL operation , even a simple one such an INSERT
  or  a SELECT count(*) on a single table, which usually returns
  quickly but now hangs for a few minutes and then return an
  error similar to the following:
  
  SQL5197N  The statement failed because of a communication error
  with a Big SQL component. Big SQL component name: "SCHEDULER".
  Reason code: "2". Log entry identifier: "DB2".  SQLSTATE=57066
  
  while in the db2 log db2diag.0.log on the BigSQL head node the
  message is:
  
  2018-01-22-22.33.11.700945+240 I1108543E950         LEVEL: Error
  PID     : 11255                TID : 70336334721456 PROC :
  db2sysc 0
  INSTANCE: bigsql               NODE : 000           DB   :
  BIGSQL
  APPHDL  : 0-5443               APPID: *N0.DB2.180122181131
  AUTHID  : BIGSQL               HOSTNAME: myhostname
  EDUID   : 388                  EDUNAME: db2agent (BIGSQL) 0
  FUNCTION: DB2 UDB, base sys utilities,
  sqeBigSqlSchedulerInternal::requestScanMetadata, probe:3386
  MESSAGE : ZRC=0xFFFFEBB3=-5197
            SQL5197N  The statement failed because of a
  communication error with
            a Big SQL component. Big SQL component name: "".
  Reason code: "". Log
            entry identifier: "".
  
  DATA #1 : String, 140 bytes
  Transport Exception occurred. The BigSql Scheduler service may
  not be running or the scheduler client request timeout may not
  be sufficient.
  DATA #2 : String, 18 bytes
  EAGAIN (timed out)
  DATA #3 : signed integer, 4 bytes
  -5197
  
  however the scheduler is up and running. Restarting the
  scheduler or the whole BigSQL instance solves the problem.
  
  The problem is more likely to occur on a system where HDFS has
  been replaced with SpectrumScale, and where operations on
  tables with a large number of files and partitions are ongoing.
  

Local fix

• Restart the BigSQL scheduler issuing the commands
  
  bigsql stop -scheduler
  bigsql start -scheduler
  
  from the BigSQL head node, as user "bigsql". Note that while
  the scheduler is restarting running statements may fail.
  

Problem summary

• See error description
  The problem is fixed in Version 5.0.3 and later fix packs.
  

Problem conclusion

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:

Modules/Macros

• Unknown
  

Fix information

Applicable component levels

• R425 PSY

     UP