Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantPlease also give a SQL DUMP with table structure (or better a few rows of data).
To work with an issue like this we will need to start reproducing every detail in the debugging environment. Anything else will be guesswork.
You can create a ticket if you want to keep that dump confidential.
You did not answer if SJA is running on the machine where MySQL runs!
peterlaursen
ParticipantActually export opens a new connection. But the server won't let you!
If you try to open a new connetion from 'file' menu (Ctrl+N) can you?
I think the reason for this must be found in server configuration or user settings!
anything special that you know about?
peterlaursen
ParticipantSQLyog runs on Wine (aand the comemrcial wine build 'cross over').
refer to: http://webyog.com/faq/31_71_en.html
There is currently no activities to build a native SQLyog for Linux.
Wine is available for Linux, FreeBSD/and PC-BSD, Solaris et. al.
peterlaursen
ParticipantQuote:I just downloaded the trial of 5.29 and with that version it's OKthen there realy is nothing that we can do. Problem is fixed – what else would you expect?
peterlaursen
ParticipantAlso:
It would be nice to know if it is a problem specific to version 5.29? Do you know?
peterlaursen
Participanthow did it go away?
peterlaursen
ParticipantI do not think this MySQL log is related to this problem!
Do you have any reason to think it is?
Are the timestaamps in the log showing the time when this problem occurred?
Obviously the OS tries to start more identical MySQL instances, but SJA does NOT start a server instaance – it only connects to a running instance!
'segmentation fault' in *nix is what we would call a
'crash' is windows. Crash is occuring on the client side and not the server side.
There is no information for analyzing the problem. We will need more info – at least:
1) a structure only dump of the jobfile (or better: a dump of a small table) wioth a few rows of data) to reproduced with
2) the jobfile
3) detailed information about the OS where the client program (SJA) runs. Linux-'dialect'? Version?
4) MySQL version(s)
do you have a chance do runs SJA on the other server (if more than one is involved) or from Windows (you may download SQLyog ENTERPRISE TRIAL) ?
I will have to ask you to do a little more research into this yourself. We cannot guess u will have to find out and report! And if there is an issue for us to solve, we need to detailed information so that we can reproduce! Try to answer for instance:
1) Does it only happen with HUGE tables, or with small tables too?
2) Can the problem be located to a specific server?
3) Is it related to the PDF's or not?
peterlaursen
ParticipantI'll move your post to the SQLyog category, and after that study details …
Please distinguish the Monyog/SQLyog categories 😉
peterlaursen
ParticipantYou can make a screendump of connection settings 8all relevant tabs) and attach to a ticket.
Fake passord and similar details as you like! But if we could have remote access (not to your data but just a 'dummy' database) that would be best of course.
April 19, 2007 at 8:54 am in reply to: Problem In Retrieving Index Information Fron Sybase To Mysql Using Sql #23766peterlaursen
ParticipantWe asked for remote access. We have no option to create a setup with exactly the same OS and Sybase version.
We need to try and import ourselves from a debugging environment.
We have read your posts of course, but words alone won't do anymore. We need to debug this if we shall do any progress. But of course the ODBC driver is supposed to send the metadata. But maybe there is an issue between the server and driver version. We cannot tell without debugging the stream of data.
If you have a licensed Sybase, can't you contact Sybase and asked for the 'perfect driver' for this version?
peterlaursen
ParticipantIn utf8 non-ASCII latin characters (umlauts, nordic characters, spanish ñ etc) are encoded with two bytes. Therefore they will not display correct – only after decoding they will. If you open a utf8 encoded file some programs will understand – others not. Excel for instance does not handle utf8 in CSV.
I do not understand every details of what you write. But please first please try upgrading to 5.29 or 6.0 beta. There were some fixes with the tunneller and charsets handling. Quite a lot of fixes actually!
Also always tell the server version(s). Is source 4.1 or higher (with unicode support) and target is 4.0 (without unicode support) ?
If problem persists please execute
Code:SHOW VARIABLES LIKE '%character%';.. on all servers involved and paste results in here. And please give a sample CSV zip and attache here).
April 19, 2007 at 8:27 am in reply to: Feature Wishes And Possible Bug In "migration Toolkit" #23785peterlaursen
ParticipantI do not think the slow speed is related til MySQl or SQLyog.
Probably it is the ODBC driver. What is the ODBC source?
If you import into any other program that can connect with ODBC (Access, OpenOffice base) is it then significantly faster?
peterlaursen
Participanthello!
we cannot use your link!
please zip and attach a dump here (or you may create a ticket, if you do not want to expose your data).
April 17, 2007 at 1:38 pm in reply to: Problem In Retrieving Index Information Fron Sybase To Mysql Using Sql #23764peterlaursen
Participant1)
The Migration tool is a Migration Tool – not a synchronisation tool. With the use of triggers and where-conditions it can be used for synchronisation. It is all explained in the doucmentation.
2)
We do not offer 'on the spot' support as you suggest. Both our sales and support concepts are 100% based on the Internet.
April 13, 2007 at 11:59 am in reply to: Problem In Retrieving Index Information Fron Sybase To Mysql Using Sql #23762peterlaursen
ParticipantWe have no opton to test with that specific version and not on Solaris either.
Could you arrange remote acces to some (silly) database?
-
AuthorPosts