Re: Constraint violation in spite of trigger with sequence
Date: Tue, 2 Feb 2010 11:29:25 -0600
The only ways I know of to avoid a trigger is:
- Disable it.
- Use SQL*Loader in direct mode, which will write blocks directly, bypassing triggers.
It could be that there are multiple before-insert triggers on the table, or an instead-of trigger of a view that shoots data into the table in question; in 9i, I know trigger invocation order is indeterminate, so some other trigger could be superseding the one listed.
On Tue, Feb 2, 2010 at 10:12 AM, Jared Still <jkstill_at_gmail.com> wrote:
> On Tue, Feb 2, 2010 at 2:09 AM, A. Stiebing <stiebing_at_softcontract.de>
>> In spite of we got an trigger with a sequence to update an unique id key
>> insert, we get constraint violations from time to time.
>> Where could the cause be for that?
> 1) By what methods does data get into the table?
> Custom app? SQL Loader? Custom Utilities? Import?
> 2) Please post entire code for the trigger.
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
> Oracle Blog: http://jkstill.blogspot.com
> Home Page: http://jaredstill.com
-- Adam Musch ahmusch_at_gmail.com -- http://www.freelists.org/webpage/oracle-lReceived on Tue Feb 02 2010 - 11:29:25 CST