Job run *FAILURE* in 1440 minute(s) 2 seconds

This forum contains ProfileStage posts and now focuses at newer versions Infosphere Information Analyzer.

Moderators: chulett, rschirm

Post Reply
igorbmartins
Participant
Posts: 161
Joined: Mon Mar 17, 2008 10:33 am

Job run *FAILURE* in 1440 minute(s) 2 seconds

Post 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
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

What does the Director log error message say?
rkashyap
Premium Member
Premium Member
Posts: 532
Joined: Fri Dec 02, 2011 12:02 pm
Location: Richmond VA

Post by rkashyap »

Is your job using dsjob -wait command /job control api DSWaitForJob? If yes, what is value of 'Inactivity timeout' in Administrator?
igorbmartins
Participant
Posts: 161
Joined: Mon Mar 17, 2008 10:33 am

Post 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]
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not necessary. Please check the Inactivity Timeout value as noted.
-craig

"You can never have too many knives" -- Logan Nine Fingers
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post 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.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Sure... just not the entire log, please. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply