Broken DC in CBS Consollidation Build space

[susmita_panigrahi]

Hi All

When i assembled the activity in CMS server assembling of components got failed.Reason was Broken DC exist in CBS Consollidation build space.

I have compared the CBS Development build space and CBS consollidation build space one difference i found that in CBS Consollidation build space under the column Total DC is that number of DC is Zero for the SC Name BI_UDI,SAP-JEE,SAP_BUILDT,SAP_JTECHS.

Can any body help me how to solve Broken DC problem in the CBS Consollidation Build space?

CBS Log is as follows:

Build number assigned: 1925

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "XWD_ETOOLS_C" at Node ID: 289,619,750

[id: 1,873; parentID: 0; type: 4]

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

REQUEST PROCESSING started at 2008-07-08 09:51:16.474 GMT

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

Waiting 6 ms

List of activities to be activated:

1 activity in compartment "wartsila.com_ETOOLS_1"

SPAX08_08072008_AdvanceSearchModule_ACN44341

[seq. no 129][created by SPAX08 at 2008-07-08 09:50:57.0][ID bfe2a18f4cc211dd9a0e000f203c93e0]

Analyse dependencies to predecessor activities... started at 2008-07-08 09:51:16.486 GMT

Analysing predecessors in compartment "wartsila.com_ETOOLS_1"

No dependencies to predecessor activities found.

Analyse dependencies to predecessor activities... finished at 2008-07-08 09:51:16.558 GMT and took 72 ms

Analyse activities... started at 2008-07-08 09:51:16.559 GMT

Analyse dependencies to predecessor activities... finished at 2008-07-08 09:51:16.839 GMT and took 249 ms

SKIP : Development Component "wartsila.com/AdvancedSearchModule"

No components to be build in compartment "wartsila.com_ETOOLS_1"

Analyse activities... finished at 2008-07-08 09:51:16.877 GMT and took 318 ms

Change request state from PROCESSING to PROCESSING

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

"wartsila.com/AdvancedSearchModule" variant "default"

"wartsila.com/AdvancedSearchModule" variant "default" IS BROKEN. The component therefore cannot be built and will be marked as BROKEN.

[DC 201 variant "default"][SC 388 "wartsila.com_ETOOLS_1"][last successful build: 0]

Prepare build environment in the file system... started at 2008-07-08 09:51:16.885 GMT

Synchronize development configuration... finished at 2008-07-08 09:51:16.887 GMT and took 2 ms

Synchronize component definitions... finished at 2008-07-08 09:51:16.887 GMT and took 0 ms

Synchronize sources...

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

Synchronize sources... finished at 2008-07-08 09:51:16.888 GMT and took 1 ms

Synchronize used libraries...

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

Synchronize used libraries... finished at 2008-07-08 09:51:16.888 GMT and took 0 ms

Prepare build environment in the file system... finished at 2008-07-08 09:51:16.888 GMT and took 3 ms

===== Pre-Processing ===== finished at 2008-07-08 09:51:16.890 GMT and took 410 ms

Waiting 2 ms

===== Processing =====

===== Processing ===== finished at 2008-07-08 09:51:16.892 GMT and took 0 ms

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

Waiting 6 ms

Change request state from PROCESSING to PROCESSING

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

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

Update component metadata...

STORE build results...

"wartsila.com/AdvancedSearchModule" in "default" variant was not built and has no build results to store.

"wartsila.com/AdvancedSearchModule": store meta-data

"wartsila.com/AdvancedSearchModule" in "default" variant is PROCESSED

Change request state from PROCESSING to SUCCEEDED

Analyse effect of applied changes to buildspace state... started at 2008-07-08 09:51:17.160 GMT

INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts.

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/com.sap.aii.proxy.framework [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/com.sap.aii.util.misc [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/cmi [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/ddic/ddicruntime [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/ddic/metamodel/content [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/wdp/metamodel/content [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/bi/bp/webDynpro [public-part: webDynpro] AS Build Plugin Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/com.sap.exception [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/com.sap.mw.jco [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/logging [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES UNKNOWN DC: sap.com/tc/wd/webdynpro [public-part: default] AS Build-Time Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]

Handle Cycles...

No cycles detected.

No Collateral Internal Build Requests found

Determine components that have become DIRTY due to the results of this request...

No such components have been found.

Integrate activities into active workspace(s)...

Integration of activities in compartment "wartsila.com_ETOOLS_1" started at 2008-07-08 09:51:17.231 GMT

"SPAX08_08072008_AdvanceSearchModule_ACN44341" OK

Integration of 1 activities in compartment "wartsila.com_ETOOLS_1" finished at 2008-07-08 09:51:17.714 GMT and took 483 ms

Analyse effect of applied changes to buildspace state... finished at 2008-07-08 09:51:17.714 GMT and took 554 ms

Request SUCCEEDED

===== Post-Processing ===== finished at 2008-07-08 09:51:17.717 GMT and took 819 ms

REQUEST PROCESSING finished at 2008-07-08 09:51:17.717 GMT and took 1 s 243 ms

Thanks & Regards

Susmita

[Former Member · Accepted solution]

Susmita,

try to check out that DC from consolidation build space and see if there are any compilation errors.then try to repair ,reload the project and reopen NWDS.

[susmita_panigrahi]

Hi

basis team sole the issue by re importing the SCA into track.

[snehal_kendre]

HI Sushmita,

There is nothing wrong in your developed DCs, just standerd build time dependecies are not in your consolidation compartment. so you need to import them again into consolidation

1. If you dependecies are imported in cosolidation at the time of track creation and now they are not there then

do one thing. go to cms->transport studio->consolidation-> there you have a option of history. choose the date and e it will show you all the dependecies.

select all and then say back to import queue

so you will get all you dependecies in import queue. after that re-import it again.

check your consolidation compartment in CBS. it will show no of DCs for standerd SCs and all broken DCs will be build again.

2. IF not then perform import from check in to production

[susmita_panigrahi]

Hi Snehal,

I have checked the Consolidation and i found that the build dependcies which is showing import finished is the old date that is jan 2007.

Actually one month back Assemble tab was disappeared in CMS server.After that Basis team re import the SC into the track.After reimporting the SC only we are getting build dependency error in CBS Development and Consolidation build space.On 2nd july 2008 they have reimported the required dependecy till Production.after this we are not getting any broken DC in CBS development build space, however still the problem exist (Build dependency error) in consollisation build space of CBSspace.

I have checked the history of consollidation i am not getting any dependency which was imported on 2nd july.The build dependency which is present in consollidation history page is the much oldest one (Jan 2007).I think basis team did some mistake.

Could you please tell the procedure so that we can inform the basis team (HP 3rd party) what they need to do?

Thanks & Regards

Susmita

[snehal_kendre]

HI Sushmita,

The complete import cycle can be performed only once.

after that importing same version of SCs from checkin to production has no effect.

so tell your basis team that. or you can also do that.

If by any reasson the standerd dependecies are not present at any compartment then just go to its history then it will show all the dependencies.

select all dependecies and say back to import queue

in import you will get that dependecies then again import them.

these are only steps to follow

[susmita_panigrahi]

Hi Duwuri,

I have checked the DC.Error was in Used DC.But our application doden't use an used dc (child dc) except default used dc i.e sap.com/com.sap.aii.proxy.framework etc.When we are syncing the DC from the track these used DC by default are synced from the track.The broken DC error shows that Used DC sap.com/com.sap.aii.proxy.framework is unknown.

Could you please provide your inputs for the above error message in consollidation track?

Thanks & Regards

Susmita