I tried to kill a user session and it shut down my database!!!!
Here's what I did -
I had logged into Enterprise Manager, selected the session I wanted to end, and clicked the kill session button. I received an error to the effect of "can't close session" and I clicked the cancel button (only option available). My Enterprise Manager screen went white. After a minute or so, I figured it wasn't going to come back so I closed out of Enterprise Manager, then logged back in only to find that my database had been shut down! This is the second time this has happened in the last month!
I receive the following entry in the alert log -
Thu Jan 19 12:30:05 2006
Errors in file d:\oracle\ora92\rdbms\trace\prod_pmon_4668.trc:
ORA-00474: SMON process terminated with error
Thu Jan 19 12:30:05 2006
PMON: terminating instance due to error 474
Thu Jan 19 12:30:17 2006
Instance terminated by PMON, pid = 4668
The prod_pmon_4668.trc file contains the following -
Dump file d:\oracle\ora92\rdbms\trace\prod_pmon_4668.trc
Thu Jan 19 12:30:05 2006
ORACLE V9.2.0.5.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Oracle9i Release 9.2.0.5.0 - Production
JServer Release 9.2.0.5.0 - Production
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Instance name: prod
Redo thread mounted by this instance: 1
Oracle process number: 2
Windows thread id: 4668, image: ORACLE.EXE
*** 2006-01-19 12:30:05.833
*** SESSION ID
1.1) 2006-01-19 12:30:05.833
error 474 detected in background process
ORA-00474: SMON process terminated with error
I did quite a bit of research when this happened the first time, and basically all I got was that there was an error with the PMON processes which caused it to fail, and it turn caused the database to shut down.
Has anyone else experienced a similiar problem when killing sessions via Enterprise Manager?
Here's what I did -
I had logged into Enterprise Manager, selected the session I wanted to end, and clicked the kill session button. I received an error to the effect of "can't close session" and I clicked the cancel button (only option available). My Enterprise Manager screen went white. After a minute or so, I figured it wasn't going to come back so I closed out of Enterprise Manager, then logged back in only to find that my database had been shut down! This is the second time this has happened in the last month!
I receive the following entry in the alert log -
Thu Jan 19 12:30:05 2006
Errors in file d:\oracle\ora92\rdbms\trace\prod_pmon_4668.trc:
ORA-00474: SMON process terminated with error
Thu Jan 19 12:30:05 2006
PMON: terminating instance due to error 474
Thu Jan 19 12:30:17 2006
Instance terminated by PMON, pid = 4668
The prod_pmon_4668.trc file contains the following -
Dump file d:\oracle\ora92\rdbms\trace\prod_pmon_4668.trc
Thu Jan 19 12:30:05 2006
ORACLE V9.2.0.5.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Oracle9i Release 9.2.0.5.0 - Production
JServer Release 9.2.0.5.0 - Production
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Instance name: prod
Redo thread mounted by this instance: 1
Oracle process number: 2
Windows thread id: 4668, image: ORACLE.EXE
*** 2006-01-19 12:30:05.833
*** SESSION ID
1.1) 2006-01-19 12:30:05.833error 474 detected in background process
ORA-00474: SMON process terminated with error
I did quite a bit of research when this happened the first time, and basically all I got was that there was an error with the PMON processes which caused it to fail, and it turn caused the database to shut down.
Has anyone else experienced a similiar problem when killing sessions via Enterprise Manager?
