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

Oracle Connection Management

Oracle Connection Management

Select the Oracle database type to add an Oracle database connection node to the Management Console tree.
If the Dynamic Data Masking service runs on the Oracle database server, you must switch the Oracle listener to a hidden port. Edit the
listener.ora
file to change the Oracle listener to a port that is not in use. When you change the Oracle listener to a hidden port, applications connect to the Dynamic Data Masking listener port instead of the database.
To route applications to the Dynamic Data Masking listener port, you must edit
tnsnames.ora
to add a database alias to
tnsnames.ora
for the Dynamic Data Masking service. Dynamic Data Masking uses the database alias to listen to incoming connections to the database.
Informatica recommends that you change the Oracle listener to a port that is not the default. If you do not change the port, it is possible for an unauthorized user to edit the connection properties from the client and bypass the Dynamic Data Masking Server. Also, when you change the Oracle listener and configure Dynamic Data Masking to listen on the default Oracle listener, you do not have to edit the client connection properties.
Click
Test Connection
to verify that the Dynamic Data Masking service can access the database. If a database defines multiple instances,
Test Connection
validates each Oracle instance cyclically. The test connection verifies each Oracle instance.

0 COMMENTS

We’d like to hear from you!