BusinessObjects Board

Match Review errors -- COR-10819 and COR-10820

Hi all,

We are encountering a couple of errors in the Match review module of Information Steward. Not sure what we are missing so any help would be greatly appreciated

Information Steward version : 14.2.3.514
Repository : MS SQL Server 2008 R2
Data review connection : MS SQL Server 2008 R2

1) Re-assign master record

Following options are selected in the Match Review Configuration
Approval Required After Review : Yes
Master Record Can Be Reassigned : Yes
Complete Review/Approval Within (Days) : 21
Default Match Status for Suspect Record : Match
Post Match Review Result : When match group review is completed
Enable Best Record Creation : No

After the Match review task was created, we reassigned the master record for one of the groups (40) and approved the same. The _act table contains 2 records with master record reassigned correctly.

But when we open the “match group list” tab to view the approved groups, we receive the below error
No master match record found; i.e., bad match result data [job instance ID= 2, group number= 40] (COR-10819)

We even updated the match table manually, with match score NULL for the newly re-assigned master record and some match score for the original master record. But still the error persists.

2) Best record creation
Same options selected as above except the below changes
Enable Best Record Creation : Yes
How : Create a new best record
Output Best Record Lineage : No
Best record output table : same as the Input table

When we approve the match group after review, we receive the below error and the best record is not created.
com.sap.is.boe.plugin.service.datareview.io.DaoException: An unexpected error occurred while accessing or updating the data. Contact your administrator. (COR-10820)

Thanks in advance


ack_83 (BOB member since 2011-06-02)

If you look in the SAP BI / SAP IPS server into the logging directory,

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging\

you will find a file called

InformationSteward.DataReviewService.log

Search for [E] in this file, and you should see a more explicit reason why things aren’t working as expected.


adelauw (BOB member since 2007-10-22)