Basis and others: 2021

Upgrading windows server 2008 to windows server 2019, two step upgrade required

For upgrading windows 2008 to windows 2019 - it can be straightly done with an in place upgrade to windows server 2019/

To simplify the steps follows:-

1. Upgrade your current windows server 2008 to either windows servre 2012 or 2016 first

2. Then from either 2012 or 2016 upgrade to 2019.

Simple as that.

In most cases there are scenarios where customers with windows server 2008 or 2008 R2 are reaching the maintenance end date, therefore Microsoft gives flexible choices,

1. Move your Windows 2008 R2 as it is to Microsoft Azure, in which you will be given time of extended warranty, as this gives you time to plan for you future upgrade to Windows server 2019 upgrade.

You may need to check the latest white papers from Microsoft portal if these features are still available.

Always consider not fogetting ipconfig and systeminfo file to be backup before starting the upgrade.

As for the procedure for upgrading , i would say it's a preety much wizard driven process that you don't have to crack your head so much.

For the steps and screen shots for upgrading, you can already get via google search, youtube for those independent people posting it or get it directly from Microsoft itself since you already would have a runtime license.

Applying SAP Maintenance Certificate - SAP Note 1898812 How to Renew a maintenance certificate

As for SAP maintenance certificate are concern it's very important as if you are planning to update and software within SAP landscape and if your maintenance certificate are not updated, their error would pop up in the abap system hence causing issue.

You can easily request maintenace certificate or license key from SAP one launchpad under

Application lifecycle management -> SAP Solution Manager -> Processes 7.2 -> Maintenance certiciate.

The component name of Maintenance certificate in case if you run into issue and you plan to lodge a case with SAP then choose SV-SMG-LIC

Maintenance certificate is just ensuring customers with the right corresponding maintenance agreement are allowed to apply SPAM, SAINT, JSPM and etc..

Remember before you do import or Support packages ensure to apply maintenance certificate others standard error might pop up this is applicable to SPAM/SAINT version 0034.

You might not need to worry if you SAP product is running on SAP Netweaver 7.0 but if its higher then Maintenance certificate is required.

Validity of maintenance certificate is somewhat within 3 months.

As a rule of thumb to checkif you have maintenance certificate just execute t-code SLICENSE and check the New License to see if it displays infor such as Digital -signed License Keys.

Migrating to SAP Hana Database consideration on SAP Netweaver Parameter

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

SAP Business Objects BI Essential components

Do you know the most basic essential component of SAP Business Objects BI is as below.

Reporting.
Data Discovery and Visualization.
Application and Dashboard Building.
Deployment and Administration.

You can also call it centralized suite for reporting dashboard and visualization. While being a BI laters in SAP technology front. It's sophistication makes data to be visualized in a more predominant way.

Of course as I'm writting based on my own experience therefore the below just based on my experience and not from any master guide perhaps it could be a minimum guide from it.

This is just my shortcut of notes performing installation, however you can always google sap public domain sites for more tips and tricks info or guides.

Installation quite straight forward all you need in a minimum is

8GB or more RAM

Disk space of 20GB

CPU around 4 Cores

Windows operating system x64

Java 1.6 or more higher version

Microsoft .Net framwrk and Windows installer all 3.5 higher.

Check your pre-requisite

The press next on welcome screen and accept the license agreement

After which product key required to be entered.

Choose your language - English

I normally choose full installation type

You can select whether to configure and install Sybase SQL Anywhere

You also need to choose the CMS database

You must select Tomcat web application in this case normally it would be TOMCAT 7.0

The configure install subversion

Proceed with SIA - Server intelligence agent

CMS Port info to be entered.

Password for Administrator

Configure sybase sql anywhere

Configure Tomcat

Configure HTTP listening port

Enter subversion repository port number, user account and password.

configure SMD agent for solution manager connectivity

You may choose introscope enterprise manager

Finally Start the installation - it will take a short while till you reach Finish installation.

Post steps

How to find out your SAP Enhance package level

How to find out your SAP Enhance package level

Quick tips

Most of you for sure this would be a perhaps mind blowing tips.

1. How to do you find out your SAP enhance Package level for SAP ECC6

Asnwer : - Login to your SAP -> System Status - > In the list of Support packages Look for module

SAP_APPL - 601 this means 6 is your SAP ECC6 while 01 means Enhance package 1

SAP_APPL - 606 this means 6 is your SAP ECC6 while 01 means Enhance package 6

SAP_APPL - 604 this means 6 is your SAP ECC6 while 01 means Enhance package 4

Hope this helps..

SAP Maintenance Planner, Transaction ID, Push to Download Basket, Download Stack.xml

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

Define change -> Select Files --> Download Files -- > Complete

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.

Niping network diagnosis SAP Note 500235

Niping network diagnosis SAP Note 500235

Basis consultant often feels stuck in a situation when it come to performance issues where user or factory located far away from the central server of the SAP, for instance:-

SAP ECC EHP7 server located in New Zealand DC ( Server)

While user is located in New York Office ( User)

A factory located in France. (Factory)

Basic consultant often blinded by the fact that to look at connectivity and QOS (SAP Network dedicated throughout the corporate network which sometimes termed as quality of service)

Now when P1 raised by the user saying SAP is slow for them, the first thing support will look at are system performance, dev_traces files for any hints, abap dump if its ever generated by users and etc . BUT never the thought comes most of the times to look at network quality.

This is the reason why SAP introduced their own version of ping test which is called NIPING. while niping test is often associated when user connects to the central system through SAProuter.

NIPING is similar to PING and the whole idea is to check if there's any latency in comparison for the particular user connecting to SAP server located remotely.

There are few ways in utilizing NIPING as below

1. Measuring RTT

niping -c -H <nipingsvr> -B 1 -L 100
(The buffersize of 1 may cause an error in other version of niping. If yes please use niping -c -H <nipingsvr> -B 20 -L 100 )

Some examples in using Niping

2. Long LAN stability test:

niping -c -H <nipingsvr> -B 10000 -D 100 -L 360000

The uses 100000 bytes per second of bandwidth (about 10% of a 10 mbps Ethernet) and will last 10 hours as how the parameter works.

3. Long WAN test (idle timeouts):

niping -c -H <nipingsvr> -P -D 3600000

Every hour, this test starts a TCP connection and delivers a test packet (delay of 3600000ms). It lasts for ten hours. The purpose is to see if a "idle timeout" interrupts the TCP connection.

4. Short throughput/stability test:

niping -c -H <nipingsvr> -B 1000000 -L 100

Connection is tested with 100 MB of data as quickly as possible. This should take roughly 10 seconds on a 100 Mbps Ethernet connection.

Maintenance Planner Stack. XML - Please leave comments

Maintenance Planner Stack. XML - Please leave comments

I notice that many might be a expert in planning your xml stacks while those working in operations or handking SAP day to day operation might not even tasted in creating xml stacks ever in their lifes.

I hope those you come by this this particular blogs can share in the comments atleast of some topics related to creation of xml stacks, purpose for, why the intention and etc.

Generally the evolution of Stacks.xml started with making installation and upgrade media available through secure network instead previously it was distributed via disc, CD and other media ( that was the way back then).

The last time around we used to receive CD's from SAP for the collection of product that we were using. After which we safeguard those CD's in a tight locker for security and safety purposes.

As time passes by when internet became more violantly available, SAP came up with loading these installation CD's through website, for me it was interesting, eventough ordering CD was easy by just raising a ticket but getting it online was even better.

Then i knew the comes SAP download Manager where you can park all you downloads and if you get ever intererupted due to network failure, the activity resumes back after and the downloads are intact with the use of SAP download manager.

Its was then SAP start introducing or maybe introduced much earlier, just that i might have realized about Solution manager t-code MOPZ ( Maintenance optimer ) this is used to download your stacks.

To cut it short now through SAP LaunchPad -> SAP has Maintenance planner . Now this is where it get more simpler for integrator, installers, implementers, compared to previously it requires tremendous effort navigatin through MOPZ.

For those whom are experts, maybe share our ideas, how you use this day to day basis, thanks.

How to solve dump LOAD_VERSION_LOST and dump LOAD_PROGRAM_LOST

This has been an issues very common in the SAP Circle where the dumps occurs whenever user_exit being changed or a new program being transported to production system.

Normally the solution is the revert to old program and fix the program if there are quick fix. However there are SAP notes clearly defining steps on how to resolve such issues , another method is to clear the dialog buffer or sometimes of there are no programs changed the always SAP system being restarted instead of wasting enormousness time in resolving such issues.

SAP Note : 2385919 - How to solve dump LOAD_VERSION_LOST and dump LOAD_PROGRAM_LOST

However below are some steps of my own, lets see if it works for you.

You must ensure that the programme load is loaded in the programme buffer before you can run an ABAP programme (PXA).

When you run a programme load, this is locked to prevent it from being relocated from the buffer.

The programme locks may not be kept for extended wait durations because the programme buffer is restricted in capacity (for example, user interaction). As a result, during the deployment, all previously configured locks are freed.

The programme load may be moved from the buffer after a short time if the system works actively on the application server.

If you now alter the programme before the application continues (for example, due of a transport), the database identifies that the programme has changed (the total time stamp is newer) when you reload the programme (RELOAD).

The system prompts the brief dump " LOAD PROGRAM LOST" to avoid inconsistencies when executing the programme (the programme may have changed so significantly that follow-on issues occur).

You must not alter the software that has been terminated.

This can also be caused by changing a dependant object.

The report RSDEPEND can be used to determine when the programme was last created and which change caused the total time stamp to be set. This could be the case, for example, if the DDIC types or programme inclusions used have changed.

Search the RSDEPEND result list for objects with the same or similar time stamp as the total time stamp. This method makes it simple to locate the trigger. These dependent objects were then updated using either a transport or a direct system change.

If the short dump occurs frequently, you should take steps to reduce the likelihood of it happening again.

Increase the programme buffer to prevent any further swaps.

Make sure you only import transports when there is no or a minimal load. Especially in a manufacturing environment.

Instaling Hana Studio - All you need to know the steps

Installing HANA Studio - Fundamental

Hana Studio is one of the easiest tools or interfaces to install let me in your server, desktop, or laptop, today I will share the screenshot that I went through in setting up Hana Studio with ease.

HANA Studio is an Eclipse-based, integrated development environment (IDE) that is used to develop artifacts in a HANA server. 2. It enables technical users to manage the SAP HANA database, create and manage user authorizations, create new or modify existing models of data, and others.

choose hdbsetup.exe

error quite common - but don't worry although the log looks scary but trust me to fix this just make sure you downloaded the right Hana Studio downloads software that's all.

let's continue ( i had error so i downloaded a new set of Hana Studio executables and restarted the setup process and it worked.

Completed - hurray......

Now you can access to you Hana Studio by adding the details of the server as usual.

Hana studio is the base of whatever Hana system that you are touching.

Better start using these features rather than just accessing to SAP NW or SAP ECC that runs on HANA and manage them via SAP T-code.

Below are the installation logs and how it looks like ....

HANA Studio installation Logs – just for reference purposes

22:05:05.636 - INFO: Installing signal handler

22:05:05.636 - INFO: Handler for signal INT

22:05:05.636 - INFO: Handler for signal PIPE

22:05:05.636 - INFO: Handler for signal ABRT

22:05:05.636 - INFO: Handler for signal FPE

22:05:05.636 - INFO: Handler for signal QUIT

22:05:05.636 - INFO: Handler for signal TERM

22:05:05.636 - INFO: ---------------------------------------------------------

22:05:05.636 - INFO: System Information

22:05:05.636 - INFO: ---------------------------------------------------------

22:05:05.637 - INFO: Operating System: Windows

22:05:05.637 - INFO: Architecture : AMD64

22:05:05.637 - INFO: Version : NT 6.3

22:05:05.637 - INFO: Subversion :

22:05:05.637 - INFO: Cpu features : sse sse2 cmpxchg16b

22:05:05.637 - INFO: xxcomputernamexx Name : xxcomputernamexx

22:05:05.637 - INFO: ---------------------------------------------------------

22:05:05.637 - INFO: END: System Info

22:05:05.637 - INFO: ---------------------------------------------------------

22:05:05.637 - INFO: Installer Information

22:05:05.637 - INFO: ---------------------------------------------------------

22:05:05.638 - INFO: Installer is part of installation kit

22:05:05.638 - INFO: Version is 1.2.32 (git hash: 0eafe05e7489)

22:05:05.638 - INFO: GitHash is 0eafe05e7489

22:05:05.638 - INFO: Platform is NTamd64

22:05:05.638 - INFO: Perl version is v5.22.1

22:05:05.638 - INFO: Running as gui application

22:05:05.638 - INFO: Using wxWidgets 3.0.2