We have some "lost" data and my usual techniques of finding it aren't working. SQLA 184.108.40.2065. Straight client-server app, no MobiLink. A user brought me a printout from May 14 showing 2 lines of data. Running that printout today only contains 1 line of that data. My usual high-level "audit trails" didn't show any deletes. So I did dbtran -d -t of all the transaction log files from that day until today (we do twice a day dbbackups with -r option). I found the insert transactions in the May 14th log file as expected. That gave me the PK for the lost record (a BIGINT Global Autoincrement). I ran an ISQL select for that PK just to make sure the row isn't there and suffering from some report bug. I did a Windows gnu grep search of all the files for that PK value. The ONLY result was the original insert. We run dbvalid every night on the database, and no errors reported.
So I am stumped! And would surely appreciate any further ideas. Thanks.
asked 26 Jun '14, 11:25
The mysterious part of my problem is solved! Using Mikel's suggestion, I isolated the problem to a half day. Editing the log file (with Wordpad) instantly revealed the delete for that record key. While I can find no published limitations on file sizes with the grep program I was using, it obviously did not parse this 258mb log file to find this entry almost at the end of the file. (Let me see: freeware plus the IT time to restore a lot of tape backups plus my time to isolate the particular database copy... that adds up to quite a few bucks!!)
Now to figure out what really was going on to delete the records...
Thanks again for the suggestions everyone.
After researching another issue last week which caused me to read some posts on StackExchange, quite a few of which were not helpful and often down right rude, I appreciate once again this forum and all of you who contribute respect, as well as really helpful information, to all of us! Thanks!!