Re: deprecated connect internal

And just to finish the discussion off, I used SYSTEM simply as an example user, because everyone's database has it. In point of fact, ANY user granted the SYSDBA role can perform the work that INTERNAL does.

HTH. Pete

Kevin A Lewis wrote:

> AHA
>
> What has happened is that the forks in the tread have got confused. My
> message was a response to a posting by Pete Sharman. of 22/07/99 at 17:23
>
> You and I obviously are agreed, but havn't realized we do.
>
> Sorry for any confusion.
>
> Regards
>
> --
> Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich England)
> <KevinALewis_at_HotMail.com>
>
> The views expressed herein by the author of this document
> are not necessarily those of BOCM PAULS Ltd.
> Alex Hudghton <alex_at_alenda.freeserve.co.uk> wrote in message
> news:7n9gra$2vb$1_at_taliesin.netcom.net.uk...
> > But, that's what I said 'connect / as sysdba' - in fact thats all I said,
> no
> > mention of system anywhere !!
> >
> > Alex
> >
> > Kevin A Lewis wrote in message ...
> > >The connect to SYSTEM will work as it is; however it is not 'the new
> > >method'. SYSTEM is a different user. If you wish to connect to SYS as you
> > >would have by using INTERNAL the replacement/equivalent command is
> 'CONNECT
> > >/ AS SYSDBA;'
> > >
> > >Well that's what I was told on my 'not too ancient' DBA oracle course and
> > >documentation and discussion I have read recently has confirmed. I am
> open
> > >to any informed correction as always.
> > >
> > >Regards
> > >--
> > >Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich
> England)
> > > <KevinALewis_at_HotMail.com>
> > >
> > >The views expressed herein by the author of this document
> > >are not necessarily those of BOCM PAULS Ltd.
> > >external-news <alex_at_alenda.freeserve.co.uk> wrote in message
> > >news:7n9apb$1uo$1_at_taliesin.netcom.net.uk...
> > >> So how is it not correct then ?
> > >>
> > >> Alex
> > >>
> > >> Kevin A Lewis wrote in message
> > >> <4cVl3.4171$N47.500_at_newreader.ukcore.bt.net>...
> > >> >I'm not sure that the last post is correct
> > >> >
> > >> >Oracle's new replacement for 'connect internal' is 'connect / as
> > sysdba'.
> > >> >This logs on as SYS as does INTERNAL and is equivalent. When you log
> on
> > >as
> > >> >SYSTEM you are on as a different schema owner, not the owner of the
> > >> >dictionary. You may want to log on that way but it is not the same as
> > >> >logging on as INTERNAL.
> > >> >
> > >> >Regards
> > >> >
> > >> >--
> > >> >Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich
> > >England)
> > >> > <KevinALewis_at_HotMail.com>
> > >> >
> > >> >The views expressed herein by the author of this document
> > >> >are not necessarily those of BOCM PAULS Ltd.
> > >> >Alex <alex.hudghton_at_capgemini.co.uk> wrote in message
> > >> >news:7n74uq$cs0$1_at_taliesin.netcom.net.uk...
> > >> >>
> > >> >> Anurag Minocha wrote in message
> > >> <379700F2.67625BC_at_synergy-infotech.com>...
> > >> >> >Hi,
> > >> >> >The Oracle8.0.5 documentation sayss that connect as internal has
> > >been
> > >> >> >deprecated and is being supported just for backward compatibality.
> I
> > >am
> > >> >> >using connect internal. Can somebody please help me out as to how
> to
> > >> >> >switch over to the new method. The documentation is quite
> confusing.
> > >> >> >Any help will be appreciated.
> > >> >> >
> > >> >> >Thanks
> > >> >> >anurag
> > >> >> >
> > >> >> >reply at
> > >> >> >anurag_at_synergy-infotech.com
> > >> >> >
> > >> >>
> > >> >> connect / as sysdba
> > >> >>
> > >> >> Alex
> > >> >>
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >

--
Regards

Pete

Received on Fri Jul 23 1999 - 10:56:15 CDT