Unable to run through Sequencer
Moderators: chulett, rschirm, roy
Unable to run through Sequencer
Hi
can any one please help me on below issue
when i trigger job directly ,it's running fine with out any warning
if i trigger through sequencer the job is getting aborted due to below issue .
Upd_STG_MFAINVNMP: DB2 function SQLFetch failed: SQLSTATE = HY000: Native Error Code = -1,042: Msg = [IBM][CLI Driver][DB2/AIX64] SQL1042C An unexpected system error occurred. SQLSTATE=58004 (CC_DB2Connection::queryServerHostName, file CC_DB2Connection.cpp, line 2,937)
Thanks in advance
can any one please help me on below issue
when i trigger job directly ,it's running fine with out any warning
if i trigger through sequencer the job is getting aborted due to below issue .
Upd_STG_MFAINVNMP: DB2 function SQLFetch failed: SQLSTATE = HY000: Native Error Code = -1,042: Msg = [IBM][CLI Driver][DB2/AIX64] SQL1042C An unexpected system error occurred. SQLSTATE=58004 (CC_DB2Connection::queryServerHostName, file CC_DB2Connection.cpp, line 2,937)
Thanks in advance
vijay
INDIA
INDIA
hi
we are passing one parameter which contains ( DB connection ) through sequencer .
FYI the same job is running fine in UAT and prod through sequencer
when we passed the same parameter the jobs are running fine
and now only i observed the same issue is coming for all jobs in dev environment
Thanks in advance
we are passing one parameter which contains ( DB connection ) through sequencer .
FYI the same job is running fine in UAT and prod through sequencer
when we passed the same parameter the jobs are running fine
and now only i observed the same issue is coming for all jobs in dev environment
Thanks in advance
vijay
INDIA
INDIA
That's an important piece of information. Does it matter what DB2 instance you try to connect to? If it doesn't then I'd suspect that something has gone awry with your DB2 configuration on the ETL server and I'd involve your DBA to help track it down.v_bhaskar wrote:and now only i observed the same issue is coming for all jobs in dev environment
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
In your job, in the before job sub routine - use Execsh and try to echo the parameter value. Verify if the value has any spaces, extra characters etc.
It could be possible that the connection information is being passed incorrectly by the sequence to the job.
Also, by connection information - Is it a username, password or server name?
If its a password, then verify if there are any special characters used. There could be a possibility that the special character is leading to problem.
It could be possible that the connection information is being passed incorrectly by the sequence to the job.
Also, by connection information - Is it a username, password or server name?
If its a password, then verify if there are any special characters used. There could be a possibility that the special character is leading to problem.
HI
i had checked below all things in my job
before job sub routine - use Execsh and try to echo the parameter value. Verify if the value has any spaces, extra characters etc.
but it's help less
onething i observed is when i tried to do some changes ( minor will effect any logic or code ) and compilation in sequencer its working fine.
my project is totally dependent on sequencer it's nearly 100+ is there i cannot go for the above procedure for all same
the same job if i import in UAT it working fine ( earlier also in dev all jobs are worked fine with out any issues) suddenly what happend i am not getting
in one sequencer i pluged nearly 10-15 jobs apart 10-15 only 2-3 jobs are getting aborted due to that issue
i had checked below all things in my job
before job sub routine - use Execsh and try to echo the parameter value. Verify if the value has any spaces, extra characters etc.
but it's help less
onething i observed is when i tried to do some changes ( minor will effect any logic or code ) and compilation in sequencer its working fine.
my project is totally dependent on sequencer it's nearly 100+ is there i cannot go for the above procedure for all same
the same job if i import in UAT it working fine ( earlier also in dev all jobs are worked fine with out any issues) suddenly what happend i am not getting
in one sequencer i pluged nearly 10-15 jobs apart 10-15 only 2-3 jobs are getting aborted due to that issue
vijay
INDIA
INDIA
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I don't really see this as being a parameter issue. Any searches for those two SQL error codes say to "look in the db2diag.log file" to see the actual problem. One such example here where the problem was an inability to allocate memory.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers