SYS connect

[hamhey]

Hi all,
I've configured password file with orapwd and I have problem when connecting with sys :
sqlplus sys/sys_password@service_name

any idea what's wrong.

//Hamhey

[Tarry]

And if you append your connection with --as sysdba then you can connect?

[hamhey]

Hi,
Connection with niether of
sqlplus sys/change_on_install@service_name
sqlplus sys/change_on_install@service_name as sysdba
are not possible

//Hamhey

[abhaysk]

If you are trying to connect to DB as SYSDBA from the server where DB exist, then Password File is of no use.

If from Client you want to make connection to DB as SYSDBA, then Password file will be of use..

Where are you connecting from, if at server side,
conn / as sysdba is enough.

Provided the user (OS) is in the ORA_DBA group & SQLNET authentication mode is NTS.

Abhay.

[TomazZ]

Originally posted by abhaysk
If you are trying to connect to DB as SYSDBA from the server where DB exist, then Password File is of no use.

Sure it is.
You cannot connect like "user/pass@db as sysdba" without a password file.

Hamhey, what responses do you get on those connects?

[hamhey]

Hi
Well, I have a password file and connecting as other users defined as sysdba in the password file are able to be connected like:

test/pass@service_name
connect test/pass as sysdba

which I would prefer without connect test/pass
to connect to RMAN catalog for instance.

and the user sys/change_on_install cannot connect to database even with password file using:

sqlplus sys/change_on_install@service_name

//Hamhey

[TomazZ]

Originally posted by hamhey
and the user sys/change_on_install cannot connect to database even with password file using:

sqlplus sys/change_on_install@service_name

What is the error message?

[akhadar]

C:\>SVRMGRL

Oracle Server Manager Release 3.1.7.0.0 - Production

Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.

Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production

SVRMGR> CONNECT AKHADAR AS SYSDBA
Password:
Connected.
SVRMGR> SELECT * FROM V$PWFILE_USERS;
USERNAME SYSDB SYSOP
------------------------------ ----- -----
INTERNAL TRUE TRUE
SYS TRUE TRUE
AKHADAR TRUE TRUE
TEST TRUE FALSE
4 rows selected.
SVRMGR> DISCONNECT
Disconnected.
SVRMGR> EXIT
Server Manager complete.

C:\>rman target / nocatalog

Recovery Manager: Release 8.1.7.0.0 - Production

RMAN-06005: connected to target database: RICT (DBID=148945032)
RMAN-06009: using target database controlfile instead of recovery catalog

RMAN> exit

C:\>rman target akhadar@rict nocatalog
target database Password:

Recovery Manager: Release 8.1.7.0.0 - Production

RMAN-06005: connected to target database: RICT (DBID=148945032)
RMAN-06009: using target database controlfile instead of recovery catalog

RMAN> exit


--Observe now as i commented out the SQLNET.AUTHENTICATION_services=NTS in SQLNET.Ora

C:\>rman target / nocatalog

Recovery Manager: Release 8.1.7.0.0 - Production

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: ORA-01031: insufficient privileges

Don't worry about catalog as iam using controlfile itself as catalog for test purpose.

So check your sqlnet.ora both on your seperate catalog database and also target database.

u have not followed the link which i posted in other thread.When u are connecting to RMAN with a user having SYSDBA privileges u need not mention specifically as SYSDBA while connecting.

Noteon't duplicate your questions in multiple threads.Stick to one post.As u are making other members confused with your incomplete questions.

[abhaysk]

Originally posted by TomazZ
Sure it is.
You cannot connect like "user/pass@db as sysdba" without a password file.

If you have read my post completely, i mentioned

"Provided the user (OS) is in the ORA_DBA group & SQLNET authentication mode is NTS."

Abhay.

[TomazZ]

Still, you cannot connect like "user/pass@db as sysdba" without a password file.