We've done a few restores of databases with jumbo sets -- no problems such
as the one you describe.  What software are you using to restore the
database(s)?  Also, we're on PP4 (going to PP7, soon) on our production
box, so we may have to face this, yet.  We haven't restored j-sets on our
PP6 box (Y2K test).

--
Lee Gunter                         The Regence Group
Supervisor, TRG HP/MPE Systems     503.375.4498
--
Opinions expressed are solely mine.




From: Chris Bartram <[log in to unmask]> on 08/17/99 08:11 AM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  [HP3000-L] TurboImage/Jumbo problem




Don't know if anyone else has seen this, but so far we've been batting
1000;
every time we've restored a database with a Jumbo dataset, it's
"corrupted".

Apparently there's a problem with the "chunk header timestamp" when they
get
restored and the database is inaccessible. many thanks to Tim Joseph from
Bradmark who provided us with a DEBUG script that triggers some kind of
auto correction of the jumbo files. Tim tells me that the problem is fixed
in TurboImage C.07.23 which is still in beta. S/R 1653284398.

Our systems are on 5.5 PP6 and PP7. Both encountered the same problem, on
EVERY restore (of a database w/jumbo sets).

Are we the only lucky ones that have hit this??? I don't recall hearing
about
it on the list previously? It cost us many hours...

    -Chris Bartram