Cloud Data Integration : 2021 : September Skip navigation
2021

Informatica is fixing a behavior with Azure Synapse connector when using table/schema override properties which causes a change in behavior

 

Am I impacted?

If you use Informatica Azure Synapse connection as a target and use the table/schema override  properties you may encounter the following change in behavior:

  • When you override the target table name or schema name and truncate the target table in Microsoft Azure Synapse SQL, the Secure Agent truncates the table or schema that you specify in the override property before it writes the data to the target. Previously, the Secure Agent truncated the table or schema that you specify at the design time.
  • When you override the target table name or schema name and create a new target at runtime, the Secure Agent creates the target table based on the table name or schema name override that you specify in the advanced properties. Previously, the Secure Agent created the table based on the table name or schema name that you specify at the design time

 

How do I address the issue?

 

  • Validate your mappings that use “Truncate Table” option and verify that the override schema/table values are correct, as the truncate table would now start truncating the overridden object.
  • Create Target would work as expected, if the table doesn't exist it will create, if it exists it will have the same behavior as earlier

 

 

 

Who do I contact if I need help?

If you have any questions, please contact us through Global Customer Support at 1-877-INFAHELP from the US or Worldwide.

 

 

Thank you,

Informatica Team

 

Are you paying more for cloud resources than anticipated but still not getting the outcomes you want? You don't have to choose between cost-efficiency and performance; instead, rethink your #datamanagement strategy to ensure that you get the best of both worlds.

Please join and David Menninger from Ventana Research and Informatica’s Sampa Choudhuri for a webinar on “How to Avoid Cost Overruns in Cloud Data Management,” on Sept 30th, where you will learn how to create a unified, AI-enabled
#dataarchitecture that accelerates your ROI and time to insights while protecting your #cloud data warehouse and #datalake #modernization initiatives from cost overruns, resource constraints, and technology and implementation complexity.Please register here for the webinar.

 

Here’s the reg link:

Summary

This is a notice of the upcoming change in Q1 2022 with support of TLS 1.0/1.1 on Informatica Intelligent Cloud Services Secure Agents.

Support for TLS 1.0/1.1 will no longer be enabled by default on Informatica Intelligent Cloud Services Secure Agents (“Secure Agents”) from Q1 2022. Only TLS 1.2 will be enabled by default and customers requiring TLS 1.0/1.1 support will need to manually re-enable the older TLS protocols.

Informatica will continue to support TLS1.0/1.1 by default until that time.

 

Why are we doing this?

RFC 8996 released in the Spring of 2021 formally announced the deprecation of TLS versions 1.0 and 1.1. See RFC 5246 for details about the improvements of TLS 1.2 vs older versions.

 

In conjunction with the above deprecation notice, OpenJDK began disabling TLS 1.0 and TLS 1.1 by default in April 2021. Informatica Intelligent Cloud Services will be upgrading the Secure Agent JDK to version 8u302 of OpenJDK during the October 2021 major release.

Informatica will overwrite the default JDK 8u302 setting to continue supporting TLS 1.0 and TLS 1.1 until the first Major release in Q1 2022 to allow customers time to prepare for TLS 1.2 default configuration.

 

What are the plans and actions you must take going forward?

  • If you have previously disabled TLS 1.0/1.1 and standardized TLS 1.2, you must act after the IICS October 2021 major release. You will need to reset the JDK parameter on the secure agent that controls the allowed TLS algorithms. Please follow the KB article for steps.
  • If you have not standardized TLS 1.2, we encourage you to do so and begin evaluating the overall readiness and test for TLS 1.2 compatibility prior to the first Major release in Q1 2022.

This will require you to review all the endpoints (databases, applications, mainframes, etc.) for TLS 1.2 support and ensure they are configured to support TLS 1.2. It is advised to deploy a test Secure Agent configured to only support TLS 1.2 as described in KB Article and test their connectivity and IICS workloads.

 

What connections does this impact?

  • The connection from secure agent to IICS is always TLS 1.2. There is no impact on this in Q1 2022.
  • All connections from the secure agent to your databases, applications, mainframes, etc. might have an impact in Q1 2022. You need to review all endpoints for TLS 1.2 support and ensure they are configured to support TLS 1.2.

September Monthly Release Upgrade Impact

 

ALERT: For  customers connecting to  Google Big Query V2  using  IICS

Informatica is providing a new capability to execute Advanced Push Down Optimization using latest Google API’s i.e. com.google.cloud. If customer has created Full Push Down Optimization mapping using Google Cloud Storage V2 as Source and Google Big Query V2 as target with pre SQL or post SQL configured in Google BigQuery V2 target advanced attribute, then customer may see change in behavior. Customers with these scenarios will be reached out to via email, individually.

 

 Scenario 1: (Pre/Post SQL and Full PDO)

 

Am I impacted?

If you use Informatica Google Cloud Storage V2 connection as a source and Google BigQuery V2 as target, your mappings will fail if they meet all the below conditions:

  • pre SQL or postSQL provided on target advance attribute having LegacySQL syntax (ex: screenshot1)
  • The mapping withoutUseLegacySql: true in pre/postSQL config (screenshot2), 
  • Configured PushDownOptimization=Full in Mapping Task (screenshot3)

 

The link to the Google BigQuery V2 documentation is here.

 

 

Screenshot1: Pre/Post SQL on target

 

Screenshot2: Mappings in which pre/postSQL config is not provided with UseLegacySql: true

 

Screenshot3: Full PDO in Mapping task

How do I  address  the issue?

Options are:

  • New behavior: Update pre SQL Configuration or post SQL Configuration on GBQ target in mapping add UseLegacySql”: trueas shown in (Screenshot 4)

 

Screenshot 4: pre SQL Configuration or post SQL Configuration with add UseLegacySql”: true 

  • Old behavior: Enable optional connection property to revert to older API behaviour -"UseAPIServiceForExecution:true" as shown in (Screenshot 5)

 

 

Screenshot 5: Connection property to set “UseAPIServiceForExecution:true

 

 

Scenario 2: (IS_DATE function and Full PDO)

 

Am I impacted?

If you use Informatica Google Cloud Storage V2 connection as a source and Google Big Query V2 as target, your mappings will see a change in number of rowspushed to the next transformation if they meet all the below conditions:

  • Using IS_DATE function (ex: screenshot1_b)
  • Any business logic with respect to fractional seconds(screenshot2_b), and
  • Configured PushDownOptimization=Full in Mapping Task (screenshot3_b)

Example –

  • IS_DATE(col2_string, 'YYYY-MM-DD HH24:MI:SS')

 

 

The link to the Google Big Query V2 documentation is here.

 

Screenshot1_b: IS_DATE function in a mapping

 

 

Screenshot2_b: Business logic includes seconds

 

Screenshot3_b: Full PushDownOptimization in mapping task

How do I  address  the issue?

Only if required, to get the prior (July release) behavior one will need to edit the format provided in expressions containing IS_DATE; change format from 'YYYY-MM-DD HH24:MI:SS'  to 'YYYY-MM-DD HH24:MI:SS.US'

 

 

Scenario 3: (Target Advanced attribute - Write Disposition and Full PDO)

 

Am I impacted?

If you use Informatica Google Cloud Storage V2 connection as a source and Google BigQuery V2 as target, your mappings will fail if they meet all the below conditions:

  • Write disposition provided on target advance attribute has been selected as Write Truncate or Write Empty(Screenshot 1_c, Screenshot 2_c)
  • Configured PushDownOptimization=Full in Mapping Task (screenshot3_c)

The link to the Google BigQuery V2 documentation is here.

 

Screenshot1_c: Write Disposition as “Write Truncate”

 


- Screenshot2: Write Disposition as “Write Empty”

 

Screenshot3_c: Full Push Down Optimization in Mapping task

 

How do I  address  the issue?

  • Users will have to switch the mappings manually to non- Push Down Optimization mode, if they want to truncate the table or write into an empty table using write disposition.
  • User can change Write Disposition to Write append

 

Scenario 4: (Target with runtime attribute "Create Disposition" as "Create If Needed:)

If customer has created Full Push Down Optimization mapping using Google Cloud Storage V2 as Source and Google Big Query V2 as target with runtime attribute "Create Disposition" as "Create If Needed", then customer will see a mapping failure.

Till now, all these mappings used to treat any create disposition value as "Create Never". This was leading to incorrect behavior being performed in Push Down Optimization mode. Corrected the behavior by adding the logic to fail such mappings.

 

Am I impacted?

If you use Informatica Google Cloud Storage V2 connection as a source and Google Big Query V2 as target, your mappings will fail if they meet all the below conditions:

  • Create Disposition on target advance attribute has value selected as “Create if needed” (screenshot1)
  • Configured PushDownOptimization=Full in Mapping Task (screenshot2)

 

The link to the Google Big Query V2 documentation is here.

 

Screenshot1: Create Disposition as “Create If needed”

 

Screenshot2: Full PDO in Mapping task

How do I address the issue?

  • Users will have to switch the mappings manually to non-pushdown mode, if they want to create an empty table using create disposition. User can change Create Disposition value to “Create never".

 

Who do I contact if I need help?

If you have any questions, please contact Global Customer Support.

Update: Release FAQ link added.

 

We have the following dates set for the October 2021 major release. For all future upgrades and maintenance schedules, please follow our calendar here:Link to Calendar

 

Click on Whats New Guide for the October major release.

 

Please refer to our FAQ for any common issues or behavior changes.

 

 

PODs

Date

Day

Time

 

Pre-Release

13-Sep-2021

Monday

7 AM - 12 PM PT

 

NA West 1, US East 2

03-Oct-2021

Sunday

7 AM - 10 AM PT

 

US West 1 Azure, AP NorthEast 1 Azure

03-Oct-2021

Sunday

9:30 AM - 12:30 PM PT

 

US West 3, US East 4, AP SouthEast1

10-Oct-2021

Sunday

7 AM - 10 AM PT

 

US West 3 Azure, EM West 1

10-Oct-2021

Sunday

9:30 AM - 12:30 PM PT

 

US West 1 GCP, Canada Central 1

16-Oct-2021

Saturday

7 PM - 10 PM PT

 

US West 5, US East 6

16-Oct-2021

Saturday

9:30 PM - 12:30 AM PT

AP East 2 Azure, EM Central 1 Azure

21-Oct-2021

Thursday

9 AM - 12 PM PT

 

*Private pods are not be listed. Please contact support for those dates.

The roadmap information being provided herein is for informational purposes only. The development, release, and timing of any Informatica product or functionality described herein remain at the sole discretion of Informatica and should not be relied upon in making a purchasing decision. Statements made herein are based on information currently available, which is subject to change. Such statements should not be relied upon as a representation, warranty, or commitment to deliver specific products or functionality in the future.

 

IICS products, which use the secure agent, are currently tested on the operating systems specified in the PAM. To help customers plan for 2022, we are providing guidance on anticipated updates to the tested operating systems in the PAM during the next 6-9 months:

 

  • Addition of Ubuntu 20.04 in Q4 2021. Deprecation of Ubuntu 16.04 in September 2021, with the intent of removing this version from the PAM by March 2022. Per Ubuntu’s support lifecycle, Ubuntu 16.04 is past End of Standard Support.

 

  • Update of the supported SuSE Linux version from 12 SP3 to 12 SP5 in October 2021.

Filter Blog

By date: By tag: