If you are connecting with
jena as the same user ie
dba then this would not be the source of the problem.
I note you seem to have built Virtuoso from the git develop/7 tree back in Feb 2020, with the version of the Jena Provider being
Version 3.0.0 [Build 1.31] whereas the version of the latest provider is
Version 3.0.0 [Build 1.33], thus I would recommend updating you binary and Java components (jena & JDBC) to the latest from develop/7 and retest.
Should the problem persist as indicated previously, the Virtuoso “trace_on()” command can be run to enable server side tracing to the
virtuoso.log file and the query executed via Jena and isql and the log checked to see if Jena might be changing the query in anyway before passing to Virtuoso.