How to Change the Logging Levels for Hyperion EPM Products in Release 11.1.2.x

How to Change the Logging Levels for Hyperion EPM Products in Release 11.1.2.x (Doc ID 1158016.1) Financial Reporting (FR) Usage Tracking - Report Access by Username (Doc ID 1947774.1) How to Change the Logging Levels for Hyperion EPM Products in Release 11.1.2.x (Doc ID 1158016.1) To BottomTo Bottom In this Document Goal Solution APPLIES TO: Hyperion Essbase - Version 11.1.2.0.00 and later Hyperion BI+ - Version 11.1.2.0.00 and later Hyperion Financial Management - Version 11.1.2.0.00 and later Hyperion Planning - Version 11.1.2.0.00 and later Hyperion Essbase Administration Services - Version 11.1.2.0.00 and later Information in this document applies to any platform. GOAL Diagnostic logs are needed frequently to resolve customer issues. By default the logging level is set to give a minimum set of detail to save on server disk space. The logging level will often need to be change to a level to give more details to resolve a problem. SOLUTION To resolve this take the following actions: Navigate to MIDDLEWARE_HOME/user_projects/domains/domain name/config/fmwconfig/servers/ Ex.: Oracle_Home\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers For the Product, select the corresponding managed server name: Shared Services and EPM Workspace -> FoundationServices Essbase Administration Services -> EssbaseAdminServices Provider Services -> AnalyticProviderServices Reporting and Analysis Framework -> RaFramework Financial Reporting -> FinancialReporting Financial Management -> FMWebServices Planning -> Planning Open logging.xml file in a text editor. Scroll down to the section starting with Change NOTIFICATION to any of the following logging levels: Message Type Level Description INCIDENT_ERROR 1 A serious problem that may be caused by a bug in the product and that should be reported to Oracle Support. Examples are errors from which you cannot recover or serious problems. ERROR 1 A serious problem that requires immediate attention from the administrator and is not caused by a bug in the product. An example is if Oracle Fusion Middleware cannot process a log file, but you can correct the problem by fixing the permissions on the document. WARNING 1 A potential problem that should be reviewed by the administrator. Examples are invalid parameter values or a specified file does not exist. NOTIFICATION 1 A major lifecycle event such as the activation or deactivation of a primary sub-component or feature. This is the default level for NOTIFICATION. NOTIFICATION 16 A finer level of granularity for reporting normal events. TRACE 1 Trace or debug information for events that are meaningful to administrators, such as public API entry or exit points. TRACE 16 Detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. TRACE 32 Very detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. Save the logging.xml file and restart the service(s) for the corresponding Product.