Known Limitations

Known Limitations

The following table describes the known limitations:
Reference Number
Description
TCR-3034
In Linux and WebLogic environments, when you run the
install-tcr.sh
script, the install script fails with the following error:
Buildfile: linux/build_wl.xml does not exist
Workaround: Perform the following tasks:
  1. Open the
    setup_app_wl.sh
    file in the following directory:
    <MDM Hub installation directory>/app/tcr/bin
  2. Update the absolute path of the
    build_wl.xml
    file for
    $WLS_CLASSPATH
    .
    For example, the following sample shows the absolute path of the
    build_wl.xml
    file as
    $TCR_HOME/bin/linux/
    :
    $WLS_CLASSPATH \
    org.apache.tools.ant.Main -f $TCR_HOME/bin/linux/build_wl.xml $DEF_COMMAND \
  3. Save the file.
TCR-3033
When you configure the Task Manager in the Provisioning tool, you cannot configure the action message to show when you perform an action.
TCR-3020
In IBM DB2 or Microsoft SQL Server environments, you cannot migrate to the data model based on the Party table from the data model based on the Party Role table.
TCR-3019
In IBM DB2 and JBoss environments, the dashboard view of a record might display the following error message in the Hierarchies panel:
Internal error. Cannot load the hierarchy.
Workaround: Perform the following tasks:
  1. Open the following file:
    <JBoss installation directory>/standalone/configuration/standalone-full.xml
  2. Add the following attribute to the
    xa-datasource
    section of the
    Customer 360
    Operational Reference Store:
    <xa-datasource-property name="AllowNextOnExhaustedResultSet">1</xa-datasource-property>
  3. Save the file, and restart the application server.
TCR-3014
When you use the Java project that is included in the
Customer 360
installation files to extend the user exit, the Java project fails when you compile it.
Workaround: Before you compile the project, perform the following tasks:
  1. Run the following commands:
    mvn install:install-file -Dfile=<MDM Hub installation directory>\hub\server\lib\mdm-ue.jar -DgroupId=com.informatica.mdm -DartifactId=mdm-ue -Dversion=10.3.0-SNAPSHOT -Dpackaging=jar
    mvn install:install-file -Dfile=<MDM Hub installation directory>\hub\server\lib\siperian-api.jar -DgroupId=com.informatica.mdm -DartifactId=siperian-api -Dversion=10.3.0-SNAPSHOT -Dpackaging=jar
    mvn install:install-file -Dfile=<MDM Hub installation directory>\hub\server\lib\siperian-common.jar -DgroupId=com.informatica.mdm -DartifactId=siperian-common -Dversion=10.3.0-SNAPSHOT -Dpackaging=jar
  2. Comment the following code in the Java project:
    <repository> <id>infamdm.external</id> <url>http://mdmmaven01.informatica.com:8081/nexus/content/repositories/thirdparty/</url> </repository> <repository> <id>mdmcentral</id> <name>MDM Proxy Repository</name> <url>http://mdmmaven01.informatica.com:8081/nexus/content/repositories/mdminfa/</url> </repository>
TCR-3012
In IBM DB2 environments, when you run the
lookup_localization
script, the script imports the lookup data in all the languages except the Russian language. The script fails with the following error message:
com.informatica.solutions.lookup.localisation.exception.LookupLocalisationException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.19.26
TCR-2980
After you update an active record, the dashboard view of the record shows the updated values even though the changes are not approved.
TCR-2966
In environments that use the data model based on the Party Role table, when you add a relationship between two Person records, an empty Related Person record is created for one of the records.
TCR-2938
In WebLogic environments, after you install or upgrade
Customer 360
, if you try to install or upgrade
Customer 360
again, you get the following error message:
[wldeploy] Target state: deploy failed on Server AdminServer [wldeploy] javax.naming.NameNotFoundException: Unable to resolve 'jdbc.ActiveVOS'. Resolved 'jdbc'; remaining name 'ActiveVOS'
When you run the install or upgrade script again, the data source defined in WebLogic for the ActiveVOS database is deleted.
Workaround: Manually create the data source in WebLogic.
To create a data source in WebLogic, perform the following tasks:
  1. On the WebLogic Administration Console, click
    Services
    Data Sources
    .
  2. Click
    New
    , and select
    Generic Data Source
    .
    The
    JDBC Data Source Properties
    page appears.
  3. Specify the following properties for the data source:
    • Name
      . Name for the data source.
    • JNDI Name
      . JNDI path to where the JDBC data source will be bound. Specify
      jdbc/ActiveVOS
      .
    • Database Type
      . Database type that you want to connect.
  4. Click
    Next
    .
  5. Select the database driver to connect to the database, and then click
    Next
    .
    The
    Transaction Options
    page appears.
  6. Click
    Next
    .
    The
    Connection Properties
    page appears.
  7. Specify the following connection properties:
    • Database Name
      . Name of the ActiveVOS database you want to connect.
    • Host Name
      .
      DNS name or IP address of the server that hosts the database.
    • Port
      .
      Port on which the database server listens for connection requests.
    • Database User Name
      .
      Database user name that you want to use for each connection in the data source.
    • Password
      .
      Password of the database user account.
    • Confirm Password
      .
      Password of the database user account.
  8. Click
    Next
    .
    The
    Test Database Connection
    page appears.
  9. To test the database connection, click
    Test Configuration
    .
  10. After successfully testing the database connection, click
    Next
    , and then select the server on which you want to deploy the data source.
  11. Click
    Finish
    , and then click
    Activate Changes
    .
TCR-2930
In a localized environment, when you open a record, the hierarchy name is not localized in the Hierarchy panel.
TCR-2005
If you update a verified email address, phone number, or address, the status of the email address, phone number, or address does not change to reflect the status of the updated value.
TCR-1908
On the
Home
page, when you sort the tasks based on priority, the tasks are incorrectly sorted.
TCR-1899
When you edit a record, if you update an address child record, you cannot save the changes and get the following error message:
SIP-50112: Could not run the WriteCO business entity service.
TCR-1647
In WebSphere environments, Customer 360 integration with Product 360 does not work.
TCR-1527
During a file import, if you configure the header row to a value other than 1, Customer 360 shows an incorrect preview of your imported file.
TCR-1358
In a hierarchy, if you add a relationship from a B2C customer to a B2B customer, Customer 360 does not display the change history.
TCR-1297
Customer 360 does not support the TIFF image format in the Product Details widget.
TCR-1169
For the Organization customer type, when you edit a relationship or classification to add additional relationship attributes, Customer 360 does not save the attributes that you add.
TCR-1112
The data mart service does not support the Microsoft SQL Server database.

0 COMMENTS

We’d like to hear from you!