Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2004
    Posts
    796
    Provided Answers: 1

    Unanswered: Re-creating the password file

    The pwd file for one of my databases was set up with the parameter "entries=5". I now need to increase the number of users that can log on as sysdba to more than 5, & the only way I can see how to do this is to delete the old pwd file & create a new one, using orapwd.

    As remote_login_passwordfile is already set to 'exclusive', I reckon that all I need to do is to delete the old file, create the new one, & stop/restart the database.

    My question is: Are there any pitfalls to be aware of? (I don't fancy deleting the old file & then finding that I've missed a step!).
    90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.

  2. #2
    Join Date
    Apr 2004
    Posts
    35

    Arrow deleting is the only option

    yes deleting the password file and recreate it.
    see asktom.oracle.com for a good description on this issue.
    i have read it few days back only.


    skg
    9i ocp

  3. #3
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    1) Recreate the passwordfile

    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=<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<SID>.ora to
    "exclusive".

    d) Startup the database.

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

    3) Use ORADIM

    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:\> ORADIM -delete -sid ORCL

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

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

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

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

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

    D:\> ORADIM 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] <ml2_documents.showDocument?p_id=114399.1&p_databa se_id=NOT> : WINNT: ORA-1017 WHEN CONNECTING AS INTERNAL ON NT
    [NOTE:114401.1] <ml2_documents.showDocument?p_id=114401.1&p_databa se_id=NOT> : WINNT: ORA-1031 WHEN CONNECTING AS INTERNAL ON NT

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

    <Note.19282.1> : OERR ORA 1996 GRANT failed password file <name> is full
    <Note.1032464.6>: 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_<sid>_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)

    HTH
    Gregg

  4. #4
    Join Date
    Jun 2004
    Posts
    796
    Provided Answers: 1
    Thanks for that.
    90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.

Posting Permissions

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