Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
sanjeev_nagalikar
Contributor
Contributor

Attunity Upgrade from 6.6.to 7.0 is done | tasks are running Longer for 52 Plus hours

Hi ,

 

We have perform an upgrade of our attunity servers .

Source Version

Attunity 6.6

Target 7.0

Snowflake Version is also upgraded to latest one  -- snowflake_linux_x8664_odbc-2.25.2.

Post this we are seeing that the tasks/ loads which used to run for 3 hours are taking longer time and its running for 52 plus hours.

We are seeing the slowness when used ATTREP_CDC_LOG table.

Attaching the logs with this and please let us know if any inputs are needed from our end here.

 

 

 

 

Labels (2)
4 Replies
Maria_Halley
Support
Support

@sanjeev_nagalikar 

I am moving this post to the Data integration boards instead, so you reach the right audience.

Steve_Nguyen
Support
Support

@sanjeev_nagalikar

 

1. why not upgrade to 2021.11 or the lastet kit 2022.5 , instead of 7.0 ?

 

2. i review the log and do not see anything strange.

 

3. try to set performance to trace so you can see where is the latency on source or target , then if source, set sourc_capture trace ,,, if target ,, set target_load ,, trace ,, still keep performance to get more information.

 

 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Luke69857
Contributor
Contributor


@Maria_Halley wrote:

@sanjeev_nagalikar USPayserv

I am moving this post to the Data integration boards instead, so you reach the right audience.


Problem was, that if you have a similar PNID lowercase/uppercase but the same FQDN it ends with an error. So our workaround was to change the first PNID to a temporary created FQDN, and after the change succeeded we were able to change it again to the right FQDN and PNID without any problem. We also renewed the vCenter SSL certificate.

Steve_Nguyen
Support
Support

from the task log we see:

 

00009980: 2022-06-27T14:35:45 [TARGET_LOAD ]T: Loading table 'SAPSR3'.'KONV'. 481040000 records have been sent (endpointshell.c:3035)
00009980: 2022-06-27T14:35:50 [TARGET_LOAD ]T: Loading table 'SAPSR3'.'KONV'. 481050000 records have been sent (endpointshell.c:3035)
00009980: 2022-06-27T14:35:53 [TARGET_LOAD ]T: Loading table 'SAPSR3'.'KONV'. 481060000 records have been sent (endpointshell.c:3035)
00009980: 2022-06-27T14:35:59 [TARGET_LOAD ]T: Loading table 'SAPSR3'.'KONV'. 481070000 records have been sent (endpointshell.c:3035)
00009980: 2022-06-27T14:36:02 [TARGET_LOAD ]T: Loading table 'SAPSR3'.'KONV'. 481080000 records have been sent (endpointshell.c:3035)

 

---

1. try to set the max file size on snowflake endpoint to 2000MB

2. try to set the commit rate on full load to be larger then 10,000.

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!