Cube Compression : How do I solve the issue

Question

Hello,
I had 4 requests (21 million records)  in a cube to be compressed. The compression process started and successfully loaded the data into the E table of the cube and compression flag got checked into the cube. So I saw the records are successfully compressed.
However when it was doing the next step , that is to  delete records from the F table , the server re-booted and SAP rollback the deletion from the F table.
Question : How do I delete records from the F table. There are current 21 million records lying in Fact table for no reason. If retry to compress the request SAP gives an message request already compress.
I tried loading one more request and compressing the requesting , however the program just delete records from F table for current loads and not previous loads.
Please help.
thanks,
-HAri

Answer 1

From the FAQ Note on Compression - 407260
2. The data should never become inconsistent by running a compression. Even if you stop the process manually a consistent state should be reaches. But it depends on the phase in which the compression was when it was canceled whether the requests (or at least some of them) are compressed or whether the changes are rolled back. The compression of a single request can be diveded into 2 main phases.
a) In the first phase the following actions are executed:
               Insert or update every row of the request, that should be compressed into the E-facttable
               Delete the entry for the corresponding request out of the package dimension of the cube
               Change the 'compr-dual'-flag in the table rsmdatastate
               Finally a COMMIT is is executed.
b) In the second phase the remaining data in the F-facttable is deleted. This is either done by a 'DROP PARTITION' or by a 'DELETE'. As this data is not accessible in queries (the entry of package dimension is deleted) it does not matter if this phase is terminated.
               Concluding this:
               If the process is terminated while the compression of a request is in phase (a), the data is rolled back, but if the compression is terminated in phase (b) no rollback is executed. The only problem here is, that the f-facttable might contain unusable data. This data can be deleted with the function module RSCDS_DEL_OLD_REQUESTS. For running this function module you only have to enter the name of the infocube. If you want you can also specify the dimension id of the request you want to delete (if you know this ID); if no ID is specified the module deletes all the entries without a corresponding entry in the package-dimension.
                       If you are compressing several requests in a single run and the process breaks during the compression of the request x all smaller requests are committed and so only the request x is handled as described above.