SLD and LMDB

[former_member182675]

HI

i just finish to install solution manger 7.1 on windows server 64 bit oracle

SP 04

CR - the latest version

and i have some queations

how i update abap server in smsy

SLD> LMDB> SMSY

i need to create in smsy the system

i need to create in smsy product system?

or its create from the lmdb

after i assign the system in sld i need to do somthing in LMDB (or it create automatic)

i ask becase its dont work to me i have the system in sld but i dont see nothing in smsy or in lmdb

the jov work good

best regards

Naor Shalom

[former_member182675]

HI

Its work after implement the new version (6) of the note

many thanks

Naor Shalom

[Former Member]

Is your problem solved now?

[former_member182675]

HI

yes i download note 1633725 in teh system Preparation

the dump is :

ASSERTION_FAILED

AI_LMDB_R_SYNC_RUNNER

SV-SMG-LDB

In the running application program, the ASSERT statement recognized a

situation that should not have occurred.

The runtime error was triggered for one of these reasons:

- For the checkpoint group specified with the ASSERT statement, the

activation mode is set to "abort".

- Via a system variant, the activation mode is globally set to "abort"

for checkpoint groups in this system.

- The activation mode is set to "abort" on program level.

- The ASSERT statement is not assigned to any checkpoint group.

t 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.

or analysis

The following checkpoint group was used: "No checkpoint group specified"

If in the ASSERT statement the addition FIELDS was used, you can find

the content of the first 8 specified fields in the following overview:

" %_##TVREG_002 = `Cannot change read-only CIM element: CL_CIM_REFERENCE` "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"ASSERTION_FAILED" " "

"AI_LMDB_R_SYNC_RUNNER" or "AI_LMDB_R_SYNC_RUNNER"

"END-OF-SELECTION"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

theanks naor

[nicholas_chang]

Hi Noar,

Did you apply Note 1633725 successfully? And is the Local SLD setup completed?

Try to delete your LMDB. Run the Local SLD setup again, and configure your Object Server for LMDB once more, with prefix P_****

After that, save and activate.

Do let us know how it goes.

Thanks,

Nicholas Chang

[former_member182675]

HI

and thanks

i configure my local sld in system Preparation again

and i set up the lmdb

but the sync is always 0%

i go to the job and the job (SAP_LMDB_LDB_0000000001) canceled

the error is:

Full Sync. of SAP_SystemLandscapeDirectory: 1 source instances, 1 target instances

Full Sync. of SAP_SystemLandscapeDirectory finished: 0 creations, 0 modifications, runtime 0 s

Full Sync. of SAP_BCCentralServiceInstance: 2 source instances, 2 target instances

Full Sync. of SAP_BCCentralServiceInstance finished: 0 creations, 0 modifications, runtime 0 s

Full Sync. of SAP_DatabaseInstance: 4 source instances, 4 target instances

Full Sync. of SAP_DatabaseInstance finished: 0 creations, 1 modifications, runtime 0 s

Full Sync. of SAP_DatabaseSystem: 4 source instances, 4 target instances

Internal session terminated with a runtime error (see ST22)

Job cancelled

i try to run the job alone and canceled

what i need to do?

the lmdb in system Preparation is yellow

Thamks Naor

[nicholas_chang]

Hi Noar,

please check the abap dump in ST22.

have you apply the central note for SP04 and all its child note?

Thanks,

Nicholas Chang

[prakhar_saxena]

In addition to above

Read these links for LMDB

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=250514114

https://service.sap.com/~sapidb/011000358700000074392009E/SP18_SolMan_Setup_Guide_V2.pdf

also SMP

u2022Setup Guide Landscape Management Database - Go to Solution Manager Overview > Media Library > Technical Information. Look for:

◦Setup Guide Landscape Management Database (LMDB) SP2+3

◦Setup Guide Landscape Management Database (LMDB) SP1

Hope above helps

Regards

Prakhar

[nicholas_chang]

Hi Naor

how i update abap server in smsy

>> you can update via RZ70 and the info will fetch to SLD, and the entry will sync from SLD -> LMDB -> SMSY if sync is established between the SLD & LMDB during solman_setup -> system preparation.

i need to create in smsy product system? or its create from the lmdb after i assign the system in sld i need to do somthing in LMDB (or it create automatic)

>> once you see your entry in SMSY, you can change the product version in SMSY, and if you want to change the product system, you can't change in SMSY, it'll bring you to LMDB techinical system editor.

Also, please download the guide as per advise given above.

Cheers,

Nicholas Chang

[former_member264034]

Hi,

The synchronization from SLD to LMDB needs to done via Solman_Setup ->

System Preparation.

Also refer to the note [1632481 |http://service.sap.com/sap/support/notes/1632481]which explains about setting the object

server name for the source(SLD) and the Target(LMDB). To resolve the

issue please choose a different Object server name. A recommendation

would be LMDB_<SID> where SID is the system id of the solution manager

system.

The synchronization between SLD and LMDB would take several hours.

You can get further details at the following link:

- http://service.sap.com/~sapidb/011000358700000146522011E

Regards,

Aidan