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.

Use

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.