This discussion is archived
5 Replies Latest reply: Oct 13, 2013 7:09 AM by TSharma-Oracle RSS

SYS user password change on Primary DB is NOT propogated to Standby DB

Sivaprasad S Newbie
Currently Being Moderated

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With Data Guard Physical Standby.

 

When changing the SYS user password on the Primary database, why is that change not propogated on the Standby database?

What is stopping this change?

How is that changes prevented on the standby?

Why is that prevented ?

 

What are the other changes on the Primary database, which are not propogated on the standby database ?

  • 1. Re: SYS user password change on Primary DB is NOT propogated to Standby DB
    vivalavida Journeyer
    Currently Being Moderated

    Hi ,

    the password of the user SYS is stored in the password file. That's the answer to most of your questions

    After changing the password in the primary database with "alter user sys identified by ..." you need to copy the password file to the standby site.

    Some other changes which are not propagated automatically are modifying the redo logs (create new redo logs, modify size of redo logs) or renaming/moving a datafile.

     

    HTH

    Jan

  • 2. Re: SYS user password change on Primary DB is NOT propogated to Standby DB
    saurabh Pro
    Currently Being Moderated

    When you change the sys password on the primary side. you need to copy the the password file from and replace it on the standby site.

  • 3. Re: SYS user password change on Primary DB is NOT propogated to Standby DB
    Anar Godjaev Expert
    Currently Being Moderated

    Hi

     

    VivaLavida telling the truth .

     

    Please check in Primary :

     

    SELECT status, error

    FROM V$ARCHIVE_DEST_STATUS

    WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';     Result  :  'ORA-01031: insufficient privileges

     

    And run step for OS command  (For example)

     

    bash-3.2$ scp /u01/app/oracle/product/11.2.0/db_1/dbs/orapwxxx1 Standby_ip:/u01/app/oracle/product/11.2.0/db_1/dbs/orapwxxx1

    Password:

    orapwxxx1         100% |**************************************************************************************************************************************************|  2048       00:00

     

    Problem solved

     

    OR:

     

    In Standby database please run :

     

    orapwd file=$ORACLE_HOME/dbs/orapw<local ORACLE_SID> password=<sys password> entries=5

     

    Thank you

  • 4. Re: SYS user password change on Primary DB is NOT propogated to Standby DB
    user12075536123 Pro
    Currently Being Moderated

    How about checking the following?

    SYS Password Management with RAC and Data Guard (DOCID 1267828.1)

  • 5. Re: SYS user password change on Primary DB is NOT propogated to Standby DB
    TSharma-Oracle Guru
    Currently Being Moderated

    The password for the sys user needs to be the same on the standby as the primary's when a remote login password file is used for redo transport authentication.

     

    That's why you need to copy the password file from the primary to the standby after changing the sys password on the primary database.

     

    However, the 11g database introduces a new init parameter REDO_TRANSPORT_USER which specifies the name of the user whose password verifier is used when a remote login password file is used for redo transport authentication. This user must have SYSOPER privileges and must have the same password in the database that initiates the redo transport session and in the database that is the target of the redo transport session.

     

    If this parameter is not specified, then the password verifier of the SYS user will be used when a remote login password file is used for redo transport authentication.

     

    Conclusion: As long as you specify REDO_TRANSPORT_USER to a user who has SYSOPER privileges on both the primary and the standby databases, then you don't need to copy the password file from the primary database to the standby database whenever you change the sys password on the primary database.

     

    SQL>GRANT SYSOPER to &USER;

     

    SQL>ALTER SYSTEM SET REDO_TRANSPORT_USER = <user_name> SID='*';

     

    The user you specified for REDO_TRANSPORT_USER must be an existing user in the database which exactly matches the value of the USERNAME column of a row in the V$PWFILE_USERS view and the value of the SYSDBA or SYSOPER column of the row must also be TRUE.

     

    If you need to change the password for the user specified in REDO_TRANSPORT_USER, then you would need to copy the password file from the primary to the standby site.


    Source: Re: Change user name and password of both Primary and DR instance

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points