Page 1 of 1
Job run *FAILURE* in 1440 minute(s) 2 seconds
Posted: Mon Jul 21, 2014 11:36 am
by igorbmartins
Hello, I am analyzing a very huge table and after 24 hours, it is failing with timeout error.
Job run *FAILURE* in 1440 minute(s) 2 seconds.
This error occur in more than one column, and always after 1440 minutes or 24 hours, so I would like to know if there are some way to increase this period.
Thanks,
Igor Bastos Martins
Posted: Mon Jul 21, 2014 12:28 pm
by PaulVL
What does the Director log error message say?
Posted: Mon Jul 21, 2014 1:07 pm
by rkashyap
Is your job using dsjob -wait command /job control api DSWaitForJob? If yes, what is value of 'Inactivity timeout' in Administrator?
Posted: Mon Jul 21, 2014 1:42 pm
by igorbmartins
This is the IA Log the DataStage director log is very large. If you want I can put here.
IA Job Status
--------------------------------------------------------------------------
| Job Execution Status -> DPVAT_CHASSI77791107 |
| JOB TYPE : com.ascential.investigate.ca.job.BaseProfileJob |
| JOB PROCESSOR : com.ascential.investigate.utils.jobs.osh.PXProcessor |
|------------------------------------------------------------------------|
| Data Stage> ANALYZERPROJECT@SRV2004:31538, credentialMapping=false |
| Scratch Data Source>
iadb@SRV2004.db.cnseg.alog:50000 (DB2) |
| [] pre-process completed (1 sec) |
| [] main-process failed (0 sec) |
| [] post-process failed (0 sec) |
| |
| Job run *FAILURE* in 1440 minute(s) 2 seconds.
[/list]
Posted: Mon Jul 21, 2014 3:04 pm
by chulett
Not necessary. Please check the Inactivity Timeout value as noted.
Posted: Mon Jul 21, 2014 3:15 pm
by PaulVL
Just the error messages in the log would help.
Could be a database connection timeout.
Could be a Head Node to Compute Node timeout...
Could be a Gateway Timeout if there is one between your IA server and the database...
Need to see the error message.
Posted: Mon Jul 21, 2014 3:56 pm
by chulett
Sure... just not the entire log, please.
