Не факт, но можно заглянуть в RSTSODSPART, RSTSODSREQUEST.

The activation of data in an Operational Data Store (Persistent Staging Area) can take a very long time if you try to activate a large number of requests at the same time which, in turn, contain a large number of records altogether.
The actual activation step is independent of the number of requests that are to be activated and only depends on the total number of records to be activated. The postprocessing, however, which handles the monitor logging of the activation for the activated requests and the formattin of the messages that were issued during the activation, is quadratically proportional to the number of requests and the number of data packages in the change log that were generated during the activation.
This means that if the package size of the data in the change log was set too low and the activation generates more than 1000 packages in the change log, the 'postprocessing' may take much longer than the actual activation

Ensure that the setting in the "Minimum number of data records" field of the global ODS settings is large enough to ensure that not more than the maximum number of 1000 data packages is generated during the activation step.
If you multiply the number of records to be activated in the activation queue by 2, you get the maximum number of possible records that can be contained in the change log after the activation.
Divide this number by the value of the "Minimum number of data records" field. This gives you the number of data packages.
If the "Minimum number of data records" field is empty, the system uses 10,000 internally as default value (10,000 records for each data package)