Question3Replies267Views×Close popoverPravin magar (Pravin_M) Infosys Infosys US View ProfileSend Message Pravin_M Member since 2015 8 posts Infosys Posted: February 8, 2016Last activity: May 13, 2016Posted: 8 Feb 2016 2:02 ESTLast activity: 13 May 2016 15:26 EDT Closed Solved RDB call is failingHelloWe are facing issue with the connect SQL/RDB List call. In our application cases are being created using JMS service/MQ Feed. We are making this RDB Call in routing activity. This RDB call is failing certain scenarios Please find below are the some Working and non working scenarios.1. Non Working Scenarios a. When the case is first time get routed to any workbasket (OR when case is updated by Integration user in real time scenario ) Suspecting parameters are not getting set in store procedure,2. Working Scenarios a. When case is move by agent or person to other workbasket. b. above mentioned non working scenario is also working fine if case is created from pega using JMS service rule to post the message in pega.Thanks,Pravin Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 5 years agoPosted: 8 Feb 2016 4:44 EST×Close popoverRajiv Nistala (nistr) PEGA Senior Manager - Engineering Pegasystems IN View ProfileSend Messagenistr PEGA replied to Pravin_MThe categories should have Database.That said, without details on the nature of failure, logs / stracktraces, use case details including the configuration and environment, there isn't much to help here. Kindly provide the same so that the relevant folks can take a look. Posted: 5 years agoPosted: 24 Feb 2016 2:12 EST×Close popoverPravin magar (Pravin_M) Infosys Infosys US View ProfileSend MessagePravin_M Infosys replied to nistrWe are in discussion with pega product support team. SR- A15381 has been raised for the same.As per recent discussion with the team, it has been suggested to change the driver type of both pega rules and DB2 to XA type. Accepted Solution Posted: 4 years agoPosted: 13 May 2016 15:26 EDT×Close popoverVeera Gangababu Gollapalli (Gangababu) PEGA Principal Technical Solutions Engineer PEG IN View ProfileSend MessageGangababu PEGA replied to Pravin_MROOT CAUSEIssue could be related to the driver types for both PegaRules and External databases.RESOLUTIONSuggested user to use XA drivers for both PegaRules and External databases.