1👍
The immediate error (SQL0601N) is caused by a previous run of python manage.py having begun (and possibly failed) for the same USER mentioned in the DATABASES stanza of the settings.py.
The ibm_db_django 1.5.0.0 ignores the CURRENTSCHEMA in the settings.py due to a coding defect, and the consequence is the symptom that you experience. For details of the defect and a code workaround, see this link.
You will also experience a second problem (unrelated to the first) because you are using Db2-LUW v10.5, which does not have full support for BOOLEAN datatype, which instead got introduced at Db2-LUW v11.1, so consider upgrading your Db2-LUW server to V11.1 or V11.5 at latest fixpack.
While it is possible to hack the supplied migrations to avoid using BOOLEAN, it is for you to decide on the sustainability of that approach.
Keep in mind that IBM ended Db2 defect support for v10.5 on 30/April/2020, (no further fixes or enhancements) so unless your company already purchased extended support, then you should upgrade your Db2-LUW server anyway. If your company refuses to upgrade, you must decide whether your choice of toolset is appropriate.
0👍
The error returns due to different CURRENTSCHEMA and USER:
https://github.com/ibmdb/python-ibmdb-django/issues/68