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.5.6
  • All Products

Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Application Service Guide

Application Service Guide

Back Next

Configuring Native Connectivity

Configuring Native Connectivity

You can configure native connectivity to an Oracle database to increase performance.
The following steps provide a guideline for configuring native connectivity using Oracle Net Services or Net8. For specific connectivity instructions, see the database documentation.
  1. Verify that the Oracle home directory is set.
    For example: 
    ORACLE_HOME=C:\Oracle
  2. Verify that the PATH environment variable includes the Oracle bin directory.
    For example, if you install Net8, the path might include the following entry: 
    PATH=C:\ORANT\BIN;
  3. Configure the Oracle client to connect to the database that you want to access.
    Launch SQL*Net Easy Configuration Utility or edit an existing
    tnsnames.ora
     file to the home directory and modify it.
    By default, the
    tnsnames.ora
     file is stored in the following directory:
    <OracleInstallationDir>\network\admin
    .
    Enter the correct syntax for the Oracle connect string, typically
    databasename.world
    . Make sure the SID entered here matches the database server instance ID defined on the Oracle server.
    Here is a sample
    tnsnames.ora
     file. Enter the information for the database. 
    mydatabase.world = 
   (DESCRIPTION
   (ADDRESS_LIST =
        (ADDRESS = 
           (COMMUNITY = mycompany.world
           (PROTOCOL = TCP)
           (Host = mymachine)
           (Port = 1521)
        )
   )
   (CONNECT_DATA =
      (SID = MYORA7)
      (GLOBAL_NAMES = mydatabase.world)
    Here is a sample
    tnsnames.ora
     file to connect to Oracle using Oracle Connection Manager: 
    ORCL19C_CMAN =
(description=
(address_list=
(source_route=yes)
(address=(protocol=tcp)(host=inrh74ocm.mycompany.com)(port=1521))
(address=(protocol=tcp)(host=inrh74oradb.mycompany.com)(port=1521))
)
(connect_data=
(service_name=ORCL19C.mycompany.com)
)
)
  4. Set the NLS_LANG environment variable to the locale, including language, territory, and character set, you want the database client and server to use with the login.
    The value of this variable depends on the configuration. For example, if the value is american_america.UTF8, you must set the variable as follows: 
    NLS_LANG=american_america.UTF8;
    To determine the value of this variable, contact the database administrator.
  5. To set the default session time zone when the Data Integration Service reads or writes the Timestamp with Local Time Zone data, specify the ORA_SDTZ environment variable.
    You can set the ORA_SDTZ environment variable to any of the following values:
    • Operating system local time zone ('OS_TZ')
    • Database time zone ('DB_TZ')
    • Absolute offset from UTC (for example, '-05:00')
    • Time zone region name (for example, 'America/Los_Angeles')
    You can set the environment variable at the machine where Informatica server runs.
  6. If the tnsnames.ora file is not in the same location as the Oracle client installation location, set the TNS_ADMIN environment variable to the directory where the tnsnames.ora file resides.
    For example, if the tnsnames.ora file is in the C:\oracle\files directory, set the variable as follows: 
    TNS_ADMIN= C:\oracle\files
  7. Verify that you can connect to the Oracle database.
    To connect to the database, launch SQL*Plus and enter the connectivity information. If you fail to connect to the database, verify that you correctly entered all of the connectivity information.
    Use the connect string as defined in the
    tnsnames.ora
     file.
0 COMMENTS
We’d like to hear from you!