Y46013 for 64-bit Enabled AIX |
SAS Federation Server 4.2 |
Issue(s) Addressed: | Introduced: |
58386 | In SAS® Federation Server, cached views created using TPT do not correctly display rows |
Y46002 |
57792 | SAS® Real-Time Decision Manager campaign fails with "org.apache.commons.dbcp.SQLNestedException: Borrow callableStatement from pool failed" |
Y46003 |
58789 | SAS® Federation Server clients generate "ERROR: Multiple DBMS credentials of equal precedence configured for the current authorization and rejected" |
Y46003 |
59346 | In SAS® Federation Server, an SQL query returns "An exception was thrown while waiting for a reply from the peer" when querying large volumes of data |
Y46004 |
59348 | Code generated by SAS® Federation Server Manager is incorrectly formatted |
Y46004 |
59349 | Logging on to SAS® Federation Server from the SAS® Federation Server Manager user interface takes a long time |
Y46004 |
59396 | SAS® Federation Server returns column names from a query in uppercase letters regardless of their case in the underlying table |
Y46004 |
59426 | Viewing data from SAS® Federation Server Manager 4.2 returns the error “The data cannot be shown..." |
Y46004 |
59431 | In SAS® Federation Server 4.1, the Trace driver crashes due to a memory overwrite |
Y46004 |
59499 | SAS® Federation Server 4.2 fails to retrieve data source contents when connecting to the SPD Server via an ODBC driver |
Y46006 |
61390 | Using UNION ALL with two views returns the "Table 'XXXX' not found in FROM clause" error |
Y46006 |
61391 | Using the UNION ALL query returns invalid data |
Y46006 |
59933 | When you use a null value in data-masking functions in SAS® Federation Server 4.2, "Error: HY000 Error occurred building the Execution Tree..." occurs |
Y46007 |
60076 | You are not able to see your privileges in SAS® Federation Server Manager |
Y46007 |
60546 | Incorrect results are returned from a wildcard % query on PostgreSQL Threaded Kernel Table Services (TKTS) tables |
Y46007 |
60600 | SAS® Federation Server becomes unresponsive to SAS® Real-Time Decision Manager |
Y46007 |
60676 | Issues such as system call failures and unresponsive SAS® processes occur with long-running processes that use DS2 or DATA step programming language |
Y46007 |
60714 | SAS® Scalable Performance Data Server fails to connect to a domain with "Connection does not exist...zdcrypt local buffer too small..." |
Y46007 |
60715 | SAS® Enterprise Guide® cannot display Latin5 characters that come from SAS® Federation Server |
Y46007 |
60726 | SAS® Federation Server Manager shows invalid characters for SAS® Scalable Performance Data Server data |
Y46007 |
60755 | SAS® Real-Time Decision Manager experiences intermittent high response times when you use DS2 and SAS® Federation Server 4.1 |
Y46007 |
61393 | Count(*) returns incorrect and random results for a UNION ALL query between two tables |
Y46007 |
61394 | Table field names are not displayed in the field list if the schema name contains escape characters |
Y46007 |
61399 | A "Syntax error or access violation" occurs when you use nested functions and a WHERE clause |
Y46007 |
61402 | Using the ENCRYPT data masking function with the AES algorithm yields poor performance |
Y46007 |
61403 | You experience poor performance when you use the FEDSRV engine because sub-queries are not pushed to the database in cross-database joins |
Y46007 |
61423 | In SAS® QKB Pattern Logic nodes, the "Full phrase" option in the extraction definition does not work properly |
Y46007 |
61425 | When you run SQL queries in SAS® Federation Server, the error "postprocess_setop-tlist: resjunk output columns are not implemented" occurs |
Y46007 |
61897 | SAS® Federation Server becomes non-responsive in SAS® Real-Time Decision Manager and errors are generated |
Y46008 |
62411 | You cannot view BLOB or CLOB data from an Oracle table when you use a LIBNAME statement with the FEDSVR engine |
Y46009 |
62488 | Writing numeric values to Oracle might cause precision loss |
Y46009 |
62563 | A large number of 'UNPREPARE' error messages appear in the Microsoft SQL Server log when you execute campaigns in SAS® Real-Time Decision Manager |
Y46010 |
62661 | A "Numeric Value out of range" error occurs under certain conditions when you filter data in a FedSQL view via a WHERE clause |
Y46011 |
63231 | Opening an Oracle table with the Federation Server engine causes SAS® Federation Server to fail with "ERROR: CLI cursor fetch error..." |
Y46012 |
60709 | When you insert text data containing a question mark (?) into an Oracle database table from SAS® Federation Server, the ? is converted to :1 |
Y46013 |
61314 | A SAS® process of code type "SAS DS2" fails to run and generates an error |
Y46013 |
61759 | When you run the FEDSQL procedure on Oracle tables, it generates "ERROR: FEDSQL does not support 'long data when pushdown fails'" |
Y46013 |
62519 | A DATASETS procedure that requests a large number of Oracle tables from SAS® Federation Server takes a long time to complete |
Y46013 |
63212 | ALERT - The CI_PACKAGE_X_TREATMENT table becomes locked in Teradata during the DS2 contact-history process |
Y46013 |
63468 | Running a large Oracle SQL query causes SAS® Federation Server to stop responding with "General Error - invalid Exception" |
Y46013 |
63490 | You encounter slow performance when fetching large amounts of data using the SAS® Federation Server Engine |
Y46013 |
NOTE: If you install this hot fix and have SAS Drivers for Federation Server 4.2 installed, you must also install hot fix Z51002. If you install this hot fix and have SAS Threaded Kernel 9.4_M4 installed, you must also install hot fix A5D006. If you install this hot fix and have SAS Threaded Kernel Drivers for Scalable Performance Data 5.3_M1 installed, you must also install hot fix A4U002. If you install this hot fix and have SAS Threaded Kernel 9.4_M3 installed, you must also install hot fix Y81004. If you install this hot fix and have SAS Scalable Performance Data Server 5.3 installed, you must also install hot fix A3J005. If you install this hot fix and have SAS Federation Server Manager Mid-Tier 4.2 installed, you must also install hot fix A1A004. |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |