Connect to Oracle as sys via toad or any other third party software

A remote connect as a privileged user requires the database to be configured to allow remote DBA operations. The remote user will HAVE to supply a password in order to connect AS SYSDBA.

Ie: In Oracle to perform a remote connect AS SYSDBA you must use the syntax

'CONNECT SYS/PASSWORD@ORACLE_SID AS SYSDBA'

To allow remote SYSDBA connections you must:
- Set up a password file for the database on the server
- Set up any relevant init.ora parameters

-- Setting up a Password File:
The password protection is controlled by an Oracle 'Password' file. To create a password file log in as the Oracle software owner and issue the command:

orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=mypasswd

using the required password. The file name is important and should specified as above. You should create this file when the database is shut down.

To change a password:
- shut down the database,
- Rename the $ORACLE_HOME/dbs/orapw$ORACLE_SID file
- Issue a new orapwd command with a new password

Alternatively, when the database is open use:

ALTER USER SYS IDENTIFIED BY &NEWPASSWORD;

This will propagate the (hashed) password to the existing password file.

-- Setting up the Init.Ora file To enable remote SYSDBA connections set the init.ora parameters thus:

Set REMOTE_LOGIN_PASSWORDFILE to either EXCLUSIVE or SHARED.
EXCLUSIVE forces the password file to be tied exclusively to a single instance. To disable remote internal connections set REMOTE_LOGIN_PASSWORDFILE to NONE.

NOTE: The setting of REMOTE_OS_AUTHENT does NOT affect the ability to connect AS SYSDBA from a remote machine.