Database Alert log.

Hi , I am having release Release 11.2.0.3.0 of oracle. Got database crash tuesday morning, and i am trying to get the reason for the crash. Given below is the alert.log for same. I can see Process RSM0 is getting killed , triggered the crash but could not relate it to the event follwed.
--------------------------------- ALERT.LOG---------------------------
Tue Aug 13 00:20:51 2013
Thread 1 advanced to log sequence 9737 (LGWR switch)
Current log# 3 seq# 9737 mem# 0: +DATA01/sid1004/onlinelog/group_3.379.817601969
Current log# 3 seq# 9737 mem# 1: +DATA02/sid1004/onlinelog/group_3.5858.817601983
Tue Aug 13 00:20:51 2013
LNS: Standby redo logfile selected for thread 1 sequence 9737 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:21:11 2013
Archived Log entry 20595 added for thread 1 sequence 9736 ID 0xe56c03af dest 1:
Tue Aug 13 00:30:48 2013
Thread 1 advanced to log sequence 9738 (LGWR switch)
Current log# 4 seq# 9738 mem# 0: +DATA01/sid1004/onlinelog/group_4.378.817601995
Current log# 4 seq# 9738 mem# 1: +DATA02/sid1004/onlinelog/group_4.7210.817602007
Tue Aug 13 00:30:48 2013
LNS: Standby redo logfile selected for thread 1 sequence 9738 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:30:55 2013
Archived Log entry 20597 added for thread 1 sequence 9737 ID 0xe56c03af dest 1:
Tue Aug 13 00:40:41 2013
Thread 1 advanced to log sequence 9739 (LGWR switch)
Current log# 5 seq# 9739 mem# 0: +DATA01/sid1004/onlinelog/group_5.377.817602019
Current log# 5 seq# 9739 mem# 1: +DATA02/sid1004/onlinelog/group_5.10031.817602031
Tue Aug 13 00:40:42 2013
LNS: Standby redo logfile selected for thread 1 sequence 9739 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:40:47 2013
Archived Log entry 20599 added for thread 1 sequence 9738 ID 0xe56c03af dest 1:
Tue Aug 13 00:50:41 2013
Thread 1 advanced to log sequence 9740 (LGWR switch)
Current log# 6 seq# 9740 mem# 0: +DATA01/sid1004/onlinelog/group_6.376.817602043
Current log# 6 seq# 9740 mem# 1: +DATA02/sid1004/onlinelog/group_6.6026.817602057
Tue Aug 13 00:50:41 2013
LNS: Standby redo logfile selected for thread 1 sequence 9740 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:50:46 2013
Archived Log entry 20601 added for thread 1 sequence 9739 ID 0xe56c03af dest 1:
Tue Aug 13 01:00:40 2013
Thread 1 advanced to log sequence 9741 (LGWR switch)
Current log# 7 seq# 9741 mem# 0: +DATA01/sid1004/onlinelog/group_7.375.817602069
Current log# 7 seq# 9741 mem# 1: +DATA02/sid1004/onlinelog/group_7.10703.817602081
Tue Aug 13 01:00:41 2013
LNS: Standby redo logfile selected for thread 1 sequence 9741 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 01:00:46 2013
Archived Log entry 20603 added for thread 1 sequence 9740 ID 0xe56c03af dest 1:
Tue Aug 13 01:09:02 2013
minact-scn: useg scan erroring out with error e:12751
Tue Aug 13 01:10:38 2013
Thread 1 advanced to log sequence 9742 (LGWR switch)
Current log# 8 seq# 9742 mem# 0: +DATA01/sid1004/onlinelog/group_8.374.817602093
Current log# 8 seq# 9742 mem# 1: +DATA02/sid1004/onlinelog/group_8.12060.817602105
Tue Aug 13 01:10:39 2013
LNS: Standby redo logfile selected for thread 1 sequence 9742 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 01:10:51 2013
Archived Log entry 20605 added for thread 1 sequence 9741 ID 0xe56c03af dest 1:
Tue Aug 13 01:15:55 2013
Time drift detected. Please check VKTM trace file for more details.
Tue Aug 13 01:16:27 2013
Thread 1 advanced to log sequence 9743 (LGWR switch)
Current log# 1 seq# 9743 mem# 0: +DATA01/sid1004/onlinelog/group_1.381.817601921
Current log# 1 seq# 9743 mem# 1: +DATA02/sid1004/onlinelog/group_1.5144.817601933
Tue Aug 13 01:17:51 2013
Process RSM0, PID = 8562, will be killed
Tue Aug 13 02:19:38 2013
Starting ORACLE instance (normal)

While you're at MetaLink/MyOracle support, you'd probably want to read the following doc id's as well:
Time Drift Detected. Please Check Vktm Trace File For More Details. (Doc ID 1347586.1)
Alert log shows: "Minact-scn: Useg Scan Erroring Out With Error E:12751" Warning (Doc ID 1478691.1)

Similar Messages

Errors in Database Alert Log... Please Help

Hi All,
This database is on Oracle 8i but I found errors in the alert Log.
These errors are relating to archiving.
Please take a look at this file to see the details;
http://us.f13.yahoofs.com/bc/47aff3ab_a145/bc/My+Documents/Database+Alert+Log.LOG?bfUw9sHBkd_LbjY0
ARC0: Beginning to archive log# 11 seq# 301
Wed Feb 13 14:57:45 2008
ARC0: Completed archiving log# 11 seq# 301
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03852.TRC:
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03208.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03340.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA00784.TRC:
Wed Feb 13 15:46:31 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03748.TRC:
Wed Feb 13 15:46:32 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA01228.TRC:
Wed Feb 13 16:18:57 2008
Thread 1 advanced to log sequence 303
Current log# 13 seq# 303 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 16:18:57 2008
ARC2: Beginning to archive log# 12 seq# 302
Wed Feb 13 16:19:25 2008
ARC2: Completed archiving log# 12 seq# 302
Wed Feb 13 18:40:13 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03872.TRC:
Please help out. What is exactly the cause of this error and how can I avoid it next time from occuring.

>> Please paste the output of E:\Oracle\admin\MUKREC\udump\ORA03872.TRC
Click on the link below to get the output of the ORA03872.TRC trace file
http://us.f13.yahoofs.com/bc/47aff3ab_a145/bc/My+Documents/ORA03872.TRC?bfMq_sHBSRis64KA
>> and last 100 lines of alert log
the last 100 lines of the alert log are here under;
Wed Feb 13 11:50:27 2008
Thread 1 advanced to log sequence 296
Current log# 13 seq# 296 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 11:50:27 2008
ARC0: Beginning to archive log# 12 seq# 295
Wed Feb 13 11:51:02 2008
ARC0: Completed archiving log# 12 seq# 295
Wed Feb 13 12:27:18 2008
Thread 1 advanced to log sequence 297
Current log# 7 seq# 297 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO07.LOG
Wed Feb 13 12:27:18 2008
ARC0: Beginning to archive log# 13 seq# 296
Wed Feb 13 12:27:59 2008
Thread 1 advanced to log sequence 298
Current log# 8 seq# 298 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO08.LOG
Wed Feb 13 12:27:59 2008
ARC1: Beginning to archive log# 13 seq# 296
ARC1: Failed to archive log# 13 seq# 296
ARC1: Beginning to archive log# 7 seq# 297
Wed Feb 13 12:28:33 2008
Thread 1 advanced to log sequence 299
Current log# 9 seq# 299 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO09.LOG
Wed Feb 13 12:29:10 2008
Thread 1 advanced to log sequence 300
Current log# 10 seq# 300 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO10.LOG
Wed Feb 13 12:29:11 2008
ARC0: Completed archiving log# 13 seq# 296
ARC0: STARTING ARCH PROCESSES
ARC2 started with pid=166
Wed Feb 13 12:29:11 2008
ARC0: STARTING ARCH PROCESSES COMPLETE
Wed Feb 13 12:29:11 2008
ARC0: Beginning to archive log# 7 seq# 297
ARC0: Failed to archive log# 7 seq# 297
ARC0: Beginning to archive log# 8 seq# 298
Wed Feb 13 12:29:12 2008
ARC2: Archival started
Wed Feb 13 12:29:32 2008
ARC1: Completed archiving log# 7 seq# 297
ARC1: Beginning to archive log# 8 seq# 298
ARC1: Failed to archive log# 8 seq# 298
ARC1: Beginning to archive log# 9 seq# 299
Wed Feb 13 12:29:48 2008
ARC0: Completed archiving log# 8 seq# 298
Wed Feb 13 12:29:48 2008
ARC2: Beginning to archive log# 9 seq# 299
ARC2: Failed to archive log# 9 seq# 299
Wed Feb 13 12:30:03 2008
ARC1: Completed archiving log# 9 seq# 299
Wed Feb 13 14:46:05 2008
Thread 1 advanced to log sequence 301
Current log# 11 seq# 301 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Wed Feb 13 14:46:05 2008
ARC1: Beginning to archive log# 10 seq# 300
Wed Feb 13 14:46:41 2008
ARC1: Completed archiving log# 10 seq# 300
Wed Feb 13 14:57:10 2008
Thread 1 advanced to log sequence 302
Current log# 12 seq# 302 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO12.LOG
Wed Feb 13 14:57:10 2008
ARC0: Beginning to archive log# 11 seq# 301
Wed Feb 13 14:57:45 2008
ARC0: Completed archiving log# 11 seq# 301
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03852.TRC:
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03208.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03340.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA00784.TRC:
Wed Feb 13 15:46:31 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03748.TRC:
Wed Feb 13 15:46:32 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA01228.TRC:
Wed Feb 13 16:18:57 2008
Thread 1 advanced to log sequence 303
Current log# 13 seq# 303 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 16:18:57 2008
ARC2: Beginning to archive log# 12 seq# 302
Wed Feb 13 16:19:25 2008
ARC2: Completed archiving log# 12 seq# 302
Wed Feb 13 18:40:13 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03872.TRC:
Thu Feb 14 08:03:54 2008
Thread 1 advanced to log sequence 304
Thu Feb 14 08:03:54 2008
Current log# 7 seq# 304 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO07.LOG
Thu Feb 14 08:03:55 2008
ARC1: Beginning to archive log# 13 seq# 303
Thu Feb 14 08:04:45 2008
ARC1: Completed archiving log# 13 seq# 303
Thu Feb 14 08:24:29 2008
Thread 1 advanced to log sequence 305
Current log# 8 seq# 305 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO08.LOG
Thu Feb 14 08:24:29 2008
ARC0: Beginning to archive log# 7 seq# 304
Thu Feb 14 08:25:01 2008
ARC0: Completed archiving log# 7 seq# 304
------------------------------------------------------------------------------------------------------------------------------------

Production database Alert log Message

Hi,
I am using oracle 10gR1 on windows.Recently i have created a physical standby database (sid=smtm) and production database (sid=mtm).My production alter log file dispaly some thing like please suggest my what it shows.
Mon Mar 02 00:18:31 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35722
Current log# 4 seq# 35722 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04.LOG
Current log# 4 seq# 35722 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04_A.LOG
Mon Mar 02 00:18:31 2009
ARC1: Evaluating archive   log 2 thread 1 sequence 35721
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35721_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35721 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35721 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35721 destination SMTM)*Mon Mar 02 00:29:42 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35723
Current log# 3 seq# 35723 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03.LOG
Current log# 3 seq# 35723 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03_A.LOG
Mon Mar 02 00:29:42 2009
ARC1: Evaluating archive   log 4 thread 1 sequence 35722
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35722_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35722 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35722 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35722 destination SMTM)*
Thanks

Sorry i have no metalink account.
On production database there is no any ORA error and on standby database Alert log shows.
Mon Mar 02 03:40:38 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'Mon Mar 02 04:29:14 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...Mon Mar 02 11:01:57 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Mar 02 11:01:57 2009
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35553_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT ...Mon Mar 02 11:02:05 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35554_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Mar 02 11:02:14 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35555_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Regards
Thanks for reply.

Error in primary database alert log

Dear all i am getting the following error in my primary database alert log
oracle 10.2.0.3
Os/ rhel 4
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:20:37 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Tue Jul 7 23:25:38 2009
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:25:38 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Please let me know what needs to be done.
THanks in advance,
Aj

00088, 00000, "command cannot be executed by shared server "
// *Cause: Debug command issued on shared server.
// *Action: Reissue the command using a dedicated server.

I am geting errors in my database alert log file ora-12012 and ora 44003

Hi all,
I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
and trace file is i got i am posting here please help any one is aware about this....
System name: SunOS
Node name: obrmzone1
Release: 5.10
Version: Generic_137111-06
Machine: sun4v
Instance name: ------
Redo thread mounted by this instance: 1
Oracle process number: 144
Unix process pid: 26874, image:--------- (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
*** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
*** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
*** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
*** 2011-06-10 22:00:49.372
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
thank you in advance,
Dav

I just google with "ORA-44003: invalid SQL name" and found below link:
http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
SIMPLE_SQL_NAME
The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
The first character of the name is alphabetic.
The name only contains alphanumeric characters or the "_", "$", "#"
Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
The function ignores leading and trailing white spaces are ignored
The length of the input string is not validated.

The database alert log has errors. Please help me

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:
................................................................................................................

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.

Alert log.xml or alert.log errors do not appear in EM

Little puzzled here. Using 11.1.0.6 to test if alert errors will appear on 11.1.0.1 EM Grid pages. Simple ORA-1653 triggered via sql insert and then waited and waited. Nothing. I can use EM to open log file and to display the errors but no alerts are flagged on any of the pages.
Is this a another bug?
Roman

You can read all about how the 11g alert log is monitored in: Monitoring 11g Database Alert Log Errors in Enterprise Manager [ID 949858.1]
Yes, it describes some bugs (and workarounds) too.
Eric

Alert log filtering examples

Hello.
Following the Oracle Note Monitoring 10g Database Alert Log Errors in Enterprise Manager [ID 976982.1], I am trying to include some exceptions in the alert log filtering tool but I was looking for more examples. Does anyone have any?
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0

For example, if I want to filter out any 0600 errors that contain the qctVCO:csform argument, would this be appropriate?
.*ORA-0*(54|1142|1146)\D.*|.*ORA-00600:.*\[qctVCO:csform][^\]]*\].*
Do we need to pipe for each successive ORA error, as above?
Thanks,

Dead lock detected in alert log for HTMLDB application

We have a HTMLDB application newly impletemented in our database. One day, I found a ORA-000060 deadlock detected message in database alert log. Our developer said that the application is only for users to query something and will not insert, update or delete anything. I have created a tar but still not found any problem cause this. Can anyone tell why this occur?
Thanks in advance,
Antony
*** SESSION ID:(289.143) 2005-11-17 10:35:48.976
DEADLOCK DETECTED
Current SQL statement for this session:
DELETE FROM WWV_FLOW_DATA WHERE FLOW_INSTANCE = :B1 AND ITEM_ID IN (SELECT ID FROM WWV_FLOW_PAGE_PLUGS WHERE FLOW_ID = :B3 AND PAGE_ID = :B2 AND PLUG_SOURCE_TYPE IN ( 'SIMPLE_CHART', 'UPDATABLE_SQL_QUERY', 'DBMSSQL_CURSOR', 'FUNCTION_RETURNING_DBMSSQL_CURSOR', 'FUNCTION_RETURNING_SQL_QUERY_CACHED', 'FUNCTION_RETURNING_SQL_QUERY', 'STRUCTURED_QUERY', 'SQL_QUERY'))
----- PL/SQL Call Stack -----
object line object
handle number name
7000000bb989300 228 package body FLOWS_020000.WWV_FLOW_DISP_PAGE_PLUGS
7000000bbc922c8 8961 package body FLOWS_020000.WWV_FLOW
7000000bbd00000 236 procedure FLOWS_020000.F
7000000bdf1baa0 8 anonymous block
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00050005-00756507 308 289 X 295 276 X
TX-0002000f-006fc0df 295 276 X 308 289 X
session 289: DID 0001-0134-00000005 session 276: DID 0001-0127-00000002
session 276: DID 0001-0127-00000002 session 289: DID 0001-0134-00000005

Rakesh,
Please see if (ora-600 [12333] / ora-3137 [12333] Troubleshooting [ID 828123.1]) and/or (ORA-600 [12333] "Fatal Two-Task Protocol Violation" [ID 35928.1]) is applicable.
Did you try to bounce the database and see if you can reproduce the issue?
If you still encounter the same error, please log a SR.
Thanks,
Hussein

Alert Log Archive

Hi,
Could any body tell me how can I take the day to day backup of Oracle Database Alert Log file. and in the folder containg the alert log file what are the other files and what are the purpose of those files.
Regards,
D.Abbasi

Abbasi,Danish wrote:
Hi,
Could any body tell me how can I take the day to day backup of Oracle Database Alert Log file. You can schedule a cron job to copy the alert log to a backup destination. Personally, I prefer going through the alert log and keeping the important bits in the file only (remove the basic log switch information and other things).
and in the folder containg the alert log file what are the other files and what are the purpose of those files.
Alert log is located in the background dump destination. All background processes are also dumping the data in this folder. So unless there is a critical error in alert log which indicates the details to be present in a trace file, you can remove the unwanted files.

Ossnet messages alert log

Hello Experts,
i am seeing following error messages in database alert log. based on error message OS process was not able to connect one of the cell server. is there any way to find why it is failing to connect cell server?
OSPID: 27669: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:35:16 2012
OSPID: 27665: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:35:17 2012
OSPID: 18681: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:42:22 2012
OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
Mon Nov 05 17:42:24 2012
OSPID: 20097: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
OSPID: 20097: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
please advice

Hi 892564,
i was wonder, how do you determine this is Cell server #7 ?The private network of your first exadata has a default range starting from 192.168.10.1 from the lowest compute node (db01).
A halfrack contains 11 components in the private network (4 nodes and 7 cells).
Hence 192.168.10.11 would be cell 7.
For a full rack this IP would match to cell 3.
Regards,
Tycho

Metrics to monitor Alert Log

Hi,
I am trying to make modification in metric for monitoring alertlog.
When I try to add a new line,it's asking for field "Time/Line Number",any one know what should be the value for that?
Description on that page --> "The table lists all Time/Line Number objects monitored for this metric. You can specify different threshold settings for each Time/Line Number object." doesn''t make much sense to me.
I gave a dummy value 50,but it doesn't seem to work..
Any help is highly appreciated... thanks...

For monitoring <11g database note 976982.1 may be of use to you: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETIN&id=976982.1;
For monitoring 11g db's see note 949858.1 (Monitoring 11g Database Alert Log Errors in Enterprise Manager)
I your case you may want to consider to create a UDM, see Monitor Non Critical 11g Database Alert Log Errors Using a SQL UDM [ID 961682.1]
Eric

Alert log monitoring in dbconsole 11.2.0.2.0

Hullo
Is there a way to tune out certain ORA- alerts from alerting via dbconsole? At the moment we are getting all ORA-0600s and some of them we dont need waking up by!
Thanks.
11.2.0.3
RHEL 5.5

Do you have metalink support? This is the doc you want to check into .. yes it is possible.
Database Alert log monitoring in 12c explained (Doc ID 1538482.1)
From this doc...
You need to get fancy with the regexp..
Setting thresholds for alert log metrics
Setting of the thresholds is a very complex and wide area and the values are depending on the requirements, the DBA experience and environments being monitored. This can be achieved by going to the Database target menu->Monitoring->Metrics and collection settings->Edit the "Generic Alert Log Error" from the 3 blue pencils icon on the right.
By default, the "Generic Alert Log Error" Warning threshold is set to "ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]" which means:
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] - the string ORA-0
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] - folowed by none ore more zeroes
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] - followed by 600 or 60 (the ? operator means "there is zero or one of the preceding element")
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] - or it can be 7445
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] - or it can be anything between 4000 and 4999
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] - it can follow anything but a number
For setting the thresholds, a Regular expression (RegExp) as the one above needs to be used.

Trim the alert log?

i have a alert log in <grid home>/log/<node>/alert<node>.log that is growing in size and is also owned by root. is this just like a DB alert log and if I rename it a new one will be created. i'm not sure how to maintenance this log file and I don't want to guess - any suggestions or documentation are appreciated.
thanks.

You can use the ADRCI to manage (purge,etc..) the logs of Oracle.
See this links..
http://www.dbasupport.com/oracle/ora11g/ADRCI-Extended-Commands.shtml
http://www.databasejournal.com/features/oracle/article.php/3875896/Purging-Oracle-Databases-Alert-Log-with-ADRCI---Usage-and-Warning.html
Regards,
Levi Pereira

Enterprise Manager Database Control Errors in Alert.log

Hi all
I'm posting it this forum because i think it is the best place to get some help, i suspect it is something in Entreprise Manager Database Console
sometimes i get errors in Alert.log
Errors in file e:\admin\orapd\udump\orapd_ora_3456.trc:
ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 492
ORA-06512: at line 1
Generally this error is generated when the database is shutdow for backup (3 AM)
In the shutdown script i terminate the DatabaseConsole service before i shutdown the database:
Shutdown Script:
@echo off
REM Script de shutdown base de dados orapd
REM Rui Madaleno , 2004/11/23
echo Shutdown consola de administracao ...
net stop oracledbconsoleorapd
echo Parar o servico OracleCSService ...
net stop oracleCSService
echo Parar o servico OracleOraApacheProcessManager
net stop OracleOraApacheProcessManager
echo Parar o Listener da base de dados
e:\oracle\bin\lsnrctl.exe stop
echo Shutting down database ORAPD ....
e:\oracle\bin\oradim.exe -shutdown -sid orapd -syspwd XXXX -shuttype srvc,inst -shutmode immediate
My environment:
Windows 2003 Server
Compaq Proliant DL580 G2 Server
Oracle Database 10.0.1.0.2
How can i avoid this errors ???
Thanks in Advance
Rui Madaleno

Dear ,
I am facing same problem, detail is
Errors in file d:\oracle\product\10.1.0\admin\oracle\udump\oracle_ora_2952.trc:
ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 492
ORA-06512: at line 1
this problem is happen suddenly and user are not get new connection with database.
thanks in advance

Database Alert log.

Similar Messages

Maybe you are looking for