Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantI confirm that this does not show any tables when importing.
But should it? I do not think the text-ODBC driver supports such data. I never saw anything like it before!
Never heard about such schema.ini!
The problem is between your data and the ODBC driver. It is the ODBC driver that does not find anything!
Can you import this example to anywhere else? To where and how?
peterlaursen
Participantno, but you can have an empty password.
peterlaursen
ParticipantI think the crash is reported internally already while researching this. But anyway please attach the dump tile (no private information is there).
peterlaursen
Participantissue confirmed — we are analyzing now.
peterlaursen
ParticipantOK .. maybe we got this!
In the first screen of the migration wizard did you select the option to 'enter SQL'?? If so the PK must be defined at that step as the SQL is not editable after that. But actually all non-available options should grey out here then!
peterlaursen
ParticipantWe notice that the 'Edit SQL' button is 'greyed out'. That seems to indicate that creation of (DDL-)SQL is blocked. We think this is related, but not quite sure why!
1) please tell: are you creating the table with the migration tool or are you importing to an existing table?
2) could you attach the jobfile generated? create a ticket if you want privacy, and please zip.
3) please paste returns of “SHOW GRANTS for 'thisuser'@'thishost' “
peterlaursen
ParticipantPlease try to disable transaction support in 'preferences'. If enabled SQLyog will not reconnect if connection is lost. Also tell if you are using the 'backup' tool or the 'scheduled backup' *powertool*.
This “Btw, using the website's myPhpadmin to do the backup now also fails” indicates that there is a server side problem, right? Have you reported that to the ISP support?
peterlaursen
ParticipantPlease attach an example of such file and the structure-dump of the table you import to! We need to see it with our own eyes.
peterlaursen
ParticipantOK .. this I have no option to test from here!
Please tell Oracle version and ODBC driver version and we will try to reproduce this!
peterlaursen
ParticipantIf you flush logs then MONyog will of course not be able to get any information before the flush! General log takes lots of space. That is a compromise that only you can decide!
peterlaursen
ParticipantAre you migrating from Access?
If so read this http://www.webyog.com/whitepaper/Preparing…__Migration.pdf
(this describes versions up to Access 2003, please tell if you want same for Access 2007 – they have changed the interface).
peterlaursen
ParticipantIt is not SQLyog that 'looks for'. It *does not look at all* here! The generated SQL statement is sent to the server and this error is generated by the MySQL server! All 4 digit errors starting with “1***” are server errors. You can see in HISTORY what SQL SQLyog sends to the server. That SQL would fail with any client. So either you are doing something wrong or SQLyog is generating wrong SQL.
Note that the max-length of varchars (65535 in MySQL 5+) is measured in BYTES – not in CHARACTERS. So possible length depends on the chatset. In UTF8 for instance characthers may use up to 3 bytes (and 4 bytes in MySQL 6 actually). But on my configuration the server will 'silently' transform to a MEDUMTEXT (and not return an error) if varchar is specified too long. But that probably depends on server configuration!
And please always tell the program version you are using when reporting an issue! Both server version and SQLyog version!
peterlaursen
ParticipantNo we do not have any particular advice on that. It depends on for what purpose you use the log, if you need to open it in an editor etc.
peterlaursen
ParticipantWhat is the program version you are using ?
What is 'the odbc-designer' ?
I recall the error message “ODBC Source did not return any row for the selected table” but I do not recall the context!
Could you please attach a small example of such text file that fails to import?
However one detail to observe is this
http://webyog.com/faq/content/28/73/en/i-h…ighlight=infile
“And in most of continental Europe (where the comma is used for decimal notation – ie: “4.123,7” instead of English notation “4,123.7”) it is a de facto convention to use semicolon and not comma as field separator! Localized versions of Microsoft Excel and the Microsoft text-ODBC-driver handles it that way for instance! Thus as CSV really becomes a SSV ('Semicolon Separated Value') in most of Europe.”
.. so one possibility could be that the file you created uses COMMA and your (localized) driver expects SEMICOLON as field seperator (or vice versa).
peterlaursen
Participant1)
Please read:
http://webyog.com/faq/content/30/38/en/wil…-to-access.html
“However individuals purchasing a single license may install a copy on a stationary computer and a laptop as well provided that this individual is the only user of the program and the two installed versions are not in use simultaneously.”
So in this particular situation 8and only this) we accept one licnse for two machines
2)
No problem in moving. Just install on the new machine (it will prompt for your registration details again). Copy the sqlyog.ini file from old machine if you want to migrate settings and connection details. When you have verified that everything works uninstall on the old machine.
-
AuthorPosts