SAP : SPOOL_INTERNAL_ERROR

SPOOL INTERNAL ERROR is very common in SAP landscape. whenever spool reaches to their limit so it’s start failing the jobs & prints & due to this everything get stopped in SAP system.

SAP is having a default limit of 32000 spool in SAP system as per SAP Note 48284.

You need to check the limit by logging into 000 client – SNRO – Object – SPO_NUM & check interval.

if there is an heavy usage of SPOOL in your organization. you can use 2 things to resolve the issue.

1. Schedule daily cleanup job (RSPO1041) in the system with variant value less then 7 days.
2. Increase the limit of spool count from 32000 to 60000.

if you system is having this issue & you are not able to run the report in background, then delete the old spool in DIALOG mode for temporary cleanup via SPAD. once it’s clean then you can schedule the job again with change variant.

SAP – Enable TLS in SAP ABAP & JAVA Application Servers

Enabling TLS & SSL protocol in SAP ABAP & JAVA Application Servers.

Follow below SAP notes –

2384243 – NetWeaver Application Server: How to configure strict TLS 1.2
510007 – Setting up SSL on Application Server ABAP
2110020 – Enabling TLS or disabling SSLv3 protocol versions on SAP WebDispatcher, or SAP WebAS (AS ABAP 6xx, 7xx or AS Java >= 710)

There are other blog also which are explaining of this process but the above SAP notes are sufficient to complete the process.

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

How to boost Android Performance

Some months before I have purchased Samsung mobile with 3 GB RAM, initially it was working good as expected but after some time it’s start lagging & responding very slow. I tried uninstalling application & daily cleaning up the memory but that is also not helpful.

Then I start digging some of the options & found below 3 options in “Developer Tools” in Android that can be disable to boost up the speed.

Goto — Settings —- Developer Options (if it’s not enable then there are lot of videos / blogs for the same or easy way to enable “Tap 7 times on your Build Version” under details & option will be now visible.)

Please Note – Don’t Play with Developer options, it may damage your phone. Better to hide the same again after doing above steps.

After disabling above 3 options start using your phone normally & now you can see performance the mobile is now change & responding quickly as new 🙂