Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-74143

Error during upgrade 3.9 to 4.0 on Oracle

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 3.11.7
    • 4.0
    • Questions, Quiz
    • MOODLE_400_STABLE
    • MOODLE_311_STABLE
    • Hide

      Test Oracle upgrade (master and 311)

      1. Install a 39_STABLE with Oracle.
      2. Check out the branch you're testing (e.g. for master, "git checkout master")
      3. Run the upgrade. (Better to do in the CLI as upgrading Oracle is so slow on the browser. "php admin/cli/upgrade.php")
      4. Verify that the process ends without error.

      Test SQL*Server upgrade (optional, master only)

      1. Requirement: This test requires MDL-74138 to be integrated or another error (in auth_lti) will happen.
      2. Install a 39_STABLE with SQL*Server (e.g. if using MDK, "mdk create -n isqlsrv_39 -i -t -v 39 -r users -e sqlsrv")
      3. Upgrade it to master
      4. Verify that the process ends without error.
      Show
      Test Oracle upgrade (master and 311) Install a 39_STABLE with Oracle. Check out the branch you're testing (e.g. for master, " git checkout master ") Run the upgrade. (Better to do in the CLI as upgrading Oracle is so slow on the browser. " php admin/cli/upgrade.php ") Verify that the process ends without error. Test SQL*Server upgrade (optional, master only) Requirement: This test requires MDL-74138 to be integrated or another error (in auth_lti) will happen. Install a 39_STABLE with SQL*Server (e.g. if using MDK, " mdk create -n isqlsrv_39 -i -t -v 39 -r users -e sqlsrv ") Upgrade it to master Verify that the process ends without error.

      To replicate:

      1. Install an oracle site using MOODLE_39_STABLE (integration, weekly, whatever)
      2. Now checkout integration master (4.0 beta) and try to run the upgrade
        Expected: Upgrade completes without errors
        Actual: We see the following error: 

        column "question->idnumber" cannot be modified. Dependency found with index "m_ques_catidn_uix (sys_nc00019$, idnumber)"
        		 
         
        		 
        More information about this error
        		 
         
        		 
        ×Debug info:
        		 
        Error code: ddldependencyerror
        		 
        ×Stack trace:
        		 
        line 734 of /lib/ddl/database_manager.php: ddl_dependency_exception thrown
        		 
        line 566 of /lib/ddl/database_manager.php: call to database_manager->check_field_dependencies()
        		 
        line 3969 of /lib/db/upgrade.php: call to database_manager->drop_field()
        		 
        line 1875 of /lib/upgradelib.php: call to xmldb_main_upgrade()
        		 
        line 519 of /admin/index.php: call to upgrade_core()

      Thanks to ilyatregubov for also confirming this one.

        1. get_indexes_coverage.png
          get_indexes_coverage.png
          217 kB
        2. mssql frontend.png
          mssql frontend.png
          28 kB
        3. mssql upgrade.png
          mssql upgrade.png
          41 kB
        4. oracle frontend.png
          oracle frontend.png
          40 kB
        5. oracle upgrade.png
          oracle upgrade.png
          74 kB
        6. sqlsrv-upgrade-ok.png
          sqlsrv-upgrade-ok.png
          62 kB

            stronk7 Eloy Lafuente (stronk7)
            jaked Jake Dallimore
            Tim Hunt Tim Hunt
            Jun Pataleta Jun Pataleta
            Angelia Dela Cruz Angelia Dela Cruz
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours, 45 minutes
                4h 45m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.