Answers.Body: <p>Summarizing the discussion from the comments.</p>
  
  <ol>
  <li>The error indicates that the table contains a duplicate row.</li>
  <li>After the row was updated the index could be created.</li>
  <li>To find the correct values for the row was done by examining the linked tables.</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-24T13:44:18.900Z
Answers.LastActivityDate: 2017-08-24T13:44:18.900Z
Answers.UserDisplayName: Kainuk - CiviCooP
Body: <p>I stuck with the error. When I try to repair indices I get error message: </p>
  
  <pre><code>CREATE UNIQUE INDEX index_entity_id_entity_table_account_relationship ON 
  civicrm_entity_financial_account (entity_id, entity_table, 
  account_relationship) [nativecode=1062 ** Duplicate entry '0-
  civicrm_financial_type-12' for key 
  'index_entity_id_entity_table_account_relationship']
  [type] =&gt; DB_Error
  </code></pre>
  
  <p>If I look into table see no problems.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T08:28:38.847Z
Comments.Text: What means: 0-civicrm_financial_type-12
  
  I Checked the table no duplicate for first sight on 'civicrm_financial_type' field values.
Comments.UserDisplayName: r4zoli
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T08:35:17.867Z
Comments.Text: When you say no problems, do you mean no duplicate rows?
Comments.UserDisplayName: Kainuk - CiviCooP
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T08:39:44.407Z
Comments.Text: I found it in rows: 
  
  27,civicrm_financial_type,0,12,15
  
  28,civicrm_financial_type,0,12,16
  
  Now what next?
Comments.UserDisplayName: r4zoli
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T09:19:22.047Z
Comments.Text: I found it The "0-s" is wrong values. They must be 4, and 2. The index value must be 1 or above. Can I change it?
Comments.UserDisplayName: r4zoli
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T12:24:48.923Z
Comments.Text: Well, that explains why you could not create the index, and you can retry it after the update. I do not know if the new values are functionally correct. But you did some research.
Comments.UserDisplayName: Kainuk - CiviCooP
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T12:51:06.560Z
Comments.Text: I researched the other tables, linked to this table and found these values as good as possible, Changed it, now can run indices update, finish it, but the 'Update indices' warning remains in System Status page. More work on it. But this problem solved.
Comments.UserDisplayName: r4zoli
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-24T13:45:00.083Z
Comments.Text: I summarized this discussion in an answer below.
Comments.UserDisplayName: Kainuk - CiviCooP
Tags: <upgrade>
Title: Indices repair stopped by error
ThreadText: # Indices repair stopped by error
  
  (Asked by: username_0 on 2017-08-24)
  
  I stuck with the error. When I try to repair indices I get error message: 
  CREATE UNIQUE INDEX index_entity_id_entity_table_account_relationship ON 
  civicrm_entity_financial_account (entity_id, entity_table, 
  account_relationship) [nativecode=1062 ** Duplicate entry '0-
  civicrm_financial_type-12' for key 
  'index_entity_id_entity_table_account_relationship']
  [type] => DB_Error
  
  If I look into table see no problems.
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_0**: What means: 0-civicrm_financial_type-12  I Checked the table no duplicate for first sight on 'civicrm_financial_type' field values.  
  > **username_1**: When you say no problems, do you mean no duplicate rows?  
  > **username_0**: I found it in rows:   27,civicrm_financial_type,0,12,15  28,civicrm_financial_type,0,12,16  Now what next?  
  > **username_0**: I found it The "0-s" is wrong values. They must be 4, and 2. The index value must be 1 or above. Can I change it?  
  > **username_1**: Well, that explains why you could not create the index, and you can retry it after the update. I do not know if the new values are functionally correct. But you did some research.  
  > **username_0**: I researched the other tables, linked to this table and found these values as good as possible, Changed it, now can run indices update, finish it, but the 'Update indices' warning remains in System Status page. More work on it. But this problem solved.  
  > **username_1**: I summarized this discussion in an answer below.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-08-24. Score: 1 | Accepted answer
  
  Summarizing the discussion from the comments.
  
  1. The error indicates that the table contains a duplicate row.
  2. After the row was updated the index could be created.
  3. To find the correct values for the row was done by examining the linked tables.
  
  
  ---
  
  