How to resolve java dispatcher startup issues?

This article answers following queries:

How to resolve java dispatcher startup issues?

What checks need to be done if java dispatcher doesn’t start during java startup?

What action need to be performed to fix java dispatcher startup issues?

-----------------------------------------------------------------------------------------

If java dispatcher doesn’t start during java startup, please check the std_dispatcher log from java work directory. It means, go to /usr/sap/<SID>/<instance>/work directory and look out for error messages. If you find below error message, this could be due to conflict between values maintained for thread mananger.

Loading: ThreadManager returned false! Kernel not loaded. System halted.

To resolve this issue, please proceed as follows:

•  Please login to config tool
•  Navigate to config tool -> dispatcher -> managers -> threadmanager
•  Please verify the values maintained for MinThreadCount, InitialThreadCount   and  MaxThreadCount.
•  Please make sure that MinThreadCount value <= InitialThreadCount <=    MaxThreadCount
•  If you are not sure about the values to be set, please maintain default values and check if dispatcher starts

If issue, didn’t get resolved even after performing above steps, please perform below mentioned additional tasks and retry to start the system

• In Config tool, navigate to Cluster-data --> Instance_IDxx --> dispatcher_IDxx --> managers --> ConfigurationManager
• In the local properties section, please make sure sqljdbc.jar exists for rdbms.driverLocation

How to resolve “Spool full” or “Spool overflow” errors or dumps in SAP?

This article answers following queries:

• How to resolve “Spool full” or “Spool overflow” errors or dumps in SAP?
• How to fix “SPOOL_INTERNAL_ERROR” short dump in SAP?
• What was the reason for long response times while creating new spool requests?
• What was the reason for process hang while executing SELECT statements on TSP01 table?

-----------------------------------------------------------------------------------------

In an SAP system, the number of spool requests that can be created is set to 32000 by default.Once this limit is reached, system won’t be able to generate new spool requests and generates the issues that were described. 

To overcome these issues, it is recommended to increase the spool number limit to 999999.

To set this, please follow below steps:

1) Please login to client 000 of the respective SAP system where you are encountering issues

    2) Please execute SNRO transaction. In the resulting screen, select object as SPO_NUM” as shown in  below screenshot

3)  Now, click on “Interval Editing” which results in below screen.

      4) Please click on above highlighted Intervals button to set spool number

Please set desired number in column “To Number” and save the changes.

It is recommended that, maximum value that can be set is 999999 and this task should be performed in client 000.

The size of this interval specifies, maximum number of spools that can exist in SAP system. It is recommended to execute RSPO0041 or RSPO1041 reports on a periodic basis to delete old spool requests that are not required.

What is the process to be followed to capture SAP connect trace?

This article answers following queries:

What is the process to be followed to capture SAP connect trace?

How to enable and view SAP connect trace?

What transaction can be used to capture SAP connect trace?

How to download SAPconnect trace?

How to capture SAP connect trace for messages (fax, email) being sent or received in SAP?

-----------------------------------------------------------------------------------------

Please login to SAP system and execute SCOT tcode.

After that navigate to menu Utilities --> Trace Settings as shown below

It results in below screen.

By default, outbound, inbox and global trace settings will be in deactivated state. We can either set “activated” or “errors only” based on our requirement (as shown below). 

If we want to enable trace for outgoing messages, we can activate Outbox trace. For incoming messages, we can activate Inbox trace. If we wish to capture the start and end of a send order, we need to activate global trace.

After executing SCOT, we can view SAPconnect trace by navigating to Utilities -> Trace selection (as shown below)

It will result in below screen. Please provide necessary inputs to view the trace.

Incase, you would like to download trace as a text file, please navigate to “System --> List --> Save --> local file”.

Alternatively, we can display or view trace through SOST transaction code also. We need to select respective message and click on display trace (as shown below)

Please note that in few SAP releases, instead of SCOT tcode, we can use SOST/SOIN tcodes to capture SAPconnect trace. 

How to view all SAP notes that are included in a support package?

This article answers following queries:

•          How to identify SAP notes that are part of a given support package?
•      How to view all SAP notes that are included in a support package?
•      What is the process to find SAP notes that are included in a support package?

-------------------------------------------------------------------------------------------------------

Please login to Service Market Place software delivery center using your S-user credentials

https://support.sap.com/en/my-support/software-downloads.html

It will lead to above page.

In the above page, please click on Access downloads link under Support Packages & Patches. It will result in below screen.

In the above screen, next to Downloads drop down box, mention the support package details, for which you want to identify SAP notes within it.

For example, if you wish to identify SAP notes that are present in support package SAPKB70011, please mention it next to drop down menu and click search, which results in following screen.

In the above screen, please select check box related to support package and click on icon “Content Info” icon, highlighted in the green color above.

It displays list of SAP notes within that support package as shown below. 

Using same procedure, we can find out Sap notes of any given support package.

I hope, above mentioned process is very clear to view SAP notes that are included in a given support package.