Skip to Content

Delta Merge Error in Hana 1.0 SP12

Hi All,

I am very new to hana from DB2 background and i have an issue please help

This query:

SELECT * FROM CTR_PARM WHERE CTR_PARM.PARM_SBJ IN ('BDV_AD_BH_PD_AC_TRSR','BDV_AD_BHS_PYMT_AC_RISK_CLASS') AND VAL_TP = 'S'

Delivers 2 rows while this query:

SELECT * FROM CTR_PARM WHERE CTR_PARM.PARM_SBJ IN ('BDV_AD_BH_PD_AC_TRSR','BDV_AD_BHS_PYMT_AC_RISK_CLASS') AND VAL_TP = 'S' AND PARM_CODE = 'FULL_LOAD'

Delivers 4 rows!!!!

We tried MERGE DELTA OF MD.CTR_PARM to make sure it was not a problem with the delta cache but this wasn’t successful:

MERGE DELTA OF MD.CTR_PARM

Could not execute 'MERGE DELTA OF MD.CTR_PARM' in 13 ms 467 µs . SAP DBTech JDBC: [2048]: column store error: merge delta index error: [2487] table optimization was not possible due to open metadata changes;delta merge

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jan 24 at 03:39 PM

    This is what i see in index server log ,

    There are duplicate column ids for table MD:CTR_PARM (t 28387) in metadata: [210 (2 occurrences)]. Merge not possible.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi jens ,

      what i see now is

      SELECT * FROM SYS.M_DELTA_MERGE_STATISTICS where table_name='CTR_PARM' ORDER BY START_TIME DESC;
      

      HOST;PORT;TYPE;SCHEMA_NAME;TABLE_NAME;PART_ID;HISTORY;MEMORY_MERGE;PASSPORT;START_TIME;EXECUTION_TIME;MOTIVATION;SUCCESS;MERGED_DELTA_RECORDS;LAST_ERROR;ERROR_DESCRIPTION hanasot01;33.103;MERGE;MD;CTR_PARM;0;FALSE;FALSE;;30-jan-2018 14:30:09.288;66;HARD;FALSE;0;2.048;column store error: [2487] table optimization was not possible due to open metadata changes hanasot01;33.103;SPARSE;MD;CTR_PARM;0;FALSE;FALSE;;30-jan-2018 14:29:52.375;14;HARD;FALSE;-1;2.048;column store error: [6939] AttributeEngine: commit() or rollback() was called without calling prepare() first hanasot01;33.103;RECLAIM;MD;CTR_PARM;0;FALSE;TRUE;;30-jan-2018 14:05:48.357;3;AUTO;TRUE;5.142;0; hanasot01;33.103;MERGE;MD;CTR_PARM;0;FALSE;FALSE;;30-jan-2018 14:04:48.022;5;AUTO;FALSE;0;2.048;column store error: [2487] table optimization was not possible due to open metadata changes hanasot01;33.103;SPARSE;MD;CTR_PARM;0;FALSE;FALSE;;30-jan-2018 13:57:23.613;16;HARD;FALSE;-1;2.048;column store error: [6939] AttributeEngine: commit() or rollback() was called without calling prepare() first hanasot01;33.103;SPARSE;MD;CTR_PARM;0;FALSE;FALSE;;30-jan-2018 13:18:37.476;20;HARD;FALSE;-1;2.048;column store error: [6939] AttributeEngine: commit() or rollback() was called without calling prepare() first hanasot01;33.103;RECLAIM;MD;CTR_PARM;0;FALSE;TRUE;;30-jan-2018 13:04:07.251;4;AUTO;TRUE;5.142;0; hanasot01;33.103;MERGE;MD;CTR_PARM;0;FALSE;FALSE;;30-jan-2018 13:03:06.903;6;AUTO;FALSE;0;2.048;column store error: [2487] table optimization was not possible due to open metadata changes

      Could not execute 'UPDATE MD.CTR_PARM WITH PARAMETERS ('OPTIMIZE_COMPRESSION' = 'FORCE')' in 23 ms 938 µs . SAP DBTech JDBC: [2048]: column store error: process parameters error: [6939] exception 6939: CS/OptimizeCompression/Helper.cpp:1059 AttributeEngine: commit() or rollback() was called without calling prepare() first

      No table lock as well and when i tried delta merge again it is still the same error

      Could not execute 'MERGE DELTA OF MD.CTR_PARM' in 9 ms 999 µs . SAP DBTech JDBC: [2048]: column store error: merge delta index error: [2487] table optimization was not possible due to open metadata changes;delta merge

      This is what i see in index server log

      [97330]{419348}[533/-1] 2018-01-30 14:29:52.389355 e optimize_compres Helper.cpp(01063) : changeRowOrder() failed with 'exception 6939: CS/OptimizeCompression/Helper.cpp:1059 AttributeEngine: commit() or rollback() was called without calling prepare() first (6939)' (table=MD:CTR_PARM (t 28387), passport=)

  • Jan 25 at 12:41 PM

    Did you recently import this table into HANA?

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 29 at 11:25 AM

    Nope Michael but what i see from the Log file is it is happening for a long time , thanks

    Add comment
    10|10000 characters needed characters exceeded