Page 1 of 1
Posted: Wed Jan 14, 2009 11:10 pm
by ray.wurlod
"Parameter not resolvable" probably means that you have used parameters for these three properties but, for whatever reason, the values supplied for the parameters (check in the job log) could not resolve into anything that the Oracle connection could use.
Posted: Wed Jan 14, 2009 11:53 pm
by enigmatic28
I checked all the logs of the job and did not found the DSCAPIOP_* parameters.
Just last questions before i mark this thread as resolved, can this kind of problem originate if the job was created using 7.5 rather than 7.5x2, and what is the difference using the compiler of 7.5 against 7.5x2?
thank you very much...
Posted: Thu Jan 15, 2009 6:19 am
by throbinson
Drop the DSCAPIOP_ part. Are the parameters $ORADB, $OraDBUserID
and $OraDBPswd defined in the job and as Project level env variables in the 7.5.2 project?
Posted: Thu Jan 22, 2009 4:28 am
by enigmatic28
Are the parameters $ORADB, $OraDBUserID
and $OraDBPswd defined in the job and as Project level env variables in the 7.5.2 project?
yes they are...
Posted: Thu Jan 22, 2009 2:42 pm
by ray.wurlod
"Parameter not resolvable" probably means that you have used parameters for these three properties (ignoring the DSCAPIOP_ part of the name) but, for whatever reason, the values supplied for the parameters (check in the job log) could not resolve into anything that the Oracle connection could use.
Posted: Fri Jan 23, 2009 3:48 am
by LenGreenwood
If this is a parallel job and it calls a shared container, it may be a compiler bug. There is an APAR # JR29478 that resolves a very similar error message where "DSCAPIOP_ " appears as part of the param name.