Page 1 of 1

Job Parameter : Environment variable as Password

Posted: Wed Aug 16, 2006 7:24 am
by williamswe
Hi All,

I am using an environment variable (Oracle login password) as a job parameter.

I can run the job successfully using it, but when i tri to do "view data" i can't and get this error...


Error executing View Data command:

Bad dboption list. Failed on Expected value for property "password"

i wonder why...

thx in advance

Posted: Wed Aug 16, 2006 7:48 am
by chulett
That's just The Way It Works when using ENV variables like that. Job runs but you can't view data without putting a 'real' value in there.

Re: Job Parameter : Environment variable as Password

Posted: Wed Aug 16, 2006 9:30 am
by prabu
williamswe wrote:Hi All,

I am using an environment variable (Oracle login password) as a job parameter.

I can run the job successfully using it, but when i tri to do "view data" i can't and get this error...


Error executing View Data command:

Bad dboption list. Failed on Expected value for property "password"

i wonder why...

thx in advance
Did you feed the correct password , when prompted by "view data".

Posted: Wed Aug 16, 2006 10:04 am
by Krazykoolrohit
when you do a view data. dont use variables. use hard coding when prompted for the parameter values.

Get a patch to fix it!

Posted: Fri Aug 18, 2006 6:45 pm
by pneumalin
This is a knon bug that has been fixed in latest patch for 7.5.1.A. Contact IBM for the patch download..

Posted: Mon Aug 21, 2006 1:14 am
by williamswe
Thx a lot for the info.

And any idea on how much downtime do we need to apply the patch?

Posted: Mon Aug 21, 2006 4:29 am
by rameshrr3
Im using 7.5.1 A and seems the bug has been fixed! i can use $PROJDEF as default value for password and view data seems to work without much complaints

Posted: Mon Aug 21, 2006 11:58 pm
by pneumalin
That's great they put the fix in 7.5.1.A. I just heard IBM has come out with 7.5.2(Not official, but is 7.5.1.A above), this is recommended if you want this fix since this version contains a lot more fixes. Ask for your IBM representatives. As per my experience, to apply the patches doesn't take too long( Maybe an hour). Be careful on your permission setup of your project, since I noticed the upgrade process modify the permission of some project files and caused some jobs run problem during my previous patching process...