Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Application Patch Deployment
  12. Application Patch Deployment Example
  13. Continuous Integration and Continuous Delivery (CI/CD)
  14. Object Import and Export
  15. Appendix A: Data Type Reference
  16. Appendix B: Keyboard Shortcuts
  17. Appendix C: Connection Properties

Developer Tool Guide

Developer Tool Guide

Oracle Connection Properties

Oracle Connection Properties

Use an Oracle connection to connect to an Oracle database. The Oracle connection is a relational connection type. You can create and manage an Oracle connection in the Administrator tool, the Developer tool, or the Analyst tool.
The order of the connection properties might vary depending on the tool where you view them.
The following table describes Oracle connection properties:
Property
Description
Database Type
The database type.
Name
Name of the connection. The name is not case sensitive and must be unique within the domain. The name cannot exceed 128 characters, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
ID
String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name.
Description
The description of the connection. The description cannot exceed 765 characters.
User Name
The database user name.
Password
The password for the database user name.
Pass-through security enabled
Enables pass-through security for the connection. When you enable pass-through security for a connection, the domain uses the client user name and password to log into the corresponding database, instead of the credentials defined in the connection object.
Metadata Access Properties: Connection String
Connection string used to access metadata from the database.
Use the following connection string:
jdbc:informatica:oracle://<host_name>:<port>;SID=<database name>
AdvancedJDBCSecurityOptions
Database parameters for metadata access to a secure database. Informatica treats the value of the AdvancedJDBCSecurityOptions field as sensitive data and stores the parameter string encrypted.
To connect to a secure database, include the following parameters:
  • EncryptionMethod. Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to SSL.
  • ValidateServerCertificate. Optional. Indicates whether Informatica validates the certificate that is sent by the database server.
    If this parameter is set to True, Informatica validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate.
    If this parameter is set to false, Informatica does not validate the certificate that is sent by the database server. Informatica ignores any truststore information that you specify.
  • HostNameInCertificate. Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate.
  • cryptoProtocolVersion. Optional. If you enable TLS for the Oracle instance, set the cryptoProtocolVersion parameter as follows:
    cryptoProtocolVersion=TLSv<version number>.
    For example, cryptoProtocolVersion=TLSv1.2
    The version number must be the same as the TLS version you configured for the server.
  • TrustStore. Required. Path and file name of the truststore file.
    If you configure SSL or TLS and specify only the file name, you must copy the truststore file to the Informatica installation directory.
    To test the connection and import metadata, copy the truststore file to the following directory:
    <Informatica client installation directory>/clients/DeveloperClient
    To run the mapping, copy the truststore file to the following directory:
    <Informatica server installation directory>/tomcat/bin
  • TrustStorePassword. Required. Password for the truststore file for the secure database.
  • KeyStore. Required. Path and file name of the keystore file.
  • KeyStorePassword. Required. Password for the keystore file for the secure database.
Informatica appends the secure JDBC parameters to the connection string. If you include the secure JDBC parameters directly to the connection string, do not enter any parameters in the AdvancedJDBCSecurityOptions field.
Data Access Properties: Connection String
Use the following connection string:
<database name>.world
Code Page
The code page used to read from a source database or to write to a target database or file.
Environment SQL
SQL commands to set the database environment when you connect to the database. The Data Integration Service runs the connection environment SQL each time it connects to the database.
Transaction SQL
SQL commands to set the database environment when you connect to the database. The Data Integration Service runs the transaction environment SQL at the beginning of each transaction.
Retry Period
This property is reserved for future use.
Enable Parallel Mode
Enables parallel processing when loading data into a table in bulk mode. By default, this option is cleared.
SQL Identifier Character
Type of character that the database uses to enclose delimited identifiers in SQL queries. The available characters depend on the database type.
Select (None) if the database uses regular identifiers. When the Data Integration Service generates SQL queries, the service does not place delimited characters around any identifiers.
Select a character if the database uses delimited identifiers. When the Data Integration Service generates SQL queries, the service encloses delimited identifiers within this character.
Support Mixed-case Identifiers
Enable if the database uses case-sensitive identifiers. When enabled, the Data Integration Service encloses all identifiers within the character selected for the
SQL Identifier Character
property.
When the
SQL Identifier Character
property is set to none, the
Support Mixed-case Identifiers
property is disabled.

0 COMMENTS

We’d like to hear from you!