Message Reference > I Message Codes > IDM Messages
  

IDM Messages

IDM_24007 The Data Masking transformation could not read the highgroup.txt file.

Explanation:
The highgroup.txt file is either unavailable or damaged.
User Response:
Download the latest highgroup.txt file to the <PowerCenter Installation Directory>\infa_shared\SrcFiles\.

IDM_24013 Failed to mask: <string>. Using default value from defaultValue.xml as output.

Explanation:
The source data format or datatype is invalid for the mask. The Integration Service applied a default mask to the port. The Integration Service applies mask values from the default value file
User Response:
Verify that the source data is the correct data type or the data is in the correct format for a special mask.

IDM_24023 The Data Masking transformation failed to initialize the XML parser.

Explanation:
The XML parser has failed.
User Response:
Contact Informatica Global Customer Support.

IDM_24030 The Data Masking transformation failed to mask the date.

User Response:
Check the masking rules and input values. Check the date format in the source. The date format must be supported by PowerCenter.

IDM_24036 The Data Masking transformation failed to mask the number.

Explanation:
A source number was not masked because the data was inconsistent with the masking rules.
User Response:
Review other errors in the session log to determine the problem. Check the source data against the masking rules.

IDM_24038 The Data Masking transformation failed to mask the string.

Explanation:
A source string was not masked because the data was inconsistent with the masking rules.
User Response:
Review other errors in the session log. Check the masking rules against the input values in the source data.

IDM_24039 The Data Masking transformation failed to create the masking object.

User Response:
Run the session again. If the problem persists, contact Informatica Global Customer Support.

IDM_24045 The Data Masking transformation failed to read the data masking rules.

User Response:
Run the session again. If the problem persists, contact Informatica Global Customer Support.

IDM_24051 The Data Masking transformation failed to create a masking rule.

User Response:
Run the session again. If the problem persists, contact Informatica Global Customer Support.

IDM_24055 Seed is not between 1 and 1000. Using default value for seed.

Explanation:
A column is configured for key masking in the Data Masking transformation. The seed value is configured in a mapping parameter. The mapping parameter has an incorrect value. The Integration Service used the seed value from the defaultValue.xml file. The defaultValue.xml file contains default mask values.
User Response:
Configure the mapping parameter value to be a number between 1 and 1000.

IDM_24056 Seed defined in the Data Masking default file is not between 1 and 1000. Using 725 as value for seed.

Explanation:
A column is configured for key masking in the Data Masking transformation. The seed value in a mapping parameter file is invalid. The seed value in the Data Masking default file also is invalid. The Integration Service uses 725 as the default seed value.
User Response:
Update default_seed in the default mask values file, defaultValue.xml. Verify the seed value is between 1 and 1000. The default mask values file is in the following location: <PowerCenter Installation Directory>\infa_shared\SrcFiles\defaultValue.xml.

IDM_24057 Failed to mask SSN: <number>. The SSN is invalid.

Explanation:
The source Social Security number is invalid because the area is not in the highgroup.txt file from the Social Security Administration. The area is the first three digits of the Social Security number. The Data Masking transformation does not mask the Social Security number if the source number is invalid.
User Response:
Verify the Social Security number.

IDM_24058 Transformation failed to evaluate expression <expression>.

Explanation:
The session failed when the Data Masking transformation attempted to evaluate an expression. The expression returned invalid results.
User Response:
Check the session reject file or error log to find the row that caused the error. If this is a recurring error, change the expression.

IDM_24059 Expression parse fatal error; Failed to parse expression <expression>. Should be: Fatal error while parsing Data Masking transformation expression.

Explanation:
The session failed when the Data Masking transformation attempted to evaluate an expression.
User Response:
Check the session reject file or error log to find the row that caused the error. If this is a recurring error, change the expression that references the port.

IDM_24060 Datatype of the evaluated expression, <expression>, and the port datatype are not the same. Using default value of the port datatype as output. Change to: Expression datatype is not the same as the port datatype. Using a default port value to mask data.

Explanation:
The Integration Service could not apply a mask to a port configured for expression masking. The expression returns a result that is not the same datatype as the port in the Data Masking transformation. The Data Masking transformation returns a default masked value.
User Response:
When you create an expression for a Data Masking transformation port, verify that the expression returns a value that matches the port datatype. The Expression Editor does not validate if the expression returns a datatype that is valid for the port.

IDM_24061 No connection information for the relational dictionary has been specified.

Explanation:
The Data Masking transformation is configured to use a relational dictionary, but there is no connection information for the dictionary.
User Response:
Configure a connection object for the IDM_Dictionary connection on the Mapping tab of the session properties.

IDM_24062 No connection information for storage has been specified.

Explanation:
The Data Masking transformation is configured to use a storage table for repeatable masking, but there is no connection information for the database table.
User Response:
Configure a connection object for the IDM_Storage connection on the Mapping tab of the session properties.

IDM_24063 Storage table does not exist. Create the storage table before running a session.

Explanation:
The Data Masking transformation is configured for repeatable substitution or expression masking. The storage table that maintains source data and masked value pairs does not exist.
User Response:
Informatica provides SQL scripts to create a storage table for a Sybase, Microsoft SQL Server, IBM DB2, or Oracle database. The scripts are located in the <PowerCenter installation directory>\client\bin\Extensions\DataMasking directory. Create a storage table and configure a connection to the table before you run the session.

IDM_24064 Size of the dictionary is zero. Unable to select a masked value.

Explanation:
The Data Masking transformation is configured for substitution masking. The dictionary that provides the substitute data is empty.
User Response:
Verify that the correct dictionary file or table is configured in the Masking Properties tab of the Data Masking transformation. Verify that the dictionary contains data.

IDM_24065 Unable to select a unique masked value from the dictionary.

Explanation:
The Data Masking transformation is configured for repeatable masking. The Data Masking transformation cannot return unique masked values because the dictionary does not have enough data.
User Response:
Verify that the dictionary has more unique values than the source data.

IDM_24066 Unable to select a masked value from the dictionary.

Explanation:
The Integration Service was unable to retrieve a substitute masked value from the dictionary for data masking.
User Response:
Verify the structure of the dictionary is correct. Each row in the dictionary must have a serial number. The serial numbers are integers that start at one. The rows are numbered sequentially with no gaps in the numbers. Configure the serial number column name in the Data Masking transformation.

IDM_24067 The dictionary <dictionary name> is unavailable in the connection provided.

Explanation:
The Data Masking transformation is configured for substitution masking. The relational dictionary that provides the substitute data is unavailable for the connection.
User Response:
When you configure a relational dictionary, configure a relational connection for the dictionary on the Mappings tab of session properties. Select a relational connection object for the IDM_Dictionary connection.

IDM_24068 The dictionary <dictionary name> is unavailable in the $PMLookupFileDir.

Explanation:
The Data Masking transformation is configured for substitution masking. The flat file dictionary that provides the substitute data is unavailable in the lookup file directory.
User Response:
Verify that the flat file dictionary is in the lookup files directory. By default, the directory is <PowerCenter_Installation_Directory>\server\infa_shared\LkpFiles.

IDM_26001 Invalid credit card number length: <number>.

User Response:
Verify that the source credit card number is between 13 and 19 digits.

IDM_26002 Could not mask credit card number: <number>.

User Response:
Verify that the source credit card number is valid. The number must be between 13 and 19 digits. The number can have the following characters: 0-9, spaces, and hyphens.

IDM_26003 Failed to remove delimiter from credit card number: <number>.

Explanation:
The Data Masking transformation did not apply a mask to a credit card number.
User Response:
Verify that the source credit card number is valid. The number may contain hyphens or spaces in the wrong location in the number.

IDM_26004 Bounds and blurring do not generate valid range of values for <source>.

Explanation:
The Data Masking transformation cannot apply a mask to a source column. The range masking rule and blurring masking rule combination restricts the Data Masking transformation from generating mask values.
User Response:
Change the range masking rule to a range of values that fall within the blurring range.

IDM_26005 Invalid source date.

Explanation:
The Data Masking transformation could not apply a mask to a source date because the date format is invalid.
User Response:
Verify that the date is in a format that is defined by the session configuration object. Check the DateTime Format String attribute on the Config Object tab for a session or session configuration object. By default, the date format is MM/DD/YYYY HH24:MI:SS.US.

IDM_26006 Invalid input IP address: <IP address>.

User Response:
Verify that the source IP address is four numbers, separated by a period.

IDM_26007 Invalid input SSN Format: <SSN >.

User Response:
Verify that the SSN has 11 characters.The SSN contains three sections: an area code, group number, and serial number. The sections are separated by hyphens. The Data Masking transformation returns a Social Security Number with the same format and area code as the source.

IDM_26008 Invalid input URL Format: <URL >.

User Response:
Verify that the source URL contains the ‘://’ string. The Data Masking transformation parses a URL by searching for the ‘://’ string and parsing the substring to the right of it. Verify that the URL contains numbers or alphabetic characters.

IDM_26009 License for Data Masking transformation has not been enabled.

Explanation:
The Data Masking option is not licensed to run on this machine.
User Response:
Verify you have the Data Masking incremental license file. Add the incremental license to an existing license in the Administrator tool. You can view license details using the Administrator tool or the infacmd ShowLicense command. If you do not have a license for Data Masking, contact Informatica Global Customer Support.

IDM_26010 Invalid input email: <email>.

Explanation:
The Data Masking transformation could not apply a mask to an email address because the address format is invalid.
User Response:
Verify that the email address contains the user name of the recipient, the @ sign, and the host name.

IDM_26011 Invalid input phone: <phone number>.

Explanation:
The Data Masking transformation could not apply a mask to a phone number because the source phone number is invalid.
User Response:
The Data Masking transformation masks a phone number without changing the format of the original phone number. Verify that the source number contains only the following characters: 0–9, spaces, hyphens, and parentheses. The Integration Service does not mask alphabetic or special characters.