You're now being signed in. See the referenced DB2 technote for a DESCSTAT discussion. SQLSTATE=S1C Search this topic...|Search Semantic Layer / Universe Designer...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post Forum Index There are lots of flags that can be turned off or on to affect how the SQL is generated for ODBC. weblink
I don't know what setup for it is done on the DB2 side. For example: [DATABASE_NAME] PATCH2=6 Explanation: PATCH2=6 Forces the driver to return a message indicating that scrollable cursors are not supported. You did an awesome job!
Now, I am having a problem with creating a report using DB2 data. Still i am facing the same problem. http://www-01.ibm.com/support/docview.wss?uid=swg21438706
Trey 120000BTRN 2010-09-17T01:42:02Z if this is still an issue and you would like to dig into the problem i would ask for two things, ok three.. Keep in touch with Experts ExchangeTech news and trends delivered to your inbox every month Live Consultants Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an SQLSTATE=S1C00", pcbErrorMsg=62 ) <--- SQL_SUCCESS Time elapsed - +1.816940E-001 seconds Cause A cursor type of SQL_CURSOR_STATIC is being used, which means static and read only.
I'm waiting to hear from the DBA. This is the accepted answer. Back to top scott copelandForum EnthusiastJoined: 15 Aug 2002Posts: 1219Location: State AG, Tallahassee, FL Posted: Fri Apr 22, 2005 11:08 amPost subject: Re: [IBM][CLI Driver] CLI0150E Driver not capable. After i changed to FOR cursor.
Sometimes, i got the following error also: D:\PROGRA~1\SQLLIB\BIN>db2 call nmworkb.test_sp('1',1,'1',1,1,null,null,null,?,?) CLI0104E Unable to connect to data source. Please advise me what am I doing wrong. When the schema name is not provided, it should qualify it with the connecting userid as the default schema. https://www.ibm.com/developerworks/community/forums/thread.jspa?threadID=346413 What may the reason to get the above error?
I have a ODBC connection, and I successfully connect to DB2. IBM Support Check here to start a new keyword search. Do your connections have a user ID embedded in them or does it use your BO login ID? PDT Register Now Question has a verified solution.
I would greatly appreciate any advise from any of you. https://www.experts-exchange.com/questions/20875947/Error-CLI0150E-Driver-not-capable.html Log In Create an Account Blogs Discussions CHOOSE A TOPIC Business Intelligence C Languages Cloud Computing Communications Technology CRM Data Center Data Warehouse Database Emerging Technology and Trends Enterprise Architecture and Ron am able to connect to DB2 and execute standard sql queries from my FEX code. SQLSTATE=S1C In Designer (vs5.1.5) I receive the following error when I try to insert a table "Error in retrieving tables" with details showing "[IBM][CLI Driver] CLI0150E Driver not capable.
Once you know that, you can figure which side of the fence the problem might be on. have a peek at these guys You signed in with another tab or window. Trey 120000BTRN 227 Posts Re: CLI0150E Driver not capable. RonEisner replied Jul 14, 2005 It's hard to tell without actually seeing the code that you're executing.
via informationbuilde To rs-l" Ron Eisner
What will be best solution to solve this error &avoid this error in future? IBM Support Check here to start a new keyword search. Join & Ask a Question Advertise Here Enjoyed your answer?
Please ensure that the stored procedure and related tables are created and present in the database t you are connecting to. Join Now For immediate help use Live now! Reload to refresh your session. Thanks Nilesh More...
Can you get to DB2 with the same CLI driver using anything else - like Access? SQLSTATE=08001 I dont know... Above is in line with ibi docs. this content SQLSTATE=S1C00 error.
I have downloaded new DB2 drivers, and when i create a new Data connection I pick db2jcc.jar file.
I really dont know what the problem is.
nnGuest November 03,
The database is DB2. The failure occurs when the stored procedure is called without the schema name and the stored procedure exists under the connecting userid's schema. Send through a single transaction to trigger the event then open a pmr and send in the log with all of the tracefiles created. (there will be one trace log per The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material.
SQLSetPos( hStmt=1:1, iRow=1, fOption=SQL_ADD, fLock=SQL_LOCK_NO_CHANGE ) ---> Time elapsed - +9.964000E-003 seconds SQLSetPos( ) <--- SQL_ERROR Time elapsed - +6.722200E-002 seconds SQLGetDiagRecW( fHandleType=SQL_HANDLE_STMT, hHandle=1:1, iRecNumber=1, pszSqlState=&63e3de98, pfNativeError=&63e3da7c, pszErrorMsg=&63e3da98, cbErrorMsgMax=512, pcbErrorMsg=&63e3da80 )