Skip to Content
avatar image
Former Member

Bi-cont left during ehp5 upgrade

Hi all,

I am doing Ehp5 upgrade for one client and we have done the upgrade ehp5 in dev after i reuse the xml in qas also....but after the upgrade i found that the qas and prd is having the bi-cont 703 000 also. But in dev Bi cont is not available, Now i qas has been upgraded to ehp5 but bi cont is not.....while creating the xml for prd Solman is not allowing us to generate the xml without BI-cont....

Now please let us know on how to proceed...whether  i sud upgarde the prd with bi-cont also upgrade and later is it possible to upgarde the bi cont on qas via saint,,,



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Dec 28, 2012 at 04:14 PM

    Hi Rableen,

    • I also done the EHP5 upgrade in the similar way, but i didnt face that issue. make sure that you have changed the XML file properly. before doing the upgrade set that Parameter mentioned in that note: 822380 as below:

    • 822380: If you are using several application servers, make sure that profile parameter rdisp/bufrefmode is set to sendon,exeauto, and if you are using only one application server, make sure that the profile parameter is set to sendoff,exeauto. Otherwise, you only have the option of executing the "/$sync" command to make the changes become completely effective after the installation.
    • Upgrade is system specific so, QA, PRD environment will not effect in the Dev.
    • What problem you are facing exactly, while generating the XML for PRD in solman?


    Kishore Cherukumalla

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 29, 2012 at 09:10 PM

    Hi Rableen,

    rule of thumb: never uses the same XML stack file for multiple system upgrades. Don't modify it even if the systems are on the same SP level. Please genereate a new one for each system being upgraded, SAP Support will always ask you for this.

    Now you'll likely have to bring BI_CONT to the desired SP level. Please go through MOPZ again and select only this component for upgrade. Do not include others on the same process - later on you'll be able to upgrade the whole system, this time with the correct BI_CONT SP level.

    Best regards,

    Tomas Black

    Add comment
    10|10000 characters needed characters exceeded

    • Tomas,

      I understand what you are saying but this can be quite challenging in the real world. Let me give you an example:

      1) update of DEV on 8/2012 to EHP6/SP4

      2) update of QA on 10/2012 to EHP6/SP4

      3) update of PRD on 12/2012 EHP6/SP4

      everything would be nice if MOPZ would NOT take the most recent patch levels of archives. You have no way to insure the quality of DEV-QA-PRD unless you run MOPZ for the entire landscape at once. I think this is something that SAP has overlooked. Something that should be done at once but is NOT done at once in the real world.

      People do not easily adjust their working behaviour to the working behaviour of programs.