Thursday, 31 October 2019

Deployment Error during SAP JAVA STACK SUM Update with ERRORCODE=-4229


During the SAP JAVA Stack Upgrade Executaton Phase getting below error in Solution Manager 7.2 JAVA stack upgrade.

Operating System : SUSE LINUX 12 SP04
Database               : DB2 LUW 11.1 MP4 FP4

ERROR :

An SAP NW AS Java System upgrade terminates with the following error reported in DEPLOY-COMPONENTS.log 

Deployment of archive /install/SAP/nw75_java_ads_15/MMRSERVER15_0-80000683.SCA --> bi~mmr~mmrlib.sda for component sap.com/bi~mmr~mmrlib abortedDetailed message: 1. [jcc][t4][102][10040][4.25.15] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

Solution:

Workaround

Remove SECTION_LEVEL_LOB registry value from registry variable
DB2_RUNTIME_DEBUG_FLAGS.
Change:
 DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE,
SECTION_LEVEL_LOB [DB2_WORKLOAD]

 To:
 DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE [O]

Example:
> su - db2
 >db2set  DB2_RUNTIME_DEBUG_FLAGS

DB2_RUNTIME_DEBUG_FLAGS= TOLERANT_FLOAT, DISABLE_BLANK_TOLERANCE,
SECTION_LEVEL_LOB

db2set  DB2_RUNTIME_DEBUG_FLAGS = TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE
 
 




Wednesday, 23 October 2019

SAP Response Times


SAP Response Times:

What is Response Time?

The given below times provide you with an overview of the optimal response times in your SAP system. You can display the current workload overview for your system with the workload monitor. 

Brief details of the Response Time

         Performance Data                                                   Time

1.  Average response time                                  Around 60 ms(dialog), < 60 ms  (update)
2. Average CPU time                                         Around 40% of the average response time
3. Average wait time                                          < 1% of the average response time
4. Average load time                                          < 10% of the average response time
5. Average database time per dialog step         Around 40% of the average response time 

Important Note: 

The operating system can affect these values by up to around 10%.
 

The ratio of the CPU time to the total time should not fall under 5%. A the smaller proportion could mean that there is an input/output bottleneck or that a database overload has caused long wait times.

The average response times for dialog transactions (online transactions) should not be more than a second, since a higher value would strain the patience of the user too much. 


How much time to take fetch data from the database ? 

Times for Database Access

  Database Access                     Time

1. Direct read                         < 10 ms

2. Sequential read                  < 40 ms

3. Changes                              > 25 ms




The above mention value is approximate(min) values.

Bonus:

What are all the things that increase response time in SAP response time?


Take Load more time based on the below reason?
   

  • Buffer too small
  • Transports to the productive system

Take more response Wait time?

  •  Insufficient work processes
  • Inactive update
  • Incorrect operation mode
  • Locked tasks
  • Long-running transactions

this is all the possibility to affect Response time.

Important Note :

  •  In a database system that is functioning properly, the times for direct reads and changes should not be more than 10 ms.
  • The time for sequential reads should not be more than 30-40 ms. 








More reference from SAP Help Doc.
 
 



Sunday, 29 September 2019

How can enable Scripting in SAP GUI?

Introduction about SAP GUI Scripting.

SAP GUI Scripting API is an automation interface that enhances the capabilities of SAP GUI for Windows. Using this interface, end users may automate repetitive tasks by recording and running macro-like scripts. Administrators and developers on the other hand may build tools for server-side application testing or client-side application integration.

From the SAP server’s point of view there is no difference between SAP GUI communication generated by a script and SAP GUI communication generated by a user. For this reason a script has the same rights to run SAP transactions and enter data as the user starting it. In addition, the same data verification rules are applied to data entered by a user and data entered by a script.

However, just as a person might make mistakes that cannot be detected by a verification rule, an error in a script may cause bad data to be entered into the system without being detected immediately. A script runs significantly faster than manual interaction with a system, though, and it may also run unattended. It is therefore likely that a bad script can generate more bad data than a user before the mistake is detected.

Installation

SAP GUI Scripting is only available if it has been installed. The SAP GUI Scripting is included in the SAP GUI installation per default. An administrator can prevent SAP GUI Scripting from being installed. Using NWSAPAdmin, the administrator can create an installation package without Scripting and then prevent users from selecting components manually. Installation packages can be assigned to single users or to a group of users so that an administrator can easily define who will be able to use SAP GUI Scripting and who will not. If a user has the right to select components himself he can exclude Scripting by not selecting the entry in the list of components.


SAP GUI Scripting

  • Since version 6.20 SAP GUI Scripting is provided on R/3 system. 
  • By default SAP GUI Scripting is disabled on any given SAP system.

To activate SAP GUI Scripting the administrator has to enable the profile parameter .

sapgui/user_scripting” to “TRUE” on the application server.
That way an administrator can enable scripting either for all users of a given system or for a certain group of users, which may have special access restrictions. It is also possible to completely prevent scripts from being run against a specific SAP system. This might be desirable to protect mission critical data from corrupted or downloaded.


On the following screen the “Current value” entry should be “TRUE”. If it is displayed as “FALSE”, press the “Change value” button on the toolbar, set the value to “TRUE” and save it. After saving the value the “Current value” should change to “TRUE”.
If the SAP system has several application servers and uses load balancing you may want to set the “Switch on all servers” check box. Otherwise the parameter is only set when you log into the current application server.
 The SAP GUI Scripting will then be enabled the next time you log into the server.


After SAP GUI Scripting has been enabled with the parameter “sapgui/user_scripting”, SAP GUI Scripting can be activated under ”Script Recording and Playback”.














More Details refer KBA : 2296251




 

Saturday, 28 September 2019

SAP HANA: Supported Operating Systems


SAP HANA: Supported Operating Systems


Supported Operating Systems for SAP HANA

One of the following Enterprise Linux distribution products, in the below-mentioned version, is required for running SAP HANA:

  •     Red Hat Enterprise Linux for SAP Solutions
  •     Red Hat Enterprise Linux for SAP HANA

  •     SUSE Linux Enterprise Server for SAP Applications
  •     SUSE Linux Enterprise Server

SAP strongly recommends to use "RHEL for SAP Solutions" or "SLES for SAP Applications" due to their features and extended support cycles. For detailed information about the Linux product flavors, their feature set and benefits, please contact your respective Linux sales representative.

Supported Operating Systems for SAP HANA 1.0 on Intel-Based Hardware Platforms

For running an SAP HANA 1.0 system on Intel-based hardware platforms the following operating systems are supported:

  •     Red Hat
    For general information how to configure Red Hat for SAP HANA,
        RHEL for SAP Solutions / RHEL for SAP HANA 7
  •             7.6 (HANA 1.0 SPS12 revision 122.23 and newer)
  •             7.5 (HANA 1.0 SPS12 revision 122.19 and newer)
  •             7.4 (HANA 1.0 SPS12 revision 122.14 and newer)
  •             7.3 (HANA 1.0 SPS12)
  •             7.2 (HANA 1.0 SPS12)

        RHEL for SAP Solutions / RHEL for SAP HANA 6
  •             6.10 (HANA 1.0 SPS12 revision 122.23 and newe
  •             6.7 (HANA 1.0 SPS11 and newer
  •             6.6 (up to HANA 1.0 SPS11
  •             6.5 (up to HANA 1.0 SPS11

  •     SUSE
    For general information how to configure SUSE for SAP HANA
        SLES for SAP Applications / SLES 15
            15 (GA) (HANA 1.0 SPS12 revision 122.21 and newer)

        SLES for SAP Applications / SLES 12
  •             12 SP4 (HANA 1.0 SPS12 revision 122.22 and newer)
  •             12 SP3 (HANA 1.0 SPS12 revision 122.15 and newer)
  •             12 SP2 (HANA 1.0 SPS12)
  •             12 SP1 (HANA 1.0 SPS12)
  •             12 (GA) (HANA 1.0 SPS10 and newer)

        SLES for SAP Applications / SLES 11
  •             11 SP4 (HANA 1.0 SPS10 and newer
  •             11 SP3 (HANA 1.0 SPS10 and newer
  •             11 SP2 (up to HANA 1.0 SPS11
Supported Operating Systems for SAP HANA 1.0 on IBM Power Servers
For running an SAP HANA 1.0 system on IBM Power servers the following operating system is supported:

  •     SUSE
    For general information how to configure SUSE for SAP HANA
  •         SLES for SAP Applications / SLES 11
  •             11 SP4 (HANA 1.0 SPS11 and newer

Supported Operating Systems for SAP HANA 2.0 on Intel-Based Hardware Platforms

For running a SAP HANA 2.0 system on Intel-based hardware platforms the following operating systems are supported:

  •     Red Hat
    For general information how to configure Red Hat for SAP HANA
        RHEL for SAP Solutions / RHEL for SAP HANA 8
            8.0 (HANA 2.0 SPS04 revision 40 and newer)

        RHEL for SAP Solutions / RHEL for SAP HANA 7
  •             7.6 (HANA 2.0 SPS03 revision 36 and newer)
  •             7.5 (HANA 2.0 SPS03 only, starting with revision 32)
  •             7.4 (HANA 2.0 SPS02 revision 23 and newer)
  •             7.3 (HANA 2.0 SPS02 revision 21 and newer, up to HANA 2 SPS03)
  •             7.2 (up to HANA 2.0 SPS03)

  •     SUSE
    For general information how to configure SLES for SAP HANA
        SLES for SAP Applications / SLES 15
  •             15 (GA) (HANA 2.0 SPS03 revision 34 and newer)

        SLES for SAP Applications / SLES 12
  •             12 SP4 (HANA 2.0 SPS03 revision 35 and newer)
  •             12 SP3 (HANA 2.0 SPS02 revision 23 and newer)
  •             12 SP2 (HANA 2.0 SPS01 and newer, up to HANA 2 SPS03)
  •             12 SP1 (HANA 2.0 SPS00 and newer, up to HANA 2 SPS03)

Supported Operating Systems for SAP HANA 2.0 on IBM Power Servers

For running an SAP HANA 2.0 system on IBM Power servers the following operating systems are supported:

  •     Red Hat
    For general information how to configure Red Hat for SAP HANA
         RHEL for SAP Solutions / RHEL for SAP HANA 7
  •             7.6 (HANA 2.0 SPS03 revision 36 and newer)
  •             7.5 (HANA 2.0 SPS03 only, starting with revision 32)
  •             7.4 (HANA 2.0 SPS02 revision 23 and newer)
  •             7.3 (HANA 2.0 SPS02 revision 21 and newer, up to HANA 2 SPS03)

  •     SUSE
    For general information how to configure SUSE for SAP HANA
        SLES for SAP Applications / SLES 15
            15 (GA) (HANA 2.0 SPS03 revision 34 and newer)


        SLES for SAP Applications / SLES 12
  •             12 SP4 (HANA 2.0 SPS03 revision 35 and newer)
  •             12 SP3 (HANA 2.0 SPS02 revision 23 and newer)
  •             12 SP2 (HANA 2.0 SPS02 and newer, up to HANA 2 SPS03)
  •             12 SP1 (HANA 2.0 SPS00 and newer, up to HANA 2 SPS03)




Tuesday, 24 September 2019

ERROR :Assertion failed: Detected database~ message happened during the SAP ASE installation for Business Suite


ISSUE:
  • Assertion failed: Detected database connection issues for host strsap with port 4901 and database server name .
  • Database connect via isql tool is possible.
  • Database connect via JDBC driver is not possible
  • SAP ASE log shows that the DB started with IPV6 address.

network name , interface IPv6, address abef::d4:ecff:fed9:104, type tcp, port 4901, filter NONE

Solution:

  •   Add correct hostname information with IPv6 and IPv4 address in the /etc/hosts
  •   Restart SAP ASE with IPv4 address.
  •   Shutdown SAP ASE
  •   Disable IPv6 on the host  Start SAP ASE
 

Friday, 20 September 2019

How to lock and unlock the SAP system during an upgrade!

How to lock and unlock the SAP system during an upgrade!

ISSUE:
  • You get the message "Upgrade in progress: no login is possible" when trying to logon
  •  You are trying to implement a Note in the system during the upgrade and get the message: "Changes in ACM are locked (decision taken by rule A)"

Solution:

1. To unlock the SAP system, enter the following commands. The system may be either the original SAP system or the shadow system, depending on which one the error occurred.
Original SAP system

cd //abap/bin
./SAPup unlocksys


Shadow system
 
cd //abap/bin
SAPup unlockshd


Log on to the SAP system or shadow system and correct the error.

2. To lock the original SAP system or shadow system again, enter the following commands:
Original SAP system
 
cd //abap/bin
./SAPup locksys


Shadow system
 
cd //abap/bin
SAPup lockshd