HP3000-L Archives

August 2001, 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:
Adam Dorritie <[log in to unmask]>
Reply To:
Adam Dorritie <[log in to unmask]>
Date:
Wed, 1 Aug 2001 10:41:50 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
Having seen a few posts from Ron on the subject of Netbase, it's entirely
possible that Ron may not have support with Quest.  I would strongly suggest
getting said support if such is the case (if your business case was strong
enough to buy Netbase, it's probably strong enough to warrant support).
That aside, the message is trying to tell you that your master and shadow
versions of the database are not the same.

When a record is written on the master system, Netbase remembers the record
number into which the entry is written.  It then expects that entry to be
written into the same record location on the shadow machine when that record
is applied (as would happen in physically identical databases).  When the
record is applied on the shadow system and it is placed in a different
record location, Netbase sees that as a problem (identical databases cause
records to be written into the same place, record was not written into the
same place --> databases not identical).  While there is always the
possibility that this is a Netbase issue (i.e. bug), that prospect is highly
unlikely.  More likely you've got a problem along the lines of the
following:

- A database change (like capacity) made on either the master or the shadow
copy, but not both (or not according to proper procedures).
- A resync was performed, but not according to the procedures appropriate
for your environment.
- A program which updated either the master or the shadow copy of the
database is not running through Netbase (e.g. has a NONB program entry, was
run when the JCW NBDISBALE was set to FATAL, a CM program which updated the
database was run without the CM intercepts enabled, etc.)
- And so on.

The Quest support folks should be able to provide more possible sources of
the error and to help you diagnose the problem.

Best of luck.

Adam Dorritie
Easy Does It Technologies LLC
http://www.editcorp.com
(702) 270-6402

Larry writes:
> I'm not sure but I think it translates to, "time to call Quest"?  I think
> your data base is out of sync?

in response to Ron's question

> I'm running Netbase and I keep getting this sync error:
>
>
> 212 13:08:32 NBP001/Sync problem with data base MACORD.MACSDATA.WETSEAL,
> set MESSAGE-FILE (#38)
> 212 13:08:32 NBP001/WARNING 209: Entry 11 was put in the wrong location
> 212 13:08:33 NBP001/DISABLING SET #38 (MESSAGE-FILE) OF DATA BASE
> MACORD.MACSDATA.WETSEAL
>
>
> What does this mean??

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

ATOM RSS1 RSS2