Question: What is Immutable rowid_object?

rowid_object from this source will remain same after match and merging with other data. Record can merge for this record with others but rowid_object will never change after merge; Other records can merge with this record.

Question: What is Distinct Source?

Data from that system gets inserted into BO without being consolidated.

Question: What is CMX_SYSTEM in informatica MDM?

CMX_SYSTEM is called master ORS in informatica MDM, this will all metadata/ infrastructures tables details of informatica MDM installation, this is must for proceeding with installation of MDM, without this we cannot complete informatica MDM installation.

we need to first create using SIP_ANT.BAT create_system (this will create cmx_system), then need to import required metadata table (SIP_ANT.BAT import_system).

Question: What is user exit in informatica MDM?

With the help of MDM HUB USER EXIT we can extend the functionalities of MDM Hub, if you want to add some actions which are not available in MDM HUB, you can add that with the help of MDM HUB user exits.

Types of users Exits in MDM HUB.

1. PostLandingUserExit:

It will be called once you are loading data through ETL or

Before running Stage Job.

The Post Landing user exit is called within the stage process to manipulate data in the 

landing table before the actual stage process starts.

processUserExit: Entry point from the hub to the custom user exit code. 

void processUserExit (UserExitContext userExitContext,

String stagingTableName,

String landingTableName,

String previousLandingTableName)

throws Exception

Entry point from the hub to the custom user exit code. This method is called once from the hub during the stage process.

Parameters:

userExitContext - User exit context that is passed from the hub

stagingTableName - Name of the staging table used in the stage process

landingTableName - Name of the landing table used in the stage process

previousLandingTableName - Name of the previous landing table used in the stage process

Throws:

Exception

2. PreStageUserExit:

The PreStage user exit is called as part of the stage job before the hub loads 

the data into the staging table. This is called once before the stage process starts.

3. PostStageUserExit:

The Post Stage user exit is called as part of the stage process. 

It is called once after the stage processing is completed.

4. PostLoadUserExit:

The Post Load user exit is used in both the load job and the Put SIF api. 

For the batch load, this is called at the end of processing for each block,

After sending changes to the DB and before commit. In case of the Put API,

it’s called at the end of processing for that record.

in the batch load. The data is committed after all records in the block have been processed.

5. PreMatchUserExit:

The PreMatch user exit is called as part of the match process. 

It is called once after the match job is registered and before the match process starts.

 The user exit processing is part of the match transaction. 

Any failure within the user exit will result in a rollback.

6. PostMatchUserExit:

The Post Match user exit is called as part of the match process. 

It is called once after the match processing is completed. 

The user exit processing is part of the match transaction.

Any failure within the user exit will result in a rollback.

After merge process, data from MTCH table will be deleted.

we can maintain history of MTCH data using this User exit.

7. PostMergeUserExit:

The Post Merge user exit is called at the end of the merge process. The user exit processing is part of the transaction. Any failure within the user exit will result in a rollback.

After merge process, data from MTCH table will be deleted.

we can maintain history of MTCH data using this User exit.

8. PostUnmergeUserExit:

The Post Unmerge user exit is called as part of the unmerge process. 

It is called once after the unmerge processing is complete. The user

exit processing is part of the unmerge transaction. 

Any failure within will result in a rollback.

9. PreUserMergeAssigmentUserExit:

Called before just record to be Merged and are assigned to user.

Question: What are the different ways to acquire Locks in Informatica MDM?

Below mentioned are the two types of locks used in Informatica MDM 10.1:

Exclusive Lock:  Exclusive locks allow individual users to access and modify the underlying metadata.

Write Lock: A write lock allows different users to simultaneously access and modify the underlying metadata. 

Question: What are the tools that require Lock in Informatica Master Data Management?

Following are tools that require Lock in Informatica Master Data Management

Message Queues

Users

Databases

Tool Access

Security Providers

Repository Manager

Click here, for more Informatica MDM interview Question and Answer