Home » SQL & PL/SQL » SQL & PL/SQL » Why "connection as SYS should be as SYSDBA or SYSOPER"?
Why "connection as SYS should be as SYSDBA or SYSOPER"? [message #315862] Wed, 23 April 2008 01:05 Go to next message
stnlylee
Messages: 4
Registered: April 2008
Junior Member
What's the reason causes this error? I always get this message when I am using a sys account in Oracle. I really hate that message, how can I avoid that?
Re: Why "connection as SYS should be as SYSDBA or SYSOPER"? [message #315863 is a reply to message #315862] Wed, 23 April 2008 01:07 Go to previous messageGo to next message
Frank
Messages: 7880
Registered: March 2000
Senior Member
stnlylee wrote on Wed, 23 April 2008 08:05
how can I avoid that?

Don't log in as sys.

SYS should only be used for sysadmin tasks anyway, so it should be very rare that you login as sys
Re: Why "connection as SYS should be as SYSDBA or SYSOPER"? [message #315864 is a reply to message #315862] Wed, 23 April 2008 01:15 Go to previous messageGo to next message
stnlylee
Messages: 4
Registered: April 2008
Junior Member
Thanks Frank. But I confused. What account I should use for daily maintanance and have sufficient DBA priviledge if I don't use sys? is that system? what sort of sys admin work that needs sys to carry out?
Re: Why "connection as SYS should be as SYSDBA or SYSOPER"? [message #315865 is a reply to message #315862] Wed, 23 April 2008 01:23 Go to previous messageGo to next message
varu123
Messages: 754
Registered: October 2007
Senior Member
SYS is a special user.
Only SYS along with sysdba role can startup and shutdown the database.
It should be used only for purposes that other users including system cannot do irrespective of any privileges granted to them.
Re: Why "connection as SYS should be as SYSDBA or SYSOPER"? [message #315872 is a reply to message #315864] Wed, 23 April 2008 01:35 Go to previous message
Michel Cadot
Messages: 64139
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-28009: "connection as SYS should be as SYSDBA or SYSOPER"
 *Cause:    connect SYS/<password> is no longer a valid syntax
 *Action:   Try connect SYS/<password> as SYSDBA or
            connect SYS/<password> as SYSOPER

Create a user with the privileges or roles he needs to do his job.
The simpler way (but not the most secure one) is to grant him DBA role.

Regards
Michel

[Updated on: Wed, 23 April 2008 01:36]

Report message to a moderator

Previous Topic: Bind variable not declared???
Next Topic: Next Upper value
Goto Forum:
  


Current Time: Thu Dec 08 10:13:42 CST 2016

Total time taken to generate the page: 0.07089 seconds