John: We had a similar issue a couple of years back - we were using DB2 on AIX. We'd see that some of the DARI processes would just hang there and new processes would show up. If we did not periodically kill the processes they would just pile up. So as a part of our nightly offline backup script we put in code to kill all DARI threads and recycle DB2. If you're not a 24/7 shop, this may work for you too.
Thanks, Manas. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Lantz Sent: Thursday, April 11, 2002 1:47 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [DB2EUG] keepdari Right now I'm not constrained on resources. But I don't know how many DARI processes I'll see in production.. If on my test machine I'm seeing 17 right now, with only 20 - 30 connections at the most. How many DARI processes will I see in production with 300 connections? Each DARI process looks to be using about 2 mg of memory. If I will only have 20 +/- in production as I do in test, then I will not be constrained on resources and I can set maxdari to be -1. But if I'm going to have 10 times as many DARI processes in production as I do in test, then I'm afraid I would get constrained on resources. I guess I won't know how many I will get until I turn KEEPDARI on in the production environment. Thanks. "Vilas, Ajith (USPC.PCT.Hopewell)" <[EMAIL PROTECTED]> on 04/11/2002 11:34:42 AM To: "'John Lantz'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc: Subject: RE: [DB2EUG] keepdari John, DARI processes are loaded at their first invocation time and is stored if KEEPDARI is enabled. But if you have more than one applications accessing the same DARI procedure at the same time (concurrent applications/concurrent DARI requests), database manager might be loading and keeping more than one copy of the same DARI procedure(?). Setting KEEPDARI to -1 will enable database manger to load/keep as many DARI objects as the number of co-ordinating agents. This is the ideal approach, if you are not restricted by the resources on your system. Or set it to the maximum number of applications that you think will access this stored procedure. Regards, Ajith -----Original Message----- From: John Lantz [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 9:24 AM To: [EMAIL PROTECTED] Subject: [DB2EUG] keepdari We are using stored procedures more now in UDB and we are fooling around with the KEEPDARI parameter. It's documented in many places that you should have KEEPDARI YES to improve performance of stored procedures. After first setting KEEPDARI to yes, I set MAXDARI to 5. I quickly got the error message SQL1130N (can't start any new DARI processes). I've since changed the MAXDARI to -1, and that has allowed us to avoid the SQL1130N message. I can go under Task Manager and see 12 "db2dari" processes out there right now. Before I rebooted the machine yesterday, I had 20 "db2dari" processes out there. I don't have 12 or 20 stored procedures that are executed, there are only 3 or 4 procedures that are getting called. Even after all of the connections are forced from the database, the "db2dari" processes stay out there. What I can't figure out is what will be the maximum number of "db2dari" that will be needed? I'm concerned about setting MAXDARI to -1 on our production machine. We average over 300+ connections to the production server, I am concerned how many dari processes I would have on the production box. Does anybody have any experience with these parms? How many "db2dari" processes do you have running? We are running Win2K. Thanks in advance. ******************* PLEASE NOTE ******************* This E-Mail/telefax message and any documents accompanying this transmission may contain privileged and/or confidential information and is intended solely for the addressee(s) named above. If you are not the intended addressee/recipient, you are hereby notified that any use of, disclosure, copying, distribution, or reliance on the contents of this E-Mail/telefax information is strictly prohibited and may result in legal action against you. Please reply to the sender advising of the error in transmission and immediately delete/destroy the message and any accompanying documents. Thank you. - ::: 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 - ::: 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
