1 2 3 Previous Next 36 Replies Latest reply on Dec 24, 2010 8:23 AM by Chinar Go to original post
      • 15. Re: Problem in starting oracle
        Thierry H.
        Well, i beleive that your system datafile backup is not valid. I would not know if there would be a trick to get that problem solve.
        Otherwise, you could restore an older backup, and recover from then if you still have the archive logs.

        Good luck
        • 16. Re: Problem in starting oracle
          Chinar
          Execute RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL and apply /u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log file after getting
          "Log applied.
          Media recovery complete."
          Message then execute ALTER DATABASE OPEN and post result there
          • 17. Re: Problem in starting oracle
            825983
            Here is a new execution of the recovery:

            SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
            ORA-00279: change 1470310377 generated at 12/22/2010 16:29:09 needed for thread
            1
            ORA-00289: suggestion :
            /oradata/flash_recovery/OVCDB/archivelog/2010_12_22/o1_mf_1_1_%u_.arc
            ORA-00280: change 1470310377 for thread 1 is in sequence #1


            Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
            /u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log
            Log applied.
            Media recovery complete.
            SQL> alter database open;
            alter database open
            *
            ERROR at line 1:
            ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
            • 18. Re: Problem in starting oracle
              Chinar
              Then post ALTER DATABASE OPEN RESETLOGS (without shutdown).
              • 19. Re: Problem in starting oracle
                825983
                here is the output:

                SQL> alter database open resetlogs;
                alter database open resetlogs
                *
                ERROR at line 1:
                ORA-01092: ORACLE instance terminated. Disconnection forced
                • 20. Re: Problem in starting oracle
                  Chinar
                  user9214131 wrote:
                  here is the output:

                  SQL> alter database open resetlogs;
                  alter database open resetlogs
                  *
                  ERROR at line 1:
                  ORA-01092: ORACLE instance terminated. Disconnection forced
                  Post there last 60 lines of alert.log
                  • 21. Re: Problem in starting oracle
                    825983
                    here is the output of alert file:

                    Wed Dec 22 16:45:26 2010
                    Warning: OS async I/O limit 128 is lower than recovery batch 1024
                    Wed Dec 22 16:45:26 2010
                    Warning: OS async I/O limit 128 is lower than recovery batch 1024
                    Wed Dec 22 16:45:26 2010
                    ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL ...
                    Wed Dec 22 16:45:54 2010
                    ALTER DATABASE RECOVER LOGFILE '/u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log'
                    Wed Dec 22 16:45:54 2010
                    Media Recovery Log /u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log
                    Wed Dec 22 16:45:54 2010
                    Incomplete recovery applied all redo ever generated.
                    Recovery completed through change 1470310379
                    Wed Dec 22 16:45:54 2010
                    Media Recovery Complete (OVCDB)
                    Completed: ALTER DATABASE RECOVER LOGFILE '/u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log'
                    Wed Dec 22 16:46:09 2010
                    alter database open
                    Wed Dec 22 16:46:09 2010
                    ORA-1589 signalled during: alter database open...
                    Wed Dec 22 16:49:31 2010
                    alter database open resetlogs
                    Wed Dec 22 16:49:31 2010
                    RESETLOGS is being done without consistancy checks. This may result
                    in a corrupted database. The database should be recreated.
                    RESETLOGS after incomplete recovery UNTIL CHANGE 1470310379
                    Resetting resetlogs activation ID 3676349497 (0xdb20a439)
                    Online log /u01/OVCDB/onlinelog/o1_mf_2_55yb9o52_.log: Thread 1 Group 2 was previously cleared
                    Online log /u02/OVCDB/onlinelog/o1_mf_2_55yb9p6m_.log: Thread 1 Group 2 was previously cleared
                    Online log /u03/OVCDB/onlinelog/o1_mf_2_55yb9q7k_.log: Thread 1 Group 2 was previously cleared
                    Online log /u01/OVCDB/onlinelog/o1_mf_3_55yb9r7k_.log: Thread 1 Group 3 was previously cleared
                    Online log /u02/OVCDB/onlinelog/o1_mf_3_55yb9s8s_.log: Thread 1 Group 3 was previously cleared
                    Online log /u03/OVCDB/onlinelog/o1_mf_3_55yb9tb1_.log: Thread 1 Group 3 was previously cleared
                    Wed Dec 22 16:49:32 2010
                    Setting recovery target incarnation to 7
                    Wed Dec 22 16:49:32 2010
                    Assigning activation ID 3676332168 (0xdb206088)
                    Thread 1 opened at log sequence 1
                    Current log# 1 seq# 1 mem# 0: /u01/OVCDB/onlinelog/o1_mf_1_55yb9l51_.log
                    Current log# 1 seq# 1 mem# 1: /u02/OVCDB/onlinelog/o1_mf_1_55yb9m51_.log
                    Current log# 1 seq# 1 mem# 2: /u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log
                    Successful open of redo thread 1
                    Wed Dec 22 16:49:32 2010
                    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
                    Wed Dec 22 16:49:32 2010
                    SMON: enabling cache recovery
                    Wed Dec 22 16:49:32 2010
                    ORA-01555 caused by SQL statement below (SQL ID: 4krwuz0ctqxdt, Query Duration=1293036572 sec, SCN: 0x0000.57a327f0):
                    Wed Dec 22 16:49:32 2010
                    select ctime, mtime, stime from obj$ where obj# = :1
                    Wed Dec 22 16:49:32 2010
                    Errors in file /opt/oracle/admin/OVCDB/udump/ovcdb_ora_5765.trc:
                    ORA-00704: bootstrap process failure
                    ORA-00704: bootstrap process failure
                    ORA-00604: error occurred at recursive SQL level 1
                    ORA-01555: snapshot too old: rollback segment number 11 with name "_SYSSMU11$" too small
                    Error 704 happened during db open, shutting down database
                    USER: terminating instance due to error 704
                    Instance terminated by USER, pid = 5765
                    ORA-1092 signalled during: alter database open resetlogs...
                    • 22. Re: Problem in starting oracle
                      Chinar
                      Set UNDO_MANAGEMENT=MANUAL in pfile and startup again database using pfile
                      • 23. Re: Problem in starting oracle
                        825983
                        with a complete startup it gives this message:

                        SQL> startup
                        ORACLE instance started.

                        Total System Global Area 2952790016 bytes
                        Fixed Size 2059104 bytes
                        Variable Size 2315256992 bytes
                        Database Buffers 620756992 bytes
                        Redo Buffers 14716928 bytes
                        Database mounted.
                        ORA-01113: file 1 needs media recovery
                        ORA-01110: data file 1:
                        '/oradata/orasys/OVCDB/datafile/o1_mf_system_55yb814w_.dbf'
                        • 24. Re: Problem in starting oracle
                          825983
                          But i have put MANUAL in init.ora!!!
                          • 25. Re: Problem in starting oracle
                            Chinar
                            user9214131 wrote:
                            with a complete startup it gives this message:

                            SQL> startup
                            ORACLE instance started.

                            Total System Global Area 2952790016 bytes
                            Fixed Size 2059104 bytes
                            Variable Size 2315256992 bytes
                            Database Buffers 620756992 bytes
                            Redo Buffers 14716928 bytes
                            Database mounted.
                            ORA-01113: file 1 needs media recovery
                            ORA-01110: data file 1:
                            '/oradata/orasys/OVCDB/datafile/o1_mf_system_55yb814w_.dbf'
                            1) Set UNDO_MANAGEMENT=MANUAL in pfile
                            2) STARTUP MOUNT DATABASE PFILE='PFILELOCATION'
                            3) RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
                            And apply above log and ALTER DATABASE OPEN
                            • 26. Re: Problem in starting oracle
                              825983
                              here is the output:

                              SQL> STARTUP MOUNT OVCDB PFILE=/opt/oracle/admin/OVCDB/pfile/init.ora.6162009132115
                              ORACLE instance started.

                              Total System Global Area 1610612736 bytes
                              Fixed Size 2056504 bytes
                              Variable Size 385879752 bytes
                              Database Buffers 1207959552 bytes
                              Redo Buffers 14716928 bytes
                              Database mounted.
                              SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
                              ORA-00279: change 1470310381 generated at 12/22/2010 16:49:32 needed for thread
                              1
                              ORA-00289: suggestion :
                              /oradata/flash_recovery/OVCDB/archivelog/2010_12_22/o1_mf_1_1_%u_.arc
                              ORA-00280: change 1470310381 for thread 1 is in sequence #1


                              Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
                              /u03/OVCDB/onlinelog/o1_mf_1_55yb9n5c_.log
                              Log applied.
                              Media recovery complete.
                              SQL> alter database open
                              2 ;
                              alter database open
                              *
                              ERROR at line 1:
                              ORA-01589: must use RESETLOGS or NORESETLOGS option for database open


                              SQL>
                              • 27. Re: Problem in starting oracle
                                Chinar
                                Well,without shutdown database execute ALTER DATABASE OPEN RESETLOGS;
                                • 28. Re: Problem in starting oracle
                                  jgarry
                                  MOS document +"Warning: OS async I/O limit 128 is lower than recovery batch 1024" in Alert log [ID 471846.1]+
                                  kind of gives me the idea you might have changed necessary kernel parameters. It's also considered a bug: Bug 8475825: OS ASYNC I/O LIMIT 128 IS LOWER THAN RECOVERY BATCH 1024

                                  But if you don't have backups, that gives me the idea you have bigger problems. Then when you had problems, you should have backed up all the files before doing anything else.
                                  • 29. Re: Problem in starting oracle
                                    825983
                                    I just want to thank you about your effort in order to help me to solve my case.
                                    I think that we can't recover the database, so that we are going to restore an old backup, of course we are going to lose a lot of data but we dont have the choice.

                                    Thank you very much again, specially Chinar and Urgent-IT.