This discussion is archived
4 Replies Latest reply: Mar 20, 2013 1:43 AM by Madasamy Murugaboobathi RSS

DAC Failes in between with "SEVERE: DANGER:  We will hang..." Error

Madasamy Murugaboobathi Newbie
Currently Being Moderated
Hi,

We have around 150 tasks in our ETL which kicks off every night. today , there was a stuck up in the mid of ETL run and we had to run it manually again.

When i checked the nohup.out in the DAC Folder, the following were the log that i could find as the reason for the stuck up. Please let me know your view points, if you have any on this.

Giving the next server number: 1(Repository_Prod)

*8566 SEVERE Thu Mar 07 02:41:42 GMT+02:00 2013 DANGER: We will hang...*

Mar 7, 2013 2:41:42 AM null null
SEVERE: DANGER:  We will hang...
Mar 7, 2013 2:41:42 AM com.siebel.etl.engine.core.SessionHandler notifySessionHandlerOfCompletion
SEVERE: Load into Quote Fact 37 is waiting on the following ..
*(Task Name, Overall Status, Number of Tasks to notify.)*
Mar 7, 2013 2:41:42 AM com.siebel.etl.engine.core.SessionHandler notifySessionHandlerOfCompletion
SEVERE:         Mark rows as changed for S_ORDERITEM because of changes in Auxiliary Tables:Completed:0
Mar 7, 2013 2:41:42 AM com.siebel.etl.engine.core.SessionHandler notifySessionHandlerOfCompletion
SEVERE:         TASK_GROUP_Load_PositionDimension:Queued:6
*8567 SEVERE Thu Mar 07 02:41:42 GMT+02:00 2013 Load into Quote Fact 37 is waiting on the following ..*
*(Task Name, Overall Status, Number of Tasks to notify.)*

Mar 7, 2013 2:41:42 AM com.siebel.etl.engine.core.SessionHandler notifySessionHandlerOfCompletion
SEVERE:         SIL_EmployeeDimension:Queued:14
*8568 SEVERE Thu Mar 07 02:41:42 GMT+02:00 2013 Mark rows as changed for S_ORDERITEM because of changes in Auxiliary Tables:Completed:0*


Thanks,
Madasamy M.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points