Re: ORA-28009

This isn't an error on Oracle's part.

You were never supposed to get into the habit of logging in as SYS as an ordinary, but powerful, User in *any* version of Oracle. All they've done in 9i is make it official.

Therefore, the only valid way to connect as SYS now is to log in as the Privileged User version of SYS. That simply means that the connect string must be either 'connect sys/change_on_install as sysdba' if you are using a password file, or 'connect / as sysdba' if you're using O/S authentication (which requires you to have amended the memberships of the dba group in the etc/groups file).

System never was a Privileged User, so there's no problem just logging in as system/manager as in days of yore.

It's actually a nice new feature, because SYS always was there really only to perform the 5 privileged actions (startup, shutdown, backup, recover and create database), but it was all too easy to log in as 'normal' SYS (who can't perform those 5 actions), and start doing routine maintenance -which is fine, except that (for example) any segments you create as SYS tend to end up being created in the SYSTEM tablespace, and are unexportable.

There's a set of notes on all the new features of 9i on my website (under 'books'). Feel free to peruse.

Regards
HJR

--
Resources for OracleT: www.geocities.com/howardjr2000
=========================================


"Stan Brown" <stanb_at_panix.com> wrote in message
news:9qeums$gne$1_at_panix3.panix.com...


> I installed 9i on a Linux box this weekend, and I thought I had everything

>  right. However when I tryied to log in as "SYS" this morning, I got:

>

>  ORA-28009: Conection to sys should be as sysdba or sysoper

>

>  I can log in as "system" with no proble.

>

>  Have I got a groups problem? Doesnit matter?

>

> --

> "They that would give up essential liberty for temporary safety deserve

> neither liberty nor safety."

> -- Benjamin Franklin