![]() The threading option may address possible SIGABT crashes that have been observed in multithreaded ODBC applications. ![]() The following odbcinst.ini options were used with the DB2 ODBC driver: On UNIX platforms, with the unixODBC 2.3.0 driver manager and the DB2 9.7 client (FixPack 4 on Linux platforms, FixPack 2 on others): Alternatively, call MySQL native API mysql_server_init() ( mysql_library_init() for MySQL 5.x) before accessing the DB Access Module for MySQL. To work around this problem, serialize the production of the first RWDBDatabase object. This is due to a MySQL native call that is not multithread-safe. In multithreaded applications, producing RWDBDatabase objects using an RWDBManager::database() call in each thread simultaneously results in a segmentation fault. RWDBDatabase and multithreaded applications. During testing, no undetermined behavior has been detected. However, the SQL Server 7.0 and SQL Server 2000 documentation states that the use of Transact-SQL statements may cause undetermined behavior in the driver. ![]() In the Microsoft ODBC SQL Server documentation for SQL Server version 6.5, this is the recommended method for implementing savepoints. Support for transaction savepoints is implemented using Transact-SQL statements, as the ODBC API has no methods to support savepoints. Please see IBM's DB2 APAR JR18223 (SP-9012).ĭB Access Module for Microsoft SQL Server Setting the maximum number of connections was deprecated in DB2 8.1 by IBM. Setting the maximum number of connections. This has been identified as a problem in the DB2 CLI client. ![]() During testing, intermittent failures have been observed when dropping stored procedures with SQL error SQL0658N. SourcePro Release Notes SourcePro DB DB Access Module for DB2 CLIĭropping stored procedures. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |