8.0.1 Mobile Link の推奨 ODBC ドライバ

On Unix and Linux, make sure the directory containing the symbolic link to your ASA ODBC driver is first in your LD_LIBRARY_PATH. This prevents the loading of the driver manager used by the non-ASA ODBC drivers. The ASA ODBC driver must not be used with this driver manager.

The driver has problems calling ASE 12.5 stored procedures which have output values, but not ASE 12 stored procedures. The -hwC+ worksround solves the problem.

On Unix, the driver doesn’t show the correct minor version number. The driver name is wqase17.so and the file date is Jun 17, 2002. The bug will be fixed in an EBF.

The performance of this driver (4.1) is better than the 4.0 driver.

-hwF+ required for Oracle 8.1.6.

This driver has problems with double-hyphen comments and unnecessary semicolons.

When setting up the DSN, on Win32, don’t check “Enable Static Cursors for Long Data”; on Unix, don’t set EnableStaticCursorsForLongData=1, it will adversely affect MobiLink performance. “Application Using Threads” should always be checked on Win32 or “ApplicationUsingThreads=1″ should be set on Unix.

On Linux, Net8 version 8.1.7.0.1 is required, plus a patch that addresses Oracle bugs 1489496 and 1467074.

On Unix, unset the LC_MESSAGES enviroment variable or set the LC_MESSAGES=en_US. Improper setting of LC_MESSAGES will make the driver unusable.

It’s best if the character set of the Oracle client is the same as the database server character set. If they are different, there are many ways mentioned in Oracle documents to avoid the problem, the simplest way is setting the NLS_LANG enviroment variable on the client side. For example, on Unix, if the charset of consolidated database is WE8ISO8859P1, export NLS_LANG on the command line as
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1

For Oracle 8.1.6 server, the workaround -hwF+ needs to fix the script fetching problem.

On Unix, the driver doesn’t show up the correct minor version number. The driver name is wqor817.so and the file date is Jun 17, 2002.

This driver cannot handle BLOB or LONG RAW data of zero length.

Fails MLB tests with conversion errors when run with multiple MobiLink worker threads.

For statement-based uploads, LONG and LONG RAW synchronization failed, and the tests for zero-length BLOB and CLOB failed with a crash.

For cursor-based uploads, LONG, BLOB and CLOB conflict-resolution tests failed.

The test for inserting the username as an extra column (or parameter) to the new row (new_row_cursor, upload_new_row_insert) and old row (old_row_cursor, upload_old_row_insert) scripts failed.

This driver tends to fail with multiple simultaneous synchronizations even when running only on a single processor. Therefore we do not recommend it. The failure typically occurs as a conversion error (“ORA-01461 can bind a LONG value only for insert into a LONG column” or “ORA-01460 unimplemented or unreasonable conversion requested”).

You can restrict it to work on only one synchronization at a time by limiting the number of MobiLink worker threads to one (via ?w 1), but this will seriously limit throughput performance.

LONG and LONG RAW synchronization tests fail when using statement-based uploads. BLOB tests fail when using cursor-based uploads.

Fails MLB tests when run on multiple processors.

With version 8.0.5.10.0 of the Oracle ODBC driver, the MLB tests could not be run at all. The tests failed from driver errors about invalid attribute/option identifier and changed option values. The same problem occurs with version 8.0.5.9.0 of the Oracle ODBC driver.

We have not been able to determine a viable workaround for these issues, but we are aware that some customers are able to use this driver successfully.

MLR test with REAL columns failed because values uploaded were slightly different when downloaded. This is yet another good reason to stay away from imprecise types like REAL.

Need to disable bulk fetching (via ?s 1). Since rows must be fetched one at a time download performance is adversely affected.

We have not been able to determine a viable workaround for this issue, but we are aware that some customers are able to use this driver successfully.

You can restrict it to work on only one synchronization at a time by limiting the number of MobiLink worker threads to one (via ?w 1), but this will seriously limit throughput performance.

For SQL Server 2000, the driver has problem with
    { call MyMSSProc(?, ?, ? ) },
using the native version
    exec MyMSSProc ?, ?, ?
instead.

The MLR tests all pass with the ODBC drivers included with Microsoft SQL Server 7 and 2000.

Passes most MLR tests using cursor-based upload.

Passes most MLB tests.

To install this driver, if your DB2 UDB client is 7.01.0000, you need first to install FixPak3 and then to install FixPak 7; if your DB2 UDB client is 7.02.0000, just install FixPak 7 directly.

Passes most MLR tests using cursor-based upload.

Passes most MLB tests.

Cursor-based uploads of BLOB and CLOB fail.

Tests for LONG VARCHAR and LONG VARCHAR FOR BIT DATA fail when using the new_row_cursor or old_row_cursor scripts.

LONG VARCHAR and LONG VARCHAR FOR BIT DATA tests need -hwE+ for cursor-based uploads. However, -hwE+ is not necessary for statement-based uploads.

Statement-based uploads perform better than cursor-based uploads, especially dealing with CLOB, BLOB, LONG VARCHAR and LONG VARCHAR FOR BIT DATA. We suggest using statement-based scripts for these data types.

Passes most MLR tests using cursor-based upload.

Passes most MLB tests.

Cursor-based uploads of BLOB and CLOB fail.

Tests for LONG VARCHAR and LONG VARCHAR FOR BIT DATA fail when using the new_row_cursor or old_row_cursor scripts.

LONG VARCHAR and LONG VARCHAR FOR BIT DATA tests need -hwE+ for cursor-based uploads. However, -hwE+ is not necessary for statement-based uploads.

Statement-based uploads perform better than cursor-based uploads, especially dealing with CLOB, BLOB, LONG VARCHAR and LONG VARCHAR FOR BIT DATA. We suggest using statement-based scripts for these data types.

This driver doesn’t support passing literal values to stored procedures.

This driver only supports up to 32K-length values of the CLOB data type.

Many conflict-resolution tests failed because of the error: “L517 cursor C1 does not identify a prepared select statement”. This bug will be fixed in an EBF.

On Win32, CLOB and LONG VARCHAR tests needs -hwE+ using cursor-based uploads, however, -hwE+ is not necessary for statement-based uploads.

When setting up a DSN on Unix, set “DecimalPrecision=31″ and “WithHold=1″; on Win32, select “31” for “DecimalPrecision” and check “With Hold Cursors”. This driver has the bug of freeing the prepared statments, set a big number as possible for Dynamic Sections, this number should be bigger than the number of rows inserted into a table. This bug will be fixed in an EBF.

The conflict-resolution synchronization doesn’t work with cursor-based upload, an EBF will fixed the bug. The statement-based upload is highly recommended for this driver.

On Unix, the driver doesn’t show the correct minor version number. The driver name is wqdb217.so and the file date is Jun 17, 2002.