Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC)

MOSC Banner

Unable to purge FDMEE Work Repository after log4j remediation

in Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC) 3 commentsAnswered

We have applied the remediation steps for the log4j issue per this document:

Apache Log4j Security Alert CVE-2021-44228 also referencing CVE-2021-45046 Mitigation on Oracle Enterprise Performance Management ( Doc ID 2828262.1 )

We have come across an issue when starting FDMEE back up and not being able to purge the FDMEE work repository:

Is this due to having removed the JndiLookup.Class in the JAR files (as instructed) or something else?

FDMEE startup log:

<Dec 23, 2021 1:59:55,370 PM CAT> <Warning> <oracle.as.jmx.framework.MessageLocalizationHelper> <J2EE JMX-46041> <The resource for bundle "java.util.PropertyResourceBundle" with key "WorkRepositoryMXBean.operation.purgeWorkRepository.param

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center