Slqyog Database Synchronization Wizard Hangs While Synchronizing Table

This topic is empty.

Viewing 10 reply threads

Author

Posts
- April 10, 2006 at 10:14 am #9609
  
  sach97
  Member
  
  Hi,
  
  I am trying to syncronize a table using synchronization wizard. It hangs at folloing step and make the terminate button invisible.
  
  SQLyog Job Agent Version 5.01
  
  Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.
  
  Sync started at Mon Apr 10 15:29:12 2006
  
  Table SrcRows TgtRows Inserted Updated Deleted
  
  ========================= ======= ======= ======== ======= =======
  
  `capuser` 21 18
- April 10, 2006 at 1:58 pm #21201
  
  sarat
  Member
  
  More information would be appreciated,
  
  Can you send us the table structure and data of which you r trying to synchronize.. If it is not confidential
- April 10, 2006 at 2:01 pm #21202
  
  peterlaursen
  Participant
  
  We will need more info to be able to answer this. To answer we must first understand and to understand we must reproduce. 😛
  
  Is it possible that you attached a – not too big – test case to reproduce.
  
  Also read: http://www.webyog.com/faq/1_26_en.html
- April 10, 2006 at 2:10 pm #21203
  
  Ritesh
  Member
  
  Terminate button becoming invisible means that the background SJA process is over. If you execute SJA from the command line, the application should come out in between.
  
  What happens when you run SJA from the command line?
- April 10, 2006 at 3:13 pm #21204
  
  sach97
  Member
  
  Ritesh wrote on Apr 10 2006, 07:40 PM:
  
  Terminate button becoming invisible means that the background SJA process is over. If you execute SJA from the command line, the application should come out in between.
  
  What happens when you run SJA from the command line?
  
  Following is result from command line execution…
  
  D:Program FilesSQLyog Enterprise Trial>sja Capuser
  
  SQLyog Job Agent Version 5.01
  
  Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.
  
  Sync started at Mon Apr 10 20:36:22 2006
  
  Table SrcRows TgtRows Inserted Updated Deleted
  
  ========================= ======= ======= ======== ======= =======
  
  `capuser` 21 18
  
  D:Program FilesSQLyog Enterprise Trial>
  
  the table is create statement is and field PWD has encoded character.
  
  CREATE TABLE `capnew`.`capuser` (
  
  `CAPUserId` bigint(20) unsigned NOT NULL auto_increment,
  
  `GroupId` bigint(20) unsigned NOT NULL,
  
  `Name` varchar(20) character set ucs2 NOT NULL,
  
  `Email` varchar(255) character set ucs2 default NULL,
  
  `FullName` varchar(255) character set ucs2 default NULL,
  
  `PWD` varchar(255) character set ucs2 NOT NULL default '',
  
  `LastBookmarkId` bigint(20) unsigned default NULL,
  
  PRIMARY KEY (`CAPUserId`),
  
  UNIQUE KEY `Name` (`Name`),
  
  KEY `CAPUser_FKIndex1` (`GroupId`),
  
  CONSTRAINT `capuser_ibfk_1` FOREIGN KEY (`GroupId`) REFERENCES `usergroups` (`GroupId`)
  
  ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
- April 10, 2006 at 4:22 pm #21205
  
  peterlaursen
  Participant
  
  It is a pretty old verison you are using, I guess?
  
  Where did you get if from?
  
  Could I ask you to try 5.1 beta (trial also available here).
  
  This new version should fix issues with enocdings, as it issues a 'SET NAMES = uft8' on both servers.
  
  Are you using HTTP-tunnelling?
  
  If yes there may still be a problem (to be fixed in BETA 7), but I think we can fix it with hard-coding the tunnelling file …
- April 11, 2006 at 5:10 am #21206
  
  sach97
  Member
  
  peterlaursen wrote on Apr 10 2006, 09:52 PM:
  
  It is a pretty old verison you are using, I guess?
  
  Where did you get if from?
  
  Could I ask you to try 5.1 beta (trial also available here).
  
  This new version should fix issues with enocdings, as it issues a 'SET NAMES = uft8' on both servers.
  
  Are you using HTTP-tunnelling?
  
  If yes there may still be a problem (to be fixed in BETA 7), but I think we can fix it with hard-coding the tunnelling file …
  
  Hi tried it with Sqlyog Enterprise V5.1 Beta 6 but i am facing same problem. I have attached the job and log file. I have attached capuser.htm file for schema.
  
  D:Program FilesSQLyog Enterprise Trial>sja -lCapuser.log Capuser
  
  SQLyog Job Agent Version 5.1
  
  Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.
  
  Sync started at Tue Apr 11 10:33:24 2006
  
  Table SrcRows TgtRows Inserted Updated Deleted
  
  ========================= ======= ======= ======== ======= =======
  
  `capuser` 21 18
  
  D:Program FilesSQLyog Enterprise Trial>
- April 11, 2006 at 5:27 am #21207
  
  peterlaursen
  Participant
  
  hmmm …
  
  I asked you if you were usig HTTP-tunnel? That is important to know! I don't think HTTP-tunnel can handle UCS2-data in all situations as of now. But As I said, I think we can 'hack' the tunnelling file if it is the case.
  
  Also with only about 20 rows of data isn't it possible to dump the data (both) and zip them here?
  
  If you don't want to expose the data in public you can create a 'ticket' and attach it there.
- April 11, 2006 at 5:54 am #21208
  
  Ritesh
  Member
  
  It would be really nice if you can mail the db to us. We will delete it from our system as soon as we are able to trace the issue. I think the problem is indeed due to the UCS-2 data.
- April 11, 2006 at 1:45 pm #21209
  
  sach97
  Member
  
  Ritesh wrote on Apr 11 2006, 11:24 AM:
  
  It would be really nice if you can mail the db to us. We will delete it from our system as soon as we are able to trace the issue. I think the problem is indeed due to the UCS-2 data.
- April 11, 2006 at 2:16 pm #21210
  
  sarat
  Member
  
  can you send the table schema and the data in sql format
  
  it would be really helpful
Author

Posts