on 04-01-2015 3:16 PM
Hi All,
I am moving Portal application project to NWDI.
I am able to build and check in the activity to DTR. But activation requests are failing.
I am getting Build log
Build number assigned: 223
Change request state from QUEUED to PROCESSING
REQUEST PROCESSING started at 2015-04-01 11:49:56.244 GMT
ACTIVATION request in Build Space "NDG_MERP3N_D" at Node ID: 798,620,250
[id: 225; parentID: 0; type: 4]
[options: FORCE ACTIVATE PREDECESSORS]
Waiting for access: 5 ms
===== Pre-Processing ===== started at 2015-04-01 11:49:56.249 GMT
List of requested for activation activities:
''com.jnj.mercury_MER_P3N_1'' compartment
LKODAVAT_1APR15_AGLogoff
[ISN 63][created by 643003319 at 2015-04-01 07:49:33.0][OID 9247e2efd85811e497be00002f99fa5a]
There is 1 activity in compartment com.jnj.mercury_MER_P3N_1
1 activity will be processed by this request
Analyze dependencies to predecessor activities... started at 2015-04-01 11:49:56.290 GMT
Analyzing predecessors in compartment "com.jnj.mercury_MER_P3N_1"
2 not activated predecessors are detected
The following activities are being added to request:
"15JAN15_NWDI_LKODAVAT" [seq. no 40][created by 643003319 at 1/16/15 2:27 AM][ID c5a51e719cad11e4c4ab00002f99fa5a]
"LKODAVAT_30MAR15_Aglogoff" [seq. no 53][created by 643003319 at 3/30/15 7:27 AM][ID ee776076d6c311e4a7bd00002f99fa5a]
Analyze dependencies to predecessor activities... finished at 2015-04-01 11:49:56.305 GMT and took 15 ms
Analyze versions... started at 2015-04-01 11:49:56.305 GMT
List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2015-04-01 11:49:56.352 GMT and took 47 ms
Resource "/SCs/com.jnj.mercury/MER_P3N/_comp/TopLevelDCs/com.jnj.mercury aglogoff.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/com.jnj.mercury/MER_P3N/_comp/TopLevelDCs/com.jnj.mercury aglogoff.dcref'. URL does not point to DCs root directory.
Synchronize metadata for [com.jnj.mercury/aglogoff] started at 2015-04-01 11:49:56.380 GMT
Verification of DL [ws/MERP3N/com.jnj.mercury_MER_P3N/dev/active/] finished at 2015-04-01 11:49:56.397 GMT and took 8 ms
Verification of cache (level 2: Comparison of attributes) finished at 2015-04-01 11:49:56.404 GMT and took 7 ms
Synchronize metadata for [com.jnj.mercury/aglogoff] finished at 2015-04-01 11:49:56.404 GMT and took 24 ms
< CREATE > ''com.jnj.mercury/aglogoff'' DC
Analyze versions... finished at 2015-04-01 11:49:56.406 GMT and took 101 ms
Analyze activities... started at 2015-04-01 11:49:56.406 GMT
Loading component definitions
1 component to be build in compartment "com.jnj.mercury_MER_P3N_1"
Analyze activities... finished at 2015-04-01 11:49:56.419 GMT and took 13 ms
Calculate all combinations of components and variants to be built...
Analyze request DC BV... started at 2015-04-01 11:49:56.436 GMT
''com.jnj.mercury/aglogoff'' variant ''default''
''com.jnj.mercury/aglogoff'' variant ''default'' cannot be built. ACTIVATION will fail.
Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
Analyze request DC BV... finished at 2015-04-01 11:49:56.450 GMT and took 14 ms
===== Pre-Processing ===== finished at 2015-04-01 11:49:56.452 GMT and took 203 ms
Change request state from PROCESSING to FAILED
Error! The following problem(s) occurred during request processing:
Error! The following error occurred during request processing: Activation failed due to component "com.jnj.mercury/aglogoff" variant "default". The component is BROKEN.
REQUEST PROCESSING finished at 2015-04-01 11:49:56.452 GMT and took 208 ms
No build logs available for the request.
Regards,
Narayana
Hi Narayana,
As per the your original post log, plesae see below
"Analyze dependencies to predecessor activities... started at 2015-04-01 11:49:56.290 GMT
Analyzing predecessors in compartment "com.jnj.mercury_MER_P3N_1"
2 not activated predecessors are detected"
As per the above log, you are having some predecessors.
Go to DTR and and check your open activities and take action accordingly.
As Ervin mentioned, please paste the screen shot & log to understand well.
Thanks,
Hamendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
...
you might as well have a look on this TSG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
ok, then now click on the row NDG_MERP3N_D and then on the next view sort per "Broken DCs". After this select the line where you can see the broken DCs and on the lower table select "Broken by iself".
Click on the DC and then investigate the "Request Log" and the "Build Log" (if this one available).
Cheers,
Ervin
Hello Narayana,
In the post from Apr 2, 2015 6:21 PM (your lastly attach screenshot)
you have shown NDG_MERP3N_D - this is the Development buildspace.
After that in the post from Apr 2, 2015 6:21 PM you are showing (as far as I see NDG_MERP3N_C or at least a buildspace that finishes with 'C') - Consolidation buidspace!
So please consider carefully what Ervin suggested in Apr 2, 2015 2:32 PM
Please go to NDG_MERP3N_D and try to find out the Broken DCs (by sorting the column).
In addition you have many SCs which have not been imported in the CBS (it might be seen in the column Total DCs). Please check-in in CMS and re-import.
Regards
Milen
Hi Narayana,
could you please trigger "Initialize" compartment and see whether the 15 broken DCs are disappearing? Perhaps this is some kind of display problem that is misleading us.
However: the logs are telling the same that you have broken DCs and that cannot be a display issue.
Best Regards,
Ervin
Hi,
another important thing, maybe you tried but I rather mention it to be on the safe side:
Can you see the black arrow in the table column header "Sources" on your latest screenshot?
That means the column is sorted as per that column and sorted in a descending way (down arrow is filled).
Could you please send a screenshot where we can see that before making the screenshot you have clicked the "Broken DCs" column ?
Thank you and Regards,
Ervin
Hi Narayana,
Please use this TSG for more directions:
Please pay attention to those DCs which the DC has invalid metadata & the DC build failed.
Is there available a build log? If so please provide provide it (or at least the messages with the error in it).
Else please provide the request log.
Regards
Milen
Hi,
focus on the lines where you have red lamp for "Compile state".
if you click on the link (in column "DC name", see your last screenshot for example) then on the next screen you'll find links for "Request log" and "Build log". Request log will be always available, Build log sometimes not (in case build could not be triggered, e.g. due to missing DC dependencies).
Send us the content of the Request Log and Build log. If possible check more broken DCs with red compile state and so attach more logs, because there can be different reasons for brokenness for different DCs (most likely the reason will be the same or similar, but there can be various reasons depending on which log of which broken DC you are investigating).
For more directions refer to the guide Milen pointed out.
Thank you and Regards,
Ervin
Hello Narayana,
Which version of NWDI do you use?
What kind of data base management system do you use?
Regards,
Milen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.