Configure Data Pipeline Logging

you can troubleshoot data pipelines using the standard logging mechanism in {{ocient}} set these log levels in consultation with ocient support because this setting might impact performance modify the level of logging execute these two sql statements in this order to bump up the log message first, set the log level alter system alter log level set 'log4j' 'edebug'; then, set the level for the logging configuration alter system alter config set 'streamloader extractorengineparameters loggingconfig com ocient extractor allowlevel' 'trace'; if the log level of the first sql statement is lower than the log level of the second sql statement, the system loses log entries it is also possible to repeat the second sql statement for different package names, such as alter system alter config set 'streamloader extractorengineparameters loggingconfig com ocient extractor allowlevel' 'info'; alter system alter config set 'streamloader extractorengineparameters loggingconfig com ocient extractor en gine allowlevel' 'trace'; valid log levels this table provides an overview of the log levels you can specify for the alter system alter log level set sql statements with the streamloader extractorengineparameters loggingconfig keys the necessary log level for log4j must be set accordingly to at least the value specified in the column for the log4j level log level of streamloader extractorengineparameters loggingconfig derived level for log4j fatal error error error warn warn info info debug debug trace edebug reset the log level to reset the log level after you reproduce a problem, execute these sql statements alter system alter config reset 'streamloader extractorengineparameters loggingconfig com ocient extractor allowlevel'; alter system alter config reset 'log4j'; related links docid\ jtogwzl3dyxndxierzyzt docid\ f9wusuqndrusdbzuwr g9