Bequeath (BEQ) protocol happens only when the client you're running is on the same box as the database. You must be logged in to the database server to utilize bequeath. Normally, when you connect from a remote client, or even on the database server when you specify a service name, i.e. user/password@mydb, you're connecting via SQL*Net. Your client program contacts a listener, the listener spawns a server process on your behalf, and hands off the connection. In the case of bequeath, the listener is out of the loop. When you connect on the local database server, without a service name, you're doing a bequeath connection. You directly start the server process, and the listener is not involved in the connection. Hope that helps, -Mark ________________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of sundar mahadevan [sundarmahadevan82@xxxxxxxxx] Sent: Tuesday, September 22, 2009 21:51 To: Oracle-L@xxxxxxxxxxxxx Subject: Re: SQLNET.AUTHENTICATION_SERVICES = (NONE) results in ERROR: ORA-01031: insufficient privileges Thanks Mark. SQLNET.AUTHENTICATION_SERVICES=(BEQ,NONE) works perfect. I came across BEQ earlier on some forums but learnt from it that BEQ means bequeath protocol. I would appreciate if anyone could explain more about BEQ ? Thanks to one and all for helping me out........ -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l