CBS Activation Failure

[Former Member]

Hi All,

We are working on ESS Components which are having few modifications and everything went on well till yesterday. Today we are seeing strange behaviors while activating the activity. It juts throws an error like cache verification failure. Please find below the CBS Request log. Sorry for posting the Build log.

REQUEST PROCESSING started at 2010-09-02 21:59:15.053 GMT

ACTIVATION request in Build Space "MRCK_HTRESSDV_D" at Node ID: 14,793,550

[id: 24,237; parentID: 0; type: 4]

[options: NO OPTIONS]

Waiting for access: 3 ms

===== Pre-Processing ===== started at 2010-09-02 21:59:15.057 GMT

List of requested for activation activities:

'sap.com_SAP_ESS_1' compartment

DHTR094 - TIR236 BE ADDR Subtype Text Display Problem

[ISN 171][created by KUMARAPP at 2010-09-02 17:56:21.0][OID 303b3c5db6d211df875b00237da9de6a]

There is 1 activity in compartment sap.com_SAP_ESS_1

1 activity will be processed by this request

Analyze dependencies to predecessor activities... started at 2010-09-02 21:59:15.069 GMT

Analyzing predecessors in compartment "sap.com_SAP_ESS_1"

No dependencies to predecessor activities found.

Analyze dependencies to predecessor activities... finished at 2010-09-02 21:59:15.112 GMT and took 43 ms

Analyze versions... started at 2010-09-02 21:59:15.112 GMT

List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-09-02 21:59:15.168 GMT and took 55 ms

Synchronize metadata for [sap.com/ess/be/addr] started at 2010-09-02 21:59:15.170 GMT

Verification of DL [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/] finished at 2010-09-02 21:59:15.272 GMT and took 19 ms

Verification of cache (level 2: Comparison of attributes) finished at 2010-09-02 21:59:15.294 GMT and took 21 ms

Synchronize metadata for [sap.com/ess/be/addr] finished at 2010-09-02 21:59:15.303 GMT and took 133 ms

< CHANGE > 'sap.com/ess/be/addr' DC

Analyze versions... finished at 2010-09-02 21:59:15.304 GMT and took 192 ms

Analyze activities... started at 2010-09-02 21:59:15.304 GMT

Loading component definitions

1 component to be build in compartment "sap.com_SAP_ESS_1"

Analyze activities... finished at 2010-09-02 21:59:15.382 GMT and took 78 ms

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

Analyze request DC BV... started at 2010-09-02 21:59:15.385 GMT

'sap.com/ess/be/addr' variant 'default'

Analyze request DC BV... finished at 2010-09-02 21:59:15.487 GMT and took 102 ms

Prepare build environment in the file system... started at 2010-09-02 21:59:15.488 GMT

Synchronize development configuration... started at 2010-09-02 21:59:15.488 GMT

Synchronize development configuration... finished at 2010-09-02 21:59:15.489 GMT and took 1 ms

Synchronize sources for [sap.com/ess/be/addr] started at 2010-09-02 21:59:15.518 GMT

Verification of DL [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/] finished at 2010-09-02 21:59:17.890 GMT and took 13 ms

Verification of cache FAILED due to the following reasons:

Cache inconsistency detected: comparison of cache items on the paths:

[/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_bg.xlf]

[ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_bg.xlf]

on verification level 2 FAILED:

Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

Cache inconsistency detected: comparison of cache items on the paths:

[/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_el.xlf]

[ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_el.xlf]

on verification level 2 FAILED:

Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

Cache inconsistency detected: comparison of cache items on the paths:

[/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_es.xlf]

[ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_es.xlf]

on verification level 2 FAILED: Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

Verification of cache (level 2: Comparison of attributes) finished at 2010-09-02 21:59:18.498 GMT and took 608 ms

Synchronize sources for [sap.com/ess/be/addr] finished at 2010-09-02 21:59:18.857 GMT and took 3 s 339 ms

Synchronize used libraries... started at 2010-09-02 21:59:19.056 GMT

PP 'FloorplanManager' of DC 'sap.com/pcui_gp/xssfpm' [DCID=1188] (in SC 'sap.com_SAPPCUI_GP_1' [SCID=1373]) ... OK

PP 'default' of DC 'sap.com/tc/wd/webdynpro' [DCID=592] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

PP 'default' of DC 'sap.com/com.sap.exception' [DCID=8] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

PP 'default' of DC 'sap.com/tc/ddic/ddicruntime' [DCID=400] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'default' of DC 'sap.com/tc/col/api' [DCID=397] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'default' of DC 'sap.com/tc/wdp/metamodel/content' [DCID=415] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'default' of DC 'sap.com/com.sap.mw.jco' [DCID=12] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

PP 'default' of DC 'sap.com/com.sap.aii.proxy.framework' [DCID=336] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'default' of DC 'sap.com/tc/logging' [DCID=11] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

PP 'default' of DC 'sap.com/com.sap.aii.util.misc' [DCID=337] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'FPMUtils' of DC 'sap.com/pcui_gp/xssutils' [DCID=1189] (in SC 'sap.com_SAPPCUI_GP_1' [SCID=1373]) ... OK

PP 'default' of DC 'sap.com/tc/ddic/metamodel/content' [DCID=117] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'default' of DC 'sap.com/tc/cmi' [DCID=396] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

PP 'InternationalPersInfo' of DC 'sap.com/ess/per' [DCID=844] (in SC 'sap.com_SAP_ESS_1' [SCID=1375]) ... OK

Synchronize used libraries... finished at 2010-09-02 21:59:20.986 GMT and took 1 s 930 ms

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 2010-09-02 21:59:20.987 GMT and took 5 s 499 ms

===== Pre-Processing ===== finished at 2010-09-02 21:59:20.988 GMT and took 5 s 931 ms

Waiting for access: 3 ms

===== Processing ===== started at 2010-09-02 21:59:20.991 GMT

BUILD DCs

'sap.com/ess/be/addr' in variant 'default'

The build was SUCCESSFUL. Archives have been created.

===== Processing ===== finished at 2010-09-02 22:00:31.588 GMT and took 1 m 10 s 597 ms

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

Waiting for access: 14 ms

===== Post-Processing ===== started at 2010-09-02 22:00:31.603 GMT

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

"sap.com/ess/be/addr" in variant "default" OK

STORE activation build results... started at 2010-09-02 22:00:33.402 GMT

Update DC metadata... started at 2010-09-02 22:00:33.408 GMT

'sap.com/ess/be/addr' DC is CHANGED

Update DC metadata... finished at 2010-09-02 22:00:33.539 GMT and took 131 ms

STORE build results... started at 2010-09-02 22:00:33.540 GMT

"sap.com/ess/be/addr": store meta-data

"sap.com/ess/be/addr" in "default" variant is PROCESSED

STORE build results... finished at 2010-09-02 22:00:35.549 GMT and took 2 s 9 ms

STORE activation build results... finished at 2010-09-02 22:00:35.549 GMT and took 2 s 147 ms

Change request state from PROCESSING to SUCCEEDED

Analyze effect of applied changes to buildspace state... started at 2010-09-02 22:00:35.550 GMT

Handle Cycles... started at 2010-09-02 22:00:35.572 GMT

No new cycles detected.

Handle Cycles... finished at 2010-09-02 22:00:39.175 GMT and took 3 s 603 ms

Determine components that have become DIRTY due to the results of this request started at 2010-09-02 22:00:39.296 GMT

No such components have been found.

Determine components that have become DIRTY due to the results of this request finished at 2010-09-02 22:00:39.297 GMT and took 1 ms

The following Internal Build Requests will be canceled because Request DCBVs are already built by this request

INTERNAL BUILD request in Build Space "MRCK_HTRESSDV_D" at Node ID: 14,793,550

[id: 24,165; parentID: 23,837; type: 32]

Analyze effect of applied changes to buildspace state... finished at 2010-09-02 22:00:41.498 GMT and took 5 s 948 ms

Integrate activities into active workspace(s)...

Integration of activities in compartment "sap.com_SAP_ESS_1" started at 2010-09-02 22:00:41.505 GMT

Integration of 1 activities in compartment "sap.com_SAP_ESS_1" finished at 2010-09-02 22:00:42.826 GMT and took 1 s 321 ms

An incomplete integration in compartment "sap.com_SAP_ESS_1" of buildspace "MRCK_HTRESSDV_D" has resulted because of errors during request processing!

Request 24238 has been created to re-initialize the compartment

===== Post-Processing ===== finished at 2010-09-02 22:00:42.852 GMT and took 11 s 249 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@5719ce2c]. Request FAILED.

REQUEST PROCESSING finished at 2010-09-02 22:00:42.865 GMT and took 1 m 27 s 812 ms

Regards,

Nagarajan

[ErvinSzolke · Accepted solution]

Hi,

first please take a look at the note:

http://service.sap.com/sap/support/notes/133013

As long as you don't have any 'real' issue you can ignore this error message.

If this is not the case, then try to proceed this way:

1. delete the buildspaces dev and cons (you can do it in the Buildspace view of the CBS webui)

2. resave the track ,this will recreate the buildspaces. (you do it in the landscape configurator of CMS -- track data tab)

3. Restore system state (you find a button for it on the development and consolidation tabs in the transport studio of CMS webui)

4. reimport the software into development and consolidation (transport studio -- development/consolidation tab).

Until the buildspaces are deleted, your developers won't be able to activate and build. Do not forget to reimport the software back to the buildspaces dev and cons before your developers are continuing their work. Your sources won't get lost as they are stored in DTR.

Best Regards,

Ervin

[Former Member · Accepted solution]

Thanks for the reply.

My only concern is about the work we did on the tracks. I know the DTR holds the source code. Will the restore system state brings to intiali version of the Software component and Development components?

Since this is an ESS track and was done by a upgrade we had to resolve more than 200 conflicts and to keep in mind it should not be lost while restoring the system state. All the manual effort to resolve the conflicts would end for no cause.

Will the resolved conflicts come up again when we restore the system state?

Thanks,

Nagarajan.

[Former Member]

Hi,

I compared the other tracks and found a difference in the DTR Active Workspace State. For the current development track it was somehow set to closed. I opened the state of the DTR Active WS through DTR Console Command line.

Then I tried activating the activities which went through fine.

Thanks,

Nagarajan.

[Former Member]

Hi Nagarajan,

I am facing the same issue here. Could you tell me where I could check DTR Active Workspace state? In mean whether in NWDI or somewhere else?. And also how to trigger 'Initialize Compartment' for build space, I do not see any thing called 'Initialize Compartment' for the build space.

Thanks for your time.

Regards,

Manoj

[ErvinSzolke]

Hi Nagarajan,

A quick update: we continue the investigation of this issue in your ticket which I've handed over for our development support.

(The other reason of this entry is a small correction due to my typo: I meant above the note number 1133013)

Best Regards,

Ervin

[ErvinSzolke]

Hi,

could you please first try to trigger an initialize compartment? You do it in the CBS webui after selecting the corresponding buildspace.

Thank you!

Best Regards,

Ervin

[Former Member]

Tried it. No luck.