Академический Документы
Профессиональный Документы
Культура Документы
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
HANA ADMINISTRATION
HOW TO
PERFORMANCE
RECOVERY
25%
25%
Comprar
Comprar
CATEGORIES
Sap Hana Administration
Sap Hana Backup
Sap Hana Restore
Sap Hana MultiTenant
Database
Sap Hana Upgrade
Sap Hana Installation
Sap Hana Parameters
Sap Hana Replication
SapStartSrv Functions
Sap Hana troubbleshooting
guide
Sap Hana -List Of Upgrade
issues
Sap Hana -Most frequencty
Used sql Commands
Sap Hana -What's New ?
Sap Hana -New System
Views
Sap Hana Performance
Tuning
Sap Hana Quiz
Sap Hana Interview
Questions and Answers
1/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
Adsby Google
SapHanaBW
Also see
SapHanaintheCloud
RECOVERY
Search
102.04
SAP HANA INTERVIEW QUESTIONS
CONTACT US
2242726 SAP HANA SPS 10 Database Maintenance Revision
102.03
ARCHIVES
October 2016
September 2016
August 2016
July 2016
June 2016
March 2016
This is the central entry point for all information around SAP
HANA Platform Support Package Stack (SPS 10), the
comprised SAP HANA Revisions and subsequent SAP HANA
Maintenance Revisions.
February 2016
October 2015
December 2015
November 2015
September 2015
August 2015
July 2015
June 2015
Before you start the upgrade from Revision 64, 65, and 66.
Pleasecheck outSAP Hot News Note 1918267.
As part of the installationor the upgrade to Revision 101 or
higher the master key of the secure store in the le system
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
2/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
If you are using SAP HANA live, please check Release Note
1778607 before you start upgrading to SPS 10.
Before you start the upgrade to this Revision, please check
out SAP Note2159899 Release Notes for SAP HANA
Application Lifecycle Management for SAP HANA SPS 10.
In order to run the SAP HANA Database Revision 80 (or higher)
on SLES 11, additional operating system software packages
are required.
RECENT COMMENTS
RECOVERY
Mohammed Khan on
[Solved] FAIL: process
hdbdaemon HDB
Daemon not running in
SAP HANA
General
3/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
statistics
server asQUESTIONS
of Revision 94.
SAP HANA
INTERVIEW
CONTACT US
Please note that when the Embedded Statistics Server is
used, some program changes are required in the ABAP
monitoring tools. See SAP Note 1925684 for details.
If the recovery ofdata without using the backup catalog fails
with incorrect syntax near USING,please check out SAP
Note 2157184.
If you are using SAP Web Dispatcher as the HTTP load
balancer, additional conguration is required. Please see SAP
Note 2146931 for details.
If you have problems creating or modifying a user in the SAP
HANA web-based development workbench, please check out
SAP Note 2183760.
If you are using the SAP HANA cockpit delivery unit
HANA_ADMIN Version 1.3.9, the start, killing, andstopping of
services do not work properly, even if successfully reported.
Please check out SAP Note 2182831.
Pleasenote that the virtual table function is currently not
supported on multitenant databases. Please check out SAP
Note 2182597.
The version of libnuma1 (library for Non-Uniform Memory
Access) delivered with SLES 11 SP1 up to versionlibnuma12.0.3-0.4.3 contains a bug which causes the name server to
crash. Please check out SAP Note 2132504.
You can nd information about SHINE (SAP HANA Interactive
Education) demo content in SAP Note1934114.
You can nd documentation corrections information for the
SAP HANA optionAdvanced Data Processing in SAP Note
2183605.
Introduced a new security feature to congure if the SYSTEM
user is locked due to too many failed connect attempts.
The new parameter password_lock_for_system_user in
section [password_policy] of le indexserver.ini (or
nameserver.ini for the system database of a multiplehttp://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
4/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
Other Terms
NewDB, in-memory database, Hybrid database, update,
installation, SPS 10
Solution
If you upgrade from a lower SAP HANA SPS, it is recommended
to update ALL other components (Studio, Modeler, DB Clients,
DBSL, SLT, DS, ) to at least the minimal version of SAP HANA
SPS 10.
Documentation
5/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
CONTACT US
6/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
7/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
2:
DataAccess::ReplicationProtocolSecondaryHandler::createTCBforRestartSessions
3:
DataAccess::ReplicationProtocolSecondaryHandler::buildOpenSessionList
4:
DataAccess::ReplicationProtocolSecondaryHandler::preloadTables.
Fixed the issue that takeover to the standby node did not
happen and the landscape was broken until a failed host was
working again when a tenant catalog master was not located
on the master node and a none master node failed in a
HANA ADMINISTRATION
HOW TO
PERFORMANCE
MultiDB scenario.
Languages
(SQL Script,QUESTIONS
R, River)
SAP
HANA INTERVIEW
RECOVERY
CONTACT US
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
8/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
Security
RECOVERY
M_CONNECTIONS.
Selecting this view resulted in the error message invalid
SAP HANA INTERVIEW QUESTIONS
CONTACT US
character encoding.
Text search
9/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
namespace)::LCodeArgumentWrapper::~LCodeArgumentWrapper()
2: expr::Evaluator::Dispatch<46>().
Fixed an indexserver crash. The error stack was:
ptime::NBaseString:_clone.
Fixed an issue that could cause a corruption leading to a
crash with the following crashstack during table access:
exception 1: no.1000000
Orphaned timestamp TS[tcbidx=2147483647,ssn=any];
$condition$=tcb
HANA1:ADMINISTRATION
HOW TO
PERFORMANCE
RECOVERY
TransactionManager::TransactionControlBlockFactory::getTimestampState
2:
TransactionManager::ConsistentView::isTransactionCommitted
SAP HANA
INTERVIEW QUESTIONS
CONTACT US
3:
TransactionManager::ConsistentView::isTimestampRangeVisible
4: DataContainer::FileIDMapping::isVisible.
Fixed a bug where the Table Consistency Check could
consume too much memory and result in a OOM situation and
a performance problem.
Improved performance for inserts into global temporary
column tables.
Fixed an indexserver crash with the following call stack:
joinEvaluator::SearchAlgorithm::expand().
Fixed an issue in NUMA awareness. The issue was visible with
the following trace message, but did not harm the system:
libnuma: Error: mbind: Invalid argument.
Fixed an issue with delta merge handling, which could have
resulted in high amount of no longer needed UDIV/MVCC
data in the main memory of column store attributes not being
released, even if the number of rows in the main-memory was
not high.
Fixed a crash by terminating the corresponding SQL
statement instead of crashing the indexserver. The
corresponding call stack was the following:
1:MemoryManager::BigBlockAllocator::addFreeBlock().
Reduced compilation time for SQL statements with
large/complex expression lists.
Most of the time was spend in the check for duplicate
aggregation using trex expression.
Fixed insucient performance for SELECT queries on
SYS.GRANTED_PRIVILEGES.
Fixed an out of memory situation that could occur when a
primary key or a secondary index on existing, large column
store tables was created. A typical scenario where this could
have happened was a part of a data migration.
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
10/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
2: ptime::Qc2QoConverter::convert_relation_project_record().
Fixed a bug which could lead to obsolete memory and cpu
consumption baused
on the calculation
HANAresource
ADMINISTRATION
HOWby
TOa query PERFORMANCE
model because a stacked qoPop was generated.
Fixed the inconsistent status of the result view of procedures
RECOVERY
after an
upgrade. QUESTIONS
SAP HANA
INTERVIEW
CONTACT US
Fixed an issue that original snapshots failed and
inconsistencies were reported when the snapshot directory
was cleared incorrectly after a snapshot was opened for
secondary.
Reduced CPU usage on function calls like JoinEvaluator
jeReadIndex or SQL optimizer estimations
(prefetchSampleData). Kernel Proler traces revealed that a
high amount of CPU time was spent on
generateOLAPBitmapMVCC.
Fixed an issue in the XS Job Dashboard that did not allow to
add parameter values including a : to a schedule.
Fixed an issue in the XS Job Dashboard that preveted show
schedules for jobs that are referencing .hdbprocedure objects
from being shown.
Fixed a bug that allowed invalid date values to be inserted
into HANA tables. These values could lead to the error
AttributeStoreFile error TABLEattribute_204.bin: attribute
value is not a date or wrong syntax; failed with rc 6931
when loading the table subsequently.
Fixed a crash that could occur when a query was run against a
calcview.
The crash stack was as follows:
-> Symbolic stack backtrace <0: OlapEngine::BwDocids::prepareMdDocIdsForMain()
1: OlapEngine::BwDocids::getDocids()
2: OlapEngine::BwPopJoin12::executePop.
Fixed a crash with the following call stack:
[CRASH_STACK] stacktrace of crash: (0000-00-00 11:11:11 111
Local)
-> Pending exceptions (possible root cause) <exception 1: no.1000000 (Basis/Container/SafePointer.hpp:91)
Assertion failed: (oldValue & RESET_BIT) == 0
exception throw location:
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
11/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
1: 0x00007fbb97499c38 in
Container::SafePointerHolder<ptime::Statement>::reset()
2: 0x00007fbb974fb53b in ptime::EntryStatementInfo::set
3: 0x00007fbb974fb592 in
ptime::Connection::setEntryStatement_
4: 0x00007fbb97521bfa in ptime::EntryStatementScope::reset()
5: 0x00007fbb97537dc1 in ptime::Statement::compile_.
RECOVERY
plan execution;Cannot
nd column CONTACT US
SAP HANA
INTERVIEW QUESTIONS
DISCOUNT_AMOUNT$sum$ in input itab.
Fixed a performance issue caused by slow ltering on
DDIC_NUMC elds due to non optimized search method was
used.
Fixed a bug which caused an indexserver crash when
SQLScript procedures with DDL statements were called in
parallel.
The following assertion could be found in the crashdump:
Pure virtual function called, block=MemoryBlock block:
Deallocated block
1: __cxa_pure_virtual
2: TRexCommonObjects::InternalTableBase::size() const
3: ptime::Query::Plan::clear_temp_indexes().
Fixed an indexserver crash that was triggered by a query on
top of a calculation view. The crash stack contained the
following entries:
2ptime::qo_Exp::clone_subtree
ptime::qo_Normalizer::getExpForPlaceholders
TrexCalculationEngine::QueryEntryToQoTranslator::getExpFromQueryEntryConstVal
TrexCalculationEngine::QueryEntryToQoTranslator::translateTerm
TrexCalculationEngine::QueryEntryToQoTranslator::translateQueryEntry
TrexCalculationEngine::QueryEntryToQoTranslator::translate
TrexCalculationEngine::ceQOBuilder::buildPostFilter
TrexCalculationEngine::ceQOBuilder::buildNode
TrexCalculationEngine::ceQOBuilder::build
TrexCalculationEngine::ceQOExecutor::execute
TrexCalculationEngine::ceQoPop::executePopInternal
TrexCalculationEngine::ceQoPop::executePop.
Fixed the crash caused by the query that used GROUPING
SETS over UNION ALL on OLAP views.
Fixed an out of memory issue when a prepared like lter was
used.
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
12/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
AttributeEngine::BTreeAttribute<TrexTypes::IntAttributeValue>::bwGetValueIdsFromValues().
an issue in the area of
dataTO
aging which
could lead to
HANAFixed
ADMINISTRATION
HOW
PERFORMANCE
RECOVERY
incorrect results returned from a SELECT query with WHERE
conditions on key attributes.
PleaseINTERVIEW
refer to SAPQUESTIONS
Note 2206359 for CONTACT
details.
SAP HANA
US
Fixed a bug in the OLAP engine that could have resulted in
the column store error:
search table error: [2620] executor: plan operation
failed;GroupByColumnSetter skip,BwPopJoin1Inwards.
Improved tracing to analyze the error 2434: join index
inconsistent; Invalid schema: Invalid table for index.
Introduced a proper error message when the default schema
specied in the JDBC connection string does not exist.
Fixed an indexserver crash with the following call stack:
[CRASH_STACK] Stacktrace of crash: ()
-> Symbolic stack backtrace <0: qo3::OptimizerImpl::initializeInListNode()
1: bool
qo3::OptimizerImpl::initialTree<TRexCommonObjects::QueryEntry>
()
2: qo3::OptimizerImpl::prepare()
3: qo3::Optimizer::prepare().
Tables containing colums with string-like types (VARCHAR,
NVARCHAR, VARBINARY), where all the data in these columns
is of the same length, could take long to merge due to
suboptimal coding. The coding has been improved and
merges are now fast.
Removed incorrect/ignorable trace entries related to
metadata handling. These could have resulted in index server
trace le entries during startup like:
catalog.cc(04301) : [OID] wrong oid is set from objectinfo oid
:72057594044083712.
Fixed the fatal error: ColDicVal (0,0) not found error, which
was caused by wrong column information being generated
for column aggregation during query plan generation.
Improved the startup time of the index server service when
many in-memory sequences needed to be initialized with new
startup values.
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
13/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
2: Synchronization::CondVariable::wait()
3:
SAP HANA INTERVIEW QUESTIONS
CONTACT US
TRexUtils::Parallel::__indexHash<IndexHash<TrexTypes::StringAttributeValue>
4:
TRexUtils::Parallel::__indexHash<IndexHash<TrexTypes::StringAttributeValue>
5: TRexUtils::Parallel::JobBase::run()
6: Execution::JobObjectImpl::run()
This hang only happened when the corresponding SQL
statement was running into an OOM before by running either
into GAL or a user dened statement memory limit.
Crash in Execution::JobWorker::enterWait: Fix avoids false
detection of sysWaiting worker threads when theres lock
contention
between setting this ag and actually calling the run method,
for example transaction handling.
TrexViaDbsl: rethrow caught exceptions. An OLAP query leads
to metadata inconsistency. If the TrexViaDbsl does not ignore
the caught exception, commit will not be issued, and the
metadata will not be corrupted.
TrexViaDbsl continues to catch exceptions in order to write
error messages in trace le, but throws them again now.
Fixed a sporadic crash when using Smart Data Access and it
attempts to create an attribute denition for a rowid column.
The crashstack will contain,
ptime::FederationQuery::convertCIStoITab.
References
This document refers to:
SAP Notes
2210637
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
14/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
2184635
2184536
2184376
2183648
RECOVERY
2183624
2183500
2183363
2183246
2182831
2182779
2182597
2159899
2157184
2135596
2135443
2135097
2132504
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
15/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
2130083
2119442
2106836
2104798
RECOVERY
Container fails
SAP HANA INTERVIEW QUESTIONS
CONTACT US
2099820
MOPZ missing product instances::MOPZ
does not nd HANA Addon Products
2099661
2099489
2099478
2078425
2072211
2068807
2066903
2066313
2056079
2054883
2053116
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
16/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
2052914
2045050
2039810
2039085
PERFORMANCE
RECOVERY
2032600
2025702
2023669
2023163
2022779
2022747
2021789
2014334
2001528
1998966
1963779
1962287
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
17/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
name
1957136
1952701
1948334
HANA
ADMINISTRATION
HOW TO
1934114
SAP HANA DEMO
MODEL PERFORMANCE
SHINE Release &
Information Note
RECOVERY
1925684
ABAP adjustments for the new Embedded
SAP HANA INTERVIEW QUESTIONS
CONTACT US
Statistic Server
1918267
1898497
1795885
1778607
1710832
1666976
1523337
1514967
38%
Chamarra Puma Footb
$619
VER MS
22%
Short Nike Cool
$349
VER MS
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
18/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
Share 0
Like
Related Posts
HANA ADMINISTRATION
Tweet
HOW TO
PERFORMANCE
RECOVERY
19/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
20/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
RECOVERY
Leave a Reply
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
21/22
3/1/2017
2193110SAPHANASPS10DatabaseRevision102SapHanaWiki
Enteryourcommenthere...
HANA ADMINISTRATION
HOW TO
PERFORMANCE
RECOVERY
CONTACT US
http://www.saphanawiki.com/2015/09/2193110saphanasps10databaserevision102/
22/22