Re: SYS as SYSDBA

Howard J. Rogers <dba_at_hjrdba.com> wrote:
> 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

Thanks. That worked (but only locally). I could not use a 8.0.5 client's sqlplus to do that. I got ORA-01031 insufficient privilege.

But I think connecting to SYS as SYSDBA doesn't make any sense when VIEWs should be created that can be used by other users.

Gupta/formerly CenturaSoft/formerly Gupta provide an SQL script that lets a Gupta application use their SYSADM user and their views to SYSCOLUMS, SYSTABLES etc.

To give an example:

DROP VIEW SYSCOLCOUNT; CREATE VIEW SYSCOLCOUNT (OBJ#, COLCOUNT)         AS
SELECT C.OBJ#, COUNT(*)
FROM SYS.COL$ C
GROUP BY C.OBJ#
;

DROP PUBLIC SYNONYM SYSTABLES;
CREATE PUBLIC SYNONYM SYSTABLES FOR SYS.SYSTABLES; When the SYS user isn't suitable any longer for these tables to access which user would it be then?

> 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
> --

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