Before in kgllkdl(), hd=7d097638. Before in kgllkdl(), hd=7d096740. Before in kgllkdl(), hd=7d097638. Before in kgllkdl(), hd=7d096740. Before in kgllkdl(), hd=7d097638. Before in kgllkdl(), hd=7d096740.
I only have this system running for 7 days and already the bdump directories has more files than my other test system.
On Monday 11 July 2005 15:30, Magni Fabrizio wrote: > Hi, > you should find some error (and probably traces) in you alert log and > bdump. > > Try to cut and paste those errors. > Maybe somebody has already seen your problem and can be of help. > > If the error is a ORA-600 (See ORA-600.ora-code.com) or ORA-7445 (See ORA-7445.ora-code.com) you should search on metalink or > better you sould open a service tar. > > Regards > Fabrizio > > > -- --Original Message-- -- > > From: Seah Hong Yee [mailto:hongyee@(protected)] > > Sent: Monday, July 11, 2005 9:31 AM > > To: suse-oracle@(protected) > > Subject: [suse-oracle] SLES 9 Oracle 10g Instance Crash opteron > > > > > > Hi, > > > > I am currently testing Oracle 10g on two machine, the 32 bit > > machine runs on > > > > SLES9 > > 1 gig RAM > > 2 X Pentium III 866Mhz > > ext3 on scsi > > > > The above machine runs without problems for one month. > > > > Last weekend I set up another machine with the same > > application but this time > > is the 64bit version of Oracle 10g. > > > > > > The specification is like this > > > > SLES9 > > 2 gig RAM > > 2 X Opteron 244 > > ADAPTEC ZCR 2015 (I2O) RAID, I configure as raid 10. > > ext 3 > > > > I am also using ORARUN on both machine, both of them is the > > script as of June > > 9 2005 downloaded from suse's site. > > > > The installation method was the documentation provided by > > SUse on oracle 10g > > and SLES 9 installation. The only modification I did to the > > orarun script was > > to comment out dbsnmp portion which does not apply to 10g. > > > > The problem is my oracle instance tend to crash ( become > > unavailable) at least > > once a day. And I have notice once it was during starting up > > of emctl start > > dbconsole. The machine itself was quite stable with no > > crashes on Jboss. > > When access http://192.168.1.102:5500/em/ I get a message database > > unavailable. Individual client was not able to connect to > > the database, I > > have to either do "rcoracle restart" or manually run > > "dbstart " to restart > > the database. However, I was not able to do "emctl stop > > dbconsole." > > > > Thanks. > > > > Regards, > > > > Hong Yee > > > > -- > > To unsubscribe, email: suse-oracle-unsubscribe@(protected) > > For additional commands, email: suse-oracle-help@(protected) > > Please see http://www.suse.com/oracle/ before posting
-- To unsubscribe, email: suse-oracle-unsubscribe@(protected) For additional commands, email: suse-oracle-help@(protected) Please see http://www.suse.com/oracle/ before posting
