System crash during infoCube compression

Question

Hello Community,
Our system crashed due to failed memory DIMM while two fact table compression jobs were active. 
Because it was a hard crash without an orderly shutdown, any transactions in SAP not yet committed were lost. 
However, the oracle database did a successful recovery when the system was restarted, so no committed transaction were lost.
Is it possible that data was lost, corrupted, or duplicated in those cubes as a result of the interrupted compression jobs ?

Answer 1

Hi Fredrik,
you can either:
a) remove all necessary parameters from the paramfile using the relevant dbmcli commands (param_directdel)
b) perform a parameterfile recovery using dbmcli (param_restore)
You're okay as long as nothing was written on the new volume.
When using a) you need to make sure you delete all necessary parameter entries belonging to the datavolume (size, type etc.).
When you're restoring to an old parameterfile, you need to make sure the parameterfile's only difference is the datavolume extension as the last change, otherwise you'd possibly reset more than you'd like. To check the parameterhistory, you can for example take a look at the <DBSID>.pah file in the /sapdb/data/config directory.
If you're unsure what to do, i.e. if it's a productive system and you're an SAP customer: open an OSS message.
Regards,
Roland