Greetings,
Im running into issues with using Oracle with Oracle OCI stages
1. Some of my table access is through Public synonyms from other systems, I could pull the metadata for these tables through Manager. Should this work?
2. I can successfully run jobs with the OCI stage info hardcoded, specifically Database Source name, User Id and Password. Id prefer to use job parameters as I may have several jobs within a batch. With job parameters however, the job will compile but will not resolve the database connection. If I HC the source name, which may be ok, I cant resolve the user id/password with parameters. I know the parameter value are correct, because I cut/paste then into the exection
Any help would be appreciated. By the way, Im using DS 4.0 on a Sun/Solaris server. Thanks, Bob
Oracle OCI questions
Bob,
You may have already done this test.
But if the parameter name is incorrectly spelt the ODBC/OCI stage (ie it does not match the spelling of the paramters in the in the Job Properties) then is will use the inocooect spelling as the parameter.
To test that it is set up correctly try View on the ODBC/OCI stage, it will then prompt you for every parameter used by that stage.
I have had no problems using Public synonyms they have always performed as expected.
Hope it helps.
Jack
----- Original Message -----
From:
To:
Sent: Saturday, June 23, 2001 1:22 AM
Subject: Oracle OCI questions
> Greetings,
>
> Im running into issues with using Oracle with Oracle OCI stages
> 1. Some of my table access is through Public synonyms from other
> systems, I could pull the metadata for these tables through Manager.
> Should this work?
> 2. I can successfully run jobs with the OCI stage info
> hardcoded, specifically Database Source name, User Id and Password.
> Id prefer to
use
> job parameters as I may have several jobs within a batch. With job
> parameters however, the job will compile but will not resolve the
> database connection. If I HC the source name, which may be ok, I
> cant resolve the user id/password with parameters. I know the
> parameter value are correct, because I cut/paste then into the
> exection
>
> Any help would be appreciated. By the way, Im using DS 4.0 on a
> Sun/Solaris server. Thanks, Bob
>
You may have already done this test.
But if the parameter name is incorrectly spelt the ODBC/OCI stage (ie it does not match the spelling of the paramters in the in the Job Properties) then is will use the inocooect spelling as the parameter.
To test that it is set up correctly try View on the ODBC/OCI stage, it will then prompt you for every parameter used by that stage.
I have had no problems using Public synonyms they have always performed as expected.
Hope it helps.
Jack
----- Original Message -----
From:
To:
Sent: Saturday, June 23, 2001 1:22 AM
Subject: Oracle OCI questions
> Greetings,
>
> Im running into issues with using Oracle with Oracle OCI stages
> 1. Some of my table access is through Public synonyms from other
> systems, I could pull the metadata for these tables through Manager.
> Should this work?
> 2. I can successfully run jobs with the OCI stage info
> hardcoded, specifically Database Source name, User Id and Password.
> Id prefer to
use
> job parameters as I may have several jobs within a batch. With job
> parameters however, the job will compile but will not resolve the
> database connection. If I HC the source name, which may be ok, I
> cant resolve the user id/password with parameters. I know the
> parameter value are correct, because I cut/paste then into the
> exection
>
> Any help would be appreciated. By the way, Im using DS 4.0 on a
> Sun/Solaris server. Thanks, Bob
>