You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There we go - it's the scc and it even says what it does: Skipping Compatibility check with framework version, expecting the latest version to be installed in database
Two issues:
First of all, it assumes the wrong latest version
Second, even when assuming we should somehow still try to get the actual version and state this in the logs.
Activity
pesse commentedon Mar 29, 2019
Can you provide the output of
utplsql info user/pw@connectstring?This is very strange, because we get the right output for all versions tested against:
https://travis-ci.org/utPLSQL/utPLSQL-cli/builds/512875014
jgebal commentedon Mar 29, 2019
This is what I get when I run locally.
jgebal commentedon Mar 29, 2019
It seems to be related to
-sccoption.When I run without scc, it works fine.
pesse commentedon Mar 29, 2019
There we go - it's the
sccand it even says what it does:Skipping Compatibility check with framework version, expecting the latest version to be installed in databaseTwo issues:
First of all, it assumes the wrong latest version
Second, even when assuming we should somehow still try to get the actual version and state this in the logs.
Thanks for the finding :)
Enable DBMS-Output and use some new Compatibility-Proxy functions