Re: SYS as SYSDBA

Two answers.

First. You can issue 'connect / as sysdba', or 'connect sys/changedpassword as sysdba'. Either will get you on as SYS. You may or may not have to enclose the entire thing in quotes, because the spaces in the string can throw things somewhat. You may also need to escape the quotes if used, because some operating systems seem to get thrown by unescaped quote characters. For example, when doing a demo of transportable tablespaces on Solaris, I have to type ... exp \'/ as sysdba\' file=etc etc etc

Second. The reason why SYS can't log in as an ordinary user any more is actually because in 9i they took the opportunity to change the default of the parameter o7_dictionary_accessibility from true to false. Were you to set that parameter explicity in your init.ora, and take the opportunity to explicity set it to be TRUE, then connect sys/password will work, no problems, and not a 'as sysdba' in sight.

Whether any of that's adviseable is another question entirely, of course. But if you have the need, the possibility is there.

Regards
HJR

--
----------------------------------------------
Resources for Oracle: http://www.hjrdba.com
===============================


"Christoph Kukulies" <kuku_at_gil.physik.rwth-aachen.de> wrote in message
news:a4gnup$4r1$1_at_nets3.rz.RWTH-Aachen.DE...


> Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote:

> > Christoph Kukulies <kuku_at_gil.physik.rwth-aachen.de> wrote in message

news:<a4g1k


> > 8$cd1$1_at_nets3.rz.RWTH-Aachen.DE>...

> >> First off: What do the many REPOST: messages mean in this NG?

> >>

> >>

> >> With the installation of Oracle 9i my installation scripts failed

> >> since user SYS is required to connect as SYSDBA.

> >>

> >> I'm using an OCI program which I wrote some time ago.

> >> Does anyone know how to add the role to the connection string?

> >>

> >> OCIAttrSet()

>


> > Are you saying you are routinely connecting as SYS using OCI?

> > SYS has never been intended to be used as an everyday user, which is

> > one reason why Oracle removed the normal connect.

> > If you want to compromise the security of your database, having a

> > hardcoded SYS password in OCI programs is one of the best ways to do

> > so.

>


> I was in error. Examining the situation further is that I do not need the

> SYS connection over the OCI interface. It was a two step process:

>


> 1. sqlplus was used to connect to the DB as SYS and install some

>    views (view8.ora that comes from centurasoft/gupta) and

>    add some public synonyms and views to tables owned by SYS.

>    Also a user is created by the sql file.

>


> 2. the OCI program is used to connect as the user established under 1.

>    and fills the database from a Gupta SQL file (It does the

>    necessary adaptations to the Oracle SQL syntax)

>


> So I was in error when assuming that I was connecting as SYS over

> OCI. False alarm.

>


> But what I need to know now:

>


> How can I still connect via SQLPlus to the Oracle9i

> database as SYS with the SYDBA priviledge?

>


> --

> Chris Christoph P. U. Kukulies kuku_at_gil.physik.rwth-aachen.de