Merge Customers Failed. Violation of Primary Key Constraint on T_CREDITEE

Hello, We are having a hard time with our merge-customer scheduled job (the job that runs [AP_MERGE_CUSTOMER2]). Any help on this would be very much appreciated. This job usually runs on Sundays, but as of two weeks ago, it has started to fail, complaining about Violation of Primary Key on dbo.T_CREDITEE. Below is the full error message in the logs: The job failed. The Job was invoked by Schedule 15 (Sunday at 10:59PM). The last step to run was step 1 (Merge Customers). Violation of PRIMARY KEY constraint 'PK_T_CREDITEE_1__18'. Cannot insert duplicate key in object 'dbo.T_CREDITEE'. [SQLSTATE 23000] (Error 2627) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed. At this point, our guess was that two accounts that are scheduled to be merged both have soft credits which results in a primary key violation after merge. Looking at the T_CREDITEE table, there are only two rows with dates after February (the first time the merge started to fail). We'll call them accounts 1234 and 5678. The problem is that neither of these two accounts are scheduled to be merged. The following query SELECT * FROM [dbo].[TW_POTENTIAL_DUPS] where customer_no = 1234 or customer_no = 5678 or keep_cust = 1234 or keep_cust = 5678 returns no records. Does anyone know what we are missing here? What is causing the primary key violation on T_CREDITEE?
Parents
  • Beth, I would open a support ticket.  We can help you resolve this issue.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
    Sent: Wednesday, February 22, 2012 10:11 AM
    To: Ryan Creps
    Subject: Re: [Tessitura Technical Forum] Merge Customers Failed. Violation of Primary Key Constraint on T_CREDITEE

     

    Sorry. That was a copy/paste message that obviously didn't keep any formatting....

    From: Beth Hawryluk <bounce-bethhawryluk7830@tessituranetwork.com>
    Sent: 2/22/2012 12:07:22 PM

    Hello, We are having a hard time with our merge-customer scheduled job (the job that runs [AP_MERGE_CUSTOMER2]). Any help on this would be very much appreciated. This job usually runs on Sundays, but as of two weeks ago, it has started to fail, complaining about Violation of Primary Key on dbo.T_CREDITEE. Below is the full error message in the logs: The job failed. The Job was invoked by Schedule 15 (Sunday at 10:59PM). The last step to run was step 1 (Merge Customers). Violation of PRIMARY KEY constraint 'PK_T_CREDITEE_1__18'. Cannot insert duplicate key in object 'dbo.T_CREDITEE'. [SQLSTATE 23000] (Error 2627) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed. At this point, our guess was that two accounts that are scheduled to be merged both have soft credits which results in a primary key violation after merge. Looking at the T_CREDITEE table, there are only two rows with dates after February (the first time the merge started to fail). We'll call them accounts 1234 and 5678. The problem is that neither of these two accounts are scheduled to be merged. The following query SELECT * FROM [dbo].[TW_POTENTIAL_DUPS] where customer_no = 1234 or customer_no = 5678 or keep_cust = 1234 or keep_cust = 5678 returns no records. Does anyone know what we are missing here? What is causing the primary key violation on T_CREDITEE?




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply Children
No Data