529 Enterprises
2008-10-25 00:11:47 UTC
(Sorry for the repeat, but I left out some info)
I have a client running a peer2peer network with machines running everything
from Win2k to XP_Sp2 and a dB IV app that has run reliably (with minor
glitches) for over 15 years. Within the last three days, one machine has
suddenly decided to blow up during indexing. The machine is a 3+/- GHz with
512mb memory running XP sp2 (sorry, I don't know additional details). The
program is run through a DOS window with the default settings on all
machines.
Here are the details:
Two master tables having 60k+ records
A detail table having 160k records
The indexing routine deletes existing NDX files using the "DELETE FILE"
command and then recreates the NDX from scratch. The problem machine issued
a "File already exists" command even though the DELETE FILE command was
successful and a directory listing confirmed no NDX files. When it did get
past the NDX recreation, it blew up on the detail table reindexing.
I ran the same process programatically 4-5 times last night and reindexed
manually twice from a tablet PC running Windows Tablet XP (or whatever its
callled) and everything worked fine. Several other machines in the office,
including the Win2k machines, pass the indexing fine. The tablet PC also
has 512mb memory, consistently had less available memory (according to task
manager) during the indexing process than the problem machine, but processed
with no problems. The command to reindex the detail file is:
Use DetFile
Pack
It uses two simple index keys in an MDX file, and this machine worked fine
on it until about two or three days ago. Physical memory has been swapped
and tested, the hard drive has been tested and I am stumped as to what has
happened unless XP has suddenly changed a disk caching method. Any input,
WAGs or other ideas welcome.
DR Berry
I have a client running a peer2peer network with machines running everything
from Win2k to XP_Sp2 and a dB IV app that has run reliably (with minor
glitches) for over 15 years. Within the last three days, one machine has
suddenly decided to blow up during indexing. The machine is a 3+/- GHz with
512mb memory running XP sp2 (sorry, I don't know additional details). The
program is run through a DOS window with the default settings on all
machines.
Here are the details:
Two master tables having 60k+ records
A detail table having 160k records
The indexing routine deletes existing NDX files using the "DELETE FILE"
command and then recreates the NDX from scratch. The problem machine issued
a "File already exists" command even though the DELETE FILE command was
successful and a directory listing confirmed no NDX files. When it did get
past the NDX recreation, it blew up on the detail table reindexing.
I ran the same process programatically 4-5 times last night and reindexed
manually twice from a tablet PC running Windows Tablet XP (or whatever its
callled) and everything worked fine. Several other machines in the office,
including the Win2k machines, pass the indexing fine. The tablet PC also
has 512mb memory, consistently had less available memory (according to task
manager) during the indexing process than the problem machine, but processed
with no problems. The command to reindex the detail file is:
Use DetFile
Pack
It uses two simple index keys in an MDX file, and this machine worked fine
on it until about two or three days ago. Physical memory has been swapped
and tested, the hard drive has been tested and I am stumped as to what has
happened unless XP has suddenly changed a disk caching method. Any input,
WAGs or other ideas welcome.
DR Berry