Logs
This table shows the logs, their descriptions, and information on how to access them:
| OLAP log | Description |
|---|---|
| ALEAPR.txt | Database log that is logged by Log Service. In EPM Administration, select . Filter for OLAP Service Dynamic Worker events. file is in the local data root directory, not in theIn multi-tenant Infor Cloud, only Infor Support and Infor Cloud Operations can access these logs because they contain sensitive information. Caution: If the integrity of the implemented solutions depends on the content
log files, you must use the logs database after migration. The default name of the
Logs database is BIFarmLog.
|
| ALEALOG.txt
CellToSQL |
Records data changes that are specified by the Changelog
settings. In EPM Administration, select . When Changelog is enabled, OLAP continues to write cell changes to ALEALOG.txt file. Optionally, you can log cell changes to a relational database. If that is enabled, the ALEALOG.txt file is emptied every 10 seconds to the configured SQL tables. |
| Transactional Log | Contains the difference between the memory version of the database and the saved database. This log is used by OLAP internally. No administration is required. |
| Used Config | Contains a list of configurations of OLAP databases. The UsedConfig file is in the local database directory, not in the central database directory. |
| Used Config CM | Contains a list of OLAP system worker (Com Manager) configurations. The UsedConfigCM file is in the local data root directory, not in the central data root directory. |
| Request Log | Contains troubleshooting logs. These binary logs are accessible
only through development tools. In EPM Administration,
select . In multi-tenant Infor Cloud, only Infor Support and Infor Cloud Operations can access these logs because they contain sensitive information. |