Informatica® Data Integration - Free & PayGo

MySQL Connector
Informatica Data Integration - Free & PayGo MySQL Connector
November 2023
© Copyright Informatica LLC 2017, 2023

This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be
reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC.

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial
computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the
extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.

Informatica, the Informatica logo, Informatica Cloud, and PowerCenter are trademarks or registered trademarks of Informatica LLC in the United States and many
jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company
and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product.

See patents at https://www.informatica.com/legal/patents.html.

DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied
warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The
information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation
is subject to change at any time without notice.

NOTICES

This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES
OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH
OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at
[email protected].

Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE
INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.

Publication Date: 2023-11-19

Table of Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Intelligent Cloud Services web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Intelligent Cloud Services Communities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Intelligent Cloud Services Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Data Integration connector documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services Trust Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 1: Introduction to MySQL Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

MySQL Connector assets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Administration of MySQL Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installing MySQL JDBC driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing MySQL ODBC driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Rules and guidelines for MySQL sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2: MySQL connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

MySQL connection properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SSL properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3: Mappings and mapping tasks with MySQL Connector. . . . . . . . . . . . . 14

MySQL sources in mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
MySQL lookups in mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Calling a stored procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Rules and guidelines for calling a stored procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4: Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Appendix A: Data type reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

MySQL and transformation data types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table of Contents 3
Preface
Use MySQL Connector to learn how to read from MySQL databases by using Data Integration. Learn to create
a MySQL connection, develop mappings, and run mapping and data transfer tasks in Data Integration.

Informatica Resources
Informatica provides you with a range of product resources through the Informatica Network and other online
portals. Use the resources to get the most from your Informatica products and solutions and to learn from
other Informatica users and subject matter experts.

Informatica Documentation
Use the Informatica Documentation Portal to explore an extensive library of documentation for current and
recent product releases. To explore the Documentation Portal, visit https://docs.informatica.com.

If you have questions, comments, or ideas about the product documentation, contact the Informatica
Documentation team at [email protected].

Informatica Intelligent Cloud Services web site

You can access the Informatica Intelligent Cloud Services web site at http://www.informatica.com/cloud.
This site contains information about Informatica Cloud integration services.

Informatica Intelligent Cloud Services Communities

Use the Informatica Intelligent Cloud Services Community to discuss and resolve technical issues. You can
also find technical tips, documentation updates, and answers to frequently asked questions.

Access the Informatica Intelligent Cloud Services Community at:

https://network.informatica.com/community/informatica-network/products/cloud-integration

Developers can learn more and share tips at the Cloud Developer community:

https://network.informatica.com/community/informatica-network/products/cloud-integration/cloud-
developers

Informatica Intelligent Cloud Services Marketplace

Visit the Informatica Marketplace to try and buy Data Integration Connectors, templates, and mapplets:

https://marketplace.informatica.com/

Data Integration connector documentation

You can access documentation for Data Integration Connectors at the Documentation Portal. To explore the
Documentation Portal, visit https://docs.informatica.com.

4
Informatica Knowledge Base
Use the Informatica Knowledge Base to find product resources such as how-to articles, best practices, video
tutorials, and answers to frequently asked questions.

To search the Knowledge Base, visit https://search.informatica.com. If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team at
[email protected].

Informatica Intelligent Cloud Services Trust Center

The Informatica Intelligent Cloud Services Trust Center provides information about Informatica security
policies and real-time system availability.

You can access the trust center at https://www.informatica.com/trust-center.html.

Subscribe to the Informatica Intelligent Cloud Services Trust Center to receive upgrade, maintenance, and
incident notifications. The Informatica Intelligent Cloud Services Status page displays the production status
of all the Informatica cloud products. All maintenance updates are posted to this page, and during an outage,
it will have the most current information. To ensure you are notified of updates and outages, you can
subscribe to receive updates for a single component or all Informatica Intelligent Cloud Services
components. Subscribing to all components is the best way to be certain you never miss an update.

To subscribe, on the Informatica Intelligent Cloud Services Status page, click SUBSCRIBE TO UPDATES. You
can choose to receive notifications sent as emails, SMS text messages, webhooks, RSS feeds, or any
combination of the four.

Informatica Global Customer Support

You can contact a Global Support Center through the Informatica Network or by telephone.

To find online support resources on the Informatica Network, click Contact Support in the Informatica
Intelligent Cloud Services Help menu to go to the Cloud Support page. The Cloud Support page includes
system status information and community discussions. Log in to Informatica Network and click Need Help to
find additional resources and to contact Informatica Global Customer Support through email.

The telephone numbers for Informatica Global Customer Support are available from the Informatica web site
at https://www.informatica.com/services-and-training/support-services/contact-us.html.

Informatica Resources 5
Chapter 1

Introduction to MySQL Connector

You can use MySQL Connector to connect to MySQL databases from Data Integration to read data.

You can also use MySQL Connector to connect to the following databases:

• Amazon Aurora MySQL

• Amazon Aurora MySQL and Azure MySQL private endpoints on virtual networks

You can use MySQL objects as sources in mappings, mapping tasks, and data transfer tasks.

MySQL Connector assets

Create assets in Data Integration to integrate data using MySQL Connector.

When you use MySQL Connector, you can include the following Data Integration assets:

• Data transfer task

• Mapping
• Mapping task

For more information about configuring assets and transformations, see Mappings, Transformations, and
Tasks in the Data Integration documentation.

Administration of MySQL Connector

To use MySQL Connector, you must download and install the JDBC and ODBC drivers on your Windows or
Linux machine where the Secure Agent is installed.

Before you use MySQL Connector, complete the following tasks:

1. Install the MySQL JDBC driver.

2. Install the MySQL ODBC driver.

6
Installing MySQL JDBC driver
Before you use MySQL Connector, you must install the MySQL JDBC driver version 8.0.12 and MySQL ODBC
driver on the Windows or Linux machine where you installed the Secure Agent.

Perform the following steps to install the MySQL JDBC drivers on Windows or Linux:

1. Click the following link to download the MySQL JDBC driver: https://downloads.mysql.com/archives/c-j/
2. Select the Product Version as 8.0.12.
3. Select the Operating System as Platform Independent.
4. Download the .zip or .tar file based on your Windows or Linux system.
5. Extract the downloaded file and copy the mysql-connector-java-8.0.12.jar file.
6. Paste the mysql-connector-java-8.0.12.jar file in the following directory on the Secure Agent
machine:
• On Windows: <Secure Agent installation directory>\apps\Data_Integration_Server\ext
\drivers
• On Linux: <Secure Agent installation directory>/apps/Data_Integration_Server/ext/drivers
7. Restart the Secure Agent.

Installing MySQL ODBC driver

Before you use MySQL Connector, you must install the MySQL ODBC driver on the Windows or Linux machine
where you installed the Secure Agent.

Installing MySQL ODBC driver on Windows

Perform the following steps to install the MySQL ODBC driver on Windows:

1. Click the following link to download the MySQL ODBC driver:

https://downloads.mysql.com/archives/c-odbc/
2. Select the Product Version as 8.0.12.
3. Select the Operating System as Microsoft Windows.
4. Select the OS Version as Windows (x86, 64-bit).
5. Download the ZIP Archive mysql-connector-odbc-noinstall-8.0.12-winx64.zip file.
Note: Do not use the MSI installer because it removes the existing MySQL ODBC driver versions from the
system.
6. Extract the .zip file.
7. Open the Command Prompt as an administrator and navigate to the extracted .zip file location.
8. Run the following command in the command prompt: Install.bat
After you install the MySQL ODBC driver, check if the MySQL ODBC 8.0 Unicode Driver name appears as one
of the available ODBC drivers under the ODBC Data Source Administrator (64-bit) dialog box:

Administration of MySQL Connector 7

 The following image shows the MySQL ODBC 8.0 Unicode Driver driver name in the ODBC Data Source
Administrator (64-bit) dialog box when you try to create a new data source:

Installing MySQL ODBC driver on Linux

Perform the following steps to install the MySQL ODBC driver on Linux:

1. Click the following link to download the MySQL ODBC driver:

https://downloads.mysql.com/archives/c-odbc/
2. Select the Product Version as 8.0.12.
3. Select the Operating System as Linux- Generic.
4. Select the OS Version as All.
5. Download the Linux - Generic (glibc 2.12) (x86, 64-bit) file.
6. Extract the downloaded file to a local directory in your system.
Note: When you extract the file, ensure that you copy all files from the downloaded driver package.
7. Edit the <Secure Agent installation directory>/odbcinst.ini file and add the following values:
[MySQL ODBC 8.0 Unicode Driver]
Description = ODBC for MySQL
Driver = <Extracted folder path>/lib/libmyodbc8w.so
Setup = <Extracted folder path>/lib/libmyodbc8w.so
FileUsage = 1
In the Driver and Setup fields, you must specify the file path of the libmyodbc8w.so file that you
extracted to the local directory in your system.

8 Chapter 1: Introduction to MySQL Connector

Rules and guidelines for MySQL sources
Use the following rules and guidelines for MySQL sources:

• You cannot include lookup fields of Text or Ntext data type because MySQL connections use a UTF-8 code
page.
• When you use a saved query to read data from a MySQL source, you must not use the full outer join
operation.
• When you use a saved query to read data from a MySQL source that contains Float columns, the Secure
Agent imports the Float data type as Real data type.
• When you use a saved query to read data from a MySQL source that contains Double columns, the Secure
Agent imports the Double data type as Decimal data type.
• You cannot use the select * from <table_name> command in a saved query. You must provide the
explicit column list.
• When you run a MySQL mapping to read from a stored procedure, ensure that the precision of the Float
data type does not exceed 18.
• When the source column name that you read has hyphens and you use the Create New at Runtime option
to create a target, the hyphens in the table name are converted to underscores in the target column.
• You cannot use SQL ELT optimization to push the transformation logic to MySQL.

Rules and guidelines for MySQL sources 9

Chapter 2

MySQL connections
Create a MySQL connection to connect to MySQL so that the Secure Agent can read data from MySQL.

You create a MySQL connection on the Connections page. Use the connection when you create the
mappings, mapping tasks, and data transfer tasks.

MySQL connection properties

When you set up a MySQL connection, configure the connection properties.

The following table describes the MySQL connection properties:

Property Description

Connection Name Name of the connection.

Each connection name must be unique within the organization. Connection names can
contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.

Description Description of the connection. Maximum length is 4000 characters.

Type Type of connection.

Select MySQL from the list.

Runtime Environment The name of the runtime environment where you want to run the tasks.
Specify a Secure Agent or a Hosted Agent.

User Name User name for the database login. The user name can't contain a semicolon.

Password Password for the database login. The password can't contain a semicolon.

Host Name of the machine that hosts the database server.

Port Network port number used to connect to the database server.

Default is 3306.

Database Name Name of the MySQL database that you want to connect to.
Note: The database name is case-sensitive.
Maximum length is 64 characters. Database name can contain alphanumeric and underscore
characters.

10
 Property Description

Code Page The code page of the database server.

Metadata Advanced Additional properties for the JDBC driver to fetch the metadata.
Connection If you specify more than one property, separate each key-value pair with a semicolon.
Properties

Runtime Advanced Additional properties for the ODBC driver to run mappings.
Connection If you specify more than one property, separate each key-value pair with a semicolon.
Properties

SSL properties
You can configure a MySQL connection to use SSL to securely communicate with the MySQL database.

Note: You can enable SSL for a MySQL connection only when you use the 8.x MySQL JDBC and ODBC drivers.
Ensure that both the MySQL JDBC and ODBC drivers are of 8.x version.

To configure SSL, you must first download and install the MySQL ODBC and JDBC drivers, version 8.x. For
information about installing the MySQL ODBC and JDBC drivers, version 8.x, see the Knowledge Base article:
561573

After you install the drivers, in the MySQL connection properties, enable SSL and specify the TLS protocols
that you want to use for the secure communication.

When you enable SSL for the MySQL connection, you must configure the SSL properties for both the MySQL
JDBC and ODBC drivers. Configure the required SSL properties for the JDBC driver, so that the Secure Agent
can access metadata securely from MySQL. Also, configure the required SSL properties for the ODBC driver,
so that the Secure Agent runs mappings to securely read from or write data to MySQL.

Note: SSL is not applicable when you use the Hosted Agent. You can configure SSL when you use the Secure
Agent.

The following table describes the MySQL connection SSL properties:

Connection Description
property

Use SSL Determines whether the Secure Agent establishes a secure connection to the MySQL database.
When you select this option and the database server supports SSL, the Secure Agent establishes
an encrypted connection. If the MySQL database server cannot configure SSL, the connection
either fails or the Secure Agent establishes an unencrypted connection depending on whether you
enable or disable the Require SSL checkbox.
If you do not select the Use SSL checkbox, the Secure Agent attempts to establish an unencrypted
connection.

Verify Server If you select Use SSL and select this option, the client validates the server certificate that is sent
Certificate by the database server.

MySQL connection properties 11

 Connection Description
property

Require SSL Applicable only if you select Use SSL.

If you select the Require SSL checkbox, and the MySQL database supports SSL, the Secure Agent
establishes an SSL connection.
If you select the Require SSL checkbox, and the MySQL database cannot configure SSL, the Secure
Agent attempts to establish an SSL connection but fails.
If you clear the Require SSL checkbox, and the MySQL database cannot configure SSL, the Secure
Agent establishes an unencrypted connection.

TLS Protocols The TLS protocols used for the secure communication when you select Use SSL.
You can select from the following protocols:
- TLSv1
- TLSv1.1
- TLSv1.2
Default is TLSv1.2. The TLSv1 and TLSv1.1 protocols are not applicable.

The following table describes the MySQL connection properties for the JDBC driver version 8.x when you
enable Use SSL:

Connection property Description

Trust Certificate Key The path and file name of the truststore file. You must prefix the file path with file colon
Store (file:).
For example, file:C:\SSL\mysql_new\truststore

Trust Certificate Key The password for the truststore file.

Store Password

Client Certificate Key The path and file name of the keystore file. You must prefix the file path with file colon
Store (file:).
For example, file:C:\SSL\mysql_new\keystore

Client Certificate Key The password to access the keystore file.

Store Password

JDBC Cipher Suites Colon-separated cipher suite values in RFC format.

For example:
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

12 Chapter 2: MySQL connections

The following table describes the MySQL connection properties for the ODBC driver version 8.x when you
enable Use SSL:

Connection property Description

SSL Certificate The path and name of the CA certificate.

Authority For example, C:\SSL\mysql_new\ca.pem

SSL Certificate The path and name of the client certificate.

For example, C:\SSL\mysql_new\client-cert.pem

SSL Key The path and the name of the private key of the client.
For example, C:\SSL\mysql_new\client-key.pem

SSL Cipher Colon-separated cipher-suite values in OpenSSL format.

For example:
ECDHE-ECDSA-AES128-GCM-SHA256:
ECDHE-ECDSA-AES256-GCM-SHA384:
ECDHE-RSA-AES128-GCM-SHA256:

Verify Server's Identity Verifies the host name in the certificate while verifying the server CA certificate.
This property is applicable only when you enable Verify Server Certificate in the SSL
properties.

MySQL connection properties 13

Chapter 3

Mappings and mapping tasks

with MySQL Connector
Use the Data Integration Mapping Designer to create a mapping. When you create a mapping, you configure a
source to represent a MySQL object.

Describe the flow of data from source and target along with the required transformations before the agent
writes data to the target. When you create a mapping task, select the mapping that you want to use. Use the
Mapping Task wizard to create a mapping task. Validate and run the mapping to read data from sources and
write to a target. The mapping task processes data based on the data flow logic you define in the mapping.

MySQL sources in mappings

To read data from a MySQL database, configure a MySQL object as the Source transformation in a mapping.

Specify the name and description of the MySQL source. Configure the source, query options, and advanced
properties for the source object.

The following table describes the source properties that you can configure for a MySQL source:

Property Description

Connection Name of the source connection.

You can select an existing connection, create a new connection, or define parameter values for the
source connection property.
If you want to overwrite the source connection properties at runtime, select the Allow parameter to
be overridden at run time option.
Specify the parameter file directory and name in the advanced session properties.

Source Type Type of the MySQL source object available. You can choose from the following source types:
- Single
- Multiple
- Query
- Parameter

14
 Property Description

Parameter A parameter file where you define values that you want to update without having to edit the task.
Select an existing parameter for the source object or click New Parameter to define a new
parameter for the source object.
The Parameter property appears only if you select parameter as the source type.
If you want to overwrite the parameter at runtime, select the Allow parameter to be overridden at
run time option.
When the task runs, the Secure Agent uses the parameters from the file that you specify in the
advanced session properties.

Object Name of the MySQL source object.

Filter Configure a simple filter or an advanced filter to remove rows at the source. You can improve
efficiency by filtering early in the data flow.
A simple filter includes a field name, operator, and value. Use an advanced filter to define a more
complex filter condition, which can include multiple conditions using the AND or OR logical
operators.

Sort Select the fields and type of sorting to use. To sort data for a parameterized source, you must use a
parameter for the sort options.

Select distinct Select this option to read only distinct rows.

rows

The following table describes the advanced source properties that you can configure for a MySQL source:

Property Description

Tracing level Amount of detail that appears in the log for this transformation. You can choose terse, normal,
verbose initialization, or verbose data. Default is normal.

Pre SQL Pre-SQL command to run before reading data from the source.

Post SQL Post-SQL command that must be run after reading data from the source.

Output is Relational source or transformation output that does not change between session runs when
Deterministic the input data is consistent between runs.
When you configure this property, the Secure Agent does not stage source data for recovery if
transformations in the pipeline always produce repeatable data.

Output is repeatable Relational source or transformation output that is in the same order between session runs
when the order of the input data is consistent.
When output is deterministic and output is repeatable, the Secure Agent does not stage source
data for recovery.

MySQL lookups in mapping

You can create lookups for objects using a MySQL connection. You can retrieve data from a MySQL lookup
object based on the specified lookup condition.

When you configure a lookup in MySQL, you select the lookup connection and lookup object.

MySQL lookups in mapping 15

 Note: You can't configure a Lookup transformation in a data transfer task.

The following table describes the MySQL lookup object properties that you can configure in a Lookup
transformation:

Property Description

Connection Name of the lookup connection.

You can select an existing connection, create a new connection, or define parameter values for the
lookup connection property.
If you want to overwrite the lookup connection properties at runtime, select the Allow parameter to
be overridden at run time option.
Specify the parameter file directory and name in the advanced session properties.

Source Type Type of the MySQL lookup object available. You can choose from the following lookup object types:
- Single Object
- Parameter

Parameter A parameter file where you define values that you want to update without having to edit the task.
Select an existing parameter for the lookup object or click New Parameter to define a new
parameter for the lookup object.
The Parameter property appears only if you select parameter as the source type.
If you want to overwrite the parameter at runtime, select the Allow parameter to be overridden at
run time option.
When the task runs, the Secure Agent uses the parameters from the file that you specify in the
advanced session properties.

Lookup Object Name of the MySQL lookup object.

Multiple The behavior when the lookup condition returns multiple matches.
Matches You can select one of the following options:
- Return first row
- Return last row
- Return any row
- Return all rows
- Report error

Calling a stored procedure

You can use the SQL transformation to call a stored procedure in a MySQL database or to process SQL
queries midstream in a pipeline.

Before you configure stored procedures, you must specify the following property in the Runtime Advanced
Connection Properties in the MySQL connection for stored procedures to work: NO_SSPS=1

Note: Informatica recommends that you create a separate MySQL connection and specify the property when
you configure stored procedures.

You can then configure the SQL transformation to process the following types of SQL statements:

16 Chapter 3: Mappings and mapping tasks with MySQL Connector

 Stored procedure

Stored procedures reside in the database and run within the database. When you configure the SQL
transformation to process a stored procedure, it passes input parameters to the stored procedure. The
stored procedure passes the return value or values to the output fields of the transformation.

SQL Query

You can configure the SQL transformation to process a saved query that you create in Data Integration
or you can enter a query in the SQL editor.

For more information about SQL transformations, see Transformations in the Data Integration
documentation.

Rules and guidelines for calling a stored procedure

Consider the following rules and guidelines for calling a stored procedure:

• You can't define a stored procedure that contains Unicode characters.

• You can't configure an unconnected stored procedure using the SQL transformation.
• You can't process a stored function in an SQL transformation.
• You can't configure the input or in-out parameter in an entered query that you define in the SQL editor.

Calling a stored procedure 17

Chapter 4

Troubleshooting
Use the following sections to troubleshoot errors in MySQL Connector.

For a list of common error messages and possible solutions, see the article,
"Troubleshooting: Common Error Messages".

18
Appendix A

Data type reference

Data Integration uses the following data types in tasks and mappings with MySQL:
MySQL native data types

MySQL data types appear in the source transformations when you choose to edit metadata for the fields.

Transformation data types

Set of data types that appear in the transformations. They are internal data types based on ANSI SQL-92
generic data types, which the Secure Agent uses to move data across platforms. Transformation data
types appear in all transformations in a mapping.

When Data Integration reads source data, it converts the native data types to the comparable
transformation data types before transforming the data.

MySQL and transformation data types

The following table lists the MySQL data types that Data Integration supports and the corresponding
transformation data types:

MySQL Data Transformation Data Description

Type Type

Char String 1 to 104,857,600 characters

Varchar String 1 to 104,857,600 characters

Boolean Integer -2,147,483,648 to 2,147,483,647 (Precision 10, scale 0)

TinyInt Integer -2,147,483,648 to 2,147,483,647 (Precision 10, scale 0)

SmallInt Integer -2,147,483,648 to 2,147,483,647 (Precision 10, scale 0)

MediumInt Integer -2,147,483,648 to 2,147,483,647 (Precision 10, scale 0)

Int Integer -2,147,483,648 to 2,147,483,647 (Precision 10, scale 0)

Note: Unsigned Int is not applicable.

Bigint Bigint -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 (Precision 19,

scale 0)
Note: Unsigned Bigint is not applicable.

19
 MySQL Data Transformation Data Description
Type Type

Float Decimal Precision 1 to 28, scale 0 to 28

Double Double Precision 15

Note: Unsigned Double is not applicable.

Decimal Decimal Precision 1 to 28, scale 0 to 28

Date Date/Time Jan 1, 0001 A.D. to Dec 31, 9999 A.D. (Precision to the nanosecond)

Datetime Date/Time Jan 1, 0001 A.D. to Dec 31, 9999 A.D. (precision to the nanosecond)

Timestamp Date/Time Jan 1, 0001 A.D. to Dec 31, 9999 A.D. (precision to the nanosecond)

20 Appendix A: Data type reference

Index

C MySQL Connector (continued)

administration 6
Cloud Application Integration community connections 10
URL 4 supported assets 6
Cloud Developer community MySQL JDBC driver
URL 4 configuration 7
connections MySQL ODBC driver
MySQL 10 configuration 7
installation on Linux 8
installation on Windows 7

D MySQL sources
mapping 15
Data Integration community rules and guidelines 9
URL 4
data type reference
overview 19 S
status

I Informatica Intelligent Cloud Services 5

system status 5
Informatica Global Customer Support
contact information 5
Informatica Intelligent Cloud Services
web site 4
T
troubleshooting
overview 18

M trust site
description 5
maintenance outages 5
mapping
mapping task 14
mappings
U
MySQL sources 14 upgrade notifications 5
MySQL
connection properties 10
data types 19
MySQL connector
W
rules and guidelines 17 web site 4
MySQL Connector
overview 6

21