Just ome quick tips on parameter to be alert when initiating SAP Netweaver Hana Database Migration
All Databases: r3load and jload Procedures
While migrating to SAP hana Database consideration requirement for SAP Netweaver Instance parameters
rsdb/prefer_in_itab_opt
rsdb/max_in_blocking_factor
rsdb/min_in_blocking_factor
rsdb/prefer_union_all
rsdb/prefer_join
rsdb/prefer_fix_blocking
rsdb/max_blocking_factor
rsdb/min_blocking_factor
rsdb/max_union_blocking_factor
rsdb/min_union_blocking_factor
SAP Business Objects BI Essential components
Do you know the most basic essential component of SAP Business Objects BI is as below.
This maybe the qiuckest, simplified note on how to learn about generating stack.xml and what its about.
In the current SAP technology I'm sure those SAP basis folks would have heard or went through the following ways to get their new system or existing system installed or even would have downloaded simplest pluggin of support pakcages to certain extreme.
But i know rarely SAP basis folks touched so much on Maintenance optimizer, Maintenance Planner, knowing what is Support Package Stacks and side-effect reports outcomes.
Well today i would like to share with you simple ways to understand SAP Maintenance Planner
Scenario 1 - If you plan to download a new installation
In Maintenance Planner choose --> Plan a new system
Scenario 2- If plan for upgrade example SAP ECC6 EHP5 to SAP ECC6 EHP8
In Maintenance Planner choose --> Choose Explore system
Scenario 3 - If you plan to download Support Packages only
In Maintenance Planner choose --> Choose Explore system
Answer : Goto SAP one lauchpad --> login with S user id, -> in the screen goto Maintenance Planner -> Choose Explore system or Plan a new system tab --> enter relevant details such as sap product, db , os and then next button top left all the way till you get few options
Push to Download basket , Download Stack.XML
So what happens here is that once you have went through the Plan process, maintenance planner have created a repository requirement of all your components required for installation or upgrade, where you dont have to choose manually during those days before maintenance planner existed.
Then at the screen it gives you option either to download on the spot by choosing download basket and generate Stack.xml where both are required unless if want to manually perform installation or upgrade.
Push to Download basket , Download Stack.XML
As you can see the Push to download basket option, basically what it does, is that all the selected software component are then linked or pushed to your SAP download manager tagged to your S user id. ( In ur repository server you need to have SAP download manager application downloaded which are available in SAP one launch pad download center.
At the ame time you need to download stack.xml - this is used for installing any system for example sapinst with xxxxxxxstack.xml file and the rest are taken care by the installation process.
At the end when you click complete - a PDF file given stating your Stack.xml details of all the software selected, purpose of the software and transaction id.
All downloaded software , stack.xml and PDF file need to be kept in 1 single location.
You may have notice Transaction ID. what is this?
Well its basically content of all the stack.xml that you have generated, for example if you have generated 10 stacks.xml either r new system or upgrade, then all these are recorded as transaction in the Transaction tab in Maintenance Planner. Therefore in the future you can always enter the Transaction tab and check your Stack.XML that you have created.
Well hope this helps and clarifies all relevant information required for you to use Maintenance planner confidently. The understanding is very important.
