SOlman_setup issue at implement SAP Note Step

[Former Member]

Hi Friends,

While i am performing the solman_setup (system preparation) facing once issue at Implement SAP Note step.

In this step while i am performing  the post processing step (3rd step) giving the red signal The system only partially implemented the manual activities for note 1856234.

And i followed the note 1856234 as per the note i ran the report AI_CRM_ANALYZE_IBASE_SORTF and i got the error messages.

The Ibase component 000000000000003598 has deviceid: SID 00XXXXXXX

Sort string is needed!

Comp. with same device id:

Replace Sort string with (from LMDB):

The Ibase component 000000000000003272 has deviceid: SID 00XXXXXXX Etc.

Sort string is needed!

Comp. with same device id:

Replace Sort string with (from LMDB):

And as per the note

when i am executing IB_GEN i am getting below errors.

Object not found - will be created.

No changes made; Saving not allowed

Failed to save object %   1 (Object family 7001).

Kindly suggest on this.

Thank you,

Chowdary.

[Former Member · Accepted solution]

Hello,

Please check note 1741109 - ITSM 7.1 - Generation of IBase Components is not working

BR,

K.

[Former Member]

Hi,

Refer to this document:

[divyanshu_srivastava3]

Hi,

Refer this note and check if this helps:

2009638 - Solution Manager Central Note Post Process Fails

Regards,

Divyanshu

[Former Member]

Hi,

Thank you for your reply. I  implemented this not still issue persist.

in my system i have duplicate SID's for my Production and QA system in LMDB, it seems to be it causes the issue.

Like for PRD we have SID like ABC, ABC00001, ABC00002

for QA DEF and DEF00001.

Kindly suggest on this.

Thank you.

[Former Member]

Hi,

Thank you for your reply. I  Looked at this but it seems to be some issue as per the point in the document.

in my system i have duplicate SID's for my Production and QA system in LMDB, it seems to be it causes the issue.

Like for PRD we have SID like ABC, ABC00001, ABC00002

for QA DEF and DEF00001.

Kindly suggest How to resolve this.

Thank you.

[Former Member]

Please refer to SAP Notes 1694004 - Dealing with duplicate technical system names (SIDs) and 1747926 - Dealing with duplicate technical system names (old SLD)

[divyanshu_srivastava3]

Then really can be because of the association.

Perhaps, some additional cleaning + cleanup of duplicate extended ID will be helpful.

I believe notes posted by Sudheer will be helpful.