1 2 Previous Next 26 Replies Latest reply on Jul 15, 2014 5:39 AM by MariaKarpa(MK)

    Read Only DG

      Hi all,

       

      11.2.0.3.10

      aix6

       

      I have created a DG physical standby. Then I tried to open it read-only. But It throws this errors:

       

      SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

       

       

      Database altered.

       

       

      SQL> alter database open;

      alter database open

      *

      ERROR at line 1:

      ORA-10458: standby database requires recovery

      ORA-01194: file 1 needs more recovery to be consistent

      ORA-01110: data file 1: '/u21/ORACLE/ORADATA/PROD/system01.dbf'

       

       

      What is happening to my standby? Please help....

       

      Thanks all,

      mk

        • 1. Re: Read Only DG
          Hemant K Chitale

          How many and *which* archivelogs have been applied to the database --- relative to the time the backup began.

           

           

          Hemant K Chitale


          1 person found this helpful
          • 2. Re: Read Only DG

            I do not know I thought dataguard will automate the copying and applying of logs?

            So why do I have to bother about it?

             

            I also have another error. I have not created an online redo log for my standby.

             

            So I run these commands:

             

            SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL;

             

             

            System altered.

             

             

            SQL> ALTER DATABASE ADD LOGFILE ('/u21/ORACLE/ORADATA/PROD/redo01.log') SIZE 50M;

            ALTER DATABASE ADD LOGFILE ('/u21/ORACLE/ORADATA/PROD/redo01.log') SIZE 50M

            *

            ERROR at line 1:

            ORA-01156: recovery or flashback in progress may need access to files

             

            Is my standby messed up?

             

            Was it successfully created in the first place? Installed it yesterday and I did not encouter any error.

             

             

            Thanks.

            • 3. Re: Read Only DG
              Hemant K Chitale

              I have no idea how you setup dataguard and confirmed that it was working.

               

               

              Hemant K Chitale


              1 person found this helpful
              • 4. Re: Read Only DG

                I just follow this document and it was successful> http://www.oracle-base.com/articles/11g/data-guard-setup-11gr2.php

                 

                Can you guide me how to troubleshoot please

                 

                 

                Thanks

                • 5. Re: Read Only DG

                  I tried to cancel the recovery and add the redo log:

                   

                  SQL> alter database recover managed standby database cancel ;

                   

                   

                  Database altered.

                   

                   

                  SQL> ALTER DATABASE ADD LOGFILE ('/u21/ORACLE/ORADATA/BNCTSIT/redo01.log') SIZE 50M;

                  ALTER DATABASE ADD LOGFILE ('/u21/ORACLE/ORADATA/BNCTSIT/redo01.log') SIZE 50M

                  *

                  ERROR at line 1:

                  ORA-01577: cannot add log file '/u21/ORACLE/ORADATA/BNCTSIT/redo01.log' - file

                  already part of database

                   

                   

                  So you see, This is what I mentioned in my previous post. I can not add redo log because it is part of the database but the physical file is not existing?

                  How do I handle this?

                   

                  Thanks

                  • 6. Re: Read Only DG
                    BPeaslandDBA

                      SQL> alter database open;

                    alter database open

                    *

                    ERROR at line 1:

                    ORA-10458: standby database requires recovery

                    ORA-01194: file 1 needs more recovery to be consistent

                    ORA-01110: data file 1: '/u21/ORACLE/ORADATA/PROD/system01.dbf'

                     

                     

                    What is happening to my standby? Please help....

                     

                     

                     

                    As the error states, the standby database needs more recovery to be consistent. As such, it will not open, even read only. Apply more recovery.

                     

                    Did you standby stop applying recovery for some reason? After you startup managed recovery, are there errors in the alert log?

                     

                    Cheers,
                    Brian

                    1 person found this helpful
                    • 7. Re: Read Only DG

                      Thanks Brian,

                       

                      I am checking the alerts now. brb

                      • 8. Re: Read Only DG
                        Hemant K Chitale

                        You have NO CLUE as to the difference between "apply archivelogs" and "add redolog"  (duh ! "archivelog" and "redo log" are different in this case !!!).

                         

                        As for the physical redo logs againlet me say this ... they are *created* when you OPEN RESETLOGS.

                         

                         

                        Hemant K Chitale


                        1 person found this helpful
                        • 9. Re: Read Only DG


                          "As for the physical redo logs again let me say this ... they are *created* when you OPEN RESETLOGS."


                          Yeah, that is what i meant. The docs I followed seem have mistake? I do not need to create new redo logs since they are created when you open resetlogs.

                          Did you check the ORACLE-BASE dataguard doc?  ORACLE-BASE - Data Guard Physical Standby Setup in Oracle Database 11g Release 2


                          This step should not be done?


                          Create Redo Logs

                          Create online redo logs for the standby. It's a good idea to match the configuration of the primary server.

                          ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL;

                          ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/oradata/DB11G/online_redo01.log') SIZE 50M;

                          ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/oradata/DB11G/online_redo02.log') SIZE 50M;

                          ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/oradata/DB11G/online_redo03.log') SIZE 50M;

                          ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;

                           

                          Thanks,

                          • 10. Re: Read Only DG
                            Hemant K Chitale

                            Why not ask the author of the article ?  You might have misunderstood some lines from the notes.

                             

                            Hemant K Chitale

                            1 person found this helpful
                            • 11. Re: Read Only DG
                              Hemant K Chitale

                              If you also follow the documentation :  http://docs.oracle.com/cd/E11882_01/server.112/e41134/toc.htm

                              you could actually log an SR with Oracle Support when you have problems.

                               

                               

                              Hemant K Chitale


                              1 person found this helpful
                              • 12. Re: Read Only DG

                                "Why not ask the author of the article ?  You might have misunderstood some lines from the notes."


                                There is no author specified. May it is TimHall?

                                Do you have your own blog? Maybe your procedure is clearer



                                "If you also follow the documentation :  http://docs.oracle.com/cd/E11882_01/server.112/e41134/toc.htm"


                                Yikes to much to read, the patient will be dead by the time I complete reading all that

                                 

                                "you could actually log an SR with Oracle Support when you have problems."


                                It is hard to explain to the support all the context in ORACLE-BASE documentation, hence it will takes longer time to resolve.


                                Thanks

                                • 13. Re: Read Only DG
                                  Hemant K Chitale

                                  >It is hard to explain to the support all the context in ORACLE-BASE documentation

                                  That is why you should follow the documentation.  Support works with Oracle's documentation.

                                   

                                   

                                  In any case, I am confident that the oracle-base articles are good.

                                   

                                  Hemant K Chitale

                                   

                                  1 person found this helpful
                                  • 14. Re: Read Only DG

                                    Hi,

                                     

                                    I am rechecking the docs again.

                                     

                                    Test Log Transport

                                     

                                    On the primary server, check the latest archived redo log and force a log switch.

                                     

                                    ALTER SESSION SET nls_date_format='DD-MON-YYYY HH24:MI:SS';

                                     

                                    SEQUENCE# FIRST_TIME           NEXT_TIME

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

                                           664 09-JUL-2014 22:05:23 10-JUL-2014 01:01:00

                                           665 10-JUL-2014 01:01:00 10-JUL-2014 07:41:36

                                           666 10-JUL-2014 07:41:36 10-JUL-2014 08:20:30

                                           667 10-JUL-2014 08:20:30 10-JUL-2014 12:00:03

                                           668 10-JUL-2014 12:00:03 10-JUL-2014 17:05:44

                                           669 10-JUL-2014 17:05:44 10-JUL-2014 22:03:00

                                           670 10-JUL-2014 22:03:00 10-JUL-2014 22:07:15

                                           671 10-JUL-2014 22:07:15 11-JUL-2014 04:00:51

                                           672 11-JUL-2014 04:00:51 11-JUL-2014 08:21:59

                                           673 11-JUL-2014 08:21:59 11-JUL-2014 09:00:54

                                     

                                    956 rows selected.

                                     

                                     

                                    SQL> ALTER SYSTEM SWITCH LOGFILE;

                                     

                                     

                                    System altered.

                                     

                                    SQL> /

                                     

                                    System altered.

                                     

                                    SQL> /

                                     

                                    System altered.

                                     

                                     

                                    Check the new archived redo log has arrived at the standby server and been applied.

                                     

                                     

                                    ALTER SESSION SET nls_date_format='DD-MON-YYYY HH24:MI:SS';

                                     

                                    SELECT sequence#, first_time, next_time, applied

                                    FROM   v$archived_log

                                    ORDER BY sequence#;

                                     

                                    no rows selected

                                     

                                     

                                    Why is my standby has no logs applied yet?

                                    How can I force it to apply?

                                     

                                    I checked the alert but there is no alert log activity. It seems the alert does not know of the standby config???

                                     

                                    Thanks

                                    1 2 Previous Next