Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: sqlplus /nolog can't manage instance
Hi, Rogers
really sorry for my poor expression,
"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
news:3d589da7_at_dnews.tpgi.com.au...
>
> As for the rest of what you wrote, I'll take it a step at a time:
>
> "So in normal case, connect to privileged users will not connect to the
> database instance".
>
> What? Of course privileged users connect to an Instance, just like
> non-privileged users. There's just one exception: when the database is
> shutdown, and the privileged user seeks a connection in order to start it
> up, then obviously they don't connect to the Instance. They connect to the
> Listener, request a Server Process, and that Server Process then goes
about
> the business of creating the Instance, mounting the database and opening
the
> database.
I mean to the database is shutdown situation. but For local user (without
useing
the alias name) to connect to system, I think the sqlplus dirrectly use
bequeched
protocol to connect oracle and listener server is not involved in, since SID
is used here and no alias name is proviced.
>
> "But in my situation, it connects to, so I think there may be some wrong
> with the privileged setting so priveleged can't be verified normally, and
it
> try to connect to instance to verify it."
>
> I honestly haven't a clue what you are talking about here. You mean you
get
> a 'connected' response when you connect as a privileged user, but the
> database is down? Great: you've connected to the Listener, and are ready
to
> issue the 'startup' command. If your database is down, you can't connect
to
> an Instance, to verify anything, because there isn't one. Perfectly
normal.
>
I mean the sqlplus try connect to , but it didn't connectted to the server
and report sqlnet error.
> "I think the user sys and system can also be verify by the user table
since
> they can change their password."
>
> Naturally. Both SYS and SYSTEM are users with entries in the DBA_TABLES
data
> dictionary view. So yes, they can use DATA DICTIONARY authentication.
SYSTEM
> is NOT a privileged user, however, and can ONLY use data dictionary
> authentication. SYS (in 8i) can log on EITHER as a privileged user OR as
an
> ordinary dictionary-authenticated user. To log on normally, he does
'connect
> sys/something'. To log on as a privileged user, he does 'connect
> sys/something AS SYSDBA'. The extra two words invoke the external
> authentication mechanisms I mentioned earlier: either a password file or a
> check to see if you, the NT user, are a member of the ORA_DBA group.
>
> Have you read the concepts manual?
just partially now
> HJR
>
My question is if I start the service first, all is OK. I hope just use sqlplus /nologin to start the oracle instance locally( in unix, it is possible) .So I don't start the oracle instance service and fire up sqlplus /nolog , so it reports the error below:
E:\NTDDK\src\general\portio>sqlplus /nolog
SQL*Plus: Release 8.1.7.0.0 - Production on 星期五 8月 9 19:49:59 2002
(c) Copyright 2000 Oracle Corporation. All rights reserved.
SQL> connect / as sysdba
ERROR:
ORA-12560: TNS: 协议适配器错误(adapter error)
Now, I chenk the document, it is said:
Oracle services must be started for you to use the Oracle9i database and its products. (I think this means start the oracle instance at least the oracle server should run first)
If so, it is different form unix which I missed it before. For unix, administrator can start the oracle just use sqlplus. And if so, I have no problem now.
thanks and regards,
PanTao
Received on Tue Aug 13 2002 - 02:52:13 CDT
![]() |
![]() |