Re: connect question

Ryan is right. The only way to bounce an instance is to connect sys thru SINGLE line of command, i.e., conn / as sysdba or conn sys/change_on_install as sysdba

The TWO line manner i.e.,
conn sys as sysdba
password: change_on_install
won't work until database is open.

That's life. Oracle made it arbitrary.

• Jack

"Ryan Gaffuri" <rgaffuri_at_cox.net> wrote in message news:1efdad5b.0304280304.868eff7_at_posting.google.com...
> sdg <stefano1_at_att.net> wrote in message
news:<3EAC311A.8C812AAE_at_att.net>...
> > I get to the startup on the second method, and that is where I use
> > startup. My question is why 'not' using a password in the connect string
> > gets me an error where using a password in the connect string does
not....
> > it get me to the connected to idle instance where I enter the startup
> > info.
> >
> >
> > Ryan wrote:
> >
> > > "sdg" <nospan_at_noway.org> wrote in message
> > > news:3EABEA99.EB596171_at_noway.org...
> > > > Using 8.1.7.0.0
> > > >
> > > > When I use SQLPlus to start database following happens and I can not
> > > > determine if this is correct.
> > > >
> > > > Connect abc as sysdba
> > > > Enter password: ******
> > > > ERROR:
> > > > ORA-01034: ORACLE not available
> > > > ORA-27101: shared memory realm does not exist
> > > >
> > > > connect abc/password as sysdba
> > > > Connected to an idle instance.
> > > > SQL>
> > > >
> > > > Entering the password as opposed to not causes this error and is
> > > > correct?
> > > >
> > > >
> > > >
> > >
> > > you need to startup the database.
> > >
> > > go to the command line of the server.
> > >
> > > sqlplus
> > > / as SYSDBA
> > > startup
> > >
> > > then try to connect
> > >
> > > or try sys/change_on_install as SYSDBA

>