The first problem reported by my EM 12c is an ORA-7445 error. After checking the alert log following is the exact message:
Sun Feb 19 12:09:41 2012 Errors in file /u01/app/oracle/diag/rdbms/pkldb/pkldb/trace/pkldb_j035_14712.trc (incident=52961): ORA-07445: exception encountered: core dump [kokscold()+849] [SIGSEGV] [ADDR:0x50] [PC:0x115E16F] [Address not mapped to object]  Incident details in: /u01/app/oracle/diag/rdbms/pkldb/pkldb/incident/incdir_52961/pkldb_j035_14712_i52961.trc
From the incident trace file:
*** 2012-02-19 12:09:43.016 dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0) ----- Current SQL Statement for this session (sql_id=azmq8z48r7wk4) ----- /* SQL Analyze(117,1) */ MERGE INTO MGMT_ARU_PATCH_RECOMMENDATIONS p USING (SELECT :1 as patch_guid, :2 as PATCH_TYPE, :3 as BUG_ID, :4 as REQUEST_ID, :5 as PLATFORM_ID, :6 as PRODUCT_ID, :7 as RELEASE_ID , :8 as LANGUAGE_ID, :9 as CLASSIFICATION_ID, :10 as PLATFORM, :11 as PRODUCT, :12 as RELEASE, :13 as LANGUAGE, :14 as CLASSIFICATION, :15 as ARU_TARGET_TYPE, :16 as ABSTRACT, :17 as RELEASE_DATE, :18 as LOAD_TIMESTAMP, :19 as TEXT_CONTENT, :20 as SUPPORT_LEVEL, :21 as SUPPORT_LEVEL_ID FROM DUAL) n ON (p.patch_guid = n.patch_guid) WHEN MATCHED THEN UPDATE SET p.PATCH_TYPE = n.PATCH_TYPE, p.BUG_ID = n.BUG_ID, p.REQUEST_ID = n.REQUEST_ID, p.PLATFORM_ID = n.PLATFORM_ID, p.PRODUCT_ID = n.PRODUCT_ID, p.RELEASE_ID = n.RELEASE_ID, p.LANGUAGE_ID = n.LANGUAGE_ID, p.CLASSIFICATION_ID = n.CLASSIFICATION_ID, p.PLATFORM = n.PLATFORM, p.PRODUCT = n.PRODUCT, p.RELEASE = n.RELEASE, p.LANGUAGE = n.LANGUAGE, p.CLASSIFICATION = n.CLASSIFICATION, p.ARU_TARGET_TYPE = n.ARU_TARGET_TYPE, p.ABSTRACT = n.ABSTRACT, p.RELEASE_DATE = n.RELEASE_DATE,p.LOAD_TIMESTAMP = n.LOAD_TIMESTAMP, p.TEXT_CONTENT = n.TEXT_CONTENT, p.SUPPORT_LEVEL = n.SUPPORT_LEVEL, p.SUPPORT_LEVEL_ID = n.SUPPORT_LEVEL_ID WHEN NOT MATCHED THEN INSERT (PATCH_GUID, PATCH_TYPE, BUG_ID, REQUEST_ID, PLATFORM_ID, PRODUCT_ID, RELEASE_ID, LANGUAGE_ID, CLASSIFICATION_ID, PLATFORM, PRODUCT, RELEASE, LANGUAGE, CLASSIFICATION, ARU_TARGET_TYPE, ABSTRACT, RELEASE_DATE,LOAD_TIMESTAMP, TEXT_CONTENT, SUPPORT_LEVEL, SUPPORT_LEVEL_ID) VALUES (n.PATCH_GUID, n.PATCH_TYPE, n.BUG_ID, n.REQUEST_ID, n.PLATFORM_ID, n.PRODUCT_ID, n.RELEASE_ID, n.LANGUAGE_ID, n.CLASSIFICATION_ID, n.PLATFORM, n.PRODUCT, n.RELEASE, n.LANGUAGE, n.CLASSIFICATION, n.ARU_TARGET_TYPE, n.ABSTRACT, n.RELEASE_DATE,n.LOAD_TIMESTAMP, n.TEXT_CONTENT, n.SUPPORT_LEVEL, n.SUPPORT_LEVEL_ID) ----- PL/SQL Call Stack ----- object line object handle number name 0x80bd47c0 11774 package body SYS.DBMS_SQLTUNE_INTERNAL 0x80b50a80 7 SYS.WRI$_ADV_SQLTUNE 0x82d550f8 545 package body SYS.PRVT_ADVISOR 0x82d550f8 2613 package body SYS.PRVT_ADVISOR 0x80bf0da8 241 package body SYS.DBMS_ADVISOR 0x81987268 772 package body SYS.DBMS_SQLTUNE 0x8187d290 4 anonymous block *** 2012-02-19 12:09:42.839 > (0x115e16f) mov 0x50(%r11),%rdx (0x115e173) movzbl 0x1(%r13),%ecx (0x115e178) movzbl 0x1(%r15),%r9d (0x115e17d) mov 0x8(%rdx),%edx (0x115e180) lea 0x10(%r13),%r8
The error seems to be coming from some automated scheduled SQL Tuning Task (Yet to figureout that). Searching at MOS gives reference to bug 9594372, which shows that the problem is with merge statement. It says that applying the patch will fix the issue.
While checking the error from my EM12c, it also gives a search button to search the error at MOS( I have already installed the MOS plug-in) which I found is very good thing as I need not to login to separate MOS windows.