TRFC Hanging queues in SMQ1 and SMQ2

To monitor the outbound queues start SMQ1, the inbound queues can be monitored using SMQ2
SMQ1

SMQ2

1. Select all appearing queues and select details.

2. At the top a failed LUW (message) will appear.

3. Execute that LUW again using the menu item Execute LUW.

4. The messages will be reprocessed now.


Transactional RFC

Start transaction code SM58.

Transactional RFC related checks and maintenance can be done using SM58 transaction code

Sometimes, in real time scenario you can face following issues :

i) Process chain related performance issues in BIW system due to transactional RFCs stuck in R3 system.

ii) Idocs flow not happening from R/3 to XI system

In these scenarios, SM58 transaction code will be useful to find out stuck tRFCs and action them accordingly.

Please login into SAP system and use SM58 as shown below

Using SM58, we can select TRFCs based on

i) Any 2 dates

ii) User id

iii) Function of TRFC

iv) TRFC Destination

v) TRFC Status

If you would like to list all, then use * as input in these fields

Remove the user name and press execute.

1. At the top a failed LUW (logical unit of work) will appear which has an error text marked with a red background.

2. Execute that LUW again by selecting the line item and using the menu item Execute LUW.

3. The messages will be reprocessed now.

NOTE: If there is no error shown but the queue is still stopped try Edit > Reset status to reset the status of the queue.

Changing IP address in SAP systems

Internally, SAP systems use host names to communicate. As a result, you should experience no problems when you change an IP address.


Theoretically, you only need to make changes at operating system level:

- /etc/hosts

- /etc/services

- DNS entries

- Routing tables

However, you should err on the side of caution and check the following in the SAP system:

- Transaction SM59, table RFCDES, also see Note 88346 for additional information

- Transaction SM55, if you are using IP addresses here, you must adjust them

- Transaction SM51, check for consistent host names

- Transaction SMLG, check whether the entries for the server groups have been created with IP addresses

Also ensure that changes are not only made in the affected system but in all SAP systems, clients, and external programs that communicate with the affected system in any way.

Outside the SAP system:

- saprouter, adjust the saprouttab to the changes

* If the saprouter receives a new address:

You should inform SAP on  this change (for sapserv3).

Open a message on the 'xx-ser-net-chg' component and inform us of the address change.

- Adjust the IP addresses so that the service connection continues to function

- If you use an APO system, see Note 154997

Depending on your system landscape and configuration, additional relevant points may be added.

JSPM – Java Support Pack Manager

Check whether the used JDK version and the Java VM settings of the Java runtime system comply with  the requirements in the SAP Note 723909. Update the JDK and adjust the settings if necessary. You can update all software components of SAP products that are deployed on the system by applying a support package stack. Support package stacks are defined by SAP collections of support packages for software components that work best together. In addition, you can apply a support package stack, which contains newer versions of SAP software components that have been modified in the NWDI

Before you can apply a support package stack of a given level, you have to update JSPM to the same level by applying it as a single support package The update of JSPM does not require a restart of the J2EE Engine and does not affect the system operation. If the stack is produced for this system by the Maintenance Optimizer, this option will: upgrade with the included components all components that are already deployed on the system to a higher release or to the same release but a higher support/patch level install new components if there are any in the support package stack.

Prerequisites

The settings of your system are according to note 723909.

The SAP NetWeaver Application Server Java (AS Java) and the database have been backed upDirectories and files have not been deleted, renamed, or created in the following directories and their subdirectories: /usr/sap//SYS/exe and /usr/sap//SYS/profile. Otherwise, JSPM cannot detect the kernel and the system profiles, and cannot be started. If a backup of the kernel and the system profiles has been required, it has been created in a different directory.

If your database is MaxDB, the overwrite mode for the log area has been set

The support package stack you want to apply and the corresponding stack definition XML file have been downloaded to the global EPS inbox directory /usr/sap/trans/EPS/in. For more information about SAP products, see SAP Service Marketplace at service.sap.com/sp-stacks.

If the support package stack you want to apply includes the Enterprise Portal, the SDM timeout for the automatic start/stop of the J2EE Engine has been increased to 2 hours.

The adm user has Read permissions for the global EPS inbox directory /usr/sap/trans/EPS/in.

The database and the SDM repository have been synchronized.

There is enough disk space..

Maintenance Optimizer and Support package definition file creation

More information at help.sap.com ® SAP Solutions ® SAP Solution Manager ® select a language ® Change Management ® Maintenance Optimizer

Download the support package stack with all the usage types that need to be updated and the Support Package Stack definition file.

Note: The Support package definition file can be created as follows:

After adding the support package stack in the download basket, you can choose the option to “save in a file”. Right click on the option tab and save as XML file. You can also save it as a CSV file. You can also find more details in SAP Note 884537

Copy the downloaded Support Package files and the definition file (XML file) to the JSPM inbox. [:\\usr\sap\trans\EPS\in]

Note: There must be one and half times as much disk space available as the SP files to be deployed in the JSPM inbox for temporary file transfer by SDM.

To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available disk space during the update process, you can change the file transfer directory of SDM in a system by using the following commands:

cd StopServer.bat

sdm.bat jstartup "mode=standalone" sdm.bat filetransferdir "dir=" sdm.bat jstartup "mode=integrated" StartServer.bat

Check whether the used JDK version and the Java VM settings of the Java runtime system comply with the requirements in the SAP Note 723909. Update the JDK and adjust the settings if necessary.

Solution Manager EarlyWatch Alert Setup for ABAP Systems

EarlyWatch Alert generation is a service provided by the SAP Solution Manager that provides technical insight in the operation of SAP systems. It uses general recommendations and KPI from SAP to determine the health of the SAP system. Focus is mostly on measuring the capacity of the system and showing possible issues that might jeopardize operation in the future.

EarlyWatch Alert generation has to be configured before related functionality such as Service Level Reporting can be used. This document describes the configuration of EarlyWatch Alerts for ABAP systems only.

Pre-requisites

To perform the steps as indicated in this document, the following pre-requisites have to be fulfilled.

• Solution Manager 4 basic configuration has been performed (see reference IMG)

• The system for which the EarlyWatch Alert are to be generated it connected to the Solution Manager as per my previous blog posting ‘Attach SAP System to Solution Manager’( http://sapbasistechnical.blogspot.in/2012/05/sap-basis-technical-attach-sap-system.html )

• On the system for which EarlyWatch Alert generation is to be configured, the latest ST-PI and ST- A/PI have to be installed

• Service connection from the system for which EarlyWatch Alert is to be created to SAP has to be configured (i.e. transaction OSS1 has to be configured).

Choose the ‘Call Service Data Control Center’ button. This logs on to the remote system and launches transaction SDCCN there

Choose ‘Yes’.

Choose ‘Yes’.
The settings for the preparation tool are shown

The default values are fine. Choose ‘Save’.

Note: all items should be green. Note 69455 might be red, but that is easily fixed. Choose the button

‘Addons & Upgr’

Choose ‘Procedure after addon implementation’ 

Now the ‘After impl’ is green too. Choose ‘OK’ to continue.

Now, all items should be green. If it does, leave the screen and choose ‘Yes’ on the following pop-up

Schedule regular retrieval of sessions

 

The system for which Early Watch Alert reports should be created, will have to check at the Solution Manager for new reports to generate daily. For this, a task will be scheduled. From the menu choose ‘Task’ --> ‘Create’.

From the menu choose ‘Task’ --> ‘Create’

Double-click ‘Refresh sessions’.

Choose the RFC connection to the Solution Manager as the ‘Target RFC Destination’. Also, click the

‘Run Task Periodically’ button. This will make the task run daily. If no RFC destination to the Solution Manager is shown, proceed as shown in the appendix in sections 3.3. Note: you can choose any start time.

In principle, the configuration of Early Watch Alert reports is now done. However, it is wise to try and generate a report manually at this time.

Manually create an EarlyWatch Alert report

Log on to the Solution Manager and call transaction SOLUTION_MANAGER. Choose the landscape containing the system for which EWA needs to be created. Go to ‘Operations’  ‘Solution Monitoring’ ‘Early Watch Alert’.

Choose ‘Create Service’.

Choose the system the system for which the EWA needs to be created. Choose ‘Create’.

Choose ‘Task’  ‘Create’

 
 
 
 
 
 
 
 
 
 
 
 
 
 
Double-click ‘Refresh sessions’
 

Choose to schedule ‘Now’. Also, choose the RFC connection to the Solution Manager system as the

Target RFC destination. Choose ‘Continue’

That’s nice. Now, choose ‘Continue’.

The task is scheduled to start. Choose ‘Refresh’ to update the status. Once it is done, automatically EWA entries are created.

Start EWA data collection manually

The new EWA is added to the task list. Click the SAP Early Watch Alert link.

Choose the ‘Call Service Data Control Center’ button. This logs on to the remote system and launches transaction SDCCN there

Refresh sessions

Start EWA data collection manually

These services will run periodically. However, to check the creation of EWA, creation of an EWA will be triggered immediately. Choose the first row with an EarlyWatch Alert task. Then choose ‘Edit’ ‘Start now’

Appendix: add the Solution Manager RFC to the SDCCN

From transaction SDCCN, choose ‘Goto’ --> ‘Settings’ --> ‘Task-Specific’

Click on the table button in the ‘RFC Destinations’ section.

No RFC destinations are shown. Go to change mode and click the ‘Add RFC destination’ button.

Give the RFC destination a name and choose the RFC connection to the Solution Manager.

The RFC destination is now shown in the list. Now, set it as the master system, so it will be default for all manually created sessions. Click the ‘Set Master SAP Solution Manager system’ button.

Choose the RFC connection to Solution Manager as the Destination.

The Solution Manager can now be accessed from SDCCN. Click OK to continue.

Optional: Automatic sending of reports by e- mail

Prerequisite

The task has started execution. Note it might run for 30-60 minutes!

When it is done, it will be removed from the ‘To do’ tab. Choose ‘Back’ to leave the satellite system. Choose ‘Back’ again to see the list of EWA services in the Solution Manager

Start processing of received data manually

In the overview of EWA tasks, a new entry is created. This entry means that data has been received from the system and is ready to be processed. Click this entry

The processing of the received data will also start automatically at some point in time. But for testing purposes, the processing will be triggered manually. Choose ‘Start service processing’.

Choose ‘OK’ to continue.

The processing will run for some time. When it is done, the icon before the Early Watch Alert will change to a value indicating it’s status. The yellow icon means that issues were found in the EWA. Choose the Word icon to view the EWA.

SAP Kernal upgrade on Linux Step by Step

 I am doing SAP Kernel upgrade on Net weaver 7.3 version.

Login to sap system and click on system status button will show the below screen. You can your current Kernel patch lever with your OS and Data base versions.

My current versions:

Kernel release 720

Current version 70

Database name MaxDB 7.7

Operating system Linux 2.6

 

 I logged into service market place, there go to Software Downloads SAP Software Download Center  My company’s Application components  Complementary Software  SAP KERNEL 64-Bit Unicode  SAP KERNEL 7.20 64-BIT UNICODE


Here you need to select your OS and Database, than it displays below screen. Please check the latest version (N) and always better to go for N-1 version

 

 As per my selection criteria 201 is the latest one, I am going for (N-1) 120 version
Please select the SAPEXEDB_120_10007264 this file
To Software Downloads SAP Software Download Center  My company’s Application components  Complementary Software  SAP KERNEL 64-Bit Unicode  SAP KERNEL 7.20 64-BIT UNICODE MAXDB  SAPEXEDB_120_10007264.SAR file and add to download basket

Please select the SAPEXE_120_10007264 this file


to Software Downloads SAP Software Download Center  My company’s Application components  Complementary Software  SAP KERNEL 64-Bit Unicode  SAP KERNEL 7.20 64-BIT UNICODE Database Independent  SAPEXE_120_10007264.SAR file and add to download basket

For kernel upgrade this below two SAR file required. Please download these two files.  

I am downloading  above two SAR files using download manager.

Login as SIDADM, Make new backup directory

mkdir SID_Kernalbackup_24052012

Create latest kernel backup

cp -pr /usr/sap/SID/DVE*/exe/* / SID_Kernalbackup_24052012

Compare the original kernel and the backup

du -sk /usr/sap/SID/DVE*/exe

du -sk /uar/sap/SID/SID_Kernalbackup_24052012

 

Make new shadow kernel directory,

mkdir SID_NewKernal_120_24052012

Copy the new downloaded kernel files into SID_NewKernal_120_24052012 directory

Unpack the new downloaded kernel in folder / SID_NewKernal_120_24052012

SAPCAR -xvf SAPEXE_120-10007264.SAR

SAPCAR -xvf SAPEXEDB_120-10007262.SAR

Login as sidadm

Stop the SAP System

stopsap
Stop saposcol
saposcol -k

Login as root


Go to the current kernel directory

cd /usr/sap/SID/DVE*/exe

Copy all extracted support packages into this folder

cp -pr / SID_NewKernal_120_24052012/* /usr/sap/SID/DVE*/exe/*

Go tCopy back the original file saproot.sh into this folder.

cd /usr/sap/SID/DVE*/exe

login as sidadm

Start the saposcol service

saposcol

Start the SAP system

startsap