Hai,
Thanks for posting that qt.
Indeed, the migration command mentioned in old docu (see below) may have been depreciated since DJango 1.7.
Instead you should use:
# 1. Run migrations after you restart your platform
sudo su edxapp -s /bin/bash
cd ~
source edxapp_env
python /edx/app/edxapp/edx-platform/manage.py lms migrate --settings=aws
# 2. Then do check the mentioned tables exit in the db:
mysql> SHOW DATABASES;
+--------------------+
| Database |
+--------------------+
| information_schema |
| analytics-api |
| dashboard |
| discovery |
| ecommerce |
| edx_hive_metastore |
| edxapp |
| edxapp_csmh |
| mysql |
| notes |
| performance_schema |
| reports |
| xqueue |
+--------------------+
13 rows in set (0.00 sec)
mysql> USE edxapp;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> show tables;
+------------------------------------------------------------------+
| Tables_in_edxapp |
+------------------------------------------------------------------+
| api_admin_apiaccessconfig |
....................
| lms_xblock_xblockasidesconfig |
| lti_provider_gradedassignment |
| lti_provider_lticonsumer |
| lti_provider_ltiuser |
| lti_provider_outcomeservice |
| microsite_configuration_microsite |
| microsite_configuration_micrositehistory |
..................
| xblock_django_xblockstudioconfigurationflag |
+------------------------------------------------------------------+
365 rows in set (0.00 sec)
mysql>