Symptom
After upgrading to SAP HANA 2.0 SPS06 or higher, ADSO activation fails with the following error:
Could not activate in step SAP HANA optimized activation
Serious error occurred: transaction rolled back by an internal error: generic. setColumns() is not allowed
Error during in-memory activation
The affected statement is a DML Statement (Update/Insert/Upsert) that is also visible in indexserver traces.
E.g.:
[75924] 2023-09-17 01:02:03.000000 SQL statement: UPDATE "SAPABAP1"."/BIC/A<ADSO name>2" SET "RECORDMODE" = ?, "RECORDTP" = ? WHERE "$rowid$" = ?,
exception 1: no.70041002 (BW_DataStoreObject/TableUpdate/DSOTableUpdateViaEAPI.cpp:189) TID: 92861
transaction rolled back by an internal error: generic. setColumns() is not allowed at ptime/query/plan_executor/dml/proc/qe_proc_trex.
Read more...
Environment
SAP BW systems on SAP HANA 2.0 SPS06 or higher
Product
Keywords
KBA , HAN-DB-ENG-BW , SAP HANA BW Engine , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.