SAP HANA 2 SPS07 Revision 071.00

Symptom

This is the Release Note for SAP HANA 2 SPS07 Revision 071.00 (2.00.071.00).

It is released for customers since 30th of June, 2023.

For further information on the Release Strategy, Downloading Media, Installation/Upgrade, Supported Platforms and General Remarks, please refer to the sources below.

Release Strategy:

• SAP Note 2380229 - SAP HANA Platform 2.0 - Central Note
• SAP Note 3198680 - SAP HANA Platform 2.0 SPS 07 - Release Note
• SAP Note 2941449 - SAP HANA Client 2.0 Releases
• SAP Note 2378962 - SAP HANA 2.0 Revision and Maintenance Strategy document on SAP Software Download Center for an overview regarding the SAP HANA revision and maintenance strategy.
  
  

Downloading Media:

• In the SAP Software Download Center you find media required to install a new SAP HANA system or upgrade an existing one.
  Please note that all SAP HANA media on SAP Software Download Center are a self-contained full installation media - this applies for the media available in section Installations & Upgrades as well as for the media available in section Support Packages & Patches.
  
  Section Installations & Upgrades only contains media for the very first revision of an SPS.
  Section Support Packages & Patches only contains the latest revision of an SPS.
  
  It is strongly recommended to use the most recent revision of an SPS, to avoid running into issues which are already known and fixed.
  Therefore, by default, please refer to section Support Packages & Patches to download media for all components of SAP HANA for an installation/upgrade.
  
  See chapter "Software Download" in the SAP_HANA_Master_Guide for the path to the media.
  
  

Installation/Upgrade

• To successfully upgrade from SAP HANA 1 you need to follow the mandatory steps in SAP Note 2372809 as:
• The metadata persistence layout has changed and
• An older column store persistence format has been deprecated and is not supported anymore and
• Multitenant Database Containers (MDC) have become default as the only operation mode. See SAP Note 2423367 for details
  
  
• See https://help.sap.com/viewer/product/SAP_HANA_PLATFORM/2.0.04/en-US --> SAP_HANA_Master_Guide, Version 2.0 SPS 07, chapters:
• Updating an SAP HANA System Landscape
• Prerequisites and Update Process
   
• From a technical perspecive, upgrading to a higher revision within the same SPS is the same as upgrading to a higher SPS or release.
  In all cases, the prerequisite for an upgrade is that every fix included in the source revision is also part of the target revision. 
  Some Revisions of a lower SPS are not allowed to upgrade to a revison of a higher SPS, as they contain more fixes in comparison.
  Please check SAP Note 1948334 for supported upgrade paths for SAP HANA, to ensure that the direct upgrade from your source revision is supported. 
  
  
• In case of problems with dropping global temporary tables please check SAP Note 2503043.
• For a troubleshooting guide for the SAP HANA Lifecycle Management Tool hdblcm, please see SAP Note 2078425. 

    For more information please refer to the items below:

• Please see SAP Note 2399995 - Hardware requirement for SAP HANA 2.0.
• For an overview of supported operating systems releases, see SAP Note 2235581 and the SAP HANA OS Release Support Matrix which is attached to it.
• For a list of additionally required operating system software packages, see SAP Note 2886607.
• Please see further information in the SAP HANA Product Availability Matrix - SAP HANA PAM.
  
  

General Remarks:

• If you are using SAP Web Dispatcher as HTTP load balancer, additional configuration is required - please see SAP Note 2146931.
• If you have scheduled a periodic database backup job with the DBA Planning Calendar (DB13) in a revision <= SAP HANA 2 SPS00, you might need to re-schedule the job after the upgrade. See SAP Note 2452552 for details.
• Attaching a debugger to HANA is only possible with installation of a special debug symbol build. In the unlikely event of requiring to debug HANA on your local system, debug symbol builds for all released revisions can be requested by creating an incident as it is not available for download by default.

Other Terms

[Enter your Other Terms here...]

Reason and Prerequisites

• Running the installation and the upgrade is only supported on a validated SAP HANA appliance and SAP HANA Tailored Datacenter Integration setup. 

Solution

If you upgrade from a lower SAP HANA SPS, it is recommended to upgrade the following components; Studio, Modeler, DB Clients, SLT, and DS to at least the minimal version of SAP HANA SPS 12. 
If you update the SAP Kernel version, please check the PAM – Technical Release Information – for the compatible SAP Kernel version. This SAP Kernel version also includes a compatible DBSL version.

Documentation

• See SAP Help Portal at https://help.sap.com/viewer/product/SAP_HANA_PLATFORM/2.0.05/en-US/ for the complete SAP HANA 2 SPS05 product documentation set.
• The SAP HANA 2.0 SPS 05 Feature Scope Description describes which features are available for the editions and options of SAP HANA.
  

Issues solved with this revision:

This Revision includes all fixes also included in previously released revisions of lower SPS (HANA 2 SPS04 Rev 048.00, HANA 2 SPS03 Rev 037.06, HANA 1 SPS 12 Rev 122.31). Please consult the respective release notes for details.

BW/OLAP

• [Issue number 230623] Fixed an issue that caused unexpected results for N:M join queries where join attribute cardinality times number of columns coming from right table exceeds 2^32.

• [Issue number 303582] Fixed an issue that could result in extended BW Query runtimes with long in-list filters in large distributed environments when utilizing the HANA Execution Engine (HEX).

Backup & Recovery

• [Issue number 299965] Fixed an issue which may have caused a HANA Instance with Extended Storage Service to fail with a crash during a PIT Recovery.
  See SAP Note 3349040 for details.

Database Client

• [Issue number 304695] Fixed an issue which led to an indexserver crash due to an unnecessary deallocation of out of memory scenarios.
  See SAP Note 3331598 for details.

Enterprise Search

• [Issue number 308028] Fixed an issue which caused unexpected results when using the 'NOT IN ROW' operator in ESH queries, like 'ROW:(NOT city:EQ(S):*)'.

• [Issue number 308047] Fixed an issue which may cause unexpected results when ESH queries involve searching for NULL values, such as '... AND ROW:(NOT col:EQ:*) ...'.

HDI/BAS

• [Issue number 302890] Fixed an issue which may have caused an indexserver crash at 'ltt::smartptr_handle<bimc::BimcElement> DeployUtils::findElement' when deploying models in HDI.

High Availability

• [Issue number 297660] Fixed an issue that CPU limitations have not applied correctly during technical consistency check (TCC) runs on secondary sites of HANA System Replication environments. This could have led to high CPU consumption on those sites while TCC runs were ongoing.

• [Issue number 299439] Fixed an issue where an error related to replication status persisted after disconnecting and reconnecting to the Disaster Recovery (DR) site in HANA Replication Services (HRS), even though the log replay had internally resumed.

• [Issue number 305077] Fixed an issue in which the automatic data volume reclaim may not have been effective on HANA system replication secondary sites.

Languages (SQL Script, R)

• [Issue number 302738] Fixed the issue that could cause SQLScript procedures to fail with the following error being written into the indexserver traces:

  "exception 1: no.1000000 (SQLScript/Executor/Dist/DistRequestHandler.cpp:343) TID: <TID>
  > Assertion failed: parent_ctx_handle->getPurpose() == Context::CreationPurpose::DeserializationFromClient"

Smart Data Access

• [Issue number 302710] Fixed an issue where a MDS query using the remote database could fail with the error message: "invalid character encoding".

Smart Data Integration

• [Issue number 304162] Fixed an issue which may have caused an internal deadlock when subscriptions on a remote source are altered.
  See SAP Note 3313320 for details.

• [Issue number 305050] Fixed an issue which may have caused a deadlock situation when the remote source got shut down.
  See SAP Note 3321717 for details.

• [Issue number 306966] Fixed an issue which may cause deadlock situation on DPserver on "DPFramework::cancelMessages" when SDI query gets cancelled.

• [Issue number 298941] Fixed an issue which could have caused the Data Provisioning Server to crash at  "TRexUtils::JsonAllocator::deleteAll".

Supportability

• [Issue number 302729] Fixed an issue that could lead to the generation of a PlanViz Trace to fail with errors like "Assertion failed: context_id_.second >= 0" when it comes to an internal integer logic overflow, under certain circumstances.

• [Issue number 303957] Fixed an issue in which a fullsysteminfodump did not collect backup.log nor backint.log files when log rotation was enabled for these kind of log files.

General

• [Issue number 285435] Fixed an issue that executing procedure "_SYS_STATISTICS"."ALERT_ADMISSION_CONTROL_ENQUEUE_EVENT" could have failed with a composite out of memory (oom) event.

• [Issue number 289241] Fixed an issue which may have caused an indexserver crash on long "ljit::types::ForeignStringT_equals_ForeignStringT" or unexpected results when the window function got queried.

• [Issue number 290890] Fixed an issue causing the indexserver to crash during the execution of "ptime::qo_Table::print_property" when gathering data for PlanViz or SQLOptStep trace analysis.
  See SAP Note 3216554 for details.

• [Issue number 295885] Fixed an issue that the activation or redeployment of an object (e.g. a view) could fail with error "Cyclic runtime dependency detected.;Found circular dependency of runtimes", if it had dependencies on objects of types flowgraph and procedure.

• [Issue number 299496] Fixed an issue that could have led to an unexpected result when using the HEXTORAW() expression converter during the processing of filters in the calculation view.

• [Issue number 299572] Fixed an issue which causes that more threads are active for executing an SQL Script procedure than allowed by the workload class mapping of the total statement thread limit.

• [Issue number 301486] Fixed an issue which may have caused a query on calculation view, including a window function, to fail with the error 'invalid number: attribute value is not a number'.

• [Issue number 301537] Fixed an issue which may cause a query failure with the error message: "temp index create error: [2999] general error (no further information available); $message$=unable to create itabindex.."

• [Issue number 301729] Fixed an issue that could have caused an indexserver crash at: "hex::operators::JsonTableOp::run(hex::RunContext)".

• [Issue number 301846] Fixed an issue in an exception handling (query cancelation or out-of-memory) within the CalculationEngine execution plan, which may have led to a memory leakage on allocators like:

  "Pool/JoinEvaluator/JERequestedAttributes/Results
  Pool/parallel/aggregates
  Pool/parallel/compactcol
  Pool/itab/VectorColumn
  Pool/itab"

  See SAP Note 2866563 for details.

• [Issue number 301955] Fixed an issue due to which there was a lack of information about the merge motivation and return code when delta merge fail with the error message:

  "Error in local merge: not enough merge tokens for delta merge or optimize compression : table = ..., merge motivation = ".

• [Issue number 302200] Fixed an issue that could have led to a memory leak on the allocator "Pool/JoinEvaluator/JERequestedAttributes/Results".

• [Issue number 302750] Fixed an issue that could have caused an indexserver crash when a field expression was used as an argument to an embedded function "SQL FUNCTION ()".
  See SAP Note 3301406 for details.

• [Issue number 303538] Fixed an issue which led to an indexserver crash at "Synchronization::Mutex::unlock" with an exception like "Mutex connStatMutex at xxx not locked when unlocking by context JobWrk00 at xxx ownerId xxx".
  See SAP Note 3337208 for details.

• [Issue number 303634] Fixed an issue that the indexserver could crash with exception throw location:

  "MemoryManager::SmallBlockAllocator::delayedDeallocate
  MemoryManager::MemoryPool::deallocate
  ptime::DynCachedView::LRUImpl::update"

  due to attempting to delete a block in memory, which has already been deleted.

• [Issue number 303932] Fixed an issue which could have led to an indexserver crash containing:

  "TRexCommonObjects::DocAttribute::setValue
  TRexCommonObjects::DocAttribute::append
  TRexCommonObjects::DocAttributeList::append"

• [Issue number 304288] Fixed an issue with slow delta fusion due to missing page prefetching for an .aux page chain (TEXT, GIS). This could lead to prolonged system startup times.

• [Issue number 304351] Fixed an issue which may have led to an indexserver crash when the number of XiDs was sent as 0 in the application or client library.

• [Issue number 304356] Fixed an issue which may have caused frequent delta merges of small tables.
  See SAP Note 3331435 for details.

• [Issue number 305585] Fixed an issue which may have caused an indexserver crash on "ljit::llang::LocalInterpreter::process(ljit::llang::InterpreterASTPtrInt64AddNode const*)" when executing a query with a stacked hash join.

• [Issue number 306508] Fixed an issue which could have led to an indexserver crash with an error message "error in Lfunction::runBlockOnSE", when using SQL Script.
  See SAP Note 3338120 for details.
• [Issue number 303777] Fixed an SQL performance issue related to SQL queries with CAST or SUBSTRING predicates when an argument of those SQL functions was a column of a remote data source and the ABAP VARCHAR mode was enabled.
  See SAP Note 3333831 for details.

• [Issue number 305736] Fixed an issue which could have led to an indexserver crash at "Control_switch::do_close_iterator" when using the Dynamic Cached.
  See SAP Note 3338104 for details.

• [Issue number 301404] Fixed an issue that could have resulted in a query containing the statement hint "CHECK_JOIN_CARDINALITY" to fail with the error message "[2]: general error: ; $condition$=logicalJoin->is_right_join_cardinality_to_one()".
  See SAP Note 3350455 for details.

• [Issue number 303533] Fixed an issue which may have caused an indexserver crash on "TRexCommonObjects::ValueIdMapper::~ValueIdMapper".

• [Issue number 307595] Fixed the issue that caused the following error messages to be written into the indexserver traces after upgrading to SAP HANA revision 070.00:

  "e PlanStability plan_stability_manager.cc(00124) : Error while initializing Plan Stability Manager: invalid column name"
  "e PlanStability plan_stability_manager.cc(00135) : failed to initialize manager; Cannot load plan map."