What are the log Files in Informatica MDM ?

        Are you trying to analyze the issue in Informatica MDM? Are you looking for the details of the log files which are generated during various Processes in the Informatica MDM? This article will explore more about the log files, their locations, and when to use those.

A) Introduction

         Informatica MDM has various components such as application server, database, business process management tool, Application user interface such as Entity 360 or customer 360. Each of these components generates logs throughout its processing.

         Here we will understand various types of log files and these are

         1. Hub server logs

         2. Process or cleanse server logs

         3. E360 logs

         4. Provisioning logs

         5. Post Installation logs

         6. Elastic search logs

         7. Application server logs

         8. Database logs

1. Hub server logs

         Informatica MDM has two core components: hub server and process server earlier it was called cleanse server. The hub server is used to initiate the jobs, managing and controlling the threads in short hub server is master component in Informatica. The logs are generated when we access the Administration section of the MDM hub. Especially when we validate the ORS . These logs are captured in Hub server logs.

          Location :- <Informatica MDM install folder>/hub|server|log

        e.g./abc|hub|server|logs|cmxserver.log

2. Process server logs

           When we execute the jobs such as Stage, load, tokenization, match and merge jobs, the logs are captured in the process server logs.

            Location :- <Informatica MDM install folder>/hub|Cleanse/logs

             e.g . /abc/hub|cleanse/logs|cmxcleanse.log

3. E360 logs

              We can configure the user Interface using the provisioning tool. The User Interface is called Entity 360 application. When we access the application the logs are generated.

              Location:- <Informatica MDM install folder>/hub|server|logs 

              e.g. /abc/hub|server|logs|entity360view.log

4. Provisioning logs

             We use provisioning to configure business entities, transformations, views, tasks, and E360 applications. When we use the provisioning tool the logs are generated and stored below location.

             Location :- < Informatica MDM install folder>/hub|server/logs 

             e.g. /abc/hub|server|logs|provisioning.logs

5. Post Install logs

               The post-install logs are generated when we install Informatica MDM as well as when we apply EBF or upgrade.

               Location :- <Informatica MDM install folder>/hub|server|logs

              e.g. /abc/hub|server|logs|postInstallSetup.log

6. Elastic search logs

                If you are using Elastic search in your Informatica MDM then you may need to use Elastic search logs.

                Location:- <Elastic search folder>/logs 

                e.g. /aqr|logs|elastic search.log

7. Application server logs

                Application server logs are located as below

                a) Jboss

                 <Jboss home>/standalone/log/server.log

                  b) Weblogic

                   < Weblogic home >/domains/domain name/servers/server name/log/abc.out

                  c) websphere

                   <websphere home>/Appserver/profiles/profile name/logs/server name/systemout.log

8. Database logs

                  Database logs are not directly accessible. You need to reach out to your DBA to get database logs.

           Learn more about Informatica MDM here

        

What is difference between 'Remove from match list ' and 'Not a match' in IDD ?

             Are you looking for an article on Informatica Data Director which explains what is the difference between 'Remove from match list' and 'Not a match' options which are available in IDD application in Informatica Master Data Management? If so, then you reached the right place. Let's understand these two options here.

A) What is the match process?

                Informatica MDM comes with a process named match process. With help of this process, we can determine potential matching records. In other words, we can remove duplicate records from the system. Informatica Data Director application uses a match engine that comes with MDM in order to achieve it.

                   IDD application uses a match engine at the time of processing manual match records as well as at the time of creating a new record. This requires some specific to be mode using IDD configuration manager.

B) Where in the IDD application we can find the match feature?

                IDD application is used by data stewards or business users to manage the data. In order to manage the data, records need to be first searched and then opened. Once the record is opened we can see data, Xref, timeline, history, and match sections. The match section shows potential matching consolidate to the given record.

C)  Difference between ' Remove from match list ' and ' Not a match' in IDD

                  As discussed in the earlier section, potential matching records are available in the match section. If uses are working on a manual merge queue using this match section the users either can merge the record or can perform one of the below actions on the merge task.

                  1. Remove from match list

                  2. Not a match

                 The remove from match list removes the record from the match view in the IDD application. If the user logins again the record will be shown again on the screen.

              On the other hand, if the user selects the ' Not a match ' action then the matching entry will be deleted from match table. The record will not be shown in the IDD view anymore. This will also delete the merge task.

              Learn more about the merge process here -

 

What is lifecycle of consolidation_ind ?

    Are you looking for details about consolidation indicator in Informatica MDM? Are you also interested in knowing what are valid values for the consolidation indicator column? If so then you are right place. In this article, we will also explore the lifecycle of consolidation indicator for a record.

A) What is a consolidation indicator?

          The consolidation indicator is a column in the base object table. The consolidation process is also known as the merge process updates the consolidation indicator value for a record based on the record's process.

B) What are valid values for consolidation_ind?

          When we execute load jobs, Match job and merge jobs record goes through various processes because which value of consolidation indicator column goes through the values below

        4 : New record

        3 : Record queued for the match process

        2 : Record has gone through the match process

        1 : Consolidation record  

a) Consolidation_ind = 4

           The actions below cause record to have consolidation_ind = 4

          1. Inserting a new record in the Informatica hub 

          2. Queue a record as the new using data manager 

          3. When we unmerge the record either through API or E360 application

b) Consolidation_ind = 3

          The actions below cause record to have the consolidation_ind=3

           1. When we queue a record for a match using data manager

           2. If match job fails, the records that were picked up for matching but the match did not complete for that record will have value for consolidation indicator as 3

C) Consolidation_ind = 2

         The actions below cause record to have the consolidation_ind =2

         1. When the match process completes for the record

         2. When the record is queued for merge using data manager or any API or application.

d) Consolidation_ind = 1 

          The actions below cause record to have consolidation_ind =1 

         1. For the Golden source system the records will be loaded with consolidation_ind=1

         2. When the record is accepted as unique 

         3. If Accept Record as unique is set to yes and match process does not find matching record.

         4. If Accept Record as unique is set to yes and after merging records, it does not have any more matches.

e) Consolidation_ind =9

         If a business user puts the record on hold.

 

      Learn more about consolidation indicator in Informatica MDM here -

Top 10 commonly used commands in Snowflake

        Are you looking for details about commonly used commands in Snowflake? Are you also interested in knowing what are DML, DDL snowflake commands? Then you have reached the right place. In this article, we will explore more about snowflake commands.

A) Types of commands in Snowflake

          There are four types of commands present in snowflake and those are 

          1. DDL - Data Definition Language

          2. DML - Data Manipulation Language

          3. DCL - Data Control Language

          4. TCL - Transaction Control Language

         In this article, we will focus on DDL and DML commands use in Snowflake

B) What commonly used DDL commands in Snowflake?

            Here is the list of DDL commands used in snowflake

           1. ALTER

           2. CREATE

           3. DROP 

           4. USE

           5. SHOW

           Let's see each of these commands one by one -

1. AFTER - AFTER command is used to modify metadata of on account level, parameters for session or metadata of the database object

Syntax : 

              AFTER <object_type> <object_name> <actions>

e.g  AFTER SESSION SET < params >

2. CREATE - CREATE command is used to create new object

Syntax : 

              CREATE <object_type> <object_name>

e.g.  CREATE  DATABASE ABC

3. DROP - DROP command is used for removing object from system.

Syntax : DROP <object_type> [IF EXISTS] <identifier>

e.g  DROP USER [IF EXISTS] abc_ user

4. USE - USE command is used to specify role, warehouse database ,or schema for current session

Syntax : USE WAREHOUSE <name>

e.g   USE WAREHOUSE xyz 

5. SHOW - SHOW command is used to provide metadata for the object.

Syntax : SHOW <object_ type_plural> [LIKE '<pattern>']

e.g  SHOW PARAMETERS [LIKE '<pattern>']

C) What are commonly used DML commands in Snowflake?

         Here is the list of DDL commands used in Snowflake

          1. INSERT

          2. MERGE

          3. UPDATE

          4. DELETE

          5. TRUNCATE

             Let's see each of these commands one by one.

1. INSERT - INSERT command is used to insert one or more rows into the table.

       Syntax :

       INSERT INTO <table_name> [< column_name>]

           VALUES (<value>|DEFAULT|NULL,...)

        

       e.g

        INSERT INTO TAB_ABC  (id, name)

         VALUES ( 100 , ' DRONA')

2) MERGE - MERGE command is used to Insert, delete and update values in a table based on values in a subquery or another table.

         Syntax : 

         MERGE INTO <table_name> USING <source> ON <join_exp>L

         e.g

         MERGE INTO TAB_ABC USING TAB_PQR ON TAB_ABC.ID=TAB_PQR.ID WHEN MATCHED Then 

         Update set TAB_ABC .NAME = TAB_PQR.NAME

3. UPDATE: The UPDATE command is used to update rows in the table.

       Syntax : 

              UPDATE <table_name> SET <field>=<value>

       e.g 

            UPDATE TAB_ABC SET NAME = 'XYZ'

4. DELETE : DELETE command is used to delete records from the table.

         Syntax : 

              DELETE FROM <table_name > WHERE <condition>

          e.g 

              DELETE FROM TAB_ABC WHERE NAME='BOB'

5) TRUNCATE: TRUNCATE command is used to remove records from the table including privileges and constraints.

          Syntax :

              TRUNCATE TABLE <table _name>

          e.g 

              TRUNCATE TABLE TAB_ ABC.

Top 10 things you need to know before implementing Informatica MDM?

           Are you planning to implement Informatica Master Data Management aka MDM? Are you not sure what are the things you need to consider before considering MDM solution? If so, then you reached the right place. In this article, we will see the top 10 things which you need to know before implementing Informatica Master Data management in your organization. 

 1.Data Quality Measurement 

            You need to know how you are currently measuring data quality not only in a single project but also across the enterprise. This will give you two benefits one, you will know better options for quality of data measurement, and second, a baseline to measure the quality of data after MDM implementation.

 2.MDM and Data Quality

              Is there a relationship between master Data management and Data Quality? Can MDM help in improving data quality? The answer is Yes. However MDM and Data Quality are two distinct processes in any organization. You need to know what is the relationship between Master Data Management and Data Quality.

 3.Returns of Improved data quality?

               We initiative various projects for improvement in the processes and to achieve better results on Investment. You need to know what is the return you will be getting after improving data quality.

 4.Data Governance 

              Data governance is a crucial part of the business. Are you aware of how is data governance is implemented in your enterprise? You need to have proper data governance to get optimum benefits from MDM implementation.

 5.Data for business strategy 

               It is not new that this Era of data. We are in data 4.0 where the majority of the businesses are data-driven. You need to plan your business strategies based on data that is of great quality and well maintained.

 6.Data enrichment

               Why do you need data enrichment? One may ask this question. The answer is to make better decisions and recommendations we need to take important steps towards data enrichment.

 7.Privacy regulations 

               These rules and regulations we need to follow a business. We need to be fully aware of those rules and regulations and consider those implementing any MDM solutions.

 8.Customer satisfaction 

                Is your customer satisfied with your services? What are your customer's preferences and how are you managing these? How are addressing your customer's concerns and feedback? These are important questions you need to answer so that you improve those with MDM.

 9.Risk measurement and assessment 

                Informatica MDM defiantly plays a vital role in risk assessment and measurement. However, you need to know your current solutions and look for better opportunities to improve those.

 10.Future Perspective

             While implementing Informatica MDM, you need to look for long-term benefits instead of short-term MDM with great benefits for the long run.

Learn more about information MDM here

       

Howto fix - "ORA-00245: control file backup failed" issue

 Are you looking for an article about fixing "ORA-00245: control file backup" error? If so, then you reached the right place. In this article, we will see what is root cause of "ORA-00245: control file backup" error message at the database side and how to fix it?

What is "ORA-00245: control file backup" error ?

This error message occurs when Archive logs backup fails. This is Oracle database level functionality which takes backup of archive logs so that you can restore your device quickly and seamlessly in the event of data loss.

Whar the error messages are associated with "ORA-00245: control file backup"?

Here is the list of error messages associated with "ORA-00245: control file backup" -

• RMAN-03009: Failure of full resync command on default channel
• RMAN-03002: Failure of configuring command
• RMAN-03014: implicit resync of recovery catalog failed
• ORA-00245: control file backup failed; in Oracle RAC, target might not be on shared storage

 

What is the root cause of "ORA-00245: control file backup" error message?

The root cause can be the failure of   SNAPSHOT CONTROLFILE due to local file system configuration e.g. /abc CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<oracle home>/snapcf_pqr1.f'

However, you need to find out all possible other root causes.

 

How to fix  "ORA-00245: control file backup" error?

In order to fix this error message change SNAPSHOT CONTROLFILE NAME  RAMN parameter to shared storage e.g. +RECO_PROD

Learn more about Oracle here -

 

What is Active VOS Central , Active Console and Active VOS Process designer ?

     Are you looking for details about Active VOS Central, Active VOS Console, and Active VOS designer? Are you also would like to know what is process designer? If so, then you reached the right place. In this article, we explore these tools.

A) Active VOS Central

      Active VOS Central aka process central is used by business users. The business user uses process central to work on tasks such as approving or rejecting the requests. Once tasks are generated by automated business process engines, those will be queued to pool for business users. The request form can be submitted to start an automated business process.

        We can perform the following actions in Active VOS Central -

         a) View Task 

         b) Claim Task 

         c) Approve Or Reject Task

         d) Provide Comments

         e) Attach Files 

         f) Refresh Task

         g) View Task history

         h) Assign Tasks to other users  

B) Active VOS Console

       The Active VOS Console is used by an administrator to monitor & Fix processes related to the task. The administrator can also perform actions such as deployment of workflows, test user connectivity, configure URN mapping, delete or schedule faulted tasks, Fix any active VOS related issues using Active VOS Console.

       The Active VOS Console is a thin client application that can be accessed using the browser.

C) Active VOS Designer

       Active VOS designer is also known as process designer. Process designer is used by developers to create a new business workflow. It can be also used to update or customize existing workflow. Process designer contains drag & drop components for easy development and least programming. However, it extensively uses expression language.

       Active VOS central, Active VOS Console, and Active VOS designer are part of the Informatica Product suit. Learn more about Active VOS - here