Database problem on upgrading from 3.8 to 3.11

Database problem on upgrading from 3.8 to 3.11

by Максим Вейсгейм -
Number of replies: 0

ive made a backup using
pg_dump -U username -h myhost --file=moodle_39.sql moodle
i had repository of moodle 3.8 and had a tack to upgrade it to 3.11, ive  cloned it on local machine and (here is probably where i made mistake) copied 3.11 files on top of it.
Somehow it didnt trigger upgrade interface but blocked access to admin page with errors like this https://pastebin.com/VgfnKXtL so i didnt have the ability to put site in mainenance mode (later i tried to do it using script in admin/cli folder it completed without errors but site still wasnt in maintenance mode)  

I started anew, cleaning repository folder and putting only 3.11 distributive in it, then according to guides copied mod themes and config.php from my old codebase, it triggered upgrade ui, but upgrade couldnt finish cause it didnt have appropried required mod-plugins and themes (cause i copied them from old codebase and they had old version hardcoded in version.php i assume) so i couldnt install them vie ui cause admin page was still filled with errors from pastebin link, so i overwritten old folders with new ones of required mod and themes

it did let me finish upgrade procces via ui, but more errors appeared (https://pastebin.com/LNdx4U07) after nervous googling i came to a conclusion that database migration somehow failed

i checked database integrity using according admin/cli script and got this https://pastebin.com/gKZ6VtR4

i tried using admin/cli/upgrade.php script but it told me that my version is not in need of updating since it checks hardcoded version from version.php and it is 3.11 but i assume my db structure is still in 3.8 state

im considering changing version written in /version.php to my old version and running admin/cli/upgrade.php again, but line with version have comment about not pandering with it manually

Is there any way to fix this problems using any scripts or maybe pandering with them juuuuust a little? i would love to fix this problem without full on reinstall and db restoration, but if there isnt any, then any help will be appriciated

Average of ratings: -