SAP Diagnostics Agent disconnect from Solution Manager 7.2

if you are facing issue where all DIA agents are getting disconnected from Solution Manager 7.2 due to error “Exception occurred” or “Processing RMI-P4 request failed. There are no resources to handle the request”. This means there are no more P4 threads are free to handle the request.

This issue is usually occurred in big landscape where more then 600-700 DIA agents are there.

P4 thread usage can be monitor via below method –

telnet localhost 5instance_number08
add p4
p4info

If the displayed value of the “Thread usage” stays at 100% for several minutes so there is an requirement to adjust/increase the threads/queue.

P4 Thread & Queue request size can be calculate as per below Blog –

https://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+7.2+Troubleshooting#DiagnosticsAgent7.2Troubleshooting-scalability

Section – Connectivity Instability in Huge Landscapes – Quick Sizer Tool

There is an attached excel document which give you the correct parameters details as per DIA agents numbers.update the same in your landscape & restart the Java Instance.

References –

https://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+7.2+Troubleshooting#DiagnosticsAgent7.2Troubleshooting-scalability

SAP Note – 2370752 – Diagnostics Agents do not connect to SAP Solution Manager 7.2 due to error in the Default Trace ”Processing RMI-P4 request failed. There are no resources to handle the request.”

SAP also recommend to update the LM-SERVICE patch to latest one to avoid the disconnection issue & also implement Lightweight Ping note as below –

2599110 – Lightweight Ping

2574270 – LM-SERVICE 7.20 SP06 Patch 2

2599110 – LM Service Patch Update

SAP – Unable to create new native thread

Whenever you face this issue in ABAP or JAVA system where your system is not starting up & dumping out by error “unable to create new native thread”.

Please crosscheck the below OS values, this should be set to high/unlimited.

My Suggestion is below –

For Linux – limits or csh -c limits

maxproc – unlimited
descriptors – 65536
stacksize – 32768

after changing these values restart the application server & check.

for More information, follow below SAP notes –

1827960 – Adjusting operating system limits for SAP instances
1847508 – Unable to create new native threadVersion 5 from 26.09.2018 in Eng
1496410 – Red Hat Enterprise Linux 6.x: Installation and Upgrade

SAP – RSTBPDEL – Delete Table Logs

Hi All,

RSTBPDEL is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). This report deletes change documents from the table log database. if you are facing issue while deleting the table logs (job completed successfully but no reduction in DB or table logs) as per SAP note – 2388295 – RSTBPDEL | Delete logs periodically.

SAP released another note for resolving this issue – 2634844 – Deletion program RSTBPDEL not deleting data of table logs.

This note need to implement via SNOTE in all the impacted systems & this will also introduce a new authorization object. Once SAP note has been implemented re trigger the job again & see the difference now.

SAP S4 HANA 1809 Release

SAP has released the S4HANA 1809 for their customers.

There are many blogs which are explaining the features of new version.

The best thing what I have seen is from SAP is the tutorial Library & repository for 1809 version. it’s very much beneficial for new & existing S4 HANA users as it’s providing the examples of multiple technical & functional activities.

Click below for access the URL

https://education.hana.ondemand.com/education/pub/s4/index.html#group!GR_D80CA75852B82A9D”>https://education.hana.ondemand.com/education/pub/s4/index.html#group!GR_D80CA75852B82A9D

SAP S4HANA – Define Background Job – Job Repository

Hi All,

Recently while working on Background Job Management for SAP Netweaver 751 for S4HANA, we discovered that there is a small change in Background Job Scheduling via SM36- Job Repository (Technical Job Repository) or SJOBREPO Tx.

The change is if you have scheduled any background job via Job Repository then you only can change the status (Scheduled/Remove) of that particular job from Job Repository only.

for Example – SAP_REORG_APPLJOBS – if you have activated this job via Job Repository then making changes of this job directly in SM37 will not work, like variant change, release to schedule status or remove. if you perform any action directly in SM37 then this change happen for the time but again after some minute the job will reappear with the release status as it’s still active in Job Repository.

if you change the variant directly in SM37 then there will be 2 job will appear, 1 is with New Variant & 2 is old default variant.

The last option for stopping this job permanently via SM36 – Job Repository – Select the Job & Click Deactivate Technical Job Definition Locally.

Once you perform this action the default job will stop permanently in the system. if you have created any modified job in the system (new variant) that job will run as per their scheduled time.

SAP SUM Error: Unable to find delivery event

Hi All,

Recently while patching & migration to HANA of Solution Manager 7.2, we have faced the below error in Configuration Phase –

Error in PREP_EXTENSION/CPK_INCLUSION

To Fix this issue, please follow below steps –

1. Please check the error – Unable to find delivery event XXXX XXXXXXXXXXX
2. Login into the system – SE16 – CWBCMPNT – Package – XXXX (Find the Component)
3. Once component is identified then login into SAP Launchpad & search for any note related to the component with respective system release.
4. Download the SAP note via SNOTE (No need to implement the note)
5. Repeat the SUM Phase

Please follow this SAP Note for more details – 2527823 – Error in CPK_INCLUSION during SUM: Unable to find delivery event

SAP Line Opener Program – LOP for SAP Remote Access Support

Hello All,

Going through some of my old stuff, i found interesting tool of SAP which is called Line Opener Program, it’s use to open R/3 connection to your SAP system for SAP Remote Access Support, I have collected some details with the help of SAP documentation & Note –

1. What is LOP(Line Opener Program)

Line Opener (LOP) is a standalone program which integrated directly into Solution Manager 7.1 SP13 onwards with below Key features

Key features are:

LOP runs as a program on the ABAP stack of the Solution Manager.
It can be started automatically during system start-up.
It can be scheduled to run as a batch job.

Advantages:

SAP can access a system at customer side faster and even in times (e.g. night times or weekends) when it is difficult to reach contact persons at customer side or in case of serious problems.

Communication costs can be reduced (e.g. when using an ISDN connection) as the network connection is only opened for the time needed.

Customers can allow Semi Automatic Opening on system level for each system.
Every time a service connection is opened, you are informed via email and the action is stored in the log book.

2. How it works

LOP uses https-requests to check periodically whether an opening request for one of your systems exists in SAP Service Marketplace. If an appropriate request is found the LOP opens the corresponding network connection between your SAProuter and SAP.

3. Implementations Steps

To successfully set up and run the Line Opener Program some prerequisites must be fulfilled.

Import SSL Certificate in Solution Manager as per Note – 797124

Create RFC Destination(HTTP Connection to External Server) & assign S user ID in RFC for communication

Configure AI_SC_LINE_OPENER program to run in batch mode

Perform SAO(Semi Automatic Opening) setup in SMP(SAP Market Place) for each system

4. Mail Confirmation – When SAP open connection directly (LOP configured)

5. Challenge

R/3 connection can open directly by SAP but for other connections (HTTP/WTS etc) requires manual intervention

Security team manage credentials for system manually

Background Job should be running continuously & if cancel should schedule again to check for opening connection.

For Detailed Steps please follow below documentation from SAP –

https://support.sap.com/en/tools/connectivity-tools/line-opener.html

https://launchpad.support.sap.com/#/notes/797124

https://support.sap.com/content/dam/support/en_us/library/ssp/tools/connectivity-tools/line-opener-program/lop-documentation.pdf

SAP STANDALONE GATEWAY INSTALLATION & CONFIGURATION

Environment –

SAP Distributed Installation – ASCS, DB & PAS running on separate host

Issue – DB13 Jobs(check DB & Update stats etc) are not running due to distributed installation.

Solution – Requires SAP gateway on DB Host to run the SAPXPG RFC. As per SAP recommendation we requires to install SAP Standalone Gateway with new SID.

SAPSID – SAP System SID

GWSID – Gateway SID

This document is separated with 4 phases – (Unix Installation)

Preparation

1. Identify the DB physical hostname for GW server installation

2. Identify the (SID) of GW server – i.e. – G30, G50 etc

3. Create local Mount Point request for new identified GW SID (if requires or else sapinst will create)
/usr/sap/(GW SID) – 5GB
/sapmnt/(GW SID) – 5 GB

4. Permission for mount point – (gwsid)adm:sapsys (full permission & others read only)

5. Download SWPM & Non Unicode Kernel for GW installation

6. Verify /tmp should have enough space to complete the installation (as SAPINST extract in /tmp by default)

Installation

1. Login via root & run SWPM in putty with command “./sapinst SAPINST_USE_HOSTNAME=db” (Virtual Host Name of DB server, if available or else physical)

2. Type GWSID(G30)

3. SAP Mount Directory – /usr/sap/ (As it will pick automatically new created mount point identified earlier)

4. Master Password for users

5. Provide SAPEXE.SAR & SAPHOSTAGENT.SAR (from Kernel directory)

6. Parameter Summary – Verify Details & Click on Show Details – Select Gateway Instance & Click Revise (if requires)

7. Successful installation will start the Gateway Service in host & Verify the same.

8. Specify Issues Encountered (Verify the installation error logs in /tmp directory & take corrective action.)

Post Installation Steps (Configuration)

1. login to (gwsid)adm & stopsap to stop the gateway server

2. Navigate to /usr/sap/(GWSID)//data & create 2 below files
vi reginfo
vi secinfo
Paste the below contents in 2 files –
TP=* USER=* USER-HOST=* HOST=*

3. Copy below files from SAP exe(kernel) directory to GATEWAY exe(kernel) folder –
sapxpg
libsapnwrfc.so
BR* (all BRTOOLS binaries)

4. Set the below BRTOOLS permission in GATEWAY exe(kernel) folder –
brarchive, brbackup, and brconnect belong to ora(sid) : sapsys and have authorization 4774
brrestore, brrecover, brspace, and brtools belong to (sapdsid)adm : sapsys and have authorization 755

5. Set below parameters in Gateway Instance Profile –
SETENV_04 = PATH=$(DIR_EXECUTABLE):/usr/sap/SAPSID/SYS/exe/run:/oracle/SAPSID/121/bin:%(PATH)
SETENV_06 = ORACLE_SID=SAPSID
SETENV_07 = SAPDATA_HOME=/oracle/SAPSID

(Replace SAPSID to respective SAP system name)

6. Set below parameters in Gateway ENV variable file – Verify SHELL = echo $SHELL & create a copy of existing ENV file & edit the same.
(.sapenv_(hostname).csh or .sapenv_(hostname).sh or .sapenv.sh)

(Replace SAPSID with respective SAP System Name)

setenv SAPDATA_HOME /oracle/SAPSID
setenv ORACLE_SID SAPSID
setenv PATH /oracle/SAPSID/121/bin:$PATH
setenv ORACLE_HOME /oracle/SAPSID/121(oracle version)
setenv USER (sapsid)adm
setenv dbs_ora_schema SAPSR3(schema user)
setenv NLS_LANG AMERICAN_AMERICA.UTF8
setenv DB_SID (SAPSID)
setenv dbs_ora_tnsname (SAPSID)
setenv dbms_type ORA
setenv SAPDATA_HOME /oracle/(SAPSID)
setenv SAPSID (SAPSID)
setenv LD_LIBRARY_PATH /usr/sap//SYS/exe/run:$LD_LIBRARY_PATH

Save the file, Log off & Login & verify the Environment Variables.

7. Start the gateway server by startsap

8. Login into ABAP System – SM59 – TCP/IP – SAPXPG_DBEST_DB(SID)
Program – sapxpg
Target Host – DB Hostname
Gateway Host – DB Hostname
Gateway Service – sapgw(GW instance number)
Save the RFC & Verify the Connection Test

9. DB13 – Choose update optimizer statistics & check DB & run immediately to verify SAPXPG is connecting to DB successfully with correct authorizations.

Troubleshooting

1. Installation Error TST_ERROR while installing the GW service
Generic error – it failed while starting the GW service in respective time frame, please crosscheck all the folders created in /usr/sap/GWSID & try to start the same directly from OS level.
startsap
if GW started successfully then ignore the installation error.”
“SAPXPG RFC Connection Error

2. Error – SAPXPG RFC not working – is SAP gateway started
Please check SAP Gateway should be started & in running status.

3. Error – SAXPG RFC not working – Storage allocation error
Please check whether it’s reading reginfo & secinfo file or restart the GW server

4. Error – SAPXPG RFC not working – Getting Timeout
Please check if you have copied the LIB file in GW exe folder, mentioned in Post Installation Steps”

5. Error – Permission denied to read log file in sapcheck directory
Login via ora(sid) & give 775 permission to respective connection file in sapcheck directory

6. Error – Invalid username / password
Please check the environment variables should be corrected & try to run BRCONNECT from OS level, sometime there will be issue at OPS$ mechanism, verify BRCONNECT from SAP user also.

7. Error – No Valid License Found
Please check the below ENV variable should exists for GW user.
setenv SAPSID (Replace with respective SAP server name)

Please share your comments –

SAP BDLS failing – Syntax Error in Program SAPLRSSTATMAN

Hi All,

During recent System Refresh, we have faced issue in SAP – Global Batch Trace System where BDLS for Logical System Conversion is failing with Syntax Error in table “/BI0/SREQUID”.

According to SAP, this issue is capture on SAP Note – 2133885.

for successful BDLS run (Logical System Conversion), we have implemented above note by SNOTE(no manual steps) on the system & re run BDLS again.

SAP BW Process Chains – Variant does not exists

Hi All,

Recently we have performed BW & SCM system refresh from PRD, once after the post steps Process chains were not working & throwing below error – “Variant does not exists”

To resolve the inconsistencies in post steps, you need to implement SAP note – 1455417

According to note 1455417, execute the report SA38 – RS_FIND_JOBS_WITHOUT_VARIANT in your system. This would remove all the inconsistent job entries & inform the BW team to run the process chains again.


However in some cases if the above report is not able to clean the variant then you need to create Z report given in the SAP note “Z_FIND_JOBS_WITHOUT_VARIANT” & run on the system to clean up the inconsistent entries.

Let me know if this solution helps you.