cancel
Showing results for 
Search instead for 
Did you mean: 

CBS-make Failed while importing SCs from Dev to Consolidation Track in CMS

Former Member
0 Kudos


Hi Experts,

By mistake, we triggerd the import for the released activities from Dev to consolidation track and the import running for a long time and it is failed with the  below error. Refer the attachment.

The view log shows as below,

Import Running:

20140517125118 Info  :build process already running: waiting for another period of 30000 ms

20140517125148 Info  :build process already running: waiting for another period of 30000 ms

20140517125218 Info  :build process already running: waiting for another period of 30000 ms

20140517125248 Info  :build process already running: waiting for another period of 30000 ms

20140517125318 Info  :build process already running: waiting for another period of 30000 ms

20140517125348 Info  :build process already running: waiting for another period of 30000 ms

20140517125418 Info  :build process already running: waiting for another period of 30000 ms

20140517125448 Info  :build process already running: waiting for another period of 30000 ms

Import Failed:

20140517075500 Info  :Starting Step CBS-make at 2014-05-17 07:55:00.0076 +3:00

20140517075500 Info  :wait until CBS queue of buildspace Track_C is completely processed, before starting the import

20140517075500 Info  :CBS queue of buildspace Track_C is completely processed. Starting the import now.

20140517080515 Fatal  :CBS throws exception during activation:

20140517080515 Fatal  :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Call to {http://host:50000/CBSWebService/CBSHttpSOAP?style=rpc} returned http code 500 (Internal Server Error) with unacceptable content type (text/html).

500 Connection timed out



Error:-5
Version:7200
Component:ICM
Date/Time:Sat May 17 08:05:15 2014
Module:icxxthr_mt.c
Line:4295
Server:
Error Tag:{-}
Detail:Connection to partner timed out after 600s

© 2001-2009, SAP AG

(Service call exception; nested exception is:

java.lang.Exception: Call to {http://host:50000/CBSWebService/CBSHttpSOAP?style=rpc} returned http code 500 (Internal Server Error) with unacceptable content type (text/html).

NOTE:  The CBS Web UI  is not accessible from the landscape configurator and it is ending with the 500 connection time out error.

http://host:50000/webdynpro/dispatcher/sap.com/tc.CBS.WebUI/WebUI?BSName=Track_C

We have fixed the error in the DC and activated the new activity. Now there are no errors in the DC (no dirty DCs).

But still the import is not successful.

We have tried by Start and Stop the CBS service and it didn't make any difference

.

Please help to fix the issue.

Appreciate your quick response.

Regards,

Senthil

Accepted Solutions (1)

Accepted Solutions (1)

former_member191643
Active Contributor
0 Kudos

Sounds weird, but try restarting the server once and then trigger the import. Kind of worked once for me.


Former Member
0 Kudos

Hi Experts,

We are facing the same issue again and it is taking several hours to import the CBS-make.

CBS-Binary-Sweeper 4136050/a255ee59-ddeb-11e3-c260-0000003f1c72 faces the following problem: com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:failure during deletion of assemblies
Original Cause: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.13.80
OpenSQLExceptionCategories: [TRANSIENT, TRANSACTION_ROLLBACK]

Appreciate your help to fix this issue.

Regards,

Senthil

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Oh, I haven't seen the latest post.

This seems to be some DB related issue.

I am not expert of this area, so let's hope the note makes sense here:

1619814 - Potential deadlock situation during cache refresh

Former Member
0 Kudos

Hi Ervin,

Thanks for your input.

We are facing this issue only for this SCA. The other SCAs available in the track or any other track are working fine.

I am providing some more input about this error, Please check if you could help with this.

Repository Import:

STARTED

20140611121236 Info   :Starting Step Repository-import at 2014-06-11 12:12:36.0063 +3:00

20140611121236 Info   :Component:XXXXXX.com/YSC_UNCCP_UI

20140611121236 Info   :Version  :JD3_CE72UID_D.79

20140611121236 Info   :1. propagation request is of type TCSChangeRequest

20140611121236 Info   :Propagatable:b3984ea0ddff11e3816a0000003f1c72 exists allready in the repository. No import necessary.

20140611122043 Info   :Integration of changelist:b3984ea0ddff11e3816a0000003f1c72 succeeded without conflicts.

20140611122043 Info   :Propagatable:2d921ca9de0d11e3c9110000003f1c72 exists allready in the repository. No import necessary.

20140611123002 Info   :Integration of changelist:2d921ca9de0d11e3c9110000003f1c72 succeeded without conflicts.

ENDED

20140611152813 Info   :Propagatable:6e2aeaebdf1e11e395120000003f1c72 exists allready in the repository. No import necessary.

20140611153616 Info   :Integration of changelist:6e2aeaebdf1e11e395120000003f1c72 succeeded without conflicts.

20140611153616 Info   :Step Repository-import ended with result 'success' at 2014-06-11 15:36:16.0206 +3:00

CBS-Make:

STARTED:

20140611153616 Info   :Starting Step CBS-make at 2014-06-11 15:36:16.0207 +3:00

20140611153616 Info   :wait until CBS queue of buildspace JD3_CE72UID_C is completely processed, before starting the import

20140611153616 Info   :CBS queue of buildspace JD3_CE72UID_C is completely processed. Starting the import now.

20140611153617 Info   :=================================================================

20140611153617 Info   :buildspace = JD3_CE72UID_C   build request id = 50862

20140611153617 Info   :wait until CBS queue of buildspace JD3_CE72UID_C is completely processed, before asking for build results

20140611153617 Info   :waiting for CBS queue activity

20140611153647 Info   :maximal waiting time is temporally increased

20140611153647 Info   :build process already running: waiting for another period of 30000 ms

20140611153717 Info   :build process already running: waiting for another period of 30000 ms

20140611153747 Info   :build process already running: waiting for another period of 30000 ms

ENDED:

in this case it is still running. But it took 2 hr 30 mins in the last import.

in NWA, we could see the below logs,

NWDIBrokerBean #4788 called store for service dtr catched java.lang.NullPointerException: while trying to invoke the method java.lang.String.equals(java.lang.Object) of an object returned from java.util.Properties.getProperty(java.lang.String)java.lang.NullPointerException: while trying to invoke the method java.lang.String.equals(java.lang.Object) of an object returned from java.util.Properties.getProperty(java.lang.String)

at com.sap.tc.di.nty.broker.NWDIBrokerBean.handleMessage(NWDIBrokerBean.java:206)

at com.sap.tc.di.nty.broker.NWDIBrokerBean.onMessage(NWDIBrokerBean.java:58)

at sun.reflect.GeneratedMethodAccessor490.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:111)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:78)

at com.sun.proxy.$Proxy217.onMessage(Unknown Source)

at com.sap.jms.client.session.JMSSession.deliverMessage(JMSSession.java:1042)

at com.sap.jms.client.session.JMSSession.run(JMSSession.java:886)

at com.sap.jms.resourceadapter.RaServerSession.run(RaServerSession.java:139)

at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:410)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

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

Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.

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

The source cache is in inconsistent state. (Request ID: 50864, BS: JD3_CE72UID_D [BSID: 457])

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

A problem during RUN
[EXCEPTION]
com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:failure during deletion of assemblies
Original Cause: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.13.80
OpenSQLExceptionCategories: [TRANSIENT, TRANSACTION_ROLLBACK]
at com.sap.tc.cbs.server.db.impl.DBDelete.deleteNonLogAssemblies(DBDelete.java:949)
at com.sap.tc.cbs.server.db.impl.DBDelete.cleanupNonLogAssemblies(DBDelete.java:753)
at com.sap.tc.cbs.server.db.impl.DBDelete.cleanupNonLogAssemblies(DBDelete.java:724)
at com.sap.tc.cbs.server.db.impl.AdminDB.cleanupBinaries(AdminDB.java:292)
at com.sap.tc.cbs.server.rt.impl.BinarySweeper.act(BinarySweeper.java:87)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:743)
Caused by: com.sap.sql.exception.OpenSQLTransactionRollbackException: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.13.80
OpenSQLExceptionCategories: [TRANSIENT, TRANSACTION_ROLLBACK]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:138)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1537)
at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:149)
at com.sap.sql.jdbc.common.CommonResultSet.next(CommonResultSet.java:528)
at com.sap.engine.services.dbpool.wrappers.ResultSetWrapper.next(ResultSetWrapper.java:615)
at com.sap.tc.cbs.server.db.impl.DBDelete.deleteNonLogAssemblies(DBDelete.java:925)
... 6 more
Caused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.13.80
at com.ibm.db2.jcc.am.id.a(id.java:664)
at com.ibm.db2.jcc.am.id.a(id.java:60)
at com.ibm.db2.jcc.am.id.a(id.java:127)
at com.ibm.db2.jcc.am.tn.b(tn.java:4101)
at com.ibm.db2.jcc.t4.db.h(db.java:286)
at com.ibm.db2.jcc.t4.db.a(db.java:244)
at com.ibm.db2.jcc.t4.db.c(db.java:31)
at com.ibm.db2.jcc.t4.r.a(r.java:32)
at com.ibm.db2.jcc.t4.j.Zb(j.java:263)
at com.ibm.db2.jcc.am.tn.X(tn.java:3863)
at com.ibm.db2.jcc.t4.d.f(d.java:2266)
at com.ibm.db2.jcc.am.lc.a(lc.java:206)
at com.ibm.db2.jcc.t4.d.a(d.java:128)
at com.ibm.db2.jcc.am.tn.c(tn.java:382)
at com.ibm.db2.jcc.am.tn.next(tn.java:309)
at com.sap.sql.jdbc.basic.BasicResultSet.next(BasicResultSet.java:65)
at com.sap.sql.jdbc.db6.Db6ResultSet.next(Db6ResultSet.java:54)
at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:146)
... 9 more

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

Appreciate your quick help to fix this.

Thanks in advance!

Regards,

Senthil

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

I think this will be really a DB problem in which unfortunately I cannot help. Perhaps others or your DB admin colleagues. Did you make an attempt restarting the server (including the DB) ?

Perhaps that helps too.

Best Regards,
Ervin

Former Member
0 Kudos

Hi Ervin,

Thanks for your input. We are following it up with a customer message and yet to receive the fix.

Meanwhile, the CBS-make is failed with errors with the below logs. Do you have any input on this?

There is no broken or Dirty DCs in the track.

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

CBS Request Log - [  50936/JD3_CE72UID_C  ]

  sajdi01.xxxxxx.com SAP Component Build Server   

 

Build number assigned: 53038

Change request state from QUEUED to PROCESSING

REQUEST PROCESSING started at 2014-06-13 10:17:10.956 GMT

    ACTIVATION request in Build Space "JD3_CE72UID_C" at Node ID: 4,136,050

  [id: 50,936; parentID: 0; type: 4]

  [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]

    Waiting for access: 48 ms

   

    ===== Pre-Processing =====  started at 2014-06-13 10:17:11.004 GMT

        List of requested for activation activities:

            ''xxxxxx.com_YSC_UNCCP_UI_1'' compartment

                change scenario-

                    [ISN 1494][created by E0344163 at 2014-06-12 12:33:40.0][OID cb7e073fe05411e38d240000003f1c72]

                changeScenario

                    [ISN 1495][created by E0344163 at 2014-06-12 12:41:43.0][OID 2d109ecce05911e39d030000003f1c72]

                responsevalues

                    [ISN 1496][created by E0344163 at 2014-06-12 12:50:28.0][OID 948bb1fce05e11e3bec40000003f1c72]

                sapIDvalue

                    [ISN 1497][created by E0344163 at 2014-06-12 12:59:03.0][OID eead1b9ce06011e3b13f0000003f1c72]

                errorHandling

                    [ISN 1498][created by E0344163 at 2014-06-12 13:08:43.0][OID a6976fc0e06311e382d60000003f1c72]

                BillToparty

                    [ISN 1499][created by E0344163 at 2014-06-12 13:17:12.0][OID 96429eade06711e3af7f0000003f1c72]

                BankInfo

                    [ISN 1500][created by E0344163 at 2014-06-12 13:24:50.0][OID d3d0a948e06c11e3c4ef0000003f1c72]

                bankInfo

                    [ISN 1501][created by E0344163 at 2014-06-12 13:32:27.0][OID 6f38ed6de06e11e39d050000003f1c72]

                shipToParty

                    [ISN 1502][created by E0344163 at 2014-06-12 13:41:41.0][OID bea6cab0e07311e3be580000003f1c72]

                default_w_CE72UID_xxxxxx_2e_com_YSC_UNCCP_UI_dev_inactive_u_e0344163_t_2014_05_21_01_54_34_GMT_20331c86-abe4-4c62-ae54-db2541ade711

                    [ISN 1503][created by E0344163 at 2014-06-12 13:51:01.0][OID b5e8211be08a11e3aa7c0000003f1c72]

                defauiltValue ahndling

                    [ISN 1504][created by E0344163 at 2014-06-12 14:00:07.0][OID c344d645e08a11e38c600000003f1c72]

                bankInfoIsChanged

                    [ISN 1505][created by E0344163 at 2014-06-12 14:10:00.0][OID 3dc237fce08e11e3b7640000003f1c72]

                errorhandling

                    [ISN 1506][created by E0344163 at 2014-06-12 14:18:54.0][OID e74093f0e08f11e3c4fb0000003f1c72]

                errorHandling

                    [ISN 1507][created by E0344163 at 2014-06-12 14:26:16.0][OID 371fc5f7e09111e396010000003f1c72]

                errorHandling

                    [ISN 1508][created by E0344163 at 2014-06-12 14:35:59.0][OID e989345ce09511e38a2f0000003f1c72]

                bankInfo

                    [ISN 1509][created by E0344163 at 2014-06-12 14:43:43.0][OID eab0748be09811e39e410000003f1c72]

                errorHandling

                    [ISN 1510][created by E0344163 at 2014-06-12 14:52:44.0][OID 2a7d7800e09a11e3abac0000003f1c72]

                countryDetails mapping

                    [ISN 1511][created by E0344163 at 2014-06-12 15:01:48.0][OID b7179d68e09c11e3bd420000003f1c72]

                Country Mapping

                    [ISN 1512][created by E0344163 at 2014-06-12 15:01:51.0][OID 8c571940e0bc11e3c8fc0000003f1c72]

                Delete Attachment

                    [ISN 1513][created by E0344163 at 2014-06-12 15:10:44.0][OID 5a81b091e0c411e3cbb30000003f1c72]

            There are 20 activities in compartment xxxxxx.com_YSC_UNCCP_UI_1

            20 activities will be processed by this request

       

        Analyze dependencies to predecessor activities... started at 2014-06-13 10:17:11.015 GMT

            Analyzing predecessors in compartment "xxxxxx.com_YSC_UNCCP_UI_1"

                No dependencies to predecessor activities found.

        Analyze dependencies to predecessor activities... finished at 2014-06-13 10:17:11.025 GMT and took 10 ms

       

        Analyze versions... started at 2014-06-13 10:17:11.026 GMT

            List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2014-06-13 10:17:11.107 GMT and took 81 ms

           

            Synchronize metadata for [xxxxxx.com/unccp/main/wdj] started at 2014-06-13 10:17:11.108 GMT

                    Verification of DL [ws/CE72UID/xxxxxx.com_YSC_UNCCP_UI/cons/active/] FAILED due to following reason:

                    Last ISN has changed from 1493 to 1494.

                Verification of DL [ws/CE72UID/xxxxxx.com_YSC_UNCCP_UI/cons/active/] finished at 2014-06-13 10:17:11.163 GMT and took 28 ms

            Synchronize metadata for [xxxxxx.com/unccp/main/wdj] finished at 2014-06-13 10:17:11.176 GMT and took 68 ms

            < CHANGE > ''xxxxxx.com/unccp/main/wdj'' DC

        Analyze versions... finished at 2014-06-13 10:17:11.176 GMT and took 150 ms

       

        Analyze activities... started at 2014-06-13 10:17:11.176 GMT

            Loading component definitions

            1 component to be build in compartment "xxxxxx.com_YSC_UNCCP_UI_1"

        Analyze activities... finished at 2014-06-13 10:17:11.205 GMT and took 29 ms

        Calculate all combinations of components and variants to be built...

       

        Analyze request DC BV... started at 2014-06-13 10:17:11.210 GMT

                ''xxxxxx.com/unccp/main/wdj'' variant ''default''

        Analyze request DC BV... finished at 2014-06-13 10:17:11.309 GMT and took 99 ms

       

        Prepare build environment in the file system... started at 2014-06-13 10:17:11.309 GMT

           

            Synchronize development configuration... started at 2014-06-13 10:17:11.309 GMT

            Synchronize development configuration... finished at 2014-06-13 10:17:11.334 GMT and took 25 ms

            Synchronization of sources is skipped for Activation with option IGNORE BROKEN DC

            Synchronization of libraries is skipped for Activation with option IGNORE BROKEN DC

            Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.

        Prepare build environment in the file system... finished at 2014-06-13 10:17:11.350 GMT and took 41 ms

    ===== Pre-Processing =====  finished at 2014-06-13 10:17:11.350 GMT and took 346 ms

    Waiting for access: 10 ms

   

    ===== Processing =====  started at 2014-06-13 10:17:11.360 GMT

    ===== Processing =====  finished at 2014-06-13 10:17:11.360 GMT and took 0 ms

    ===== Post-Processing =====

    Waiting for access: 9 ms

   

    ===== Post-Processing =====  started at 2014-06-13 10:17:11.369 GMT

        Check whether build was successful for all required variants...

        ..SKIPPED. Request option "IGNORE BROKEN DC" was given.

       

        STORE activation build results... started at 2014-06-13 10:17:11.372 GMT

           

            Update DC metadata... started at 2014-06-13 10:17:11.372 GMT

                ''xxxxxx.com/unccp/main/wdj'' DC is CHANGED

            Update DC metadata... finished at 2014-06-13 10:17:11.428 GMT and took 56 ms

            "xxxxxx.com/unccp/main/wdj" in "default" variant was not built and has no build results to store.

            "xxxxxx.com/unccp/main/wdj": store meta-data

            "xxxxxx.com/unccp/main/wdj" in "default" variant  is PROCESSED

        STORE activation build results... finished at 2014-06-13 10:17:11.453 GMT and took 81 ms

        Change request state from PROCESSING to SUCCEEDED

       

        Analyze effect of applied changes to buildspace state... started at 2014-06-13 10:17:11.453 GMT

            Skip check for build time dependency cycles. DC metadata is not changed.

           

            Determine components that have become DIRTY due to the results of this request started at 2014-06-13 10:17:11.573 GMT

                "xxxxxx.com/unccp/main/wdj" (variant "default").

            Determine components that have become DIRTY due to the results of this request finished at 2014-06-13 10:17:11.574 GMT and took 1 ms

            Internal Build Request 50937 has been CREATED to build the following component:

            "xxxxxx.com/unccp/main/wdj" variant "default"

        Analyze effect of applied changes to buildspace state... finished at 2014-06-13 10:17:11.589 GMT and took 136 ms

        Integrate activities into active workspace(s)...

       

        Integration of activities in compartment "xxxxxx.com_YSC_UNCCP_UI_1" started at 2014-06-13 10:17:11.592 GMT

            "change scenario-"   OK

            "changeScenario"   OK

            "responsevalues"   OK

            "sapIDvalue"   OK

            "errorHandling"   OK

            "BillToparty"   OK

            "BankInfo"   OK

            "bankInfo"   OK

        Integration of 9 activities in compartment "xxxxxx.com_YSC_UNCCP_UI_1" finished at 2014-06-13 11:29:10.232 GMT and took 71 m 58 s 640 ms

        An incomplete integration in compartment "xxxxxx.com_YSC_UNCCP_UI_1" of buildspace "JD3_CE72UID_C" has resulted because of errors during request processing!

Request 50940 has been created to re-initialize the compartment

    ===== Post-Processing =====  finished at 2014-06-13 11:29:10.251 GMT and took 71 m 58 s 882 ms

    Change request state from SUCCEEDED to FAILED

    Error! The following problem(s) occurred  during request processing:

    Error! Communication error when performing integrations. Integration failed with unexpected CONFLICT status [com.sap.dtr.client.lib.protocol.entities.ErrorEntity@4abd897b]. Request FAILED.

REQUEST PROCESSING finished at 2014-06-13 11:29:10.263 GMT and took 71 m 59 s 307 ms

No build logs available for the request.

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

Thanks in advance.

Regards,

Senthil

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Senthil,

at the very beginning of this post I can see an ICM error. Is it possible that all this is due to the

issue described in the following note?

1750758 - DC build in CBS fails due to ICM FCA connection broken with DTR server


Regards,

Ervin


Former Member
0 Kudos

Hi Ervin,

The current NWDI version is 7.3 SP9. I could not able to figure out these parameter via nwa.

The SAP Note 737625 is not applicable for 7.3.

As you said, it could be a ICM parameter issue. Getting the connection timeout after 600s.

The CBS log is not giving the exact cause for the issue. We are still waiting for SAP response for the message.

Please help if there is any other way to analyse or fix the issue.

Thanks.

Regards,

Senthil

Former Member
0 Kudos

Hi ,

Is there any other way to assemble the SCA?

It is taking approx. 6 hrs per import which is causing delay for our deliverables.

Thanks in advance!

Regards,

Senthil

junwu
Active Contributor
0 Kudos

save as a new track to see if any luck

Former Member
0 Kudos

Hi,

The NWDI import issue is not yet resolved and it is still taking several hours and getting failed most of the time.

As a workaround, (running out of time for the UAT)

Can we export the SCA file from the development track and deploy manually in the higher environments?

Once the import issue is resolved, we can undeploy those components and import the new SCAs through CTS+ transport request.

Is it advisable to do this? Is there any risk in this approach?

Did any one try this in the past?

Regards,

Senthil

junwu
Active Contributor
0 Kudos

i think it should be ok.

Former Member
0 Kudos

Hi All,

The issue is fixed by propagating the dev track to cons track using the DTR console as guided by SAP customer message.

The issue occurs becos of the DTR fusion.

Thanks to the SAP developer who guided us in the right direction.

I am marking this as answered.

Thanks once again for the responses.

Regards,

Senthil

Former Member
0 Kudos

Hi Senthil,

Could you please post the solution?

We are getting the same issue...

Thanks.

Marcos

Answers (1)

Answers (1)

junwu
Active Contributor
0 Kudos

what's the error in default trace?

Former Member
0 Kudos


Hi Jun Wu,

I could see the below error in the log,

CBS-Binary-Sweeper 4136050/49b4cd04-dda2-11e3-9b10-0000003f1c72 faces the following problem: com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:failure during deletion of assemblies
Original Cause: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.13.80
OpenSQLExceptionCategories: [TRANSIENT, TRANSACTION_ROLLBACK]

Any clue?

Regards,

Senthil

Former Member
0 Kudos

Hi,

To add more from the CBS-make import log shows as below,

20140517164048 Info   :Starting Step CBS-make at 2014-05-17 16:40:48.0940 +3:00

20140517164049 Info   :wait until CBS queue of buildspace UID_C is completely processed, before starting the import

20140517164049 Info   :CBS queue of buildspace UID_C is completely processed. Starting the import now.

20140517164049 Info   :=================================================================

20140517164049 Info   :buildspace = UID_C   build request id = 48689

20140517164049 Info   :wait until CBS queue of buildspace UID_C is completely processed, before asking for build results

20140517164049 Info   :waiting for CBS queue activity

20140517164119 Info   :maximal waiting time is temporally increased

20140517164119 Info   :build process already running: waiting for another period of 30000 ms

20140517164149 Info   :build process already running: waiting for another period of 30000 ms

20140517164219 Info   :build process already running: waiting for another period of 30000 ms

It is running for long time(taking more than 30 mins for a single import)  and the CBS is not reachable during this period.

Once the import is finished then the CBS is reachable.

Regards,

Senthil