alter system set event= '10513 trace name context forever , level 2 : 10231 trace name context forever, level 10' scope=spfile; shutdown immediate; startup ; otherwise you'd better upload the alert.log -ML -- Maclean Liu Senior Director Product Management ParnassusData Software ,Inc. http://www.parnassusdata.com/ Phone : (+86) 400-690-3643 ; Mobile : (+86) 13764045638 My Blog: http://askmaclean.com/ 4/F, No.733 Gaoping Road Shanghai , China zip code: 200436 On Sun, Nov 30, 2014 at 10:10 PM, Mostafa Eletriby < dmarc-noreply@xxxxxxxxxxxxx> wrote: > Hello , > I have the same problem , after running those statements by this > procedure, database goes down after a while. > > shutdown abort; > startup mount; > Alter system set events '10513 trace name context forever, level 2'; > alter database open; > > Then I restarted again but same problem. > Please advice. > Regards, > > > On Sunday, November 30, 2014 3:57 PM, Mostafa Eletriby < > dmarc-noreply@xxxxxxxxxxxxx> wrote: > > > Hello, > I tried those statements and restarted database. I am checking now. > Database version 11.2.0.2 Enterprise edition > > Alter system set events '10513 trace name context forever, level 2'; > ALTER SYSTEM SET EVENTS '10231 trace name context forever, level 10'; > > > > On Sunday, November 30, 2014 3:37 PM, Maclean Liu <maclean_007@xxxxxxx> > wrote: > > > Mostafa, > > event 10513 level 2 may help you keep database open temporarily . > You can skip the corrupted block by setting event 10231 level 10 , if > you the data is really not important . > > > > -ML > -- > > Maclean Liu > Senior Director Product Management > ParnassusData Software ,Inc. http://www.parnassusdata.com/ > Phone : (+86) 400-690-3643 ; Mobile : (+86) 13764045638 > My Blog: http://askmaclean.com/ > 4/F, No.733 Gaoping Road Shanghai , China > zip code: 200436 > > On Sun, Nov 30, 2014 at 9:16 PM, Mostafa Eletriby < > dmarc-noreply@xxxxxxxxxxxxx> wrote: > > Hello Uwe, > Yes you are right , this block is not in the online redo logs anymore. > Also the data in this database is not important to me, the most important > thing is just the instance to be running. > The database could be online when I startup but after a while it goes down. > I tried to export the database but gave me errors due to block corruption > , I am working at these errors. > > Thanks so much > Regards, > > > On Sunday, November 30, 2014 3:01 PM, Uwe Küchler <uwe@xxxxxxxxxxxx> > wrote: > > > Mostafa, > > If this block was corrupted BEFORE you switched archive log mode on and > recovery info for this block is not in the online redo logs anymore (which > I guess is the case), then this block is lost. > > Not meaning to be rude, but I suppose the data within this database is of > low importance to you / your organization, because otherwise you'd have had > this DB backed up properly beforehand. > > Are you able to get the DB online? Then do an export of the schema(s) that > matter to you instantly! Then try to find out more about the ORA-600 and > then start with a new DB where you re-import your data. > If the ORA-1124 persists, > > 1. shutdown immediate, > 2. startup mount and > 3. recover database; > > If it still persists, file an SR with Oracle. > > Regards, > Uwe > > On 30.11.2014 13:38, Mostafa Eletriby (Redacted sender m_etrib@xxxxxxxxx > for DMARC) wrote: > > Hello Uwe, > Thanks for reply. > I will try ORA-00600-Troubleshooting Tool > <https://support.oracle.com/epmos/faces/ui/gr/GrHome.jspx?domainId=ORA600> > > I tried to recover database because I had a block corruption shown at the > alert log file. > But I couldn't upload log files here because uploading contents is not > allowed at that moment. > Regards, > > > On Sunday, November 30, 2014 2:29 PM, Uwe Küchler <uwe@xxxxxxxxxxxx> > <uwe@xxxxxxxxxxxx> wrote: > > > Mostafa, > > as for the ORA-600 you should try the > “ORA-00600-Troubleshooting Tool > <https://support.oracle.com/epmos/faces/ui/gr/GrHome.jspx?domainId=ORA600> > ” > on My Oracle Support for a suggestion. Upload the corresponding trace file > or an IPS package and see what the tool comes up with. > > As for the recovery error, you didn't provide us with much information. > Why did you have to "recover database" in the first place? Could it be that > your database is already open instead of just mounted? > > Regards, > Uwe > --- > http://oraculix.com/ > > On 30.11.2014 11:55, Mostafa Eletriby (Redacted sender m_etrib@xxxxxxxxx > for DMARC) wrote: > > Hello DBAs, > I have a problem regarding Ora-600 error at Alert log file. > It appears regularly at alert log file and stops database and needs to > re-open database. > Please tell me which procedures that I should follow in order to solve the > problem. > > Database has no previous backup taken. > Database was in no archive mode before problem happened but now it is > switched to archive log mode > > ------------------------------------ > SQL> recover database; > ORA-00283: recovery session canceled due to errors > ORA-01124: cannot recover data file 1 - file is in use or recovery > ORA-01110: data file 1: '/oraData/cdsdb/system01.dbf' > > > Please advice me. > > Thanks > Regards, > > > > > > > > > > > > > >