Title: Connect sys/[EMAIL PROTECTED] as sysdba E-Business suite
Hi All,
I have seen some weird behaviour and must have been searching in the wrong places.
When logging in to a 9i RAC environment using the syntax sys/[EMAIL PROTECTED] as sysdba it works fine at the primary instance but
Title: Connect sys/[EMAIL PROTECTED] as sysdba & E-Business suite
Hi!
Are you sure that you have correct password file in
second instance?
Maybe you're using wrong password (or do not have
pwdfile) buf on first instance you just belong to os DBA group, thus you can log
on using whatever
Hi Tanel
I did not mention that w/o the connect string it works
Will look at the password file.
I have not tried to run a query in SQL*Plus, will ask the cst to do so.
I use a new user for the repository (not apps)
Jack
-Original Message-
Sent: Friday, September 12, 2003 1:49 PM
Hi Tanel
I did not mention that w/o the connect string it works
Try to log on as sysdba with bogus password (without connect string), you
should be able to log on anyway, because you're in os dba group.
Tanel.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Tanel
Title: Message
You
should set remote_os_authent and remote_os_rolesto true, otherwise
RMAN will not be able to connect to the remote isntance as
sysdba. On the other hand, you might want to reconsider it, because that
would open your instance wide to the various forms of
network
attacks.
You are not right. SYSDBA is authenticated through the operating system. You
must have a DBA role
to be a SYSDBA, be it local or remote. To allow authentication of a remote
user as a sysdba, you
must explicitely tell oracle to do so. Dictionary accessibility has nothing
to do with that.
--
Hi!
No, o7_dictionary_accessibility controls whether SYS user can log on to
database without SYSDBA privilege (starting from 9.2). If it's false, sys
always has to connect as sysdba.
Mladen, don't you think that if you have created passwordfiles for each
instance in RAC and set
You are not right. SYSDBA is authenticated through the operating system.
You
must have a DBA role
to be a SYSDBA, be it local or remote. To allow authentication of a remote
You probably meant SYSDBA privilege to be a SYSDBA? DBA role is irrelevant
here.
Tanel.
--
Please see the official
You're right. I made a mess of this. I'm busy, and I'll stay away from the
list
today.
--
Mladen Gogala
Oracle DBA
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tanel Poder
Sent: Friday, September 12, 2003 1:05 PM
To: Multiple recipients of
