My Oracle Support Banner

'SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"' Warning when Starting ODI Agent or Studio (Doc ID 2613021.1)

Last updated on APRIL 28, 2023

Applies to:

Oracle Data Integrator - Version 12.2.1.4.0 to 12.2.1.4.200304 [Release 12c]
Oracle Data Integrator on Marketplace - Version 12.2.1.4.200123 to 12.2.1.4.200304
Information in this document applies to any platform.

Symptoms

The following error is logged when starting Oracle Data Integrator (ODI) 12.2.1.4 Standalone Agent, and a similar error when starting the Studio component.

2019-11-01 14:50:22.375 NOTIFICATION New data source: [<REPO_SCEMA_NAME>/*******@jdbc:oracle:thin:@//:/]
2019-11-01 14:50:27.547 NOTIFICATION ODI-1128 Agent <AGENT_NAME> is starting. Container: STANDALONE. Agent Version: 12.2.1. Port: <AGENT_PORT>. JMX Port: <AGENT_JMX_PORT>.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Allowing :
2019-11-01 14:50:32.498 WARNING odi.core.security.SecurityManager.loadAuthenticationMode found the authMode:mUsingLDAPAuthentication: false,mUsingIDCSAuthentication:false,indExternalAuth:null.
2019-11-01 14:50:33.766 NOTIFICATION New data source: [<REPO_SCEMA_NAME>/*******@jdbc:oracle:thin:@:/]
2019-11-01 14:50:34.047 WARNING odi.core.security.SecurityManager.loadAuthenticationMode found the authMode:mUsingLDAPAuthentication: false,mUsingIDCSAuthentication:false,indExternalAuth:null.
2019-11-01 14:50:34.329 WARNING odi.core.security.SecurityManager.loadAuthenticationMode found the authMode:mUsingLDAPAuthentication: false,mUsingIDCSAuthentication:false,indExternalAuth:null.
2019-11-01 14:50:34.907 NOTIFICATION ODI-1111 Agent <AGENT_NAME> started. Agent version: 12.2.1. Port: <AGENT_PORT>. JMX Port: <AGENT_JMX_PORT>.
2019-11-01 14:50:34.922 NOTIFICATION ODI-1136 Starting Schedulers on Agent <AGENT_NAME>.
2019-11-01 14:50:35.719 NOTIFICATION ODI-1137 Scheduler started for work repository WORKREP on Agent <AGENT_NAME>.

There are no issues observed with executions or schedules.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.