AnsweredAssumed Answered

Trigger exception not caught by Clarity

Question asked by daniele.f on Sep 19, 2011
Latest reply on Sep 20, 2011 by Dave
Hi,
I've done a trigger that raise an exception if the resource date range is not inside of project date range.
The problem is that the exception is not caught by Clarty:

the trigger raise the exception with the code 20065 and in the file "messages.properties" I have inserted thi line:

odf-pmd.20065=Resource allocation date is not correct: please check the resource range date is in of project range date

but when the error occurred I get this error:

[CA Clarity][Oracle JDBC Driver][Oracle]ORA-20065: Resource allocation date is not correct: please check the resource range date is in of project range date - ORA-06512: at "CLADWM.Z_CHECK_TEAM_DATE", line 10 ORA-04088: error during execution of trigger 'CLADWM.Z_CHECK_TEAM_DATE'

The error with the code ORA-20065 is the custom exception raise by me.
The error ORA-06512 at line 10 (in the trigger corresponding at the BEGIN)
The error ORA-04088 indicates that a runtime error occurred during execution of a trigger

I've checked the trigger with the debug but no error found.
In the log file I've found this message:
   WARN  2011-09-19 11:51:27,876 [http-80-2] niku.union (admin:5033304__-5e612b98:projmgr.staffMemberPropertiesPost) [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20065:  Resource allocation date is not correct: please check the resource range date is in of project range date - 
   ORA-06512: at "CLADWM.Z_CHECK_TEAM_DATE", line 11
   ORA-04088: error during execution of trigger 'CLADWM.Z_CHECK_TEAM_DATE'
      was not found in file: messages.properties
Clarity don't find the message error in the file "messages.properties" with code 20065.
I think that Clarity don't catch the error message.


Thanks
Daniele

Outcomes