DB2 and cygwin ...

[Dirk Deimeke]

Hi,

I am running the newest Adminclient with Cygwin as shell.

db2cmd /c /w /i "bash --login -i"

In two of thre cases, I cannot connect to a database using

db2 connect to <database> user <user>

I get the question for a password, the password is typed in and I see
the last letter of the password (the other part is hidden) and the
connect goes fail.

If I try another conenct, I can see the whole password.

db2 connect to <database> user <user> using <password>

works in all cases. But it is bad to see the cleartext password.

Any ideas?

Thanks in advance

Dirk

[Larry]

What is the complete error msg?

Larry Edelstein

Dirk Deimeke wrote:

Hi,

I am running the newest Adminclient with Cygwin as shell.

db2cmd /c /w /i "bash --login -i"

In two of thre cases, I cannot connect to a database using

db2 connect to <database> user <user>

I get the question for a password, the password is typed in and I see
the last letter of the password (the other part is hidden) and the
connect goes fail.

If I try another conenct, I can see the whole password.

db2 connect to <database> user <user> using <password>

works in all cases. But it is bad to see the cleartext password.

Any ideas?

Thanks in advance

Dirk

[Dave Hughes]

On 2005-07-15, Dirk Deimeke scribbled:

Hi,

I am running the newest Adminclient with Cygwin as shell.

db2cmd /c /w /i "bash --login -i"

In two of thre cases, I cannot connect to a database using

db2 connect to <database> user <user>

I get the question for a password, the password is typed in and I see
the last letter of the password (the other part is hidden) and the
connect goes fail.

If I try another conenct, I can see the whole password.

db2 connect to <database> user <user> using <password>

works in all cases. But it is bad to see the cleartext password.

Any ideas?

Strange, I just tried this and it seems to work fine for me.
Traditionally, I've used the latter method (including the USING clause
for the password) as I seem to remember running into the problem with
entering the password interactively in the past. But, as mentioned
above, it seems to work fine now.

Are you running a reasonably recent version of Cygwin / DB2? For
reference, the versions I'm running are:

Cygwin DLL: 1.5.17-1
Bash: 2.05b-17
DB2: 8.1.0.36 (DB2 Connect client)

The other thing to check is your CYGWIN environment variable. I seem to
remember including "tty" in the variable causes problems (for
reference, mine doesn't include tty).

HTH, Dave.

--
Dave (remove _nospam for e-mail)
"Cogito cogito ergo cogito sum" - Ambrose Bierce

[Dirk Deimeke]

Larry <la***@nospam.net> schrieb:

What is the complete error msg?

SQL30082N Attempt to establish connection failed with security reason
"24"
("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

Greetings

Dirk

[Dirk Deimeke]

Dave Hughes <da*********@waveform.plus.com> schrieb:

Strange, I just tried this and it seems to work fine for me.
Traditionally, I've used the latter method (including the USING clause
for the password) as I seem to remember running into the problem with
entering the password interactively in the past. But, as mentioned
above, it seems to work fine now.
The "using-clause" works fine for me too. Unfortunately I sometimes have
someone looking over my back ...
Are you running a reasonably recent version of Cygwin / DB2? For
reference, the versions I'm running are:
Your versions are pretty old ...
Cygwin DLL: 1.5.17-1
Cygwin DLL: 1.5.18-1
Bash: 2.05b-17
Bash: 3.00.16(7)-release
DB2: 8.1.0.36 (DB2 Connect client)
DB2 v8.1.9.917 (recent Adminclient for windows)
The other thing to check is your CYGWIN environment variable. I seem to
remember including "tty" in the variable causes problems (for
reference, mine doesn't include tty).

Direct hit!

I tried setting CYGWIN environment to 'ntsec' (formerly 'ntsec tty') and
now it seems to work.

Many thanks for your help.

Dirk