haithinh81
asked on
SMON: terminating instance due to error 600
Hi,
My oracle database 8.1 has a trouble when startup
When I logon database by sqlplus, it shows me this message ORA-01092: Oracle instance terminated. Disconnection forced
I try to start up database by svrmgrl
svrmgr>connect internal
svrmgr>startup
ORA-01081: Cannot start already-running oracle - shut it down first
svrmgr>shutdown
ORA-03114 not connected to oracle
Here is my alert log
...
SMON: enabling cache recovery
SMON: enabling tx recovery
Fri Jun 23 03:19:38 2006
Completed: alter database open
Fri Jun 23 03:19:38 2006
Errors in file I:\Oracle\admin\QLBTC\bdum p\qlbtcSMO N.TRC:
ORA-00600: internal error code, arguments: [ktpridestroy2], [], [], [], [], [], [], []
Fri Jun 23 03:19:43 2006
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 161
How can I get the database to startup again?
Thanks in advance for the help
My oracle database 8.1 has a trouble when startup
When I logon database by sqlplus, it shows me this message ORA-01092: Oracle instance terminated. Disconnection forced
I try to start up database by svrmgrl
svrmgr>connect internal
svrmgr>startup
ORA-01081: Cannot start already-running oracle - shut it down first
svrmgr>shutdown
ORA-03114 not connected to oracle
Here is my alert log
...
SMON: enabling cache recovery
SMON: enabling tx recovery
Fri Jun 23 03:19:38 2006
Completed: alter database open
Fri Jun 23 03:19:38 2006
Errors in file I:\Oracle\admin\QLBTC\bdum
ORA-00600: internal error code, arguments: [ktpridestroy2], [], [], [], [], [], [], []
Fri Jun 23 03:19:43 2006
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 161
How can I get the database to startup again?
Thanks in advance for the help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
seems like you have to recovery your database.
database by setting the parameter fast_start_parallel_rollba
INIT<oracle_sid>.ORA file.
This problem can be caused by a corruption in the rollback segment.