All DCs of ESS Mentioned as Dirty DCs in the track

[Former Member]

Hi,

We are using a Track in the ESS for the Changes.

All were working fine , we were able to check in code and activate also.

Some changes done in the Track and now i saw that all the DCs in the track are in the Broken state.

In NWDS , we are getting a new configuration messdage.

If we are using the new configuration, we are getting lots of error in the DC.

The below is the error trace in the CBS:

Analyze effect of applied changes to buildspace state... started at 2009-04-21 11:57:50.487 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.

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/bi/bp/webDynpro' DC, does not exist [public-part: webDynpro] AS Build Plugin Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.aii.proxy.framework' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.aii.util.misc' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/cmi' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/ddic/ddicruntime' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/ddic/metamodel/content' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/wdp/metamodel/content' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.exception' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.mw.jco' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/logging' DC, does not exist [public-part: default] AS Build-Time Dependency

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

'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/wd/webdynpro' DC, does not exist [public-part: default] AS Build-Time Dependency

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

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

Thanks,

Anumit

[Former Member · Accepted solution]

Re-import the base SCA's (SAP_BUILDT, SAP-JEE, etc.); your track seems to be missing them.

Edited by: Pascal Willemsen on Apr 22, 2009 8:13 AM

[Former Member · Accepted solution]

Hi,

I reimported the same again but getting the below error in CBS build:

20090421211210 Error :Resetting to old mode (open) failed. The reset is tried once again with new CBS connection

20090421221210 Error :CBS throws exception during setting input mode (to open):

20090421221210 Error :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out):Read timed out (Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out)

thanks,

Anumit

[Former Member · Accepted solution]

Check the state of the _D buildspace in CBS. It should be set to Open. You can change it to Open using the CBS WebUI.

[Former Member · Accepted solution]

Thanks Pascal,

Now , i am able to reimport the mentioned DCs. But when i am activating any activity then getting the below error log:

Build number assigned: 11970

Change request state from QUEUED to PROCESSING

REQUEST PROCESSING started at 2009-04-22 08:31:05.378 GMT

ACTIVATION request in Build Space "EPD_XSSTRACK_D" at Node ID: 15,357,950

[id: 10,985; parentID: 0; type: 4]

[options: NO OPTIONS]

Waiting for access: 58 ms

===== Pre-Processing ===== started at 2009-04-22 08:31:05.437 GMT

List of requested for activation activities:

'sap.com_SAP_ESS_1' compartment

medicalrem_remove_info_from _test

[ISN 53][created by J2EE_ADMIN at 2009-04-14 14:33:18.0][OID 95c9ff2928d211de878900144fa0ee66]

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 2009-04-22 08:31:05.667 GMT

Analyzing predecessors in compartment "sap.com_SAP_ESS_1"

No dependencies to predecessor activities found.

Analyze dependencies to predecessor activities... finished at 2009-04-22 08:31:05.801 GMT and took 134 ms

Analyze versions... started at 2009-04-22 08:31:05.802 GMT

List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2009-04-22 08:31:06.454 GMT and took 527 ms

Synchronize metadata for [sap.com/medirem] started at 2009-04-22 08:31:06.510 GMT

Verification of DL [ws/XSSTRACK/sap.com_SAP_ESS/dev/active/] finished at 2009-04-22 08:31:06.623 GMT and took 39 ms

Verification of cache (level 2: Comparison of attributes) finished at 2009-04-22 08:31:06.696 GMT and took 72 ms

Synchronize metadata for [sap.com/medirem] finished at 2009-04-22 08:31:06.702 GMT and took 192 ms

< CHANGE > 'sap.com/medirem' DC

Analyze versions... finished at 2009-04-22 08:31:06.704 GMT and took 902 ms

Analyze activities... started at 2009-04-22 08:31:06.705 GMT

Loading component definitions

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

Analyze activities... finished at 2009-04-22 08:31:06.793 GMT and took 88 ms

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

Analyze request DC BV... started at 2009-04-22 08:31:06.824 GMT

'sap.com/medirem' variant 'default'

Analyze request DC BV... finished at 2009-04-22 08:31:07.510 GMT and took 686 ms

Prepare build environment in the file system... started at 2009-04-22 08:31:07.511 GMT

Synchronize development configuration... started at 2009-04-22 08:31:07.512 GMT

Synchronize development configuration... finished at 2009-04-22 08:31:07.517 GMT and took 5 ms

Synchronize sources for [sap.com/medirem] started at 2009-04-22 08:31:07.563 GMT

Verification of DL [ws/XSSTRACK/sap.com_SAP_ESS/dev/active/] finished at 2009-04-22 08:31:13.251 GMT and took 47 ms

Verification of cache (level 2: Comparison of attributes) finished at 2009-04-22 08:31:14.615 GMT and took 1 s 363 ms

Synchronize sources for [sap.com/medirem] finished at 2009-04-22 08:31:15.273 GMT and took 7 s 710 ms

Synchronize used libraries... started at 2009-04-22 08:31:15.584 GMT

DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.

Used DC 'sap.com/tc/cmi' HAS NO PUBLIC PART 'default'.

[DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 211 variant 'default'][SCID=76][last successful build: 11532]

DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.

Used DC 'sap.com/tc/ddic/ddicruntime' HAS NO PUBLIC PART 'default'.

[DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 217 variant 'default'][SCID=76][last successful build: 11532]

DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.

Used DC 'sap.com/tc/ddic/metamodel/content' HAS NO PUBLIC PART 'default'.

[DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 218 variant 'default'][SCID=76][last successful build: 11532]

DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.

Used DC 'sap.com/tc/wd/webdynpro' HAS NO PUBLIC PART 'default'.

[DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 85 variant 'default'][SCID=72][last successful build: 11532]

DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.

Used DC 'sap.com/tc/logging' HAS NO PUBLIC PART 'default'.

Synchronize used libraries... finished at 2009-04-22 08:31:18.845 GMT and took 3 s 261 ms

===== Pre-Processing ===== finished at 2009-04-22 08:31:18.878 GMT and took 13 s 441 ms

Change request state from PROCESSING to FAILED

Thanks,

Anumit

[Former Member · Accepted solution]

Which SP/Patch level are you importing? Does the SAP Marketplace list any newer patchlevels for these SC's?

[Former Member · Accepted solution]

HI ,

We are using ESS 1.0 sp15.

The error is appearing ,when i am changing a application(Using NWDS) and after chech-in and activation. Check-In is perfect but activation of the activity is failing.

Thanks,

Anoop

[Former Member · Accepted solution]

Please specify SP and patchlevels for all SC's that are in your track.

[Former Member · Accepted solution]

Hi,

Please find the details below:

SAP-JEE 7.00 SP15

SAP_JTECHS 7.00 SP15

SAPPCUI_GP 600 SP12

SAP_ESS 600 SP0

Thanks,

Anumit

[Former Member · Accepted solution]

You are missing SAP_BUILDT and EP_BUILDT. Besides that, you may require SP18 of SAP_JTECHS, SAP-JEE, SAP_BUILDT and EP_BUILDT, since SP18 was released around the same time that ESS SP15 was released.

[Former Member · Accepted solution]

Hi Pascal,

I forgot to put the below:

SAP_BUILDT 7.0 sp 15

EP_BUILDT 7.0 sp15

We are able to activate Activities before but after changing runtime system it is not working.

We put the same runtime system now, but not able to activate activities.

Thanks,

anumit

[Former Member · Accepted solution]

After changing Development/Consolidation runtime systems you need to perform a Restore System State. Effectively this re-imports and rebuilds the Base SC's and all dependent SC's. You can reimport them yourself as well by using the Development/Consolidation History to re-add these SC's to the import queue and then import them.

[Former Member · Accepted solution]

Hi,

Could you please guide me that how to perform a Restore System State.

Thanks,

[Former Member · Accepted solution]

That's what the last sentence of my previous reply is telling you...