My Oracle Support Banner

SDU Ignored By The JDBC Thin Client Connection (Doc ID 2652240.1)

Last updated on MARCH 30, 2020

Applies to:

JDBC - Version 12.1.0.2.0 and later
Information in this document applies to any platform.

Symptoms

There is the need to increase the SDU size of the database connections to 32K (or more) to improve performance of a Java application using JDBC  Thin 18.3.

The database is a single instance multi-tenant database running on a 4 node cluster. GI is 12.2.0.1 and RDBMS is on 12.1.0.2.

The following has been implemented:
- Set DEFAULT_SDU_SIZE=131072 in sqlnet.ora of RDBMS home on all the nodes of the cluster, as well as set DEFAULT_SDU_SIZE=131072 in sqlnet.ora file of GI home.
SCAN and local listeners are restarted on all the nodes of the cluster.

- The sqlnet.ora file is updated on the client and DEFAULT_SDU_SIZE=131072 was added to it, and also (SDU=32768) was added to the TNS entries used by SQL*Plus connections.

- Additionally, the JDBC URL is set to include (SDU=32768) like the following:
jdbc:oracle:thin:@(DESCRIPTION=(SDU=32768) (ADDRESS=(PROTOCOL=TCP) (HOST=<PORT>) (PORT=<PORT>)) (CONNECT_DATA=(SERVICE_NAME=<SERVICA NAME>)))

Issue:
From SQL Plus (and Toad), when connecting to SCAN or LOCAL listeners, tracing connections shows that SDU size of 32K is used. 
From SQL Developer (or Java application), when connecting to SCAN listener, the trace shows the connection is using the default 8K of SDU.

JDBC seems to ignore the SDU setting in the connection string.


 

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
References


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