Re: [PyDB2-discuss] Can't connect to database, error SQL1042C

[Yuval T. <yu...@ad...>]

Alisdair Tullo wrote:
> Hi,
>
> I've installed PyDB2 on an Opteron machine running Fedora Core 5 x64. The 
> database is DB2 Express-C.
>
> When I try to connect from python I get the following error:
>
> alisdair@xxxx ~: python
> Python 2.4.2 (#1, Feb 12 2006, 03:45:41)
> [GCC 4.1.0 20060210 (Red Hat 4.1.0-0.24)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>   
>>>> import DB2
>>>> DB2.connect(dsn="onetest", uid="alisdair", pwd="xxxx")
>>>>         
> Traceback (most recent call last):
>    File "<stdin>", line 1, in ?
>    File "/usr/lib64/python2.4/site-packages/DB2.py", line 271, in __init__
>      self._db = _db2.connect(*args, **kwargs)
> _db2.DatabaseError: ('HY000', -1042, '[IBM][CLI Driver] SQL1042C  An 
> unexpected system error occurred.  SQLSTATE=58004\n')
>
> and in the db2diag.log I get some warnings of the form:
>
> 2006-06-09-17.13.52.251413+060 E220936G303        LEVEL: Warning (OS)
> PID     : 3935                 TID  : 4069239712  PROC : java
> INSTANCE: db2inst1             NODE : 000
> FUNCTION: DB2 UDB, oper system services, sqloclose, probe:110
> CALLED  : OS, -, unspecified_system_function      OSERR: EBADF (9)
>
> and one error:
>
> 2006-06-12-13.54.22.605271+060 I265406E425        LEVEL: Error
> PID     : 28127                TID : 47166186442352
> FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:40
> MESSAGE : ECF=0x90000403 Unexpected cryptographic error
> DATA #1 : Hex, 4 bytes
> 0x0
> DATA #2 : Hex, 4 bytes
> 0x0
> DATA #3 : Hex, 4 bytes
> 0x0
> DATA #4 : String, 78 bytes
> /home/db2inst1/sqllib/lib/icc/icclib/libicclib.so: wrong ELF class: 
> ELFCLASS32
>
> This seems to indicate a 64/32 bit problem. I changed the lib and include 
> paths in db2profile to lib64 and include64 and restarted the database. The 
> warnings went away but not the error. (It surprised me that this made any 
> difference since it is a 32-bit instance of the database).
>
> Any suggestions on how I can diagnose this, or things to try to get it 
> working, would be much appreciated.

Is your module compiled for 32 or 64 bit ?