Unexpect Socket closed error while connecting to MYSQL
Posted: Mon Oct 01, 2012 2:54 pm
Hi All,
We are facing the issue of Socket Closed error when trying to read data from the MYSQL database.
The very first time in production the process completede without any issues but from the second day onwards we are seeing that two out of 3 jobs that we use to read data from the MYSQL tables.
But we see that when we rerun the main sequence again after sometime the sequence completes successfully without issues.
We even tried to change the schedule of the main sequence to run at a later time , then for 4 to 5 days the process ran fine without issues but again since two days now we have started to see the same issue where it falis at first for two of the jobs (while one job always rund successfully at the first run itself) .
Below is the Fatal error
MYSQL_SKILLS,0: [IBM(DataDirect OEM)][ODBC MySQL Wire Protocol driver]Socket closed.
The runLocally() of the operator failed.
MYSQL_SKILLS,0: Operator terminated abnormally: runLocally() did not return APT_StatusOk
We are facing the issue of Socket Closed error when trying to read data from the MYSQL database.
The very first time in production the process completede without any issues but from the second day onwards we are seeing that two out of 3 jobs that we use to read data from the MYSQL tables.
But we see that when we rerun the main sequence again after sometime the sequence completes successfully without issues.
We even tried to change the schedule of the main sequence to run at a later time , then for 4 to 5 days the process ran fine without issues but again since two days now we have started to see the same issue where it falis at first for two of the jobs (while one job always rund successfully at the first run itself) .
Below is the Fatal error
MYSQL_SKILLS,0: [IBM(DataDirect OEM)][ODBC MySQL Wire Protocol driver]Socket closed.
The runLocally() of the operator failed.
MYSQL_SKILLS,0: Operator terminated abnormally: runLocally() did not return APT_StatusOk