In a Microsoft SQL Server database, Dynamic Data Masking fails to mask a stored procedure that has all data types as parameters.

In a Microsoft SQL Server database, Dynamic Data Masking fails to mask a table valued statement that ends in a semicolon (;).

In a Microsoft SQL Server database, Dynamic Data Masking fails to mask a statement that contains the CURRENT TIMESTAMP keyword.

In a Microsoft SQL Server database, Dynamic Data Masking fails to mask a statement that contains the CONVERT(value, type) function.

Dynamic Data Masking fails to mask a statement with the From Clause Object matcher if the statement contains table hints.

In a Microsoft SQL Server database, Dynamic Data Masking does not display the column name for a statement that contains the DISTINCT function.

In a Microsoft SQL Server database, Dynamic Data Masking fails to parse a DECLARE block.

In a Microsoft SQL Server database, Dynamic Data Masking fails to mask a statement that contains SELECT * while in command mode.

In Impala and Hive databases, Dynamic Data Masking fails to mask a statement that contains fully qualified quoted column names.

For a generic database node, the database connection fails if the database server restarts.

In a Hive 2 database, Dynamic Data Masking fails to parse a statement that contains the LIMIT keyword.

In Impala and Hive databases, the masked query is not valid.

In a Microsoft SQL Server database, Dynamic Data Masking fails to mask data when creating a temporary table and inserting data into the temporary table.

The AUTH_MACHINE and AUTH_PROGRAM_NM do not work for IBM DB2 i/OS with JDBC drivers.

Dynamic Data Masking does not impersonate columns that use the INTERNAL data type on an Informix database.

The Stored Procedure Accelerator for Sybase does not mask a stored procedure if the stored procedure name starts with a number.

The AUTH_MACHINE and AUTH_PROGRAM_NM do not work for IBM DB2 z/OS with JDBC drivers.

The Stored Procedure Accelerator for Sybase does not mask a stored procedure if the stored procedure name is a Sybase reserved word.

The Stored Procedure Accelerator for Sybase does not mask a stored procedure if the stored procedure name contains an at-sign (@).

Impersonation does not work in the Rule Set Simulator for Teradata and Sybase databases.

Oracle stored procedure masking fails if the request contains multiple columns with the same name.

A SELECT * query does not work with Hive ODBC drivers.

Dynamic Data Masking does not parse IBM DB2 XQuery expressions.

If you join two schemas that have the same table name and column name, when you mask one table, Dynamic Data Masking masks both tables.

Masking fails for an Informix database request if the table contains a column with the INTERVAL data type.

Spaces are added to rule.log that are not in the Security Rule Simulator output.

Dynamic Data Masking returns unmasked data if the query contains an XMLQUERY function.

Dynamic Data Masking does not parse the MOD function with a percent sign (%).

On a MySQL database, Dynamic Data Masking returns unmasked data for a SELECT * FROM EMPLOYEES query.

Dynamic Data Masking does not mask data correctly for the DDM for ODBC and DDM for JDBC services if the rule tree hierarchy contains multiple levels and the rules use the Continue processing action.

Dynamic Data Masking does not parse the WITH common table expression.

Oracle stored procedure masking fails when passing TO_DATE() as a constant input for a date argument.

If you have a Teradata database with COP enabled, the Dynamic Data Masking Server gives an error with an unresolved address exception.

During upgrade, Dynamic Data Masking does not restart the computer if the restart option has been selected.

The AUTH_CURRENT_DATABASE symbol does not work for Informix native JDBC drivers and ODBC drivers.

Some keywords are not parsed for IBM DB2 databases.

The setport Server Control command logs incorrect information.

Dynamic Data Masking returns unmasked data if the query contains an XMLTABLE function.

Dynamic Data Masking does not parse the IBM DB2 CURRENT TIMEZONE special register.

In a Sybase database, Dynamic Data Masking fails to mask a statement that contains the DISTINCT function.

On a Greenplum database, Dynamic Data Masking does not mask a column that has a name that is a keyword. Workaround: Add the word "as" between the column name and the alias. For example, enter "select last_name as name from employee."

The query fails if you use the column alias \(alias) with the column alias \(col).

Dynamic Data Masking does not parse the INTO statement in a query to Amazon Redshift.

Dynamic Data Masking does not parse the DATEDIFF function in a query to Amazon Redshift.

Dynamic Data Masking does not parse the TIMESTAMP EPOCH value in a query to Amazon Redshift.

Dynamic Data Masking does not parse the LIMIT clause in a query to Amazon Redshift.

You receive an error if the connection to Amazon Redshift is idle for an extended period of time.

Dynamic Data Masking does not parse a query to Amazon Redshift that uses :: to cast.

Dynamic Data Masking does not parse the IBM DB2 REC2XML function.

Dynamic Data Masking does not parse the FROM match clause in a query.

Dynamic Data Masking does not mask a column if there is a join and a custom alias for the column.

Dynamic Data Masking does not preserve the order in an ORDER BY clause.

Dynamic Data Masking does not parse IBM DB2 queries with a VALUES clause.

Dynamic Data Masking does not parse a function that contains the ALL keyword in a query to Amazon Redshift.

Dynamic Data Masking does not parse the NTH_VALUE function in a query to Amazon Redshift.

Dynamic Data Masking does not parse ROWNUM as an alias in a query to Amazon Redshift.

Dynamic Data Masking does not parse a substring(<Literal> from <val> for <val>) function in a query to Amazon Redshift.

Dynamic Data Masking does not parse an expression that contains a caret in a query to Amazon Redshift.

The LDAP Accelerator template contains incorrect rules.

A SELECT * query to an IBM DB2 database fails if the owner is not the current user.

Dynamic Data Masking places double quotes around table names, column names, and aliases.

When you query a Teradata database with the QUALIFY_RANK keyword, the query fails.

Dynamic Data Masking does not match the host in the Client/Application Information rule matcher for File Archive Service databases.

The PL/SQL Function rule action does not return "Include Program Name" with the IBM DB2 Informatica JDBC drivers.

The Block Statement rule action returns an incorrect block statement for DB2 databases.

Connection pooling does not work for all databases.

A query to a Sybase database fails if the query contains an alias.

The AUTH_SID global symbol does not work for Microsoft SQL Server, Informix, Data Vault, and Sybase databases.

Some keywords are not parsed for Sybase databases.

In some cases, the Client/Application Information rule matcher does not work for a Microsoft SQL Server database.

The Microsoft SQL Server Stored Procedure Accelerator returns an invalid status when the procedure returns a status code through a C# program.

Dynamic Data Masking does not mask the column if it is given as a nested query to a Sybase database.

If the database name is not in the connect string, the AUTH_CURRENT_DATABASE global symbol does not work for Informix databases. If you switch the database within a session, the AUTH_CURRENT_DATABASE global variable does not work for Informix.

Dynamic Data Masking returns unmasked data if the query contains an XMLELEMENT function.

Dynamic Data Masking returns unmasked data if the query contains an XMLFOREST function.

A connection to Oracle 12C through Dynamic Data Masking using an ODAC 12.x driver fails.

Dynamic Data Masking impersonation does not work for Informix.

You must use a table name alias for statements that contain LIMIT, SORT BY, CLUSTER BY, and DISTRIBUTE BY clauses for Hive databases.

The Stored Procedure Accelerator for Sybase does not support the timestamp data type in the bind variable for the OLE DB provider.

The Stored Procedure Accelerator for Sybase does not support the timestamp data type in the bind variable for the ODBC driver.

The Stored Procedure Accelerator for Sybase does not support the datetime data type in the bind variable for the jTDS driver.

When you use the Manage Licenses option in the Management Console to add a new license key, Dynamic Data Masking removes the old license from the installation directory.

On a Greenplum database, if you query "select employee from employee," Dynamic Data Masking does not mask the result set.

The AUTH_URL global symbol does not work for the DDM for ODBC service when you use the Check Property connection rule matcher.

When you use the Dynamic Data Masking for FAS service, if you enable SSL in the Data Vault for client server communication, the Dynamic Data Masking test connection fails.

When you use the -Drules.mask.new=true flag, if the inner query contains a column specification in the SELECT clause with a different alias than the column alias, masking fails.

The Symbol matcher cannot contain more than 160,000 values.

Dynamic Data Masking might mask incorrect columns if the query contains a column alias.

The PL/SQL Function rule action fails when passing a statement as an argument if the statement contains a query with single quotes (').

In an Impala database, Dynamic Data Masking fails to parse a SELECT clause that contains the NOT LIKE operator.

In an Impala database, Dynamic Data Masking fails to parse a SELECT clause that contains the LIKE operator.

In an Impala database, Dynamic Data Masking fails to parse a statement that contains <=> operator (IS DISTINCT FROM ).

In an Impala database, Dynamic Data Masking fails to parse the ! operator.

In an Impala database, Dynamic Data Masking fails to parse a SELECT clause that contains the BETWEEN operator.