Data Management Logs
FDMEE Logs
Default Log Location | Log File Name and Contents |
---|---|
MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/ErpIntegrator0/logs |
|
|
|
|
|
|
|
MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/ErpIntegrator0/logs/oracledi |
|
APPLICATION_ROOT_DIRECTORY/outbox/logs |
EPM-APPLICATION-NAME_PROCESS-ID.log —Logs generated by various load processes. This log can be viewed using the Show Log link in the Process Details page of FDMEE.
|
Data Relationship Management Logs
The Oracle Data Relationship Management Console Repository Wizard writes repository creation, copy, and upgrade information to a log that you can view during Repository Wizard operations. You can save the Repository Wizard log from the Repository Operation Complete page of the wizard. The Repository Wizard log is user-defined.
To capture Data Relationship Management installation issues, enable logging in the Data Relationship Management installer. For instructions, see the Oracle Data Relationship Management Installation Guide.
These Data Relationship Management log files are in the user's Windows temp directory; for example, C:/Documents and Settings/
user name/temp
:
-
MSI.log
—Information about the installation processThe primary log file for the Data Relationship Management is overwritten each time the Data Relationship Management installer is run. This log can be deleted.
-
MSI
xxxx.log
(where xxxx is a random alphanumeric character sequence)This log is useful for troubleshooting an installation failure. It can be deleted.
Caution:
MSI
xxxx.log
files of other products may be in the same folder, so verify that the time and date of the file match the time and date of the Data Relationship Management installation to ensure that you are deleting the correct file.
Note:
The path to the user's Windows home directory varies among Windows versions.
Data Relationship Management Analytics Logs
A persistent ODL logger is automatically configured for the Oracle Data Relationship Management Analytics application. Manual configuration of the managed server is not necessary. However, by default the logger level is set to the NOTIFICATION:1 level. If tracing is desired then set the level to TRACE:1 by navigating to Enterprise Manager and turning on debugging levels using the Configure Logging menu for the application.