This discussion is archived
1 2 3 4 Previous Next 57 Replies Latest reply: Oct 17, 2013 3:43 AM by BluShadow Go to original post RSS
  • 15. Re: Standby Gaps after changing sys password
    Anar Godjaev Expert
    Currently Being Moderated

    NO. connect Primary OS (root user ) and run :

     

    1)

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

    Password:

    orapwXXXXX1         100% |**************************************************************************************************************************************************|  2048       00:00 

     

    2)

    And please run sql query again: (in Primary)

     

    SELECT status, error

    FROM V$ARCHIVE_DEST_STATUS

    WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';

     

    Thank you

  • 16. Re: Standby Gaps after changing sys password
    MahirM.Quluzade Guru
    Currently Being Moderated

    Can I run  at primary server > sqlplus sys/passwd@standby as sysdba ? to test if I can connect using the password file?


    Yes, This connection is using password file of standby ,

  • 17. Re: Standby Gaps after changing sys password
    yxes2013 Newbie
    Currently Being Moderated

    Hi all,

     

    At primary, I run >  sqlplus sys/password@proddr as sysdba

     

    And I was able to connect using the new password, so the orapwPRODDR works.

     

    So what is this

    STATUS    ERROR

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

    VALID

    ERROR     ORA-01031: insufficient privileges

     

     

    I have not backed up my orapw file

     

    Please help...

  • 18. Re: Standby Gaps after changing sys password
    CKPT Guru
    Currently Being Moderated

    Hi,

     

    once you copied the password file you can also check the view for reference, v$pwfile_users

    Later you can perform the connectivity from primary to stndby using TNS service.. and vice versa.

    From Primary: sqlplus sys/****@standby as sysdba

    From Standby: sqlplus sys/****@primary as sysdba

     

    After that perform couple of log switches on primary and check the errors in alert log or using below query relate to authentication

    select severity,error_code,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') "timestamp" , message from v$dataguard_status where dest_id=2;

  • 19. Re: Standby Gaps after changing sys password
    Anar Godjaev Expert
    Currently Being Moderated

    Hİ,

     

    You can check this step:

     

    Maybe you should do it in Secondary database:  orapwd file='..\dbs\orapwxxx.ora password=XXXXX entries=5 force=y

     

    Thank you

  • 20. Re: Standby Gaps after changing sys password
    MahirM.Quluzade Guru
    Currently Being Moderated

    Yxes2013 you  must use same password file for all  databases in Data Guard configuration.

    If you changed SYS or REDO_TRANSPORT_USER password, you msut copy changed password file to all standby  databases.

     

    You not need backup of password file. You  need copy to standby priamry's password file. That is all.

  • 21. Re: Standby Gaps after changing sys password
    Asif Muhammad Guru
    Currently Being Moderated

    Hi,

     

    I have not backed up my orapw file

    It is always a MUST you backup your binary files or logical DB structures before you do any changes.

     

    Anwyays, from primary site after you ran query:

    sqlplus sys/password@proddr as sysdba

     

    what does this output shows:

    select * from v$pwfile_users;

     

    If record exists and you are very much sure the password file is the same between the two sites, then issue command from primary site :

    alter system switch logfile.

     

    Copy the last 30 lines of the alert logfile and paste them here.

     

    Also please review the links I reference before

     

    Thanks &

    Best Regards,

  • 22. Re: Standby Gaps after changing sys password
    yxes2013 Newbie
    Currently Being Moderated

    Hi all,

     

    SQL> select * from v$pwfile_users;

     

     

    USERNAME                       SYSDB SYSOP SYSAS

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

    SYS                            TRUE  TRUE  FALSE

  • 23. Re: Standby Gaps after changing sys password
    Anar Godjaev Expert
    Currently Being Moderated

    Dear Yxes2013

     

    You can check this step:

     

    Maybe you should do it in Secondary database:  orapwd file='..\dbs\orapwxxx.ora password=XXXXX(sys password ) entries=5 force=y

     

    upadte: And run query in primary:

     

    SELECT status, error

    FROM V$ARCHIVE_DEST_STATUS

    WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';

     

    Thank you

  • 24. Re: Standby Gaps after changing sys password
    Asif Muhammad Guru
    Currently Being Moderated

    Hi,

     

    If record exists and you are very much sure the password file is the same between the two sites, then issue command from primary site :

    alter system switch logfile.

     

    Copy the last 30 lines of the alert logfile and paste them here.

     

    Best Regards,

  • 25. Re: Standby Gaps after changing sys password
    yxes2013 Newbie
    Currently Being Moderated

    Hi all

     

    contents of alterPROD:

     

    Private strand flush not complete

      Current log# 1 seq# 2635 mem# 0: /u01/oradata/PROD/redo/redo01a.log

      Current log# 1 seq# 2635 mem# 1: /u02/oradata/PROD/redo/redo01b.log

      Current log# 1 seq# 2635 mem# 2: /u03/oradata/PROD/redo/redo01c.log

    Thread 1 advanced to log sequence 2636 (LGWR switch)

      Current log# 2 seq# 2636 mem# 0: /u01/oradata/PROD/redo/redo02a.log

      Current log# 2 seq# 2636 mem# 1: /u02/oradata/PROD/redo/redo02b.log

      Current log# 2 seq# 2636 mem# 2: /u03/oradata/PROD/redo/redo02c.log

    Thu Oct 17 13:48:47 2013

    ******************************************************************

    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2

    ******************************************************************

    Thu Oct 17 13:48:47 2013

    Archived Log entry 4441 added for thread 1 sequence 2635 ID 0x2324e993 dest 1:

    LNS: Standby redo logfile selected for thread 1 sequence 2636 for destination LOG_ARCHIVE_DEST_2

    Thu Oct 17 13:49:44 2013

    Error 1031 received logging on to the standby

    Errors in file /oracle/diag/rdbms/PROD/PROD/trace/PROD_arc0_1601618.trc:

    ORA-01031: insufficient privileges

    PING[ARC0]: Heartbeat failed to connect to standby 'PRODDR'. Error is 1031.

    Thu Oct 17 13:50:45 2013

    Error 1031 received logging on to the standby

    Errors in file /oracle/diag/rdbms/PROD/PROD/trace/PROD_arc0_1601618.trc:

    ORA-01031: insufficient privileges

    PING[ARC0]: Heartbeat failed to connect to standby 'PRODDR'. Error is 1031.

    Thu Oct 17 13:51:46 2013

    Error 1031 received logging on to the standby

    Errors in file /oracle/diag/rdbms/PROD/PROD/trace/PROD_arc0_1601618.trc:

    ORA-01031: insufficient privileges

    PING[ARC0]: Heartbeat failed to connect to standby 'PRODDR'. Error is 1031.

    Thu Oct 17 13:52:49 2013

    Error 1031 received logging on to the standby

    Errors in file /oracle/diag/rdbms/PROD/PROD/trace/PROD_arc0_1601618.trc:

    ORA-01031: insufficient privileges

    PING[ARC0]: Heartbeat failed to connect to standby 'PRODDR'. Error is 1031.

    Thu Oct 17 15:03:02 2013

    Thread 1 cannot allocate new log, sequence 2637

    Private strand flush not complete

      Current log# 2 seq# 2636 mem# 0: /u01/oradata/PROD/redo/redo02a.log

      Current log# 2 seq# 2636 mem# 1: /u02/oradata/PROD/redo/redo02b.log

      Current log# 2 seq# 2636 mem# 2: /u03/oradata/PROD/redo/redo02c.log

    Thread 1 advanced to log sequence 2637 (LGWR switch)

      Current log# 3 seq# 2637 mem# 0: /u01/oradata/PROD/redo/redo03a.log

      Current log# 3 seq# 2637 mem# 1: /u02/oradata/PROD/redo/redo03b.log

      Current log# 3 seq# 2637 mem# 2: /u03/oradata/PROD/redo/redo03c.log

    Thu Oct 17 15:03:05 2013

  • 26. Re: Standby Gaps after changing sys password
    Asif Muhammad Guru
    Currently Being Moderated

    Hi,

     

    Please do the following:

     

    1) SQL> alter system set log_archive_dest_state_2='defer';

    2) Now perform couple of log swtiches using command:

         alter system switch logfile.

    3) SQL> alter system set log_archive_dest_state_2='enable';

     


    4. Now check the alert logfile again and post them here if any errors.


    Thanks &

    Best Regards,

  • 28. Re: Standby Gaps after changing sys password
    yxes2013 Newbie
    Currently Being Moderated

    Hi Anar,

     

    SQL> alter system set log_archive_dest_state_2='defer';

     

     

    System altered.

     

     

    SQL> alter system set log_archive_dest_state_2='enable';

     

     

    System altered.

     

     

    SQL> alter system switch logfile;

     

     

    System altered.

     

    The alert log did not move? I only see old error?

     

    Why is my alert switch logfile not updating? or how do I know alert is moving?

     

    ===========================

    ******************************************************************

    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2

    ******************************************************************

    Thu Oct 17 15:55:37 2013

    Archived Log entry 4445 added for thread 1 sequence 2637 ID 0x2324e993 dest 1:

    LNS: Standby redo logfile selected for thread 1 sequence 2638 for destination LOG_ARCHIVE_DEST_2

    Thu Oct 17 16:25:29 2013

    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

    ALTER SYSTEM SET log_archive_dest_state_2='defer' SCOPE=BOTH;

    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST

    ALTER SYSTEM SET log_archive_dest_state_2='enable' SCOPE=BOTH;

    Thu Oct 17 16:25:39 2013

    Thread 1 cannot allocate new log, sequence 2639

    Private strand flush not complete

      Current log# 4 seq# 2638 mem# 0: /u01/oradata/PROD/redo/redo04a.log

      Current log# 4 seq# 2638 mem# 1: /u02/oradata/PROD/redo/redo04b.log

      Current log# 4 seq# 2638 mem# 2: /u03/oradata/PROD/redo/redo04c.log

    Thread 1 advanced to log sequence 2639 (LGWR switch)

      Current log# 1 seq# 2639 mem# 0: /u01/oradata/PROD/redo/redo01a.log

      Current log# 1 seq# 2639 mem# 1: /u02/oradata/PROD/redo/redo01b.log

      Current log# 1 seq# 2639 mem# 2: /u03/oradata/PROD/redo/redo01c.log

    Thu Oct 17 16:25:42 2013

    ******************************************************************

    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2

    ******************************************************************

    Thu Oct 17 16:25:42 2013

    Archived Log entry 4447 added for thread 1 sequence 2638 ID 0x2324e993 dest 1:

    LNS: Standby redo logfile selected for thread 1 sequence 2639 for destination LOG_ARCHIVE_DEST_2

    Thu Oct 17 16:26:00 2013

    Thread 1 cannot allocate new log, sequence 2640

    Private strand flush not complete

      Current log# 1 seq# 2639 mem# 0: /u01/oradata/PROD/redo/redo01a.log

      Current log# 1 seq# 2639 mem# 1: /u02/oradata/PROD/redo/redo01b.log

      Current log# 1 seq# 2639 mem# 2: /u03/oradata/PROD/redo/redo01c.log

    Thread 1 advanced to log sequence 2640 (LGWR switch)

      Current log# 2 seq# 2640 mem# 0: /u01/oradata/PROD/redo/redo02a.log

      Current log# 2 seq# 2640 mem# 1: /u02/oradata/PROD/redo/redo02b.log

      Current log# 2 seq# 2640 mem# 2: /u03/oradata/PROD/redo/redo02c.log

    Thu Oct 17 16:26:00 2013

    Archived Log entry 4448 added for thread 1 sequence 2639 ID 0x2324e993 dest 1:

    Thu Oct 17 16:26:00 2013

    ******************************************************************

    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2

    ******************************************************************

    LNS: Standby redo logfile selected for thread 1 sequence 2640 for destination LOG_ARCHIVE_DEST_2

     

    Thanks

  • 29. Re: Standby Gaps after changing sys password
    Asif Muhammad Guru
    Currently Being Moderated

    Hi,

     

    Please issue another 2 to 3 log switches and check the log file.

     

    Now provide the output of:

    SELECT status, error

    FROM V$ARCHIVE_DEST_STATUS

    WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';

     

    Thanks &

    Best Regards,

Legend

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