This SAS KB article provides steps to enable debug traces for SAS Infrastructure for Risk Management Live ETL job failures in Linux and Microsoft Windows operating environments.
log4j.logger.com.sas=TRACE, A1
2. Open the SASIRMServer-log4j file that resides in the SAS-configuration-directory\Lev1\Web\Common\LogConfig\ directory and locate the following code:
<!-- SAS: IRM Solutions -->
<logger name="com.sas.solutions.risk.irm" additivity="false">
<level value="INFO" />
<appender-ref ref="SAS_FILE"/>
<appender-ref ref="SAS_CONSOLE"/>
</logger>
Change that code so that it looks like the following:
<!-- SAS: IRM Solutions -->
<logger name="com.sas.solutions.risk.irm" additivity="false">
<level value="DEBUG" />
<appender-ref ref="SAS_FILE"/>
<appender-ref ref="SAS_CONSOLE"/>
</logger>
3. Stop and restart SASServer8_1.
4. Reproduce the problem with the Live ETL job, and collect the following log data:
log4j.logger.com.sas=TRACE, A1
2. Open the SASIRMServer-log4j file that resides in the SAS-configuration-directory/Lev1/Web/Common/LogConfig/ directory. Locate the following code lines:
<!-- SAS: IRM Solutions -->
<logger name="com.sas.solutions.risk.irm" additivity="false">
<level value="INFO" />
<appender-ref ref="SAS_FILE"/>
<appender-ref ref="SAS_CONSOLE"/>
</logger>
Change those lines so that they look like the code below:
<!-- SAS: IRM Solutions -->
<logger name="com.sas.solutions.risk.irm" additivity="false">
<level value="DEBUG" />
<appender-ref ref="SAS_FILE"/>
<appender-ref ref="SAS_CONSOLE"/>
</logger>
3. Stop and restart SASServer8_1.
4. Reproduce the problem with Live ETL job, and collect the following log data: