OEM 13C : Enterprise Manager Not Sending Database Down Alerts - Incident Manager Reports 'Updated State By Skipping Rule Processing'
(Doc ID 2863036.1)
Last updated on APRIL 06, 2023
Applies to:
Enterprise Manager for Oracle Database - Version 13.4.0.0.0 and laterEnterprise Manager Base Platform - Version 13.5.0.0.0 to 13.5.0.0.0 [Release 13c]
Information in this document applies to any platform.
Symptoms
Enterprise Manager is not able to send target down alerts for any target type like Database, even though the incident rule set is configured for Warning, Critical, Clear alerts. Only the clear alerts are being sent by Enterprise Manager. When navigated to incident manager and looked at the DOWN event, the incident manager shows update as 'Updated State By Skipping Rule Processing'. So incident rule is skipping all the DOWN events.
-----------
022-04-14 09:08:48,794 [#EM_SYSTEM_POOL#:resourcemanager] WARN jobs.JobDispatcherStats logp.251 - Failed to write job dispatcher statistics to the repository
java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:510)
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:462)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1105)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:551)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:656)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:271)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:92)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:971)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1280)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3719)
at oracle.jdbc.driver.T4CPreparedStatement.executeInternal(T4CPreparedStatement.java:1427)
at oracle.jdbc.driver.OraclePreparedStatement.executeLargeUpdate(OraclePreparedStatement.java:3809)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3789)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1064)
at oracle.sysman.emSDK.core.util.jdbc.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:525)
at oracle.sysman.emdrep.jobs.JobDispatcherStats.flushStats(JobDispatcherStats.java:268)
at oracle.sysman.core.common.internalmetrics.StatsHolder.flush(StatsHolder.java:414)
at oracle.sysman.core.common.internalmetrics.StatsHolder.flush(StatsHolder.java:318)
at oracle.sysman.core.pbs.gcloader.ResourceManager.doWork(ResourceManager.java:1184)
at oracle.sysman.core.common.workmanager.Work.handleScheduledWork(Work.java:439)
at oracle.sysman.core.common.workmanager.Work.call(Work.java:284)
at oracle.sysman.core.common.workmanager.Work.call(Work.java:50)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: Error : 14400, Position : 0, Sql = INSERT INTO em_jobstep_stats (collection_time, job_owner, job_type, step_name, command_name, command_type, oms_guid, count_of_execs, count_of_milliseconds) VALUES (:1 , :2 , :3 , :4 , :5 , :6 , NULL, :7 , :8 ), OriginalSql = INSERT INTO em_jobstep_stats (collection_time, job_owner, job_type, step_name, command_name, command_type, oms_guid, count_of_execs, count_of_milliseconds) VALUES (?, ?, ?, ?, ?, ?, NULL, ?, ?), Error Msg = ORA-14400: inserted partition key does not map to any partition
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |