Condition Wait Netnorm

Hi all, am the project manager for an application running on IDS 10. Off late the users complain of the sessions getting stuck. Whenever they try to insert an record it takes a lot of time to insert. At times the session just hangs and then they have to get it killed. From whatever feedback i get from the DBA is that there are certain locks which create a deadlock situation. Out of the o/p we get from the various onstat commands we found that there are many users whose sessions is waiting for a session which is 'cond wait (netnorm)'. It seems these netnorm sessions donot belon to any user id in specific ... Form what i have read on the various forums etc .. is that this netnorm is a very normal condition. But there are way too many such processes and i guess that it what is creating a problem. Can you please guide my as to what could be a possible solution.

There could be a genuine issue here.. but what do we mean by "netnorm sessions donot belong to any userid in specific"? sqlexec threads are always associated (so are specific to some user sessions) with user sessions (like dbaccess/esqlc) and they wait on net= norm condition to recieve more work from client side. Manoj = "NIRAJ KHANDWALA" = <niraj.khandwala@ = gmail.com> = To Sent by: ids@iiug.org = ids-bounces@iiug. = cc org = Subj= ect Condition Wait Netnorm [10300] = 11/03/2007 12:40 = AM = = = Please respond to = ids@iiug.org = = = Hi all, am the project manager for an application running on IDS 10. Of= f late the users complain of the sessions getting stuck. Whenever they try to insert an record it takes a lot of time to insert. At times the session just h= angs and then they have to get it killed. >From whatever feedback i get from the DBA is that there are certain lo= cks which create a deadlock situation. Out of the o/p we get from the various onstat commands we found that th= ere are many users whose sessions is waiting for a session which is 'cond wait (netnorm)'. It seems these netnorm sessions donot belon to any user id = in specific ... Form what i have read on the various forums etc .. is that this netnorm= is a very normal condition. But there are way too many such processes and i guess that it what is creating a problem. Can you please guide my as to what could be a possible solution. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Hi, Could be many things: - find out what tables are locked and check if these have lock mode row. If not (page or table), inserts will possibly block (always in lock mode table) You can look at the locked rows using onstat -u (find out which session is waiting (L at first place in flags), execute onstat -k | grep <wait value from onstat -u> and find out the owner (use onstat -u again to track the session and then onstat -g sql to find out what is happening there). You could also query sysmaster database for who is waiting for a lock of whom: database sysmaster; set isolation to dirty read; select dbsname,tabname[1,12] table,rowidlk,type,owner,waiter,b.username[1,8] lock_waiter,a.sid,a.username[1,8] lock_owner from syslocks, syssessions a, outer syssessions b where owner = a.sid and waiter = b.sid order by waiter desc, type desc, table - is there any trigger involved, which updates a secondary table (maybe there is a lock situation) - Are your transactions too long ? Maybe the application should be changed to not hold locks that long. Hope this helps, Marcus -----Original Message----- From: NIRAJ KHANDWALA [mailto:niraj.khandwala@gmail.com] Sent: Saturday, November 03, 2007 6:40 AM To: ids@iiug.org Subject: Condition Wait Netnorm [10300] Hi all, am the project manager for an application running on IDS 10. Off late the users complain of the sessions getting stuck. Whenever they try to insert an record it takes a lot of time to insert. At times the session just hangs and then they have to get it killed. >From whatever feedback i get from the DBA is that there are certain >locks which create a deadlock situation. Out of the o/p we get from the various onstat commands we found that there are many users whose sessions is waiting for a session which is 'cond wait (netnorm)'. It seems these netnorm sessions donot belon to any user id in specific ... Form what i have read on the various forums etc .. is that this netnorm is a very normal condition. But there are way too many such processes and i guess that it what is creating a problem. Can you please guide my as to what could be a possible solution. ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.