Transports: Environment xxx already exists with the prefix D6

[parmjit_saroya3]

CPMPC 800: SP0009

Transport issue: Transport fails with RC8 with following error message “
Environment XX  already exists with the prefix D6”.

We recently migrated our BPC 7.5 environment to BPC 10. We  could not use in place migration because of
still open OSS message with SAP.  But we were able to export our BPC 7.5 environment and import it back into BPC 10.  We did not have any issues with export and import method until we started doing transport after we went live with BPC 10.We can transport our templates, Data manager packages, script and ABAP with no problem on existing models. The issue is that now we cannot transport any newly
created models or dimensions.  We get the error listed above when we transport. During our investigation we discovered
that in table UJA_APPSET_INFO APPSET_PREFIX for our APPSET_ID is “NL” in development box, But in QA and production it is “D6”.

   We have two solutions  that we are thinking should fix the problem. But we needed your recommendations on this or
any other solution that you might think solve our issue.

1. UJA_APPSET_INFO table in development is editable in development box and we could simply change the APPSET_PREFIX for our APPSET to “D6”. But we don’t know if it will cause other problems once prefix is changed. It is my understanding that infoobjects  and comments table use this prefix to create technical names in bw.
2. The second solution is to completely delete our environment in development box and export the environment from our QA box and import it back in development box. We will turn on the option to keep the technical name same when we import it in development box.

Step 2 will require significant amount of more work and we will need to redo some of the development work we will lose because of the deletion of the environment.  Please let us know if you have better solution or we should go with solution 1 or solution 2.

[Former Member]

Hi Parmjit,

The best option would be to do backup and restore from QA to Dev (not recommended though) and ofcourse you have to re-do the additonal development that you already did in DEV and are not in QA.

Regards,

Kalyan.

[former_member182766]

Hi!

You cannot change prefix on the existing system. If you go to RSA1 and check your backend BPC objects, you will see that each cube and each infoobject has that prefix - /CPMB/xx, where xx is your prefix, hence it cannot be changed.

The second option will work and the transports should be fine as long as you don't forget to check box "Use technical names from backup" in UJBR, this way the prefix will stay D6 and won't change.