Skip to Content

SLD: SAP CR not updated in target SLD when using export/import

Hi Guys

I have read in the SLD planning guide that an export/import with export line will import CR (Component Repository data) as well as LD (landscape data) and NR (Name Reservation).

However when I try to do this by:

1) Export ALL (Full) from a source SLD (with SAP CR content version = "SAP_CR 5.0")

2) Import this export file to a starget SLD (with SAP CR content version = "SAP_CR 3.0")

then the SAP_CR version is not changed in the target SLD. (Can be seen under "Administration -> details -> Data")

The two SLD do have the same version (7.0) and CIM model 1.5.42.

The import have the following error, but I don't think this is the reason for the above mentioned problem:

233 objects failed to load:

CIM_ERR_FAILED: Qualifier MAX(1) violated for property reference SAP_SPFeatureStackSoftwareFeature.Antecedent: SAP_SPFeatureStackSoftwareFeature.Antecedent=ref"SAP_CoherentSoftwareUnit.IdentifyingNumber=\"01200314690900000164\",Name=\"1\",ProductName=\"SAP XMAM\",Vendor=\"sap.com\",Version=\"SAP MAM 2.5 (ON ME2.1)\"",Dependent=ref"SAP_SupportPackageFeatureStack.CollectionID=\"012003146933000000761\""

BR

Tom Bo

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 06, 2009 at 11:15 AM

    You might be right a merge might occur rather than an overwrite

    The recommended way is note 1093168 - however because this is a export ALL - it cannot be determined if

    a CR repair will be enough - another thing to note avoid Export ALLs to SLDs that already contain content (any content from any another source) - usually an Export ALL is done to a empty namespace then only incremental exports lines are performed in future

    Assuming this is test environment you might be able to experiment - the worst case scenario is to empty (delete) the

    default namespace (this will recreate a new default namespace) and start again with valid backup or manually

    Best wishes

    Stuart

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 05, 2009 at 12:57 PM

    Check if SAP

    Note 669669 - Updating the SAP Component Repository in the SLD

    helps you.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 06, 2009 at 09:42 AM

    Hi Tom

    If in this case you chose to "Import Anyway" please see note 1045423 and 1093168

    Other potential causes -->

    1) If you did not "Import Anyway" this time, perhaps this was done in the past i.e the CR already inconsistent

    therefore you have to either repair or restore

    2) If you did not import anyway at all now or in the past its most likely the error is caused by the target SLD being used to

    getting an import line from a different source than the source SLD - whats happening now is you are mixing content from

    another SLD (albeit CR) with CR that was likely previously imported from SAP

    In terms of point 2 to it is important to establish the import line at the planning stage and stick to it - i.e if the SLD gets content from SAP continue patching from SAP - if the SLD gets content from another SLD continue with this import line

    - avoid mixing content from different import lines. Ideal use of a CR export would be target SLD is at base installation

    level and receives only routine updates from source SLD i.e no individual patching from SAP download is undertaking since installation on the target SLD

    Also important --> Before importing any content ensure the target SLD is fully backed up - that way you don't need

    to do a repair or individual analysis of the errors - can just restore

    Best wishes

    Stuart

    Add a comment
    10|10000 characters needed characters exceeded

    • Hej Stuart

      Thanks a lot for the recommendations. I am playing a little around with SLD's and export/imports and it seems that it is very important to have a transport-landscape/strategy and "stick" to it as you mentioned.

      I am trying to investigate this further in an test environment, where I know the exact status (which content from where) of the SLD's involved.

      One specific question regarding the backup: Can a restore (import of backup) restore the original SLD namespace - It is my believe that an import will not clear the target SLD (namespace) - but try to merge the import into the existing content?

      A workaround of cause is to create a new (test) namespace as a copy of the active (import CIM and EXPORT ALL/FULL) and do test-imports here and if ok, then the imports can be done in the active namespace.

      BR

      Tom Bo

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.