The database alert log has errors. Please help me

Question

Hi all
I have an Oracle 8i Database that seams to be functioning well but when I
Checked the Database alert Log I realized that something is not fine
Part of the alert log content is here under. What can be problem and how can I
Resolve it. Please I need you assistance...
Thu Feb 07 08:50:37 2008
Thread 1 advanced to log sequence 266
Thu Feb 07 08:50:37 2008
Current log# 11 seq# 266 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Thu Feb 07 08:50:38 2008
ARC0: Beginning to archive log# 10 seq# 265
Thu Feb 07 08:51:07 2008
ARC0: Completed archiving log# 10 seq# 265
Thu Feb 07 09:23:22 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03976.TRC:
Thu Feb 07 09:23:23 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA04092.TRC:
................................................................................................................

Answer 1

I'll just throw a shameless copy-paste from Metalink note : 164839.1 , hope you can use it to get further ? :
Subject: FATAL ERROR IN TWO-TASK SERVER: error = 12571 Found in Alert File
Doc ID: Note:164839.1 Type: PROBLEM
Last Revision Date: 17-DEC-2007 Status: PUBLISHED
fact: Oracle Server - Enterprise Edition
symptom: Errors appear in alert file
symptom: FATAL ERROR IN TWO-TASK SERVER:
symptom: ERROR = 12571
symptom: trace file generated
symptom: Database operations continue successfully
cause: The most common cause for the above error is an ungraceful
disconnection of a session from the oracle db while the db is currently running
a dml statement issued by that session. The error is recorded when oracle
attempts to reply back to the session with the results of the dml and cannot
access the session. Overall database operations are usually not affected.
An ungraceful disconnection could cause by but is not limited to any of the
following:
- the client machine crashed
- the network connection crashed
- the user exited the session improperly (not issuing the 'exit' command)
- the user application allows the user to exit the application without properly
terminating the session.
The above can cause problems with corrupted rollback segments if occurring on a
regular basis and is not addressed. This would require db recovery and
possibly a db rebuild (not a light matter)
PMON will usually rollback most transactions in the rollback segments for a
session if it finds that the session has been ungracefully disconnected, but
there is always a chance that it cannot and this will lead to rollback segment
corruption.
fix:
The dml and the user that issued the dml can be determined from the trace file.
The current dml is in the tracefile header section. The user can be found in
the process state dump of the trace. The process state shows the machine,
o/suser, and user for the session.
The DBA can use this information to determine what the user was doing at the
time and if there was an ungraceful exit from the session the user was
utilizing.
The DBA should then address the cause of the ungraceful exit to reduce the
possibility of recurrence.