Hyperion Financial Management - Version 184.108.40.206.00 to 220.127.116.11.702 [Release 9.2 to 11.1] Information in this document applies to any platform.
Delete Invalid Records does not complete. HsvEventLog.log contains errors like this:
<Num HEX=0x80041E80>-2147213696</Num> <Description Src=HFM>An unknown error has occurred in the HsvDSData2 object </Description> <Type>1</Type> <DTime>8/18/2009 4:39:20 PM</DTime> <Svr>...</Svr> <File>CHsvDSData2RefInt.cpp</File> <Line>2610</Line> <Ver>18.104.22.168.2143</Ver>
This is usually observed when big changes are implemented in metadata, resulting in great numbers of records becoming invalid. It is very likely to appear after deleting an entire Scenario, for example.
The process heavily relies on database performance. As soon as the database cannot keep up with requests from the application, the process is aborted. There appears to be less tolerance of database failures in this particular feature of FinancialManagement. Database performance can be slow for a number of reasons (heavy usage, bad network, bad indexes etc) which are not covered in this note.
The process will completes as long as you set the SQLCommandTimeout to a high enough value, for example 240.
You can change this value on the FinancialManagement application server under Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server. Create a DWORD called SQLCommandTimeout if not there already. Reboot the application server after the change.
This value may not be optimal for day-to-day operations of Financial Management. Unless you are also experiencing other issues / errors related to slow database performance, it is recommended to revert back to the original value (or delete the parameter) after a successful run of Delete Invalid Records.
Please make sure a full backup of the registry exists.