SOLMAN 7.1 after upgrade - Can't migrate SMSY properly to LMDB

[Former Member]

Hello,

We performed an upgrade to our VAR Solution Manager ( 7.01 to 7.1 ).

In 7.01 we had all our clients created in SMSY, using the ExtendSID, by synchronizing our solution manager with our SAP Marketplace Portal SUser account ( using report REFRESH_ADMIN_DATA_FROM_SUPPORT ). None of our clients were added in the 7.01 SLD.

After the upgrade we tried to perform the SMSY migration in order to populate the newly created LMDB with the client information. The problem is that only a few were imported correctly. Most of the information existing in the SMSY ( product systems, logical component ) fails to migrate with the following errors:

• No active product version assigned in SMSY
• No relevant product instance found for product SAP ECC

How can we fix these issues?

-----------------------------------------------------------

Another problem that appeared:

We deleted the IBASE and recreated it (using the REFRESH_ADMIN_DATA_FROM_SUPPORT again), in order to fix some issues with our Service Desk functionalities, The problem is that the systems in SMSY got mixed up (the ExtendedSIDs changed for some customers changed and logical components / RFCs got associated with the wrong customers).

Is this normal?

[Vivek_Hegde]

Hi Pedro,

The activity you are trying to perform is called System-Oriented Migration. This is not a recommended approach however in your case we can take the exception. To perform this you must initially synchronize SLD and LMDB. Only after this you can synchronize SMSY to LMDB.

After you successfully sync SLD and LMDB, before migrating make sure that you have at least maintained the following data in SMSY.

◦Installation Number

◦Message Server

◦Database is assigned to the system

◦The server of the assigned database

◦The manufacturer of the assigned database

Regards,

Vivek

[VJain]

also check:

1752124 - LMDB Infrastructure Checks and Support Tools Enhancement

1755172 - Analyzing Issues with LMDB (self-help assistance)

Thanks

Vikram

[VJain]

Hi,

If the technical system information cannot be provided by SLD data suppliers or a product system description cannot be migrated, use the Product System Editor in LMDB to create it manually.

You can use a report to create system information based on license data downloaded from the support portal.
Prerequisites:
- The license data has been defined correctly and sufficiently in SAP Support Portal, for example, system ID, installation number, system number, and product version must be defined.
- The report to download the license data from SAP Support Portal hasbeen executed.

The download is executed by the AI_SC_REFRESH_READ_ONLY_DATA report, which usually is scheduled as background job(REFRESH_ADMIN_DATA_FROM_SUPPORT) once a day.

The job Job REFRESH_ADMIN_DATA_FROM_SUPPORT reads various categories of information from the SAP Support Portal and saves them locally in the Solution Manager.

Please read SAP note 1490774 (is also largely valid for Solution Manager 7.1).

ATTENTION: In order that the Job is able to download data for an installation, at least one system of an installation with correct system number has to exist in LMDB.

Please maintain all required technical and product systems in SMSY.
Delete all old  systems, hosts and databases.
Then you can migrate the product system data from SMSY to LMDB.

Errors:
1. No active product version assigned in SMSY.
Choose the product system in SMSY- Use the button "Change Product Assignmt".
Before try to "Synchronize" the system in Tab "System Data in SAP Support Portal".

2. No relevant product instance found
Choose the product system -> Tab "Product Instance Selection".
select the correct product instances -> Save the changes.

For Java instances maintain the last two columns (Technical System and System Type) also.

Thanks

Vikram