what is password for internal user ?
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 9 of 9

Thread: what is password for internal user ?

  1. #1
    Join Date
    Apr 2001
    Posts
    21

    Angry

    Hi ,

    Finally i installed the Oracle on my Linux ( Mandrake Linux 7.1 ) box. After finishing the installation of software. I wanted to setup DB instance. I have all the DB Creation script & initsid.ora file. So when i tried connect using internal , i got error login denied :-

    --------------------------------------------------
    oracle@home$ svrmgrl

    Oracle Server Manager Release 3.0.5.0.0 - Production

    (c) Copyright 1997, Oracle Corporation. All Rights Reserved.

    Oracle8 Release 8.0.5.0.0 - Production
    PL/SQL Release 8.0.5.0.0 - Production

    SVRMGR> connect inernal
    Password:
    ORA-01017: invalid username/password; logon denied
    SVRMGR>

    ---------------------------------------------

    So i am surprised :-
    1. Why it is asking password. Becoz i did not set it up.
    2. How do i reset the password so i can create the db after doing connect internal.


    I tried resetting password using :

    orapwd file=pwdinternal.ora password=abcdef

    But even after doing this , when i try to connec to internal it does not accept the password abcdef

    Can somebody help here

    Thanks in advance.

    -DBKID

  2. #2
    Join Date
    Feb 2001
    Location
    Bombay,India
    Posts
    530
    Hi,
    the default password for internal is oracle.in ur init.ora file make the parameter REMOTE_LOGIN_PASSWORDFILE=exclusive

    In case of any help please be free to ask me at rohitsn@altavista.com


    regards,
    Rohit Nirkhe,Oracle DBA,OCP 8i
    rohitsn@altavista.com

  3. #3
    Join Date
    Apr 2001
    Posts
    21

    Still Doesn't like password.....

    Hi Rohit,

    I appriciate your quick reply. I added the parameter you asked in initsid.ora

    But it still doesn't like the password oracle or one i setup by orapwd utility.

    Just curious, clear me if i am wrong, Since i am new to oracle. If parameter REMOTE_LOGIN.. is not there in initsid.ora , then it is NONE, which means that it will not allow the SYSDBA SYSOPER prev user over unsecured connection. But since this task i am doing right on machine which host oracle db as oracle user. So it shouldn't ask me the password ?

    Another thing, when i say connect internal ( at this point i have not setup DB instance on this machine ) , why should it read initsid.ora ?

    thanks & regards

    -DBKID


  4. #4
    Join Date
    Mar 2000
    Location
    Chennai.Tamilnadu.India.
    Posts
    658

    Solution

    Hi, 19th May 2001 15:08 hrs chennai

    This link discusses several issues on connect internal in real time problems.

    http://otn.oracle.com/support/bboard/content/203.htm

    I am sure it may help you out.

    =====Another way without pwd this info for general idea==

    This also means that one can connect as 'INTERNAL'
    without a password, since the password for 'INTERNAL' and the database password are synonymous.

    In ORACLE.INI include the line:
    DBA_AUTHORIZATION=BYPASS

    Please note that this takes effect only on restarting each
    tool. To ensure this, exit Windows completely once, and restart everything.

    Cheers

    Padmam
    Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it

  5. #5
    Join Date
    Mar 2001
    Posts
    635
    Hi

    I see that you have typed it as

    connect inernal

    You should be typing it as

    connect internal

    You have missed out the T from there

    Anway later on you might have typed the correct username

    check weather the OS user from where you are connecting to the Internal user is part of the dba group.When the OS user is part of the dba group it will not prompt for the password when you connect to the Internal user.You can check the above in

    /etc/passwd

    Regards

    Santosh

  6. #6
    Join Date
    May 2001
    Posts
    41
    Originally posted by santoshym
    Hi

    I see that you have typed it as

    connect inernal

    You should be typing it as

    connect internal

    You have missed out the T from there

    Anway later on you might have typed the correct username

    check weather the OS user from where you are connecting to the Internal user is part of the dba group.When the OS user is part of the dba group it will not prompt for the password when you connect to the Internal user.You can check the above in

    /etc/passwd

    Regards


    Hi,
    why do you want to create the database from script,

    do the simple method just login to oracle installed user then type DBASSIST enter it will start one GUI menu from this you can create the N no of databases in that machine..


    This is for your information and necessary action..

    RAMESH GIRI .N

  7. #7
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    is your user oracle in the DBA group, and is the dba group defined as SYSOPER and SYSDBA ???

  8. #8
    Join Date
    Apr 2001
    Posts
    21

    Now ORA-00445 Error

    Thanks to all of you guys. I am sorry for writing internal incorrectly. But even after writing "internal" correctly it was not allowing me. So i reinstalled the whole thing. And it started working now. And i can do connect internal without any password.

    Now a new problem. Whenever i try to start the db instance:-

    start nomount
    it gives this error

    ORA-00445: background process PMON did not start after 120 seconds.

    Any idea ?

    - DBKID -

  9. #9
    Join Date
    Mar 2001
    Posts
    635
    Hi

    This is what metalink has to say about ur error if you have access to metalink login and check on the error number if not put ur email id in the thread I can send you a copy of that documentation

    The error explanation states:

    ORA-00445: background process did not start after seconds
    Cause: The specified process did not start.
    Action: Check and, if necessary, correct problems indicated by one or more of
    the following:
    -the size of the SGA
    -the operating system-specific initialization parameters
    -accompanying messages
    -the background trace file
    -the executable image is not in the right location with the
    correct protections.
    See also your operating system-specific Oracle documentation.

    Regards
    Santosh

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