IBM Informix connections

DataMasque masks IBM Informix tables in place.

• Required privileges
• Connection parameters
• Limitations
• Unsupported key columns

Required privileges

A DataMasque connection for IBM Informix requires at least the following permissions:

• CONNECT privilege on the database. Informix does not grant this implicitly; it must be granted to the user (or to PUBLIC).
• RESOURCE privilege on the database. DataMasque uses this to create the mapping and staging tables and sequences it requires during masking (CREATE TABLE and CREATE SEQUENCE).
• SELECT and UPDATE on each table to be masked.
• ALTER on each table to be masked. DataMasque uses this to manage constraints during masking (via SET CONSTRAINTS).
• INDEX on each table to be masked. DataMasque uses this to recreate indexes during masking. Informix permits DROP INDEX only to the index owner or a user with DBA, so the connection user must own the masked tables' indexes (typically by connecting as the schema owner), or hold DBA.
• DELETE on each table targeted by a truncate_table task, where truncation tasks are used.

GRANT CONNECT TO <user>;
GRANT RESOURCE TO <user>;

GRANT SELECT, UPDATE, ALTER, INDEX ON <table> TO <user>;

-- Required only where truncation tasks are used
GRANT DELETE ON <table> TO <user>;

Notes:

1. The system catalogue tables DataMasque reads during discovery (systables, syscolumns, sysindexes, sysconstraints, and sysreferences) are readable by any user with the CONNECT privilege; no explicit grants are required.

2. Repeat the table-level grants for each table to be masked.

Connection parameters

For IBM Informix databases, the following field is optional:

Schema	The name of the schema (table owner) that DataMasque will operate on. If not specified, the connection user's name will be used as the default schema.

Notes:

1. The default port for Informix connections is 9089. If no port is specified in the connection settings, DataMasque will use this default.

2. Informix folds unquoted identifiers to lower case. Specify schema, table, and column names in lower case unless they were created as quoted (delimited) identifiers.

Limitations

• mask_unique_key tasks are not supported. Use the imitate_unique mask instead.

• Subsetting is not supported.

Unsupported key columns

Data Type	Unsupported Format
text	All
byte	All
blob	All
clob	All
boolean	All
decimal (fixed point)	Precision >= 32
decimal (floating point)	Precision >= 16
money	Precision >= 32