Two BatchOut Tables created with Same CMPR by ProcessCampaignRun
SummaryIn production environment, two BatchOuts were created with the same Id during ProcessCampaignRun activity.
Data Flow error was produced, and the campaign is in Resolved-Failed status.
Error MessagesException-2523 Rule resolution identified 2 versions of the rule with class Rule-Decision-DataSet and name DATA-BATCHOUTCMPR1609!BATCHOUTCMPR1609
Exception-2522 Cannot delete Rule RULE-DECISION-DATASET DATA-BATCHOUTCMPR1609 BATCHOUTCMPR1609 #20170123T040124.310 GMT with security checking: its RuleSet property is blank
Steps to ReproduceNot Applicable
Root CauseA defect or configuration issue in the operating environment.Based on a review of the code, this scenario should not have occurred during normal day-to-day operations. Having multiple Data Set instances with the same keys should not happen. User suspects that somehow these instances were imported onto this system.
ResolutionTo resolve this situation, one should remove one of the duplicate instances. To remove one of the duplicates, create an activity that does the following:
1. Takes in the pzInsKey
of the data set as input parameter (say Param.DSKey)
a. Step 1 - Obj-Open-By-Handle - Open the Data Set using the input parameter
2. Save this activity.
b. Step 2 - Obj-Delete on the opened Data Set
c. Step 3 - Commit
3. Next determine, the pzInsKey of the Data Sets to remove. One must remove one of each of the four duplicate Data Sets.
4. Run a report that outputs the pzInsKey for these Data Sets.
5. Run the above created activity four times. Each time, pass in one of the Data Set pzInsKey to be deleted.
Published April 13, 2017 - Updated May 9, 2017