Financial Reporting Studio: Enabling Standard Out & Standard Error Logs in Windows Registry
(Doc ID 1108390.1)
Last updated on MARCH 12, 2018
Applies to:Hyperion BI+ - Version 126.96.36.199.00 to 188.8.131.52.00 [Release 9.3 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 4.1.2015***
This article is intended to provide the steps to enable the standard out (stdout) & standard error (stderr) logs in Windows Registry to assist in troubleshooting FR Studio issues
While the FRPrintSrv, FRReportSrv, FRSchedSrv, FRUserLogin, & FRWebapp logs collect information needed to resolve FR Studio issues, the stderr provides additional details.
The stdout log is a redirect of the stdout of the JVM that is imbedded in Financial Reporting and provides other information, including Environment & Classpath information. The stderr log is also a redirect of the stdout of the JVM.
The System Admin has access to the server where Financial Reporting Studio is installed,and can create the logs and locations.
The logs are stored under the HYPERION_HOME on the FR Studio server, and the logs are updated anytime a action is taken in FR Studio.
This document is intended to be used by Support Engineers for troubleshooting Financial Reporting
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Financial Reporting Studio: Enabling Standard Out & Standard Error Logs in Windows Registry|