Home » RDBMS Server » Server Administration » VERY URGENT! SYSDBA
VERY URGENT! SYSDBA [message #57609] Wed, 25 June 2003 12:52 Go to next message
Tony
Messages: 190
Registered: June 2001
Senior Member
Hi,
I am trying to execute the Remote Diagnostic Agent on Oracle on our Solaris database server. However when it asks for a sql_login userid to connect as sysdba, I have only the "system" to give. But it fails saying that it cannot connect to the database as sysdba using system. What else can I give? what about "sys"? So do I need to do some special setup to create a sysdba type user ? If so can you please tell me the complete procedure for solaris? I need this as quickly as possible to send the diagnostic results to oracle. Oracle version 7.3.4/8.1.7.

Thanks
Re: VERY URGENT! SYSDBA [message #57611 is a reply to message #57609] Wed, 25 June 2003 14:35 Go to previous messageGo to next message
Tony
Messages: 190
Registered: June 2001
Senior Member
Here's the error I get when I run rda (remote diagnostic Agent). Its not the password,because the password is correct (100% sure).

$./rda.sh
RDA Started Wed Jun 25 13:15:16 PDT 2003
RDA Starting Version 3.11, please wait..
Reading and processing RDAParms.xml file
SQL_Run_Time_Limit value will be 30 seconds
Please enter the sqlplus password for sys connecting as sysdba
The value will not be visible to you

Please re-enter password to confirm
Password confirmed

Testing connection to database with userid sys connecting as sysdba

Could not connect to the database with userid sys connecting as sysdba

- Ensure there are no prompts being made by $ORACLE_HOME/sqlplus/admin/glogin.sql
or $HOME/login.sql.

- If the userid is incorrect, cancel this run of rda.sh by pressing ctl-c and:
- either rerun setup.sh to recreate setup.txt with correct values
-or-
- manually edit setup.txt to supply the correct value for the user.

- If the userid is correct, it's possible an incorrect password was specified.
- If the password is incorrect:
Please cancel out of rda.sh by hitting ctl-c
re-run rda.sh, providing a valid password for sys when prompted.

Remember that for sysdba users, the password used should
be the database password for the user, not the password stored
in the password file.
Re: VERY URGENT! SYSDBA [message #57614 is a reply to message #57609] Thu, 26 June 2003 00:34 Go to previous messageGo to next message
Maaher
Messages: 7065
Registered: December 2001
Senior Member
What happens if you try to connect AS SYSDBA in SQL*Plus?

MHE
Re: VERY URGENT! SYSDBA [message #57635 is a reply to message #57614] Thu, 26 June 2003 10:57 Go to previous messageGo to next message
Tony
Messages: 190
Registered: June 2001
Senior Member
Ok, This is what happens when I try to run sqlplus at the database server itself: (I've given here all scenarios)

$setenv ORACLE_SID gsm
$echo $ORACLE_SID
gsm
$sqlplus

SQL*Plus: Release 3.3.4.0.1 - Production on Thu Jun 26 09:36:00 2003

Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.

Enter user-name: sys
Enter password:

Connected to:
Oracle7 Server Release 7.3.4.4.0 - Production
With the distributed option
PL/SQL Release 2.3.4.4.0 - Production

SQL> disconnect
Disconnected from Oracle7 Server Release 7.3.4.4.0 - Production
With the distributed option
PL/SQL Release 2.3.4.4.0 - Production
SQL> connect sys/pass123 as sysdba;
ERROR: ORA-01017: invalid username/password; logon denied
SQL> connect sys/dbabop
Connected.
SQL> disc
Disconnected from Oracle7 Server Release 7.3.4.4.0 - Production
With the distributed option
PL/SQL Release 2.3.4.4.0 - Production
SQL>

However from remote clients, I'm able to connect to the databse using dba studio and with sysdba privilege. A password file for the databse is also setup.
Re: VERY URGENT! SYSDBA [message #57636 is a reply to message #57614] Thu, 26 June 2003 11:01 Go to previous messageGo to next message
Tony
Messages: 190
Registered: June 2001
Senior Member
In the sqlplus script below, I forgot to mask the real password below (dbabop) , and I masked it above as pass123. So please know that its not a password issue. I just have to do this for security purposes.
Re: VERY URGENT! SYSDBA [message #57648 is a reply to message #57635] Fri, 27 June 2003 01:04 Go to previous message
Maaher
Messages: 7065
Registered: December 2001
Senior Member
So, the problem you've got with RDA is not one specific for RDA. It is the issue that you cannot connect as sysdba. Try connecting as user INTERNAL (you have version 7.3)

At Metalink you'll find methods to reset the INTERNAL/SYSDBA password.

MHE
Previous Topic: Help from OCP's
Next Topic: ORA-12545
Goto Forum:
  


Current Time: Fri Sep 20 13:32:59 CDT 2024