Issues with NWDI after copying to test/dummy NWDI

[former_member188073]

Hi SAPians,

As part of a 7.3 upgrade project we copied two runtime systems and upgraded to 7.3. Whilst upgrading NWDI to 7.3, the live NWDI system started giving problems.

We intended to create everything separate for the dummy code and system migration. We ensure that we have Separate SLD. separate Runtime systems and separate NWDI.

But after starting making changes to teh SLD server and test NWDI, suddenly we found the live NWDI buildspaces affected.

Kindly let us know how to proceed and bring things back to normalcy.

Thanks,

Varun

[former_member188073 · Accepted solution]

Hi Team,

This is what we had done.

• We copied existing NWDI (NW1)
• Installed dummy NWDI for trail upgrades (NW2)
• Created seperate SLD for NW2 and pointed all possible configuration to the new SLD (object server, name server etc).
• The moment we changed the track data in NW2, things changed in NW1 as well. No DCs, changed CBS, etc etc

We changed the CBS and other directories in the tracks in the new NWDI. and we got back our DCs but broken.

It seems while the export was taken the "Move" option take precedence for CBS and CMS.

We had to use the 'CmsSupportTool‘ as the SAP note 973346  and we imported all dependecies again to get things back.

The only thing which we cannot understand, how can we create a test NWDI when by default CMS and CBS gets moved.

What is connectino mechanism that causes the tracks share data between NW1 and NW2

We have been extensively following http://scn.sap.com/docs/DOC-14296

Regards,

Varun

[dao_ha · Accepted solution]

Hi Varun,

If you've been following that doc, you should have read the pages 4-5 of the doc carefully where it mentions the limitations/problems of copying an NWDI system as well as

"After the System Copy is done you are not allowed to use the NWDI/JDI on the source system any more "

I hope you have a good backup that you can restore for your original NWDI system.

In order to have a test NWDI, I'd suggest you install a fresh NWDI and create new tracks.

Hope it helps.

Dao

[Stefan-EA · Accepted solution]

Try deleting a build space for one of your tracks and rebuilding it.

1) Go to the CBS and delete a build space (ie myDevTrack_D)

2) Go to the Landscape Configurator, select the track with the deleted build space and click on Change followed by Save

3) Go to the Transport Studio and go to the Development tab and click the Restore button. In the popup you will see all the build plugin. Select the Reimport button. This will trigger a build of your buildspace a rebuild all your DCs

[former_member188073 · Accepted solution]

Guys,

You are not getting my question. Where is the connection or what is it that makes the source and target NWDI share track data?

Where i changed track data in the target NWDI, it got changed in source as well.

[dao_ha · Accepted solution]

Hi Varun,

Again, you should have read the doc you followed carefully. It is because of 'global unique IDs' which caused them to be modified concurrently as explained in the doc (page 4, 'Problems', the first paragraph).

The doc also clearly mentions that CBS and CMS do not support the 'COPY' option so it'll always be a 'MOVE' for them (page 11).

Dao

[junwu]

don't know what you have done...

don't know what the error is.....

[Stefan-EA]

 
But after starting making changes to teh SLD server and test NWDI, suddenly we found the live NWDI buildspaces affected.

Are the build plugins present (JTECHS, BUILDT, etc)? Take a look at the NWDI build options to see if that helps.