HP3000-L Archives

June 1996, Week 3

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:
Ken Sletten b894 c332 x62525 <[log in to unmask]>
Reply To:
Ken Sletten b894 c332 x62525 <[log in to unmask]>
Date:
Tue, 18 Jun 1996 12:05:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Joe Smith wrote after I wrote:
 
>We too, do not have the full Allbase product.  We installed PP5 last week
>and began getting an error message on any Image DBCLOSE.  It turned out to
>be a harmless but none-the-less annoying message.  HP said the problem was
>due to a mismatch in Image/SQL versions due to the checksumming problem you
>referred to, and the full set of Image/SQL patches had to be applied to fix
>the problem.  So, let the installer beware...
 
I knew about the DBCLOSE problem, but I didn't know that
it was another checksum thing that caused it.  Thanks.
 
It turns out the follow-on "post PP 5" patches I alluded to in
my previous email contain the fix for this problem:
 
"TIXHXX9 - VUF C.06.12.  When user logging enabled,
                    DBCLOSE may generate -333."
 
Plus there is:
 
"ATCHXY3 - Image/SQL internal error 127,137,00
                    (DBERR 13553)"
 
Ken Sletten

ATOM RSS1 RSS2