XPSImport

[Shrwn]

Hi All,

 

When we are trying to import policies, domain and aco in R12.5 Policy server by taking Export from R12.52 Policy server, we are getting following error:

 

CA-XPS:IMP0045(ERROR) : The attribute named "CA.SM::Policy.ValidateIdDifferentUser" is invalid and does not exist in the data dictionary.
CA-XPS:IMP0039(ERROR) : An error was encountered while resolving the XML object with XID "CA.SM::Policy@04-00048e66-6391-17fb-a109-04820a28a08e" in the XML file to an object.
CA-XPS:IMP0039(ERROR) : An error was encountered while resolving the XML object with XID "CA.SM::Domain@03-0001fb4f-b089-1799-b411-04820a2880aa" in the XML file to an object.
CA-XPS:IMP0003(FATAL) : An error was encountered during import of policy data

 

 

Is this because of Policy Server different version? if so, what's the possible solution for this?

 

Regards,

Shrawan

[Ujwol]

That's right Shrawn.

You cannot migrate policies (xpsexport) from higher version of policy store to lower version. This is because often a newer schema  would have been added which may be missing in the lower version.

For e.g in your case a new attribute CA.SM.Policy.ValidateIdDifferentUser seems to have been added in 12.52 which wasn't available in12.5.

You can check this yourself by searching for this property in all of .xdd files (e.g SmObjects.xdd, SmMaster.xdd etc)

If the changes are not much, you may be able to manually delete the unavailable attribute from the XPSExport and import it. But it's going to be tricky as it involves manual modification.

[Shrwn]

Hi Ujwol

 

Thanks for your response.

 

Is there any CA thread to guide us how can we manually delete these attributes?

 

Regards,

Shrawan

[Shrwn]

Hi Ujwol,

We have done this far enough to remove extra attributes from XML file but we are getting problems with trusted hosts movement. 

Any suggestions from your side? because if we remove them from XML we need to re-register agents again.

Regards,

Shrawan

[Ujwol]

No there's isn't any as it isn't common and support use case.

But what you need to do is something like this:

For e.g lets say your export is:

<object>

  <attr1 />

  <attr2 />

  <attr3 />

</object>

Now, if attr2 is missing in lower version you would simply delete this from the export file and reimport

So, the above export should look like this after modification 

<object>

  <attr1 />

  <attr3 />

</object>

But again this could be as simple as this or may be much more complex than this. It depends on how many attributes are chnaged.

[Shrwn]

Hi Ujwol,

 

Thanks for your response.