TOAD How To connect WITH SYS USER as SYSDBA

[Sidnet]

Can we connect through TOAD to an ORACLE DATABASE with the System USER
"SYS" as SYSDBA



How to do ??



Thank for the response



Sidnet


--
Posted via http://dbforums.com

[Turkbear]

Sidnet <member46035@dbforums.com> wrote:
Can we connect through TOAD to an ORACLE DATABASE with the System USER"SYS" as SYSDBAHow to do ??Thank for the responseSidnet

In my TOAD ( 7.4.0.3 with DBA option ) the Login Screen has a 'connect as' drop-down box..Choose it from there..

hth,

[Sidnet]

How to connect with TOAD 6.3.7.1 to an ORACLE DATABASE with a system
user SYS as SYSDBA



Thank for your repy



Sidnet


--
Posted via http://dbforums.com

[Turkbear]

Sidnet <member46035@dbforums.com> wrote:
How to connect with TOAD 6.3.7.1 to an ORACLE DATABASE with a systemuser SYS as SYSDBAThank for your repySidnet
Does not the login screen have a drop-down for connection type? 7.4 does.

If not try 'sys/password as sysdba' ( with the single quotes) as the username - leave the password one blank)

[Sidnet]

When i try 'SYS/password as SYSDBA' in USER/SCHEMA field and blank
in PASSWORD Field It show error ORA-01017 invalid USERNAME/PASSWORD
Logon denied



The problem is that someone has done a truncate table throught TOAD



And in the v$sql we can identified the PARSING_USER_ID = 0
(corresponding to USER SYS )



So i have to search proof of being able to connect through TOAD
with USER SYS



But i have'nt succeeded in it yet !!



How can i get the real user who mad this truncate !!!!


--
Posted via http://dbforums.com

[Burt Peltier]

How do you know the truncate was done in Toad?

Anyway, I just did a connect via Toad specifying SYS as the user and SYSDBA
in the dropdown for connect type.

The older versions of TOAD might now have had the dropdown.

Also, whenever SYS connects in our database a file is created on the server
in $ORACLE_HOME/rdbms/audit and it shows things like the client/user O/S
account and machine/desktop name along with a return code for success or for
failure to connect.

I don't recall turning on any auditing, but this audit of SYS (only) is
being done for 8.1.7.4 on Solaris .

Note: I don't have a Windows Oracle server, but I wonder if you could do a
connect to SYS if you ran Toad on the Windows server? You might not need
the SYSDBA dropdown ... maybe if you specify internal as the userid? Just a
thought...

--
"Sidnet" <member46035@dbforums.com> wrote in message
news:3540032.1067506173@dbforums.com... When i try 'SYS/password as SYSDBA' in USER/SCHEMA field and blank in PASSWORD Field It show error ORA-01017 invalid USERNAME/PASSWORD Logon denied The problem is that someone has done a truncate table throught TOAD And in the v$sql we can identified the PARSING_USER_ID = 0 (corresponding to USER SYS ) So i have to search proof of being able to connect through TOAD with USER SYS But i have'nt succeeded in it yet !! How can i get the real user who mad this truncate !!!! -- Posted via http://dbforums.com

[Burt Peltier]

Oops ... 1 character off in following statement I just posted:

Wrong: The older versions of TOAD might now have had the dropdown.
Correct: The older versions of TOAD might noT have had the dropdown.

--
"Burt Peltier" <burttemp1ReMoVeThIs@bellsouth.net> wrote in message
news:eS2pb.5864$ns.1199@bignews4.bellsouth.net... How do you know the truncate was done in Toad? Anyway, I just did a connect via Toad specifying SYS as the user and
SYSDBA in the dropdown for connect type. The older versions of TOAD might now have had the dropdown. Also, whenever SYS connects in our database a file is created on the
server in $ORACLE_HOME/rdbms/audit and it shows things like the client/user O/S account and machine/desktop name along with a return code for success or
for failure to connect. I don't recall turning on any auditing, but this audit of SYS (only) is being done for 8.1.7.4 on Solaris . Note: I don't have a Windows Oracle server, but I wonder if you could do a connect to SYS if you ran Toad on the Windows server? You might not need the SYSDBA dropdown ... maybe if you specify internal as the userid? Just
a thought... -- "Sidnet" <member46035@dbforums.com> wrote in message news:3540032.1067506173@dbforums.com... When i try 'SYS/password as SYSDBA' in USER/SCHEMA field and blank in PASSWORD Field It show error ORA-01017 invalid USERNAME/PASSWORD Logon denied The problem is that someone has done a truncate table throught TOAD And in the v$sql we can identified the PARSING_USER_ID = 0 (corresponding to USER SYS ) So i have to search proof of being able to connect through TOAD with USER SYS But i have'nt succeeded in it yet !! How can i get the real user who mad this truncate !!!! -- Posted via http://dbforums.com