Re: startup nomount & not logged on

From: Pete Sharman <psharman_at_us.oracle.com>
Date: Tue, 13 Apr 1999 16:04:02 -0700
Message-ID: <3713CD62.D470EC98@us.oracle.com>

Connect internal is still supported for backward compatibility. I've seen nothing that says when that support will stop. It's certainly still there in 8.1.5.

HTH. Pete

Diane wrote:

> I think connect internal is supposed to be replaced by connect / as
> sysdba
> I did hear connect internal was not supported but all the support staff
> I've talked to still use it
> (I'm only on 8.0.5 so can't be definite)
>
> In article <7etopi$128_at_clannad.cs.colostate.edu>, georgios varsamopoulos
> <varsamop_at_cs.colostate.edu> writes
> >Hi,
> > I'm installing Oracle8i on a Solaris 2.7 machine and
> >I have created the necessary sripts through dbassist to create
> >a database. The first script had the following lines
> >
> >spool somefile
> >connect internal
> >startup nomount pfile = /somewhere/oracle/admin/SOLDB/pfile/initSOLDB.ora
> >
> >and I'm getting the following:
> >
> > ORACLE instance started.
> > ORA-01012: not logged on
> >
> >The first one is expected, the second is not. What's is going on?
> >(note that the next command is a CREATE DATABASE statement that doesn't
> >get executed because "ORA-01012: not logged on")
> >
> >Can anybody help me sove this problem?
> >
> >Thank you in advance,
> >George Varsamopoulos
> >
>
> --
> Diane

Regards

Pete

Peter Sharman                             Email: psharman_at_us.oracle.com
WISE Course Development Manager           Phone: +1.650.607.0109 (int'l)
Worldwide Internal Services Education            (650)607 0109 (local)

San Francisco

SQL> select standard_disclaimer, witty_remark 2 from company_requirements;

Opinions are mine and do not necessarily reflect those of Oracle Corporation

"Controlling application developers is like herding cats." Kevin Loney, ORACLE DBA Handbook
"Oh no it's not! It's much harder than that!" Bruce Pihlamae, long term ORACLE DBA

Received on Tue Apr 13 1999 - 18:04:02 CDT