Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Oracle / Oracle Server / February 2006

Tip: Looking for answers? Try searching our database.

Q: why are these logons different?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Vince Laurent - 27 Feb 2006 21:29 GMT
I can connect to as database from the SQL prompt like:

SQL> connect sys/****** as sysdba

but cannot from OEM or the Data Guard interface?
The login screen says to connect as sysdba.  Why
doesn't sys work in this case?

Side note: should I create a new user account to manage the DG
interface?  What is recommended?

Thanks!
Vince
-----------------------------------------------------
Come race with us!
http://www.mgpmrc.org
Maxim Demenko - 27 Feb 2006 21:37 GMT
Vince Laurent schrieb:
> I can connect to as database from the SQL prompt like:
>
[quoted text clipped - 12 lines]
> Come race with us!
> http://www.mgpmrc.org

You most likely connect using os authentification. In that case,
password which you provide in sqlplus will not be evaluated. You can try
to connect with sys/blabla - should work.
On another side, OEM connects over Net8, so to connect as sysdba you
should create password file , set required initialization parameter and
bounce the instance.

Best regards

Maxim
Vince Laurent - 28 Feb 2006 19:47 GMT
>Vince Laurent schrieb:
>> but cannot from OEM or the Data Guard interface?
>> The login screen says to connect as sysdba.  Why
>> doesn't sys work in this case?

>You most likely connect using os authentification. In that case,
>password which you provide in sqlplus will not be evaluated. You can try
>to connect with sys/blabla - should work.
>On another side, OEM connects over Net8, so to connect as sysdba you
>should create password file , set required initialization parameter and
>bounce the instance.

Bingo.  Found the document "Subject:  How to Avoid Common Flaws and
Errors Using Passwordfile   Doc ID:  Note:185703.1" shortly after
posting -again. BUT it is great to learn that I am doing it right.

I appreicate your help!
Vince

-----------------------------------------------------
Come race with us!
http://www.mgpmrc.org
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.