imavo
commented
1 year ago You understand that the ibm_db_django will not use the pyodbc interface, but instead will use the DBI interface.
Which bitness of python are you using? If you use 64-bit python you should use a 64-bit CLI driver along with the 64bit version of odbcad32.exe gui on MS-Windows. If you use a 32-bit python you must use a 32-bit CLI driver along with the 32-bit version of odbcad32.exe gui.
ibm_db_django uses the DBI interface to connect to the database, which in turn uses the underlying ibm_db interface, which in turn uses a CLI driver. But which CLI (odbc) driver will it actually use, that depends on your configuration, your PATH , your choices before installing ibm_db_django, and your connection-string.
By default the chosen CLI (odbc) driver will be the tiny "clidriver" from IBM (which needs a licence file when connecting to as400), but you can arrange BEFORE installing ibm_db to specify to not install clidriver , which causes ibm_db later to try to use a pre-existing CLI driver as long as that pre-existing CLI driver is already fully configured, and already on the PATH, and already operating with the odbcad32.exe and already with a working DSN (data source name) corresponding to your database that matches your connection-string and PATH.
If you did not set environment variable IBM_DB_HOME to point to your working odbc driver BEFORE installing ibm_db_django (or ibm_db) then perform a full uninstall of ibm_db_django and ibm_db (with pip uninstall ibm_db_django , pip uninstall ibm_db) , set the IBM_DB_HOME variable correctly to point to the executables directory containing your working and configured odbc driver, verify the chosen odbc driver is on the PATH, and then run pip install ibm_db_django... (with whatever options are required for your django version, as per the README on the ibm_db_django github page).
Next, It is wise to verify that your stack is able to connect with DBI explicitly, before you try the django framework. Doing it that way allows for easier problem determination. If you cannot connect with simple DBI, then django and ibm_db_django will also not connect.
The simplest way to test the DBI connection explicitly is with a tiny python script , something like this:
import ibm_db_dbi
conn_string='...' # put your known working connection string here, it can identify the odbc driver via DRIVER=....
user='...' # whatever your userid for accessing the as400
userPassword='...' # the matching password for that account
try:
conn = ibm_db_dbi.connect(conn_string , user, userPassword)
except Exception as e:
print(e)If you get an exception, report all its details in full. If you do not get an exception, it means your DBI is successfully connecting using your specified odbc driver.
florisjkruger4
praveen-db2
bimalkjha
SabaKauser
kadler
Hello Everyone,
So I have been trying to connect to an already existing AS400 iSeries Database using a Django project. It is important to know that this database I am trying to connect to already has a lot of data on it... but I am not sure if that would explain why my command line "hangs" or freezes whenever I try to run the following commands:
However when I run python manage.py runserver, I get this response: `(env) C:\Users\floris.kruger\OneDrive - Dot Foods, Inc\Desktop\test\plzwrk>python manage.py runserver Watching for file changes with StatReloader Performing system checks...
System check identified no issues (0 silenced).`
Usually you would get another message after this stating that the development has started on a server at http://127.0.0.1:8000/ or something like that. But my terminal just stops at system checks and I am not able to access the web page.
I have followed all the steps listed in this github documentation and the following is what my current 'pip list' is within the virtual environment my Django Project is configured with: `(env) C:\Users\floris.kruger\OneDrive - Dot Foods, Inc\Desktop\test>pip list Package Version
asgiref 3.7.2 Django 3.2 ibm-db 3.1.4 ibm-db-django 1.5.2.0 pip 23.0.1 pytz 2023.3 regex 2023.6.3 setuptools 65.5.0 six 1.16.0 sqlparse 0.4.4 typing_extensions 4.7.1`
I am also using python version 3.10.11
(env) C:\Users\floris.kruger\OneDrive - Dot Foods, Inc\Desktop\test\plzwrk>python --version Python 3.10.11Furthermore, I believe I have my settings.py database settings and installed apps settings configured correctly. `INSTALLED_APPS = [ 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles',
]`
DATABASES = { 'default': { 'ENGINE' : 'ibm_db_django', 'NAME' : 'DB_name', 'USER' : 'USERNAME', 'PASSWORD' : 'PASSWORD', 'HOST' : 'IP_ADDRESS', 'PORT' : 'PORT', 'PCONNECT' : True, } }And I know all the values for these Database settings are in fact connect since I am able to connect to the AS400 system when using the PYODBC library which requires a connection string with the same data in order to access the AS400 system.connection_string = 'DRIVER={IBM i Access ODBC Driver};SYSTEM=_____;UID=_____;PWD=_____'However, I would like to connect properly using the actual database settings since this is much more efficient vs using the PYODBC method.
I was also able to get all three drivers installed: Client Access ODBC Driver (32-bit) IBM i Access ODBC Driver iSeries Access ODBC Driver
The default driver ibm_db uses is the Client Access Driver. However, I am still faced with the same problem and not getting any feedback when running the commands to connect. Also, my trace facility is not writing anything to the files... This must mean that the ODBC driver is not really being used? I'm completely stumped...