Skip to Content

EWA has old systems information


We just completed OS migration and upgrade for our ECC and CRM systems, and now are in process of scheduling periodic EWA in solution manager for these systems.

After OS migration and upgrade, our ECC and CRM systems have different hostnames but same SID

And since the SID was already being used in solution manager by old ECC and CRM systems (i.e systems prior to OS migration and upgrade systems), I had to maintain all new ECC and CRM systems with the help of extended SID in solution manager

I have already maintained the NEW systems in solman_setup and solman_workcenter for EWA and the manual processing of EWA for each system works fine

But the periodic EWA gets generated under correct extended SID but information about old systems

The NEW systems are assigned to different logical components in solution manager but same solutions as old systems.

Can someone help to find where is the problem area for periodic EWA still giving information on old systems ?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    May 20, 2015 at 01:22 PM

    What was the need to setup new SIDs in SolMan after upgrading the systems?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member shradha sampat

      Have you verified sdccn on one of the old systems to verify if the schedule task was removed, it might be that they are sending in the info as part of a schedule and SolMan is just collecting off of those remote jobs.

  • avatar image
    Former Member
    May 28, 2015 at 12:36 AM

    Hi Shradha,

    Have you come across this blog:

    It discusses how to correct duplicate entries in the LMDB/SLD. Not sure if it applies to you but I am looking at doing this once we complete migrating our systems to new hardware.

    Add comment
    10|10000 characters needed characters exceeded

  • May 28, 2015 at 01:19 AM

    Hello Shradha,

    Please check / update following points -

    1. Ensure that you have updated ST-PI & ST-A/PI in both Solution Manager & Managed Systems

    2. Ensure that below 3 jobs are periodically running in your Managed system in SDCCN with its default frequency as per sequence -

    a. Refresh Service Definition

    b. Maintenance Package

    c. Refresh Session

    This would most probably fix your issue.

    If not, it would be better to open an OSS message, as it might be a bug that requires some fix.

    Hope this helps.


    Add comment
    10|10000 characters needed characters exceeded