2087735 - Targeted CR List for ASE 15.0.3 ESD#4.3

CR number

Description

491727

In rare circumstances, after HA-failover, a message "infected with signal 11" in module 'astc__h_ase_sendrpc' may be reported in the ASE errorlog, along with a stacktrace.

621863

When a DISTINCT view (or derived table) is queried in a parent DISTINCT query or is part of an EXISTS join (e.g. under IN/Any subquery), signal 11 stacktrace could happen in CgpPop::_CgpPePredBmToScalar() for distinct operator (CgpDistinctHashing/CgpDistinctSorting/CgpDistinctSorted) when the following three conditions are all true: 1. The DISTINCT view/derived table has at least one expression SELECT column; 2. The parent SELECT DISTINCT columns are only a subset of the DISTINCT view columns. Or if the EXISTS join is on one of the DISTINCT view columns; 3. One of DISTINCT view columns which is not part of 2) has a predicate on it in the parent query block.

670199

A signal 11 could be encountered with a stacktrace involving the function ResRelOp() called from CgpDistinctSorted::_cgpInit() when a DISTINCT VIEW with an expression DISTINCT SELECT column is queried with a constant equality predicate over the expression column and the final plan chooses DistinctSorted operator.

685171

When the set option "timestamp_insert" is enabled, an invalid value may result when inserting a "NULL" value into a timestamp column.

686209

When statement cache is on and after a variable assignment from a column of a table statement is cached, it will return wrong results for the subsequent select of the variable value if the lwp for the statement need to be recompiled.

696642

The message, "current process infected with 11", together with a stack trace which includes the module 'ulreleasespinlock' may be reported in the ASE errorlog when the remote server is shut down abruptly using 'shutdown with nowait' when a transactional query is in progress.

698063

When an INSERT query attempts to insert an explicit value for a TIMESTAMP column a warning will be reported, but query execution continues. If the explicit value for the TIMESTAMP column is the result of evaluating an expression, and the query plan for the INSERT is re-executed (i.e. because the statement cache and literal auto parameterization are enabled or because the INSERT query is part of a stored procedure), memory corruption may occur, leading to various stack traces.

700382

Shared locks, which are blocked by a demand lock on an earlier lock request, cannot be requeued after the blocking process is killed.

706799

Memory allocation failures appear in the ASE errorlog when the network memory pool is exhausted or when fragmentation of memory occurs due to memory that is not freed.

722777

ASE does not respond and appears to hang when certain invalid packets are sent to it.

729766

A new configuration value of '2' is added to configuration option 'enable xml' for external entity reference in XML documents, ie, set "sp_configure 'enable xml', 2" for external entity reference in XML documents.

729919

In very rare situations where incorrect port number is specified for sp_listener, subsequent calls to sp_listener might fail.

730183

Extended stored procedures added using sp_addextendedproc are malformed leading to failure of the extended stored procedure. sp_helpextendedproc shows an extraneous '[' character in the DLL name.

731758

When executing UPDATE STATISTICS with an object name that contains unusual characters, the command may fail with an internal error.

735292

An ASE task making a remote procedure call to a server with server option 'net password encryption' set to true and 'cis_rpc_handling' disabled can go to sleep indefinitely and the client appears to be hung.

735884

ASE may suffer from a memory leak when several client connections are simultaneously made using encrypted passwords.

736268

A login account that has a login-specific password expiration setting may have the global password expiration setting applied to it if the server encounters a 1204 (out of locks) error during the login attempt.

736550

Under rare circumstances a 696 error: "An attempt was made to read logical page ' < page# > ' for database ' < dbname > ' ( < dbid > ), object ' < tablename > ' ... from disk. Wrong logical page ' < page# > ' was brought into cache 'default data cache'." may be reported in the error log for allocation pages after the execution of CREATE, ALTER or LOAD DATABASE commands in an ASE installation using a page size that is greater than 2K-bytes and when during their execution the message "No large buffers were available, so pages are being cleared by writing each page separately. Please be patient" is reported. Alternatively a 2529 error, "Table Corrupt: Attempted to get page < page# > , partition ID 99; got page < page# > , partition ID 99." may be reported by DBCC CHECKALLOC.

737697

When running UPDATE INDEX STATISTICS with SAMPLING command, numerous errors may be reported in the errorlog - 1105 errors: "Can't allocate space for object 'temp worktable' in database 'tempdb' because 'system' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment" and 1764 errors: "Failed to insert row into worktable, when projecting base table on to work table for collecting statistics".

737762

Under rare circumstances backup server may produce unpredictable text attached to the dump trailer.

738322

Backup Server introduces a remote access control feature that prevents remote dumps and loads and execution of remote procedure calls (RPC) from any client or server running on unauthorized servers. Local dumps are not affected by this feature. Authorization to dump or load, to or from Backup Server is achieved by including the authorized hosts in the host.allow access control file. The default location of hosts.allow file is $SYBASE. The location and name can be changed using the Backup Server parameter -h.

738771

Under rare circumstances, a 12313 error: "Internal error: Insert into page id < pageno > of index id < indid > of table 'sysobjects' (id= 1) in database ' < dbname > ' tried to replace undeleted RID ( < pageid > , < rownum > ) at slot < slotnum > and ridposn < ridposn > . Try dropping and recreating the index." may be reported while loading a transaction log dump after onlining the database with STANDBY_ACCESS mode. The fix provides trace flag 3170 to bypass this error. Please turn on trace flag 3170 and reload the dump sequence.