Stats

  • Locked Locked
  • Replies 3
  • Subscribers 165
  • Views 2196
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MySQL Community Server Installed on Linux doesn't work with OrCAD CIS, but it works with Windows based MySQL Community Server

PK787

Hi,

We are migrating from our Windows based MySQL Community server version 5.0 to Linux based MySQL Community server 5.6 and we are having trouble for this.

This is only happening if we point the MySQL ODBC Driver from computer to Linux Based MySQL Server with below error:

=================================================================================================

ERROR #8012 Database Operation Failed
Please Check Session For More Details
ODBC Error Code: -1
Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax

==================================================================================================

But, if I  point the MySQL ODBC Driver from computer to Windows Based MySQL Server, every thing looks fine. The same thing is happening for all the OrCAD CIS users in my comany.

Any software needed to be installed after installing MySQL Community Server on Linux.

Please help us.

  • oldmouldy
    "a" possibility is that the default "part type" delimiter of "\" is being interpreted on Linux but not on Windows, it might be worth checking what you have set for that in the CIS Configuration Administration and trying "something else". After that, historically, there were two ODBC versions supported for MySQL, 3.5 and 5.x, it might be worth trying the "other" version, if you haven't tried both. Next, you could turn on ODBC logging from the CIS client machines, either from the Windows Datasource administration or specifically on the MySQL Connector Configuration Details, these will write an extensive log of transactions over the ODBC interface, a bit of a "trawl" through this will usually indicate what the illegal syntax is, especially since you could compare the "working" and "failing" logs - this may just lead you back to the "part type" delimiter so worth eliminating that before getting involved in logging.
  • PK787

    Hi,

    Issue is solved.

    I found that FORCE is being used as one of the column in MySQL Views. Since this is RESERVERD word, and being used as a db column is causing the problems in the linux based server.

    Some how, when we use Windows based MySQL server FORCE is being converted as FORCE_1 in the OrCAD CIS Capture tool, but it is not happening when we connect the OrCAD CIS Capture to Linux based MySQL Server.


    Renamed the db column to FORCE_1 in the MySQL DB Server and NO ISSUE after that and it looks fine.

    Thanks for support

  • oldmouldy
    OK, probably a good plan to avoid reserved and keywords for naming to ensure consistency, a pretty wild issue nonetheless!
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.