com.ibm.tivoli.namereconciliation.common.NrsDatabaseException: 3001. An unexpected database system error has occurred.The displayed message is very generic, so to be able to further debug the issue, we need to enable the IT Registry logging and tracing. This is achieved by performing the following steps:
############################################################ # Default Logging Configuration File # # "handlers" specifies a comma separated list of log Handler # classes. These handlers will be installed during VM startup. handlers= com.ibm.tivoli.dataintegration.common.logging.DISLogFileHandler, com.ibm.tivoli.dataintegration.common.logging.DISTraceFileHandler # Default global logging level. The valid logging levels are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST .level= FINEST # DIS Log File Handler # default file output is in user's home directory. com.ibm.tivoli.dataintegration.common.logging.DISLogFileHandler.pattern = logs/dis%u.log com.ibm.tivoli.dataintegration.common.logging.DISLogFileHandler.limit = 5000000 com.ibm.tivoli.dataintegration.common.logging.DISLogFileHandler.count = 1000 com.ibm.tivoli.dataintegration.common.logging.DISLogFileHandler.formatter = java.util.logging.SimpleFormatter # DIS Trace File Handler # default file output is in user's home directory. com.ibm.tivoli.dataintegration.common.logging.DISTraceFileHandler.pattern = logs/dis%u.trace com.ibm.tivoli.dataintegration.common.logging.DISTraceFileHandler.limit = 5000000 com.ibm.tivoli.dataintegration.common.logging.DISTraceFileHandler.count = 1000 com.ibm.tivoli.dataintegration.common.logging.DISTraceFileHandler.formatter = java.util.logging.SimpleFormatter # Facility specific properties. # Provides extra control for each logger. #com.ibm.tivoli.namereconciliation.api.level = FINE #com.ibm.tivoli.namereconciliation.service.level = FINE #com.ibm.tivoli.namereconciliation.service.plugins.level = FINE #com.ibm.tivoli.namereconciliation.service.plugins.cdm.level = FINE #com.ibm.tivoli.datacleanser.level = FINE #com.ibm.tivoli.dataintegration.metadata.level = FINEPlease notice the paths in bold - logs/dis%u/log and logs/dis%u.trace. They determine where the IT Registry log and trace files will be stored and the file name format. Also, this configuration causes all occurring events to be logged since its logging level is set to FINEST. This is required for discovering some database errors, which are logged only at the lowest level. For more details on Java logging and the configuration file see http://www.oracle.com/technology/pub/articles/hunter_logging.html.
Save the file as dis.logging.properties and place it in the solution directory of TDI.
rem Take the supported env variables and pass them to Java program set LOG_4J=-Dlog4j.configuration="file:etc\log4j.properties" set DIS_LOG=-Djava.util.logging.config.file=dis.logging.properties set ENV_VARIABLES=%LOG_4J% %DIS_LOG% "%TDI_JAVA_PROGRAM%" -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %*For Linux/UNIX systems the change is very similar, in ibmdisrv.sh make the changes outlined in bold:
# Log4j configuration file LOG_4J=-Dlog4j.configuration=file:etc/log4j.properties DIS_LOG=-Djava.util.logging.config.file=dis.logging.properties "$TDI_JAVA_PROGRAM" $TDI_MIXEDMODE_FLAG -cp "$TDI_HOME_DIR/IDILoader.jar" "$LOG_4J" "$DIS_LOG" com.ibm.di.loader.ServerLauncher "$@" &The path to dis.logging.properties can vary depending on the location where you placed the file. If it is in TDI's solution directory, only its name is needed.