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

 

 

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.