Synchronization between SLD/LMDB to table DB6NAVSYST

[jmgr]

Hello, Experts.

We have an issues regarding with our manage system configuration, one of our external system does not have instance db in the step 4 configuration of msc (DB parameters). Upon checking, there are no data in the entries registered in table DB6NAVSYST. We have already resynchronize the lmdb from sld, unfortunately entries still no data or entries. Please advise on how we can sync the entries of the table DB6NAVSYST to fetch the data in lmdb/sld.

Thank you in advance

[jan_j_novak · Accepted solution]

Hi Cire,

could you, please, specify, what kind of system on what DB are you configuring?

Please check LMDB, if your DB instance exists (LMDB > Technical systems > Type Database system or SAP HANA Database). When missing DB instance in Diagnostic Agent Assignment, it points towards the DB not being assigned to your system in LMDB (check LMDB > Technical systems > Type: Aplication server ABAP/JAVA > Enter your SID > Display > System Database - here should be info about your DB).

Check, if you have info about your DB in LMDB as noted above. check, if you have info about DB with your system in SLD. Check if your DB is correctly registered to SLD in case of HANA DB.

Please, let us know your progress and some more info.

Thanks!

Jan

[jmgr · Accepted solution]

Hello, Jan.

We're managing HANA DB 2.0 System Replication and our solman is at 7.2 SP05. Before, we have changed the extended system id of one our system from sid00004 to <sid> . The old ext.sysid is no longer available in LMDB, instead we are viewing this as <SID>. There are also data in SLD. The only problem is that the data in sld/lmdb does not show in the table DB6NAVSYST. Somehow this data does not get populated. Kindly see screenshot for your reference.

[jan_j_novak · Accepted solution]

Hi Cire,

I would probably delete all entries of this erroneous system in LMDB, try to create new entry in LMDB with correct Type, SID, hostname and then resync the system from SLD (technical system > enter type/SID > Edit > Advanced > Resynchronize).

Let me know, if you were able to do that.

Thanks!

Jan

[jmgr · Accepted solution]

Hi, Jan.

Do you mean that we need to start again from scratch and remove them via lmdb? if so, what about re triggering again the registration of the sld of hana db via hdblcm? Is there anyway that we can fetch the information from the lmdb/sld into that table? It seems that this table is connected to DBACOCKPIT, we have created the entry in dbacockpit, but it still not generating automatically from sld.

[jan_j_novak · Accepted solution]

Hi Cire,

Entry in DBA cockpit (as well as entry in DBCO) is usually done during managed system configuration in step 5.

You can try re-registration via hdblcm, but it seems that there is issue with SLD-LMDB synchronization of your system. Have you tried re-synchronizing it from existing Hana DB entry in LMDB (technical system > Type: SAP HANA Database + SID > Edit > Advanced > Resynchronize)? Are you getting any error in that step?

Jan

[jmgr · Accepted solution]

Hi, Jan.

I have already tried to resync it via LMDB, no errors were encountered during the synchronization. Is it okay if we remove the entries in DBACOCKPIT and clean the entrie in sld and lmdb then push the data again via hdblcm to sld?

[jan_j_novak · Accepted solution]

Hi Cire,

If the system is not yet configured with some monitoring etc., I would definitely try to delete it from LMDB & SLD, then re-register it via hdblcm, check, if the system is correctly in SLD, sync it with LMDB (job SAP_LMDB_LDB* or wait for a few minutes) and check LMDB, if you can find system correctly.

When deleting it from LMDB, try to search & delete all instances of the SID in LMDB with Overview > Search.

Also try running report AI_LMDB_EXTSID_CONSISTENCY for checking and removing inconsistencies.

I hope that some of it at least partially helps!

Jan

[jmgr · Accepted solution]

Hello, Jan.

Thank you very much for your help. Unfortunately, there is already monitoring but I think it is still not working correctly. Would you know which one should I check for the report AI_LMDB_EXTSID_CONSISTENCY? Is it also safe to delete all the entries in DBACOCKPIT for this specific instance?

[jan_j_novak · Accepted solution]

Hi Cire,

While running the report AI_LMDB_EXTSID_CONSISTENCY, check Display Inconsistencies and Display Orphans. This should show you the issues in LMDB. Check, if you can see SID of your problematic system there. Then select Delete Inconsistencies and Delete Orphans.

This report helps also if you have issues while renaming the systems in LMDB etc. It should delete only entries, which are erroneous.

If you have not finished Managed system configuration for the system, I guess it is OK to delete DBACOCKPIT entries as well as DBCO entries. These will be created again in step 5 of Managed System Configuration.

My approach would be following:

1. Delete the system from LMDB
2. Run AI_LMDB_EXTSID_CONSISTENCY report
3. Re-register the system via hdblcm
4. Check the system in SLD
5. Re-execute job SAP_LMDB_LDB* and check its log, if there are actual changes being transfered from SLD to LMDB
6. Check LMDB if the system is correctly entered

Of course, you have to think, if it is OK for your business, but from my perspective: If you have system incorrectly in LMDB, you cannot finish Managed system configuration correctly, which is base for any kind of monitoring. So "if the foundation (LMDB, MSC) is bad, the roof (SysMon) will probably fall down anyway".

Jan

[jmgr · Accepted solution]

Hello, Jan.

Unfortunately, we have already completed the msc for this instance, it is just that the issue happened when we have a fail-over testing last week and it seems that the issue is probably due to the renaming of the external system ID in LMDB. All the information fetched by the msc is already broken. I would probably follow your approach, is it also okay if we also clean the entries in sld for this instance and re-register them via HDBLCM?

For dbco and dbacockpit i still don't know how to correct the information since you have mentioned that it is okay to delete them if we have already completed the MSC.

[jan_j_novak · Accepted solution]

Hi Cire,

In this case that could be caused by inconsistencies in Key element fingerprints in LMDB entry and SLD entry.

You may possibly be able to correct that without deleting anything (in case it is this case).

I will try to describe, how to check it, hopefully it would be at least a little bit comprehensible:

1. Go to SLD > Administration > Maintenance > CIM Instances
2. Select Class HANA DB server, filter your SID and select the correct line
3. Select Associations and search Associated Role "Collection", Associated Class "Supplied Elements" and Associated Instance "HanaDatabase <SID> on <hostname>", then click on the link in Associated Instance
4. Copy KeyElementFingerprint, that you can find there
5. Go To LMDB > Technical Systems > Type: SAP HANA Database & SID > Display
6. Click on Details > Associated instances tab > Search the same Associated Role/Class/Instance as in SLD and click on the Instance link
7. In the top part of instance details you will see the Reference string with property sap_suppliedelements.keyelementfingerprint=
8. Check, if this is the same as you have in SLD.
9. If not, you should click Actions > Rename Instance > Change keyelementfingerpront property > Click Calculate Reference String > Click Execute Renaming and Close Popup.
10. Refresh LMDB page and on affected system LMDB page try Advanced > Resynchronize.

Jan

[jmgr · Accepted solution]

Hello, Jan.

I have followed your approach I just added some step which was to clean the entries in SLD and reregister them again via hdblcm. Currently I am re-configuring the system in msc. I've also delete the entries in dbacockpit and dbco, you are right they have been created automatically when you completed the step 5 in msc. Currently I have encountered some problem (The definition of Technical System '<SID>~HANADB' is not correct: '<SID>~HANADB': Technical System must be installed on at least one Host.) when configuring one of the external system ID in step 2. It seems that there are missing entries in SLD (association tab), which I think I have to redo again the registration from hdblcm to sld.

[jan_j_novak · Accepted solution]

Hello Cire,

Good to hear, you are through with step 5.

The error "Technical System must be installed on at least one Host" sounds to me as outside discovery issue with external's system SMDA. Please, check, if your SLD and Solman with ports are available from the system's OS. Probably by telneting the ports on solman and SLD. The ports should be same as used with installation and/or during registration of SMDA to solman and SLD.