Providing software solutions since 1976
46389 - The incorrect DB2 table might be referenced when CURRENT SQLID is set within implicit pass-through- Problem Note
The LIBNAME option DBCONINIT= is used to pass a specific DBMS statement to be executed immediately after each DBMS connection is successfully established. If you use this option to submit the SET CURRENT SQLID= ...
45386 - The DB2UTIL procedure might insert incorrect characters into character variables- Problem Note
If a DB2 variable that is defined as a VARCHAR or CHAR has a length greater than 200 bytes, the DB2UTIL procedure might insert incorrect data in the variable. The only workaround is to switch to using the DB2 LIBNAME ...
37033 - Using the DBKEY= option in the SQL procedure might cause incorrect results- Problem Note
Incorrect values might result in a situation where you use the DBKEY= option, the key variable contains a missing value, and the DB2 field in a DB2 table is defined as NOT NULL. In this situation, the values from the ...
In the z/OS environment, when you use SAS/ACCESS® Interface to DB2 to pass arguments in the INDEX() function to DB2, the implicit pass-through facility does not correctly switch the argument order for the DB2 function ...
Incorrect results might occur if you use the PUT() function in a WHERE clause to convert a DB2 timestamp to a character value so it can be compared to a constant in the WHERE clause. Even if matches exist, they will not ...
20419 - Joining SQL Views of Oracle tables that contain where clauses results in invalid SQL query- Problem Note
Joining 2 SQL views of DBMS tables that contain where clauses yields incorrect SQL being passed to the DBMS. Using Oracle will return the following error: ERROR: ORACLE prepare error: ORA-00904: "CELL_DW"."DW_DIM_ ...
44189 - Poor performance might occur when subsetting against a DB2 binary (raw/bit) data type- Problem Note
SAS does not pass WHERE clauses against binary data types to DB2. Instead, data is being read into SAS and processed there.
20650 - SAS/ACCESS® Interface to Netezza fails with "ERROR: The NETEZZA engine cannot be found"- Problem Note
When you use SAS/ACCESS Interface to Netezza, it might generate the following failure message: ERROR: The NETEZZA engine cannot be found This problem occurs because the logical name NETEZZA is not registered in ...
20129 - An incorrect Implicit Pass-Through query is generated when you use a combination of inner and outer Joins- Problem Note
An incorrect Implicit Pass-Through query is generated when you use the following code, which contains a mixture of inner and outer joins: proc sql; create table work.tab1 as select * from SQLD5A a lef
19747 - Trying to add a password to a DBMS table might result in an error- Problem Note
You might get the following error message if you try to add a password from within SAS by right-clicking on a DBMS table that has been defined either in a LIBNAME statement in the Explorer window or with the SETPASSWORD ...
4391 - SYSDBMSG displays erroneous error message after inserting rows into DBMS table with PROC APPEND- Problem Note
When appending to a DBMS table using PROC APPEND, SYSDBMSG will display the following error message when the insert into the table is successful: ERROR: MEMBER level locking for UPDATE or RANDOM access is not ...
12222 - 'ERROR: Floating Point Exception' occurs using SAS/ACCESS engines- Problem Note
Using SAS 9.1 and SAS/ACCESS to compare a numeric field to '' in a WHERE clause or CASE expression will result in the following error: ERROR: Invalid Operation. ERROR: Termination due to Floating Point Exception ...
9514 - Accessing DBMS tables with column aliases defined via a view may prevent implicit pass-thru- Problem Note
Using a PROC SQL view that contains column aliases to access a DBMS table may result in SAS doing all the processing. As a workaround, column aliases can be removed from the view, or access the DBMS tables directly ...
12757 - SAS/ACCESS query may return incorrect results when duplicate variable names exist- Problem Note
Running a query with a group by clause using SAS/ACCESS LIBNAME engine may yield incorrect number of rows. This scenario occurs when SAS detects duplicate variable names. A Technical Support hot fix for Release 8.2 ( ...
12405 - Access violation or system hang using SASTRACE option on 64-bit Windows- Problem Note
Using the SASTRACE option on 64-bit windows and executing a DATA step or PROC may cause the SAS session to hang or return an access violation. The following code will cause this problem: options SASTRACE=',,,d' ...
4996 - "ERROR: Invalid Sequence of Commands" importing a DBF file- Problem Note
When using PROC IMPORT to import a DBF file, you may encounter the following error: Error: Invalid Sequence of Commands. This error can be generated if the DBF file contains duplicate column names. This does not ...
9743 - Using VIEWTABLE to subset a view of a DBMS table with an ORDER BY loses sorted order- Problem Note
Using VIEWTABLE to subset an SQL view of DBMS data that contains an ORDER BY will successfully subset the data, but the order is lost. There currently is no circumvention for this problem.
12083 - "Column may not be updated" error messages when using DBMS LIBNAME engine- Problem Note
Running a PROC SQL UPDATE statement against DBMS tables may result in the error message "column may not be updated", even though the SQL UPDATE has not been coded to update the column in question. For example, TABLE1 ...
11220 - Numeric literals in an ON clause with outer join of some DBMS tables may not return correct results- Problem Note
A portion of the WHERE criteria may be lost when doing an outer join on DBMS tables with a numeric literal listed on the ON clause. This causes incorrect results to be returned to SAS. for example: select * from x. ...
6720 - "Error: file libref.tablename is sequential" using SAS/ACCESS LIBNAME with DATA Step MODIFY statement- Problem Note
When attempting to update a DBMS table with a MODIFY statement in a DATA Step using the SAS/ACCESS LIBNAME engine, you may receive the following error: ERROR: File libref.tablename is sequential. This task requires ...
10026 - Joins are not occuring on the DBMS when DBKEY with 2 column values are specified- Problem Note
When using PROC SQL with the Access LIBNAME engine to join DBMS tables and specifying two columns for the DBKEY= clause, the join may not get passed to the DBMS. For example, with one column specified for DBKEY we ...
5708 - ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state- Problem Note
Using SAS/ACCESS to ODBC or SAS/ACCESS to DB2 may result in the following error: ERROR: CLI open cursor error. [IBM][CLI Driver][DB2] The cursor "SQLCURCS297" is not in prepared state. SQLSTATE=26501 We have ...
9723 - Interrupt Handling not available with SAS/ACCESS on UNIX- Problem Note
When using the SAS/ACCESS Interface to a database, it is not possible to interrupt the process. This is true for both non-interactive (batch) processes and for DMS sessions. Once the database has gained control of a ...
9727 - Aliased columns in SQL views which perform a simple calculation may lose part of the condition- Problem Note
If you have an SQL view to a DBMS table and the view recodes a column, under certain conditions the calculations performed in the view are lost. For example, in the following code the multiplication operation is lost ...
When performing a new installation of SAS on Unix, if you choose "Load All Licensed Software," SASSETUP will notify you if ACCESS modules are licensed and will tell you that these ACCESS modules require configuring. ...
