DronaBlog

Friday, November 13, 2020

Informatica MDM - How to fix an error - ORA-01555: snapshot too old?

While working on Informatica MDM jobs, I came across one issue. The issue is an ORA-01555: snapshot too old. This error message was reported while running the tokenization job. If you are also noticing a similar issue then this article will help. This article provides details about an error message and a solution to fix it.






Error Message:

The detailed error message is as below -

java.sql.BatchUpdateException: ORA-01555: snapshot too old: rollback segment number 11 with name "_SYSSMU11_2399779032$" too small

SIP-16084: Error occurred while verifying the need to tokenize records. Return code 12801, 

Error SQLException During VerifyNeedToStrip :ORA-12801: error signaled in parallel query server P000,
ORA-01555: snapshot too old: rollback segment number 30 with name "_SYSSMU30_2998435469$" too small.
 at com.siperian.common.SipRuntimeException.createNotExternalized(SipRuntimeException.java:74)
 at com.delos.cmx.server.interact.caller.InteractCleanseClient.executeGenerateMatchTokens(InteractCleanseClient.java:460)


Solution:

To fix the issue perform the steps below -

A. Database Issue
First, analyze if there is any database issue going on. If the database looks good then perform the steps below

Step 1: Stop any job running as 'INCOMPLETE'
Step 2: Stop the Application server
Step 3: Verify undo_retention value by running the query below on db side
           
             show parameter undo_retention;

Step 4: If the value is lower then increase the value to 4000 by executing the command below

            ALTER SYSTEM SET UNDO_RETENTION = 4000;

Step 5: Increase Undo Tablespace to Auto Extended on.

Step 6: Restart the database servers with the clear cache

Step 7: Drop T$ table if present any in database

Step 8: Start the MDM servers with a clear cache.






This will fix the issue. I hope this is helpful. You can learn more about job tuning here -





Wednesday, November 11, 2020

How to fix Error - SIP-52054: Failed to create collection name for orsId


Are you looking for how to fix an error : SIP-52054: Failed to create collection name for orsId  in the MDM hub? Are also interested in knowing what is the root cause of this error? If so, then you reached the right place. In this article, we will focus on Elastic Search error in Informatica Master Data Management (MDM).






Error Message:

If you are running any soap request against Business Entity services which internally uses Elastic Search then may encounter an error below :

SIP-52054: Failed to create collection name for orsId


Detailed Error stack:


[ERROR] com.informatica.mdm.cs.server.CompositeServiceInvoker: SIP-52054: Failed to create collection name for orsId [mdmsbx-CMX_ORS] because of error: Connection refused.
com.informatica.mdm.spi.cs.StepException: SIP-52054: Failed to create collection name for orsId [CMX_ORS] because of error: Connection refused.
 at com.informatica.mdm.cs.steps.SearchCO.invoke(SearchCO.java:337)
 at com.informatica.mdm.cs.server.CompositeServiceInvoker.executeStep(CompositeServiceInvoker.java:426)
 at com.informatica.mdm.cs.server.CompositeServiceInvoker.processService(CompositeServiceInvoker.java:308)
 at com.informatica.mdm.cs.server.CompositeServiceInvoker.executeService(CompositeServiceInvoker.java:385)
 at com.informatica.mdm.cs.server.CompositeServiceInvoker.processService(CompositeServiceInvoker.java:312)
 at com.informatica.mdm.cs.server.CompositeServiceInvoker.process(CompositeServiceInvoker.java:187)
 at com.informatica.mdm.cs.server.CompositeServiceInvoker.invoke(CompositeServiceInvoker.java:118)
 at com.informatica.mdm.cs.server.ejb.CompositeServiceEjbBean.doProcess(CompositeServiceEjbBean.java:53)
 at com.informatica.mdm.cs.server.ejb.CompositeServiceEjbBean.process(CompositeServiceEjbBean.java:37)


How to fix this issue?

In order to fix this issue, perform the steps below -

1. Verify the MDM hub is accessible. Also, verify the connection to the process server from MDM hub -> Utilities -> Process Server

2. Verify Elastic Search server is working fine

3. If the above two steps look good then make sure the Elastic Search is properly configured in the Provisioning tool.

The location is : Provisioning Tool -> Configuration -> Infrastructure Settings  -> ESCluster

Here make sure the server name is properly configured for Elastic Search






Root cause:

The error 'SIP-52054: Failed to create collection name for orsId ' normally occurs when the Elastic Search server tries to make a connection to the MDM hub. If there is a mismatch in server ion in the Provisioning tool then we get this error.


Learn more about the provisioning tool here -



What are differences between multimerge and merge API in Informatica MDM

                Are you interested in knowing what is the use of multimerge and merge APIs? Are you also would like to know the difference b...