The Instructure Community will enter a read-only state on November 22, 2025 as we prepare to migrate to our new Community platform in early December.
Read our blog post for more info about this change.
Found this content helpful? Log in or sign up to leave a like!
Has anyone experience this issue?
When we run syncdb to refresh our CD2 enrollments table to postgres, the process hangs and does not finish. All other tables sync successfully.
Some enrollments data are being loaded to the database. We can confirm this from using the latest updated_at date on the enrollments table. However, the instructure_dap.table_sync table shows timestamp from 2 days prior, so the metadata is not being updated.
Below is the log from the enrollments table and from the enrollment_terms table, which does complete successfully and contains a final "update-metadata" step.
Log from enrollments:
2025-02-27 12:01:21,850 - DEBUG - sync: insert data from resources saved to disk into database table (sql_op_sync.py:82)
2025-02-27 12:01:21,850 - DEBUG - processing file 1 of 3 (sql_op_sync.py:96)
2025-02-27 12:01:21,865 - DEBUG - inserting/updating data from C:\Users\SRV-SQ~2\AppData\Local\Temp\tmpymu7x0z2\part-00000-0e9e1797-f3c3-4ba8-b94c-0ac5951e0751-c000.tsv into database table (sql_op_sync.py:106)
2025-02-27 12:01:37,367 - DEBUG - insert/update data from C:\Users\SRV-SQ~2\AppData\Local\Temp\tmpymu7x0z2\part-00000-0e9e1797-f3c3-4ba8-b94c-0ac5951e0751-c000.tsv into database table (sql_op_sync.py:129)
2025-02-27 12:02:05,244 - DEBUG - insert/update data from C:\Users\SRV-SQ~2\AppData\Local\Temp\tmpymu7x0z2\part-00000-0e9e1797-f3c3-4ba8-b94c-0ac5951e0751-c000.tsv into database table (sql_op_sync.py:129)
Log from enrollment_terms:
2025-02-27 12:01:14,239 - DEBUG - sync: insert data from resources saved to disk into database table (sql_op_sync.py:82)
2025-02-27 12:01:14,239 - DEBUG - processing file 1 of 1 (sql_op_sync.py:96)
2025-02-27 12:01:14,255 - DEBUG - inserting/updating data from C:\Users\SRV-SQ~2\AppData\Local\Temp\tmp7_hk8ep2\part-00000-01eaad88-d5d2-4820-a0e2-a87a915ffcf3-c000.tsv into database table (sql_op_sync.py:106)
2025-02-27 12:01:14,255 - DEBUG - update meta-data about table enrollment_terms that has been replicated (sql_metatable_handler.py:74)
We get this occasionally when a table won't sync. In this case my process is to run a manual "dropdb" on the table, followed by an "initdb" on it. Works every time. No need to parse through logs...
Thank you for responding. We will try this.
🙂
Community helpTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in