A data load or dimension build can be stopped before it completes in two cases :
You should not stop a data load or dimension build unless it is necessary.
If a data load or dimension build process is terminated, Essbase displays the file name as partially loaded.
The recovery procedures that you must perform depend on the type of load you are performing and the Isolation Level database transaction setting:
If you are adding to or subtracting from data values during a data load to a block storage database, use the Committed Isolation Level setting, if possible. If the data load is terminated, this setting rolls the data load back to its previous state.
If you are adding to or subtracting from existing values in the data source and the Isolation Level setting is:
If you are overwriting the values of the data source, reload the data source when the server is running again.
If you initiate a data load or dimension build from a client and terminate the data load or dimension build from the server, it could take time before the client responds to the termination request. Because Essbase reads the source file until all source data is read, the amount of time depends on the file size and the amount of source data that Essbase has processed. If the process is terminated from the computer that initiated it, termination is immediate.
To stop a data load or dimension build before it completes, use a tool:
Tool | Topic | Location |
---|---|---|
Essbase - Administration Service (EAS) | Disconnecting User Sessions and Requests | Oracle Essbase Administration Services Online Help |
Essbase - MaxL | alter system kill request | Oracle Essbase Technical Reference |