Skip to Content
0

UJHANA_SQE_EXCEPTION_007 (invalidated view)

Jun 22, 2017 at 08:03 AM

66

avatar image

Hello,

after maintaining a dimension I am getting an error on opening any report (or creating one) in one model.

I have another model which contains the dimension throwing the Error "WMDCRR4". Here I can create reports without any problems.

Here is the error:

Bad request.

Server message:

code: UJHANA_SQE_EXCEPTION_007
severity: error
description: Run SQE HANA query fail
log id: 051Mgqtu7jULuyFuQmIWpG

-----------------code: UJHANA_SQE_EXCEPTION_004
severity: error
description: Run SQE HANA query fail
log id: 051Mgqtu7jULuyFuQmIWpG

-----------------code:
severity:
description: Run SQE HANA query fail
log id: 051Mgqtu7jULuyFuQmIWpG
CONNECTION_CLOSED:
CONNECTION_OPEN_ERROR:
DBOBJECT_EXISTS:
DBOBJECT_NOT_EXISTS:
DB_ERROR:X
DUPLICATE_KEY:
EXTERNAL_ERROR:
INTERNAL_ERROR:1
INVALID_CURSOR:
NO_MORE_MEMORY:
SQL_CODE:391
SQL_MESSAGE:invalidated view: $BPC$V$WMDCRR4P1: line 1 col 88 (at pos 87)
UNKNOWN_CONNECTION:

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

Framework message:
Der Remoteserver hat einen Fehler zurückgegeben: (400) Ungültige Anforderung.

Der Remoteserver hat einen Fehler zurückgegeben: (400) Ungültige Anforderung.

System Data:

HANABPC 8.10 SP7

CPMBPC 8.10 SP7

SAPBASIS 7.40 SP12

SAPBW 7.40 SP12

I tried applying note:

2248959 - Missing HANA view error when refreshing EPM Report

This note seems to have the same problem, except that the SQL_CODE and message is slightly different.

It didn't help though. I also tried executing the program UJXO_CLEAN_DIM_CACHE, but it didn't help either.

Anyone had this problem ever before?

Best regards,

Alex

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Vadim Kalinin Jun 22, 2017 at 08:09 AM
0

As far as I remember there are number of notes related to DUPLICATE KEY issue.

Try to upgrade to the latest SP for BPC and BW.

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Why do you think it is a duplicate key issue?

0

Ups... not sure :) Just read your question once again...

Anyway the note is not very informative...

If you upgrade to the latest SP this issue may disappear...

0