latm configurations

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

latm configurations; Too many deadlocks!
Topic Started: Oct 27 2009, 06:24 AM (133 Views)
lpatena	Oct 27 2009, 06:24 AM Post #1
Advanced Member Posts: 56 Group: Members Member #390 Joined: January 26, 2006	All - I'm looking for suggestions on latm.cfg that may allow an online process to wait a little longer before blowing up due to a deadlock. The Lawson ITEMLOC table is heavily used/updated here. Consequently, we run into alot of deadlocking issueswith this table - particularly in 4th quarter which is our busiest time of year. Question #1 - is the OPENTIMEOUT parameter what indicates how long a process/program waits before throwing a database deadlock error? If not, is there such a parameter? Question #2 - if this is the correct parameter - what do you have yours set to? Ours is currently set to 240 seconds. Lawson Apps 8.0.3 MSP8 Lawson Env 8.0.3 ESP7 Oracle Unix Thanks so much in advance, Laura Patenaude Yankee Candle Company lpatena@yankeecandle.com



schroncd	Oct 28 2009, 08:32 AM Post #2
Lawson Technorati Posts: 689 Group: Members Member #13 Joined: January 11, 2006	The default for OPENTIMEOUT is 240 and is consistent at 240 for any size client. It's one of those things you "just don't change" when you are performance tuning. Usually your Deadlock Timeouts are set in your RDBMS, and Lawson just reports that the timeout occurred after being notified of the event by the database. If you are getting database timeout messages they are coming from your DB and not a Lawson configuration



lpatena	Oct 30 2009, 04:47 AM Post #3
Advanced Member Posts: 56 Group: Members Member #390 Joined: January 26, 2006	Thanks so much for the information!


« Previous Topic · Other · Next Topic »