This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
To resolve this issue, add SQLNET.SEND_TIMEOUT=<seconds> to sqlnet.ora on the server side.
In addition, contact your DBA for exact value.
SQLNET.SEND_TIMEOUTis usedto specify the time, in seconds, for a database server to complete a send operation to clients after connection establishment.
For environments in which clients shut down on occasion or abnormally, setting this parameter is recommended. If the database server is unable to complete a send operation in the time specified, then itlogs anORA-12535: TNS:operation timed outandORA-12608: TNS: Send timeout occurredto thesqlnet.logfile. Without this parameter, the database server may continue to send responses to clients that are unable to receive data due to a downed computer or is in a busy state.
You can also set this parameter on the client-side to specify the time, in seconds, for a client to complete the send operations to the database server after connection establishment. Without this parameter, the client may continue to send requests to a database server already saturated with requests.
@jbyrne4 Unfortunately no one replied to my post but after some research I found that the same workflow does not error out on my laptop but it errors out on the Alteryx server. I think tried other ETL tools recreating the same process and they all worked. So it was fair to say it was not oracle or the network. It had something to do with the Alteryx server. Are you running yours on the Alteryx server? I was trying to import a large file but added 2 columns using the formula tool before it imported. I removed the formula tool and imported the file as is then completed the 2 additional columns using the in database formula tool and it worked. After hours of frustration it makes little sense that this was the solution.
I have tried all kinds of different hacks to get it to work...
-Block Until Done to read in all of the data before writing
-Lowering Transaction Size (just ends up failing at the same rate and you end up having like 800k/10M records of a file written to the database, which is a mess)
-Running from Server, Running from Workstation
-Reading from CSV File
-Reading from YXDB
My DBA's could not see any issues with the network. Additionally, with programs like SQL Developer loader, I can load without fail...albeit more slowly than Alteryx and not something I can schedule on the server like I need.
Alteryx is really the only ETL tool I can use at this time, so it's frustrating that larger write jobs are extremely unreliable.