Failure During Execution of Operator Logic

pravin1581 · Post by **pravin1581** » Fri Jan 04, 2008 10:29 am

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.

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.

ArndW · Post by **ArndW** » Fri Jan 04, 2008 10:43 am

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...

pravin1581 · Post by **pravin1581** » Fri Jan 04, 2008 12:27 pm

ArndW wrote: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...

I have done the same even if you replace any hardcoded values with the parameters the job fails.

dspxlearn · Post by **dspxlearn** » Fri Jan 04, 2008 12:37 pm

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!!

pravin1581 · Post by **pravin1581** » Fri Jan 04, 2008 1:06 pm

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!!

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 · Post by **dspxlearn** » Fri Jan 04, 2008 1:21 pm

you are right.
Can you check if you are enclosing all the parameters with '#'.
Even your password parameter should be enclosed with '#'.

pravin1581 · Post by **pravin1581** » Fri Jan 04, 2008 1:27 pm

dspxlearn wrote: you are right.
Can you check if you are enclosing all the parameters with '#'.
Even your password parameter should be enclosed with '#'.

All these issues have been double checked !!!

pravin1581 · Post by **pravin1581** » Mon Jan 07, 2008 11:05 am

pravin1581 wrote:
dspxlearn wrote: you are right.
Can you check if you are enclosing all the parameters with '#'.
Even your password parameter should be enclosed with '#'.
All these issues have been double checked !!!

The problem still persists , can any one help me with this.

ray.wurlod · Post by **ray.wurlod** » Mon Jan 07, 2008 11:55 am

Yes. Your support provider. That's one of the reasons you pay maintenance.

reddy.cba · Post by **reddy.cba** » Wed Feb 06, 2008 6:16 pm

remove semicolon from the sql statement..it worked fine for me..

ag_ram · Post by **ag_ram** » Mon Feb 11, 2008 3:38 pm

I faced a similar problem. The round- about way is to define user-defined parameters at the job level and map the same to environment variables in the sequencer. This should work, atleast it did for me.

Aruna Gutti · Post by **Aruna Gutti** » Wed Feb 13, 2008 2:18 pm

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

vivekgadwal · Post by **vivekgadwal** » Wed Feb 13, 2008 3:39 pm

pravin1581 wrote:
ArndW wrote:Are any of the DB2 connection fields (server,user,password) parameters?
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.

Pravin,

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!

shin0066 · Post by **shin0066** » Wed Feb 13, 2008 4:15 pm

I am not sure the Database is cataloged on the ETL server.. Please check it.

shin0066 · Post by **shin0066** » Wed Feb 13, 2008 4:16 pm

I am not sure the Database is cataloged on the ETL server.. Please check it.