I am not able to connect to a DB2 database from datastage.Its giving the error message like dsadm Username/Password is expired.But then when i was connectiing to the database using the same user id and password ,its working fine. Please help me on this.
Could it be that you are connecting to different databases in DataStage and from the command line? That is the simplest explanation. Could you also post the exact error message, please?
Are you using the same user id to connect to database via datastage and command line. This is a simple permissions issue where you either provided a wrong user name or password or both or the password got locked.
kris007 wrote:Are you using the same user id to connect to database via datastage and command line. This is a simple permissions issue where you either provided a wrong user name or password or both or the password got locked.
Yes. I have used the same username and password in datastage and command line.
Just to test that you are actually using the userid/password combination that you think, take another userid/password and use those as parameters to the database job. Is the error message the same or is it working?
That should tell you that the entries you are putting into your job aren't the ones that DB2 is getting.
How are you declaring the userid/password in the job?
The Datastage server is shared with Systest environment and Dev environment. but each environments having its own databases. there is no problem to connect the systest environment. I have faced the issue in dev environment.
Assuming your password is encrypted in your job properties, are you typing in your password there or are you referring it to an environment variable. Also, what DB2 stage are you using? API or Enterprise? Are you setting your password within the DB2 stage using #parametername# #$ENV_VARIABLE_NAME# or are you just typing in the password for dsadm? What exactly are you providing within the DB2 Stage?
prasanna_anbu wrote:The Datastage server is shared with Systest environment and Dev environment. but each environments having its own databases. there is no problem to connect the systest environment. I have faced the issue in dev environment.
Are you getting the same issue when you are trying to "View" data from DStage job by putting the same username/password
I have used the enterprise stage and I passed the credentials as parameterset values. The Password is hardcode in the parameterset against the database name. I am getting the same error when I tried to viewdata.
What happens if you test it without hardcoded parameter values, perhaps make a copy and manually type in the values - does it work then? If yes, then you can start to track back the error.
</a>