Hello Siva. Yes, others have reported this. Theja reproduced it here, and Rainiel, Lucas, Federica, Suhasini and others reported similar failures in this thread. Rainiel also shared that SailPoint Support attributed it to a recent update and was working on a fix.
This looks like a validation regression. SailPoint’s official JDBC Provision Rule example still uses PreparedStatement and executeUpdate() for INSERT, UPDATE and DELETE, and I do not see PreparedStatement, executeUpdate() or executeQuery() in the published Rule Code Restrictions. Since the API also rejects the rule, this is unlikely to be a VS Code issue. I would leave existing deployed rules unchanged and verify provisioning still works.
For new implementations, Vikas’s suggestion is a supported alternative. The VA-based JDBC connector supports SQL queries or stored procedures without a rule. However, it is not a direct replacement for custom logic, and Update Account requires Attribute Sync for the affected attributes.
I have not found a verified workaround within the rule. Since you already have a Support case, I would share these references and ask for the fix and rollout status.
