|[CDO] Diagnostic/Reparation tool [message #1001705]
||Thu, 17 January 2013 03:54
| Christophe MOINE
Registered: February 2012
We have clients' DB that are corrupted, for exemple (in case of multiple refs, and default db mapping):
- The table tableA_myref_list have index no more starting at zero
- The number of items referenced in the tableA_myref_list table does not match the size specified in the "myref" column of tableA
Of course, it makes insiduous problems in the runtime that are quite difficult to track. So far we try try fix the client DB manually, but it would be great to have to tool that repair the Database more or less automatically: has someone ever worked on something like this ?
Thank you in advance,
|Re: [CDO] Diagnostic/Reparation tool [message #1002194 is a reply to message #1001868]
||Fri, 18 January 2013 01:35
| Eike Stepper
Registered: July 2009
Am 17.01.2013 14:32, schrieb Christophe MOINE:|
> Can we customize the isolation level at CDO level ?
No, I don't think so. Maybe it's part of the data source URL? I *believe* that's normally part of the configuration of
the external DB system, but I'm not an expert. And I didn't say that this is likely the cause.
> Just to be sure: if a request something like select min(cdo_idx) from tableA_ref_list where cdo_source=.... Does it
> necessarily return zero (or no row of course) ? If so, we have plenty of theses :(
I don't know what you mean here.
One thing is clear: we update the element rows and the count value in the other table within the same JDBC transaction.
With an adequate transaction isolation level other connections shouldn't ever see intermediate, inconsistent states. As
you say, most DB-based systems have plenty of these multi-table updates and wouldn't work at all if this fundamental
guarantee wasn't there.
Powered by FUDForum
. Page generated in 0.02472 seconds