Source Extractor - SQL PLSQL - Error - IO exception Socket read timed out
Description
This page provides solution to the PL/SQL extraction error :
Extracting: Oracle system check constraints on tables.. Extraction error: Io exception: Socket read timed out
on Query
——
Extraction error: Closed Connection
Observed in CAST AIP
| Release | Yes/No |
|---|---|
| 8.2.x | ❌ |
| 8.1.x | ❌ |
| 8.0.x | ❌ |
| 7.3.x | ❌ |
| 7.2.x | ❌ |
| 7.0.x | ✅ |
Observed on RDBMS
| RDBMS | Yes/No |
|---|---|
| Oracle Server | ✅ |
| Microsoft SQL Server | ✅ |
| CSS2 | ❌ |
| CSS1 | ✅ |
Step by Step Scenario
Run the DB extractor
Action Plan
When large volume of data is extracted, the time taken is more; which may cause time-out at the router’s side that closes the socket.
To avoid this
- A parameter has to be added in Oracle to ping regularly in sqlnet.ora file. Apply the solution mentioned in the page CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ORA-17410 - No more data to read from socket
- Re-run the extraction.
Impact on Analysis Results and Dashboard
Impact of the error : Extraction is not complete
Impact of solution : No impact and extraction gets completed successfully.
Notes/comments
Ticket # 2844
Related Pages