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
ladb.log not being written to
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:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
211
Members:
0
Total:
211
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
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
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
ladb.log not being written to
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
beverly godwin
Veteran Member
Posts: 143
11/2/2011 7:57 PM
We are windows and I think that this could have to do with permissions. I was told to clean out the logs, I'd remove several logs while lawson was stopped and then when it was restarted, they did recreate ..It has not been written to since that date 9/25 with the exception of 10/14 when we did a reboot...so it is only being written to upon a reboot. Any ideas? GSC was no help.
We are 9.0.1.7 GL/HR Suites
KevinH
Basic Member
Posts: 15
11/2/2011 9:26 PM
I'm not sure you have a problem. We're are also Windows, running 9.0.1.5, and I do a weekly reboot which includes a script to archive off and delete the ladb, latm and lajs logs. It's not uncommon to go an entire week without records written to the ladb and latm logs except for the startup and shutdown entries. If there are error conditions encountered though, those records do get written out as they occur.
have you tried to force an error condition to see if anything goes to ladb.log? (like putting an invalid password in your MICROSOFT file...on a test prodln of course).
JimY
Veteran Member
Posts: 510
11/3/2011 10:28 AM
We are on Unix and we can go several days/weeks without anything being written to the ladb.log file except for when we shutdown and restart for backups. When there are errors they are being written to it.
beverly godwin
Veteran Member
Posts: 143
11/3/2011 12:13 PM
Thanks for the responses. This is only happening on live and no errors have been written since 9/25. I'd like to be able to force an error if there was something somewhat non-invasive that I could do on the live system. What types of things would force an error that would not be a big deal to do on live?
KevinH
Basic Member
Posts: 15
11/3/2011 6:04 PM
From the errors I see in my ladb logs, they are all big deals -- unable to connect to the db server, bad triggers to my frontoffice TM app, etc. I'm not aware of any trivial conditions that would write out to that log. The fact that you get the startup/shutdown entries in the log tells me that the system is able to write to the file successfully.
If I really had to prove this out, I might consider doing a quickpaint on an empty table in an unused system code (it would be SL for me), drop the table with bldxxxddl, try to access the table which should generate the error, then rebuild the table. It's not totally non-invasive or risk-free...but that's all I could think of.
Jimmy Chiu
Veteran Member
Posts: 641
11/3/2011 6:44 PM
if you have another prodline in the same environment like test etc. You can take the test database offline and force some ladb.log entries. Or you can put it in read only mode and attempt to change data. That should do it.
You are not authorized to post a reply.