ADS version 12.0.0-rc-23
We need to double check that the server selected matches the DBA Tool
\\...\\ .\\हिñçêČάй語简�?한\\.Kᢒꌊꇄꇎ: java.lang.OutOfMemoryError: Java heap space at \\...\\ .\\हिñçêČάй語简�?한\\.Iꁃ⠜ꇏꄳ.handleException(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.Iꁃ⠜ꇏꄳ.a(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.rᛣᢅꄅ͔.h(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.rᛣᢅꄅ͔.aL(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.m⣵ꂥ᜵ꎚ finally 4.a(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.yꇱꇆꄡꁷ.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:721) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:682) at java.awt.EventQueue$3.run(EventQueue.java:680) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:691) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139) at java.awt.EventDispatchThread.run(EventDispatchThread.java:97) Caused by: java.sql.SQLException: java.lang.OutOfMemoryError: Java heap space at \\...\\ .\\हिñçêČάй語简�?한\\.tꈄ⠱ꏿ⣅ throws final.executeQuery(Unknown Source) ... 19 more Caused by: java.lang.OutOfMemoryError: Java heap space at java.lang.reflect.Array.newArray(Native Method) at java.lang.reflect.Array.newInstance(Array.java:70) at oracle.jdbc.driver.BufferCache.get(BufferCache.java:226) at oracle.jdbc.driver.PhysicalConnection.getCharBuffer(PhysicalConnection.java:7672) at oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:1005) at oracle.jdbc.driver.T4CTTIdcb.receiveCommon(T4CTTIdcb.java:277) at oracle.jdbc.driver.T4CTTIdcb.receive(T4CTTIdcb.java:146) at oracle.jdbc.driver.T4C8Oall.readDCB(T4C8Oall.java:844) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:358) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193) at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:873) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289) at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1491) at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:406) at \\...\\ .\\हिñçêČάй語简�?한\\.tꈄ⠱ꏿ⣅ throws final.executeQuery(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.Iꁃ⠜ꇏꄳ.a(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.rᛣᢅꄅ͔.h(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.rᛣᢅꄅ͔.aL(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.m⣵ꂥ᜵ꎚ finally 4.a(Unknown Source) at \\...\\ .\\हिñçêČάй語简�?한\\.yꇱꇆꄡꁷ.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:721) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:682) at java.awt.EventQueue$3.run(EventQueue.java:680) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:691) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244)
Sorry it was my mistake I had connected to Oracle server. But in nay case there should be correct error about non interoperability of tools.
This is a bug in the Oracle JDBC drivers. ADS currently uses 11.2.0.3, which is the latest version from Oracle.
This is a bug in the Oracle JDBC drivers. ADS currently uses 11.2.0.3, which is the latest version from Oracle.
We where setting the default fetch size for oracle drivers to 5000. This seems to cause huge memory consumption by the drivers, so we reduced it to 1000 for our statement executions.
We where setting the default fetch size for oracle drivers to 5000. This seems to cause huge memory consumption by the drivers, so we reduced it to 1000 for our statement executions.
after a bit more testing and research we found and fixed a memory leak and set the default oracle fetch size to 500 to better suit the default needs.
after a bit more testing and research we found and fixed a memory leak and set the default oracle fetch size to 500 to better suit the default needs.
> This is a bug in the Oracle JDBC drivers.
Could you please then point on that bugreport?
> This is a bug in the Oracle JDBC drivers.
Could you please then point on that bugreport?
After further investigation, we found that is was not a bug in the JDBC driver, but a bug caused by a combined change in the 11g driver and the default fetch size in ADS. In the 11g driver, the way data is retrieved over the network is effected differently by the fetch size. In ADS 12.0 we changed the default fetch size to 5,000 initially. Fetch size of 5,000 and the 11g JDBC driver don't work well. The default fetch size is now 100, which works well with 11g driver. In ADS you can change the fetch size for a connection in Server Registration->Advanced->Fetch Size.
After further investigation, we found that is was not a bug in the JDBC driver, but a bug caused by a combined change in the 11g driver and the default fetch size in ADS. In the 11g driver, the way data is retrieved over the network is effected differently by the fetch size. In ADS 12.0 we changed the default fetch size to 5,000 initially. Fetch size of 5,000 and the 11g JDBC driver don't work well. The default fetch size is now 100, which works well with 11g driver. In ADS you can change the fetch size for a connection in Server Registration->Advanced->Fetch Size.
Issue #7817 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 12.0.2 |
No time estimate |
Sorry it was my mistake I had connected to Oracle server. But in nay case there should be correct error about non interoperability of tools.