Articles

Unable to open a SAS/ACCESS® Interface to DB2 table that contains columns names longer than 30 characters

The error "SESSION.tabname IS AN UNDEFINED NAME" occurs when joining a temporary DB2 table

Bulk Insert data conversion error when import dimensionMember table intoSAS ABM model

An error might occur when you create a new BigQuery table using a PROC SORT of a BigQuery table with a date before 01JAN1582

A SAS® Viya® platform SAS/CONNECT® scripted SIGNON to a SAS®9 SAS/CONNECT spawner does not work

Errors are generated when you declare a PROC DS2 matrix package with SAS® Embedded Process for Hadoop

The expression for an existing computed column might be updated incorrectly in SAS® Enterprise Guide®

Bridge failure with ANNOTATE= option in PROC UNIVARIATE

Prior to SAS® 9.1, PROC SHEWHART might terminate abnormally with the OVERLAY= option and many subgroups

The message "ERROR: The connection to the data source driver failed...[..." occurs when you create a caslib with SAS/ACCESS® Interface to ODBC

SAS/ACCESS® Interface to ODBC on SAS® Viya® 3.5 fails to establish a PostgreSQL connection with "ERROR: CLI error trying to establish connection"

The VARCLUS procedure issues "WARNING: Iteration limit exceeded in search phase"

Interrupting a long-running query that is accessing DB2 is not supported when SAS® is running on an IBM z/OS platform

The SCOREACCEL procedure might generate "ERROR: Could not open source file" when you use a fileref with the PROGRAMFILE= or the VARXMLFILE= parameter

A syntax error might occur when you try to use the scoring functions in Teradata

SAS® Enterprise Guide® might fail and return the error "Not enough quota is available to process this command"

Using the RANK procedure or the SORT procedure with a Google BigQuery table might generate an error

Using the SQL procedure to update a table allocated via SAS/SHARE® might not update the table

Reading in a BigQuery table using BULKUNLOAD might result in incorrect values

FEDSQL JOIN code in a CAS session on SAS® Viya 3.5 incorrectly changes values that are greater than 24 hours for data with the TIMEw.d format