cancel
Showing results for 
Search instead for 
Did you mean: 

Incosistencies where found when checking multiprovider

Former Member
0 Kudos

Hi,

after upgrading BW from 3.x to 7.31, I'm getting this error when trying to execute a query.

Inconsistencies where found when checking MultiProvider ODS_C01

Program error in class SAPMSSY1 method: UNCAUGHT_EXCEPTION

This error occurs from analyzer and from RSRT.

The infoprovider is an ODS, not a Multiprovider. I don't understand why message talk about infoprovider.

No missing compunding characteristics are found in ODS.

RSRV check are OK.

REport RSCOMPCONS doesn't show any problema (it's normal, because ODS is not a multiprovider).

Does anybody has any idea?

Regards.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Ok have your tried to open the query with Bex query designer to check what's wrong?

Regards

Christophe

Former Member
0 Kudos

Problem is not in the query. Problem is in ODS or in Multiprovider linked to ODS by RRI.

In fact, if I try to delete master data for an infoobject present in multiprovider/ODS, I get error:

Inconsistency in metadata of using object MULTIP of Type MPRO

Former Member
0 Kudos

As close as I have been to the solution is described in this note:

2004942 - Inconsistency in metadata of using object XXX of type XXX

But problem is not solved following these instructions.

Former Member
0 Kudos

Hi have you tried to reactivate your DSO?

Regards

Christophe

Former Member
0 Kudos

Yes, it was the first thing I tried.
Everything correct.

I have found that there is a RRI defined between a multiprovider and my ODS. Checking this multiprovider I get message "no inconsistencies" and a log with "inconsistencies found".

I don't find an explanation because it is contradictory. I have checked all infoobjects, assignments, and sources for multiprovider and I can't see any error. Also I can actívate it, still a log with inconsistencies appear but another message with "no inconsistencies found" is also shown.

Also I have marked flag to avoid checking relationship as error, but problem still arises.