dbTalk Databases Forums  

Trigger Invalid State

comp.databases.oracle.misc comp.databases.oracle.misc


Discuss Trigger Invalid State in the comp.databases.oracle.misc forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
rzaleski
 
Posts: n/a

Default Trigger Invalid State - 06-18-2008 , 07:49 PM






What would cause a trigger to have an invalid state? Do triggers
become invalid if you alter a table (but do not add/drop any columns
that trigger references)? Do triggers become invalid if you add an
index to a table?

Reply With Quote
  #2  
Old   
Mark D Powell
 
Posts: n/a

Default Re: Trigger Invalid State - 06-18-2008 , 08:15 PM






On Jun 18, 8:49*pm, rzaleski <rzale... (AT) gmail (DOT) com> wrote:
Quote:
What would cause a trigger to have an invalid state? *Do triggers
become invalid if you alter a table (but do not add/drop any columns
that trigger references)? *Do triggers become invalid if you add an
index to a table?
For table triggers adding an index to a table referenced by the
trigger has no effect on the trigger state. Alteringa table
referenced by the trigger on the other hand is likely to require
Oracle to re-compile the trigger to ensure the code is valid prior to
11g and Oracle's more advanced dependency tracking.

Check DBA_DEPENDENCIES before altering any table to see what dependent
objects are going to be affected.

Loss of object privileges can cause a trigger to become INVALID when
the trigger code references tables owned by a different user than the
trigger owner.

HTH -- Mark D Powell --





Reply With Quote
  #3  
Old   
Mark D Powell
 
Posts: n/a

Default Re: Trigger Invalid State - 06-18-2008 , 08:15 PM



On Jun 18, 8:49*pm, rzaleski <rzale... (AT) gmail (DOT) com> wrote:
Quote:
What would cause a trigger to have an invalid state? *Do triggers
become invalid if you alter a table (but do not add/drop any columns
that trigger references)? *Do triggers become invalid if you add an
index to a table?
For table triggers adding an index to a table referenced by the
trigger has no effect on the trigger state. Alteringa table
referenced by the trigger on the other hand is likely to require
Oracle to re-compile the trigger to ensure the code is valid prior to
11g and Oracle's more advanced dependency tracking.

Check DBA_DEPENDENCIES before altering any table to see what dependent
objects are going to be affected.

Loss of object privileges can cause a trigger to become INVALID when
the trigger code references tables owned by a different user than the
trigger owner.

HTH -- Mark D Powell --





Reply With Quote
  #4  
Old   
Mark D Powell
 
Posts: n/a

Default Re: Trigger Invalid State - 06-18-2008 , 08:15 PM



On Jun 18, 8:49*pm, rzaleski <rzale... (AT) gmail (DOT) com> wrote:
Quote:
What would cause a trigger to have an invalid state? *Do triggers
become invalid if you alter a table (but do not add/drop any columns
that trigger references)? *Do triggers become invalid if you add an
index to a table?
For table triggers adding an index to a table referenced by the
trigger has no effect on the trigger state. Alteringa table
referenced by the trigger on the other hand is likely to require
Oracle to re-compile the trigger to ensure the code is valid prior to
11g and Oracle's more advanced dependency tracking.

Check DBA_DEPENDENCIES before altering any table to see what dependent
objects are going to be affected.

Loss of object privileges can cause a trigger to become INVALID when
the trigger code references tables owned by a different user than the
trigger owner.

HTH -- Mark D Powell --





Reply With Quote
  #5  
Old   
Mark D Powell
 
Posts: n/a

Default Re: Trigger Invalid State - 06-18-2008 , 08:15 PM



On Jun 18, 8:49*pm, rzaleski <rzale... (AT) gmail (DOT) com> wrote:
Quote:
What would cause a trigger to have an invalid state? *Do triggers
become invalid if you alter a table (but do not add/drop any columns
that trigger references)? *Do triggers become invalid if you add an
index to a table?
For table triggers adding an index to a table referenced by the
trigger has no effect on the trigger state. Alteringa table
referenced by the trigger on the other hand is likely to require
Oracle to re-compile the trigger to ensure the code is valid prior to
11g and Oracle's more advanced dependency tracking.

Check DBA_DEPENDENCIES before altering any table to see what dependent
objects are going to be affected.

Loss of object privileges can cause a trigger to become INVALID when
the trigger code references tables owned by a different user than the
trigger owner.

HTH -- Mark D Powell --





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.