Page 1 of 1

Unable to view data in DATASTAGE

Posted: Tue Sep 20, 2005 11:35 am
by bobthebuilder
Hello,

The following was the ODBC set up for Oracle on the DS Server

[e1dev]

Driver=/home/dsadm/Ascential/DataStage/branded_odbc/lib/VMora20.sl

Description=DataDirect Oracle Wire Protocol

ApplicationUsingThreads=1

ArraySize=60000

CachedCursorLimit=32

CachedDescLimit=0

CatalogIncludesSynonyms=1

CatalogOptions=0

DefaultLongDataBuffLen=1024

DescribeAtPrepare=0

EnableDescribeParam=0

EnableNcharSupport=0

EnableScrollableCursors=1

EnableStaticCursorsForLongData=0

EnableTimestampWithTimeZone=0

HostName=erpdvd01

LocalTimeZoneOffset=

LockTimeOut=-1

LogonID=ivgnro

Password=reado

PortNumber=1521

ProcedureRetResults=0

SID=e1dvd

UseCurrentSchema=1

----------------------------------------------------------------------

I tried viewing data both at the manager and the ODBC Stage
for a table. But met with the same error

Test2..ODBC_0.DSLink3: DSD.BCIOpenR call to SQLExecDirect failed.
Statement was:SELECT CRPCTL.F00021.NLKCO, CRPCTL.F00021.NLDCT, CRPCTL.F00021.NLCTRY, CRPCTL.F00021.NLFY, CRPCTL.F00021.NLSMAS, CRPCTL.F00021.NLN001, CRPCTL.F00021.NLAUR, CRPCTL.F00021.NLIMB, CRPCTL.F00021.NLCK01, CRPCTL.F00021.NLSEQ FROM CRPCTL.F00021

SQLSTATE=S1C00, DBMS.CODE=0
[DataStage][SQL Client][ODBC][DataDirect][ODBC Oracle Wire Protocol driver]Optional feature not implemented.
-----------------------------------------------------------------------------------

I ran the same query at the SQL Prompt and it worked!!!

Can any one help me out with this.....

--Bob

Posted: Tue Sep 20, 2005 12:37 pm
by chulett
Your problem is not in the query, but with at least one of the configuration options you've specified. Cut them back to the bare minimum and see if it works then. Would guess for a wire driver that would mean:

Code: Select all

Description=DataDirect Oracle Wire Protocol
LogonID=uid
Password=pwd
HostName=oracleserver
PortNumber=1521
SID=oraclesid
If you really want to know the culprit, keep adding options back until you get your error again.

Better yet, forget ODBC and configure things so you can use the native OCI stages. :wink: