About ORAPWD
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: About ORAPWD

  1. #1
    Join Date
    Jul 2000
    Posts
    10
    Is the REMOTE_LOGIN_PASSWORD parameter valid in Init.ora !?

    I read a book saying that you need to assign the password file
    to the INIT.ORA variable REMOTE_LOGIN_PASSWORD.

    Please advice me. Thanks

  2. #2
    Join Date
    Sep 2000
    Posts
    33
    Yes it is necessary.

    If you are using Database Authentication then REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE

    It is also necessary when you want to give SYSDBA priviledge to other users.

  3. #3
    Join Date
    Jul 2000
    Posts
    10
    The problem is that when I use the ORAPWD to create my password file for the SYS and INTERNAL,
    how can I use the password file for my database authentication !?

    let's say, I type the follow command :

    orapwd80 file=c:\ownpass.dat password=abc123

    After this, the ownpass.dat file will be created,
    when I add the line "REMOTE_LOGIN_PASSWORD=c:\ownpass.dat" in the init.ora, when I restart the server, it said
    "INVALID REMOTE_LOGIN_PASSWORD parameter".

    Pls advice me.
    Thanks.


  4. #4
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    the values for REMOTE_LOGIN_PASSWORD are

    NONE, SHARED, EXCLUSIVE

    since you are not using any of these, instead you are using the file name that is why Oracle is complaining about this parameter.

    To use parameter file you should set

    REMOTE_LOGIN_PASSWORD=SHARED or

    REMOTE_LOGIN_PASSWORD=EXCLUSIVE

    any of these 2 would work

  5. #5
    Join Date
    Nov 2000
    Posts
    26
    hi,
    looks like u are a bit confused here, the orapwd utility as already explained by pando takes three values one none- the password file is not required this would be the case when u are connecting to the database externally, like what we do here, the next one is 'shared' which is available on oracle parallel server, but this constrains users to use only 'sys' or 'internal' to connect to the database with sysdba previleges, the last one is 'exclusive' this value allows for users who are granted the priveleges of 'sysdba' or 'sysoper' by the internal or sys user, (u could verify this in the view 'v$pwfile_users'), then those users could connect to the database with 'sysdba' or 'sysoper' priveleges and they would be connecting to the sys schema, be very very cautious when using this feature, if compromised it could well be uer waterloo!!!
    cheers,
    soren

  6. #6
    Join Date
    Nov 2000
    Posts
    79

    error while seleting from v$pwfile_users

    I can't understand this.
    If anybody can suggest


    SQL> select * from v$pwfile_users;
    ERROR:
    ORA-00600: internal error code, arguments: [KSSRMP1], [], [], [], [], [], [], []

  7. #7
    Join Date
    Dec 2000
    Posts
    9
    I believe that it's a bug. What version are you running?

    A workaround is using:

    select * from v$pwfile_users order by 1;

    Don't ask me why that works.

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