Table of Contents

Search

  1. Abstract
  2. Installation and Upgrade
  3. 10.2 HF1 Fixed Limitations and Closed Enhancements
  4. 10.2 HF1 Known Limitations
  5. 10.2 Fixed Limitations and Closed Enhancements
  6. 10.2 Known Limitations
  7. Emergency Bug Fixes Merged into 10.2
  8. Informatica Global Customer Support

Application Services Fixed Limitations (10.2)

Application Services Fixed Limitations (10.2)

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
Bug
Description
PLAT-18192
The Model Repository Service upgrade from version 9.6.1 to version 10.1.1 HotFix 1 fails when the Model repository has logical data objects that contain deleted mappings or objects.
PLAT-18116
A
Data Transport Error
error appears when you run the scorecards in version 10.1.
PLAT-17986
When you recycle the Data Integration Service, all logical data objects that are enabled for caching are cached again, even if the cache from the previous run is still available.
PLAT-16944
Some Data Integration Service threads use the default naming convention instead of a descriptive name.
PLAT-16542
After you upgrade the Model Repository Service from version 9.5.1 HotFix 4 to version 10.1, when you create a schedule for profile run or scorecard run, the schedule wizard does not display the profile names or scorecard names in the Model repository.
PLAT-16188
In the Administrator tool, the running Data Integration Service jobs do not appear on the Monitoring tab when the monitoring Model Repository Service has restarted or is not available.
PLAT-16154
Sometimes, the content upgrade for Model Repository Service fails when you upgrade from version 9.6.1 HotFix 3 to version 10.1.1.
PLAT-15910
Sometimes, the infacmd isp purgeMonitoringData command does not purge all the tables in the Model repository.
PLAT-14508
The Model Repository Service upgrade fails with the error
Any getter or setter method cannot be accessed on a proxy object
if any mapping in the Model repository contains deleted objects.
PLAT-14202
After you create and assign a monitoring Model repository, you cannot disable or remove the associated Model Repository Service in the Administrator tool.
PLAT-12070
If you run multiple concurrent mappings on a Data Integration Service grid configured to run jobs in separate remote processes and the Model repository is not configured to store run-time statistics, some of the mappings might fail to run with the following error:
[ICMD_10033] Command [runmapping] failed with error [com.informatica.ds.ms.service.MonitorHelper.purgeStatistics(MonitorHelper.java:125)
(441281)
MRS-1344
After you upgrade the Model Repository Service from version 9.6.1 HotFix 3 to version 10.1.1 HotFix 1, you cannot use backup or restore operations.
MRS-1340
The login session for the Model repository is valid only for half an hour and you are logged off even when the session is active.
MRS-1333
In the Developer tool, the
Assign Tags for Object
dialog box takes more than 90 seconds to appear when you open a mapping in the editor and click
Edit
in the Tags view.
MRS-1289
When you upgrade the Model Repository Service from version 9.6.1 HotFix 1 to version 10.1, the upgrade takes more than 3 hours to complete.
MRS-1282
When you run the infacmd mrs PopulateVCS command, synchronization fails if the Subversion version control system repository contains subfolders.
MRS-1266
When you upgrade from version 9.6.1 to version 10.0, the Model Repository Service upgrade shuts down unexpectedly during Model repository content upgrade.
MRS-1235
Sometimes, when you upgrade from version 9.6.1 HotFix 2 to version 10.1, the StackOverflowError error appears during Model repository contents upgrade.
MRS-1225
A syntax error appears when you run the infacmd xrf generateReadableViewXML command in version 10.1.
MRS-1223
Unable to import a mapping that exceeds 255 characters into the Model repository when the repository is IBM DB2 database.
MRS-1194
Sometimes, the error
SQL command not properly ended
appears when you restore the Model Repository Service.
MRS-1191
When you configure the Model Repository Service for version control, the error
unknown protocol: svn
appears if the Subversion version control system is in daemon mode.


Updated June 29, 2020