Home » RDBMS Server » Server Administration » Doublequestion: Trace and authentification!
Doublequestion: Trace and authentification! [message #62176] Fri, 02 July 2004 00:16 Go to next message
Alex
Messages: 190
Registered: August 1999
Senior Member
First question:

Is it possible to trace the sql-statements to one especially table which I specify?

Second question:

How I have to set which parameters to deactivate os authentification? I understood it to set all (os_authenti_prefix is " ", all others like remote_os are false) on false but I am still able to connect lokal to my 9.2. DB on windows2000 as sysdba with any name I want!
Re: Doublequestion: Trace and authentification! [message #62182 is a reply to message #62176] Fri, 02 July 2004 07:59 Go to previous messageGo to next message
croK
Messages: 170
Registered: April 2002
Senior Member
Second question: you must login into your windows system as administrator in order to login as sysdba without passwd required into oracle db.

I assume you are connecting: sqlplus /as sysdba ???
if you are specifying username/passwd
that user must be granted SYSDBA role in order to log in that way.

Best luck.
Re: Doublequestion: Trace and authentification! [message #62195 is a reply to message #62182] Mon, 05 July 2004 00:16 Go to previous messageGo to next message
Alex
Messages: 190
Registered: August 1999
Senior Member
The problem is that I am not able to deactivate the os-authentfication! I login as administrator on my windows system and then I am able to connect to my db's without password, even with users which don't exist! Every time I type 'connect / as sysdba' I am connected as sys!
But I checked init.ora and the 4 parameters are setted correct:
os_authent_prefix = OPS$
os_roles = false
remote_login_passwordfile = exclusive
remote_os_authent = false
remote_os_roles = false
Is it something other? I want that only sys/change_on_install and system/manager can connect as sysdba!
Re: Doublequestion: Trace and authentification! [message #62201 is a reply to message #62195] Mon, 05 July 2004 07:01 Go to previous messageGo to next message
croK
Messages: 170
Registered: April 2002
Senior Member
I have same init.ora parameters.
I can't do sqlplus /as sysdba
my oracle installation always requires user/pwd, there is no automatic SYSDBA login possibility.
Difference is, i have the following file in my
oracle_homedatabase
PWDPRUEBAS.ora
where PRUEBAS is my SID.
The file is encrypted.
If i remove that file, i can't no longer login as SYSDBA.
But, when the file is present, i can always login as
sys/pwd as sysdba

This is a fresh install i've made alst week.
On unix i DO have the possibility to login
/ as sysdba (but i know how to fix it on unix)

But i don't know how in the hell this file PWDSID.ora was created in my system. But it works.
Maybe you can check the documentation about this file...
best regards....
Re: Doublequestion: Trace and authentification! [message #62212 is a reply to message #62201] Mon, 05 July 2004 21:33 Go to previous message
Alex
Messages: 190
Registered: August 1999
Senior Member
PWDSID.ora is the passwordfile. There are stored the passwords for sys (and in former times for internal) and who has attitional sysdba-grants.
You can change/renew this file with the orapwd-utility.
I know this, because I rebuild this file at the beginning to change the sys-password. So I noticed this strange thing!
First I thought I damaged anything at my instance, but there are running 3 instances on my test-system and I can connect to each of them with "connect bla/bla@SID as sysdba" (whereas bla a user is which doesn't exist!)
There must be an explanation for this phenomen!
Previous Topic: Retrive Oracle Database
Next Topic: archive logs
Goto Forum:
  


Current Time: Thu Jan 09 03:51:27 CST 2025