Can't Start Demantra Application After Applying The CPU Patch - Invalid class: com.demantra.applicationServer.metaDataObjects.user.SGEUser
Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
On : 188.8.131.52 version, Technical
When attempting to start up application server after applying CPU <Patch.17808535>
the following error occurs.
2015-06-16 15:45:39,673 BST [OC4J Launcher] ERROR appserver.error:
oracle.classloader.util.AnnotatedClassFormatError: Bad version number in .class file
Invalid class: com.demantra.applicationServer.metaDataObjects.user.SGEUser
The issue can be reproduced at will with the following steps:
1. Apply CPU Patch 17808535.
2. Recreate and redeploy demantra.war file.
3. Restart the application server.
4. Try to log into Collaborator Workbench.
The issue has the following business impact:
Due to this issue, customer can't apply CPU patch that is a prerequisite patch in order to fix the data collection issue. Upon completion of Data collection (from EBS to Demantra) a sample of series become locked and unavailable for use. Customer need to perform a bounce to restart each time this occurs in order to rectify. This requires users to log out of the system which disrupts their working.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms