Solved: CMS import failure - ESS (Dirty DC)

Former Member · ‎09-14-2006

Hi jdi gurus,

Please help out ...

the MSS, pcui, buildt, jee, jtech packages have been imported successfully into development and consolidation.

however the ess package is not being imported into development.

with respect,

amit

WebAS 640, EP 6.0, SP 13 on Windows with MS SQL server, ESS 100, SP 9.

CMS-make

Info:Starting Step CBS-make at 2006-09-14 17:03:44.0842 +12:00

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

Info:waiting for CBS queue activity

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

Info:waiting for CBS queue activity

Info:build process already running: waiting for another period of 30000 ms (1)

Info:CBS server log has been written to CBS log

Fatal:the compartment sap.com_SAP_ESS_1 contains dirty DCs after the CBS build process:

Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre dcvendor=sap.com)

Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre/trs dcvendor=sap.com)

Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process

Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-09-14 17:04:18.0077 +12:00

CBS Log :-

CBS Request Log - [ 295/EPD_ESSTrack_D ]

devep SAP Component Build Server

Build number assigned: 305

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050

[id: 295; parentID: 0; type: 4]

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

REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT

===== Pre-Processing =====

List of activities to be activated:

The following components belong to activities which already have been activated before:

sap.com/ess/tra/tre/trs

sap.com/ess/mx/addr

sap.com/ess/fr/addr

sap.com/ess/tra/trp

sap.com/ess/de/fam

sap.com/ess/br/addr

sap.com/ess/tra

sap.com/ess/au

sap.com/ess/tra/tre

sap.com/ess/it/pdata

sap.com/ess/hk/fam

sap.com/ess/us/pdata

sap.com/ess/tw/fam

sap.com/ess/sg/addr

sap.com/ess/de/pdata

sap.com/ess/ca/addr

sap.com/ess/kr/bank

sap.com/ess/be/fam

sap.com/ess/us

sap.com/ess/kr/fam

sap.com/ess/ar/addr

sap.com/ess/hk/addr

sap.com/ess/ph/pdata

sap.com/ess/wtcor

sap.com/ess/us/addr

sap.com/ess/at/addr

sap.com/ess/mx/pdata

sap.com/ess/wiw

sap.com/ess/ca/empeq

sap.com/ess/th/bank

sap.com/ess/dk/fam

sap.com/ess/tw/bank

sap.com/ess/th/pdata

sap.com/ess/grt/srv

sap.com/ess/be/bank

sap.com/ess/mx/fam

sap.com/ess/es/fam

sap.com/ess/at/pdata

sap.com/ess/ie/fam

sap.com/ess/ch/fam

sap.com/ess/id/addr

sap.com/ess/xx

sap.com/ess/ca/pdata

sap.com/ess/nz/pdata

sap.com/ess/de/dcomp

sap.com/ess/gb/pdata

sap.com/ess/au/addr

sap.com/ess/th/fam

sap.com/ess/cn/bank

sap.com/ess/ve/bank

sap.com/ess/nl/fam

sap.com/ess/es/bank

sap.com/ess/sg/perid

sap.com/ess/skl

sap.com/ess/cat

sap.com/ess/nl/addr

sap.com/ess/fr/pdata

sap.com/ess/se/pdata

sap.com/ess/au/bank

sap.com/ess/ben

sap.com/ess/lea

sap.com/ess/it/addr

sap.com/ess/ie/bank

sap.com/ess/au/pdata

sap.com/ess/th/pid

sap.com/ess/be/pdata

sap.com/ess/id/bank

sap.com/ess/de/addr

sap.com/ess/nz/bank

sap.com/ess/tra/tri

sap.com/ess/jp/addr

sap.com/ess/au/rep

sap.com/ess/us/w4

sap.com/ess/us/bank

sap.com/ess/rep

sap.com/ess/nz/addr

sap.com/ess/za/pdata

sap.com/ess/tra/trr

sap.com/ess/cn/addr

sap.com/ess/de

sap.com/ess/be/addr

sap.com/ess/tw/pdata

sap.com/ess/my/addr

sap.com/ess/hk/perid

sap.com/ess/cod

sap.com/ess/th/addr

sap.com/ess/gb/fam

sap.com/ess/au/tax

sap.com/ess/us/fam

sap.com/ess/ch/pdata

sap.com/ess/ca/bank

sap.com/ess/ie/addr

sap.com/ess/ca/fam

sap.com/ess/za/fam

sap.com/ess/se/bank

sap.com/ess/jp/bank

sap.com/ess/fr/fam

sap.com/ess/ve/fam

sap.com/ess/ve/pdata

sap.com/ess/sg/fam

sap.com/ess/ph/bank

sap.com/ess/sg/bank

sap.com/ess/au/fam

sap.com/ess/sg/pdata

sap.com/ess/sg

sap.com/ess/ve/addr

sap.com/ess/com

sap.com/ess/ar/pdata

sap.com/ess/gb/addr

sap.com/ess/nl/pdata

sap.com/ess/kr/addr

sap.com/ess/tw/pid

sap.com/ess/no/pdata

sap.com/ess/cn/fam

sap.com/ess/hk/bank

sap.com/ess/es/pdata

sap.com/ess/pt/bank

sap.com/ess/se/fam

sap.com/ess/id/fam

sap.com/ess/dk/pdata

sap.com/ess/jp/pdata

sap.com/ess/no/fam

sap.com/ess/at/bank

sap.com/ess/it/fam

sap.com/ess/per

sap.com/ess/br/fam

sap.com/ess/ie/pdata

sap.com/ess/pt/pdata

sap.com/ess/gb/bank

sap.com/ess/hk/pdata

sap.com/ess/my/pdata

sap.com/ess/jp/fam

sap.com/ess/za/bank

sap.com/ess/tw/addr

sap.com/ess/mx/bank

sap.com/ess/ar/bank

sap.com/ess/cn/pdata

sap.com/ess/pt/addr

sap.com/ess/at/fam

sap.com/ess/rem

sap.com/ess/my/bank

sap.com/ess/it/bank

sap.com/ess/br/pdata

sap.com/ess/nl/bank

sap.com/ess/ch/addr

sap.com/temp/testit0188

sap.com/temp/testit0185

sap.com/temp/testit0006_au

sap.com/temp/pers_data_sg

sap.com/temp/essmenu

sap.com/temp/ESS_Homepage

sap.com/temp/bentest

sap.com/temp/address_sg

sap.com/ess/id/pdata

sap.com/ess/de/bank

sap.com/ess/tim

sap.com/ess/my/fam

sap.com/ess/se/addr

sap.com/ess/kr/pdata

sap.com/ess/ar/fam

sap.com/ess/no/bank

sap.com/ess/pt/fam

sap.com/ess/nz/fam

sap.com/ess/no/addr

sap.com/ess/tra/trp/trt

sap.com/ess/dk/bank

sap.com/ess/ph/fam

sap.com/ess/ch/bank

sap.com/ess/es/addr

sap.com/ess/id/pid

sap.com/ess/org

sap.com/ess/dk/addr

sap.com/ess/ph/addr

sap.com/ess/my/pid

sap.com/ess/za/addr

sap.com/ess/fr/bank

sap.com/ess/br/bank

sap.com/ess/tri

sap.com/ess/trt

sap.com/ess/tev

They will be removed from this request.

Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT

Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

Analyse activities... started at 2006-09-14 05:03:52.733 GMT

Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

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

Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT

Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

Synchronize sources...

...Skipped for Activation with option : IGNORE BROKEN DC

Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

Synchronize used libraries...

...Skipped for Activation with option : IGNORE BROKEN DC

Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms

===== Pre-Processing ===== finished at 2006-09-14 05:03:52.733 GMT and took 438 ms

===== Processing =====

===== Processing ===== finished at 2006-09-14 05:03:52.748 GMT and took 0 ms

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

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

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

Update component metadata...

STORE build results...

Change request state from PROCESSING to SUCCEEDED

Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT

Handle Cycles...

No cycles detected.

Determine components that have become DIRTY due to this request...

No such components have been found.

Integrate activities into active workspace(s)...

Nothing to integrate in compartment sap.com_SAP_ESS_1

Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms

Request SUCCEEDED

===== Post-Processing ===== finished at 2006-09-14 05:03:53.327 GMT and took 563 ms

REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms

Message was edited by: Amit Chawathe

Former Member · ‎09-19-2006

Hi Marc,

Sorry for the delayed 'i dunno where to get the build log' answer ..

Could you please let me know wher i might be able to locate it ?

with respect,

amit

Former Member · ‎09-18-2006

Hi Marc,

Thank you for your time and attention to the problem at hand. It is most appreciated.

The CBS log life of the request in question is pasted below.Please let me know if there is any more information you would require.