Error in the alert Log

Hi There,
Recently I started seeing these errors in the alert log for one of the databases:
Tue Aug 04 05:05:00 2009
Errors in file c:\oracle\product\10.2.0\admin\xxxxxx\bdump\xxxxxx_j000_6104.trc:
ORA-12012: error on auto execute of job 130961
ORA-27370: job slave failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agent failed with status: 109
ORA-27301: OS failure message: The pipe has been ended.
ORA-27302: failure occurred at: sjsec 9
ORA-27303: additional information: The pipe has been ended.
So, I tried looking at the trace file associated with the error, and here is what I get:
$ cat ebcd01_j000_6104.trc
Dump file c:\oracle\product\10.2.0\admin\xxxxxx\bdump\xxxxxx_j000_6104.trc
Tue Aug 04 05:05:00 2009
ORACLE V10.2.0.3.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Release 10.2.0.3.0 - Production
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1095M/4095M, Ph+PgF:7747M/12110M, VA:1367M/2047M
Instance name: ebcd01
Redo thread mounted by this instance: 1
Oracle process number: 53
Windows thread id: 6104, image: ORACLE.EXE (J000)
*** ACTION NAME:(DEL_ARCH_EBCP01) 2009-08-04 05:05:00.191
*** MODULE NAME:(DBMS_SCHEDULER) 2009-08-04 05:05:00.191
*** SERVICE NAME:(SYS$USERS) 2009-08-04 05:05:00.191
*** SESSION ID:(871.15642) 2009-08-04 05:05:00.191
*** 2009-08-04 05:05:00.191
ORA-12012: error on auto execute of job 130961
ORA-27370: job slave failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agent failed with status: 109
ORA-27301: OS failure message: The pipe has been ended.
ORA-27302: failure occurred at: sjsec 9
ORA-27303: additional information: The pipe has been ended.
I'm not sure what job is causing this as there is no reference and also not sure how to resolve this issue!! How can I properly trace back these errors? Any ideas or tips to what should I do?
I'm running 10.2.0.3 database on windows 2003 server.
Thanks

I found the problem.. the executable job was referring to a none existing batch file..
I have refreshed the database from production some time ago and the jobs I have setup are referring to production scripts and paths (which we didnt have on dev)..
This is now resolved.
Thanks

Similar Messages

"Error in the alert log file " - please help

Hi ALL,
I am getting following errors in the alert log frequently.
My database version is:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
NLSRTL Version 10.2.0.1.0 - Production
Thu Aug 30 16:58:19 2007
Memory Notification: Library Cache Object loaded into SGA
Heap size 2172K exceeds notification threshold (2048K)
KGL object name :select object_name from all_objects where object_name='TOAD_PROFILER' and object_type='PACKAGE'
Thu Aug 30 17:09:36 2007
************************************************************************************

Additionally you can visit here:
Alert Error from trc files--Heap size 5236K exceeds notification threshold
geting error in alert log file
Adith

Oradism not set up correctly error in the alert log in 9.2.0.4

Hello,
I have installed 9.2.0.4 patch on top of 9.2.0.1 database.
The O/S is Solaris 5.9
The database is set to work with:
workarea_size_policy=AUTO.
The database is not working properly compared to other machines we have.
After looking in the alert log I found the following error popping after restart:
WARNING: -------------------------------
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 16, 5001]
I found the following two notes on the subject, contradicting each other and also contradicting the status of the machine:
Note:151222.1
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=151222.1
Telling me not to do the below procedure on 9.2.0.4, though I get the same error and miss the required etc entries specified.
Note:262886.1
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=262886.1
Telling me to copy oradism.sav to oradism and I already have those.
Can you please supply a full and DETAILED procedure regarding what should I do, in case it is not a procedure, please specify how I should solve the oradism not set up correctly error.
Tal Olier
[email protected]

Hi Tal,
Just looked at the notes you referred to. The first doesn't apply to 9.2.0.4. as you state. The other note is for 9.2.0.4e (note the "e", stands for embedded). This "e" release is not what you have, so that note doesn't apply either.
The AR that I referred to is for 10g, but the 9iR2 info is the same. You need to make sure that $ORACLE_HOME/bin/oradism is owned by root.

Error in the alert.log file

hi,
my database is down , when chk the alert log i found the below error
please help me
Sun Mar 8 20:06:01 2009
Errors in file /busdata/sp01/eur1/_lgi/oracle/vol1/admin/udump/sp01eur1_ora_3731494.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 5
Sun Mar 8 20:06:04 2009
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Sun Mar 8 20:06:04 2009
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled

madhukrishna wrote:
i am not authorised to start the databse or any servicesThen You have only one choice - please contact Your system administrator and he will investigate what happened, why and how to solve that.
We can't help or say what was wrong if You have no rights to do anything, even look at trace files.

Errors in the alert log upon portal 3.0.6 installation

We installed Portal 3.0.6 with with Oracle 8.1.7 on a RedHat 6.2, kernel 2.2.17 machine. We noticed the following error lines in the alert-log, just before opening the DB:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of SYS./cd252dcc_RegisterService
ORA-30511: invalid DDL operation in system triggers
ORA-06512: at "SYS.DBMS_JAVA", line 0
ORA-06512: at line 2
Any idea what might be the problem here?
The DB and Portal seem to communicate well so far. The pool_sizes in init.ora are setup high, 50Mb each.
Thanks.
K.
null

Krassi,
Not sure what the error is. Have you tried to look at the object using DBA Studio to see if it can be recompiled?
Rich

Create custom rule: Looking for ORA errors in the alert log

I would like to create a rule to notify me when ORA errors are generated to the alert log. When I try to create a rule, I seem to only be able to choose from predefined lists. Has anyone configured a rule for this?

Grrr. This is for 10.2 Grid:
Go to databases --> select your database
Under Diagnostic summary, you'll see:
Alert Log 28-Dec-2006 09:19:48
The date part is a clickable link, click on it. Scroll to the bootom of the next page and click on:
"Generic Alert Log Error Monitoring Configuration"
Now read the page very carefully, its all self explanatory. The reason who haven't had some errors reported is because of that filter. Now set it up the way you want it.
Good luck
Bazzza

Ora -3113 error in the alert log

Hi ,
We are getting ORA-3113 error in the alertlog and i pasted below alert log entry.
VERSION INFORMATION:
TNS for Linux: Version 11.1.0.7.0 - Production
Unix Domain Socket IPC NT Protocol Adaptor for Linux: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
Time: 27-JAN-2011 16:11:25
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNSperation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.100.72.127)(PORT=2844))
Thu Jan 27 16:13:55 2011
opidcl aborting process unknown ospid (18585_47319544949952) due to error ORA-3113
Thu Jan 27 16:14:03 2011
Thread 2 advanced to log sequence 2022 (LGWR switch)
Current log# 4 seq# 2022 mem# 0: +DATA/systemprod/onlinelog/group_4.269.736019283
Current log# 4 seq# 2022 mem# 1: +FLASH1/systemprod/onlinelog/group_4.262.736019285
Thu Jan 27 16:14:13 2011
opidcl aborting process unknown ospid (14096_47207734746304) due to error ORA-3113
Thu Jan 27 16:16:34 2011
Thread 2 advanced to log sequence 2023 (LGWR switch)
Current log# 8 seq# 2023 mem# 0: +DATA/systemprod/onlinelog/group_8.319.736018999
Current log# 8 seq# 2023 mem# 1: +FLASH1/systemprod/onlinelog/group_8.3138.736018999
Thu Jan 27 16:19:33 2011
Thread 2 advanced to log sequence 2024 (LGWR switch)
Current log# 3 seq# 2024 mem# 0: +DATA/systemprod/onlinelog/group_3.268.736019049
Current log# 3 seq# 2024 mem# 1: +FLASH1/systemprod/onlinelog/group_3.261.736019051
Thu Jan 27 16:22:17 2011
What could be the workaround to resove this issue
Regards
Prem

ORA-00600/ORA-07445/ORA-03113 = Oracle bug => search on Metalink and/or call Oracle support

Need to find the way to get the actual error message in the alert log.

Hi,
I have configured OEM 11G and monitoring target versions are from 9i to 11g. Now my problem is i have defined the metrics for monitoring the alert log contents and OEM is sending alert if there is any error in the alert log but it is not showing the actual error message just it is showing as below.
============================
Target Name=IDMPRD
Target type=Database Instance
Host=oidmprd01.ho.abc.com
Occurred At=Dec 21, 2011 12:05:21 AM GMT+03:00
Message=1 distinct types of ORA- errors have been found in the alert log.
Metric=Generic Alert Log Error Status
Metric value=1
Severity=Warning
Acknowledged=No
Notification Rule Name=RULE_4_PROD_DATABASES
Notification Rule Owner=SYSMAN
============================
Is there any way to get the complete error details in the OEM alert itself.
Regards
DBA.

You need to look at the Alert Log error messages, not the "status" messages. See doc http://docs.oracle.com/cd/E11857_01/em.111/e16285/oracle_database.htm#autoId2

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

ORA-01033 Error cannot be traced in the alert log or v$views

Hello There,
I'm hoping you can shed some light on what seems a rather odd occurrence on our Production Oracle Instance.
Before i elaborate on the nature of the problem, I must confess that i am not an Oracle DBA and have been compelled to post this query since i have no joy from the in house DBA community on the origins of this error.
We've had an ORA-01033 error being issued by our ETL installation (deployed on a Linux machine) a couple of days ago whence trying to extract some data from the Oracle instance (during overnight DataWarehouse loads) which has consequently aborted the loads necessitating a cleanup.
This event has already occurred twice before, the first time being a month ago when the event was captured in the v$instance (using the Startup time column where the timestamp corroborates to the first time we experienced this issue and also ackowledged by the DBA team) and also in the V$Dataguard_status.
Since then, This error has been generated twice although there seems to be no evidence of this in either the Oracle alert log(as confirmed by DBA team) or in any of the v$views (as pointed out by Tom in an earlier post) such as DBA_LOGSTDBY_HISTORY, v$logstdby_state, $logstdby_stats, dba_logstdby_log, dba_logstdby_events,v$dataguard_status, v$dataguard_stats, v$dataguard_config,v$database,v$database_incarnation, v$managed_standby, v$standby_log, v$instance. I searched these views since i suspected a latency issue during a failover which could be the reason for the
ORA-01033 but found nothing.
The DBA team have pretty much disowned this issue since they claim to not have any actual evidence of this from the logs and this is the crux of the matter here.
The Problem i have as the downstream "recepient" of this error is to prove to the DBA team that this is indeed a genuine issue with the Oracle instance affecting it's availability and concomittantly affecting the DW loads.
FYI, The Oracle instance is in Failover mode, so it's swiftly back online after bombing out for a few seconds.
Also, I don't have access to the Alert log as it's a Production environment and employs restricted access policy to the server.
Having said that, Is there anything else besides the obvious ORA errors that should be looked for in the Alert log?
Where else can ORA-01033 errors be traced/traced in the Dictionary besides the Alert Log?
Thoughts??
Regards

Thank You John for that query, but i'm on V10.2 and this view is relevant for 11g and beyond i believe.
Perhaps there is an equivalent for V10g?
I am also a bit bemused by the comment earlier about no trace being left behind if the DBA's performed a manual restart, surely it doesn't matter how the DB is restarted, the event is captured in the dictionary?
In the meantime, I've got a copy of the Alert log and have found redo log issues (DBWR/LGWR) very close to the time (a min after ORA-01033) of the shutdown event.
ALTER SYSTEM ARCHIVE LOG
Thread 1 cannot allocate new log, sequence 117732
Checkpoint not complete
I've looked into this a fair bit and this error apparently causes Oracle to suspend all processing on the database until the log switch is made.
Is this the causal link for my issue?
Does " suspend all processing on the database " actually translate into an actual ORA-01033 error (or some form of) when the ETL application is trying to connect to and extract data from the Oracle database at that time?
Edited by: shareeman on 16-Oct-2012 03:50

How to be notified for all ORA- Errors recorded in the alert.log file

based on Note:405396.1, I Changed the Matches Warning from the default value ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] to ORA-* in order to receive an warning alert for all ORA- errors.
but I just recieved the alert like the following:
Metric=Generic Alert Log Error
Time/Line Number=Mon Feb 25 23:52:21 2008/21234
Timestamp=Feb 26, 2008 12:06:03 AM EST
Severity=Warning
Message=ORA-error stack (1654, 1654, 1654) logged in /opt/oracle/admin/PRD/bdump/alert_PRD.log.
Notification Rule Name=Alert Log Error
Notification Rule Owner=SYSMAN
as you can see, the message only indicate the ORA-1654, nothing else.
How to set in 10g grid control to get the details alert that in the alert log like:
"ORA-1654: unable to extend index ADM.RC_BP_STATUS by 1024 in tablespace PSINDEX"
I can't believe Oracle 10g Grid control only provide the ORA- number without details

Go to your database target.
On the home tab, on the left hand side under Diagnostic Summary, you'll see a clickable date link next to where it says 'Alert Log'. Click on that.
next click on Generic Alert Log Error Monitoring Configuration (its at the bottom)
In the alert thresholds put:
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]
I believe that will pick anything up but experiment, its only perl.
If you want to test this use the DBMS_System.ksdwrt package but I would advise you only do so on a test database. If you've never heard of it, google it. Its a way of writing to your alert log.
Make sure you have your emails sent to long format as well.

Not clearable : 1 distinct types of ORA- errors have been found in the alert log.

( Correct me if I'm wrong.)
What could be the reason for the fact that the event "1 distinct types of ORA- errors have been found in the alert log." is not clearable?
Even if the problem is solved, the ORA- error will still be in the alert.log.
Therefore the event would eventually only disappear after 7 days.
Doesn't sound very logical to me.

- The event page showing a warning event for "Generic Alert Log Error Status" metric,
- "Generic Alert Log Error Status" event is a statefull metric,
- On each evaluation of the metric defined as 'Statefull', the Cloud Control Agent recalculates the severity,
- This means, EM Agent scans the alert log for ORA errors, "Generic Alert Log Error Status" will return the number of ORA error found,
- Whenever the returned number is grater than the assigned thresholds of "Generic Alert Log Error Status", an alert is raised on EM console,
- On the next scan of alert log file, this alert will be cleared ONLY if the collected value is less than the assigned threshold,
- By checking your system, the warning threshold of "Generic Alert Log Error Status" is 0, so whenever a single ORA error is found in alert log, a warning event will be raised and you will not be able to clear it manually as this is a stateful metric.
There are three cases where this alert can be cleared:
1. The agent found 0 ORA errors in Alert log, then the alert will be cleared automatically
2. Manual clear: By disabling/enabling the metric
3. Manual clear and further not receiving similar alerts frequently: By assigning higher thresholds values
So, I suggest to disable the metric, then, enable it after some time as follows as follows:
- Go to the problematic database home page >> open the 'Oracle Database' drop-down menu >> 'Monitoring' >> 'Metric and Collection Settings',
- Choose 'All metrics' from the 'View' drop-down list >> search for the 'Generic Alert Log Error Status' metric,
- Click the pencil icon under 'Edit' column opposite to the above metric >> remove the Warning Threshold (make it empty) >> 'Continue' >> 'OK'.
- Wait for the next collection schedule in order for the warning events to be cleared, then, enable the metric again with the same steps (setting Warning Threshold=0).
References:
Note 604385.1 Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric
Note 733784.1 What are Statefull and Stateless Metrics in Enterprise Manager - Explanation and Example
HTH
Mani

Question about the Initialization Parameters Information in the Alert.log

Hi, All -
What is the correct answer for the following question.
Specifically, what information does Oracle provide you with in the alert.log regarding initialization parameters?
a. Values of all initialization parameters at startup
b. Values of initialization parameters modified since last startup
c. Values of initialization parameters with non-default values
d. Only values of initialization parameters that cannot be modified dynamically.
I think the answer should be B, but I would like to confirm.

The answer is C
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm#sthref1633
The alert log is a special trace file. The alert log of a database is a chronological log of messages and errors, and includes the following items:
All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur
Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements
Messages and errors relating to the functions of shared server and dispatcher processes
Errors occurring during the automatic refresh of a materialized view
The values of all initialization parameters that had nondefault values at the time the database and instance start
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com

Ora-07445 reported in the alert log file

Hi all,
We are using the following platform:-
OS: Solaris Operating System (SPARC 32-bit)
Oracle Server - Enterprise Edition / Product Version: 9.2.0.5.0
We encountered the following problem:-
There is Ora-07445 reported in the alert log file.
"ORA-07445: exception encountered: core dump [kgghash()+308] [SIGSEGV] [Address not mapped to object] [0x3222
000] [] []reported in the database."
These errors are signaled in more than 3 independent, unexplained, occurrences every day.
When this error occurred while User was accessing the application system, by right the case will be shown on the system, but they were no case found.
alert log are as below:-
Fri Jul 27 09:12:30 2007
Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27371.trc:
ORA-07445: exception encountered: core dump [kgghash()+340] [SIGSEGV] [Address not mapped to object] [0x3184000] [] []
Fri Jul 27 09:22:10 2007
Thread 1 advanced to log sequence 10730
Current log# 2 seq# 10730 mem# 0: /disc3/oracle9205/RFDB/RDO/logRFDB2a.rdo
Current log# 2 seq# 10730 mem# 1: /disc3/oracle9205/RFDB/RDO/logRFDB2b.rdo
Fri Jul 27 09:29:26 2007
Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27372.trc:
ORA-07445: exception encountered: core dump [kgghash()+296] [SIGSEGV] [Address not mapped to object] [0x3182000] [] []
The applications have encountered ora-3113 after a short period of time followed by ora-3114.
application log:-
RF0120-1 2007-Jul-27 09:46:57] Load m[RF0120-1 2007-Jul-27 09:29:30] SQLCODE: -3113
[RF0120-1 2007-Jul-27 09:29:30] Error Code -4105 returning from get score pan no.
[RF0120-1 2007-Jul-27 09:29:30] Message type :120
[RF0120-1 2007-Jul-27 09:29:30] Primary Account Number(PAN) DE0
02 :5440640155262702
[RF0120-1 2007-Jul-27 09:29:30] Processing code DE003 :003000
[RF0120-1 2007-Jul-27 09:29:30] Transaction amount DE004 :000000000001
[RF0120-1 2007-Jul-27 09:29:30] Settlement amount DE005 :000000000000
[RF0120-1 2007-Jul-27 09:29:30] Transmission Date and time
DE007 :0727092717
[RF0120-1 2007-Jul-27 09:29:30] Settlement conversion rate DE009 :60263158
[RF0120-1 2007-Jul-27 09:29:30] System trace audit no. DE011 :754710
[RF0120-1 2007-Jul-27 09:29:30] Local transaction time DE012 :092717
[RF0120-1 2007-Jul-27 09:29:30] Local transaction date DE013 :0727
[RF0120-1 2007-Jul-27 09:29:30] Expiration date D
E014 :0712
[RF0120-1 2007-Jul-27 09:29:30] Settlement date DE015 :0727
[RF0120-1 2007-Jul-27 09:29:30] Merchant type DE018 :5311
[RF0120-1 2007-Jul-27 09:29:30] Point-of-service(POS) entry code DE022 :051
[RF0120-1 2007-Jul-27 09:29:30] Acquiring inst. ID code DE032 :001912
[RF0120-1 2007-Jul-27 09:29:30] Forwarding Inst. ID code DE033 :001912
[RF0120-1 2007-Jul-27 09:29:30] Retrieval ref. no.
DE037 :754710356390
[RF0120-1 2007-Jul-27 09:29:30] Autholization ID response DE038 :356390
[RF0120-1 2007-Jul-27 09:29:30] Response code DE039 :00
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor terminal ID DE041 :19306002
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor ID code DE042 :000001106
020132
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor Name/Location
What could have caused the above mentioned errors i.e Ora-07445 ; ora-3113 / ora-3114? How to resolve the problem.
Please help .
Thanks.

i am also facing the same some time in ora 9.2.0.6 on Sun OS 9 SPARC 64-bits
Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6076.trc:
ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
Thu Aug 30 08:52:39 2007
Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6078.trc:
ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
Thu Aug 30 09:41:49 2007

ORA-07445 in the alert log when inserting into table with XMLType column

I'm trying to insert an xml-document into a table with a schema-based XMLType column. When I try to insert a row (using plsql-developer) - oracle is busy for a few seconds and then the connection to oracle is lost.
Below you''ll find the following to recreate the problem:
a) contents from the alert log
b) create script for the table
c) the before-insert trigger
d) the xml-schema
e) code for registering the schema
f) the test program
g) platform information
Alert Log:
Fri Aug 17 00:44:11 2007
Errors in file /oracle/app/oracle/product/10.2.0/db_1/admin/dntspilot2/udump/dntspilot2_ora_13807.trc:
ORA-07445: exception encountered: core dump [SIGSEGV] [Address not mapped to object] [475177] [] [] []
Create script for the table:
CREATE TABLE "DNTSB"."SIGNATURETABLE"
(     "XML_DOCUMENT" "SYS"."XMLTYPE" ,
"TS" TIMESTAMP (6) WITH TIME ZONE NOT NULL ENABLE
) XMLTYPE COLUMN "XML_DOCUMENT" XMLSCHEMA "http://www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd" ELEMENT "Object"
ROWDEPENDENCIES ;
Before-insert trigger:
create or replace trigger BIS_SIGNATURETABLE
before insert on signaturetable
for each row
declare
-- local variables here
l_sigtab_rec signaturetable%rowtype;
begin
if (:new.xml_document is not null) then
:new.xml_document.schemavalidate();
end if;
l_sigtab_rec.xml_document := :new.xml_document;
end BIS_SIGNATURETABLE2;
XML-Schema (xmldsig-core-schema.xsd):
=====================================================================================
<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xdb="http://xmlns.oracle.com/xdb"
targetNamespace="http://www.w3.org/2000/09/xmldsig#" version="0.1" elementFormDefault="qualified">

<xs:simpleType name="CryptoBinary">
<xs:restriction base="xs:base64Binary">
</xs:restriction>
</xs:simpleType>

<xs:element name="Signature" type="ds:SignatureType"/>
<xs:complexType name="SignatureType">
<xs:sequence>
<xs:element ref="ds:SignedInfo"/>
<xs:element ref="ds:SignatureValue"/>
<xs:element ref="ds:KeyInfo" minOccurs="0"/>
<xs:element ref="ds:Object" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="SignatureValue" type="ds:SignatureValueType"/>
<xs:complexType name="SignatureValueType">
<xs:simpleContent>
<xs:extension base="xs:base64Binary">
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>

<xs:element name="SignedInfo" type="ds:SignedInfoType"/>
<xs:complexType name="SignedInfoType">
<xs:sequence>
<xs:element ref="ds:CanonicalizationMethod"/>
<xs:element ref="ds:SignatureMethod"/>
<xs:element ref="ds:Reference" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="CanonicalizationMethod" type="ds:CanonicalizationMethodType"/>
<xs:complexType name="CanonicalizationMethodType" mixed="true">
<xs:sequence>
<xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>
<xs:element name="SignatureMethod" type="ds:SignatureMethodType"/>
<xs:complexType name="SignatureMethodType" mixed="true">
<xs:sequence>
<xs:element name="HMACOutputLength" minOccurs="0" type="ds:HMACOutputLengthType"/>
<xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>

<xs:element name="Reference" type="ds:ReferenceType"/>
<xs:complexType name="ReferenceType">
<xs:sequence>
<xs:element ref="ds:Transforms" minOccurs="0"/>
<xs:element ref="ds:DigestMethod"/>
<xs:element ref="ds:DigestValue"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
<xs:attribute name="URI" type="xs:anyURI" use="optional"/>
<xs:attribute name="Type" type="xs:anyURI" use="optional"/>
</xs:complexType>
<xs:element name="Transforms" type="ds:TransformsType"/>
<xs:complexType name="TransformsType">
<xs:sequence>
<xs:element ref="ds:Transform" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:element name="Transform" type="ds:TransformType"/>
<xs:complexType name="TransformType" mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:any namespace="##other" processContents="lax"/>

<xs:element name="XPath" type="xs:string"/>
</xs:choice>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>

<xs:element name="DigestMethod" type="ds:DigestMethodType"/>
<xs:complexType name="DigestMethodType" mixed="true">
<xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>
<xs:element name="DigestValue" type="ds:DigestValueType"/>
<xs:simpleType name="DigestValueType">
<xs:restriction base="xs:base64Binary"/>
</xs:simpleType>


<xs:element name="KeyInfo" type="ds:KeyInfoType"/>
<xs:complexType name="KeyInfoType" mixed="true">
<xs:choice maxOccurs="unbounded">
<xs:element ref="ds:KeyName"/>
<xs:element ref="ds:KeyValue"/>
<xs:element ref="ds:RetrievalMethod"/>
<xs:element ref="ds:X509Data"/>
<xs:element ref="ds:PGPData"/>
<xs:element ref="ds:SPKIData"/>
<xs:element ref="ds:MgmtData"/>
<xs:any processContents="lax" namespace="##other"/>

</xs:choice>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="KeyName" type="xs:string"/>
<xs:element name="MgmtData" type="xs:string"/>
<xs:element name="KeyValue" type="ds:KeyValueType"/>
<xs:complexType name="KeyValueType" mixed="true">
<xs:choice>
<xs:element ref="ds:DSAKeyValue"/>
<xs:element ref="ds:RSAKeyValue"/>
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:complexType>
<xs:element name="RetrievalMethod" type="ds:RetrievalMethodType"/>
<xs:complexType name="RetrievalMethodType">
<xs:sequence>
<xs:element ref="ds:Transforms" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="URI" type="xs:anyURI"/>
<xs:attribute name="Type" type="xs:anyURI" use="optional"/>
</xs:complexType>

<xs:element name="X509Data" type="ds:X509DataType"/>
<xs:complexType name="X509DataType">
<xs:sequence maxOccurs="unbounded">
<xs:choice>
<xs:element name="X509IssuerSerial" type="ds:X509IssuerSerialType"/>
<xs:element name="X509SKI" type="xs:base64Binary"/>
<xs:element name="X509SubjectName" type="xs:string"/>
<xs:element name="X509Certificate" type="xs:base64Binary"/>
<xs:element name="X509CRL" type="xs:base64Binary"/>
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
<xs:complexType name="X509IssuerSerialType">
<xs:sequence>
<xs:element name="X509IssuerName" type="xs:string"/>
<xs:element name="X509SerialNumber" type="xs:integer"/>
</xs:sequence>
</xs:complexType>


<xs:element name="PGPData" type="ds:PGPDataType"/>
<xs:complexType name="PGPDataType">
<xs:choice>
<xs:sequence>
<xs:element name="PGPKeyID" type="xs:base64Binary"/>
<xs:element name="PGPKeyPacket" type="xs:base64Binary" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:sequence>
<xs:element name="PGPKeyPacket" type="xs:base64Binary"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:choice>
</xs:complexType>


<xs:element name="SPKIData" type="ds:SPKIDataType"/>
<xs:complexType name="SPKIDataType">
<xs:sequence maxOccurs="unbounded">
<xs:element name="SPKISexp" type="xs:base64Binary"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"/>
</xs:sequence>
</xs:complexType>



<xs:element name="Object" type="ds:ObjectType"/>
<xs:complexType name="ObjectType" mixed="true">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:any namespace="##any" processContents="lax"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
<xs:attribute name="MimeType" type="xs:string" use="optional"/> 
<xs:attribute name="Encoding" type="xs:anyURI" use="optional"/>
</xs:complexType>
<xs:element name="Manifest" type="ds:ManifestType"/>
<xs:complexType name="ManifestType">
<xs:sequence>
<xs:element ref="ds:Reference" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="SignatureProperties" type="ds:SignaturePropertiesType"/>
<xs:complexType name="SignaturePropertiesType">
<xs:sequence>
<xs:element ref="ds:SignatureProperty" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="SignatureProperty" type="ds:SignaturePropertyType"/>
<xs:complexType name="SignaturePropertyType" mixed="true">
<xs:choice maxOccurs="unbounded">
<xs:any namespace="##other" processContents="lax"/>

</xs:choice>
<xs:attribute name="Target" type="xs:anyURI" use="required"/>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>


<xs:simpleType name="HMACOutputLengthType">
<xs:restriction base="xs:integer"/>
</xs:simpleType>

<xs:element name="DSAKeyValue" type="ds:DSAKeyValueType"/>
<xs:complexType name="DSAKeyValueType">
<xs:sequence>
<xs:sequence minOccurs="0">
<xs:element name="P" type="ds:CryptoBinary"/>
<xs:element name="Q" type="ds:CryptoBinary"/>
</xs:sequence>
<xs:element name="G" type="ds:CryptoBinary" minOccurs="0"/>
<xs:element name="Y" type="ds:CryptoBinary"/>
<xs:element name="J" type="ds:CryptoBinary" minOccurs="0"/>
<xs:sequence minOccurs="0">
<xs:element name="Seed" type="ds:CryptoBinary"/>
<xs:element name="PgenCounter" type="ds:CryptoBinary"/>
</xs:sequence>
</xs:sequence>
</xs:complexType>
<xs:element name="RSAKeyValue" type="ds:RSAKeyValueType"/>
<xs:complexType name="RSAKeyValueType">
<xs:sequence>
<xs:element name="Modulus" type="ds:CryptoBinary"/>
<xs:element name="Exponent" type="ds:CryptoBinary"/>
</xs:sequence>
</xs:complexType>


</xs:schema>
===============================================================================
Code for registering the xml-schema
begin
dbms_xmlschema.deleteSchema('http://xmlns.oracle.com/xdb/schemas/DNTSB/www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd',
dbms_xmlschema.DELETE_CASCADE_FORCE);
end;
begin
DBMS_XMLSCHEMA.REGISTERURI(
schemaurl => 'http://www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd',
schemadocuri => 'http://www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd',
local => TRUE,
gentypes => TRUE,
genbean => FALSE,
gentables => TRUE,
force => FALSE,
owner => 'DNTSB',
options => 0);
end;
Test program
-- Created on 17-07-2006 by EEJ
declare
XML_TEXT3 CLOB := '<Object xmlns="http://www.w3.org/2000/09/xmldsig#">
                              <SignatureProperties>
                                   <SignatureProperty Target="">
                                        <Timestamp xmlns="http://www.sporfori.fo/schemas/dnts/general/2006/11/14">2007-05-10T12:00:00-05:00</Timestamp>
                                   </SignatureProperty>
                              </SignatureProperties>
                         </Object>';
xmldoc xmltype;
begin
xmldoc := xmltype(xml_text3);
insert into signaturetable
(xml_document, ts)
values
(xmldoc, current_timestamp);
end;
Platform information
Operating system:
-bash-3.00$ uname -a
SunOS dntsdb 5.10 Generic_125101-09 i86pc i386 i86pc
SQLPlus:
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Aug 17 00:15:13 2007
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning and Data Mining options
Kind Regards,
Eyðun

You should report this in a service request on http://metalink.oracle.com.
It is a shame that you put all the effort here to describe your problem, but on the other hand you can now also copy & paste the question to Oracle Support.
Because you are using 10.2.0.3; I am guessing that you have a valid service contract...

Error in the alert Log

Similar Messages

Maybe you are looking for