Mark Thomas wrote: > > > > I did manage to reproduce the -5001 error. It is not a > > significant problem > > anymore, now that I know how to get around it. I am > > including a vtrace in > > the event that it is useful to the SAPDB development team. > >
Hurra, here we are, the vtrace brought the info we needed. Unfortunately it is a bug in our code, which will be fixed with one of the next versions. To explain, why it sometimes happens, sometimes it works: When some complex views, not created by the sysdba (at least some systemviews are of that kind) are selected, we have to change internally some states to handle these views with the correct privileges and so on. Unfortunately one state, only for the sysdba, will not be restored correctly after handling this view. But this state is checked for alter password. And then, depending of the work done before in this sysdba-session the alter password will work or not. Some clients do some implicit selects before the user can work with them. Therefore it might be, that for some of them it will never work with the current server. If your first statement in the session is this alter password (or one other causing -5001, although it should be accepted) and it does not succeed, then please try another client. Sorry for any inconveniences and thank you for helping us to find this bug. Elke SAP Labs Berlin > > -----Original Message----- > > From: Zabach, Elke [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, November 18, 2003 9:04 AM > > To: 'Mark Thomas'; SAPDB General > > Subject: RE: Cannot change passwords > > > > > > Mark Thomas wrote: > > > > > > Hello, all. > > > > > > Yesterday, I discovered that my SYSDBA account has lost its > > ability to > > > change passwords--any password but its own. It was working > > > on Monday. Now, > > > I execute: "alter password fakeuser somepass" and I get: > > > "[-5001] (at 16) > > > Missing privilege:OWNER" > > > > > > Do you have any idea what has caused this? Do you need me > > to attach a > > > vtrace? > > > > > > Thanks! > > > > > > > After some private communication, the JDBC-driver was > > upgraded (which was > > used to do the alter password) and the problem did not > occur any more. > > It cannot be explained why this changed things, but as the > > problem cannot > > be repeated, there is no chance to check if JDBC, user-input > > or server-state > > caused the trouble. > > > > Elke > > SAP Labs Berlin > > > > > -- > > > Mark "T.C." Thomas > > > United Drugs > > > > > > > > > > > > -- > > > MaxDB Discussion Mailing List > > > For list archives: http://lists.mysql.com/maxdb > > > To unsubscribe: > > > http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
