1 2 Previous Next 21 Replies Latest reply: Nov 9, 2012 6:10 AM by CKPT Go to original post RSS
      • 15. Re: Archived log file are not shifted to standby side and applied
        CKPT
        vk82 wrote:
        I already done the same below is my init file for pri

        DB_NAME=orcl
        DB_UNIQUE_NAME=orcl
        LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,sbyorcl)'
        LOG_ARCHIVE_DEST_1='LOCATION=/home/oracle/app/oracle/flash_recovery_area/orcl/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl'
        LOG_ARCHIVE_DEST_2='SERVICE=sbyorcl ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=sbyorcl'
        LOG_ARCHIVE_DEST_STATE_1=ENABLE
        LOG_ARCHIVE_DEST_STATE_2=ENABLE
        REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
        LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
        LOG_ARCHIVE_MAX_PROCESSES=30
        FAL_SERVER=sbyorcl
        FAL_CLIENT=orcl
        DB_FILE_NAME_CONVERT='sbyorcl','orcl'
        LOG_FILE_NAME_CONVERT='/home/oracle/app/oracle/flash_recovery_area/sbyorcl/','/home/oracle/app/oracle/flash_recovery_area/orcl/'
        STANDBY_FILE_MANAGEMENT=AUTO


        What i need to do next
        No, you haven't

        change this parameter as below
        LOG_ARCHIVE_DEST_2='SERVICE=sbyorcl lgwr ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=sbyorcl'
        It doen't work if you just mention lgwr and you must create standby redo log files as i mentioned in earlier note
        • 16. Re: Archived log file are not shifted to standby side and applied
          817202
          After chnaging this parameter i am still not getting any archives applied on standby database

          can you please help me out
          • 17. Re: Archived log file are not shifted to standby side and applied
            CKPT
            I already mentioned to change parameter and to add same or more number of standby redo logs than online redo logs and same or more size of standby redo logs than online redo logs.

            And have you started recovery with real time apply?
            SQL> alter database recover managed standby database using current logfile disconnect from session;

            So you have to do all these 3 things to enable and use of real time apply. :)
            • 18. Re: Archived log file are not shifted to standby side and applied
              817202
              i changed the parameter as you mentioned and i have already 3 standby files of same size and same number.Also i started recovery with real time apply as you mentioned.

              If you require other details i will provide it to you.
              • 19. Re: Archived log file are not shifted to standby side and applied
                CKPT
                vk82 wrote:
                i changed the parameter as you mentioned and i have already 3 standby files of same size and same number.Also i started recovery with real time apply as you mentioned.

                If you require other details i will provide it to you.
                Once again restart MRP and post last 50 lines of standby alert log file information.
                and post
                SQL> SELECT THREAD#,SEQUENCE#,PROCESS,CLIENT_PROCESS,STATUS,BLOCK#,BLOCKS FROM V$MANAGED_STANDBY;
                And can you confirm whether your standby database is Open with Read only option? which means Active Data Guard. Then only you can view this query if not it will result no rows.
                However once again am testing it.
                Done
                SQL> select open_mode from v$database;
                
                OPEN_MODE
                --------------------
                MOUNTED
                
                SQL> select * from v$standby_event_histogram;
                
                no rows selected
                
                SQL> alter database recover managed standby database cancel;
                
                Database altered.
                
                SQL> alter database open;
                
                Database altered.
                
                SQL> alter database recover managed standby database using current logfile disconnect from session;
                
                Database altered.
                
                SQL> select open_mode from v$database;
                
                OPEN_MODE
                --------------------
                READ ONLY WITH APPLY
                
                SQL> select * from v$standby_event_histogram;
                
                NAME                                                                   TIME
                ---------------------------------------------------------------- ----------
                UNIT                  COUNT LAST_TIME_UPDATED
                ---------------- ---------- --------------------
                apply lag                                                                 0
                seconds                   2 11/09/2012 17:32:07
                
                SQL>
                Is it fine?

                Edited by: CKPT on Nov 9, 2012 5:30 PM

                Edited by: CKPT on Nov 9, 2012 5:32 PM
                • 20. Re: Archived log file are not shifted to standby side and applied
                  817202
                  SQL> select open_mode from v$database;

                  OPEN_MODE
                  --------------------
                  MOUNTED


                  SQL> select * from v$standby_event_histogram;

                  no rows selected

                  SQL> alter database recover managed standby database cancel;
                  alter database recover managed standby database cancel
                  *
                  ERROR at line 1:
                  ORA-16136: Managed Standby Recovery not active
                  • 21. Re: Archived log file are not shifted to standby side and applied
                    CKPT
                    vk82 wrote:
                    SQL> select open_mode from v$database;

                    OPEN_MODE
                    --------------------
                    MOUNTED


                    SQL> select * from v$standby_event_histogram;

                    no rows selected

                    SQL> alter database recover managed standby database cancel;
                    alter database recover managed standby database cancel
                    *
                    ERROR at line 1:
                    ORA-16136: Managed Standby Recovery not active
                    Check errors using "oerr" utility, what it is referring to.
                    16136, 00000, "Managed Standby Recovery not active"
                    // *Cause:  An attempt was made to cancel a managed recovery session but
                    //          no managed recovery session was active.
                    // *Action: No action is necessary.
                    So no media recovery is On, now open database and start apply using current log file, I have already mentioned in my previous post
                    1 2 Previous Next