suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT26596 Status: Geschlossen

XA Connection fails if keyword value in connection string contains
space.SSLServerCertificate is not working with XA Connection.

Produkt:
DB2 CONNECT / DB2CONNCT / B10 - DB2
Problembeschreibung:
This APAR addresses the following:

1) XA connection fails with SSL when stash file and keydb files
are present in a folder name which has spaces

2) XA connection fails when either password or passphrase or
userid has space in it .

3) Simplified ssl server certificate
mechanism(SSLSeverCertificate keyword) is not working with XA.

Basically, the space issue is applicable for all the
parameters which are passed to Microsoft XA API from Db2 client.


Steps to reproduce:
1) Create stash file and kdb file and store it in a folder which
has spaces in its path name
e.g: Program File has space
C:Program FileIBMcertshost2.sth

C:Program FileIBMcertshost2.kdb


2) Run testconn and CLI test case with -dtc option, and
XAconnection fails

























testconn test case :

C:>testconn40 "DATABASE=testdb;" -dtc
adding MSDTC step

Step 1: Printing version info
.NET Framework version: 4.0.30319.36460
64-bit
IBM DB .NET provider version: 9.7.4.4
IBM DB .NET file version: 11.1.3030.4
Capability bits: ALLDEFINED
Build: s1803021700
Factory for invariant name IBM.Data.DB2 verified
Warning, failed load of DbFactory
for:Microsoft.HostIntegration.MsDb2Cli
ent
Warning, failed load of DbFactory
for:Microsoft.HostIntegration.MsHostFi
leClient
Warning, failed load of DbFactory
for:IBM.Data.Informix.11.1.2020
Warning, failed load of DbFactory for:IBM.Data.Informix.11.1.0
Elapsed: 0.3276006

Step 2: DB2DSDRIVER_CFG_PATH env var: unset
Validating db2dsdriver.cfg against db2dsdriver.xsd schema file
C:ProgramDataIBMDB2DB2COPY1cfgdb2dsdriver.cfg against
C:Program FilesIBMSQLLIBcfgdb2dsdriver.xsd
Elapsed: 0.1248002

Step 3: Connecting using "DATABASE=testdb;"
Server type and version: DB2/LINUXX8664 11.01.0404
Elapsed: 3.7632103

Step 4: Selecting rows from SYSIBM.SYSTABLES to validate
existence of packages
SELECT * FROM SYSIBM.SYSTABLES FETCH FIRST 5 rows only
Elapsed: 1.0296018

Step 5: Calling GetSchema for tables to validate existence of
schema functions
Elapsed: 1.185602

Step 6: Creating XA connection
DB2TransactionScope: Failed to open connection to database!
IBM.Data.DB2.DB2Exception (0x80004005): ERROR [58005]
[IBM][DB2/LINUXX8664] SQL0
998N Error occurred during transaction or heuristic processing.
Reason Code =
"16". Subcode = "2-FFFFFFFF80004005". SQLSTATE=58005

at IBM.Data.DB2.DB2ConnPool.Open(DB2Connection connection,
String& szConnecti
onString, DB2ConnSettings& ppSettings, Object& ppConn)
at IBM.Data.DB2.DB2Connection.Open()
at TestConn.DB2TransactionScope.Open(String connstr)

Looking for XADLL key for C:Program
FilesIBMSQLLIBindb2app.dll
Incorrect registry entry for C:Program
FilesIBMSQLLIBindb2app.dll
in SOFTWAREMicrosoftMSDTCXADLL
is: C:Program FilesIBMSQLLIBBINDB2APP64.DLL, should be
C:Progra
m FilesIBMSQLLIBindb2app.dll

Test failed.


C:>testconn40
"DATABASE=testdb;SSLServerCertificate=C:server1.arm" -dtc
adding MSDTC step

Step 1: Printing version info
.NET Framework version: 4.0.30319.36460
64-bit
IBM DB .NET provider version: 9.7.4.4
IBM DB .NET file version: 11.1.3030.4
Capability bits: ALLDEFINED
Build: s1803021700
Factory for invariant name IBM.Data.DB2 verified
Warning, failed load of DbFactory
for:Microsoft.HostIntegration.MsDb2Cli
ent
Warning, failed load of DbFactory
for:Microsoft.HostIntegration.MsHostFi
leClient
Warning, failed load of DbFactory
for:IBM.Data.Informix.11.1.2020
Warning, failed load of DbFactory for:IBM.Data.Informix.11.1.0
Elapsed: 0.3432006

Step 2: DB2DSDRIVER_CFG_PATH env var: unset
Validating db2dsdriver.cfg against db2dsdriver.xsd schema file
C:ProgramDataIBMDB2DB2COPY1cfgdb2dsdriver.cfg against
C:Program FilesIBMSQLLIBcfgdb2dsdriver.xsd
Elapsed: 0.1248002

Step 3: Connecting using
"DATABASE=testdb;SSLServerCertificate=C:server1.arm"
Server type and version: DB2/LINUXX8664 11.01.0404
Elapsed: 3.8320069

Step 4: Selecting rows from SYSIBM.SYSTABLES to validate
existence of packages
SELECT * FROM SYSIBM.SYSTABLES FETCH FIRST 5 rows only
Elapsed: 1.2580023

Step 5: Calling GetSchema for tables to validate existence of
schema functions
Elapsed: 1.6068029

Step 6: Creating XA connection
DB2TransactionScope: Failed to open connection to database!
IBM.Data.DB2.DB2Exception (0x80004005): ERROR [58005]
[IBM][DB2/LINUXX8664] SQL0
998N Error occurred during transaction or heuristic processing.
Reason Code =
"16". Subcode = "2-FFFFFFFF80004005". SQLSTATE=58005

at IBM.Data.DB2.DB2ConnPool.Open(DB2Connection connection,
String& szConnecti
onString, DB2ConnSettings& ppSettings, Object& ppConn)
at IBM.Data.DB2.DB2Connection.Open()
at TestConn.DB2TransactionScope.Open(String connstr)

Looking for XADLL key for C:Program
FilesIBMSQLLIBindb2app.dll
Incorrect registry entry for C:Program
FilesIBMSQLLIBindb2app.dll
in SOFTWAREMicrosoftMSDTCXADLL
is: C:Program FilesIBMSQLLIBBINDB2APP64.DLL, should be
C:Progra
m FilesIBMSQLLIBindb2app.dll

Test failed.
Problem-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* XA or MS-DTC users                                           *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 version 11.1.4.5                              *
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.10.2018
17.01.2020
17.01.2020
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version