Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Security
  5. Connection Management
  6. JDBC Client Configuration
  7. ODBC Client Configuration
  8. Configuration for MicroStrategy
  9. Access Control
  10. Logs
  11. High Availability
  12. Server Control
  13. Performance Tuning
  14. Troubleshooting
  15. Appendix A: Database Keywords

Administrator Guide

Administrator Guide

COP Discovery through the Teradata Driver

COP Discovery through the Teradata Driver

In a typical Teradata environment, the Teradata JDBC driver handles COP discovery. COP discovery through the Teradata driver identifies all of the COP host IP addresses.
Internally, when the Teradata JDBC Driver runs COP discovery, it appends "cop1" to the database hostname, then proceeds to cop2, cop3, cop4. The driver will continue running DNS lookups sequentially until it encounters an unknown COP hostname. Alternatively, if you have enabled the COPLAST connection parameter, the driver runs DNS lookups until it finds a COP hostname whose IP address matches the coplast hostname. For more information on the COPLAST connection parameter and the coplast hostname, see the Teradata connectivity documentation.
When a client connects to a Teradata database through a JDBC URL, the client provides the hostname without the COP suffix and the driver selects a COP entry to attempt to connect. If the first COP entry fails, the driver tries another.

0 COMMENTS

We’d like to hear from you!