EMAD4JMANAGER Script Fails With StringIndexOutOfBoundsException (Doc ID 1382304.1)

Last updated on MARCH 08, 2017

Applies to:

Enterprise Manager Base Platform - Version: 11.1.0.1 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


EMAD4JMANAGER installation is failing due to a JDBC connection error.

Error stack will be similar to this,

lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:686) at
oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:386)
at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:634)
at oracle.net.ns.NSProtocol.connect(NSProtocol.java:208)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:966)
oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:203) at
oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:185) at
oracle.sysman.e2e.model.ad4j.common.dbconnection.testdictcon(dbconnection.java:519) at
oracle.sysman.e2e.model.ad4j.common.adminJam.runDiagnostic(adminJam.java:1138) at oracle.sysman.e2e.model.ad4j.remote.Jam.init(Jam.java:801) at
oracle.sysman.e2e.model.ad4j.remote.servlet.AD4JManagerServlet.init(AD4JManagerServlet.java:51)
at
weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

Cause

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 hundreds of Community platforms