Online Tutorials & Training Materials |
Register Login

SAP HANA Database: Issue Solved with the Revision 60

15 Feb 2016 12:12 pm || 0

Issue Solved with the Revision 60 of SAP HANA Database

Stored procedure with cursor on a table on a different host might fail.

The indexserver trace file contains the following message:

"GenericFailure exception: column store error: [70000000] exception in LateMatColumnSource".

A memory leak becomes visible when OLAP queries with lot of query entries were executed. As a result the memory consumption of the pool Pool/malloc/ keeps constantly growing.

The indexserver trace file contains the following message:


INSERT statements which insert more data than can fit into a single packet into non-LOB-columns will fail with error 1033 ("error while parsing protocol").

Performance was improved for BW queries which have very unrestrictive fems0 filter and restrictive fems-N filters.

Decimal places of microseconds are not truncated anymore when transferring values of fields of type "timestamp(longdate)" from database layer to application layer.

Significant performance increase in data replication scenarios based on R3Load based on reorganization of database copy processes.

M_WORKLOADS is displaying inaccurate EXECUTE_COUNT values under high user load.

NEXTVAL is not considered during Upsert/Select join condition evaluation.

Fix NullPointerException during Decision Table creation in HANA studio.

The stack trace contains: ""

1. SAP HANA studio displays incorrect CODE_SIZE
2. Queries on m_service_memory returns incorrect CODE_SIZE
3. Total memory consumption of out of box HANA instance shows unexpected size
4.Licensing is checking incorrect memory consumption (due to in correct CODE_SIZE)

For more detailed descriptions please see SAP 1877480.

When failover happens on a distributed system, the slave node becomes master node but the SAP HANA Studio still points to the old master node, the following error occurs when trying to activate or copy models in studio:

"Error saving object: SAP DBTech JDBC: [1033]: error while parsing protocol: no such data type"

Wrong code generation of the MDEXISTS function might lead to the situtation that a master data entry is not found, which is actually present in the dictionary and master data table.

An indexserver crash might occur when the parallel dispatcher is trying to get job details.

The indexserver trace file contains the following message:

"ptime::ParallelFetchJob::getName() const."
An Indexserver crash might occur when the transaction abort method is not called. This occurs when the transaction times out during a table lock.
The indexserver trace file contains the following message:
"exception 1: no.2100002 (ptime/storage/cc/lock/ invalid trans_id in WaitGraph"
Select on table with varbinary column as part of partitioning key gives wrong results when varbinary value is used in where clause.
Selecting a calculation/analytic view may fail with the following column store error in the indexserver trace:
"Error during plan execution; Failed to find source column row.count in itab."
Workaround for HANA revisions < 60:
Set the indexserver parameter
instantiate_remove_transient = 0

Using analytic privileges on attributes of attribute views - which are itself being used within calculation views - can result in unexpected behaviour in terms of authorization issues. For instance, data access restrictions are not enforced or errors like #column store error: search table error: [2950] user is not authorized" may be shown.
This bug has likely shown up starting with HANA revision 48.
Fixed the out of memory situations for very complex script-based calculation views. This issue we improve already with Revision 57. For a more detailed description please see SAP 1852300.
Fixed: cannot debug stored procedures that use AFL library.
Fixed a stored procedure failure that has sql-filter pushdown with prepared statements.

The indexserver trace file contains the following message:

"cePlanExec cePlanExecutor.cpp() : Error during Plan execution of model SYSTEM:AGING_ENTITY_PROCVIEW (-1), reason: SYSTEM.AGING_ENTITY_AMOUNT:... not all variables bound exception: not all variables bound: [340] not all variables bound: unbound parameter : 0 of 3"
In a scale-out landscape internal tables are allowed to live until the connection is gone unless it is deleted from the point of creation.
Dropping transient temporary indices may lead to an error.

The indexserver trace file contains the following message:

"EmbeddedAPI : failed to cleanup temp indexes"
Local temporary tables are created when users issue requests against BIMC tables.
Metadata is now used to manage the tables.
The Index Server writes incorrect warnning message about NFS 4 file system to the log file.
For a more detailed description please see SAP Document 1866126
Count on restricted keyfigures in OLAP cubes with n:m joins is not working correctly.
A SQL query might fail in scale out system when splitted tables distributed across several nodes are joined together.

You will find the following error in indexserver alert trace:

"partition: search failed in :_SYS_SPLIT_~"
Filter pushdown for guided navigation doesn't work with currency conversion.

In some cases Statistic Server queries are stuck in an infinite loop. The call stack of the thread look similar to this:

1 : syscall+0x15
2 : Synchronization::BinarySemaphore::timedWait
3 : TrexSync::Event::waitFor
4 : Executor::X2::calculate(Executor::X2Statistics
5 :Executor::PlanExecutor::calculateX2
6 :Executor::PlanExecutor::calculate(
7 : ptime::TrexExecutor::calculate(ptime::Quey::result_t
8 : ptime::Query::result_t::open
9 : ptime::ResultSet::open_(bool, bool, bool
10 : ptime::Statement::execute_(bool, bool
11 : ptime::PreparedStatement::execute(bool, bool, bool, bool...

Query fails with out-of-memory when join_eval trace is set to DEBUG or INFO as >1000Tb get allocated.

The indexserver trace file contains the following message:

8: 0x00007f3c3bab1dce in JoinEvaluator::DictsAndDocs::dump(TrexTrace::TraceStream&, unsigned long) const+0x1ea at JEPlanData.cpp:1276 (
9: 0x00007f3c3bb1d850 in JoinEvaluator::JEUtils::
traceOutputs(char const*, unsigned int, ltt_adp::vector > const&, JoinEvaluator::JEPops::Pops)+0x360 at JEUtils.cpp:2411 (
Improving performance of statements with ALTER TABLE ... SET GROUP TYPE ... GROUP NAME ... GROUP SUBTYPE
A specific column view query with a calculation scenario on top fails due to huge results caused by missing filter push-down.

You will find the following error in indexserver alert trace:

"[1999] Error executing physical plan: exception 1999: TRexUtils/IndexHashMap.cpp:689 TRexUtils::IndexHashMapResizeException;in >executor::Executor in cube".

Running nested SQL statement to select distinct value from different tables and insert into one table may cause indexserver crash due to compression issue.

The indexserver trace file contains the following message:

AttributeEngine::fnGetAggregateMeasures, AttributeEngine::NspDocuments>
(AttributeEngine::SpValues, AttributeEngine::NspDocuments>&, int const*, unsigned long, char*, int, bool&, int*, int)

Fixed failure "Inconsistent calculation model (34011)" in stored procedure functions.

The indexserver trace file contains the following message:

Error: Function call 'expr::typecast_(RSFixed16, Int32)' does not match any of the 244 function overloads. Workaround: ALTER PROCEDURE RECOMPILE ...

CalcEngine ceManager.cpp(01260) : The following errors occured: Inconsistent calculation model (34011)".

Filtering a column using the string '' can result in the error message "error parsing lucene constraint: unmatched quotes".

A query against a specific column view with attribute mappings in a projection node failed, due to wrong attribute names in the calculation plan.

The indexserver trace file contains the following message:

"SAP DBTech JDBC: [2048]: column store error: search table error: [34051] Error during plan execution;Failed to find source column in itab."

The memory consumption of queries with grouping sets, but without calculated attributes, was too high since aggregations were not pushed down to the OLAPEngine.
Queries against calculation views may abort with the error" Failed to find column in input itab"

The indexserver trace file contains the following message:

"SAP DBTech JDBC: [2048]: column store error: search table error: [34051] Error during plan execution;Failed to find column in input itab"
When a batch insert with statement routing is executed via python then the slave nodes can not be determined if the table is hash(string)-partitioned. The corresponding hash function is not found and the calling statement returns false.

Fixed wrong environment for Storage Connector during add host operation in a distributed landscape.

Fixed potential Fiber Channel Storage Connector issue on persistent reservation acquisition (HANA was not able to start if this occurs).

Fixed: Statistics server is continuously throwing alerts "Join graph not connected; join not connected (HY000))" after the index server restarted from a crash.

Upgrade fails for a few Custom Storage Connectors.

The HANA upgrade shows an error message similar to this:

"Upgrade failed - error upgrading - Could not execute/parse ' sudoers ....
Output line 1: Program terminated with exit code 0"