Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread DBISAM_REMOTEUNKNOWN (11279)
Tue, Feb 14 2006 9:47 PMPermanent Link

Philip Frank
One of my clients just received this error. They're running C/S 3.24. What should I possibly look for as a cause? In addition to this error, we've
experienced at least three times over the same number of months where the database has overwritten an existing record when appending a new
one.  I thought that perhaps one of the workstations had some bad RAM, but since this is running as a C/S app the impact of a local workstation's
RAM should have much less impact.

I've only had the 'overwriting' issue happen one other time at a different client. That it's happened three times in the recent past is a big issue,
and I'd like to try and track down the cause, if there is one. I'm wondering if the 11279 error may be a contributing factor.

Phil Frank
Wed, Feb 15 2006 12:22 AMPermanent Link

Eryk Bottomley
Philip,

> One of my clients just received this error. They're running C/S 3.24. What should I possibly look for as a cause? In addition to this error, we've
> experienced at least three times over the same number of months where the database has overwritten an existing record when appending a new
> one.  I thought that perhaps one of the workstations had some bad RAM, but since this is running as a C/S app the impact of a local workstation's
> RAM should have much less impact.

Have you checked the server log file (use SrvAdmin for this)? There may
be further details recorded there.

Eryk
Wed, Feb 15 2006 11:30 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Phil,

<< One of my clients just received this error. They're running C/S 3.24.
What should I possibly look for as a cause? >>

I would have to see the log to be able to tell you more.  The log will
indicate which operation caused the error, and that is the most important
piece of information.

<< In addition to this error, we've experienced at least three times over
the same number of months where the database has overwritten an existing
record when appending a new one.  I thought that perhaps one of the
workstations had some bad RAM, but since this is running as a C/S app the
impact of a local workstation's RAM should have much less impact. >>

DBISAM does not overwrite existing records, accidentally or otherwise.  What
you're seeing must be caused by something external to DBISAM.

--
Tim Young
Elevate Software
www.elevatesoft.com



Wed, Feb 15 2006 2:14 PMPermanent Link

Philip Frank
"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

> I would have to see the log to be able to tell you more.  The log will
> indicate which operation caused the error, and that is the most important
> piece of information.

I've just looked at the log, and I don't see anything out of the ordinary at the time the error occurred. Nothing but connections, re-connections, log-
ins, etc. I'm attaching the log for the last two days though, so you can take a look.

> DBISAM does not overwrite existing records, accidentally or otherwise.  What
you're seeing must be caused by something external to DBISAM.

Any thoughts as to what might cause this? I'm on a witch hunt, because the client is getting apprehensive. The scenario has been the same almost
every time: a new record is being created, but rather than creating a new record, an existing record (the first one in the table has been the target
twice) is replaced with the new data.

I was hoping that yesterday's server error might be a clue.

Phil Frank



Attachments: PAH DBISAM Log.txt
Wed, Feb 15 2006 2:25 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Philip


Probably not the case but is there any corruption?

Roy Lambert
Wed, Feb 15 2006 5:05 PMPermanent Link

Philip Frank
Roy Lambert <roy.lambert@skynet.co.uk> wrote:

> Probably not the case but is there any corruption?

Well, after this problem occurs there always is. At a minimum the index gets out of whack. I've never been told if there was corruption beforehand,
but the client themselves wouldn't necessarily know that either. I was just granted remote access to the data. I'm think going to start running a
weekly preemptive repair.

Phil Frank
Thu, Feb 16 2006 4:26 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Phil,

<< I've just looked at the log, and I don't see anything out of the ordinary
at the time the error occurred. Nothing but connections, re-connections,
log- ins, etc. I'm attaching the log for the last two days though, so you
can take a look. >>

Does this log cover the time period when the error occurred ?

<< Any thoughts as to what might cause this? I'm on a witch hunt, because
the client is getting apprehensive. The scenario has been the same almost
every time: a new record is being created, but rather than creating a new
record, an existing record (the first one in the table has been the target
twice) is replaced with the new data. >>

Well, the most obvious reason is a coding error or SQL error where you think
you're inserting when you're actually editing, or a situation where the
first record is accidentally deleted and then a new one is re-added.  This
is all just supposition, however, since I don't have the code in front of me
to check.  Apart from that, only a DBISAM error could cause this.  However,
as I stated before, I have no reason to believe that DBISAM is doing this.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Feb 16 2006 4:27 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Phil,

<< Well, after this problem occurs there always is. At a minimum the index
gets out of whack. I've never been told if there was corruption beforehand,
but the client themselves wouldn't necessarily know that either. I was just
granted remote access to the data. I'm think going to start running a weekly
preemptive repair. >>

You should probably consider updating them to 3.30.  That will make sure, at
the very least, that you're using the latest 3.x with the most fixes in it.
There were quite a few fixes between the two releases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image