parameter problem
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 142
- Joined: Wed Mar 24, 2004 10:51 am
- Location: Brazil
parameter problem
I'm having some problems with parameters.
I constructed some jobs with parameters and suddenly they do not work.
I created parameters for date source name, user and password, in DB2 stage.
And give me an error message saying that password or user is wrong.
If I take off the parameter and put fixed value, the job work.
When I make the the opposite (take off the fixed values and put the parameters) the job works.
But in some days, suddenly they do not work more and I have to do everything again.
Somebody already have this problem?
To clarify it follows the order of that it happens.
1 - the job(with parameter) aborted saying that password or user is wrong
2 - I take off the parameters and put fixed values
3 - run and execute the job(without parameter) - it work very well
4 - I take off the fixed values and put parameters
5 - run and execute the job (with parameter) - it work very well
6 - Some days, suddenly they do not work more and I have to do everything again.
Fernando Martins
I constructed some jobs with parameters and suddenly they do not work.
I created parameters for date source name, user and password, in DB2 stage.
And give me an error message saying that password or user is wrong.
If I take off the parameter and put fixed value, the job work.
When I make the the opposite (take off the fixed values and put the parameters) the job works.
But in some days, suddenly they do not work more and I have to do everything again.
Somebody already have this problem?
To clarify it follows the order of that it happens.
1 - the job(with parameter) aborted saying that password or user is wrong
2 - I take off the parameters and put fixed values
3 - run and execute the job(without parameter) - it work very well
4 - I take off the fixed values and put parameters
5 - run and execute the job (with parameter) - it work very well
6 - Some days, suddenly they do not work more and I have to do everything again.
Fernando Martins
Hi,
I had issues like this only when someone changed the job, never when it was untouched.
Are you sure no one touched the job?
the only other times it happend was when they actually changed the passwords.
Good Luck,
I had issues like this only when someone changed the job, never when it was untouched.
Are you sure no one touched the job?
the only other times it happend was when they actually changed the passwords.
Good Luck,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
-
- Participant
- Posts: 142
- Joined: Wed Mar 24, 2004 10:51 am
- Location: Brazil
parameter problem
Nobody touched the job and nobody changed the password.
Fernando Martins
Fernando Martins
Hi,
then i think you should report this to your support provider
then i think you should report this to your support provider
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Yeah, I've run into that one before. The defaults you save in Designer are one way, so everything looks fine in design time, but someone's changed them in Director (usually just the encrypted password field), so it fails to run with the bad login. It seems to me like changing the defaults in Designer only carries over to Director if a recompile is done. I may be wrong on that, but my experience with the default values leads me to that conclusion.chulett wrote:Did anyone go in and change the 'defaults' via the Director? This has been known to case the problem you are seeing, even if you don't touch the password field.
-
- Participant
- Posts: 142
- Joined: Wed Mar 24, 2004 10:51 am
- Location: Brazil
parameter problem
Nobody changed the 'defaults' via the Director.
The process was running every day and sunddely aborted.
The process was running every day and sunddely aborted.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
-
- Participant
- Posts: 142
- Joined: Wed Mar 24, 2004 10:51 am
- Location: Brazil
parameter problem
well, we did a restart in the Data Stage Server and the problem, not exist more.
somedoby knows of how much in how much time it is good for making a restart in the server?
Fernando Martins
somedoby knows of how much in how much time it is good for making a restart in the server?
Fernando Martins
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Possible. His English is still better than my non-existent Portuguese!
Theoretically, you should only need to restart DataStage on UNIX when you change something in dsenv or uvconfig, provided you let dsdlockd run. Of course, DataStage is restarted for an upgrade and if ever UNIX is rebooted.
Theoretically, you should only need to restart DataStage on UNIX when you change something in dsenv or uvconfig, provided you let dsdlockd run. Of course, DataStage is restarted for an upgrade and if ever UNIX is rebooted.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: