ORA-01031 Insufficient privilege when connecting from client - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: ORA-01031 Insufficient privilege when connecting from client

  1. #11
    Join Date
    Dec 2001
    Location
    USA
    Posts
    620
    Hi Supower,

    Nope. It still does not work. I have 'Exclusive' in init.ora.

    I bounced the listener also.

    Still I am able to connect to sys as sysdba but with internal, it gives 'incorrect username/password' and with system, it gives 'insufficient privilege'.

    Pl. help.

    Thanks,
    Sam
    ------------------------
    To handle yourself, use your head. To handle others, use your heart

  2. #12
    Join Date
    Dec 2002
    Location
    USA
    Posts
    53
    I forgot you are in win2000. Please set
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    so you can locally connect to internal w/o passwd if you login in as oracle owner or local admin.

    There is security concern here, if set
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    and REMOTE_LOGIN_ PASSWORDFILE=exclusive in Wins.
    You can connect sys/ANYPASSWD@SID as sysdba.
    So oracle suggest that, if set
    SQLNET.AUTHENTICATION_SERVICES= (NTS) in Wins,
    set REMOTE_LOGIN_PASSWORDFILE=NONE to avoid remote connection as sysdba.
    Last edited by supower; 01-09-2003 at 10:57 AM.

  3. #13
    Join Date
    Dec 2001
    Location
    USA
    Posts
    620
    Hi Supower,

    Here is the situation.

    #SQLNET.AUTHENTICATION_SERVICES= (NTS) in sqlnet.ora.

    I had to recreate password file with internal password instead of sys because my database startup script stopped working as I am using internal for starting the DB.

    Now, I am able to connect internal as sysdba but not to sys as sysdba. So, what happens is whatever password I use in creating the oracle password file, it is able to connect as sysdba.

    Now even with commented SQLNET.AUTHENTICATION... I am not able to connect to sys or system as sysdba.

    I think the password file is more important here.

    What should I do now?

    Thanks,
    Sam
    ------------------------
    To handle yourself, use your head. To handle others, use your heart

  4. #14
    Join Date
    Dec 2002
    Location
    USA
    Posts
    53
    *******************************************
    Now, I am able to connect internal as sysdba but not to sys as sysdba. So, what happens is whatever password I use in creating the oracle password file, it is able to connect as sysdba.
    **********************************************

    It looks ok.

    **************************************
    Now even with commented SQLNET.AUTHENTICATION... I am not able to connect to sys or system as sysdba.
    ***************************************

    Did you shutdown oracle service when you create passwd file ?

    Try shutdwon database, shutdwon oracle service (wins), recreate passwd file, start oracle service, start db and
    sqL> alter user sys identifiy by PASSWD(same as your passwd file).
    Last edited by supower; 01-09-2003 at 11:49 AM.

  5. #15
    Join Date
    Dec 2001
    Location
    USA
    Posts
    620
    Hi Supower,

    After altering the SYS pwd as you said, now I am able to connect to internal and SYS both as sysdba but with system, it still gives 'insufficient privileges'. I altered SYSTEM password also but why it gives this error?

    Thanks for your help.
    Sam
    ------------------------
    To handle yourself, use your head. To handle others, use your heart

  6. #16
    Join Date
    Dec 2002
    Location
    USA
    Posts
    53
    If you set REMOTE_LOGIN_PASSWORDFILE=exclusive
    Grant sysdba to system;

  7. #17
    Join Date
    Dec 2001
    Location
    USA
    Posts
    620
    Hi Supower,

    Thank you very much.

    My problem got resolved with your help.

    I have also kept the SQL.AUTHENTICATION... in sqlnet.ora because without that it was giving problem in starting the database where I use connect internal/intpwd as sysdba;

    I did the foll. to fix the problem.

    1. Shutdown database, its services
    2. Rename existing password file.
    3. create the new password file with internal password.
    4. Connect to internal as sysdba.
    5. alter user sys identified by syspwd;
    6. grant sysdba to sys;
    7. alter user system identified by systempwd;
    8. grant sysdba to system;

    After this, I am now able to connect to sys and system as sysdba.

    Thanks a lot.
    Last edited by samdba; 01-09-2003 at 01:18 PM.
    Sam
    ------------------------
    To handle yourself, use your head. To handle others, use your heart

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width