+1 to Howard's suggestion, but ... a catch 22 ... and this is directly related to OVH support.
You could send the .sql output to helpdesk and ask if they would perform the task on your database, but think they will still baulk at that ... shared server means shared DB server and anything of a global nature to settings of the DB server would/might affect *ALL* customers on that shared system.
OVH claims Moodle can be run on their servers ... well, since you are going to 3.3, just how many of the new Moodle additions can a shared server setup support? Will they setup unoconv, LibreOffice, Apache Solr, JRE 1.8 and a listener? (I kinda doubt it.)
So, yes, you might get 3.3 to run with the help of OVH helpdesk, but even if you do, don't expect to be able to use all the features.
Maybe what OVH and other providers should do is have dedicated shared servers just for Moodle customers ... uhhhh, good luck with that.
It would be interesting to see OVH provide the number of customers on shared hosting successfully running 3.3 of Moodle with all features enabled and functioning.
Even if a 'work-around' is found, what of future Moodle updates or upgrades?
Said this before ... will say it again ... think the days of Moodle on shared hosting are drawing to a close.
2 cent opinion ...
'spirit of sharing', Ken