[AccessD] Database Corruption

Hi Jennifer,

In my experiences with corruptions over the years, pretty much all of
them have been caused by network connectivity issues. Even with the
database moved off the SAN ad back to the original server, did they
still have other drives mapped to the SAN?? Did all the workstations
reboot after the move back?? I am theorizing that some connectivity
issue with the SAN is causing the workstations to go into some
temporary wait state and then the Access database thinks the user has
disconnected....and bang, it sets the corrupted flag and the next user
that tries to get in is locked out until the compact/repair is done.

Good luck figuring it out, its likely gonna be tough.

GK

On 11/30/05, Jennifer Gross <jengross at gte.net> wrote:
> I have a multi-user (approximately 15 users) database split BE and FE,
> with the FE residing on each individual work station or Terminal Server
> in separate user directories.  About a week ago IT moved the BE to a SAN
> and since then we have been experiencing corruption of the BE about 3
> times a day.  I have imported all the tables and relationships into a
> new database - still corrupting, rolled back the FE to one that was
> stable prior to the corruptions starting - still corrupting, moved the
> BE back to the server off the SAN - still corrupting and now I am going
> to import the table structures into a new database and then import the
> data into the new tables.
>
> It is an A2K FE and BE.  Most users are on Win2K with A2K, some are on
> WinXP with AXP or A2003.  Does anyone have any ideas what could be going
> on here?  Any suggestions are appreciated.
>
> Thanks in advance,
>
> Jennifer Gross
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


--
Gary Kjos
garykjos at gmail.com