By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,586 Members | 2,445 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,586 IT Pros & Developers. It's quick & easy.

DB2 Connect db2cli.ini file changes

P: n/a
I am trying to add a line to the db2cli.ini file. I want to add a [common]
section with the line disableunicode=1. I am able to make the changes - but
I am not certain DB2 Connect is picking up the changes. So I added some
trace statements - and indeed - no trace file. Is there a trick to picking
up the new db2cli.ini file?
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
You need to keep two things in mind when doing this:

1. If your application is running on a separate client machine that
uses DB2 Connect to access DB2 then you should update the db2cli.ini
file on the client machine only, and not on the DB2 Connect machine.
The only exception to this is if your application is actually running
locally on the DB2 Connect machine itself.

2. If your application caches its connection string (which many do),
a change to the db2cli.ini will not be picked up until the application
process and any related services are stopped and restarted, or the
machine is rebooted.

Just a caution - be careful to limit tracing, it will slow your machine
down dramatically!

Hope this helps.

Perry Shindle
BearingPoint, Inc.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.