SLD Changelog growth

[Former Member]

We installed SAP SLD systems (NetWeaver 7.3 Java stack only) and connected our DEV/SBX to the design time system and all other systems to the PRD SLD.  We also stood up a backup SLD which is fully synch'd from the PRD SLD.  Since the beginning the changelog grew more than originally expected, but it would take approximately 3 weeks for it to reach over 10 million rows and all of the SLDs grew at approximately the same rate.  Since we upgraded our kernel to 720 on all non-SLD systems and restarted those systems, the rate of changelog growth is approximately 4 Million/DAY.  Incidentally, now only the two SLDs that have systems connected are experiencing this extreme increase, the other is averaging about 16 entries a day. Has anyone else experienced such an astronomical change?

[Former Member]

Hi,

In most cases this issue occured when Data Supplier Circular Redirection
detected.

Check if SLD Bridge Forwarding activated on your system?
If yes then check following note:

SAP Note 1721707 for the symptoms described in it.
1705423 Data Supplier Circular Redirection detected in SLD

delete any circular redirection if exist and it will resolve your issue.

Regards,

VIpin

[sufw]

Hi Vipin,

thank you very much for the pointers! We are currently experiencing the same issue after installing a Java-only 7.31 system and setting up the SLDs.

I think it's odd that note 1705423 recommends not to use circular Data Supplier links, when this always used to work! Neither the SLD planning guide, nor Note 1721707 make the same recommendation, so I would take this with a grain of salt...

Sascha

[Former Member]

Hi Sascha,

Note 1721707 suggest that either you have to remove circular Data Supplier or you have to import the patch mentioned in the note. Please refer the following line from the note:

"It is recommended to remove

the circle, e.g. by removing the forwarding in one direction, until the

SLD patch can be deployed."

Thanks and Regards,

Vipin

[sufw]

Hello all,

I just wanted to report back that we fixed this issue in our SLD landscape. Like Note 1721707 mentioned, if one of the systems in the sync relationship has been patched, then the issue disappears.

Unfortunately the note did not have a patch for our 7.31 SP04 system, so we upgraded to the latest SP05 which fixed the problem 🙂

Sascha