cancel
Showing results for 
Search instead for 
Did you mean: 

LMDB - initial synchronisation

Former Member
0 Kudos

hello,

I'm currently running solman_setup on a soman 7.1 sp4

I have an issue with sync between LMDB and SLD :

Critical error in content synchronisation setup: Namespace ID 0000000002 not found in persistence (domain Landscape Management Database)

when I execute, Program RLMDB_SHM_READ_TEST

Reading ChangelogId: 1.327.425.645.000.001.000 SHM build on UTC time: 20.120.124.172.046,3335520 in NamespaceID:

LDB:0000000001

I have a namespace ID of 000001.

But it seems that the synchrosisation is trying to setup namespace 00002.

Any hint?

Thanks in advance

Accepted Solutions (0)

Answers (2)

Answers (2)

guilherme_balbinot
Active Participant
0 Kudos

Hello,

If possible, remove all the configuration from the System Preparation, step 6.4, enter on edit mode, make sure you click on "Configure Object Server" and change the name to a new one (i.e. MYLMDB002).

Afterwards set the SLD sources again.

Best regards,

Guilherme

nicholas_chang
Active Contributor
0 Kudos

Hi,

Agree with above, deactivate and delete everything. Ensure you've configure object server name. if hostname is used for your SLD object server name, you can use something like "P_YourHostName"

Proceed to add synchronization and ensure below are filly correctly:

source URL: http://yourHostName.FQDN:5XX00/sld/cimom

source namespace = 10

target namespace = 20 (just need to ensure the priority is lower than source)

save and activate

Do try and let us know how it goes,

Cheers,

Nicholas Chang

Former Member
0 Kudos

Hello,

I already tried to change again object server name, no more success. I saw on forum that it can take some time. So I wait some hours before retrying. .

But this morning, I still have the same dump reported upper.

thanks

nicholas_chang
Active Contributor
0 Kudos

Hi,

Do you check the LMDB* log??

Try to implement note Note 1659101 - Programme zur Unterstützung im Umgang mit LMDB Namensräumen

You patch CR and CIM content before or after LMDB Sync?

If you patch after, you may need to delete and configure object server for LMDB again. In SETUP LMDB -> deactivate -> Delete -> and Configure Object Server again.

Once done, let the sync begin and try to monitor the progress in SM37.

Thanks,

Nicholas Chang

Former Member
0 Kudos

Hello,

Sap note has been already implemented with central sap note of solman_setup.

Unfortunatly, I patched CR/Cim content after the first sync attempt.

after patch, I had this dump.

I already deleted the sync, but I can't reactivate it as I have this error message. So current state is that there is no sync between LMDB and SLD..

regards

nicholas_chang
Active Contributor
0 Kudos

Hi,

Just to ensure have you delete everything - object server, SLD and try overall again?

Cheers,

Thanks,

Nicholas Chang

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

Prior to running solman_setup, did you follow the guidance of SAP Note 669669 Updating the SAP Component Repository in the SLD?

If you missed this Note, then you will have issues with syncronization during Solman_setup.You can perform the activity in the Note now, and then re-execute the failing step.

Regards,

Paul

Former Member
0 Kudos

Hello,

thanks for anwser.

Yes i already uploaded latest version of CR/cim content according to this note.

all is at the latest version..

report which is failing is duming

RLMDB_SYNC_TECHNICAL_SYSTEM

"""""""""""""""""""""""""""""""""""""

ABAP Programming Error

UNCAUGHT_EXCEPTION

CX_LMDB_OM_CIM_ERR

RSDBRUNT

BC-ABA-TO

25.01.2012 21:42:32

""""""""""""""""""""""""""""""""""""""""

The exception, which is assigned to class 'CX_LMDB_OM_CIM_ERR', was not caught

in

procedure "%_INIT_PBO_FIRST" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

Namespace ID 0000000002 not found in persistence (domain Landscape Management

Database)

""""""""""""""""""""""""""""""""""""""""""