What causes a trigger to become disabled?

What causes a trigger to become disabled?

Hello,
How is it possible for a trigger to appear as disabled (in user_triggers) without explicity issuing ALTER TRIGGER ..DISABLE?

We exported the db to a client site, checked for invalid objects (there were none) and now a week later mysteriously proceses have stopped working which we have found is related to triggers being disabled.

Here's what I checked.
>Ran a simple testcase with a trigger that inserts values into specific columns of a table. Dropped one of the columns that the trigger inserts into. The trigger shows as invalid but is still enabled
>Droped a table that the trigger inserts into. The trigger shows as invalid but is still enabled.

I also thought that perhaps the trigger may not have got enabled on import however these processes have been working fine since the import
until just the past day. The import occured over a week ago.

We are 90140 on win 2k

tks for any suggestion

A trigger can become invalid if you alter one of the dependant objects (table, function call in the trigger, etc).

marist89 tks,

invalid i understand, but disabled....that is the question, what could cause the trigget to become 'DISABLED'?

tks


teve

check when the trigger got disabled .

select object_name, , last_ddl_time , timestamp from all_objects where object_type='TRIGGER' ;

if u have applied any patch on the database just check if
system_enabled_trigger=FALSE is set or not ?

do u use materialised views for replication ??

tks prakashs43

check when the trigger got disabled .

select object_name, , last_ddl_time , timestamp from all_objects where object_type='TRIGGER' ;
....dooh, what a rookie mistake, i guess I should have checked that before I renabled the trigger

if u have applied any patch on the database just check if
system_enabled_trigger=FALSE is set or not ?
...no not the case

do u use materialised views for replication ??
>no