DSMSERV Start-up Errors

ILCattivo

ADSM.ORG Senior Member
Joined
Jul 9, 2013
Messages
192
Reaction score
14
Points
0
Location
Oxford, United Kingdom
PREDATAR Control23

We have a v7.1.4 TSM server that was running fine, but today I have discovered that the dsmserv service on it had stopped.
It's basically used solely for Node Replication data. Nothing has changed on it to my knowledge??

When trying to start dsmserv we get the following output :-

C:\Program Files\Tivoli\TSM\server>dsmserv
The server has not been properly installed.
Could not find the output logfile key.
Issue dsmserv -help for a usage statement

ANR7800I DSMSERV generated at 16:57:23 on Jan 24 2016.

IBM Tivoli Storage Manager for Windows
Version 7, Release 1, Level 4.100

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2015.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR0900I Processing options file C:\Program Files\Tivoli\TSM\server\dsmserv.op-
t.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.

DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.

ANR0152I Database manager successfully started.
ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1572) Thread<0>: Missing
sqlState=42524, sqlCode=-5193 from table. Returning rc = 9994.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA34DEFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA34D8ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA31E65E0 ReportSQLDiagInfo()+2a0
ANR9999D Thread<0> 00007FFFA31E55C3 DbiEvalSQLOutcomeX()+4f3
ANR9999D Thread<0> 00007FFFA31D2C49 DbiExecuteOnConn()+1f9
ANR9999D Thread<0> 00007FFFA31EA9AE RdbSetQryOptLevel()+6e
ANR9999D Thread<0> 00007FFFA317271B RdbCreateConnection()+7cb
ANR9999D Thread<0> 00007FFFA3170C2D DbiGetConnectionTracked()+18d
ANR9999D Thread<0> 00007FFFA31D1195 tbSQLExecuteSelect()+85
ANR9999D Thread<0> 00007FFFA31D201E tbSQLExecuteToStrings()+ce
ANR9999D Thread<0> 00007FFFA31FC62C GetDB2LevelStr()+16c
ANR9999D Thread<0> 00007FFFA31F5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA3156691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA2B70D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA2B6C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA2B523FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).
ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1572) Thread<0>: Missing
sqlState=42524, sqlCode=-5193 from table. Returning rc = 9994.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA34DEFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA34D8ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA31E65E0 ReportSQLDiagInfo()+2a0
ANR9999D Thread<0> 00007FFFA31E55C3 DbiEvalSQLOutcomeX()+4f3
ANR9999D Thread<0> 00007FFFA31D2C49 DbiExecuteOnConn()+1f9
ANR9999D Thread<0> 00007FFFA31EAA82 RdbSetSchema()+a2
ANR9999D Thread<0> 00007FFFA31D11C7 tbSQLExecuteSelect()+b7
ANR9999D Thread<0> 00007FFFA31D201E tbSQLExecuteToStrings()+ce
ANR9999D Thread<0> 00007FFFA31FC62C GetDB2LevelStr()+16c
ANR9999D Thread<0> 00007FFFA31F5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA3156691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA2B70D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA2B6C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA2B523FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).
ANR9999D_0737318079 tbSQLExecuteToStrings(tbnsql.c:1227) Thread<0>: Unexpected
rc 9994 from tbSQLExecuteSelect.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA34DEFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA34D8ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA31D2079 tbSQLExecuteToStrings()+129
ANR9999D Thread<0> 00007FFFA31FC62C GetDB2LevelStr()+16c
ANR9999D Thread<0> 00007FFFA31F5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA3156691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA2B70D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA2B6C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA2B523FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR9999D_3325034490 GetDB2LevelStr(rdbdb.c:8617) Thread<0>: Rc 9994 from
tbSQLExecuteToStrings for SELECT SERVICE_LEVEL FROM SYSIBMADM.ENV_INST_INFO.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA34DEFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA34D8ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA31FC667 GetDB2LevelStr()+1a7
ANR9999D Thread<0> 00007FFFA31F5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA3156691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA2B70D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA2B6C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA2B523FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR9999D_2095217645 RdbCrossCheckDb2Level(rdbdb.c:5487) Thread<0>: Error 9994
retrieving installed DB2 level. See previous message for problem determinatio-
n.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA34DEFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA34D8ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA31F5BC3 RdbCrossCheckDb2Level()+1f3
ANR9999D Thread<0> 00007FFFA3156691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA2B70D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA2B6C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA2B523FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1572) Thread<5>: Missing
sqlState=42524, sqlCode=-5193 from table. Returning rc = 9994.
ANR9999D Thread<5> issued message 9999 from:
ANR9999D Thread<5> 00007FFFA34DEFC8 OutDiagToCons()+158
ANR9999D Thread<5> 00007FFFA34D8ABD outDiagfExt()+10d
ANR9999D Thread<5> 00007FFFA31E65E0 ReportSQLDiagInfo()+2a0
ANR9999D Thread<5> 00007FFFA31E55C3 DbiEvalSQLOutcomeX()+4f3
ANR9999D Thread<5> 00007FFFA31D2C49 DbiExecuteOnConn()+1f9
ANR9999D Thread<5> 00007FFFA31EA9AE RdbSetQryOptLevel()+6e
ANR9999D Thread<5> 00007FFFA317271B RdbCreateConnection()+7cb
ANR9999D Thread<5> 00007FFFA3170C2D DbiGetConnectionTracked()+18d
ANR9999D Thread<5> 00007FFFA31F13F9 RdbDeactivateDatabaseThread()+129
ANR9999D Thread<5> 00007FFFA2B57681 startThread()+171
ANR9999D Thread<5> 00007FFFB0C34F7F beginthreadex()+107
ANR9999D Thread<5> 00007FFFB0C35126 endthreadex()+192
ANR9999D Thread<5> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<5> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).


Anyone any idea's what's happening here and how to resolve it? I'm not particularly an expert in DB2, which it appears to be pointing at here?

Thanks
 
PREDATAR Control23

Were you logged in as the instance owner?

You also omitted the server key:
dsmserv -k server1
 
PREDATAR Control23

Hi marclant,

Output is the same regardless of being logged into the OS via the Instance Owner or not.

'dsmserv -k server1' also produces the same output?? Unless I'm missing something here?
 
PREDATAR Control23

The server has not been properly installed.
Could not find the output logfile key.

DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.

ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).
It's these errors that suggested to me that either you weren't logged as the instance owner or use the -k server1.

Do you still see the above errors when you start the server as the instance owner and with -k server1? Or even better, what`s the output of "dsmserv -k server1" when you are logged in as the instance owner.
 
PREDATAR Control23

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\tsminst1>cd\

C:\>cd "Program Files\Tivoli\TSM\server"

C:\Program Files\Tivoli\TSM\server>dsmserv -k server1
The server has not been properly installed.
Could not find the output logfile key.
Issue dsmserv -help for a usage statement

ANR7800I DSMSERV generated at 16:57:23 on Jan 24 2016.

IBM Tivoli Storage Manager for Windows
Version 7, Release 1, Level 4.100

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2015.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR0900I Processing options file C:\Program Files\Tivoli\TSM\server\dsmserv.op-
t.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.

DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.


DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User response:

Specify an existing instance name or create the required instance.

ANR0152I Database manager successfully started.
ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1572) Thread<0>: Missing
sqlState=42524, sqlCode=-5193 from table. Returning rc = 9994.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA479EFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA4798ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA44A65E0 ReportSQLDiagInfo()+2a0
ANR9999D Thread<0> 00007FFFA44A55C3 DbiEvalSQLOutcomeX()+4f3
ANR9999D Thread<0> 00007FFFA4492C49 DbiExecuteOnConn()+1f9
ANR9999D Thread<0> 00007FFFA44AA9AE RdbSetQryOptLevel()+6e
ANR9999D Thread<0> 00007FFFA443271B RdbCreateConnection()+7cb
ANR9999D Thread<0> 00007FFFA4430C2D DbiGetConnectionTracked()+18d
ANR9999D Thread<0> 00007FFFA4491195 tbSQLExecuteSelect()+85
ANR9999D Thread<0> 00007FFFA449201E tbSQLExecuteToStrings()+ce
ANR9999D Thread<0> 00007FFFA44BC62C GetDB2LevelStr()+16c
ANR9999D Thread<0> 00007FFFA44B5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA4416691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA3E30D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA3E2C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA3E123FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).
ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1572) Thread<0>: Missing
sqlState=42524, sqlCode=-5193 from table. Returning rc = 9994.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA479EFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA4798ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA44A65E0 ReportSQLDiagInfo()+2a0
ANR9999D Thread<0> 00007FFFA44A55C3 DbiEvalSQLOutcomeX()+4f3
ANR9999D Thread<0> 00007FFFA4492C49 DbiExecuteOnConn()+1f9
ANR9999D Thread<0> 00007FFFA44AAA82 RdbSetSchema()+a2
ANR9999D Thread<0> 00007FFFA44911C7 tbSQLExecuteSelect()+b7
ANR9999D Thread<0> 00007FFFA449201E tbSQLExecuteToStrings()+ce
ANR9999D Thread<0> 00007FFFA44BC62C GetDB2LevelStr()+16c
ANR9999D Thread<0> 00007FFFA44B5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA4416691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA3E30D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA3E2C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA3E123FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).
ANR9999D_0737318079 tbSQLExecuteToStrings(tbnsql.c:1227) Thread<0>: Unexpected
rc 9994 from tbSQLExecuteSelect.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA479EFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA4798ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA4492079 tbSQLExecuteToStrings()+129
ANR9999D Thread<0> 00007FFFA44BC62C GetDB2LevelStr()+16c
ANR9999D Thread<0> 00007FFFA44B5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA4416691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA3E30D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA3E2C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA3E123FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR9999D_3325034490 GetDB2LevelStr(rdbdb.c:8617) Thread<0>: Rc 9994 from
tbSQLExecuteToStrings for SELECT SERVICE_LEVEL FROM SYSIBMADM.ENV_INST_INFO.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA479EFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA4798ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA44BC667 GetDB2LevelStr()+1a7
ANR9999D Thread<0> 00007FFFA44B5A67 RdbCrossCheckDb2Level()+97
ANR9999D Thread<0> 00007FFFA4416691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA3E30D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA3E2C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA3E123FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR9999D_2095217645 RdbCrossCheckDb2Level(rdbdb.c:5487) Thread<0>: Error 9994
retrieving installed DB2 level. See previous message for problem determinatio-
n.
ANR9999D Thread<0> issued message 9999 from:
ANR9999D Thread<0> 00007FFFA479EFC8 OutDiagToCons()+158
ANR9999D Thread<0> 00007FFFA4798ABD outDiagfExt()+10d
ANR9999D Thread<0> 00007FFFA44B5BC3 RdbCrossCheckDb2Level()+1f3
ANR9999D Thread<0> 00007FFFA4416691 dbiInit()+4c1
ANR9999D Thread<0> 00007FFFA3E30D4F StartServer()+2cf
ANR9999D Thread<0> 00007FFFA3E2C5CF admStartServer()+ff
ANR9999D Thread<0> 00007FFFA3E123FF adsmMain()+134f
ANR9999D Thread<0> 00007FF733E9110D main()+8d dsmserv.c:241
ANR9999D Thread<0> 00007FF733E9272B __tmainCRTStartup()+10f crtexe.c:626
ANR9999D Thread<0> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<0> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1572) Thread<5>: Missing
sqlState=42524, sqlCode=-5193 from table. Returning rc = 9994.
ANR9999D Thread<5> issued message 9999 from:
ANR9999D Thread<5> 00007FFFA479EFC8 OutDiagToCons()+158
ANR9999D Thread<5> 00007FFFA4798ABD outDiagfExt()+10d
ANR9999D Thread<5> 00007FFFA44A65E0 ReportSQLDiagInfo()+2a0
ANR9999D Thread<5> 00007FFFA44A55C3 DbiEvalSQLOutcomeX()+4f3
ANR9999D Thread<5> 00007FFFA4492C49 DbiExecuteOnConn()+1f9
ANR9999D Thread<5> 00007FFFA44AA9AE RdbSetQryOptLevel()+6e
ANR9999D Thread<5> 00007FFFA443271B RdbCreateConnection()+7cb
ANR9999D Thread<5> 00007FFFA4430C2D DbiGetConnectionTracked()+18d
ANR9999D Thread<5> 00007FFFA44B13F9 RdbDeactivateDatabaseThread()+129
ANR9999D Thread<5> 00007FFFA3E17681 startThread()+171
ANR9999D Thread<5> 00007FFFB5BC4F7F beginthreadex()+107
ANR9999D Thread<5> 00007FFFB5BC5126 endthreadex()+192
ANR9999D Thread<5> 00007FFFCA7C13D2 BaseThreadInitThunk()+22
ANR9999D Thread<5> 00007FFFCCC85454 RtlUserThreadStart()+34
ANR0162W Supplemental database diagnostic information: -1:42524:-5193
([IBM][CLI Driver][DB2/NT64] SQL5193N The current session user does not have
usage privilege on any enabled workloads. SQLSTATE=42524
).


C:\Program Files\Tivoli\TSM\server>
 
PREDATAR Control23

Curious, did you open the CMD prompt as Administrator or not? Whichever way you did, try the other to see if it makes a difference.

If you get the same thing, probably best you open a case with IBM. Looks like the instance lost some of it's environment settings.
 
PREDATAR Control23

Yep, tried both ways within a cmd prompt.

Very odd as this server has been running for years with little to no user intervention at all, then all of sudden it's gone belly up without warning?

Will get a case open with IBM as you say.

Thanks
 
Top