Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Error No. 2006

forums › forums › SQLyog › Using SQLyog › Error No. 2006

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • May 17, 2006 at 5:21 pm #9689
      croaker
      Member

      sja for linux v5.12

      local mySQL v4.1x

      remote mySQL v4.0x

      256k uplink

      I have a database with a number of tables that all sync fine apart from 1 table that has 22 records that include large blob fields – each record is about 2-3 Mb. I'm trying to sync these databases for the first time (ie. there's currently no data in the remote database).

      When syncing this table, sja falls over with:

      Error No. 2006 mySQL Server has gone away.

      I get the same problem using the free version of sja for windows (using the export/import table option).

      sja seems to start out doing a lot of thinking, I guess it's collating the data required to work out what to sync. It seems that once it's ready, the remote server has timed out?

      Any solutions to my problem?

      I hoping that once I've got the 22 records on the remote server, syncing small changes will be easier but not if it's going to think for so long before acting.

      Shouldn't there be some sort of remote server pinging going on inside sja to keep the remote connection open?

      Cheers

      TIA.

      croaker

    • May 18, 2006 at 7:03 pm #21647
      croaker
      Member

      <_< Turned out my ISP had set their timeout to 5mins. My sja session was taking 40mins+ Doh! I got them to set it to 8hrs which did the trick. 🙂

    • May 19, 2006 at 4:52 pm #21648
      Ritesh
      Member

      Looks like the MySQL server takes a lot of time in returning MD5 for BLOB data. Did you try by using COLUMNS i.e. selecting particular columns which will be used to generate checksums.

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.