That's exactly what's weird. The DRS stage for connecting to SQL server from Unix, always uses ODBC. It does not fail. Also, other projects ODBC stages do not fail when this occurs. That is, this problem when it occurs does not span the Datastage server. It only occurs for a project at a time.keshav0307 wrote:Does DRS stage use ODBC?? or the native client connection??
Black Magic
Moderators: chulett, rschirm, roy
-
Ultramundane
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
Can you do a quick test to isolate the issue when the job is hanging ( for what ever reason). 1. Identify the processess associated with the job 2. Capture the memory usage and disc usage stats for untill the job stops and a minute after that. 3. Check the number of semophores opened. Gather this information this will help isolate the issue.
M.T.Anwer
The day the child realizes that all adults are imperfect he becomes an adolescent;
the day he forgives them, he becomes an adult; the day he forgives himself, he becomes wise.
-Aiden Nowlan
The day the child realizes that all adults are imperfect he becomes an adolescent;
the day he forgives them, he becomes an adult; the day he forgives himself, he becomes wise.
-Aiden Nowlan
-
Ultramundane
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
The jobs abort immediately once this starts.MTA wrote:Can you do a quick test to isolate the issue when the job is hanging ( for what ever reason). 1. Identify the processess associated with the job 2. Capture the memory usage and disc usage stats for untill the job stops and a minute after that. 3. Check the number of semophores opened. Gather this information this will help isolate the issue.
-
Ultramundane
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
The jobs abort immediately once this starts.MTA wrote:Can you do a quick test to isolate the issue when the job is hanging ( for what ever reason). 1. Identify the processess associated with the job 2. Capture the memory usage and disc usage stats for untill the job stops and a minute after that. 3. Check the number of semophores opened. Gather this information this will help isolate the issue.