Re: sysdba login

>
>
> So, just what exactly IS "male situation complex"?

Sorry there was typo... it should be "make situation complex"

In article <954riv$lm3$1_at_nnrp1.deja.com>,   David Fitzjarrell <oratune_at_aol.com> wrote:
> In our last gripping episode amana32_at_my-deja.com wrote:
> > There is difference in SYSDBA role and a user named as SYSDBA. First
 of
> > all one should avoid using such reserved words and male situation
> > complex. Better create a different user and use oracle utility to
> > export and import entire schema.
> >
> > Aaman
> >
> > In article <953klg$hnv$1_at_nnrp1.deja.com>,
> > gorgos_at_my-deja.com wrote:
> > > Hello all,
> > > I've inherited an application that has a schema called sysdba!
 I've
> > > also got a user who wishes to be able to login as sysdba using
 SQLPLUS
> > > 8.1.5 but he gets the error:
> > >
> > > SP2-0306: Invalid option.
> > > Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}] | [INTERNAL]
> > > where <logon> ::= <username>[/<password>][@<connect_string>] | /
> > >
> > > Is there any way around this ? svrmgrl is not an option, as he
 can't
> > > access the server.
> > >
> > > This apparantly works in 8.0.4.
> > >
> > > Thanks
> > >
> > > Sent via Deja.com
> > > http://www.deja.com/
> > >
> >
> > Sent via Deja.com
> > http://www.deja.com/
>
> --
> David Fitzjarrell
> Oracle Certified DBA
>
> Sent via Deja.com
> http://www.deja.com/
>

Sent via Deja.com
http://www.deja.com/ Received on Tue Jan 30 2001 - 10:10:48 CST