My Oracle Support Banner

EM 11g: Enterprise Manager Grid Control 11.1.0.1 OMS rcuJDBCEngine Fails Executing Post-Install Steps in a Patch with Message: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 (Doc ID 1202185.1)

Last updated on OCTOBER 17, 2019

Applies to:

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

Symptoms

Many Oracle Management Server (OMS) patches for Grid Control 11.1 require two steps to be fully applied:
1. The opatch utility should be at the version required for application of the patch, as stated in teh patch README.
2. Run the opatch command to patch the binary bits on the OMS Oracle Home.
3. Run the rcuJDBCEngine to apply some SQL scripts against the repository.

Depending on the patch content, the 2nd step might be optional. These steps are always clearly documented in the patch README.txt file.

Under some circumstances, the execution of rcuJDBCEngine fails with the following exception:

Exception in thread "main" java.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)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:292)
        at 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:154)
        at oracle.sysman.assistants.common.dbutil.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:259)
        at oracle.sysman.assistants.common.dbutil.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:142)
        at oracle.sysman.assistants.common.dbutil.jdbc.ConnectionHelper.getConnection(ConnectionHelper.java:61)
        at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.getConnection(JDBCEngine.java:889)
        at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.connect(JDBCEngine.java:440)
        at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.main(JDBCEngine.java:1978)

 

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!

In this Document
Symptoms
Changes
Cause
Solution

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