SOLVED Back-end System JDBC statement execute ignore-list

[dsh]

Hi,

I was wondering whether it is possible to configure specific SQL statement ignore patterns (exceptions) for backend notifications?
We have our JDBC statement execute threshold set to 30s. Some of the statements run on the datasource take longer than 30s occasionally (i.e. AD group to application role mapping). We’d still like to retain the ability to catch long running statements on the same datasource for the server, so setting the pool exception doesn’t seem a viable option.

We were thinking the server-specific exception list can be configured with a %like patter for our SQL procedure call:
%JOB.PAK_JOB_USER_GRANTS_AD.SYNC_USER_ROLES%
in order to ignore notification about this specific query, but it doesn’t look like such option exists?

[mustafa.sensoy-wlsdmteam]

Hi @dsh,

As you point, WLSDM supports only the pool (data source) for the exception.
But, adding a statement exception mechanism could be a nice upgrade, we will consider it.

Additionally, you can take a look at the WL-OPC product.
WL-OPC may offer a solution to your requirement by writing a notification delivery rule.

https://wlsdm.com/download

[mustafa.sensoy-wlsdmteam]

Hi @dsh,

As you point, WLSDM supports only the pool (data source) for the exception.
But, adding a statement exception mechanism could be a nice upgrade, we will consider it.

Additionally, you can take a look at the WL-OPC product.
WL-OPC may offer a solution to your requirement by writing a notification delivery rule.

https://wlsdm.com/download

[dsh]

Thank you for the prompt reply and for consideration.
In the meantime, as you suggest, ww will have a look at WL-OPC.

[wlsdmsupport]

@dsh said:

Hi,

I was wondering whether it is possible to configure specific SQL statement ignore patterns (exceptions) for backend notifications?
We have our JDBC statement execute threshold set to 30s. Some of the statements run on the datasource take longer than 30s occasionally (i.e. AD group to application role mapping). We’d still like to retain the ability to catch long running statements on the same datasource for the server, so setting the pool exception doesn’t seem a viable option.

We were thinking the server-specific exception list can be configured with a %like patter for our SQL procedure call:
%JOB.PAK_JOB_USER_GRANTS_AD.SYNC_USER_ROLES%
in order to ignore notification about this specific query, but it doesn’t look like such option exists?

Hi,
We have implemented this feature in our latest version which is v3.9.1.
Thank you for the contribution. For your information.
Regards…

Screen Capture

[dsh]

Oh, that’s lovely, thank you very much!
Have installed 3.9.1 in out sandbox environment after receiving the newsletter last week, will give this a shot right away!