Re: updating sys.user$ table...

"kazhkas" <member31144_at_dbforums.com> wrote in message news:2999754.1055521872_at_dbforums.com...
>
> Originally posted by Holger Baer
> > ...
> > These people that read the manual would be the same people
> > that for some strange reason *don't* directly manipulate
> > the data dictionary.
> >
> > So if you just give a good reason as why you did this, then
> > maybe, but only maybe someone might be inclined to give you
> > a more helpfull answer
> >
> > cheers
> >
> > Holger
>
> :)
>
> ok. it's a long story to explain why i did it.
> i had a problem with new users whitch i created from old database.
> because there ware profile witch sets password lifetime 30d.
>
> these new users have no password date,
> so havo no 'password expire date'.
> and i can't login with any that user.
>
> of course, i know that something was made bad when creating profile
> or users...
>
> but there were a lot users, and i had to fix somehow.
>
> alter user <> identified by values '123..' didnt work out.
> alter user <> identified by 'passwww' work out,
> but i has only values, not passwords.
>
> so i filled sys.user$ table, sets field whitch means password date.
>
> the 'password expire date' shows up, but i still can't login.
> that is because system 'dont look at my corrections'.
>
> i know that in other DB there are some statments for that reason,
> like "flush privilegies" in mySQL.
>
> of course helps shutdown and startup database.
>
> thats all.
>
> P.S. if i will notice anything "bad" of this all, i will write.
>
> --
> Posted via http://dbforums.com

if you really didnt know what to do, why not drop and re-create? Received on Fri Jun 13 2003 - 13:09:31 CDT