@jbrost @apenning Actually I am the only Admin working on the environment. I did not run the script before, at least I do not remember 
I wasn’t even aware an update was available. I just noticed that IcingaDB printet the warning that my database has schema “4” instead of expected “5”. Then I ran the script which caused the error message. I am sorry I can not tell you how my database got into this state.