OBIEE 10.1.3.4.1 & MySQL ODBC on linux. Generated SQL is wrong.

Anyone know how to fix this situation?
We are running OBIEE 10.1.3.4.1 on Redhat Linux 5.3 with MySQL ODBC connector.
When connecting to MySQL we have need to connect to multiple databases.
Problem is that OBIEE is generating incorrect sql.
Example:
select * from db_name..table_name;
Note the two dots between db and table.
This is incorrect syntax for MySQL. Should be only 1 dot.
But I can't find a way to get OBIEE to only use 1 dot.

MySQL is not a supported Datasource.
http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10417.pdf

Similar Messages

OBIEE 11g "WITH SAWITH0 AS" subquery factoring clause in the generated sql

I've observed that the OBIEE 11g generates in the query log physical query using the WITH (sub-query factoring) clause to make the generated sql elegantly readable. This is great! Thanks for the developers. However I have some questions about this.
__Background__
Oracle Database' default behaviour is that if you have only one sub-query in the WITH section, it executes it as an in-line view and does not materialize it before the main sql is executed. If you have more than one, by default the database engine materializes all of them in the order of the definition. In some cases this can completely blow up the SGA and make the query never ending. To divert this behaviour you can apply two hints that work both in inline views and in sub-queries as well: /*+ MATERIALIZE */ and /*+ INLINE*/, however Analytics 11g does not seem to have hint capabilities at the logical table level, only at physical table level.
If we go with the current defaults, developers not aware of this feature can bump into serious performance issues for the sake of some syntax candy at the generated sql level, I'm afraid.
__Questions__
* Is it possible to turn the Analytics server not to use WITH but use inline views instead?
* Is there any way to sneak in some hints that would put the /*+ INLINE */ hint to the appropriate place in the generated sub-queries if needed
* Does the Oracle Database have any initialization parameter that can influence this sub-query factoring behavior and divert from the default?

The WITH statement is not added to make the query more elegant, it's added for performance reasons. If your queries take long to run then you may have a design issue. In a typical DWH DB SGA needs to be seriously increased since the queries ran are much larger and complex than on an OLTP DB. In any case you can disable the WITH statement in the Admin Tool by double clicking on your database object on the physical layer and going to the Features tab. The feature is called WITH_CLAUSE_SUPPORTED.

Adobe LiveCycle Designer ES Error while Connecting to MYSQL ODBC Driver

Hi
I'm getting an strange error message when i try to connect a LC PDF form to
MYSQL DB using MySQL Connector /ODBC 3.51 Driver
Here is the complete detail how i was trying to build a connection
string :-
I Opened a form in Adobe LiveCycle Designer ES2 Ver.9.0.0
Clicked on Data View Pallete --> New Data Connection --> selected OLEDB Database radio button --> Build a Connection string (clicked on build button) --> selected MS OLE DB Provider for ODBC Drivers (the default selected option ) --> clicked on Next >> button --> Use connection string (radio button) --> Build connection string on clicking Build button --> Select Data Source windows opens --> Clicked on Machine Data Source tab --> created a new data source (with User Data Source) --> Selected the MySQL ODBC Driver (MySQL ODBC 3.51 Driver) --> Clicked on next button and then Finish
A Connector/ ODBC 3.51.28 - Add Data Source Name window opens up which have the DSN connection details (DSN Name , Server , user , password , database).
I put all the default details
After this i got a error message saying that
Adobe LiveCycle Designer ES has encountered a problem and needs to
close. we are sorry for the inconvenience
I tried this number of time and was getting this error message every
time i try to put the DSN Detail and trying to connect to the DB. This
was really irritating.
Can somebody's what's the Issue . Is this a Resource Conflict or
something else
P.S :- I am using Adobe LiveCycle Designer ES2 Ver.9.0.0 with Windows XP and MySQL
Connector /ODBC 3.51 and the DB Connection is working good for MS
Access( though i don't need MySQL Connector fot this ).
Any Help would be highly appreciated
Thanks Alok

Hi
I'm getting an strange error message when i try to connect a LC PDF form to
MYSQL DB using MySQL Connector /ODBC 3.51 Driver
Here is the complete detail how i was trying to build a connection
string :-
I Opened a form in Adobe LiveCycle Designer ES2 Ver.9.0.0
Clicked on Data View Pallete --> New Data Connection --> selected OLEDB Database radio button --> Build a Connection string (clicked on build button) --> selected MS OLE DB Provider for ODBC Drivers (the default selected option ) --> clicked on Next >> button --> Use connection string (radio button) --> Build connection string on clicking Build button --> Select Data Source windows opens --> Clicked on Machine Data Source tab --> created a new data source (with User Data Source) --> Selected the MySQL ODBC Driver (MySQL ODBC 3.51 Driver) --> Clicked on next button and then Finish
A Connector/ ODBC 3.51.28 - Add Data Source Name window opens up which have the DSN connection details (DSN Name , Server , user , password , database).
I put all the default details
After this i got a error message saying that
Adobe LiveCycle Designer ES has encountered a problem and needs to
close. we are sorry for the inconvenience
I tried this number of time and was getting this error message every
time i try to put the DSN Detail and trying to connect to the DB. This
was really irritating.
Can somebody's what's the Issue . Is this a Resource Conflict or
something else
P.S :- I am using Adobe LiveCycle Designer ES2 Ver.9.0.0 with Windows XP and MySQL
Connector /ODBC 3.51 and the DB Connection is working good for MS
Access( though i don't need MySQL Connector fot this ).
Any Help would be highly appreciated
Thanks Alok

Crystal Reports Server 2008 (Linux) - Crystal Reports/MySQL/ODBC Issue

Hello,
I have successfully installed CRS '08 on a Red Hat Enterprise Linux 4 server. All services run fine.
In the CMC, I have uploaded a Crystal Report that connect to a remote MySQL server.
I have installed the My SQL ODBC 3.51.11 and .12 Drivers as a System DSN.
I have proven that the reports run fine in Crystal Reports 2008 directly against the remote MySQL DB server.
(in Windows but with the same 3.51 ODBC Drivers)
I have also proven that the database connection works okay from the CRS '08 Red Hat server to the remote MySQL DB server, when also creating a system DSN (using bash ./ODBCConfig)
The problem is that when I log into the CMC or InfoView, and when I run the Crystal Reports from there, I get an error message:
"Error in File <MyCrystalReport>: Failed to load database information"
Is there something wrong with my specific Crystal Reports' Database Configuration? (Right click- Database Configuration)
I see the driver was registered correctly in the /etc/odbc.ini file
Am I supposed to set any other ODBC environment variables?
Is there are firewall issue (port 3306 is already open)?
In summary, the install was successful, and Crystal Reports can be uploaded and viewed via CMC or InfoView, but I cannot run the Crystal Reports against the database.
Please advise, Thanks!

Hi, I'm facing a similar problem. My ODBC DSN never works with CRS. Here are the details: 
(1) I installed the CRS 2008 in /opt/crystalreportsserver_2008_v1/ on a Linux platform. The CRS works well. I created a report with Crystal Reports 2008. This report directly connects to a MySQL server. After I published the report and manually modify its database configuration, I can browse it from InfoView. I'm sure that CRS, MySQL, and a report connecting to MySQL are all good. 
(2) Then, I created an ODBC DSN on a Windows platform. This DSN connects to a MySQL server. I created another report with Crystal Reports using this DSN. The report can show the data within Crystal Reports. 
(3) Then, I published the second report to CRS, but when I try to browse it, I always get such a message: Failed to open the connection. 
I have configured the ODBC for CRS on the Linux server and I think the configuration is correct. This is how I do that: I edited the /opt/crystalreportsserver_2008_v1/bobje/odbc.ini file. In the file I added a data source called ods_telstar. Following is the content of the file: 
[ODBC Data Sources] <
CRSQLServerWP=DataDirect 5.3 SQLServer Wire Protocol Driver 
CRSybaseWP=DataDirect 5.3 Sybase Wire Protocol Driver 
CRText=DataDirect 5.3 Text Driver 
%SYBASEDSN%=DataDirect 5.3 Sybase Wire Protocol Driver 
ods_telstar = MySQL 
 
... 
 
[ods_telstar] 
Description = ODS on telstar 
Trace = Off 
TraceFile = stderr 
Driver = /opt/crystalreportsserver_2008_v1/bobje/enterprise120/linux_x86/odbc/lib/libmyodbc5.so 
SERVER = xxx 
USER = xxx 
PASSWORD = xxx 
PORT = 3306 
DATABASE = ods 
 
In the middle I removed some data source definitions that are by default in the file. Note that I use "xxx" to replace the server name, user, and password. Such information is for internal use and I'm sure the original information is correct. The MySQL ODBC driver file has been put in the correct location. Correct access permissions has been assigned to the file. 
I've tried to restart the CRS server, but still the report using ODBC DSN cannot be viewed. 
The reason that we want to user ODBC DSN is that we may have many reports to publish. When we design the reports, we specify that they get data through an ODBC DSN such as ods_telstar. If we configure the same DSN on CRS, then we don't need manually modify each report's configuration after we publish them. If these reports are directly connecting to MySQL, then we have to manually modify each one's database configuration after we publish them. 
I've no idea what's wrong with all the setup. Any suggestions and comments are appreciated!

DAS Can't connect to mySQL ODBC

Using: HPS 8.3 Sun Solaris 8 I've created a BQY in Intelligence Explorer that connects using mySQL ODBC in Windows XP and wanted to publish it to the web, but I needed to publish the OCE to the server and set it up with DAS. Here are the steps I took 1. Installed the mysql connector odbc 3.51.12 sun solaris2.8 sparc 64bit ODBC in Solaris. 2. Created an odbc.ini file in Solaris with my mySQL connection settings in the home directory of the user running the services. I even made a copy of it in the $BP_HOME directory. 3. Added the library path for my ODBC library to all my scripts. 4. Added the data source using the service config tool. 5. Restarted services 6. published the OCE and BQY When I access the BQY using the plug-in, it gives me "Server Error [2009]; Internal Error Detected in Data Access Service" When I access it using the thin-client (iHTML), it gives me: "An Intelligence Service error has occurred.-Failed to acquire requested service" What else needs to be done? I tried some the other suggestions to no avail: --added the library path to the LD_PRELOAD variable in the $BP_HOME/bin/services.sh script Also, I noticed that when I ran ServiceConfig.sh, there were no data sources to pick from the dropdown. Anyone know how to make that active so I can just PICK the connection to use?

I'd strongly recommend that you take all that JDBC code out of your JSP. Put it into a class that you can test on the command line. Once you have it working, you can use it to get at data and pass it along to your JSP for display.
I'd also recommend that you not use scriptlets and learn JSTL right away. MVC separation suggests that putting Java code in a JSP is a very bad idea.
%

Problems with MySQL ODBC install on Linux

Oracle 11gR2
Linux 6.3
I am using the Oracle ODBC Gateway and trying to configure for connectivity to MySQL.
Can anyone forward me:
(1) link to MySQL ODBC Driver
(2) instructions on how to install
I have tried installing the following and I am getting dependency errors:
[root]# rpm -ivh mysql-connector-odbc-5.1.10-1.x86_64.rpm
Preparing... ########################################### [100%]
 1:mysql-connector-odbc ########################################### [100%]
myodbc-installer: symbol lookup error: myodbc-installer: undefined symbol: SQLInstallDriverEx
error: %post(mysql-connector-odbc-5.1.10-1.x86_64) scriptlet failed, exit status 127
[root]# rpm -ivh mysql-connector-odbc-5.2.6-1.el6.x86_64.rpm
error: Failed dependencies:
 libodbc.so.2()(64bit) is needed by mysql-connector-odbc-5.2.6-1.el6.x86_64
 libodbcinst.so.2()(64bit) is needed by mysql-connector-odbc-5.2.6-1.el6.x86_64
 rpmlib(FileDigests) <= 4.6.0-1 is needed by mysql-connector-odbc-5.2.6-1.el6.x86_64
 rpmlib(PayloadIsXz) <= 5.2-1 is needed by mysql-connector-odbc-5.2.6-1.el6.x86_64

The MySQl ODBC driver requires an ODBC Driver Manager (libodbc.so.2). So please make sure you first install an ODBC Driver manager (for example unixODBC Driver Manager release 2.3) using an RPM or compile it from the soiurce files (www.unixODBC.org).
- Klaus

Crystal Reports Server 2008 V1, RedHat Enterprise Linux, MySQL, ODBC

Iu2019m confused about connecting to an ODBC source from a report within CMC. Iu2019m a Unix guy; I donu2019t know much about Crystal reports, but Iu2019m working with a Crystal guy to get this thing working.
 
First, background: I have installed Crystal Reports Server 2008 V1 in RedHat Enterprise Linux (5.4), and itu2019s running just fine! Iu2019m using the included Tomcat application server, but Iu2019m storing CMS and Audit data our local running copy of MySQL (5.1.42). The RHEL install is native 32-bit (the only way I could get it to work), Crystal is storing and retrieving data from MySQL, The Central Management Console is responding to port 8080 over Tomcat, Iu2019m able to log in and see stuff, and so far, life is good.
 
Now, where Iu2019m stuck: the data weu2019re trying to build reports from also resides in this local Linux / MySQL install, and connecting to it from a report within CMC is where Iu2019m lost.
 
First, I successfully installed the unixODBC and MyODBC drivers in Linux. Iu2019m able to connect to MySQL successfully using the isql utility. Here are my conf files:
 
<pre class="jive-pre"><code class="jive-code jive-java">/etc/odbc.ini
[DSN_NAME]
Driver = MySQL ODBC 5.1 Driver
DATABASE = project_web_prod
DESCRIPTION = Project Description
UID = username
PWD = password
SOCKET = /var/lib/mysql/mysql.sock
/etc/odbcinst.ini
[MySQL ODBC 5.1 Driver]
Driver = /usr/lib/libmyodbc5.so
UsageCount = 1
</code></pre>
 
Again, this all works with isql (Iu2019ve even used both a socket connection, and port 3306, in odbc.ini).
 
Now, our Crystal guy uploads a report into the CMC. I go to Folders -> <Project Folder>, right-click the report I want to test, click Database Configuration, and check the option Use custom database login information specified here. I select database driver ODBC from the dropdown, and type in the server, database, username, and password info. However, when I try to run the report, it fails to connect.
 
So, stupid question, can Crystalu2019s CMC use the system ODBC configuration options? (The ones stored in /etc). Because I saw an odbc.ini file in ~crystalinstalldir/bobje/. I edited it to match the contents of my /etc/odbc[inst].ini files, but to no avail. I saw that Crystal has itu2019s own ODBC engine, but it doesnu2019t support MyODBC driver, does it? I even tried hacking env.sh to use the system unixODBC library instead of the included one, but no luck.
 
So, in short, my question: how do I simply get reports in CMC to connect to a MySQL data source (using ODBC)?
 
Thanks so much! An answer to this question will save my day!
 

Thank you, Efstratios, for the helpful reply!
So, I followed the directions in the PDF file you attached, and everything went smoothly. However, Iu2019m still not able to connect to ODBC within CMC.
Hereu2019s what I did:
<ul style="list-style-type:disc">
<li>Copied the unixODBC libraries over to <installdir>/bobje/enterprise120/linux_x86/odbc/lib</li>
<li>Removed MySQL ODBC connector 5.1, installed MySQL ODBC connector 3.51.</li>
<li>Edited <installdir>/bobje/defaultodbc.ini, added my DSN and MySQL library info as per the instructions (I have both an odbc.ini, and defaultodbc.ini, identical files, just to be safe)</li>
<li>Tested the connection using these libraries, this odbc.ini, and isql. Worked just fine</li>
</ul>
So, my problem seems to be in getting the CMC to actually use my ODBC setup!
Any other hints / things I could try?
When I right-click a report, and go to “Database Configuration,” which connection options should I use for the report? Iu2019ve tried both “Use original database logon information from the report,” and “Use custom database logon information specified here” (using the ODBC option from the drop-down menu). Either way, if I enter in the database, username, password, and then try to run the report (“Run Now”), I get this message in the History: “Failed - Information is needed before this report can be processed.”
Is there another place I could get a more helpful error message? Or is there, perhaps, another way I could test database connectivity from within CMC? I wish there were at least a “Test Database Connection” optionu2026 :P
Thanks so much for your help!

Crystal Report on Universe with MySQL ODBC

Hi
I created a report with Crystal reports by using a Universe based on MySQL ODBC. In my local (Windows XP) installed Report Designer everything is running fine. I'm also able to publish this report to my BOE, based on RHEL.
If I will refresh my report on InfoView, database credential are required, but my credential are not accepted. I only become a error message: Failed to open the connection
If I use Webi with the same universe and the same connection, everything is fine.
I have also change the ODBC version, but no other result.
Any idea, where I can trace this connection?
Versions:
Crystal Reports 2008 (12.0.0.683)
Business Objects Enterprise 3.0 (12.0.0.683)
MySQL ODBC 3.51.27 and 5.1.5
Thanks a lot
Christoph

Hi,
thank you very much for reply.
I think you got it. We have the goal to create a report that can be printed and is top-gloss-report for management ; ) One query would not be able to include all that stuff. It is very different.
So we created 7 different queries in SAP BW Query Designer and we want to put them together in BO Crystal Reports.
All Queries work with input variable for period and year. These input variables are used in the columns of the queries for calculating the key figures.
So, if we put these queries together into Crystal Reports, we should actually use "replacement path" for variables. But the sap.help says, that isn't doable.

MySQL ODBC driver (32 bit) linked server, architecture mismatch

Hello,
I am trying to create a linked server in SQL 2012 Management Studio with a MySQL external server. I have used the 32bit ODBC driver as instructed by the developer, following this rule:
To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe.
My connection is fine using the ODBC connector, but when I try to create the linked server I get an architecture mismatch error: The specified DSN contains an architecture mismatch between the Driver and Application Error 7303.
Can someone help?
Best regards
Kostas
Kostas Backas-Systemgraph Technologies

Hello,
What's the bit verison of the SQL Server ?
Based on your description, you create a DSN connect to MySQL database with 32 bit MySQL ODBC driver under 32bit ODBC Administrator tool (sysWOW64\odbcad32.exe).
When you create linked server on SQL Server instance, it will use 64 bit Microsoft OLE DB Provider for ODBC Drivers if the bit version of SQL Server is 64 bit. That may cause the error you received. In that case, please download 64bit MySQL ODBC driver and
create a DSN with 64 bit ODBC Administrator tool.
Reference: http://dev.mysql.com/downloads/connector/odbc/
If I have any misunderstanding, please correct me.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

MySQL ODBC DNS

Hi to everyone! First of all let me tell you that i've been looking for an example on how to do this for a long time before even considering making this post.
Let's go back to business, I'm having an issue trying to connect a mySQL database through "DSN".
$connectionDB = new-object system.data.odbc.odbcconnection
$connectionDB.connectionstring = "(Driver={MySQL ODBC 5.2w Driver};DSN=RENTABILIDAD_DES)"
$connectionDB.open()
Results are not very promising
[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"[0]
Enviroment:
Connection from a Windows 64 Enterprise
Connection to mySQL database (remote)
Powershell v3
Just in case you, I can and did connect to mySQL done the stuff i needed to do making the proper conection string. The issue in doind this, is that the password is in plain text (Harcoded on the code), now when i move the development to production site i
wont be able to do this. Example above
#dataBase info
$mysql_server = "10.1.131.106"
$mysql_user = "USER"
$mysql_password = "PASSWORD"
$Mysql_db = "db_XXXXXXX"
$ConnectionString = "SERVER=$mysql_server;UID=$mysql_user;PWD=$mysql_password;database=$Mysql_db"
$connectionDB = New-Object -TypeName MySql.Data.MySqlClient.MySqlConnection
$connectionDB.ConnectionString = $ConnectionString
$connectionDB.Open()
Works like a charm... anyway does anyone know to to use an ODBC already created to connect a mySQL data Base using powershell?
In advance thanks!!

I'm suggesting that might be part of the problem, take those out and try it again. You aren't using parentheses in the 2nd example and I don't think your first example would work with them. The error message tends to support my suspicion that
the values for DSN and Driver are not being passed correctly.
I hope this post has helped!

MySQL ODBC Setup

Post Author: Andrewr
CA Forum: Data Connectivity and SQL
Greetings,
I have a question as to how to get my ODBC connection setup.
I have XP and a Mysql DB running on a Linux Server, on my XP machine I am using the Mysql ODBC Connection tool. I have tried both the 3.51.23 and the new 5.xxxx versions of this tool.
I know that my username and password are correct in the setup.
Whenever I try to setup the ODBC I get the error " Request Returned SQL_ERROR"
[MySQL][ODBC 3.51 Driver]Can't connect to MySQL server on '192.168.0.197' (10061)
My XP Firewall is disabled.
Does anybody happen to have any suggestions?
Thank you
Andrew
Edit: I should probably add - that I am trying to generate reports with Crystal.
Thanks

Post Author: Andrewr
CA Forum: Data Connectivity and SQL
Well - Problem is not solved yet, but I think I have it figured out.
When I log into my Linux server, and telnet to port 3306 I get a connection, so I know that Mysql is answering.
When I try to telnet to the server on 3306 from my windows machine, I get nothing.
So this leads me to believe that it is a firewall issue. Even though both the WS & Server's firewalls are disabled, I do have a dedicated firewall/DHCP server on the fringes of my network. I suspect that this may be the issue. All the hostnames for all machines are correctly located in the respective hosts files. So I know that is not the issue. Just gotta setup the correct rule for the firewall - I hope.
Thanks
Andrew

CR2008: MySQL ODBC Connection duplicating FROM statement in SQL Expression

Maybe I'm doing something wrong here, but I think maybe I'm not and that I've found a bug.
I'm doing a very simple select statement:
SELECT count(*)
FROM labtech.computers
WHERE os NOT LIKE %server%
When I do this statement, I get an error:
Crystal Reports
Error in compiling SQL Expression :
Database Connector Error: '42000:[MySQL][ODBC 5.1 Driver][mysqld-5.1.37-community]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT count(*)
FROM labtech.computers
WHERE os NOT LIKE %server% FROM `labtec' at line 1 [Database Vendor Code: 1064 ]'.
OK
There is nothing wrong with this sql statement, so I started digging a little, removing everything except for
Select *
Crystal Reports
Error in compiling SQL Expression :
Database Connector Error: '42000:[MySQL][ODBC 5.1 Driver][mysqld-5.1.37-community]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT *
FROM `labtech`.`clients` `clients1`' at line 1 [Database Vendor Code: 1064 ]'.
OK
You will see that it is adding the
FROM `labtech`.`clients` `clients1`
So, my questions is:
1) Is this an issue with CR2008 or the MySQL ODBC driver
2) If it's CR2008, how do I report it?
3) Can anybody else duplicate it?
Thanks in advance for any help.
-Scott

Hi Scott,
Lots of info in these forums, more info in the [Crystal Report Designer|SAP Crystal Reports; forum. If you search in there you'll find references to others who suggested training material. You can also click on the eLearning tab above and find more info...
Thank you
Don

The ODBC data source administrator does not have the mysql odbc 3.51 driver

Hi^^,
I am trying to create the DSN for the type 1 driver.
I go the the ODBC data source administrator > click userdsn>add
It takes me to the screen"Create new data source"
Here i want to select Mysql ODBC 3.51 Driver and then click on finish.
My problem is that I do not have the choice of Mysql ODBC 3.51 Driver.
How do I get it among my list of choices.
Is the mysql software corrupt and do i need to install it.
Regards,
Prashant

Don't use odbc at all for java <-->MySQL. Use the JDBC driver from the MySQL website

Installed MySQL ODBC, system DSN configured and working, provider still not showing in SQL 2005 provider list

As per the title, really.
I need to fetch data periodically from a MySQL DB. Installed the 5.1 MySQL 32bit ODBC driver onto the SQL server, configured and tested the DSN, all fine.
Provider still not showing in the list in Management Studio.
Can anyone offer any advice? is it a simple case of restarting services? I haven't tried that due to the server being in production.

Hello,
Is this a 64 bit SQL Server? For a linked server you can only use OleDB data provider, have you also installed OleDB for MySQL? If not, then you have to use the ODBC OleDB provider together with a System DSN.
Olaf Helper
[ Blog] [ Xing] [ MVP]

BO DS - MySQL ODBC driver on Win7 64 bit

Hi
We have installed BO DS klient tools (Designer) on Win 7 64 bit. We have also installed the MySQL ODBC driver for 64 bit and created the DSN. The test of the DSE is successfull. When we try to log on to the DS server with DS we get the error message:
EROR: ODBC call <SQLDriverConnect> for data source <my_system> failed: [MicroSoft][ODBC Driver Manager] Te specified DSN contains an architecture mismatch between the Driver and Application. BODI-1111340
Has anyone seen this error before and dos anyone know how to fix this?
Kind regards
Erik

Hi,
Windows 7 is still not supported even on the latest version of Data Services - XI 3.2 SP2. This may explain your issue. An example of supported desktop product for this version is Windows XP SP2 Professional, Windows Vista, Windows Vista SP1. Please check the supported platform document in our Service Market Place (http://service.sap.com)
Hope this helps.

OBIEE 10.1.3.4.1 & MySQL ODBC on linux. Generated SQL is wrong.

Similar Messages

Maybe you are looking for