some times not going to db write trigger

Posted by shireeshn on 29-Jan-2010 00:31

Hi all,

     I have seen this rarely at customer system. Normally when we update any field it goes to db-trigger (create, delete or write).

      Now at one customer only it is not going to Db-trigger.

     

      Does any one know in which case this happens, any one can suggest me on this, what can be the reasons?

Note:-     NO OVERRIDE IS used.

    

Regards

Shireesh

All Replies

Posted by Admin on 29-Jan-2010 01:56

Have you checked the logs.  Perhaps the propath or the compiled procedure out of date.

Posted by shireeshn on 29-Jan-2010 02:27

we have just moved from 9.1D to 10.2A, from that time the prob exits.

"propath or the compiled procedure out of date" how can we know this out of date or not.

Posted by Admin on 29-Jan-2010 15:01

That's why I was suggesting checking your logs to see if there were any messages.  If for example you had recompiled after the upgrade or the client hasn't got the latest compile then the log will have an error message indicating the incorrect version.  Or if your propath is incorrect then there will be a message indicating it can't locate the procedure.

This thread is closed