Does seem to still be a semaphore problem. As far as I recall, semaphores are used to control communications between processes.
I think to increase the maximum number of semaphores available, you need to increase:- set semsys:seminfo_semvmx=<whatever value>. (I'd double the existing one) Hope this helps, I'm not a Solaris expert, unfortunately. James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ScotDB Sent: 01 August 2003 11:51 To: DB2 Data Base Discussion List; DB2EUG Subject: [DB2EUG] DB2 for Solaris V7.2 FP9 and FP10 Semaphore Problem Guys, We're getting the following problem (extract from db2diag.log below) when testing a DB2 for Solaris server with Fixpacks 9 or 10. We've checked the various kernel parameters have been set correctly. Anyone else had similar problems ? === START OF EXTRACT === 2003-07-30-11.31.59.273322 Instance:db2inst1 Node:000 PID:347(db2sysc) Appid:none oper_system_services sqloGetShrEDUWaitElem Probe:10 SysV semget failed with errno:0000 001c .... 2003-07-30-11.31.59.366200 Instance:db2inst1 Node:000 PID:347(db2sysc) Appid:none oper_system_services sqloCreateEDU Probe:3 DiagData 7371 6c6f 4765 7453 6872 4544 5557 6169 sqloGetShrEDUWai 7445 6c65 6d20 6661 696c 6564 tElem failed 2003-07-30-11.32.00.451716 Instance:db2inst1 Node:000 PID:348(db2gds) Appid:none oper_system_services sqloGetShrEDUWaitElem Probe:10 SysV semget failed with errno:0000 001c .... 2003-07-30-11.32.00.509531 Instance:db2inst1 Node:000 PID:348(db2gds) Appid:none oper_system_services sqloCreateEDU Probe:3 DiagData 7371 6c6f 4765 7453 6872 4544 5557 6169 sqloGetShrEDUWai 7445 6c65 6d20 6661 696c 6564 Elem failed 2003-07-30-11.32.00.585516 Instance:db2inst1 Node:000 PID:348(db2gds) Appid:none oper_system_services sqloGetShrEDUWaitElem Probe:10 SysV semget failed with errno:0000 001c .... 2003-07-30-11.32.00.646994 Instance:db2inst1 Node:000 PID:348(db2gds) Appid:none oper_system_services sqloCreateEDU Probe:3 DiagData 7371 6c6f 4765 7453 6872 4544 5557 6169 sqloGetShrEDUWai 7445 6c65 6d20 6661 696c 6564 Elem failed 2003-07-30-11.32.00.750716 Instance:db2inst1 Node:000 PID:344(db2star2) Appid:none base_sys_utilities startdbm Probe:911 Database manager is started. 2003-07-31-10.15.52.234625 Instance:db2inst1 Node:000 PID:349(db2ipccm) Appid:none common_communication sqlccGetIPCs Probe:5 DIA3636C Requested too many semaphores. ZRC=0xFFFFD681 Data Title:IPC Semaphore Set ID PID:349 Node:000 0000 0000 0000 0000 0000 0000 0000 0000 ................ ffff ffff ffff ffff 0000 0000 0000 0000 ................ 2003-07-31-10.24.58.846034 Instance:db2inst1 Node:000 PID:349(db2ipccm) Appid:none common_communication sqlccGetIPCs Probe:5 DIA3636C Requested too many semaphores. ZRC=0xFFFFD681 Data Title:IPC Semaphore Set ID PID:349 Node:000 0000 0000 0000 0000 0000 0000 0000 0000 ................ ffff ffff ffff ffff 0000 0000 0000 0000 ................ 2003-07-31-10.25.25.012448 Instance:db2inst1 Node:000 PID:349(db2ipccm) Appid:none common_communication sqlccGetIPCs Probe:5 DIA3636C Requested too many semaphores. ZRC=0xFFFFD681 Data Title:IPC Semaphore Set ID PID:349 Node:000 0000 0000 0000 0000 0000 0000 0000 0000 ................ ffff ffff ffff ffff 0000 0000 0000 0000 ................ 2003-07-31-11.36.22.933664 Instance:db2inst1 Node:000 PID:349(db2ipccm) Appid:none common_communication sqlccGetIPCs Probe:5 DIA3636C Requested too many semaphores. ZRC=0xFFFFD681 Data Title:IPC Semaphore Set ID PID:349 Node:000 0000 0000 0000 0000 0000 0000 0000 0000 ................ ffff ffff ffff ffff 0000 0000 0000 0000 ................ 2003-07-31-15.16.51.411964 Instance:db2inst1 Node:000 PID:349(db2ipccm) Appid:none common_communication sqlccGetIPCs Probe:5 DIA3636C Requested too many semaphores. ZRC=0xFFFFD681 Data Title:IPC Semaphore Set ID PID:349 Node:000 0000 0000 0000 0000 0000 0000 0000 0000 ................ ffff ffff ffff ffff 0000 0000 0000 0000 ................ 2003-07-31-15.25.48.269595 Instance:db2inst1 Node:000 PID:347(db2sysc) Appid:none oper_system_services sqloEDUCodeTrapHandler Probe:10 ******************************************************************** * * * DB2 USERS : * * ----------- * * An internal processing error occurred on this B2 instance. * * * * A stack trace-back for the process in which the error was * * detected may be written to a trap file in the directory * * containing this log. The name of the file will be 'tppppp.nnn' * * where ppppp is the process id, and nnn is the node number. * * * * * * ALL DB2 PROCESSES ASSOCIATED WITH * * THIS INSTANCE HAVE BEEN SHUTDOWN. * * * * Contact your technical service representative with the * * information from this log and from the auxiliary trace and dump * * files in the same directory. * ******************************************************************** === END OF EXTRACT === TIA Phil Nelson -- ScotDB <[EMAIL PROTECTED]> ScotDB Limited - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
