Symptom
This is the SAP Release Note for SAP HANA 2.0 Database Revision 034 (2.00.034.00) of the SAP HANA platform software Support Package Stack (SPS 03).
Please refer to the following SAP Notes:
SAP Note 2380229 – SAP HANA Platform 2.0 – Central Note
SAP Note 2551355 – SAP HANA Platform 2.0 SPS 03 – Release Note
This is the central entry point for all information around SAP HANA Platform 2.0 Support Package Stack 03 (SPS 03), the comprised SAP HANA Revisions and subsequent SAP HANA Maintenance Revisions.
SAP HANA is available for Intel-Based Hardware Platforms and IBM Power Systems.
Please refer to the 2378962 SAP HANA 2.0 Revision and Maintenance Strategy document on SAP Service Marketplace for an overview regarding the SAP HANA revision and maintenance strategy.
In the SAP Software Download Center, you have access to the installation media and components for SAP HANA.
You can find the installation media and components for SAP HANA in the following locations on the SAP Software Download Center:
- “Installation media for an SAP HANA SP”
- “Support Packages and Patches for SAP HANA”.
For detailed information, see chapter “Software Download” in the SAP_HANA_Master_Guide.
Installation/Upgrade
With HANA Platform 2.0, the metadata persistence layout has been changed. Furthermore an older column store persistence format has been deprecated and is not supported anymore. Therefore you need to take some special attention before upgrading your existing SAP HANA Platform 1.0 system to SAP HANA Platform 2.0.
- A direct upgrade from SPS09 or lower version to SAP HANA Platform 2.0 is not supported.
- If you start your upgrade from an SAP HANA system in multiple-container mode (MDC) you first must upgrade to SAP HANA Database Revision 122.04 or higher.
Please read the guideline for upgrading an SAP HANA Platform 1.0 system to SAP HANA Platform 2.0 2372809 – Guideline for upgrading an SAP HANA Platform 1.0 system into SAP HANA Platform 2.0.
More information for updating an existing SAP HANA system can be found in the SAP_HANA_Master_Guide (Version: HANA Platform 2.0 SPS 03) in the chapters Updating an SAP HANA System Landscape, Prerequisites and Update Process and the following chapters on SAP Help Portal at https://help.sap.com/viewer/product/SAP_HANA_PLATFORM/.
In general, you can update your database from an SAP HANA Maintenance Revision / SAP HANA Support Package Stack (SPS) Revision to a higher SAP HANA SPS Revision / SAP HANA Maintenance Revision from a higher SPS by following the same procedure updating from one Revision to another Revision.
The prerequisite for an upgrade is that every fix included in the source revision is also part of the target revision.
As an exception for some Maintenance Revisions this prerequisite is not valid.
Some Revisions of a lower SPS are not allowed to upgrade to a revison of a higher SPS.
Due to incompatibility reasons, these Revisions of a lower SPS include more fixes than the SPS Revisions / Maintenance Revisions of the higher SPS, which had been produced earlier.
Please see for details SAP Note 1948334 – SAP HANA Database Update Paths for Maintenance Revisions.
Before you start the upgrade to this Revision, please see SAP Note 2428375 – Release Notes for SAP HANA Application Lifecycle Management for SAP HANA 2.0 SPS 01.
In case of problems dropping global temporary tables please check SAP Note 2503043 – Global temporary table could not be dropped.
Troubleshooting guide for the SAP HANA platform lifecycle management tool hdblcm.
Please see SAP Note 2078425 – Troubleshooting note for SAP HANA platform lifecycle management tool hdblcm.
General
Please see SAP Note 2399995 – Hardware requirement for SAP HANA 2.0
For an overview which HANA Database Support Package Stack (SPS) is supported on which Operating System (OS) Release, please refer to the
SAP Note 2235581 – SAP HANA: Supported Operating Systems.
As an attachment of this node you find the HANA SPS/OS Release – Support Matrix.
- 2455582 – Linux: Running SAP applications compiled with GCC 6.x
- 2292690 – SAP HANA DB: Recommended OS settings for RHEL 7.x
- 2205917 – SAP HANA DB: Recommended OS settings for SLES 12
Please see SAP Note 2684254- Recommended OS Settings for SLES 15
Please see further information in the SAP HANA Product Availability Matrix – SAP HANA PAM.
If you are using SAP Web Dispatcher as the HTTP load balancer, additional configuration is required.
Please see SAP Note 2146931 – Web Dispatcher – XSSRV – Initialization fails because access to topology information is forbidden.
If you have scheduled a periodic HANA Backup job with the DBA Planning Calendar (DB13) in an older HANA Revision, then you need to re-schedule this job after the Upgrade to HANA 2.0 SPS 01 (or higher) is completed. See SAP note 2452552 for details.
Multitenant database containers is the standard and the only operation mode. See SAP note 2423367 for details.
Other Terms
NewDB, in-memory database, Hybrid database, update, installation, HANA 2, SPS 03
Reason and Prerequisites
Running the installation and the update 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 update 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/ for the complete SAP HANA platform 2.0 SPS 03 product documentation set.
The SAP HANA 2.0 SPS 03 Feature Scope Description describes which features are available for the editions and options of SAP HANA.
Issues solved with this revision
BW/OLAP
Fixed an issue that performed rounding of “double/float” values before disaggregation when the target was set to 0 decimal places.
See SAP Note 2691805 for details.
Fixed an overflow issue that leads to an indexserver crash in the case of OLAP queries with FEMS filter and excessive parallelism.
See SAP Note 2690674 for details.
Backup & Recovery
Fixed an issue where “point-in-time” database recovery (system copy) using data snapshot and backint-based log backups failed with an error message informing that a log backup of the SYSTEMDB could not be found.
Fixed a Nameserver crash issue at “Backup::BackupCatalog_MemoryCatalog” During snapshot operation.
See SAP Note 2700356 for details.
Fixed an issue where, in the case where “log_mode” is changed to “overwrite” while “log_backup_interval_mode” is set to “service”, automatic log backups do not start after log_mode is changed back to “normal”.
Fixed the indexserver crash issue which occurred after the backup was canceled. The following back stack was written to the crashdump:
“[CRASH_STACK] Stacktrace of crash: (XXX)
—-> Pending exceptions (possible root cause) <—-
exception 1: no.2100002
unexpected exception type thrown
exception throw location:
1: Basis::DefaultCrashHandlers::abort(char const, int, char const)
2: ltt_extern::import::abort(char const, int, char const)
3: ltt::unexpected_handler()
4: std::terminate()+0x22 (libstdc++.so.6)
5: __cxa_call_unexpected+0x30 (libstdc++.so.6)
6: Backup::BackupSrc_Copier::verifyChannels(ltt::refcounted_handle &, ltt::refcounted_handle &, unsigned long)
7: Backup::BackupSrc_Copier::copySynchronousMultiplex(ltt::refcounted_handle &, ltt::refcounted_handle &, unsigned long, unsigned long, ltt::smartptr_handle const&)
….”
Capture & Replay
Fixed an issue that could have caused long preprocessing times when using the SYSTEMDB to preprocess capture files.
Data Provisioning
Fixed an issue which could have caused join of OData virtual tables by navigation property fail.
See SAP Note 2657932 for details.
Fixed an issue that could cause the error “unable to insert null in the column”. This occurred when deleting a row from a source table replicated by a reptask set to “Replicate with logical delete” or “Preserve All” when the target table had a non-null column without a default value.
See SAP Note 2679347 for details.
Fixed an issue which could have caused join of OData virtual tables by multiple columns fail.
See SAP Note 2679230 for details.
Fixed an issue that led to an OData Adapter error “year out of range while initializing timestamp” with DateTime string “endDate” :
“/Date(253402300799000)/” due to unsupported GMT+1 format.
See SAP Note 2689994 for details.
Enhanced SSL client certificate management.
Database Client
Fixed an issue which could, in some special cases, have caused a client failure (CORE Dumps being generated with function call “SQLDBC::Connection::updateTopology”), if a unexpected topology was sent from the server side to Hana’s client side.
Dynamic Tiering
Fixed an issue that could lead to failure of adding new host when the new host has different failover group from other hosts. You may see the following trace: “adding host ‘ ‘ failed as the test attach failed on , , .. , “.
Fixed an issue that could lead to errors connecting to SAN during a failover of the master node when Dynamic Tiering was used.
High Availability
Removed following confusing ‘connection refused’ error messages on secondary master host after master host has performed a failover on primary site: “error when sending request ‘dr_hasfailoverrunning’ to XXX.XXX.XXX.XXX:YYYYY: connection refused,location=XXX.XXX.XXX.XXX:YYYYY”.
See SAP Note 2685891 for details.
Fixed an issue which could have caused a crash in one of the services with ‘log position inconsistency detected’ after takeover.
See SAP Note 2691947 for details.
Fixed an issue where the JDBC client failed to connect to secondary site after a failover.
Fixed an issue regarding error message flooding in worker node indexserver after master node failover was done when table replication was enabled.
See SAP Note 2695510 for details.
Fixed an issue, which could happen on a secondary system at “DataAccess::RecoveryChannel::applyMetaData ()”.
The crash was caused by row store segment deletion, which could be related to a row store reorganization.
Installation/Upgrade
Fixed issues related to “_SYS_SR” user, where migration failed with the error “GRANT PUBLIC TO _SYS_SR BY SYS”.
Fixed an issue where during a HANA upgrade using HDBLCM, an Activation step failed on “HANA_XS_LM”, causing the upgrade to fail.
Fixed an issue which could have led to the adding host(hdblcm –addhosts) of second node failing when the “Fiber Channel Storage Connector” is used.
Languages (SQL Script, R)
Fixed an issue that could have caused error “column store error: import failed: [30111] Import failed (could not execute create statement);object=xxxxxxxxxxxxxx,return type mismatch: Procedure xxxxxxxxxxxxxx: Type “78” of attribute “xxxxxxxxxxxxxx not compatible to type “26” of attribute “xxxxxxxxxxxxxx”…” while importing or creating an SQLScript procedure.
Fixed an issue where the expression beneath exception handling was checked at compile time when it is supposed to be checked at runtime.
Live Cache
Fixed a potential deadlock between savepoint and livecache internal cleanup process which could lead to a system hang situation.
MDS
Fixed an issue in method “ptime::qo_Normalizer::evaluate_exp” which could have happened if a calculation view was queried with a very large number of filter conditions.
See SAP Note 2704395 for details.
Fixed an issue for MDS Hierarchy Member Requests that caused the error:
“unhandled exception -exception 75000001: Internal error during hierarchy operation” access to EmptyStringIsNull before initialization.
MDX
Fixed an issue when using the ‘lag’ method on a calculated member, where the calculated member is creating a new member, not shadowing an existing one. The error “‘plan operation failed;PopHierarchyExpressionMDX’ setCalculatedMemberInfos error” is no longer encountered and the expected NULL value is shown.
Fixed an issue where an MDX report wrongly aggregated the value of member formula twice.
Fixed an issue where the MDX query delivered unexpected results when TIME was a page key.
Fixed an issue that could lead to unexpected results when multiple hierarchies were used for a dimension and a CalculatedMember is defined for one of the hierarchies for this dimension and a dependent CalculatedMember is defined for another dimension.
Fixed an issue where restricted KeyFigures were delivering unexpected results from MDX perspective.
Fixed an issue that could lead to unexpected results when handling CalculatedMembers when they are used in hierarchy expressions of other CalculatedMembers.
Fixed precision issue in rounding for double calculations.
Planning
Fixed an issue which led to errors in transaction RSPLAN when executing a BW planning sequence using HANA PAK:
System error in program “CL_RSPLS_CR_CONTROLLER” and form “IF_RSPLS_HDB_CHECK_RES_HANDLER~HANDLE__IS_EMPTY-01”
PE error “34.023: Instantiation of calculation model failed”;”exception 306114: Cache node ‘00023_result_lookup_invalid’ “
Reason:
The level disaggregation command in the planning engine did not support the combination “DISAGGREGATE_DETAILS=1” and no “JOIN_ATTRIBUTES”.
Fixed an issue where a planning sequence execution failed with error: “Condition ‘getCalcScenario()->saveScenario()’ failed”.
Scale Out
Fixed a program issue which could in some rare cases lead to an indexserver crash on a slave node when a DDL is executed for a table residing on this slave node.
See SAP Note 2699968 for details.
Smart Data Access
Fixed an issue that Korean characters in the result set could have been truncated in case they were queried from a virtual table using a remote Adaptive Server Enterprise (ASE) database.
Fixed the indexserver crash issue with the following back stack in the crashdump:
“[CRASH_STACK] Stacktrace of crash: (2018-06-12 —-> Symbolic stack backtrace <—-
0: ltt::string_base<char, ltt::char_traits >::grow_(unsigned long) 04:47:27 954 Local)
1: ltt::basic_string<char, ltt::char_traits >::assign(char const*, unsigned long)
2: ptime::Proc_insert_sda::populateParametersInfo(ptime::Env&, void**, federation::FederationSqlGenerator , federation::Parameter) const
3: ptime::Proc_insert_sda::executeInsertAsArray(ptime::Env&, federation::FederationContext , federation::FederationSqlGenerator) const
4: ptime::Proc_insert_sda::operator()(ptime::Env&) const
5: ptime:: Query::_execute(Execution::Context&, ptime::Transaction&, char const , ptime::Query::Plan, ptime:: Query::param_t , ptime::Query::result_t, bool, bool)
…”
Text Search
Fixed an issue, which could have led to an indexserver crash at “AttributeEngine::FuzzyQueryTermMappingCombination::_fillTokenInfo()”, if a CONTAINS predicate was used.
See SAP Note 2701282 for details.
XS Engine
Fixed an issue that could cause an XS Engine crash at “httpclient::TupelList::get”.
General
Fixed an issue which could have led to repository objects not being migrated correctly during conversion from Single Database Container (SDC) to Multi Database Container (MDC). Activating objects which were affected by this could have failed with errors indicating missing privilege “REPO.EDIT_IMPORTED_OBJECT”.
Fixed an issue which could have led to a hdbcons crash if the relevant hdbcons commands were running in parallel.
Fixed an issue in which metadata of a view could be registered incorrectly when a view was created based on an XML file from another application.
Fixed an issue which caused the BW-System to become unresponsive. In some cases OOM situation could occur and the following kind of error message could be observed within the indexserver traces:
“e Row_Engine RetentionTableManager.cc(xxxxx) : failed to drop nologging table with retention period”
See SAP Note 2690620 for details.
Fixed an issue with a “datatype does not match” error when activating a calculation view which had a virtual table column of type big integer or fractional digits joining with a column table of the same type.
Fixed an issue where a Full Outer Join in unfolded calculation views might cause unexpected results for not null consuming input expressions.
Fixed an issue which generated a lot of warning messages in HANA traces: “Could not get some memory usage statistics from Cgroup, fetching from /proc/meminfo file”.
See SAP Note 2694985 for details.
Fixed an issue where invalid expression errors were returned when calculation views including mixed data types were activated.
Fixed an issue that could caused a long running table repartitioning due to an uneven distribution of threads on one node.
Fixed an issue which made queries on calculation views slow and blocked query plan unfolding when using input parameter with SQL language expressions.
Fixed an issue where “Pool/FRSWLockAllocator” and “Pool/CSRowLocking” consume a lot of memory because many “SeParamMapLock” ReadWrite lock objects are created.
Fixed an issue that caused the system startup to hang. In indexserver trace you see repeated entries like:
“i Service_Startup GlobalTransCommImpl.cpp() : Processing Slave_GetMasterLogPos for volume x
i Service_Startup GlobalTransCommImpl.cpp() : Finished processing Slave_GetMasterLogPos, lsn=0xffffffffffffffff”
See SAP Note 2668174 for details.
Fixed an issue where query execution failed with the following error:
“Fatal error: Execution flow must not reach here. See error trace for details.”
The following stacks could be observed in the indexserver trace files:
“1:ptime::qo_TrexSearch::add_aggr_col
2: ptime::qo_TrexSearch::gen_exec_trex_aggr
3:ptime::qo_TrexSearch::gen_exec_trex_for_single_index
4:ptime::qo_TrexSearch::gen_exec_plan_node”
Fixed an issue where the replay of redo logs was hanging when a delta merge or optimize compression was running while a rollback and a DDL statement were performed.
See SAP Note 2605215 for details.
Fixed a performance issue which could have led to an increased query runtime during the execution caused by metadata reads.
Fixed an issue which caused a huge number of threads and transactions to be opened by “check_table_consistency”.
See SAP Note 2697450 for details.
Fixed an issue which can lead to slow batch updates on tables via SQL view.
Fixed an issue where the creation of an SQL Script procedure failed with an error message like:
“SqlScript: Invalid parse tree: No such column .” The error occurred if the was a hidden column of a calculation view.
Improved the runtime of DDL statements on database objects with a high number of dependencies.
Fixed an issue, where repartitioning a table could lead to an indexserver crash at “TRexAPI::Partitioning::Allocator::partVecToDocIdVec”.
See SAP Note 2691084 for details.
Fixed an issue which could have led to an indexserver crash due to a coding issue in the DML layer, when some code could dereference index pointers without checking a null pointer.
Fixed an issue related to slow package authorization checks for findObjects. Solution is to cache already checked packages.
Fixed an issue which caused an indexserver crash on “ptime::SequenceManager::getCycle”. This occurred when trying to insert a sequence into an identity column.
See SAP Note 2691930 for details.
Fixed an export issue in SAP Support Mode where all the dependent objects were not exported if ” (“) is used in the creation script of the dependent objects.
Fixed an issue that could have led to an indexserver crash at “ptime::qo_position::set_position” when executing a SQL statement which combines an aggregation, a count distinct and an order by.
See SAP Note 2687785 for details.
Fix an issue which could lead to a crash when a statement contains UNION ALL which is done during GROUPING SET e.g.:
“SELECT * FROM (<select_with_grouping_sets#1>)
UNION ALL
SELECT * FROM (<select_with_grouping_sets#2>)”
Fixed an issue in unbalanced partitioning that could lead to ADD PARTITION commands failing with
“argument type mismatch: Partition X and Partition Y under same first level partition but not at same location”. A possible workaround is to completely repartition the table to the intended partition specification.
Fixed an issue where a unexpected object status was set for implicitly redeployed HANA repository objects, which were successfully revalidated.
Fixed an issue where query preparation times could take too long for higly partitioned tables.
Fixed an issue where query preparation times to collect table statistics for partitioned tables were taking a long time.
Fixed an issue when the ESX engine was used to fetch data from the full outer hash join.
See SAP Note 2696126 for details.
Fixed an issue which could have led to an indexserver crash due to the unexpected result type of “the typed_Integer function”.
See SAP Note 2696065 for details.
Fixed an issue related to the SQL engine which occurred when a restricted measure was used in a calculated column.
Fixed an issue that an SSL-related error during communication initialization could have led to an indexserver crash at “Synchronization::Mutex::lock / TrexNet::Responder::countRequestsBefore”.
See SAP Note 2706159 for details.
Fixed an issue which could have led indexserver crash due to calling “JobObjectForHandle::wait()” more than once while handling out of memory situation.
You may be able to see crash stack as below:
“[CRASH_STACK] Stacktrace of crash: (0000-00-00 00:00:00 00 Local)
—-> Pending exceptions (possible root cause) <—-
exception 1: no.1000000 (Basis/Execution/impl/JobExecutorImpl.cpp:000)
Wrong waiter state 0x0000000000000002 on job, expected DONE.; $condition$=barrier == DONETAG
exception throw location:
1: Execution::JobObjectImpl::wait(bool, bool)+0x406 at JobExecutorImpl.cpp:913 (libhdbbasis.so)
2: JoinEvaluator::JEStep2Impl::ReducerRuntimeData::~ReducerRuntimeData()+…
3: JoinEvaluator::JEStep2::executePopConst…
4: JoinEvaluator::JEPlanOperation::executePop…
5: Executor::X2::runPopTask…
6: Executor::X2::runPopJob(Executor::X2Job)+…
7: Executor::X2Job::run(Execution::Context&, Execution::JobObject&)+…
8: Execution::JobObjectImpl::run(Execution::JobWorker)+…
…”
Fixed an issue which could have led to an indexserver crash due to an unexpected exception thrown, other than SQLException from “ResultSet::close”.
The exception section is displayed below:
“[CRASH_STACK] Stacktrace of crash: (0000-00-00 00:00:00 000 Local)
—-> Pending exceptions (possible root cause) <—-
exception 1: no.1000002 (ltt/impl/memory.cpp:110)
Allocation failed ; $size$=00; $name$=xxx; $type$=pool; $inuse_count$=000000; $allocated_size$=000000000
exception throw location:
…
ERROR [SQL-591] internal error
exception 1: no.71000591 (ptime/session/eapi/jdbc/SQLException.cc:000)
SQLException
NO exception throw location recorded. Stack generation suppressed.
—-> Symbolic stack backtrace <—-
0: __GI_raise + …
1: __GI_abort + …
2: __gnu_cxx::__verbose_terminate_handler() + …
3: std::rethrow_exception(std::__exception_ptr::exception_ptr) + …
4: __cxa_bad_typeid + …
5: __gxx_personality_v0 + …
6: _Unwind_RaiseException_Phase2 + …
7: _Unwind_Resume + …
8: ptime::ResultSet::close(Execution::Context&, bool, bool, bool, bool) + …
…”
Fixed an issue which could have led to an indexserver crash at “config::ConfigMgr::ConfigMgr” when trying to start a tenant with high isolation level.
See SAP Note 2698812 for details.
Fixed an issue which occurred when moving empty partitions to extended storage. This which could lead to an error like
“SAP DBTech JDBC: [2561]: distributed metadata error: Failed to get table location during table lock….”
Fixed the indexserver crash issue with the following back stack in the crashdump:
“[CRASH_STACK] Stacktrace of crash: (XXX)
—-> Pending exceptions (possible root cause) <—-
exception 1: no.1000000 (TransactionManager/impl/Transaction.cpp:560)
Cannot reclaim the object while being used; $condition$=sub_trans->ref_counter_ == 0
exception throw location:
1:TransactionManager::Transaction::reclaimSubTransactionObject(TransactionManager::SubTransaction)
2:TransactionManager::SubTransaction::start()
3:ptime::SubTransactionWrapper::start(bool, bool, ptime::Transaction::ReadUpdateTrans, unsigned long, Newdb::TransToken)
…”
Fixed an issue where parsing an expression with a huge number of nested parentheses can run into a stackoverflow error.
Fixed an issue that could give unexpected result or a performance drop when executing a query because a filter condition was not pushed down properly.
Fixed an issue which could have caused an insert statement into a partitioned column store table to fail with error “[303]: invalid DATE, TIME or TIMESTAMP value: Error while parsing CURRENT_TIMESTAMP as TIMESTAMP at function typecast()”
See SAP Note 2690785 for details.
Fixed a column store issue “create index [2724] Olap temporary data size exceeded 31/32 bit limit” during the creation of index.
Fixed an unexpected rank value issue when using the “MACRO AUTHORIZATION” function.
Fixed an issue which could have led to an indexserver crash due to unexpected values passed to JoinEngine for size estimation.
The crash stack read as below:
“[CRASH_STACK] Stacktrace of crash: (2018-09-07 10:26:30 556 Local)
—-> Symbolic stack backtrace <—-
0: JoinEvaluator::CJEGraph::computeFullyRedDurats()+…
1: JoinEvaluator::CJEGraph::CJEGraph(JoinEvaluator::BitSet256 const&, JoinEvaluator::BitSet256 const&, JoinEvaluator::BitSet256 const&, JoinEvaluator::ColJoinEstimator const&, JoinEvaluator::MemPool &, ltt::allocator&)+…
2: JoinEvaluator::ColJoinEstimator::reductionCost(JoinEvaluator::BitSet256 const&, JoinEvaluator::BitSet256 const&, JoinEvaluator::BitSet256 const&, ltt_adp::vector<double, ltt::integral_constant<bool, true> >&)+…
3: JoinEvaluator::ColJoinEstimator::estimate(JoinEvaluator::BitSet256 const&, JoinEvaluator::BitSet256 const&)+…
…”
Fixed an issue of HANA1 to HANA2 migration on IBM power PC which was not supported.
See SAP Note 2696843 for details.
Fixed an issue which could have led to an indexserver crash at “PageAccess::PageFlushCallback::pageChunkWritten” with “Unexpected offset”, if striped data volumes were in use.
See SAP Note 2700123 for details.
Fixed an issue which occurred when executing “alter/drop sequence” which failed with “transaction rolled back by an internal error: net exception in thread xxxxx: NotAvailable//TransToken is invalid”. The issue affected systems with the running standby node/s only.
Fixed an issue which caused and indexserver crash which could not then be restarted. The root cause was that the container was deleted when there were still pending UNDOs on the container.
“exception 1:
Could not get table container for container id
exception throw location:
CSAccessor::Exception::TableContainerLoadException::TableContainerLoadException”
See SAP Note 2701165 for details.
Fixed an issue which caused a longer execution time. This occurred for a stored procedure with input parameters and the filter was applied at the remote location instead of local.
The solution is to push the INSERT SELECT SQL statement to the remote location.
Fixed an issue related to a DB hang situation at “ptime::SQLTrace::acquireBatchPrint” due to the unexpected exception handling.
Fixed a bug that causes no result. This was caused by the authorization filer of Analytic privilege which was not applied to the sub-view that was referenced in the calculation view.
软件组件
软件组件 自 至 以及后续
HDB 2.00 2.00
支持包补丁
软件组件 支持包 补丁级别 下载
SAP HANA CLIENT 2.0 SP003 000123
参考
该文档参考
编号 标题
877795 Problems with sapstartsrv from Release 7.00 and 6.40 patch 169
2706459 Numeric Overflow Error When Using SQL Function SUM() on a BIGINT Column of M_DISKS And M_VOLUME_SIZES System Views
2706159 Indexserver Crash at Synchronization::Mutex::lock / TrexNet::Responder::countRequestsBefore After SSL-Related Error During Communication Initialization
2701282 Indexserver Crash at AttributeEngine::FuzzyQueryTermMappingCombination ::_fillTokenInfo
2700356 Nameserver Crash at Backup::BackupCatalog_MemoryCatalog During Snapshot Operation
2700123 Indexserver Crash at PageAccess::PageFlushCallback::pageChunkWritten With “Unexpected offset”
2699968 Indexserver of a Slave Crashes When Replaying the log Triggered by CSAccessor::Redo::RedoHandler::redoDml
2698812 Crash at _crashImpl(char const , int, char const, ltt::exception const*) When Trying to Start a Tenant With High Isolation Level
2697450 Check Table Consistency Leads to Spawning a Huge Number of Threads While Table Load
2696843 Migration of HANA 1.0 on IBM Power Systems Big-Endian to SAP HANA 2.0 on IBM Power Systems Little-Endian Fails With HANA DI Server Missing
2696126 Indexserver Crash at ESX::HashJoin::fetch
2696065 Indexserver Crash due to Unexpected Result Type of type_Integer Function
2695510 With table replication, error message flooding in slave node indexserver after master node failed-over
2694985 Many Warning Messages “Could not get some memory usage statistics from Cgroup, fetching from /proc/meminfo file” in HANA Traces
2691947 Service Crash After Takeover With ‘log position inconsistency detected’ in SAP HANA System Replication Setup With Mode Delta_Datashipping
2691930 Indexserver Crashes With ptime::SequenceManager::getCycle When Inserting Sequence Into Identity Column
2691805 Unexpected Results In Planning Scenarios During Disaggregation
2691084 Indexserver Crash at TRexAPI::Partitioning::Allocator::partVecToDocIdVec While Repartitioning a Columnstore Table
2690785 Insert Into a Hash-Partitioned Column Store Table Fails With Parse Error in SAP HANA 2.0 SPS03
2690674 Indexserver Crash at OlapEngine::Parallel::ParallelHashMap::CompressFemsParallel During OLAP Queries with FEMs Filter Execution
