cancel
Showing results for 
Search instead for 
Did you mean: 

SolMan 7.1 SP4: Diagnostics data upgrader ended with errors

former_member313130
Participant
0 Kudos

Hi,

after installation of SP4 for our SolMan 7.1 I tried to make the post activities. I got the

following error in step "Solution Manger Internal Connectivity":

"Diagnostics data upgrader ended with errors"

Details:

-


Upgrade Information: Executed Wed, 4 Jan 2012 08:56:48 +0100 for the version 7.10 SP4 (1000.7.10.4.0.20111125140311)

Name Description Last Upgrade Status

WEBADMIN Upgrade Upgrades WEBADMIN RFC Destination (HA compatibility). Success in 11ms.

E2E Trace reorganization Reorganizes E2E Traces that have been recorded before version 7.01.6 (SP22) Patch 1 Success in 136ms.

E2E BI Data Upgrade Upgrades E2E-related BI data. Success in 16672ms.

Wily Enterprise Managers Migration Wily Enterprise Managers Migration to Robomate Success in 274ms.

Technical System Paths Migrate the Technical System paths stored in SMSY. Success in 86ms.

Setup Data Upgrade Upgrades Setup status and history. Fail in 923ms.

Scheduler Upgrade Upgrades Scheduler tasks and logs. Success in 288ms.

Report Upgrade for Setup Data Upgrade

-


Status: Fail in 923ms.

Upgrade Result:

0 properties were successfully moved from java global configuration to setup configuration

10 properties were successfully deleted from java global configuration.

A failure occured during the upgrade of setup data : systems could not be retrieved from Landscape DB (SMSY)

!! Exception : Cannot retrieve the Grouped Technical System list!(cause=com.sap.sup.admin.abap.rfc.exception.RfcExecutionException An exception occured during the execution of the function 'FM_DIAGLS_GET_GRP_TECH_SYSTS': Cannot retrieve all CIM Instances from CIM class name 'SAP_SUPCluster' via LMDB Mass Access API)

0 Technical Systems were updated and saved in Generic Storage

Setup Messages have already been migrated to Robomate logs during a previous execution of the upgrader

Upgrade of Setup data : done with the upgrade of 0 system (grouped TS) definitions

Exception Cause:

java.lang.IllegalStateException: com.sap.sup.admin.abap.landscape.exception.AbapLandscapeRetrieveException: Cannot retrieve the Grouped Technical System list!

at com.sap.sup.admin.abap.landscape.factory.impl.AbapRfcLandscapeFactory.getGroupedTechnicalSystems(AbapRfcLandscapeFactory.java:1033)

at com.sap.sup.admin.setup.LandscapeAdapter.getSapClusters(LandscapeAdapter.java:91)

at com.sap.sup.admin.setup.SetupUpgrader.execute(SetupUpgrader.java:46)

at com.sap.smd.SMDUpgradeManager.executeUpgrade(SMDUpgradeManager.java:227)

at com.sap.sup.admin.setup.ManagingServices.runUpgrader(ManagingServices.java:2544)

at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:541)

at com.sap.sup.admin.setup.SetupStep$StepRunner.run(SetupStep.java:729)

at java.lang.Thread.run(Thread.java:770)

Caused by: com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: An exception occured during the execution of the function 'FM_DIAGLS_GET_GRP_TECH_SYSTS': Cannot retrieve all CIM Instances from CIM class name 'SAP_SUPCluster' via LMDB Mass Access API

at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:111)

at com.sap.sup.admin.abap.landscape.factory.impl.AbapRfcLandscapeFactory.getGroupedTechnicalSystems(AbapRfcLandscapeFactory.java:1024)

... 7 more

Caused by: com.sap.mw.jco.JCO$AbapException: (126) RETRIEVE_EXCEPTION: If there is an error during the Solution retrievial.

at com.sap.mw.jco.JCO$AbapException.<init>(JCO.java:1406)

at com.sap.mw.jco.JCO$Client.execute(JCO.java:3486)

at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:81)

... 8 more

at com.sap.sup.admin.setup.SetupUpgrader.execute(SetupUpgrader.java:178)

at com.sap.smd.SMDUpgradeManager.executeUpgrade(SMDUpgradeManager.java:227)

at com.sap.sup.admin.setup.ManagingServices.runUpgrader(ManagingServices.java:2544)

at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:541)

at com.sap.sup.admin.setup.SetupStep$StepRunner.run(SetupStep.java:729)

at java.lang.Thread.run(Thread.java:770)

Has someone an idea what the reason could be for this issue?

Thanks in advance for your help!

Kind regards,

Joern

Accepted Solutions (0)

Answers (3)

Answers (3)

andreu_mendoza2
Explorer
0 Kudos

Hi Joern,

I reckon that you should update yout CIM Model and CR Content as per the SAP Note 669669.

And also apply the SAP Note:

1659101 Programme zur Unterstützung im Umgang mit LMDB Namensräumen

I hope this helps.

All the best,

Andreu

former_member313130
Participant
0 Kudos

Hi,

I checked the thread and in parallel I determined that the job SAP_LMDB_LCACHE_LDB_0000000001 stops every time with a dump:

Category ABAP Programming Error

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_LMDB_OM_CIM_ERR

ABAP Program CL_LAPI_UTILITIES=============CP

Application Component SV-SMG-LDB

Date and Time 04.01.2012 15:42:05

-


-


Short text

An exception occurred that was not caught.

-


-


What happened?

The exception 'CX_LMDB_OM_CIM_ERR' was raised, but it was not caught anywhere

along

the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program

'CL_LAPI_UTILITIES=============CP' has to be

terminated.

-


Kind regards,

Joern

Former Member
0 Kudos

Hi,

Check this thread for a similar issue:

Cheers,

Diego.