Hi @mujtabaomar
So this seems like a known bug that can be tracked here [DHIS2-8782] - Jira.
The bug is fixed in all the development branches 2.34dev , 2.35dev and 2.36dev. Which means the fixes will be available in the next patch release of all of these versions.
Until then, it is possible to workaround around this issue. You will have to delete an entry in the systemsetting table for the upgrade to happen successfully. You can execute this statement
delete from systemsetting where name = 'keySmsSetting'
in your 2.33.6 db, and then try to upgrade it by deploying 2.35.0 and it should workaround this error. But note that the existing sms configuration will be deleted and you will have to recreate the sms configuration after the upgrade.
I ran the script given for 2.35.0
Also please do not run any scripts manually, the application war file is supposed to do the migrations automatically and track the changes on deployment. Manual changes will make the db inconsistent or corrupted.
Some details of the same issue was discussed here a while ago Use caution if upgrading to 2.34 while using SMS Configuration