SAP Knowledge Base Article - Preview

2706892 - Cannot commit handler in operation [update] with application [sap.com/ui~five]

Symptom

Upgrade fails with UI5 component with the following errors:

SUM DEPLOY-COMPONENTS_xx.LOG:

Deployment message for component UISAPUI5_JAVA : Deployment of archive /install/stack_patch/UISAPUI5JAVA13P_1-80000708.SCA for component sap.com/UISAPUI5_JAVA aborted
Detailed message:
1. Contains Aborted deployment component:
sap.com_ui~five
Deployment of archive /install/stack_patch/UISAPUI5JAVA13P_1-80000708.SCA --> ui~five.sda for component sap.com/ui~five aborted
Detailed message: 1. [jcc][t4][102][10040][4.19.49] 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

defaultTrace.x.trc:

#2.0�#2018 10 04 18:42:26:037#+0200#Error#com.sap.engine.services.deploy.server.application.ApplicationTransaction#
#N/A#Deploy Service#C0000A6D037603640000009F000051C7#2025550000003874##com.sap.engine.services.deploy.server.application.ApplicationTransaction#Administrator#0##D654E32BC7F111E8BC230000001EE84E#d654e32bc7f111e8bc230000001ee84e##0#Thread[DeployThread[sap.com_ui~five],5,Managed_Application_Thread]#Plain##
Cannot commit handler in operation [update] with application [sap.com/ui~five].
[EXCEPTION]
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot commit handler in operation [update] with application [sap.com/ui~five].

Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access:

Caused by: com.sap.sql.exception.OpenBatchUpdateException: [jcc][t4][102][10040][4.19.49] 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
OpenSQLExceptionCategories: []

#2.0�#2018 10 04 18:42:25:933#+0200#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C0000A6D037603640000009E000051C7#2025550000003874##com.sap.sql.jdbc.direct.DirectPreparedStatement#Administrator#0##D654E32BC7F111E8BC230000001EE84E#d654e32bc7f111e8bc230000001ee84e##0#Thread[DeployThread[sap.com_ui~five],5,Managed_Application_Thread]#Plain##
SQL error occurred on connection rixsapajv000:AJV:SAPSR3DB: code=-4,225, state="<null>", message="[jcc][103][10843][4.19.49] Non-recoverable chain-breaking exception occurred during batch processing. The batch is terminated non-atomically. ERRORCODE=-4225, SQLSTATE=null";
SQL statement is "INSERT INTO "J2EE_CONFIGENTRY"("CID","NAMEHASH","NAME","DTYPE","FBLOB","ISFILE") VALUES(?, ?, ?, ?, ?, 1)".
[EXCEPTION]
com.ibm.db2.jcc.am.SqlException: [jcc][103][10843][4.19.49] Non-recoverable chain-breaking exception occurred during batch processing. The batch is terminated non-atomically. ERRORCODE=-4225, SQLSTATE=null

*****************************************************************************************************************************************************************************

  • The SqlException with the line batch is terminated non-atomically. ERRORCODE=-4225, is generated by the SUM tool.
    It is not an actual database error, however may indicate that there is a database issue. 
  • The next steps is therefore important.  In the /db2/db2<SID> directory path, the db2diag.log (latest) is located.
    Check the db2diag.log for any errors relating to the database or the underlying file system storage against the exact timestamp of the deployment log errors.
    For example;

Cross-referencing with the db2diag.log timestamps shows that there termporary tablespace is full.  This resulted then in the above error during the INSERT on table J2EE_CONFIGENTRY

2018-10-04-18.42.22.740522+120 E675046E615 LEVEL: Error
PID : 5475 TID : 139685418493696 PROC : db2sysc 0
INSTANCE: db2<SID> NODE : 000 DB : <SID>
HOSTNAME: rixsalx18425
EDUID : 39 EDUNAME: db2pfchr (AJV) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSDirectWrite, probe:1443
MESSAGE : ADM6017E The following table space is full. Table space name:
"PSAPTEMP16". Table space identifier: "3". Container path:
"/db2/<SID>/<temp_directory>/db2<SID>/NODE0000/<SID>/T0000003/C0000002.TMP".
Container identifier: "2".


Read more...

Environment

SAP NetWeaver Application Server Java
DB2 LUW IBM

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

UI5, upgrade fails, cannot deploy, deployment, PSAPTEMP, Temporary Tablespace. , KBA , BC-JAS-DPL , Deployment , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.