My Oracle Support Banner

After Deploying Patchset 20.1.0.2.1, "Obdx.app.timer" Is In Failed State And Not Even Starting Manually. (Doc ID 2745316.1)

Last updated on JANUARY 25, 2021

Applies to:

Oracle Banking Digital Experience - Version 20.1.0.0.0 to 20.1.0.0.0 [Release 20]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
After 20.1.0.2.1 Patchset(PS) deployment obdx.app.timer is in failed state and not even starting manually

and getting below errors in OBDx logs.

ERROR
-----------------------

Caused By: java.lang.NoSuchMethodError: com.ofss.digx.app.common.timer.service.TimerDetailsService.read(Lcom/ofss/fc/app/context/SessionContext;Lcom/ofss/digx/app/timer/dto/TimerDetailsDTO;)Lcom/ofss/digx/app/timer/dto/TimerDetailsResponseDTO;
at com.ofss.digx.timer.AbstractTimer.initialize(AbstractTimer.java:147)


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
References


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