DB2 ERROR: CLI cursor fetch error: [IBM][CLI Driver][AS] SQL0904N

[sureshbaipu1]

Hi,

We are getting ERROR: CLI cursor fetch error: [IBM][CLI Driver][AS] SQL0904N Unsuccessful execution caused by an unavailable resource. Reason code: "13", type of resource: "423", and resource name: "". SQLSTATE=57011 while running a simple code as below.

libname XXXX ODBC user=XXXX password=XXXX schema='XXXXX' UTILCONN_TRANSIENT=YES DATAsrc=XXXX dbsliceparm=all;

PROC SQL;
CREATE TABLE XXXX AS
SELECT DATE, TERMINAL, TRACKID FROM XXX.XXXX;
QUIT;

[ballardw]

Please make sure that the example code you show is as submitted. When you start trying to hide things details may be obscured.

What you show

PROC SQL;
CREATE TABLE XXXX AS
SELECT DATE, TERMINAL, TRACKID FROM XXX.XXXX;
QUIT;

The XXX would be the LIBNAME, which you show as defined as XXXX. So hiding information with too many XXX's is likely hiding the actual problem between the schema, the libname and the table name(s).

Best is to show the LOG, copy from the log with the libname connection string, submitted code and all the notes and error messages. Paste into a text box opened on the forum with the </>. Edit the password/user information if needed.

If your Library and table names are that sensitive then perhaps that needs to be addressed internally.

[sureshbaipu1]

Sorry, Here is the sample code

libname abc ODBC user=def password=def1 schema='TEST' UTILCONN_TRANSIENT=YES DATAsrc=DB2 dbsliceparm=all;

PROC SQL;
CREATE TABLE test_table AS
SELECT DATE, TERMINAL, TRACKID FROM abc.emp;
QUIT;

run;

[sureshbaipu1]

Here is the Log

1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;7273
libname abc ODBC user=def password=def1 schema='TEST' UTILCONN_TRANSIENT=YES DATAsrc=cana dbsliceparm=all;

NOTE: Libref abc was successfully assigned as follows:Engine: ODBC Physical Name: cana 7475
PROC SQL;76 CREATE TABLE test_table AS77 SELECT DATE, TERMINAL, TRACKID FROM canamst.INT606F WHERE DATE BETWEEN 1210201 AND 1210208;
ERROR: CLI cursor fetch error: [IBM][CLI Driver][AS] SQL0904N Unsuccessful execution caused by an unavailable resource. Reason code: "13", type of resource: "423", and resource name: "". SQLSTATE=57011NOTE: Compressing data set WORK.test_table increased size by 20.33 percent.Compressed is 290 pages; un-compressed would require 241 pages.NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements.78 QUIT;NOTE: The SAS System stopped processing this step because of errors.NOTE: PROCEDURE SQL used (Total process time):real time 14.97 secondscpu time 1.19 seconds7980 run;8182 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;94

[ballardw]

Do you know if the table you are attempted to use is an actual table or a view in the DB2 database?

I am guessing here as I don't use DB2 but that missing resource name makes me wonder if you are accessing a view that needs to run dynamically at access time and either you do not have permissions or something may not be set correctly in your ODBC connection.

From https://www.ibm.com/support/pages/anr0172i-and-anr0162w-failure-when-attempting-start-server

SQL6030N START or STOP DATABASE MANAGER failed. Reason code "13".

Cause

The Tivoli Storage Manager fails due to the DB2 Database manager failing to start.

Diagnosing The Problem

The problem can be verified by issuing the 'db2start' command.
Start the Database manager with the db2start command. In this example db2start failed with the following error:

> db2start
SQL6030N START or STOP DATABASE MANAGER failed. Reason code "13".

RC =13 is a DB2 return code that means:
No port value is defined for your DB2 instance id (/etc/services file on UNIX-based systems).