My Oracle Support Banner

Grid Control Performance: OMS Crashes Every Night due to Job Dispatcher's Failure to Connect to Repository Database (Doc ID 559298.1)

Last updated on NOVEMBER 09, 2019

Applies to:

Enterprise Manager Base Platform - Version to [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 29-07-2012***


The OC4J_EM / OMS process crashes each night around 21:00. Due to this issue, the scheduled jobs are failing with :

'A management system issue (eg., the oms and/or repository was down, which prevented the execution from running).'

The emoms.trc shows :

2008-02-14 20:59:56,421 [HealthMonitor] ERROR emd.main run.299 - 
HealthMonitor : Found errant task : TaskRegn:ID10,Callback:class,Iterative:true,Duration:300,DueTime:12030
2008-02-14 20:59:56,431 [HealthMonitor] INFO pingPastDue.1797 - 
Entry - aborting eml.  Job Dispatcher id=168
2008-02-14 20:59:56,432 [HealthMonitor] ERROR emd.main restart.418 - 
HealthMonitor Feb 14, 2008 8:59:56 PM Job Dispatcher error: Job Dispatcher 
timed out.  Job Dispatcher id=168

2008-02-14 20:59:56,451 [HealthMonitor] DEBUG emd.main 
executeDiagnosticCommands.498 - HealthMonitor :  OMS_DIAG_MODULES 
2008-02-14 20:59:56,474 [HealthMonitor] DEBUG emd.main executeCommand.610 - 
HealthMonitor : Executing diagnostic command for module omsThread. Feb 14, 
2008 8:59:56 PM

- The mgmt_system_error_log shows these errors for the Jobs :

02/11/2008 20:54 Exception when
retrieving oms name for job id 167:ORA-01403:no data found

- EMDiag does not show any issues with the Job system.

OMS has to be re-started manually each morning.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.