DTS.Pipeline: Validation phase is beginning, but never stop
Dear All,
I face the some issues, and I totally not idea what happened on this, please help.
I have one SSIS is to export the data from database, and the table size was quite large. When it run on UAT environment (Windows 2003 32 bit) not problem, but not sure is it because the data was not large compare with Production. When move to production,
which the OS is Windows 2003 64 bit, the process was hang there, no error, so I not sure is still running back end check up or lack.
And this is the process screen been capture
What step can i check? I try to capture the log when run the SSIS, but also still show the Pre-Execute in 77%, not update in the log anymore.
Judy
March 7th, 2012 5:58am
fas you mentioned that your machine is 32bit and the production is 64, and i see that you are using EXCEL in your package, first question is how are you calling calling your package? is it through a SQL Job ? and if so are you using the DTEXEC 32bit?
if so please check this
link and look for what it says about dtexec 32 bit Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 8:29am
It's also quite a bit more useful (IMHO) to look at the Output Window than the Progress Window. The Output Window shows messages in chronological order... what are the last few messages?
Talk to me now on
March 7th, 2012 8:44am
fas you mentioned that your machine is 32bit and the production is 64, and i see that you are using EXCEL in your package, first question is how are you calling calling your package? is it through a SQL Job ? and if so are you using the DTEXEC 32bit?
if so please check this
link and look for what it says about dtexec 32 bit
Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
Yes, i use DTEXEC 32bit to call at SQL Job, I not think the calling process have problem, else the package will totally cannot start, right?
And, the screen I capture is I manually run at Visual StudioJudy
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 9:09am
As todd suggest it would be good to see the last few lines as well, though as a sugegstion you can try to quell your thoughts about the data, by keeping all the three Data Flow tasks in there own DFT containers each executing in parallel and let us know
your findings.Abhinav
March 7th, 2012 9:10am
It's also quite a bit more useful (IMHO) to look at the Output Window than the Progress Window. The Output Window shows messages in chronological order... what are the last few messages?
Talk to me now on
The output window only show this
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Data Flow Task, DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, DTS.Pipeline: Pre-Execute phase is beginning.
Judy
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 11:01am
As todd suggest it would be good to see the last few lines as well, though as a sugegstion you can try to quell your thoughts about the data, by keeping all the three Data Flow tasks in there own DFT containers each executing in parallel and let us know
your findings.
Abhinav
I try to split the 3 import process to 3 data flow, and it work!! What is the logic inside? Can anyone told meJudy
March 7th, 2012 11:43am
As todd suggest it would be good to see the last few lines as well, though as a sugegstion you can try to quell your thoughts about the data, by keeping all the three Data Flow tasks in there own DFT containers each executing in parallel and let us know
your findings.
Abhinav
I try to split the 3 import process to 3 data flow, and it work!! What is the logic inside? Can anyone told me
Judy
This will give you an idea why is it so
http://www.sql-server-performance.com/2009/ssis-an-inside-view-part-4/
yOu can think ot as that individual threads are generated when you have 3 DFTAbhinav
Free Windows Admin Tool Kit Click here and download it now
March 8th, 2012 10:13am
If that's the case, there may have been some dependencies between your sources and destinations that were causing deadlocks? Very hard to tell without looking at the package and metadata...
Talk to me now on
April 8th, 2012 3:27pm
If that's the case, there may have been some dependencies between your sources and destinations that were causing deadlocks? Very hard to tell without looking at the package and metadata...
Talk to me now on
The source is the store procedure, and all the store procedure will extract the data from different table and then import to one temporary table. The the destination are the same excel file, just different sheet, is it will be the reason? Because after I
split all the extraction to different data flow task, although I have 11 sheets, the package was successful completed.Judy
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2012 9:23pm
It's very odd that it behaves this way, but it does lend more evidence to the best practice of placing only one flow into each Data Flow Task...
Talk to me now on
April 8th, 2012 11:10pm
As todd suggest it would be good to see the last few lines as well, though as a sugegstion you can try to quell your thoughts about the data, by keeping all the three Data Flow tasks in there own DFT containers each executing in parallel and let us know
your findings.
Abhinav
I try to split the 3 import process to 3 data flow, and it work!! What is the logic inside? Can anyone told me
Judy
This will give you an idea why is it so
http://www.sql-server-performance.com/2009/ssis-an-inside-view-part-4/
yOu can think ot as that individual threads are generated when you have 3 DFTAbhinav
Free Windows Admin Tool Kit Click here and download it now
April 9th, 2012 2:38am