Preferred way for PLSQL analysis initiated by Jenkins

This is the same stacktrace as reported in another thread.
It’s due to a NOT IN query where the subquery has redundant parentheses, for example:

SELECT c1 FROM t1
WHERE c1 NOT IN ((SELECT c2 FROM t2));

We have an open ticket about it and we should definitely fix it.

In the meantime, you can either:

  • remove the redundant parentheses in your code
  • or disable the rule S3641 in your quality profile
  • or exclude the file from your analysis using sonar.exclusions