Re: Constraint violation in spite of trigger with sequence
- From: Adam Musch <ahmusch@xxxxxxxxx>
- To: jkstill@xxxxxxxxx
- Date: Tue, 2 Feb 2010 11:29:25 -0600
The only ways I know of to avoid a trigger is:
1. Disable it.
2. 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@xxxxxxxxx> wrote:
> On Tue, Feb 2, 2010 at 2:09 AM, A. Stiebing <stiebing@xxxxxxxxxxxxxxx>
> wrote:
>>
>>
>> In spite of we got an trigger with a sequence to update an unique id key
>> on
>> 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@xxxxxxxxx
--
//www.freelists.org/webpage/oracle-l
Other related posts:
