How can I improve the performance of the Extracts run?

There are several options you could try to optimize the performance during such phases.

Improve the performance of your extract runs by using the new Baseline Only parameter. Use this parameter in your extract to create a baseline against which you can run all subsequent changes only extracts against. The baseline only parameter saves time when you run the extract because it does not generate an XML file and it does not deliver any output. It creates a full extract in less time and uses less storage in your application. Use this feature by selecting the Show hidden parameters option, and setting the Display column to Yes or Mandatory for the Baseline Only parameter. Use the Baseline Only parameter when submitting a baseline extract, and if the changes only parameter is set to mandatory, then use the All Attributes option.

Free up storage space in your application and improve performance by using the Delete Archive parameter. Use this parameter when you create a full extract of data, and not for changes only extract. When you run the extract the application generates the XML and archive and delivers the output to the destination. After the application delivers the output, for example the WebCenter Content, you have the option to discard the archive data and XML files, therefore reducing storage consumption by deleting these extract archives. Use this feature by selecting the Show hidden parameters option, and setting the Display column to Yes or Mandatory for the Delete Archive parameter.

Contact the help desk to manually gather the database table statistics for your pod. You might experience slow HCM Extract operations during certain testing phases of your implementation cycle, especially when the application tests bulk data loads at the same time. During regular operations the collection of statistics is scheduled to run weekly. However, if the data volume is high due to bulk data loads, then you should request this process to run manually.