Re: insufficient privileges as sysdba 8.1.7 on Win2k

You know why I got upset about this?

Because slide Number 3 (or thereabouts) on Oracle's own 9i New Features course has someone connecting system... as sysdba.

Do you know how long it takes to explain that away??!

Their example connects (and all appropriate errors) are just stuffed, stuffed, stuffed... and you know how it long it takes to explain *that* away??

If I misunderstood, I apologise

Regards
HJR "Rauf Sarwar" <rs_arwar_at_hotmail.com> wrote in message news:92eeeff0.0210031358.7329f2f8_at_posting.google.com...
> > > You can also just recreate the password file using orapwd.
> > > 1) Shutdown database as internal from svrmgrl
> > > 2) Delete old PWD<SID>.ora file
> > > 3) orapwd file=%ORACLE_HOME%\database\pwd<sid>.ora password=xxxxxx
> > > 4) Start database as internal from svrmgrl
> > > 5) grant sysdba to system;
> >
> > Ye Gods! Why Oh Why would you want to grant sysdba to SYSTEM???? When
you
> > connect system....AS SYSDBA, you are actually logged on as SYS. Half the
> > things you then proceed to do are never replicable via export/import
(just
> > for starters).
> >
> > PLEASE don't suggest we all connect as SYS. It's extremely bad news,
and
> > very bad practice.
> >
> > Don't do it.
> >
> > Regards
> > HJR
> >
> > > 6) Exit from svrmgrl and login as system then try again
> > >
> > > /Rauf Sarwar
>
>
> HJR,
>
> Seems like you did not read the Original post or else my reply would
> not have been this agonizing. :)
>
> I personally don't use System to do Sys's job... specially SYSDBA
> privilege. However, if someone wants to do it, then they have to carry
> their own bricks. According to this snip from the Orginal post... they
> have already granted SYSDBA to System... (for whatever reason).
>
> > SQL> connect system_at_pprddm as sysdba
> > Enter password:
> > Connected.
>
> Hence my reply with,
> > > 5) grant sysdba to system;
>
> Hope this clarifies it.
> Regards
> /Rauf Sarwar
Received on Fri Oct 04 2002 - 06:47:56 CDT