Results 1 to 9 of 9
  1. #1
    Join Date
    Jan 2004
    Location
    Bangalore
    Posts
    25

    Unanswered: problem with connect internal

    Hi all,

    i am getting error when i try to connect as internal & here i am giving password as "oracle".Can u tell me password is "oracle" for internal or is there any password.

    SVRMGR> connect internal
    Password:
    ORA-01031: insufficient privileges


    can u give me the solution how to give the privileges for the error.

    thanks,
    clarify

  2. #2
    Join Date
    Jan 2004
    Posts
    99
    this is because a password file may have been setup, either recreate the password file or remove the remote_login_passwordfile parameter from the init.ora and restart the instance.

    ps. have you tried oracle as the password?

    good luck.

  3. #3
    Join Date
    Dec 2003
    Location
    Oklahoma, USA
    Posts
    354
    Also, so you know, after 8.1.7, the "internal" user name went away.

    JoeB

  4. #4
    Join Date
    Apr 2002
    Posts
    56
    I also thought that internal had gone.

    In the Oracle-supplied shell-scripts dbstart and dbshut on my Oracle 10g installation on linux the connection is still made using 'internal' though.

  5. #5
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    Hi Clarify,
    Just check whether the OS userid which u r using to log into that m/c belongs to ORA_DBA group.

    I assume that u r on the server and as I recall from ur previous posts .
    That u r on Oracle8 so Internal user is very well there.

    Last but not least u have the option of doing either of the two things as I mention below.

    1. Stop the OracleService and delete that using Oradim -delete -sid.
    Then recreate the service using Oradim utility where u have the option of providing the password for internal ie intpwd parameter.
    But before doing that make sure u delete the Pwd<sid>.ora file.

    OR.

    2. Stop the service and delete the password file Pwd<sid>.ora.
    Then recreate the password file using Orapwd utility.


    The syntax for both the utilities can be obtained from the command prompt.

    Kaushik

  6. #6
    Join Date
    Jan 2004
    Location
    Bangalore
    Posts
    25

    problem with connect internal

    Hi kausik,

    Thanks,for your help. Now its working i can do "connect internal"

    As per your reply i followed step 2. Its fine it went good.

    shall i query if any oracle error in future.

    Thanks
    clarify

  7. #7
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    Anytime ........................


    All the best
    Kaushik

  8. #8
    Join Date
    Jan 2004
    Location
    Bangalore
    Posts
    25

    OCI Call file

    Hi kausik,

    I am getting the oci call failed.The below is the log traces what i get in the log files:

    4 ETW000 [developertrace,0] Fri Apr 16 12:31:32 2004 1057417 1.487774
    4 ETW000 [dboci.c ,2420] *** ERROR => OCI-call 'olog' failed: rc = 1017
    4 ETW000 67 1.487841
    4 ETW000 [dboci.c ,6473] *** ERROR => CONNECT failed with sql error '1017'
    4 ETW000 41 1.487882

    help me out

  9. #9
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    I think Sky writer gave u some info in the other posts

Posting Permissions

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