The title represents the meaning of using the operating system for local authentication, generally not, there is a security issue. It is usually necessary to change to the following value: Sqlnet. Authentication_services= (NONE) 1. This does not allow the use of the operating system for local authentication, for example: C:\>sqlplus/nolog Sqlplus>connect/as SYSDBA Error:ora-01031:insufficient Privileges 2. If so set: sqlnet.authentication_services= (NTS) The effect is as follows: C:\>sqlplus/nolog Sqlplus>connect/as SYSDBA Connected Note: The above premise requires that the current login user must be in the ORA_DBA group. As shown in the following: 3. Oracle client, Sqlnet. The Ora file is generated after the local naming method is configured, note that the network service name is not configured. Net Configuration assistant--> Second local naming method---> Local 4. If there is more than one instance of the current system, which instance is connected to? Check registry: Hkey_local_machine/software/oracle/homeo related content, found missing Oralce_sid item After trial: If the database has more than two instances, after using DBCA to delete an instance, The system will also remove the ORACLE_SID entry for the registry, resulting in a failure to perform connenct/as sysdba. After the associated ORALCE_SID item is added to the registry, the execution Sql> conn/@orcldb as SYSDBA (same as connect/@orcldb as SYSDBA) is connected. 5. Disconnecting the current connection Sqlplus>disconn 6. Querying the currently used DB instance Sqlplus>select name from V$database; NAME ----------------------------------- Orcldb Attention: V$xxxx is the name of the dynamic performance view, or the Oracle Digital Dictionary view. V$ the beginning of the general is used by the DBA user, ordinary users want to use, to use the grant Select any dictionary to give the query data dictionary permissions |