Symptom
The indexserver of the SAP HANA database crashes in the method
"TrexTypes::OneBin<long>::fromBinaryString". Please check the
crash dump file for this expression.
Other Terms
NewDB, HANA, indexserver crash, MIN/MAX function, OLAP, query
Reason and Prerequisites
Reason:
Due to a programming error in the SAP HANA database a BW query with MIN/MAX functions on string keyfigures can lead to an indexserver crash in the method "TrexTypes::OneBin<long>::fromBinaryString".
Prerequisites:
Revision 27 or previous.
Due to a programming error in the SAP HANA database a BW query with MIN/MAX functions on string keyfigures can lead to an indexserver crash in the method "TrexTypes::OneBin<long>::fromBinaryString".
Prerequisites:
Revision 27 or previous.
Solution
This crash will be fixed in SAP HANA database Revision 28 and later.
As a workaround it is possible to use SQL-execution instead of HANA-optimized-Query access for single BW-Querys to bypass the database crash. Go to transaction RSRT and choose the technical Queryname. Push the button "Properties" and select "Operations ins BWA" = "0 No Operations in BWA". Please don't care about the word "BWA". It will also work for HANA. As soon as you switched to Revision 28 you can go back to "3 Standard" which will have some better performance.
As a workaround it is possible to use SQL-execution instead of HANA-optimized-Query access for single BW-Querys to bypass the database crash. Go to transaction RSRT and choose the technical Queryname. Push the button "Properties" and select "Operations ins BWA" = "0 No Operations in BWA". Please don't care about the word "BWA". It will also work for HANA. As soon as you switched to Revision 28 you can go back to "3 Standard" which will have some better performance.
Header Data
| Released On | 07.05.2012 14:42:19 | ||
| Release Status | Released for Customer | ||
| Component | HAN-DB SAP HANA Database | ||
| Other Components |
| ||
| Priority | Correction with medium priority | ||
| Category | Program error |
No comments:
Post a Comment