If you are using Unix, here are some steps that you should accomplish:
A) Checking what the prefix is set to:
svrmgr> connect internal
Connected.
svrmgr> show parameter os_authent_prefix
NAME TYPE VALUE
----------------------------------- ------- ------------------------------
os_authent_prefix string
svrmgr> exit
B) Since the prefix value was blank, let's check to be sure OPS$ logins are
turned on!
% cd $ORACLE_HOME/dbs
% grep os_auth initV713.ora
initV713.oras_authent_prefix="" <----no prefix is used
initV713.ora:remote_os_authent=true <----OPS$ Logins are turned on
C) Setting up a user to be able to use OPS$ logins. The user already exists
with a Unix userid of 'query'.
% sqlplus system/manager
svrmgr> create user query identified externally;
svrmgr> grant connect to query;
svrmgr> exit
Note that if os_authent_prefix was set to 'ops$' you would have to say:
svrmgr> create user ops$query identified externally;
Can you post your connections and errors while trying to connect via svrmgr30 to better understand your requirement?
Here's additional info on OS authentication in NT:
If you can access metalink, I suggest you to read Note:77665.1 and Note:60634.1
Here's a part of that Note:
I. Connecting Without a Password as a Privileged Database User
===========================================================
CONNECT / AS SYSOPER
-or-
CONNECT / AS SYSDBA
Verify that your MS Windows NT Local or Domain User Account that you use to
administer the Oracle Instance/Database belongs to one of the following four
MS Windows NT Local Groups on the MS Windows NT Server/Workstation:
Local Group Explanation
----------- -----------
ORA_OPER SYSOPER database privileges, for all instances
ORA_DBA SYSDBA database privileges, for all instances
ORA_<SID>_OPER SYSOPER database privileges, for the specified instance only
ORA_<SID>_DBA SYSDBA database privileges, for the specified instance only
REMARK:
Use Server Manager (SVRMGRxx) to connect as SYSOPER and SYSDBA without a
password. SQL*Plus and the Oracle Enterprise Manager Console cannot be used for
this type of connection. On the other hand, Oracle Enterprise Manager
Administration Tools such as Instance Manager, can be used to establish this
connection.
A. Authentication Tasks on the Server
----------------------------------
1. Create a new Local Group on the Database Server and name it according to
the privilege group you want to create.
e.g. ORA_ORCL_DBA -or- ORA_DBA
2. Add the MS Windows NT User Account to the Local Group using User
Manager/User Manager for Domains.
3. Verify SQLNET.ORA has SQLNET.AUTHENTICATION_SERVICES = (NTS) set.
If this parameter is commented out with a '#', remove the '#'.
The default directory for this file is:
Version 7 - %ORACLE_HOME%\NETWORK\ADMIN
Version 8 - %ORACLE_HOME%\NET80\ADMIN
B. Authentication Tasks on the Client
----------------------------------
1. Verify SQLNET.ORA has SQLNET.AUTHENTICATION_SERVICES = (NTS) set.
If this parameter is commented out with a '#', remove the '#'.
The default directory for this file is:
Version 7 - %ORACLE_HOME%\NETWORK\ADMIN
Version 8 - %ORACLE_HOME%\NET80\ADMIN
2. Log on to the client machine using the Local or Domain User Account.
3. Start Server Manager (SVRMGRxx). In the following examples <SERVICE_NAME>
is the client SQL*Net/Net8 alias that you use to connect to the Oracle
Database.
Method 1 (Oracle8 v8.0.5 Release used)
--------
C:\>SVRMGR30
Oracle Server Manager Release 3.0.5.0.0 - Production
(c) Copyright 1997, Oracle Corporation. All Rights Reserved.
ORA-12203: TNS:unable to connect to destination
SVRMGR> set instance <SERVICE_NAME>
Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production
PL/SQL Release 8.0.5.2.0 - Production
Instance <SERVICE_NAME>
SVRMGR> connect / as sysdba
Connected
-or-
SVRMGR> connect / as sysoper
Connected
Remark: The ORA-12203 error as shown above is intended behavior since
you did not specify an instance to connect to yet.
Method 2 (Oracle8 v8.0.5 Release used)
--------
C:\>set local=<SERVICE_NAME>
C:\>SVRMGR30
Oracle Server Manager Release 3.0.5.0.0 - Production
(c) Copyright 1997, Oracle Corporation. All Rights Reserved.
Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production
PL/SQL Release 8.0.5.2.0 - Production
SVRMGR> connect / as sysdba
Connected
-or-
SVRMGR> connect / as sysoper
Connected
But if you only want OS authentication for non-priv users, you need only to do the following plus the steps I gave you in UNIX OS:
1) Install and configure SQL*Net version 2.3.4 or Net*8 on clients and servers:
- The Windows NT authentication adapter is automatically installed on
both clients and server.
- For both clients and server, add the following entry to the
SQLNET.ORA file or remove the comment-mark '#':
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.