Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: connect question
See inline response
Daniel Morgan wrote:
> sdg wrote:
>
> > Ok, now I am more confused if that is possible. Are you saying that if user
> > abc did not install oracle, this slight difference in the (connection
> > string?) (one not inserting the password and one inserting it) is correct
> > syntax?
> >
> > Daniel Morgan wrote:
> >
> > > sdg wrote:
> > >
> > > > 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?
> > >
> > > If I understand your posting the issue is one of privileges. ABC did not
> > > install, and does not own, the Oracle executables.
> > > --
> > > Daniel Morgan
> > > http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
> > > (remove one 'x' from my email address to reply)
>
> Yes. If you are not a member of the operating system group ORA_DBA (Windows),
> DBA (UNIX) you must use the password.
I think you are missing my question/problem. User abc is a member (Windose)
ORA_DBA. I am obviously presenting the problem/question poorly.
In both examples I gave the system was given a password.
In first example the user name was given and the password was given in response
to system query. So, both user name and password given, but system errored out.
Connect abc as sysdba
Enter password: ****** <-- system generated 'Enter password:' and I entered
password.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
In second example I input both user name and password (connect abc/password) and
the system responds correctly.
connect abc/password as sysdba
Connected to an idle instance.
SQL> here is where is issue startup.
I do not understand why there is a difference. Same user, same password. Only
difference is password IS NOT entered with connect string 'connect abc as sysdba'
but entered when system requests it vs. password IS enterned, 'connect
abc/password as sysdba' in initial string.
>
> --
> Daniel Morgan
> http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
> (remove one 'x' from my email address to reply)
Received on Sun Apr 27 2003 - 18:02:17 CDT