Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Store Post-Installation Tasks
  6. Hub Server Installation
  7. Hub Server Post-Installation Tasks
  8. Process Server Installation
  9. Process Server Post-Installation Tasks
  10. ActiveVOS Post-Installation Tasks for the Application Server
  11. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  12. Resource Kit Installation
  13. Resource Kit Post-Installation Tasks
  14. Troubleshooting the MDM Hub
  15. Uninstallation

Installation Guide for Oracle Database with IBM WebSphere

Installation Guide for Oracle Database with IBM WebSphere

Back Next

Troubleshooting the Installation Process

Troubleshooting the Installation Process

If the installation fails, use the following information to troubleshoot the failure.

You did not install the application server profile in the default directory

If you did not install the application server profile in the default directory, the postInstallSetup script fails to deploy the Hub Server and
Process Server
 applications to the application server.
Use the following default directory:
On UNIX.
<
Websphere_install_home
>/profiles
On Windows.
<
Websphere_install_home
>\profiles
To resolve the issue, repackage the Hub Server and Cleanse Match Server EAR files and then manually deploy the Hub Server and Cleanse Match Server applications to the custom directory where you installed the application server.

PostInstallSetUp script fails as the directory contains the siperian-mrm.ear file

If you try to deploy the Hub Server application to a directory that contains a file with the name siperian-mrm.ear, the following error appears: 
[wsadmin] ADMA5016I: Installation of siperian-mrm.ear started.

 [wsadmin] A composition unit with name siperian-mrm.ear already exists. Select a different application name.
To resolve the issue, remove all the directories that contain a
siperian-mrm.ear
 file, and then run postInstallSetup again to deploy the EAR file.
If you undeploy the Hub Server application, a
siperian-mrm.ear
 file might still exist in an application server directory.

PostInstallSetUp script fails because the socket times out

When you install the Hub Server in a WebSphere environment, the post-installation setup process fails, and the following error appears: 
[wsadmin] Saving configuration ... 
  [wsadmin] WASX7017E: Exception received while running file "wsinstall.jacl"; exception information: com.ibm.websphere.management.exception.ConfigServiceException 
  [wsadmin] com.ibm.websphere.management.exception.ConnectorException 
  [wsadmin] org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out] 
  [wsadmin] WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
To resolve the issue, restart WebSphere and start the Hub Console.

MDM Hub users cannot login

If you re-create the CMX_SYSTEM schema after installation of the Hub Server, the MDM Hub cannot recognize the hashed passwords. As a result, users cannot log in to the MDM Hub.
To resolve the issue, run the
postInstallSetup
 script again manually. This script ensures that the passwords of the MDM Hub users are hashed again and users can log in.
Alternatively, if you do not want to run the
postInstallSetup
 script again, run the following commands to migrate the user passwords to hashed passwords and create application users.
On UNIX. 
cd <
MDM Hub installation directory
>/server/bin
./sip_ant.sh hash_users_passwords
./sip_ant.sh add_application_users
On Windows. 
cd <
MDM Hub installation directory
>\server\bin
sip_ant.bat hash_users_passwords
sip_ant.bat add_application_users
In a WebSphere environment, the MDM Hub user must have access and write permissions for the following directory: 
<
MDM Hub installation directory
>/server/bin/resources/certificates

WebLogic instance redirects to Data Director

If you install MDM Hub on a WebLogic port other than 7001, the instance is redirected to Data Director with the following error: 
javax.faces.application.ViewExpiredException: viewId:/config/config_login.jsf - View /config/config_login.jsf could not be restored.
To resolve the issue, set to the host name and the IP address of the WebLogic host. Do not use localhost.

PostInstallSetUp script fails because the ActiveVOS server deployment times out

When you install the Hub Server, the post-installation setup process might fail after trying to deploy the ActiveVOS server.
To resolve the issue, increase the value of the
deploy.wait.time
 property in the
build.properties
 file in the following directory:
On UNIX.
<infamdm installation directory>/hub/server/bin
On Windows.
<infamdm installation directory>\hub\server\bin

Inaccurate start or stop timestamp for Operational Reference Store

When you export an Operational Reference Store that you create, the MDM Hub creates a .dmp file. You can reuse the .dmp file of the Operational Reference Store to create a second Operational Reference Store. The start date and end date columns in the C_REPOS_DB_VERSION table of the Operational Reference Store will contain incorrect start date and end date. You can ignore this error as it does not affect any functionality.

The Hub Server cannot connect to the cmx_system schema

To verify that the Hub Server cannot connect to the cmx_system schema, review the application server log.
For example, you might find the following error, which confirms that the database is not accessible: 
Caused by: java.sql.SQLException: ORA-28000: the account is locked 
DSRA0010E: SQL State = 99999, Error Code = 28,000
To resolve the issue, resolve the database connection issue. Use the application server console to test the connection to the database. If you cannot resolve the connection to the cmx_system schema, re-create the cmx_system schema.

Failed to verify the need to tokenize records

When you run the Match process, you might receive the following error: 
SIP-16062: Failed to verify the need to tokenize records.
Verify the following environment variable settings:
  • The library path environment variable must contain the following path:
    On UNIX.
    <
    infamdm_install_directory
    >/hub/cleanse/lib
    On Windows.
    <
    infamdm_install_directory
    >\hub\cleanse\lib
    The library path environment variable depends on the operating system:
    • AIX.
      LIBPATH
    • HP-UX.
      SHLIB_PATH
    • Solaris, Suse, or RedHat.
      LD_LIBRARY_PATH
    • Windows.
      PATH
  • The
    SSAPR
     environment variable must include the following path for all users:
    On UNIX.
    <
    infamdm_install_directory
    >/server_install_dir>/cleanse/resources
    On Windows.
    <
    infamdm_install_directory
    >\server_install_dir>\cleanse\resources

major.minor version errors when loading the Process Server

If you see multiple
major.minor
 console errors when you try to load the
Process Server
, check that the system has the correct Java version installed.

CORBA TRANSACTION_ROLLEDBACK exception

When you use the Data Manager or the Merge Manager, the MDM Hub might generate the
CORBA TRANSACTION_ROLLEDBACK
 exception. If the exception is generated, open the WebSphere Administrative console to manually set the
-Djava.vendor=IBM
 Java option in the WebSphere process definitions.

Informatica Address Verification
 exception during certification

Informatica Address Verification
 generates an exception during certification. Ensure that the stack size for the JVM is sufficient.
  1. Open the WebSphere Console.
  2. Go to
    Servers
    Application Server
    <
    Your Server
    >
    Process Definition
    Java Virtual Machine
    .
  3. Add the following arguments to the generic JVM arguments: 
    -Xss2000k - Initializes the stack size to 2000k
-Xms128m - Initializes the heap with at least 128 MB
-Xmx1024m - Initializes the heap with a maximum of 1024 MB
  4. Save the configuration.
  5. Restart the WebSphere server.

Operational Reference Store does not have a workflow engine configured

If you install the
MDM Hub
 and then import an
Operational Reference Store
 (ORS) from a previous version, you see a fatal error that indicates that the ORS does not have a workflow engine configured. This error occurs because the Siperian BPM workflow engine is not registered by default. Use the Workflow Manager to register the Siperian BPM workflow engine with the name that the ORS expects to find.
0 COMMENTS
We’d like to hear from you!