Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Corruption in LogEvents table
Mon, Jun 17 2019 11:15 AMPermanent Link

Alan Craker

We have a customer getting '0.0' is not a valid timestamp error.  We've tracked it down to a few corrupted records in the LogEvents table.  What options do I have to repair the table or delete the offending records?  Trying to delete through EDB Manager tells me I'm trying to update a read-only cursor.
Tue, Jun 18 2019 2:48 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Alan


If you're talking about the built in LogEvents table then, as far as I know, there are no facilities for editing it - its purely a system maintained file.

What you can do is delete it totally. However, I'd recommend taking a copy first and sending to Tim because since its a system maintained file it shouldn't have invalid entries

The file to delete is EDBConfig.EDBLog

You'll need everyone off the system first, and any server shut down.

If its not the system LogEvents table then we need more info.

Roy Lambert
Fri, Jun 21 2019 10:55 AMPermanent Link

Alan Craker

Thanks Roy.  Deleting EDBConfig.EDBLog took care of it.
Image