Skip to main content
Solved

IAM Sync error role_tab_variant_col

  • September 23, 2024
  • 4 replies
  • 47 views

Forum|alt.badge.img+5

We upgraded to 2024.2   Upgrade of SF and DEV went fine. But when sync IAM to TST, it's stuck on script role_tab_variant_col. Already cancelled en restarted the job, result is the same. How can we solve this, because we can't continue the upgrade.

 

Best answer by Mark Jongeling

Okay, perhaps SQL Server has chosen a bad plan or the indexes and statistics are out of date, which can have massive impact. Could you run tsf_optimize and try again? 

If that also does not help, we may need to look closer into what exactly is causing this performance degradation. Could you create a ticket with a SF backup? If the database is too large, our support team can supply a FileCap link where you can upload the backup.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

4 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3936 replies
  • September 23, 2024

Hi @avandervelden,

It is actually not stuck, but this step takes much longer than others. In 2024.3 coming next week of writing this, this process has been optimized significantly.

This step in 2024.2 can take several minutes and is dependent on the amount of roles, granted tables in those roles in combination with the amount of Table variants in your model.

Edit: when cancelling/aborting this job, ensure that the SQL Server process is also stopped. Otherwise the process is running and using Server capacity.


Forum|alt.badge.img+5
  • Author
  • Vanguard
  • 32 replies
  • September 23, 2024

On DEV it took 6 minutes, on TST it ran already for hours!!

And yes, we have a large model etc, but that's why we switched to Thinkwise - this should not be an issue compared to another platform we had before.


Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3936 replies
  • Answer
  • September 23, 2024

Okay, perhaps SQL Server has chosen a bad plan or the indexes and statistics are out of date, which can have massive impact. Could you run tsf_optimize and try again? 

If that also does not help, we may need to look closer into what exactly is causing this performance degradation. Could you create a ticket with a SF backup? If the database is too large, our support team can supply a FileCap link where you can upload the backup.


Forum|alt.badge.img+5
  • Author
  • Vanguard
  • 32 replies
  • September 23, 2024

Thanks. Worked

tsf_optimize took more than an hour, but we can continue


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings