Yes they are inserted with the Insert Job parameter helper, everything has been double checked, the job was developed again from the scratch but still the error persists.ray.wurlod wrote:Do you add them to the stage using the parameter helper tool (Insert Job Parameter)? What do they look like when loaded into properties? Is the generated connection string consistent with what you've put into the individual properties?
Are all the required "#" characters in place? You did not answer this following my earlier post.
Failure During Execution of Operator Logic
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 497
- Joined: Sun Dec 17, 2006 11:52 pm
- Location: Kolkata
- Contact:
Can you replace the 3 parameters 1 by 1 to see which one is causing the error? My guess would be something to do with the password...
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 497
- Joined: Sun Dec 17, 2006 11:52 pm
- Location: Kolkata
- Contact:
-
- Premium Member
- Posts: 497
- Joined: Sun Dec 17, 2006 11:52 pm
- Location: Kolkata
- Contact:
If it had been the problem with the user then it should persist when we replace the parameters with the hardcoded values. If we use the hardcoded vales then the job runs fine.dspxlearn wrote:pravin1581,
Check the connectivity to DB2 from DS for your user. I guess it is not the problem with the pasword. If it was the problem with the password, the error would be different and moreover, your password would have been locked up by now!!
-
- Premium Member
- Posts: 497
- Joined: Sun Dec 17, 2006 11:52 pm
- Location: Kolkata
- Contact:
-
- Premium Member
- Posts: 497
- Joined: Sun Dec 17, 2006 11:52 pm
- Location: Kolkata
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 145
- Joined: Fri Sep 21, 2007 9:35 am
- Location: Boston
I got the exact same error in version 8.0.1 which was fixed with the install of patch_118170v3.
But your version is not 8.x right ?
This was the error I used to receive when db2 parameters are not hardcoded in the job:
Fatal Error: Fatal: [IBM][CLI Driver] CLI0124E
Invalid argument value. SQLSTATE=HY009
DSTAGE-DB2CLI-0005`:`Unable to connect to DB2 server
But your version is not 8.x right ?
This was the error I used to receive when db2 parameters are not hardcoded in the job:
Fatal Error: Fatal: [IBM][CLI Driver] CLI0124E
Invalid argument value. SQLSTATE=HY009
DSTAGE-DB2CLI-0005`:`Unable to connect to DB2 server
-
- Premium Member
- Posts: 457
- Joined: Tue Sep 25, 2007 4:05 pm
Pravin,pravin1581 wrote:Yes they were all env parameters and when we replace them with the actual values in all the individual stages , then the job runs fine, but we need to declare all the connection details through env parameters as per requirement and standard practice followed.ArndW wrote:Are any of the DB2 connection fields (server,user,password) parameters?
You say you are using the environment variables isn't it! Are you checking for '$' sign in front of the variable? If that is fine...then I do not see why this is going awry!
Vivek Gadwal
Experience is what you get when you didn't get what you wanted
Experience is what you get when you didn't get what you wanted