How to Extract Hyperion Financial Management (HFM) ErrorLog Entries from Database Using HFMErrorLogViewer.exe

The purpose of this article is to explain how to extract Hyperion Financial Management (HFM) server messages from the database either to assist Oracle Support with working on a Service request or simply to archive entries. HFM application servers write messages to 3 locations: Windows server Application Event log, database table named HFM_Errorlog and to a text file named HsvEventlog.log located “%Hyperion_Home%\FinancialManagement\Server Working Folder” for all versions prior to 11.1.1.0.00 and %Hyperion_home%\logs\hfm in versions 11.1.1.0.00 through 11.1.1.3.00. The application event log and HsvEventlog.log files will contain messages specific to that HFM application server while the HFM_Errorlog entries will contain messages from all HFM application servers that access the same schema. In general, the only messages that are not contained in the HFM_Errorlog table will be database connection related messages and it is this reason that Oracle Support will usually request extracts from the database anytime the HFM implementation has more than 1 HFM application server and database connection issues are not suspected. DETAILS Tool Location: The utility is located in the “%Hyperion_Home%\FinancialManagement\Consultant Utilities” directory on the HFM application server as well as HFM client installations where the Consultant utilities optional component was selected during installation. Extracting the Database entries into the log viewer: When the utility is launched, the initial messages are populated with HFM messages parsed from the server’s application event log. Although it is not necessary to view the database messages before extracting, messages from the database can be viewed by selecting “Open an Error log from a database” from the File menu. To extract entries from the Database, select “Extract Database Entries to File(s)” from the Tools menu. A new window is opened with multiple options that can be selected. The HFM Database UDL file should be selected. Options to control what entries will be extracted can be checked as needed. Extracting to a Single file – This option generates 1 output file containing all entries in HFM_Errolog table. Extracting into Multiple files - This option takes the following modifiers: Split Files by Date – All entries in the HFM_Errorlog table will be extracted and the entries in the output files can be grouped by: - Day - Month – This is generally the preferred option when providing logs to Oracle support. Providing logs covering the last 2 month will generally be sufficient. - Year Split by Size – All entries in HFM_Errorlog table will be extracted and output size limits can be specified. Extract for a single HFM application – Drop down list allows for extracting all entries specific to an application. Extract for a specific data range – Allows for limiting entries extracted by date. Output File Format - Four options of selecting the output file has been defined. HFM Log File Format – This is default and preferred output file format when working with Oracle Support. Comma-Delimited CSV Format Semi-Colon Delimited CSV Format CSV Format Custom Delimiter Output folder - Select a location with sufficient space to hold the output files. Output Filename or Prefix – Default prefix name can be specified or use the default. As the title indicates, this article demonstrates the extraction of the Error Log entries from the hosting Database. Similarly, the Error log entries can be extracted from the HsvEventlog file or the application event log file