cancel
Showing results for 
Search instead for 
Did you mean: 

Error while refreshing the EPM Report

Niranjan_K
Advisor
Advisor
0 Kudos

Hi Team,

While refreshing the EPM report we are getting below Error.

One or more errors occurred.
The execution of report Default Report failed. Please contact your administrator.
Bad request.

Server message:

code: UJO_READ_EXCEPTION_000
severity: error
description: MDX statement error:"ORA-00904: "H6"."SEQ_NR": invalid identifier"
log id: 01LT1BME7jcQuqoq7No0zG
DATAVALUE:ORA-00904: "H6"."SEQ_NR": invalid identifier
MDX:
V1:
V2:
V3:
V4:

-----------------

Framework message:
The remote server returned an error: (400) Bad Request.

The remote server returned an error: (400) Bad Request.

epm-refresh-error.jpg

I have cleared cache with "UJA_REFRESH_DIM_CACHE" Program and "Refresh the Metadata" in the report but no luck. The reports are worked properly earlier.

If anyone faces a smellier issue, please let me know .

Thanks in Advance,

former_member186338
Active Contributor
0 Kudos

Please use "Insert Image" instead of incorrect "Insert File" if you want an answer from me.

Accepted Solutions (0)

Answers (4)

Answers (4)

srshekars
Participant
0 Kudos

Hi Niranjan,

If it is BPC Standard Model, then Clear the BPC/BW cache in SE38 using following reports:

- UJA_REFRESH_DIM_CACHE (flag "Refresh all dimensions)

- UJXO_CLEAN_CACHE

- UJXO_CLEAN_DIM_CACHE (you don't have to select a dimension. leave the dimension field blank, It will apply to all)

This will help you to clear cache and refresh the dimension/s.

- T.Code: RSRCACHE - search for /CPMB/ objects (Model Technical Names) and delete them. This will also clear the clears the cache at Model level.

Thanks

Raja Sekhar

Niranjan_K
Advisor
Advisor
0 Kudos

Hi Sekhar,

I have tried all the options already but no luck, We have raised an issue with SAP. let's wait for the replay.

Thanks,

Niranjan K

tamil_arasan
Active Contributor
0 Kudos

Hi Niranjan,

ORA-00904 Error is occurs if non-existence column is specified in the SQL statement however sometimes due to program errors also cause ORA-00904. Can you please check if any dump occurred in ST22 ?

Thanks,

Pradeep

Niranjan_K
Advisor
Advisor
0 Kudos

Hi Pradeep,

System not generated any dump.

Thanks,

Niranjan K

tamil_arasan
Active Contributor
0 Kudos

Any additional error messages/clues from SLG1 transaction ?

Thanks,

Pradeep

Niranjan_K
Advisor
Advisor
0 Kudos

splevel.jpgHi Pradeep,

Thanks for the replay, I have checked the note and it's related to BW 7.3.

But we are BW -7.4 sp21 and BPC 10.1 sp 16

Will it be useful for BW 7.4? and may I know the reason for issue.

Thanks

Niranjan

former_member186338
Active Contributor
0 Kudos

"Will it be useful for BW 7.4" - no!

tamil_arasan
Active Contributor
0 Kudos

Hi,

Check if this note suitable for your issue/release https://launchpad.support.sap.com/#/notes/1671190

Thanks,

Pradeep

former_member186338
Active Contributor
0 Kudos

Hope that question author is not on BW SP mentioned in this note)))

tamil_arasan
Active Contributor
0 Kudos

Yes but he has not mentioned release details in the initial question , shared the note upon assumption

former_member186338
Active Contributor
0 Kudos

Well, there is some very low probability that in 2019 the question author is using the system from 2012 🙂

tamil_arasan
Active Contributor
0 Kudos

Who knows I still have customer who is using system from 2000 🙂 anyway will make note of the version of KBA before posting 🙂