[VAPP] XML Load Error

[Ruslan Zasukhin]

on 2/8/04 2:50 PM, Martin Kloss at martin.kloss at gmx.de wrote:

Hi Martin,

> I just did a XML Dump / Load from VAPP to repair a 700MB
> database, which had several corrupt records. I don't know how
> on earth these records got corrupted, but the diagnose report
> said that a lot of text blobs had orphaned segments and so on.
> The result was that the text got displayed as garbage, not very
> nice and even deleting the records and creating new records
> didn't help,. because the binary space seems to get recycled.
> 
> So after my client freaked and shouted and said very bad things
> about valentina, I'm now in the process of trying to repair the
> database by doing an XML dump and load and then re-inserting
> 10.000 pictures, because it seems that there is no other way
> to repair this database :-(

ops

> Anyway, the XML dump took only about 15 minutes on a dual
> cpu., 1GB RAM, OS X 10.3.2 machine with VAPP. It worked
> fine and produced a gigantic XML file. Subsequently, I tried to
> load the XML file, which took the whole night. This morning
> VAPP showed an error about a line in the XML file being
> "not well formed" (position 0). How can that be?

I have see ... One reason of this:

1) text contains some characters that XML parser do not understand.


> I don't have another night to load the XML file and I don't
> know how to fix the database now. How can a XML file that
> has been generated by VAPP cause an error when being
> read again with VAPP? I'm very frustrated, time is running
> away, my client is pissed and the database is still broken...

To make you client COOL, please tell him 2 things

1) I know EXACTLY 100% that even BIG DBMS that have
        -- transactions,
        -- logs,
        -- recovery system

Also can broke things.
Just not so far one of our developer have great dancing with Sybase,
He work in local bank.

2) IF your customer have SO IMPORTANT data,
    he MUST to use EVERY DAY or even EVERY HOUR backup.

Without back up -- SORRY. HIS MISTAKE.


-------
According to how recover.

1) you can try open that file in editor and go to that bad formed line.
Most probably you will see some garbage on that line, and can try fix it.
But that also will follow by LONG TIME XML parsing.
And who know may be exist other bad place.


2) you can try next way:

* write small lingo project that will open his bad db,
* which will create empty tables (or you can truncate XML file self
    to get empty structure of tables from it)

* now for each table
    for each record
         do COPY of each field
          and add record.

If you meet some bad record, then skip it.
Question is how to recognize bad record...
In any case, such procedure must give you new fresh db with data,
Without orphan segments.


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------