SAP Knowledge Base Article - Preview

2839297 - Targeted CR List for ASE 15.7 SP142

Symptom

The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in Adaptive Server Enterprise (ASE) 15.7 SP142. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the support.sap.com.

Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.

CR NumberDescription
650665 In rare circumstances the message "Current process infected with signal 11 (SIGSEGV)" in the module 'norm3_expr' together with a stack trace which includes the module 'norm3__process_case' may be reported in the error log when a query includes a derived table and has a DISTINCT clause with a SUBQ in resdom and has an OJ. See KBA 2413073.
694618 The message, “The log page count in DBINFO for database < name > is inaccurate because dbi_freelogpages_at_ckpt < value > should be less than dbt_logsize < value > . Run DBCC TABLEALLOC(syslogs, full, fix) on this database in single-user mode to make the counts consistent again.”, may be reported in the SAP ASE error log during a database CHECKPOINT to help diagnose the origin of a 3475 error, “There is no space available in SYSLOGS to log a record for which space has been reserved in database < value > (id < value > ). This process will retry at intervals of one minute.”.
717519 The execution of "sp_setrepproc integer_p, 'table'" on primary ASE is replicated as "exec sp_setrepproc @replicate_name='integer_p', @setflag='table', @logflag='log_sproc'" which will lead to error 18108 because the parameters combination is incorrect.
752984 Feature request for a configurable parameter for the limit on the number of or-terms.
774104 A 15476 error, "Failed to find login password information for user < username > for key xxx", may be reported when 'login_passwd' option used in ALTER ENCRYPTION... MODIFY ENCRYPTION ... command on a connection authenticated using Kerberos.
774751 The value of IOTime, ReadTime and WriteTime queried from MDA monDeviceIO table may frequently overflow when ASE under heavy IO activity workloads. See KBA 2097726.
778763 dbcc memusage command might report inconsistent values under "Cache Memory" when caches are dynamically created/deleted.
780764 The error message, "Current process infected with signal 11 (SIGSEGV)", followed by the stack trace involving the modules 'ra__coord_driver' and 'ra_schema_dealloc_cache' may be reported against the Replication Agent Coordinator Thread when Replication Agent is configured for Multiple Paths Replication and Multiple Scanners, and it is stopped by executing sp_stop_rep_agent.
789192 Under rare cisrcumstances, after an upgrade of SAP ASE, a 11031 error, "Procedure ' < procedure-name > ': Execution of SQL function < function-name > failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo. < procedure-name > .", or a 11798 error, "Illegal CREATE FUNCTION statement within a scalar SQL function.", may be reported when executing a stored procedure or a function. See KBA 2217001.
799279 The error 536, "Invalid length parameter with value of -1 passed to the substring function", may be reported in the SAP ASE error log when executing sp_helptext on a VIEW when the VIEW is created with a long string. KBA: 2837764 - 'Msg: 536' raised from sp_helptext with 'view_text' option
802852 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 's_unsave_kept_stmts' together with a stack trace which includes the modules 's_normalize' and 's_xform_to_execute' may be reported in the SAP ASE error log when a query in a batch is executed and the statement cache is enabled. See KBA 2453655.
803087 The message "current process infected with 11 (SIGSEGV)" in the module 'CgGenLava::CGConsScanOp' together with a stack trace which includes the modules 's_compile_stmt' and 'GenLava' may be reported in the SAP ASE error log when executing a query that use a non-correlated subquery which contains an IN clause. See KBA 2383992.
807420 Msg 247, Level 16, State 1: "Arithmetic overflow during implicit conversion of UNSIGNED INT value " < value > " to a INT field" cat be seen when running the sp_spaceusage stored procedure to display syslogs. See KBA 2776772
808897 In rare circumstances, a 706 error, "Process < value > tried to remove PROC_HDR < value > that it does not hold in Pss.", together with a stack trace which includes the modules 'rm_prochdr' and 'memfree' may be reported in the SAP ASE error log when a process is killed. See KBA 2171618.
811034 The message "current process indectred with signal 8 (SIGFPE)" or "timeslice < value > , current process infected at < address > " in the module "s__collectdiagparam" may be reported in the errorlog when ASE has not restarted for long time. See KBA 2542965.
812532 In rare circumstances, a 11060 error, "This statement has exceeded the maximum number of recompilations (10).", may be reported when Dynamic SQL queries are executed from Java or Python clients. See KBA 2845818.
815204 The message "current process infected with 11 (SIGSEGV)" in the module 'np_conn_props' together with a stack trace which includes the modules 'omni_ct_cancel' and 'hk_cis_idle_timeout' may be reported in the SAP ASE error log when many CIS connections exist and the configuration option "cis idle connection timeout" is enabled. Alternatively the SIGSEGV can be hit in the modules ‘comn_loc_copy’, ‘ct_poll’, ‘ct_gp_version’, ‘ct_gp_version’ or ‘ct__tds_sendcmds’. See KBA 2651690.
815851 The message, "Current process infected with signal 10 (SIGBUS)" in the module 'odlrh__toloh' together with a stack trace which includes the modules 'onl__test_upgraded_replicated_db' and 'online_database' may be reported in the SAP ASE error log, when a replicated database dump is loaded into an upgraded Adaptive Server version. See KBA 2686290.
816054 The message, "Current process infected with signal 11(SIGSEGV)", followed by a stack trace that includes the modules 'bt__col_cmp_noopt' and 'bt__nonlfrow_cmp' may be reported in the SAP ASE error log when a SELECT query with GROUP BY that contains expressions is executed. See KBA 2681394.
816102 The message "current process infected with 11" in the module 'norm3_expr' together with a stack trace which includes the modules 'norm3__process_case' and 'crcpc_norm' may be reported in the error log when computed columns is queried in a SELECT statment. See KBA 2844942.
816716 A 11030 error, "Execution of unknown type ptncond_xxx_0 failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo.ptncond_xxx_0.", can be seen after an upgrade when a roundrobin partitioned table with a clustered index has an index key with bigdatetime/bigdate/bigtime datatype. See KBA 2697077.
817097 A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact Sybase Technical Support.", may be reported when a SELECT query with two tables join and a GROUP BY clause on each side of the join is executed while the optimization goal allrows_mix is enabled but hash_join is not. See KBA 2708697.
817400 In rare circumstances, random failures with the message "current process infected with signal 11 (SIGSEGV)" together with a stack trace may be reported in the SAP ASE error log when SELECT queries were earlier executed with the reformat strategy applied and the reformat worktable had rows whose size was unexpectedly bigger than the current Adaptive Server configured page size. See KBA 2763915.
817869 In rare circumstances, a 102 error, "Incorrect syntax near ';'.", followed by a 111 error, "CREATE PROCEDURE must be the first command in a query batch.", and a 156 error, "Incorrect syntax near the keyword 'END'.", may be reported when CREATE PROCEDURE is executed and the stored procedure text includes a large number of white space characters. See KBA 2716155.
818538 In rare circumstances, a process may run into a self-deadlock with the message, "Killing spid: < value > will not be immediate because it is waiting for a latch held by spid: < value > .", reported in the SAP ASE error log upon a KILL. This process was attempting to create a temporary table but was waiting for an allocation page lock which was held by another process. See KBA 2789764.
818627 In rare circumstances, following a 1204 error, "ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.", queries or built-ins execution on SYSLOGINS may hang. See KBA 2763234.
818852 A 10795 error, "The file ' < xx > .class' contained in the jar does not represent a valid Java class file" may be reported while install the jar file in ASE database. See KBA 2790939.
818885 When running sp_sysmon using the appl or appl_and_login option, the application or application- > login section reports inaccurate Disk and Network I/Os when there are multiple sessions with the same application or application- > login pairing. See KBA 2776095.
818891 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'oh_copy' and 'oh_dup', may be reported in the SAP ASE error log when When creating login within IF-ELSE with auditing enabled. See KBA 2843548.
818953 The message "ELC_VALIDATION_ERROR: Page address not aligned to memory page size.", followed by "Current process infected with signal 11 (SIGSEGV)" in the module 'subp' together with a stack trace which includes the modules 's_execsetvar' and 'subparams' may be reported in the SAP ASE error log when prepared INSERT statements are executed. See KBA 2774710.
818972 The message "current process infected with 11" in the module 'lt_run' together with a stack trace which includes the modules 'lt_send_row', 'mda_populate_monMemoryUsage', 'mdarpc_exec' and 'execrpc' may be reported in the error log when the monMemoryUsage MDA table is queried remotely as an RPC for a proxy table. See KBA 2781904.
818978 A 7124 error, "The offset and length specified in the READTEXT command is greater than the actual data length of < value > ." may be reported when running "readtext" with the "size" or "offset" parameter datatype different than integer. See KBA 2778603.
819187 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘kstcpnetctlrCancelRequests’ together with a stack trace may be reported in the SAP ASE error log. If shared memory dump is configured for signal 11, then ASE may hang. See KBA 2786903.
819224 The message "current process infected with signal 8 (SIGFPE)" in the module 'proc_setdb' together with a stack trace which includes the modules 's_getTreeOrPlan', 'attachrule' and 's_compile' may be reported in the error log. See KBA 2593370.
819231 Under rare circumstances, the message "Volume validation error: attempt to open < ASE_devicename > returned No such file or directory", may be reported on a Solaris platform during the execution of a DUMP command when the Backup Server received a SIGPOLL signal while attempting to open an ASE device. See KBA 2774930.
819260 A 911 error, "Attempt to locate entry in sysdatabases for database '' by name failed - no entry found under that name. Make sure that name is entered properly.", may be reported when a prepared statement issuing CHECKPOINT < database_name > is executed. See KBA 2791971.
819273 SAP Adaptive Server dataserver process leaks O/S memory when the built-in xmlextract() is executed. See KBA 2806756.
819308 In rare circumstances, a 2620 error, “The offset of the row number at offset < value > does not match the entry in the offset table of the following page: Page pointer = < value > , pageno = < value > , etc.”, together with a stack trace which includes the modules ‘update’ and ‘putdow’ may be reported in the SAP ASE error log during a DML execution on an All Pages Locked (APL) table when one or more previous UPDATE command(s) were executed in deferred mode. See KBA 2838778
819388 In rare circumstances, SAP Adaptive Server may not shutdown when the SHUTDOWN command is executed or when shutdown from the Windows Service. The module 'shutdownjobscheduler’ will be reported by DBCC STACKTRACE on the session executing the SHUTDOWN command or the SHUTDOWN HANDLER task. See KBA 2797851.
819468 When the configuration option 'enable granular permissions' is set, a user that is aliased to dbo in the master database is aliased to dbo in all databases. See KBA 2795960.
819493 A 247 error, "Arithmetic overflow during explicit conversion of FLOAT value ' < value > ' to a NUMERIC field" may be reported when executing sp_helpcache or manually querying the syscacheinfo or syscachepoolinfo view on the system that configures very large caches. See KBA 2402812
819500 Under rare circumstances, on a heavily-loaded multi-engine SAP ASE, the 'Operations' column in monOpenObjectActivity MDA table might get wrapped in a short time.
819523 A 2901 error, "Exception stack limit exceeded", followed by a rolled back transaction, may be reported in the SAP ASE error log when executing "dbcc upgrade_object(dbname, 'procedure', 'check')" on AIX platform.
819538 jConnect applications may fail with the message, ‘java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).’, reported when SAP ASE is configured with MIT Kerberos and charset conversion is not available between Adaptive Server and jConnect charsets in use. See KBA 2807020.
819570 Under rare circumstances, a 3935 error, "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context. The transaction is currently in 'NULL XDES' state.", may be reported in the SAP ASE error log when before many 1105 errors were encountered. See KBA 2816667.
819626 Workload capture takes longer time to stop especially when ASE configured with multiple online engines. The more engines configured, the more time it takes to stop the workload capture. Typically, it may takes over 1 minute when ASE configured with 32 engines.
819746 The message 156 "Incorrect syntax near the keyword 'else'." can be seen when running the sp_dropdevice command after an upgrade. See KBA 2818609.
819756 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'com__exctnume_copy' together with stack trace which includes the module 's__convert_nume' may be reported in the SAP ASE error log when a prepared statement performs UPDATE on numeric columns to NULL and the option DYNAMIC_PREPARE is set to FALSE and trace flag 11013 is enabled. See KBA 2819614.
819846 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'rvm_has_decrypt_permission' together with a stack trace which includes the modules 'LeRun' and 'exec_lava' may be reported in the SAP ASE error log when a SELECT query against an encrypted column is executed. See KBA 2827203.

Read more...

Environment

  • AIX 64bit
  • HP-UX on IA64 64bit
  • Linux on Power 64bit
  • Linux on x86 64 64bit
  • Solaris on Sparc 64bit
  • Solaris on x86 64 64bit
  • Windows on x64 64bit

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition

Keywords

CR, CR List, ASE 15.7 SP142, ASE SP142, Adaptive Server Enterprise, Fix, Patch, Error, Bug, SP142 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.