cancel
Showing results for 
Search instead for 
Did you mean: 

Error while importing HCM_Staging_Area_Identity Store

Former Member
0 Kudos

Hi *

During import of "HCM_Staging_Area_Identity Store.mcc" I receive the following Error: Could not update identity center with attribute '333\MX_ENTRYTYPE'

I realized that the Import-File has a Schema-version 517 while the Target IdentityCenter has version 543 (7.1 SP3-01)

How can I solve this error?

Will there be a new version of the Import-File?

Br

Michael

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Michael,

I had the same error and reported this to SAP support. They responded:

Hi, this is du to an hardcoded reference to an identity store 4 in the export file. As a workaround for now, I have attached a developer build-ed version of the imxport.jar. It is a SP4 version, and you need to modify the MX_ENTRYTYPE attribute after the import, so that it is referingthe identity store the attribute resides in. I have forwarded the bug in the HCM file internally. When the SP4 official version is released, upgrade the imxport.jar to that version, so we can better help you in the future.

I tried the mentioned JAR file update and guess what? This specific error is now gone but the next appears when trying to update the entry types. I re-reported this minutes ago so we'll see. I'll keep you posted.

BTW: I think the error can be circumvented by importing the file several times, thus eventually creating ID store '4'. This should work I guess, I just haven't tried it yet.

Regards,

Jos

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

the last error was due to Oracle's open_cursors parameter. I increased the parameter to 400

ALTER SYSTEM SET open_cursors = 400 ;

and after this the import went just fine.

I can send you the updated jar file if you wish, with this you can import the mcc file without errors.

Regards,

Jos

Former Member
0 Kudos

Yes, please forward it to me. Look at my SDN Business Card.

Since I use MSSQL05 I have to test if this jar will help me.

BR

Michael

Former Member
0 Kudos

The new imXport.jar solved my problem with MSSQL05 and IdM 7.1 SP3 and current patch.

Thanks.

Former Member
0 Kudos

too bad - I just tried that option but the import keeps failing, even with IDstore 4. I'll await the repsonse from SAP...