Skip to Content

This blog is continuation of my previous work BW on HANA – Pre Migration ACTIVITY .

Many of us , who have been involved in OS/DB migration project [including migration of BW system from XXX (non hana db) to YYY(non hana db)] would be

already aware of the post migration activities . So the 1st question , for first timers (BW on HANA) , that comes to your mind is – “how different is this migration

from the one that i have been doing”.In terms of post migration activity , yes you would be doing most of the activities that you were doing in your

previous  project. In addition to that , you will have to take extra care of :-

1. converting the standard Info Cubes and Data stores Objects(Not required as of BW 7.4 and should reconvert all the HANA to Standard DSO )

2. No JAVA support (7.3X) on HANA DB ,so configure you JAVA stack ( only if you had dual stack BW before migration) .From NetWeaver 7.40 onwards


you can install BI-JAVA as separate Instance also in HANA.

3. Be aware that now you do not Need BWA or other such accelerators .

4.Validate the activities at HANA studio and in BW (DBA cockpit).

5. Delta handling

other than this (you are invited to add points , if i had missed something ) , at planning level ,i feel you will do the same activity that you have done earlier .

so , we can  follow the below task list :-

TASK Action
put check on the batch jobs Run BTCTRNS1
Activate partner profiles. check WE20 /WE21 if you maintain partner profiles and Inbound/outbound RFCs
convert  logical system Run BDLS (converts one logical system to another,which is not present in ur current machine after system copy) on BW and Source systems
restore Source System in BW restore it with standards method
Reset Prog. for ODS and DTP run RSSGPCLA
Consistency Check

Run Report RSUPGRCHECK  to checks the consistency of generated DDIC objects for BI metadata like

InfoObjects, InfoCubes and transfer rules. it helps to  determine whether the DDIC tables required for a BI

meta object are active.

check correctness of tables run RSDU_TABLE_CONSISTENCY to check correctness of tables in row/column store ** check SAP Note for latest info on the same.
Adjust DB specific DDIC entries

Execute RS_BW_POST_MIGRATION choose HANA specific options :-

*chose the variant “SAP&POSTMGRHDB”

/wp-content/uploads/2014/04/pic1_428209.png

once done with it , validate that you see these in HANA studio and DBA cockpit –

a. Calculation view for all DSOs and Infocubes( for existing ones).

**When you activate – CALC views get created for the newly created DSO and InfoCube.

Optimization

Migrating BW on HANA does not chnages DSOs/InfoCubes  into HANA optimized.

Only infocube of type standard can be converted to SAP HANA -optimized infocube.

use – RSMIGRHANADB or RSDRI_CONVERT_CUBE_TO_INMEMORY .

After migration standard infocubes can be found in the SAP HANA database column store..

Similar for DSOs.

/wp-content/uploads/2014/04/pic2_428267.png

during conversion be reminded to choose :-

a. choose without change log – if you no longer need the data saved in the change log. After migration , no rollback or a delta upgrade old request would be possible.

b Reconstruct change log – it has more run time  but if the data has been archieved from the DSO only request that affect the archieve area can be restored .

Remarks :-

i.Standard DSOs are converted to SAP HANA Optimized DSOs only if the DSO is not a part of hybrid provider or a semantically -partitioned objects(SPO).

ii.If You are doing delta handling then you should choose keep the change log.

JAVA Stack (** dual stack system moving to HANADB)

a. goto config tool –> UME and manage it .

b. cross check the beckend parameters like – BACKEND_CLIENT,BACKEND_SID,J2EE_ADMIN,J2EE_SID etc

c.go to  NWA–> Select function BW-Java Configuration

Delta Handling

Load the latest delta queues to BW –>activate the Info Providers–> Stop all the process chains–>  Migrate BW

on HANA –> convert the DSO’s and Cubes to In memory(if not done  above)–> Restart the Process chains.

SAP Notes to refer SAP note – 1659383 ; 1695778 , 1846493,1949273

do help me to make this checklist better , please give you inputs .

Happy migration 🙂

To report this post you need to login first.

16 Comments

You must be Logged on to comment or reply to a post.

  1. srikanth mandalapu

    1. converting the standard Info Cubes and Data stores Objects.

    Not required as of BW 7.4 and should reconvert all the HANA to Standard DSO

    2. RSDU_TABLE_CONSISTENCY

    This report has lot of Bugs, SAP agreed on the call that it needs fixes.

    (0) 
      1. Sankameshwar Ramakrishnan

        Hi Roland/Vinay,

        Please clarify, if Infocube conversion is still necessary using RSMIGRHANADB? SAP note 0001691096 provides a matrix which states, moving a standard cube from Non-HANA to HANA will make it HANA optimized, which is contradictory to vinay’s statement Migrating BW on HANA does not chnages DSOs/InfoCubes  into HANA optimized” and your’sInfoCubes are still to be converted into IMO“.

        We are migrating one system from 7.0 & another 7.3 (non HANA DB) to 7.4 on HANA.

        Also, Kindly clarify below points which would be of great help:

        1. Apart from DSO/Cube, is there any manual task to be carried out once migration is done to 7.4 purely with respect to BW objects?

        2. Will transformations with routines become inactive , because of new popup to select the fields used in the routines?

        3. Which of BW objects will have version adaptability/compatability problem, this will help us to plan before migration.

        Many thanks.

        @ Vinay: Thanks for such good document.

        Regards,

        Sankamesh

        (0) 
  2. Bhupesh Pant

    Hello Vinay Singh,

    Regrading you point no 2 ” No JAVA support right now on HANA DB”. But Java can be installed in separate system through SAPINST connecting to your Hana DB from NW7.40 SP3 onwards.

    I would like to understand, in which context you said “” No JAVA support right now on HANA DB”.

    Thanks,

    Bhupesh Pant

    (0) 
    1. Roland Kramer

      from NetWeaver 7.40 onwards you can install BI-JAVA as separate Instance also in HANA. Dualstacks are not supported anymore in 7.40, despite of HANA od anyDB.

      Best Regards Roland

      (0) 
    2. singh vinay Post author

      Hi Bhupesh ,

      Hope Roland’s reply answers your query , thanks for reading and helping me to improve with you questions .

      regards,

      vinay singh

      (0) 
      1. Bhupesh Pant

        Hello Viany,

        Actually, your statement No JAVA support right now on HANA DB, so configure you JAVA stack” made me confused. I know SAP Nw 7.4 SR3 onward supports JAVA on SAP HANA. I wanted to ask you which context you put No JAVA support right now on HANA DB ,so configure you JAVA stack” statement. My question was for you only.

        (0) 
        1. singh vinay Post author

          hi Bhupesh,

          since most of the migration would be from Dual stack to BW on HANA .we would be either required to use dual stack split-er or carve out the instances. So in both the cases we will have to configure/install/manage our Java stack separately. I guess my work “right now ” is confusing (it was in context of  730 ).

          so my context was 730 . i have just updated the blog .Hope the statement now is more understandable .

          Thanks a lot for helping here.

          regards,

          vinaysingh

          (0) 
    1. singh vinay Post author

      HI Daniel ,

      thanks for reading the blog and suggesting the note numbers .Indeed they are important ,I have added them as well.

      regards,

      Vinaysingh

      (0) 
  3. Prasanthi K

    Hi Vinay,

    Couild please let me know the note 1847431 – SAP BW ABAP Routine Analyzer is part of post upgrade activity or Pre upgrade activity.

    How do we check HANA adapatation for BW ABAP objects.

    Thanks & Regards

    Prasanthi

    (0) 

Leave a Reply