Ralph
Copying all the data to one transaction log = there is corruption.
Therefore, it is not possible to do the big clean in the way you
describe in your book. Copying all the data one panel at a time = no
corruption. As I described below, doing the big clean (after exporting
one panel at a time) and then exporting all the data to one transaction
log made no difference. There is still the corruption.
Any ideas with this would be gratefully received.
Victor Warner.
Ralph Alvy wrote:
Did you see that all the corruption was gone after doing the Big
Clean? To see that, simply do an export of all data to log and view
the log.
On Thu, 23 Aug 2007 12:05:36 -0700, Victor Warner
<[EMAIL PROTECTED]> wrote:
I wanted to do a big clean on a database. Following Ralph's method I
copied all the data in one single Transaction Log. I looked at the
log and I noticed at the beginning of the log file some serious
corruption.
I then created a transaction log for each panel (14 of them) and then
used the report function to print to wpd files all of the panels
individually. Looking through them, there appeared to be no corruption.
I then proceeded to the big clean importing the 14 log files 1 at a
time. This all worked without any problems.
Also I tried "Cleaning the .STR Without Re-indexing" method in
Ralph's book and in addition ran dpdiag which reported not warnings.
The database runs fine and there appears to be no problem in
running/using the data.
Is there any way I can track down/deal with the problem is?
Running the latest version of DP (2.6X).
Victor Warner.
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
