Known issues for DB2 on Solaris Operating Environment

• November 15, 2005
  DB2 trap on Solaris 8 when using with FASTGROUPS registry variable.
• October 24, 2006
  Performance degradation with Solaris 10 and Solaris 10 Update 1.
• March 7, 2008
  DB2 load command does not complete when loading a table, which defined in tablespace with more than one container.
• March 11, 2008

  DB2 will trap on Sun SPARC T2/T2+ base machine.

  DB2 9.5 may crash on Sun hardware that support 256M pagesize.

• DB2 will trap on Sun SPARC T2/T2+ base machine like Sun SPARC Enterprise T5120 Server and Sun SPARC Enterprise T5220 Server.

  The problem is caused by a hypervisor bug in the hardware firmware. SUN's bug ID is 6200096. The fix is in Sun Firmware 7.0.3.c and above. It is recommended to install the firmware fix when running any version of DB2 on those hardwares. There is no workaround for the problem.

Know issues when running DB2 Version 9.5 on Solaris:

• DB2 9.5 may crash on Sun hardware that support 256M pagesize with large number of concurrent connection. In the db2diag.log DB2 will report "DIA8305C Memory allocation failure occurred" error from sqlbReadPage(). Solaris bug ID 6559612 is created for the problem. That is no fix from the SUN yet. However, DB2 9.5 Fixpack 2 will contain a fix for that.

  Example of db2diag.log entry may like:
  007-12-20-11.39.05.978445-300 I5523A2324 LEVEL: Severe
  PID : 2119 TID : 218 PROC : db2sysc 0
  INSTANCE: db2inst1 NODE : 000 DB : IGEN
  APPHDL : 0-587 APPID: 10.8.4.165.41191.071220164759
  AUTHID : DB2INST1
  EDUID : 218 EDUNAME: db2agent (IGEN) 0
  FUNCTION: DB2 UDB, buffer pool services, sqlbReadPage, probe:1140
  MESSAGE : ZRC=0x85020005=-2063466491=SQLB_NO_MEMORY
  "No pageread because no-mem error from OSS"
  DIA8305C Memory allocation failure occurred.

Known issues when running DB2 Version 9 on Solaris:

Solaris 10

• Performance degradation with Solaris 10 and Solaris 10 Update 1
  due to significant increase of CPU User Time (up to 30%).
  
  The problem is a result of a bug in a Page Coloring mechanism, identified in SUN's CR 6337073. This bug was fixed in the kernel patch 118833-02, though it is recommended to install Solaris 10 Update 2, which comes with kernel patch 118833-17. Another way of fixing the problem is setting consistent_coloring = 2 in /etc/system.
  
• DB2 load command does not complete when loading a table, which defined in tablespace with more than one container.
  
  The problem caused by the msgrcv() bug, introduced in kernel patch 127111-02. SUN's bug CR 6657170 had been opened. It is recommended to uninstall the identified kernel patch. Another way of avoiding the problem is setting DISK_PARALLELISM option of DB2 load command to 1, but it may harm load performance and should only be used if uninstalling the patch 127111-02 is impossible. The problem also can fixed by install Solaris 10 Update 5 release or Solaris 10 kernel patch 127127-11.

Known issues when running DB2® Universal Database (DB2 UDB) Version 8 on Solaris:

Solaris 8

• DB2 UDB traps on Solaris 8 when using FASTGROUPS registry variable.
  
  The DB2 UDB instance traps in a dlopen(NULL, RTLD_NOW) call. The problem is related to a SUN linker bug and was fixed in the patch 109147-40.