GitHubContribute in GitHub: Edit online

Cannot Read Input File in Informatica PowerCenter Scanner

Problem

Informatica PowerCenter scanner reports the following message in the mantaflow/cli/log/ifpcDataflowMasterScenario_*.properties.log log file.

2020-07-03 06:05:01.923 [pool-2-thread-1] 0 ERROR eu.profinit.manta.dataflow.generator.informatica.task.impl.IfpcScenario Error reading \OUTOPS_INOP\wkf_Extract_Collateral_File.xml: java.io.IOException: Cannot read input "D:\mantaflow\cli\platform\bin\..\..\temp\ifpc\REPO_INFA_PC_TEST\workflow\OUTOPS_INOP\wkf_Extract_Collateral_File.xml".
2020-07-03 06:05:01.923 [pool-2-thread-1] 0 ERROR eu.profinit.manta.dataflow.generator.informatica.task.impl.IfpcDataflowTask java.io.IOException: Cannot read input "D:\mantaflow\cli\platform\bin\..\..\temp\ifpc\REPO_INFA_PC_TEST\workflow\OUTOPS_INOP\wkf_Extract_Collateral_File.xml".
2020-07-03 06:05:01.923 [pool-2-thread-1] 0 INFO  eu.profinit.manta.dataflow.generator.modelutils.GraphScenario Processed file \OUTOPS_INOP\wkf_Extract_Collateral_File.xml, found 0 edges.

Additionally, the workflows do not show any details in Manta Dataflow Viewer.

More Details

This has been known to occur in cases where an incomplete workflow file was passed to the Manta scanner.

  1. Verify that the file(s) mentioned in the log exist.

  2. Verify that the user running Manta Flow CLI has read access to the file(s).

  3. Open the workflow file in a text editor (Notepad, Vim, or something similar) and verify if the extracted workflow XML file(s) in mantaflow/cli/temp/ifpc/<repository>/workflows/ is/are complete and valid. A typical issue is that the workflow file is not complete. 

    <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE POWERMART SYSTEM "powrmart.dtd">
<POWERMART CREATION_DATE="01/30/2018 10:09:01" REPOSITORY_VERSION="185.94">
<REPOSITORY NAME="INFA_REP" VERSION="185" CODEPAGE="UTF-8" DATABASETYPE="Oracle">
<FOLDER NAME="DataFlow" GROUP="" OWNER="Administrator" SHARED="NOTSHARED" DESCRIPTION="Contains testing workflows." PERMISSIONS="rwx---r--" UUID="dbec9eef-00e4-4b23-b1e1-98d36a170102">
    <SOURCE BUSINESSNAME ="" DATABASETYPE ="Oracle" DBDNAME ="Oracle" DESCRIPTION ="" NAME ="Nodes" OBJECTVERSION ="1" OWNERNAME ="Metadata" VERSIONNUMBER ="1">
        ...
    </SOURCE>
    <TARGET BUSINESSNAME ="" CONSTRAINT ="" DATABASETYPE ="Flat File" DESCRIPTION ="" NAME ="node" OBJECTVERSION ="1" TABLEOPTIONS ="" VERSIONNUMBER ="1">
        ...
    </TARGET>
    <MAPPING DESCRIPTION ="" ISVALID ="YES" NAME ="SqlOverrideMapping" OBJECTVERSION ="1" VERSIONNUMBER ="1">
        ...
    </MAPPING>
    <CONFIG DESCRIPTION ="Default session configuration object" ISDEFAULT ="YES" NAME ="default_session_config" VERSIONNUMBER ="1">
        <ATTRIBUTE NAME ="Advanced" VALUE =""/>
        ...
    </CONFIG>

    Notice that the FOLDER, REPOSIRTORY, and POWERMART elements do not have an XML tag at the end of the file.

  4. Unfortunately, no error messages were logged during the workflow extraction step in the log file mantaflow/cli/log/ifpcWorkflowExtractorMasterScenario_*.properties.log.

Solution

This behavior was observed when an incorrect instance of the pmrep utility from the Informatica client installation was used.

  1. Locate another instance of pmrep utility in the Informatica PowerCenter client folder. See ERROR: While running pmrep objectexport from the client machine, it closes abruptly for more details about pmrep instances.

  2. Configure the new pmrep instance path to Manta’s Informatica connection in the property pmrep application path.

  3. Run the Informatica PowerCenter extraction scenarios again, at least ifpcConnectionExtractorMasterScenario and ifpcWorkflowExtractorMasterScenario. See Manta Orchestration API Scripts on how to run scenarios.

  4. Verify if the extracted workflow files in mantaflow/cli/temp/ifpc/<repository>/workflows/ are complete now and if the file is properly terminated as follows.

        ...
    </WORKFLOW>
</FOLDER>
</REPOSITORY>
</POWERMART>

  5. Run the complete lineage analysis again.