1 of 1 people found this helpful
I believe you need at least SEVERITY_ERROR to trigger an incident.
thanks for the reply, well, i dont get the purpose then for the additional severities like warning, even in the interface under incidents you can filter for severity warning for example
I ran into the same issue with an Oracle API query. Using SEVERITY_ERROR still did not raise an incident in Central when an error occured in the Oracle API. After working with support, was told the only way to catch this is by using a DCLEVENT for EVENT_RAISE_PROC_EXIT. I'm not happy with the solution, but it did work after doing this. I coded this to trap error numbers we most commonly saw, and then fall thru to a more generic error message.
OracleQueryGeneric.bdf 2.0 K