Raquel wrote:
This is the rest of db2diag.log message. I am also confused what these
various messages about db2bp.exe are all about (seems like bufferpool
related). Why should a Create Procedure invoke errors for db2bp.exe.
db2bp (or db2bp.exe) is the background process on the client that will talk
to your DB2 server. So if you do a
db2 "select ... from ..."
Then the "db2" command line processor will talk to the db2bp, which in turn
knows things like the current connection, and the db2bp will pass the
request on.
[...] PID:4016 TID:4020 Node:000 Title: SQLCA
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1131 sqlerrml: 36
sqlerrmc: -2029060040 * * * * SEMAPHORE WAIT
sqlerrp : SQLJCMN
sqlerrd : (1) 0x8136001C (2) 0x0000001C (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 38503
I don't know any specifics on your error, but it seems that there was some
sort of communication problem related to a semaphore between DB2 and the
db2fmp (fenced mode process).
Because you are running on Windows, have you tried to reboot the system?
This helps me quite often for various problems on that OS.
--
Knut Stolze
Information Integration
IBM Germany / University of Jena