Question
Accenture
IN
Last activity: 13 Apr 2018 10:27 EDT
DB Connection Pool Failure
Hello,
We see below error in our log file. Appreciate if you can help us understand the reason for this and its resolution.
Not returning connection 7 for database "pegadata" to the pool as it previously encountered the following error
User ID: uat.orguserone@gmail.com
Last SQL: DELETE FROM PEGADATA.pr_CAAS_Data_AssignedOrg WHERE OfficerProfileID=? ;
java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
PFA for stack trace from log file for details.
Pegasystems Inc.
IN
Hi There,
I guess you would be using RDB methods to manipulate data in the DB.
Somehow I think while writing the query you may have included ";" at the end for connect-sql rule.
Regards,
Ujjwal
Pegasystems Inc.
IN
Hi Satish,
Thanks for posting on PSC.
If my assumption is correct and as mentioned by my colleague as well, you're using this syntax in the SQL Connect rule(RDB methods).
You shouldn't have ";" in the ending.
Syntax for example:-
DELETE FROM {Table:<YourTableName>} WHERE <PropertyNameToBeComparedWith> = <Key>
Please share your exact usecase, if this isn't the scenario and issue didn't get resolve.
Regards,
Asif
Accenture
IN
Thanks for the response Asif.
As identified by you above, we are using RDB methods and using "; " as well at the end of the query. This query was working in dev where SQL Server is the data base but not working in higher env where Oracle is being used as DB server.
I see ; being used in OOTB connect SQL rules as well. Ex: PegaSample-Integration-Data-StockTrader-Holding • createHolding • SQL Pega-LP-Integration:07-10-21 . However there are few OOTB rules as well where ; is not being used.
Can you help me understand when to use ; in Connect-SQL rules of Pega.
Pegasystems Inc.
IN
Hi @LadeSatishKumar,
I am not sure but are you able to see any difference in the SQL generated in this case and how come query generated from the application is database specific. I'll research more and update you.
Accepted Solution
Accenture
IN
Hi Asif,
My issue got resolved after removing ; at the end of the query. Now it is working for both SQL and Oracle DB servers. Earlier it was working only for SQL when ; is at the end of query.