HP3000-L Archives

March 2003, Week 4

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:
Patrick Mullen <[log in to unmask]>
Reply To:
Patrick Mullen <[log in to unmask]>
Date:
Thu, 20 Mar 2003 08:56:03 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
Michael,

>
>i am getting this error-message and can't find anything in the manual.
>Bad search value in path 2, set 113.
>This occurs at a DBPUT and the DB-COND is +95 as a return-value.
>
>No other problems with this dataset. Just with 1 record.
>There is 1 SUPERDEX-Key on the dataset.
>
>Anybody has any knowledge about this error?

This is not a very common error return status from DBPUT.  I thought that I
had seen it before and in fact you can read a report here:

http://www.adager.com/LiteraturePDF/BusinessCritical.pdf

Do you have the entire return output from DBEXPLAIN?  That might shed more
light on this issue.

I would suggest using a diagnostic ('Path Examine' in Adager) on both the
detail and master sets in question and do whatever repairs it indicates are
necessary.

If they come out clean (no errors), you might want to try adding the entry
while indexing is disabled.  If that works, you should reindex.

Patrick

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

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

ATOM RSS1 RSS2