password file
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: password file

Hybrid View

  1. #1
    Join Date
    Jul 2000
    Location
    india
    Posts
    213
    Hi everybody
    How do i know that the password file is present in my database OR How do i create a password file.
    When i query i got the follo error...should i have to create a password file...or is the follo error is related with the password file...

    SQL> desc SYS.V_$PWFILE_USERS
    Name Null? Type
    ------------------------------- -------- ----
    USERNAME VARCHAR2(30)
    SYSDBA VARCHAR2(5)
    SYSOPER VARCHAR2(5)

    SQL> select * from SYS.V_$PWFILE_USERS;
    ERROR:
    ORA-00600: internal error code, arguments: [KSSRMP1], [], [], [], [], [], [], []



    no rows selected

    SQL>

    Pls help...
    thanks in advance
    pras

  2. #2
    Join Date
    Feb 2001
    Location
    Bombay,India
    Posts
    530
    Hi.
    There is a known bug in Oracle when u try to query against v$pwfile_users.

    In order to see the contents of v$pwfile_users fire the following query.Login in svrmgr or sqlplus as sys as sysdba and enter the following query

    svrmgr> select * from v$pwfile_users order by 1;

    U can see whether password is present by looking in dbs directory.Oracle creates a password file in $ORACLE_HOME/dbs directory with the name passwd.ora

    If u want to create a password file use the follwoing syntax.
    In UNIX
    $orapwd file= password= entries=n

    In Windows NT
    c:\>orapwd80 file=
    password= entries=n max users having sysdba and sysoper roles>


    If u have already have a password file remove it and then create a new one using the above give command.




    Regards,
    ROhit Nirkhe,Oracle DBA,OCP 8i
    rohitsn@altavista.com

  3. #3
    Join Date
    Jul 2000
    Location
    india
    Posts
    213
    Hi rohit
    Thank you for ur help.
    The password file i created will it change the previous passwords for the SYS and INTERNAL...cause after creating the password file i am still able to connect with the previous passwords.
    Thanks again
    pras

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

    Solution

    Hi, 16th May 2001 17:04 hrs *******

    Delete physically the old pwd file.

    Cheers

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

  5. #5
    Join Date
    Jul 2000
    Location
    india
    Posts
    213
    Hi
    rohit and padmam,
    this is the problem i faced..first i physically deleted the password file..then i queried the view v_$pwfile_users thru the svrmgr and i got the feedback as no rows selected...then i connect thru the sql and i got connected as sys and its old password...
    then i created the new password file thru orapwd80 the password file get created successfully and then i queried the view v_$pwfile_users thru the svrmgr it shows me two rows selected..then again i connect thru the sql and i got connected as sys and its old password...
    now my question is after creating the newpassword file will it change the old password or retain it..
    any feedback from all will be appreciated.
    and padmam i am also waiting for the result of ur investigation on the AUDITING..
    thanks and regards
    pras

  6. #6
    Join Date
    May 2000
    Location
    Delhi
    Posts
    108

    Talking changing internal password

    Dear Prash

    You MUST be logged into the Windows NT system as the user
    Administrator -OR- a user within the Windows NT Administrative Group with full administrative rights to perform the following steps.

    I) Usage
    a) Connecting Without a Password
    b) Password file
    c) ORAPWDxx
    d) Adding & Removing users to the password file
    e) Listing users recorded in the password file
    f) Resetting/Changing the password of the user internal
    g) Updating Windows NT registry when password file moved or renamed
    h) Finding back the internal password (7.3.4 - 8.0.x)

    II) Most Common Problems
    1) OPW-00005: File with same name exists - please delete or rename
    2) ORA-1017 or ORA-1031 when trying to connect as internal
    3) ORA-1996 when trying to grant sysdba or sysoper to user
    4) By default in 8.1.x, a new database will use Windows NT Native
    Authentication by having the following already set in the
    sqlnet.ora file.

    Usage
    -----

    Connecting as internal or sysdba/sysoper can be setup in 2 different ways:

    - to connect without the necessity to provide a password
    - to connect with the necessity to provide a password


    a) Connecting Without a Password:
    ------------------------------

    [NOTE:77665.1] :WINNT Connecting Without a Password as a Privileged
    Database User


    b) Password file:
    -------------

    When the "init.ora file" parameter remote_login_passwordfile is set to EXCLUSIVE or SHARED, Oracle can have a password file to maintain

    - the password of internal
    - the list of users and their passwords that have been granted administrator privileges

    The name of the password file has the format: "pwd.ora" and is situated by
    default in the \Database-directory.

    The password is automatically created in the \Database
    directory when an instance is created with the instance manager
    ORADIMxx.

    For example (8.1.5):
    D:\> ORADIM -new -sid ORCL -intpwd ORACLE -startmode auto
    -pfile d:\orant\database\initorcl.ora

    will automatically create a file

    D:\ORANT\DATABASE\PWDORCL.ORA


    c) ORAPWDxx
    --------

    ORAPWDxx is a specific command-line utility for password file creation.
    ORAPWDxx is automatically installed with the RDBMS utilities


    SYNTAX:
    ------

    When you type ORAPWDxx at the DOS-prompt, it will enlist the syntax
    to use it.

    D:\> ORAPWDxx
    Usage: orapwd file= password= entries=

    where
    file - name of password file (mand),
    password - password for SYS and INTERNAL (mand),
    entries - maximum number of distinct DBA and OPERs (opt),
    There are no spaces around the equal-to (=) character.

    File:
    this option lets you specify the name of the password file. It should
    containt the full path, \DATABASE, and be of this format
    PWD.ORA. Its content is encrypted.

    Password:
    sets the password for internal.

    Entries:
    specifies the maximum number of distinct SYSDBA and SYSOPER USERS

    Example (8.1.5):
    D:\> ORAPWD file=D:\ORANT\DATABASE\PWDORCL.ORA password=ORACLE


    d) Adding & Removing users to the password file:
    --------------------------------------------

    Adding users to password file is done by granting them the sysdba or
    sysoper system privilege.

    SVRMGR> grant sysdba to system;
    SVRMGR> grant sysoper to test_user;
    SVRMGR> grant sysoper to test_user2;

    Removing users from the password file is done by revoking the
    correspondig priviliges from the specific users;

    SVRMGR> revoke sysoper from test_user2;


    e) Listing users recorded in the password file:
    --------------------------------------------

    There is a view defined in the database that will give you the list
    of the users recorded in the password file: v$pwfile_users.


    SVRMGR> describe v$pwfile_users;
    Column Name Null? Type
    ------------------------------ -------- ----
    USERNAME VARCHAR2(30)
    SYSDBA VARCHAR2(5)
    SYSOPER VARCHAR2(5)

    SVRMGR> select * from v$pwfile_users;
    USERNAME SYSDB SYSOP
    ------------------------------ ----- -----
    INTERNAL TRUE TRUE
    SYSTEM TRUE FALSE
    TEST_USER FALSE TRUE

    [BUG:425862] : ORA-600 [1113] SELECTING FROM V$PWFILE_USERS


    f) Resetting/changing the password of the user internal:
    ----------------------------------------------------

    There are 3 common ways to change to password of internal:

    1) Recreate the passwordfile (Read Warning 1 & 2):

    You can recreate the password file using the ORAPWDxx command by which you can
    specify the password for internal. Before running this command to create the
    new password file, make sure to delete the old password file. Otherwise, the
    ORAPWDxx utility will give an error message.

    D:\> ORAPWD file=D:\ORANT\DATABASE\PWDORCL.ORA password=
    entries=5

    Verify if the new file has been created.

    The passwordfile might be hidden. Hidden files can be seen:
    on the DOS-prompt by type :
    c:\> dir /A:H
    in Windows NT explorer :
    use the Windows Explorer View/Option 'show all files' to see the
    file.


    Remark:
    -------

    If the value of the "remote_login_passwordfile" parameter in the "init.ora" is
    EXCLUSIVE then you must shutdown your database before recreating the password
    file.

    Failure to do so will result in being unable to connect as internal as long as
    you don't stop the database by for example stopping services.

    2) Alter the password of the user 'SYS' (Read Warning 1)

    a) Verify the values of the "remote_login_passwordfile" in the
    "init.ora" parameter file.

    If its values is exclusive continue with e) if Shared continue with b)

    b) Stop the database if it is started

    c) Change the "remote_login_passwordfile" in the Init.ora to
    "exclusive".

    d) Startup the database.

    e) Alter the user SYS to a new password, now also the password for
    internal.

    3) Use ORADIMxx (Read Warning 2)

    You could drop the instance and recreate it with a new password.

    Suppose the SID in question is ORCL:

    a) You shutdown the database and stop the services.

    b) D:\> ORADIMxx -delete -sid ORCL

    c) D:\> ORADIMxx -new -sid ORCL -intpwd -startmode
    auto -pfile D:\ORANT\DATABASE\INITORCL.ORA

    -----------
    WARNING
    -----------

    1) (Methods 1 and 2) Changing the password of the internal might prevent
    your database from starting up automatically in Oracle7 7.3.x and Oracle8
    8.0.x. . When you create your instance with the instance manager and
    configure it to startup automatically.

    (ORADIMxx -new -sid ORCL -intpwd ORACLE -startmode AUTO -pfile
    D:\ORANT\DATABASE\INITORCL.ORA),

    a file \DATABASE\strt.cmd is generated. That file contains
    (hardcoded) the password of internal. If the password in there does not match
    the actual password of internal, the instance will fail to startup
    automatically.

    When you change the password of internal in one of the above described ways and
    if you still want your database to start up automatically, you need to adjust
    the password manually.

    2) Methods 1 and 3 can result in loosing all previously registered sysdba
    and sysoper-users. If you had granted specific users those privileges again,
    you will need to grant it again.


    g) Updating Windows NT registry when password file moved or renamed
    ----------------------------------------------------------------

    You either renamed or moved your password file. The Registry has an
    entry to denote the password file. When the file is moved or renamed
    the Registry must be updated.


    Solution Description:
    =====================

    CAUTION:
    Editing the REGISTRY could cause severe damage to Windows NT.
    If you are not familiar with the Registry, please consult with your System
    Administrator. A damaged registry could require a complete reload of the NT
    Operating System.

    1. Run REGEDT32.EXE to open the Registry.

    2. Click on the HKEY_LOCAL_MACHINE on Local Machine hive.

    3. Click on the SOFTWARE folder.

    4. Click on the ORACLE folder.

    If the database is created in the default home, skipt step 5.

    5. If the database is not created in the default home, but in HomeXX
    (XX is a number from 1 to the number of homes installed on your Server)
    Click on the HomeXX folder.

    6. Update or Create ORA__PWFILE (where is the database SID).
    String with the correct name and path of the password file.
    After changing the registry entry, the OracleService service will
    need to be stopped and restarted for the change to take affect.


    Solution Explanation:
    =====================

    The HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORA__PWFILE or
    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HomeXX\ORA__PWFILE
    registry entry is used to store the name and location of the password file.


    h) Finding back the internal password (7.3.4 - 8.0.x)
    --------------------------------------------------

    When you're using Oracle 7.3.4 or 8.0.x, the ORADIMxx command
    creates the password-file: pwd.ora that contains the encrypted
    internal password. If you're using the automatic startup option
    (-startmode auto), there is also a file strt.cmd created that
    contains the not-encrypted password of internal.



    II) Most Common Problems
    --------------------

    1) You're trying to recreate the Password file with ORAPWDxx and
    you get the following error:

    D:\> ORADIMxx file=D:\ORANT\DATABASE\PWDORCL.ORA password=ORACLE

    OPW-00005: File with same name exists - please delete or rename

    Solution:
    There is already a file with the same name in the specified
    directory. Remove or rename that specific file, before creating the
    new one.

    The passwordfile might be hidden. Hidden files can be seen:
    on the DOS-prompt by type :
    c:\> dir /A:H
    in Windows NT explorer :
    use the Windows Explorer View/Option 'show all files' to see the
    file.

    2)ORA-1017 or ORA-1031 when trying to connect as internal

    [NOTE:114399.1] : WINNT: ORA-1017 WHEN CONNECTING AS INTERNAL ON NT
    [NOTE:114401.1] : WINNT: ORA-1031 WHEN CONNECTING AS INTERNAL ON NT

    3) ORA-1996 when trying to grant sysdba or sysoper to user

    : OERR ORA 1996 GRANT failed password file is full
    : ORA-1994 WHEN GRANTING SYSDBA TO A USER

    You must create a larger password file to be able to contain more entries
    and re-grant the privileges to all of the users.

    4) By default in 8.1.x, a new database will use Windows NT Native
    Authentication by having the following already set in the "sqlnet.ora" file:

    SQLNET.AUTHENTICATION_SERVICES = (NTS)

    This will allow any privileged user defined in the NT user group (named
    ORA__DBA) to login to database without providing a password. To disable
    this feature and force all users to provide a password, simply comment out
    the above in the sqlnet.ora file:

    #SQLNET.AUTHENTICATION_SERVICES = (NTS)

    Bye
    i think it will helpful for you
    Abhishek


  7. #7
    Join Date
    May 2001
    Location
    India
    Posts
    55

    Arrow password file

    Hi,

    first of you have set the oracle sid then create the password file.

    Here I given the steps for how to creating password file, you shoud follow the same way :

    Example :

    1. set oracle_sid=orcl

    2. orapwd file=d:\oracle\database\dbs\orclpwd.ora password=oracle entries=10


    this is the way to create password file.

    If you any doubt in this, mail me,

    my id is shankar_gk@hotmail.com,shankar_gk@usa.net

    Bye,


    G.shankar.


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