Hello Team…
This is Arun…!!

So, i am facing this issue while turning to enable in the JDBC pooling notification.
[ART.116.3038] Adapter Runtime (Notification): Error in Notification Callback:enableCallback notification myTraining.adaptersNotification.notificationUpdate:continentsData. [ADA.1.114] The database objects for “myTraining.adaptersNotification.notificationUpdate:continentsData” notification already exist. You can delete the objects and try enabling the notification again. To delete the existing database objects use the “pub.pollingNotificationUtils:dropDatabaseObjects” service.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/7053bd0f8c77af2a1d8b443d0d9546540665e42d_2_1035x546.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/7053bd0f8c77af2a1d8b443d0d9546540665e42d.png 2x" data-dominant-color="D8E4EB">

image1366×721 61.3 KB

webMethods version 10.11

can you please help me with this issue
Regards…

Did you follow the steps given in error itself, its likely that the user you are using doesnt have delete privilige. Please go to database and delete trigger and buffer table manually.

Hi Arun,

usually a polling notification consists of three database objects (check the server.log and/or error log for the exact names of them):

• BufferTable
• Trigger
• Sequence

Remember do delete all of them if they do not get deleted automatically when disabling the Notification in the JDBC Adapter UI.

See IS Built-In-Services Reference (section ART package) for further informations about the mentioned service.

Regards,
Holger

This is one of the reasons I usually advocate for using “Basic Notifications” and not the insert, update, delete specific notifications.

While it seems convenient for the notification to fully manage the DB objects, there are constraints to consider: Search the forums for “basic notification” to see the discussions in the past about the options and pros/cons. I would strongly suggest always using basic notifications.