I had the exact same problem during the upgrade of a Solution Manager instance running on MaxDB.First, to diagnose the problem, try to execute the following command with the user that is executing the upgrade:dbmcli -U c -USQL DEFAULT sql_execute SEL...