{"id":5640,"date":"2026-06-04T02:57:15","date_gmt":"2026-06-04T02:57:15","guid":{"rendered":"https:\/\/www.cmsgalaxy.com\/blog\/?p=5640"},"modified":"2026-06-04T02:57:15","modified_gmt":"2026-06-04T02:57:15","slug":"moodle-how-to-fix-moodle-cant-find-data-record-in-database-error-in-enrolment-methods-after-deleting-linked-courses","status":"publish","type":"post","link":"https:\/\/www.cmsgalaxy.com\/blog\/moodle-how-to-fix-moodle-cant-find-data-record-in-database-error-in-enrolment-methods-after-deleting-linked-courses\/","title":{"rendered":"Moodle: How to Fix Moodle \u201cCan\u2019t Find Data Record in Database\u201d Error in Enrolment Methods After Deleting Linked Courses"},"content":{"rendered":"\n

<\/p>\n\n\n\n

Managing enrolments in Moodle is usually simple when everything is cleanly configured. But sometimes, after deleting old courses or changing the enrolment structure, Moodle may suddenly start showing this error when opening a course enrolment page:<\/p>\n\n\n\n

Can't find data record in database.\n<\/code><\/pre>\n\n\n\n
This commonly happens when you go to:<\/p>\n\n\n\n
Course \u2192 Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
If this error appears only for some courses, there is a strong possibility that those courses still contain broken enrolment references from old Course meta link<\/strong> enrolment methods.<\/p>\n\n\n\n
This tutorial explains why this happens, how to identify the broken records safely, and how to fix the issue properly using Moodle\u2019s own API instead of directly deleting database rows.<\/p>\n\n\n\n
\n\n\n\n
Understanding the Problem<\/h1>\n\n\n\n
In Moodle, there are different enrolment methods. Two commonly confused methods are:<\/p>\n\n\n\n
Course meta link\nCohort sync\n<\/code><\/pre>\n\n\n\n
They sound similar because both can automatically enrol users, but they work differently.<\/p>\n\n\n\n
Course Meta Link<\/h2>\n\n\n\n
A Course meta link<\/strong> enrolment method allows users enrolled in one course to be automatically enrolled into another course.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
Course A users \u2192 Course meta link \u2192 Course B\n<\/code><\/pre>\n\n\n\n
In this setup, Course A is the source course. Course B depends on Course A for enrolments.<\/p>\n\n\n\n
This method is useful when you want one course to act as a master enrolment source for one or more other courses.<\/p>\n\n\n\n
Cohort Sync<\/h2>\n\n\n\n
A Cohort sync<\/strong> enrolment method allows users from a Moodle cohort to be automatically enrolled into a course.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
Cohort \u2192 Cohort sync \u2192 Course B\n<\/code><\/pre>\n\n\n\n
This is usually better when you want to manage users centrally from one group and attach that group directly to multiple courses.<\/p>\n\n\n\n
For large Moodle setups with many courses, Cohort sync is usually cleaner than creating one course just to act as an enrolment source for other courses.<\/p>\n\n\n\n
\n\n\n\n
Why the Error Happens<\/h1>\n\n\n\n
Suppose earlier you had this structure:<\/p>\n\n\n\n
Master Course \u2192 Course meta link \u2192 Course 1\nMaster Course \u2192 Course meta link \u2192 Course 2\nMaster Course \u2192 Course meta link \u2192 Course 3\n<\/code><\/pre>\n\n\n\n
Later, you deleted the old Master Course<\/strong> because you decided to use cohorts directly.<\/p>\n\n\n\n
Now Moodle may still have some old meta<\/code> enrolment records inside the affected courses. These records may still point to the deleted source course.<\/p>\n\n\n\n
So when Moodle opens:<\/p>\n\n\n\n
Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
it tries to load the old linked source course.<\/p>\n\n\n\n
But that source course no longer exists.<\/p>\n\n\n\n
So Moodle throws:<\/p>\n\n\n\n
Can't find data record in database.\n<\/code><\/pre>\n\n\n\n
This is not usually a permission issue. It is normally a broken reference issue.<\/p>\n\n\n\n
\n\n\n\n
Most Likely Cause<\/h1>\n\n\n\n
The most likely cause is an orphaned Course meta link<\/strong> record in the Moodle enrol<\/code> table.<\/p>\n\n\n\n
In Moodle, enrolment methods are stored in the enrolment table. For Course meta link enrolment, Moodle stores the linked source course ID in the customint1<\/code> field.<\/p>\n\n\n\n
So if the old source course was deleted, you may have a record like this:<\/p>\n\n\n\n
enrol = meta\ncustomint1 = deleted source course ID\n<\/code><\/pre>\n\n\n\n
That means Moodle still thinks the course is linked to another course, but the linked course no longer exists.<\/p>\n\n\n\n
\n\n\n\n
Before You Start<\/h1>\n\n\n\n
Do not directly delete database records without a backup.<\/p>\n\n\n\n
This fix touches enrolment records, so you should first:<\/p>\n\n\n\n
    \n
  1. Take a full database backup.<\/li>\n\n\n\n
  2. Identify the broken records.<\/li>\n\n\n\n
  3. Remove them using Moodle\u2019s enrolment API.<\/li>\n\n\n\n
  4. Clear cache.<\/li>\n\n\n\n
  5. Run cron.<\/li>\n\n\n\n
  6. Recheck the affected courses.<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n
    Step 1: Identify Broken Course Meta Links<\/h1>\n\n\n\n
    Log in to your Moodle database and run the following SQL query.<\/p>\n\n\n\n
    Replace mdl_<\/code> with your actual Moodle table prefix if your Moodle installation uses a different prefix.<\/p>\n\n\n\n
    SELECT \n    e.id AS enrol_instance_id,\n    e.courseid AS target_course_id,\n    target.shortname AS target_shortname,\n    target.fullname AS target_course_name,\n    e.customint1 AS missing_source_course_id\nFROM mdl_enrol e\nJOIN mdl_course target ON target.id = e.courseid\nLEFT JOIN mdl_course source ON source.id = e.customint1\nWHERE e.enrol = 'meta'\nAND source.id IS NULL;\n<\/code><\/pre>\n\n\n\n
    This query checks all Course meta link enrolment methods and finds records where the source course no longer exists.<\/p>\n\n\n\n
    If the query returns rows, those are broken meta enrolment records.<\/p>\n\n\n\n
    Example output:<\/p>\n\n\n\n
    enrol_instance_id | target_course_id | target_shortname | target_course_name | missing_source_course_id\n101               | 25               | linux-basic       | Linux Basic Course | 7\n102               | 26               | devops-basic      | DevOps Basic Course | 7\n<\/code><\/pre>\n\n\n\n
    Meaning:<\/p>\n\n\n\n
    target_course_id = course where the enrolment method page may be breaking\nmissing_source_course_id = deleted old course that was previously linked\n<\/code><\/pre>\n\n\n\n
    In this example, course ID 7<\/code> was deleted, but courses 25<\/code> and 26<\/code> still have meta enrolment records pointing to it.<\/p>\n\n\n\n
    \n\n\n\n
    Step 2: Take a Database Backup<\/h1>\n\n\n\n
    Before making any change, take a Moodle database backup.<\/p>\n\n\n\n
    For MySQL or MariaDB:<\/p>\n\n\n\n
    mysqldump -u DBUSER -p DBNAME > moodle_before_fix_broken_meta_links.sql\n<\/code><\/pre>\n\n\n\n
    Example:<\/p>\n\n\n\n
    mysqldump -u moodleuser -p moodledb > moodle_before_fix_broken_meta_links.sql\n<\/code><\/pre>\n\n\n\n
    For large production Moodle sites, also confirm that you have a proper server backup or snapshot.<\/p>\n\n\n\n
    Do not skip this step. Enrolment records affect user access to courses.<\/p>\n\n\n\n
    \n\n\n\n
    Step 3: Create a Moodle CLI Script to Remove Broken Meta Links<\/h1>\n\n\n\n
    The safest way is to remove the broken enrolment instances using Moodle\u2019s API.<\/p>\n\n\n\n
    Do not simply run a DELETE FROM mdl_enrol<\/code> query unless you fully understand all related records. Moodle enrolment methods may have associated user enrolments, roles, events, and plugin-level cleanup logic.<\/p>\n\n\n\n
    Go to your Moodle root directory and create a new CLI script:<\/p>\n\n\n\n
    nano admin\/cli\/fix_broken_meta_links.php\n<\/code><\/pre>\n\n\n\n
    Paste the following code:<\/p>\n\n\n\n
    <?php\ndefine('CLI_SCRIPT', true);\n\nrequire(__DIR__ . '\/..\/..\/config.php');\nrequire_once($CFG->libdir . '\/clilib.php');\nrequire_once($CFG->libdir . '\/enrollib.php');\n\nglobal $DB;\n\n$plugin = enrol_get_plugin('meta');\n\nif (!$plugin) {\n    cli_error('Course meta link enrolment plugin not found.');\n}\n\n$sql = \"\n    SELECT e.*\n      FROM {enrol} e\n LEFT JOIN {course} source ON source.id = e.customint1\n     WHERE e.enrol = :enrol\n       AND source.id IS NULL\n\";\n\n$instances = $DB->get_records_sql($sql, ['enrol' => 'meta']);\n\nif (!$instances) {\n    mtrace('No broken course meta link enrolment instances found.');\n    exit(0);\n}\n\nmtrace('Found ' . count($instances) . ' broken course meta link instance(s).');\n\nforeach ($instances as $instance) {\n    mtrace(\n        'Deleting broken meta enrol instance ID ' . $instance->id .\n        ' from target course ID ' . $instance->courseid .\n        ', missing source course ID ' . $instance->customint1\n    );\n\n    $plugin->delete_instance($instance);\n}\n\nmtrace('Done.');\n<\/code><\/pre>\n\n\n\n
    Save and exit.<\/p>\n\n\n\n
    This script does the following:<\/p>\n\n\n\n
    Finds all Course meta link enrolment instances\nChecks whether the linked source course exists\nFinds records where the source course is missing\nDeletes the broken enrolment instance using Moodle's enrolment API\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Step 4: Run the Script<\/h1>\n\n\n\n
    From your Moodle root directory, run:<\/p>\n\n\n\n
    php admin\/cli\/fix_broken_meta_links.php\n<\/code><\/pre>\n\n\n\n
    Example output:<\/p>\n\n\n\n
    Found 3 broken course meta link instance(s).\nDeleting broken meta enrol instance ID 101 from target course ID 25, missing source course ID 7\nDeleting broken meta enrol instance ID 102 from target course ID 26, missing source course ID 7\nDeleting broken meta enrol instance ID 103 from target course ID 27, missing source course ID 7\nDone.\n<\/code><\/pre>\n\n\n\n
    If there are no broken records, you may see:<\/p>\n\n\n\n
    No broken course meta link enrolment instances found.\n<\/code><\/pre>\n\n\n\n
    In that case, the issue may be related to another broken enrolment method, missing context record, deleted role, or third-party enrolment plugin.<\/p>\n\n\n\n
    \n\n\n\n
    Step 5: Purge Moodle Cache<\/h1>\n\n\n\n
    After deleting broken enrolment instances, purge Moodle cache.<\/p>\n\n\n\n
    Run:<\/p>\n\n\n\n
    php admin\/cli\/purge_caches.php\n<\/code><\/pre>\n\n\n\n
    This ensures Moodle does not continue using old cached enrolment or course data.<\/p>\n\n\n\n
    \n\n\n\n
    Step 6: Run Moodle Cron<\/h1>\n\n\n\n
    Now run Moodle cron:<\/p>\n\n\n\n
    php admin\/cli\/cron.php\n<\/code><\/pre>\n\n\n\n
    You can run it more than once:<\/p>\n\n\n\n
    php admin\/cli\/cron.php\nphp admin\/cli\/cron.php\n<\/code><\/pre>\n\n\n\n
    Cron helps Moodle process pending cleanup tasks, enrolment syncs, deleted contexts, and scheduled maintenance operations.<\/p>\n\n\n\n
    \n\n\n\n
    Step 7: Run Context Cleanup If Needed<\/h1>\n\n\n\n
    If the error still appears and the debug message mentions context<\/code>, run Moodle\u2019s context cleanup task.<\/p>\n\n\n\n
    php admin\/tool\/task\/cli\/schedule_task.php --execute='\\core\\task\\context_cleanup_task' --showdebugging\n<\/code><\/pre>\n\n\n\n
    This helps clean up broken or orphaned context records caused by deleted courses, categories, users, or enrolment structures.<\/p>\n\n\n\n
    \n\n\n\n
    Step 8: Recheck the Course<\/h1>\n\n\n\n
    Now open the affected course again:<\/p>\n\n\n\n
    Course \u2192 Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
    The page should now load normally.<\/p>\n\n\n\n
    If the old Course meta link was the cause, the broken enrolment method should be gone.<\/p>\n\n\n\n
    Now you can add the correct enrolment method:<\/p>\n\n\n\n
    Add method \u2192 Cohort sync\n<\/code><\/pre>\n\n\n\n
    Select your cohort and assign the correct role, usually:<\/p>\n\n\n\n
    Student\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Step 9: Move from Course Meta Link to Cohort Sync<\/h1>\n\n\n\n
    If your goal is to give one group of users access to many courses, Cohort sync is usually the cleaner approach.<\/p>\n\n\n\n
    Old approach:<\/p>\n\n\n\n
    Users enrolled in Master Course\n        \u2193\nCourse meta link\n        \u2193\nUsers get access to other courses\n<\/code><\/pre>\n\n\n\n
    Better approach:<\/p>\n\n\n\n
    Users added to Cohort\n        \u2193\nCohort sync\n        \u2193\nUsers get access to required courses\n<\/code><\/pre>\n\n\n\n
    This is easier to manage because cohorts are designed for grouping users at the site or category level.<\/p>\n\n\n\n
    \n\n\n\n
    Step 10: Bulk Add Cohort Sync to Many Courses<\/h1>\n\n\n\n
    If you have hundreds of courses, adding Cohort sync manually one by one is painful.<\/p>\n\n\n\n
    Instead, use Moodle\u2019s Upload courses<\/strong> feature.<\/p>\n\n\n\n
    Go to:<\/p>\n\n\n\n
    Site administration \u2192 Courses \u2192 Upload courses\n<\/code><\/pre>\n\n\n\n
    Prepare a CSV file like this:<\/p>\n\n\n\n
    shortname,enrolment_1,enrolment_1_cohortidnumber,enrolment_1_role\nCOURSE001,cohort,premium_students,student\nCOURSE002,cohort,premium_students,student\nCOURSE003,cohort,premium_students,student\n<\/code><\/pre>\n\n\n\n
    Where:<\/p>\n\n\n\n
    shortname = existing Moodle course shortname\nenrolment_1 = cohort\nenrolment_1_cohortidnumber = Cohort ID\nenrolment_1_role = role to assign, usually student\n<\/code><\/pre>\n\n\n\n
    Important: enrolment_1_cohortidnumber<\/code> should match the Cohort ID<\/strong>, not just the cohort display name.<\/p>\n\n\n\n
    Then upload the CSV with:<\/p>\n\n\n\n
    Upload mode: Update existing courses only\nUpdate mode: Update with CSV data\n<\/code><\/pre>\n\n\n\n
    Always preview before applying changes.<\/p>\n\n\n\n
    \n\n\n\n
    Useful SQL Queries for Troubleshooting<\/h1>\n\n\n\n
    Check enrolment methods for one course<\/h2>\n\n\n\n
    Replace 123<\/code> with your course ID.<\/p>\n\n\n\n
    SELECT \n    e.id,\n    e.enrol,\n    e.status,\n    e.courseid,\n    e.roleid,\n    e.customint1,\n    e.customint2,\n    e.customchar1\nFROM mdl_enrol e\nWHERE e.courseid = 123\nORDER BY e.sortorder, e.id;\n<\/code><\/pre>\n\n\n\n
    Find broken meta enrolments<\/h2>\n\n\n\n
    SELECT \n    e.id,\n    e.courseid,\n    target.shortname AS target_course,\n    e.customint1 AS missing_source_course_id\nFROM mdl_enrol e\nJOIN mdl_course target ON target.id = e.courseid\nLEFT JOIN mdl_course source ON source.id = e.customint1\nWHERE e.enrol = 'meta'\nAND source.id IS NULL;\n<\/code><\/pre>\n\n\n\n
    Find enrolment records pointing to missing courses<\/h2>\n\n\n\n
    SELECT e.*\nFROM mdl_enrol e\nLEFT JOIN mdl_course c ON c.id = e.courseid\nWHERE c.id IS NULL;\n<\/code><\/pre>\n\n\n\n
    Find user enrolments pointing to missing enrolment instances<\/h2>\n\n\n\n
    SELECT ue.*\nFROM mdl_user_enrolments ue\nLEFT JOIN mdl_enrol e ON e.id = ue.enrolid\nWHERE e.id IS NULL;\n<\/code><\/pre>\n\n\n\n
    Find cohort sync records pointing to missing cohorts<\/h2>\n\n\n\n
    SELECT e.*\nFROM mdl_enrol e\nLEFT JOIN mdl_cohort ch ON ch.id = e.customint1\nWHERE e.enrol = 'cohort'\nAND e.customint1 IS NOT NULL\nAND ch.id IS NULL;\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Best Practices to Avoid This Issue in Future<\/h1>\n\n\n\n
    1. Do not use courses as enrolment containers unless necessary<\/h2>\n\n\n\n
    If your goal is to manage groups of users, use cohorts.<\/p>\n\n\n\n
    Better:<\/p>\n\n\n\n
    Cohort \u2192 Courses\n<\/code><\/pre>\n\n\n\n
    Avoid unnecessary dependency like:<\/p>\n\n\n\n
    Master Course \u2192 Other Courses\n<\/code><\/pre>\n\n\n\n
    2. Before deleting courses, check meta links<\/h2>\n\n\n\n
    Before deleting any old master\/source course, check whether other courses are using it as a Course meta link source.<\/p>\n\n\n\n
    You can run:<\/p>\n\n\n\n
    SELECT \n    e.id,\n    e.courseid AS target_course_id,\n    target.shortname AS target_course,\n    e.customint1 AS source_course_id,\n    source.shortname AS source_course\nFROM mdl_enrol e\nJOIN mdl_course target ON target.id = e.courseid\nJOIN mdl_course source ON source.id = e.customint1\nWHERE e.enrol = 'meta';\n<\/code><\/pre>\n\n\n\n
    This shows which courses depend on which source courses.<\/p>\n\n\n\n
    3. Use Cohort sync for large-scale access<\/h2>\n\n\n\n
    For large Moodle installations with many courses, Cohort sync is easier to maintain.<\/p>\n\n\n\n
    Example:<\/p>\n\n\n\n
    SEO Students Cohort \u2192 50 SEO Courses\nDevOps Students Cohort \u2192 80 DevOps Courses\nSRE Students Cohort \u2192 40 SRE Courses\n<\/code><\/pre>\n\n\n\n
    4. Keep regular database backups<\/h2>\n\n\n\n
    Before deleting courses, categories, cohorts, or enrolment methods, always keep a backup.<\/p>\n\n\n\n
    5. Run cron regularly<\/h2>\n\n\n\n
    Moodle cron should run every minute or as recommended for your Moodle version and server environment.<\/p>\n\n\n\n
    Example crontab:<\/p>\n\n\n\n
    * * * * * \/usr\/bin\/php \/path\/to\/moodle\/admin\/cli\/cron.php >\/dev\/null\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Final Summary<\/h1>\n\n\n\n
    If Moodle shows this error:<\/p>\n\n\n\n
    Can't find data record in database.\n<\/code><\/pre>\n\n\n\n
    when opening:<\/p>\n\n\n\n
    Course \u2192 Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
    and you recently deleted old linked courses, the most likely cause is a broken Course meta link<\/strong> enrolment record.<\/p>\n\n\n\n
    The deleted course was probably still referenced by another course through a meta enrolment method.<\/p>\n\n\n\n
    The safest fix is:<\/p>\n\n\n\n
    1. Find broken meta enrolment records\n2. Backup the database\n3. Remove broken records using Moodle API\n4. Purge caches\n5. Run cron\n6. Recheck enrolment methods page\n7. Move to Cohort sync for future course access\n<\/code><\/pre>\n\n\n\n
    The important lesson is this:<\/p>\n\n\n\n
    Course meta link depends on another course.\nCohort sync depends on a cohort.\n<\/code><\/pre>\n\n\n\n
    If you delete the source course used by Course meta link, Moodle may break when trying to load the enrolment method. But if you use Cohort sync properly, user access is cleaner, easier to manage, and much better for hundreds of courses.<\/p>\n\n\n\n
    \n\n\n\n
    References<\/h2>\n\n\n\n
      \n
    1. Moodle Docs: Course meta link enrolment
      https:\/\/docs.moodle.org\/en\/Course_meta_link_enrolment<\/a><\/li>\n\n\n\n
    2. Moodle Developer Resources: Enrolment plugins
      https:\/\/moodledev.io\/docs\/4.5\/apis\/plugintypes\/enrol<\/a><\/li>\n\n\n\n
    3. Moodle GitHub: Course meta link enrolment code
      https:\/\/github.com\/moodle\/moodle\/blob\/MOODLE_405_STABLE\/enrol\/meta\/lib.php<\/a><\/li>\n\n\n\n
    4. Moodle Docs: Course enrolment
      https:\/\/docs.moodle.org\/en\/Course_enrolment<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
      Managing enrolments in Moodle is usually simple when everything is cleanly configured. But sometimes, after deleting old courses or changing the enrolment structure, Moodle may suddenly start… <\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5640","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/5640","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/comments?post=5640"}],"version-history":[{"count":1,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/5640\/revisions"}],"predecessor-version":[{"id":5641,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/5640\/revisions\/5641"}],"wp:attachment":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media?parent=5640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/categories?post=5640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/tags?post=5640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}