User <dbyy@[EMAIL PROTECTED]
> wrote
news:4bbb8ff8-583b-4858-b2c8-f9e2ed5359dc@[EMAIL PROTECTED]
> Since 2004, more and more applications (PL/SQL and Delphi) in our
> corporation using the tables on Oracle in concurrency to Clipper.
> At the same time, some table size have grown significantly.
> Now we're facing the problem that we have more and more errors on
> "Unique key constraints violation".
> For the non-Clipper applications we implemented "BEFORE_INSERT"
> triggers to populate the next available RECNO sequence via "Select
> max(recno) from <TABLE>".
> On tables with more than 12 million rows this is getting more and more
> time consuming and we have the suspicion that due to the execution
> time for this statement and the simultaneous use of RECNO inside of
> Mediator, we receiving the key constrain violation.
> We know that we could turn of the internal buffering of RECNO in
> Mediator, but this bring down the performance of all Clipper
> applications. And also we considered already the use "NEXTVAL" from
> Sequence for the triggers, But that doesn't solve the problem that
> Mediator has still the internal RECNO sequence.
[..]
There is a possibility to use Oracle triggers for numbering RECNO
field, but it depends on Mediator version. Please let me know
which version you use (better on support@[EMAIL PROTECTED]
).
Regards,
Bozena Potempa
|
