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

Named Pipes Problem

P: n/a
Hi,

DB2 7.1 FP11
Windows 2000

Earlier this evening, after dropping and recreating a trigger, DB2 locked
up. I am not entirely sure that the cause of the problem was the replacing
of the trigger, but all of a sudden no users were able to connect to our
customers database. After running db2dart I found numerous corrupted indexes
which I removed using "db2dart MYDB /IM". Finally I was able to get a
connect to work, although the connect does take very long to actually
connect (~1 minute), so I think there is some sort of timeout issue involved
as well.

Our main problem is the fact that remote users are still not able to connect
to the DB. We use named pipes to connect the clients to the server, but when
connecting, we get the following error message:

SQL1287N ATTACH für Exemplar "NPIP0000" ist fehlgeschlagen, da die benannte
Pipe "\\ZHBDBS04\pipe\db2\DB2_0.cnt" nicht gefunden wurde

or in English

SQL1287N ATTACH to instance "NPIP0000" failed, as the named pipe
"\\ZHBDBS04\pipe\db2\DB2_0.cnt" could not be found

I am neither able to connect locally using named pipes, nor remotely.

Does anyone know how I can reinitialize the DB2 named pipes support?
Will a re-install of the software help, or will I still have the same
problem afer re-installation?

Regards

Rudolf Bargholz
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Rudolf Bargholz wrote:
Hi,

DB2 7.1 FP11
Windows 2000

Earlier this evening, after dropping and recreating a trigger, DB2 locked
up. I am not entirely sure that the cause of the problem was the replacing
of the trigger, but all of a sudden no users were able to connect to our
customers database. After running db2dart I found numerous corrupted indexes
which I removed using "db2dart MYDB /IM". Finally I was able to get a
connect to work, although the connect does take very long to actually
connect (~1 minute), so I think there is some sort of timeout issue involved
as well.

Our main problem is the fact that remote users are still not able to connect
to the DB. We use named pipes to connect the clients to the server, but when
connecting, we get the following error message:

SQL1287N ATTACH für Exemplar "NPIP0000" ist fehlgeschlagen, da die benannte
Pipe "\\ZHBDBS04\pipe\db2\DB2_0.cnt" nicht gefunden wurde

or in English

SQL1287N ATTACH to instance "NPIP0000" failed, as the named pipe
"\\ZHBDBS04\pipe\db2\DB2_0.cnt" could not be found

I am neither able to connect locally using named pipes, nor remotely.

Does anyone know how I can reinitialize the DB2 named pipes support?
Will a re-install of the software help, or will I still have the same
problem afer re-installation?

I don't have a solution, but I'm 99.999% sure that the trigger had
nothing to do with it.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #2

P: n/a
Hi Serge,
I don't have a solution, but I'm 99.999% sure that the trigger had nothing
to do with it.


After reinstalling DB2 7.1, FP3, and then FP11, reattaching the databases,
named pipes worked again, although the installation as usual did not work
out of the box, with the usual errors

<================>
Error during installation: C:\PROGRA~1\SQLLIB\bin\iwh2regi.exe 10 DWCTRLDB
DWCTRLDB NULL 1252 EN : -1032.
<================>
Error during installation: C:\PROGRA~1\SQLLIB\BIN\IWH2REGI.EXE 12 DWCTRLDB
IWH db2admin ******** C:\PROGRA~1\SQLLIB\LOGGING C:\PROGRA~1\SQLLIB : 2009.
<================>

Only after installing FP11 did the error no longer occur, and I had to
install in english as german did not work any more (same errors as above).
At least our customer was able to go back online at six in the morning. And
I was able to go offline ....

Regards

Rudolf Bargholz
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.