Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Regular Reboot of Lawson System
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
51
Members:
0
Total:
51
Online Now:
New Topics
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Infor ION
ION vs IPA
2/29/2024 1:24 AM
We had a person new to Lawson and Infor go to Info
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Regular Reboot of Lawson System
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
beverly godwin
Veteran Member
Posts: 143
6/28/2010 6:56 PM
We are on 9.0.1.5 win 2008 64 bit. GSC advised that we should be scheduling regular reboots. I think it has to do with memory leaks or not a good 'clean up' process?
Before our latest upgrade...we did see an issue with job submit error every 20 or so days if we had not rebooted. We are not seeing that since moving to 9.0.1.5.
Are others doing a regular reboot? If so..how often?
Thanks for any info
Tomwise
Advanced Member
Posts: 32
6/29/2010 9:41 AM
Where on UNIX, we never do periodic reboots. It seems to be an inherit problem with Windows, reboots and Hangs. Any application on Windows seems to need to be rebooted every so often. Our ADAM/MKS Window server, Citrix farm, print servers, etc need periodic reboots, especially when they hang.
John Costa
Veteran Member
Posts: 154
6/29/2010 11:33 AM
We are also a Windows 2008 shop and I have scripts that shut down all WebSphere and Lawson services, do a clean-up of temp files and logs, and then reboot the servers. My scripts run evey Sunday morning when user activity is next to none. All of my Lawson and WebSphere products are set up as services that automatically restart in a specific order after the server has come back up. Seems to work pretty well for us.
TBonney
Veteran Member
Posts: 277
6/29/2010 12:12 PM
We're on Windows 2003 (R2) and we also do a regular shutdoen of all WebSphere services and full reboot each sunday after we do the full backup of our Lawson production server. We used to have a fairly frequent amount of stability issues and a reboot was the only fix. Since getting up to 9.0.0.5 in March (and getting Websphere up to 6.1.0.27), we've been quite stable though. However, we have continued to do the full reboot on a weekly basis just to be safe.
Jimmy Chiu
Veteran Member
Posts: 641
7/8/2010 2:42 PM
It depends on your transaction volume. I think your GSC meant by reboot is to clean up work files and log files. Periodically, you should delete the GLTDISKxxxx.idx/dat and TMPxxxxxxx.idx/dat files under your /<lawdir>/<prodline>/work folder and purge the log files in your /<lawdir> also. I would check your work directory if you have not and see how many files you already have (i clean up this directory whenever it's over 5000 files and backup the log files and purge it)
John Henley
Senior Member
Posts: 3348
7/8/2010 3:46 PM
However, do be VERY CAREFUL about deleting work files.
If you have any queued jobs running or in 'needs recovery', you probably shouldn't be rebooting ....
DarS
New Member
Posts: 1
7/8/2010 4:41 PM
I am confused about rebooting. If a job is in needs recovery, it is not running and is waiting for repairs or changes to be made and then to be re-submitted. How does this affect the determination to do a reboot?
We are on Windows 2003 R2 SP2, WAS 6.1.0.27, 9.0.1.4 Portal & Tech and have had to re-start services for WAS and Lawson during past couple of weeks, in prime time, and are now setup for a once a week reboot, early Monday morning.
What items should we be on the lookout for, prior to the reboot, and the proper repair techniques to follow?
John Henley
Senior Member
Posts: 3348
7/8/2010 5:16 PM
What I meant was: you should never script a blind delete of the work (or any, IMHO) files in conjunction with a reboot. Often what you might want to analyze after the reboot would then be missing (one of the reasons I never suggest removing log files in conjunction with a shutdown/reboot, etc. either). As for the perils of rebooting while a job is in needs recovery, it would depend on 1) why the job is in recovery, 2) how serious the job in recovery is (i.e. is it PR140?) and 3) why you are rebooting.
Jimmy Chiu
Veteran Member
Posts: 641
7/9/2010 4:38 PM
I should add this. When purging the GLT/TMP files in work directory, you should be really careful and do the following steps:
1) dbdump <prodline> ckpoint
2) look at the restart-info column in your CKPOINT for any GLTxxxxxx.xxx or TMPxxxxxx.xxx, ***YOU DO NOT DELETE THESE FILES***
3) delete any other GLTXXXXXX.XXX and TMPXXXXX.XXX files in the <prodline>\work that are more than one day old and not the one showing in your CKPOINT restart-info column.
You are not authorized to post a reply.