My Oracle Support Banner

Siebel Generate Merge Report Fails with Error ORA-00955: name is already used by an existing object (Doc ID 2348363.1)

Last updated on FEBRUARY 01, 2024

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.
Checked on currency: 11-Sep-2019




Symptoms

This issue occurs while upgrading (IRM) Siebel IP14 to Siebel IP17+ version, but it is applicable to other upgrade paths, including the most Siebel recent versions.

When attempting to run Generate Merge Reports during IRM execution, after the repository merge,
the following errors occur:

This is the upgrep phase <siebel-root>\siebsrvr\log\upgrep_dev_<siebel-source-version>\output\upgwiz.log file, but the same can be displayed while running IRM in Unix environments in /upgrep_dev_<siebel-source-version>/output/srvrupgwiz.log file:

 

UpgradeLog UpgradeError 1 000000025a520eb8:0 2018-01-08 14:41:53 (err=-1) was returned by application (D:\Siebel\IP2017\ses\siebsrvr\bin\..\..\jre\bin\java.exe -jar D:\Siebel\IP2017\ses\dbsrvr\common\MergeReport.jar /s D:\Siebel_Clients\IP2017 /c "deventp_DSN" /t apps /u user_apps /p ******** /o D:\Siebel\IP2017\ses\siebsrvr\log\upgrep_dev_81114\output /d oracle /r "New Siebel Repository" /l D:\Siebel\IP2017\ses\siebsrvr\log\upgrep_dev_81114\output/gen_merge_report.log /g Y /b SIEBEL_DATA1 /x SIEBEL_INDX1 /z N /a SSE_ROLE).

UpgradeLog UpgradeError 1 000000025a520eb8:0 2018-01-08 14:41:53 There was an error in launching the application.

UpgradeLog UpgradeError 1 000000025a520eb8:0 2018-01-08 14:41:53 Execute file action failed.

UpgradeLog UpgradeError 1 000000025a520eb8:0 2018-01-08 14:41:53 Error executing action (Generate Merge Report).

UpgradeLog UpgradeInfo 3 000000025a520eb8:0 2018-01-08 14:41:53 Status Message (Errors encountered)


Steps to be executed:

-----------------------


1. Run the Siebel Database Configuration Wizard > Upgrade > Upgrep step and enter all parameters required. Read Siebel Database Upgrade Guide > Performing a Siebel Incremental Repository Merge.

2. When Upgrep is paused, take a back up of the Siebel database, run the update statistics and execute the Repository Merge. All instructions can be read in the link above.

3. When the Repository Merge completes (Check <Siebel-Tools-Root>\logs\ IRM_MERGE*.* log files and verify if it ran successfully), resume the Upgrade from command line and it will run the next steps.

4. The Generate merge reports will fail.

 

Changes

 Siebel IRM execution to  IP17+ version in Development environment.

Cause

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
Symptoms
Changes
Cause
Solution


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