Re: Invalid Triggers

In article <fongdaEIw18C.DFp_at_netcom.com>,   fongda_at_netcom.com wrote:

> We've got instances in our database where a trigger has a status of
> enabled in user_triggers and has a status of invalid in
> user_objects...has anyone run into this before?

[snip]

Don't worry about the INVALID status.
It does NOT mean that the trigger won't run.

Oracle keeps track of which database objects a stored procedure (or trigger) refrences. When any of those objects is ALTERed, the stored proc referencing them needs to be re-compiled. Oracle defers this compilation until an attempt is made to execute the refering procedure. The INVALID status is simply Oracle's way of noting that the db server needs to re-compile the proc before executing it.

The trigger will only need re-compiling, and therefore will only be marked INVALID if one of the objects it references is ALTERed. Your proc is marked INVALID because it references an ALTERed table. You did not ALTER your proc, so the trigger does not need to be re-compiled and is NOT marked INVALID. The trigger should fire like normal and when it calls the proc the proc will re-compile (and, hopefully, be VALID). If the procedure should fail to re-compile, the trigger will fail on the call, unless it handles the failed call with an EXCEPTION.

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet