How to trace the queries and parameters - external database
The tracer has options to trace any DB queries which interact with the PegaRules Data base, do we have a way to check the interactions/data with other databases?
The above link explain the tracer options.
***Edited by Moderator Marissa to update Platform Capability***
Nat West Group
IN
The question popped up when there was an issue when a Pega Marketing strategy tries to insert a record into Batchout table . The actual issue was a String not a date error .
There are records inserted into the batch out table but due to this exception campaign run has failed and we are not able to trace which record may have caused this error since the tracer is not displaying the insert queries into the batch out table.
Hope the issue is clear now. Can you help us with this?
Pegasystems Inc.
US
There is a troubleshooting video for failed campaigns and the example scenario deals directly with the issue you're describing.
https://community.pega.com/video-library/support-guide-debugging-failed-campaign-execution
Please note each campaign creates and uses a dedicated batchout table that is named for the campaign.
Pegasystems Inc.
US
This may need an enhancement. It is possible that Pega Marketing doesn't use the standard API to execute these SQLs and thus they don't show up in Tracer. Or is this run by a Batch requestor that needs to be Traced instead of the user session?
Nat West Group
IN
Can you please check and confirm if its run by a Batch requestor? if so when and how the trace has to be started during the campaign schedule.