Error in LMDB

Hi experts,
I have installed Solution Manager 7.1 Stack 10 succesfully but when I access to the LMBD it shows me the next error message:
"Error in method call References: No such instance: sld/active:SAP_SoftwareComponent.ElementTypeID="67837800100200024170",Name="HCO_DESIGN_STUD",Vendor="sap.com", Version="1.3""
Also, the background job SAP_LMDB_LDB_0000000001 is cancelled with the same error.
What can I do to run this job fine?
Thanks in advance,

Hi,
You could try removing active namespace in SLD and reloading the cim model and CR content.
To delete the active namespace go to the Administration section of SLD and there in Namespaces link you can delete the namespace.
After reloading the SLD content resync the SLD with the LMDB.
Hope that solves the problem..
Kind regards,
Iñaki.

Similar Messages

Synchronization error between LMDB and SMSY

Hello Experts
I have a sync error between LMDB and SMSY entries. I want your help to make this synchronization to Solution Manager 7.1 SP07.
Thank you very much for your help
Juan Carlos Salazar R

Solman Setup - Configuration Lost
To try to solve the synchronization error
I have been running a Report for get some information and as a consequence all the information into the solman configuration was lost. I mean everything, all the clock (the date of modification) are in zero, and all the status are grey.
Someone know How to bring this information back; without performing a backup or to perform a setup again.
The report is the RLMDB_SYNC_TECHNICAL_SYSTEM

Error in lmdb sync

Dear all
we are on solman 7.1 sp4 we are trying to add product system it shows system not add in LMDB the lmdb job cancelled SAP_LMDB_LDB_0000000001 can cancelled continuously it throws error
it shows
HTTP destination LMDB_SyncDest1 is unreachable (http://IDxxx.ra.com:8001/sld/cimom (sld/active))
for this we have check rfc LMDB_SyncDest1 changed user and made it successful but still there is error
give me some solution
Regards

Dear
the authorazation for RFC LMDB_SyncDest1 passing the authorization the test
we are using for LMDB_SyncDest1? and our user we are using the user SLDDSUSER for the RFC.
it passes the connection test
now it throws following error
Thanks in advance

Sol Man 7.1 - SLD / LMDB Synchronisation Error

Hi experts,
I am trying to perfom a full synchronisation between LMDB of Sol Man 7.1 and our Central SLD (CIM 1.6.16, SAP_CR 7.3)
Somewhere around 20% - 30% the full synch gets an error and restarts automatically at 0%.
Error message in application log is:
Error in method call SAPExt_EnumerateInstancesNoSubclasses: Failed to leave transaction:
Full sync failed for class SAP_SoftwareFeatureSoftwareComponent
Full sync needs to be repeated after correcting this error
Error message #s:
BL001
LMDB_CS_ERROR023
LMDB_CS_ERROR024
Did raise a call already but no useful response until now.
Anyone else had problems like this?
Thanks

Hi,
[Note 1480419 - Release Restrictions for SAP Solution Manager 7.1|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1480419], this note saying the restriction on LMDB and SLD sync, Moreover they are suggesting to upgrade SP01 to fix the LMDB issue..
Have you tried out?
Thanks,
Jansi

SLD to LMDB synchronization error- cim model mismatch

Hello All,
In system preparation, we have configured the SLD and in the setup LMDB step we have added this SLD for synchronization to LMDB. Once we activate the synchronization (full sync) we first get a message "LMDB is on cim model 1.6.31 and SLD is on 1.6.37.Please confirm if you want to update LMDB to cim model 1.6.37." I clicked YES for this. Then it starts a job SAP_LMDB_LDB_0000000001 in the ABAP stack. However this job is getting cancelled with below message:
An exception of class CX_LMDB_CIM_ERR occurred
Classes for sync do not match: source model version 1.6.37, target 1.6.31
Can anyone advice what can be done to resolve this situation? Just FYI, This is not a new implementation there was another SLD that was connected to the LMDB earlier, however that stopped working due to a version mismatch. So now I am trying to sync the LMDB to a new SLD.
Thanks,
Anilraj Menon

Hi Anilraj,
When switching Your CRsource for the SLD/LMDB sync on Solution Manager, SOLMAN_SETUP You have to be very carefully as this is not a standard operation as such. You need to make sure that You don't have pending changes in the LMDB sync from the old SLD.
Furthermore, You should use the template in Solman_Setup, system preparation, step 5.2 --> click on "Advanced", and in actions, You should set the CRsource to the new SLD.
But please remark, this could lead to some inconsistence in Your LMDB thus the need to have no pending changes in the LMDB sync (You can see if there are any in the very same GUI where You set the CRsource - look in the "Status Details" pane: "Number of Source Changes Pending". This figure should be "0".
Also have a look on the blog from Wolf Hengevoss. I guess this adress Your exact problem:
SLD and LMDB Topology: Replacing the Source SLD for the LMDB
Regards,
Kurt

Error while scheduling data collector: Error adding routine 'SAPTOOLS.DBH_FWK_CLEANUP' to task scheduler

Error Detail
Exception CX_DBA_ADBC in program RAGS_SISE_ACTIVITY_JOB line 0
Kernel Error ID:
WP ID: 23
WP PID: 28977
SYSID: CR5
SY-SUBRC: 0
SQL statement:
Database: CR5
caused by
Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
Kernel Error ID:
DB Error: Yes
SQL Code: 444-
SQL Message: SQL0444N Routine "*TASK_ADD" (specific name "SQL140704080729140") is implemented with code in library or path "...ib/function/SYSPROC.ADMIN_TASK_ADD", function "*" which cannot be accessed. Reason code: "4". SQLSTATE=42724 row=1
DB Object Exists: No
Duplicated Key: No
Internal Error: 1
Invalid Cursor: No
Unknown Connection: No
Connection Closed: No
System Detail:
Solman 7.1
ST    710    0010    SAPKITL710    SAP Solution Manager Tool
SAP_BASIS    702    0013    SAPKB70213    SAP Basis Component
Managed system:
SAP CRM ABAP 7.0
SAP_BASIS    701    0005    SAPKB70105    SAP Basis Component
SAP_ABA    701    0005    SAPKA70105    Cross-Application Component
PI_BASIS    701    0005    SAPK-70105INPIBASIS    Basis Plug-In
ST-PI    2008_1_700    0008    SAPKITLRD8    SAP Solution Tools Plug-In
CRMLOY    700    0005    SAPK-70005INCRMLOY    CRM Loyalty Management 700
SAP_BS_FND    701    0005    SAPK-70105INSAPBSFND    SAP Business Suite Foundation
SAP_BW    701    0005    SAPKW70105    SAP Business Warehouse
LCAPPS    2005_700    0007    SAPKIBHD07    LC Applications (LCAPPS) 2005_700
Database DB2
db2level
DB21085I Instance "db2cr5" uses "64" bits and DB2 code release "SQL09016" with
level identifier "01070107".
Informational tokens are "DB2 v9.1.0.6", "s081007", "U817474", and Fix Pack
"6".
Activity detail:
We are performing managed system configuration for CRM into Solman by using solman_setup transaction. While performing the Database Extractor Setup in step 8 we have observed above error.
Action take at our end:
1. Clean the LMDB and restart the configuration. - no luck
2. Upgrade the hostagent at CRM - No luck
3. Update the SLD for CRM entry - no luck
4. implemented SAP notes:
875986    Note Assistant: Important notes for SAP_BASIS up to 702
1246964    Note Assistant: Master language of notes incorrect
1262653    SPAU: New object is deleted after note is reset
1309424    DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11
1335017    DB6:"Remove Redundant Restrictions" can return wrong results
1349277    Note Assistant: Method cannot be implemented
1365677    Note Assistant: Runtime error MOVE_CAST_ERROR during implmtn
1372652    DB6: Short dump when viewing diaglog due to NULL bytes
1373957    DB6: CX_SY_CONVERSION_OVERFLOW in new EXPLAIN
1376543    DB6: OPTIONS parameters for backup jobs in DB13
1378499    DB6: CLI error CLI0112E with "REORGCK_ALL" job
1379260    DB6: Add BW query name as comment to SQL statements
1379346    DB6: Scheduling of data collectors fails
1381179    DB6: Incorrect values for 'number of objects in tablespace'
1382634    DB6: Unable to create view 'SAPTOOLS.DBH_TABCLASS'
1382996    DB6: Update of DPW Back-End in Monitored DBs does not work
1384238    DB6: Defect scheduler on DB2 9.1 FP7/FP8 for LUW on Linux
1387022    DBA Cockpit: Month displayed incorrectly in DB13C
1387297    DB6: SQL-Fehler 901 during RUNSTATS and REORGCHK
1397709    Ignore Dynpro element fields AGLT and ADEZ in SNOTE/CWB
1398258    DB6: Job REORGCK_ALL places load on package cache
1400843    DB6: Incorrect display of key fields in EXPLAIN
1412719    SNOTE: error when implementing enhancement implementations
1413008    DB6: SQL0206N in function module DB6_PM_LOCKSNAP
1414624    DB6: Performance views if database monitors are deactivated
1414626    DB6: Incorrect display of file system sizes of containers
1415680    Note Assistant: Incorrect status in subsequent systems
1421157    DB6: SQL error 204 when accessing table DBSTATC
1425487    SE24: Error regarding READ-ONLY for complex attributes
1426092    DB6: Incorrect DROPPED TABLE clause for tablespaces
1426480    DB2: Incorrect display of registry values for DPF systems
1427030    DB6: Container specifications for tablespaces not changeable
1429082    DB6: No REORG after deactivating compression
1429687    DB6: SQL cache performance
1438168    DB6: REORGCHK recommendations for indexes are missing
1444373    DB6: Loading the package cache with monitor functions
1449482    DB6: Error message 'Command LIST_DB2DUMP failed'
1451958    DBA Cockpit: Incorrect start time for jobs
1452197    DB6: SQL error 100 in job REORGCK_ALL
1452502    DBA Cockpit: Jobs are missing in central planning calendar
1455897    DB6: Display of data classes is not updated
1456379    DB6: No display of indexes in data classes
1460895    DB6: SQL0104N during creation of WLM threshold
1462415    DB6: SQL -444 error messages in system log
1462855    DB6: Incorrect database name in HA environment
1464800    DB6: SQL Commands executes automatically on system change
1464858    DB6: COMPUTE_BCD_OVERFLOW during EXPLAIN Test Execute
1469515    DB6: Runtime error GETWA_NOT_ASSIGNED_RANGE in SAPLSDB6MON
1485313    DBA Cockpit: Incomplete system entries after SLD import
1486972    DB6: Parameters for DB/DBM configuration cannot be changed
1489968    DBA: DBA Cockpit WebDynpro does not care about HTTPURLLOC
1496515    DB6: SQL error 1428N when starting the DBA Cockpit
1501130    DB6: SQL error 802 in DB6_DIAG_COUNT_TABLE_ENTRIES
1508074    RZ20: 'Connection' attribute does not report alerts
1509121    DBA Cockpit: Endless loop occurs when starting DBA Cockpit
1511803    DB6: DB_TABLE_DATA_READ does not return data
1521525    DB6: Table display is not sorted
1522617    DB6: Availability of BW-specific functions in DBA Cockpit
1532114    DB6: Too many locks when collecting table history
1536787    DBA Cockpit: WebDynpro Explain - LOADDATA requires a model
1542311    DB6: Runtime error BCD_OVERFLOW in auto maintenance display
1546866    DB6: Runstats_DBSTATC interprets runtime param. incorrectly
1551729    DB6: Incorrect number of key fields in EXPLAIN
1552812    DB6: Use of db2sap functions
1559699    DB6: Missing data in SQL cache display
1559967    DB6: SQL error 206 when collecting the table history
1563327    DB6: SQL error SQL0551N when accessing SYSSTAT.TABLES
1568800    DB6: Error when deleting alert messages
1569592    DB6: SQL error SQL0433N in EXPLAIN
1569669    DB6: Incomplete history for performance data
1571365    DB6: SQL error SQL0443N in alert monitoring of DPF system
1576094    DB6: Database error SQL1751N in partitioning wizard
1597281    DB6: Incorrect compression displays for tables
1599764    DB6: SQL error 1428 when calling transaction SM50
1602403    DB6: No VOLATILE attribute after RUNSTATS or REORG job
1613270    DB6: Runtime error DYNPRO_FIELD_CONVERSION in DBA cockpit
1615698    DBA Cockpit: Incorrect date selection in DB13C
1619084    DBA Cockpit: Runtime err MESSAGE_TYPE_X when alert displayed
1619636    DBA Cockpit: Daily scheduling is not deleted
1624436    DBA Cockpit: Errors when accessing SHM area CL_DBA_SHM_AREA
1639631    DBA Cockpit: Failed schedulings in DB13
1720495    Invalid deimplementation of obsolete notes by Snote tool
Kindly suggest the correct solution to fix the issue.

Dear Deepak
Thanks for quick response.
Note 1462415 - DB6: SQL -444 error messages in system log ( SAP_BW 701 SP7 suggested)
This is already implemented and updated in my 1st message.
Note 978319 - DB6: Incorrectly cataloged table functions
This note can not be implemented due to version issue.
Kindly suggest some more hints on top of what I already did.
Regards
Bipin

Upgrade-phase "SYIDUP_EXTRACT/PROFREAD" error

We are upgrading SCC system.
While generating stack.xml file from solman 7.1 sp 10, we got error in the verification execution as Cannot recognize installed product instance in lmdb.
We referred the note - 1816146 - Correction of installed software information (CISI.
1. We run the report RLMDB_DOWNLOAD_INST_SOFT_INFO and created .xml file.
2. downloaded SUM sp10
While running SUM tools we got the error the phase "SYIDUP_EXTRACT/PROFREAD" as below.
Attaching files as -
1. All log file from directory 'S:\usr\sap\SCC\SUM\abap\log'
2. All profiles
We analyzed the issue. Error is coming the file PROFREAD.LOG as
1 ETQ201 Entering upgrade-phase "SYIDUP_EXTRACT/PROFREAD" ("20140409192228")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '', GwService = 'sapgw' Client = '000'
4 ETQ399 Environment variables:
4 ETQ399 auth_shadow_upgrade=<null>
1 ETQ200 Executing actual phase 'SYIDUP_EXTRACT/PROFREAD'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'DDICPWD_ONLY'
4 ETQ399 Starting dialog 'Passwords' at 20140409192229.
1 ETQ359 RFC Login to: System="SCC", AsHost="dl5802" Nr="", GwHost="dl5802", GwService="sapgw"
2EETQ231 RFC Login failed
4EETQ399 Dialogue validator 'DDICValidator' failed with 'DDIC password does not work:
RFC login to system SCC ashost dl5802 nr gwhost dl5802 gwservice sapgw failed with code 1 key RFC_COMMUNICATION_FAILURE:
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR      partner 'dl5802:3300' not reached
TIME        Wed Apr 09 19:22:37 2014
RELEASE    721
COMPONENT NI (network interface)
VERSION    40
RC          -10
MODULE      nixxi.cpp
LINE        3285
DETAIL      NiPConnect2: 172.17.206.26:3300
SYSTEM CALL connect
ERRNO      10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER    1
4 ETQ399 Repeat dialog since input validation failed.
Please check the same and revert backup.
Thanks,
Kundan Gandhi
9930446697

Hi all,
Please check 4 ETQ399 System-nr = '', GwService = 'sapgw' Client = '000' in the log mentioned.
Why it is not picking up any value for System-nr = (It should get system no. 40 - as my system no is 40)
Please revert, if any body faced this type of issue.
Thanks,
Kundan Gandhi

MOPZ error while generating stack file for EREC upgrade

I need to upgrade E-Recruitment 604 to 606.
Currently we are on Netweaver 7.01 While adding this system in SOLMAN 7.1 SPS 05 in order to generate
stack.xml file i manually selected this product system in product system
editor and we had selected below combinations
1)EHP4 for SAP ERP 6.0/NW 7.01(marked as installed) + SAP ERP
-> started MOPZ with same and selected target as SAP ERP 6 EHP 7 but
while doing so got error as Invalid queue because EA_APPL is not selected
but actually EA_APPL is not in components for EREC system
2)EHP4 for SAP ERP 6 with ABAP technology and E RECRUITING + EHP1 for
NW 7.0
->started MOPZ with target as SAP netweaver 7.4 but while doing so
getting error as "EHP Component ERECRUIT 604 without suitable Technical Usage!"
and Mark relevant instance to include the software component ERECRUIT
604 in SMSY/LMDB but Product system editor is perfect and verification tool is also green.
Please help
Warm Regards,
Sumit

Problem has been resolved.
SAP E-recruiting should be selected in SAP ERP 6.0 as a pre-requisite.
Warm Regards,
Sumit

Error in Managed System Configuration - Sol Man 7.1

Dear Experts,
Whle configuring using solman_setup, I am getting below mentioned error in Managed System Configuaration:
Cannot retrieve CIM Instances from CIM Class 'SAP_DiagnosticsRelevantSoftwareFeature'!
Cannot retrieve all CIM Instances from CIM class name 'SAP_TechnicalScenario' via LMDB Mass Access API!
Cannot retrieve all CIM Instances from CIM class name 'SAP_DatabaseSystem' via LMDB Mass Access API!
Any suggestions??
Regards
Vivek

Hi Paul ,
Thanks for the note that you provided.
I am reconfiguring the LMDB and conteny Sync... The refresh will take 15-16 hours.. I am just waiting for the
sync to be finished. Let's see what is in the store for me
Keeping my fingers crossed untill then.
Regards
Vivek

RABAX_STATE error in SOLMAN_SETUP step 6.6

Hi all,
I'm doing the Solman_setup, step "System Preparation" for a new Solution Manager 7.1 sp 14.
As I try to get into the task 6.6 "Connect Diagnostics" the system generates a short dump :
Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_UNKNOWN
ABAP Program           CL_WDR_MESSAGE_MANAGER========CP
Application Component BC-WD-ABA-RUN
Date and Time          20.06.2014 11:26:31
|Short text                                                                                        |
|    Message type "e" is unknown.                                                                  |
|What happened?                                                                                    |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "CL_WDR_MESSAGE_MANAGER========CP" had to be                         |
|     terminated because it has                                                                    |
|    come across a statement that unfortunately cannot be executed.                                |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    Only message types A, E, I, W, S, and X are allowed.                                          |
|    There is probably an error in the program                                                     |
|    "CL_WDR_MESSAGE_MANAGER========CP".
All the previous tasks were performed successfully.
It seems to be a program error, but I can't find any Oss Note for it.
Any advise ?
regards

Hi,
Please check the below link
http://www.saptechies.org/system-preparation-short-dump-step-66-connect-diagnostics/
Resyncronize the Solution Manager system with the SLD in the LMDB.
Execute the steps below for the Solution Manager ABAP and JAVA:
Go to the Managed System Configuration
Select the Solution Manager system
Select System Operations -> Maintain System
A new screen will open, select the option Advanced -> Resynchronize the System from SLD, as seen in the example below
Rg,
Karthik

Error: The logical component X is still being used

Hi,
In Transaction SMSY, i want to delete a Logical Component. So, pre-condition is to check whether it is mapped to any Projects/Solutions. By right-clicking - Where used list , i have seen that it is mapped to a Project. So, in transaction SOLAR_PROJECT_ADMIN under tab System Landscape, i tried to delete the Logical Component but receiving the error message - The logical component X is still being used.
Please help.
Many Thanks,
Mohan.

Hello Mohan,
You can also solve this by using the "Replace Logical Component" button in the system landscape within SOLAR_PROJECT_ADMIN.
Thus you can replace all the occurances of the Z_ logical component by e.g. an existing standard SAP logical component.
Afterwards you will be able to delete your Z_ logical component in SMSY (or in LMDB from 7.1 SP9 on).
Best regards,
Peter

SLD to LMDB sync is not working

Hi ,
i hvae upgraded my ERP ECC6.0 EHP6 SYSTEM to EHP7 after upgrade when i checked in SOLUTION MANAGER (USING VERSION 7.1 SP12) LMDB ,,prodcut version is showing the previous release(EHP 6) .i deleted the system entry in LMDB under product systems and tried to re-sync the data from SLD using the report RLMDB_SYNC_TECHNICAL_SYSTEM but no use ..
could you please some one help me how to sync it .and what is the procedure to sync data from SLD
vijayapratap

Hi Vijayapratap,
Please check the following -
In EHP7 system, transaction SLDAPICUST & RZ70 are pointing to correct SLD (hostname & port).
Check entries in host file for all related system (each host file should have an entry for itself as well as the system it communicates with).
Make sure the periodic job is scheduled via RZ70
If the above is working fine, data will be automatically collected & pushed to the SLD
In SLD, login to check if the technical system details are getting updated, with successful completion of RZ70 job.
In LMDB, of the technical system already exists & is not upward compatible by the data available in SLD, LMDB re-creates another technical system with name SID00001, SID00002, and so on.
So it would be better to clean-up technical & product system from the LMDB related to EHP7 system before pusing the data via RZ70 system.
Also, please note that replication of SLD data to LMDB for creating a Technical system sometimes takes time.
If you are not patient, then you can manually create a Technical system of type AS ABAP for the SAPSID of EHP7 system. Make sure that correct DB host already exists in LMDB with correct IP address & host name (FQDN if specfied).
Then you need to set-up the RFC destinations from LMDB Technical System to EHP7 system.
Once these RFC(s) are successfully generated & working, assign a product system to the technical system.
To get the exact details on the installed components in EHP7 system, execute the Verification check in the Product system, and adjustments to have a green rating on the same.
Verification check uses the RFC destinations generated earlier to verify & validate the components available in EHP7 system.
Please let me know if you receive an error while performing the above steps.
Best Regards,
Tanmeya

Error while configuring system preparation in solman step 5.6(configure SAPconnect)

Hello,
We have recently upgrade solman from SP4 to SP 11. I am doing reconfiguration of the Solman. Stuck in one step of system preparation ->Step 5 Configure Connectivity -> 5.6 Configure SAPconnect.
The error which i am facing is "Email address could not be updated because of the CUA" after saving the entries. I tried disconnecting the system from parent system and run the setup but still getting the same error.
Any help in this regards will be highly appreciated. Let me know if more information is required.

Hi Ravi,
I presume
you refer to user-id SOLMAN_BTC (default user-id) used in step 5.6 of System Preparation"
an email address exists for above user-id
After system/client was removed from CUA, did you re-sync system via RZ70 to SLD and then to LMDB / SMSY?
Please re-sync and restart "System Preparation"; hopefully that should resolve your issue.
Best regards,
Shaji

Several errors during system preparation / basic configuration

Hello,
during the basic configuration I get stuck in the process step configure automatically -> setup bw.
In the slg1 I can see several errors where I don't know if they are related to my bw problem or other probleme. Maybe someone can give me a hint how to solve the issue.
@5C\QError@     2011/11/10 16:58:07 : DIAGTPL/CONFIG/HANDLER=CL_DIAGLS_ABAP_INST_TECH_SY Item does not exist
@5C\QError@     Product system DUM has no active standalone product version     @35\QLong text exists@
@5C\QError@     No detected product instances available for technical system C21     @35\QLong text exists@
in the Solman_setup I have the problem that
ESR: Extractor setup is not sucessful!
Cube 0SM_BPMRH is not active and will now be activated automatically
System status failed for system
Could someone please help me to solve some of the problems?
Thanks a lot, Vanessa

Hello Vanessa,
I wouldn't recommend looking at SLG1 at all times and try to find solutions for it, since Solution Manager deals with a huge landscape and in most cases some warning is thrown in the logs for any reason.
For example, the "CL_DIAGLS_ABAP_INST_TECH_SY Item does not exist" and "no active standalone product version @35\QLong text exists@" can be due to systems coming from SLD to the LMDB with no correct definition. If SLD is not passing this information, it is 99% because the system is not well defined there. Hence it is just a warning.
Now if you see something in SLG1 and indeed you have issues in this diagnostics system, it must be investigated.
For your BI problem:
Please execute the steps as described in section "3.2.1 Activation of
Info Cube from BI Content" in the Setup BPA Guide.
1430754 Business Process Analytics: Setup guide
(https://websmp101.sap-ag.de/~sapdownload/011000358700001210492010E/Setu
p_Guide_BP_Analytics.pdf)
Furthermore, I strongly recommend that, for Solution Manager 7.1, you make sure you have the latest SP in ABAP and JAVA. Now we are at ST400 SP03 and LM-SERVICE SP03 patch level 1.
You must not forward to the next steps if you have a step yellow, red or with Update checked.
Best regards,
Guilherme

MAnaged system configuration error in solution manager

Hi,
While doing managed system configuration getting the error, below versions are using.
MDM 7.1 SP10 Import server and Solution manager 7.1 SP10.
Can anyone help me?.
Regards
Chandra

Two cases you have
1) Satellite system
Re-install The DIA agent and give correct (port numbers )SLD details
Once you re-install the DIA agent, run Rz70 from satellite system
data will pull from satellite system to central SLD.
2)Run SLD check from Solman system , check its successful or not
Go to LMDB and check satellite system
After re-Synchronize technical system from SLD
Thanks ,
Rahul yedapally

Error in LMDB

Similar Messages

Maybe you are looking for