Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Non-fatal internal error happenned while SMON was doing logging scn->t

Status
Not open for further replies.

dbalearner

Technical User
Aug 23, 2003
170
GB
Guys,

I am getting this message in my alert file

Errors in file /u01/app/oracle/diag/rdbms/mydb/mydb/trace/mydb_smon_7194.trc (incident=220642):
ORA-00600: internal error code, arguments: [13013], [5001], [267], [8459028], [2], [8459028], [17], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/mydb/mydb/incident/incdir_220642/mydb_smon_7194_i220642.trc
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 3 out of maximum 100 non-fatal internal errors.
Tue May 18 13:23:45 2010
Trace dumping is performing id=[cdmp_20100518132345]
Tue May 18 13:24:36 2010
Sweep [inc][220642]: completed
Sweep [inc2][220642]: completed


Has anyone come across this?

Thanks,

Learner
 
Have you checked the trace file, mydb_smon_7194_i220642.trc? The Oracle support articles on this error indicate that it can have a number of different causes, depending on the version you are running and the type of operation that was in progress when the error occurred. Unforunately. one of the possible causes is block corruption.

Also, please run the following query and report the results. For at least some of these ORA-00600 errors, the [267] argument indicates the database object that has the problem.

Code:
Select object_name,object_type,owner from dba_objects where data_object_id=267;
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top