Oracle listener/tnsnames setup for (SDU/TDU) through SQLNet TCPIP: DCS performance reduction/slowdown

Resolving The Problem

* Check how the DCS application and background jobs are connecting to Oracle:
- If DCS and the database are on the same machine
- check the ORACLE_HOME and connect string from whse_schema.map
- can be a direct connection or through SQL Net client using a connect string
- If DCS and the database are on separate boxes, connect through SQL Net client using a connect string

Check for SDU and TDU parameters as follows
These parameters should be set for the services in
Client Side : tnsnames.ora
Server Side : listner.ora
for appropriate connect string definitions
( SDU = 8192 )
( TDU = 8192 )

Note that BLANK spaces around "=" is a mandatory part of this syntax.

Please get in touch with DBA to verify that this configuration is correct and restart the server and the client.

Check that SDU is in effect: Check the parameters for the Oracle shadow process on Oracle DB Server.
ps -ef | grep -i oracle | grep -i 'local=no'

This should also show SDU as another call parameter in the Oracle Shadow Process call
Example :
oracle"xxxxSID" (DESCRIPTION=(LOCAL=NO)(SDU=8192))

Otherwise, the default value of 2k will be assigned to these pipes.
As the data rate in DCS during queries is more that 2k, the resultant fragments will slow the system down.