As far as I know, it works like this:
You will need to set init parameter REMOTE_LOGIN_PASSWORD_FILE to EXCLUSIVE.
You then can sign on as SYS remotely, or as another user remotely if the other user has SYSDBA. See the users that have SYSDBA or SYSOPER in v$pwfile_users.
As the view name suggests, you will also need a password file for the database, which should be created with the orapwd utility.
$ orapwd
Usage: orapwd file=<fname> password=<password> entries=<users>
where
file - name of password file (mand),
password - password for SYS and INTERNAL (mand),
entries - maximum number of distinct DBA and OPERs (opt),
There are no spaces around the equal-to (=) character.
Once you've done all that, you can connect remotely by saying the following in SQL*Plus:
connect sys/[EMAIL PROTECTED] as sysdba
But I don't think you will ever be able to do
connect / as sysdba remotely. For one thing, the syntax in SQL*Plus is:
Syntaxe : CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
ou <logon> ::= <username>[/<password>][@<connect_string>] | /
So the logon is either username/[EMAIL PROTECTED] or else "/" all by itself. How would you tell SQL*Plus which remote database you want to connect to? I tried setting TWO_TASK to the tns_alias for the database, but that didn't help. It seems to me that when you enable remote SYSDBA logins Oracle will insist on verifying a password for the SYSDBA user in the password file.
Or is there some clever trick I don't know about?
> -----Original Message-----
> From: [EMAIL PROTECTED]
>
> env: Oracle 9.2.0.2 on Solaris 9.
>
> Does anyone know of a way to use the "/ as sysdba" logon remotely?
> (to a separate Oracle instance on a separate machine)
>
> Other remote user logons work OK.
>
> I have tried several variations from sqlplus, such as
>
> [EMAIL PROTECTED]>connect /@DWQ as sysdba
> ERROR:
> ORA-01031: insufficient privileges
>
> Warning: You are no longer connected to ORACLE.
>
> [EMAIL PROTECTED]>connect sys/[EMAIL PROTECTED] as sysdba
> ERROR:
> ORA-01017: invalid username/password; logon denied
>
> [EMAIL PROTECTED]>connect sys/exr_sys as [EMAIL PROTECTED]
> SP2-0306: Invalid option.
> Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
> where <logon> ::= <username>[/<password>][@<connect_string>] | /
>
> [EMAIL PROTECTED]>connect sys/[EMAIL PROTECTED]
> ERROR:
> ORA-28009: connection to sys should be as sysdba or sysoper
>
> I also find I cannot even "connect sys/syspassword" locally:
>
> [EMAIL PROTECTED]>connect sys/sys_password
> ERROR:
> ORA-28009: connection to sys should be as sysdba or sysoper
>
> This does work locally, but not remotely:
>
> [EMAIL PROTECTED]>connect sys/sys_password as sysdba
> Connected.
>
> I am a member of the dba group on both platforms.
>
> I have verified that I am using the correct sys_password for sys
> on the remote instance.
>
> Eventually, I want to do a remote transportable tablespace
> import, where
> the userid would be listed in a parfile; I have tried the
> same logons in
> a parfile, and that also fails.
>
> I found a Metalink doc that says the O7_DICTIONARY_ACCESSIBILITY (sp?)
> must be true to do this, but the same doc strongly advises
> against setting
> this to true.
>
> So, has anyone found a way to use the "/ as sysdba" logon remotely?
> (without setting the O7 parameter to true)
