hi there - please direct these requests to the IBM list at:
https://groups.google.com/forum/#!forum/ibm_db On Tue, Nov 21, 2017 at 2:25 PM, nahumcastro <nahumcas...@gmail.com> wrote: > Hello all. > > I have the same problem with db2 for as400, seems to be very different from > db2 in windows, linux. > > Here is what I have found: > > this string dont apply for as400 as documented: > ibm_db_sa://user:pass@server:port/database > because when you connect to an as400 there is only one database with a bunch > of schems. > It should be: > ibm_db_sa+pyodbc://user:password@ server:446/*local > *local are the equivalent to a database. > Now the problem is that you need a license to connect to the server or you > will get: > > SQL1598N Ha fallado un intento de conectar con el servidor de bases de > datos debido a un problema de licencia. > The text is in spanish but says: buy a license to connect to the server. > > > > > On Friday, February 12, 2016 at 8:58:39 AM UTC-6, Alex Hall wrote: >> >> Thanks so much for your reply--this really helps! I asked the people >> at work, and was told that my machine does, in fact, have some sort of >> IBM manager installed. (Can you tell I'm new to this technology and >> this job?) Using it, I was able to create a DSN to the test database >> and, it seems, connect. I'm getting an error when I call >> >> dbInspector = inspect(dbEngine) >> >> but at least I'm getting that far. I'll ask about the error in a >> separate thread, since more people are likely to have run across that >> than seem to have experience with the 400 and IBM's wrapper. >> >> On 2/12/16, Michal Petrucha <michal....@koniiiik.org> wrote: >> > On Thu, Feb 11, 2016 at 01:16:03PM -0500, Alex Hall wrote: >> >> I've done more research on this topic. There's a lot out there about >> >> using MSSQL with SA, but next to nothing about using ibm_db_sa or >> >> specifying drivers. >> >> >> >> I have pyodbc installed. I downloaded IBM's ODBC zip file, and I've >> >> put db2odbc64.dll in my project folder, but don't know how to point SA >> >> or pyodbc to it. I've tried several versions of >> >> "?driver="db2odbc64.dll"" appended to my connection string, but I keep >> >> getting an error: "data source not found and no default driver >> >> specified". It doesn't even time out anymore, it just errors out >> >> immediately. I've also tried "ibm_db_sa+pyodbc://" to start the >> >> string, but that fails too. >> >> >> >> This *must* be a simple thing, but I can't work out what to do, and >> >> Google is failing me. If anyone has any ideas, I'd greatly appreciate >> >> hearing them. Thanks, and sorry to keep bugging the list about this. I >> >> just have no other options at the moment and I need to get this >> >> working soon. >> > >> > Hi Alex, >> > >> > Unfortunately, I can't offer you any specific help with IBM DB, but >> > judging by the number of replies, it seems nobody on this list can, so >> > I only have some stab-in-the-dark suggestions. >> > >> > In my experience with enterprise software, *nothing* is ever a simple >> > thing, not even seemingly trivial operations, such as connecting to a >> > database. >> > >> > You can try using either pyodbc, or the ibm_db driver – in both cases, >> > those are just the Python DBAPI drivers which take in textual SQL >> > statements, send them to the database in the low-level network >> > protocol, and present the results as dumb Python objects. SQLAlchemy >> > is a layer on top of them. That means, the first step would be to get >> > your Python runtime to open a raw pyodbc, or ibm_db connection to the >> > server, and be able to execute raw SQL statements there. Only after >> > you confirm this works you can move on to getting SQLAlchemy to work >> > with the DBAPI driver. >> > >> > >> > In my understanding, pyodbc is a wrapper around the library unixodbc. >> > I'm not sure how it's implemented on Windows – whether it's a port of >> > unixodbc, or it uses a different ODBC implementation there. Whatever >> > the case, though, on Linux with unixodbc, when I wanted to connect to >> > MS SQL, I had to register a low-level driver with the unixodbc >> > library. I had to edit a system-wide configuration file >> > (/etc/unixODBC/odbcinst.ini), and create a new driver definition in >> > there to make unixodbc recognize the FreeTDS driver I'm using as the >> > low-level protocol implementation. >> > >> > I have no idea what low-level ODBC driver is required to connect to >> > IBM DB, I'm afraid you'll have to figure that out on your own. The >> > official IBM docs at >> > >> > https://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.apdv.cli.doc/doc/c0007944.html?cp=SSEPGG_9.7.0%2F4-0-4 >> > seem to imply that IBM provides their own low-level ODBC driver which >> > you'll need to have in place in order to be able to connect to the >> > server using ODBC. >> > >> > In any case, I would expect that the ODBC machinery would expect to >> > have the db2odbc64.dll registered somehow with a symbolic name in some >> > configuration file, registry, or whatever, and that would be the >> > string you're expected to pass as the driver name in the ODBC >> > connection string. >> > >> > Actually, I think with ODBC, you're expected to define all database >> > servers in a system-wide configuration file or some such, give each >> > one of them a nickname (“DSN”), and just use that to connect to the >> > database. >> > >> > >> > The other option is to use the ibm_db Python DBAPI driver. I expect >> > you have already seen the official docs: >> > >> > https://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.swg.im.dbclient.python.doc/doc/c0054366.html >> > Have you tried following the set-up steps in that section there? Try >> > to first get it into a state where you can connect to the database >> > with ``ibm_db.connect()``, and successfully execute SQL statements >> > from the Python shell. >> > >> > Once you get that to work, you can try to install ibm_db_sa, and try >> > to call >> > >> > ``sqlalchemy.create_engine('ibm_db_sa://user:passw...@host.name.com:50000/database')`` >> > >> > If that fails, you still have the option to turn to the official IBM >> > support channels – you're using an expensive enterprise database, >> > which should come with a support contract. The ibm_db drivers seem to >> > be officially supported by IBM, which would mean, if it doesn't work >> > for you, you should be able to request help from IBM to fix it. >> > >> > Good luck! >> > >> > Michal >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "sqlalchemy" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to sqlalchemy+...@googlegroups.com. >> > To post to this group, send email to sqlal...@googlegroups.com. >> > Visit this group at https://groups.google.com/group/sqlalchemy. >> > For more options, visit https://groups.google.com/d/optout. >> > > > -- > SQLAlchemy - > The Python SQL Toolkit and Object Relational Mapper > > http://www.sqlalchemy.org/ > > To post example code, please provide an MCVE: Minimal, Complete, and > Verifiable Example. See http://stackoverflow.com/help/mcve for a full > description. > --- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at https://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
