Lookup error
Moderators: chulett, rschirm, roy
Lookup error
We are getting the following erorr when trying to lookup on a oracle stage in Datastage 7.5 .Error
Fetch failed for: GenericStmt_3
>query is: SELECT banner FROM V$VERSION
>sqlcode is: -3106
>esql complaint: ORA-03106: fatal two-task communication protocol error
Fetch failed for: GenericStmt_3
>query is: SELECT banner FROM V$VERSION
>sqlcode is: -3106
>esql complaint: ORA-03106: fatal two-task communication protocol error
Sree
srekant,
what happens if you try the same query from an ODBC stage to the database? Is this a custom statement - how does it execute in SQLPLUS?
Is it a problem only in the view or only for this view?
what happens if you try the same query from an ODBC stage to the database? Is this a custom statement - how does it execute in SQLPLUS?
Is it a problem only in the view or only for this view?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Lookup
Since i am working in DataStage 7.5 parallel jobs there is only Oracle Enterprise stage.I am able to import the metadata of the oracle table and also view the data from Import MetaData window.
When i execute the query fom Sqlplus it is working finw.
Above error i am getting when trying to view data from Oracle_Enterprise stage.
When i execute the query fom Sqlplus it is working finw.
Above error i am getting when trying to view data from Oracle_Enterprise stage.
Sree
srekant,
you would be surprised at what you can do from PX (take a look at the Dynamic RDBMS stage) .
(sorry, didn't read all of your post)
What is your query statement that worked from SQLPlus? If you make a non-lookup stage with the same SQL syntax does it do a VIEW-DATA correctly?
you would be surprised at what you can do from PX (take a look at the Dynamic RDBMS stage) .
(sorry, didn't read all of your post)
What is your query statement that worked from SQLPlus? If you make a non-lookup stage with the same SQL syntax does it do a VIEW-DATA correctly?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
A quick look on google shows that this error is normally not issued and the caller should contact Oracle support
Can you change your job to do a select from the lookup table, write the result to a lookup stage and then do a lookup on that stage? It is an efficient method of doing it and might either solve or at least help narrow down the problem.
Can you change your job to do a select from the lookup table, write the result to a lookup stage and then do a lookup on that stage? It is an efficient method of doing it and might either solve or at least help narrow down the problem.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
1. What is your misbehaving SQL
2. Is this the only table with a problem
2. Is this the only table with a problem
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Have you chosen the automatic SQL or user defined SQL? And what about th 2nd half of the previous question - is this a problem only with this query or does it occur with other tables?
If you create a simple job with ONLY this query and going to a peek stage is the error the same? What happens if you fully qualify your columns with Schema information? Does a "SELECT COUNT(*) FROM DUAL;" return a value from the same stage but with custom SQL?
If you create a simple job with ONLY this query and going to a peek stage is the error the same? What happens if you fully qualify your columns with Schema information? Does a "SELECT COUNT(*) FROM DUAL;" return a value from the same stage but with custom SQL?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom