Index storage capacity analysis

&

Re-build

Introduction:

Indexes are the vital component in database to search data in most optimal way using filter. By continuous changes in the data due to Insert, Update and Delete operations, the index stored on the database gets fragmented thus increasing Application response time and consuming hardware resources like disk space and CPU. Index rebuild is considered as one of the important activity in performance optimization.

1. Index storage capacity analysis

Execute report RSORAISQ/RSORAISQN through T-code SE38.

Provide any ID to distinguish it from others.

Provide the Index, Table and Tablespace name as shown. (Currently we are analyzing the PSAPSR3 Tablespace so it is provided).

Choose "Start workingset" option with Analyze (Fast) option and execute the report in background.

Check the job status from SM37 --> job name RSORAISQN.

Upon successful completion of job execute the report again. And choose the option “Show History” to get the results.

The report will provide us the list of indexes with their size, storage capacity and other details.

Sort the details in the report by index size and storage capacity and extract the details in sheet.

2. Index Re-build Methods

Method 1: Execute the report RSANAORA (Recommended)

Execute the report RSANAORA.

Select the Index option --> Enter Index names that are to be rebuilt from the extracted sheet.

(To avoid the system load it’s recommended to choose indexes batch wise for rebuild)

After copying the list of Indices through clipboard, select ALTER INDEX REBUILD ONLINE option

Execute the program in Background

This method is recommended as it does the index rebuild by online method.

Method 2: Transaction code – DBACOCKPIT/ DB02OLD

Execute the Transaction Code DB02OLD

Choose the option current sizes

Choose Tables/Indexes option.

Select the index and choose for detailed analysis option.

In the detailed analysis it will show the size of the index which is 192 KB in the current case.

From the menus choose Alter index --> Rebuild

Transaction Code – DBACOCKPIT

Execute the T-code DBACOCKPIT and navigate as space --> segments --> detailed analysis.

From the main screen select the Index.

Main Data tab you can validate / Rebuild index

Storage tab provides the current size and storage quality of selected index

Method 3: Brtools

You can use brtools for rebuild indexes

Launch the brtools by ora<SID> user and choose the following options to traverse.

Method 4: By executing Oracle query

Connect to oracle by

Sqlplus / as sysdba

And execute the query as

Syntax: alter index <tablesapace_name>.<index_name> REBUILD ONLINE

E.g. alter index SAPSR3.CRM_ACE2_OBJ_WL~0 REBUILD ONLINE

3. Result/Observation:

The usable memory capacity of the tablespace is increased. The increased system response time can also be observed.

This can be checked by T-code ST04 --> space --> Tablespace --> Overview.

Before index rebuild:

After index rebuild:

4. Reference Notes:

332677 – Alternatives to rebuild indexes

682926 – Problems with Create/rebuild index with the solutions.

712098 - RSORAISQ: Index Storage Quality Management, in order to fix authorization problem.

In this 2-part document, the steps of a new test server installation via system copy of development system are described. In the first part you find HANA DB installation steps. In the second part you find the SAP System installation steps and some main postprocessing steps. In our scenario, SAP System and HANA DB run on different servers. SAP System is based on NW 7.40.

Main SAP Note : http://service.sap.com/sap/support/notes/1844468

I've downloaded the main guide for the installation with S-User and password via that link: https://websmp104.sap-ag.de/~sapidb/011000358700000877172012E

Then please go through: SAP HANA Database->Unix.

For the filesystems, prerequisites and preparations for the system, you should look at the guide.

Here are main steps and screenshots of database installation on the new server:

• Login with root user to server where HANA DB will run and change directory to the path where HANA Software is located. Then execute ./hdblcmgui in order to start HANA installation interface.

• Local hostname is the hostname of the server where HANA will be located. Provide SID for your HANA DB.

• Check your inputs once again.

For the SAP System installation please see : SAP HANA System copy - part 2/2 (SAP System Installation)

In this 2-part document, the steps of a new test server installation via system copy of development system are described. In the first part you find HANA DB installation steps. In the second part you find the SAP System installation steps and some main postprocessing steps. In our scenario, SAP System and HANA DB run on different servers. SAP System is based on NW 7.40. For the first part (HANA DB Installation) plese see : SAP HANA System copy - part 1/2 (HANA DB Installation)

Main SAP Note : http://service.sap.com/sap/support/notes/1844468

I've downloaded the main guide for the installation with S-User and password via that link: https://websmp104.sap-ag.de/~sapidb/011000358700000877172012E

Then please go through: SAP HANA Database->Unix.

For the filesystems, prerequisites and preparations for the system, you should look at the guide. The latest version of SWPM is strongly recommended.

Here are main steps and screenshots of primary instance installation on the new server:

• Create a backup of the source system via SAP HANA DB Studio.

• Copy the backup files to the target server. The name of the backup will be used as SWPM input.

• SID is the system ID of application server (SAP System). It differs from DB SID. 7.40 Kernel DVD number is 51049350.

• Hostname of the server where HANA DB is installed. Also DB SID and HANA system number (from part 1/2) should be given. All DB-related passwords MUST be same with the source system DB.

• The name of the source system's backup. And the location where the backup files have been moved in the first step above.

• Latest kernel DVD has been downloaded and pointed to SWPM, in order to save time and effort. So we don't need to patch default SWPM kernel.

• Check your inputs once again and execute the installation.

• ERROR DURING INSTALLATION and SOLUTION

Root cause was unsuccessful connection attempt to the database. The reason was that ".KEY" and ".DAT" files had not been created properly. R3trans -d testing was also unsuccessful.

sapinst_dev.log

WARNING 2016-04-04 17:34:57.434 (root/sapinst) id=modlib.jslib.childAppReturn

Execution of the command "/usr/sap/SID/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSSN_HOST -install_first_temp N1211111111 XXXXXX" finished with return code 2. Output:

saplikey: failed to connect to the database.

ERROR 2016-04-04 17:34:57.436 (root/sapinst) id=nw.processError errno=CJS-30023

Process call '/usr/sap/SID/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSSN_HOST -install_first_temp N1111111 XXXXXX' exits with error code 2. For details see log file(s) saplikey.log, dev_slic.

ERROR 2016-04-04 17:34:57.583 (root/sapinst) id=controller.stepExecuted errno=FCO-00011

The step createTempLicense with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_Temp_License_ABAP|ind|ind|ind|ind|lic|0|createTempLicense was executed with

status ERROR ( Last error reported by the step: Process call '/usr/sap/SID/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSSN_HOST -install_first_temp N111111111 XXXXXX' exits with error code 2. For details

see log file(s) saplikey.log, dev_slic.).

SOLUTION

The hdbuserstorelist command should give the following outputs on the servers where SAP Instance and HANA DB are installed:

<DB_HOST>:HDB:<DB_SID>adm /usr/sap/<DB_SID>/HDB<HANA_SN>> hdbuserstore set SYSTEM <DB_HOST>:3<HANA_SN>15 SYSTEM <PASSWORD>

<DB_HOST>:HDB:khqadm /usr/sap/<DB_SID>/HDB<HANA_SN>> hdbuserstore list

DATA FILE       : /home/khqadm/.hdb/<DB_SID>/SSFS_HDB.DAT

KEY FILE        : /home/khqadm/.hdb/<DB_SID>/SSFS_HDB.KEY

KEY DEFAULT

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SAPSR3

KEY SYSTEM

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SYSTEM

<PAS_HOST>:SAPSIDadm> hdbuserstore set SYSTEM <PAS_HOST>:3<HANA_SN>15 SYSTEM <PASSWORD>

<PAS_HOST>:SAPSIDadm> hdbuserstore list

DATA FILE       : /home/DBSIDadm/.hdb/PAS_HOST/SSFS_HDB.DAT

KEY FILE        : /home/DBSIDadm/.hdb/PAS_HOST/SSFS_HDB.KEY

KEY DEFAULT

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SAPSR3

KEY SYSTEM

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SYSTEM

• After successful installation, install SAP HANA License via SAP HANA DB Studio. Right click DB there and select properties->licenses. License key is requested from service.sap.com.

• Post system copy steps can be checked from the guide.

Hi All,

Most of the times we face this error message in the Web dispatcher trace file (dev_webdisp) stating that connection to message server is not possible.

There are different reasons for this to occur. Most of the times the issue is occurring because of wrong configuration of the message server port in the Web Dispatcher port.

We can configure the parameter related to message server port HTTP(S) in the Web Dispatcher host profile.

The concerned parameter is => ms/server_port_xx: The port on which the message server receives HTTP requests

The common entries occurring the trace file looks like:

*** ERROR => Connection request from (-1/65535/0) to host: <message server hostname>, service: <message server port> failed (NIECONN_REFUSED) {001d7388} [icxxconn.c 2712]

*** ERROR => IcmConnClientRqCreate() failed (rc=-8) [icrxx.c 6910]

*** ERROR => Could not connect to SAP Message Server at <message server host> URL=/msgserver/text/logon?version=1.2 [icrxx.c 3870]

*** ERROR => rc=-1, HTTP response code: 0 [icrxx.c 3871]

These entries show us that web dispatcher is not able to connect to message server on the http port.

To check this we have one solution to do.

We can check the connectivity of the backend message server's http port by using simple telnet command.

How to check the connectivity using telnet ?

You can check this by using

telnet <message server hostname> <message server port>

where message server port would be ms/server_port_xx which you have maintained in Web Dispatcher profile.

You should be able to successfully test telnet command. The result would be something like :

telnet <msg server hostname> <msg server port>

trying to connect ..

connected successfully..

If you are not able to see successful connectivity of the telnet test then you need to configure the ms/server_port_xx  in the Web dispatcher profile.

Post this again check the connectivity.

We were performing SAP Installtion for a new Project and during the Target system installation using SYSTEM COPY method I was facing below error

Not sufficient space is available on drive.  xxx MB are required, only yyy MB are free.

SOLUTION: Provide enough space

We created eight different mount points and made sure we had enough spaces on all the mount pounts but SAPinst was still throwing the error.

How to resolve the error in SAPInst?

The error in SAPInst is cause by the SAP Installer checking the freespace on the Mount Point Root Disk and not on the individual Mounted Disks.

There are two easy solutions to this problem:

1.     Create the Database manually before starting SAPInst using the script below – SAPInst will bypass this screen and install

2.     Set the size of the Database to something very small (such as 1GB) and the installer will continue.  SQL Server Data Files will grow automatically during the installation or you can manually increase them (ensure Note 1238993 is implemented).

We followed option 2 and everything went fine.

SAP on SQL Installation on Mount Points | Running SAP Applications on the Microsoft Platform

In My Project we have multiple Bolton system so i want to consolidate  the same in this article

Download the SAP media required to install/update HANA DB and copy it on the HANA server.

Navigate to the path of the media on the server and run the hdblcm . It will detect existing instances of HANA DB if any .

From the below screen , you can update an existing HANA system or install a new instances of HANA DB.

In this case , we are installing a new system . So we choose the relevant option(7) .

If you want to get a gui screen instead of a command line , you can use tools like xclock .In this case , we have used xclock to get the gui screen.

Click next.

Choose Install new system and click on next

Review the summary page and click on next if all looks ok.

Use the HANA Studio to connect to the installed HANA DB.

We were performing EHP7 SP11 upgrade for our landscape. CRM, EP, PI, ADS all went fine. However in our ECC system in MAIN_POSTPROC/JOB_RASUVAR2 phase the job RASUVAR2 was running too long and the system was giving dump "DYN_IMEX_OBJ_NAME_EMPTY" for different components. When we checked the job status it was running but it seems that it was actually doing nothing.

Resolution

Upon searrching we found SAP Note 2294892 - Many dumps DYN_IMEX_OBJ_NAME_EMPTY during upgrade which describes the exact scenario.

• The program RASUVAR_FINISH is executed to convert the variants. It checks whether all selection variants for the programs which were previously saved in the table TASUVAR1 can still be read (further restriction of RASUVAR_FINISH is possible on the selection screen). If a variant can no longer be read, an attempt is made to read the variant values using the information from the table TASUVAR1 and to convert them to the current fields of the selection screen.
• After the variant restorer performs the conversion (RASUVAR2 or RASUVAR_FINISH, that is, after the upgrade), use transactions SE38 or SA38 to execute the program RASUVAR_DETECT manually. It then checks the reports and the variants, and compares the results with the information contained in the table TASUVAR1. It is therefore necessary for this information (that was created before the upgrade) to remain available.

So we followed below steps to move ahead.

1) Cancel the execution of RASUVAR2 from SM37.

2) Stop SUM

3) Import the transport E4AK273146 as per SAP Note 160685 - Using the ASU variant restorer outside of the technical upgrade

4) Execute the RASUVAR_FINISH in a batch job with the default parameters

Wait for the job to be finished. It  took 1805 seconds in our case.

5) As per SAP Note 1052664 - Performance during Uppgrade - JOB_RASUVAR2, the JOB_RASUVAR2 can be canceled during the upgrade. Normally we can ignore the phase without being asked for a password. In case SAPup requires a password for the next phase, please check which toolversion of SAPup you are using (this can be found in SAPup.log).Depending on the toolversion, the next phase differs.

We were using below SAPup version so we used the password 55238 as described in the note ( <SUM Location>\SUM\abap\log\SAPup.log)

# ************************* SAPup started in PREPARE mode *************************

# This is SAPup release lmt_005 version 54.000 compile time 20:03:28 Nov 29 2015.

6) Stop SAPup Process using below command

7) Exit SAPup and call SAPup again with option "allowJump=always"

    Click on Execute.

8) Now it asks for the next pahse and the password.

9) Provide the phase name and passowrd carefully depending upon the SAPup version

10) Now select "End single step mode and continue to the next breakpoint"

11) Continue the upgrade

12) Use the pool log file generated by the program RASUVAR_FINISH to analyze the Variant issue and get them fixed after the upgrade.

Reference

2294892 - Many dumps DYN_IMEX_OBJ_NAME_EMPTY during upgrade

1052664 - Performance during Uppgrade - JOB_RASUVAR2

160685 - Using the ASU variant restorer outside of the technical upgrade

1384051 - ASU variant restorer: Consistency check after upgrade

Kernel upgrade from release 700 to 7.21

SAP system environment

SAP ECC 6 NW 7.00 SP 21 on IBM i(OS / DB V7R1).

Kernel Upgrade Steps on IBM I

1. Stop the SAP instance, SAPOSCOL, CCMS

2.  Create the two folder in ‘rootbin’ share (Example folder names SAPK7x (SAP kernel files SAPEXE.sar,SAPEXEDB.sar,IGSEXE.sar & IGhelper.sar) & SAPILE (ILE.sar & ilrtools)

3. Add the 'ALLOBJ' authority in SIDADM user as mention below screenshot

4.  Create the new library using the SAP SIDADM user id  “CRTLIB SAP_TOOLS”  

5. Change the current folder name to ILE folder (For example SAPILE” CHGCURDIR /SAPILE”), and then add the library to SIDADM user

“ Addlible SAP_TOOLS"

6. First unpack the ILE.SAR & then SAP kernels sar files

            6.1   -  CALL QP2SHELL PARM('/QOpenSys/usr/bin/csh' '-c' 'SAPCAR -xvf ILE.SAR iletools ILE_TOOLS; ./iletools')

            6.2 -   CALL QP2SHELL PARM('/QOpenSys/usr/bin/csh' '-c' 'SAPCAR -xvf SAPEXE.SAR iletools ILE_TOOLS; ./iletools')

            6.3 -  Check the SAP_TOOLS library after unpack you may find all kernel objects

7.   Set the authorities of the objects in SAP_TOOLS by these commands

If you’re starting kernel is already running with the 'newuserconcept' set:

ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('N')

ADDLIBLE  SAP_TOOLS

FIXSAPOWN *NONE SAP_TOOLS

If you’re starting kernel is still running with the 'classicuserconcept' set:

ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')

ADDLIBLE  SAP_TOOLS

FIXSAPOWN *NONE SAP_TOOLS

NOTE: You can check the user concept in SIDADM user environment variable using the command “WRKENVVAR LEVEL(*JOB)”

8.  Apply the kernel new kernel, from the kernel sar files copied in to /SAPK7x/*

APYSIDKRN SID(<SAPSID>) ARCHIVES('/SAPK7x/*') SAVSAR(*NONE) MODE(*FULLY) CHGENV(*NO) UPDAPAR(*NO)

During the process you may get the below message Just reply ‘Y’

Kernel upgrade completed then check the log kernel apply log in \rootbin\sapmnt\PEC\patches\log\apysidkrn*.log

9.  Delete the SAP ABAP database Sql packages, From the SAP SIDADM user option number 4. SAP Database– select option number 5

10. In stratup profile remove the parameter “Start_Program_06 = local $(DIR_EXECUTABLE)/DLTOLDPKGS SID”

          Add the parameter in Instance profile - dbs/db4/dltoldpkg = no

11. Logoff & logon SIDADM  Start the SAP Instance with  new kernel,

12.  Only necessary for a dual-stack system: you must set the following parameter in the default system profile DEFAULT.PFL:

     system/type = DS

      For dual-Stack and Java-only systems: in all (Dnn, DVEBMGSnn, Jnn, JCnn etc.) instance profiles, you must set the following parameter:

        FN_JSTART = jcontrol$(FT_EXE

13 . Due to the situation described in note 1517379, you have to set the following instance profile parameter

          rslg/new_layout = 9

14. Implement the SAP Note 1610716 for correction in the finds and rectifies the inconsistencies alignment and transaction code SM66

15. The 720 and 721 kernel versions support the dynamic increase of the number of work processes at runtime. However, this function is not fully compatible         with NW 7.00 and NW 7.01. To prevent errors from occurring, deactivate it by setting the following parameters: in instance Profile

   rdisp/wp_no_restricted = 0

   rdisp/configurable_wp_no = 0

   rdisp/dynamic_wp_check = FALSE

   rdisp/wp_max_no = Sum of:( rdisp/wp_no_dia + rdisp/wp_no_vb2 + rdisp/wp_no_btc + rdisp/wp_no_vb + rdisp/wp_no_spo + rdisp/wp_no_enq )

   rdisp/del_triv_joblog = 0

   Refer the SAP note 1882691 prevent errors while displaying the job logs

16.  Refer the SAP Note 1097997 to install the New RFC SDK on System i

17. Finally execute the SGEN on IBM-I system. If you are having any Application servers based on the OS you have upgrade the kernel and then run the SGEN

18. After completed the kernel upgrade, Remove the 'ALLOBJ' authority in SIDADM user id refer the point number 3.

Note References for IBMi Kernel upgrade

1097751 - iSeries: Information and recommendations for kernel libraries

1716826 - Usage of the downward compatible kernel 721 (EXT)

1882691 - 7.21 kernel: Job log cannot be displayed

1610716 - Correcting runtime objects with the wrong alignment

1468596 - Trivial job logs are automatically deleted

1657890 - IBM i: STARTSAP calling DLTOLDPKG via instance profile

1713986 - Installation of kernel 721 (EXT)

1097997 - Installing SAP NW RFC SDK on System i

1581595 - rfcexec or startrfc fail after upgrade

1025361 - Installation, Support and Availability of the SAP NetWeaver RFC Library

19466    - Downloading SAP kernel patches

1. Go to respective system.

2. T CODE : SXMB_MONI.

3. click on --> monitor for processed xml messages.

4. Tab go to --> Advanced selection criteria.

5. put message id = _________________

6. execute.

7. Tab Edit --> cancel message with errors.

8. Refresh.

     Here I will try to give a explanation on what, how to generate the SAP Users license Usage during the year-cycle. Here I will try to demonstrate via a Single Development & Production System to do the job. Hope this document makes the newbie a lot more easier because I have spoken with a lot people who fear if something happens & SAPLabs ask for a Fine/Charges if not followed the correct procedure. So here is my document for the person who are newer & fearful in this matter.

Note: Java & Portal applications can not be measured through LAW Tool.

So, we will Login to development system 1st through GUI & generate report & we will combine later on that in production system & send it through the production system system as we are not using any SOLMAN System for that. Basically you can collate the reports in SOLMAN or any ABAP system, does not have to be the Central or Satellite System here.

1st we will login to ABAP development system, through GUI.

Login to Development SAP using the active-client which is set to send the reports of the Users, will show where it is configured also later on.

Enter t-code USMM as show in the below pic.

Observe the scenarios here.

Here Date shows when the last system measurement ran. Data not Released means it is saying the report(License Audit) which was generated or combined was not sent to SAP till now.

Also we have to maintain the development system marked in t-code SCC4 as follows:-

Here C Customizing means it can be used as the development system. Now in USMM->

This is where it is showing like that as we are giving to SAPLabs that our developments are happening in .... client only & hence the license report goes for development history of ... client.

Here are the kind of users that license report we sending to SAP according to how we are entitle/licensed to use these kind of users License only. According to the license Strength :-

Now in User classification area of the above screenshot:-

Here only ABAP user id is converted in to developer  user id & the rest as Test as we are going to combine this result with the PROD system. Go back again then,

Now Press the System measurement Button here.

Now in here(Measurement Statistics), it shows the measurement task progress state.

After it is completed here, say after 10-20 minutes, execute as below,

Here press the execute button as shown below & save the License Audit file of this Development System as LicenseSID.txt in your preferred location, generally is goes in your My Documents-> SAP -> SAP GUI -> as that is the temporary location of your SAP document saves.

To get the License report on how it will reflect, you can have a preview by generating the License PDF file as below by clicking on the Log Button as shown below

Now we can go for Prod1 login as we are sending through the SAP Central Instance Installation prod1 or the production system if it is a Central Installation for the Prod server SAP.

In USMM-> In User Classification- We have to compare the licensed user list numbers with the list of End User license Agreement license nos. & need to manage & manipulate if required

  Then in USMM-> System Measurement-> Once completed in Measurement Statistics or say this WorkBench User Classification is coming or need to see manually if any inconsistency of any no of users are coming then need to swap the user license type with some other less used SAP User Ids but always maintain the no & type of license of SAP Users provided by SAP. And then again run the System measurement to see this area is fine till  now.

Basically here the top hit or multiple login users hit in total showing should not in total the amount mentioned by SAP at times of purchase of License Agreement or can ask any time SAPLabs for that also. If the total amount here crosses then SAP will ask for Fine/charges.

In my case, top multiple login hits are as below,

After all this & running in the System Measurement & everything is OK & no workbench users issue & it will say some users considered as TEST & some other users as per the license agreement,  similarly will save like in development system here save file as License< Production SID >.txt

Then run t-code SLAW in Prod system as below because now we are going to combine/merge the reports of Development & Prod in a single file,

Here we can upload the template(.xml file) given by SAP & upload all the req systems License report or here in you may just leave as it is if no new SAP system launched since last year & just make a reply mail by saying that other systems we are not using. If want to upload the .xml file then, as below Change view-> Maintain RFC Data

Then save the .xml file sent from SAPLabs to your desktop & as follows click on the open button to browse to the .xml template & click open & it will show what & all the systems are required to be measured as per SAPLabs & whatever systems License data you will not be sending to SAPLabs , you can just select the column & press the delete button as follows,

So now here your job is to combine the license reports of License< Development SID >.txt & License< Production SID >.txt. To do so, click as follows,

Then similarly,

Once both the system License file uploaded , it is showing green as below,

Remember that when you upload any1 license file also, it will show green. But as we are suppossed to send after combining all the systems report into 1 system report not to send report of individual system, so we better here should upload both the files at a time, & then press 2nd option Combined Users option button as below,

Once turned green as below, will go for the 3rd option to Consolidate data like below,

Once the job is completed here & turned green as below,

Now it is time to send SAP all the results. For that we can press here 4th option "Send Results" Button

Or in USMM t-code "Send to SAP Button" is there to send to SAP. Now say in case SAP is not getting this online transfer, we need to download in e-mail format, that is "Download in SDCC(N) format" as below & send to SAPLabs via writing a mail to SAP. For safe side we will generate both the files as shown below & send to SAPlabs via e-mail with writing reasons why the other systems or portals License reports like Un-used or Not-Available systems license reports we are not generating & sending to SAP

For online transfer to SAP we can also use the below option/process.

Thanks for the patience of watching & following to avoid any issues from SAPLabs side.

After doing all these activities & after some days, if you click as below, can see the status of this License report transfer to SAP as below,

Also in addition for safe side can call SAP License office for the report received & everything is OK mail to feel yourself safe after a few days after sending the license report mail & online transfer.

AT LAST MANY MANY THANKS FOR GOING THROUGH THE ENTIRE DOCUMENT. Hope it helps the Newbies to make their job much more easier.

I am open to suggestions & Comments. So Friends, Please fell free.

With Regards,

Kaushik Debnath

Hi Dear ones,

SAP Basis Consultants manage lot of Operating system level commands, some major commands i listed here.

hope it helps you,

Regards,

Sajmal TS