经常数据库损坏 [英] frequent database corruption

问题描述

我已经在新闻组和其他访问上阅读了很多有关数据损坏的相关网站，但是因为我们仍然无法确定这个问题吗？我发布了这个详细解释我的

问题：


我们有一个23用户环境，带有Windows高级服务器和windows

具有访问权限2002的2000个客户端以FE / BE
格式在所有客户端上运行。问题是我们的数据库在

a忙碌的一天被损坏了近3-6次（正在处理大量数据）。


通常情况下，以下方式是数据库损坏：

1.我们收到错误消息无法识别的数据库格式 - 你是否需要修复... b $ b ... ？这种情况最常见，数据库上的压缩和修复对我们来说很有用。

2.第二种错误是任何表中的一条记录变为

腐败？这通常发生在#error中。在记录的每个字段中

或####在每个领域或有时东方和其他乱码

字符代替记录中的数据。有时可以删除此记录

，有时其余记录必须将

复制到新表中。


问题面孔还可以从任何客户端开始吗？因此，我们不会因为任何一个特定的客户而认为它是b $ b。


这是一个简短的历史，可以帮助您帮助我们识别

问题来源：


1.早些时候我们在使用新版Netware上的BE的access97时获得了win95。

那个时候，四年来，我们从未遇到过这个问题。

2.我们为win2000的所有节点安装了新机器

access2000（仍在使用netware服务器）。我们将相同的

访问文件从97升级到2000.仍然没有问题。

3.然后我们将服务器更改为赢得2000高级服务器。当我们开始遇到腐败问题时，这就是
。

4.我们进一步改为access2002？希望这会消除

问题？但它没有。


我们进一步确保：

1.所有节点都有访问2002，SP4 for win2000和相同的Jet引擎

4.0

2.我们更改了服务器的网卡，服务器的电缆和

切换以确保它不是因为网络硬件设备？仍然

问题仍然存在。


任何人都可以指导我们如何进一步隔离问题然后

我们如何解决它。

提前致谢

adirat

I have read a lot on this subject on newsgroups and other access
related websites on data corruption, but since we are still not able
to isolate the problem ? I am posting this detailed explanation of my
problem:

We have a 23 user environment with Windows advanced server and windows
2000 clients with access 2002 running on all clients in a FE/BE
format. The problem is our database gets corrupted almost 3-6 times on
a busy day (lot of data being processed).

Typically the following ways are in which the database gets corrupt:
1. We get the error message "Unrecognizable database format - do you
want to repair...." ? this situation is most common and a compress and
repair on the database does the trick for us.
2. The second kind of error is when one record in any table becomes
corrupt ? this usually happens with "#error" in each field of a record
or "####" in each field or sometimes "oriental and other garbled
characters" in place of the data in a record. Deleting this record is
sometimes possible, sometimes the rest of the records have to be
copied into a fresh table.

Also the problem faces could start on any client ? hence we do not
think it is because of any one particular client.

Here is a brief history which can assist you in helping us dentify the
source of problem:

1. Earlier we had win95 with access97 with BE on Novel Netware. At
that time, for four years, we never faced this problem.
2. The we got new machines for all the nodes with win2000 with
access2000 (still using the netware server). We upgraded the same
access file from 97 to 2000. STILL NO PROBLEM.
3. Then we changed the server to win 2000 advanced server. That is
when we started having the corruption problems.
4. We further changed to access2002 ? hoping this would remove the
problem ? but it hasn''t.

Further we have ensured that:
1. All the nodes have access 2002, SP4 for win2000 and same Jet engine
4.0
2. We have changed the server''s network card, server''s cable and
switch to ensure it is not because of network hardware devices ? still
the problem persists.

Can anybody guide us how do we further isolate the problem and then
how do we resolve it.
Thanks in advance
adirat

推荐答案

有一点你没提到：你有没有从前端（查询，表单，报告，

宏，模块和任何本地）分离后端（表，

数据和关系）查找表）并给每个用户自己的

副本的前端链接到后端的表？有多个用户登录到前端的同一副本或

单片数据库，大大增加了腐败的可能性。


在多用户环境中有一个关于Access的介绍性演示

我为我的用户组做的，你可以从
下载 http://appdevissues.tripod.com 。它将确定我认为值得讨论的话题，以及更多内容。关于多用户环境中Access的主题的详细

信息和链接的最佳集合

是MVP Tony Toews的网站， http://www.granite.ab.ca/accsmstr.htm 。你会在Tony的网站上找到你问题的答案。


Larry Linson

Microsoft Access MVP


" adirat" <广告**** @ vsnl.com>在消息中写道

news：1b ************************** @ posting.google.c om ...

One thing you did not mention: have you separated the back-end (tables,
data, and relationships) from the front-end (queries, forms, reports,
macros, modules, and any local lookup tables) and given each user their own
copy of the front-end to be linked to the tables in the back end? Having
multiple users logged in to the same copy of the front-end or to the
monolithic database greatly increases the chances of corruption.

There''s an introductory presentation on Access in a Multiuser Environment
that I did for my user group that you can download from
http://appdevissues.tripod.com. It will identify topics that I thought
worthwhile to discuss, and a bit more. The best collection of detailed
information and links on the subject of Access in the multiuser environment
is at MVP Tony Toews'' site, http://www.granite.ab.ca/accsmstr.htm. You''ll
likely find the answer to your problem in the references at Tony''s site.

Larry Linson
Microsoft Access MVP

"adirat" <ad****@vsnl.com> wrote in message
news:1b**************************@posting.google.c om...

我已经在新闻组和其他访问相关网站上阅读了很多有关数据损坏的内容，但由于我们仍然无法隔离问题 - 我发布了我对这个问题的详细解释：

我们有一个23用户环境，带有Windows高级服务器和windows
2000个客户端，其访问权限2002运行在FE / BE中的所有客户端<格式。问题是我们的数据库在忙碌的一天中被破坏了近3-6次（正在处理大量数据）。

通常，以下方式会导致数据库损坏：
2.第二种错误是任何表中的一条记录变得腐败 - 这个通常发生在#error中。在记录的每个字段中
或####在每个领域或有时东方和其他乱码
字符代替记录中的数据。删除此记录有时是可能的，有时其他记录必须被复制到一个新表中。

问题面孔也可以从任何客户端开始 - 因此我们不要认为这是因为任何一个特定的客户。

这是一个简短的历史，可以帮助您帮助我们找出问题的根源：

1.早些时候，我们在新网络版上使用了Access97和win97获得了win95。当时，四年来，我们从未遇到过这个问题。
2.我们为win2000的所有节点安装了新的机器，使用了access2000（仍在使用netware服务器）。我们将相同的
访问文件从97升级到2000.仍然没有问题。
3.然后我们将服务器更改为赢得2000高级服务器。那是当我们开始遇到腐败问题时。
4.我们进一步改为access2002 - 希望这会消除问题 - 但它没有。
1.所有节点都有访问2002，SP4 for win2000和相同的Jet引擎
4.0
2.我们已经更改了服务器的网卡，服务器的电缆和
开关，以确保它不是因为网络硬件设备 - 仍然存在问题。

任何人都可以指导我们如何进一步隔离问题然后
我们如何解决它。
提前致谢
adirat

I have read a lot on this subject on newsgroups and other access
related websites on data corruption, but since we are still not able
to isolate the problem - I am posting this detailed explanation of my
problem:

We have a 23 user environment with Windows advanced server and windows
2000 clients with access 2002 running on all clients in a FE/BE
format. The problem is our database gets corrupted almost 3-6 times on
a busy day (lot of data being processed).

Typically the following ways are in which the database gets corrupt:
1. We get the error message "Unrecognizable database format - do you
want to repair...." - this situation is most common and a compress and
repair on the database does the trick for us.
2. The second kind of error is when one record in any table becomes
corrupt - this usually happens with "#error" in each field of a record
or "####" in each field or sometimes "oriental and other garbled
characters" in place of the data in a record. Deleting this record is
sometimes possible, sometimes the rest of the records have to be
copied into a fresh table.

Also the problem faces could start on any client - hence we do not
think it is because of any one particular client.

Here is a brief history which can assist you in helping us dentify the
source of problem:

1. Earlier we had win95 with access97 with BE on Novel Netware. At
that time, for four years, we never faced this problem.
2. The we got new machines for all the nodes with win2000 with
access2000 (still using the netware server). We upgraded the same
access file from 97 to 2000. STILL NO PROBLEM.
3. Then we changed the server to win 2000 advanced server. That is
when we started having the corruption problems.
4. We further changed to access2002 - hoping this would remove the
problem - but it hasn''t.

Further we have ensured that:
1. All the nodes have access 2002, SP4 for win2000 and same Jet engine
4.0
2. We have changed the server''s network card, server''s cable and
switch to ensure it is not because of network hardware devices - still
the problem persists.

Can anybody guide us how do we further isolate the problem and then
how do we resolve it.
Thanks in advance
adirat

你试过吗 http://support.microsoft.com/?kbid=272582 ??


它在类似但不完全相同的环境中为我们工作。


John

" adirat" <广告**** @ vsnl.com>在消息中写道

news：1b ************************** @ posting.google.c om ...

Have you tried http://support.microsoft.com/?kbid=272582 ??

It worked for us in a similar, but not exactly the same, environment.

John
"adirat" <ad****@vsnl.com> wrote in message
news:1b**************************@posting.google.c om...

我已经在新闻组和其他访问相关网站上阅读了很多有关数据损坏的内容，但由于我们仍然无法隔离问题 - 我发布了我对这个问题的详细解释：

我们有一个23用户环境，带有Windows高级服务器和windows
2000个客户端，其访问权限2002运行在FE / BE中的所有客户端<格式。问题是我们的数据库在忙碌的一天中被破坏了近3-6次（正在处理大量数据）。

通常，以下方式会导致数据库损坏：
2.第二种错误是任何表中的一条记录变得腐败 - 这个通常发生在#error中。在记录的每个字段中
或####在每个领域或有时东方和其他乱码
字符代替记录中的数据。删除此记录有时是可能的，有时其他记录必须被复制到一个新表中。

问题面孔也可以从任何客户端开始 - 因此我们不要认为这是因为任何一个特定的客户。

这是一个简短的历史，可以帮助您帮助我们找出问题的根源：

1.早些时候，我们在新网络版上使用了Access97和win97获得了win95。当时，四年来，我们从未遇到过这个问题。
2.我们为win2000的所有节点安装了新的机器，使用了access2000（仍在使用netware服务器）。我们将相同的
访问文件从97升级到2000.仍然没有问题。
3.然后我们将服务器更改为赢得2000高级服务器。那是当我们开始遇到腐败问题时。
4.我们进一步改为access2002 - 希望这会消除
问题 - 但它没有。
1.所有节点都有访问2002，SP4 for win2000和相同的Jet引擎
4.0
2.我们已经更改了服务器的网卡，服务器的电缆和
开关，以确保它不是因为网络硬件设备 - 仍然存在问题。

任何人都可以指导我们如何进一步隔离问题然后
我们如何解决它。
提前致谢
adirat

I have read a lot on this subject on newsgroups and other access
related websites on data corruption, but since we are still not able
to isolate the problem - I am posting this detailed explanation of my
problem:

We have a 23 user environment with Windows advanced server and windows
2000 clients with access 2002 running on all clients in a FE/BE
format. The problem is our database gets corrupted almost 3-6 times on
a busy day (lot of data being processed).

Typically the following ways are in which the database gets corrupt:
1. We get the error message "Unrecognizable database format - do you
want to repair...." - this situation is most common and a compress and
repair on the database does the trick for us.
2. The second kind of error is when one record in any table becomes
corrupt - this usually happens with "#error" in each field of a record
or "####" in each field or sometimes "oriental and other garbled
characters" in place of the data in a record. Deleting this record is
sometimes possible, sometimes the rest of the records have to be
copied into a fresh table.

Also the problem faces could start on any client - hence we do not
think it is because of any one particular client.

Here is a brief history which can assist you in helping us dentify the
source of problem:

1. Earlier we had win95 with access97 with BE on Novel Netware. At
that time, for four years, we never faced this problem.
2. The we got new machines for all the nodes with win2000 with
access2000 (still using the netware server). We upgraded the same
access file from 97 to 2000. STILL NO PROBLEM.
3. Then we changed the server to win 2000 advanced server. That is
when we started having the corruption problems.
4. We further changed to access2002 - hoping this would remove the
problem - but it hasn''t.

Further we have ensured that:
1. All the nodes have access 2002, SP4 for win2000 and same Jet engine
4.0
2. We have changed the server''s network card, server''s cable and
switch to ensure it is not because of network hardware devices - still
the problem persists.

Can anybody guide us how do we further isolate the problem and then
how do we resolve it.
Thanks in advance
adirat

ad **** @ vsnl.com （adirat）写道：

ad****@vsnl.com (adirat) wrote:

3。然后我们更改了服务器以赢得2000高级服务器。那是当我们开始遇到腐败问题时。

3. Then we changed the server to win 2000 advanced server. That is
when we started having the corruption problems.

鉴于此历史，我强烈怀疑问题是
$ b上的OpLocks设置$ b服务器。损坏的Microsoft Access MDB原因 - OpLocks
http：/ /www.granite.ab.ca/access/corr...sesoplocks.htm


Tony

-

Tony Toews，Microsoft Access MVP

请仅在新闻组中回复，以便其他人可以

阅读整个帖子。

Microsoft Access Links，Hints，Tips&会计系统
http://www.granite.ab.ca /accsmstr.htm

这篇关于经常数据库损坏的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！