Problem after changing repository database name

dataservices administration
1

Hi

As part of a recent upgrade from 11.5 to 12.2, we renamed our repository database to something more appropriate. Unfortunately objects checked out in the central repository at the time now point to the old database name (understandably), and all options are now greyed out (check in/un-check out etc) to rectify the problem.

I tried editing an ATL backup of the central repository and replaced old with new database name. However, re-importing this has the effect of loosing ALL checked out information. Thus central repo suggests nothing is checked out, whereas local repositories indicate that there still is.

Could I amend the repository directly - can someone tell me which central repo table(s) store the checkout details?

Thanks
Simon

simonkirk (BOB member since 2006-10-10)

2

Please try re-sync the Local Repository in the Server Manager

ganeshxp :us: (BOB member since 2008-07-17)

3

Tech support can give you some queries to hack the repo to un-set the checkout properties.

This has long been a missing feature in DI’s central repo – the ability for a superuser to break a checkout lock.

dnewton :us: (BOB member since 2004-01-30)

4

Hey

Even me looking for this option!!! Someone ever tried contacting support?

ganeshxp :us: (BOB member since 2008-07-17)

5

Either that or a utility to update the central repo with new repository database details. There is a lot of historic stuff in there which would be difficult to update with a superuser override.

I’ve run a PL/SQL script to identify all the repository table columns containing the old database name.

This list comprises:
AL_FUNCINFO
AL_LANG
AL_LANGTEXT
AL_PROJECTS
AL_SCHEMA
AL_SETOPTIONS

Going to try a global replace within these - fingers crossed!

simonkirk (BOB member since 2006-10-10)