Answers.Body: <p>It's been so long since I looked at that docs page - the numbering has got messed up I think and in any case it's a difficult read. First, do NOT use <code>--ignore-table</code> when moving an existing site with live data. It does say that in 7b but it's hard to see.</p>
  <p>Then second, it stops at step 8 and then starts at 1 again, but it should really be continuing on. You need to do those other steps too.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-03-17T15:29:38.790Z
Answers.Text: I did see the comment '*** If copying an existing install don't skip the cache tables they will not be created automatically" but I read this as if I was copying code from one site to another rather than using a new installed. I did a dump and restore without --ignore-table but the site sill errors out. I wonder if I need to install CiviCRM 5.19 under Drupal 7.89, restore the DB, then upgrade 5.19 to 5.47? Or, should I be able to restore a dump of Civi 5.19 to Civi 5.47?
Answers.UserDisplayName: carclubadmin
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-03-17T19:09:50.133Z
Answers.Text: That might be a good sanity check but note I don't think 5.19 officially supports php 7.4, but might work.  Since it's a jump over 28 releases, you might have to go in smaller steps. Also stick to 5.46 for now if using CiviEvents - you don't want 5.47. Also the full error will be in sites/default/files/civicrm/ConfigAndLog.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-03-17T20:24:44.703Z
Answers.Text: You are right. Too big of a jump. 5.19 fails to start up after the install. Thanks for the advice in 5.46. I may try a data dump and import to see if that works.
Answers.UserDisplayName: carclubadmin
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-03-17T05:14:27.553Z
Answers.LastActivityDate: 2022-03-17T05:14:27.553Z
Answers.UserDisplayName: Demerit
Body: <p>We are attempting to move off an old machine and onto a new but restoration of CiviCRM constantly fails with the error:</p>
  <p>Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred.
  DB Error: no such field</p>
  <p>Here are the details</p>
  <p>Old Machine:
  Drupal: 7.78
  CiviCRM: 5.19
  MySQL 5.5
  PHP: 7.2</p>
  <p>New Machine
  Drupal 7.89
  CiviCRM: 5.47.1
  MySQL: 8
  PHP: 7.4</p>
  <p>Moving Drupal was a breeze. No major issues. But Civi seems to require more intervention or skill that I do not yet possess.</p>
  <p>I am dumping the old data using (where the Civi database is called civicrm)</p>
  <p>mysqldump -u root -p --ignore-table=civicrm.civicrm_domain --ignore-table=civicrm.civicrm_acl_cache --ignore-table=civicrm.civicrm_acl_contact_cache --ignore-table=civicrm.civicrm_group_contact_cache civicrm &gt; civi-sql-dump.sql</p>
  <p>And ingesting the data using
  mysql -u root -p civicrm &lt; civi-sql-dump.sql</p>
  <p>But this fails to work. I've followed the instructions at <a href="https://docs.civicrm.org/sysadmin/en/latest/misc/switch-servers/" rel="nofollow noreferrer">https://docs.civicrm.org/sysadmin/en/latest/misc/switch-servers/</a> but after a few tries, no success.</p>
  <p>Is it possible to move between the two machine noted above? Would it just be faster to export data and re-import it and just re-setup Civi? I've check the log file /var/www/drupal/sites/default/files/civicrm/ConfigAndLog and it's a huge mess.</p>
  <p>What are my options here? Thanks in advance for any tips or advice.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-03-17T05:08:12.770Z
Comments.Text: is it possible you didn't skip triggers with the db dump? Our team use
  
  perl -pi -e 's#\/\*\!5001[7|3].*?`[^\*]*\*\/##g'
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-03-17T05:17:30.057Z
Comments.Text: I think that will be ok as long as they do the trigger rebuild step in the second 5e (which is really step 13e).
Comments.UserDisplayName: Demerit
Tags: <drupal><civicrm-home>
Title: CiviCRM database restore fails on new server
ThreadText: # CiviCRM database restore fails on new server
  
  (Asked by: username_0 on 2022-03-17)
  
  We are attempting to move off an old machine and onto a new but restoration of CiviCRM constantly fails with the error:
  
  Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred.
  DB Error: no such field
  
  Here are the details
  
  Old Machine:
  Drupal: 7.78
  CiviCRM: 5.19
  MySQL 5.5
  PHP: 7.2
  
  New Machine
  Drupal 7.89
  CiviCRM: 5.47.1
  MySQL: 8
  PHP: 7.4
  
  Moving Drupal was a breeze. No major issues. But Civi seems to require more intervention or skill that I do not yet possess.
  
  I am dumping the old data using (where the Civi database is called civicrm)
  
  mysqldump -u root -p --ignore-table=civicrm.civicrm\_domain --ignore-table=civicrm.civicrm\_acl\_cache --ignore-table=civicrm.civicrm\_acl\_contact\_cache --ignore-table=civicrm.civicrm\_group\_contact\_cache civicrm > civi-sql-dump.sql
  
  And ingesting the data using
  mysql -u root -p civicrm < civi-sql-dump.sql
  
  But this fails to work. I've followed the instructions at <https://docs.civicrm.org/sysadmin/en/latest/misc/switch-servers/> but after a few tries, no success.
  
  Is it possible to move between the two machine noted above? Would it just be faster to export data and re-import it and just re-setup Civi? I've check the log file /var/www/drupal/sites/default/files/civicrm/ConfigAndLog and it's a huge mess.
  
  What are my options here? Thanks in advance for any tips or advice.
  
  **Tags:** drupal, civicrm-home
  
  > **Comments:**
  > **username_1**: is it possible you didn't skip triggers with the db dump? Our team use  perl -pi -e 's#\/\*\!5001[7|3].*?`[^\*]*\*\/##g'  
  > **username_2**: I think that will be ok as long as they do the trigger rebuild step in the second 5e (which is really step 13e).  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2022-03-17. Score: 1
  
  It's been so long since I looked at that docs page - the numbering has got messed up I think and in any case it's a difficult read. First, do NOT use `--ignore-table` when moving an existing site with live data. It does say that in 7b but it's hard to see.
  
  Then second, it stops at step 8 and then starts at 1 again, but it should really be continuing on. You need to do those other steps too.
  
  > **Comments:**
  > **username_0**: I did see the comment '*** If copying an existing install don't skip the cache tables they will not be created automatically" but I read this as if I was copying code from one site to another rather than using a new installed. I did a dump and restore without --ignore-table but the site sill errors out. I wonder if I need to install CiviCRM 5.19 under Drupal 7.89, restore the DB, then upgrade 5.19 to 5.47? Or, should I be able to restore a dump of Civi 5.19 to Civi 5.47?  
  > **username_2**: That might be a good sanity check but note I don't think 5.19 officially supports php 7.4, but might work.  Since it's a jump over 28 releases, you might have to go in smaller steps. Also stick to 5.46 for now if using CiviEvents - you don't want 5.47. Also the full error will be in sites/default/files/civicrm/ConfigAndLog.  
  > **username_0**: You are right. Too big of a jump. 5.19 fails to start up after the install. Thanks for the advice in 5.46. I may try a data dump and import to see if that works.  
  
  ---
  
  