Lawson Addins LSF9 'Time out' problems

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

dd21

New Member Send Private Message

Posts: 0

2/12/2010 2:46 PM

Since the upgrade to LSF9 (and patches that were since installed) I am experiencing problems running large queries using Lawson addins. I am getting a 'time out' message regularly or a 'Fatal error' message very occasionally. The IS department is telling me that this is causing problems with slowing down the users of Lawson Portal but I cannot understand why this did not happen previously as I have been using the same query regularly for almost 4 years. I have to run large data sets regularly and although Lawson tells me to break down the running of these queries into small chunks, this is causing me time management issues as it takes ages to get the information required out and validated. I could previously run it in 6 month time frames and now have to run it monthly and by Buyer. Any help on this would be greatly appreciated.

mark.cook

Veteran Member Send Private Message

Posts: 444

2/12/2010 5:12 PM

Is your IS department seeing anything in the websphere logs? We had some similar issues with data calls in LSF9, we have addins as well as MSCM data calls (MSCM for us is on UNIX). We ended up splittling out these types of transactions into a separate JVM but could see hung threads in the websphere logs.

Our requirements were a little bigger with a different set up than the norm for MSCM but basically it sounds like your fighting over the same resources which is slowing things down and causing the errors.

dd21

New Member Send Private Message

Posts: 0

2/12/2010 5:28 PM

Thank you for your reply. It definitely is something like you suggested (according to our IS department). I am not sure about your other question although I do know that patches were installed at the turn of the year and since then real problems have occured. Since I posted my question I noted that there is another thread talking about a similar problem as mine and it was posted nearly two years ago so think this is something that is ongoing. I always use indexes and know how to build efficient queries so do not think there is anything else I can do except keep breaking down the queries which is so labor and time intensive. Thanks again.

dd21

New Member Send Private Message

Posts: 0

2/18/2010 1:57 PM

I would like to hear from anyone who uses Crystal reports to extract data as opposed to Lawson addins. Pros, cons or any other information would be great. I am trying to decide whether this is a route to go down. Thanks.

Deleted User

New Member Send Private Message

Posts: 0

2/18/2010 3:51 PM

Hi Debra - I'm not sure it's really an "either or" question - both tools afford different functionality, and are good and bad for their own reasons. In my opinion, add-ins is the easier of the 2 tools for end users, mainly because most employees have at least some exposure to excel, tables are already linked, it follows security access, etc. Crystal, on the other hand, requires some different type of training, has the capacity to build more complex reports, utilizes subreports, etc. We use both tools here, and I wouldn't have it any other way -

Good luck with your decision!

dd21

New Member Send Private Message

Posts: 0

2/18/2010 8:08 PM

Thanks for your reply Stephanie. Can Crystal just be used to run a list of data that can then be manipulated as needed in Excel? Or does it always have to be a formatted report as an end result? I am thinking this could be used just for the large queries that are failing to run in addins at the moment due to the Lawson 9.0.0.3 installation. We do need the end result to be exported to Excel though for tweaking. Thanks again.

Dave Mitchell

Advanced Member Send Private Message

Posts: 18

2/19/2010 3:44 PM

Hi,

As Stephanie stated, there are other tools that can be used. In addition to MS-Add-In's, and Crystal, we also use SQL. WinSQL (a free download from the net), and RapidSQL. For quick table queries SQL is ideal, with the results being capable of being pasted into Excel.

A hint for WinSQL (the free parts of it anyway), once the query is complete, r-click on any of the query "cells" and select copy entire grid. This puts the information into ClipBoard. You can then paste directly into Excel. Or you can clcik Edit, Select All, Edit, Copy, and then paste into Excel. The second method is twice as many key-strokes.

Dave