2079918 - Targeted CR List for ASE 15.7 SP61 -SAP ASE

CR number

Description

715203

DBCC CHECKSTORAGE does not detect LOB compression flag inconsistencies in the TIPSA. With DBCC CHECKTABLE and DBCC CHECKDB these types of inconsistencies were already being reported with message 15960.

736622

When running REORG REBUILD against a table whose name or any column name might form part of a reserved double or triple keyword phrase it is possible for an error 156 error to be reported along with error 11934 and for the REORG REBUILD command to abort.

749279

When a rule is created which is not compatible with the column to which it is bound, SAP ASE generates an error message when it tries to insert a value. After raising the error, a SIGSEGV is then reported.

750937

Sometimes a long running transaction can be seen in tempdb for $sort_local which results in tempdb filling up if a large data set needs to be sorted.

752115

When the SAP ASE kernel mode is configured as process and an SSL session/connection is abruptly killed/aborted, a SIGSEGV (infected with 11) with a stacktrace may be reported in the SAP ASE errorlog. The functions drop_connection() and ssl_nclose() are likely to be seen as part of the stacktrace.

752408

In rare circumstances, a 3474 error, "During redo the page timestamp value is less than old timestamp from log....", may be reported during boottime or LOAD DATABASE recovery, when a transaction that allocated a page, rolled back that allocation while a checkpoint was active.

752639

When the SAP ASE server is out of locks, a permission check can cause the error message "ulpspinlock: spinlock order violation" to be reported followed by a crash the SAP ASE server.

752839

The message "current process infected with 11" in the module 'cpynodes' together with a stack trace which includes the modules 's_copytmps' and 'batch_loopend' may be reported in the SAP ASE error log when a BATCH INSERT into a temporary table is executed, followed by 6103 and 703 error while SAP ASE attempts to free procedure cache memory.

753022

SAP ASE running on Windows platforms may report the following message in the SAP ASE errorlog early on during startup: "kernel KERNEL structure not padded correctly - size = 1736". This message may be safely ignored, and this CR prevents it being reported.

753098

In a long running ASE server configured for SSL, SSL handshake errors due to memory allocation failures appear for new incoming connections.

753461

A segmentation violation occurs when sp_listener starts an SSL listener where no SSL listeners had been started previously.

753525

SAP ASE running on Unix/Linux platforms only prints the top 25 stack frames in a stack overflow stacktrace report which could mask the root cause and also provide insufficient diagnostics when a stack overflow is caused by a recursive function. If the stack overflow backout code uses too much stack, the backout process can cause stack guard word corruption resulting in server shutdown. This CR removes the limitation on number of frames in the stacktrace and if the stack overflow backout code use of the stack reaches within 4K bytes of the stack boundary, it then initiates forcible termination of the task to prevent stack guardword corruption. The default value of 'stack guard size' is increased by 4K bytes to retain earlier level of stack availability. Traceflag 3687 provides a stacktrace when a transaction is aborted due to insufficient stack space that can provide additional diagnostics on stack usage by the query. Traceflag 3686 disables this change. This change is not applicable to the Microsoft Windows platforms.

753905

When using ALTER DATABASE, an 806 error, "Could not find virtual page for logical page < page# > in database ' < dbname > '..." may be reported if ALTER DATABASE removes more than a single fragment from the end of the given database.

753956

When an insert trigger exists on the target table of the MERGE statement, the wrong result may happen.

753989

On Microsoft Windows platforms an isql session may hang when establishing an SSL connection to an SAP ASE.

753996

An SAP ASE shutdown occurs after hitting a SIGSEGV (infected with 11). In the SIGSEGV message in the SAP ASE errorlog the faulting address may reference the function uppushaffinity().

754075

In some rare conditions, error 8201, severity 26, state 1 might be raised during high availability failover accompanied by a stack trace with des_do_get/ha_session_check in it.

754095

On the AIX platform, when SSL is enabled, after a few thousand connections, connection failures occur and error message "ks_falloc: Cannot allocate using ubfalloc" appears in the SAP ASE errorlog.

754273

Client connections to SAP ASE may hang when SSL is enabled and the network memory pool is exhausted.

754679

In some cases, a DML command is not correctly replicated because SAP ASE Replication Agent may mistakenly generate the table schema definition for metadata reduction for a table that is marked for replication. Schema building is needed when the table is created or altered in the same user transaction as the DML which affects the same table.

755330

When using LDAP, an assertion message and a SIGABRT/SIGIOT (infected with 6) stacktrace may be reported in the SAP ASE errorlog. The assertion will say "result == SYBCSI_RESULT_OK, file core/source/csimemory.c". The stacktrace will include the function login__ldapauth().

756648

A 213 error can be reported "Insert error: column name or number of supplied values does not match table definition." in a stored procedure, when deferred compilation is active, if a column is added to a table and there is a dependency on "select * " behavior to ignore the extra column. Trace flag 7798 will ignore this error if deferred compilation is turned on and allow normal compilation to process the statement. If normal compilation still sees an inconsistency, or some other activity causes re-resolution of the stored procedure, then errors may be still be reported.