Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

New Upgrade Woes With RepCrawler

Starting with 17.0 we have run the upgrade at least once on nearly every version up to 18.11.  We had never noticed this before at least in 18.11 RepCrawler has inactived hundreds and even thousands of object some of which a very much used.  Looks like maybe the code was tweaked but now it goes too far and our client's upgraded application errors out since some of the objects inactivated are needed.

We are working on a better method to inactivate objects not needed in order to speed up the time it takes to read the runtime repository on application start up.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center