The following sections contain information about Oracle Hyperion Data Relationship Management logs, which are in EPM_ORACLE_HOME/products/DataRelationshipManagement/server/bin.
| Name | Contents | Rotation |
|---|---|---|
drm-dbconfig.log | Database configuration log—Information generated by the Data Relationship Management console upon configuration of an application database. | Archive |
Windows Application Event log | Information written by the Data Relationship Management Server. Includes Data Relationship Management events, server messages, and errors. | Follow standard IT practices should be followed in managing the application event log. |
Import log | Information written by the Data Relationship Management Batch Client. This log includes details about an Import operation. | Can be deleted when not needed |
Blender log | Information written by the Data Relationship Management Batch Client. Includes details about a Blender operation. | Can be deleted when not needed |
DRM_Batch_Client_[datestamp].log | Information written by the Data Relationship Management Batch Client (User can override the name and location). Includes process-related information for all operations for a given date. | Can be deleted when not needed |
Transaction History | Transaction information written by the Data Relationship Management system and maintained in the Data Relationship Management repository database Note: To view Transaction History from the Data Relationship Management client, click Audit. | As Data Relationship Management versions are deleted, the corresponding transactional history is also deleted. |
Data Relationship Management logging is divided between runtime processes and transaction history.
To change logging levels for runtime processes, edit MIDDLEWARE_HOME/EPMSystem11R1/products/DataRelationshipManagement/server/configdrm-log4net.xml on the process manager machine.
You must have application administrator privileges to set Data Relationship Management Transaction History logging levels. Set TransactionLevels system preferences to specify the action types to capture in the transaction history.
Note: | After changing log levels for the Transaction History, the application administrator must restart the Data Relationship Management service. |
To set Transaction History logging levels:
In the Data Relationship Management Web client, select Administer.
Under Metadata, expand the System Preferences, and edit the TransactionLevels preference.
In TransactionLevels, select a transaction level type:
Logged Action records basic logging information, such as users logging in and logging out.
Core Action records actions that change the version, hierarchy, or node information, such as Add Node, Change Property, or Move Node.
Result Action records actions that result from core actions. For example, if the “clear all below core” action is performed, then properties are cleared from individual nodes. Clearing properties from the individual nodes is a result action.
Loss Action records loss of data due to a core action. For example, when a node is deleted, the defined properties for that node are deleted, which is a loss action. Loss actions are controlled by the LossLevel system preference.
Set additional system preferences:
LossLevel indicates what to track for lost information. You can set the preference to Defined or All Items. When set to Defined, only values that are specifically set at the node are tracked when the node is deleted. When set to All, derived, default, and inherited values also are tracked in the LossAction.
AllowAsOf forces tracking of Core Actions.
Note:
If the Loss Action is specified, or if AllowAsOf is turned on, then Core Actions are tracked, even if not set in the TransactionLevels system preference. Recommended preference settings are All Items and AllowAsOf unless you require different settings for storage or performance reasons.
Restart the application to put the setting changes into effect.