Subject: | |
From: | |
Reply To: | Reynolds, James |
Date: | Tue, 17 Aug 1999 09:28:00 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Chris,
We were having the same problem with our Jumbo data Sets. The good folks at
Adager
recommended that we purge the databases before we do the restore, and since
we've
been doing that, we haven't had the problem
James Reynolds
PHP
Albuquerque, NM
----------
From: Chris Bartram
To: [log in to unmask]
Subject: TurboImage/Jumbo problem
Date: Tuesday, August 17, 1999 9:17AM
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
|
|
|