(IICS) Informatica Cloud Feb 2021 Major Release FAQ

Version 25

    Are you facing issues after the IICS Feb 2021 Major Release? We are here to help. We have identified some of the common issues encountered by users and pulled together a list of solutions to help you address them. Read on to know more.

     

    Note: If you have any technical issues, clickhere to open a support case or to contact Global Customer Support.

     

    SUMMARY

    We have a running list of known issues for the Feb 2021 Major Release queries and solutions. We will continue to update this list so check back later for more updates. If you already have a network.informatica.com login, we recommend following this post so that you can automatically receive updates for any new issues when they are posted.

     

    New features and Documentation - Feb 2021 Major release

    The 'Whats New' Guide is available here
    Cloud Data Integration enhancements
    Connector Release Notes
    Taskflow enhancements.
    Cloud Application Integration PostgreSQL Upgrade
    Runtime Continuity

     

    ISSUES AND SOLUTIONS

              US East 6 pod - 6 March 9:00 PM PT - 7 March 12 AM  PT

                          

    CLOUD DATA INTEGRATION

    Issue: Multiple versions of Data Integration Services.

    Solution: This is expected behavior due to Runtime Continuity, this will be removed after 24 hours.

    Issue: Resume icon is not visible in the My Jobs in Data Integration, All Jobs and Running Jobs pages in Monitor.

    or Permissions issues when monitoring Job status over API (like runajobCLI)

    Solution:

    Resume:

    As part of this release, the Resume icon is moved from the My Jobs page in Data Integration, and the All Jobs and Running Jobs pages in Monitor to the corresponding taskflow status page and has been renamed to "Resume from faulted step".

     

    Permission:

    The “Monitor - View Job Results” privilege is now required to view a Taskflow’s status using the Status API. This privilege can be enabled / disabled through Administrator -> User Roles (Click on a role) -> Services (Monitor) -> Features -> Job Results - view

     

    Please refer: Taskflows

    Issue: "Agentcore is upgrading" is shown for a secure agent after Upgrade in IICS.

    Agentcore shows error - ERROR [com.informatica.saas.infaagent.agentcore.AgentCoreStateMachine] - Authentication failed due to: [407 AuthenticationRequired: [no body]].

     

     

    Solution: Please refer to the KB for the solution: https://knowledge.informatica.com/s/article/AgentcoreStuckInUpgradingState

    Issue: Windows Secure Agent Oracle/SQL Server tasks failing with error "Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user and connection string [Driver=DataDirect CLOSED 8.0 SQL Server Wire Protocol for Informatica - R36;].]".

     

    - This issue is being caused due to the Windows Registry not being updated. This can happen due to permission restrictions on the Agent machine preventing the Registry update needed during the upgrade.

     

    Solution: Please refer the KB for the solution: https://knowledge.informatica.com/s/article/633877

    CLOUD APPLICATION INTEGRATION

    Issue: Process Server in "Restart Required" status after the release

    Solution: As part of this release, updates were made to the Process Server service on the Secure Agent. The updates do not affect the service and the agent processes will continue to work as is. As a result of the deployment of the updates, you will see that the status of the Process Server service shows up as Restart Required.
    Please refer: https://docs.informatica.com/integration-cloud/cloud-application-integration/current-version/what-s-new/application-integration/upgrade/process-server-restart.html

    Issue: Postgresql DB maintenance script throws an error on executing without port number as an argument

    Solution: As part of this release,the postgresql database maintenance script db_maintenance.bat or db_maintenance.sh now accepts port number as an additional mandatory parameter.  Apart from db username and password the db port also needs to be passed as an argument to the script.

     

    Example : db_maintenance.sh <dbusername> <dbpassword> <dbport (default:5432)> [vacuum | reindex] [table1 table2 ...]

    Sample 1: db_maintenance.bat bpeluser bpel 5432 vacuum

    Sample 2: db_maintenance.bat bpeluser bpel 5432 vacuum aeprocesslogdata

     

    Table names as an argument is not mandatory.

    Please refer Script Changes section at Upgrading the PostgreSQL database from version 9.5.2 to 12.4

    Issue: If the Process Server service was in an error state prior to the upgrade, your process server will continue to be in an error state under Administer > Runtime environment post-upgrade.

    The error "The data directory was initialized by PostgreSQL version 9.5, which is not compatible with this version 12.4" can be seen in the PostgreSQL logs ([Informatica Cloud Secure Agent dir]\apps\process-engine\logs\PostGreSql\postgresql.log)

    Solution: Please refer to the KB for solution: https://knowledge.informatica.com/s/articlepreview?c__number=5004w000025eibnAAA&language=en_US

     

     

     

     

    PAST UPGRADES:

     

    ISSUES AND SOLUTIONS

              US West 1 GCP pods - Feb 26 (6:00 AM PT - 9 AM  PT)

    AP SouthEast 1 pod, AP Northeast 1 Azure - Feb 26 (8:00 AM PT - 11 AM  PT)

                           

    CLOUD DATA INTEGRATION

    Issue: Multiple versions of Data Integration Services.

    Solution: This is expected behavior due to Runtime Continuity, this will be removed after 24 hours.

    Issue: Resume icon is not visible in the My Jobs in Data Integration, All Jobs and Running Jobs pages in Monitor.

    or Permissions issues when monitoring Job status over API (like runajobCLI)

    Solution:

    Resume:

    As part of this release, the Resume icon is moved from the My Jobs page in Data Integration, and the All Jobs and Running Jobs pages in Monitor to the corresponding taskflow status page and has been renamed to "Resume from faulted step".

     

    Permission:

    The “Monitor - View Job Results” privilege is now required to view a Taskflow’s status using the Status API. This privilege can be enabled / disabled through Administrator -> User Roles (Click on a role) -> Services (Monitor) -> Features -> Job Results - view

     

    Please refer: Taskflows

    Issue: "Agentcore is upgrading" is shown for a secure agent after Upgrade in IICS.

    Agentcore shows error - ERROR [com.informatica.saas.infaagent.agentcore.AgentCoreStateMachine] - Authentication failed due to: [407 AuthenticationRequired: [no body]].

     

     

    Solution: Please refer to the KB for the solution: https://knowledge.informatica.com/s/article/AgentcoreStuckInUpgradingState

    Issue: Windows Secure Agent Oracle/SQL Server tasks failing with error "Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user and connection string [Driver=DataDirect CLOSED 8.0 SQL Server Wire Protocol for Informatica - R36;].]".

     

    - This issue is being caused due to the Windows Registry not being updated. This can happen due to permission restrictions on the Agent machine preventing the Registry update needed during the upgrade.

     

    Solution: Please refer the KB for the solution: https://knowledge.informatica.com/s/article/633877

    CLOUD APPLICATION INTEGRATION

    Issue: Process Server in "Restart Required" status after the release

    Solution: As part of this release, updates were made to the Process Server service on the Secure Agent. The updates do not affect the service and the agent processes will continue to work as is. As a result of the deployment of the updates, you will see that the status of the Process Server service shows up as Restart Required.
    Please refer: https://docs.informatica.com/integration-cloud/cloud-application-integration/current-version/what-s-new/application-integration/upgrade/process-server-restart.html

    Issue: Postgresql DB maintenance script throws an error on executing without port number as an argument

    Solution: As part of this release,the postgresql database maintenance script db_maintenance.bat or db_maintenance.sh now accepts port number as an additional mandatory parameter.  Apart from db username and password the db port also needs to be passed as an argument to the script.

     

    Example : db_maintenance.sh <dbusername> <dbpassword> <dbport (default:5432)> [vacuum | reindex] [table1 table2 ...]

    Sample 1: db_maintenance.bat bpeluser bpel 5432 vacuum

    Sample 2: db_maintenance.bat bpeluser bpel 5432 vacuum aeprocesslogdata

     

    Table names as an argument is not mandatory.

    Please refer Script Changes section at Upgrading the PostgreSQL database from version 9.5.2 to 12.4

    Issue: If the Process Server service was in an error state prior to the upgrade, your process server will continue to be in an error state under Administer > Runtime environment post-upgrade.

    The error "The data directory was initialized by PostgreSQL version 9.5, which is not compatible with this version 12.4" can be seen in the PostgreSQL logs ([Informatica Cloud Secure Agent dir]\apps\process-engine\logs\PostGreSql\postgresql.log)

    Solution: Please refer to the KB for solution: https://knowledge.informatica.com/s/articlepreview?c__number=5004w000025eibnAAA&language=en_US

     

     

    ISSUES AND SOLUTIONS

              EM West 1, US WEST 3 Azure pods - Feb 20 (6:00 AM PT - 9 AM  PT)

    US West 3, US EAST 4 pods - Feb 20 (8:00 AM PT - 11 AM  PT)

                           

    CLOUD DATA INTEGRATION

    Issue: Multiple versions of Data Integration Services.

    Solution: This is expected behavior due to Runtime Continuity, this will be removed after 24 hours.

    Issue: Resume icon is not visible in the My Jobs in Data Integration, All Jobs and Running Jobs pages in Monitor.

    or Permissions issues when monitoring Job status over API (like runajobCLI)

    Solution:

    Resume:

    As part of this release, the Resume icon is moved from the My Jobs page in Data Integration, and the All Jobs and Running Jobs pages in Monitor to the corresponding taskflow status page and has been renamed to "Resume from faulted step".

     

    Permission:

    The “Monitor - View Job Results” privilege is now required to view a Taskflow’s status using the Status API. This privilege can be enabled / disabled through Administrator -> User Roles (Click on a role) -> Services (Monitor) -> Features -> Job Results - view

     

    Please refer: Taskflows

    Issue: "Agentcore is upgrading" is shown for a secure agent after Upgrade in IICS.

    Agentcore shows error - ERROR [com.informatica.saas.infaagent.agentcore.AgentCoreStateMachine] - Authentication failed due to: [407 AuthenticationRequired: [no body]].

     

    Solution: Please refer to the KB for the solution: https://knowledge.informatica.com/s/article/AgentcoreStuckInUpgradingState 

    Issue: Windows Secure Agent Oracle/SQL Server tasks failing with error "Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user and connection string [Driver=DataDirect CLOSED 8.0 SQL Server Wire Protocol for Informatica - R36;].]".

     

    - This issue is being caused due to the Windows Registry not being updated. This can happen due to permission restrictions on the Agent machine preventing the Registry update needed during the upgrade.

     

    Solution: Please refer the KB for the solution: https://knowledge.informatica.com/s/article/633877

    CLOUD APPLICATION INTEGRATION

    Issue: Process Server in "Restart Required" status after the release

    Solution: As part of this release, updates were made to the Process Server service on the Secure Agent. The updates do not affect the service and the agent processes will continue to work as is. As a result of the deployment of the updates, you will see that the status of the Process Server service shows up as Restart Required.
    Please refer: https://docs.informatica.com/integration-cloud/cloud-application-integration/current-version/what-s-new/application-integration/upgrade/process-server-restart.html

    Issue: Postgresql DB maintenance script throws an error on executing without port number as an argument

    Solution: As part of this release,the postgresql database maintenance script db_maintenance.bat or db_maintenance.sh now accepts port number as an additional mandatory parameter.  Apart from db username and password the db port also needs to be passed as an argument to the script.

     

    Example : db_maintenance.sh <dbusername> <dbpassword> <dbport (default:5432)> [vacuum | reindex] [table1 table2 ...]

    Sample 1: db_maintenance.bat bpeluser bpel 5432 vacuum

    Sample 2: db_maintenance.bat bpeluser bpel 5432 vacuum aeprocesslogdata

     

    Table names as an argument is not mandatory.

    Please refer Script Changes section at Upgrading the PostgreSQL database from version 9.5.2 to 12.4

    Issue: If the Process Server service was in an error state prior to the upgrade, your process server will continue to be in an error state under Administer > Runtime environment post-upgrade.

    The error "The data directory was initialized by PostgreSQL version 9.5, which is not compatible with this version 12.4" can be seen in the PostgreSQL logs ([Informatica Cloud Secure Agent dir]\apps\process-engine\logs\PostGreSql\postgresql.log)

    Solution: Please refer to the KB for solution: https://knowledge.informatica.com/s/articlepreview?c__number=5004w000025eibnAAA&language=en_US

     

     

    ISSUES AND SOLUTIONS

              NA West 1, NA East 2 pods - Feb 13 (6:00 AM PT - 9 AM  PT)

    US West 1 Azure and Canada Central 1 pods - Feb 13 (8:00 AM PT - 11 AM  PT)

                            

    CLOUD DATA INTEGRATION

    Issue: Multiple versions of Data Integration Services.

    Solution: This is expected behavior due to Runtime Continuity, this will be removed after 24 hours.

    Issue: Resume icon is not visible in the My Jobs in Data Integration, All Jobs and Running Jobs pages in Monitor.

    or Permissions issues when monitoring Job status over API (like runajobCLI)

    Solution:

    Resume:

    As part of this release, the Resume icon is moved from the My Jobs page in Data Integration, and the All Jobs and Running Jobs pages in Monitor to the corresponding taskflow status page and has been renamed to "Resume from faulted step".

     

    Permission:

    The “Monitor - View Job Results” privilege is now required to view a Taskflow’s status using the Status API. This privilege can be enabled / disabled through Administrator -> User Roles (Click on a role) -> Services (Monitor) -> Features -> Job Results - view

     

    Please refer: Taskflows

    Issue: RunAJobCli utility fails post February 2021 release. (Fixed for releases after 2/13)

    Solution: The issue is identified as a defect- CLDDI-6128.

     

    To resolve the issue, please follow the steps mentioned below-

    -Stop the agent.

    -Navigate to the directory {Agent_Dir}/apps/

    -Rename the 'runAJobCli' folder to 'runAJobCli_bkp' to take a backup (Very Imp)

    -Restart the agent.

    -Copy the log4j.properties and restenv.properties file to the newly deployed runAJobCli folder.

     

    THIS ISSUE WILL BE RESOLVED FOR FUTURE POD UPGRADES.

    Issue: Windows Secure Agent Oracle/SQL Server tasks failing with error "Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user and connection string [Driver=DataDirect CLOSED 8.0 SQL Server Wire Protocol for Informatica - R36;].]".

     

    - This issue is being caused due to the Windows Registry not being updated. This can happen due to permission restrictions on the Agent machine preventing the Registry update needed during the upgrade.

     

    Solution: Please refer the KB for the solution: https://knowledge.informatica.com/s/article/633877

    CLOUD APPLICATION INTEGRATION

    Issue: Process Server in "Restart Required" status after the release

    Solution: As part of this release, updates were made to the Process Server service on the Secure Agent. The updates do not affect the service and the agent processes will continue to work as is. As a result of the deployment of the updates, you will see that the status of the Process Server service shows up as Restart Required.
    Please refer: https://docs.informatica.com/integration-cloud/cloud-application-integration/current-version/what-s-new/application-integration/upgrade/process-server-restart.html

    Issue: Postgresql DB maintenance script throws an error on executing without port number as an argument

    Solution: As part of this release,the postgresql database maintenance script db_maintenance.bat or db_maintenance.sh now accepts port number as an additional mandatory parameter.  Apart from db username and password the db port also needs to be passed as an argument to the script.

     

     

    Example : db_maintenance.sh <dbusername> <dbpassword> <dbport (default:5432)> [vacuum | reindex] [table1 table2 ...]

     

     

    Sample 1: db_maintenance.bat bpeluser bpel 5432 vacuum

    Sample 2: db_maintenance.bat bpeluser bpel 5432 vacuum aeprocesslogdata

     

     

    Table names as an argument is not mandatory.

     

    Please refer Script Changes section at Upgrading the PostgreSQL database from version 9.5.2 to 12.4

    Issue: If the Process Server service was in an error state prior to the upgrade, your process server will continue to be in an error state under Administer > Runtime environment post-upgrade.

    The error "The data directory was initialized by PostgreSQL version 9.5, which is not compatible with this version 12.4" can be seen in the PostgreSQL logs ([Informatica Cloud Secure Agent dir]\apps\process-engine\logs\PostGreSql\postgresql.log)

    Solution: Please refer to the KB for solution: https://knowledge.informatica.com/s/articlepreview?c__number=5004w000025eibnAAA&language=en_US