Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
DROP TOOLS CATALOG Requires Password ?
615 views
Skip to first unread message
Fin
Dec 5, 2011, 10:54:48 AM12/5/11
to
Using Express-C 9.7.5 64 bit on Win 7 Pro sp1 I am trying to drop the existing tools catalog in one of my databases as i am having all manner of issues with it. However the manual states the command syntax as:
DROP TOOLS CATALOG TOOLSCAT IN DATABASE DBNAME force
But when I try it, it fails with SQL30082N Security processing failed with reason "" (""). Manual mentions nothing about user or password and cannot get syntax to work, any ideas ?
db2diag.log shows :
2011-12-05-09.51.21.389000-360 I83154F413 LEVEL: Error
PID : 4456 TID : 3136 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3136
FUNCTION: DB2 Tools, DB2 administration server, writeICMErrorMsg, probe:10
DATA #1 : String, 111 bytes
ICM00001N An SQL error occurred while connecting to the database. Database = "DBNAME ", Catalog = "TOOLSCAT".
2011-12-05-09.51.21.389000-360 I83569F411 LEVEL: Error
PID : 4456 TID : 3136 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3136
FUNCTION: DB2 Tools, DB2 administration server, writeICMErrorMsg, probe:10
DATA #1 : String, 111 bytes
[IBM][CLI Driver] SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING"). SQLSTATE=08001
DROP TOOLS CATALOG TOOLSCAT IN DATABASE DBNAME force
But when I try it, it fails with SQL30082N Security processing failed with reason "" (""). Manual mentions nothing about user or password and cannot get syntax to work, any ideas ?
db2diag.log shows :
2011-12-05-09.51.21.389000-360 I83154F413 LEVEL: Error
PID : 4456 TID : 3136 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3136
FUNCTION: DB2 Tools, DB2 administration server, writeICMErrorMsg, probe:10
DATA #1 : String, 111 bytes
ICM00001N An SQL error occurred while connecting to the database. Database = "DBNAME ", Catalog = "TOOLSCAT".
2011-12-05-09.51.21.389000-360 I83569F411 LEVEL: Error
PID : 4456 TID : 3136 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3136
FUNCTION: DB2 Tools, DB2 administration server, writeICMErrorMsg, probe:10
DATA #1 : String, 111 bytes
[IBM][CLI Driver] SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING"). SQLSTATE=08001
Helmut Tessarek
Dec 5, 2011, 11:21:20 AM12/5/11
to
On 05.12.11 10:54 , Fin wrote:
> But when I try it, it fails with SQL30082N Security processing failed with
> reason "" (""). Manual mentions nothing about user or password and cannot
> get syntax to work, any ideas ?
Tools Catalog means you have to have an administration server running.
> But when I try it, it fails with SQL30082N Security processing failed with
> reason "" (""). Manual mentions nothing about user or password and cannot
> get syntax to work, any ideas ?
Try to attach to it and run the command again.
--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab
Fin
Dec 5, 2011, 12:04:20 PM12/5/11
to
How do I attach to an admin server ? I had no instance node defined, so I added one and attach to that, still doesn't work however.
Command : db2 DROP TOOLS CATALOG TOOLSCAT IN DATABASE DBNAME
Gives a response of:
1. ECF errors, unresolved in the IBM Express-C forum
2. Health monitor errors (see below)
3. BIND option does not work via the Configuration Assistant
4. The get snapshot command from Storage Management does not work
and now this.
I appreciate the help Helmut, really I do. I am getting these errors on both 32-bit AND 64-bit systems I recently upgraded from 9.7.4 to 9.7.5 and it's damned frustrating. I just wonder if I have missed an upgrade command anywhere, but the manual stated when moving within releases it was all automatic.
Thanks again for the help.
2011-12-05-11.00.34.416000-360 I3965F432 LEVEL: Warning
PID : 6080 TID : 5900 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 5900
FUNCTION: DB2 UDB, Health Monitor, HmonMainCB::refreshDbAutonomicSwitches, probe:160
MESSAGE : Failed connecting to database "SQ4TEST "
DATA #1 : Hexdump, 4 bytes
0x000000000768D6EC : 7E8A FFFF ~...
Command : db2 DROP TOOLS CATALOG TOOLSCAT IN DATABASE DBNAME
Gives a response of:
SQL30082N Security processing failed with reason "" ("").
I now have five (5) issues with the latest release 9.7.5
1. ECF errors, unresolved in the IBM Express-C forum
2. Health monitor errors (see below)
3. BIND option does not work via the Configuration Assistant
4. The get snapshot command from Storage Management does not work
and now this.
I appreciate the help Helmut, really I do. I am getting these errors on both 32-bit AND 64-bit systems I recently upgraded from 9.7.4 to 9.7.5 and it's damned frustrating. I just wonder if I have missed an upgrade command anywhere, but the manual stated when moving within releases it was all automatic.
Thanks again for the help.
2011-12-05-11.00.34.416000-360 I3965F432 LEVEL: Warning
PID : 6080 TID : 5900 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 5900
FUNCTION: DB2 UDB, Health Monitor, HmonMainCB::refreshDbAutonomicSwitches, probe:160
MESSAGE : Failed connecting to database "SQ4TEST "
DATA #1 : Hexdump, 4 bytes
0x000000000768D6EC : 7E8A FFFF ~...
Helmut Tessarek
Dec 5, 2011, 12:24:37 PM12/5/11
to
Hi,
If you upgrade within releases everything should be taken care of (at least on
Windows I think - I'm not using Windows nor DB2 on Windows, so my experience
is rather limited)
But you can definitely run the following for your databases:
db2 CONNECT TO <DBNAME>
db2 BIND ~/sqllib/bnd/@db2ubind.lst GRANT PUBLIC BLOCKING ALL
db2 BIND ~/sqllib/bnd/@db2cli.lst GRANT PUBLIC BLOCKING ALL
db2 BIND ~/sqllib/bnd/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 CONNECT RESET
Change the path to your bnd directory.
You should also run: db2updv97 -d <DBNAME>
Those are usually the steps you should complete when you install a new Fixpak...
I'm really sorry that you have so much trouble with 9.7.5.
With regard to your sql30082n (drop tools catalog). Do you have a db2diag.log
output? diaglevel 4 would be great.
What about the health monitor entry? Is that all there is?
If you upgrade within releases everything should be taken care of (at least on
Windows I think - I'm not using Windows nor DB2 on Windows, so my experience
is rather limited)
But you can definitely run the following for your databases:
db2 CONNECT TO <DBNAME>
db2 BIND ~/sqllib/bnd/@db2ubind.lst GRANT PUBLIC BLOCKING ALL
db2 BIND ~/sqllib/bnd/@db2cli.lst GRANT PUBLIC BLOCKING ALL
db2 BIND ~/sqllib/bnd/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 CONNECT RESET
Change the path to your bnd directory.
You should also run: db2updv97 -d <DBNAME>
Those are usually the steps you should complete when you install a new Fixpak...
I'm really sorry that you have so much trouble with 9.7.5.
With regard to your sql30082n (drop tools catalog). Do you have a db2diag.log
output? diaglevel 4 would be great.
What about the health monitor entry? Is that all there is?
Fin
Dec 5, 2011, 1:30:56 PM12/5/11
to
Thanks for the help, appreciate it. Unfortunately after updating and rebinding the errors still exist. I set diaglevel to 4 and the log file went nuts ! The following is a very short extract of what occurred.
In summary,
1. We have ECF issues with the Admin Server
2. The health monitor errors
3. BIND will not work from the Configuration Assistant
4. Capture Snapshot will not work from the Storage Management.
2011-12-05-12.08.20.054000-360 I26866F442 LEVEL: Event
PID : 2728 TID : 2816 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
APPHDL : 0-54 APPID: *LOCAL.DB2.111205180820
AUTHID : TIM
EDUID : 2816 EDUNAME: db2agent (instance)
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Diaglevel" From: "3" To: "4"
2011-12-05-12.09.09.100000-360 I27310F405 LEVEL: Info
PID : 2728 TID : 5116 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 5116 EDUNAME: db2ipccm
FUNCTION: DB2 UDB, base sys utilities, sqeAppServices::CreateAppl, probe:100
DATA #1 : <preformatted>
Addr[B3AF760] Nodes=[1]:: Appl[0 55]AppNodes[1],krcbNodes[1],maxNode=[0]
2011-12-05-12.09.09.131000-360 I27717F405 LEVEL: Info
PID : 2728 TID : 5116 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 5116 EDUNAME: db2ipccm
FUNCTION: DB2 UDB, base sys utilities, sqeAppServices::CreateAppl, probe:100
DATA #1 : <preformatted>
Addr[B3AF760] Nodes=[1]:: Appl[0 56]AppNodes[1],krcbNodes[1],maxNode=[0]
2011-12-05-12.09.09.131000-360 E28124F727 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsPostProcessingConnectAttach, probe:647
MESSAGE : DIA5000C A DRDA AS token "INFORMATIONAL ONLY" was detected. The
diagnostic data returned is (SRVDGN): "FUNCTION ID = 0012 , PROBE
POINT = 0647 , TRACE POINT = 0160 , SUBCODE1 = FFFFFFFF8005006D,
SUBCODE2 = FFFFFFFFFFFFFB38, SUBCODE3 = 0000000000000000, ERROR MSG =
SQLAM: CONNECT failed. See sqlcode".
2011-12-05-12.09.09.131000-360 I28853F498 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsPostProcessingConnectAttach, probe:160
MESSAGE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific control block."
2011-12-05-12.09.09.147000-360 I29353F187 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DRDA ASCB ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I29542F192 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DRDA CMNMGR CB ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I29736F189 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DSS SEGMENT ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I29927F192 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** RECEIVE BUFFER ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30121F190 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** SEND BUFFERS ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30313F195 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** CONNECTION HANDLE ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30510F193 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DRDA ATTRIBUTES ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30705F192 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** AS UCINTERFACE ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30899F765 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0
sqlerrmc:
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: 55032
2011-12-05-12.09.09.162000-360 E31666F694 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSqlam, probe:1
MESSAGE : DIA5000C A DRDA AS token "INFORMATIONAL ONLY" was detected. The
diagnostic data returned is (SRVDGN): "FUNCTION ID = 0004 , PROBE
POINT = 0001 , TRACE POINT = 0040 , SUBCODE1 = FFFFFFFF81360068,
SUBCODE2 = FFFFFFFFFFFFFB38, SUBCODE3 = 0000000000000000, ERROR MSG =
AGENT: CMNMGR Send failed".
2011-12-05-12.09.09.162000-360 I32362F453 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSqlam, probe:40
MESSAGE : ZRC=0x81360068=-2127167384=SQLJC_ERROR_NOCONNECTION
"COMMUNICATION ERROR, NO CONNECTION"
2011-12-05-12.09.09.162000-360 I32817F466 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsDrdaAsInnerDriver, probe:100
MESSAGE : ZRC=0x81360068=-2127167384=SQLJC_ERROR_NOCONNECTION
"COMMUNICATION ERROR, NO CONNECTION"
2011-12-05-12.09.09.490000-360 I33285F430 LEVEL: Info
PID : 516 TID : 2352 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 2352
FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:100
DATA #1 : String, 20 bytes
ICC VERSION: 8.0.0.0
DATA #2 : String, 39 bytes
ICC INSTALL PATH: C:\SQLLIB\BIN\ICC64\C
DATA #3 : String, 18 bytes
ICC FIPS MODE: YES
2011-12-05-12.09.09.131000-360 I33717F703 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30082 sqlerrml: 19
sqlerrmc: 3 PASSWORD MISSING
sqlerrp : SQLEXSMC
sqlerrd : (1) 0x805C013E (2) 0x0000013E (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 08001
2011-12-05-12.09.09.662000-360 I34422F405 LEVEL: Info
PID : 2728 TID : 5116 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 5116 EDUNAME: db2ipccm
FUNCTION: DB2 UDB, base sys utilities, sqeAppServices::CreateAppl, probe:100
DATA #1 : <preformatted>
Addr[B3AF760] Nodes=[1]:: Appl[0 57]AppNodes[1],krcbNodes[1],maxNode=[0]
2011-12-05-12.09.09.662000-360 I34829F703 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30082 sqlerrml: 19
sqlerrmc: 3 PASSWORD MISSING
sqlerrp : SQLEXSMC
sqlerrd : (1) 0x805C013E (2) 0x0000013E (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 08001
2011-12-05-12.09.09.662000-360 I35534F310 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, Health Monitor, hmonSQLConnect, probe:60
MESSAGE : SQLConnect error sqlRC=[-1] sqlcode=[-30082]
2011-12-05-12.09.09.662000-360 I35846F432 LEVEL: Warning
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
2011-12-05-12.09.09.662000-360 I36280F448 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, Health Monitor, HmonMainCB::addDatabaseEntry, probe:100
MESSAGE : Failed to refresh auto maintenance information for database "SQ4TEST
2011-12-05-12.09.09.740000-360 I36730F389 LEVEL: Info
PID : 516 TID : 3904 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3904
FUNCTION: DB2 Common, Security, Users and Groups, secLoadClientAuthPlugin, probe:10
DATA #1 : String, 80 bytes
Loaded plugin library C:\SQLLIB\security\plugin\IBM\client\IBMOSauthclient64.dll
2011-12-05-12.09.09.740000-360 I37121F337 LEVEL: Info
PID : 516 TID : 3904 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3904
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 37 bytes
db2secClientAuthPluginInit successful
In summary,
1. We have ECF issues with the Admin Server
2. The health monitor errors
3. BIND will not work from the Configuration Assistant
4. Capture Snapshot will not work from the Storage Management.
2011-12-05-12.08.20.054000-360 I26866F442 LEVEL: Event
PID : 2728 TID : 2816 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
APPHDL : 0-54 APPID: *LOCAL.DB2.111205180820
AUTHID : TIM
EDUID : 2816 EDUNAME: db2agent (instance)
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Diaglevel" From: "3" To: "4"
2011-12-05-12.09.09.100000-360 I27310F405 LEVEL: Info
PID : 2728 TID : 5116 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 5116 EDUNAME: db2ipccm
FUNCTION: DB2 UDB, base sys utilities, sqeAppServices::CreateAppl, probe:100
DATA #1 : <preformatted>
Addr[B3AF760] Nodes=[1]:: Appl[0 55]AppNodes[1],krcbNodes[1],maxNode=[0]
2011-12-05-12.09.09.131000-360 I27717F405 LEVEL: Info
PID : 2728 TID : 5116 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 5116 EDUNAME: db2ipccm
FUNCTION: DB2 UDB, base sys utilities, sqeAppServices::CreateAppl, probe:100
DATA #1 : <preformatted>
Addr[B3AF760] Nodes=[1]:: Appl[0 56]AppNodes[1],krcbNodes[1],maxNode=[0]
2011-12-05-12.09.09.131000-360 E28124F727 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsPostProcessingConnectAttach, probe:647
MESSAGE : DIA5000C A DRDA AS token "INFORMATIONAL ONLY" was detected. The
diagnostic data returned is (SRVDGN): "FUNCTION ID = 0012 , PROBE
POINT = 0647 , TRACE POINT = 0160 , SUBCODE1 = FFFFFFFF8005006D,
SUBCODE2 = FFFFFFFFFFFFFB38, SUBCODE3 = 0000000000000000, ERROR MSG =
SQLAM: CONNECT failed. See sqlcode".
2011-12-05-12.09.09.131000-360 I28853F498 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsPostProcessingConnectAttach, probe:160
MESSAGE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific control block."
2011-12-05-12.09.09.147000-360 I29353F187 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DRDA ASCB ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I29542F192 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DRDA CMNMGR CB ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I29736F189 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DSS SEGMENT ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I29927F192 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** RECEIVE BUFFER ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30121F190 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** SEND BUFFERS ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30313F195 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** CONNECTION HANDLE ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30510F193 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** DRDA ATTRIBUTES ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30705F192 LEVEL: Info
PID:2728 TID:172 NODE:000 Title: **** AS UCINTERFACE ****
Dump File: C:\ProgramData\IBM\DB2\DB2COPY1\DB2\2728.172.000.dump.bin
2011-12-05-12.09.09.162000-360 I30899F765 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0
sqlerrmc:
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: 55032
2011-12-05-12.09.09.162000-360 E31666F694 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSqlam, probe:1
MESSAGE : DIA5000C A DRDA AS token "INFORMATIONAL ONLY" was detected. The
diagnostic data returned is (SRVDGN): "FUNCTION ID = 0004 , PROBE
POINT = 0001 , TRACE POINT = 0040 , SUBCODE1 = FFFFFFFF81360068,
SUBCODE2 = FFFFFFFFFFFFFB38, SUBCODE3 = 0000000000000000, ERROR MSG =
AGENT: CMNMGR Send failed".
2011-12-05-12.09.09.162000-360 I32362F453 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSqlam, probe:40
MESSAGE : ZRC=0x81360068=-2127167384=SQLJC_ERROR_NOCONNECTION
"COMMUNICATION ERROR, NO CONNECTION"
2011-12-05-12.09.09.162000-360 I32817F466 LEVEL: Info
PID : 2728 TID : 172 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4TEST
APPHDL : 0-56
EDUID : 172 EDUNAME: db2agent (SQ4TEST)
FUNCTION: DB2 UDB, DRDA Application Server, sqljsDrdaAsInnerDriver, probe:100
MESSAGE : ZRC=0x81360068=-2127167384=SQLJC_ERROR_NOCONNECTION
"COMMUNICATION ERROR, NO CONNECTION"
2011-12-05-12.09.09.490000-360 I33285F430 LEVEL: Info
PID : 516 TID : 2352 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 2352
FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:100
DATA #1 : String, 20 bytes
ICC VERSION: 8.0.0.0
DATA #2 : String, 39 bytes
ICC INSTALL PATH: C:\SQLLIB\BIN\ICC64\C
DATA #3 : String, 18 bytes
ICC FIPS MODE: YES
2011-12-05-12.09.09.131000-360 I33717F703 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30082 sqlerrml: 19
sqlerrmc: 3 PASSWORD MISSING
sqlerrp : SQLEXSMC
sqlerrd : (1) 0x805C013E (2) 0x0000013E (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 08001
2011-12-05-12.09.09.662000-360 I34422F405 LEVEL: Info
PID : 2728 TID : 5116 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 5116 EDUNAME: db2ipccm
FUNCTION: DB2 UDB, base sys utilities, sqeAppServices::CreateAppl, probe:100
DATA #1 : <preformatted>
Addr[B3AF760] Nodes=[1]:: Appl[0 57]AppNodes[1],krcbNodes[1],maxNode=[0]
2011-12-05-12.09.09.662000-360 I34829F703 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30082 sqlerrml: 19
sqlerrmc: 3 PASSWORD MISSING
sqlerrp : SQLEXSMC
sqlerrd : (1) 0x805C013E (2) 0x0000013E (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 08001
2011-12-05-12.09.09.662000-360 I35534F310 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, Health Monitor, hmonSQLConnect, probe:60
MESSAGE : SQLConnect error sqlRC=[-1] sqlcode=[-30082]
2011-12-05-12.09.09.662000-360 I35846F432 LEVEL: Warning
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, Health Monitor, HmonMainCB::refreshDbAutonomicSwitches, probe:160
MESSAGE : Failed connecting to database "SQ4TEST "
DATA #1 : Hexdump, 4 bytes
0x00000000076DD41C : 7E8A FFFF ~...
MESSAGE : Failed connecting to database "SQ4TEST "
DATA #1 : Hexdump, 4 bytes
2011-12-05-12.09.09.662000-360 I36280F448 LEVEL: Info
PID : 2700 TID : 1600 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 1600
FUNCTION: DB2 UDB, Health Monitor, HmonMainCB::addDatabaseEntry, probe:100
MESSAGE : Failed to refresh auto maintenance information for database "SQ4TEST
DATA #1 : Hexdump, 4 bytes
0x00000000076DD6AC : 0200 0090 ....
2011-12-05-12.09.09.740000-360 I36730F389 LEVEL: Info
PID : 516 TID : 3904 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3904
FUNCTION: DB2 Common, Security, Users and Groups, secLoadClientAuthPlugin, probe:10
DATA #1 : String, 80 bytes
Loaded plugin library C:\SQLLIB\security\plugin\IBM\client\IBMOSauthclient64.dll
2011-12-05-12.09.09.740000-360 I37121F337 LEVEL: Info
PID : 516 TID : 3904 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
EDUID : 3904
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 37 bytes
db2secClientAuthPluginInit successful
Helmut Tessarek
Dec 5, 2011, 2:10:07 PM12/5/11
to
On 05.12.11 13:30 , Fin wrote:
> Thanks for the help, appreciate it. Unfortunately after updating and
> rebinding the errors still exist. I set diaglevel to 4 and the log file
> went nuts ! The following is a very short extract of what occurred.
diaglevel 4 really outputs a lot of data, but sometimes diaglevel 3 has just
> Thanks for the help, appreciate it. Unfortunately after updating and
> rebinding the errors still exist. I set diaglevel to 4 and the log file
> went nuts ! The following is a very short extract of what occurred.
too less info in the output.
I could also see a sql1224c which is not a good sign. One of the reasons for
this error could be:
On the Windows operating system with Extended Security enabled,
a request was submitted to the database under a user ID that
was not a member of the DB2USERS or DBADMINS group. Extended
Security prevents unauthorized access to the DB2 product by
locking DB2 system files and is enabled by default.
> In summary,
>
> 1. We have ECF issues with the Admin Server 2. The health monitor errors 3.
> BIND will not work from the Configuration Assistant 4. Capture Snapshot
> will not work from the Storage Management.
they are related to some sort of security issue. Years back when we introduced
the extended security on Windows, a lot of people started to have problems
because the permissions were not set correctly.
The IBMers in the Express-C forum should be able to help you. I don't know why
there hasn't been any progress so far.
Maybe something went wrong during the install or upgrade.
Fin
Dec 6, 2011, 2:17:10 PM12/6/11
to
I figured it may be security related, but for the life of me I cannot see where the problem is. I checked DB2_EXTSECURITY and that is set to NO. All the group policies and user groups seem fine to me. User Rights seem ok too.
Sadly nobody seems too interested in helping on the Express-C forum I'm afraid, no responses at all. The install and the redirected restore seemed to go fine, no issues at all. I do however have the same ECF issue on the 32-bit system I upgraded to 9.7.5 and that was the backup I used to restore the 64-bit system but the Health monitor is fine on the system. Seemingly I inherited the ECF issue off the 32-bit system following the upgrade.
Sadly nobody seems too interested in helping on the Express-C forum I'm afraid, no responses at all. The install and the redirected restore seemed to go fine, no issues at all. I do however have the same ECF issue on the 32-bit system I upgraded to 9.7.5 and that was the backup I used to restore the 64-bit system but the Health monitor is fine on the system. Seemingly I inherited the ECF issue off the 32-bit system following the upgrade.
Fin
Dec 6, 2011, 3:07:07 PM12/6/11
to
I don't know if this is related but when doing the bind yesterday I got the following errors:
1173 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1203 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1234 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1482 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1499 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1517 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1555 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1679 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1696 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1715 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1732 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1895 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
SQLSTATE=01532
1950 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
SQLSTATE=01532
1962 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1979 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
SQLSTATE=01532
1173 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1203 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1234 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1482 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1499 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1517 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1555 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1679 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1696 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1715 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1732 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1895 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
SQLSTATE=01532
1950 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
SQLSTATE=01532
1962 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
SQLSTATE=01532
1979 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
SQLSTATE=01532
Helmut Tessarek
Dec 10, 2011, 5:39:04 PM12/10/11
to
On 06.12.11 15:07 , Fin wrote:
> I don't know if this is related but when doing the bind yesterday I got the following errors:
>
> I don't know if this is related but when doing the bind yesterday I got the following errors:
>
> 1732 SQL0204N "SYSTOOLS.ADMINTASKS" is an undefined name.
> SQLSTATE=01532
> 1895 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
> SQLSTATE=01532
No, this has nothing to do with it.
> SQLSTATE=01532
> 1895 SQL0204N "SYSTOOLS.ADMINTASKSTATUS" is an undefined name.
> SQLSTATE=01532
The Administrative Task Scheduler (ATS) is a new feature that was introduced
in DB2 9.5.
Internally, ATS stores task definitions and status information in two tables
called SYSTOOLS.ADMINTASKS and SYSTOOLS.ADMINTASKSTATUS. These tables will be
created by the SYSPROC.ADMIN_TASK_ADD stored procedure (if they do not exist).
The tables will be created in the SYSTOOLSPACE tablespace. The SYSTOOLSPACE
tablespace is a user data tablespace that is created by the DB2 administration
tools and some SQL administrative routines.
In this scenario, the new tables have not been created, so BIND generates
these undefined name errors. These errors are harmless. The ATS stored
procedures were created to perform the necessary validation at runtime (not
bind time).
Helmut Tessarek
Dec 10, 2011, 5:53:31 PM12/10/11
to
On 06.12.11 14:17 , Fin wrote:
> I figured it may be security related, but for the life of me I cannot see
> where the problem is. I checked DB2_EXTSECURITY and that is set to NO. All
> the group policies and user groups seem fine to me. User Rights seem ok
> too.
I'm not using the administration server and it is deprecated. Despite of that
> I figured it may be security related, but for the life of me I cannot see
> where the problem is. I checked DB2_EXTSECURITY and that is set to NO. All
> the group policies and user groups seem fine to me. User Rights seem ok
> too.
I have used the admin server in the past for testing purposes and I
experienced issues with upgrading it. The best way to solve all the probems
was deleting and recreating the admin server.
I suggest you try to do the same. It is not a nice solution, but since it is
deprecated you won't get much help for it, and it is really not too much work.
I'm really sorry that I'm not able to help you with this any further.
> Sadly nobody seems too interested in helping on the Express-C forum I'm
> afraid, no responses at all. The install and the redirected restore seemed
> to go fine, no issues at all. I do however have the same ECF issue on the
> 32-bit system I upgraded to 9.7.5 and that was the backup I used to restore
> the 64-bit system but the Health monitor is fine on the system. Seemingly I
> inherited the ECF issue off the 32-bit system following the upgrade.
answer soon.
Just to clarify some things:
The ECF problem occurs on both systems, 32bit and 64bit? Right?
Both databases have been upgraded from a previous version, correct? If yes,
which version/release?
What happens, if you create a new test database on 9.7.5? Do you see the same
error messages?
With regard to the Health Monitor problem, I sadly have to say that it is
deprecated as well and I'm not really sure how to address this.
0 new messages