Hi.

I have installed my application with elevatedb in a dozen of my customers, most of
them with several clients in net, working in file shared mode.

About half of them sometimes gets the error "Elevate Error #100 there is an error in
the metadata for the table XXXXXX (a write operation did not complete and a repair
is required)". This error occurs in tables that are used and mantained by triggers.
I talk with my customers and no power fail, no net fail, only working normally.
After consulting with Tim i change one of them to client/server mode but error persist,
occasionally but persist.

I'm somewhat concerned about this because i don't know how fix it and my customers
are angry with me because they must stop all clients and repair damage table to
continue.

Any idea?

Thank you

What do the triggers look like ?


"Francisco Fernandez" <paco@newtron.es> wrote in message
news:3E60D296-1BF4-4C85-B958-F8DB50CEF441@news.elevatesoft.com...
> Hi.
>
> I have installed my application with elevatedb in a dozen of my customers,
> most of
> them with several clients in net, working in file shared mode.
>
> About half of them sometimes gets the error "Elevate Error #100 there is
> an error in
> the metadata for the table XXXXXX (a write operation did not complete and
> a repair
> is required)". This error occurs in tables that are used and mantained by
> triggers.
> I talk with my customers and no power fail, no net fail, only working
> normally.
> After consulting with Tim i change one of them to client/server mode but
> error persist,
> occasionally but persist.
>
> I'm somewhat concerned about this because i don't know how fix it and my
> customers
> are angry with me because they must stop all clients and repair damage
> table to
> continue.
>
> Any idea?
>
> Thank you
>

Francisco,

<< After consulting with Tim i change one of them to client/server mode but
error persist, occasionally but persist. >>

Could you send me a copy of the database that you're using ?  It doesn't
need to have data, I just need the database catalog (edbdatabase.edbcat
file).

--
Tim Young
Elevate Software
www.elevatesoft.com

Francisco,

BTW, did you check to see if they are using any type of anti-virus or hot
backup software that can interfere with the I/O of ElevateDB ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi.

My customers don't using backup software but most of them are using diferents anti-virus software but, how can i
know if the problem is the anti-virus software?

I send you database to the binary post. The trigger that was working in the most of problems
is "InsertaVentasLineas" of table "VentasLineas" and the table that broke most of times is "Existencias".

Regards.

Francisco,

<< My customers don't using backup software but most of them are using
diferents anti-virus software but, how can i know if the problem is the
anti-virus software? >>

The best way is to make sure that any AV software is *not* scanning the EDB
database catalog and table files.  If it is, then it can interfere with the
normal operation of the database.

<< I send you database to the binary post. The trigger that was working in
the most of problems is "InsertaVentasLineas" of table "VentasLineas" and
the table that broke most of times is "Existencias". >>

Well, for starters I would change these EXCEPTION blocks in your triggers
from this:

    EXCEPTION
      ROLLBACK;
    END;

to this:

    EXCEPTION
      ROLLBACK;
      RAISE;
    END;

That will at least give us some information regarding whether there are any
I/O exceptions that are possibly causing a problem.

--
Tim Young
Elevate Software
www.elevatesoft.com

Ok

I'll try it

Thank you