Data Services Central Repository Table Locks

[former_member744516]

My operations team has discovered that they can query tables and views from our SAP Data Services Central Repositories in order to track and analyze how our ETL objects are evolving.

However, I've noticed that when they do this, it often seems to cause our developers' Central Repository operations to fail with strange error messages. I believe it's because the query against the Central Repo views / tables is somehow locking objects that need to be updated. And usually, having the ops team disconnect their database connections fixes the problem.

However, I'm wondering if there is any documentation or knowledge in the community about why a simple table read might lock the Central Repo. Does querying views versus tables make any difference? Is there a safe way to query the Central Repo metadata?

We're running Data Services 14.2.14 on Windows Server 2016 Datacenter backed with Oracle 19c databases.

Many thanks for your help!

[denise_meyer · Accepted solution]

Hello,

Please check with your database provider on the table locks. It depends on the type of database when locks might be generated.

My suggestion would be to have a backup that is refreshed regularly of the central repository - and query that instead.

Thanks,
Denise
SAP Support