Symptom
- When importing or validating various versions picklists from Import and Export Data, in Monitor Jobs, the import/Validation job failed
- Check from provisioning Job run history, the corresponding MDF Data Import job details, it display error message like"...Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded (max heap: 35916 MB)
at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:....."
Environment
- SAP SuccessFactors HXM Suite
- SAP SuccessFactors Metadata Framework (MDF)
Reproducing the Issue
User attempts to import picklists with various versions in Import and Export data, however the import job status is failed.
Cause
Go to provisioning job history and check the corresponding job failed details:
...Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded (max heap: 35916 MB)
at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:....."
If the job failed due to above error, engineering team has identified that if Picklist have too many versions, it will cause below error in MDF Data Import job Details of provisioning Job run histoyr:
And even picklist file can be imported, customer will have bigger problem when they use and manage the picklist, too many version of picklist will also bring trouble to customer.
Resolution
The best option is to reduce the version of picklist. It is actually a mis-use of version (timeslice) of picklist.
It is recommended to only keep 2-5 versions of a picklists and If necessary, insert two or three middle versions to represent big picklists changes.
See Also
2714036 - How to Import and Export a MDF Picklist - SuccessFactors
Keywords
SF, SuccessFactors, MDF, Picklist, Import Picklist, MDF-33910 , KBA , LOD-SF-MDF-IMP , Import and Export Issues , LOD-SF-MDF-PKL , Picklists , How To