Answers.Body: <p>I share my solution for the problem. First of all, I did this because of a partially loaded database problem. I was getting this error when I did any CiviCRM version upgrade.</p>
  
  <p>When I checked the database, the information in the "civicrm_domain" table was displayed as "5.14.alpha1.upgrade". However, because the site was an FTP update CiviCRM version 5.19.1 was.</p>
  
  <p>First of all, I set up a backup of a time before 5.14 with a different subdomain. Then I upgraded the Joomla and CiviCRM version of this backup to the version I had problems, ie 5.14.1.</p>
  
  <p>Then I deleted everything in the database, including Joomla tables. I have thrown the SQL files with the actual site data into the SQL files of the new subdomain. In the "civicrm_domain" table, I manually changed the version information to "5.14.1".</p>
  
  <p>After that I started the update with the URL of CiviCRM 5.15.0 in Joomla Plugin Update and this time I didn't get "partially loaded database" error and the whole update was successful.</p>
  
  <p>The only problem is that any update, installation and uninstallation of the CiviCRM plug-ins is displayed. I have raised a question for this error. You can also follow it if you want. Of course, that problem will be corrected.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-20T06:16:20.310Z
Answers.LastActivityDate: 2019-11-20T06:16:20.310Z
Answers.UserDisplayName: Fatih ATEŞ
Body: <p>Under <a href="https://civicrm.stackexchange.com/questions/31636/how-to-transfer-big-data-to-a-different-domain">How to Transfer Big Data to a Different Domain</a>, I asked a question about transferring data to a different domain, but I couldn't find a solution. Before writing a comment, please read the information I have provided here. So I tried to implement my own solution. However, according to my mistake, my own solution steps did not work.</p>
  
  <hr>
  
  <p>Namely;</p>
  
  <p>I installed a joomla and CiviCRM from scratch. I didn't make any customization and updates in my installation.</p>
  
  <p>Then I threw the following tables and all log tables into new SQL. I have not encountered any errors in this transfer. (I transferred by typing _bacup next to the existing table names to avoid conflicts.)</p>
  
  <ol>
  <li>civicrm_activity</li>
  <li>civicrm_activity</li>
  <li>civicrm_activity_contact</li>
  <li>civicrm_contact</li>
  <li>civicrm_custom_field</li>
  <li>civicrm_custom_group</li>
  <li>civicrm_email</li>
  <li>civicrm_log</li>
  <li>civicrm_option_group</li>
  <li>civicrm_option_value</li>
  <li>civicrm_phone</li>
  <li>civicrm_setting</li>
  <li>civicrm_uf_match</li>
  <li>joomla_usergroups</li>
  <li>joomla_users</li>
  <li>joomla_user_usergroup_map</li>
  </ol>
  
  <p>Now when I try to log in to CiviCRM I get an error like the following. Do you know about the solution to this error?</p>
  
  <p><strong>CiviCRM_API3_Exception: "DB Error: constraint violation"</strong></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-19T08:30:03.927Z
Comments.Text: To get more information about the error. You can run the api from the API explorer and check the box debug. You will probably then get a backtrace of where in the api the error occurs.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-19T08:38:42.550Z
Comments.Text: How do I access the API when I can't log in to CiviCRM?
Comments.UserDisplayName: Fatih ATEŞ
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-19T08:41:35.417Z
Comments.Text: Ah than you are stuck because I made the assumption you could login into civicrm and just one specific api is causing a trouble. But that is not the case. This still sound you did not do the import/backup correctly.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-19T08:47:58.673Z
Comments.Text: There's serious data. CiviCRM gives an error because the export and import data from their menu is large. I can't update. I need to get these files to a clean CiviCRM. So when I make a transfer, which tables do I need to import from the database?
Comments.UserDisplayName: Fatih ATEŞ
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-19T08:58:16.333Z
Comments.Text: A rule of thumb is that you need all of them. And you dont usually have to do a transfer (or I have not come in such situations where it is really needed).
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-19T09:47:18.123Z
Comments.Text: Thank you Jaap Jansma for your answers worker. However I have a problem with the Update. And I believe that this issue will be a big problem in a future update.
  
  I'm starting an update when a new CiviCRM version arrives. At the end of the transaction
  
  The Error version I received was 5.14.1. We are currently using 5.19.1. When I update, I see version 5.19.1 at the bottom, but in the System State, the "Partially upgraded database" gives a critical error.
  
  Therefore, I believe that either this problem should be solved or a current CiviCRM installation should be transferred to my data.
Comments.UserDisplayName: Fatih ATEŞ
Tags: <joomla>
Title: CiviCRM_API3_Exception: "DB Error: constraint violation"
ThreadText: # CiviCRM_API3_Exception: "DB Error: constraint violation"
  
  (Asked by: username_0 on 2019-11-19)
  
  Under [How to Transfer Big Data to a Different Domain](https://civicrm.stackexchange.com/questions/31636/how-to-transfer-big-data-to-a-different-domain), I asked a question about transferring data to a different domain, but I couldn't find a solution. Before writing a comment, please read the information I have provided here. So I tried to implement my own solution. However, according to my mistake, my own solution steps did not work.
  
  ---
  
  Namely;
  
  I installed a joomla and CiviCRM from scratch. I didn't make any customization and updates in my installation.
  
  Then I threw the following tables and all log tables into new SQL. I have not encountered any errors in this transfer. (I transferred by typing \_bacup next to the existing table names to avoid conflicts.)
  
  1. civicrm\_activity
  2. civicrm\_activity
  3. civicrm\_activity\_contact
  4. civicrm\_contact
  5. civicrm\_custom\_field
  6. civicrm\_custom\_group
  7. civicrm\_email
  8. civicrm\_log
  9. civicrm\_option\_group
  10. civicrm\_option\_value
  11. civicrm\_phone
  12. civicrm\_setting
  13. civicrm\_uf\_match
  14. joomla\_usergroups
  15. joomla\_users
  16. joomla\_user\_usergroup\_map
  
  Now when I try to log in to CiviCRM I get an error like the following. Do you know about the solution to this error?
  
  **CiviCRM\_API3\_Exception: "DB Error: constraint violation"**
  
  **Tags:** joomla
  
  > **Comments:**
  > **username_1**: To get more information about the error. You can run the api from the API explorer and check the box debug. You will probably then get a backtrace of where in the api the error occurs.  
  > **username_0**: How do I access the API when I can't log in to CiviCRM?  
  > **username_1**: Ah than you are stuck because I made the assumption you could login into civicrm and just one specific api is causing a trouble. But that is not the case. This still sound you did not do the import/backup correctly.  
  > **username_0**: There's serious data. CiviCRM gives an error because the export and import data from their menu is large. I can't update. I need to get these files to a clean CiviCRM. So when I make a transfer, which tables do I need to import from the database?  
  > **username_1**: A rule of thumb is that you need all of them. And you dont usually have to do a transfer (or I have not come in such situations where it is really needed).  
  > **username_0**: Thank you Jaap Jansma for your answers worker. However I have a problem with the Update. And I believe that this issue will be a big problem in a future update.  I'm starting an update when a new CiviCRM version arrives. At the end of the transaction  The Error version I received was 5.14.1. We are currently using 5.19.1. When I update, I see version 5.19.1 at the bottom, but in the System State, the "Partially upgraded database" gives a critical error.  Therefore, I believe that either this problem should be solved or a current CiviCRM installation should be transferred to my data.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-11-20. Score: 1 | Accepted answer
  
  I share my solution for the problem. First of all, I did this because of a partially loaded database problem. I was getting this error when I did any CiviCRM version upgrade.
  
  When I checked the database, the information in the "civicrm\_domain" table was displayed as "5.14.alpha1.upgrade". However, because the site was an FTP update CiviCRM version 5.19.1 was.
  
  First of all, I set up a backup of a time before 5.14 with a different subdomain. Then I upgraded the Joomla and CiviCRM version of this backup to the version I had problems, ie 5.14.1.
  
  Then I deleted everything in the database, including Joomla tables. I have thrown the SQL files with the actual site data into the SQL files of the new subdomain. In the "civicrm\_domain" table, I manually changed the version information to "5.14.1".
  
  After that I started the update with the URL of CiviCRM 5.15.0 in Joomla Plugin Update and this time I didn't get "partially loaded database" error and the whole update was successful.
  
  The only problem is that any update, installation and uninstallation of the CiviCRM plug-ins is displayed. I have raised a question for this error. You can also follow it if you want. Of course, that problem will be corrected.
  
  
  ---
  
  