i got this message
DSD.BCIOpenR call to SQLExecDirect failed.
what is the expected resson , what i have to do
thanks
DSD.BCIOpenR call to SQLExecDirect failed.
Moderators: chulett, rschirm, roy
dsonly - welcome to DSXChange.
In order to help answer your question you should add a bit more information to your post. Even though some can be read from the error message, you should tell us what stage you are using and what you are doing in it. Does the error happen on view data or when running? Do you have other jobs which use this stage successfully?
In order to help answer your question you should add a bit more information to your post. Even though some can be read from the error message, you should tell us what stage you are using and what you are doing in it. Does the error happen on view data or when running? Do you have other jobs which use this stage successfully?
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
BCI.OpenR suggests ODBC or UniVerse stage. A problem is occurring when trying to "open" (establish a connection) in order to perform a SELECT (or execute a stored procedure that returns rows).
Check that the authentication information is correct. The easiest way to do this is to open the stage and click GetSQLInfo on the stage properties - if this does not generate an error, then connectivity is correct. You then need to look at the job log to get more information. Post full details of error message(s) here - use copy/paste so that it's accurate.
Check that the authentication information is correct. The easiest way to do this is to open the stage and click GetSQLInfo on the stage properties - if this does not generate an error, then connectivity is correct. You then need to look at the job log to get more information. Post full details of error message(s) here - use copy/paste so that it's accurate.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
</a>