PH07304: BIGSQL ADDITIONAL LOGICAL WORKERS MAY BE MISSING TABLESPACES AND CRASH WHEN GLOBAL TEMPORARY TABLES ARE CREATED

APAR status

• Closed as program error.

Error description

• You have performed an installation of Big SQL 5.0.4 on a
  cluster with one Big SQL worker per node and things work well.
  
  You decide to add logical Big SQL workers by selecting "Add Big
  SQL logical Worker" in the BigSQL Service Actions menu. The
  operation succedes and the new workers are installed and
  started but they will only have the tablespace
  
  TEMPSPACE1
  
  and miss the tablespaces
  
  IDAX_USERTEMPSPACE
  BIGSQLUTILITYSPACE
  
  This can be verified by checking the output of
  
  db2_all "db2pd -db bigsql -tablespaces"
  
  While most operations in BigSQL will still succeed some will
  fail with the potential to bring down the worker nodes. One
  such operation is the creation of temporary tables using the
  statement
  
  DECLARE GLOBAL TEMPORARY TABLE ...
  

Local fix

• 1) disconnect all connections to BigSQL
  
  2) Drop and re-create the tablespaces by running the following
  statements from the BigSQL head node:
  
  db2 connect to BIGSQL
  
  db2 "call syshadoop.big_sql_service_mode('on')"
  
  db2 drop tablespace bigsqlutilityspace
  
  db2 create tablespace bigsqlutilityspace in ibmdefaultgroup
  
  db2 drop tablespace IDAX_USERTEMPSPACE
  
  db2 CREATE USER TEMPORARY TABLESPACE "IDAX_USERTEMPSPACE" IN
  DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED
  BY AUTOMATIC STORAGE USING STOGROUP "IBMSTOGROUP" EXTENTSIZE
  128 PREFETCHSIZE AUTOMATIC BUFFERPOOL "IBMDEFAULTBP" OVERHEAD
   INHERIT TRANSFERRATE INHERIT FILE SYSTEM CACHING DROPPED TABLE
  RECOVERY OFF
  
  db2 CALL SYSPROC.SYSINSTALLOBJECTS('IDAX', 'C', CAST (NULL AS
  VARCHAR(128)), CAST (NULL AS VARCHAR(128)))
  
  db2 "call syshadoop.big_sql_service_mode('off')"
  
  db2 commit
  
  db2 terminate
  
  
  3) verify from the output of
  
  db2_all "db2pd -db bigsql -tablespaces"
  
  that all worker nodes have the three tablespaces.
  
  In doubt contact  IBM Technical Support for Big SQL.
  

Problem summary

• See error description
  

Problem conclusion

• The problem is fixed in Version 6.0.0 and later fix packs.
  

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

• Fixed component name

  IBM BIG SQL

• Fixed component ID

  5737E7400

Applicable component levels