on 12-17-2016 5:54 AM - last edited on 02-04-2024 6:35 AM by postmig_api_4
Hi,
We are using BI Platform 4.2 SP3 .
We are trying to promote one webi report created on top of Bex(OLAP Connection) and One Xcelcious Dashboard 4.2(with 4 BI web service connection) from our DEV server to the Quality server using promotion management tool from CMC. In First instance Job went successful however server path was still pointing to Dev server so I rollback completely that instance and again when I promote the job then it finishes with partial success along with error as:-For Folder-> " Resolution Status=Copied, Dependency Status=All the required dependencies are included., Commit Status=Commit attempted and failed., Promotion Status=Failure : The property SI_CUID of info object with id number 7587 is not unique. Table = 'CMS_InfoObjects7'. Column = 'SI_CUID'. The server supplied the following details: The property of an object is not unique." For Dasboard,Webi and OLAP connection error as:-" Resolution Status=Copied, Dependency Status=Some of the required dependencies are not selected., Commit Status=Commit attempted and failed., Promotion Status=Failure : Must create object under it's defined root folder." While all four BI web service connection went partial success with warning as :-" Resolution Status=Copied, Dependency Status=Some of the required dependencies are not selected., Promotion Status=No errors detected."
I checked there are no duplicate folders or reports are there in Destination server. Missed to mention that prior to Promotion I had promoted the override settings for BI web service and OLAP connection and made them active with server credential changed to Quality.
Please help me what could be the steps to make the job success.
Empty recycle bin in CMC and try the migration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the same issue and a very similar experience with promotion management/rolling back. I found that the SI_CUID and SI_GUID of the failing object was associated with an "orphaned" OBJECTID. I determined the CUID by logging into the source and using the properties. On the failing target I logged directly into the database and issued the query:
SQL> select OBJECTID, SI_CUID, SI_GUID from CMS_INFOOBJECTS7 where SI_CUID='<CUID You Found from Source>';
Verified it was not associated with anything and then proceeded to delete.
SQL> delete from CMS_INFOOBJECTS7 where OBJECTID=<ID from the above query> (Run this on the target database where failures occured)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you also trying to promote the objects along with security?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.