I have configured the odbc.ini to connect to mysql database ,but when I am trying to import table definition it is not connecting and also breaking the datastage client connection.
I am using the following entry in the odbc.ini. Is it correct for MYSQL
[mysqldsn]
Driver=/d01/Ascential/DataStage/branded_odbc/lib/branded_odbc/lib/VMmysql23.so
Description=MySQL ODBC 3.51 Driver DSN
SERVER=65.91.255.2
Database=edw1kn
PORT=3306
USER=guest
Password=welcome1
OPTION=3
SOCKET=
Configuring ODBC connection for MYSQL database
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 27
- Joined: Thu May 22, 2003 4:40 am
- Location: California
-
- Participant
- Posts: 27
- Joined: Thu May 22, 2003 4:40 am
- Location: California
-
- Participant
- Posts: 27
- Joined: Thu May 22, 2003 4:40 am
- Location: California
-
- Participant
- Posts: 27
- Joined: Thu May 22, 2003 4:40 am
- Location: California
mysqldsn]
Driver=/d01/Ascential/DataStage/branded_odbc/lib/branded_odbc/lib/VMmysql23.so
Description=MySQL ODBC 3.51 Driver DSN
SERVER=65.91.255.2
Database=edw1kn
PORT=3306
USER=guest
Password=welcome1
OPTION=3
SOCKET=
check the odbc drivers library path it seems you have entered twice
It supposed to be d01/Ascential/DataStage/branded_odbc/lib/
Driver=/d01/Ascential/DataStage/branded_odbc/lib/branded_odbc/lib/VMmysql23.so
Description=MySQL ODBC 3.51 Driver DSN
SERVER=65.91.255.2
Database=edw1kn
PORT=3306
USER=guest
Password=welcome1
OPTION=3
SOCKET=
check the odbc drivers library path it seems you have entered twice
It supposed to be d01/Ascential/DataStage/branded_odbc/lib/
Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.
By William A.Foster
By William A.Foster
-
- Participant
- Posts: 27
- Joined: Thu May 22, 2003 4:40 am
- Location: California