Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Engineering 10.4.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dp Command Reference
  16. infacmd idp Command Reference
  17. infacmd edp Command Reference
  18. Infacmd es Command Reference
  19. infacmd ihs Command Reference
  20. infacmd ipc Command Reference
  21. infacmd isp Command Reference
  22. infacmd ldm Command Reference
  23. infacmd mas Command Reference
  24. infacmd mi Command Reference
  25. infacmd mrs Command Reference
  26. infacmd ms Command Reference
  27. infacmd oie Command Reference
  28. infacmd ps Command Reference
  29. infacmd pwx Command Reference
  30. infacmd roh Command Reference
  31. infacmd rms Command Reference
  32. infacmd rtm Command Reference
  33. infacmd sch Command Reference
  34. infacmd search Command Reference
  35. infacmd sql Command Reference
  36. infacmd tdm Command Reference
  37. infacmd tools Command Reference
  38. infacmd wfs Command Reference
  39. infacmd ws Command Reference
  40. infacmd xrf Command Reference
  41. infacmd Control Files
  42. infasetup Command Reference
  43. pmcmd Command Reference
  44. pmrep Command Reference
  45. Working with pmrep Files

Command Reference

Command Reference

Back Next

JDBC Connection Options

JDBC Connection Options

Use connection options to define a JDBC connection.
Enter connection options in the following format:
... -o option_name=value option_name=value ...
To enter multiple options, separate options with spaces. To enter a value that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
The following table describes JDBC connection options for infacmd isp CreateConnection and UpdateConnection commands:
Option
Description
JDBCDriverClassName
The Java class that you use to connect to the database.
The following list provides the driver class name that you can enter for the applicable database type:
  • DataDirect JDBC driver class name for Oracle: 
    com.informatica.jdbc.oracle.OracleDriver
  • DataDirect JDBC driver class name for IBM DB2: 
    com.informatica.jdbc.db2.DB2Driver
  • DataDirect JDBC driver class name for Microsoft SQL Server: 
    com.informatica.jdbc.sqlserver.SQLServerDriver
  • DataDirect JDBC driver class name for Sybase ASE: 
    com.informatica.jdbc.sybase.SybaseDriver
  • DataDirect JDBC driver class name for Informix: 
    com.informatica.jdbc.informix.InformixDriver
  • DataDirect JDBC driver class name for MySQL: 
    com.informatica.jdbc.mysql.MySQLDriver
For more information about which driver class to use with specific databases, see the vendor documentation.
MetadataConnString
The URL that you use to connect to the database.
The following list provides the connection string that you can enter for the applicable database type:
  • DataDirect JDBC driver for Oracle: 
    jdbc:informatica:oracle://<hostname>:<port>;SID=<sid>
  • DataDirect JDBC driver for IBM DB2: 
    jdbc:informatica:db2://<hostname>:<port>;DatabaseName=<database name>
  • DataDirect JDBC driver for Microsoft SQL Server: 
    jdbc:informatica:sqlserver://<host>:<port>;DatabaseName=<database name>
  • DataDirect JDBC driver for Sybase ASE: 
    jdbc:informatica:sybase://<host>:<port>;DatabaseName=<database name>
  • DataDirect JDBC driver for Informix: 
    jdbc:informatica:informix://<host>:<port>;informixServer=<informix server name>;databaseName=<dbName>
  • DataDirect JDBC driver for MySQL: 
    jdbc:informatica:mysql://<host>:<port>;DatabaseName=<database name>
For more information about the connection string to use for specific databases, see the vendor documentation for the URL syntax.
EnvironmentSQL
Optional. SQL commands to set the database environment when you connect to the database. The Data Integration Service executes the connection environment SQL each time it connects to the database.
For example,
ALTER SESSION SET CURRENT_SCHEMA=INFA_USR;
Enclose special characters in double quotation marks.
TransactionSQL
Optional. SQL commands to execute before each transaction. The Data Integration Service executes the transaction SQL at the beginning of each transaction.
For example,
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
Enclose special characters in double quotes.
QuoteChar
Optional. The character that you will use for quotes in this connection.
The type of character used to identify special characters and reserved SQL keywords, such as WHERE. The Data Integration Service places the selected character around special characters and reserved SQL keywords. The Data Integration Service also uses this character for the QuoteChar property. Default is DOUBLE_QUOTE.
EnableQuotes
Optional. Select to enable quotes or not for this connection.
When enabled, the Data Integration Service places identifier characters around table, view, schema, synonym, and column names when generating and executing SQL against these objects in the connection. Use if the objects have mixed-case or lowercase names. Valid values are True or False. Default is True.
hadoopConnector
Required if you want to enable Sqoop connectivity for the data object that uses the JDBC connection. The Data Integration Service runs the mapping in the Hadoop run-time environment through Sqoop.
You can configure Sqoop connectivity for relational data objects, customized data objects, and logical data objects that are based on a JDBC-compliant database.
Set the value to
SQOOP_146
 to enable Sqoop connectivity.
hadoopConnectorArgs
Optional. Enter the arguments that Sqoop must use to connect to the database. Enclose the Sqoop arguments within single quotes. Separate multiple arguments with a space.
For example,
hadoopConnectorArgs='--<Sqoop argument 1> --<Sqoop argument 2>'
To read data from or write data to Teradata through Teradata Connector for Hadoop (TDCH) specialized connectors for Sqoop, define the TDCH connection factory class in the hadoopConnectorArgs argument. The connection factory class varies based on the TDCH Sqoop Connector that you want to use.
  • To use Cloudera Connector Powered by Teradata, configure the hadoopConnectorArgs argument as follows:
    hadoopConnectorArgs='-Dsqoop.connection.factories=com.cloudera.connector.teradata.TeradataManagerFactory'
  • To use Hortonworks Connector for Teradata (powered by the Teradata Connector for Hadoop), configure the hadoopConnectorArgs argument as follows:
    hadoopConnectorArgs='-Dsqoop.connection.factories=org.apache.sqoop.teradata.TeradataManagerFactory'
If you do not enter Sqoop arguments, the Data Integration Service constructs the Sqoop command based on the JDBC connection properties.
0 COMMENTS
We’d like to hear from you!