SSMA for Db2 にて Microsoft OLE DB Provider for Db2 経由で AIX上で稼働するDB2に接続したいです。

Question

SSMA for Db2 からMicrosoft OLE DB Provider for Db2 経由で AIX上で稼働するDB2に接続したいです。なお接続したいDB2は複数あり、データベースコードページが932のものと943のものがあります。接続文字列のサンプルをご教示ください

Answer 1

補足：現在コードページが943のデータベースには接続のうえカタログ情報が取得できますが、コードページが932のデータベースには接続(認証)はできるもののカタログ情報が取得できません。

Answer 2

Hi @Ikuo Takekawa,

Thanks for sharing the details. When connecting from SSMA for Db2 to DB2 on AIX using the Microsoft OLE DB Provider for DB2, you’ll want to make sure the connection string explicitly specifies the database code page. That’s why you’re seeing catalog information correctly with code page 943, but not with 932 unless you set it.

Here are sample connection strings you can try:

ini

For DB2 with code page 943

Provider=DB2OLEDB;Network Address=yourAIXHostName;

Initial Catalog=DBNAME943;Package Collection=SSMA;

User ID=db2user;Password=db2password;CodePage=943;

For DB2 with code page 932

Provider=DB2OLEDB;Network Address=yourAIXHostName;

Initial Catalog=DBNAME932;Package Collection=SSMA;

User ID=db2user;Password=db2password;CodePage=932;

Key points:

• Provider=DB2OLEDB ensures SSMA uses the Microsoft OLE DB Provider for DB2.
• CodePage must match the database encoding (932 or 943).
• Package Collection is where SSMA creates its packages (often SSMA).
• If catalog retrieval still fails with 932, confirm the provider version supports Japanese code pages and that the DB2 Connect license is correctly applied.

Hope this helps.

Thanks,

Lakshmi.

Answer 3

Hi Lakshmi.

Thanks for your reply.

I've tried specifying the code page in various ways.

There are two ways to specify a code page:

Host CCSID=932 ( or DBMS CCSID=932 )

PC Code Page=932

I have used both, and sometimes just one, and both have failed.

'package collection' is specified as NULLID. If successful, NULLID.MSCS001 is created. If unsuccessful, NULLID.MSCS001 is not created.

I am using "Microsoft OLE DB Provider for Db2 version 7.0" and downloaded the Japanese version.

I'm very grateful for your reply, but unfortunately it didn't solve the problem. I apologize for not being able to provide enough information.

If there are any other points I should be aware of, I'd be grateful if you could let me know.

Thanks.