Technical Blog Post
Abstract
Troubleshooting BIRT report logger
Body
If you have upgraded from an earlier version of Maximo, in some environments the MAXLOGGER.PARENTLOGGERID of BIRT report loggers does not execute correctly. In these cases, if the loggers are enabled and the application server is restarted - but still the Report SQLs do not appear in the log - then execute the following sql.
select logger, logkey, maxloggerid, parentloggerid from maxlogger where logkey in ('log4j.logger.maximo.report', 'log4j.logger.maximo.report.birt','log4j.logger.maximo.report.birt.sql')
The result of the SQL will be something similar to this.
LOGGER LOGKEY MAXLOGGERID PARENTLOGGERID
---------- ------------------------------------------------ -------------- -----------------
report log4j.logger.maximo.report 24 (null)
birt log4j.logger.maximo.report.birt 25 24
sql log4j.logger.maximo.report.birt.sql 29 25
Make sure that the PARENTLOGGERID of LOGKEY log4j.logger.maximo.report.birt is same as MAXLOGGERID of
LOGKEY log4j.logger.maximo.report. If not then update PARENTLOGGERID of LOGKEY
log4j.logger.maximo.report.birt to match MAXLOGGERID of LOGKEY log4j.logger.maximo.report.
Similarly make sure that the PARENTLOGGERID of LOGKEY log4j.logger.maximo.report.birt.sql is same as MAXLOGGERID of LOGKEY log4j.logger.maximo.report.birt. If not then update PARENTLOGGERID of LOGKEY
log4j.logger.maximo.report.birt.sql to match MAXLOGGERID of LOGKEY log4j.logger.maximo.report.birt.
After making this change, restart the server for the logger to work properly.
UID
ibm11134351