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:
Wojo
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
5265
People Online:
Visitors:
413
Members:
0
Total:
413
Online Now:
New Topics
Lawson S3 Procurement
Tolerance Settings
3/31/2025 2:01 PM
I've been trying to set a tolerance for some t
Dealing with Lawson / Infor
Printing Solutions other than MHC
3/27/2025 1:00 PM
What are others using for printing solutions besid
Lawson S3 Procurement
Green check marks in Lawson 9.0.1
3/20/2025 4:55 PM
Hi, How to remove green check mark on items when o
Lawson S3 HR/Payroll/Benefits
Pay Rate History to Show All Positions
2/26/2025 3:34 PM
Does anyone know how to modify payratehistory.htm
Infor CloudSuite
How to build a Pre-Prod tenant
2/7/2025 1:28 AM
After we finished our implementation and ended our
Lawson S3 Procurement
Browser issue with RQC Shopping
1/28/2025 5:49 PM
Since the recent Chrome/Edge updates, our RQC shop
Lawson S3 Procurement
S3-Procurement New Company
1/22/2025 10:38 PM
My Accounting Department has created a new Company
S3 Customization/Development
JUSTIFIED RIGHT
1/15/2025 7:41 PM
Is there a way in Lawson COBOL to make a character
S3 Systems Administration
ADFS certificate - new cert
12/3/2024 9:38 PM
The certificates on the windows boxes expired and
Lawson S3 HR/Payroll/Benefits
Post Tax Benefit Plan Table
11/14/2024 9:16 PM
Hi, totally new to Laswon. I have a repor
Top Forum Posters
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
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
ladb.log not being written to
Please
login
to post a reply.
5 Replies
0
Subscribed to this topic
27 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
beverly godwin
New Member
Posts: 0
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
Deleted User
New Member
Posts: 0
11/2/2011 9:26 PM
Split
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
Split
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
New Member
Posts: 0
11/3/2011 12:13 PM
Split
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?
Deleted User
New Member
Posts: 0
11/3/2011 6:04 PM
Split
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
Split
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.
Please
login
to post a reply.