| SYSDBA [message #331091] |
Wed, 02 July 2008 05:22  |
VenkatMethuku
Messages: 8
Registered: June 2008
|
Junior Member |
|
|
Hello,
No user is there as abc in the database still we see this happening. Any idea what is this strange here ?
SQL> conn abc/abc as sysdba
Connected.
SQL> sho user
USER is "SYS"
SQL>
Thanks,
Venkat
|
|
|
|
| Re: SYSDBA [message #331096 is a reply to message #331091] |
Wed, 02 July 2008 05:30  |
ThomasG
Messages: 3212
Registered: April 2005
Location: Heilbronn, Germany
|
Senior Member |
|
|
|
A connect "as sysdba" also works if the operating system user is in the operating system DBA group.
|
|
|
|
| Re: SYSDBA [message #331098 is a reply to message #331091] |
Wed, 02 July 2008 05:34 |
VenkatMethuku
Messages: 8
Registered: June 2008
|
Junior Member |
|
|
Any specificreason behind that ????
Also when I use a wrong password I am able to connect and in the previous case the user abc doenot exist in the database ?
WHere is the security here ?
What if a user logs in using this phrase ?
thanks!!
|
|
|
|
| Re: SYSDBA [message #331105 is a reply to message #331098] |
Wed, 02 July 2008 05:45 |
ThomasG
Messages: 3212
Registered: April 2005
Location: Heilbronn, Germany
|
Senior Member |
|
|
One reason is, that after you create a new Oracle database there are no database users. So you have to connect "as sysdba" to create them.
Also, users should definetely NEVER connect as sysdba.
Also, users should NEVER be in the DBA group of the OS.
The DBA group is for, well, DBAs. And once you logged into the OS as a database administrator you have the rights of a databse administrator. Which gives you rights to delete database and/or configuration files anyway, so you can pretty much destroy the datebase in that moment whether you can log into it or not.
|
|
|
|
|
|
| Re: SYSDBA [message #331122 is a reply to message #331091] |
Wed, 02 July 2008 05:57 |
VenkatMethuku
Messages: 8
Registered: June 2008
|
Junior Member |
|
|
Okey Agreed here!!!
1.How do we go for security here ? Any specific methodology to be followed?
2. How about he same in window's environment.
3.system is secured where as SYS is not ...How do we avoid this ?
thx again for all your inputs,
Venkat
Special thanks to Mike for spreading Oracle knowledge all over the ORAFAQ.
|
|
|
|
|
|
| Re: SYSDBA [message #331243 is a reply to message #331091] |
Wed, 02 July 2008 14:24 |
srini_thiru
Messages: 133
Registered: May 2008
|
Senior Member |
|
|
I too have this same question.
I can login to the database by using the following command.
sql> conn / as sysdba
connected.
My question is every one can connect to the database using this.
How can i restrict this.
Thanks in Advance,
Seenu
|
|
|
|
| Re: SYSDBA [message #331247 is a reply to message #331243] |
Wed, 02 July 2008 14:35 |
 |
Michel Cadot
Messages: 68672
Registered: March 2007
Location: Nanterre, France, http://...
|
Senior Member
Account Moderator |
|
|
Only if you are in "dba" OS group.
| Quote: | How can i restrict this.
|
Remove users from this group.
Regards
Michel
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
