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.4 HotFix 2
  • All Products

Table of Contents

Search

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

Installation Guide for IBM Db2 with Red Hat JBoss

Installation Guide for IBM Db2 with Red Hat JBoss

Back Next

Troubleshooting the Installation Process

Troubleshooting the Installation Process

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

Cannot launch the Hub Console

After installation, the Hub Console fails to launch and generates the following error in the log file: 
SIP-09131: General Decryption failure and [ERROR] com.delos.util.StringUtil: Unable to decrypt
Encrypt and update the MDM Hub Master Database password or Operational Reference Store password.
  1. To encrypt a database schema password, run the following command from a command prompt: 
    java -classpath siperian-api.jar;siperian-common.jar;siperian-server.jar com.delos.util.PublicKeyBasedEncryptionHelper <plain text password> <Hub Server
installation directory>
    The results are echoed to the terminal window.
  2. To update your Master Database password or Operational Reference Store password, connect as the
    cmx_system
     user and run the following statement: 
    UPDATE C_REPOS_DATABASE SET PASSWORD = '<new_password>' WHERE USER_NAME =
<user_name>;
COMMIT;
  3. Run the
    postInstallSetup
     script.

Hub Server EAR file deployment fails with
concurrent.RejectedExecutionException

The Hub Server EAR file deployment might fail with the exception
concurrent.RejectedExecutionException
.
To resolve the issue, increase the length of the task queue in the
standalone-full.xml
 file.
The following sample shows the
queue-length count
 parameter to modify: 
<long-running-threads>
  <core-threads count="50"/>
  
<queue-length count="300"/>

  <max-threads count="50"/>
  <keepalive-time time="10" unit="seconds"/>
</long-running-threads>

Cannot start JBoss or launch the Hub Console after installation

After installation, JBoss might not restart after you stop JBoss. When you launch the Hub Console, the Hub Console fails to launch and generates the following error: 
SIP-09070: Failed to initialize repository layer.
To resolve the issue, run the following code in a batch file to restart JBoss: 
rmdir C:\<JBoss installation directory>\standalone\tmp /s /q 
\mkdir C:\<JBoss installation directory>\standalone\tmp 
C:\<JBoss installation directory>\bin\standalone.bat -c standalone-full.xml -b 0.0.0.0

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

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

Operational Reference Store registration fails because the connection times out

When you register the Operational Reference Store (ORS) in a JBoss cluster node, the ORS registration fails with a connection timeout error similar to the following: 
SIP-10313: SIP-09061: Failed connecting with provider url abc03.
java.net.ConnectException: JBAS012144: Could not connect to remote://abc03:9999. The connection timed out.
To resolve the issue, when you register an ORS, disable the JBoss administrative security, and then enable the JBoss administrative security after ORS registration.

Hub Server deployment fails because JBoss composite operation fails

When you deploy the Hub Server in the JBoss application server, the Hub Server deployment fails with the following error: 
JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {
			"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./cmx" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./cmx:
			org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"
To resolve the issue, perform the following steps:
  1. Stop the JBoss application server.
  2. Use a text editor to open the
    standalone.xml
     file in the following directory:
    On UNIX.
    <JBoss Installation Directory>/standalone/configuration
    On Windows.
    <JBoss Installation Directory>\standalone\configuration
  3. Find the following code: 
    <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
        <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
</subsystem>
  4. Add the
    deployment-timeout="300"
     attribute as shown in the following sample code: 
    <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
        <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" 
    deployment-timeout="300"
    />
</subsystem>
  5. Save changes, and start the JBoss application server.
    The default deployment timeout value is
    60
    , which is changed to
    300
    .
  6. Deploy the Hub Server.

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.
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
    • Suse or RedHat Linux.
      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.

Java XA Exception

When you restart JBoss after you have installed the Hub Server, the following exception might appear: 
WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException
at oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:730)
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.recover(XAResourceWrapperImpl.java:185)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:597)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:194)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:140)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377)
The exception occurs if you run the
sip_ant
 script and do not have access to the Oracle database SYS account. The script performs grants on the Oracle system tables that require the SYS user account privilege. Without access to the SYS account, you cannot set up the
cmx_system
 or
cmx_ors
 schema.
You can create a privileged account associated with the DBA role. The DBA user can perform the grant statements manually, outside of the
sip_ant
 script. Alternatively, to avoid the XA exception error in the log, grant the SELECT and EXECUTE privileges to the
cmx_system
 and
cmx_ors
users: 
GRANT EXECUTE ON sys.dbms_lock TO <DBA user> with grant option;
When you run the
sip_ant
 script to create the MDM Hub Master Database (
cmx_system
) or an Operational Reference Store (
cmx_ors
), the following error might appear: 
[exec] GRANT SELECT ON SYS.PENDING_TRANS$ TO cmx_system
[exec] DBA user should have grantable privilege for PENDING_TRANS$
[exec] ERROR CODE: -1031
[exec] DECLARE
[exec] *
[exec] ERROR at line 1:
[exec] ORA-01031: insufficient privileges
[exec] ORA-06512: at line 24
[exec] ORA-06512: at line 27
Grant the required privileges to the SYS user, so that the user can run the
create_system
 and
create_ors ant
as targets: 
GRANT SELECT ON sys.pending_trans$ TO <DBA user> with grant option;
GRANT SELECT ON sys.dba_pending_transactions TO <DBA user> with grant option;
GRANT SELECT ON sys.dba_2pc_pending TO <DBA user> with grant option;
GRANT EXECUTE ON sys.dbms_xa TO <DBA user> with grant option;

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. Navigate to the bin directory under the JBoss root directory.
  2. Open the following file in a text editor.
    On UNIX.
    run.sh
    On Windows.
    run.bat
  3. Set the JAVA_OPTS variable as follows: 
    JAVA_OPTS=${JAVA_OPTS} -Xss2000k
  4. Save and close the file.

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.

After you deploy the Process Server .ear files, an error occurs

On a Linux environment with WebSphere 8.5.5.9, after you deploy the
Process Server
, the following error occurs: 
Too many open files. Unable to start cleanse ear.
Increase the value of the
ulimit
 parameter in Linux, and deploy the
Process Server
.

Cannot add the application users using the sip_ant script

The following applications are affected: Business Process Manager (formerly known as ActiveVOS), Data Director, MDM Hub Console and Provisioning Tool.
To add the application users, run the
sip_ant
command, using the
add_app_users
 parameter.
You can fetch the connect URL from the following location:
hub/server/bin/build.properties (masterdatabase.jdbc.url)
)
Run the following command:
  • On Windows. 
    sip_ant.bat add_app_users -Ddatabase.password=<cmx system password> -Dmaster.​connecturl="jdbc:oracle:thin:@<Database Host name>:<DB Port>:<SID>" -Dmaster.username=cmx_system​
  • On Unix. 
    ./sip_ant.sh add_app_users -Ddatabase.password=<cmx system password> -Dmaster.​connecturl="jdbc:oracle:thin:@//<Database Host name>:<DB Port>:<SID>" -Dmaster.username=cmx_system​​
Run the following command on the SQL Server: 
./sip_ant​.sh add_app_users -Ddatabase.password=<cmx system password> -Dmaster.connecturl="jdbc:sqlserver://<Database Host Name>:<DB Port>;DatabaseName=cmx_system" -Dmaster.username=cmx_system
​

The Certificates folder is not created

The Certificates folder is not created as expected, after you back up the existing Certificates folder from
\infamdm\hub\server\resources\
, and run the
sip_ant.sh hash_users_passwords
 script. ​​This issue occurs when the
sip_ant.sh hash_users_passwords
 script updates the C_REPOS_USER table in
cmx_system
.
To resolve this issue, restart the application server. As a result, the Certificates folder is created in the expected location:
\infamdm\hub\server\resources\
.
The folder will contain only the
MDM_KEYSTORE_FILE_JKS
 keystore.
To generate other certificates, run the following command: 
./sip_ant.sh add_app_users
0 COMMENTS
We’d like to hear from you!