Hi,
We have the jobs existing Datastage7.1.
Now we are using DS7.5. We have to modify the target table structure as the database has been upgraded.
We have old environment variables set for the database connection.
We changed the job parameter to point to the new environment variables as part of upgrade
The new variables are initialised in the Administrator.
But when we run the job, it is throwing the following error.
FDM84_89_LEDGER_F00_HF..SQ_PS_ETL_JOB_CTL: Unknown client library - #$SRCDBType#
#$SRCDBType# is the old envronment variable for the source where as #$TGLB_DBTYPE# is the new environment variable.
Pls help me
Environment variables
Moderators: chulett, rschirm, roy
Environment variables
Thanks,
Madhavi
Madhavi
-
- Participant
- Posts: 437
- Joined: Fri Oct 21, 2005 10:00 pm
Re: Environment variables
"We changed the job parameter to point to the new environment variables as part of upgrade"
Did you actually delete the old job parameter and import the new environmental variable?
Is there a sequence involved in this that could still be referencing the old environmental variable. Did all of the jobs and sequences involved get recompiled, you cannot change a job without recompiling the sequence associated with it.
You might want to post the OSH so we could more easily see what's involved in your job.
Did you actually delete the old job parameter and import the new environmental variable?
Is there a sequence involved in this that could still be referencing the old environmental variable. Did all of the jobs and sequences involved get recompiled, you cannot change a job without recompiling the sequence associated with it.
You might want to post the OSH so we could more easily see what's involved in your job.
Keith Williams
keith@peacefieldinc.com
keith@peacefieldinc.com
Re: Environment variables
First clarify me whether we can set up the environment variables in the dsenv file at Unix machine??kwwilliams wrote:"We changed the job parameter to point to the new environment variables as part of upgrade"
Did you actually delete the old job parameter and import the new environmental variable?
Is there a sequence involved in this that could still be referencing the old environmental variable. Did all of the jobs and sequences involved get recompiled, you cannot change a job without recompiling the sequence associated with it.
You might want to post the OSH so we could more easily see what's involved in your job.
Because the old environment variables have not been defined in the administrator.
So we created new variables for our project and added in the jobs.
We restarted the Unix server. But the new values are not getting reflected in the jobs.
Thanks,
Madhavi
Madhavi
-
- Participant
- Posts: 437
- Joined: Fri Oct 21, 2005 10:00 pm
Re: Environment variables
Do your jobs reference the environmental variable directly in any way? If they do, you would need to change the job and recompile the job. It sounds like you did not set up the environmental variable, but your job still references these variables. Go to your job and look at the properties. See if you see the $SRCDBType as one of the variables. My guess is that you will.
Keith Williams
keith@peacefieldinc.com
keith@peacefieldinc.com
Re: Environment variables
You have changed the job parameters, but did you also make this change in the stage properties of Source and target database stages ? If you didn't, then they would still be referncing old parameters, which obviously can't be found.pmadhavi wrote:Hi,
We have the jobs existing Datastage7.1.
Now we are using DS7.5. We have to modify the target table structure as the database has been upgraded.
We have old environment variables set for the database connection.
We changed the job parameter to point to the new environment variables as part of upgrade
The new variables are initialised in the Administrator.
But when we run the job, it is throwing the following error.
FDM84_89_LEDGER_F00_HF..SQ_PS_ETL_JOB_CTL: Unknown client library - #$SRCDBType#
#$SRCDBType# is the old envronment variable for the source where as #$TGLB_DBTYPE# is the new environment variable.
Pls help me