Nothing has changed but all of a sudden I am getting #8965 errors on half my
files (Index page buffers corrupt). I go into dbsys and Repair all files,
incl. indexes, and it reports all went well. Then I ran Verify again and 9
show corrupt again.

What is going on here and why all of a sudden? Also don't have a clue how to
correct this situation.

dbsys: Version 4.30 (4.30 Build 5), XP Pro

Jerry

I should have noted that I am also getting an I/O error 32 on at least two
of the databases when attempting to open them. Don't know why that's
happening either.

I will try shutting down our server to see if it clears any unusual database
conditions that may exist (files somehow left open, etc.). We'll see.

Jerry

"Jerry Clancy" <jclancy@billtrak.com> wrote in message
news:8B1BF640-DEC8-4405-A5ED-C81AD480C31C@news.elevatesoft.com...
> Nothing has changed but all of a sudden I am getting #8965 errors on half
> my files (Index page buffers corrupt). I go into dbsys and Repair all
> files, incl. indexes, and it reports all went well. Then I ran Verify
> again and 9 show corrupt again.
>
> What is going on here and why all of a sudden? Also don't have a clue how
> to correct this situation.
>
> dbsys: Version 4.30 (4.30 Build 5), XP Pro
>
> Jerry

Problem resolved, though puzzles remain. After rerunning the
Verify/Repair/Verify scenario again -- and again getting errors in the last
verify -- I decided that 1) the .dat was corrupted and 2) dbsys couldn't
repair it, though it thought it did. My suspicion is that some part of the
file header was screwed up. Since this was a fairly non-volatile file, I
decided to replace the server's copy with a local copy that was a few days
older and, voilà, all was well again.

At one point earlier I was prevented from opening the file, though no
corruption, as if the program in question was trying to open the file in
exclusive mode while someone else was accessing it or vice versa. I could
find nothing on any of our boxes with the file open but rebooted everything,
including the server box, to clear any vestiges of open files should there
really have been any.

In any event, we're back on the air but that #8965 error out of nowhere is
still disturbing.

Jerry

"Jerry Clancy" <jclancy@billtrak.com> wrote in message
news:5EDCA13A-8C46-4B6D-A167-4E62C8B48649@news.elevatesoft.com...
>I should have noted that I am also getting an I/O error 32 on at least two
>of the databases when attempting to open them. Don't know why that's
>happening either.
>
> I will try shutting down our server to see if it clears any unusual
> database conditions that may exist (files somehow left open, etc.). We'll
> see.
>
> Jerry
>
> "Jerry Clancy" <jclancy@billtrak.com> wrote in message
> news:8B1BF640-DEC8-4405-A5ED-C81AD480C31C@news.elevatesoft.com...
>> Nothing has changed but all of a sudden I am getting #8965 errors on half
>> my files (Index page buffers corrupt). I go into dbsys and Repair all
>> files, incl. indexes, and it reports all went well. Then I ran Verify
>> again and 9 show corrupt again.
>>
>> What is going on here and why all of a sudden? Also don't have a clue how
>> to correct this situation.
>>
>> dbsys: Version 4.30 (4.30 Build 5), XP Pro
>>
>> Jerry
>

Jerry,

<<
My suspicion is that some part of the
file header was screwed up. Since this was a fairly non-volatile file, I
decided to replace the server's copy with a local copy that was a few days
older and, voilà, all was well again.
>>

That's definitely curious. My initial suspicion was AV update or something else at OS file handling level that caused the problems. Good to see you've resolved it.

If you have the corrupted version of the file i would suggest you email it to Elevate support so Tim can take a look and see what was really going on there.

Raul

I also thought of that [sending Tim the file] but unfortunately too late.
Didn't keep a copy of the bad one, just copied over it.

Immediately subsequent to resolving it I also got some "insufficient
permissions" issue flagged downloading a zip file that I do routinely from a
state site every hour of every day without issues. In fact, the process had
worked fine just an hour earlier. Something funky was definietly going on
that day. It's resolved but I don't have a warm fuzzy about it.

My first indication of something wrong was getting an "Exception on Send
4.2.0" error sending clients alerts with one of our apps (that use these
files). This is usually an MS Exchange error on the mail server, but my
process may possibly have left stuff open when it encountered it which then
snowballed. Only thing I can thing of.

Moving on...

Jerry

<Raul> wrote in message
news:EF188DCD-1428-4D58-AB55-DC2D72EE5A7F@news.elevatesoft.com...
> Jerry,
>
> <<
> My suspicion is that some part of the
> file header was screwed up. Since this was a fairly non-volatile file, I
> decided to replace the server's copy with a local copy that was a few days
> older and, voilà, all was well again.
>>>
>
> That's definitely curious. My initial suspicion was AV update or something
> else at OS file handling level that caused the problems. Good to see
> you've resolved it.
>
> If you have the corrupted version of the file i would suggest you email it
> to Elevate support so Tim can take a look and see what was really going on
> there.
>
> Raul
>

Jerry,

<< Nothing has changed but all of a sudden I am getting #8965 errors on half
my files (Index page buffers corrupt). I go into dbsys and Repair all files,
incl. indexes, and it reports all went well. Then I ran Verify again and 9
show corrupt again. >>

I know that you resolved this, but if you suddenly start getting such errors
"out of the blue" then the most likely cause is something environmental such
as a disk issue, lack of disk space, AV software, improper shutdown, etc.

Also, don't be shy about contacting support directly for these issues.
You'll get a much faster response than here, and I can give you proper
guidance on how to save the "bad copies" of the table so that you can send
them to me.  I can then tell you what kind of corruption you're seeing, and
its likely cause.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks, Tim. I'll remember that.

Jerry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:C7543465-FDAD-4217-A7BF-2AADAF1BCA5A@news.elevatesoft.com...
> Jerry,
>
> << Nothing has changed but all of a sudden I am getting #8965 errors on
> half my files (Index page buffers corrupt). I go into dbsys and Repair all
> files, incl. indexes, and it reports all went well. Then I ran Verify
> again and 9 show corrupt again. >>
>
> I know that you resolved this, but if you suddenly start getting such
> errors "out of the blue" then the most likely cause is something
> environmental such as a disk issue, lack of disk space, AV software,
> improper shutdown, etc.
>
> Also, don't be shy about contacting support directly for these issues.
> You'll get a much faster response than here, and I can give you proper
> guidance on how to save the "bad copies" of the table so that you can send
> them to me.  I can then tell you what kind of corruption you're seeing,
> and its likely cause.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com