Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

CLM 4.0_All OOTB ETL doesn't work -insight

Hello All,

After setting up CLM v 4.0 with Insight 1.1.1 in our evaluation environment, we are unable to run CLM4.0_ALL ETL in the OOTB catalog. The ETL just hangs/freezes on RRCRequirementLinkType build.

Did anyone run into this?

Thank you!

Deepaa

0 votes



7 answers

Permanent link
Marc,

We finally figured what was happening but not sure why. When running this build, the build hangs at the same place. Once we turn the READ SNAPSHOT on in the database (SQL Server), the build stopped hanging. Not sure why this happens on this build and not others. Also, our DBA turned on the SQL Profiler trace and monitored the jobs on prior runs and did not find any deadlocks in the database. Any insights will be appreciated. Thanks.

Kunal

1 vote


Permanent link
We didn't have any issues with this.  Have you resolved this by now?

0 votes


Permanent link
 We are facing the same issue with the RRCRequirementLinkType build. We are on Insight 1.1.1.2 and CLM 4.03. Have you been able to resolve this? Can you please share how you resolved it? Thanks.

0 votes


Permanent link
Kunal, can you enable full tracing by selecting all the trace levels when you run the job (in the 'Execute Jobstream' window) and paste the details of that specific fact build here? Is it hanging at the same place within that build?

0 votes


Permanent link
Hello Kunal,

thanks for sharing your solution.
I had the same hang issue on RRCRequirementLinkType and setting READ_COMMITTED_SNAPSHOT on for the data warehouse fixed it.

For reference the command i used was:
ALTER DATABASE DW
SET READ_COMMITTED_SNAPSHOT ON
Best Regards,

Francesco Chiossi

0 votes


Permanent link
 Francesco,

Thanks for confirming. We used the same command. Btw, did you experience any performance degradation in the ETL process because of this. Any other 'side effects'?

Kunal

0 votes


Permanent link
Hello Kunal,

so far I'm not aware of any side effect of the change.
Since this issue seems to be recurrent, there is an IBM internal work item where development is investigating the impact of the READ_COMMITTED_SNAPSHOT ON setting on the data warehouse (Internal reference: RRDI (private) - Task 108171).
I'll update this thread when there will be a conclusion that can be shared.

Best Regards,

Francesco Chiossi

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,497
× 40

Question asked: Nov 16 '12, 4:37 p.m.

Question was seen: 5,646 times

Last updated: Mar 13 '14, 11:32 a.m.

Confirmation Cancel Confirm