One database tells on every connect statement:
SQL1092N "" does not have the authority to perform the requested command.

Another database at the same instance works fine.
One day before the first database worked too.
Any idea what could have happened and how I can connect again?

Thanks
Klemens

Sounds like someone has changed the database connection authorization
list in a way that excludes your userid...you'll need to talk to your
system administrator.

Klemens wrote:
> One database tells on every connect statement:
> SQL1092N "" does not have the authority to perform the requested command.
>
> Another database at the same instance works fine.
> One day before the first database worked too.
> Any idea what could have happened and how I can connect again?
>
> Thanks
> Klemens
>
>
>

The User I used has SYSADM authority.

"Sean McKeough" <mckeough@nospam.ca.ibm.com> schrieb im Newsbeitrag
news:bvlm2h$60c$1@hanover.torolab.ibm.com...
> Sounds like someone has changed the database connection authorization
> list in a way that excludes your userid...you'll need to talk to your
> system administrator.
>
> Klemens wrote:
> > One database tells on every connect statement:
> > SQL1092N "" does not have the authority to perform the requested
command.
> >
> > Another database at the same instance works fine.
> > One day before the first database worked too.
> > Any idea what could have happened and how I can connect again?
> >
> > Thanks
> > Klemens
> >
> >
> >

If this is a windows computer make sure you log on as the
administrator on windows -- in other words when you go to Start -
Settings - Control Panel you should see your user name listed with
Administrative privileges - hope this helps!

================================================== ====================

"Klemens" <DUMMY@dummy.de> wrote in message news:<bvm0ed$u1v9n$1@ID-155009.news.uni-berlin.de>...
> The User I used has SYSADM authority.
>
> "Sean McKeough" <mckeough@nospam.ca.ibm.com> schrieb im Newsbeitrag
> news:bvlm2h$60c$1@hanover.torolab.ibm.com...
> > Sounds like someone has changed the database connection authorization
> > list in a way that excludes your userid...you'll need to talk to your
> > system administrator.
> >
> > Klemens wrote:
> > > One database tells on every connect statement:
> > > SQL1092N "" does not have the authority to perform the requested
> command.
> > >
> > > Another database at the same instance works fine.
> > > One day before the first database worked too.
> > > Any idea what could have happened and how I can connect again?
> > >
> > > Thanks
> > > Klemens
> > >
> > >
> > >

It is on windows2000 with UDB8.1 fix3 and I tried with local and with domain
administrator.
SYSADM is not set explicit at dbm cfg.

In db2diag.log I get this with rising port numbers several times:
-------------------------
2004-02-02-16.31.32.282004 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:2528 Appid:none
common communication sqlcctcpconnmgr_child Probe:117

DIA3219I Client connecting from IP address = "10.10.1.228", port = "2315".

2004-02-02-16.31.32.298001 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:2532 Appid:none
common communication sqlcctcpconnmgr_child Probe:117

DIA3219I Client connecting from IP address = "10.10.1.228", port = "2571".

....
-----------------------------------------------

until I get this:
----------------------------------------------
2004-02-02-16.31.35.157000 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:2532 Appid:none
base sys utilities sqleGetAgent Probe:70

Agent not allocated, sqlcode = -1226

2004-02-02-16.31.35.157002 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:2532 Appid:none
common communication sqlcctcpconnmgr_child Probe:125

ADM7009E An error was encountered in the "TCPIP" protocol support. A
possible
cause is that the maximum number of agents has been exceeded.

2004-02-02-16.31.35.157003 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:2532 Appid:none
common communication sqlcctcpconnmgr_child Probe:126

Return code from sqleGetAgent =
0x0154F7E8 : 0xFFFFFB36 6ûÿÿ

2004-02-02-16.31.35.173000 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3832 Appid:none
DRDA Communication Manager sqljcReceive Probe:30

CCI Error:
0x12ECBFD0 : 0x00000036 6...

2004-02-02-16.31.35.173001 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3832 Appid:none
DRDA Communication Manager sqljcReceive Probe:30

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x81360012".

2004-02-02-16.31.35.173002 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3832 Appid:none
oper system services sqlofica Probe:10

PID:2504 TID:3832 Node:000 Title: SQLCA ^
0x03B5A058 : 5351 4C43 4120 2020 8800 0000 BCFB FFFF SQLCA ^...¼ûÿÿ
0x03B5A068 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x03B5A078 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x03B5A088 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x03B5A098 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x03B5A0A8 : 0000 0000 0000 0000 5351 4C45 5843 4D4E ........SQLEXCMN
0x03B5A0B8 : 1200 3681 1200 0000 0000 0000 0000 0000 ..6.............
0x03B5A0C8 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
0x03B5A0D8 : 2020 2020 2020 2020

2004-02-02-16.31.35.173003 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3852 Appid:none
DRDA Application Requester sqljrReportServerErrReply Probe:20

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x8037006D".

PID:2504 TID:3852 Node:000 Title: SQLCA
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1092 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLEXCMN
sqlerrd : (1) 0x81360012 (2) 0x00000012 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

PID:2504 TID:3852 Node:000 Title: **** DRDA ARCB ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** AR REQUEST LIST ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** DRDA CMNMGR CB ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** RECEIVE BUFFER ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** SEND BUFFERS ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** AR UCINTERFACE ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

2004-02-02-16.31.35.220000 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3852 Appid:none
DRDA Application Server sqljsPostProcessingConnectAttach Probe:160

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x8037006D".

2004-02-02-16.31.35.220001 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3852 Appid:none
DRDA Application Server sqljsPostProcessingConnectAttach Probe:647

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 = 8037006D, SUBCODE2 = FFFFFBBC, SUBCODE3 =
00000000,
ERROR MSG = SQLAM: CONNECT failed. See sqlcode".

PID:2504 TID:3852 Node:000 Title: **** DRDA ASCB ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** DRDA CMNMGR CB ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** RECEIVE BUFFER ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** SEND BUFFERS ****


PID:2504 TID:3852 Node:000 Title: **** CONNECTION HANDLE ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** DRDA ATTRIBUTES ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

PID:2504 TID:3852 Node:000 Title: **** AS UCINTERFACE ****
Dump File:C:\Programme\IBM\SQLLIB\SCHULUNG\25043852.000

2004-02-02-16.31.35.235002 Instance:SCHULUNG Node:000
PID:2504(db2syscs.exe) TID:3852 Appid:none
oper system services sqlofica Probe:10

PID:2504 TID:3852 Node:000 Title: SQLCA ^
0x03884178 : 5351 4C43 4120 2020 8800 0000 BCFB FFFF SQLCA ^...¼ûÿÿ
0x03884188 : 0000 2020 2020 2020 2020 2020 2020 2020 ..
0x03884198 : 2020 2020 2020 2020 2020 2020 2020 2020
0x038841A8 : 2020 2020 2020 2020 2020 2020 2020 2020
0x038841B8 : 2020 2020 2020 2020 2020 2020 2020 2020
0x038841C8 : 2020 2020 2020 2020 5351 4C45 5843 4D4E SQLEXCMN
0x038841D8 : 1200 3681 1200 0000 0000 0000 0000 0000 ..6.............
0x038841E8 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
0x038841F8 : 2020 2020 2020 2020
-----------------------------------------------

expeting that somthing with the connection manager is wrong I tried:
db2set DB2TCPCONNMGRS=2
db2stop
db2start
it worked but after
db2set DB2TCPCONNMGRS=
db2stop
db2start
it still worked
One day before I tried :
db2stop
db2start
and it did id not work.


Klemens




"sea" <sea_099@hotmail.com> schrieb im Newsbeitrag
news:f8c6e337.0402030755.5fc8cdda@posting.google.c om...
> If this is a windows computer make sure you log on as the
> administrator on windows -- in other words when you go to Start -
> Settings - Control Panel you should see your user name listed with
> Administrative privileges - hope this helps!
>
> ================================================== ====================
>
> "Klemens" <DUMMY@dummy.de> wrote in message
news:<bvm0ed$u1v9n$1@ID-155009.news.uni-berlin.de>...
> > The User I used has SYSADM authority.
> >
> > "Sean McKeough" <mckeough@nospam.ca.ibm.com> schrieb im Newsbeitrag
> > news:bvlm2h$60c$1@hanover.torolab.ibm.com...
> > > Sounds like someone has changed the database connection authorization
> > > list in a way that excludes your userid...you'll need to talk to your
> > > system administrator.
> > >
> > > Klemens wrote:
> > > > One database tells on every connect statement:
> > > > SQL1092N "" does not have the authority to perform the requested
> > command.
> > > >
> > > > Another database at the same instance works fine.
> > > > One day before the first database worked too.
> > > > Any idea what could have happened and how I can connect again?
> > > >
> > > > Thanks
> > > > Klemens
> > > >
> > > >
> > > >