do a
db2 "list node directory"
Node 2 entry:
Node name = DB264
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = 192.168.0.1 <----- go to this hostname
from your output
Service name = 50000
and look for the NDE35256 node name and then go to that server and see if
you can login and then connect from there.
there might be some messages in the log there that tell you the real
error.
"darko "
<db2udbdba-ezmlms
hield-x11150978.x To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
12/13/2006 02:23
PM Subject
Can't connect to (nor activate)
databases
Hello, DB2 Gurus.
There is a problem with a DB2 engine that I am
not responsible for, but I am the only available
tonight. (Informix engines are my primary
responsibility :-) . I do not have any written
configuration information available, so I tried
to acquire some info. I will list the outputs I
got. All was done on the same host.
OS: AIX 5.3 (in a partition)
DB2: 8.1 + fixpacks (effectively 8.2,
Datawarehousing Edition, I think, there are
addons installed like Intelligent Miner...)
The guy that is dealing with loading the data
into some databases (used by MicroStrategy)
located at that server alarmed that he can see no database.
So, let's see if there is any active database:
bash-3.00$ db2 list active databases
SQL1611W No data was returned by Database System Monitor. SQLSTATE=00000
(That was the base for his reasoning that there is no database)
===============================================================================================
But, is there any database at all:
bash-3.00$ db2 list database directory
System Database Directory
Number of entries in the directory = 5
Database 1 entry:
Database alias = DWESCHED
Database name = DWESCHED
Node name = NDE35256
Database release level = a.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database 2 entry:
Database alias = SQWCTRL
Database name = SQWCTRL
Node name = NDE35256
Database release level = a.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database 3 entry:
Database alias = DWNBMETA
Database name = DWNBMETA
Node name = NDE35256
Database release level = a.00
Comment = Microstrategy meta baza
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database 4 entry:
Database alias = BIS
Database name = BIS15
Node name = DBBIS
Database release level = a.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database 5 entry:
Database alias = DWNB
Database name = DWNB
Node name = NDE35256
Database release level = a.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
At least they don't seem to be erased, but it's
not possible to activate them nor connect to them, as we will see.
===============================================================================================
When I try to activate one database:
bash-3.00$ db2 activate database DWNB
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.1.50.252". Communication function
detecting
the error: "recv". Protocol specific error code(s): "*", "*", "0".
SQLSTATE=08001
===============================================================================================
If I try to connect (it should activate the database, right?):
bash-3.00$ db2 connect to DWNB
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.1.50.252". Communication function
detecting
the error: "recv". Protocol specific error code(s): "*", "*", "0".
SQLSTATE=08001
And then:
bash-3.00$ db2 -a connect to DWNB
SQLCA Information
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30081 sqlerrml: 38
sqlerrmc: *˙*˙0˙TCP/IP˙SOCKETS˙10.1.50.252˙recv˙
sqlerrp : SQLJCMN
sqlerrd : (1) -2127167470 (2) 18 (3) 0
(4) 0 (5) 0 (6) 0
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 08001
===============================================================================================
I've noticed that db2diag.log in sqllib/db2dump
subdirectory is rather large (IMHO), about 260
MB. That server is still in light use
(experimental) and it's used for several weeks.
Whenever I look at it, it's being updated within
a minute ago. So, the bottom of that log in one moment was:
bash-3.00$ tail -40 db2diag.log
FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70
MESSAGE : Agent not allocated, sqlcode = -1226
2006-12-13-20.01.11.337779+060 E263171871A421 LEVEL: Error
PID : 1187952 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol
support.
A possible cause is that the maximum number of agents has been
exceeded.
2006-12-13-20.01.11.338162+060 I263172293A386 LEVEL: Error
PID : 1187952 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
MESSAGE : Return code from sqleGetAgent =
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFF66B4 : FFFF FB36 ...6
2006-12-13-20.01.28.699461+060 I263172680A282 LEVEL: Error
PID : 2453532 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70
MESSAGE : Agent not allocated, sqlcode = -1226
2006-12-13-20.01.28.701445+060 E263172963A421 LEVEL: Error
PID : 2453532 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol
support.
A possible cause is that the maximum number of agents has been
exceeded.
2006-12-13-20.01.28.701705+060 I263173385A386 LEVEL: Error
PID : 2453532 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
MESSAGE : Return code from sqleGetAgent =
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFF66B4 : FFFF FB36 ...6
bash-3.00$
===============================================================================================
Does anyone have an idea on what is the problem, and how to solve it?
TIA,
Darko
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page