Errors in file /oradata/oracle/admin/***/udump/**_ora_655776.trc:
ORA-00600: internal error code, arguments: [kteuPropTime-2], [], [], [], [], [], [],
下为oracle的回复,可以参考,选择一下方法来解决:
Bug 2431450
Abstract: START EXTENT NUMBER NOT UPDATED CORRECTLY, FOR COMMITTED TXNS WHICH HAVE NTP SET
Abstract: START EXTENT NUMBER NOT UPDATED CORRECTLY, FOR COMMITTED TXNS WHICH HAVE NTP SET
Note.233864.1ORA-600 [kteuproptime-2]
Note.2431450.8 Bug 2431450 - SMU Undo corruption possible on instance crash
Note.2431450.8 Bug 2431450 - SMU Undo corruption possible on instance crash
SOLUTION / ACTION PLAN
=======================
To implement the solution, please execute the following steps:
You can choose any one of following solutions
Note: Make sure you have a good BACKUP of your database before implement the fol
lowing methods:
1. Upgrade database to a fixed version of this bug.
This issue is fixed in:
9.2.0.4 (Server Patch Set)
10.1.0.2 (Base Release)
OR, if you cannot upgrade your database, then use the following method 2:
2. Drop current UNDO TBS and create a new one.
Shutdown the database .
If using Spfile :-
Startup nomount ;
Create pfile='/tmp/corrupt.ora' from spfile ;
Shutdown immediate;
Add the following two parameter in corrupt.ora
Comment Undo_tablespace parameter
undo_management=Manual
event="10513 trace name context forever, level 2"
Startup mount pfile='/tmp/corrupt.ora'
Show parameter event
It should show the parameter set.
Alter database open ;
If the database opens, then
Dropped the Old undo tablespace
Created a new Undo tablespace with same name
Then re-start database using the original spfile without event setting.
=======================
To implement the solution, please execute the following steps:
You can choose any one of following solutions
Note: Make sure you have a good BACKUP of your database before implement the fol
lowing methods:
1. Upgrade database to a fixed version of this bug.
This issue is fixed in:
9.2.0.4 (Server Patch Set)
10.1.0.2 (Base Release)
OR, if you cannot upgrade your database, then use the following method 2:
2. Drop current UNDO TBS and create a new one.
Shutdown the database .
If using Spfile :-
Startup nomount ;
Create pfile='/tmp/corrupt.ora' from spfile ;
Shutdown immediate;
Add the following two parameter in corrupt.ora
Comment Undo_tablespace parameter
undo_management=Manual
event="10513 trace name context forever, level 2"
Startup mount pfile='/tmp/corrupt.ora'
Show parameter event
It should show the parameter set.
Alter database open ;
If the database opens, then
Dropped the Old undo tablespace
Created a new Undo tablespace with same name
Then re-start database using the original spfile without event setting.
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/10834762/viewspace-474931/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
