My Oracle Support Banner

Full Publish Errors After Siebel Database Upgrade Repository Merge Execution - What Errors Can Be Ignored? (Doc ID 2860506.1)

Last updated on AUGUST 19, 2022

Applies to:

Siebel CRM - Version 22.1 and later
Information in this document applies to any platform.

Goal

Full Publish Errors After Siebel Database Upgrade Repository Merge Execution - What Errors Can Be Ignored?

Once the Repository merge is complete and after all merge conflicts have been resolved and before starting upgphys, you must generate the Siebel Runtime Repository data.

To generate the Siebel Runtime Repository data, you must execute the Full Publish command in Siebel Tools. Full publish has to be executed against the New Customer Repository. Make sure to change the DockRepositoryName in tools.cfg to New Customer Repository (refer to Siebel DB upgrade guide for the version) and ensure Siebel tools launches against the right Repository.

See: When Should We Run FullPublish During Upgrade Process From Lower Versions to Siebel IP2017 And Later? (Doc ID 2590526.1)


 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.