HP3000-L Archives

March 2002, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Fri, 1 Mar 2002 10:52:43 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Ron ponders:
> Looking at the Netbase $stdlist, I saw this message:
>
>     WARNING 209: Entry 10 was put in the wrong location
>
> What does this mean, and how can I prevent it.

It means that when the POSTing process on the shadow system applied a dbput
that originated on the master system to the shadow copy of the database the
data went into a different physical record in the shadow database than it
had on the master system.

If the databses are truly identical (in sync) then the "deleted chain" and
other structures in the two databases will be the same and therefore newly
"put" records will land in the same physical records on each system.

This is one of the checks that NetBase makes to confirm that your databases
have not gotten out of sync, as has apparently happened in this case.

It implies that one of the databases was modified without going through
NetBase so that the updates would be shadowed, or that one of the databases
was transformed (Adager, etc.), or :RESTORED, or other wise independently
altered.  You could have told NetBase to ignore the operation of some
program inappropriately, or there could be various operational failures
(failure to ENABLE NetBase, etc.) depending on which version of NetBase
you're running.

G.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2