My Oracle Support Banner

ECC Developer Responsibility Shows 400 Bad Request Error When Accessing Dashboard. (Doc ID 2772358.1)

Last updated on APRIL 30, 2021

Applies to:

Oracle Enterprise Command Center Framework - Version 12.2.8 and later
Information in this document applies to any platform.

Symptoms

When attempting to access Dashboard from ECC developer the following error occurs


400 Bad Request: {"title":"Attribute with key EXP_COST_POOL doesn't exist for dataset fa-asset","errorKey":null,"stackTraceStr":null,"status":400,"detail":[{"methodName":"addNewDimension","fileName":"AggregatorModel.java","lineNumber":320,"className":"oracle.ecc.index.retrieve.aggregators.model.AggregatorModel","nativeMethod":false},{"methodName":"parse","fileName":"AggregatorModel.java","lineNumber":197,"className":"oracle.ecc.index.retrieve.aggregators.model.AggregatorModel","nativeMethod":false},{"methodName":"aggregate","fileName":"RollupAggregator.java","lineNumber":44,"className":"oracle.ecc.index.retrieve.aggregators.impl.RollupAggregator","nativeMethod":false}],"


ERROR

400 Bad Request


STEPS

The issue can be reproduced at will with the following steps:

1/ Responsibility : ECC Developer
2/ M: ECC developer -> Assets.



Changes

 

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
Changes
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.