Oracle Connector issue in migration

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
kamalshil
Participant
Posts: 179
Joined: Mon Jun 23, 2008 1:19 am

Oracle Connector issue in migration

Post by kamalshil »

Hi,
We are developing the jobs in a project using the oracle connector stage in 8.5. And associating it with the Database connection set.

It works fine in the development environment.
But when we migrate it to another environment or new project we compile & run.
While running we are getting the below fatal error.
Read_NS: The variable nContext has value 0 which is not valid in the current context. (CC_OraRecordDataSetProducer::init, file CC_OraRecordDataSetProducer.cpp, line 343)

The workaround for this issue we found its working but we cannot do that for all the environments where we deploy the code.
Please suggest what can be done to try to avoid this issue.

Workaround:
1. Open the connector stage
2. click on test connection.
3. Click on Ok
4. Save the job then force compile.

And it runs fine.
felixyong
Participant
Posts: 35
Joined: Tue Jul 22, 2003 7:24 pm
Location: Australia

Re: Oracle Connector issue in migration

Post by felixyong »

Hi

Did you check with IBM Support on any patches available?
Regards
Felix
BI-RMA
Premium Member
Premium Member
Posts: 463
Joined: Sun Nov 01, 2009 3:55 pm
Location: Hamburg

Post by BI-RMA »

I would prefer not to compile the job in the production-environment at all. Use parameter-sets and attached value files to run the precompiled job with different runtime-credentials in another environment.

We haven't even got a compiler on the production-environment in our current project!
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
Post Reply