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.

Learn more
I AGREE
Reject
Calling all Racers for the Alteryx Grand Prix! It's time to rev your engines and race to the stage at Inspire! Sign up here.
community Data Science Portal Alteryx.com
alteryx Community
Search
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Close
Free Trial

Alteryx Designer Knowledge Base

Definitive answers from Designer experts.

Error: "ORA-12592: TNS:Bad Packet Error" occurs when running a workflow

gtorres8
Alteryx Alumni (Retired)
Created

‎06-03-2020 07:14 AM

Environment Details


When running a workflow, intermittently the following error occurs:
 

ORA-12592: TNS:Bad Packet Error
 

idea Skyscrapers

The error seems to be more prominent while on VPN.
 

  • Alteryx Designer + Scheduler
    • All versions
  • Oracle
    • 11g +


Cause


Cause 1

ORA-12592 is an Oracle network error that could be related to the network or the amount of data that is running through the workflow or both.

 

Cause 2

Incoming Null data is being loaded to an Oracle table that has NOT NULL constraints.

 



Resolution


Solution 1

Adjust Oracle parameters on the Oracle server. Contact the organization's IT team to help with any network monitoring and/or the Oracle DBA to adjust the following Oracle parameter in the SQLnet.ora file.

 

SQLNET.SEND_TIMEOUT=

(Ask the Oracle DBA for the exact value.)

Example:
SQLNET.SEND_TIMEOUT=600

 

Solution 2

If data coming into the workflow has null values and the Oracle table(s) constraints are set to NOT NULL; change the constraints to the table(s) to nullable. Please consult the Oracle DBA to make the change. See the Alteryx Community post for more information.


 

Workaround 1

Add the throttle tool to the workflow to control the amount of data that can pass through to downstream tools by dictating how many records are sent per minute; in case too much data is coming in at once. See the throttle tool help file for more information.
 

Workaround 2

Attempt to schedule data intensive workflows for the weekends or late nights when network and VPN loads are minimal.
 

Additional Information

Oracle documentation
Alteryx Community Post

Labels