LCM Error - Duplicate Name

[Former Member]

Hi,

I am new to the LCM tool. Whenever I am trying to move my objects(Universes & Reports) from Dev to Quality, the Universes and the connections got successfully moved. But when we move the report it gives an error in the promotion status showing"Promotion Status=Failure : Trying to create an object with duplicate name. Id = 2017 ". Some one in the forum said about this error as CUID. Can anyone explain me what is CUID and how we can rectify this error.

Thanks & Regards,

Praveen Kumar

[denis_konovalov · Accepted solution]

this error message means that report you are migrating from source to destination has name conflict with report already existing in the destination.

Name conflict means that Report in source has same name with report in destination, but report in destination has different CUID.

CUID is the single most important aspect of the XI architecture. It is a Unique Identifyer that every object in XI architecture has.

The moment an object (universe, report, connection, user etc) is created - it gets new CUID and the CUID stays with object all its life. It cannot be changed.

Please review Admin guide for more details.

LCM user guide should give you more info on the particular situation you run into.

To fix this issue you have 2 choices :

1. Delete report in source, import report back from QA into Dev, make required changes - promote it back to QA.

2. Delete existing report in QA - promote again from DEV.

[Former Member · Accepted solution]

Hi Denis,

Thanks for your valuable reply. But from your solutions , can i conclude that there is no possiblity of overwriting a report(or object) in BOBJ using LCM. Because all of my reports are getting this eror.

Thanks,

Praveen Kumar

[denis_konovalov · Accepted solution]

This means you are not maintaining CUID persistancy.

LCM as well as Import Wizard are designed with CUID persistancy in mind.

LCM specificaly, as it is created to promote content between Dev-QA-Prod and all content in that chain has to be originated from Dev and has same CUID for all its lifecycle...

If you will not maintain CUID persistancy - you will always have problems in different areas of the product.

So, to answer your question - Yes, LCM will not overwrite reports with name conflict.

[Former Member · Accepted solution]

Thanks a lot. If possible can u tell me how to mantain this CUID Consistency. Can you provide me some links or tips to maintain this CUID.

[denis_konovalov · Accepted solution]

Admin guide is the main document, LCM admin and user guides are the additions.

To maintain CUID consistancy you need to establish a process which prevents developers from deleting original doc and creating new one with same name.

Or from making a copy of the object, then deleting the original.

or from saving report localy with option "save for all users".....

[Former Member · Accepted solution]

HI Denis,

Still i have some concerns about this discussion. I migrated this report one week before, and i made some modifications to the report & saved it today. Now I created a new job for this report and promoted but it gives error. If you mean to say that the LCM will not overwrite the report in the above mentioned scenario then i have some huge concern on the purpose of LCM.

Thanks ,

Praveen

[denis_konovalov · Accepted solution]

What error does it gives ?

What was the exact workflow you used to edit doc/then save it ?

If CUID of the report hasn't changed in the source or destination - then LCM will work.

If it changed - there will be problems.

Just go to report properties in source and destination and compare CUID's. This will explain the error.

[Former Member · Accepted solution]

The reports were developed in DEV system and testing was done in QA system so we migrated to QA. After testing there was some changes need to be done like adding the overall result. So we made these changes in DEV and again migrated. At that time we got the error... Here is the exact error.

Resolution Status=Overwritten, Dependency Status=All required dependencies are included, Commit Status=Commit attempted and failed, Promotion Status=Failure : Trying to create an object with duplicate name. Id = 2017

Even i checked the CUID of the reports in DEV and QA . They are completely different.

[denis_konovalov · Accepted solution]

This means one thing - during report change somehow its CUID was changed. How exactly do you go about making changes to the reports ?

Basicaly here is the workflow :

You develop report in Dev, it has CUID =1 and name ONE, you migrate report to QA, now you have report named ONE and CUID 1 in both environments.

Then 2 things might have happend : 1 - you made changes to report in DEV and in doing so its CUID is now 2. OR 2 - somone did something to report in QA and now in QA its CUID is 2....

When LCM is migrating report from DEV to QA it sees that it's migrating report with name ONE and CUID 2 (scenario 1) and in destination in the same folder it already has report ONE, but its CUID is 1 or

It's trying to move Report ONE/CUID 1 and sees report ONE and CUID 2 in the destination...

Another possibility is that it's not the report conflict issue

What is object with ID 2017 ?

Could it be the parent folder for your reports ?

run following query in Query builder

select SI_NAME, SI_TYPE from ci_infoobjects, ci_appobjects, ci_systemobjects where SI_ID=2017

[Former Member · Accepted solution]

Hello Denis,

The following situation has happened on the Business Objects XI 3.1 SP4 with LCM SP4 environments.

I have set the SNC for both Entitlements, I needed.

I have set also LCM Job. The result is "Partial success" - please, look at the [screenshot|http://www.edisk.eu/en/download/51788/LCM_mig-result.JPG_158.13KB.html].

I have followed your advice to [track|http://www.edisk.eu/en/download/06050/QB-2568.JPG_113.25KB.html], what exactly happend for both IDs. The result is [useless|http://www.edisk.eu/en/download/90226/QB-2568-result.JPG_62.13KB.html].

Can you help me, Where am I supposed to dig?

Thank you very much.

Edited by: Ladislav Varga on Nov 12, 2011 11:43 AM

In addition I have ran another job with checking dependencies of the failsed folders. There are no dependencies. Customer have not provided me the records to the tnsnames.ora... I have realized. So, that is, what I need to check... I hope.

[Former Member · Accepted solution]

Hi there,

Let me join the discussion.

When you work on reports in QA you might save a document under a new name ("report_new") because you want to check first how the changes affect the report. Than after testing it successfully you delete the old one and rename the new one with the old ones name. Big mistake!

The name of a report is not important - the CUID is. To keep the CUID intact you mustn't copy and create dublicate reports and rename them. "report_new" has got another CUID assigned to it and won't be promoted correctly when you try to overwrite it from DEV to QA again.

Rather save it under its original name and if you want to reinstate the original version you have to promote it again from DEV to QA. I don't see any other way.

Cheers

Sven