-
Title
Invalid DPRMembershipAction entries with wrong Namespace -
Description
The scalar function ‘DPR_FSQTriggerWatchMemberShip’ generates the trigger “GEN_T4261A2AFAFE3CE37FDAEEE86D” on the table ‘UNSAccountBHasUNSGroupB’ based on the Target System configuration.
There is no condition specified for which DPRNamespace the DPRMembershipAction entries should be generated.
This results in invalid DPRMembershipAction entries, for example when creating UNSAccountBHasUNSGroupB entries.
The trigger contains a UNION block for each Target System for which the trigger is relevant (--> makes no sense). -
Cause
Product Defect
-
Resolution
Open a Service Request with the OID Support Team and request for Hotfix #651429.
After running the DB Transporter to install the Hotfix, regenerate the memberships triggers via the DBQueue task that handles this job.
The task name is DPR-K-TriggerCreateMembership.
For example, after importing the transport run:
DECLARE @GenProcId VARCHAR(38) = NEWID() EXEC dbo.QBM_PDBQueueInsert_Single 'DPR-K-TriggerCreateMembership', 'UNSAccountBHasUNSGroupB', NULL, @GenProcId(replace UNSAccountBHasUNSGroupB with any affected table, could also be UNSAccountBHasUNSGroupB1, UNSAccountBHasUNSGroupB2 and/or UNSAccountBHasUNSGroupB3)
You can execute this SQL code in e.g. Microsoft SSMS or Object Browser.
As an alternative, you can toggle IsAdHocSingleMemberShip (merge mode) on DPRNameSpaceHasDialogTable (disable then re-enable) in the Manager or Object Browser.
The update trigger on that table will insert a DBQueue task that performs the necessary work.
However, this approach can be very time-consuming because you must do it for every affected DPRNameSpace object. Running the SQL DBQueue task insert statement above would be better.