Explanation: | An internal error occurred. |
System Action: | Processing ends. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The createdatamaps utility found a syntax or other error in the XML control file. |
System Action: | Processing ends. |
User Response: | Correct the error in the control file and run the command again. |
Explanation: | A syntax or other error was found in the XML control file. |
User Response: | Correct the error in the XML control file. |
Explanation: | An error was encountered in the connection definition. |
System Action: | Processing ends. |
User Response: | Verify that the node name, user ID, password, and other connection settings are configured correctly. |
Explanation: | An error occurred when retrieving metadata for the specified record. For example, a copybook file name or path might be incorrect. |
System Action: | Processing ends. |
User Response: | Check the XML control file for possible errors. |
Explanation: | The environment variable is missing or has an invalid value. |
System Action: | Processing ends. |
User Response: | Define or correct the environment variable. |
Explanation: | The createdatamaps utility was unable to find the control file. |
System Action: | Processing ends. |
User Response: | Run the command again with the correct the file name and path of the control file. |
Explanation: | An error was encountered in the connection definition. |
System Action: | Processing ends. |
User Response: | Verify that the node name, user ID, password, and other connection settings are configured correctly. |
Explanation: | An I/O error occurred writing to the data map file. For example, the data map output directory might be invalid. |
System Action: | Processing ends. |
User Response: | Verify that the data map file path and name are specified correctly. |
Explanation: | An error occurred during data map generation. |
System Action: | Processing ends. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The control file does not specify a copybook. |
User Response: | Processing ends. |
User Response: | Check the control file to ensure that a copybook is specified correctly. |
Explanation: | An invalid code page ID is specified in the control file. |
System Action: | Processing ends. |
User Response: | Correct the code page in the control file. |
Explanation: | An error occurred while the createdatamaps utility was building the specified data map. |
User Response: | Check the accompanying error messages and then correct the reported problems. |
Explanation: | The createdatamaps utility was unable to read an integer value in the specified field in a data record. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | A data file name was not specified in the control file for the specified data map. The control file must specify a valid data file name to identify the record ID fields. |
User Response: | Specify a valid data file name in the control file. |
Explanation: | The specified cache path is not valid. |
User Response: | Edit the control file to specify a valid cache path and run the createdatamaps utility again. |
Explanation: | The createdatamaps utlity was unable to load the JCS library. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | A failure occurred when the createdatamaps utility tried to clear the disk cache. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | A failure occurred when the createdatamaps utility tried to write the file properties object to the cache. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | A failure occurred when the createdatamaps utility tried to add the record to the cache. |
User Response: | Contact Informatica Global Customer Support. |