CCDB errors for some JAVA 7.40 systems

[Former Member]

All,

We have solman 7.10 SP13.

Most of the CCDB stuff is all Green for my managed systems!  But I do have a few consistent errors across most of my Pure Java AS 7.40 systems.

See below screen shots

Also, I am going to cut/paste the text of the error that I see:

Upload failed 'Loader error' CX_ELEMENT_CREATION_DATE_2: Store ID '5625B5BF99FB10B0E10080000AE201A8': Element date '20160225022009 ' is older than or equal to store instance date '20160225022009 '. [CX_DIAGST_RETRIEVE_EXCEPTION]

Caused by
Program: CL_DIAGST_STORE===============CP
Include: CL_DIAGST_STORE===============CM012
Source line: 159

I have checked all through the SAP support site for any notes that might be relevant, but I have found none yet!

I checked these notes, but we have them or newer:

1964531

1740720

2169368

1813914

1533668

2110480

Thanks for any help that you can think of!

NICK

[pelle_westerlund1 · Accepted solution]

Another thing I would like to recommend is to utilize "System Recommendations" in Solman_Workcenter. At least there I could find a bunch of potential note corrections for Solman and CCDB etc. Example of notes I found was:

• 2279053 Collective Note for Extractor FWK - ST710
• 263717 Missing table columns in EFWK Admin UI
• 2271942 Service Data Collection Causes Exception C
• 2207857 - ST-SER 701_2010_1 Final Corrections for
• 964531 CCDB: Housekeeper causes red admini task st

If you do not have activated "System Recommendations" I can highly recommend doing so.

[Former Member · Accepted solution]

Hey again Pelle,

The beers sound great to me!

I reviewed / applied these (THANKS):

2271942

2207857

I already had this one:

2279053

But I could not find these you mentioned:

263717 Missing table columns in EFWK Admin UI

964531 CCDB: Housekeeper causes red admini task st

typo?

I think you really meant:

2263717 Missing table columns in EFWK Admin UI

1964531   CCDB: Housekeeper causes red administration task status

and I didn't have 1964531 so thanks again.

and thanks for the tip about sys rec.  never looked at that but I will.

NICK

[pelle_westerlund1 · Accepted solution]

Sorry for the typo, you are absolutely correct, I meant:

• 2263717 Missing table columns in EFWK Admin UI
• 1964531 CCDB: Housekeeper causes red administration task status

About the "System Recommendations" in solman, it is really easy to activate provided that SLD and LMDB are updated with the correct information about the managed system

Happy to help out if I can and always nice to contribute. Let´s see who solves this first, seems like there are more people having the same issue. And then we can celebrate =D

[Former Member · Accepted solution]

"System Recommendations" in solman is an awesome tool!  I really does work.

Thanks for sharing that!

Yes, the race is on!

[Former Member · Accepted solution]

Pelle,

SAP responded with this for me:

The cause of the problem is that there are several CTC configurations
maintained and CCDB does currently support only one. Technically it
means that data with the same key is uploaded more than one time which
finally leads to this error.
One example is ConfigStore "http" where two technical paths are
delivered:
j2ee/cluster_config/system/custom_templates/ZATPL_AIO/cfg/services/http/j2ee/cluster_config/system/custom_templates/kernel.sda/cfg/services/http/
Because this path is not a key field in CCDB an error is raised.
The solution is here to modify the CCDB template to choose the one you
want to load. Here the default is "ZATPL_AIO" and therefore I attached
a template ("ST_SP13-J2EE ENGINE SERVERCORE 7.10-CTC-ZATPL_AIO.xml")
containing this configuration

Solution:
Upload the attached file of this incident as it is described in note
2166834. Afterwards please wait one night and check if the problem is
solved.

So I have this file named: ST_SP13-J2EE ENGINE SERVERCORE 7.10-CTC-ZATPL_AIO.xml

I have uploaded per the note...so just waiting another day or so to see what happens...

**I wish I could attach that XML file here in SCN but I don't see a way.

Email me direct and I'll get it to you.  Assuming you think this'll help your issue as well.

--NICK

[Former Member · Accepted solution]

My last post did resolve the error.  So what SAP gave me for a solution regarding our Solman 7.1 SP13 system did the trick

[KatJohnston]

SAP Support has resolved the issue for us:

It is likely that the problem occurs because a custom template is usedin your environment. For this case our current template definitions donot match by default and have to be adapted manually.Please upload the attached template "J2EE_710_Custom" to your solutionmanager system. The procedure is described in SAP Note 2234877 - RCATemplate for Solution Manager 7.10 SP14

We didn't have a custom template installed but we went ahead and uploaded the Template that SAP had provided. After uploading the template I ran the extractors for the BW Java Systems and we no longer have extractors in Error Status.

[KatJohnston]

I have also come across the same issue with some Java 7.40 Systems. I feel I have exhausted all troubleshooting options and have raised a message with SAP. No response yet received.

We are SolMan SP14 (LM-SERVICE 7.10 SP14 patch 2).

The issue is only happening with our BW Java 7.40 systems. Our PO Java 7.40 systems have no errors in the CCDB. Both environments are on SPS13.

[pelle_westerlund1]

Same here, our PI systems does not have this issue, only BW Java portals running on NW 7.40. Seems like SAP has some explaining to do

[pelle_westerlund1]

Did you get any luck with this? I am facing the same issue

ps, I found sapnote http://service.sap.com/sap/support/notes/2179984 and that points to fixed issues in the related notes below witch is a lot!!

So it basically suggest that you update LM-SERVICE component for Solution Manager.

I patched from 7.10.13.0 to 7.10.13.4. so I am very excited to see if I get any bugfixes and improvment next couple of days.

Cheers

2208517		Root Cause Analysis log file meta-description not supporting non-standard field names
2203243		EXM: Severity displayed in cockpit is always of type Error
2201563		Exception Management - collector issues with SAP Convergence Charging Sytem logs
2200363		Outside Discovery: improving log traces
2196103		Disable HostAgent versioninfo check for Diagnostics Agents On-the-fly
2195279		Diagnostics Agents On-the-fly: fallback to single node fails
2195070		Exception Management collector for 3rd party components is failing: Number of fields does not match
2191356		Introscope Transaction traces missing for Agent 9.5 and higher
2189016		EEM Trace Extractor fails with IllegalArgumentException when collecting traces for SAPGUI-based scri...
2183337		Agent disconnects with Ping failed error when Solution Manager is in cluster
2183051		Diagnostics Agents Administration: table size error due to bad i18n handling
2180687		E2E Exception Analysis - reading the Eventlog for Windows Server 2012 fails
2179915		CCDB improvements for SAP CC
2178661		Variables are not replaced in CCDB Template for type WS
2177818		Diagnostics Agent smdsetup script throws NoClassDefFoundError for SLD configuration
2106825		SAP Host Agent status is missing in the Diagnostics Agents Administration
1962932		HTTP 401 Unauthorized error resulting in false alerts
1833171		Introscope Host Adapter Setup compatibility
1333571		E2E Exception Analysis

[mamartins]

Hi there,

Nice work!

Did you just patched the LM-SERVICE? Usually, this component have dependencies, and you need to patch them also. When you go to SAP SUPPORT PORTAL to do the download, there is an option to check for dependencies for each JAVA component patch.

Regards,

MM

[pelle_westerlund1]

Actually, I patched ISAGENT as well but for LM-SERVICE it did not have any dependencies. It went fine patching through SUM. However, issues still remains so no difference from the patching I am afraid. I will open up an OSS ticket.

Also, there is a really good wiki around this behaviors that I would recommend, I have seen it in another SCN thread also but here it is:

https://wiki.scn.sap.com/wiki/display/TechOps/Troubleshooting+Workload+Analysis+data+for+ABAP%2C+JAV...

[Former Member]

Hey Pelle,

I've had a message open for a few weeks now.  Nothing has been resolved yet.  Still going back and forth with SAP support.

But in terms of notes, I think I exhausted my search both for notes/threads and google.  so I'm leaving it in SAP hands now.  For me, opening a message is an absolute last resort.  Like you, I try to figure it out on my own if I can.

Thanks for responding with that info though.  Also, in regard to that other post, I have LM-SERVICE 7.10 SP13 patch4 which was the latest as of last month.  And yes, I always check those dependencies before deploying any individual java component.

NICK

[pelle_westerlund1]

Good old SAP Support Let me know if you get an explanation/solution for this ugly issue and I will bring you beer anytime =D I will post here if I get anything from the OSS ticket. Good luck Nick.

Cheers