Re: SYS password is not known (Oracle for NT)

Hi Rachel and List,

from time to time I need do some specific SYS's job (for instance run any rdbms/admin/*.sql ) I have dba user but haven't sys's password and time to wait while our busy dba 'wake up' (we are at development side). Look, it works for sys also. You need 5sec only to change the sys's password back.

SQL> select password from dba_users where username='SCOTT';

           PASSWORD
           -----------------------------
           F894844C34402B67

SQL> alter user scott identified by lion;
           User altered.

SQL> connect scott/lion
           Connected.

REM Do whatever you like...

SQL> connect system/manager

          Connected.

SQL> alter user scott identified by values 'F894844C34402B67'; User altered.

SQL> connect scott/tiger

           Connected.

Regards,
Ed

> If you REALLY need to log in as SYS (and I agree with Joe, you shouldn't
be)
>
> you can change the password:
>
> log into sqlplus as SYSTEM (you said you have this password, yes)
>
> then run:
>
> alter user sys identified by <new password>;
>
> and you will have changed the SYS password... no need to hack anything)
>
> Rachel
>
> >
> >you're not stuck NOTHING should be logging in as sys anyways, if you
> >change it and someone is, too bad.
> >
> >You're living way to dangerously letting anyone/application login as
> >sys.
> >
> >joe
> >
> >Don Dealy II wrote:
> > >
> > > The dba left and now we are stuck!
> > >
> > > We know the SYSTEM password, but we don't know the SYS password. Is
> >there any way that this can be "hacked" (Ver 8.0.5.1.1) so we can know
what
> >it is?
> > >
> > > Yes, we could change it, but nobody knows what scripts or other
> >applications rely on the current SYS password. It's kind of a sticky
> >wicket.
> > >
> > > We want to get OEM 2.1 up and running with the intelligent agent, but
> >that may require building the password file. Will that mess up the
Received on Tue Dec 12 2000 - 13:48:51 CST